Disabling, using a designated process, hybrid automatic repeat request (HARQ) acknowledgments for packets for which acknowledgements are supported at network or higher layer
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.
1. A method of operating a first communications device which is a User Equipment (UE) device that includes a transmitter, the method comprising:
identifying a first packet flow for which end to end retransmission of packets is supported; and
assigning said first packet flow to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NACKs) from a device receiving data corresponding to said first packet flow, 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 HARQ process to which the first packet flow is assigned being used for an uplink (UL) transmission block (TB) transmitted in an uplink channel; and
transmitting data corresponding to said first packet flow to a second communications device, said second communications device being a base station device.
2. The method of claim 1 , wherein said HARQ process is a HARQ process for a TCP packet flow which supports end to end retransmission of packets, said HARQ process not supporting retransmission of data in response to a NACK and not requiring transmission of ACKs/NACKs from the receiving device to which data was transmitted.
3. The method of claim 2 , 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.
4. The method of claim 1 , wherein said HARQ process ID for the first packet flow is communicated in a RRC IE (Radio Resource Control Information Element).
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, to said second communications device.
8. A method of operating a first communications device including a transmitter, said first communications device being a base station, the method comprising:
identifying a first packet flow for which end to end retransmission of packets is supported, said first packet flow being a downlink packet flow;
assigning said first packet flow to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NACKs) from a device receiving data corresponding to said first packet flow;
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;
generating a radio resource control (RRC) message including a RRC information element (IE) identifying the K HARQ processes designated a No ACK/NACK expected, generating a RRC control message including 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;
transmitting said generated RRC message, including said RCC IE identifying the K HARQ processes designated as No ACK/NACK, to a second communications device, said second communications device being a user equipment (UE) device; and
transmitting data corresponding to said first packet flow to the second communications device.
9. The method of claim 8 , 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 the K number of HARQ processes designated as No HARQ ACK/NACK expected.
10. The method of claim 8 , wherein said HARQ process is a HARQ process for a TCP packet flow which supports end to end retransmission of packets, said HARQ process not supporting retransmission of data in response to a NACK and not requiring transmission of ACKs/NACKs from the receiving device to which data was transmitted.
11. The method of claim 10 , 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.
12. A first communications device, said first communications device being a User Equipment (UE) device comprising:
a transmitter; and
a processor configured to:
identify a first packet flow for which end to end retransmission of packets is supported;
assign said first packet flow to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NACKs) from a device receiving data corresponding to said first packet flow, 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 HARQ process to which the first packet flow is assigned being used for an uplink (UL) transmission block (TB) transmitted in an uplink channel; and
operate said transmitter to transmit data corresponding to said first packet flow to a second communications device, said second communications device being a base station device.
13. The first communications device of claim 12 , wherein said HARQ process is a HARQ process for a TCP packet flow which supports end to end retransmission of packets, said HARQ process not supporting retransmission of data in response to a NACK and not requiring transmission of ACKs/NACKs from the receiving device to which data was transmitted.
14. The first communications device of claim 12 , 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.
15. The first communications device of claim 12 , wherein said HARQ process ID for the first packet flow is communicated in a RRC IE (Radio Resource Control Information Element).
16. A non-transitory computer readable medium including computer executable instructions which when executed by a processor of a first communications device which is a User Equipment device cause the first communications device to perform the steps of:
identifying a first packet flow for which end to end retransmission of packets is supported;
assigning said first packet flow to a Hybrid Automatic Repeat Request (HARQ) process which does not require generation of acknowledgements (ACKs) or negative acknowledgements (NACKs) from a device receiving data corresponding to said first packet flow, 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 HARQ process to which the first packet flow is assigned being used for an uplink (UL) transmission block (TB) transmitted in an uplink channel; and
transmitting data corresponding to said first packet flow to a second communications device, said second communications device being a base station device.
17. The non-transitory computer readable medium of claim 16 , wherein said HARQ process is a HARQ process for a TCP packet flow which supports end to end retransmission of packets, said HARQ process not supporting retransmission of data in response to a NACK and not requiring transmission of ACKs/NACKs from the receiving device to which data was transmitted.
18. The non-transitory computer readable medium of claim 16 , 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.
19. The non-transitory computer readable medium of claim 16 , wherein said HARQ process ID for the first packet flow is communicated in a RRC IE (Radio Resource Control Information Element).