12/17/2014

ShareTechnote

BasicCallProcessingTypicalPacketCallHome:www.sharetechnote.com

Inthissection,IwillgothroughatypicalprotocolsequenceofLTEpacketcall.Thiswillbethebackbonestructurefor
allothercallprocessing.
BasicStateMachine
BigPictureFirst
ChannelMappingTablethroughoutCallProcessing
CellConfigurationandChannelConfigurationduringCallProcessing
NowinVeryDetailedPicture
OverallComparisionwithWCDMA
InterimComments

FollowingistheoverprotocalsequencebeingexchangedbetweenUEandNetwork.Actuallyunderstandingallthe
detailsofthesestepswouldbethegoalofyourwholeLTEcareer.

1)<CellSearchandDetection>
2)MIB
3)SIB1
4)<CheckCellSelectionCriteria>
5)SIB2andotherSIBs
6)RRC:PRACHPreamble
7)RRC:RACHResponse
8)RRC:RRCConnectionRequest
9)RRC:RRCConnectionSetup
10)RRC:RRCConnectionSetupComplete+NAS:AttachRequest+ESM:PDNConnectivityRequest
11)RRC:DLInformationTransfer+NAS:AuthenticationRequest
12)RRC:ULInformationTransfer+NAS:AuthenticationResponse
13)RRC:DLInformationTransfer+NAS:SecurityModeCommand
14)RRC:ULInformationTransfer+NAS:SecurityModeComplete
15)RRC:SecurityModeCommand
16)RRC:SecurityModeComplete
O1)RRC:UECapabilityEnquiry
O2)RRC:UECapabilityInformation
O3)ESM:ESMInformationRequest
O4)ESM:ESMInformationResponse
O5)EMM:EMMIdentityRequest
O6)EMM:EMMIdentityResponse
17)RRC:RRCConnectionReconfiguration+NAS:AttachAccept+NAS:ActivateDefaultEPSBearerContextReq
18)RRC:RRCConnectionReconfigurationComplete+NAS:AttachComplete+NAS:ActivateDefaultEPSBearer
ContextAccept
O7)EMM:EMMInformation
19)RRC:RRCConnectionRelease
20)<PerformNeibourcellMeasurement>
21)<CheckCellReselectionCriteria>
22)<MOorMTcall>:InMTcall,Pagingshouldbesent.
23)RRC:PRACHPreamble
24)RRC:RACHResponse
25)RRC:RRCConnectionRequest
26)RRC:RRCConnectionSetup
27)RRC:RRCConnectionSetupComplete+NAS:ServiceRequest
28)RRC:SecurityModeCommand
29)RRC:SecurityModeComplete
30)RRC:RRCConnectionReconfiguration+NAS:ActivateDedicatedEPSBearerContextRequest
31)RRC:RRCConnectionReconfigurationComplete+NAS:ActivateDedicatedEPSBearerContextAccept
32)RRC:RRCConnectionRelease

BasicStateMachine

FollowingdiagramshowsapossiblestatemachinethataUEwouldgothrough.Thestatetransitioninthispostwillbe
about(s0)>(a)>(b1)>(c1)>(d1)>(e1)>(f1)>(g1)>(h1).Mostofothertransitionwillbedescribedin
"Handover"page.

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

1/38

12/17/2014

ShareTechnote

NoteforStep23)~32):IntialRegistrationandDefaultEPSBearerSetupprocedurewouldbecommontoalmostall
LTEnetwork.Ofcourse,therewouldbeasmallvariationsbutoverallconceptwouldbealmostsame.Butthe
procedureafter<Idle>(Step23~32)wouldbequitedifferentamongNetworkOperators.Followingwouldbetwo
majorvariations.
SetupRRCConnection,RRCConnectionReconfigurationwithoutcreatinganydedicatedEPSBearer.(Inthiscase,
UEusestheexistingDefaultEPSbearerfortraffic).
SetupRRCConnection,RRCConnectionReconfigurationwithadedicatedEPSBearer.(Inthiscase,Ueusesthe
existingDefaultEPSbearerorDedicatedEPSBearerdependingonsituation).
Theexampletestsequenceinthiscaseshowsthesecondcase,

BigPictureFirst

DependingonwhichlevelyouareworkingoninUEdevelopment/Testprocedure,theamountofknowledgeyouneed
toknowwouldbedifferent.ButIthinkthereareacoupleofbigpicturesthatmayhelpalmostanybodyworkingin
fullprotocolstack.

FirstbigpictureIwouldliketointroduceisthechannelmappingasshownbelow.JusttrytopickanyRRCmessages
andtrytofollowthearrowforthemessage.IfyoureadthosepagesaboutMACandRLC,itwillremindyouofalot
ofdetailedinformation.

<<OverallSequenceandLayerMapping>>

Followingisasequencediagramshowingnotonlythemessagebutalsobasicconfigurationsofeachlayer.More
detaileddescriptionofeachlayerinthecontextoffullprotocolstackwillbeexplainedin"FullStack"section.

Justreadthroughthissequencewheneveryouhavetimeuntilyoucanduplicatethesequencewithoutlookinginto
thisagain.Thiscanbeagoodframeworkforyourstudyandgoodguidefortroubleshooting.

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

2/38

12/17/2014

ShareTechnote

<<DownlinkChannelMap>>

Thediagramyousawaboveakindofmessageflow(eventdiagram)intimesequence.Thediagramshownbelowis
notatimebased,butitshowsthechannelmapping(ordataflowacrossthefullprotocolstack).Pickoneofthe
messagefromthediagramshownaboveandtrytofindrightrouteforthisdigramandseehowmuchdetailsyoucan
add.
Forexample,ifyoupickedthemessage"RRCConnectionSetup",thestartpointwouldbe"RRCMessagemsg4".

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

3/38

12/17/2014

ShareTechnote

FollowingisatabularpresentationofDLChannelMap.(LCIDandTrCHNumberwouldbedifferentdependingonthe
networkorNetworkSimulator)

RB

LoCH

PDCP

RLC

LoCH

LCID

MACHdr

HARQ

RNTI

TrCH

PCCH

TM

PCCH

N/A

NONE

NONE

NONE

PCH

BCCH0

TM

BCCH0

N/A

NONE

NONE

NONE

BCH0

BCCH1

TM

BCCH1

N/A

NONE

Broadcast

SIRNTI

DLSCH0

TM

RA_RES

N/A

NONE

NONE

RARNTI

DLSCH1

SRB0

DLCCCH

RA_RES

USED

TM

DLCCCH

NONE

NORMAL

TCRNTI

DLSCH1

SRB1

DLDCCH0

USED

AM

DLDCCH0

NORMAL

NORMAL

CRNTI

DLSCH1

SRB2

DLDCCH1

USED

AM

DLDCCH0

NORMAL

NORMAL

CRNTI

DLSCH1

DRB0

DLDTCH0

USED

UM/AM

DLDTCH0

NORMAL

NORMAL

CRNTI

DLSCH1

DRB1

DLDTCH1

USED

UM/AM

DLDTCH1

NORMAL

NORMAL

CRNTI

DLSCH1

DRB2

DLDTCH2

USED

UM/AM

DLDTCH2

NORMAL

NORMAL

CRNTI

DLSCH1

<<UplinkChannelMap>>

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

4/38

12/17/2014

ShareTechnote

FollowingisatabularpresentationofDLChannelMap.(LCIDandTrCHNumberwouldbedifferentdependingonthe
networkorNetworkSimulator)

RB

LoCH
RA_PRE

PDCP

RLC

LoCH

LCID

MACHdr

HARQ

RNTI

TrCH

TM

RA_PRE

N/A

NONE

NONE

NONE

ULSCH0

SRB0

ULCCCH

USED

TM

ULCCCH

NONE

NORMAL

TCRNTI

ULSCH0

SRB1

ULDCCH0

USED

AM

ULDCCH0

NORMAL

NORMAL

CRNTI

ULSCH0

SRB2

ULDCCH1

USED

AM

ULDCCH0

NORMAL

NORMAL

CRNTI

ULSCH0

DRB0

ULDTCH0

USED

UM/AM

ULDTCH0

NORMAL

NORMAL

CRNTI

ULSCH0

DRB1

ULDTCH1

USED

UM/AM

ULDTCH1

NORMAL

NORMAL

CRNTI

ULSCH0

DRB2

ULDTCH2

USED

UM/AM

ULDTCH2

NORMAL

NORMAL

CRNTI

ULSCH0

ChannelMappingTablethroughoutCallProcessing

ThisisonlyanexamplecaseandMapping(especiallLoCHNo)canvarydependingonsituations.Thepointisthatit
willbereallyhelpfulforyourtroubleshootingortestcasecreationifyoucreatethiskindoftableforyourcase.

Message

RB

LoCH

LoCHNo

LCID

MIB

BCCH

SIB1

BCCH

SIB2

BCCH

RRC:PRACHPreamble

RRC:RACHResponse

RRC:RRCConnectionRequest

SRB0

ULCCCH

RRC:RRCConnectionSetup

SRB0

DLCCCH

RRC:RRCConnectionSetupComplete+NAS:AttachRequest+ESM:PDNConnectivityRequest

SRB1

ULDCCH

RRC:DLInformationTransfer+NAS:AuthenticationRequest

SRB1

DLDCCH

RRC:ULInformationTransfer+NAS:AuthenticationResponse

SRB1

ULDCCH

RRC:DLInformationTransfer+NAS:SecurityModeCommand

SRB1

DLDCCH

RRC:ULInformationTransfer+NAS:SecurityModeComplete

SRB1

ULDCCH

RRC:SecurityModeCommand

SRB1

DLDCCH

RRC:SecurityModeComplete

SRB1

ULDCCH

RRC:RRCConnectionReconfiguration

SRB1

DLDCCH

RRC:RRCConnectionReconfigurationComplete

SRB1

ULDCCH

RRC:ULInformationTransfer+NAS:AttachComplete+NAS:ActivateDefaultEPSBearer

SRB2

ULDCCH

RRC:ULInformationTransfer+ESM:PDNConnectivityRequest

SRB2

ULDCCH

Note:RefertoTS36.3319.1.1Logicalchannelconfigurations

CellConfigurationandChannelConfigurationduringCallProcessing

Config1)ActivateCellPhysicallLayer
1)MIB
Config2)ActivatePHY,MAC,RLCforSIBTransmission(BCCHDLDSCH)
2)SIB1
3)SIB2
Config3)ConfigurePHY,MACforPRACHReceptionandRACHResponseTransmission
4)RRC:PRACHPreamble
5)RRC:RACHResponse
Config3)ConfigurePHY,MAC,RLCforMsg3(RRCConnectionRequest)Reception(ULCCCH)
6)RRC:RRCConnectionRequest
Config4)ConfigureMAC,RLC,PDCHforDLDCCH,ULDCCH
7)RRC:RRCConnectionSetup
8)RRC:RRCConnectionSetupComplete+NAS:AttachRequest+ESM:PDNConnectivityRequest
9)RRC:DLInformationTransfer+NAS:AuthenticationRequest
10)RRC:ULInformationTransfer+NAS:AuthenticationResponse
11)RRC:DLInformationTransfer+NAS:SecurityModeCommand
12)RRC:ULInformationTransfer+NAS:SecurityModeComplete
Config5)ConfigurePDCPforIntegrity,Ciphering(WemaydisableIntegiry/Cipheringforsometestenvironment)
13)RRC:SecurityModeCommand
14)RRC:SecurityModeComplete
15)RRC:RRCConnectionReconfiguration+NAS:AttachAccept+NAS:ActivateDefaultEPSBearerContextReq
Config6)ConfigureMAC,RLC,PDCPforDL/ULDTCH+DCCH
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

5/38

12/17/2014

ShareTechnote

16)RRC:RRCConnectionReconfigurationComplete+NAS:AttachComplete+NAS:ActivateDefaultEPSBearer
ContextAccept
17)RRC:RRCConnectionRelease
Config7)DeactivateallthechannelsrelatedtoDCCH,DTCH

Config8)ActivatechannelsforPCCH
<MOorMTcall>:InMTcall,Pagingshouldbesent.
Config9)ConfigurePHY,MACforPRACHReceptionandRACHResponseTransmission
18)RRC:PRACHPreamble
19)RRC:RACHResponse
Config10)ConfigurePHY,MAC,RLCforMsg3(RRCConnectionRequest)Reception(ULCCCH)
20)RRC:RRCConnectionRequest
Config11)ConfigureMAC,RLC,PDCHforDLDCCH,ULDCCH
21)RRC:RRCConnectionSetup
22)RRC:RRCConnectionSetupComplete+NAS:ServiceRequest
23)RRC:SecurityModeCommand
24)RRC:SecurityModeComplete
25)RRC:RRCConnectionReconfiguration+NAS:ActivateDedicatedEPSBearerContextRequest
Config12)ConfigureMAC,RLC,PDCPforDL/ULDTCH+DCCH
26)RRC:RRCConnectionReconfigurationComplete+NAS:ActivateDedicatedEPSBearerContextAccept
27)RRC:RRCConnectionRelease

NowinVeryDetailedPicture

Nowthenextstepistodescribeeachofthestepsinasmuchdetailaspossible.Themoreindetailyoucandescribe,
theeasierthedevelopment,testing,troubleshootingwillbe.TherearemanystepsIcouldn'tdescribeherebecause
themostofstepsnotdescribedherewouldberelatedtocompanyconfidentials(Ofcourse,youcansay"Every
detailsarein3GPPspecification".Yes,that'strue,but3GPPsaysonlyabout"Whattodo",itdoesn'tsaymuchabout
"Howtodo".Inrealimplementation,this"Howtodo"partisasimportantas"Whattodo")Youcantakethisasa
minimumofpossibledetaileddescription.Goingthroughthistable,thinkabouthowmuchadditionalcommentsyou
thinkyoucanputin'Memo'column.(Ifyouwanttoseewhat'sreallyhappeninginrealnetwork,seetheliveair
exampleinFullStackpage)

Step

Direction

Message

Memo

UE<SS MIB

UE<SS SIB1

UE<SS SIB2,3andothers

UE>SS PRACH

<NW>

PHY_PRACH_IND

<NW>

MAC_DATA_IND

UE<SS RACHResponse

<NW>

MAC_DATA_REQ

<NW>

PHY_PRACH_REQ

<NW>

PHY_PRACH_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

UE>SS RRCConnectionRequest
<UE>

UEMACstartmacContentionResolutionTimer

3GPP36.3215.1.5
CRTimervalueissetin
SIB2

UE<SS ACK(PHICH)

UE<SS ContentionResolution

SSmustsendCRbefore
CRtimergetexpired

<UE>

UEMACstopmacContentionResolutionTimer

<NW>

MAC_DATA_REQ

<NW>

PHY_PRACH_REQ

UE<SS RRCConnectionSetup

<NW>

RLC_DATA_REQ

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

10

UE>SS ACK(PUCCH)

11

UE>SS SchedulingRequest(PUCCH)

12

UE<SS ULGrant(DCI0,PDCCH)

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

6/38

12/17/2014

ShareTechnote

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

<NW>

PDCP_DATA_IND

13

RRCConnectionSetupComplete
UE>SS +AttachRequeset
+(PDNConnRequest)

14

UE<SS ACK(PHICH)

15

UE<SS RLCACK

16

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

UE<SS AuthenticationRequest

<NW>

PDCP_DATA_REQ

<NW>

RLC_DATA_REQ

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

17

UE>SS ACK(PUCCH)

18

UE>SS SchedulingRequest(PUCCH)

19

UE<SS ULGrant(DCI0,PDCCH)

20

UE>SS RLCACK

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

21

UE>SS SchedulingRequest(PUCCH)

22

UE>SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

<NW>

PDCP_DATA_IND

23

UE>SS AuthenticationResponse

24

UE<SS ACK(PHICH)

25

UE<SS RLCACK

26

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

UE<SS NASSecurityModeCommand

<NW>

PDCP_DATA_REQ

<NW>

RLC_DATA_REQ

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

27

UE>SS ACK(PUCCH)

28

UE>SS SchedulingRequest(PUCCH)

29

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

30

UE>SS RLCACK

31

UE>SS SchedulingRequest(PUCCH)

32

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

<NW>

PDCP_DATA_IND

33

UE>SS NASSecurityModeComplete

34

UE<SS ACK(PHICH)

35

UE<SS RLCACK

<NW>

MAC_DATA_REQ

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

7/38

12/17/2014

36

ShareTechnote

<NW>

PHY_DATA_REQ

UE<SS RRCSecurityModeCommand

<NW>

PDCP_DATA_REQ

<NW>

RLC_DATA_REQ

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

37

UE>SS ACK(PUCCH)

38

UE>SS SchedulingRequest(PUCCH)

39

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

40

UE>SS RLCACK

41

UE>SS SchedulingRequest(PUCCH)

42

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

<NW>

PDCP_DATA_IND

43

UE>SS RRCSecurityModeComplete

44

UE>SS ACK(PHICH)

45

UE<SS RLCACK

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

<ManyothermessagecanbeaddedheredependingonNW>

46

47

RRCConnectionReconfiguration
UE<SS +AttachAccept
+ActivateDefaultEPSBearerContextRequest

<NW>

PDCP_DATA_REQ

<NW>

RLC_DATA_REQ

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

48

UE>SS ACK(PUCCH)

49

UE>SS SchedulingRequest(PUCCH)

50

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

51

UE>SS RLCACK

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

<NW>

RLC_DATA_IND

<NW>

PDCP_DATA_IND

52

RRCConnectionReconfigurationComplete
UE>SS +AttachComplete
+ActivateDefaultEPSBearerContextAccept

53

UE<SS ACK(PHICH)

54

UE<SS RLCACK

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

<IPDataTrafficifneeded>

55

58

UE<SS RRCConnectionRelease

<NW>

PDCP_DATA_REQ

<NW>

RLC_DATA_REQ

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

8/38

12/17/2014

ShareTechnote

<NW>

MAC_DATA_REQ

<NW>

PHY_DATA_REQ

62

UE>SS RLCACK

63

UE

<NowUEshouldbeinIDLEmode>

64

UE

DecodeMIB

65

UE

DecodeSIB1

66

UE

DecodeorDoesn'tDecodeOtherSIBsbasedonSystemInfoValueTag

onSIB1

67

UE<SS Paging

68

UE>SS PRACH

69

UE<SS RACHResponse

70

UE>SS RRCConnectionRequest

71

UE<SS ACK(PHICH)

72

UE<SS ContentionResolution

73

UE<SS RRCConnectionSetup

74

UE>SS ACK(PUCCH)

75

UE>SS SchedulingRequest(PUCCH)

76

UE<SS ULGrant(DCI0,PDCCH)

77

RRCConnectionSetupComplete
UE>SS
+ServiceRequeset

78

UE<SS ACK(PHICH)

79

UE<SS RLCACK

80

UE<SS

81

UE>SS ACK(PUCCH)

82

UE>SS SchedulingRequest(PUCCH)

83

UE<SS ULGrant(DCI0,PDCCH)

84

UE>SS RLCACK

85

RRCConnectionReconfiguration
UE>SS
+ActivateDedicatedEPSBearerContextAccept

86

UE<SS ACK(PHICH)

87

UE<SS RLCACK

88

59

UE>SS ACK(PUCCH)

60

UE>SS SchedulingRequest(PUCCH)

61

UE<SS ULGrant(DCI0,PDCCH)

<NW>

PHY_DATA_IND

<NW>

MAC_DATA_IND

RRCConnectionReconfiguration
+ActivateDedicatedEPSBearerContextRequest

<IPDataTrafficifneeded>

OverallComparisionwithWCDMA

EventhoughoverallsequenceisprettysimilartoWCDMAsequence,thereareacoupleofdifferentpointscomparing
toWCDMAsequence.

FirstpointyouhavetolookatisthatinLTE'RACHPreamble'issentasapartofMACLayerprocess.Asyouknow
RACHprocesswasthereinWCDMA,butinWCDMAitwasapartofPhysicallayerprocess.

AnotherpartInoticeisthatRRCConnectionSetupCompleteandAttachRequestiscarriedinasinglestep.Thisis
onlyoneexample.InLTE,manyofNASMessageispiggybackedonRRCMessages.Thiswouldmakemessage
decoding/encodingprocesscomplicatedbutitwouldbeefficienttoreducethenumberofmessageexchangebetween
UEandeNodeB.

Thesearethedifferencesyoucannoticejustbylookingatthemessagetype,therearemoredifferencesyouwillfind
whenyougointotheinformationelementsofeachmessagesasyouwillseeinfollowingsections.

NextthingyouwillnoticewouldbethattherearemuchlessSIBsbeingtransmittedinLTEcompartingtoWCDMA.Of
coursetherearemoreSIBsnotbeingtransmittedinthissequence(LTEhas10SIBsintotal),butwithonlythesetwo
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

9/38

12/17/2014

ShareTechnote

SIBsitcantransmitalltheinformationtoletUEcamponthenetwork.InWCDMAthereareatotal18SIBsandin
mostcaseweusedatleastSIB1,3,5,7,11eveninverybasicconfigurations.AndsomeoftheWCDMASIBslikeSIB5
and11hasmultipesegments.InLTE,numberofSIBissmallandnoneofthemaresegmented.

MIB

MIBinLTEhasveryminimalinformation(ThisisabigdifferencefromWCDMAMIB).Theonlyinformationitcarries
are

i)BandWidth
ii)PHICH
iii)SystemFrameNumber

Ofcoursethemostimportantinformationis"BandWidth".

Accordingto36.331section5.2.1.2,theMIBschedulingisasfollows:
TheMIBusesafixedschedulewithaperiodicityof40msandrepetitionsmadewithin40ms.Thefirsttransmission
oftheMIBisscheduledinsubframe#0ofradioframesforwhichtheSFNmod4=0,andrepetitionsarescheduled
insubframe#0ofallotherradioframes.

SIB1

SIB1inLTEcontainstheinformationliketheonesinWCDMAMIB&SIB1&SIB3.TheimportantinformationonSIB
1is

i)PLMN
ii)TrackingAreaCode
iii)CellSelectionInfo
iv)FrequencyBandIndicator
v)Schedulinginformation(periodicity)ofotherSIBs

YoumaynoticethatLTESIB1isverysimilartoWCDMAMIB.
Especiallyatinitialtestcasedevelopment,youhavetobeverycarefulaboutitemv).Ifyousetthisvalue
incorrectly,alltheotherSIBswillnotbedecodedbyUE.Andasaresult,UEwouldnotrecognizethecellandshow
"NoService"message.

Accordingto36.331section5.2.1.2,theSIB1schedulingisasfollows:
TheSystemInformationBlockType1usesafixedschedulewithaperiodicityof80msandrepetitionsmadewithin80
ms.ThefirsttransmissionofSystemInformationBlockType1isscheduledinsubframe#5ofradioframesforwhichthe
SFNmod8=0,andrepetitionsarescheduledinsubframe#5ofallotherradioframesforwhichSFNmod2=0.

ThismeansthateventhoughSIB1periodicityis80ms,differentcopies(Redudancyversion:RV)oftheSIB1is
transmittedevery20ms.MeaningthatatL3youwillseetheSIB1every80ms,butatPHYlayeryouwillseeitevery
20ms.ForthedetailedRVassignmentforeachtransmission,referto36.321section5.3.1(thelastpartofthe
section)

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

10/38

12/17/2014

ShareTechnote

OneexampleofLTESIB1isasfollows:
RRC_LTE:BCCH-DL-SCH-Message
BCCH-DL-SCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [systemInformationBlockType1]
+-systemInformationBlockType1 ::= SEQUENCE [000]
+-cellAccessRelatedInfo ::= SEQUENCE [0]
| +-plmn-IdentityList ::= SEQUENCE OF SIZE(1..6) [1]
| | +-PLMN-IdentityInfo ::= SEQUENCE
| |
+-plmn-Identity ::= SEQUENCE [1]
| |
| +-mcc ::= SEQUENCE OF SIZE(3) OPTIONAL:Exist
| |
| | +-MCC-MNC-Digit ::= INTEGER (0..9) [0]
| |
| | +-MCC-MNC-Digit ::= INTEGER (0..9) [0]
| |
| | +-MCC-MNC-Digit ::= INTEGER (0..9) [1]
| |
| +-mnc ::= SEQUENCE OF SIZE(2..3) [2]
| |
|
+-MCC-MNC-Digit ::= INTEGER (0..9) [0]
| |
|
+-MCC-MNC-Digit ::= INTEGER (0..9) [1]
| |
+-cellReservedForOperatorUse ::= ENUMERATED [notReserved]
| +-trackingAreaCode ::= BIT STRING SIZE(16) [0000000000000001]
| +-cellIdentity ::= BIT STRING SIZE(28) [0000000000000000000100000000]
| +-cellBarred ::= ENUMERATED [notBarred]
| +-intraFreqReselection ::= ENUMERATED [notAllowed]
| +-csg-Indication ::= BOOLEAN [FALSE]
| +-csg-Identity ::= BIT STRING OPTIONAL:Omit
+-cellSelectionInfo ::= SEQUENCE [0]
| +-q-RxLevMin ::= INTEGER (-70..-22) [-53]
| +-q-RxLevMinOffset ::= INTEGER OPTIONAL:Omit
+-p-Max ::= INTEGER OPTIONAL:Omit
+-freqBandIndicator ::= INTEGER (1..64) [7]
+-schedulingInfoList ::= SEQUENCE OF SIZE(1..maxSI-Message[32]) [2]
| +-SchedulingInfo ::= SEQUENCE
| | +-si-Periodicity ::= ENUMERATED [rf8]
| | +-sib-MappingInfo ::= SEQUENCE OF SIZE(0..maxSIB-1[31]) [0]
| +-SchedulingInfo ::= SEQUENCE
|
+-si-Periodicity ::= ENUMERATED [rf8]
|
+-sib-MappingInfo ::= SEQUENCE OF SIZE(0..maxSIB-1[31]) [1]
|
+-SIB-Type ::= ENUMERATED [sibType3]
+-tdd-Config ::= SEQUENCE OPTIONAL:Omit
+-si-WindowLength ::= ENUMERATED [ms20]
+-systemInfoValueTag ::= INTEGER (0..31) [0]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

SIB2

TheimportantinformationonSIB2is

i)RACHConfiguration
ii)bcch,pcch,pdsch,pusch,pucchconfiguration
iii)soundingRSConfiguration
iv)UETimers

IwouldsaySIB2isthemostimportantSIBinLTEandyouwilllookintothisSIBmostfrequentlywhenyouare
implementingprotocolstackandtroubleshooting,sinceitdefinesthecharacteristicsofthemostphysicalchannels.

Ifyouhavesomeissuesatregistrationprocessespeciallybefore'RRCConnectionReconfiguration'.Thefirstpartyou
havetocheckisSIB2andcheckifUEproperlydecodedthisandproperlyconfigureUEaccordingtoSIB2.Sometimes
onlyoneparametermismatchofSIB2betweenNetworkandUEcanmakedifferencebetweensuccessandfailureof
thewholeregistrationprocess.

FollowingisoneexampleofSIB2.IlookstomethatLTESIB2issimilartoWCDMASIB5configuringvariouscommon
channel.

RRC_LTE:BCCH-DL-SCH-Message
BCCH-DL-SCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [systemInformation]
+-systemInformation ::= SEQUENCE
+-criticalExtensions ::= CHOICE [systemInformation-r8]
+-systemInformation-r8 ::= SEQUENCE [0]
+-sib-TypeAndInfo ::= SEQUENCE OF SIZE(1..maxSIB[32]) [1]
| +- ::= CHOICE [sib2]
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

11/38

12/17/2014

ShareTechnote

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

+-sib2 ::= SEQUENCE [00]

+-ac-BarringInfo ::= SEQUENCE OPTIONAL:Omit
+-radioResourceConfigCommon ::= SEQUENCE
| +-rach-Config ::= SEQUENCE
| | +-preambleInfo ::= SEQUENCE [0]
| | | +-numberOfRA-Preambles ::= ENUMERATED [n52]
| | | +-preamblesGroupAConfig ::= SEQUENCE OPTIONAL:Omit
| | +-powerRampingParameters ::= SEQUENCE
| | | +-powerRampingStep ::= ENUMERATED [dB2]
| | | +-preambleInitialReceivedTargetPower ::= ENUMERATED [dBm-104]
| | +-ra-SupervisionInfo ::= SEQUENCE
| | | +-preambleTransMax ::= ENUMERATED [n6]
| | | +-ra-ResponseWindowSize ::= ENUMERATED [sf10]
| | | +-mac-ContentionResolutionTimer ::= ENUMERATED [sf48]
| | +-maxHARQ-Msg3Tx ::= INTEGER (1..8) [4]
| +-bcch-Config ::= SEQUENCE
| | +-modificationPeriodCoeff ::= ENUMERATED [n4]
| +-pcch-Config ::= SEQUENCE
| | +-defaultPagingCycle ::= ENUMERATED [rf128]
| | +-nB ::= ENUMERATED [oneT]
| +-prach-Config ::= SEQUENCE
| | +-rootSequenceIndex ::= INTEGER (0..837) [22]
| | +-prach-ConfigInfo ::= SEQUENCE
| |
+-prach-ConfigIndex ::= INTEGER (0..63) [3]
| |
+-highSpeedFlag ::= BOOLEAN [FALSE]
| |
+-zeroCorrelationZoneConfig ::= INTEGER (0..15) [5]
| |
+-prach-FreqOffset ::= INTEGER (0..94) [2]
| +-pdsch-Config ::= SEQUENCE
| | +-referenceSignalPower ::= INTEGER (-60..50) [18]
| | +-p-b ::= INTEGER (0..3) [0]
| +-pusch-Config ::= SEQUENCE
| | +-pusch-ConfigBasic ::= SEQUENCE
| | | +-n-SB ::= INTEGER (1..4) [1]
| | | +-hoppingMode ::= ENUMERATED [interSubFrame]
| | | +-pusch-HoppingOffset ::= INTEGER (0..98) [4]
| | | +-enable64QAM ::= BOOLEAN [FALSE]
| | +-ul-ReferenceSignalsPUSCH ::= SEQUENCE
| |
+-groupHoppingEnabled ::= BOOLEAN [TRUE]
| |
+-groupAssignmentPUSCH ::= INTEGER (0..29) [0]
| |
+-sequenceHoppingEnabled ::= BOOLEAN [FALSE]
| |
+-cyclicShift ::= INTEGER (0..7) [0]
| +-pucch-Config ::= SEQUENCE
| | +-deltaPUCCH-Shift ::= ENUMERATED [ds2]
| | +-nRB-CQI ::= INTEGER (0..98) [2]
| | +-nCS-AN ::= INTEGER (0..7) [6]
| | +-n1PUCCH-AN ::= INTEGER (0..2047) [0]
| +-soundingRS-UL-Config ::= CHOICE [setup]
| | +-setup ::= SEQUENCE [0]
| |
+-srs-BandwidthConfig ::= ENUMERATED [bw3]
| |
+-srs-SubframeConfig ::= ENUMERATED [sc0]
| |
+-ackNackSRS-SimultaneousTransmission ::= BOOLEAN [TRUE]
| |
+-srs-MaxUpPts ::= ENUMERATED OPTIONAL:Omit
| +-uplinkPowerControl ::= SEQUENCE
| | +-p0-NominalPUSCH ::= INTEGER (-126..24) [-85]
| | +-alpha ::= ENUMERATED [al08]
| | +-p0-NominalPUCCH ::= INTEGER (-127..-96) [-117]
| | +-deltaFList-PUCCH ::= SEQUENCE
| | | +-deltaF-PUCCH-Format1 ::= ENUMERATED [deltaF0]
| | | +-deltaF-PUCCH-Format1b ::= ENUMERATED [deltaF3]
| | | +-deltaF-PUCCH-Format2 ::= ENUMERATED [deltaF0]
| | | +-deltaF-PUCCH-Format2a ::= ENUMERATED [deltaF0]
| | | +-deltaF-PUCCH-Format2b ::= ENUMERATED [deltaF0]
| | +-deltaPreambleMsg3 ::= INTEGER (-1..6) [4]
| +-ul-CyclicPrefixLength ::= ENUMERATED [len1]
+-ue-TimersAndConstants ::= SEQUENCE
| +-t300 ::= ENUMERATED [ms1000]
| +-t301 ::= ENUMERATED [ms1000]
| +-t310 ::= ENUMERATED [ms1000]
| +-n310 ::= ENUMERATED [n1]
| +-t311 ::= ENUMERATED [ms1000]
| +-n311 ::= ENUMERATED [n1]
+-freqInfo ::= SEQUENCE [00]
| +-ul-CarrierFreq ::= INTEGER OPTIONAL:Omit

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

