throbber
SAMSUNG 1033-0001
`
`

`
`3GEVOLUTION:HSPAANDLTBFORMOBILEBROADBAND
`
`I ‘
`
`I
`
`
`
`SAM SU NG 1033-0002
`
`SAMSUNG 1033-0002
`
`

`
`3G Evolution
`
`HSPA and LTE for Mobile Broadband
`
`Second edition
`
`Erik Dahlman. Stefan Parkvall. Johan Skiild and Pet Bcming
`
`-:-—.-v—,»——a-.-«ecu.-.c-—«:-a-u-..sv-._
`
`
`
`AMS'l'llDAM'BO&‘IU(¢ flEfil.II'.'RO-LONDON‘ NIWYORKNIJOURD
`EARLS-SAN Ufl‘SANFIANClK.O‘SNUA|'0RB-SYDIGY-1DKYO
`
`EISBVIER
`
`Aaaaicflmllunlqxtnlofakwlu
`
`SAM SU NG 1033-0003
`
`SAMSUNG 1033-0003
`
`

`
`Aqldanichesthuhprimafauwier
`LhuueHuune,.lcmmfllll.0xloId,0x28DP
`30CotponIel)rive.BItlin;1on.MA01K)3
`1'|mediIioI12IU7
`Seeoldedilinnfllifl
`
`CopyIi$ItG2|I)8.EikDahm:u;SndunPadrvdLJdnl|SH)flmdPerB¢nIh1g.
`PubI1shedbyB.sev1crlM. Aurlmmuved
`ThaxightofB1ikN:lmm.SInfnnPurknfl.Johu1S1:flldandPe¢Beminzlbhe
`ldaadfieauunuthouofflxiswodthlshaenauatudinucuudnmewithlln
`Copyright. Dadgnsantl Palnnn M21988
`Noputoflluin pflalinntiou mayborvyxuducld. mud in alufieval memo:
`wuuminadinuIyfonnmbynnyrn:an5dedmn1c,mAchInicI,p1moeopyiIg.
`Iecotdlagoromuwln winnnuhnpriorwniuenpemiuionoflhcpuhlflncu
`ParmluimmqyhcIou[hldIncIIyfi'omEswiat‘:Scinou&1‘e=hnohgBigln
`Dqurmmtlnoxlttd. UK: ohm: (+44) (0) 1365 masmru (+44) (0) 1365 853333;
`email:
`Alma:-nnivety you can submit you racpstnnlinaby
`visitingttnilnaviarwdasiteatmJMw g mdsduaing
`wldnlugpmul-lonbouu Eluviarnaturial
`Notlec
`Nouspalfibifityhuwmndbymepubfiiuxfuuryiajuyand/wdamzgetopusom
`orpmpenynsnnmerofpnodnxwfiab1Ety.1c;flgneauothuwin.ocfiomnnyuu
`_oIopenflonofanyme¢1odgpmdum.in:unm1m:uIdaoconuha1hthemnuin1 hen-.in
`Brllkhblbliryfilllnuulnnhlilollafionbala
`3OevulIllinl:HSPAIndIJ'EfowlIIrIIile17nndhtnd.—2nded.
`1.Bmulu|denmm:nicanuuy:Iem-Smudards 1 Mobilcoommunicnflm
`xyweum-Standards
`3. Cellularlzlqinnnasywems-Stnntlurck
`L Dnl-n1man,Eri.|:
`62158546
`
`Lilnnry 0fCwfl$ Ccllkd Nullbar: 2€I)39312'IB
`ISBN: 97&0- I2-374533-:5
`
`Potinfulnuion on all Academic Pm: publicaims
`vim our wablitn at elawiqfihecucom
`
`‘lypnetby Chnxon ‘be 1.411.. A Macmillan Company. (wvwnnanflhnnlufiausun)
`Ptinnednndbunu1hGna1BrininbyMPGBooknLM.Bo¢rIin.0oImmfl
`os'o91o11n1o9a16s4321
`
`- —.—»——:——.
`
`.—.....n-r.--.uu;-....,—u-vs:-awn...-.—.—.\
`
`...\.-..._;.._...1--1.-n....
`
`Vforlcing together to grow
`libraries in developing oountrics
`vwundscvieccnnu | wwwboohidmg | wvmldanmg
`
`
`
`. . . . . ..24
`
`Lista('Figu'a
`
`Lmfilhblm
`
`W
`
`Admowledpmcnts
`
`L'utofAcmnyms
`
`Partlzlntroduction
`
`xv
`
`gnu
`
`N‘
`
`xni
`
`M“
`
`1
`
`1 Baekgmundof3GcvoII6on...................................3
`1.1
`1-11stoxynndbackgmundof3G .
`.
`. . . . . . . . .
`. . .
`. . . . . . . ..3
`1.1.1 Bfio1e3G . . .
`. . . . . .
`.
`.
`. . . . . . . . . . .
`. . . . . .
`. . . .
`. . . ..3
`1.1.2 Batly3Gdiscuasiona....... .
`. . . . . . . . . . . . .
`. . . . .
`. ..5
`1.1.3 Resean:hon3G.. . .
`.
`. . . . . . .
`. . . . . . . . . . . . .
`. . . . . . . ..6
`1.1.4
`3GsIandaxdizationstnm...
`. . . . . .
`.
`1.2 Stmdaxdiution . . . . .
`. . . . . .
`.
`. . .
`. . .
`.
`.
`. . . . .
`.
`. . . . . .
`. . . . . .
`. ..7
`.7
`
`1.2.2
`3GPP . . . . . .
`. .
`. . . .
`.
`. . . . . . . . . . . . . . . . . . . . .
`. . . . . . . ..9
`1.7.3
`IMT-2000activiu'esin1'IU........... .
`. . . . .
`. . .
`. . . ..]1
`1.3 Specu'umfor3Gandsyslemsbeyond3G.
`. . . . . . . . . . . . . . . . .
`. ..13
`
`2
`
`2.2
`
`'1'l|emntivesbelnin¢Ithe3GevoInIion...........................15
`2.1 Drivixlgfalces .
`. . . . . . .
`. . . . . . . .
`. .
`.
`. . .
`. . . . .
`. . . . . . . . . . . . . ..15
`2.1.1 Technologyadvarlcemerns . .
`. .
`. . . . . . . . . . . . . ........16
`2.1.2
`Services . . . .
`. .
`. . . . . . .
`.
`.
`.
`.
`.
`. . . . . .
`. . . . .
`. ..17
`2.1.3 Costandperfonnance . . . . .
`. . . . . . . . . . . . . . . . . . . . . . ..20
`3Gevoluzion:'IwoKadioAccessNetwott approaches
`. . . . . . ..21
`andalievolvedooronetwudc. . . . .
`.
`.
`. . . .
`. . .
`. . . .
`2.2.1 R.udioANetworkevo1ut1on . . . . . .
`. . . . . . . .
`. . .
`. . .. 21
`2.2.2 Ancvolvedcore neLwod::systema.rd:iteaLIre
`evolution. . . . . . . . . . .
`. .
`.
`. . . . . . . .
`. . .
`. . . .
`. . . .
`
`SAM SU NG 1033-0004
`
`SAMSUNG 1033-0004
`
`

