Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 1 of 20 PageID #: 181
`
`
`
`
`
`
`
`
`
`Exhibit “B”
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 2 of 20 PageID #: 182
`eSTTTTTT
`
`US008848556B2
`
`a2) United States Patent
`US 8,848,556 B2
`(0) Patent No.:
`Sep. 30, 2014
`(45) Date of Patent:
`Wu et al.
`
`(54)
`
`(75)
`
`(73)
`
`CARRIER AGGREGATION WITH POWER
`HEADROOM REPORT
`
`Inventors: Chunli Wu, Beijing (CN); Benoist
`Pierre Sebire, Tokyo (JP)
`
`Assignee: Cellular Communications Equipment
`LLC, Plano, TX (US)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 743 days.
`
`(21)
`
`Appl. No.: 13/164,266
`
`(22)
`
`Filed:
`
`Jun. 20, 2011
`
`(65)
`
`Prior Publication Data
`
`US 2011/0310760 Al
`
`Dec. 22, 2011
`
`FOREIGN PATENT DOCUMENTS
`
`JP
`WO
`WO
`WO
`
`2013-509759 A
`2010/065759 A2
`WO 2011/050921
`2010/073191 Al
`
`3/2013
`6/2010
`5/2011
`6/2011
`
`OTHER PUBLICATIONS
`
`Alcatel-Lucent Shanghai Bell et al.. 3GPP TSG-RAN WG?Meeting
`#70, R2-102879, “Considerations on PHR for CA”, May 2010, pp.
`1-3.
`Potevio, 3GPP TSG RAN WG2#70, R2-102770,“Remaining Issues
`on PHR for CA”, May 2010, pp. 1-3.
`3GPP TS 36.321 V8.8.0, 3rd Generation Partnership Project; Tech-
`nical Specification Group radio Access Network; Evolved Universal
`Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC)
`Protocol specification (Release 8), Dec. 2009, pp. 1-44.
`International Search Report application No. PCT/EP2011/060118
`dated Sep. 2, 2011.
`Japanese Office Action Notice of Reasons application No. 2013-
`515821 dated Jan. 6, 2014.
`
`Related U.S. Application Data
`
`* cited by examiner
`
`(60)
`
`Provisional application No. 61/356,867, filed on Jun.
`21, 2010.
`
`(51)
`
`Int. Cl.
`
`(52)
`
`(58)
`
`(56)
`
`(2006.01)
`(2006.01)
`
`HOAL 1/00
`HOAL 12/26
`U.S. Cl.
`USPC coececcccccccccsecestesssscecesseeesesesseeceeseeeseeees 370/252
`Field of Classification Search
`CPC vieeeccccccccccsseeetecesseees HO4L 47/10; HO4L 43/50
`USPC coececcccccccccsecestesssscecesseeesesesseeceeseeeseeees 370/252
`
`See application file for complete search history.
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`4/2011 Kimetal. wc 455/450
`2011/0092217 Al*
`2011/0243016 Al* 10/2011 Zhangetal. o.......0.. 370/252
`
`Primary Examiner — Ronald Abelson
`(74) Attorney, Agent, or Firm — Martin & Ferraro, LLP
`
`(57)
`
`ABSTRACT
`
`Methods, apparatuses, and software can be used for providing
`powerheadroom reporting in a telecommunication system. A
`method can include configuring a user equipment to send a
`power headroom report control element in uplink, wherein
`the power headroom report control element includes a bitmap
`indicating which powerheadroomreports are being reported.
`The method can further include receiving the power head-
`room report control element from the user equipment. The
`method additionally can include processing the received
`powerheadroom report control element based on the configu-
`ration of the user equipment.
`
`24 Claims, 13 Drawing Sheets
`
`an eNB configuring 610 power headroom reporting fora usar equipment
`
`using 639 a logical channelidentifier
`for Type 2 powerheadroom report,
`‘while for Type 1 the format can
`‘correspondtoa release 8 format
`a power headroom reportcan betriggered 620.
`—————______
`determining 630 which type of power headroomreport and the power
`headroom ofwhich componentcaniar(s) should be included inthe power
`indicating 640with the bitmap the type of power headroom report andthe]
`power headroomreports ofat leastone componentcartier
`indicating 637, In the bitmap, fora
`
`primary serving esl type 1 and type 2
`power headroom reports via anRbit in
`the powerheadroomreport payload
`receiving 650 the power headroom report control elementat the base
`stationfrom the
`User equipment
`processing 630 the received power headroom report control element}
`based on the configurati
`ion ofthe user equipment
`processing 631 the received power
`
`processing 633the received power
`headroom reportcontral element, whereln
`headroom report control element,
`thecontrol elementincludes the bitmap
`wherein the bitmapis exactlyeight bts
`ina media access control subheader
`processing635 the received power
`headroom reportcontol element, wherein
`the bitmap includesa first bitfora
`usarequipment power headroom report,
`a second bitfora type 1 power
`headroom report for a primaryserving cell,
`athird bitfora type 2 power headroom report
`for the primary serving cell, fourth
`through seventh bits for powerheadroom,
`reportsforfoursecondarycells and a reserved bit
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 3 of 20 PageID #: 183
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 3 of 20 PagelD#: 183
`
`Sheet 1 of 13
`
`US 8,848,556 B2
`
`U.S. Patent
`
`Sep. 30, 2014
`
`henner>UjpImMpueqWe}SAS
`PsoUBAPY-F7
`
`
`
`
`
`SJ@LUECODJUSUOCLUODZHIOZXS\
`
`
`
`
`
`
`
`UWIdISASPIOUBAPYV-1_LTJWUOJ0}SIate*DyUoUOdUIOZJoVOTES]oIseg:[oINsIy
`
`Yiprmpueq
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 4 of 20 PageID #: 184
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 4 of 20 PagelD#: 184
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 2 of 13
`
`US 8,848,556 B2
`
`Oct1
`
`LCID
`
`erRe
`
`
`
`E1/R/E/LCIDsub-header
`
`Figure2
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 5 of 20 PageID #: 185
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 5 of 20 PagelD#: 185
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 3 of 13
`
`US 8,848,556 B2
`
`
`
`Sub-headerforPHR
`
`Figure3
`
`Oct1 Oct2
`
`or
`
`OO—
`
`
`
`BitmapforPHR
`
`=O
`
`u 2 o
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 6 of 20 PageID #: 186
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 6 of 20 PagelD #: 186
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 4 of 13
`
`US 8,848,556 B2
`
`—- N
`—_/
`_/
`O
`O
`O O
`
`Cc
`—_
`O
`O
`
`rt|Ll =
`
`
`oO|;&@ OW
`
`ndependonhowmanyindividualPHRs
`
`indicatedinthethebitmap
`
`Figure4
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 7 of 20 PageID #: 187
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 7 of 20 PagelD #: 187
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 5 of 13
`
`US 8,848,556 B2
`
`- N ~)
`—_
`—_
`—_
`oO
`oO
`oO
`O OO O
`
`or
`as
`OW
`
`Cc
`—_
`oO
`O
`
`PH
`
`indicatedinthethebitmap Figure5
`ndependonhowmanyindividualPHRs
`
`
`_ £ o
`
`O.
`4)
`
`Ea
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 8 of 20 PageID #: 188
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 8 of 20 PagelD #: 188
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 6 of 13
`
`US 8,848,556 B2
`
`an eNB configuring 610 power headroom reporting for a user equipment
`
`
`
`using 639 a logical channel identifier
`for Type 2 power headroom report,
`while for Type 1 the format can
`correspond to a release 8 format
`
`a power headroom report can betriggered 620
`
`determining 630 which type of power headroom report and the power
`headroom of which component carrier(s) should be includedin the power
`
`indicating 640 with the bitmap the type of power headroom report and the
`power headroom reports of at least one componentcarrier
`
`indicating 637, in the bitmap,for a
`primary serving cell, type 1 and type 2
`power headroom reports via anRbitin
`the power headroom report payload
`
`
`
`receiving 650 the power headroom report control elementat the base
`station from the user equipment
`
`processing 630 the received power headroom report control element
`based on the configuration of the user equipment
`
`wherein the bitmap is exactly eight bits
`
`processing 631 the received power
`headroom report control element, wherein
`the control elementincludes the bitmap
`in a media access control subheader
`
`processing 633 the received power
`headroom report control element,
`
`Figure 6
`
`processing 635 the received power
`headroom report control element, wherein
`the bitmap includesa first bit for a
`user equipment power headroom report,
`a secondbit for a type 1 power
`headroom report for a primary serving cell,
`a third bit for a type 2 power headroom report
`for the primary serving cell, fourth
`through seventh bits for power headroom
`reports for four secondary cells and a reservedbit
`
`.
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 9 of 20 PageID #: 189
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 9 of 20 PagelD#: 189
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 7 of 13
`
`US 8,848,556 B2
`
`
`
`
`
`[JeoSUIAIEsAreumad
`
`Loansiy
`
`
`
`Suumedaid povodar
`
`
`
`
`
`
`
`
`aul|addysoyapy“jrodaswicoipeayiamadZBLAsodasWooupeayJamodzaddypue|adAy“{]29UOTE]SOsBqOY}O}JUSLUO]O[O.1JUCDPOdoL
`addJ,IOJJOMUSptJouUBYp[BoIsoyBGZ/SuIsNSuratasAreunideJoy‘deuniqoy)ul‘77/SuyesiputwoouspesyJomodparedaidouiOp,Sulpuss
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`JULIOJgSsvafo1&0}pUOdsaLI09Wed1eULIOYJoypeo<edylodoswoospesyJomodoy)ULIgYuR
`NYOuv
`
`
`
`up40ywoderWoorpreyJomod7odavJoy11qpip&‘TJooSuesAreurudsyqWYsIe
`
`
`HOO]xaiewonsocavnApoexooq07deuntqom¢7/,Sutedoid
`VW2Buldeunigay)[ZZSuuedaidsuneorpuldeunigq&o¢/Sutyeiodicout
`
`
`
`
`
`
`
`
`
`
`syrodarwoorprayFemodJojsyiqYUaaesYSnompyLMo;TsoSuraresAreurtid
`
`
`
`JamodqnamidinhaJasneIoy11q180Bapnyouroydeuniqayy¢z/
`¥JoypodarWoOIpesyJoMod[ad4qv1OFJIGpuosasvoder
`peolxed&UlJoJopeoyqnsBulagaresyiodalwoospesyJamodyor
`
`
`
`Jigp2vrssalvpur‘sT[a9AmepuosesNoyJOT
`
`
`
`
`podertoorpereyJomodoy}97,sulredaid
`
`
`SIOSS11]OY)UOpase‘USTIETA[O.WUOS
`LO}SIOSSLQTLSULMSBIFUOS
`
`
`yiodarwoorprayJamodveSurpuas
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 10 of 20 PageID #: 190
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 10 of 20 PagelD #: 190
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 8 of 13
`
`US 8,848,556 B2
`
`863
`
`receiver
`
`receiver|
`863
`
`<>
`
`First Apparatus
`
`810
`
`Second Apparatus
`
`820
`
`Figure 8
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 11 of 20 PageID #: 191
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 11 of 20 PagelD #: 191
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 9 of 13
`
`US 8,848,556 B2
`
`Oct1
`
`LCID
`
`Tire
`
`Figure9
`
`
`
`T/R/E/LCIDsub-header
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 12 of 20 PageID #: 192
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 12 of 20 PagelD #: 192
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 10 of 13
`
`US 8,848,556 B2
`
`®Oo
`
`O S
`
`as
`
`= v>
`
`ay
`fy
`
`Ae)
`
`O©©>©o
`
`.
`
`Y 70
`
`LL
`oO
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 13 of 20 PageID #: 193
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 13 of 20 PagelD #: 193
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 11 of 13
`
`US 8,848,556 B2
`
`Oct1
`
`N o©
`
`.>— S
`
`ame
`
`Figure11
`
`sub-header
`R/R/E/LCID
`
`Oi OO—
`
`! So
`
`d)
`Zz
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 14 of 20 PageID #: 194
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 14 of 20 PagelD#: 194
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 12 of 13
`
`US 8,848,556 B2
`
`PH#1|Oct1PRUR|R|R|oa2
`
`Figure12
`
`PH#0
`
`PH#1
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 15 of 20 PageID #: 195
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 15 of 20 PagelD #: 195
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 13 of 13
`
`US 8,848,556 B2
`
`—
`—_
`O
`O
`
`N
`—_
`O
`O
`
`oD
`_
`O
`O
`
`Figure13
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 16 of 20 PageID #: 196
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 16 of 20 PagelD #: 196
`
`US 8,848,556 B2
`
`1
`CARRIER AGGREGATION WITH POWER
`HEADROOM REPORT
`
`CROSS-REFERENCE TO RELATED
`APPLICATION
`
`The present applicationis related to and claimsthepriority
`of U.S. Provisional Patent Application No. 61/356,867 filed
`Jun. 21, 2011, the entirety of which is hereby incorporated
`herein by reference.
`
`BACKGROUND
`
`1. Field
`Carrier aggregation (CA) is atechniquethatis applicable to
`such networks as evolved universal terrestrial radio access
`(E-UTRA) networks (E-UTRAN). E-UTRANis just one
`example, as the technique may be used in other kinds of
`networks. In carrier aggregation, two or more component
`carriers (CCs) or serving cells can be aggregated in order to
`support wider transmission bandwidths up to, for example,
`100 MHz and for spectrum aggregation. In carrier aggrega-
`tion,
`it is possible to configure a user equipment (UE) to
`aggregate a different number of componentcarriers or serv-
`ing cells originating from the same enhanced node B (eNB)
`and of possibly different bandwidths in the uplink (UL) and
`the downlink (DL).
`2. Description of the Related Art
`In releases 8 and 9 of the third generation partnership
`projectGPP), without carrier aggregation, a power head-
`room report is triggered if any of the following occur, see
`3GPP specification, 36.321, which is hereby incorporated
`herein by reference: a timer called “prohibitPHR-Timer”
`expires or has expired and the path loss has changed more
`than a predetermined amount, “dl-PathlossChange”dB, since
`the transmission of a power headroom report when the user
`equipmenthas uplink resources for new transmission; a timer
`called “periodicPHR-Timer” expires; or upon configuration
`or reconfiguration ofthe power headroom reporting function-
`ality by upperlayers, which is not used to disable the function.
`The “prohibitPHR-Timer,” “periodicPHR-Timer,” and “dl-
`PathlossChange,” are configured by a radio resource control-
`ler. Similar power headroom report triggering could also be
`appliedto carrier aggregation. When powerheadroomreport-
`ing is triggered, power headroom reports onall the scheduled
`CC (or serving cells) or configured CC (or configured serving
`cells) should be reported.
`One approach to addressing power headroom reporting is
`to limit each power headroom report (PHR)to the corre-
`sponding component carrier. Although such an approach
`minimizes changes, because of potential hybrid automatic
`repeat request (HARQ)retransmission timing differences,
`the eNB cannot obtain a power headroom report from all
`componentcarriers at the same time. Furthermore, onelogi-
`cal channelidentifier (LCID)is used per reported component
`carrier (or serving cell), increasing overhead.
`Anotheroptionis to allow a cross carrier power headroom
`report with a cross carrier indicator for each power headroom
`report to indicate which componentcarrier(or serving cell) it
`is referring to. This approach requires one media access con-
`trol (MAC)sub-header for each individual power headroom
`report or a “length”field to indicate the length for such vari-
`able size payload. Furthermore, there are only 2 R bits in the
`power headroom report MAC control element (CE) whichis
`not enoughto indicate 5 componentcarriers(or serving cells).
`
`SUMMARY
`
`A method,in certain embodiments, includes configuring a
`user equipment to send a power headroom report control
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`55
`
`60
`
`65
`
`2
`element in uplink. The power headroom report control ele-
`ment includes a bitmap indicating which power headroom
`reports are being reported. The method further includes
`receiving the power headroom report control element from
`the user equipment. The method additionally includes pro-
`cessing the received power headroom report control element
`based on the configuration of the user equipment.
`In another embodiment, a method includes preparing a
`power headroom report control element, based on a trigger
`configured by a base station. The trigger determines when a
`powerheadroom report control elementis to be sent in uplink.
`Preparing the control element includes incorporating a bit-
`map indicating which power headroom reports are being
`reported. The method further includes sending the prepared
`powerheadroom report control element to the basestation.
`A non-transitory computer readable medium, in certain
`further embodiments, is encoded with a computer program
`that, when executed in hardware, causes the hardware to
`perform a process. The process includes configuring a user
`equipmentto send a power headroom report control element
`in uplink. The power headroom report control element
`includes a bitmap indicating which power headroom reports
`are being reported. The process further includes receiving the
`power headroom report control element from the user equip-
`ment. The process additionally includes processing the
`received power headroom report control] element based on the
`configuration of the user equipment.
`A non-transitory computer readable medium, in another
`embodiment, is encoded with a computer program that, when
`executed in hardware, causes the hardware to perform a pro-
`cess. The process can also include preparing a power head-
`room report control element, based on a trigger configured by
`a base station. The trigger determines when a power head-
`room report control elementis to be sent in uplink. Preparing
`the control element includes incorporating a bitmap indicat-
`ing which power headroom reports are being reported. The
`process further includes sending the prepared power head-
`room report control elementto the base station.
`In certain embodiments, an apparatus includesat least one
`processor and at least one memory including computer pro-
`gram code. The at least one memory and computer program
`code are configured to, with at least one processor, cause the
`apparatus at least to configure a user equipment to send a
`power headroom report control element in uplink. The power
`headroom report control elementincludes a bitmapindicating
`which power headroom reports are being reported. The at
`least one memory and computer program code are also con-
`figured to, with at least one processor, cause the apparatus at
`least to receive the power headroom report control element
`from the user equipment. The at least one memory and com-
`puter program code are further configured to, with at least one
`processor, cause the apparatusat least to process the received
`powerheadroom report control element based on the configu-
`ration of the user equipment.
`An apparatus, in another embodiment,includesat least one
`processor and at least one memory including computer pro-
`gram code. The at least one memory and computer program
`code are configured to, with at least one processor, cause the
`apparatusat least to prepare a power headroomreport control
`element, based on a trigger configured by a basestation. The
`trigger determines when a power headroom report control
`elementis to be sent in uplink. The at least one memory and
`computer program code are also configured to, with at least
`one processor, cause the apparatus at least to prepare the
`control element by incorporating a bitmap indicating which
`power headroom reports are being reported. Theat least one
`memory and computer program codeare also configuredto,
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 17 of 20 PageID #: 197
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 17 of 20 PagelD #: 197
`
`US 8,848,556 B2
`
`3
`with at least one processor, cause the apparatusat least to send
`the prepared power headroom report control element to the
`basestation.
`
`In certain embodiments, an apparatus includes configuring
`means for configuring a user equipment to send a power
`headroom report control element in uplink. The power head-
`room report control element includes a bitmap indicating
`which powerheadroomreports are being reported. The appa-
`ratus also includes receiving means for receiving the power
`headroom report control element from the user equipment.
`The apparatus further includes processing meansfor process-
`ing the received power headroom report control element
`based on the configuration of the user equipment.
`An apparatus, according to certain embodiments, includes
`preparing meansfor preparing a power headroom report con-
`trol element, based on a trigger configured by a basestation.
`The trigger determines when a power headroom report con-
`trol element is to be sent in uplink. Preparing the control
`element includes incorporating a bitmap indicating which
`power headroom reports are being reported. The apparatus
`also includes sending means for sending the prepared power
`headroom report control elementto the base station.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`reference
`For proper understanding of the invention,
`should be made to the accompanying drawings, wherein:
`FIG.1 illustrates carrier aggregation.
`FIG.2 illustrates an E1/R/LCID sub-header.
`
`FIG.3 illustrates a sub-header for power headroom report-
`ing.
`FIG.4 illustrates individual power headroom reports for
`each componentcarrier.
`FIG.5 illustrates a power headroom report payload includ-
`ing a bitmap for power headroom reporting as the first octet.
`FIG.6 illustrates a method according to certain embodi-
`ments of the present invention.
`FIG.7 illustrates a method according to certain embodi-
`ments of the present invention.
`FIG.8 illustrates a system according to certain embodi-
`ments of the present invention.
`FIG.9 illustrates a format in which a single bit is used to
`indicate whether Type 1 power headroom report or Type 2
`powerheadroom report is being used.
`FIG. 10 illustrates a format in which Type 1 and Type 2
`power headroom reports are indicated via the R bit in the
`powerheadroom report payload for PCell.
`FIG.11 illustrates a format in which a new logical channel
`identifier is used for a Type 2 power headroom report, while
`for Type 1 the format can correspondto a release 8 format.
`FIG.12 illustrates a format in which each individual power
`headroom report is 6 bits, with R bits for byte alignment when
`the payloadis not byte aligned.
`FIG.13 illustrates a format in which each individual power
`headroom report is 6 bits, without R bits for byte alignment
`whenthe payloadis byte aligned.
`
`DETAILED DESCRIPTION OF THE PREFERRED
`
`EMBODIMENT(S)
`
`Certain embodimentsofthe present invention report power
`headroom using a new power headroom report MAC control
`element which canstart with a bitmap indicating which power
`headroom reports are being reported. Each bit of the bitmap
`can be linked to a particular power headroom report (e.g.
`primary serving cell (PCell) PHR, secondary serving cell
`(SCell), such as SCell1, PHR#) and theorder in whichthe bits
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`are read in the bitmap also defines the order in which the
`power headroom reports follow the bitmap. The bitmap can,
`therefore, indicate the size of the power headroom report
`MACcontrol element. Thus, the control element can address
`variable power headroom report size and can avoid using one
`sub-headerper individual power headroom report.
`It may be beneficial to limit power headroom reporting to
`the serving cells that are scheduled to reduce overhead and
`simplify power headroom evaluation from user equipment
`side. Also, it may be beneficial for the eNB to obtain, at the
`same time, power headroom reports for all the serving cells
`scheduled. Because of potential hybrid automatic repeat
`request (HARQ)retransmission timing differences, schedul-
`ing all componentcarriers with new transmission in the same
`transmission time interval (TTI) maynotbefeasible.
`Theprinciple of carrier aggregationis illustrated in FIG.1.
`Third generation partnership project (GPP)release 8 (Rel-8)
`user equipment maybe served by a stand-alone component
`carrieror serving cell, while release 10 (Rel-10) terminals can
`be configured to receive or transmit simultaneously on mul-
`tiple componentcarriers or remote serving cells in the same
`transmission time interval (TTT).
`When carrier aggregation is configured, the user equip-
`ment only has one radio resource control (RRC) connection
`with the network. At RRC connection establishment/re-es-
`tablishment, one serving cell provides the security input and
`the non-access stratum (NAS) mobility information (e.g. tim-
`ing advance information (TAI)) similarly as in Rel-8/9. The
`security input can include one E-UTRANcell global identi-
`fier (ECGI),one physical cell identity (PCI) and one absolute
`radio-frequency channel number (ARFCN).
`This cell that provides the security input and the NAS
`mobility informationis referredto as the primary serving cell
`(PCell). In the downlink, the carrier corresponding to the
`PCell is the downlink (DL) primary componentcarrier (DL
`PCC)while in the uplink it is the uplink (UL) primary com-
`ponent carrier (UL PCC).
`Depending on user equipment capabilities, secondary
`serving cells (SCells) can be configured to form, together
`with the PCell, a set of serving cells. In the downlink, the
`carrier corresponding to an SCell is a downlink secondary
`component carrier (DL SCC) while in the uplink it is an
`uplink secondary componentcarrier (UL SCC).
`In view of the above, the configured set of serving cells for
`a user equipment may always include one PCell and one or
`more SCells. For each SCell, the usage ofuplink resources by
`the user equipment in addition to the downlink ones can be
`configurable. The number of DL SCCs configured can,there-
`fore, be set always to be larger or equal to the number of UL
`SCCsand, thus, no SCell can be configured for usage of
`uplink resources only. Additionally, the number of serving
`cells that can be configured can depend upon the aggregation
`capability of the user equipment.
`Furthermore,to assist the scheduler, the eNB can configure
`user equipment to send buffer status reports (BSRs) and
`power headroom reports in uplink. BSR can indicate the
`amountof data the user equipmenthasavailable for transmis-
`sion. A power headroom report can provide the eNB with
`information about the difference between the nominal user
`
`equipment maximum transmit power and the estimated
`powerfor uplink synchronization channel (UL-SCH)trans-
`mission.
`A powerheadroom report can be sent by the user equip-
`ment in uplink in the form of PHR media access control
`(MAC) control elements in which the “power headroom”
`field indicates the power headroom level. In the context of
`carrier aggregation, per componentcarrier (or serving cell)
`
`

