IP Library › Granted Patent US 11,664,932
Granted Patent B2
US 11,664,932 · App. 17/080,824 · Granted May 30, 2023

Disabling, using a designated process, hybrid automatic repeat request (HARQ) acknowledgments for packets for which acknowledgements are supported at network or higher layer

Inventors: Maulik Vaidya (Escondido, CA); Diwelawatte Pj Jayawardene (Centennial, CO); Amitav Mukherjee (Elk Grove, CA); Pratik Das (Centennial, CO)
Assignee: Charter Communications Operating, LLC
H04L1/1812H04L1/1829H04L1/1861H04L1/1864H04L47/34H04W72/23H04W80/06
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 11,664,932
App. No.
17/080,824
Filed
Oct 26, 2020
Granted
May 30, 2023
Kind
B2
Examiner
SHAH, SAUMIT
Art Unit
2414
USPC
370/329
Abstract

A first communications device including a transmitter, such as a base station or UE, identifies a first packet flow for which end to end packet retransmission is supported. The first communications device assigns said first packet flow to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said first packet flow; and transmits data corresponding to said first packet flow to a second communications device. In some embodiments, the HARQ process to which the first packet flow is assigned is a dedicated HARQ suppression process. In some embodiments, the HARQ process to which the first packet flow is assigned is a HARQ process which has been temporarily designated as a HARQ suppression process. HARQ suppression is applied for the first packet flow at a radio link layer and/or MAC layer.

Claims (64)

1. A method of operating a first communications device including a transmitter, the method comprising:

identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assigning, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression, said first communications device being said first end device; and

communicating data corresponding to said first packet flow over said radio link as part of communicating packets of said first packet flow between the first and said second end devices; and

wherein said HARQ process to which the first packet flow is assigned is to be used for a corresponding uplink (UL) transmission block (TB) transmitted in an uplink channel.

2. The method of claim 1 ,

wherein said first end device is a User Equipment (UE) device.

3. The method of claim 2 , wherein said HARQ process ID for the first packet flow is communicated in a RRC IE (Radio Resource Control Information Element).

4. The method of claim 3 ,

where the RRC IE indicates a HARQ process to be used for a corresponding transmission block (TB).

5. The method of claim 1 , further comprising:

designating K HARQ process IDs, corresponding to K HARQ processes, to be used to mean no ACK/NACK expected, said K HARQ processes to be used for transport blocks (TBs) on which HARQ is to be suppressed.

6. The method of claim 5 , further comprising:

generating a radio resource control (RRC) message including a RRC information element (IE) identifying the K HARQ processes designated a No ACK/NACK expected.

7. The method of claim 6 , further comprising:

transmitting said generated RRC message, including said RCC IE identifying the K HARQ processes designated as No ACK/NACK.

8. A method of operating a first communications device including a transmitter, the method comprising:

identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assigning, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression, said first communications device being one of said first end device and said base station; and

communicating data corresponding to said first packet flow over said radio link as part of communicating packets of said first packet flow between the first and said second end devices; and

wherein identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported includes identifying a first TCP packet flow between said first and second end devices; and

wherein said HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression is a HARQ process applied to communication of packets corresponding to the first packet flow over said radio link, said HARQ process not supporting retransmission of data in response to a NACK and not requiring transmission of ACKs/NACKs from a receiving device to which data was transmitted over said radio link; and

wherein a HARQ process which supports retransmission of data over said radio link is applied to packets of a packet flow which does not support end to end packet retransmission.

9. The method of claim 8 ,

wherein identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported includes identifying said first packet flow from a plurality of packet flows, some of said plurality of packet flows not supporting end to end retransmission of packets; and

wherein said HARQ process is a dedicated HARQ process for a flow for which suppression of ACK/NACK is required, said dedicated HARQ process for the flow not triggering generation of ACK/NACK at the physical layer.

10. A method of operating a first communications device including a transmitter, the method comprising:

identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assigning, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression; and

communicating data corresponding to said first packet flow over said radio link as part of communicating packets of said first packet flow between the first and said second end devices; and

wherein said first communications device is said base station;

wherein said first end device is a first user equipment (UE) device;

wherein said first packet flow is a downlink packet flow; and

wherein the method further comprising

