as) United States
`a2) Patent Application Publication co) Pub. No.: US 2013/0039202 Al
`(43) Pub. Date: Feb. 14, 2013
`
`Feuersangeret al.
`
`US 20130039202A1
`
`(54) COMPONENT CARRIER (DE)ACTIVATION
`IN COMMUNICATION SYSTEMS USING
`CARRIER AGGREGATION
`
`(75)
`
`Inventors: Martin Feuersanger, Bremen (DE);
`Joachim Lohr, Wiesbaden (DE);
`Alexander Golitschek Edler Von
`
`Elbwart, Darmstadt (DE); Christian
`Wengerter, Kleinheubach (DE)
`
`(73) Assignee: PANASONIC CORPORATION,Osaka
`(JP)
`
`(21) Appl. No.:
`
`13/578,216
`
`(22)
`
`PCTFiled:
`
`Feb. 4, 2011
`
`(86) PCT No.:
`
`PCT/EP2011/000532
`
`§ 371 ()Q),
`(2), (4) Date:
`
`Oct. 5, 2012
`
`(30)
`
`Foreign Application Priority Data
`
`Feb. 12, 2010
`Apr. 1, 2010
`
`(EP) veecssssssseessesssesssseessen 10001479.4
`(EP) veecssssssseessesssssssseessen 10003667.2
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`(2009.01)
`HO4W 72/00
`(2009.01)
`HO4W 24/00
`(52) US. CD.
`cccccsesssssssssssssssssseneeseeseees 370/252; 370/329
`
`(57)
`
`ABSTRACT
`
`This invention relates to the proposal of componentcarrier
`(de)activation message that is allowing a activation or deac-
`tivation of one or more componentcarriers in the uplink or
`downlink. Furthermore, the invention relates to the use of the
`new componentcarrier (de)activation message in methodsfor
`(de)activation of downlink componentcarrier(s) configured
`for a mobile terminal, a base station and a mobile terminal. To
`enable efficient and robust (de)activation of componentcar-
`riers, the invention proposes to use componentcarrier-spe-
`cific or cell-RNTI(s) for the scrambling of the CRC of the
`componentcarrier (de)activation message, and to explicitly
`indicate the intended recipient of the componentcarrier (de)
`activation message in a correspondingfield in the message.
`Furthermore, the invention further proposes different designs
`of the componentcarrier (de)activation message and further
`uses thereof, so as to trigger CQI reporting and/or SRStrans-
`mission by a mobile terminal.
`
`SFCa oe
`
`g
`
`Operator
`Services
`
`(y)
`
`< SGi
`
`
`
`
`
`
`yj vew_f} & $5
`
`IP access
`
`Untrusted non-3GPP
`
`oy,
`
`&
`
`Trusted/Untrusted
`
`non-3GGP/3GPP
`
`IP access
`
`
`UE
`
`eNB
`
`Sarving-GW
`
`Trusted non-3GPP
`
`IP access
`
`qU
`
`E
`
`SAMSUNG 1005
`
`SAMSUNG 1005
`
`1
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 1 of 18
`
`US 2013/0039202 Al
`
`Joyeedo
`
`SOdINeS
`
`SSH
`
` \_
`adI}
`jaw}
`
`295
`
`
`
`ddO¢-Uoupeysnqun
`
`ssa0cedq]
`
`paysruyupypeysruy
`
`dddeidooe-uou
`
`ssed0ed]
`
`
`
`ddSDe-uoupays
`
`SS8008gj
`
`|64
`
`&x
`
`12
`
`OS
`
`Mo-Gujales
`
`an|nalli,20
`
`2
`
`
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 2 of 18
`
`US 2013/0039202 Al
`
`ServingGW
`
`
`
`MME/ServingGWMME/
`
`3
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 3 of 18
`
`US 2013/0039202 Al
`
`sub-frame
`
`*downlink | downlink |
`slot
`i
`slot
`i
`f
`\
`Trot
`Tro /
`/
`
`k= NDLVRB _}
`earecaetesienne rT
`||
`
`PETTTT
`PtyTy
`PTEtett
`PttTTEtT
`PTTTT
`Pe
`PETttt
`PettTt
`PETTt
`PTTTTI
`PtTtyt
`Ptyyy
`PttT
`PttTet
`Petttt
`PEtTtTTt
`
`NekxNZ®subcarriers
`
`
`
`
`
`P|td
`—_fitcetTt
`1=0
`
`k=0
`t= Ney— |
`
`4
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 4 of 18
`
`US 2013/0039202 Al
`
`One downlink slot 7;
`
`\
`;
`/
`.
`( Neyep OFDM symbols»
`
`——_—— Resource block
`
`Now x NE® resource elements
`
`§
`.
`3 g
`=
`
`Bi
`5
`=|
`*«
`ag
`z
`
`Resource element (k,/)
`
`5
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 5 of 18
`
`US 2013/0039202 Al
`
`Bulxejdainy“an=
`Burjpuey—{Buynpeyugsjseoiun
`
`3)8DYV338OHV
`
`SHOUSHOW
`
`‘wes‘wBag
`syauuny)1091807Jd
`
`
`-SiaavagoIpoyC>
`ws319DYV318DYV
`rar]-Ca)|T_.
`feu]~[bavi
`
`‘wBasg‘was
`
`
`
`HOOdHOOFHIDD
`
`
`
`
`
`©©C>sauuny’)jaodsuo4.yC>C>
`
`~~dodd
`
`
`
`
`
`
`
`HOW,HodHogHOS~1dHOS-1dHOS-1dHOS71d
`
`g‘Big
`
`“9to19uo*9UoIg00
`
`6
`
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 14,2013 Sheet 6 of 18
`
`US 2013/0039202 Al
`
`perm re Radio Bearers
`
`
`
`PDCP ~<
`
`RLC -<
`
`naceeeenecee
`
`ecneeennecnenennecnenee
`
`\,womennn
`
`Sernnnnno
`
`nnnnnnn
`
`prnnrnnnLogical Channels
`
`MAC <
`
`Nenpnnnn cececca Transport Channels
`
`
`
`UL-SCH
`on CC,
`
`UL-SCH
`on CC,
`
`Fig. 6
`
`7
`
`