`

`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 18 of 20 PageID #: 198
`Case 6:14-cv-00982-KNM Document 28-2 Filed 04/16/15 Page 18 of 20 PagelD #: 198
`
`US 8,848,556 B2
`
`5
`power headroom reporting can be used, and, optionally, per
`user equipment power headroom reporting can also be used
`on top ofthose.
`As mentioned above, a new power headroom report MAC
`control element can be provided, which starts with a bitmap
`indicating which PHRsare being reported. Each bit of the
`bitmap can be linked to a particular power headroom report
`(e.g. PCell PHR, SCell1 PHR .. .) and the order in which the
`bits are read in the bitmap can also define the order in which
`the power headroom reports follow the bitmap. The bitmap
`therefore indicates the size of the power headroom report
`MACcontrol element.
`
`The bit in the bitmap can indicate whether a power head-
`room (PH)fieldis being reported. For example, a bit set to “1”
`can indicate that a power headroom field for a corresponding
`secondary cell is being reported. The bit set to “0”, on the
`other hand, can indicate that a power headroom field for a
`corresponding secondary cell is not being reported. Thus, for
`example if the bit for SCell_i is set to zero, the power head-
`room field for the secondary cell with secondary cell index i
`is not being reported. Alternatively, the opposite convention
`can be used, wherein “1” indicates that a report is not being
`provided and “0”indicates that a report is being provided.
`For example, the bitmap can be 8 bits long and can be
`organized as follows. A first bit can be used for a user equip-
`ment power headroom report (UE-PHR). Theuse of thefirst
`bit for UE-PHR is, of course, an optional item. In some
`embodiments, there may be no need for such a PHRin addi-
`tion to per-CC PHR.
`A secondbit can be used for Type 1 PHR for PCell. A third
`bit can be used for Type 2 PHR for PCell. Fourth through
`seventh bits can be for PHR of SCell1, SCell2, SCell3, and
`SCell4. There can also be one reservedbit. In other embodi-
`ments, suchasifthefirst bit is not used for UE-PHR,there can
`be more than onereservedbit.
`
`Type 1 and Type 2 power headroom reports may employ
`the following definition. Their presence can be indicated to
`the eNB. Type 1 power headroom report can be computedas:
`P_cmax,c minus PUSCH power. Type 2 power headroom
`report can be computed as: P_cmax,c minus PUCCH power
`minus PUSCH power
`There are some additional considerations as well. For
`
`PCell, if in a TTI there can be either only Type 1 or Type 2
`PHR,onebit in the bitmap can be usedto indicate the type.
`Still another possibility for PCell is to indicate Type 1 and
`Type 2 power headroom reports via the R bit in the MAC
`sub-header for PCell. This formatis illustrated in FIG.9. Still
`
`another possibility for PCell is to indicate Type 1 and Type 2
`power headroomreports via the R bit in the power headroom
`report payload for PCell. This formatis illustrated in FIG. 10.
`A further alternativeis to use a new logical channelidentifier
`for Type 2 power headroom report, while for Type 1 the
`format can correspondto a release 8 format. Then, if thereis
`only a power headroom report for PCell included, the bitmap
`byte is not needed. This formatis illustrated in FIG. 11.
`The order of SCells can be according the order in which
`they are configured or according to a cell index or component
`carrier index. If only a power headroom report for one serving
`cell is needed in a TTI, a simplified format could be used.
`The new power headroom report format could use a new
`logical channelidentifier (LCID) or makeuseof one of the R
`bits ofthe subheaderto indicate the occurrence of the bitmap.
`This bit is denoted E1 in FIG. 2. The bitmap could either
`follow the MAC Sub-headerfor a power headroom report, or
`it can be as the first byte of the power headroom report
`payload. FIG.3 illustrates the bitmap for the power headroom
`report has a sub-header.
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`Theindividual power headroom report for each component
`carrier, each type or per UE PHR can resemble that found in
`Release 8 or Release 9: 1 byte for each component carrier
`with 2 R bits+6 bits PH. This approachis illustrated in FIG.4.
`Alternatively, each individual power headroom report can be
`6 bits, with R bits for byte alignment whenthe payloadis not
`byte aligned, as shown in FIG. 12; whenit is byte aligned, no
`R bit needed, as shown in FIG. 13. FIG. 5 showsan alternative
`embodiment in which the first octet of the payload is the
`bitmap for the power headroom report.
`Various embodimentsofthe present invention may provide
`advantageouseffects. For example, in certain embodiments,
`there may be no needto have a separate MAC sub-header for
`each individual power headroom report (different type of
`power headroom report, per componentcarrier power head-
`room report for each component carrier and per-UE power
`headroom report). Thus, overhead may be reduced. Addition-
`ally, issues arising from uncertainty of variable size may be
`avoided or handled. Furthermore, certain embodiments ofthe
`present invention may clearly and efficiently indicate which
`componentcarriers have power headroom report included,
`without a cross-CCindicator for each individual powerhead-
`room report separately.
`FIG.6 illustrates a method according to certain embodi-
`ments of the present invention. The method can include an
`eNBconfiguring 610 power headroom reporting for a user
`equipment. In the method, a power headroom report can be
`triggered 620. The method can additionally include determin-
`ing 630 which type of power headroom report and the power
`headroom of which componentcarrier(s) should be included
`in the power headroom report MAC control element. The
`method can also include indicating 640 with the bitmap the
`type of power headroom report and the power headroom
`reports of at least one componentcarrier.
`The method can include receiving 650 the power headroom
`report control elementat the basestation from the user equip-
`ment. The method additionally includes processing 630 the
`received power headroom report control] element based on the
`configuration of the user equipment.
`The method can include processing 631 the received power
`headroom report control element, wherein the control ele-
`mentincludes the bitmap in a media access control subheader
`or in a payload. The methodcan also include processing 633
`the received power headroom report control element, wherein
`the bitmap is exactly eight bits. The method can also include
`processing 635 the received power headroom report control
`element, wherein the bitmap includesa first bit for a user
`equipment power headroom report, a secondbit for a type 1
`power headroom report for a primary serving cell, a third bit
`for a type 2 power headroom report for the primary serving
`cell, fourth through seventh bits for power headroom reports
`for four secondary cells, anda reserved bit. Because the eight
`bits can include a reserved bit, the power headroom report
`control element can alternatively be said to be exactly seven
`bits in length.
`The method can further include indicating 637,in the bit-
`map, for a primary serving cell, type 1 and type 2 power
`headroom reports via an R bit in the power headroom report
`payload for primary serving cell. The me