`
`9 P
`
`lane 1.2
`
`JGPP organlunlon.
`
`Rm.-flrurndaflflewllman
`
`
`
`lilnrehl
`
`Ihesmrdardlzadanphasuswrduerudwpmceu
`
`3. Deaailedspecificarionx, where every interface is specified in detail.
`4. Tesdngardwrifieuziomwhemthemtafaeespecificafionsuepmvenw
`wotkwith reel-lifeequipment.
`
`‘I-hese phases are overlapping and iterative. As an example. requirements can be
`added. changed. or dmwed during the later phases if the technical solutions call
`for it. Likewise, the technical solution in the detailed specifications can change
`due to problems found in thetestingand verifieationphase.
`
`Standardization starts with the requimrnems phase, where the standards body
`decides what should be achieved with the standard. This phase is usually rela-
`tively short.
`
`In tlreamhirecurr: phase. the srarudards body decides ahoutthe architecture. i.e.
`the principles of how to meet the requirements. The architecture phase includes
`decisions about reference points and interface: to be standardized. This phase is
`usually quite long and may change the requirements.
`
`After the architecture phase, the detailed specification phase starts. It is in this
`phase the denils for each of the identified interfaces are specified. During the
`detailed specificsfion of the intufaces. the standards body may find that it has
`tochlnge decisionscloneeitherrinthe architechnetxevenintherequirernents
`phases.
`
`Frna‘lIy.tliet¢stiugarrdven‘ficatiorIpha.se starts. Itlsusuallynotapartofthe
`actual staridardizztionin the standards bodies, but takes place in plrallel through
`testing by Vendor: and imuopcrability tmting between vmdom This phase is
`fliefiJmlptoofofflresnndard.Duflngfltetesfin3u1dverificafionphase,m1ms
`in the stanrhntl may still be found and those errors may change decisions in the
`detailed stanrhrd. Albeit notcommon. changes msyneeduohedone alsotothe
`architecture or the requirements. To verify the standard, products are needed.
`Hence. the implementation of the produas starts aha (or during) the daailed
`specification phase. The testing and verification phase ends when there are
`
`stable test specifications that canbe used to verltythattlreequipmetrr is fulfilling
`thestandard.
`
`5
`
`Normally, it talces one to two years from the time when the standard is com-
`pleted until commercial pmdncm are out on the market. However, if the standard
`it built from scratch. it may take longettime time there are no stable compo-
`nents to build from.
`'
`
`1.2.2 3GPP
`
`The flrird-Generation Ptmnership Pmjecr (SGPP) ll the stantllds-develnpirrg
`body that specifies the 3G UTRA and GSM systema.3GPP isapnrtnership project
`formed by the standards bodies EFSI. ARIB. 'I'I‘C. 'I'l'A. CCSA and A118. SGPP
`consists of several Technical Specificatiot1s Groups (T803 ). (see Figure 1.2).
`
`l_\ parallel partnership project called SGPP2 was formed in 1999. It also devel-
`ops 3G specifications. but for odrna2000. which is the 3G technology developed
`
`
`
`SAM SU NG 1033-0005
`
`SAMSUNG 1033-0005
`
`

`
`I0
`
`'
`
`i
`
`30 Eboludnu: H3PA andLTEfi!rI|l0bll£Brna&1Id
`
`from the 20 CDMA-based standard 13-95. It is also a global project. and the
`ouganizatlonal pennem are ARIB. CCSA. TIA, TTA Ind'ITC.
`'
`
`3GPPTSGRANisthetechnlcalspedflcnIiongmupmatbasdeve1opedWCDMA.
`ltsevulutionl-lSPA.eswellasLTE.andi;intheforet'rontofthetedanology.'l‘SG
`RANeonslstxofflvewotl<h1ggtoups(WGa):
`
`1. RANWGI dealing withthepllyaieal layer
`2. RANWG2dealingwiththelayer2andlnyer3radiointeriaoe qnciflcationa.
`3. RAN WG3 dealing with the fixed RAN interfaces. for example imetfaoes
`betweennodeainthe RAN,lxn|1notheinnerfIl:ebetweentheRANandtite
`WIOEEIWNK
`'4. RANWG4dee1ingwithdter¢diofiequaacy(RF)andradioresaurcemau-
`agemenl (RRM) perfonnanoe reqlirements.
`.
`5. RANWGS dealingwithdntenninal confonnaneetlestiog.
`
`'I1teseopeof3GPPwl1eoltwaefomaedln l99Bwaetopmdueeglobalapeelll-
`cations fora 3G mobile system based on an evolved GSM cote netwodt. including
`the WCDMA-based radio access of theUI'RA FDD and the TD-CIDMA-based
`radioaoeessoftineUTRATDDn1ode.Theta:ktomaintainanddevdopthe
`GSNI/BDGBspeeificafimswasaddedm3GPPatalntetstage.TheUmA(md
`GSMIEDGE) tfiecifications are developed, maintained and apptuved in 3GPP.
`AfterappmvaLflnotganizIiom1patmmuuampoeed|eminto&ppIopri1teddiv-
`cnblesasltmdatdsineacltmgion.
`
`[nparallelwithtbel.nitial3GPPwork. a3Gsyetembuedon'I'D-SCDMAwas
`developedinChilia.TD-SCDMAwasevenmallymetgedintoReluse4ofd1e
`SGPP specifications as an additional TDD mode.
`
`Theworkin 3GPPiscan-iedont withte.levantI'I'U xecommeodmions inmind
`
`and the result of the work is also submitted to ITU. The organizational put.-
`mmamobfigedmideofifytegktnnlmquhmnmmthnmayleadmoptionsinthe
`standard. Examples are regional fieqicncy bands and special protection lequite-
`ments local to a region. The specifications are developed with global roaming
`and cinzulatim of terminals in mind This implies that many regional require-
`menmineuanoewillbeglobalrequixements focal] nermimls.5inoeat'ouning
`terminal has to meet the suzictest of all tegioml requirements. Regional options
`in the specification: ue thus mote common for hue stations then fix terminals.
`
`The specifications of all releases can be updated aha each set of TSG meetings,
`whichoooul'4timen year. 'l‘he 3GPP documentsaredividedinto teieaeen. where
`
`
`
`Fun 1.3 Rllum a_/3GPP .-pccguafimpr arm,
`
`eachmleuebIsaaetoffeaunesaddedooupmdmthepreviauzelease.Thefes
`' mreeuedefinedinWorkIbnnugteedmdund=mkenbythe1’SGs.Then:|eases
`uptokeleasesandsomcmainfeatmesofthoseazeshawninFigure1.3.The
`dareslIownforeachreIeuelsthe(hytheeontentofdaereleasewufimen.Fm
`l:i:ton'ealrensons.thefirst release is nnmbetedby lheyearitwu frozen (1999),
`whilethefollowing:eleuesuemmbe:ed4.5,etc.
`
`For the WUJMA Radio A0053 developed in TSG RAN, Release 99 contains
`all feature: needed to tmet lhe IMT-Z100 requirements as defined by ITU.
`There are circuit"-switched voice and video services‘ and data services over bod:
`packet-switched and citeult-switched bearers. The first major addition of radio
`access features to WCDMA is Release 5 with High Speed Dawnlink Packet
`Access (HSDPA) and Release 6 with Enhanced Uphnlz. These two ate mgetllet
`te:E¢-nedtoasl-lSPAandaIedscl'ibcdinmorcdet:iJinPattlllofthisbook.
`With I-ISPA. UTRA goes beyond the definition ofa 36 mobile sywem and also
`encompasses broadband mobile data,
`
`With the inclusion of an Evolved UTRAN (I..'l'E) and the related System
`Amhitectwre Evolution (SAE) in Release 8. further steps are tqkell in terms of
`broadband capabilities. The specific solutions chosen for LTE and SAB are
`deacribedinPartIVofdtisbook.
`-
`
`1.2.3 IM'F2000 activities in ITU
`
`The present r'tU work on 30 takes place in ITU-R Working Party 50‘ cwpsn),
`wherc3Gaystem:metefe:redtouIMT-2000.WP5Ddoeanotwliteteclmieal
`
`‘1\ewuknnlNfl‘-30fl0vmnmadnnmWmHo;Puly3PIoWmHnghttySDin200&
`
`
`
`SAM SU NG 1033-0006
`
`SAMSUNG 1033-0006
`
`

`
`20
`
`36 Evaltdicn: lfihl and lTEfiIr Mobile Broadband
`
`I1aenn¢tlvetbehb:dthe3G¢noMloa
`
`21
`
`
`
`liflullzl 1Mblt:uu—ddaywrvlcaspoudwl:lupa1anInaour_whandalg:bI;anew
`aellularsystewl.
`
`oftltemobile-communication systemsneedtostopatarensonablelevel.alevel
`flmtlteteehnology avnilahleattltetimeofstmdardizationcanprovide.
`
`2. 1.3 Cost andperfonnanca
`
`inmate is anotltepintportant driving factor for future mobile-communication sys-
`tetDpu1dfl1atisthbw3toffln:uvicep'ovisbnmg.Ihebdmobgyadvameunnt
`thatenablesnew scrvicescanalsot>cutilizedtopmvldebenermnbile-commtmi-
`entionsystems using more advancedteehnical featmes.HereIPtechnolcgyisnot
`only_a hey enable: to allow for new services to pop up. butnlso 1 way ofreduo-
`ingeoatusfnewaenrioes.'I‘hereasonitthatIPasabearerofnewsu-vicescanbe
`n:eda>htunducenewuewicesastheycmne.mt1eqIfifinganextarsivespecial
`design oft:ltesystem.0fcourse.t.li:requirea tlrat_tl:edeviceauaedintl:emohila-
`communication systunumbeptognmntedbythird-party pmvidasandthatthe
`opuammfllowfifird-partysavbeprwihsmmeflaekltawukfotuxllmutficalbn.
`
`Anodterimprrtmnfxanrthatoperatorsneedtopxovideduservieestoantte
`users.Notonlyoneuserneedstogetthe1awdela3ahighdetarnte,etc.thsIits
`seMeemeds.butallmeusaswhhthdr_difla-axserviceneedsshouubeserved
`efficiently. The prooming capacity evolution nndMoore'a lowhelp also forthis
`problem. New techniques are enabled by the higher processing power in the
`deviees—rechniqnesthnddivusmorebiuofdmperhertz.Funhermore.d|e
`covengeisioomasedwhhmoresdva1cedantemasmdreeeivers.Thisenab]es
`theopemtorstodclivetthescrviceslornnreusersfromonebaseatalion. lhus
`requiring fewer sites. Fewa sites imply lower opaatlonal and capitdization costs.
`Incssenceflteopcruommedfewerhmemtionsandalteemlxovidefinscnise.
`
`Obviously, all services would be ‘happy’ if they ‘were provided with the
`highest data rue, lowest delay. and lowest jitter that the syntax: can provide
`Unfortunately. thin in unattainable in practice and contradictory to the operator
`goalofanetlicicntsyxtemzinothea-wocds,dremore deluaservioecanlnndle
`the more eflicient the system can be. Thur. the cost of providing lowest possi-
`ble delay. jitter antlcall setup timeis somewhat in conflict with the need ofllle
`mobile-networkopemortnp:uvideiuoolld1eusers.Herwe,thereisauade-off
`between user experience and Iystean performanw. The better the syaem per-
`fonnanceia.thelowerdIecoetofu1enetwork.Hmvevu.theendususdsoneed
`uogctadequatepaformancewhichofienisinconflictwilhthesynunperfom-
`mce. thus the opium: cannot only optimize for system performance.
`-
`
`2.2 36 evolutton:Two Fladlo Access Network approaches
`‘and an evolved core network
`2.2. 1 Radio Access Network evolution
`
`TSG RAN organized a workshop on 3GPP long-term Evolution in the fall of
`wD4.'I‘l1ewotlts.lI>p wastheatnrti.r1gpointofthedcvelopmentoftheI.ong-
`‘Ram Evolution (LIFE) radio interface. After the initial requirement phase In the
`spn'ngof2005, wherefltetargetsandohiectivea ofL'l'Bweresettled,titetenhni-
`cal specification gonp TSG SA launched a corresponding wodr on the System
`Architecture Evolution, since it was felt that the LTE radio interface neecbd a
`suitable evolved system architecture.
`,
`
`The result ofthe LTB workshop was that a study item in 3GPP TSG RAN
`wascrealedinDecetnber2(Xl4.I1teflrst6monthewueepentondefir|ingthe
`:equimmonu.o:designmgeu.ro:u'arhesewaedocumentedtna3G1>P
`technical report [86] and approved in Iune 2.005. Chqxer I3 will go through
`the requirementsininore detail. Most notableatetherequiremermanhighdata
`ntnattheeefledgemdmeirnportar|ceoflowdehy,inaddi&ontomenonnal
`capacity andpeakdataraterequirements.Furthemt0re.Epectmmflexibilityu|d
`nnximurn commonality between PDDamiTDD solutionsarepronounced.
`
`During the fall 2005, 3GPP'l'SG RAN W01 "made extensive studies of different
`basic physical layer technologies and in December 2005 the T80 RAN plenary
`decided that the LTE radio access should be based on OFDM in the downlink
`and single carrier mm in the uplink.
`'
`
`TSG RAN and its working groups then worked on the {IE specifications and
`the specifications were approved in December 2007. However, SGPP TSG RAN
`did not stop working on LT}! when the first version of the specifications was
`
`
`
`SAM SU NG 1033-0007
`
`SAMSUNG 1033-0007
`
`

`
`431
`
`3G EVHUHM: HS!!! and 11810!’Moblle Broadband
`
`LIE acunpmcedurer
`
`Eh
`
`_
`
`.
`
`syndrome to
`dnvurllrlr umru
`(Hamil In-rdrj
`
`433
`
`3%,.
`
`In case of a relatively small 81 and a relatively large system bendwirltlr, a sin-
`gle suhfrarrte may he luflicient for the transmission of the $1. In oflrer cum.
`multiple rubframesmaybeneededfortlreunnamissionofasinglesl Irrthe
`latter case, instead of segmenting each SI into sufficiently email blocks tint
`aresepariuelychnmreloodedaaduansnnttedinseparatesizbfzmrres. thccom-
`plete SI i.schmneleodednndmappedtomultiple,notnecessuily consecutive
`subframea.
`
`Siniilartao thecaseofthe BCH, terminals thatareexperiencing goodchannel
`coiiditionsmaythenbcabIedecodethecompleteSIafterreceivirrgonlyasub-
`setoftilesuhframestowhichtlrecodedslismapped, whileterminalsinbad
`positions need to receive more subfnmcs for proper decoding of the $1. This
`npptoudrhastwobenefiu:
`
`0 Similar to BC!-I decoding, mrminalx in good position: need to receive fewer
`suhfuunes. implying the possibility for reduced terminal power consumption.
`0 The use of larger code hloelu in combination with ‘lube ending lead: to
`improved channel-coding gain.
`
`18.3 Random access
`
`A fmdamental reqilirement for any cellular system is the possibility for the ter-
`minal to request a connection setup. commonly referred to as random access. In
`LTB, random access is med for several purposes, including:
`
`0 for initialacoess when establishing a radio link (moving from RRCJDLB to
`RRC_CONNEC'l‘ED; see Chapter 15 for a discussion on difierent erminal
`states);
`0 tore-esteblisharadio link afterradiolinkfiilure;
`e for handover when uplink synchronization needs no he established to the
`new cell;
`0 to estibliflr uplink synchronization ifuplink or downlink data arrives when
`the terminal is in RRC_CONN'BC'I'ED and the uplink is not synchronized;
`0 as a scheduling request if no dedicated scheduling-request resources have
`beeneonfiguredonPUCCH(seeChapter 19 foradiscussion onuplirrk
`scheduling procedures).
`
`Establislmmcm of uplink syrrnhronimtion is the main objective for all the cases
`above: when establishing an
`radio link (Le. when moving from RRC_
`IDLE to RRC_CONNEC.'I‘ED). the random-access procedure also serves the
`purpose olessignlng I unique identity. the C-RNTI. to the terminal.
`
`
`
`Onlyifualenetknewnheflodfl
`tlnllelrmderneeeeeei
`
`
`
`Figure 13.! Own-r':w oftha rwrdaur-arxaar prucuduu:
`
`The basis for random access in a contention-based procedure. illusrmecl in
`Figure l8.8,andeon.sr’su offoursteps:
`
`1.
`
`'ll:flrststepconsimofI:nnsrnissiorr<rfa randorii-accessprcamblemllowing
`the eNodeB to animate the rnnsrnission timing of the terminal. Uplink synchro-
`nintionin nmesearyudreterminalothezwisecarrnottranurritany uplinkdatn.
`2. The second rtepconiiatx of the network transmitting a tinting advance corn-
`rmnd to adjust the terminal transmit timing, based on the timing estimate in
`the tint step. In addition to emblishing uplink ayndrronizatian, the second
`atepalsoaasignsuplinkreaoumeetouretemrirmltobeusedintherhirdstep
`in the random-access procedure.
`3. The third step consists of uanamission of the mobile-terminal identity to
`the network using the UL-SCH similar to nonml scheduled data. ‘lite exact
`content of this signaling depends on the state of the terminal. i.n particnlnr
`whether it is previously lmuwn to the network or not.
`4. The fourth and final step oondstx of transmission of a contention-resolution
`message fromthenetworktotirenerminal ontheDL-SCI-l. This step also
`resolves any contention due to multiple terrninnls trying Io access the system
`using the same random-access resource.
`
`Only the first step uses physical-layer processing specifically designed for ran-
`dom access. The last three steps utilize the same physical-layer processing as
`
`
`
`SAM SU NG 1033-0008
`
`SAMSUNG 1033-0008
`
`

`
`434
`
`3G Evolution: FISH! and Lltjorllablle Broadband
`
`Ilfiazcasprocrdnru
`
`435
`
`used for normal uplink and downlink data trnnsmision. In the following. each
`of these steps is described in more detail
`
`step. Hence. from the preamble the tenninal used, the eNodeB, will get some
`guidance on the rtrnount of Irplinl: resources to be granted to the terminal.
`
`Additionally. for handover purposes it is possible to use the random-access
`ntedwnnism in n contention-free manner ss described further below. In this care
`only thefirittwosleps oftheprocerlrrrenreusedasthernistroneedforconten-
`tion resolution in a contention-free scheme.
`
`18.3. 1 Step 1: Random-access preamble transmission
`The first step in the random-access procedure is the uarrsrrrission of ti random-
`sooe preamble. The main purpose of the preamble transrnission is to indicate
`no the base station the presence ofa random-access attempt and to allow the
`bnsestaIiontoesfimatethede.laybetweenfl1eeNodeBandlheUermirraI. The
`delay estimate will be used in the second step to adjust the uplink
`
`The tirne-tieqtrency resotroce on which the random-access preamble is n'nnsrnit-
`ted upon is known as the Phylvical Random Accm Channel (PRACI-1’). The net-
`work broadcasts information to all terminals in which tltme-frequency resources
`nndom-scenes preamble ttnnsrnission is allowed (i.e., the PRACH resources. in
`SIB-2). As part
`the filst step of the random-access procedure, the terminal
`selects one preamble to transmit on the PRACH.
`
`lntachcell, tlrerear:64prcamblesequenoes :wai1n'nle'l\wos1tbsetsol'the64
`sequences are defined as illustrated in Figure 18.9. where the set 0! sequences
`in each subset is signaled as part of the system irrtorrnnlion. When performing
`it (contnrtion-based) random-access attempt. the terminal at random selects one
`sequenceinoneol't.hesubsets.Aslourgas nootherterntinalisperforminga
`random-access attempt using the same sequence at the some time instant, m
`eollisionswiflocanandtheatremptwin.widlahlghflkeflhood.bedctcctedby
`thee.NodeB.
`
`Thesubsettoselecttltepresmblesequarcefiomisgivenby thearrrountofdatn
`thelenninalworrldliketo trnnamitontheUL~SCl-Iinthethirtirandtrm-access
`
`Pnemblo eat no
`
`Ptosnoto out 01
`
`Foroontontton-tree oecoso
`
` 64 Poonmbbn in cool: eel
`
`lkun 18.9 Pmnnbi: suture
`
`If the terminal has been requested to pa-form a contention-free random access,
`forexnmple,forhnndovutnauew cell. thepreamhlelaouseis explicitly indi-
`cated from the eNodeB. To avoid collisions. the eNodeB should prcfcnbly
`select the eonterrtion-free preamble from sequences outside the two subsets used
`for contention-based random access.
`
`18.3.11 PHACH time-frequency resources
`In the frequency domain, the PRACH resource, illustrated in Figure 18.10,
`has a bandwidth corresponding to six resource blocks (l.08MHz). This nicely
`rnatdtes the smallest uplink cell bandwidth of six resource blocks in which LTE
`can operate. Hence. the sun: random-access preamble structure can be used.
`regardless ofthe transrrrissionbnndwidthinlhecell.
`
`In the time domain, the length of the preamble region depends-on configured
`preamble as will be discussed further below. Thebasic random-ncces resource
`is lmsindurationmutflrereisnleodtepoasihihtymoontlgtuelorrgerproaor
`bler. Also. note that the eNodeB uplinlc scheduler in principle can reserve an
`nrbitrary long mndorn-access region by simply avoiding scheduling terminals in
`multiple subsequent subfran-res.
`
`Iypicnlly. the eNodeB avoids scheduling any uplink transmissions in the time-
`frequency resources usedforrsndom nceers.‘l‘hisnvoidsinterfuencebetween
`UL-SCH trmstnissions and random-access nttempts from diflerent
`termi-
`nnls.'Drera.hdom-acoempresmbleisslidtobearfinganaltourerdatn, unlike
`WCDMA where upliulr data trtlmmission and randorn-access attempts share the
`same resources. However. from a specification perspective. nothing prevents the
`upiink sdrednlu to schedule nnnsminsions in the random-nccoss region. Hybrid-
`ARQ retransmissions are an example of this: synchronous non-adaptive hybrid-
`ARQretran.srnissiousrnayoverl.np withtlternndom-access region snditisupto
`the irnplementntion to handle this. either by moving the retranstnisslons in the
`frequency domain as discussed in Qrnptcr 1.9 or by handling theinterferenee at
`the eNodeB receiver:
`
`For FDD, there is at most one random-access region per subfnme. that is, multi-
`ple rsndom-nooess attempt: are not multiplexed in the frequency domain. From
`a delay perspective, it is better to spread out the random-access opportunities in
`the time domain to minimize the average waiting time before a rnndoru-access
`attempt can be
`For TDD. multiple random-access regions can be
`
`
`
`SAM SU NG 1033-0009
`
`SAMSUNG 1033-0009

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket