Exhibit 103 3 -0001
`
`ZTE/HTC
`Exhibit 1033-0001
`
`

`
`3G EVOLUTION: HSPA AND LTB FOR MOBILE BROADBAND
`
`ZTE/HTC
`Exhibit 1033-0002
`
`

`
`3G Evolution
`
`HSPA and LTE for Mobile Broadband
`
`Second edition
`
`Erik Dahlman. Slnfan Pukvall. Johan Skfild and Pet Bcming
`
`AMSTERDAM-IO5‘lKX(¢l(Elfl.IERO'LDNIWK'NEWYOIK'0XR)llD
`PARISISAN E'SANPIANClfiK)-SNIZAFOKB-SYDIEV-1DKYO
`Auaank Pmlllh Inamlotmmtu
`
`ZTE/HTC
`Exhibit 1033-0003
`
`

`
`_
`
`ha.“
`
`Admowledpments
`L'g¢nfA¢mnym,
`
`Part I: Intmdudion
`
`Aqulunichesuhu lllprintoffiuovier
`LiucIeHnuse,.lcm|n fllll.0KIoI'd.0X18DP
`30CoIponln Dri\e.BIllingm,MA0lm’5
`P|meditioIl7Jl)'1
`Secoldcdilinnfllfi
`
`Capy1ifi1t62Il)8.EI-ikD|hhumSod'|nPadm1LJdInSl1l!HmdPerBa11mg.
`mb11_shedhya1saAez1u.Aunpmauvu1
`Thar1gmofBtlkMIlmIn.StnfnnParknn.5ohm1Sldfld:ndPerB¢mingIbhe
`ifluudfieduunmlhuuoflhhworkhnnheentuatedinunaadmnewilhfln
`COW|'ilh¢.DodgnundPuIanuM¢l98l
`No pm of thin pub1io.nm my 1» mpmaucu. mm in a 1:11-iavnlsyulm or
`tnMniIted'u1uIyformorbyanymenn:aimronlc,mAch:nicI,phomeopyig,
`recnrdhgorumuwlnwidnuthspwiorwdueapexmissionafxhapnablidua
`Parulndonmnyhcnouflld1neIlyfiumEuviu’|Scinauu&1'h:hmlogyRigh:
`n11II1111'.tlI1101m111I.UIC; pm:(+44) (0) was s43a31z£u(+44) (0) 10651153333;
`email:
`mummy you can submit you lI1;11s'tunl111abY
`fififing®Hnvkw&dUnmm1MW gmdabflu
`flldnbsgpuulnlonbuuibniu-muurhl
`"wee
`Nonspuwtifiukuumwbymepuhflmufuuyiniuyadhrchmaggtopumm
`“F‘wnq“.m‘nadfl'.°d.‘mfi.bi-fl‘y..au}a“uh“'i&“f.°mIny“u
`.0IopeflflM0fIwmeflw&,wudI1u3.1nlruxh1IuIdaowudnaihl.|nmnnh!hu:in
`mmmmummhmmmm
`3Gmo1uIio1:l'ISFAIndlJ'EforIIlrbibbmIdhInd.—1I1lad.
`1. BmI1I1ndoomnnI1iuIi1IIy:1cnI—Sta11da1vds 1 Mobileoommmienion
`rysuum-Snndurls
`3. Cdlulunalqimnasymmn-Sunrhdn
`I. 9.1.11.1». E-11:
`m1.s'ss«s
`I.i|'n'Iry ofcupul Contact Nunbnr: 111211931218
`ISBN: 91llv0-12.371538-.5
`
`p«hfi,,um,non,uA“mm1¢pm‘wblm¢m,
`vinixonrwuhinnatelseviexdirectoom
`
`'lypuetbyC|1I1nn'n::l.Ad., AM1cm‘Lll:nCompu1y. (wvw.ma1:niIh1mlution:.c1m)
`mmdlfimmhmmmnhwmcmohljinmdmommu
`050910 11
`11 l09876.‘l-I321
`
`together to glow
`oountrigs
`lib]-31-ics
`vwmdgvieccan I wwwbcnhidntg | wwwmdmnng
`
`’
`
`:
`
`'
`E_
`1
`
`1
`‘
`"
`,
`
`‘
`1
`
`.
`
`_
`1 Bfifiglvundflsc
`gmhhon...................................
`1.1 Historyandba1:kgoundof3G . . . . . . . . . . . ....... . . . . . . . . . . ..
`1.1.] BEfOlE3G.'....: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
`1.1.2 Eally3Gd1scuss1on11.....
`1.13 Resean:hon3G. ................................ ..
`1.1.4 w nmm . . . . . . .
`. . . . .
`. . . . . . .
`. . . . . . . ..
`. S , , _ . _
`_ _ _ . _ _ _ , _ __
`1.11
`
`1
`
`3
`
`1.3
`
`Spec1r11mfor3Gandsysuam.sbeyond3G.
`
`. . . . . . . . . . . . . . . . .
`
`. .. 13
`
`'l‘|1a1I111tiveil1ehl.n¢ltl1e3GevohIIion ................... ........ 15
`2.1 Driving f0lC:5 .
`. . . . . . .
`. . . . . . . .
`. . .
`. , ,
`2.1.1
`Technology advancements . . .
`_ , ,
`2.1.2
`Servizes . . . .
`. .
`. . . . . . . .
`.
`. . . . . . . . . . . . . . . . . . ..
`2.1.3 Cosundperformance . . .
`. . . . . .
`. . . . . . . . . . . . . . . . . . . .
`and an evolved core network. . . . .
`. . . . . .
`3G"'?l"’j°"‘1"°R‘di°A°°°“N°‘“'°‘*'PW“°”h“
`2.2.1 RadioA Network evolution . . . . . . . . . . . . .
`22.2 An evolved care network: system ardnitemne
`evolution. . . . . . . . . . .
`.
`. . . . . . .
`. . .
`. . , . . . . . . . . . . . . . . . 24
`
`ZTE/HTC
`Exhibit 1033-0004
`
`€
`

`
`FIIIIILI
`
`'Z'lIefluJIdarilzad0npllaJlsalIdI‘t¢rutt'v¢pruc¢.ss
`
`3, Demiledspeciflcations. whete every interface is specified in daail.
`4. itxdngandwrificmtbmwhetethemtafioespeeificafionsucprovenw
`workwith real-lifeequipment.
`
`These phases ere overlapping and itentive. As an example. requirements can be
`added. changed. or dmwed duting the later phases if the technical solutions call
`for i_t. Likewise. the technical solution in the detailed specifications can change
`dueto ptoblemsfound in thetatingandverificationphnae.
`
`Standatdimtion starts with the ruquimnems phase, where the standards body
`decides wbatnhouldhonchieved withthe standard. Thisphueia usually teln-
`tively nhort.
`
`In tlteardutecmre phase. the sumdards body decides about the a1chitectI:ue,i.e.
`the principles of how to meet the teqnhements. The utchitectule phase includes
`decisions about tefexmce points and interfaces to be nandardized. This phase is
`usually quite long and may change the tequitemeats
`
`Aflertheatchitectunephase, the daailedspccijicatian phaeestans. It is inthis
`phase the details the each of the identified interfaces are specified. During the
`detailed specification of the irmei-faces. the standards body may find that it has
`to chlnge decisions done either in the architecture :3’ even in the requirement:
`phases.
`
`F1na'lly.tl1ete:ti:t5ra1tdver¢‘Iicationphz:sestarts. ltisusuailynotapanofthe
`actual stattdaldiulionin theataudaldsbodies. buttnkesplace in parallel flnough
`testlttgbyvendots andimn'opetabilitytatinghetweenvs1dol1.Thisphaseis
`thefinnlpuoofofthestandatd. During the teatingandverification phaee,et-tors
`in the standard may still he found and those errors may change decisions in the
`detailed atnnthtd. Albeit not common. changes may need In be done also totlle
`atchitectute or the requitements. To verify the standard. products are needed.
`l-lance. the implementation of the pmduas stints afler (or during) the daailed
`specification phase. The testing and verification phase ends when there are
`
`Figure 1.2
`
`JGPP orgauhxlan.
`
`i
`
`stable test specifications that can be used to verify that the equipment is fulfilling
`the standard.
`
`Normally, it tubes one to two years ftom the time when the standard is com-
`pleted until commercial products are out on the marltet. However, ifthe standard
`is built from scratch. it may talne longer time since there an no stable compo-
`nents to build from.
`'
`
`1.2.2 3GF'P
`
`Tb 71u‘rd-Generation Rtrmcnhip Project CSGPP) in the atxndlds-developing
`body rliatnpeoifies the 3GUTRAandGSM syatema.3GPPisapnItnmthippmject
`formed by the standards bodies l:Tl‘Sl. ARIB. 'li'IlC. TIA. OZSA and A118. 3GPP
`consists of sevetal Teclm.ictI| Specifiuttious Gloups (TSOS ). (see Figure 1.2).
`
`l_\ parallel partnership project called SGPP2 was formed in 1999. It also devel-
`ops 3G specifications. but for cdma2000. which is the 3G technology developed
`
`ZTE/HTC
`Exhibit 1033-0005
`
`

`
`I0
`
`'
`
`I
`
`36 B'i¢lutloII:flSPAMlL1'EfirMobllt.BImdl9atd
`
`fioln the 2G CDMA-based standard 13-95. It is also a global project. and the
`organintional partners are ARIB. CCSA. TIA, TIA Iod'I'l‘C.
`‘
`
`3GPPTSGRANlsuletechnlealspeciflcatlongloupdlaxhasdevelopedWCDMA.
`itsevohltionl-lSPA.asvvellas_IJ'E.andisixlthefolefrontofthetechno|ogy.'l'SG
`RANcooxlst_solllveworldnggmups(WGs):
`
`1. RANWGI dealingwithtbephyeiéal layer
`2. RAN WG2 dealing with the layer 2 and leyerl radio interiwe q)ecl'ficatiom.
`3. RAN WG3 dealing with the fixed RAN interfaces, furexample interfaces
`betweennodeeinIheR.AN,hmnlnodleinn=t'hoehetweerltheRANmdthe
`noremnwork.
`4. RANW'G4dealingwithd1eradiofiequency(RP)andmdiore:auIeemavi-
`agemeur (RRM) perfonnanee requirements.
`.
`5. RANWG5deal.in,gwithlh9tvouni.naloonfotmaneetuting.
`
`'['he.seopeof3GPPwhenltwaslbnnedln l99Bwmtoprodueeg1obelapeclll-
`cationsfora3GmoIlilesyatemhaaedonnllevolvedGSMeorenetwod:.including
`the WCDMA-based radio access of the UTRA FDD and the TD-CDMA-based
`rad'u:messofdBUTRATDDnnde.11leta:ktonmintninulddeve1opflle
`GSMlBDGl.‘,speclfieatiorlr \vasaddedt:o3GPPstnlnIerstnge.TheU'l'RA(amd
`GSMEDGB) aifecilicaiions ale developed, maintained and approved in 3GPP.
`Aftm'approvnLfl:emganiznimnlpumuIu‘mapoeelheminmippropfinnede1iv-
`e~.'ahlesasuat1dnnk inendl region.
`
`lnparullelwithtIieinitiAl3GPPwork. a3G6yItembuedon'I'DSCDMAwu
`developedinChin1.TD-SCDMAwaseveuuullymelgedirltoRelease4oftlle
`SGPP specifimtionsasanadditinnal TDD mode.
`
`Theworkin3GPPiscaxriedonrudxhrelevantI1'Uxecommendationsinmind
`and the result of the work is also submitted In l.TU. The olganiutional put-
`nerealeobligedto identifylegiomlrequirernmmtlmmay leedlooplionaintlle
`standard. Examples are regional freqilency bands and special protection require-
`ments local to a region. The specifications are developed with global roaming
`and circllllltion of terminals in mind. This implies that many regional require-
`nlentsineeeencewillbeglobalroquilementn foul] mmhlalgsinuamuning
`terminal hes to meet the strictest of all regional requiremts. Regional options
`in the specifications are thus more common for blue stations than for terminals.
`
`The specifications of ell releases an be updated afler each set ol'TSG meeting,
`whiehoculr4fimesayear.11le3GPPdocumenmamdividedinwmleases.where
`
`WU!!! 1.3 Ra!uJaof3G!’P:p¢q'filafiomfarUTRA.
`
`‘eacllm1usehnasetoffeaunesaddedmnparedmthapievioureleese.'nlefe+
`mleearedefinedinwwklnemsagxeedmilmda-mkenbythe1'SGs.Thercleases
`uptlallielleaselialldsornemainfealillesofthomateshawninF’l,gurel.3.The
`dateshownRneachreleuelsthedayrtecontentofdlemleasewuftmen.Fnr
`the firs: release is numbered by the year-it was frozen (1999),
`whilethefollowingleleuauemnnbeled4.5,etc.
`
`For the WCDMA Radio ADOBE developed in TSG RAN, Relense 99 contains
`all features needed to meet the IMT-2000 requirements as defined by 1111.
`'l‘lle1-e are cirulii-switched voice and video services‘, and data services over both
`packet-switched and circuit-svlltlclled bearers. The first major addition of radio
`access features to WCDMA is Release 5 with High Speed Downlink Racket
`Access (HSDPA) and Release 6 with Enhanced Uplink. These two are mgerlla:
`le:Ea1edtnasl-lSPAandaredesc-ribedinmoredetnilinPanlltofthisbook.
`Willi HSPA.U'l'RAgoes beyond the definition ch; 36 mobile sysuemand also
`erlcompas broadband mobile data.
`
`With the inclusion of an Evolved UTRAN (LTE) and the related symn
`Amllitectlae Evolution (SAE) in Release 3. furthu steps are taken" in mm of
`broadband mpabilities. The specific solutions chosen for LTB and SAB are
`deac1'ibedinP|rtlVoftllisboek.
`.
`
`1.23 IMT-2000 activities in ITU
`
`The plasma l'l'U work on 3G takes place in [TU-R Working may 50‘ (wpsm,
`wllel-l:3Gsyatem: ntelefetredm nlM‘l'-2000. WP5Ddoee notwritetedlniczil
`
`‘1\awuxonn4rr-zeooivmmunnmwoiungruiysruwmungrmysrllnzoav.
`
`ZTE/HTC
`Exhibit 1033-0006
`
`

`
`36 Evolrdiort: EM mJLTEfir Mobik Broadband
`
`fltenrorlmbdrbtdrlnrlcelobnloa
`
`2|
`
`Fhrnzl 1lnbltrnu—JrIaya¢wicc:paeeA\ul:lnqponaMh:0avu_whcndalgniI;aMw
`aelldarsyelem.
`
`offl|emobileoommunieafimrystetnsneedtosmpatareaaonnbleleveLalevel
`thntmeteehnologyavaflableatfltetinieofstandarrlizafiareanpzuvide.
`
`2.1.3 Cost andperfonnance
`‘There is motltepirnportant driving hour fior future nwbile-ootntnlllieatiott sys-
`empu1ddtuisthheostofduwrvioeprovLskmh:g.Theted1nobgyadvmeen:nt
`thatenabksnewservicescanflsobeu&hzedtopmvidebenermalilo-oommuni-
`cuionsystmnrusingmoreadnmedtochnicalfomnos.HerelPneehmhgyisnm
`only; key ennblertu allow for new servioeslnpop np.lmulsoaway ofreduc-
`ingeootofnewaervioes.1'hereasoninthntIPnsabearerofnewservienscnnbo
`nndtointroduoenewnervieesasthey cornomotrequiringanertensivespecial
`design oftl1esystem.0fcourse.tlisrequirt:a flntthodeviees u.1edinthemobila-
`oomrmnication systernoanbepmgrnmntedlaylhird-pattyprovidersandfltattite
`opmmmanownird-pmymvbcprwuasmmeflaeirnerwukfueormnunicatbn.
`
`Anndfl'impuuntfactnristhntopa'nlmSneedtop10Videflnservi:estoaHtte
`usas.Notonlyonouserneedsloguttl1elUWde1ay.highdIl¢ruie,elc.tllntils
`savleeneech.bnta1lmetoaswhhdtdr_diflm-anerviceneedrshnmdbesuved
`eflleimtly. The proeming capacity evolution nndMoore‘a lawhelpalao for this
`pmhlem. New techniques are enabled by the higher rxowssing power in the
`devices-reehniqresthntdelivcnr morebitaofdatnperht-rtz.Funhn-more,tlte
`eoveugeisiocmasedwhhmoreadvanoedantemmmdreoeive:s.Thisenab]es
`theopetatwnlodelivertbeservioeslornoreusersfivmenebneatuionfilms
`requiring fewer sites. Fewa sites imply lower qauational and capitalization costs.
`Ineasmoeflteopuuorsneedlewerhmestationsandsheehoprovideflnsewice.
`
`if they were provided with the
`Obviously. all services would be ‘happy’
`highest data rate, lowest delay. and lowest jitter that the systnn can provide
`Unfortunnuely. this is unattainable in practice and contradictory to theoperamr
`goalofaneflieicntrymanzinahu-words,themmedelayaservioecmlundle
`themereaflicientthesyaoemcanbe.11m.theoostofprvviding lowutpossi-
`bledelny,jitterandea1lsemptirneissarnewhatinoonflictwiflr thenaedofthe
`mobile-networlropentortnprovideitnoalltlteuua-r.Her1oe.thereisatrade-of!
`between user experience and system performance. The better the sysem per-
`fonmnoeiauhelowertlnaostoftltenatwork.Howovernheendtreersulooneed
`wgetadequatepct'Eommoewhlehofienisinconfliawiththeaysnunpufonn-
`once. that the opeumt ctnnot only optimize for system performance.
`«
`
`2.2 36 evolution: Two Radio Access Network approaches
`_and an evolved core network
`2.2. 1 Radio Access Network evolution
`
`TSG RAN organized a workshop on 3GPP long-tum Evolution in the fall of
`zC04.'I‘lteworkshop wuthesurtirigpointofthc dtwelopmentofthe Long-
`Tam Bvolution(l.1'E) radio intafaee. Ana the initinl toquiromontphase lo the
`spu‘ngofZOD5, wheretltetar2etsamlohiectivosofLTEweresetfled.theted:ni-
`cal specification group TSG SA launched a corresponding wad: on the System
`Architecture Evolution, since it was felt tlut the LIE radio interface neetbd a
`suitable evolved system architecture.
`.
`
`'l'heresultoftheL'l‘B~wortsl1op vIastlIalaslndyitelnin3GPPTSGRAN
`wasctealedinDecember2lX)4.The£lt1t 6 months werospentondefiningthe
`requirements. ordesignmrgets. mcuarhaewuedocummud 1na3G1'>P
`technical report [86] and approved in June 2005. (Input 13 will go throtlgh
`the requirernents in more detail. Most notabloaretherequiremertts on high-data
`ntartthceol!edgeandtl1oimportanceoflowdelny,inadditionnothenomml
`enpacity andpeakdntnmcrequiremetu. Purthenrtorempectrurnflexibilityanrl
`nnximum commonality between PDDa.t1dTDD rolutiurtsrnepronooncad.
`
`During the fall 2005, 3GPP 1’SG RAN W0] made extensive studies of different
`basic physical layer technologies and in December 2005 the T86 RAN plenary
`decided that the LTE radio access should be based on 0Fl_)M in the downlink
`and single carrier FDMA in the uplink.
`
`TSG RAN and its working groups then worked on the 1.113 specifications and
`the specifications were approved in December 2007. However. JGPP TSG RAN
`did not stop working on LT}! when the first version of the specifications was
`
`ZTE/HTC
`Exhibit 1033-0007
`
`

`
`432
`
`3GEhvludon.‘ HEM DdLIEJWfloblk Broldbd
`
`In case of a relatively small SI and a relatively lerge system bandwidth, a sin-
`gle suhfnme may be euficient for the tmnsniission of the 81. In other cases,
`multiph rubfrnmesmnybeneededforthetmnamisonofnsinglesl. lntlu:
`latter case, instead of segmenting each SI into sufficiently small block: tlm
`azesepateue1ychenneloodedandnanrmittedmsepmtesubfiemes.thewm-
`pleteslischutneleodedendmnppedtomulriplmnotneoesurily eonseeutive
`subfrarnea.
`
`SiinilnmdtecaseofdteBCH.terminehfltatateexpe1iencinggoodchannel
`ooiiditiotlsmaydnrtheabledecodemecomplewsletterteceiviugonlyasub
`setoftilesubfitemestowhichtheoodedSlismxpped,wl:i1eterminalsi.nbad
`positions need to receive more subfntnet for prop: decoding of the $1. This
`apptundthsntwobenefits:
`
`I Similar to BC}! decoding, terrninnls in good position: need to Iemive fewer
`subfnmes, implying the possibility for reduced terminal power eonrumpdon.
`o 'l‘he use of larger eode blocks in eornhinatien with ‘limbo ending lends to
`improved channel-coding gain.
`
`13.3 Random neeess
`
`A fundamental reqiiirement for any cellular system is the possibility for the ter-
`minal to request a connection settm. commonly tefened to as random access. In
`LTE, rnndomneoess ixnaedforseveral purposes, including:
`
`for initialaooets when establishing a radio link (moving from RRCJDIJ3 to
`RRC_CONNBC'l‘ED: see Chapter 15 for a discussion on ditferent tenninal
`states);
`to re-estnblirh a radio link afterradio link failure;
`for handover when uplink syntzhrtmizntion needs no he estahlislnd to the
`new cell;
`to establish uplink synchronization if uplink or downlinlt date arrives when
`the terminal is in RRC_CONNBCTH) and the uplink is not synchronized;
`as a scheduling request if no dedicated scheduling-request resources have
`beenean.figuredonPLlCCH(teeClmpter 19 foradiseussinnonuplink
`scheduling procedures).
`
`Esublishntem of uplink synchronimtion is the main objective for all the cases
`above: when establishing en
`radio link (i.e.. when moving from RRC_
`IDLE In RRC_CONNEC'I‘ED). the random-ncoesr procedure also serves the
`purpose otesslgnlng it unique ldentity. the C-RN11. to the terminal.
`
`Flptre I81 Owrviewofriu rwtdalt-«ecu: procedure.
`
`The basis for random access in a contention-based procedure. illustrated in
`Fign:e1s.8,andoonsisu offourttepe:
`
`1. nnmstsep consists oftnnernissiort nfa lfllldolll-30C$$|X¢amN¢,IlI|1Wi.l§
`the eNodeB tn stirnate the transnI'ssion timing ofthe terminal. Uplink synchro-
`nimtionie rtecesenryas theterminalotherwisecarmottranemitany uplinkd.aia_
`. The second step consists of the network transmitting a tinting advance com-
`mand to adjust the terminal transmit timing, based on the timing estimate in
`the fint step. In addition to establishing uplinl: syrtdtronizatian, the second
`atepnlsousignsuplinktewtuoeetothetemnnnltoheusedinthethirdstep
`in the random-access pronenitre.
`. The third step consists of transnission of the mobile-tuminnl identity to
`the network using the UL-SCH similar to normal scheduled date. The exact
`content ofthis ignsling tbpends on the statue of the terminal, in particular
`whether it is previously lmawn to the network or not.
`. The fourth and final step consists of transmission of at contention-molution
`meuageftom the networktotheterm'tnnlontheDL-SCI-I. This step also
`resolves any contention due to multiple terminals trying to access the system
`using the same nndon1—aoeess resource.
`
`Only the tint step uses physical-layer processing specifically designed for ran-
`dom access. 11:: last three steps utilize the same physical-layer processing as
`
`ZTE/HTC
`Exhibit 1033-0008
`
`

`
`434
`
`5G Elaoluliut: HS!!! and LltfaruablkBmedlad
`
`L13axecrprocedruer
`
`435
`
`used for normal uplinl: and dawnlink data transmission. In the following. each
`of these steps is described in more detail.
`
`step. Hence. [min tlte preamble die uenninal used, the eNodel3, will get some
`guidance on the emount of uplinl: motuces to be granted to the terminal.
`
`Additionally. for handover purposes it is possible to use the random-access
`medtanism in a eontention-flee manner as described further below. In this case
`nnlythefitittwusleps oflhepmt:e4l.t.uenreusednsflnreisnoneedfnrconlen-
`lion resolution in : conieniiomfiee scheme.
`
`18.3. 1 Step 1: Random-access preamble transmission
`The firs: step in the random-access procedure is the tntnsrnission on random-
`ncoe preamble. 1‘he main purpose of the prmmble transmission is to indiare
`no the hue station the presence of it random-access attempt and to allow the
`bnsestnfiontoestimntethedeIoybetweer1flteeNodeBunddteUamirtalThe
`delay estimate will be used in the second step to adjust the uplinl:
`
`The time-trequency resounee on which the randurn-access preamble is transmit-
`ted upon is lcnorvn as the Phyviazl Random Accm Channel (PRACH). The net-
`work broadcast: infonmtion to nll tennimls in which tirrte-frequency resources
`random-aeceu preamble trartsrniuion is allowed (ie.. the PRACH resources, in
`SIB-2). As part
`the fitst step of the randotn-acceu procedure, the terminal
`selects one preamble In lnrtslrtil on the PRACH.
`
`In each celL there are 64 preamble sequences avai1Ahle.'l\N‘o subsets oflhe 64
`sequences are defined as illustrated in Figure 18.9. where the set of sequences
`in each subset is signaled as part of the system information. When performing
`a (contention-based) random-access attempt. the terminal at random Ielect: one
`sequenoeiuoneofd1esuhsets.As1ougasnootherterminnlisperiorminga
`random-access attempt using the same sequence etthe same time instant. no
`ee1llnionswfllocetnandrheunemptwin.wldiahlghflkeuhood.bedenecnedby
`lheeNodeB.
`
`Iheeubsettoseleetdtepreemblesequerieefromisgivenbythenrnoumofdntn
`theterminalwouldfllcetnnnnsmitonflteULrSC'HiuthethiIdnndom-access
`
`Fnemhio not no
`
`64 P-umhtu In oedl eel
`
`Igure 13.9 Pnanble urban
`
`Ifthe terminal has been requested to parent: a connention-free nndom aeeeas.
`forexample. forlnndovertnauew cell. Ihepieamble tn useis explicitly indi-
`cated fmrn the eNodeB. To avoid collisions, the eNodeB should preferably
`select the contention-free preamble from sequences outside the two subsets used
`for contention-based random access.
`
`18.3.1.1 PHACH flmo-frequency resources
`In the frequency domain, the PRACH renounce. illustrated in Figure 18.10,
`in: a bandwidth corresponding to six resource blocks (l.08MHz). This nicely
`rnntehes the smallest uplink cell bandwidth of six resource block: in which LTE
`can operate. Hence. the same random-access preamble stru.ctu.re can be used.
`regurdlessoftbetransrniseionbnndwirlthintheeell.
`
`In the time domain, the length of the preamble region depeudson configured
`preambleswillhe discussed iurt:herbeIow.'I'hebasicrandorn-ucees resource
`is lmsinduration.,butd1ereisuleothepoarlbiliry ooeonligtueltirtgerpreanr
`blei. Also. note that the eNodeB uplink scheduler in principle can reserve an
`xbitmry long random-access reg'ou by simply avokiing scheduling terminals in
`multiple subsequent sultframes.
`3-
`
`Typically. the eNode.'B evoide scheduling any uplink transmissions in the time-
`frequency resumes usedforrmdomeeeess.'l'hienvoidsinterfa‘eucebetween
`UL-SCH tlmstnisaiom and mnsdom-access attempt: from difierent
`tenni-
`nals.’Ihnrandom-scoesspreambleissaidtobeorthngonaltourerdarn, unlike
`WCDMA where uplink date u-anemiaaion and randorn-«wees attempts share the
`same resources. However. from a speciiication perspective. nothing prevents the
`upliuk scheduler to sehedule uznamimionn in the random-eceeas region. Hybrid-
`ARQ retransmission: are an example of thb: synchronous non-adaptive hybrid-
`ARQretrnn:rnis:ionsmayovedap withtherandorn-aeoeasregionenditiaupto
`the implementation to handle this. either by moving the retransmission: in the
`frequency domain as discussed in Chapter 1.9 or by lnndling theinterferenee at
`the eNodeB receiver.
`
`ForFDD, there is at most one random-access region per subfrnme. that is, utiliti-
`ple random-s attempts 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 avenge waiting time before a rnndorn-access
`attempt can be
`For TDD. multiple random-access regions can be
`
`ZTE/HTC
`Exhibit 1033-0009