12/38

12/17/2014

ShareTechnote

|
| +-ul-Bandwidth ::= ENUMERATED OPTIONAL:Omit
|
| +-additionalSpectrumEmission ::= INTEGER (1..32) [1]
|
+-mbsfn-SubframeConfigList ::= SEQUENCE OF OPTIONAL:Omit
|
+-timeAlignmentTimerCommon ::= ENUMERATED [sf750]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

RRC:PRACHPreamble/RRC:RACHResponse

Ithinkthistwostepscanbebestsummerizedbythefollowingdiagram.Forthedetails,referto
http://www.sharetechnote.com/html/RACH_LTE.html

InterimComments

Fromthispointon,theL3messagecarriesbothRRCandNASmessages.Soyouneedtohaveoverallunderstanding
ofNASmessagesaswellasRRCmessages.
YouneedtounderstandallthedetailsofTS29.274tohandletohandledatatrafficrelatedIEsinNASmessage.Of
courseitwouldbeimpossibletounderstandallthosedetailswithinaday..myapproachistogothroughfollowing
tablesasoftenaspossibleuntilIgetsomebigpictureinmymind.Youmayhavetogobackandforthbetween
36.331and29.274.

*Table7.2.21:InformationElementsinaCreateSessionResponse
*Table7.2.31:InformationElementsinaCreateBearerRequest
*Table7.2.32:BearerContextwithinCreateBearerRequest
*Table7.2.51:InformationElementsinaBearerResourceCommand
*Table7.2.71:InformationElementsinaModifyBearerRequest
*Table7.2.81:InformationElementsinaModifyBearerResponse
*Table7.2.9.11:InformationElementsinaDeleteSessionRequest
*Table7.2.9.21:InformationElementsinaDeleteBearerRequest
*Table7.2.10.21:InformationElementsinDeleteBearerResponse
*Table7.3.51:InformationElementsinaContextRequest
*Table7.3.62:MME/SGSNUEEPSPDNConnectionswithinContextResponse
*Table7.3.81:InformationElementsinanIdentificationRequest

RRC:RRCConnectionRequest

'RRCConnectionRequest'and'RRCConnectionSetup'procedurecanbesummerizedasinfollowingdiagram.Forthe
details,refertohttp://www.sharetechnote.com/html/RACH_LTE.html(Themessagecontentsshownintheboxisonly
anexample.TheHEXarraysyouwouldseeonyourdeviceandnetworkwouldbedifferentfromwhatyouseehere.
Butoverallstructureshouldbesimilartothis)

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

13/38

12/17/2014

ShareTechnote

Note:ThisexampleshowsthecasewhereContentionResolutionandRRCConnectionSetupisbeingtransmittedata
singlestep,butitisalsopossiblethatContentionResolutionandRRCConnectionSetupmessageistransmittedastwo
separateprocess.

RRC:RRCConnectionSetup

Asyouseeinthefollowingdiagram,themostimportantIE(infomrationelement)inRRCConnectionSetupmessage
is"RadioResourceConfigDedicated"underwhichyoucansetupSRB,DRB,MACandPHYconfig.Eventhouththereis
IEsrelatedtoDRB,inmostcasewesetuponlySRBsinRRCConnectionSetup.ItissimilartoWCDMARRC
ConnectionsetupmessageinwhichyouusuallysetuponlySRB(ControlChannelPart)eventhoughthereisIEsfor
RB(DataTraffic).

Onethingyouhavetonoticeisthatyouwillfind"RadioResourceCondigDedicated"IEnotonlyinRRCConnection
SetupmessagebutalsoinRRCConnectionReconfigurationmessage.Inthatcase,youhavetobecarefulsothatthe
oneyousetinRRCConnectionReconfigmessageproperlymatchtheoneyousetinRRCConnectionSetupmessage.
ItmeansthatyouhavetounderstandthecorrelationveryclearlybetweenRRCConnectionSetupmessageandRRC
ConnectionReconfigmessage.ThisisalsoverysimilartoWCDMAcase.

OneexampleofRRCConnectionSetupisasfollows.Asyouseethecontentsbelow,mainpurposeofRRCConnection
SetupmessageistospecifytheMAC/RLC/PHYsetupforSRB0andSRB1bearer.Soifyoumakeanymistakeinthis
message,NetworkorUEwillfailtodecodemessagesthatcomesafterthismessage.

EspeciallyyouhavetobeverycarefulaboutPhysicalConfigDedicatedpart.Ifyouseeoneofthefollowingissuesafter
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

14/38

12/17/2014

ShareTechnote

'RRCConnectionSetup',thefirstthingyouhavetocheckisPhysicalConfigDedicated.(Youhavetocheckallthe
detailedparameterandmakeitsurethatUEproperlydecodedthoseinformationandproperlyconfigureitself
accordingtothecontents).
i)CRCErrorforPUSCH
ii)UElogshowsittransmitPUSCH,butNetworklogshowsnoPUSCH,notevenCRCerror

DL-CCCH-Message ::= SEQUENCE

+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionSetup]
+-rrcConnectionSetup ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionSetup-r8]
+-rrcConnectionSetup-r8 ::= SEQUENCE [0]
+-radioResourceConfigDedicated ::= SEQUENCE [100101]
| +-srb-ToAddModList ::= SEQUENCE OF SIZE(1..2) [1] OPTIONAL:Exist
| | +-SRB-ToAddMod ::= SEQUENCE [11]
| |
+-srb-Identity ::= INTEGER (1..2) [1]
| |
+-rlc-Config ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
| +-defaultValue ::= NULL
| |
+-logicalChannelConfig ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
+-defaultValue ::= NULL
| +-drb-ToAddModList ::= SEQUENCE OF OPTIONAL:Omit
| +-drb-ToReleaseList ::= SEQUENCE OF OPTIONAL:Omit
| +-mac-MainConfig ::= CHOICE [explicitValue] OPTIONAL:Exist
| | +-explicitValue ::= SEQUENCE [111]
| |
+-ul-SCH-Config ::= SEQUENCE [11] OPTIONAL:Exist
| |
| +-maxHARQ-Tx ::= ENUMERATED [n5] OPTIONAL:Exist
| |
| +-periodicBSR-Timer ::= ENUMERATED [sf20] OPTIONAL:Exist
| |
| +-retxBSR-Timer ::= ENUMERATED [sf320]
| |
| +-ttiBundling ::= BOOLEAN [FALSE]
| |
+-drx-Config ::= CHOICE [release] OPTIONAL:Exist
| |
| +-release ::= NULL
| |
+-timeAlignmentTimerDedicated ::= ENUMERATED [infinity]
| |
+-phr-Config ::= CHOICE [setup] OPTIONAL:Exist
| |
+-setup ::= SEQUENCE
| |
+-periodicPHR-Timer ::= ENUMERATED [sf500]
| |
+-prohibitPHR-Timer ::= ENUMERATED [sf200]
| |
+-dl-PathlossChange ::= ENUMERATED [dB3]
| +-sps-Config ::= SEQUENCE OPTIONAL:Omit
| +-physicalConfigDedicated ::= SEQUENCE [1111001011] OPTIONAL:Exist
|
+-pdsch-ConfigDedicated ::= SEQUENCE OPTIONAL:Exist
|
| +-p-a ::= ENUMERATED [dB-3]
|
+-pucch-ConfigDedicated ::= SEQUENCE [0] OPTIONAL:Exist
|
| +-ackNackRepetition ::= CHOICE [release]
|
| | +-release ::= NULL
|
| +-tdd-AckNackFeedbackMode ::= ENUMERATED OPTIONAL:Omit
|
+-pusch-ConfigDedicated ::= SEQUENCE OPTIONAL:Exist
|
| +-betaOffset-ACK-Index ::= INTEGER (0..15) [9]
|
| +-betaOffset-RI-Index ::= INTEGER (0..15) [6]
|
| +-betaOffset-CQI-Index ::= INTEGER (0..15) [6]
|
+-uplinkPowerControlDedicated ::= SEQUENCE [1] OPTIONAL:Exist
|
| +-p0-UE-PUSCH ::= INTEGER (-8..7) [0]
|
| +-deltaMCS-Enabled ::= ENUMERATED [en0]
|
| +-accumulationEnabled ::= BOOLEAN [TRUE]
|
| +-p0-UE-PUCCH ::= INTEGER (-8..7) [0]
|
| +-pSRS-Offset ::= INTEGER (0..15) [3]
|
| +-filterCoefficient ::= ENUMERATED [fc4] OPTIONAL:Exist
|
+-tpc-PDCCH-ConfigPUCCH ::= CHOICE OPTIONAL:Omit
|
+-tpc-PDCCH-ConfigPUSCH ::= CHOICE OPTIONAL:Omit
|
+-cqi-ReportConfig ::= SEQUENCE [10] OPTIONAL:Exist
|
| +-cqi-ReportModeAperiodic ::= ENUMERATED [rm30] OPTIONAL:Exist
|
| +-nomPDSCH-RS-EPRE-Offset ::= INTEGER (-1..6) [0]
|
| +-cqi-ReportPeriodic ::= CHOICE OPTIONAL:Omit
|
+-soundingRS-UL-ConfigDedicated ::= CHOICE OPTIONAL:Omit
|
+-antennaInfo ::= CHOICE [defaultValue] OPTIONAL:Exist
|
| +-defaultValue ::= NULL
|
+-schedulingRequestConfig ::= CHOICE [setup] OPTIONAL:Exist
|
+-setup ::= SEQUENCE
|
+-sr-PUCCH-ResourceIndex ::= INTEGER (0..2047) [20]
|
+-sr-ConfigIndex ::= INTEGER (0..155) [30]
|
+-dsr-TransMax ::= ENUMERATED [n4]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

15/38

12/17/2014

ShareTechnote

<Note1>
+-pdsch-ConfigDedicated ::= SEQUENCE OPTIONAL:Exist
| +-p-a ::= ENUMERATED [dB-3]
:transmissionpoweriscalculatedaccordingtoSection5.2of3GPPTS36.213fromthereferencesignalpowerandthe
valuesoftheP_AandP_Bparametersspecifiedforthisprocedure.TheseparameterssetthePDSCHtransmission
powerdifferencesbetweensymbolswithandwithoutRS.
UnpropersettingsforthisvaluewouldcauselargeamountofCRCerrorsonPDSCHreceptiononUEside,resultingin
alotofHARQNACKfromUE.

<Note2>
IfyouseeSRBToAddModIE,youwouldseeacoupleofDefaultValue.Whatdoesthismean?
Followingtwosectionsof36.331willgiveyoutheanswer.
9.1.2SRBconfigurations
9.2Defaultradioconfigurations

RRC:RRCConnectionSetupComplete+NAS:AttachRequest+ESM:PDNConnectivityRequest

ThisstepwouldbeoneofveryimportantstepsduringtheinitialregistrationprocessmainlybecauseUEsendalotof
it'scapabilityinformation(especaillyNASlayercapabilityinformation)tothecorenetwork.

AsyouseethisstepcarriestwoimportantNASmessageasfollows.

NAS:AttachRequest:ThemostimportantinformationcarriedbythismessagewouldbeUEcapabilityintermsof
cipheringandintegrity.Ifyoudon'tdoproperfollowingstep(especiallyatAttachacceptstep)basedonthe
informationonthis,UEwillfailtoregistration.Evenbiggerproblemisthatthefailuremodeofregistrationvaries
dependingUEprotocolstackimplementation.Soinmanycaseitisveryhardtofindtherootcauseoftheproblem.

ESM:PDNConnectivityRequest:Themostinformationofthismessagewouldbetheprotocolconfigurationoptions
(PCO).FromthisyoucanfigureoutwhatkindofpacketserviceUEsupportorwanttogetsupported.Ifyoudon't
properlyhandlethisinformation,itwillalsoresultinregistrationfailureandthefailuremodewouldvarydepending
onUEimplementation.

Attach request ::= DIVISION

+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Attach request message identity ::= V
| +-Message type ::= MSG [41]
+-NAS key set identifier ::= V
| +-TSC ::= CHOICE [native security context (for KSI ASME)]
| +-NAS key set identifier ::= CHOICE [possible values for the NAS key set identifier 1]
+-EPS attach type ::= V
| +-Spare ::= FIX [0]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

16/38

12/17/2014

ShareTechnote

| +-EPS attach type value ::= CHOICE [EPS attach]

