IP Library › Granted Patent US 12,356,382
Granted Patent B2
US 12,356,382 · App. 18/465,476 · Granted Jul 8, 2025

Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers

Inventors: Philip J. Pietraski (Jericho, NY); Rui Yang (Greenlawn, NY); Kai Li (Edison, NJ); Carl Wang (Melville, NY); Tao Deng (Roslyn, NY); Samian Kaur (Plymouth Meeting, PA); Erdem Bala (East Meadow, NY); Ravikumar V. Pragada (Warrington, PA)
Assignee: InterDigital Patent Holdings, Inc.
H04W72/0453H04L5/001H04W52/146H04W52/325H04W52/346H04W72/23
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,356,382
App. No.
18/465,476
Granted
Jul 8, 2025
Kind
B2
Abstract

A wireless transmit/receive unit (WTRU) receives first timing advances and first power control commands from a first eNodeB and second timing advances and second power control commands from a second eNodeB and transmits, to the first eNodeB, a first physical uplink control channel using a first uplink component carrier. The first physical uplink control channel has a first timing adjusted by the first timing advances but not by the second timing advances and a first power level adjusted by the first power control commands but not by the second power control commands. The WTRU transmits a second physical uplink control channel using a second uplink component carrier. The second physical uplink control channel has a second timing adjusted by the second timing advances but not by the first timing advances and a second power level adjusted by the second power control commands but not by the first power control commands.

Claims (38)

1. A method implemented by a wireless transmit/receive unit (WTRU), the method comprising:

receiving a radio resource control (RRC) message via a first downlink component carrier associated with a first site, the RRC message comprising information indicating first search space information for decoding physical downlink control channel (PDCCH) transmissions via the first downlink component carrier associated with the first site, and second search space information for decoding PDCCH transmissions via a second downlink component carrier associated with a second site;

receiving a first PDCCH transmission via the first downlink component carrier associated with the first site in accordance with the first search space information;

receiving a second PDCCH transmission via the first downlink component carrier associated with the first site in accordance with the first search space information;

sending a first transmission via a first uplink component carrier associated with the first site in accordance with the first PDCCH transmission; and

sending a second transmission via a second uplink component carrier associated with the second site in accordance with the second PDCCH transmission, wherein the first transmission and second transmission at least partially overlap in time.

2. The method of claim 1 , wherein the first site is associated with a first plurality of downlink component carriers utilized by the WTRU.

3. The method of claim 2 , further comprising receiving a third PDCCH transmission via the first downlink carrier associated with the first site in accordance with the first search space information, wherein the third PDCCH transmission schedules a downlink transmission in one of the first plurality of downlink component carriers associated with the first site, and the third PDCCH transmission comprises a carrier indicator (CI) field indicating which of the first plurality of component carriers is being scheduled.

4. The method of claim 3 , further comprising receiving a fourth PDCCH transmission via the second downlink carrier associated with the second site in accordance with the second search space information, wherein the second site is associated with a second plurality of downlink component carriers utilized by the WTRU, the fourth PDCCH transmission schedules a second downlink transmission in one of the second plurality of downlink component carriers associated with the second site, and the fourth PDCCH transmission comprises a CI field indicating which of the second plurality of component carriers is being scheduled.

5. The method as in claim 3 , further comprising receiving a fifth PDCCH transmission via the first downlink carrier associated with the first site in accordance with the first search space information, wherein the fifth PDCCH transmission schedules a second downlink transmission in one of the first plurality of downlink component carriers associated with the first site, and the fifth PDCCH transmission is separately coded from the third PDCCH transmission.

6. The method of claim 1 , wherein the first site is associated with a first plurality of uplink component carriers, the second site is associated with a second plurality of uplink component carriers, one of the first plurality of uplink component carriers is used for sending physical uplink control channel (PUCCH) transmissions to the first site, and one of the second plurality of uplink component carriers is used for sending PUCCH transmissions to the second site.