`

`Patent Application Publication
`
`Feb. 14,2013 Sheet 7 of 18
`
`US 2013/0039202 Al
`
`
`
`Fig. 7
`
`
`
`Fig. 8
`
`8
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 8 of 18
`
`z
`
`3
`os2
`85
`85
`55
`ae
`
`Pad
`
`acm
`
`&e
`
`2
`
`US 2013/0039202 Al
`
`Fig.9
`
`MCS= M ele
`
`aoao
`a
`
`<<ao
`ae
`
`Sao
`
`eae|efiefee|
`
`MCS
`
`9
`
`

`

`Patent Application Publ
`
`icat
`
`ion
`
`US 2013/0039202 Al
`
`
`
`asnpapuayxe/Buipped
`
`
`
`(SuiqZ0}0)yyGue7juepuadag
`
`"Ma
`
`Feb. 14, 2013 Sheet 9 of 18
`
`pv(ea)
`
`
`
`mise)|Parsowtat|wien|Ectoowin|Fen]arcoveie|Aem|torso|cianayleg)|PASOPBEL|nvieq)|ECDL|oiiaq)|2a1901e6eL
`
`
`Lal99yebveyGlanyefvey
`+OOFOFOut51142wsSUq?WatS92waeSQZSHqOL
`
`SidG0}0iq}Sug2SHG?SUZSU9}
`
`
`eaoorehe,|Zaire,|tq}90166,aanyebuey—
`SUQ§0}2HaLSHqZSq9}
`pylag)|0!90e6eLainyebie)
`
`>-———_—>+—_:—«nk
`
`_—__
`
`jBurpped
`
`
`
`asnpapuayxe
`
`pv(eq)
`
`bey
`
`Bey
`
`0}‘Big
`
`
`
`LL“Big
`
`2}‘64
`
`}bey
`
`10
`
`10
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`SUGOLOESUG?SwSL
`
`
`
`asnpapus}xe/Bulpped
`
`Gi9916e,GI3nyehuey
`
`Feb. 14, 2013 Sheet 10 of 18
`
`
`
`esnpepus)xa/buippedbeyGlanyeue,
`
`py(eq)
`
`11
`
`vb‘64
`
`SiGZLFSSHIQ9}
`
`e}‘By
`
`SUG|}OYWhS1!q9}
`
`US 2013/0039202 Al
`
`
`
`/Buipped
`
`
`
`asnpapus|xe
`
`aianyebiey
`
`G}‘big
`
`11
`
`
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 11 of 18
`
`US 2013/0039202 Al
`
`
`
`asnpepueyxe/Buipped
`
`asnpapusyxe/Buipped
`
`pjeyeaunosal
`
`rnpth
`
`S14.90}0SUQZwyWq5SHGSHGOF
`SH89}WwWWaSQZSUq9
`ypeqpea}00|19|pvyieg)|M99}glaneve
`jsanbar|BeyDo|yaylag)|19979621gianye6ve
` Ly‘64
`
`
`
`
`9}‘Bly
`
`12
`
`12
`
`
`
`
`

`