+-Old GUTI or IMSI ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of EPS mobile identity contents ::= LEN (0..255) [11]
| +-Octet2 ::= DIVISION
| | +-Spare ::= FIX [F]
| | +-Odd/even indication ::= CHOICE [even number of identity digits and also when the GUTI is used]
| | +-Type of identity ::= CHOICE [GUTI]
| +-Octet3 ::= DIVISION
| | +-MCC digit 2 ::= INT (0..15) [0]
| | +-MCC digit 1 ::= INT (0..15) [0]
| +-Octet4 ::= DIVISION
| | +-MNC digit 3 ::= INT (0..15) [15]
| | +-MCC digit 3 ::= INT (0..15) [1]
| +-Octet5 ::= DIVISION
| | +-MNC digit 2 ::= INT (0..15) [1]
| | +-MNC digit 1 ::= INT (0..15) [0]
| +-Octet6 ::= DIVISION
| | +-MME Group ID ::= INT (0..255) [0]
| +-Octet7 ::= DIVISION
| | +-MME Group ID(continued) ::= INT (0..255) [1]
| +-Octet8 ::= DIVISION
| | +-MME Code ::= INT (0..255) [1]
| +-Octet9 ::= DIVISION
| | +-M-TMSI ::= INT (0..255) [18]
| +-Octet10 ::= DIVISION
| | +-M-TMSI(continued) ::= INT (0..255) [52]
| +-Octet11 ::= DIVISION
| | +-M-TMSI(continued) ::= INT (0..255) [86]
| +-Octet12 ::= DIVISION
|
+-M-TMSI(continued) ::= INT (0..255) [120]
+-UE network capability ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of UE network capability contents ::= LEN (0..255) [2]
| +-Octet2 ::= DIVISION
| | +-EEA0 ::= CHOICE [EPS encryption algorithm EEA0 supported]
| | +-128-EEA1 ::= CHOICE [EPS encryption algorithm 128-EEA1 supported]
| | +-128-EEA2 ::= CHOICE [EPS encryption algorithm 128-EEA2 supported]
| | +-EEA3 ::= CHOICE [EPS encryption algorithm EEA3 not supported]
| | +-EEA4 ::= CHOICE [EPS encryption algorithm EEA4 not supported]
| | +-EEA5 ::= CHOICE [EPS encryption algorithm EEA5 not supported]
| | +-EEA6 ::= CHOICE [EPS encryption algorithm EEA6 not supported]
| | +-EEA7 ::= CHOICE [EPS encryption algorithm EEA7 not supported]
| +-Octet3 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-128-EIA1 ::= CHOICE [EPS integrity algorithm 128-EIA1 supported]
| | +-128-EIA2 ::= CHOICE [EPS integrity algorithm 128-EIA2 supported]
| | +-EIA3 ::= CHOICE [EPS integrity algorithm EIA3 not supported]
| | +-EIA4 ::= CHOICE [EPS integrity algorithm EIA4 not supported]
| | +-EIA5 ::= CHOICE [EPS integrity algorithm EIA5 not supported]
| | +-EIA6 ::= CHOICE [EPS integrity algorithm EIA6 not supported]
| | +-EIA7 ::= CHOICE [EPS integrity algorithm EIA7 not supported]
| +-Octet4 ::= DIVISION
| | +-UEA0 ::= CHOICE [UMTS encryption algorithm UEA0 not supported]
| | +-UEA1 ::= CHOICE [UMTS encryption algorithm UEA1 not supported]
| | +-UEA2 ::= CHOICE [UMTS encryption algorithm UEA2 not supported]
| | +-UEA3 ::= CHOICE [UMTS encryption algorithm UEA3 not supported]
| | +-UEA4 ::= CHOICE [UMTS encryption algorithm UEA4 not supported]
| | +-UEA5 ::= CHOICE [UMTS encryption algorithm UEA5 not supported]
| | +-UEA6 ::= CHOICE [UMTS encryption algorithm UEA6 not supported]
| | +-UEA7 ::= CHOICE [UMTS encryption algorithm UEA7 not supported]
| +-Octet5 ::= DIVISION
| | +-UCS2 ::= CHOICE [The UE has a preference for the default alphabet (defined in 3GPP TS 23.038 [3]) over
UCS2 (see ISO/IEC 10646 [29])]
| | +-UIA1 ::= CHOICE [UMTS integrity algorithm UIA1 not supported]
| | +-UIA2 ::= CHOICE [UMTS integrity algorithm UIA2 not supported]
| | +-UIA3 ::= CHOICE [UMTS integrity algorithm UIA3 not supported]
| | +-UIA4 ::= CHOICE [UMTS integrity algorithm UIA4 not supported]
| | +-UIA5 ::= CHOICE [UMTS integrity algorithm UIA5 not supported]
| | +-UIA6 ::= CHOICE [UMTS integrity algorithm UIA6 not supported]
| | +-UIA7 ::= CHOICE [UMTS integrity algorithm UIA7 not supported]
| +-Octet6 ::= DIVISION
| | +-spare ::= FIX [0]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

17/38

12/17/2014

ShareTechnote

| | +-1xSRVCC ::= CHOICE [SRVCC from E-UTRAN to cdma2000 1xCS not supported]
| | +-spare ::= FIX [0]
| +-Octet7-14 ::= DIVISION
|
+-Spare ::= OCTETARRAY SIZE(0..8) [00]
+-ESM message container ::= LV-E
| +-Octet1-Octet2 ::= DIVISION
| | +-Length of ESM message container ::= LEN (0..65535) [23]
| +-Octet3- ::= DIVISION
|
+-ESM message container contents ::= OCTETARRAY SIZE(0..65535)
[0201D031D1271080000100000300000A00000C00000D00]
+-Old P-TMSI signature ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-P-TMSI signature IEI ::= IEI [19]
| +-Octet2-4 ::= DIVISION
|
+-P-TMSI signature value ::= INT (0..16777215) [0]
+-Additional GUTI ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-EPS mobile identity IEI ::= IEI [50]
| +-Octet2 ::= DIVISION
| | +-Length of mobile identity IEI ::= LEN (0..255) [1]
| +-Octet3 ::= DIVISION
| | +-Identity digit 1 ::= INT (0..15) [0]
| | +-Odd/even indication ::= CHOICE [even number of identity digits and also when the GUTI is used]
| | +-Type of identity ::= CHOICE [IMSI]
| +-Octet4 ::= DIVISION
|
+-Identity digit p ::= OCTETARRAY SIZE(0..10)
+-Last visited registered TAI ::= TV OPTIONAL:Exist
| +-Octet1 ::= DIVISION
| | +-Tracking area identity IEI ::= IEI [52]
| +-Octet2 ::= DIVISION
| | +-MCC digit 2 ::= INT (0..15) [1]
| | +-MCC digit 1 ::= INT (0..15) [3]
| +-Octet3 ::= DIVISION
| | +-MNC digit 3 ::= INT (0..15) [0]
| | +-MCC digit 3 ::= INT (0..15) [1]
| +-Octet4 ::= DIVISION
| | +-MNC digit 2 ::= INT (0..15) [8]
| | +-MNC digit 1 ::= INT (0..15) [4]
| +-Octet5 ::= DIVISION
| | +-TAC ::= INT (0..255) [0]
| +-Octet6 ::= DIVISION
|
+-TAC(continued) ::= INT (0..255) [1]
+-DRX parameter ::= TV OPTIONAL:Omit
+-MS network capability ::= TLV OPTIONAL:Omit
+-Old location area identification ::= TV OPTIONAL:Omit
+-TMSI status ::= TV OPTIONAL:Omit
+-Mobile Station Classmark 2 ::= TLV OPTIONAL:Omit
+-Mobile Station Classmark 3 ::= TLV OPTIONAL:Omit
+-Supported Codecs ::= TLV OPTIONAL:Omit

IfyoudecodetheESMmessagecontainercontentspart,youwillgetthefollowingcontents.

NAS_LTE:ESM,PDN connectivity request

PDN connectivity request ::= DIVISION
+-EPS bearer identity ::= V
| +-EPS bearer identity value ::= CHOICE [No EPS bearer identity assigned]
+-EPS session management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [2]
+-Procedure transaction identity ::= V
| +-Procedure transaction identity ::= CHOICE [Procedure transaction identity value 1]
+-PDN connectivity request message identity ::= V
| +-Message type ::= MSG [D0]
+-PDN type ::= V
| +-spare ::= FIX [0]
| +-PDN type value ::= CHOICE [IPv4v6]
+-Request type ::= V
| +-Spare ::= FIX [0]
| +-Request type value ::= CHOICE [initial request]
+-ESM information transfer flag ::= TV OPTIONAL:Exist
| +-Octet1 ::= DIVISION
|
+-ESM information transfer flag IEI ::= IEI [D-]
|
+-spare ::= FIX [0]
|
+-EIT value ::= CHOICE [security protected ESM information transfer required]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

18/38

12/17/2014

ShareTechnote

+-Access point name ::= TLV OPTIONAL:Omit

| +-Octet1 ::= DIVISION
| | +-Access point name IEI ::= IEI [28]
| +-Octet2 ::= DIVISION
| | +-Length of access point name contents ::= LEN (0..255) [0]
| +-Octet3-Octet102 ::= DIVISION
|
+-Access point name value ::= OCTETARRAY SIZE(0..100)
+-Protocol configuration options ::= TLV OPTIONAL:Exist
+-Octet1 ::= DIVISION
| +-Protocol configuration options IEI ::= IEI [27]
+-Octet2 ::= DIVISION
| +-Length of protocol config options contents ::= LEN (0..255) [16]
+-Octet3 ::= DIVISION
| +-ext ::= EXT1 [1]
| +-spare ::= FIX [0]
| +-Configuration protocol ::= CHOICE [PPP for use with IP PDP type]
+-Octet4-Octet253 ::= DIVISION
+-protocol config options contents ::= OCTETARRAY SIZE(0..250) [000100000300000A00000C00000D00]

Therearecoupleofimportantinformationinthismessageasdescribedbelow.

ESMinformationtransferflag:AccordingtoStep9a1ofTable4.5.2.31:UEregistrationprocedure(state1tostate
2)of36.508,NetworkhastogothroughESM:InformationRequestasdescribedbelow.

IFtheUEsetstheESMinformationtransferflaginthelastPDNCONNECTIVITYREQUESTmessageTHENtheSS
transmitsanESMINFORMATIONREQUESTmessagetoinitiateexchangeofprotocolconfigurationoptionsand/or
APN

PDNType:specifiesIPversionthattheUEwantstouseforEPSBearerandNetworkmayormaynotusethesame
IPversioninDefault(orDedicated)EPSBearerContextRequest.SomeUEwouldacceptwhateverIPversionis
specifiedbythenetworkatEPSBearerestablishmentstep,butsomeUEfailtosetupEPSbeareriftheIPversion
NetworkspecifyinDefault(orDedicated)EPSBearerContextRequestdoesnotmatchthePDNtypeinthismessage.

AccessPointName:UEshowsmanydifferentbehaviorrelatedtothisAPNname.Followingsaresomeofthe
behaviorthatIobservedfromacoupleofdifferencedevices.
i)UEdoesnotspecifyanyAPNhereandacceptwhateverNetworkspecifiesinActivateDefaultEPSBearerContext
Request.
ii)UEspecifyaspecificAPNhere,butitacceptwhateverNetworkspecifiesinActivateDefaultEPSBearerContext
Request.
iii)UEspecifyaspecificAPNhere,butitrejecttheAPNthatNetworkspecifiesinActivateDefaultEPSBearerContext
RequestifitisdifferentfromwhatUEspecifiedhere.

ProtocolConfigurationOptions:Youcangetthedetailedinformationfromthisprotocolconfigoptionscontentsfrom
TS24_00810.5.6.3Protocolconfigurationoptionswhichcanbesummarizedasfollows.
Thisisaprettycomplicatedtopic.SoIwilldescribethisonaseparateposthere.

RRC:DLInformationTransfer+NAS:AuthenticationRequest
RRC:ULInformationTransfer+NAS:AuthenticationResponse
"Authentication"processisaprocesssimilarto'login'processwhenyouuseacomputer.InC2KandGSM,this
authenticationprocessis'unidirectional',meaningthatonlyNetworkauthenticateUEandUEdoesnotauthenticate
thenetwork.Asyoumayeasilyguess,thiswouldcauseaserioussecurityproblem.IfImakeafakenetworkwhich
acceptanyUE,IcancheataUEtocamponthefakenetworkratherthantheonetheUEissupposedtocamponto.
(Butthiskindof'unidirectional'authenticationwouldmakeitsoeasytotestaUEusingnetworksimulator:)

Toimprovethissecurityissues,inLTE(inWCDMAaswell)theydo'bidirectional'authentication,meaningthatUE
hastopasstheauthenticationprocessandNewtorkalsohastopasstheprocessaswell.

Theoverallauthenticationprocessisasfollows.

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

19/38

12/17/2014

ShareTechnote

Therearethreemaincomponentsofthisauthenticationprocess:
i)InputParameters
ii)AuthenticationAlgorithm
iii)OutputValues(calcuatedbyAuthenticationAlgorithmusingtheInputParameters).

BothUEandNetworkusesthesameInputParametersandthesameAuthenticationAlgorithms,sotheybothshould
producethesameOutputValues,otherwiseAuthenticationfails.

OnethingyouhavetokeepinmindisthatUEandNetworkexchangeonlyInputParametersandOutputvalues,not
theauthenticationAlgorithm.AuthenticationAlgorithmonUEsideisstoredinUSIMandAuthenticationAlgorithmon
NWsideisstoredinAuthenticationCenter.BothUEandNWjustassumethattheywouldusetheidenticalalgorithms.
NormallyuseusediffentAuthenticationAlgorithmfortestingandforlivenetwork.Themostcommonlyused
algorithmfortestingiswhatweoftencall"DummyXOR"algorithmwhichisdefinedin36.508section4.9Common
testUSIMparametersforLTEand34.408section8TestUSIMParametersforWCDMA.

Themostcommonusedalgorithminlivenetwork(asfarasIknow)isMilenagealgorithm.
One example of Authentication Request and Authentication Response is as follows. You would notice
that RAND, AUTN are carried by Authentication Request message and RES value is carried by
Authentication Response.
NAS_LTE:EMM,Authentication request
Authentication request ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Authentication request message type ::= V
| +-Message type ::= MSG [52]
+-Spare half octet ::= V
| +-Spare half octet ::= FIX [0]
+-NAS key set identifier ASME ::= V
| +-TSC ::= CHOICE [native security context (for KSI ASME)]
| +-NAS key set identifier ::= CHOICE [possible values for the NAS key set identifier 0]
+-Authentication parameter RAND ::= V
| +-Octet1-Octet16 ::= DIVISION
|
+-RAND value ::= OCTETARRAY SIZE(16..16) [A3DE0C6D363E30C364A4078F1BF8D577]
+-Authentication parameter AUTN ::= LV
+-Octet1 ::= DIVISION
| +-Length of AUTN contents ::= LEN (0..255) [16]
+-Octet2-Octet17 ::= DIVISION
+-AUTN ::= OCTETARRAY SIZE(0..16) [5E726B56B4EC9001A3CF2E5E726BC6B5]
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

20/38

12/17/2014

ShareTechnote

NAS_LTE:EMM,Authentication response
Authentication response ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Authentication response message identity ::= V
| +-Message type ::= MSG [53]
+-Authentication response parameter ::= LV
+-Octet1 ::= DIVISION
| +-Length of Authentication response parameter contents ::= LEN (0..255) [8]
+-Octet2-17 ::= DIVISION
+-RES ::= OCTETARRAY SIZE(0..16) [A3CF2E5E726B56B4]

RRC:DLInformationTransfer+NAS:SecurityModeCommand