7. The method of claim 1 , further comprising maintaining a first timing advance value for the first uplink component carrier associated with the first site and a second timing advance value for the second uplink component carrier associated with the second site.

8. The method of claim 1 , further comprising:

determining a first transmission power for a first set of one or more transmissions sent to the first site, the first set of one or more transmissions comprising the first transmission sent via the first uplink component carrier associated with the first site;

determining a second transmission power for a second set of one or more transmissions sent to the second site, the second set of one or more transmissions comprising the second transmission sent via the second uplink component carrier associated with the second site; and

determining to scale at least one of the second set of one or more transmissions sent to the second site based on a total of the first determined transmission power and the second determined transmission power exceeding a maximum transmission power, wherein the first set of one or more transmission sent to the first site are not scaled.

9. The method of claim 8 , wherein determining to scale at least one of the set of one or more transmissions sent to the second site comprises reducing a power to the second transmission sent via the first component carrier based on the second transmission corresponding to a physical uplink shared channel transmission (PUSCH) without uplink control information (UCI) and at least one other transmission of the second set of one or more transmissions comprising a physical uplink control channel (PUCCH) transmission sent to the second site.

10. The method of claim 8 , wherein determining to scale at least one of the second set of one or more transmissions sent to the second site comprises maintaining a determined power level for the second transmission sent via the first component carrier based on the second transmission corresponding to a physical uplink control channel transmission (PUSCH), and reducing a power level of at least one other transmission of the second set of one or more transmissions based on the at least one other transmission comprising a physical uplink shared channel (PUSCH) transmission sent to the second site.

11. A wireless transmit/receive unit (WTRU) comprising:

a transceiver; and

a processor configured to:

receive, via the transceiver, a radio resource control (RRC) message via a first downlink component carrier associated with a first site, the RRC message comprising information indicating first search space information for decoding physical downlink control channel (PDCCH) transmissions via the first downlink component carrier associated with the first site, and second search space information for decoding PDCCH transmissions via a second downlink component carrier associated with a second site;

receive, via the transceiver, a first PDCCH transmission via the first downlink component carrier associated with the first site in accordance with the first search space information;

receive, via the transceiver, a second PDCCH transmission via the first downlink component carrier associated with the first site in accordance with the first search space information;

send, via the transceiver, a first transmission via a first uplink component carrier associated with the first site in accordance with the first PDCCH transmission; and

send, via the transceiver, a second transmission via a second uplink component carrier associated with the second site in accordance with the second PDCCH transmission, wherein the first transmission and second transmission at least partially overlap in time.

12. The WTRU of claim 11 , wherein the first site is associated with a first plurality of downlink component carriers utilized by the WTRU.

13. The WTRU of claim 12 , the processor further configured to receive, via the transceiver, a third PDCCH transmission via the first downlink carrier associated with the first site in accordance with the first search space information, wherein the third PDCCH transmission schedules a downlink transmission in one of the first plurality of downlink component carriers associated with the first site, and the third PDCCH transmission comprises a carrier indicator (CI) field indicating which of the first plurality of component carriers is being scheduled.

14. The WTRU of claim 13 , the processor further configured to receive, via the transceiver, a fourth PDCCH transmission via the second downlink carrier associated with the second site in accordance with the second search space information, wherein the second site is associated with a second plurality of downlink component carriers utilized by the WTRU, the fourth PDCCH transmission schedules a second downlink transmission in one of the second plurality of downlink component carriers associated with the second site, and the fourth PDCCH transmission comprises a CI field indicating which of the second plurality of component carriers is being scheduled.

15. The WTRU as in claim 13 , the processor further configured to receive, via the transceiver, a fifth PDCCH transmission via the first downlink carrier associated with the first site in accordance with the first search space information, wherein the fifth PDCCH transmission schedules a second downlink transmission in one of the first plurality of downlink component carriers associated with the first site, and the fifth PDCCH transmission is separately coded from the third PDCCH transmission.

