Abstract
A method for reporting power headroom is disclosed. Power headroom may be reported across all carriers (wideband) for a specific carrier or for a carrier group. The formula used to calculate the power headroom depends on whether the carrier (or a carrier in the carrier group) has a valid uplink grant. If the carrier or carrier group does not have a valid uplink grant the power headroom may be calculated based on a reference grant. The power headroom is calculated by a wireless transmit/receive unit and is reported to an eNodeB.
| Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Information | ||||||
| 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
Specification Information
Specification Information
Technologies
Family Information
| All Granted Patents In Patent Family : | ---- |
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||
| US2010158147A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
Yes | Basis Patent | |||
| US2010158147A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | Yes | Basis Patent | ||||
| US8315320B2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
Yes | Basis Patent | |||
| US8315320B2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | Yes | Basis Patent | ||||
| AR074461A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| AR074461A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| WO2010065759A2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| WO2010065759A2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| WO2010065759A3 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| WO2010065759A3 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| EP2371078A2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| EP2371078A2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| EP2371078B1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| EP2371078B1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TW201101908A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TW201101908A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TWI455630B | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TWI455630B | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR101502439B1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR101502439B1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR20110098768A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR20110098768A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| CN102318426A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| CN102318426A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| CN102318426B | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| CN102318426B | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| JP2012510785A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| JP2012510785A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| JP5581331B2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| JP5581331B2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TW201134277A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TW201134277A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TWI487416B | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TWI487416B | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| US2013028231A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| US2013028231A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| US9426752B2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| US9426752B2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| RU2011127204A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| RU2011127204A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| RU2522175C2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| RU2522175C2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR101722810B1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR101722810B1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR20130076893A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR20130076893A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| JP2014233073A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| JP2014233073A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| JP5993901B2 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| JP5993901B2 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR20150023886A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR20150023886A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR101724053B1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR101724053B1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| KR20150052353A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| KR20150052353A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TW201528852A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TW201528852A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| TWI542241B | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| TWI542241B | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| CN105307255A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| CN105307255A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| US2016309426A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| US2016309426A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| HK1161026A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| HK1161026A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| JP2016226028A | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| JP2016226028A | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| EP3197230A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| EP3197230A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| CN105307255B | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| CN105307255B | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| US2019246361A1 | 4G | 16/09/2010 | ISLD-201010-010 | INTERDIGITAL INC |
S1
S2
|
No | Family Member | |||
| US2019246361A1 | 5G | 08/11/2019 | ISLD-201910-015 | INTERDIGITAL INC | No | Family Member | ||||
| EP3197230B1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US10798663B2 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| US2021014798A1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | Status | National Phase Entries | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||||
| ----- | ----- | ----- | ----- | ----- |
S1
|
----- | ----- | ----- | ----- | |||
Technologies
Resource configuration Power Control
Product
User Equipment (UE/Terminal)
Use Cases
Wireless communication
Services
Transmitting/receiving data in uplink
Claim
1. A wireless transmit/receive unit (WTRU) comprising, the WTRU comprising:
a processor configured to:
determine a carrier that does not have a physical uplink shared channel (PUSCH) transmission in a subframe i from a plurality of aggregated carriers;
calculate a power headroom for the carrier according to the formula:
PH(k,i)=P CMAX _ carrier(k)?P PUSCH _ REF(k,i)
where PH(k,i) is the power headroom for the carrier, k is the carrier, PCMAX _ carrier(k) is a maximum power for the carrier, and PPUSCH _ REF(k,i) is a transmit power determined according to a reference grant; and
report the power headroom for the carrier.
2. The WTRU of claim 1, wherein the processor is configured to report the power headroom for the carrier by sending a power headroom report to an eNodeB.
3. The WTRU of claim 2, wherein the power headroom report is a type 1 power headroom report.
4. The WTRU of claim 1, wherein the reference grant is a pre-defined allocation.
5. The WTRU of claim 4, wherein the pre-defined allocation is a pre-defined number of resource blocks.
6. The WTRU of claim 1, wherein the carrier does not have a valid uplink grant.
7. The WTRU of claim 1, wherein the carrier is a first carrier and wherein the processor is configured to report the power headroom for the first carrier by reporting the power headroom for the first carrier to a second carrier.
8. The WTRU of claim 2, wherein the carrier is a first carrier, the power headroom for the carrier is a first power headroom for the first carrier, and the power headroom report comprises the first power headroom for the first carrier and a second power headroom for a second carrier that has a valid uplink grant.
9. The WTRU of claim 1, wherein the processor is configured to report the power headroom for the carrier by reporting the power headroom for the carrier via medium access control (MAC) signaling.
10. A wireless transmit/receive unit (WTRU), the WTRU comprising:
a processor configured to:
determine a carrier that does not have a physical uplink shared channel (PUSCH) transmission in a subframe from a plurality aggregated carriers;
determine a maximum power for the carrier;
calculate a power headroom for the carrier using the maximum power for the carrier and a reference grant; and
send a power headroom report that includes the power headroom for the carrier.
11. The WTRU of claim 10, wherein the processor is configured to send the power headroom report by sending the power headroom report to an eNodeB.
12. The WTRU of claim 10, wherein the power headroom report is a type 1 power headroom report.
13. The WTRU of claim 10, wherein the power headroom report is a type 2 power headroom report.
14. The WTRU of claim 10, wherein the reference grant is a pre-defined allocation.
15. The WTRU of claim 14, wherein the pre-defined allocation is a pre-defined number of resource blocks.
16. The WTRU of claim 10, wherein the carrier does not have a valid uplink grant.
17. The WTRU of claim 10, wherein the processor is further configured to calculate a reference transmit power using the reference grant.
18. The WTRU of claim 10, wherein the processor is further configured to calculate the power headroom for the carrier using the maximum power for the carrier and the reference grant by:
calculating a reference transmit power using the reference grant; and
calculating the power headroom for the carrier using the maximum power for the carrier and the reference transmit power.
19. The WTRU of claim 18, wherein the processor is further configured to calculate the power headroom for the carrier using the maximum power for the carrier and the reference grant by determining a difference between the maximum power for the carrier and the reference transmit power.
20. The WTRU of claim 10, wherein the carrier is a first carrier and wherein the processor is configured to send the power headroom report by sending the power headroom report to a second carrier.
21. The WTRU of claim 10, wherein the carrier is a first carrier, the power headroom for the carrier is a first power headroom for the first carrier, and the power headroom report comprises the first power headroom for the first carrier and a second power headroom for a second carrier that has a valid uplink grant.
22. The WTRU of claim 10, wherein the processor is configured to send the power headroom report via medium access control (MAC) signaling.
23. A method for reporting power headroom, the method comprising:
determining a carrier that does not have a physical uplink shared channel (PUSCH) transmission in a subframe i from a plurality of aggregated carriers;
calculating a power headroom for the carrier according to the formula:
PH(k,i)=P CMAX _ carrier(k)?P PUSCH _ REF(k,i)
where PH(k,i) is the power headroom for the carrier, k is the carrier, PCMAX _ carrier(k) is a maximum power for the carrier, and PPUSCH _ REF(k, i) is a transmit power determined according to a reference grant; and
reporting the power headroom for the carrier.
24. The method of claim 23, wherein reporting the power headroom for the carrier comprises sending a power headroom report to an eNodeB.
25. The method of claim 24, wherein the power headroom report is a type 1 power headroom report.
26. The method of claim 23, wherein the reference grant is a pre-defined allocation.
27. The method of claim 26, wherein the pre-defined allocation is a pre-defined number of resource blocks.
28. The method of claim 23, wherein the carrier does not have a valid uplink grant.
29. The method of claim 23, wherein the carrier is a first carrier and wherein reporting the power headroom for the first carrier comprises reporting the power headroom for the first carrier to a second carrier.
30. The method of claim 25, wherein the carrier is a first carrier, the power headroom for the carrier is a first power headroom for the first carrier, and the power headroom report comprises the first power headroom for the first carrier and a second power headroom for a second carrier that has a valid uplink grant.
31. The method of claim 23, wherein reporting the power headroom for the carrier comprises reporting the power headroom via medium access control (MAC) signaling.
32. A method for reporting power headroom, the method comprising:
determining a carrier that does not have a physical uplink shared channel (PUSCH) transmission in a subframe from a plurality of aggregated carriers;
determining a maximum power for the carrier;
calculating a power headroom for the carrier using the maximum power for the carrier and a reference grant; and
sending a power headroom report that includes the power headroom for the carrier.
33. The method of claim 32, wherein sending the power headroom report comprises sending the power headroom report to an eNodeB.
34. The method of claim 32, wherein the power headroom report is a type 1 power headroom report.
35. The method of claim 32, wherein the power headroom report is a type 2 power headroom report.
36. The method of claim 32, wherein the reference grant is a pre-defined allocation.
37. The method of claim 36, wherein the pre-defined allocation is a pre-defined number of resource blocks.
38. The method of claim 32, wherein the carrier does not have a valid uplink grant.
39. The method of claim 32, further comprising calculating a reference transmit power using the reference grant.
40. The method of claim 32, wherein calculating the power headroom for the carrier using the maximum power for the carrier and the reference grant comprises:
calculating a reference transmit power using the reference grant; and
calculating the power headroom for the carrier using the maximum power for the carrier and the reference transmit power.
41. The method of claim 40, wherein calculating the power headroom for the carrier using the maximum power for the carrier and the reference grant further comprises determining a difference between the maximum power for the carrier and the reference transmit power.
42. The method of claim 32, wherein the carrier is a first carrier and wherein sending the power headroom report comprises sending the power headroom report to a second carrier.
43. The method of claim 32, wherein the carrier is a first carrier, the power headroom for the carrier is a first power headroom for the first carrier, and the power headroom report comprises the first power headroom for the first carrier and a second power headroom for a second carrier that has a valid uplink grant.
44. The method of claim 32, wherein sending the power headroom report comprises sending the power headroom report via medium access control (MAC) signaling.
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
To view claim charts you must become a Gold or Platinum Member.
Upgrade your subscriptionYou have reached the maximum number of patents which can be associated to your account per your subscription. If you wish to associate more patents
Please upgrade your subscription.Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent:openly and comprehensibly describes all details of the invention in the patent document.
Implicitly disclosed patent:does not explicitly state certain aspects of the invention, but still allows for these to be inferred from the information provided.
Basis patent:The core patent in a family, outlining the fundamental invention from which related patents or applications originate.
Family member:related patents or applications that share a common priority or original filing.