com
Whatisthemosttrickypartindevicetroubleshooting?Myexperiencesays"Ifaproblemhappensinthemiddleofdoing
something,itisrelativelyeasytofindtherootcauseandtroubleshootit(probablyImighthaveoversimplifiedthe
situation:),butifsomethinghappenedbeforeanythingstarted,itwouldbeanightmare."Forexample,yousettheall
theparametersatthenetworkemulatorforaUEyouwanttotestandthenturnedontheUE.InaseveralsecondUE
startbootingandtheninacoupleofsecondyouseeacoupleofantennabarssomewhereatthetopofUEscreen..and
theninseveralsecondsyousee'SOS'or'ServiceNotAvailable'insteadofyournetworkoperatornamedisplayedon
yourscreenandnormalAntennabars.ThisiswhatImeanby"probleminthemiddleofdoingsomething".Inthiscase,
ifyoucollectUElogandequipmentlog,atleastyoucaneasilypinpointoutthelocationtheproblemhappensandstart
fromthereforfurtherdetails.Butwhatifyouareinthissituation?yousetthealltheparametersatthenetwork
emulatorsideandturnontheUE..UEstartbootingup..showingthemessagesaying"SearchingNetwork...."andgot
stuckthere..withnoAntennabars..noteven'SOS'..justsaying"Noservice".AndIcollectedUEsidelogandNetwork
Emulatorsidelog,butnosignallingmessage.Thisiswhereourheadachestarts.
Asexamples,
i)Whatifyoudon'tsee'RRCConnectionRequest'whenyourturnedontheWCDMAUE?
ii)Whatifyoudon'tsee'ChannelRequest'whenyourturnedontheGSMUE?
iii)Whatifyoudon'tsee'RACHPreamble'whenyourturnedontheLTEUE?
Firstthingyouhavetodoistounderstandtheeverydetailsofthisprocedurenotonlyinthehighersignalinglayer,but
alsoallthewaydowntothephysicallayersrelatedtothesefirststep.Andalsoyouhavetouseproperequipmentwhich
canshowthesedetailedprocess.Ifyouhaveanequipmentthatdoesnotprovidetheloggingoritprovideslogbutonly
higherlayersingnalinglog,itwillbeextremlydifficulttotroubleshoot.Giventhatyouhavethepropertools,thenext
thingyouhavetobereadyistounderstandthedetailedknowledgeoftheseprocess.Withouttheknowledge,however
goodtoolsIhaveitdoesn'tmeananythingtome.So?IwanttoteachmyselfhereaboutthefirststepofLTEsignaling
whichisRACHprocess.(SomebodywouldsaytherearemanyofotherstepsevenbeforetheRACH,likefrequencySync,
TimeSync,MIB/SIBdecoding..butitputtheseasidefornow..sinceitismorelikebasebandprocessing).
WhyRACH?(WhatisthefunctionalityofRACH?)
WhenRACHProcessoccurs?
TwotypesofRACHprocess:ContentionbasedandContentionfree
HowtheinformationisencodedintoPRACH(RACHPreamble)?
ExactlywhenandWhereaUEtransmitRACH?
Whatispreambleformat?
WhyMultiplePreambleFormat?
HowtodeterminedwhichPreambleformattouse?
HowdoesNetworkknowsexactlywhenUEwilltransmittheRACH?
HowmanyRAPreamblescanbeused?
HowtoGenerate64PRACHPreambleSequences?
PRACHPreambleSignalStructure
HowtogenerateRACHSignal?
PRACHSequenceinFrequencyDomain
PRACHSequenceinTimeDomain
ExactlywhenandwhereNetworktransmitRACHResponse
PRACHParametersandit'sPhysicalMeaning
prachConfigIndex
zeroCorrelationZoneConfigandHighspeedflag
prachFreqOffset
rootSequenceIndex
RACHProcedureduringInitialRegistrationRACHProcedureSummary
HowcanwegetRARNTI?
AnExampleofFullRACHProcess
PRACHRetransmission
RACHProcessOverviewInDiagrams
RACHProcedureonInitialRegistration
RACHProcedureonHandoverContentionBased
RACHProcedureonHandoverNonContentionBased
RACHProcedureonDLDataArrivalwhenOutofSyncNonContentionBased
RACHProcedureonDLDataArrivalwhenOutofSyncContentionBased
RACHProcedureonULDataArrivalwhenOutofSync
RACHProcedureonRRCConnectionReestablishmentwhenOutofSync
PRACHRFSnapshot
3GPPStandardforRACHProcess
GlobaliteMen's
Rs.349.00
GlobaliteMen's
Rs.349.00Rs.
499.00
GuavaMen's
Rs.749.00
WhyRACH?(WhatisthefunctionalityofRACH?)
ThefirstquestionpopingupinyourmindwhenyoufirsthearaboutthewordRACHorRACHProcesswouldbe'Why
RACH?','Whatisthefunctionality/purposeofRACHprocess?',"Whyweneedthiskindofcomplicated(looksover
complicated)?'.
Forsure,itisnotforconfusingyou:),RACHhasveryimportantfunctionalityespeciallyinLTE(andinWCDMAaswell).
ThemainpurposeofRACHcanbedescribedasfollows.
i)AchieveUPlinksynchronizationbetweenUEandeNB
ii)ObtaintheresourceforMessage3(e.g,RRCConnectionRequest)
Inmostofthecommunication(especiallydigitalcomunicationregardlessofwhetheritiswiredorwireless),themost
importantpreconditionistoestablishthetimingsynchronizationbetweentherecieverandtransmitter.Sowhatever
communicationtechnologyyouwouldstudy,youwouldseesomekindofsynchronizationmechanismthatisspecially
designedforthespecificcommunication.
InLTE(inWCDMAaswell),thesynchronizationindownlink(Transmitter=eNB,Reciever=UE),thissynchronizationis
achievedbythespecialsynchronizationchannel(specialphysicalsignalpattern).RefertoTimeSyncProcesspagefor
thedetails.Thisdownlinksyncsignalgetsbroadcastedtoeverybodyanditisgettransmittedallthetimewithacertain
interval.
HoweverinUplink(Transmitter=UE,Reciever=eNB),itisnotefficient(actuallywasteofenergyandcausingalotof
interferencetootherUEs)ifUEisusingthiskindofbroadcasting/alwaysonsynchronizationmechanism.Youmayeasily
understandthiskindofproblem.Incaseofuplink,thissynchronizationprocessshouldmeetfollowingcriteria
i)Thesynchronizationprocessshouldhappenonlywhenthereisimmediatenecessity
ii)ThesynchronizationshouldbededicatedtoonlyaspecificUE
Allthecomplicated/confusingstoriesinthispageismostlyabouttheprocessspeciallydesignedmechanismtomeet
thesecriteria.
AnotherpurposeofRACHprocessistoobtaintheresourceforMsg3(Message3).RRCConnectionRequestisone
exampleofMsg3andthereareseveraldifferenttypesofMsg3dependingonsituation.Youwouldfigureoutthispartin
readingthroughthispageandthisisnotverycomplicatedtounderstand.
WhenRACHProcessoccurs?
Itwouldbehelpfultounderstandifyouthinkaboutwhen'RRCConnection'happens(orwhenPRACHprocesshappensif
youareinterestedinlowerlayerstuffs)inWCDMA.Itwouldalsobehelpfulifyouthinkaboutwhen'ChannelRequest'
happensinGSMUE.
MyimpressionofLTERACHprocessislikethecombinationofPRACHprocess(WCDMA)andChannelRequest(GSM).It
maynotbe100%correctanalogy..butanywayIgotthiskindofimpression.InLTE,RACHprocesshappensinfollowing
situation(3GPPspecification,10.1.5RandomAccessProcedureof36.300)
i)InitialaccessfromRRC_IDLE
ii)RRCConnectionReestablishmentprocedure
iii)Handove(ContentionBasedorNonContetionBased)
iv)DLdataarrivalduringRRC_CONNECTEDrequiringrandomaccessprocedure
E.g.whenULsynchronisationstatusisnonsynchronised
v)ULdataarrivalduringRRC_CONNECTEDrequiringrandomaccessprocedure
E.g.whenULsynchronisationstatusis"nonsynchronised"ortherearenoPUCCHresourcesforSRavailable.
vi)ForpositioningpurposeduringRRC_CONNECTEDrequiringrandomaccessprocedure
E.g.whentimingadvanceisneededforUEpositioning
TwotypesofRACHprocess:ContentionbasedandContentionfree
WhenaUEtransmitaPRACHPreamble,ittransmitswithaspecificpatternandthisspecificpatterniscalleda
"Signature".IneachLTEcell,total64preamblesignaturesareavailableandUEselectrandomlyoneofthesesignatures.
UEselect"Randomly"oneofthesesignatures?
DoesthismeanthatthereissomepossibilitythatmultipleUEssendPRACHwithidenticalsignatures?
Yes.
Thereissuchapossibility.ItmeansthesamePRACHpreamblefrommultipeUEreachestheNWatthesametime..this
kindofPRACHcollisioniscalled"Contention"andtheRACHprocessthatallowsthistypeof"Contention"iscalled
"Contentionbased"RACHProcess.InthiskindofcontentionbasedRACHprocess,Networkwouldgothroughadditional
processatlatersteptoresolvethesecontentionandthisprocessiscalled"ContentionResolution"step.
Butthereissomecasesthatthesekindofcontentionisnotacceptableduetosomereason(e.g,timingrestriction)and
thesecontentioncanbeprevented.Usuallyinthiscase,theNetworkinformseachoftheUEofexactlywhenandwhich
preamblesignatureithastouse.Ofcourse,inthiscaseNetworkwillallocatethesepreamblesignaturesothatitwould
notcollide.ThiskindofRACHprocessiscalled"ContentionFree"RACHprocedure.Toinitiatethe"ContentionFree"
RACHprocess,UEshouldbeinConnectedModebeforetheRACHprocessasinHandovercase.
Typical'ContentionBased'RACHProcedureisasfollows:
i)UE>NW:RACHPreamble(RARNTI,indicationforL2/L3messagesize)
ii)UE<NW:RandomAccessResponse(TimingAdvance,T_CRNTI,ULgrantforL2/L3message)
iii)UE>NW:L2/L3message
iv)Messageforearlycontentionresolution
Nowlet'sassumethatacontentionhappenedatstepi).Forexample,twoUEssentPRACH.Inthiscase,bothoftheUE
willrecievethesameT_CRNTIandresourceallocationatstepii).Andasaresult,bothUEwouldsendL2/L3message
throughthesameresourceallocation(meaningwiththesametime/frequencylocation)toNWatstepiii).Whatwould
happenwhenbothUEtransmittheexactsameinformationontheexactsametime/frequencylocation?Onepossibility
isthatthesetwosignalactasinterferencetoeachotherandNWdecodeneitherofthem.Inthiscase,noneoftheUE
wouldhaveanyresponse(HARQACK)fromNWandtheyallthinkthatRACHprocesshasfailedandgobacktostepi).
TheotherpossibilitywouldbethatNWcouldsuccessfullydecodethemessagefromonlyoneUEandfailedtodecodeit
fromtheotherUE.Inthiscase,theUEwiththesuccessfulL2/L3decodingonNWsidewillgettheHARQACKfrom
Network.ThisHARQACKprocessforstepiii)messageiscalled"contentionresolution"process.
Typical'ContentionFree'RACHProcedureisasfollows:
i)UE<NW:RACHPreamble(PRACH)Assignment
ii)UE>NW:RACHPreamble(RARNTI,indicationforL2/L3messagesize)
iii)UE<NW:RandomAccessResponse(TimingAdvance,CRNTI,ULgrantforL2/L3message)
HowtheinformationisencodedintoPRACH(RACHPreamble)?
InLTE,alltheinformation(data)afterPRACHPreamblehasitsownbinarystructuremeaningthattheyaretranslated
intoacertaindatastructure.However,theinformationinPRACHPreambleisrepresentedbypurelyphysicalproperties.
ThephysicalpropertiesthatformstheinformationinPRACHareasfollows.
i)PRACHPreambletransmissionTiming(t_id)
ii)LocationofPRACHtransmissioninfrequencydomain(f_id)
iii)SequenceofthewholeI/QdataofPRACHsignal(oneexampleshownbelow)
FollowingisthePRACHsignaltransmittedinTimeDomain.(Youmaythinkthislooksdifferentfromwhatyouexpected.
YoumighthaveexpecttoseeZadoffChusequencebutthisdoesnotlooklikeaZadoffChusequence.TheZadoffChu
sequenceforPRACHisinFrequencyDomain,butthisisthetimedomainsequence.ThePRACHZadoffChuis
transformedtothetimedomainsequenceasshownbelowviaatransformationthatisshowninHowtoGenerateRACH
signalsection)
Fromitemi)andii),RA_RNTIisderibedasdescribedinHowcanwegetRARNTI.Fromitemiii),PreambleIndex
(RAPID)canbederived.
YoumaynothavemuchdifficultiesinunderstandingthederivationofRA_RNTIbutitwouldnotbethatsimpleto
understandthederivationofPreambleIndexpart.Mostofthethispagewithalotofequationsandcomplextablesare
relatedtothisprocess,butIdon'tthinkIdidagoodjobtosimply/clearlydescribethispart.Iwilladdanothershort
sectionsinthefuturewhenIhaveeverythingclearedupinmybrain.Inthemeantime,pleaserefertoMatlabLTE
Toolbox:PRACHpagetogettheintuitive(sorryitmaynotbethatintuitive:)imageinyourbrainandreadthesections
aboutPRACHPreamblesignalgenerationpartinthispage.Ofcourse,youwouldnotgeteverythingwithsinglelook.
Nothingcomeseasyinengineering:)
ExactlywhenandWhereaUEtransmitRACH?
Toanswertothisquestion,youneedtoreferto3GPPspecificationTS36.211Table5.7.12.Thistablewouldgiveyou
atwhichframeandsubframethatUEisallowedtotransmitaPRACHPreamble.Asyouseeatthistable,theprach
preambletimingandprachpreambletypeisdeterminedbyPRACHConfigurationIndex.The,howPRACHConfiguration
Indexisdetermined?ItisdeterminedbySIB2parameterprachConfigIndex.
Didyouopenthespecificationnow?ItshowsexactlywhenaUEissupposedtosendRACHdependingonaparameter
called"PRACHConfigurationIndex".
Forexample,iftheUEisusing"PRACHConfigurationIdex0",itshouldtransmittheRACHonlyinEVENnumber
SFN(SystemFrameNumber).Isthisgoodenoughanswer?DoesthismeanthatthisUEcantransmittheRACHinany
timewithinthespecifiedtheSFN?Theanswertothisquestionisin"SubFrameNumber"colulmnofthetable.Itsays
"1"for"PRACHConfigurationIdex0".ItmeanstheUEisallowedtotransmitRACHonlyatsubframenumber1ofevery
evenSFN.
Checkingyourunderstandingofthetable,Iwillgiveyouonequestion.Withwhich"PRACHConfigurationIdex",itwould
betheeasiestfortheNetworktodetecttheRACHfromUE?andWhy?
Theanswerwouldbe14,becauseUEcansendtheRACHinanySFNandanyslotswithintheframe.
Inabigpicture,youshouldknowallthedimmensionsinthefollowingdiagram.(TheRedrectangleisPRACHsignal).
TheR_SlotisdeterminedbyPRACHConfigurationIndexandR_lengthisdeterminedbyPremableformat.F_offsetis
derminedbythefollowingequationwhenthepreambleformatis0~3.n_RA_PRBoffsetinthisequationisspecifiedby
prachFreqOffsetinSIB2.(Referto36.2115.7Physicalrandomaccesschannelforthedetails)
<FDD>
<TDD:Preambleformat03>
<TDD:Preambleformat4>
Whatispreambleformat?
Ifyouseethetable5.7.11showabove,youseethecolumntitledas"PreambleFormat".Whatisthepreambleformat?
Itisdefinedasfollowingdiagram.
YouwouldseethatthelengthofPRACHpreamblevariesdependingonthepreambleformat.Forexample,thelengthof
PRACHwithpreambleformat0is(3186+24567)Samples.(Asyouknow,onesample(Ts)is1/30.72(=0.03255)us.It
isdefinedas1/(15000x2048)seconds(=0.03255us)in36.2114Framestructure).
WhyMultiplePreambleFormat?
Youmayask"Whyweneedthiskindofmultiplepreambleformat?",especially"WhyweneedvariousPRACHformat
withdifferentlengthintime?".
Firsttrytofigureoutwhatisthedifferenceamongpreambleformatbasedonthetableabove(Table5.7.11)?For
simplicity,let'sthinkofonlyformat0,1,2,3.
Let'slookintoT_SEQ(lengthofSequence).Youseeformat0andformat1ismadeupofsinglecopiesofPRACH
convertedintimedomain.Format2and3ismadeupoftwocopiesofPRACHsequenceconcatenated.Whatwouldbe
theadvantagethatformat2,3haveoverformat1,2.IthinkthelongerT_SEQwouldhelpdecodingPRACHundernoised
conditionbecauseitprovidelongercorrelationwindowtodetectPRACH.
Nowlet'slookatT_CPpart.youwouldnoticeformat2and3hasmuchlongerT_CPcomparingtoformat0and2.Longer
CPwouldgiveyoubettertoleranceinfadingenvironmentandreducingISIeveninhighlyfadingenvironment.
ActuallythereisanotherimportantdifferencesamongeachpreambleformatthatisnotexplicitelyshowninTable5.7.1
1.Itisguardtimedifference.Howthisguardtimeinfluencethecellsize?(RefertothecommentsbeloworCellSize
ConfigurationinRandomAccessProcedure(I)PreambleFormatatLTEUniversity)
Iwanttorecommendabooktitled"LTE:TheUMTSFromTheorytoPractice"Section19.4.2ThePRACHStructure.This
isthematerialthatdescribesthePRACHinthemostdetailedlevelIhaveeverread.
Justasabriefconclusionforcellsize,wecanrewritethetableasfollows.
Total
Preamble
T_CP
T_CP
T_SEQ
T_SEQ
Numberof
GuardTime
Length
CellRadius
Format
(inTs)
(inms)
(inTs)
(inms)
Subframes
(inms)
(inms)
0
3168
0.103
24576
0.800
0.903
0.097
~14km
21024
6240
0.684
24576
0.800
1.484
0.516
~75km
0.203
2x24576
1.600
1.803
0.197
~28km
21024
0.684
2x24576
1.600
2.284
0.716
~108km
448
0.015
4096
0.133
0.148
Note1:T_CP(inms)=T_CP(inTs)x0.03255x1/1000,
where0.03225isoneTsinus,1/1000isusedtoconverttheunitfrom'us'to'ms'
Note2:T_SEQ(inms)=T_SEQ(inTs)x0.03255x1/1000,
where0.03225isoneTsinus,1/1000isusedtoconverttheunitfrom'us'to'ms'
Note3:GuardTime(inms)=NumberofSubframeTotalLength
Note4:CellRadiusisroughlythedistancethattheelectromaticwavecantravelduringtheguardtimeanddevidedby
2.
Incaseoffreespace(invacumm)itisroughlyis300(km/ms)xGuardTime(ms)/2.
HowtodeterminedwhichPreambleformattouse?
HowUEknowwhichPreambleformatithastousewhenitgeneratePRACHandtrnasmit?Itisdeterminedbyfollowing
table.Asyousee,PRACHConfigurationIndexdeterminesthePreambleFormattobeused.Forexample,ifPRACH
ConfigurationIndexis10asshowninthefollowingexample,thepreambleformat0isused.
Theyoumayask'WhodeterminesPRACHConfigurationindex?'.Theansweris'eNBdeterminesitviaprachConfigindex
IEinSIB2'.RefertoprachConfigIndexsectionforthedetails.
<TS36.211Table5.7.12>
HowdoesNetworkknowsexactlywhenUEwilltransmittheRACH?
Itissimple.NetworkknowswhenUEwillsendtheRACHevenbeforeUEsendsitbecauseNetworktellsUEwhentheUE
issupposedtotransmittheRACH.(IfUEfailstodecodeproperlythenetworkinformationabouttheRACH,Networkwill
failtodetectiteventhoughUEsendsRACH).
FollowingsectionwilldescribenetworkinformatononRACH.
WhichRRCMessagecontainsRACHConfiguration?
ItisinSIB2andyoucanfindthedetailsin3GPP36.331.
HowmanyRAPreamblescanbeused?
Theoretically64PRACHpreamblesareavailableintotal,butthenumberofthepreamblesavailableinaspecific
condition(e.g,inacertaincell,whetheritisforattachorforhandoveretc)aredeterminedbyacoupleofSIB2
parametersasshownbelow.
sib2
radioResourceConfigCommon
rachConfigCommon
preambleInfo
numberOfRAPreambles:n52(12)
preamblesGroupAConfig
sizeOfRAPreamblesGroupA:n48(11)
messageSizeGroupA:b56(0)
messagePowerOffsetGroupB:dB5(2)
powerRampingParameters
powerRampingStep:dB2(1)
preambleInitialReceivedTargetPower:dBm104(8)
raSupervisionInfo
preambleTransMax:n6(3)
raResponseWindowSize:sf10(7)
macContentionResolutionTimer:sf48(5)
maxHARQMsg3Tx:4
...
prachConfig
rootSequenceIndex:22
prachConfigInfo
prachConfigIndex:3
..0.....highSpeedFlag:False
zeroCorrelationZoneConfig:5
prachFreqOffset:4
...
additionalSpectrumEmission:1
timeAlignmentTimerCommon:infinity(7)
TherearetwogroupsofRAPreambles,GroupAandGroupB.GroupAalwaysexistsandGroupBexistsonlywiththe
specificconfigurationinSIB2parameter.ThedeterminationofGroupAandGroupBisdescribedin36.3215.1.1
RandomAccessProcedureinitializationasfollows.
IfsizeOfRAPreamblesGroupAisequaltonumberOfRAPreamblesthenthereisnoRandomAccessPreamblesgroupB.
ThepreamblesinRandomAccessPreamblegroupAarethepreambles(0tosizeOfRAPreamblesGroupA1)and,ifit
exists,thepreamblesinRandomAccessPreamblegroupBare(thepreamblessizeOfRAPreamblesGroupAto
numberOfRAPreambles1)fromthesetof64preamblesasdefinedin36.211.
IfRandomAccessPreamblesgroupBexists,thethresholds,messagePowerOffsetGroupBandmessageSizeGroupA,the
configuredUEtransmittedpoweroftheServingCellperformingtheRandomAccessProcedure,PCMAX,c[36.101],and
theoffsetbetweenthepreambleandMsg3,deltaPreambleMsg3,thatarerequiredforselectingoneofthetwogroupsof
RandomAccessPreambles(PCellonly).//deltaPreambleMsg3ispowercontrolrelatedparameter(Referto36.331and
36.2135.1.1.1UEbehaviourforthedetails)
HowtoGenerate64PRACHPreambleSequences?
Asdescribedabove,themaximumnumberofPRACHSequenceaUEcanuseinacellis64.Howthese64differenttypes
ofPRACHSequencecanbegenerated?Theprocedureisasfollows.
i)GenerateaZaddoffChusequence(849samples)usingrootSequenceIndex(let'scallthissequenceas'basesequence')
ii)Generate64differentsequencybydoingcyclicshiftofthebasesequence.Thecyclicshiftintervalisdeterminedby
NcsandtheNcsisdeterminedbyzeroCorrelationZoneConfigandHighspeedflag.
Forexample>
Let'ssupposeSIB2broadcasttheparametersasfollows.
a)rootSequenceindex=22
b)Highspeedflag=false
c)zeroCorrelationZoneConfig=5
Froma),youwillgetthebaseZaddoffChusequencewithu=1(RefertorootSequenceIndexsectionifyouwantto
knowhowthisnumberisderived).
Fromb)andc),youwillgettheNzc(Cyclicshiftinterval)=26(RefertozeroCorrelationZoneConfigand
Highspeedflag.sectionifyouwanttoknowhowthisnumberisderived).
Nowyoucangetthe64differentPRACHsequenceasfollows.
PRACHSequence[0]=basesequence
PRACHSequence[1]=docyclicshifttobasesequenceby1*26samples
PRACHSequence[2]=docyclicshifttobasesequenceby2*26samples
PRACHSequence[3]=docyclicshifttobasesequenceby3*26samples
....
PRACHSequence[63]=docyclicshifttobasesequenceby63*26samples
PRACHSignalStructure
FollowingfigureshowsthePRACHPremablesignalstructureincomparisonwithnormalUplinksubframe.Acoupleof
pointstobespeciallymentionedare
PreambleLengthinFrequencyDomainisamountto6RBsofULSubframe,whichis1.08Mhz
PreambleLengthinTimeDomainincludingGuardTime(=CPLength+SEQUENCYLength+GTLength)canbe1
or2or3dependingonPreambleFormat
OnesubcarrierofPRACHPreambleis1.25Khzwhereas1subcarrierofULsubframeis15Khz.Itmeansthat12
preamblesubcarrierisamountto1ULSubframesubcarrier.
HowtogenerateRACHSignal?
Youdon'thavetoknowthedetailsofthisprocedureunlessyouaretheDSPorFPGAengineerimplementingLTEPHY.
<PRACHSignalinFrequencyDomain>
JustasacommonsenseaboutLTE,let'sknowthatPRACHisakindofZaddOffChuSequencegeneratedbythefollowing
equation.BeawarethatthissequenceisallocatedalongFrequencyDomain.
,whereu=physicalrootsequenceindex
UEcanselectalogicalrootsequencebasedonRachRootSequenceIndex.OnceUEpickaspecificLogicalRootSequence
Indexvalue,itcanfigureoutthephysicalrootsequenceindex(u)basedonTable5.7.24.
Nzcindicate'numberofdataintheZaddOffChuSequence'.Thisnumberisfixedtobe839inpreambleformat1,2,3and
139inpreambleformat4.
Thereare64preamblesavailableforeachcellandUEhastobeabletogeneratethe64preamblesforthecellitwantto
campon.
Youcaneasilygenerate64differentpreamblesjustbycyclicallyshiftinganexistingsequence,butthereisacondition
forthis.Allthepreamlesequencesshouldbeothogonaltoeachother.Otherwise,variouspreamblesfrommultipleUEs
withinthesamecellcaninterfereeachother.Sowehavetoshiftthegeneratedsequencebyaspecificallydesigned
valueandthisvalueiscalledCv(CyclicShiftValue)anditisdefinedasfollows.(IthinkdeterminingtheCvisoneofthe
mostcomplicatedprocessinPRACHpreamblegenerationbecauseitgetsinvolvedwithsomanydifferentparametersin
cascadingmanner).
First,youwouldnoticethatweusedifferentprocesstocalculateCvdependingonwhetherweuse'unrestrictedsets'or
'restrictedsets'.Thisdecisionismadeby'Highspeedflag'informationelementsinSIB2.IfHighspeedflagissettobe
TRUE,wehavetouse'restrictedsets'andifHighspeedflagisfalse,wehavetouse'unrestrictedsets'.
N_csisspecifiedbyzeroCorrelationZoneConfiginformationelementsinSIB2.Asyouseeinthismapping,N_csvalues
alsogetsdifferentdependingonwhetherweuse'restrictedsets'or'unrestrictedsets'.
Nowlet'slookathowwegetNzc.Thisisprettystraightforward.Nzcisdeterminedbythefollowingtable.(Preamble
format4isusedonlyinTDDLTE.SoincaseofFDD,youcansayNzcisfixedtobe839)
IfthePreambleisusingtheunrestrictedsets,itisprettysimple.YouonlyhavetoknowNzc,NcstofigureoutCv.
TheproblemiswhenthePreambleisusingthe'restrictedsets'.Asyouseetheequationabove,youneedtoknowthe
following4valuestofigureoutCvin'restrictedsets'.
Theproblemisthatthecalculationofthesefourvariableisverycomplicatedasshownbelow.
Youwouldnoticedthatyouneedanothervaluetocalculatetodeterminewhichofthethreecasewehavetouse.Itis
du.Soweneedanotherprocesstodeterminedu.
Wewentthroughacomplicatedprocedurejusttodeterminonenumber(Cv).OncewegetCv,wecangeneratemultiple
preamblesusingthefollowingfunction.
<PRACHSignalinTimeDomain>
Anyway,nowwegotaPRACHPreamblesequenceinhand,butthisisnotall.Inordertotransmitthisdata.Wehaveto
convertthisdataintoatimedomainsequenceandthisconversionisdonebythefollowingprocess.
OncethefrequencydomainZaddoffChusequenceisobtainedasdescribedabove,youcanplugitintothefollowing
equationandwithsomeadditionalparametersyoucangeneratethetimedomainPRACHsequence.
Note:ForthewholePRACHgenerationprocedure,pleasereferto5.7.2/5.7.3ofTS36.211.
ExactlywhenandwhereNetworktransmitRACHResponse
WeallknowsthatNetworkshouldtransmitRACHResponseafteritrecievedRACHPreamblefromUE,butdoweknow
exactlywhen,inexactlywhichsubframe,thenetworkshouldtransmittheRACHResponse?Thefollowingiswhat3GPP
36.321(section5.1.4)describes.
OncetheRandomAccessPreambleistransmittedandregardlessofthepossibleoccurrenceofameasurementgap,the
UEshallmonitorthePDCCHforRandomAccessResponse(s)identifiedbytheRARNTIdefinedbelow,intheRA
Responsewindowwhichstartsatthesubframethatcontainstheendofthepreambletransmission[7]plusthree
subframesandhaslengthraResponseWindowSizesubframes.
ItmeanstheearliesttimewhenthenetworkcantransmittheRACHresponseis3subframelaterfromtheendofRACH
Preamble.Thenwhatisthelatesttimewhenthenetworkcantransmitit?ItisdeterminedbyraResponseWindowSize.
Thiswindowsizecanbethenumberbetween0and10intheunitofsubframes.Thismeansthatthemaximumtime
differencebetweentheendofRACHpreambleandRACHResponseisonly12subframes(12ms)whichisprettytight
timingrequirement.
PRACHParametersandPhysicalMeaning
<prachConfigIndex>
ThisparameterdetermineswhattypeofpreambleformatshouldbeusedandatwhichsystemframeandsubframeUE
cantransmitPRACHPreamble.
sib2
radioResourceConfigCommon
rachConfigCommon
preambleInfo
numberOfRAPreambles:n52(12)
powerRampingParameters
powerRampingStep:dB2(1)
preambleInitialReceivedTargetPower:dBm104(8)
raSupervisionInfo
preambleTransMax:n6(3)
raResponseWindowSize:sf10(7)
macContentionResolutionTimer:sf48(5)
maxHARQMsg3Tx:4
...
prachConfig
rootSequenceIndex:22
prachConfigInfo
prachConfigIndex:3
..0.....highSpeedFlag:False
zeroCorrelationZoneConfig:5
prachFreqOffset:4
...
additionalSpectrumEmission:1
timeAlignmentTimerCommon:infinity(7)
ThemeaningofprachConfigIndexisdefinedbythefollowingtable.Ifyouarenotfamiliarwithhowtointerpretthis
table.RefertothesectionExactlywhenandWhereaUEtransmitRACH?
<SIB2and36.211Table5.7.12:Framestructuretype1randomaccessconfigurationforpreambleformat03.>
<zeroCorrelationZoneConfigandHighspeedflag>
zeroCorrelationZoneConfigandHighspeedflgIeistospecifythecyclicshiftintervalstogenerate64PRACHSequence
fromasinglebasesequence.TheseIE(informationelements)arespecifiedinSIB2asintheexamplebelow.
sib2
radioResourceConfigCommon
rachConfigCommon
preambleInfo
numberOfRAPreambles:n52(12)
powerRampingParameters
powerRampingStep:dB2(1)
preambleInitialReceivedTargetPower:dBm104(8)
raSupervisionInfo
preambleTransMax:n6(3)
raResponseWindowSize:sf10(7)
macContentionResolutionTimer:sf48(5)
maxHARQMsg3Tx:4
...
prachConfig
rootSequenceIndex:22
prachConfigInfo
prachConfigIndex:3
..0.....highSpeedFlag:False
zeroCorrelationZoneConfig:5
prachFreqOffset:4
...
additionalSpectrumEmission:1
timeAlignmentTimerCommon:infinity(7)
Ifyouapplythevaluesintheexampleabove,youwouldgettheNcsvalueof26.(Pickthenumberatthecrossof
column'UnrestrictedSet(HighSpeedFlack=False)andtherowofNcs5)
<prachFreqOffset>
<rootSequenceIndex>
thereare838rootZadoffChusequencesavailableforpreambles.Thelengthofeachrootsequenceis839.
RootConfigurationIndexinformstheUEonwhichsequencetouseviaSIB2asshownbelow.
sib2
radioResourceConfigCommon
rachConfigCommon
preambleInfo
numberOfRAPreambles:n52(12)
powerRampingParameters
powerRampingStep:dB2(1)
preambleInitialReceivedTargetPower:dBm104(8)
raSupervisionInfo
preambleTransMax:n6(3)
raResponseWindowSize:sf10(7)
macContentionResolutionTimer:sf48(5)
maxHARQMsg3Tx:4
...
prachConfig
rootSequenceIndex:22
prachConfigInfo
prachConfigIndex:3
..0.....highSpeedFlag:False
zeroCorrelationZoneConfig:5
prachFreqOffset:4
...
additionalSpectrumEmission:1
timeAlignmentTimerCommon:infinity(7)
ThisrootSequenceIndexisalogicalvalue.Therealnumber(physicalnumber)iscalled'u'whichisavariableusedto
generatePRACHZaddOffChuSequence.ThemappingbetweentherootsequenceIndexand'u'isdeterminedbythe
followingtable.Forexample,iftherootsequenceIndexis22asintheexampleshownabove,the'u'become'1'
accordingtothistable.
Youmaywonderhowthe'rootsequenceIndex=22'istranslatedto'u=1'.Itissimple.FromtheTable5.7.24,youcan
picktheLogicalrootsequencenumberrangethattherootsequenceIndexbelongto.Forexample,therangethat22
belongtoisasfollows.
Logicalrootsequencenumber
Physicalrootsequencenumberu
023
129,710,140,699,120,719,210,629,168,671,84,755,105,734,93,746,70,769,
60,779,2,837,1,838
Thenyoucanconverttheaboverowintoatableasshownbelowandyoucaneasilyfigureoutthe
'roolSequenceIndex=22'ismappedto'u=1'.
index
u
index
u
10
11
129
710
140
699
120
719
210
629
168
671
84
755
12
13
14
15
16
17
18
10
20
21
22
23
105
734
93
746
70
769
60
779
837
838
<36.211Table5.7.24:RootZadoffChusequenceorderforpreambleformats03>
RACHProcedureduringInitialRegistrationRACHProcedureSummary
FollwingisanexampleofRACHprocedurewhichhappensduringtheinitiailregistration.Ifyouwillbeanengineerwho
isworkingonprotocolstackdevelopmentortestcasedevelopment,youshouldbeveryfamiliarwithallthedetailsof
thisprocess.
Again,wehavetoknoweverydetailsofeverystepwithoutmissinganythingtobeadeveloper,butofcourseitisnot
easytounderstandeverythingatasingleshot.So,let'sstartwithsomethingthemostimportantpart,whichIthinkis
thedetailsofRACHresponse.FollowingdiagramshowsoneexampleofRACHResponsewith5Mhzbandwidth.Wedon't
havetomemorizethedetailedvalueitselfbutshouldbefamiliarwiththedataformatandunderstandwhichpartofthis
bitstringmeanswhat.
IfyoudecodeULGrantpart,youwillgetthefollowingresult.Youwillnoticethattheinformationitcarrieswouldbe
verysimilartoDCIformat0whichcarriesResourceAllocationforuplinkdata.ThisinformationinULGrantinRACH
Responsemessageistheresourceallocationformsg3(e.g,RRCConnectionRequest).Note:ThisisexampleofRARfor
SystemBW5Mhz.IfthesytemBWgetsdifferent,youshouldhavedifferentRIVvalues(ifyouwanttohavethesame
Start_RB,N_RBasinthisexample)oryouwillhavedifferentStart_RB,N_RB(ifyoukeepRIVasbelowandjustchange
thesystemBW)
Letmedescribethisprocedureinverbalformagain.
i)UEinitiateaRandomAccessProcedureonthe(uplink)RandomAccessChannel(RACH).(ThelocationofRACHinthe
frequency/timeresourcegridtheRACHisknowntothemobileviathe(downlink)BroadcastChannel(BCH))
ii)NetworksendsaRandomAccessResponseMessage(RARM)atatimeandlocationonthePhysicalDownlinkShared
Channel(PDSCH)(ThetimeandlocationofRARMonPDSCHcanbecalculatedfromthetimeandlocationtherandom
accessmessagewassent.Thismessagecontainstherandomidentitysentbythedevice,aCellRadioNetwork
TemporaryID(T_CRNTI)whichwillbeusedforallfurtherbandwidthassignments,andaninitialuplinkbandwidth
assignment)
iii)Themobiledevicethenusesthebandwidthassignmenttosendashort(around80bits)RRCConnectionRequest
messagewhichincludesit'sidentitywhichhaspreviouslybeenassignedtoitbythecorenetwork
Onlythestepi)usesphysicallayerprocessingspecificallydesignedforrandomaccess.Theremainingstepsutilizesthe
samephysicallayerprocessingasusedfornormaluplinkanddownlinkdatatransmission
HowcanwegetRARNTI?
5.1.4RandomAccessResponsereception"in"TS36.321sayshowtocalculateRA_RNTIasfollows.
TheRARNTIassociatedwiththePRACHinwhichtheRandomAccessPreambleistransmitted,iscomputedas:
RARNTI=1+t_id+10*f_id
Wheret_idistheindexofthefirstsubframeofthespecifiedPRACH(0<t_id<10),andf_idistheindexofthe
specifiedPRACHwithinthatsubframe,inascendingorderoffrequencydomain(0f_id<6).
ForFDD,f_idisfixedas0.
Therefore,RA_RNTIisdecidedbythesendingtiming(SubFrame)ofPRACHPreamblebyUE.Itmeansthat(the
subframenumber(numberbetween0000~0009)ofPRACHtransmission+1)isRARNTI.
ItmeansthatUEspecifiesRA_RNTIbythesendingtiming(SubFrame)ofPRACHPreamble.
AnExampleofFullRACHProcess
FollowingisanexampleofFullRACHprocesswithacommercializedLTEdeviceandLTENetworkEmulator.Iwouldnot
explainanythingindetail.Justcheckifthefollowingdiagrammakeanysensetoyou.Ifitdoes,Iwouldsayyou
understandallthedetailsthatIexplainedabove.
PRACHRetransmission
MostpartofprevioussectionwasabouttheidealRACHprocess,whichmeansthatUEsendPRACHandNetworksend
RACHResponseatthefirsttrialandwentthroughallthewaytotheendofprocessatthefirsttrial.
WhatifUEdoesnotreceiveRACHResponseatthefirsttrial?WhatisUEsupposedtodointhiscase?
Theanswerissimple.Justretry(resend)PRACH.(Inthiscase,UEmightnothaveanyBackoffIndicatorvaluewhich
normallytransmittedinMACCEbeingsentwithRAR).
ThereisanothercasewhereUEneedstoretryPRACH.ItisthecasewhereUEreceivedRARfromthenetwork,butthe
RAPIDisnotforit(ItmeansthatRARisnotforsomeotherUE).Inthiscase,itishighlyprobablethataBackoff
IndicatorvalueistransmittedwithRARtocontrolthePRACHretransmissiontiming.
Thenyouwouldhavemorequestion.("I"inthefollowingdescriptionis"UE")
i)WhendoIhavetoretry?(Whatshouldbethetimedelaybetweentheprevioustransmissionandthenext
transmission?)
ii)DoIhavetoretransmitthePRACHwiththesamepoweraspreviousone?Ortrywithalittlebithigherpower?
IfIhavetotrywithalittlebithigherpower,howmuchpowerdoIhavetoincrease?
iii)IfIkeepfailingtoreceiveRACHresponse,howmanytimeIhavetoretry?DoIhavetoretryuntilthebattery
runsout?orretryonlyseveraltimesandgiveup?IfIhavetogiveupafteracertainamountofretry,exactly
howmanytimesdoIhavetoretry?
Theanswerstoallofthesequestionsareprovidedbythenetwork.
Theanswer(instruction)toquestioni)isprovidedbyNetworkviaaspecialRARMACPDUcalled"BackoffIndicator".
Theanswertoquestionii)andiii)areprovidedbyNetworkviaSIB2asfollows.powerRampingStepistheanswerto
questionii)andpreambleTransMaxistheanswertoquestioniii).
Inthefollowingexample,powerRampingStep=dB2.ItmeansUEhastoincreasePRACHpowerby2dBeverytimeit
retries.
preambleTransMax=n6.ItmeansUEretriesPRACHretransmitonly6timesandthengiveup.(Thisismy
understandingatleastasofnow.Buttryingwithrealdevice,IseemanycasesUEdoesnotgiveupevenafterit
reachespreambleTransMax.IwillgetthisupdatedasIfindmore)
|
|
|
|
|
|
|
|
|
|
|
|
|
AdditionalFactors:
PRACHConfigIndex(inSIB2)
BackoffIndicator(inMACCE)
T300(inSIB2)
FollowingisanexampleofPRACHRetrybeingobservedinarealdevice.ThisisthecasewhereUEsendPRACHandNW
doesnotsendRAR(YellowcellindicatesthetimingdeterminedbyPRACHConfigIndexwhenUEisallowedtosend
PRACH.SeeExactlywhenandwhereNetworktransmitRACHResponse.GreencellindicatesthetimingwhenUEsend
PRACHinthisspecificexample)
RACHProcessOverviewInDiagrams
IhaveexplainedlongabouttheRACHprocess.Nowyoumayask"WhatisthetriggerthatletUEinitiatetheRACH
process?".Youwillseevarioustriggersin3GTS36.300(10.1.5):OveralldescriptionofRACHProcess.
"TurningonUE"isoneofthetriggerforsure.Andfollowingisanothertriggerforthisprocess.
<RACHProcedureonInitialRegistration>
ThisisbasicallythesamesequencethatIexplainedinprevioussections,butIsimplifiedthediagraminprevious
sectionstoletreaderfocusedmoreonmessagingpartofRACHprocedure.Inthisdiagram,youseesomeadditional
stepslikeHARQACK,DCI0(ULGrant).Thisflowismoresimilartoreallivenetworkprocedure.
FollowingisoneexampleforthissequencethatIgotfromlivenetworkandsummarizedwithimportantparameters.I
hopethiscanbeagoodpracticeforyou.(Note:ThisiswithFDD)
SFN:402.4
SFN:402.8
RACHPreamble
RNTI=None
TimingOffset=2
LogicalRoot=219
Preambleindex=33
NCConfiguration=12
SetType=Unrestricted
LogicalRoot=215
PreambleFormat=0
RbStart=2
MACRAResponse
MAC:6100B0C04C2C09
SFN:403.4
E=0(False)
T=1
RAPID=33
TimingAdvanced=11
HoppingFlag0=False
FixedSizeResourceBlockAssignment=96(RBStart=46,RBLength=2)
MCS=2,I_TBS=2,rv=0
TPCCommandforPUCCH3=0
ULDelay0=False
CQIRequest=False
T_CRNTI=11273
PUSCHRRCConnectionRequest
MAC:20061F5C2C04B2ACF6
SubHeader0
R=OK
E=1
LCID=0(CCCH)
F=0(False)
L=6
SubHeader1
R=OK
E=0
LCID=31(Padding)
CCCHRLC:5C2C04B2ACF6(RRCConnectionRequest)
SFN:403.8
PHICHACK
SFN:404.7
PDCCH(DCIFormat1)+PDSCH(RRCConnectionSetup)
CCEStart=0
CCELength=8
DCIFormat1A(Hex:47D01E2)
Format=1
DistributedVRBflag=0(Local)
ResourceAllocation=500(RBStart=0,RBLength=11)
MCS=0(I_TBS=0)
HARQProcessNumber=7
NDI(NewDataIndicator)=1(True)
RV=0
TPCCommandforPUCCH=1
MAC:3C201A1F5C2C04B2ACF660129808FD4E.....
SubHeader0
R=OK
E=1
LCID=28(UEContentionResolutionIdentity)
SubHeader1
R=OK
E=1
LCID=1(CCCH)
F=0(False)
L=26
SubHeader2
R=OK
E=0
LCID=31(Padding)
UEContentionResolutionIdentity
UEContentionResolutionIdentity=5C2C04B2ACF6
SFN:405.1
PUCCHUCIHARQACK
PUCCHFormat1A
nPUCCH=16
SFN:406.2
PUCCHUCISR
NPUCCHRB=2
SFN:406.6
PDCCHDCIFormat0
PDCCHDCIFormat0(Hex:0180540)
SFN:406.7
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
SFN:406.8
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
SFN:406.9
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
SFN:407.0
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
SFN:407.0
PUSCHRRCConnectionSetupComplete(FirstSegment)
MAC=3A3D01221088000020
SubHeader0
R=OK
E=1
LCID=26(PowerHeadroomReport)
SubHeader1
R=OK
E=1
LCID=29(ShortBufferStatusReport)
SubHeader2
R=OK
E=0
LCID=1(identity)
PowerHeadroom
R=OK
PowerHeadroom>11dB<=PH<=12dB
ShortBufferStatusReport
LCGID=0
BufferSize16>91<BS<=107
RLCAMD=88000020
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=1(FirstByteoftheDataFieldcorrespondstothefirstbyteofaRLCSDU.LastbyteofData
fielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=0
PDCPCPSRB=0020
SFN:407.1
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=019801208001005917
SubHeader0
R=OK
E=0
LCID=1(identity)
RLCAMD=9801208001005917
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.
LastbyteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=1
PDCPCPSRB=208001005917
SFN:407.1
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
SFN:407.1
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=0198023945E5340B07
SubHeader0
R=OK
E=0
LCID=1(identity)
RLCAMD=98023945E5340B07
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=2
PDCPCPSRB=3945E5340B07
SFN:407.2
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
SFN:407.3
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=01980241020BF60302
SubHeader0
R=OK
E=0
LCID=1(identity)
RLCAMD=980341020BF60302
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=3
PDCPCPSRB=41020BF60302
SFN:407.3
PDCCHDCIFormat0
DCIFormat0(Hex:0180540)
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=1(True)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
SFN:407.4
PHICHACK
....
SFN:407.4
PDCCHDCIFormat0
DCIFormat0(Hex:0180440)
SFN:407.4
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=96
MCS2,RV0
NDI=0(False)
TPC=1
CyclicShiftforDMRS=0
CQIRequested=0(False)
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=01980427800100D0CC
SubHeader0
R=OK
E=0
LCID=1(identity)
RLCAMD=980427800100D0CC
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=4
PDCPCPSRB=27800100D0CC
SFN:407.5
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=3D010E9805715104E0
SubHeader0
R=OK
E=1
LCID=29(ShortBufferStatusReport)
SubHeader1
R=OK
E=0
LCID=1(identity)
ShortBufferStatusReport
LCGID=0
BufferSize14>67<BS<=78
RLCAMD=9805715104E0
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=5
PDCPCPSRB=715104E0
SFN:407.5
PHICHACK
........
SFN:407.5
PDCCHDCIFormat0
DCIFormat0(Hex:0246280)
SFN:407.6
Format0
HoppingFlag=0(False)
RBAllocationof1stSlotinULsubframe=145
MCS17,RV0
NDI=0(False)
TPC=2
CyclicShiftforDMRS=0
CQIRequested=0(False)
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=019806E0C040002102
SubHeader0
R=OK
E=0
LCID=1(Identity)
RLCAMD=9806E0C040002102
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=6
PDCPCPSRB=E0C040002102
SFN:407.6
PHICHACK
....
SFN:407.7
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=01980703D011D1271A
SubHeader0
R=OK
E=0
LCID=1(Identity)
RLCAMD=980703D011D1271A
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=7
PDCPCPSRB=03D011D1271A
SFN:407.7
PHICHACK
.....
SFN:407.8
PHICHACK
.....
SFN:407.8
PUSCHRRCConnectionSetupComplete(MidSegment)
MAC=019808808021100100
SubHeader0
R=OK
E=0
LCID=1(Identity)
RLCAMD=9808808021100100
D/C=1(DataPDU)
RF=0(AMDPDU)
P=0(StatusReportNotRequested)
Fl=3(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafielddoesnotcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=8
PDCPCPSRB=808021100100
SFN:407.9
PUSCHRRCConnectionSetupComplete(LastSegment)
MAC=3E21361F000000B0090010810600000000830600000000....
SubHeader0
R=OK
E=1
LCID=30(LongBufferStatusReport)
SubHeader1
R=OK
E=1
LCID=1(identity)
F=0(False)
L=54
SubHeader2
R=OK
E=0
LCID=31(Padding)
LongBufferStatusReport
BufferSize#0=0(BS=0)
BufferSize#1=0(BS=0)
BufferSize#2=0(BS=0)
BufferSize#3=0(BS=0)
RLCAMD=B0090010810600000000830600000000....
D/C=1(DataPDU)
RF=0(AMDPDU)
P=1(StatusReportRequested)
Fl=2(FirstByteoftheDataFielddoesnotcorrespondstothefirstbyteofaRLCSDU.Last
byteofDatafieldcorrespondstothelastbyteofaRLCPDU)
E=0(False)
SN=9
PDCPCPSRB=0010810600000000830600000000....
<RACHProcedureonHandoverContentionBased>
<RACHProcedureonHandoverNonContentionBased>
<RACHProcedureonDLDataArrivalwhenOutofSyncNonContentionBased>
<RACHProcedureonDLDataArrivalwhenOutofSyncContentionBased>
<RACHProcedureonULDataArrivalwhenOutofSync>
<RACHProcedureonRRCConnectionReestablishmentwhenOutofSync>
PRACHRFSnapshot
3GPPStandardforRACHProcess
3GTS36.300(10.1.5):OveralldescriptionofRACHProcess.Readthisfirst.
3GTS36.211(5.7):RRCMessagesandIE(InformationElements)whichareinvolvedinRACHprocess.
3GTS36.213(6):MACLayerProcedurerelatedtoRACHProcess.
BestDealson
Mobiles
Frame
Structure
Downlink
PROMOTEDON quikr.com
sharetechnote.com