16. The WTRU of claim 11 , wherein the first site is associated with a first plurality of uplink component carriers, the second site is associated with a second plurality of uplink component carriers, one of the first plurality of uplink component carriers is used for sending physical uplink control channel (PUCCH) transmissions to the first site, and one of the second plurality of uplink component carriers is used for sending PUCCH transmissions to the second site.

17. The WTRU of claim 11 , the processor further configured to maintain a first timing advance value for the first uplink component carrier associated with the first site and a second timing advance value for the second uplink component carrier associated with the second site.

18. The WTRU of claim 11 , the processor further configured to:

determine a first transmission power for a first set of one or more transmissions sent to the first site, the first set of one or more transmissions comprising the first transmission sent via the first uplink component carrier associated with the first site;

determine a second transmission power for a second set of one or more transmissions sent to the second site, the second set of one or more transmissions comprising the second transmission sent via the second uplink component carrier associated with the second site; and

determine to scale at least one of the second set of one or more transmissions sent to the second site based on a total of the first determined transmission power and the second determined transmission power exceeding a maximum transmission power, wherein the first set of one or more transmission sent to the first site are not scaled.

19. The WTRU of claim 18 , wherein to determine to scale at least one of the set of one or more transmissions sent to the second site comprises to reduce a power to the second transmission sent via the first component carrier based on the second transmission corresponding to a physical uplink shared channel transmission (PUSCH) without uplink control information (UCI) and at least one other transmission of the second set of one or more transmissions comprising a physical uplink control channel (PUCCH) transmission sent to the second site.

20. The WTRU of claim 18 , wherein to determine to scale at least one of the second set of one or more transmissions sent to the second site comprises to maintain a determined power level for the second transmission sent via the first component carrier based on the second transmission corresponding to a physical uplink control channel transmission (PUSCH), and to reduce a power level of at least one other transmission of the second set of one or more transmissions based on the at least one other transmission comprising a physical uplink shared channel (PUSCH) transmission sent to the second site.