Security Mode Command message to inform the UE of the following information (instructions).
i) I (Newtork) am capable of these kinds of ciphering (encryption) algorithms
ii) I (Newtork) am capable of these kinds of integrity algorithms
iii) Among those ciphering algorithm which I am capable of, I will be using "this specific
algorithm" for the communication with you (UE).
iv) Among those integrity algorithm which I am capable of, I will be using "this specific
algorithm" for the communication with you (UE)
InLTE,theyareusingseparateSecurityModeprocessforNASandRRC,whereasinWCDMAonlyonesecuritymode
process(RRConly)wasused(NASisindirectlyprotectedsinceNASmessagewasembeddedinRRCandprotectedas
apartofRRCmessage).Thepartmarkedinblueisforitemi)andii)listedaboveandthepartmarkedinredisfor
itemiii)andiv).
NAS_LTE:EMM,Security mode command
Security mode command ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Security mode command message identity ::= V
| +-Message type ::= MSG [5D]
+-Selected NAS security algorithms ::= V
| +-Octet1 ::= DIVISION
|
+-spare ::= FIX [0]
|
+-Type of ciphering algorithm ::= CHOICE [EPS encryption algorithm EEA0(ciphering not used)]
|
+-spare ::= FIX [0]
|
+-Type of integrity protection algorithm ::= CHOICE [Reserved 0]
+-Spare half octet ::= V
| +-Spare half octet ::= FIX [0]
+-NAS key set identifier ::= V
| +-TSC ::= CHOICE [native security context (for KSI ASME)]
| +-NAS key set identifier ::= CHOICE [possible values for the NAS key set identifier 0]
+-Replayed UE security capabilities ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of UE security capability contents ::= LEN (0..255) [2]
| +-Octet2 ::= DIVISION
| | +-EEA0 ::= CHOICE [EPS encryption algorithm EEA0 supported]
| | +-128-EEA1 ::= CHOICE [EPS encryption algorithm 128-EEA1 supported]
| | +-128-EEA2 ::= CHOICE [EPS encryption algorithm 128-EEA2 supported]
| | +-EEA3 ::= CHOICE [EPS encryption algorithm EEA3 not supported]
| | +-EEA4 ::= CHOICE [EPS encryption algorithm EEA4 not supported]
| | +-EEA5 ::= CHOICE [EPS encryption algorithm EEA5 not supported]
| | +-EEA6 ::= CHOICE [EPS encryption algorithm EEA6 not supported]
| | +-EEA7 ::= CHOICE [EPS encryption algorithm EEA7 not supported]
| +-Octet3 ::= DIVISION
| | +-spare ::= FIX [1]
| | +-128-EIA1 ::= CHOICE [EPS integrity algorithm 128-EIA1 supported]
| | +-128-EIA2 ::= CHOICE [EPS integrity algorithm 128-EIA2 supported]
| | +-EIA3 ::= CHOICE [EPS integrity algorithm EIA3 not supported]
| | +-EIA4 ::= CHOICE [EPS integrity algorithm EIA4 not supported]
| | +-EIA5 ::= CHOICE [EPS integrity algorithm EIA5 not supported]
| | +-EIA6 ::= CHOICE [EPS integrity algorithm EIA6 not supported]
| | +-EIA7 ::= CHOICE [EPS integrity algorithm EIA7 not supported]
| +-Octet4 ::= DIVISION
| | +-UEA0 ::= CHOICE [UMTS encryption algorithm UEA0 not supported]
| | +-UEA1 ::= CHOICE [UMTS encryption algorithm UEA1 not supported]
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

21/38

12/17/2014

ShareTechnote

| | +-UEA2 ::= CHOICE [UMTS encryption algorithm UEA2 not supported]

| | +-UEA3 ::= CHOICE [UMTS encryption algorithm UEA3 not supported]
| | +-UEA4 ::= CHOICE [UMTS encryption algorithm UEA4 not supported]
| | +-UEA5 ::= CHOICE [UMTS encryption algorithm UEA5 not supported]
| | +-UEA6 ::= CHOICE [UMTS encryption algorithm UEA6 not supported]
| | +-UEA7 ::= CHOICE [UMTS encryption algorithm UEA7 not supported]
| +-Octet5 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-UIA1 ::= CHOICE [UMTS integrity algorithm UIA1 not supported]
| | +-UIA2 ::= CHOICE [UMTS integrity algorithm UIA2 not supported]
| | +-UIA3 ::= CHOICE [UMTS integrity algorithm UIA3 not supported]
| | +-UIA4 ::= CHOICE [UMTS integrity algorithm UIA4 not supported]
| | +-UIA5 ::= CHOICE [UMTS integrity algorithm UIA5 not supported]
| | +-UIA6 ::= CHOICE [UMTS integrity algorithm UIA6 not supported]
| | +-UIA7 ::= CHOICE [UMTS integrity algorithm UIA7 not supported]
| +-Octet6 ::= DIVISION
|
+-spare ::= FIX [0]
|
+-GEA1 ::= CHOICE [GPRS encryption algorithm GEA1 not supported]
|
+-GEA2 ::= CHOICE [GPRS encryption algorithm GEA2 not supported]
|
+-GEA3 ::= CHOICE [GPRS encryption algorithm GEA3 not supported]
|
+-GEA4 ::= CHOICE [GPRS encryption algorithm GEA4 not supported]
|
+-GEA5 ::= CHOICE [GPRS encryption algorithm GEA5 not supported]
|
+-GEA6 ::= CHOICE [GPRS encryption algorithm GEA6 not supported]
|
+-GEA7 ::= CHOICE [GPRS encryption algorithm GEA7 not supported]
+-IMEISV request ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
|
+-IMEISV request IEI ::= IEI [C-]
|
+-spare ::= FIX [0]
|
+-IMEISV request value ::= CHOICE [IMEISV not requested]
+-Replayed nonce UE ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Nonce IEI ::= IEI [55]
| +-Octet2-Octet5 ::= DIVISION
|
+-Nonce value ::= OCTETARRAY SIZE(4..4) [00000000]
+-Nonce MME ::= TV OPTIONAL:Omit
+-Octet1 ::= DIVISION
| +-Nonce IEI ::= IEI [56]
+-Octet2-Octet5 ::= DIVISION
+-Nonce value ::= OCTETARRAY SIZE(4..4) [00000000]

RRC:ULInformationTransfer+NAS:SecurityModeComplete

SecurityModeCompleteistheanswerto"SecurityModeCommand"message,soitissimple.IfUEisalsocapableof
theIntegrity,SecurityalgorithmthatNWwanttouse,itsend'SecurityModeComplete',ifUEisnotcapableofthem,
itsend'SecurityModeFailure'.
NAS_LTE:EMM,Security mode complete
Security mode complete ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Security mode complete message identity ::= V
| +-Message type ::= MSG [5E]
+-IMEISV ::= TLV OPTIONAL:Omit
+-Octet1 ::= DIVISION
| +-Mobile Identity IEI ::= IEI [23]
+-Octet2 ::= DIVISION
| +-Length of mobile identity contents ::= LEN (0..255) [0]
+-Octet3 ::= DIVISION
| +-Identity digit 1 ::= INT (0..15) [0]
| +-Odd/even indication ::= CHOICE [even number of identity digits and also when the TMSI/PTMSI is used]
| +-Type of identity ::= CHOICE [No Identity]
+-Octet4-Octet11 ::= DIVISION
+-Identity digit p ::= OCTETARRAY SIZE(0..8)

RRC:SecurityModeCommand

This is the same step as NAS:Security Mode Command, the only difference is that this is only for
RRC message.
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

22/38

12/17/2014

ShareTechnote

RRC_LTE:DL-DCCH-Message
DL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [securityModeCommand]
+-securityModeCommand ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [securityModeCommand-r8]
+-securityModeCommand-r8 ::= SEQUENCE [0]
+-securityConfigSMC ::= SEQUENCE
| +-securityAlgorithmConfig ::= SEQUENCE
|
+-cipheringAlgorithm ::= ENUMERATED [eea1]
|
+-integrityProtAlgorithm ::= ENUMERATED [eia1]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

ForCipheringAlgorithmParamter,refertoEEApage.
ForIntegrityAlgorithmParamter,refertoEIApage.

RRC:SecurityModeComplete

SecurityModeCompleteistheanswerto"SecurityModeCommand"message,soitissimple.IfUEisalsocapableof
theIntegrity,SecurityalgorithmthatNWwanttouse,itsend'SecurityModeComplete',ifUEisnotcapableofthem,
itsend'SecurityModeFailure'.
UL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [securityModeComplete]
+-securityModeComplete ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [securityModeComplete-r8]
+-securityModeComplete-r8 ::= SEQUENCE [0]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

RRC:UECapabilityEnquiry

Asthediversityofmobileservicesgetswider,NetworkneedstoknowexactcapabilityofaUEtoprovideproper
servicesforeachUE.Forexample,whatifnetworktriggersaninterRAThandovertoaUEwhichdoesnotsupport
thatcapability?Itwouldleadtocommunicationdrop.
IncaseofWCDMA,NetworkcanfigureoutallthedetailsofUEcapabilityduringRRCConnectionSetupComplete
messagesinceUEreportallthedetailsofitscapabilityinRRCConnectionSetupCompletemessage.However,LTE
RRCConnectionSetupCompletemessagedoesnotcarrythiskindofinformation.Instead,LTEdesignedanew
messagededicatedforinvestigatingUEcapability.ThisistheroleofUECapabilityEnquiryandUECapability
Informationmessage.
Strictlyspeaking,thisisakindofoptionalstep..butitisbecomingmoreandmorecriticalstepsasLTEservice
evolves.

FollowingisoneexampleofueCapabilityRequestmessageandthisissaying"ReportallofyourLTEcapabilityand
UTRAcapability".

DL-DCCH-Message ::= SEQUENCE

+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [ueCapabilityEnquiry]
+-ueCapabilityEnquiry ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [ueCapabilityEnquiry-r8]
+-ueCapabilityEnquiry-r8 ::= SEQUENCE [0]
+-ue-CapabilityRequest ::= SEQUENCE OF SIZE(1..maxRAT-Capabilities[8]) [2]
| +-RAT-Type ::= ENUMERATED [eutra]
| +-RAT-Type ::= ENUMERATED [utra]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

RRC:UECapabilityInformation

ThismessageistheresponsetoUECapabilityRequestmessageanditcarriesallthedetailsofUEcapability.Since
thisisverycomplicatedmessagewhichhaswidevariety,ImadeaseparatepageforUECapabilityInformation.

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

23/38

12/17/2014

ShareTechnote

RRC:RRCConnectionReconfiguration+NAS:AttachAccept+NAS:ActivateDefaultEPSBearerContext
Request

Animportantproceduredoneinthisstepis"ESM:ActivateDefaultEPSBearerContextRequest".

OnethingyounoticehereisthatinLTEPacketcallisinitiatedbyNetworkwhereasinUMSTmostofthepacketcall
isinitiatedbyUE.NetworkspecifiesanIPfortheUEhere.

IfyouhaveanyexperiencewithWCDMAprotocol,youmaytakethismessagetobesimilarto'RadioBearerSetup'+
'AttachAccept'+ActivatePDPContextAccept.
Atthisstep,UEgetsanIPfromthenetworkandthisIPdoesnotgetreturnedtoNetworkevenafter'RRCconnection
Release'andUEgetsintoIDLEmode.

An example of RRC Connection Reconfiguration is as follows. Don't try to look into all the details
since this message is one of the most complicated message in LTE. Just try to understand overall
structure and compare the tree map shown above and the real messages shown below.
Probably it will take several month to understand all the details of these elements, so don't be so
hurry.
Whenever you study a little bit further details of the topics in the tree diagram shown above, open
up this section and see the details under the topics you studied. If you fully understand all the
information elements shown below, you can say you mastered the LTE. Again don't try to understand
all of these at once. It will just raise your blood pressure. Just look through these items as
often as possible and get familiar with the overall structure first.
DL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfiguration]
+-rrcConnectionReconfiguration ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfiguration-r8]
+-rrcConnectionReconfiguration-r8 ::= SEQUENCE [001100]
+-measConfig ::= SEQUENCE OPTIONAL:Omit
+-mobilityControlInfo ::= SEQUENCE OPTIONAL:Omit
+-dedicatedInfoNASList ::= SEQUENCE OF SIZE(1..maxDRB[11]) [1] OPTIONAL:Exist
| +-DedicatedInfoNAS ::= OCTET STRING SIZE(ALIGNED)
[074201E0060000F1100001002C5201C101091003777777
07616E726974737503636F6D05010A012037270E808021
0A0300000A81060A000001500BF600F11080010100000001]
+-radioResourceConfigDedicated ::= SEQUENCE [110101] OPTIONAL:Exist
| +-srb-ToAddModList ::= SEQUENCE OF SIZE(1..2) [1] OPTIONAL:Exist
| | +-SRB-ToAddMod ::= SEQUENCE [11]
| |
+-srb-Identity ::= INTEGER (1..2) [2]
| |
+-rlc-Config ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
| +-defaultValue ::= NULL
| |
+-logicalChannelConfig ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
+-defaultValue ::= NULL
| +-drb-ToAddModList ::= SEQUENCE OF SIZE(1..maxDRB[11]) [1] OPTIONAL:Exist
| | +-DRB-ToAddMod ::= SEQUENCE [11111]
| |
+-eps-BearerIdentity ::= INTEGER (0..15) [5] OPTIONAL:Exist
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

24/38

12/17/2014

ShareTechnote

| |
+-drb-Identity ::= INTEGER (1..32) [1]
| |
+-pdcp-Config ::= SEQUENCE [101] OPTIONAL:Exist
| |
| +-discardTimer ::= ENUMERATED [infinity] OPTIONAL:Exist
| |
| +-rlc-AM ::= SEQUENCE OPTIONAL:Omit
| |
| +-rlc-UM ::= SEQUENCE OPTIONAL:Exist
| |
| | +-pdcp-SN-Size ::= ENUMERATED [len12bits]
| |
| +-headerCompression ::= CHOICE [notUsed]
| |
|
+-notUsed ::= NULL
| |
+-rlc-Config ::= CHOICE [um-Bi-Directional] OPTIONAL:Exist
| |
| +-um-Bi-Directional ::= SEQUENCE
| |
|
+-ul-UM-RLC ::= SEQUENCE
| |
|
| +-sn-FieldLength ::= ENUMERATED [size10]
| |
|
+-dl-UM-RLC ::= SEQUENCE
| |
|
+-sn-FieldLength ::= ENUMERATED [size10]
| |
|
+-t-Reordering ::= ENUMERATED [ms50]
| |
+-logicalChannelIdentity ::= INTEGER (3..10) [3] OPTIONAL:Exist
| |
+-logicalChannelConfig ::= SEQUENCE [1] OPTIONAL:Exist
| |
+-ul-SpecificParameters ::= SEQUENCE [1] OPTIONAL:Exist
| |
+-priority ::= INTEGER (1..16) [13]
| |
+-prioritisedBitRate ::= ENUMERATED [infinity]
| |
+-bucketSizeDuration ::= ENUMERATED [ms100]
| |
+-logicalChannelGroup ::= INTEGER (0..3) [2] OPTIONAL:Exist
| +-drb-ToReleaseList ::= SEQUENCE OF OPTIONAL:Omit
| +-mac-MainConfig ::= CHOICE [explicitValue] OPTIONAL:Exist
| | +-explicitValue ::= SEQUENCE [111]
| |
+-ul-SCH-Config ::= SEQUENCE [11] OPTIONAL:Exist
| |
| +-maxHARQ-Tx ::= ENUMERATED [n5] OPTIONAL:Exist
| |
| +-periodicBSR-Timer ::= ENUMERATED [sf20] OPTIONAL:Exist
| |
| +-retxBSR-Timer ::= ENUMERATED [sf320]
| |
| +-ttiBundling ::= BOOLEAN [FALSE]
| |
+-drx-Config ::= CHOICE [release] OPTIONAL:Exist
| |
| +-release ::= NULL
| |
+-timeAlignmentTimerDedicated ::= ENUMERATED [infinity]
| |
+-phr-Config ::= CHOICE [setup] OPTIONAL:Exist
| |
+-setup ::= SEQUENCE
| |
+-periodicPHR-Timer ::= ENUMERATED [sf500]
| |
+-prohibitPHR-Timer ::= ENUMERATED [sf200]
| |
+-dl-PathlossChange ::= ENUMERATED [dB3]
| +-sps-Config ::= SEQUENCE OPTIONAL:Omit
| +-physicalConfigDedicated ::= SEQUENCE [0000110010] OPTIONAL:Exist
|
+-pdsch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-pucch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-pusch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-uplinkPowerControlDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-tpc-PDCCH-ConfigPUCCH ::= CHOICE [setup] OPTIONAL:Exist
|
| +-setup ::= SEQUENCE
|
|
+-tpc-RNTI ::= BIT STRING SIZE(16) [0000001111111111]
|
|
+-tpc-Index ::= CHOICE [indexOfFormat3]
|
|
+-indexOfFormat3 ::= INTEGER (1..15) [1]
|
+-tpc-PDCCH-ConfigPUSCH ::= CHOICE [setup] OPTIONAL:Exist
|
| +-setup ::= SEQUENCE
|
|
+-tpc-RNTI ::= BIT STRING SIZE(16) [0000000111111010]
|
|
+-tpc-Index ::= CHOICE [indexOfFormat3]
|
|
+-indexOfFormat3 ::= INTEGER (1..15) [1]
|
+-cqi-ReportConfig ::= SEQUENCE OPTIONAL:Omit
|
+-soundingRS-UL-ConfigDedicated ::= CHOICE OPTIONAL:Omit
|
+-antennaInfo ::= CHOICE [explicitValue] OPTIONAL:Exist
|
| +-explicitValue ::= SEQUENCE [0]
|
|
+-transmissionMode ::= ENUMERATED [tm1]
|
|
+-codebookSubsetRestriction ::= CHOICE OPTIONAL:Omit
|
|
+-ue-TransmitAntennaSelection ::= CHOICE [release]
|
|
+-release ::= NULL
|
+-schedulingRequestConfig ::= CHOICE OPTIONAL:Omit
+-securityConfigHO ::= SEQUENCE OPTIONAL:Omit
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