`Feb. 14, 2013 Sheet 12 of 18
`
`US 2013/0039202 Al
`
`
`
`asnpapuayxe/Guipped
`
`
`
`esnpepue}xe/Buipped
`
`Patent Application Publication
`
`SS
`
`$19.8}1WLwatsugZeal
`SHG80}|sidpS}!q94
` 61‘blyaway(ag)|01:9016681Ql3nyefuey
`
`
`—SSS"
`yseuryiq)-aianyefvey,
`
`gt‘By
`
`13
`
`13
`
`
`
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 13 of 18
`
`US 2013/0039202 Al
`
`
`
`puepaunByuoo20014
`
`
`
`payeagoeeppayeanoepuepainByuos79910payeanoeappuepeunByuoo79910
`
`
`
`
`
`uogeapesg
`
`
`
`10)YOWOUVHUOREAROY10}HOV-DUVH
`
`sup|SU
`
`02‘B14
`
`(WNY-uogeAqoe8q)
`
`
`
`uoneaqoe55ebesseuuonennoeEp99eBessaw
`
`
`
`(LINuoReAnoy)
`
`20910
`
`L993TN
`
`
`
`(aanoeseme)
`
`bO91d
`
`
`
`(aanoesAemje
`
`
`
`“Ja1J29JOYyoUe)
`
`14
`
`14
`
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 14 of 18
`
`US 2013/0039202 Al
`
`
`
`40)YOV-OUVH
`
`uoqeagoee()
`
`
`
`ywoudwy)Z091040}109
`
`OY
`
`L2‘Bi.
`
`49910
`
`
`
`(aajoeskemye
`
`“JUDJOYoUe)
`
`b99TN
`
`
`
`(aanjoeskemje)
`
`
`
`puepainByuoo29910
`
`payeagoeep
`
`payeanoepuepainByuos79919
`
`
`
`payeanoeappuepanByueo29910
`
`"
`
`
`
`ebessowuoneaqoeep99
`
`(WNY-Uogeanoesq)
`
`
`
`aBessawuogeagoe95
`
`(LING-Uogeanoy)
`
`15
`
`20910
`
`15
`
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 15 of 18
`
`US 2013/0039202 Al
`
`
`
`puepainByuoo7991dLoooyms
`
`
`
`
`
`
`
`peyeagoeeppayeanoepuepaunByuos79910payeagoeeppuepainByuoo79910
`
`40}YOV-ONVH
`
`UogRApESg
`
`10)10991POpod
`
`79910
`
`swSy
` zz‘Bid
`
`
`
`uonegge35ebessewuopeanoeap45aBessou
`
`
`
`
`
`
`
`109°LISda0IN
`
`20910
`
`b991N
`
`
`
`(aanoeskemje)
`
`b9914
`
`
`
`(aanoeskemye
`
`
`
`‘yaluedsoyoue)
`
`16
`
`16
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 16 of 18
`
`US 2013/0039202 Al
`
`
`
`puepaunByuod7991d
`
`uonUARIy*auDsongN
`
`payeagoeap
`
`79910
`
`eBessew
`
`
`
`40)JOW-OUVH
`
`uogeagoreg
`
`uoqeagoeep99 payeagoepuepeinByuod
`
`
`
`payeagoeeppuepainByuoo7991q
`
`
`
`afessewuoqeaqoe95
`
`29910
`
`L3991N
`
`
`
`(aaoeskemye)
`
`
`
`(aanoeskemye
`
`
`
`‘so1UedJOYoUe)
`
`b910
`
`17
`
`¢z‘Big
`
`TOD'LISALO7
`
`17
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 17 of 18
`
`US 2013/0039202 Al
`
`
`
`
`
`(dewyiquoneagoe(ap)Sys)
`
`JOS1N44|DOSTNA|SOSWING|DOS1N405 Nrmel
`—————————ehOSWY__-eee99S10€99810290810b9981d
`orpayy|orpayuy|o}payuy|0}peyuy|eeeeee|eee|ooneanoe|mewn:
`payul|UoUoReANOe(ep)SYSJO)pasnsyiquojeaoe(ap)sawedyuaUCdWOOyUI|UMOPJOpesnsjiq
`
`
`
`
`SJeluedJuaUOdWwosyuIjdn(dewniquoneagoe(ap)59)
`
`
`
`
`
`(azjSUl393901)JUaWAa]afoujJUODJY
`
`/payeaqoe[/Payeagoe[PayeAnoe/payeaqoe
`
`
`
`
`7990S10€90S1d|2908710499810
`
`yz‘Bly
`
`18
`
`18
`
`

`

`Patent Application Publication
`
`Feb. 14, 2013 Sheet 18 of 18
`
`US 2013/0039202 Al
`
`9snPpapuajxe
`
`/Gupped
`yOOS|£008
`SYS|SHS
`BeyBey
`Wq4Wat
`@snpepue}xe
`
`SidBO}|
`fSupped
`
`SYS
`
`2909S
`
`Bey
`
`LOS
`
`POOSIOIEIOS10}Z09S10}}00S10Gian
`
`DE}DEYDelDey
`
`
`
`
`
`
`
`YIOS10699810/z99s10|199s10aianyebvey
`
`
`
`——>+—_+>Wd1wahWahWatSHq9}
`
`SuS
`
`Wq4
`
`Wa}
`
`Gz‘bl4
`
`19
`
`jefe, Sq9b
`+>+_>+>OOSEetOOSPA>Hq710
`
`Bey
`
`beyBeyBeybey
`
`92‘Bi4
`
`
`
`
`
`
`
`19
`
`
`