Continuity (9)
Continuation 17567614 · Jan 3, 2022
Continuation 16700425 · Dec 2, 2019
Continuation 15612646 · Jun 2, 2017
Continuation 14684931 · Apr 13, 2015
Continuation 13577549
Provisional Application 61304371 · Feb 12, 2010
Provisional Application 61304217 · Feb 12, 2010
Provisional Application 61303967 · Feb 12, 2010
Related Publication 20240007969A1 · Jan 4, 2024
References Cited (138)
US 5596329A · Searle et al. · 1997 [cited by applicant]
US 6499128B1 · Gerlach et al. · 2002 [cited by applicant]
US 6545997B1 · Boehnke et al. · 2003 [cited by applicant]
US 8274927B2 · Kim et al. · 2012 [cited by applicant]
US 8958793B2 · Chandra et al. · 2015 [cited by applicant]
US 9215665B2 · Papasakellariou et al. · 2015 [cited by applicant]
US 9247505B2 · Pajukoski et al. · 2016 [cited by applicant]
US 11218978B2 · Pietraski et al. · 2022 [cited by applicant]
US 20030203738A1 · Brown et al. · 2003 [cited by applicant]
US 20040085940A1 · Black et al. · 2004 [cited by applicant]
US 20040106412A1 · Laroia et al. · 2004 [cited by applicant]
US 20050277419A1 · Takano · 2005 [cited by examiner]
US 20050286472A1 · Lee et al. · 2005 [cited by applicant]
US 20060003787A1 · Heo et al. · 2006 [cited by applicant]
US 20060286996A1 · Julian et al. · 2006 [cited by applicant]
US 20070183432A1 · Kim et al. · 2007 [cited by applicant]
US 20070293226A1 · Lee et al. · 2007 [cited by applicant]
US 20070293260A1 · Xiao et al. · 2007 [cited by applicant]
US 20080273610A1 · Malladi et al. · 2008 [cited by applicant]
US 20090270103A1 · Pani et al. · 2009 [cited by applicant]
US 20100020852A1 · Erell et al. · 2010 [cited by applicant]
US 20100027471A1 · Palanki et al. · 2010 [cited by applicant]
US 20100034163A1 · Damnjanovic et al. · 2010 [cited by applicant]
US 20100135237A1 · Papasakellariou et al. · 2010 [cited by applicant]
US 20100222059A1 · Pani et al. · 2010 [cited by applicant]
US 20100226327A1 · Zhang et al. · 2010 [cited by applicant]
US 20100246463A1 · Papasakellariou et al. · 2010 [cited by applicant]
US 20100291931A1 · Suemitsu et al. · 2010 [cited by applicant]
US 20100302964A1 · Guo · 2010 [cited by applicant]
US 20100303039A1 · Zhang et al. · 2010 [cited by applicant]
US 20110013581A1 · Lee et al. · 2011 [cited by applicant]
US 20110021154A1 · Marinier et al. · 2011 [cited by applicant]
US 20110038271A1 · Shin et al. · 2011 [cited by applicant]
US 20110051654A1 · Blankenship et al. · 2011 [cited by applicant]
US 20110075624A1 · Papasakellariou et al. · 2011 [cited by applicant]
US 20110092219A1 · Damnjanovic et al. · 2011 [cited by applicant]
US 20110103332A1 · Kuo · 2011 [cited by applicant]
US 20110105048A1 · Nakao et al. · 2011 [cited by applicant]
US 20110182201A1 · Pajukoski et al. · 2011 [cited by applicant]
US 20110207452A1 · Grob-Lipski et al. · 2011 [cited by applicant]
US 20120134275A1 · Choi et al. · 2012 [cited by applicant]
US 20120182950A1 · Chung · 2012 [cited by examiner]
US 20120202501A1 · Morioka et al. · 2012 [cited by applicant]
US 20130010964A1 · Fong et al. · 2013 [cited by applicant]
US 20130163527A1 · Lunttila et al. · 2013 [cited by applicant]
US 20130176988A1 · Wang et al. · 2013 [cited by applicant]
US 20130215849A1 · Heo et al. · 2013 [cited by applicant]
US 20170244534A1 · Heo et al. · 2017 [cited by applicant]
US 20180138961A1 · Imamura et al. · 2018 [cited by applicant]
CN 101404526A · 2009 [cited by applicant]
CN 101523823A · 2009 [cited by applicant]
CN 101502151B · 2012 [cited by applicant]
EP 2146545A1 · 2010 [cited by applicant]
EP 2553986A1 · 2013 [cited by applicant]
EP 2567580A1 · 2013 [cited by applicant]
JP 2002077042A · 2002 [cited by applicant]
JP 2007079476A · 2007 [cited by applicant]
JP 2011097443A · 2011 [cited by applicant]
JP 2011521524A · 2011 [cited by applicant]
JP 2011525336A · 2011 [cited by applicant]
JP 2011530845A · 2011 [cited by applicant]
KR 20090033421A · 2009 [cited by applicant]
KR 20090053835A · 2009 [cited by applicant]
KR 20090098651A · 2009 [cited by applicant]
WO WO2009057544A1 · 2009 [cited by applicant]
WO WO2009120125A1 · 2009 [cited by applicant]
WO WO2010007763A1 · 2010 [cited by applicant]
WO WO2010010516A2 · 2010 [cited by applicant]
WO WO2010016698A2 · 2010 [cited by applicant]
WO WO2010091425A2 · 2010 [cited by applicant]
WO WO2011120716A1 · 2011 [cited by applicant]
WO WO2011140504A1 · 2011 [cited by applicant]
3rd Generation Partnership Project, “Carrier aggregation in active mode,” Huawei, 3GPP TSG-RAN WG2 Meeting #66, R2-093104, San Francisco, USA (May 4-8, 2009). [cited by applicant]
3rd Generation Partnership Project, “Carrier Aggregation in Heterogeneous Networks,” Qualcomm Europe, 3GPP TSG RAN WG1 #55bis, R1-090357, Ljubljana, Slovenia (Jan. 12-16, 2009). [cited by applicant]
3rd Generation Partnership Project, “COMP Configuration for Multiple Component Carriers in LTE-A,” Sharp, 3GPP TSG RAN WG1 Meeting #56bis, R1-091134, Seoul, Korea (Mar. 23-27, 2009). [cited by applicant]
3rd Generation Partnership Project, “COMP email summary,” Qualcomm Europe, 3GPP TSG-RAN WG1 #57bis, R1-092946, Los Angeles, USA (Jun. 29-Jul. 2, 2009). [cited by applicant]
3rd Generation Partnership Project, “Component carrier operation without PDCCH,” Panasonic, 3GPP TSG-RAN WG1 Meeting #58, R1-093598, Shenzhen, China (Aug. 24-28, 2009). [cited by applicant]
3rd Generation Partnership Project, “Control plane aspects of carrier aggregation,” Ericsson, 3GPP TSG-RAN WG2 #66, R2-092958, San Francisco, USA (May 4-8, 2009). [cited by applicant]
3rd Generation Partnership Project, “Explicit carrier activation/deactivation,” ETRI, 3GPP TSG RAN WG2 #68bis, R2-100148, Valencia, Spain (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “LS on RAN2 status on carrier aggregation design,” RAN2, 3GPP TSG RAN WG1 Meeting #57bis, R1-092294, Los Angeles, CA, USA (Jun. 29-Jul. 3, 2009). [cited by applicant]
3rd Generation Partnership Project, “Measurement considerations for carrier aggregation,” Qualcomm Incorporated, 3GPP TSG-RAN WG2 meeting#68bis, R2-100421, Valencia, Spain (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “Notion of Anchor Carrier in LTE-A,” Qualcomm Europe, 3GPP TSG RAN WG1 #56bis, R1-091458, Seoul, Korea (Mar. 23-27, 2009). [cited by applicant]
3rd Generation Partnership Project, “On selection of PUSCH for UCI transmission,” ALCATEL-LUCENT et al., 3GPP TSG-RAN WG1 #63bis, R1- 110223, Dublin, Ireland (Jan. 17-21, 2011). [cited by applicant]
3rd Generation Partnership Project, “PCFICH in cross carrier operation,” Panasonic, 3GPP TSG-RAN WG1 #59bis, R1-100360, Valencia, Spain (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “Power Allocation among eNBs in Closed-Loop DL Comp Tranmission,” Nortel, 3GPP TSG-RAN Working Group 1 Meeting #56bis, R1-091378, Seoul, Korea (Mar. 23-27, 2009). [cited by applicant]
3rd Generation Partnership Project, “PUSCH and PUCCH Power Scaling for Carrier Aggregation,” Alcatel-Lucent Shanghai Bell et al., 3GPP TSG RAN WG1#59bis, R1-100414, Valencia, Spain (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “Radio Link Failure considering carrier aggregation,” LG Electronics, Inc., 3GPP TSG-RAN2 Meeting #66bis, R2-093856, Los Angeles, California (Jun. 29-Jul. 3, 2009). [cited by applicant]
3rd Generation Partnership Project, “Radio Link Failure in Carrier Aggregation,” ITRI, 3GPP TSG RAN WG2 #67bis, R2-096033, Miyazaki, Japan (Oct. 12-16, 2009). [cited by applicant]
3rd Generation Partnership Project, “Radio Link Monitoring in a Multicarrier Setting,” Qualcomm Europe, 3GPP TSG-RAN WG2 #66bis, R2-093872, Los Angeles, California (Jun. 29-Jul. 3, 2009). [cited by applicant]
3rd Generation Partnership Project, “RAN2 agreements on Carrier Aggregations, PDCP and Contention Based Uplink,” Nokia Siemens Networks, 3GPP TSG-WG2 Meeting #68, R2-097495, Jeju, Korea (Nov. 9-13, 2009). [cited by applicant]
3rd Generation Partnership Project, “Release 10 UE PUCCH/PUSCH configuration,” Motorola, 3GPP TSG-RAN Meeting Ad Hoc #2010-01, R4-100207, Sophia Antipolis, France (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “Reply LS on RAN2 status on carrier aggregation,” TSG-RAN WG4, 3GPP TSG RAN WG2 Meeting #67bis, R2-095422, Miyazaki, Japan (Oct. 12-16, 2009). [cited by applicant]
3rd Generation Partnership Project, “Reply LS on RAN2 status on carrier aggregation,” TSG-RAN WG4, 3GPP TSG RAN WG4 Meeting #51bis, R4-09xxxx (R4-092488), Los Angeles, USA (Jun. 29-Jul. 2, 2009). [cited by applicant]
3rd Generation Partnership Project, “RLF Procedures for Carrier Aggregation,” Interdigital, 3GPP TSG-RAN WG2 Meeting #67, R2-094218, Shen Zhen, China (Aug. 24-28, 2009). [cited by applicant]
3rd Generation Partnership Project, “Stage 2 description of Carrier Aggregation,” Nokia Siemens Networks, 3GPP TSG-RAN WG2 Meeting #68bis, R2-100789, Valencia, Spain, (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 8),” 3GPP TS 36… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall desc… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification (Release 8),” 3GPP TS 36.32… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification (Release 9),” 3GPP TS 36.32… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 8),” 3GPP TS 36.… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 9),” 3GPP TS 36.… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Further advancements for E-UTRA physical layer aspects (Release 9),” 3GPP TR … [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 10),” 3GPP TS 36.… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 8),” 3GPP TS 36.3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 9),” 3GPP TS 36.3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 10),” 3GPP TS 36.211 V10.0.0 (Dec. … [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8),” 3GPP TS 36.211 V8.6.0 (Mar. 20… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8),” 3GPP TS 36.211 V8.9.0 (Dec. 20… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 9),” 3GPP TS 36.211 V9.0.0 (Dec. 20… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 9),” 3GPP TS 36.211 V9.1.0 (Mar. 20… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 10),” 3GPP TS 36.213 V10.0.1 (Dec. 2010). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 8),” 3GPP TS 36.213 V8.8.0 (Sep. 2009). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 9),” 3GPP TS 36.213 V9.3.0 (Sep. 2010). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 9),” 3GPP TS 36.213 V9.0.1 (Dec. 2009). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 9),” 3GPP TS 36… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 10),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management (Release 10),” 3GPP TS … [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management (Release 8),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management (Release 9),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management (Release 9),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management (Release 8),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception (Release 9),” 3GPP TS 36… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception (Release 10),” 3GPP TS 3… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception (Release 9),” 3GPP TS 36… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 10),” 3GPP TS 36.423 V10.0.0… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 8),” 3GPP TS 36.423 V8.9.0 (… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 9),” 3GPP TS 36.423 V9.5.0 (… [cited by applicant]
3rd Generation Partnership Project, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 8) 3GPP TS 36.423 V8.8.0 (Dec… [cited by applicant]
3rd Generation Partnership Project, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 9) 3GPP TS 36.423 V9.1.0 (Dec… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Feasibility study for Further Advancements for E-UTRA (LTE-Advanced) (Release 9),” 3GPP TR 36.912 V9.1.0 (Dec. 2009). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Feasibility study for Further Advancements for E-UTRA (LTE-Advanced) (Release 9),” 3GPP TR 36.912 V9.3.0 (Jun. 2010). [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; Further Advancements for E-UTRA Physical Layer Aspects (Release 9),” 3GPP TR 36.814 V1.5.0 (Nov. 2009). [cited by applicant]
3rd Generation Partnership Project, “UL Power Control for Multicarrier Operation,” Qualcomm Incorporated, 3GPP TSG RAN WG1 #59bis, R1-100677, Valencia, Spain (Jan. 18-22, 2010). [cited by applicant]
3rd Generation Partnership Project, “UL TPC in Rel.10,” Samsung, 3GPP TSG RAN WG1 #59bis, R1-100100, Valencia, Spain (Jan. 19-23, 2010). [cited by applicant]