throbber
Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 1 of 20 PageID #: 36
`
`
`
`
`
`
`
`
`
`Exhibit “B”
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 2 of 20 PageID #: 37
`111111
`1111111111111111111111111111111111111111111111111111111111111
`US008848556B2
`
`c12) United States Patent
`Wu et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 8,848,556 B2
`Sep.30,2014
`
`(54) CARRIER AGGREGATION WITH POWER
`HEADROOM REPORT
`
`(75)
`
`Inventors: Chunli Wu, Beijing (CN); Benoist
`Pierre Sebire, Tokyo (JP)
`
`(73) Assignee: Cellular Communications Equipment
`LLC, Plano, TX (US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`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/0310760Al
`
`Dec. 22, 2011
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 61/356,867, filed on Jun.
`21, 2010.
`
`(51)
`
`(52)
`
`(58)
`
`(2006.01)
`(2006.01)
`
`Int. Cl.
`H04L 1100
`H04L 12126
`U.S. Cl.
`USPC .......................................................... 370/252
`Field of Classification Search
`CPC ................................ H04L 47/10; H04L 43/50
`USPC .......................................................... 370/252
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2011/0092217 A1 * 4/2011 Kim eta!. ..................... 455/450
`2011/0243016 A1 * 10/2011 Zhang et al ................... 370/252
`
`FOREIGN PATENT DOCUMENTS
`
`JP
`wo
`wo
`wo
`
`2013-509759 A
`2010/065759 A2
`wo 20111050921
`2010/073191 A1
`
`3/2013
`6/2010
`5/2011
`6/2011
`
`OTHER PUBLICATIONS
`
`Alcatel-Lucent Shanghai Bell et al., 3GPP TSG-RANWG2 Meeting
`#70, Rl-102879, "Considerations on PHR for CA", May 2010, pp.
`1-3.
`Potevio, 3GPP TSG RANWG2 #70, Rl-102770, "Remaining Issues
`on PHR for CA", May 2010, pp. 1-3.
`3GPP TS 36.321 V8.8.0, 3rd Generation Partnership Project; Tech(cid:173)
`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.
`* cited by examiner
`
`Primary Examiner- Ronald Abelson
`(74) Attorney, Agent, or Firm- Martin & Ferraro, LLP
`
`ABSTRACT
`(57)
`Methods, apparatuses, and software can be used for providing
`power headroom 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 power headroom reports are being reported.
`The method can further include receiving the power head(cid:173)
`room report control element from the user equipment. The
`method additionally can include processing the received
`power headroom report control element based on the configu(cid:173)
`ration of the user equipment.
`
`24 Claims, 13 Drawing Sheets
`
`processlng635thereceivedpower
`headroomre!XIrloontrolelemen~whereln
`thabitmaplncludesailrstbltiora
`userequ1pmentpowerheadroomre!Xlrt,
`asecondbitforatype1power
`headroomreportforapnmaryservmgcell,
`athirdbitforatype2powerhsadroomraport
`forthepnmaryserv1ngcell,iourth
`throughseventhbitsforpowerheadroom
`reportsforiourseoondarycellsandareservedbit
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 3 of 20 PageID #: 38
`
`L TE-Advanced system bandwidth
`
`~
`00
`•
`~
`~
`~
`
`~ = ~
`
`rFJ
`('D
`'?
`
`(.H
`~0
`N
`
`0 ....
`
`.j;o.
`
`5 x 20 MHz component carriers
`
`i
`i
`I
`
`Figure 1: Basic illustration of Component Carriers to form LTE-Advanced system
`bandwidth
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`....
`0 .....
`....
`
`(.H
`
`d
`rJl
`00
`Oo
`~
`00 u. u.
`0'1 = N
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 4 of 20 PageID #: 39
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 2 of 13
`
`US 8,848,556 B2
`
`L..
`Cl)
`
`"'C ro
`Cl)
`..c
`I ..c
`~ en
`0 -()
`.....J
`............ w
`............ 0::
`,....
`w
`
`............
`
`0 -()
`
`.....J
`
`w
`
`0::
`
`,....
`w
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 5 of 20 PageID #: 40
`
`U.S. Patent
`
`Sep. 30, 2014
`
`Sheet 3 of 13
`
`US 8,848,556 B2
`
`~ C\.1
`+-'
`+-'
`(.)
`(.)
`0
`0
`
`0:::
`I
`c..
`s.....
`~ 0:::
`I
`0
`-
`c..
`(.)
`....J ~
`c..
`ca
`E +-' ·-
`
`s.....
`
`w
`
`(0
`
`0:::
`
`~
`
`~
`~
`~
`~
`
`~
`~
`Q.)
`~
`~
`Q.)
`~
`I
`~
`rfl
`
`~
`Q)
`~
`;::::$
`......
`b1)
`~
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 6 of 20 PageID #: 41
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 4 of 13
`
`US 8,848,556 B2
`
`+-'
`(.)
`0
`
`c
`+-'
`(.)
`0
`
`I c..
`
`I c..
`
`I c..
`
`• • •
`
`0::
`
`0::
`
`0::
`
`0::
`
`roc..
`:::J ca
`:2 E
`:c.o
`>+-~
`c
`(I)
`~£
`c
`(I)
`CO..c E..,
`c ·-
`3=
`0 ..c
`"'C
`(I)
`ca
`+-'
`c
`(.) ·-
`0
`"'C"'C
`c c
`(I) · -
`c.. en
`mC::
`"'CI
`cC..
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 7 of 20 PageID #: 42
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`Bitmap for PHR
`
`R R
`
`R R
`
`I R I R I
`
`PH
`
`PH
`
`PH
`
`• • •
`
`Oct 1
`
`Oct2
`
`Oct3
`
`I Oct n
`
`n depend on how many individual
`PHRs indicated in the the bitmap
`
`Figure 5
`
`~
`00
`•
`~
`~
`~
`
`~ = ~
`
`rFJ
`('D
`'?
`
`(.H
`~0
`N
`
`0 ....
`
`.j;o.
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`Ul
`0 .....
`....
`
`(.H
`
`d
`rJl
`00
`Oo
`~
`00 u. u.
`0'1 = N
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 8 of 20 PageID #: 43
`
`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
`
`1--
`
`a power headroom report can be triggered 620
`
`determining 630 which type of power headroom report and the power
`headroom of which component carrier(s) should be included in the power
`
`indicating 640 with the bitmap the type of power headroom report and the
`power headroom reports of at least one component carrier
`
`indicating 637, in the bitmap, for a
`primary serving cell, type 1 and type 2
`power headroom reports via an R bit in
`the power headroom report payload
`
`I -
`
`receiving 650 the power headroom report control element at the base
`station from the user equipment
`
`processing 630 the received power headroom report control element
`based on the configuration of the user equipment
`
`processing 631 the received power
`headroom report control element, wherein
`the control element includes the bitmap
`in a media access control subheader
`
`I -r--
`
`processing 633 the received power
`headroom report control element,
`wherein the bitmap is exactly eight bits
`
`processing 635 the received power
`headroom report control element, wherein
`the bitmap includes a first bit for a
`user equipment power headroom report,
`a second bit 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 reserved bit
`
`I -
`
`Figure 6
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 9 of 20 PageID #: 44
`
`an eNB configuring 710 triggers for
`sending a power headroom report
`
`preparing 720 the power headroom report
`control element, based on the triggers
`
`incorporating 730 a bitmap indicating
`which power headroom reports are being
`reported
`
`preparing 721 the bitmap in a MAC
`subheader or in a payload
`
`preparing 723 the bitmap to be exactly
`eight bits
`
`piepaiing 725 the bitmap to indude a [u-sl bit for a user e4uipment power
`headroom report, a second bit ±Or a type 1 power headroom report ±Or a
`primary serving cell. a third bit for a type 2 power headroom report for the
`primary serving eel~ fourth through seventh bits for power headroom reports
`±Or ±Our secondary cells, and a reserved bit
`
`I
`sending 740 the prepared power headroom
`report control element to the base station
`
`indicating 727, in the bitmap, for a primary serving
`cell, type 1 and type 2 power headroom reports via
`an R bit in the power headroom report payload for
`primarv serving cell
`
`I
`using 729 a logical channel identifier for Type"
`2 power headroom report, while for Type 1 the
`fonnat can correspond to a release 8 fonnat
`
`Figure 7
`
`~
`00
`•
`~
`~
`~
`
`~ = ~
`
`rFJ
`('D
`'?
`
`(.H
`~0
`N
`
`0 ....
`
`.j;o.
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`-....l
`0 .....
`....
`
`(.H
`
`d
`rJl
`00
`Oo
`~
`00 u. u.
`0'1 = N
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 10 of 20 PageID #: 45
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 8 of 13
`
`US 8,848,556 B2
`
`'~V--t...870
`
`880
`
`\/--t...870
`
`trans-
`receiver
`863 mitter
`867
`
`-
`
`trans-
`receiver
`863 mitter
`-
`867
`
`\ 860 Transceiver
`
`~830 0
`
`840
`
`First Apparatus
`
`1
`(
`810
`
`'860 Transceiver
`·-------.,
`
`830
`
`I
`
`~840~ 1 850
`
`:
`
`~ __ :
`
`I
`(
`820
`
`Second Apparatus
`
`Figure 8
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 11 of 20 PageID #: 46
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 9 of 13
`
`US 8,848,556 B2
`
`0',
`C)
`;.....
`;::::$
`
`bJ) ·-
`
`~
`
`'-
`(])
`"'C
`co
`(])
`..c
`I
`..c
`:::J
`en
`
`0 -0
`.....J
`........... w
`(2
`...........
`I-
`
`0
`
`_J
`
`-0
`
`w
`
`0::
`
`I-
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 12 of 20 PageID #: 47
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 10 of 13
`
`US 8,848,556 B2
`
`Q)
`
`() a..
`s....
`Q
`"'C co
`0
`~ co a.
`0::
`I a..
`
`I a..
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 13 of 20 PageID #: 48
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 11 of 13
`
`US 8,848,556 B2
`
`N
`CD a.
`~
`I-
`L..
`0
`'+-
`
`0 -(.)
`
`_J
`~
`CD z
`
`w
`
`0::
`
`0::
`
`L..
`CD
`"'C ro
`CD
`..c:
`I ..c
`~ en
`0 -(.)
`.......... w
`..........
`0::
`..........
`0::
`
`_J
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 14 of 20 PageID #: 49
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 12 of 13
`
`US 8,848,556 B2
`
`~ C\1
`+-'
`+-'
`(.)
`(.)
`
`0
`
`0
`
`~ 0::
`=1:1::
`I a..
`
`0::
`
`0::
`
`0::
`
`0
`=1:1::
`
`I a.. ~
`I a..
`
`=1:1::
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 15 of 20 PageID #: 50
`
`U.S. Patent
`
`Sep.30,2014
`
`Sheet 13 of 13
`
`US 8,848,556 B2
`
`N
`+""'
`u
`0
`
`N
`::tt
`I a...
`
`~
`
`::tt
`I a...
`
`0
`::tt
`I a... ~
`::tt
`I a...
`
`+""'
`
`u
`0
`
`(V)
`::tt
`I a...
`
`N
`::tt
`I a...
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 16 of 20 PageID #: 51
`
`US 8,848,556 B2
`
`1
`CARRIER AGGREGATION WITH POWER
`HEADROOM REPORT
`
`CROSS-REFERENCE TO RELATED
`APPLICATION
`
`The present application is related to and claims the priority
`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
`
`2
`element in uplink. The power headroom report control ele(cid:173)
`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(cid:173)
`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
`10 configured by a base station. The trigger determines when a
`power headroom report control element is to be sent in uplink.
`Preparing the control element includes incorporating a bit(cid:173)
`map indicating which power headroom reports are being
`reported. The method further includes sending the prepared
`15 power headroom report control element to the base station.
`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
`20 equipment to 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-
`25 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
`30 executed in hardware, causes the hardware to perform a pro(cid:173)
`cess. The process can also include preparing a power head(cid:173)
`room report control element, based on a trigger configured by
`a base station. The trigger determines when a power head(cid:173)
`room report control element is to be sent in uplink. Preparing
`35 the control element includes incorporating a bitmap indicat(cid:173)
`ing which power headroom reports are being reported. The
`process further includes sending the prepared power head(cid:173)
`room report control element to the base station.
`In certain embodiments, an apparatus includes at least one
`40 processor and at least one memory including computer pro(cid:173)
`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
`45 headroom report control element includes a bitmap indicating
`which power headroom reports are being reported. The at
`least one memory and computer program code are also con(cid:173)
`figured to, with at least one processor, cause the apparatus at
`least to receive the power headroom report control element
`50 from the user equipment. The at least one memory and com(cid:173)
`puter program code are further configured to, with at least one
`processor, cause the apparatus at least to process the received
`power headroom report control element based on the configu-
`ration of the user equipment.
`An apparatus, in another embodiment, includes at least one
`processor and at least one memory including computer pro(cid:173)
`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 prepare a power headroom report control
`60 element, based on a trigger configured by a base station. The
`trigger determines when a power headroom report control
`element is 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
`65 control element by incorporating a bitmap indicating which
`power headroom reports are being reported. The at least one
`memory and computer program code are also configured to,
`
`1. Field
`Carrier aggregation (CA) is a technique that is applicable to
`such networks as evolved universal terrestrial radio access
`(E-UTRA) networks (E-UTRAN). E-UTRAN is 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(cid:173)
`tion, it is possible to configure a user equipment (UE) to
`aggregate a different number of component carriers or serv(cid:173)
`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
`project (3GPP), without carrier aggregation, a power head(cid:173)
`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
`equipment has uplink resources for new transmission; a timer
`called "periodicPHR-Timer" expires; or upon configuration
`or reconfiguration of the power headroom reporting function(cid:173)
`ality by upper layers, which is not used to disable the function.
`The "prohibitPHR-Timer," "periodicPHR-Timer," and "dl(cid:173)
`PathlossChange," are configured by a radio resource control(cid:173)
`ler. Similar power headroom report triggering could also be
`applied to carrier aggregation. When power headroom report(cid:173)
`ing is triggered, power headroom reports on all 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(cid:173)
`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
`component carriers at the same time. Furthermore, one logi(cid:173)
`cal channel identifier (LCID) is used per reported component
`carrier (or serving cell), increasing overhead.
`Another option is to allow a cross carrier power headroom
`report with a cross carrier indicator for each power headroom 55
`report to indicate which component carrier (or serving cell) it
`is referring to. This approach requires one media access con(cid:173)
`trol (MAC) sub-header for each individual power headroom
`report or a "length" field to indicate the length for such vari(cid:173)
`able size payload. Furthermore, there are only 2 R bits in the
`power headroom report MAC control element (CE) which is
`not enough to indicate 5 component carriers (or serving cells).
`
`SUMMARY
`
`A method, in certain embodiments, includes configuring a
`user equipment to send a power headroom report control
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 17 of 20 PageID #: 52
`
`US 8,848,556 B2
`
`3
`with at least one processor, cause the apparatus at least to send
`the prepared power headroom report control element to the
`base station.
`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(cid:173)
`room report control element includes a bitmap indicating
`which power headroom reports are being reported. The appa(cid:173)
`ratus also includes receiving means for receiving the power
`headroom report control element from the user equipment.
`The apparatus further includes processing means for process(cid:173)
`ing the received power headroom report control element
`based on the configuration of the user equipment.
`An apparatus, according to certain embodiments, includes
`preparing means for preparing a power headroom report con(cid:173)
`trol element, based on a trigger configured by a base station.
`The trigger determines when a power headroom report con(cid:173)
`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 element to the base station.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`For proper understanding of the invention, reference
`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(cid:173)
`ing.
`FIG. 4 illustrates individual power headroom reports for
`each component carrier.
`FIG. 5 illustrates a power headroom report payload includ(cid:173)
`ing a bitmap for power headroom reporting as the first octet.
`FIG. 6 illustrates a method according to certain embodi(cid:173)
`ments of the present invention.
`FIG. 7 illustrates a method according to certain embodi(cid:173)
`ments of the present invention.
`FIG. 8 illustrates a system according to certain embodi(cid:173)
`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
`power headroom 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
`power headroom 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 correspond to 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 payload is not byte aligned.
`FIG. 13 illustrates a format in which each individual power
`headroom report is 6 bits, without R bits for byte alignment
`when the payload is byte aligned.
`
`DETAILED DESCRIPTION OF THE PREFERRED
`EMBODIMENT(S)
`
`Certain embodiments of the present invention report power
`headroom using a new power headroom report MAC control
`element which can start 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 SCelll, PHR#) and the order in which the bits
`
`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
`MAC control element. Thus, the control element can address
`variable power headroom report size and can avoid using one
`sub-header per 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
`10 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(cid:173)
`ing all component carriers with new transmission in the same
`15 transmission time interval (TTl) may not be feasible.
`The principle of carrier aggregation is illustrated in FIG. 1.
`Third generation partnership project (3GPP) release 8 (Rel-8)
`user equipment may be served by a stand-alone component
`carrier or serving cell, while release 10 (Rel-1 0) terminals can
`20 be configured to receive or transmit simultaneously on mul(cid:173)
`tiple component carriers or remote serving cells in the same
`transmission time interval (TTl).
`When carrier aggregation is configured, the user equip(cid:173)
`ment only has one radio resource control (RRC) connection
`25 with the network. At RRC connection establishment/re-es(cid:173)
`tablishment, one serving cell provides the security input and
`the non-access stratum (NAS) mobility information (e.g. tim(cid:173)
`ing advance information (TAl)) similarly as in Rel-8/9. The
`security input can include one E-UTRAN cell global identi-
`30 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 information is referred to as the primary serving cell
`(PCell). In the downlink, the carrier corresponding to the
`35 PCell is the downlink (DL) primary component carrier (DL
`PCC) while in the uplink it is the uplink (UL) primary com(cid:173)
`ponent carrier (UL PCC).
`Depending on user equipment capabilities, secondary
`serving cells (SCells) can be configured to form, together
`40 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 component carrier (UL SCC).
`In view of the above, the configured set of serving cells for
`45 a user equipment may always include one PCell and one or
`more SCells. For each SCell, the usage of uplink resources by
`the user equipment in addition to the downlink ones can be
`configurable. The number ofDL SCCs configured can, there(cid:173)
`fore, be set always to be larger or equal to the number ofUL
`50 SCCs and, thus, no SCell can be configured for usage of
`uplink resources only. Additionally, the nnmber 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
`55 user equipment to send buffer status reports (BSRs) and
`power headroom reports in uplink. BSR can indicate the
`amount of data the user equipment has available for transmis(cid:173)
`sion. A power headroom report can provide the eNB with
`information about the difference between the nominal user
`60 equipment maximnm transmit power and the estimated
`power for uplink synchronization channel (UL-SCH) trans(cid:173)
`miSSIOn.
`A power headroom report can be sent by the user equip(cid:173)
`ment in uplink in the form of PHR media access control
`65 (MAC) control elements in which the "power headroom"
`field indicates the power headroom level. In the context of
`carrier aggregation, per component carrier (or serving cell)
`
`

`

`Case 6:14-cv-00982-KNM Document 1-3 Filed 12/19/14 Page 18 of 20 PageID #: 53
`
`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 of those.
`As mentioned above, a new power headroom report MAC
`control element can be provided, which starts with a bitmap
`indicating which PHRs are being reported. Each bit of the
`bitmap can be linked to a particular power headroom report
`(e.g. PCell PHR, SCelll 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 10
`therefore indicates the size of the power headroom report
`MAC control element.
`The bit in the bitmap can indicate whether a power head(cid:173)
`room (PH) field is 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(cid:173)
`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(cid:173)
`ment power headroom report (UE-PHR). The use of the first
`bit for UE-PHR is, of course, an optional item. In some
`embodiments, there may be no need for such a PHR in addi(cid:173)
`tion to per-CC PHR.
`A second bit 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 SCelll, SCell2, SCell3, and
`SCell4. There can also be one reserved bit. In other embodi(cid:173)
`ments, such as if the first bit is not used for UE-PHR, there can
`be more than one reserved bit.
`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 computed as:
`P _cmax,c minus PUSCH power. Type 2 power headroom
`report can be computed as: P _cmax,c minus PUCCH power 40
`minus PUSCH power
`There are some additional considerations as well. For
`PCell, if in a TTl there can be either only Type 1 or Type 2
`PHR, one bit in the bitmap can be used to 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-headerfor PCell. This format is illustrated in FIG. 9. Still
`another possibility for PCell is to indicate Type 1 and Type 2
`power headroom reports via the R bit in the power headroom
`report payload for PCell. This format is illustrated in FIG. 10.
`A further alternative is to use a new logical channel identifier
`for Type 2 power headroom report, while for Type 1 the
`format can correspond to a release 8 format. Then, ifthere is
`only a power headroom report for PCell included, the bitmap
`byte is not needed. This format is 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 TTl, a simplified format could be used.
`The new power headroom report format could use a new
`logical channel identifier (LCID) or make use of one of the R
`bits of the subheader to indicate the occurrence of the bitmap.
`This bit is denoted E1 in FIG. 2. The bitmap could either
`follow the MAC Sub-header for 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.
`
`6
`The individual 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 approach is illustrated in FIG. 4.
`Alternatively, each individual power headroom report can be
`6 bits, with R bits for byte alignment when the payload is not
`byte aligned, as shown in FIG. 12; when it is byte aligned, no
`R bit needed, as showninFIG.13. FIG. 5 shows an alternative
`embodiment in which the first octet of the payload is the
`bitmap for the power headroom report.
`Various embodiments of the present invention may provide
`advantageous effects. For example, in certain embodiments,
`there may be no need to have a separate MAC sub-header for
`each individual power headroom report (different type of
`15 power headroom report, per component carrier power head(cid:173)
`room report for each component carrier and per-UE power
`headroom report). Thus, overhead may be reduced. Addition(cid:173)
`ally, issues arising from uncertainty of variable size may be
`avoided or handled. Furthermore, certain embodiments of the
`20 present invention may clearly and efficiently indicate which
`component carriers have power headroom report included,
`without a cross-CC indicator for each individual power head(cid:173)
`room report separately.
`FIG. 6 illustrates a method according to certain embodi-
`25 ments of the present invention. The method can include an
`eNB configuring 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(cid:173)
`ing 630 which type of power headroom report and the power
`30 headroom of which component carrier(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 component carrier.
`The method can include receiving 650 the power headroom
`report control element at the base station from the user equip(cid:173)
`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(cid:173)
`ment includes the bitmap in a media access control subheader
`or in a payload. The method can also include processing 633
`the received power headroom report control element, wherein
`45 the bitmap is exactly eight bits. The method can also include
`processing 635 the received power headroom report control
`element, wherein the bitmap includes a first bit for a user
`equipment power headroom report, a second bit for a type 1
`power headroom report for a primary serving cell, a third bit
`50 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 reserved bit. Because the eight
`bits can include a reserved bit, the power headroom report
`control element can alternatively be said t

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