`

`US 2013/0039202 Al
`
`Feb. 14, 2013
`
`COMPONENT CARRIER (DE)ACTIVATION
`IN COMMUNICATION SYSTEMS USING
`CARRIER AGGREGATION
`
`FIELD OF THE INVENTION
`
`[0001] This invention relates to the proposal of component
`carrier (de)activation message that is allowing an activation
`or deactivation of one or more component carriers in the
`uplink or downlink. Furthermore, the invention relates to the
`use of the new componentcarrier (de)activation message in
`methodsfor (de)activation of downlink componentcarrier(s)
`configured for a mobile terminal, a base station and a mobile
`terminal.
`
`TECHNICAL BACKGROUND
`
`Long Term Evolution (LTE)
`
`[0002] Third-generation mobile systems (3G) based on
`WCDMAradio-access technology are being deployed on a
`broad scale all around the world.A first step in enhancing or
`evolving this technology entails introducing High-Speed
`Downlink Packet Access (HSDPA) and an enhanceduplink,
`also referred to as High Speed Uplink Packet Access
`(HSUPA), giving a radio-access technology that is highly
`competitive:
`[0003]
`In order to be prepared for further increasing user
`demands and to be competitive against new radio access
`technologies 3GPPintroduced a new mobile communication
`system which is called Long Term Evolution (LTE). LTE is
`designed to meet the carrier needs for high speed data and
`media transport as well as high capacity voice support to the
`next decade. The ability to provide high bit rates is a key
`measure for LTE.
`
`[0004] The work item (WI) specification on Long-Term
`Evolution (LTE) called Evolved UMTSTerrestrial Radio
`Access (UTRA) and UMTSTerrestrial Radio Access Net-
`work (UTRAN)is to be finalized as Release 8 (LTE). The
`LTE system represents efficient packet-based radio access
`and radio access networks that provide full IP-based func-
`tionalities with low latency and low cost. The detailed system
`requirements are given in. In LTE, scalable multiple trans-
`mission bandwidths are specified such as 1.4, 3.0, 5.0, 10.0,
`15.0, and 20.0 MHz, in order to achieve flexible system
`deployment using a given spectrum.
`In the downlink,
`Orthogonal Frequency Division Multiplexing (OFDM)based
`radio access was adopted becauseofits inherent immunity to
`multipath interference (MPI) due to a low symbolrate, the use
`of a cyclic prefix (CP), andits affinity to different transmis-
`sion bandwidth arrangements. Single-Carrier Frequency
`Division Multiple Access (SC-FDMA) based radio access
`was adopted in the uplink, since provisioning of wide area
`coverage wasprioritized over improvementin the peak data
`rate considering the restricted transmission powerofthe user
`equipment (UE). Many key packet radio access techniques
`are employed including multiple-input multiple-output
`(MIMO)channeltransmission techniques, and a highlyeffi-
`cient control signaling structure is achieved in LTE (Release
`8).
`
`LTE Architecture
`
`[0005] The overall architecture is shown in FIG. 1 and a
`moredetailed representation ofthe E-UTRANarchitecture is
`given in FIG. 2. The E-UTRANconsists of eNodeB, provid-
`
`ing the E-UTRA user plane (PDCP/RLC/MAC/PHY)and
`control plane (RRC) protocol terminations towards the user
`equipment (UE). The eNodeB (eNB) hosts the Physical
`(PHY), Medium Access Control (MAC), Radio Link Control
`(RLC), and Packet Data Control Protocol (PDCP)layersthat
`include the functionality of user-plane header-compression
`and encryption.It also offers Radio Resource Control (RRC)
`functionality correspondingto the control plane. It performs
`many functions
`including radio resource management,
`admission control, scheduling, enforcement of negotiated
`uplink Quality of Service (QoS), cell information broadcast,
`ciphering/deciphering of user and control plane data, and
`compression/decompression of downlink/uplink user plane
`packet headers. The eNodeBs are interconnected with each
`other by means of the X2 interface.
`[0006] The eNodeBs are also connected by meansofthe S1
`interface to the EPC (Evolved Packet Core), more specifically
`to the MME (Mobility Management Entity) by meansof the
`S1-MMEand to the Serving Gateway (SGW)by meansofthe
`$1-U. The S1 interface supports a many-to-many relation
`between MMEs/Serving Gateways and eNodeBs. The SGW
`routes and forwardsuser data packets, while also acting as the
`mobility anchorfor the user plane during inter-eNodeB han-
`dovers and as the anchorfor mobility between LTE and other
`3GPPtechnologies (terminating S4 interface and relaying the
`traffic between 2G/3G systems and PDN GW). Foridle state
`user equipments, the SGW terminates the downlink data path
`and triggers paging when downlink data arrives for the user
`equipment. It manages and stores user equipment contexts,
`e.g. parameters of the IP bearer service, network internal
`routing information.It also performsreplication of the user
`traffic in case of lawful interception.
`[0007] The MMEis the key control-node for the LTE
`access-network. It is responsible for idle mode user equip-
`ment tracking and paging procedure including retransmis-
`sions. It is involved in the bearer activation/deactivation pro-
`cess andis also responsible for choosing the SGW for a user
`equipmentat the initial attach and at time of intra-LTE han-
`dover involving Core Network (CN) node relocation. It is
`responsible for authenticating the user (by interacting with
`the HSS). The Non-Access Stratum (NAS) signaling termi-
`nates at the MMEanditis also responsible for generation and
`allocation of temporary identities to user equipments. It
`checks the authorization ofthe user equipmentto camp on the
`service provider’s Public Land Mobile Network (PLMN)and
`enforces user equipment roamingrestrictions. The MMEis
`the termination point in the network for ciphering/integrity
`protection for NASsignaling and handles the security key
`management. Lawful interception of signaling is also sup-
`ported by the MME. The MMEalso provides the control
`plane function for mobility between LTE and 2G/3G access
`networks with the S3 interface terminating at the MME from
`the SGSN. The MMEalso terminates the Séa interface
`towards the home HSS for roaming user equipments.
`
`ComponentCarrier Structure in LTE (Release 8)
`
`[0008] The downlink component carrier of a 3GPP LTE
`(Release 8) is subdivided in the time-frequency domain in
`so-called sub-frames. In 3GPP LTE (Release 8) each sub-
`frameis divided into two downlink slots as shownin FIG.3,
`whereinthe first downlink slot comprises the control channel
`region (PDCCH region) within the first OFDM symbols.
`Each sub-frame consists of a give number of OFDM symbols
`in the time domain (12 or 14 OFDM symbols in 3GPP LTE
`
`20
`
`20
`
`

`

`US 2013/0039202 Al
`
`Feb. 14, 2013
`
`(Release 8)), wherein each of OFDM symbolspans over the
`entire bandwidth of the componentcarrier. The OFDM sym-
`bols are thus each consists of a number of modulation sym-
`bols transmitted on respective Nz3?”xN,*” subcarriers as
`also shown in FIG.4.
`
`[0009] Assuming a multi-carrier communication system,
`e.g. employing OFDM,as for example used in 3GPP Long
`Term Evolution (LTE), the smallest unit of resources that can
`be assigned by the scheduler is one “resource block”. A
`physical resource block is defined as Nowmb consecutive
`OFDMsymbols in the time domain and N,.*” consecutive
`subcarriers in the frequency domain as exemplified in FIG.4.
`In 3GPP LTE (Release 8), a physical resource block thus
`consists ofN,,,,,°xN,.” resource elements, corresponding
`to oneslot in the time domain and 180 kHz in the frequency
`domain (for further details on the downlink resource grid, see
`for example 3GPP TS36.211, “Evolved Universal Terrestrial
`Radio Access (E-UTRA); Physical Channels and Modulation
`(Release 8)’, version 8.9.0 or 9.0.0, section 6.2, available at
`http://www.3gpp.org and incorporated herein by reference).
`
`Layer 1/Layer 2 (L1/L2) Control Signaling
`
`In order to inform the scheduled users about their
`[0010]
`allocation status,
`transport format and other data related
`information (e.g. HAM) information, transmit power control
`(TPC) commands), L1/L2 control signaling is transmitted on
`the downlink along with the data. L1/L2 control signaling is
`multiplexed with the downlink data in a sub-frame, assuming
`that the user allocation can change from sub-frame to sub-
`frame. It should be noted that user allocation might also be
`performed on a TTI (Transmission Time Interval) basis,
`where the TTT length is a multiple ofthe sub-frames. The TTI
`length maybe fixed in a service area for all users, may be
`different for different users, or may even by dynamic for each
`user. Generally, the L1/2 control signaling needs only be
`transmitted once per TT]. The L1/L2 control signaling is
`transmitted on the Physical Downlink Control Channel (PD-
`CCH). It should be noted that in 3GPP LTE,assignments for
`uplink data transmissions, also referred to as uplink schedul-
`ing grants or uplink resource assignments, are also transmit-
`ted on the PDCCH.
`
`[0011] With respect to scheduling grants, the information
`sent on the L1/L2 control signaling may be separatedinto the
`following two categories.
`
`Shared Control
`Information
`
`Information (SCI) Carrying Cat
`
`1
`
`[0012] The shared control information part of the L1/L2
`control signaling contains informationrelated to the resource
`allocation (indication). The shared control information typi-
`cally contains the following information:
`[0013] A user identity indicating the user(s) that is/are
`allocated the resources.
`
`[0014] RB allocation information for indicating the
`resources (Resource Blocks (RBs)) on which a user(s)
`is/are allocated. The number of allocated resource
`
`blocks can be dynamic.
`if an
`[0015] The duration of assignment (optional),
`assignment over multiple sub-frames (or TTIs) is pos-
`sible.
`
`[0016] Depending on the setup of other channels and the
`setup of the Downlink Control Information (DCI)—see
`below—theshared control information may additionally con-
`
`tain information such as ACK/NACKfor uplink transmis-
`sion, uplink scheduling information, information on the DCI
`(resource, MCS, etc.).
`
`Downlink Control
`Information
`
`Information (DCI) Carrying Cat 2/3
`
`[0017] The downlink control informationpart of the L1/L2
`control signaling contains information related to the trans-
`mission format (Cat 2 information) of the data transmitted to
`a scheduled user indicated by the Cat 1 information. More-
`over, in case of using (Hybrid) ARQ as a retransmission
`protocol, the Cat 2 information carries HARQ (Cat 3) infor-
`mation. The downlink control information needs only to be
`decodedbythe user scheduled according to Cat 1. The down-
`link control information typically contains information on:
`[0018] Cat 2 information: Modulation scheme, trans-
`port-block (payload) size or coding rate, MIMO (Mul-
`tiple Input Multiple Output)-related information, etc.
`Either the transport-block (or payloadsize) or the code
`rate can be signaled.In any case these parameters can be
`calculated from each other by using the modulation
`scheme information and the resource information (num-
`ber of allocated resource blocks)
`[0019] Cat 3 information: HARQ related information,
`e.g. hybrid ARQ process number, redundancy version,
`retransmission sequence number
`[0020] Downlink control information occursin several for-
`mats that differ in overall size and also in the information
`contained in its fields. The different DCI formats that are
`currently defined for LTE Release 8/9 (GPP LTE) are
`described in detail in 3GPP TS 36.212, “Multiplexing and
`channel coding (Release 9)’, version 8.8.0 or 9.0.0, section
`5.3.3.1 (available at http:/Awww.3gpp.org and incorporated
`herein by reference).
`
`Downlink & Uplink Data Transmission
`
`[0021] Regarding downlink data transmission, L1/L2 con-
`trol signaling is transmitted on a separate physical channel
`(PDCCH), along with the downlink packet data transmission.
`This L1/L2 control signaling typically contains information
`on:
`
`[0022] The physical resource(s) on which the data is
`transmitted (e.g. subcarriers or subcarrier blocks in case
`of OFDM,codes in case of CDMA). This information
`allows the UE (receiver) to identify the resources on
`whichthe data is transmitted.
`
`[0023] When user equipment is configured to have a
`Carrier Indication Field (CIF) in the L1/L2 control sig-
`naling this information identifies the componentcarrier
`for which the specific control signaling information is
`intended. This enables assignments to be sent on one
`componentcarrier which are intended for another com-
`ponent carrier (“cross-carrier scheduling”). This other,
`cross-scheduled component carrier could be
`for
`example a PDCCH-less component carrier,
`i.e.
`the
`cross-scheduled componentcarrier does not carry any
`L1/L2 control signaling.
`[0024] The Transport Format, which is used for the trans-
`mission. This can be the transport block size of the data
`(payload size, information bits size), the MCS (Modu-
`lation and Coding Scheme) level, the Spectral Effi-
`ciency, the code rate, etc. This information (usually
`together with the resource allocation (e.g. the numberof
`
`21
`
`21
`
`

`

`US 2013/0039202 Al
`
`Feb. 14, 2013
`
`[0035] Hybrid ARQinformation:
`[0036] HARQ Process number: Tells the user equip-
`ment from which hybrid ARQ process it should pick
`the data.
`
`resource blocks assigned to the user equipment)) allows
`the user equipment(receiver)to identify the information
`bit size, the modulation scheme and the coderate in
`order to start the demodulation, the de-rate-matching
`Sequence numberor new data indicator: Tells
`[0037]
`and the decoding process. The modulation scheme may
`the user equipment to transmit a new packet or to
`be signaled explicitly.
`retransmit a packet.If soft combining is implemented
`[0025] Hybrid ARQ (HARQ)information:
`in the HARQprotocol, the sequence numberor new
`[0026] HARQ process number: Allowsthe user equip-
`data indicator together with the HARQprocess num-
`ment to identify the hybrid ARQ process on which the
`ber enables soft-combining of the transmissions for a
`data is mapped.
`protocol data unit (PDU)prior to decoding.
`[0038] Redundancy and/or constellation version:
`[0027]
`Sequence numberor new data indicator (NDIJ):
`Tells the user equipment, which hybrid ARQ redun-
`Allowsthe user equipmentto identify if the transmis-
`dancyversionto use (required for rate-matching) and/
`sion is a new packetor a retransmitted packet. If soft
`or which modulation constellation version to use (re-
`combining is implementedin the HARQ protocol, the
`quired for modulation).
`sequence numberor new data indicator together with
`[0039] UE Identity (UE ID): Tells which user equipment
`the HARQ process numberenables soft-combining of
`should transmit data. In typical implementations this
`the transmissions for a PDU prior to decoding.
`information is used to mask the CRC of the L1/L2 con-
`[0028] Redundancy and/or constellation version:
`trol signaling in order to prevent other user equipments
`to read this information.
`Tells the user equipment, which hybrid ARQ redun-
`dancyversionis used (required for de-rate-matching)
`[0040] There are several different flavors how to exactly
`and/or which modulation constellation version is used
`transmit the information pieces mentioned above in uplink
`(required for demodulation).
`and downlink data transmission. Moreover, in uplink and
`downlink, the L1/L2 control information may also contain
`[0029] UE Identity (UE ID): Tells for which user equip-
`additional information or may omit someofthe information.
`ment the L1/L2 control signaling is intended for. In
`For example:
`typical implementationsthis information is used to mask
`[0041] HARQ process number maynotbe needed,i.e. is
`the CRC ofthe L1/L2 control signaling in order to pre-
`not signaled, in case of a synchronous HARQprotocol.
`vent other user equipments to read this information.
`[0042] A redundancy and/or constellation version may
`[0030]
`To enable an uplink packet data transmission, L1/L2
`not be needed, andthusnot signaled, if Chase Combin-
`control signaling is transmitted on the downlink (PDCCH)to
`ing is used (always the same redundancy and/or constel-
`tell the user equipment about the transmission details. This
`lation version)or if the sequence of redundancy and/or
`L1/L2 control signaling typically contains information on:
`constellation versionsis pre-defined.
`[0031] The physical resource(s) on which the user equip-
`[0043]
`Power control information may be additionally
`includedin the control signaling.
`ment should transmit the data (e.g. subcarriers or sub-
`carrier blocks in case of OFDM, codes in case of
`[0044] MIMOrelated control information, such as e.g.
`pre-coding, may be additionally includedin the control
`CDMA).
`signaling.
`[0032] When user equipment is configured to have a
`[0045]
`In case of multi-codeword MIMOtransmission
`Carrier Indication Field (CIF) in the L1/L2 control sig-
`transport format and/or HARQ information for multiple
`naling this information identifies the componentcarrier
`code words maybe included.
`for which the specific control signaling information is
`[0046]
`For uplink resource assignments (on the Physical
`intended. This enables assignments to be sent on one
`Uplink Shared Channel (PUSCH)) signaled on PDCCH in
`componentcarrier which are intended for another com-
`LTE, the L1/L2 control information does not containa HARQ
`ponent carrier. This other, cross-scheduled component
`process number, since a synchronous HARQ protocol is
`carrier may be for example a PDCCH-less component
`employed for LTE uplink. The HARQprocess to be used for
`carrier, i.e. the cross-scheduled component carrier does
`an uplink transmission is given by the timing. Furthermoreit
`not carry any L1/L2 control signaling.
`should be noted that the redundancy version (RV) informa-
`[0033] L1/L2 control signaling for uplink grants is sent
`tion is jointly encoded with the transport format information,
`i.e. the RV info is embeddedin the transport format (TF)field.
`on the DL component carrier that is linked with the
`The Transport Format (TF) respectively modulation and cod-
`uplink componentcarrier or on one of the several DL
`ing scheme (MCS)field has for exampleasize of 5 bits, which
`componentcarriers, if several DL component carriers
`corresponds to 32 entries. 3 TF/MCS table entries are
`link to the same UL componentcarrier.
`reserved for indicating redundancy versions (RVs) 1, 2 or 3.
`[0034] The Transport Format, the user equipment should
`The remaining MCStable entries are used to signal the MCS
`use for the transmission. This can be the transport block
`level (TBS) implicitly indicating RVO. The size of the CRC
`field of the PDCCHis 16 bits.
`size of the data (payloadsize, informationbits size), the
`MCS(Modulation and Coding Scheme) level, the Spec-
`tral Efficiency, the coderate, etc. This information (usu-
`ally together with the resource allocation (e.g. the num-
`ber of resource blocks assignedto the user equipment))
`allowsthe user equipment(transmitter) to pick the infor-
`mationbit size, the modulation scheme and the coderate
`in orderto start the modulation, the rate-matching and
`the encoding process. In some cases the modulation
`scheme maybesignaled explicitly.
`
`For downlink assignments (PDSCH) signaled on
`[0047]
`PDCCH in LTE the Redundancy Version (RV) is signaled
`separately in a two-bit field. Furthermore the modulation
`order informationis jointly encoded with the transport format
`information. Similar to the uplink case there is 5 bit MCSfield
`signaled on PDCCH. 3 oftheentries are reserved to signal an
`explicit modulation order, providing no Transport format
`(Transport block) info. For the remaining 29 entries modula-
`tion order and Transport block size info are signaled.
`
`22
`
`22
`
`

`

`US 2013/0039202 Al
`
`Feb. 14, 2013
`
`Physical Downlink Control Channel (PDCCH)
`
`[0048] The physical downlink control channel (PDCCH)
`carries the L1/L2 control signaling,i.e. transmit power con-
`trol commands and the scheduling grants for allocating
`resources for downlink or uplink data transmission. To be
`moreprecise, the downlink control channel information(i.e.
`the DCIcontents, respectively, the L1/L2 control signaling
`information) is mapped to its corresponding physical chan-
`nel, the PDCCH. This “mapping”includes the determination
`of a CRCattachmentfor the downlink control channel infor-
`mation, which is a CRC calculated on the downlink control
`channel information being masked with an RNTI, as will
`explained below in more detail. The downlink control chan-
`nel information and its CRC attachmentare then transmitted
`onthe PDCCH(see 3GPP TS 36.212, sections 4.2 and 5.3.3).
`[0049] Each scheduling grant is defined based on Control
`Channel Elements (CCEs). Each CCE correspondsto a set of
`Resource Elements (REs). In3GPP LTE, one CCEconsists of
`9 Resource Element Groups (REGs), where one REG con-
`sists of four REs.
`
`[0050] The PDCCHis transmitted on thefirst one to three
`OFDM symbols within a sub-frame. For a downlink grant on
`the physical downlink shared channel (PDSCH), the PDCCH
`assigns a PDSCH resource for (user) data within the same
`sub-frame. The PDCCHcontrol channel region within a sub-
`frame consists of a set of CCE where the total number of
`CCEs in the control region of sub-frame is distributed
`throughout time and frequency control resource. Multiple
`CCEs can be combinedto effectively reduce the coding rate
`of the control channel. CCEs are combined in a predeter-
`mined mannerusinga tree structure to achieve different cod-
`ing rate.
`In 3GPP LTE (Release 8/9), a PDCCH can aggre-
`[0051]
`gate 1, 2, 4 or 8 CCEs. The number of CCEs available for
`control channel assignmentis a function of several factors,
`including carrier bandwidth, number of transmit antennas,
`number of OFDM symbols used for control and the CCEsize,
`etc. Multiple PDCCHscan be transmitted in a sub-frame.
`[0052] Downlink control channel information in form of
`DCItransports downlink or uplink scheduling information,
`requests for aperiodic CQI reports, or uplink powercontrol
`commands for one RNTI (Radio Network Terminal Identi-
`fier). The RNTIis a unique identifier commonly used in 3GPP
`systems like 3GPP LTE (Release 8/9) for destining data or
`informationto a specific user equipment. The RNTIis implic-
`itly included in the PDCCH by masking a CRC calculated on
`the DCI with the RNTI—the result of this operation is the
`CRC attachment mentioned above. On the user equipment
`side, if decoding of the payloadsize of data is successful, the
`user equipment detects the DCI to be destined to the user
`equipment by checking whether the CRC on the decoded
`payload data using the “unmasked” CRC (..e. after removing
`the masking using the RNTTD)is successful. The masking of
`the CRC code is for example performed by scrambling the
`CRC with the RNTI.
`
`In 3GPP LTE (Release 8) the following different
`[0053]
`DCI formats are defined:
`
`[0054] Uplink DCI formats:
`[0055]
`Format 0 used for transmission of UL SCH
`assignments
`[0056]
`Format3 is used for transmission of TPC com-
`mands for PUCCH and PUSCH with 2 bit power
`adjustments (multiple UEs are addressed)
`[0057]
`Format 3A is used for transmission of TPC
`commands for PUCCH and PUSCH with single bit
`power adjustments (multiple UEs are addressed)
`
`23
`
`[0058] Downlink DCI formats:
`[0059]
`Format 1 used for transmission of DL SCH
`assignments for SIMO operation
`[0060]
`Format 1A used for compact transmission of
`DL SCHassignments for SIMO operation
`[0061]
`Format 1B used to support closed loop single
`rank transmission with possibly contiguous resource
`allocation
`[0062]
`Format 1C is for downlink transmission of
`paging, RACH response and dynamic BCCHsched-
`uling
`Format 1D is used for compact scheduling of
`[0063]
`one PDSCHcodeword with precoding and poweroff-
`set information
`[0064]
`Format 2 is used for transmission of DL-SCH
`assignments for closed-loop MIMO operation
`[0065]
`Format 2A is used for transmission ofDL-SCH
`assignments for open-loop MIMOoperation
`For further information on the LTE physical channel
`[0066]
`structure in downlink and the PDSCH and PDCCHformat,
`see Stefania Sesia etal., “LTE—The UMTSLong Term Evo-
`lution”, Wiley & Sons Ltd., ISBN 978-0-470697 16-0, April
`2009, sections 6 and 9.
`
`Blind Decoding of PDCCHsat the User Equipment
`
`In 3GPP LTE (Release 8/9), the user equipment
`[0067]
`attempts to detect the DCI within the PDCCH usingso-called
`“blind decoding” (sometimesalso referredto as “blind detec-
`tion”. This means that there is no associated control signaling
`that would indicate the CCE aggregation size or modulation
`and coding schemefor the PDCCHssignaled in the downlink,
`but the user equipmenttests for all possible combinations of
`CCEaggregation sizes and modulation and coding schemes,
`and confirms that successful decoding of a PDCCHbased on
`the RNTI. To further limit complexity a common and dedi-
`cated search space in th