IP Library Granted Patent US 12,418,490
Granted Patent B2
US 12,418,490 · App. 18/477,155 · Granted Sep 16, 2025

Logical channel management in a wireless communication network

Inventor: Paul Marinier (Brossard, CA)
Assignee: INTERDIGITAL PATENT HOLDINGS, INC.
H04L47/266H04L5/0053H04W8/04H04W28/0278H04W72/1263H04W72/20H04W72/23H04W72/52
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,418,490
App. No.
18/477,155
Granted
Sep 16, 2025
Kind
B2
Abstract

A base station may be configured to send a first downlink control information indicating that a wireless transmit/receive unit (WTRU) is to transmit uplink data on a first uplink channel. The base station may be configured to receive a plurality of a same value over a second uplink channel in response to a triggering condition. The second uplink channel may be a control channel. The base station may be configured to sending a second downlink control information in accordance with the plurality of the same value over the second uplink channel. The plurality of the same value may be in response to the first downlink control information providing an insufficient amount to transmit uplink data over the first uplink channel. The base station may be configured to send an indication of logical channels that are subject to triggering of an uplink scheduling request.

Claims (23)

1. A method, implemented by a base station, the method comprising:

sending a first downlink control information indicating that a wireless transmit/receive unit (WTRU) is to transmit uplink data on a first uplink channel;

sending an indication of logical channels that are subject to triggering of an uplink scheduling request;

receiving a plurality of a same value over a second uplink channel in response to a triggering condition, wherein the triggering condition is based on the indication of logical channels, wherein the second uplink channel is a control channel; and

sending a second downlink control information in accordance with the plurality of the same value over the second uplink channel.

2. The method of claim 1 , wherein the receiving the plurality of the same value is in response to the first downlink control information providing an insufficient amount to transmit uplink data over the first uplink channel.

3. The method of claim 1 , further comprising receiving, for a logical channel, an indication of a recommended uplink resource.

4. The method of claim 3 , wherein the indication of the recommended uplink resource is associated with a data rate.

5. The method of claim 3 , further comprising transmitting an uplink scheduling resource for the first uplink channel based on the received indication.

6. The method of claim 1 , wherein the receiving of the plurality of the same value is a request for an uplink scheduling resource.

7. A base station comprising:

a processor;

a receiver; and

a transmitter; wherein:

the processor and the transmitter are configured to transmit a first downlink control information indicating that a wireless transmit/receive unit (WTRU) is to transmit uplink data on a first uplink channel;

the processor and the transmitter are further configured to send an indication of logical channels that are subject to triggering of an uplink scheduling request;

the processor and the receiver are configured to receive, in response to a triggering condition, a plurality of a same value over a second uplink channel, wherein the triggering condition is based on the indication of logical channels, wherein the second uplink channel is a control channel; and

the processor and the transmitter are further configured to transmit a second downlink control information in accordance with the plurality of the same value over the second uplink channel.

8. The base station of claim 7 , wherein the reception of the plurality of the same value is in response to the first downlink control information providing an insufficient amount to transmit uplink data over the first uplink channel.

9. The base station of claim 7 , wherein the processor and the receiver are further configured to receive, for a logical channel, an indication of a recommended uplink resource.

10. The base station of claim 9 , wherein the indication of the recommended uplink resource is associated with a data rate.

11. The base station of claim 9 , wherein the processor and the transmitter are further configured to transmit an uplink scheduling resource for the first uplink channel based on the received indication.