Eventhoughthedecodedmessageshownabovelooksverycomplicatedalready,itisnotfullydecoded.Itshowsonly
RRCpartdecode.IfyoudecodetheNASpartinthismessage,youwillgetthefollowingcontents.

OneveryimportantthingyouhavetokeepinmindisthatyouhavetocarefullypopulatethismessagesothatIcan
properlyhandles/matchestheinformationsentfromUEviaAttachRequest,otherwisethiswouldleadtoregistration
failure.

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

25/38

12/17/2014

ShareTechnote

AS_LTE:EMM,Attach accept
Attach accept ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Attach accept message identity ::= V
| +-Message type ::= MSG [42]
+-Spare half octet ::= V
| +-Spare half octet ::= FIX [0]
+-EPS attach result ::= V
| +-Spare ::= FIX [0]
| +-EPS attach result value ::= CHOICE [EPS only]
+-T3412 value ::= V
| +-Octet1 ::= DIVISION
|
+-Unit ::= CHOICE [value indicates that the timer is deactivated]
|
+-Timer value ::= INT (0..31) [0]
+-TAI list ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of tracking area identity list contents ::= LEN (0..255) [6]
| +-Octet2-97 ::= DIVISION
|
+-tracking area identity list contents ::= OCTETARRAY SIZE(0..96) [0000F1100001]
+-ESM message container ::= LV-E
| +-Octet1-Octet2 ::= DIVISION
| | +-Length of ESM message container ::= LEN (0..65535) [44]
| +-Octet3- ::= DIVISION
|
+-ESM message container contents ::= OCTETARRAY SIZE(0..65535)
[5201C10109100377777707616E726974737503636F6D
05010A012037270E8080210A0300000A81060A000001]
+-GUTI ::= TLV OPTIONAL:Exist
| +-Octet1 ::= DIVISION
| | +-EPS mobile identity IEI ::= IEI [50]
| +-Octet2 ::= DIVISION
| | +-Length of EPS mobile identity contents ::= LEN (0..255) [11]
| +-Octet3 ::= DIVISION
| | +-Spare ::= FIX [F]
| | +-Odd/even indication ::= CHOICE [even number of identity digits and also when the GUTI is
used]
| | +-Type of identity ::= CHOICE [GUTI]
| +-Octet4 ::= DIVISION
| | +-MCC digit 2 ::= INT (0..15) [0]
| | +-MCC digit 1 ::= INT (0..15) [0]
| +-Octet5 ::= DIVISION
| | +-MNC digit 3 ::= INT (0..15) [15]
| | +-MCC digit 3 ::= INT (0..15) [1]
| +-Octet6 ::= DIVISION
| | +-MNC digit 2 ::= INT (0..15) [1]
| | +-MNC digit 1 ::= INT (0..15) [0]
| +-Octet7 ::= DIVISION
| | +-MME Group ID ::= INT (0..255) [128]
| +-Octet8 ::= DIVISION
| | +-MME Group ID(continued) ::= INT (0..255) [1]
| +-Octet9 ::= DIVISION
| | +-MME Code ::= INT (0..255) [1]
| +-Octet10 ::= DIVISION
| | +-M-TMSI ::= INT (0..255) [0]
| +-Octet11 ::= DIVISION
| | +-M-TMSI(continued) ::= INT (0..255) [0]
| +-Octet12 ::= DIVISION
| | +-M-TMSI(continued) ::= INT (0..255) [0]
| +-Octet13 ::= DIVISION
|
+-M-TMSI(continued) ::= INT (0..255) [1]
+-Location area identification ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Location Area Identification IEI ::= IEI [13]
| +-Octet2 ::= DIVISION
| | +-MCC digit 2 ::= INT (0..15) [0]
| | +-MCC digit 1 ::= INT (0..15) [0]
| +-Octet3 ::= DIVISION
| | +-MNC digit 3 ::= INT (0..15) [0]
| | +-MCC digit 3 ::= INT (0..15) [0]
| +-Octet4 ::= DIVISION
| | +-MNC digit 2 ::= INT (0..15) [0]
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

26/38

12/17/2014

ShareTechnote

| | +-MNC digit 1 ::= INT (0..15) [0]