generating a RRC control message including an RRC IE ‘HARQ process ID for suppression in downlink’, which communicates a value indicating which HARQ process IDs are to be used for Transport Blocks (TBs) in the downlink direction which do not require HARQ feedback to sender.

11. The method of claim 10 , wherein generating a RRC control message including an RRC IE ‘HARQ process ID for suppression in downlink’ includes:

including in said RRC message an RRC IE ‘HARQ process ID for suppression’ including a value indicating a K number of HARQ processes designated as No HARQ ACK/NACK expected.

12. A method of operating a first communications device including a transmitter, the method comprising:

identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assigning, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression; and

communicating data corresponding to said first packet flow over said radio link as part of communicating packets of said first packet flow between the first and said second end devices; and

wherein said first communications device is a first user equipment (UE) device which is said first end device;

wherein said first packet flow is an uplink packet flow; and

wherein the method further comprising

generating a RRC control message including an RRC IE ‘HARQ process ID for suppression in uplink’, which communicates a value indicating which HARQ process IDs are to be used in the uplink direction for Transport Blocks (TBs) identified to not require HARQ feedback from a receiver.

13. The method of claim 12 , wherein generating a RRC control message including an RRC IE ‘HARQ process ID for suppression in uplink’ includes:

including in said RRC message an RRC IE ‘HARQ process ID for suppression’ including a value indicating a K number of HARQ processes designated as No HARQ ACK/NACK expected.

14. A first communications device comprising:

a receiver;

a transmitter; and

a processor configured to control the first communications device to:

identify, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assign, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression, said first communications device being said first end device; and

operate said transmitter to transmit data corresponding to said first packet flow to the base station; and

wherein said HARQ process to which the first packet flow is assigned is to be used for a corresponding uplink (UL) transmission block (TB) transmitted in an uplink channel.

15. The first communications device of claim 14 , wherein the first end device is a User Equipment (UE) device; and

wherein said processor is configured to control the first communications device to operate said transmitter to transmit data corresponding to said first packet flow to the base station over said radio link.

16. The first communications device of claim 14 , wherein said processor is further configured to:

designate K HARQ process IDs, corresponding to K HARQ processes, to be used to mean no ACK/NACK expected, said K HARQ processes to be used for transport blocks (TBs) on which HARQ is to be suppressed.

17. A non-transitory computer readable medium including computer executable instructions which when executed by a processor of a first communications device cause the first communications device to perform the steps of:

identifying, at the first communications device, a first packet flow for which end to end retransmission of packets is supported between a first end device, located at a first end of the first packet flow, and a second end device, said second end device being located at a second end of the first packet flow;

assigning, at the first communications device, said first packet flow, which was identified, to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NAKs) from a device receiving data corresponding to said packet flow via a radio link extending between the first end device and a base station used in communicating packets in said first packet flow, said base station being a separate device which is separate from said first end device and said second end device, said step of assigning said first packet flow to a HARQ process including assigning said first packet flow to a HARQ process identified by a HARQ process ID which is designated as indicating a HARQ suppression, said first communications device being said first end device; and

communicating data corresponding to said first packet flow over said radio link as part of communicating packets of said first packet flow between the first and said second end devices; and

wherein said HARQ process to which the first packet flow is assigned is to be used for a corresponding uplink (UL) transmission block (TB) transmitted in an uplink channel.

Assignments (3)
SECURITY INTEREST Recorded Sep 22, 2022
From: CHARTER COMMUNICATIONS OPERATING, LLC; TIME WARNER CABLE ENTERPRISES, LLC
To: WELLS FARGO TRUST COMPANY, N.A.
Reel/Frame 061503/0937 →
SECURITY INTEREST Recorded Sep 22, 2022
From: CHARTER COMMUNICATIONS OPERATING, LLC; TIME WARNER CABLE ENTERPRISES, LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 061504/0307 →
SUPPLEMENTAL SECURITY AGREEMENT Recorded Aug 10, 2022
From: CHARTER COMMUNICATIONS OPERATING, LLC; TIME WARNER CABLE ENTERPRISES LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 061633/0069 →
Continuity (3)
Continuation 16112596 · Aug 24, 2018
Provisional Application 62713519 · Aug 1, 2018
Related Publication 20210044387A1 · Feb 11, 2021