12. The base station of claim 7 , wherein the reception of the plurality of the same value is a request for an uplink scheduling resource.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 9, 2025
From: INTERDIGITAL TECHNOLOGY CORPORATION
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 070793/0352 →
Continuity (8)
Continuation 16852668 · Apr 20, 2020
Continuation 16207795 · Dec 3, 2018
Continuation 15581902 · Apr 28, 2017
Continuation 14449819 · Aug 1, 2014
Continuation 12942528 · Nov 9, 2010
Continuation 11840308 · Aug 17, 2007
Provisional Application 60839198 · Aug 21, 2006
Related Publication 20240048332A1 · Feb 8, 2024
References Cited (130)
US 6091717A · Honkasalo · 2000 [cited by applicant]
US 6501745B1 · Turina et al. · 2002 [cited by applicant]
US 6580720B1 · Francis et al. · 2003 [cited by applicant]
US 6785232B1 · Kotser et al. · 2004 [cited by applicant]
US 7418260B2 · Lucidarme · 2008 [cited by applicant]
US 7447504B2 · Lohr et al. · 2008 [cited by applicant]
US 7477609B2 · Agir · 2009 [cited by applicant]
US 7580392B2 · Yang et al. · 2009 [cited by applicant]
US 7904113B2 · Ozluturk et al. · 2011 [cited by applicant]
US 7948936B2 · Lohr et al. · 2011 [cited by applicant]
US 7948958B2 · Vimpari et al. · 2011 [cited by applicant]
US 8139523B2 · Usuda et al. · 2012 [cited by applicant]
US 8320340B2 · Sim et al. · 2012 [cited by applicant]
US 8570952B2 · Terry et al. · 2013 [cited by applicant]
US 8582514B2 · Moberg et al. · 2013 [cited by applicant]
US 8861343B2 · Yang et al. · 2014 [cited by applicant]
US 8873474B2 · Pelletier et al. · 2014 [cited by applicant]
US 11818068B2 · Marinier · 2023 [cited by examiner]
US 20020154676A1 · Kowalewski et al. · 2002 [cited by applicant]
US 20030039267A1 · Koo et al. · 2003 [cited by applicant]
US 20040127225A1 · Qiu et al. · 2004 [cited by applicant]
US 20050105553A1 · Zhang · 2005 [cited by examiner]
US 20060013268A1 · Terry · 2006 [cited by applicant]
US 20060104240A1 · Sebire et al. · 2006 [cited by applicant]
US 20060143444A1 · Malkamaki · 2006 [cited by examiner]
US 20060146761A1 · Kim et al. · 2006 [cited by applicant]
US 20060209896A1 · Choi et al. · 2006 [cited by applicant]
US 20060251027A1 · Chun · 2006 [cited by examiner]
US 20060280145A1 · Revel et al. · 2006 [cited by applicant]
US 20060291429A1 · Matusz · 2006 [cited by applicant]
US 20070073895A1 · Sebire et al. · 2007 [cited by applicant]
US 20070140102A1 · Oh et al. · 2007 [cited by applicant]
US 20080159184A1 · Niwano · 2008 [cited by applicant]
EP 1507352 · 2005 [cited by applicant]
EP 1633086 · 2006 [cited by applicant]
EP 1689132 · 2006 [cited by applicant]
GB 2401760 · 2004 [cited by applicant]
WO 9941918 · 1999 [cited by applicant]
WO 0163856 · 2001 [cited by applicant]
WO 04042993 · 2004 [cited by applicant]
WO 04098222 · 2004 [cited by applicant]
WO 05078967 · 2005 [cited by applicant]
WO 06034747 · 2006 [cited by applicant]
WO 06067570 · 2006 [cited by applicant]
WO 06121262 · 2006 [cited by applicant]
WO 07024099 · 2007 [cited by applicant]
3GPP Support Team, “Draft2 minutes of the 58bis TSG-RAN WG2 meeting, (Orlando, USA, Jun. 25-29, 2007),” TSG-RAN WG2 meeting #59, R2-073623, Athens, Greece (Aug. 20-24, 2007). [cited by applicant]
3GPP Support Team, “Draft2 minutes of the 58th TSG-RAN WG2 meeting (Kobe, Japan, May 7-11, 2007),” TSG-RAN WG2 meeting #58bis, R2-072901, Orlando, USA (Jun. 25-29, 2007). [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
3GPP, 3 [cited by applicant]
China National Intellectual Property Adminsitration, Examination Decision on Request for Invalidation, Chinese Patent No. 200780031104.7 (Nov. 30, 2020). [cited by applicant]
China National Intellectual Property Adminsitration, Examination Decision on Request for Invalidation, Chinese Patent No. 201310189815.4 (Nov. 30, 2020). [cited by applicant]
European Telecommunications Standards Institute, “Universal Mobile Telecommunications System (UMTS); FDD Enhanced Uplink; Overall description; Stage 2 (3GPP TS 25.309 Version 6.1.0 Release 6)”, ETSI TS 125 309 V6.1.0 (D… [cited by applicant]
European Telecommunications Standards Institute, “Universal Mobile Telecommunications System (UMTS); Medium Access Control (MCA) Protocol Specification (3GPP TS 25.321 Version 6.9.0 Release 6)”, ETSI TS 125 321 V6.9.0 (… [cited by applicant]
Gozalvez, “First HSUPA Live Demonstrations,” IEEE Vehicular Technology Magazine, vol. 1, No. 4, pp. 60-65 (Dec. 2006). [cited by applicant]
Holma et al., HSDPA/HSUPA for UMTS: High Speed Radio Access for Mobile Communications, John Wiley & Sons, pp. 176-180, 205-213 (Apr. 2006). [cited by applicant]
Huawei, “Periodic triggering of Scheduling Information,” 3GPP TSG-RAN-WG2 Meeting #54, R2-062455, Tallinn, Esthonia (Aug. 28-Sep. 1, 2006). [cited by applicant]
Infineon, “Further clarifications on Scheduling Information,” 3GPP TSG-RAN WG2 Meeting #47, R2-051267, Athens, Greece (May 9-13, 2005). [cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
[cited by applicant]
Mobile Europe, “First HSUPA call using data card,” available at www.mobileeurope.co.uk/1665 (Oct. 11, 2006). [cited by applicant]
Nullity Action, Orope Germany GmbH Petition for Invalidity EP 2 421 318 B1 (Jun. 10, 2022). [cited by applicant]
Panasonic, “Content of E-AGCH,” 3GPP TSG-RAN WG2#46bis meeting, R2-050817, Beijing, China (Apr. 4-8, 2005). [cited by applicant]
phonearena.com, “Trial HSUPA handset to handset call completed,” available at www.phonearena.com/news/trial-HSUPA-handset-to-handset-call-completed_id1038 (Feb. 9, 2006). [cited by applicant]
Qualcomm et al., “Rate-request Proposal,” 3GPP TSG-RAN WG2 Meeting #45bis, R2-050179, Sophia Antipolis, France (Jan. 10-14, 2005). [cited by applicant]
Qualcomm Europe, “Addition of an SI trigger when UE grant <> 0 and at least one process is activated,” 3GPP TSG-RAN WG2 Meeting #59, R2-073822, Athens, Greece (Aug. 20-24, 2007). [cited by applicant]
Qualcomm Europe, “Handling of insufficient UE grant,” 3GPP TSG-RAN WG2 #59, R2-073430, Athens, Greece (Aug. 20-24, 2007). [cited by applicant]
Qualcomm, “Qualcomm Paves the Way for Next-Generation Services on HSUPA,” available at www.qualcomm.com/news/releases/2006/05/04/qualcomm-paves-way-next-generation-services-hsupa (May 4, 2006). [cited by applicant]
Qualcomm, “SI Transmission Triggering Schemes,” 3GPP TSG-RAN WG2 meeting #46bis, R2-050956, Beijing, China (Apr. 4-8, 2005). [cited by applicant]
Samsung, “Buffer Status Reporting Triggers for EDCH,” 3GPP TSG-RAN2 Meeting #46, R2-050346, Scottsdale, USA (Feb. 14-18, 2005). [cited by applicant]
Samsung, “Buffer Status Reporting Triggers for EDCH,” 3GPP TSG-RAN2 Meeting #46bis, R2-050835, Beijing, China (Apr. 4-8, 2005). [cited by applicant]
Third Generation Partnership Project, “ Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a UTRAN-based 3GPP system (Release 6),” 3GPP TS 21.101 V6.4.2 (Apr. 2… [cited by applicant]
Third Generation Partnership Project, “ Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a UTRAN-based 3GPP system (Release 6),” 3GPP TS 21.101 V6.7.0 (Jun. 2… [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Feasibility Study for Enhanced Uplink for UTRA FDD (Release 6),” 3GPP TR 25.896 V6.0.0 (Mar. 2004). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Networks; User Equipment (UE) radio transmission and reception (FDD) (Release 1999),” 3GPP TS 25.101 V3.18.0 (Sep. 2005). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Networks; User Equipment (UE) radio transmission and reception (FDD) (Release 1999),” 3GPP TS 25.101 V3.19.0 (Dec. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Networks; User Equipment (UE) radio transmission and reception (FDD) (Release 4),” 3GPP TS 25.101 V4.12.0 (Sep. 2005). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Networks; User Equipment (UE) radio transmission and reception (FDD) (Release 4),” 3GPP TS 25.101 V4.13.0 (Dec. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 5),” 3GPP TS 25.101 V5.20.0 (Dec. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 6),” 3GPP TS 25.101 V6.12.0 (Jun. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 6),” 3GPP TS 25.101 V6.14.0 (Dec. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 5),” 3GPP TS 25.101 V5.19.0 (Jun. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 7),” 3GPP TS 25.101 V7.4.0 (Jun. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD) (Release 7),” 3GPP TS 25.101 V7.8.0 (Jun. 2007). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical Channels and Modulation (Release 8),” 3GPP TS 36.211 V1.2.0 (Jun. 2007). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6),” 3GPP TS 25.301 V6.4.0 (Sep. 2005). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6),” 3GPP TS 25.301 V7.0.0 (Mar. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture (Release 6),” 3GPP TS 25.301 V7.2.0 (Jun. 2007). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 7),” 3GPP TS 25.321 V7.5.0 (Jun. 2007). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 7),” 3GPP TS 25.321, V7.6.0, (Sep. 2007). [cited by applicant]
Third Generation Partnership Project, Technical Specification Group Radio Access Network; Medium Access Control (MAC) Protocol Specification (Release 7), 3GPP TS 25.321, V6.2.0, (Jun. 2004). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 7),” 3GPP TS 25.211 V7.0.0 (Mar. 2006). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Physical channels and mapping of transport channels onto physical channels (FDD) (Release 7),” 3GPP TS 25.211 V7.2.0 (May 2007). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Technical Specifications and Technical Reports for a UTRAN-based 3GPP system (Release 6),” 3GPP TS 21.101 V6.4.1 (Jun. 20… [cited by applicant]
ZTE Corporation, “Consideration of RG-STEP Size in E-DCH,” 3GPP TSG-RAN WG2#58, R2-071749, Kobe, Japan (May 7-11, 2007). [cited by applicant]
ZTE Corporation, “Correction of Serving Grant update Procedure in E-DCH (Rel-6),” 3GPP TSG-RAN WG2#58, R2-071747, Kobe, Japan (May 7-11, 2007). [cited by applicant]
ZTE Corporation, “Correction of Serving Grant update Procedure in E-DCH (Rel-7),” 3GPP TSG-RAN WG2#58, R2-071748, Kobe, Japan (May 7-11, 2007). [cited by applicant]
ZTE Corporation, “The consideration on Serving Grant update Procedure and RG-STEP Size in E-DCH,” 3GPP TSG-RAN WG2#58bis, R2-072448, Orlando, USA (Jun. 25-29, 2007). [cited by applicant]