| +-Octet5 ::= DIVISION
| | +-LAC ::= INT (0..255) [0]
| +-Octet6 ::= DIVISION
|
+-LAC (continued) ::= INT (0..255) [0]
+-MS identity ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Mobile Identity IEI ::= IEI [23]
| +-Octet2 ::= DIVISION
| | +-Length of mobile identity contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-Identity digit 1 ::= INT (0..15) [0]
| | +-Odd/even indication ::= CHOICE [even number of identity digits and also when the TMSI/PTMSI is used]
| | +-Type of identity ::= CHOICE [No Identity]
| +-Octet4-Octet10 ::= DIVISION
|
+-Identity digit p ::= OCTETARRAY SIZE(0..7)
+-EMM cause ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-EMM cause IEI ::= IEI [53]
| +-Octet2 ::= DIVISION
|
+-Cause value ::= CHOICE [#2:IMSI unknown in HSS]
+-T3402 value ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-GPRS Timer IEI ::= IEI [17]
| +-Octet2 ::= DIVISION
|
+-Unit ::= CHOICE [value is incremented in multiples of 2 seconds]
|
+-Timer value ::= INT (0..31) [0]
+-T3423 value ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-GPRS Timer IEI ::= IEI [59]
| +-Octet2 ::= DIVISION
|
+-Unit ::= CHOICE [value is incremented in multiples of 2 seconds]
|
+-Timer value ::= INT (0..31) [0]
+-Equivalent PLMNs ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-PLMN List IEI ::= IEI [4A]
| +-Octet2 ::= DIVISION
| | +-Length of PLMN List contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-MCC digit 2 PLMN 1 ::= INT (0..15) [0]
| | +-MCC digit 1 PLMN 1 ::= INT (0..15) [0]
..... Octet 4 - Octet 45 .....
| +-Octet46 ::= DIVISION
| | +-MNC digit 3 PLMN 15 ::= INT (0..15) [0]
| | +-MCC digit 3 PLMN 15 ::= INT (0..15) [0]
| +-Octet47 ::= DIVISION
|
+-MNC digit 2 PLMN 15 ::= INT (0..15) [0]
|
+-MNC digit 1 PLMN 15 ::= INT (0..15) [0]
+-Emergency Number List ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Emergency Number List IEI ::= IEI [34]
| +-Octet2 ::= DIVISION
| | +-Length of Emergency Number List IE contents ::= LEN (0..255) [0]
| +-Octet3-50 ::= DIVISION
|
+-Emergency Number List IE contents ::= OCTETARRAY SIZE(0..48)
+-EPS network feature support ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-EPS network feature support IEI ::= IEI [64]
| +-Octet2 ::= DIVISION
| | +-Length of EPS network feature support contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
|
+-Spare ::= FIX [0]
|
+-IMS VoPS ::= CHOICE [IMS voice over PS session in S1 mode not supported]
+-Additional update result ::= TV OPTIONAL:Omit
+-Octet1 ::= DIVISION
+-Additional update result IEI ::= IEI [F-]
+-Spare ::= FIX [0]
+-Additional update result value ::= CHOICE [no additional information]

Ifyouseethecontentsshownabove,youwouldsee"ESMmessagecontainercontents",whichcanbefurtherdecoded
asbelow.TheIE(informationelement)markedinbluewouldbethemostimportantIEsforUEconnectiontodata
serviceapplication.
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

27/38

12/17/2014

ShareTechnote

NAS_LTE:ESM,Activate default EPS bearer context request

Activate default EPS bearer context request ::= DIVISION
+-EPS bearer identity ::= V
| +-EPS bearer identity value ::= CHOICE [EPS bearer identity value 5]
+-EPS session management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [2]
+-Procedure transaction identity ::= V
| +-Procedure transaction identity ::= CHOICE [Procedure transaction identity value 1]
+-Activate default EPS bearer context request message identity ::= V
| +-Message type ::= MSG [C1]
+-EPS QoS ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of EPS quality of service contents ::= LEN (0..255) [1]
| +-Octet2 ::= DIVISION
| | +-QCI ::= CHOICE [QCI 9]
| +-Octet3 ::= DIVISION
| | +-Maximum bit rate for uplink ::= CHOICE [Reserved(network to UE direction)/Subscribed
maximum bit rate for uplink(UE to network direction)]
| +-Octet4 ::= DIVISION
| | +-Maximum bit rate for downlink ::= CHOICE [Reserved(network to UE direction)/Subscribed
maximum bit rate for uplink(UE to network direction)]
| +-Octet5 ::= DIVISION
| | +-Guaranteed bit rate for uplink ::= CHOICE [Reserved(network to UE direction)/Subscribed
maximum bit rate for uplink(UE to network direction)]
| +-Octet6 ::= DIVISION
| | +-Guaranteed bit rate for downlink ::= CHOICE [Reserved(network to UE direction)/Subscribed
maximum bit rate for uplink(UE to network direction)]
| +-Octet7 ::= DIVISION
| | +-Maximum bit rate for uplink (extended) ::= CHOICE [Use the value indicated by the maximum
bit rate for uplink in octet 4]
| +-Octet8 ::= DIVISION
| | +-Maximum bit rate for downlink (extended) ::= CHOICE [Use the value indicated by the maximum
bit rate for uplink in octet 4]
| +-Octet9 ::= DIVISION
| | +-Guaranteed bit rate for uplink (extended) ::= CHOICE [Use the value indicated by the
guaranteed bit rate for uplink in octet 6]
| +-Octet10 ::= DIVISION
|
+-Guaranteed bit rate for downlink (extended) ::= CHOICE [Use the value indicated by the
guaranteed bit rate for uplink in octet 6]
+-Access point name ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of access point name contents ::= LEN (0..255) [16]
| +-Octet2-Octet101 ::= DIVISION
|
+-Access point name value ::= OCTETARRAY SIZE(0..100) [0377777707616E726974737503636F6D]
+-PDN address ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of PDN address contents ::= LEN (0..255) [5]
| +-Octet2 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-PDN type value ::= CHOICE [IPv4]
| +-Octet3-14 ::= DIVISION
|
+-PDN address information ::= OCTETARRAY SIZE(0..12) [0A012037]
+-Transaction identifier ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Transaction identifier IEI ::= IEI [5D]
| +-Octet2 ::= DIVISION
| | +-Length of Transaction identifier contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-TI flag ::= CHOICE [The message is sent from the side that originates the TI]
| | +-TIO ::= CHOICE [TI value 0]
| | +-Spare ::= FIX [0]
| +-Octet4 ::= DIVISION
|
+-ext ::= EXT (0..1) [1]
|
+-TIE ::= CHOICE [Reserved]
+-Negotiated QoS ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Quality of service IEI ::= IEI [30]
| +-Octet2 ::= DIVISION
| | +-Length of quality of service IE ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-Delay class ::= CHOICE [Subscribed delay class(MS to network direction)/Reserved(network to
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

28/38

12/17/2014

ShareTechnote

MS direction)]
| | +-Reliability class ::= CHOICE [Subscribed reliability class(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet4 ::= DIVISION
| | +-Peak throughput ::= CHOICE [Subscribed peak throughput(MS to network
direction)/Reserved(network to MS direction)]
| | +-spare ::= FIX [0]
| | +-Precedence class ::= CHOICE [Subscribed precedence(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet5 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-Mean throughput ::= CHOICE [Subscribed mean throughput(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet6 ::= DIVISION
| | +-Traffic Class ::= CHOICE [Subscribed traffic class(MS to network
direction)/Reserved(network to MS direction)]
| | +-Delivery order ::= CHOICE [Subscribed delivery order(MS to network
direction)/Reserved(network to MS direction)]
| | +-Delivery of erroneous SDUs ::= CHOICE [Subscribed delivery of erroneous SDUs(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet7 ::= DIVISION
| | +-Maximum SDU size ::= CHOICE [Subscribed maximum SDU size(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet8 ::= DIVISION
| | +-Maximum bit rate for uplink ::= CHOICE [Subscribed maximum bit rate for uplink(MS to
network direction)/Reserved(network to MS direction)]
| +-Octet9 ::= DIVISION
| | +-Maximum bit rate for downlink ::= CHOICE [Subscribed maximum bit rate for uplink(MS to
network direction)/Reserved(network to MS direction)]
| +-Octet10 ::= DIVISION
| | +-Residual BER ::= CHOICE [Subscribed residual BER(MS to network direction)/Reserved(network
to MS direction)]
| | +-SDU error ratio ::= CHOICE [Subscribed SDU error ratio(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet11 ::= DIVISION
| | +-Transfer delay ::= CHOICE [Subscribed transfer delay(MS to network
direction)/Reserved(network to MS direction)]
| | +-Traffic Handling priority ::= CHOICE [Subscribed traffic handling priority(MS to network
direction)/Reserved(network to MS direction)]
| +-Octet12 ::= DIVISION
| | +-Guaranteed bit rate for uplink ::= INT (0..255) [0]
| +-Octet13 ::= DIVISION
| | +-Guaranteed bit rate for downlink ::= INT (0..255) [0]
| +-Octet14 ::= DIVISION
| | +-Spare ::= FIX [0]
| | +-Signalling Indication ::= CHOICE [Not optimised for signalling traffic]
| | +-Source Statistics Descriptor ::= CHOICE [unknown]
| +-Octet15 ::= DIVISION
| | +-Maximum bit rate for downlink (extended) ::= CHOICE [Use the value indicated by the Maximum
bit rate for downlink in octet 9.]
| +-Octet16 ::= DIVISION
| | +-Guaranteed bit rate for downlink (extended) ::= CHOICE [Use the value indicated by the
Maximum bit rate for downlink in octet 9.]
| +-Octet17 ::= DIVISION
| | +-Maximum bit rate for uplink (extended) ::= CHOICE [Use the value indicated by the Maximum
bit rate for downlink in octet 9.]
| +-Octet18 ::= DIVISION
|
+-Guaranteed bit rate for uplink (extended) ::= CHOICE [Use the value indicated by the
Maximum bit rate for downlink in octet 9.]
+-Negotiated LLC SAPI ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-LLC SAPI IEI ::= IEI [32]
| +-Octet2 ::= DIVISION
|
+-Spare ::= FIX [0]
|
+-LLC SAPI value ::= CHOICE [LLC SAPI not assigned]
+-Radio priority ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
|
+-Radio priority IEI ::= IEI [8-]
|
+-spare ::= FIX [0]
|
+-Radio priority level value ::= CHOICE [priority level 1 (highest)]
+-Packet flow identifier ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Packet Flow Identifier IEI ::= IEI [34]
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

29/38

12/17/2014

ShareTechnote

| +-Octet2 ::= DIVISION

| | +-Length of Packet Flow Identifier IE ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
|
+-spare ::= FIX [0]
|
+-Packet Flow Identifier value ::= CHOICE [Best Effort]
+-APN-AMBR ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-APN aggregate maximum bit rate IEI ::= IEI [5E]
| +-Octet2 ::= DIVISION
| | +-Length of APN aggregate maximum bit rate contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-APN-AMBR for downlink ::= CHOICE [1kbps]
| +-Octet4 ::= DIVISION
| | +-APN-AMBR for uplink ::= CHOICE [1kbps]
| +-Octet5 ::= DIVISION
| | +-APN-AMBR for downlink (extended) ::= CHOICE [Use the value indicated by the APN-AMBR for
downlink in octet 3]
| +-Octet6 ::= DIVISION
| | +-APN-AMBR for uplink (extended) ::= CHOICE [8700kbps]
| +-Octet7 ::= DIVISION
| | +-APN-AMBR for downlink (extended-2) ::= CHOICE [Use the value indicated by the APN-AMBR for
downlink and APN-AMBR for downlink (extended) in octets 3 and 5 0]
| +-Octet8 ::= DIVISION
|
+-APN-AMBR for uplink (extended-2) ::= CHOICE [Use the value indicated by the APN-AMBR for
downlink and APN-AMBR for downlink (extended) in octets 3 and 5 0]
+-ESM cause ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-ESM cause IEI ::= IEI [58]
| +-Octet2 ::= DIVISION
|
+-Cause value ::= CHOICE [#8:Operator Determined Barring]
+-Protocol configuration options ::= TLV OPTIONAL:Exist
+-Octet1 ::= DIVISION
| +-Protocol configuration options IEI ::= IEI [27]
+-Octet2 ::= DIVISION
| +-Length of protocol config options contents ::= LEN (0..255) [14]
+-Octet3 ::= DIVISION
| +-ext ::= EXT1 [1]
| +-spare ::= FIX [0]
| +-Configuration protocol ::= CHOICE [PPP for use with IP PDP type]
+-Octet4-Octet253 ::= DIVISION
+-protocol config options contents ::= OCTETARRAY SIZE(0..250) [80210A0300000A81060A000001]

Thereisoneimportantthingyouhavetoknowatthispoint.ItisabouthowtospecifyPDNaddress.Followingthree
examplescanbeselfsufficient(Ihope:).ForalittlebitfurtherdetailsforIPv6,refertoIPv6page.

<Example:IPv4>

+-PDN address ::= LV

| +-Octet1 ::= DIVISION
| | +-Length of PDN address contents ::= LEN (0..255) [5]
| +-Octet2 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-PDN type value ::= CHOICE [IPv4]
| +-Octet3-14 ::= DIVISION
|
+-PDN address information ::= OCTETARRAY SIZE(0..12) [0A012037]

<Example:IPv6>
:SpecifythelinklocaladdressofIPv6address.

+-PDN address ::= LV

| +-Octet1 ::= DIVISION
| | +-Length of PDN address contents ::= LEN (0..255) [9]
| +-Octet2 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-PDN type value ::= CHOICE [IPv6]
| +-Octet3-14 ::= DIVISION
|
+-PDN address information ::= OCTETARRAY SIZE(0..12) [0000000001010002]

<Example:IPv4v6>
:SpecifythelinklocaladdressofIPv6addressfollowedbyIPv4address.
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

30/38

12/17/2014

ShareTechnote

+-PDN address ::= LV

| +-Octet1 ::= DIVISION
| | +-Length of PDN address contents ::= LEN (0..255) [13]
| +-Octet2 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-PDN type value ::= CHOICE [IPv4v6]
| +-Octet3-14 ::= DIVISION
|
+-PDN address information ::= OCTETARRAY SIZE(0..12) [00000000010100020A0A0A0A]

<Protocolconfigurationoptions>

Thisisaprettycomplicatedtopic.SoIwilldescribethisonaseparateposthere.

RRC:RRCConnectionReconfigurationComplete+NAS:
AttachComplete+ESM:ActivateDefaultEPSBearerContextAccept

Animportantproceduredoneinthisstepis"ESM:ActivateDefaultEPSBearerContextAccept".
RRC Connection Reconfiguration Complete part is very simple as follows.
RRC_LTE:UL-DCCH-Message
UL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfigurationComplete]
+-rrcConnectionReconfigurationComplete ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [rrcConnectionReconfigurationComplete-r8]
+-rrcConnectionReconfigurationComplete-r8 ::= SEQUENCE [0]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

NASparthasprettycomplicatedstructuresinceitisPiggybackedmultipletimes.

RRC_LTE:ULDCCHMessage
ULDCCHMessage::=SEQUENCE
+message::=CHOICE[c1]
+c1::=CHOICE[ulInformationTransfer]
+ulInformationTransfer::=SEQUENCE
+criticalExtensions::=CHOICE[c1]
+c1::=CHOICE[ulInformationTransferr8]
+ulInformationTransferr8::=SEQUENCE[0]
+dedicatedInfoType::=CHOICE[dedicatedInfoNAS]
|+dedicatedInfoNAS::=OCTETSTRINGSIZE(ALIGNED)[074300035200C2]
+nonCriticalExtension::=SEQUENCEOPTIONAL:Omit
IfyoudecodededicatedInfoNAS::=OCTETSTRINGSIZE(ALIGNED)[074300035200C2],youwillgetthefollowing
message(AttachComplete).
NAS_LTE:EMM,Attach complete
Attach complete ::= DIVISION
+-Security header type ::= V
| +-Security header type ::= CHOICE [Plain NAS message, not security protected]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-Attach complete message identity ::= V
| +-Message type ::= MSG [43]
+-ESM message container ::= LV-E
+-Octet1-Octet2 ::= DIVISION
| +-Length of ESM message container ::= LEN (0..65535) [3]
+-Octet3- ::= DIVISION
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

31/38

12/17/2014

ShareTechnote

+-ESM message container contents ::= OCTETARRAY SIZE(0..65535) [5200C2]

IfyoudecodeESMmessagecontainercontents::=OCTETARRAYSIZE(0..65535)[5200C2]part,youwillgetthe
followingmessage(ActivatedefaultEPSbearercontextaccept).

NAS_LTE:ESM,Activate default EPS bearer context accept

Activate default EPS bearer context accept ::= DIVISION
+-EPS bearer identity ::= V
| +-EPS bearer identity value ::= CHOICE [EPS bearer identity value 5]
+-EPS session management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [2]
+-Procedure transaction identity ::= V
| +-Procedure transaction identity ::= CHOICE [No procedure transaction identity assigned]
+-Activate default EPS bearer context accept message identity ::= V
| +-Message type ::= MSG [C2]
+-Protocol configuration options ::= TLV OPTIONAL:Omit
+-Octet1 ::= DIVISION
| +-Protocol configuration options IEI ::= IEI [27]
+-Octet2 ::= DIVISION
| +-Length of protocol config options contents ::= LEN (0..255) [0]
+-Octet3 ::= DIVISION
| +-ext ::= EXT1 [1]
| +-spare ::= FIX [0]
| +-Configuration protocol ::= CHOICE [PPP for use with IP PDP type]
+-Octet4-Octet253 ::= DIVISION
+-protocol config options contents ::= OCTETARRAY SIZE(0..250)

RRC:RRCConnectionRequest

Sameasstep6,butestablishmentcausegetsdifferentasshownbelow.ItwillbemtAccessormoDatadepending
onwhetheritisMTcallorMOcall.
RRC_LTE:UL-CCCH-Message
UL-CCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionRequest]
+-rrcConnectionRequest ::= SEQUENCE
+-criticalExtensions ::= CHOICE [rrcConnectionRequest-r8]
+-rrcConnectionRequest-r8 ::= SEQUENCE
+-ue-Identity ::= CHOICE [s-TMSI]
| +-s-TMSI ::= SEQUENCE
|
+-mmec ::= BIT STRING SIZE(8) [00000001]
|
+-m-TMSI ::= BIT STRING SIZE(32) [00000000000000000000000000000001]
+-establishmentCause ::= ENUMERATED [mt-Access]
+-spare ::= BIT STRING SIZE(1) [0]

RRC:RRCConnectionSetup

RefertoRRCConnectionSetup

RRC:RRCConnectionSetupComplete+NAS:ServiceRequest
RRC_LTE:UL-DCCH-Message
UL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionSetupComplete]
+-rrcConnectionSetupComplete ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionSetupComplete-r8]
+-rrcConnectionSetupComplete-r8 ::= SEQUENCE [00]
+-selectedPLMN-Identity ::= INTEGER (1..6) [1]
+-registeredMME ::= SEQUENCE OPTIONAL:Omit
+-dedicatedInfoNAS ::= OCTET STRING SIZE(ALIGNED) [C7E00000]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
IfyoudecodededicatedInfoNAS::=OCTETSTRINGSIZE(ALIGNED)[C7E00000]part,youwillgetthefollowing
message(ServiceRequest).

NAS_LTE:EMM,Service request
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

32/38

12/17/2014

ShareTechnote

Service request ::= DIVISION

+-Security header type ::= V
| +-Security header type ::= CHOICE [Security header for the SERVICE REQUEST message]
+-EPS mobility management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [7]
+-KSI and sequence number ::= V
| +-Octet1 ::= DIVISION
|
+-KSI ::= CHOICE [no key is available]
|
+-Sequence number(short) ::= INT (0..31) [0]
+-Message authentication code (short) ::= V
+-Octet1 ::= DIVISION
| +-Short MAC value ::= INT (0..255) [0]
+-Octet2 ::= DIVISION
+-Short MAC value(continued) ::= INT (0..255) [0]

RRC:SecurityModeCommand

RefertoRRC:SecurityModeCommand

RRC:SecurityModeComplete

RefertoRRC:SecurityModeComplete

RRC:RRCConnectionReconfiguration+NAS:ActivateDedicatedEPSBearerContextRequest

Thisisanother'RRCConnectionReconfiguration'message.Butyouwouldseesomedifferencebetweenthismessage
andthemessageatstep15.
Youdon'tseeany'AttachAccept'partbecauseyoualreadywentthrough'attach'processduringtheregistration.And
nowyoucreatedonly'DedicatedEPSBearer'.Doesthismeanthatyoucannotusethe'DefaultEPSBearer'you
createdatstep15)?No..thedefaultBearerisstillaliveonceitiscreatedduringtheregistration.That'swhyyou
don'thavetorecreatethedefaultEPSbeareratthisstep.

Onethinkyouwouldnoticewouldbethat'ActivateDedicatedEPSBearerContextRequest'doesnothaveIPaddress
setting.ThisisbecauseDedicatedEPSisusingthesameIPconfigurationspecifiedbyDefaultEPSBearer.The
purposeofDefaultEPSbeareristocreateadatapipewithadifferentQoSfromDefaultEPSQoS.ItmeansDedicated
EPSBearerislinkedtoaspecificDefaultEPSbearer.
Then,howdoweknowwhichdefaultEPSbearerislinkedtowhichDedicatedEPSBearer?
Thislinkisspecifiedby'LinkedEPSBearerIdentity'.Forexample,if'LinkedEPSBearerIdentity'issettobe5.It
meansthis'DedicatedEPSBearer'islinkedtotheDefaultEPSBearerwithBearerID=5andusethesameIP
configurationasdefinedinthedefaultEPSbearer.
DL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfiguration]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

33/38

12/17/2014

ShareTechnote
+-rrcConnectionReconfiguration ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfiguration-r8]
+-rrcConnectionReconfiguration-r8 ::= SEQUENCE [001100]
+-measConfig ::= SEQUENCE OPTIONAL:Omit
+-mobilityControlInfo ::= SEQUENCE OPTIONAL:Omit
+-dedicatedInfoNASList ::= SEQUENCE OF SIZE(1..maxDRB[11]) [1] OPTIONAL:Exist
| +-DedicatedInfoNAS ::= OCTET STRING SIZE(ALIGNED)
[1700000000036200C5050904686848480000000006213100023011]
+-radioResourceConfigDedicated ::= SEQUENCE [110101] OPTIONAL:Exist
| +-srb-ToAddModList ::= SEQUENCE OF SIZE(1..2) [1] OPTIONAL:Exist
| | +-SRB-ToAddMod ::= SEQUENCE [11]
| |
+-srb-Identity ::= INTEGER (1..2) [2]
| |
+-rlc-Config ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
| +-defaultValue ::= NULL
| |
+-logicalChannelConfig ::= CHOICE [defaultValue] OPTIONAL:Exist
| |
+-defaultValue ::= NULL
| +-drb-ToAddModList ::= SEQUENCE OF SIZE(1..maxDRB[11]) [2] OPTIONAL:Exist
| | +-DRB-ToAddMod ::= SEQUENCE [11111]
| | | +-eps-BearerIdentity ::= INTEGER (0..15) [5] OPTIONAL:Exist
| | | +-drb-Identity ::= INTEGER (1..32) [1]
| | | +-pdcp-Config ::= SEQUENCE [101] OPTIONAL:Exist
| | | | +-discardTimer ::= ENUMERATED [infinity] OPTIONAL:Exist
| | | | +-rlc-AM ::= SEQUENCE OPTIONAL:Omit
| | | | +-rlc-UM ::= SEQUENCE OPTIONAL:Exist
| | | | | +-pdcp-SN-Size ::= ENUMERATED [len12bits]
| | | | +-headerCompression ::= CHOICE [notUsed]
| | | |
+-notUsed ::= NULL
| | | +-rlc-Config ::= CHOICE [um-Bi-Directional] OPTIONAL:Exist
| | | | +-um-Bi-Directional ::= SEQUENCE
| | | |
+-ul-UM-RLC ::= SEQUENCE
| | | |
| +-sn-FieldLength ::= ENUMERATED [size10]
| | | |
+-dl-UM-RLC ::= SEQUENCE
| | | |
+-sn-FieldLength ::= ENUMERATED [size10]
| | | |
+-t-Reordering ::= ENUMERATED [ms50]
| | | +-logicalChannelIdentity ::= INTEGER (3..10) [3] OPTIONAL:Exist
| | | +-logicalChannelConfig ::= SEQUENCE [1] OPTIONAL:Exist
| | |
+-ul-SpecificParameters ::= SEQUENCE [1] OPTIONAL:Exist
| | |
+-priority ::= INTEGER (1..16) [13]
| | |
+-prioritisedBitRate ::= ENUMERATED [infinity]
| | |
+-bucketSizeDuration ::= ENUMERATED [ms100]
| | |
+-logicalChannelGroup ::= INTEGER (0..3) [2] OPTIONAL:Exist
| | +-DRB-ToAddMod ::= SEQUENCE [11111]
| |
+-eps-BearerIdentity ::= INTEGER (0..15) [6] OPTIONAL:Exist
| |
+-drb-Identity ::= INTEGER (1..32) [2]
| |
+-pdcp-Config ::= SEQUENCE [101] OPTIONAL:Exist
| |
| +-discardTimer ::= ENUMERATED [infinity] OPTIONAL:Exist
| |
| +-rlc-AM ::= SEQUENCE OPTIONAL:Omit
| |
| +-rlc-UM ::= SEQUENCE OPTIONAL:Exist
| |
| | +-pdcp-SN-Size ::= ENUMERATED [len12bits]
| |
| +-headerCompression ::= CHOICE [notUsed]
| |
|
+-notUsed ::= NULL
| |
+-rlc-Config ::= CHOICE [um-Bi-Directional] OPTIONAL:Exist
| |
| +-um-Bi-Directional ::= SEQUENCE
| |
|
+-ul-UM-RLC ::= SEQUENCE
| |
|
| +-sn-FieldLength ::= ENUMERATED [size10]
| |
|
+-dl-UM-RLC ::= SEQUENCE
| |
|
+-sn-FieldLength ::= ENUMERATED [size10]
| |
|
+-t-Reordering ::= ENUMERATED [ms50]
| |
+-logicalChannelIdentity ::= INTEGER (3..10) [4] OPTIONAL:Exist
| |
+-logicalChannelConfig ::= SEQUENCE [1] OPTIONAL:Exist
| |
+-ul-SpecificParameters ::= SEQUENCE [1] OPTIONAL:Exist
| |
+-priority ::= INTEGER (1..16) [13]
| |
+-prioritisedBitRate ::= ENUMERATED [infinity]
| |
+-bucketSizeDuration ::= ENUMERATED [ms100]
| |
+-logicalChannelGroup ::= INTEGER (0..3) [3] OPTIONAL:Exist
| +-drb-ToReleaseList ::= SEQUENCE OF OPTIONAL:Omit
| +-mac-MainConfig ::= CHOICE [explicitValue] OPTIONAL:Exist
| | +-explicitValue ::= SEQUENCE [111]
| |
+-ul-SCH-Config ::= SEQUENCE [11] OPTIONAL:Exist
| |
| +-maxHARQ-Tx ::= ENUMERATED [n5] OPTIONAL:Exist
| |
| +-periodicBSR-Timer ::= ENUMERATED [sf20] OPTIONAL:Exist

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

34/38

12/17/2014

ShareTechnote
| |
| +-retxBSR-Timer ::= ENUMERATED [sf320]
| |
| +-ttiBundling ::= BOOLEAN [FALSE]
| |
+-drx-Config ::= CHOICE [release] OPTIONAL:Exist
| |
| +-release ::= NULL
| |
+-timeAlignmentTimerDedicated ::= ENUMERATED [infinity]
| |
+-phr-Config ::= CHOICE [setup] OPTIONAL:Exist
| |
+-setup ::= SEQUENCE
| |
+-periodicPHR-Timer ::= ENUMERATED [sf500]
| |
+-prohibitPHR-Timer ::= ENUMERATED [sf200]
| |
+-dl-PathlossChange ::= ENUMERATED [dB3]
| +-sps-Config ::= SEQUENCE OPTIONAL:Omit
| +-physicalConfigDedicated ::= SEQUENCE [0000110010] OPTIONAL:Exist
|
+-pdsch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-pucch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-pusch-ConfigDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-uplinkPowerControlDedicated ::= SEQUENCE OPTIONAL:Omit
|
+-tpc-PDCCH-ConfigPUCCH ::= CHOICE [setup] OPTIONAL:Exist
|
| +-setup ::= SEQUENCE
|
|
+-tpc-RNTI ::= BIT STRING SIZE(16) [0000001111111111]
|
|
+-tpc-Index ::= CHOICE [indexOfFormat3]
|
|
+-indexOfFormat3 ::= INTEGER (1..15) [1]
|
+-tpc-PDCCH-ConfigPUSCH ::= CHOICE [setup] OPTIONAL:Exist
|
| +-setup ::= SEQUENCE
|
|
+-tpc-RNTI ::= BIT STRING SIZE(16) [0000000111111010]
|
|
+-tpc-Index ::= CHOICE [indexOfFormat3]
|
|
+-indexOfFormat3 ::= INTEGER (1..15) [1]
|
+-cqi-ReportConfig ::= SEQUENCE OPTIONAL:Omit
|
+-soundingRS-UL-ConfigDedicated ::= CHOICE OPTIONAL:Omit
|
+-antennaInfo ::= CHOICE [defaultValue] OPTIONAL:Exist
|
| +-defaultValue ::= NULL
|
+-schedulingRequestConfig ::= CHOICE OPTIONAL:Omit
+-securityConfigHO ::= SEQUENCE OPTIONAL:Omit
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit

Activate dedicated EPS bearer context request ::= DIVISION

+-EPS bearer identity ::= V
| +-EPS bearer identity value ::= CHOICE [EPS bearer identity value 6]
+-EPS session management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [2]
+-Procedure transaction identity ::= V
| +-Procedure transaction identity ::= CHOICE [No procedure transaction identity assigned]
+-Activate dedicated EPS bearer context request message identity ::= V
| +-Message type ::= MSG [C5]
+-Spare half octet ::= V
| +-Spare half octet ::= FIX [0]
+-Linked EPS bearer identity ::= V
| +-Linked EPS bearer identity value ::= CHOICE [EPS bearer identity value 5]
+-EPS QoS ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of EPS quality of service contents ::= LEN (0..255) [9]
| +-Octet2 ::= DIVISION
| | +-QCI ::= CHOICE [QCI 4]
| +-Octet3 ::= DIVISION
| | +-Maximum bit rate for uplink ::= CHOICE [384kbps]
| +-Octet4 ::= DIVISION
| | +-Maximum bit rate for downlink ::= CHOICE [384kbps]
| +-Octet5 ::= DIVISION
| | +-Guaranteed bit rate for uplink ::= CHOICE [128kbps]
| +-Octet6 ::= DIVISION
| | +-Guaranteed bit rate for downlink ::= CHOICE [128kbps]
| +-Octet7 ::= DIVISION
| | +-Maximum bit rate for uplink (extended) ::=
CHOICE [Use the value indicated by the maximum bit rate for uplink in octet 4]
| +-Octet8 ::= DIVISION
| | +-Maximum bit rate for downlink (extended) ::=
CHOICE [Use the value indicated by the maximum bit rate for uplink in octet 4]
| +-Octet9 ::= DIVISION
| | +-Guaranteed bit rate for uplink (extended) ::=
CHOICE [Use the value indicated by the guaranteed bit rate for uplink in octet 6]
| +-Octet10 ::= DIVISION
|
+-Guaranteed bit rate for downlink (extended) ::=
CHOICE [Use the value indicated by the guaranteed bit rate for uplink in octet 6]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

35/38

12/17/2014

ShareTechnote

+-TFT ::= LV
| +-Octet1 ::= DIVISION
| | +-Length of traffic flow template IE ::= LEN (0..255) [6]
| +-Octet2 ::= DIVISION
| | +-TFT operation code ::= CHOICE [Create new TFT]
| | +-E bit ::= CHOICE [parameters list is not included]
| | +-Number of packet filters ::= INT (0..15) [1]
| +-Octet3-Octet256 ::= DIVISION
|
+-Packet filter list/Parameters list ::= OCTETARRAY SIZE(0..254) [3100023011]
+-Transaction identifier ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Transaction identifier IEI ::= IEI [5D]
| +-Octet2 ::= DIVISION
| | +-Length of Transaction identifier contents ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-TI flag ::= CHOICE [The message is sent from the side that originates the TI]
| | +-TIO ::= CHOICE [TI value 0]
| | +-Spare ::= FIX [0]
| +-Octet4 ::= DIVISION
|
+-ext ::= EXT (0..1) [1]
|
+-TIE ::= CHOICE [Reserved]
+-Negotiated QoS ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Quality of service IEI ::= IEI [30]
| +-Octet2 ::= DIVISION
| | +-Length of quality of service IE ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-Delay class ::= CHOICE [Subscribed delay class(MS to network direction)/Reserved(network to MS direction)]
| | +-Reliability class ::=
CHOICE [Subscribed reliability class(MS to network direction)/Reserved(network to MS direction)]
| +-Octet4 ::= DIVISION
| | +-Peak throughput ::=
CHOICE [Subscribed peak throughput(MS to network direction)/Reserved(network to MS direction)]
| | +-spare ::= FIX [0]
| | +-Precedence class ::=
CHOICE [Subscribed precedence(MS to network direction)/Reserved(network to MS direction)]
| +-Octet5 ::= DIVISION
| | +-spare ::= FIX [0]
| | +-Mean throughput ::=
CHOICE [Subscribed mean throughput(MS to network direction)/Reserved(network to MS direction)]
| +-Octet6 ::= DIVISION
| | +-Traffic Class ::=
CHOICE [Subscribed traffic class(MS to network direction)/Reserved(network to MS direction)]
| | +-Delivery order ::=
CHOICE [Subscribed delivery order(MS to network direction)/Reserved(network to MS direction)]
| | +-Delivery of erroneous SDUs ::=
CHOICE [Subscribed delivery of erroneous SDUs(MS to network direction)/Reserved(network to MS direction)]
| +-Octet7 ::= DIVISION
| | +-Maximum SDU size ::=
CHOICE [Subscribed maximum SDU size(MS to network direction)/Reserved(network to MS direction)]
| +-Octet8 ::= DIVISION
| | +-Maximum bit rate for uplink ::=
CHOICE [Subscribed maximum bit rate for uplink(MS to network direction)/Reserved(network to MS direction)]
| +-Octet9 ::= DIVISION
| | +-Maximum bit rate for downlink ::=
CHOICE [Subscribed maximum bit rate for uplink(MS to network direction)/Reserved(network to MS direction)]
| +-Octet10 ::= DIVISION
| | +-Residual BER ::=
CHOICE [Subscribed residual BER(MS to network direction)/Reserved(network to MS direction)]
| | +-SDU error ratio ::=
CHOICE [Subscribed SDU error ratio(MS to network direction)/Reserved(network to MS direction)]
| +-Octet11 ::= DIVISION
| | +-Transfer delay ::=
CHOICE [Subscribed transfer delay(MS to network direction)/Reserved(network to MS direction)]
| | +-Traffic Handling priority ::=
CHOICE [Subscribed traffic handling priority(MS to network direction)/Reserved(network to MS direction)]
| +-Octet12 ::= DIVISION
| | +-Guaranteed bit rate for uplink ::= INT (0..255) [0]
| +-Octet13 ::= DIVISION
| | +-Guaranteed bit rate for downlink ::= INT (0..255) [0]
| +-Octet14 ::= DIVISION
| | +-Spare ::= FIX [0]

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

36/38

12/17/2014

ShareTechnote

|
|
|
|

| +-Signalling Indication ::= CHOICE [Not optimised for signalling traffic]

| +-Source Statistics Descriptor ::= CHOICE [unknown]
+-Octet15 ::= DIVISION
| +-Maximum bit rate for downlink (extended) ::=
CHOICE [Use the value indicated by the Maximum bit rate for downlink
| +-Octet16 ::= DIVISION
| | +-Guaranteed bit rate for downlink (extended) ::=
CHOICE [Use the value indicated by the Maximum bit rate for downlink
| +-Octet17 ::= DIVISION
| | +-Maximum bit rate for uplink (extended) ::=
CHOICE [Use the value indicated by the Maximum bit rate for downlink
| +-Octet18 ::= DIVISION
|
+-Guaranteed bit rate for uplink (extended) ::=
CHOICE [Use the value indicated by the Maximum bit rate for downlink
+-Negotiated LLC SAPI ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-LLC SAPI IEI ::= IEI [32]
| +-Octet2 ::= DIVISION
|
+-Spare ::= FIX [0]
|
+-LLC SAPI value ::= CHOICE [LLC SAPI not assigned]
+-Radio priority ::= TV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
|
+-Radio priority IEI ::= IEI [8-]
|
+-spare ::= FIX [0]
|
+-Radio priority level value ::= CHOICE [priority level 1 (highest)]
+-Packet flow identifier ::= TLV OPTIONAL:Omit
| +-Octet1 ::= DIVISION
| | +-Packet Flow Identifier IEI ::= IEI [34]
| +-Octet2 ::= DIVISION
| | +-Length of Packet Flow Identifier IE ::= LEN (0..255) [0]
| +-Octet3 ::= DIVISION
|
+-spare ::= FIX [0]
|
+-Packet Flow Identifier value ::= CHOICE [Best Effort]
+-Protocol configuration options ::= TLV OPTIONAL:Omit
+-Octet1 ::= DIVISION
| +-Protocol configuration options IEI ::= IEI [27]
+-Octet2 ::= DIVISION
| +-Length of protocol config options contents ::= LEN (0..255) [0]
+-Octet3 ::= DIVISION
| +-ext ::= EXT1 [1]
| +-spare ::= FIX [0]
| +-Configuration protocol ::= CHOICE [PPP for use with IP PDP type]
+-Octet4-253 ::= DIVISION
+-protocol config options contents ::= OCTETARRAY SIZE(0..250)

in octet 9.]

in octet 9.]

in octet 9.]

in octet 9.]

RRC:RRCConnectionReconfigurationComplete+NAS:ActivateDedicatedEPSBearerContextAccept
RRCConnectionReconfigurationCompletepartisverysimpleasshownbelow.
RRC_LTE:UL-DCCH-Message
UL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [rrcConnectionReconfigurationComplete]
+-rrcConnectionReconfigurationComplete ::= SEQUENCE
+-rrc-TransactionIdentifier ::= INTEGER (0..3) [0]
+-criticalExtensions ::= CHOICE [rrcConnectionReconfigurationComplete-r8]
+-rrcConnectionReconfigurationComplete-r8 ::= SEQUENCE [0]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
ESM,Activate dedicated EPS bearer context accept part is carried by UL information transfer message
as follows.
RRC_LTE:UL-DCCH-Message
UL-DCCH-Message ::= SEQUENCE
+-message ::= CHOICE [c1]
+-c1 ::= CHOICE [ulInformationTransfer]
+-ulInformationTransfer ::= SEQUENCE
+-criticalExtensions ::= CHOICE [c1]
+-c1 ::= CHOICE [ulInformationTransfer-r8]
+-ulInformationTransfer-r8 ::= SEQUENCE [0]
+-dedicatedInfoType ::= CHOICE [dedicatedInfoNAS]
| +-dedicatedInfoNAS ::= OCTET STRING SIZE(ALIGNED) [6200C6]
+-nonCriticalExtension ::= SEQUENCE OPTIONAL:Omit
http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

37/38

12/17/2014

ShareTechnote

IfyoudecodededicatedInfoNAS::=OCTETSTRINGSIZE(ALIGNED)[6200C6]part,youwillgetthefollowing
message(ESM,ActivatededicatedEPSbearercontextaccept)
NAS_LTE:ESM,Activate dedicated EPS bearer context accept
Activate dedicated EPS bearer context accept ::= DIVISION
+-EPS bearer identity ::= V
| +-EPS bearer identity value ::= CHOICE [EPS bearer identity value 6]
+-EPS session management protocol discriminator ::= V
| +-Protocol discriminator ::= PD [2]
+-Procedure transaction identity ::= V
| +-Procedure transaction identity ::= CHOICE [No procedure transaction identity assigned]
+-Activate dedicated EPS bearer context accept message identity ::= V
| +-Message type ::= MSG [C6]
+-Protocol configuration options ::= TLV OPTIONAL:Omit
+-Octet1 ::= DIVISION
| +-Protocol configuration options IEI ::= IEI [27]
+-Octet2 ::= DIVISION
| +-Length of protocol config options contents ::= LEN (0..255) [0]
+-Octet3 ::= DIVISION
| +-ext ::= EXT1 [1]
| +-spare ::= FIX [0]
| +-Configuration protocol ::= CHOICE [PPP for use with IP PDP type]
+-Octet4-Octet253 ::= DIVISION
+-protocol config options contents ::= OCTETARRAY SIZE(0..250)

http://www.sharetechnote.com/html/BasicCallFlow_LTE.html

38/38