Hybrid Automatic Repeat Request (HARQ) in Wireless Local Area Network (WLAN)
By introducing the Hybrid Automatic Repeat Request (HARQ) protocol between WLAN devices to implement memory management signaling, the reliability problem caused by interference during transmission of WLAN devices is solved, thereby improving the reliability of data transmission and link throughput.
Patent Information
- Application Number
- CN202080047354.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-06-30
- Filing Date
- 2020-07-01
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-07-01
AI Technical Summary
Existing wireless local area network (WLAN) devices are susceptible to interference during transmission and lack effective retransmission protocols to ensure data reliability. In particular, when the memory resources of the receiving STA are limited, existing technologies struggle to effectively manage HARQ transmissions.
The Hybrid Automatic Repeat Request (HARQ) protocol is introduced, which allows the receiving STA to control the enabling and disabling of HARQ transmissions by implementing memory management signaling between WLAN devices, and improves the reliability of data transmission by adding signaling to the physical layer header.
It improves the reliability of data transmission between WLAN devices, supports HARQ session establishment, reduces feedback overhead, increases retransmission flexibility, and dynamically switches between ARQ and HARQ protocols, thereby improving the overall link throughput.
Smart Images

Figure CN114556835B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 869,496 filed on July 1, 2019, U.S. Provisional Patent Application No. 62 / 869,512 filed on July 1, 2019, and U.S. Patent Application No. 16 / 917,605 filed on June 30, 2020. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field
[0003] The present disclosure relates generally to the field of wireless communications, and more particularly to implementing Hybrid Automatic Repeat Request (HARQ) in a Wireless Local Area Network (WLAN).
[0004] Related technical description
[0005] A wireless local area network (WLAN) may be formed by two or more WLAN devices (which may be referred to as stations (STAs)) that share a wireless communication medium using a common service setting. One or more of the WLAN devices (which may be referred to as access points (APs)) may establish a common service setting.
[0006] An AP is a STA that performs distributed system access functions in a WLAN.
[0007] The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a basic service set (BSS) managed by an AP. Each BSS is identified by a service set identifier (SSID) announced by the AP. The AP periodically broadcasts beacon frames to enable other STAs within the wireless range of the AP to establish or maintain a communication link with the WLAN.
[0008] Wireless communication between two WLAN devices (which may be referred to as a sender STA and a receiver STA) may be susceptible to interference or other challenges that impair the wireless communication medium. The wireless transmission from the sender STA may include error detection and redundancy information, which enables the receiver STA to detect or correct errors in the wireless transmission. If the error cannot be corrected, the receiver STA may request the sender STA to retransmit the data. For example, the receiver STA may send a feedback message (including an acknowledgment (ACK) or a negative acknowledgment (NACK)) to indicate whether the data was successfully received. The receiver STA and the sender STA may utilize a first retransmission protocol implemented in the WLAN. However, it may be desirable to support additional retransmission protocols.
[0009] Overview
[0010] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0011] One innovative aspect of the subject matter described in the present disclosure may be implemented in a method performed by an apparatus for implementing a hybrid automatic repeat request (HARQ) protocol in a first wireless local area network (WLAN) device. The method may include outputting a first HARQ frame for transmission to a second WLAN device. The method may include obtaining a first feedback message from the second WLAN device. The first feedback message may indicate whether the HARQ protocol is to be enabled. The method may include determining to enable the HARQ protocol based at least in part on the first feedback message indicating that the HARQ protocol is to be enabled. The method may include obtaining an indication of an amount of memory available at the second WLAN device for processing HARQ transmissions. The method may include outputting a second HARQ frame for transmission to the second WLAN device based at least in part on the amount of memory available at the second WLAN device for processing HARQ transmissions.
[0012] In some implementations, the first feedback message obtained from the second WLAN device may be a HARQ Block Acknowledgement (H-BA) message.
[0013] In some implementations, the first feedback message may include an indication that the HARQ protocol is to be enabled and an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0014] In some implementations, the method may include outputting a HARQ request to send (H-RTS) message for transmission to the second WLAN device prior to transmission of the first HARQ frame. The H-RTS message may include a request for an amount of memory available at the second WLAN device for processing the HARQ transmission. The method may include obtaining a HARQ clear to send (H-CTS) message from the second WLAN device in response to the transmission of the H-RTS message. The H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0015] In some implementations, the first feedback message and the H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0016] In some implementations, the method may include outputting the first HARQ frame for transmission to the second WLAN device based at least in part on an amount of memory available at the second WLAN device for processing the HARQ transmission indicated by the H-CTS message.
[0017] In some implementations, the method may include obtaining a management frame from the second WLAN device prior to transmission of the first HARQ frame.The management frame may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0018] In some implementations, the method may include obtaining a block acknowledgment setup message from the second WLAN device prior to transmission of the first HARQ frame. The block acknowledgment setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0019] In some implementations, the method may include obtaining a HARQ setup message from the second WLAN device prior to transmission of the first HARQ frame.The HARQ setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0020] In some implementations, the first feedback message may be a non-HARQ acknowledgment message. The method may include determining that the non-HARQ acknowledgment message indicates that a HARQ protocol is to be disabled and a non-HARQ protocol is to be enabled. The method may include outputting a non-HARQ frame for transmission to a second WLAN device.
[0021] In some implementations, the non-HARQ acknowledgment message may indicate that the second WLAN device does not have memory available to process the HARQ transmission.
[0022] In some implementations, the non-HARQ protocol may be an ARQ protocol and the non-HARQ frame may be an ARQ frame.
[0023] In some implementations, the method may include determining that a first feedback message obtained from the second WLAN device indicates a maximum number of HARQ transmissions per HARQ transmission opportunity (TXOP).
[0024] In some implementations, the method may include determining that a first feedback message obtained from the second WLAN device includes an indication of an amount of memory available at the second WLAN device for processing HARQ transmissions of a single HARQ stream or multiple HARQ streams.
[0025] In some implementations, the first feedback message may be an A-control message.The A-control message may include a HARQ status report (HSR) with an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0026] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a method performed by an apparatus for implementing a HARQ protocol in a first WLAN device. The method may include determining a HARQ acknowledgment strategy for HARQ transmissions in a HARQ transmission opportunity (TXOP). The method may include determining timing information for HARQ transmissions within the HARQ TXOP. The method may include outputting a first HARQ frame for transmission to a second WLAN device. A physical (PHY) layer header of the first HARQ frame may include at least a HARQ acknowledgment strategy. The method may include providing signaling from a PHY layer of the first WLAN device to a media access control (MAC) layer of the first WLAN device indicating timing information for HARQ transmissions within the HARQ TXOP.
[0027] In some implementations, the method may include encoding addressing information about the first HARQ frame, wherein the encoded addressing information may provide a means for deriving a MAC address of the first WLAN device and a MAC address of the second WLAN device. A PHY layer header of the first HARQ frame may include the encoded addressing information.
[0028] In some implementations, the addressing information may include one or more of a recipient identifier, a transmitter identifier, a basic service set (BSS) color, and an uplink flag.
[0029] In some implementations, the method may include determining hashed addressing information by hashing the addressing information with at least a portion of a BSS identifier (BSSID) to reduce collisions.A PHY layer header of the first HARQ frame may include the hashed addressing information.
[0030] In some implementations, a HARQ acknowledgment policy included in a PHY layer header of the first HARQ frame may indicate whether to enable a HARQ protocol and whether to request a HARQ block acknowledgment (H-BA) message from the second WLAN device.
[0031] In some implementations, the HARQ acknowledgment policy may further indicate whether to bypass the MAC layer of the second WLAN device when processing the first HARQ frame.
[0032] In some implementations, a method of determining timing information for HARQ transmissions within a HARQ TXOP may include determining, by a PHY layer of a first WLAN device, a start and end time of each HARQ transmission within the HARQ TXOP to determine an intermediate time period between HARQ transmissions within the HARQ TXOP.
[0033] In some implementations, the first HARQ frame may be associated with a first HARQ stream. The method may include, upon detecting a low latency communication associated with a different stream, determining, by a MAC layer of the first WLAN device, an intervening time period between HARQ transmissions within the HARQ TXOP for transmitting the low latency communication based at least in part on timing information of the HARQ transmissions within the HARQ TXOP.
[0034] In some implementations, the method may include outputting a low-latency communication for transmission during one of the intervening time periods between HARQ transmissions, and determining whether to delay one or more of the HARQ transmissions of the HARQ TXOP.
[0035] In some implementations, the method may include outputting an H-RTS message for transmission to the second WLAN device, the H-RTS message including a receiver address (RA) and a transmitter address (TA).
[0036] In some implementations, the method may include determining that a HARQ feedback message is not obtained in response to transmission of the first HARQ frame; and providing signaling from a PHY layer to a MAC layer of the first WLAN device to activate an acknowledgement timeout and implement an exponential backoff operation.
[0037] In some implementations, the method may include determining that a non-HARQ feedback message is obtained in response to transmission of the first HARQ frame. The method may include determining that the non-HARQ feedback message includes at least one member selected from a group including a frame duration indicator, a modulation and coding scheme (MCS) indicator, a number of spatial streams (NSS) indicator, a bandwidth (BW) indicator, a guard interval (GI) indicator, a target transmission time, a target retransmission channel, and a transmit power indicator. The method may include outputting a retransmission frame for transmission to a second WLAN device based on at least one member selected from a group including a frame duration indicator, an MCS indicator, an NSS indicator, a BW indicator, a GI indicator, a target transmission time, a target retransmission channel, and a transmit power indicator.
[0038] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a method performed by an apparatus for implementing a HARQ protocol in a second WLAN device. The method may include: determining an amount of memory available at the second WLAN device for processing HARQ transmissions associated with a first WLAN device; and determining whether to enable the HARQ protocol with the first WLAN device. The method may include: in response to determining that the HARQ protocol is to be enabled, outputting a HARQ feedback message indicating that the HARQ protocol is to be enabled for transmission to the first WLAN device; providing an indication of the amount of memory available at the second WLAN device for processing the HARQ transmission; and obtaining a first HARQ frame from the first WLAN device, wherein the first HARQ frame may be generated by the first WLAN device based at least in part on the amount of memory available at the second WLAN for processing the HARQ transmission.
[0039] In some implementations, the HARQ feedback message may be an H-BA message.
[0040] In some implementations, the HARQ feedback message may include an indication that the HARQ protocol is to be enabled and an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0041] In some implementations, the method may include obtaining an H-RTS message from the first WLAN device, wherein the H-RTS message may include a request for an amount of memory available at the second WLAN device for processing the HARQ transmission. The method may include outputting an H-CTS message for transmission to the first WLAN device in response to obtaining the H-RTS message, wherein the H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0042] In some implementations, the method may include outputting a management frame for transmission to the first WLAN device, wherein the management frame may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0043] In some implementations, the method may include outputting a block acknowledgment setup message for transmission to the first WLAN device, wherein the block acknowledgment setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0044] In some implementations, the HARQ feedback message may be an A-control message, wherein the A-control message may include the HSR with an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0045] In some implementations, the HARQ feedback message may be an H-BA message, where the H-BA message may include an indication of a maximum number of HARQ transmissions per HARQ TXOP.
[0046] In some implementations, the method of determining an amount of memory available at the second WLAN device for processing HARQ transmissions may include determining an amount of memory available at the second WLAN device for processing HARQ transmissions for a single HARQ stream or multiple HARQ streams.
[0047] In some implementations, the method of determining whether to enable a HARQ protocol with the first WLAN can be based at least in part on an amount of memory available at the second WLAN device for processing HARQ transmissions.
[0048] In some implementations, the method may include obtaining a second HARQ frame from the first WLAN device, wherein the second HARQ frame may be a first physical convergence layer protocol data unit (PPDU) including at least a first media access control protocol data unit (MPDU). The method of determining whether to enable a HARQ protocol with the first WLAN device may be based at least in part on whether at least a portion of the first MPDU is successfully received by the second WLAN device.
[0049] In some implementations, a method of determining whether to enable a HARQ protocol with a first WLAN device may include: obtaining a second HARQ frame from the first WLAN device, wherein the second HARQ frame may be a PPDU; determining a reception failure of one or more MPDUs of the PPDU; determining to disable the HARQ protocol with the first WLAN device based on the reception failure; and outputting a non-HARQ feedback message for transmission to the first WLAN device in response to determining to disable the HARQ protocol.
[0050] In some implementations, the non-HARQ feedback message may include a negative acknowledgement (N-ACK) message, where the N-ACK message may indicate to the first WLAN device that the HARQ protocol is to be disabled.
[0051] In some implementations, the N-ACK message may further indicate to the first WLAN device one or more parameters to be used to generate the retransmitted PPDU.
[0052] In some implementations, the method may include determining at least one member selected from a group including a target transmission time, a target retransmission channel, and a transmit power for retransmitting the PPDU. The non-HARQ feedback message may include at least one member selected from a group including a target transmission time, a target retransmission channel, and a transmit power for retransmitting the PPDU.
[0053] In some implementations, the method may include obtaining a retransmission PPDU from the first WLAN device, wherein the retransmission PPDU may be generated based on at least one member selected from a group including a target transmission time, a target retransmission channel, and a transmit power for the retransmission PPDU. The method may include outputting an acknowledgment message indicating that the second WLAN device successfully received the retransmission PPDU for transmission to the first WLAN device.
[0054] Another innovative aspect of the subject matter described in the present disclosure may be performed by a device for implementing a HARQ protocol in a first WLAN device. The device may include one or more interfaces and one or more processors. The one or more interfaces may be configured to output a first HARQ frame for transmission to a second WLAN device; obtain a first feedback message from the second WLAN device, the first feedback message indicating whether the HARQ protocol is to be enabled; and obtain an indication of the amount of memory available at the second WLAN device for processing HARQ transmissions. The one or more processors may be configured to determine that the HARQ protocol is to be enabled based at least in part on the first feedback message indicating that the HARQ protocol is to be enabled. The one or more interfaces may be configured to output a second HARQ frame for transmission to a second WLAN device based at least in part on the amount of memory available at the second WLAN device for processing HARQ transmissions.
[0055] In some implementations, prior to transmission of the first HARQ frame, the one or more interfaces may be configured to: output an H-RTS message for transmission to the second WLAN device, wherein the H-RTS message may include a request for an amount of memory available at the second WLAN device for processing the HARQ transmission; and obtain an H-CTS message from the second WLAN device in response to the transmission of the H-RTS message, wherein the H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0056] In some implementations, the one or more interfaces may be configured to output the first HARQ frame for transmission to the second WLAN device based at least in part on an amount of memory available at the second WLAN device for processing the HARQ transmission indicated by the H-CTS message.
[0057] In some implementations, prior to transmission of the first HARQ frame, the one or more interfaces may be configured to obtain a management frame from the second WLAN device, wherein the management frame may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0058] In some implementations, prior to transmission of the first HARQ frame, the one or more interfaces may be configured to obtain a block acknowledgment setup message from the second WLAN device, wherein the block acknowledgment setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0059] In some implementations, prior to transmission of the first HARQ frame, the one or more interfaces may be configured to obtain a HARQ setup message from the second WLAN device, wherein the HARQ setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0060] In some implementations, the first feedback message may be a non-HARQ acknowledgment message. The one or more processors may be configured to determine that the non-HARQ acknowledgment message indicates that a HARQ protocol is to be disabled and a non-HARQ protocol is to be enabled, and the one or more interfaces may be configured to output a non-HARQ frame for transmission to the second WLAN device.
[0061] In some implementations, the one or more processors may be configured to determine that the first feedback message obtained from the second WLAN device may indicate a maximum number of HARQ transmissions per HARQ TXOP.
[0062] In some implementations, the one or more processors may be configured to determine that the first feedback message obtained from the second WLAN device includes an indication of an amount of memory available at the second WLAN device for processing HARQ transmissions for a single HARQ stream or multiple HARQ streams.
[0063] Another innovative aspect of the subject matter described in the present disclosure may be performed by an apparatus for implementing a HARQ protocol in a first WLAN device. The apparatus may include one or more interfaces and one or more processors. The one or more processors may be configured to: determine a HARQ acknowledgment strategy for HARQ transmissions in a HARQ TXOP; determine timing information for HARQ transmissions within the HARQ TXOP; and provide signaling indicating timing information for HARQ transmissions within the HARQ TXOP from a PHY layer of the first WLAN device to a MAC layer of the first WLAN device. The one or more interfaces may be configured to output a first HARQ frame for transmission to a second WLAN device, wherein a PHY layer header of the first HARQ frame may include at least a HARQ acknowledgment strategy.
[0064] In some implementations, the one or more processors may be configured to encode addressing information regarding the first HARQ frame, wherein the encoded addressing information may provide a means for deriving a MAC address of the first WLAN device and a MAC address of the second WLAN device, and wherein a PHY layer header of the first HARQ frame may include the encoded addressing information.
[0065] In some implementations, the one or more processors may be configured to determine hashed addressing information by hashing the addressing information with at least a portion of the BSSID to reduce collisions, wherein the PHY layer header of the first HARQ frame may include the hashed addressing information.
[0066] In some implementations, the one or more processors may be configured to determine, by a PHY layer of the first WLAN device, a start and end time of each HARQ transmission within the HARQ TXOP to determine an intermediate time period between HARQ transmissions within the HARQ TXOP.
[0067] In some implementations, the first HARQ frame may be associated with a first HARQ stream, and in response to detecting a low-latency communication associated with a different stream, the one or more processors may be configured to determine, by a MAC layer of the first WLAN device, an intervening time period between HARQ transmissions within the HARQ TXOP for transmitting the low-latency communication based at least in part on timing information for the HARQ transmissions within the HARQ TXOP.
[0068] In some implementations, the one or more interfaces may be configured to output low latency communications for transmission during one of the intervening time periods between HARQ transmissions, and the one or more processors may be configured to determine whether to delay one or more of the HARQ transmissions of the HARQ TXOP.
[0069] In some implementations, the one or more interfaces can be configured to output an H-RTS message for transmission to the second WLAN device, where the H-RTS message can include the RA and the TA.
[0070] Another innovative aspect of the subject matter described in the present disclosure may be performed by a device for implementing a HARQ protocol in a second WLAN device. The device may include one or more interfaces and one or more processors. The one or more processors may be configured to determine the amount of memory available at the second WLAN device for processing HARQ transmissions associated with the first WLAN device; and determine whether to enable the HARQ protocol with the first WLAN device. The one or more interfaces may be configured to: in response to determining that the HARQ protocol is to be enabled, output a HARQ feedback message for transmission to the first WLAN device, wherein the HARQ feedback message may indicate that the HARQ protocol is to be enabled; provide an indication of the amount of memory available at the second WLAN device for processing HARQ transmissions; and obtain a first HARQ frame from the first WLAN device, wherein the first HARQ frame may be generated by the first WLAN device based at least in part on the amount of memory available at the second WLAN for processing HARQ transmissions.
[0071] In some implementations, the one or more interfaces may be configured to: obtain an H-RTS message from the first WLAN device, wherein the H-RTS message may include a request for an amount of memory available at the second WLAN device for processing the HARQ transmission; and output an H-CTS message for transmission to the first WLAN device in response to obtaining the H-RTS message, wherein the H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0072] In some implementations, the one or more interfaces may be configured to output a management frame for transmission to the first WLAN device, wherein the management frame may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0073] In some implementations, the one or more interfaces may be configured to output a block acknowledgment setup message for transmission to the first WLAN device, wherein the block acknowledgment setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0074] In some implementations, the one or more interfaces may be configured to obtain a second HARQ frame from the first WLAN device, wherein the second HARQ frame may be a PPDU including at least the first MPDU, and the one or more processors may be configured to determine whether to enable a HARQ protocol with the first WLAN device based at least in part on whether at least a portion of the first MPDU was successfully received by the second WLAN device.
[0075] In some implementations, the one or more interfaces may be configured to obtain a second HARQ frame from the first WLAN device, wherein the second HARQ frame may be a PPDU, and the one or more processors may be configured to determine a reception failure of one or more MPDUs of the PPDU; and determine to disable a HARQ protocol with the first WLAN device based on the reception failure. The one or more interfaces may be configured to output a non-HARQ feedback message for transmission to the first WLAN device in response to determining to disable the HARQ protocol.
[0076] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a method performed by an apparatus for implementing a HARQ protocol in a first WLAN device. The method may include outputting a first HARQ frame for transmission to a second WLAN device; and determining whether a first feedback message is obtained from the second WLAN device. The method may include: in response to obtaining the first feedback message, determining whether the first feedback message includes HARQ acknowledgment information or non-HARQ acknowledgment information; and in response to determining that the first feedback message includes HARQ acknowledgment information, outputting a second HARQ frame for transmission to the second WLAN device.
[0077] In some implementations, the first feedback message may be an H-BA message, wherein the H-BA message may include HARQ acknowledgment information, and the HARQ acknowledgment information may include one or more bitmaps.
[0078] In some implementations, the one or more bitmaps of the H-BA message may include at least one of one or more codeword level bitmaps and one or more MPDU level bitmaps.
[0079] In some implementations, the one or more codeword level bitmaps may provide a reception status of a codeword associated with the first HARQ frame, and the one or more MPDU level bitmaps may provide a reception status of an MPDU.
[0080] In some implementations, the codewords of each of the one or more codeword-level bitmaps may be identified by one or more starting codeword indexes.
[0081] In some implementations, the one or more codeword-level bitmaps may identify one or more codeword groups.
[0082] In some implementations, the method may include outputting a second HARQ frame for transmission to the second WLAN device based at least in part on one or more bitmaps included in the H-BA message.
[0083] In some implementations, the first feedback message may be an H-BA message having an M-BA (Multi-Station Block ACK) frame format, wherein the M-BA frame format may include a first indicator indicating that the first feedback message is an H-BA message.
[0084] In some implementations, the M-BA frame format may include a BA information field, where the BA information field may include at least the first indicator and one or more codeword level bitmaps of the H-BA message.
[0085] In some implementations, the BA information field may include one or more BA control fields, and each of the one or more BA control fields may include the first indicator.
[0086] In some implementations, the M-BA frame format may further include one or more C-BA (Compressed Block ACK) messages from one or more additional WLAN devices.
[0087] In some implementations, the M-BA frame format may further include at least one additional H-BA message from at least one additional WLAN device.
[0088] In some implementations, in response to determining that the first feedback message includes non-HARQ acknowledgment information, the method may include outputting a non-HARQ frame for transmission to the second WLAN device.
[0089] In some implementations, the non-HARQ frame may be a retransmission frame output using an automatic repeat request (ARQ) protocol for transmission to the second WLAN device.
[0090] In some implementations, the first feedback message obtained from the second WLAN device may be a C-BA message, wherein the C-BA message may include one or more MPDU level bitmaps.
[0091] In some implementations, the first feedback message obtained from the second WLAN device may be an N-ACK message, where the N-ACK message may indicate a reception failure of the first HARQ frame.
[0092] In some implementations, the N-ACK message may have an M-BA frame format, and the M-BA frame format may include a second indicator for indicating that the first feedback message is an N-ACK message, or a bit map with each bit set to zero to indicate that the first feedback message is an N-ACK message.
[0093] In some implementations, the M-BA frame format may include a BA information field, wherein the BA information field includes at least the second indicator.
[0094] In some implementations, in response to determining that the first feedback message is not obtained from the second WLAN device, the method may include: retransmitting the first HARQ frame to the second WLAN device; outputting a different HARQ frame for transmission to the second WLAN device, or outputting an H-BAR (HARQ block ACK request) message for transmission to the second WLAN device.
[0095] In some implementations, in response to determining that a first feedback message is not obtained from the second WLAN device within a time period after transmission of the first HARQ frame, the method may include: outputting an H-BAR message for transmission to the second WLAN device, wherein the H-BAR message may include an H-BA request or a HARQ reset request.
[0096] In some implementations, in response to the H-BAR message including an H-BA request, the method may include obtaining an H-BA message from the second WLAN device.
[0097] In some implementations, in response to the H-BAR message including a HARQ reset request, the method may include obtaining an ACK message from the second WLAN device, wherein the ACK message may acknowledge completion of the HARQ reset.
[0098] In some implementations, the H-BAR message may include a BAR control field with a third indicator indicating that the message type is an H-BAR message.
[0099] In some implementations, a method of outputting an H-BAR message for transmission to a second WLAN device may include outputting a multi-user (MU) BAR trigger frame including the H-BAR message.
[0100] Another innovative aspect of the subject matter described in the present disclosure can be implemented in a method performed by an apparatus for implementing a HARQ protocol in a second WLAN device. The method may include: obtaining a first HARQ frame from a first WLAN device; and determining whether to generate a first feedback message including HARQ acknowledgment information or non-HARQ acknowledgment information based at least in part on the first HARQ frame. The method may include, in response to determining that a first feedback message including HARQ acknowledgment information is to be generated, outputting the first feedback message including HARQ acknowledgment information for transmission to the first WLAN device.
[0101] In some implementations, the first feedback message may be an H-BA message, wherein the H-BA message may include HARQ acknowledgment information.
[0102] In some implementations, the H-BA message may include at least one of one or more codeword level bitmaps and one or more MPDU level bitmaps.
[0103] In some implementations, the method may include determining to generate an H-BA message based at least in part on determining that at least a portion of a codeword associated with a first HARQ frame was successfully received and a remaining portion of the codeword was not successfully received; and determining to enable a HARQ protocol.
[0104] In some implementations, the method may include: determining, based at least in part on the first HARQ frame, to disable a HARQ protocol; determining, in response to determining that the HARQ protocol is to be disabled, to generate a first feedback message including non-HARQ acknowledgment information; and in response to determining that the first feedback message including non-HARQ acknowledgment information is to be generated, outputting the first feedback message including the non-HARQ acknowledgment information for transmission to the first WLAN device.
[0105] In some implementations, the first feedback message including the non-HARQ acknowledgment information may be a C-BA message, where the C-BA message may include one or more MPDU level bitmaps.
[0106] In some implementations, the first feedback message including the non-HARQ acknowledgement information may be an N-ACK message, where the N-ACK message may indicate a reception failure of the first HARQ frame.
[0107] In some implementations, the N-ACK message may have an M-BA frame format, where the M-BA frame format may include a second indicator for indicating that the first feedback message is an N-ACK message, or a bit map with each bit set to zero to indicate that the first feedback message is an N-ACK message.
[0108] In some implementations, the M-BA frame format may include a BA information field, where the BA information field may include at least the second indicator.
[0109] In some implementations, the method may include obtaining an H-BAR message from the first WLAN device; and determining whether the H-BAR message includes an H-BA request or a HARQ reset request.
[0110] In some implementations, in response to determining that the H-BAR message includes an H-BA request, the method may include outputting the H-BA message for transmission to the first WLAN device.
[0111] In some implementations, in response to determining that the H-BAR message includes a HARQ reset request, the method may include performing a HARQ reset at the second WLAN device; and outputting an ACK message for transmission to the first WLAN device to acknowledge completion of the HARQ reset.
[0112] Another innovative aspect of the subject matter described in the present disclosure may be performed by a device for implementing a HARQ protocol in a first WLAN device. The device may include one or more interfaces and one or more processors. The one or more interfaces may be configured to output a first HARQ frame for transmission to a second WLAN device. The one or more processors may be configured to determine whether a first feedback message is obtained from a second WLAN device; and in response to obtaining the first feedback message, determine whether the first feedback message includes HARQ acknowledgment information or non-HARQ acknowledgment information. The one or more interfaces may be configured to output a second HARQ frame for transmission to a second WLAN device in response to determining that the first feedback message includes HARQ acknowledgment information.
[0113] In some implementations, in response to determining that the first feedback message includes non-HARQ acknowledgment information, the one or more interfaces may be configured to output a non-HARQ frame for transmission to the second WLAN device.
[0114] In some implementations, in response to determining that the first feedback message is not obtained from the second WLAN device, the one or more interfaces may be configured to: retransmit the first HARQ frame to the second WLAN device; output a different HARQ frame for transmission to the second WLAN device, or output an H-BAR message for transmission to the second WLAN device.
[0115] In some implementations, in response to determining that a first feedback message is not obtained from the second WLAN device within a time period after transmission of the first HARQ frame, the one or more interfaces may be configured to: output an H-BAR message for transmission to the second WLAN device, wherein the H-BAR message may include an H-BA request or a HARQ reset request.
[0116] In some implementations, in response to the H-BAR message including the H-BA request, the one or more interfaces may be configured to obtain the H-BA message from the second WLAN device.
[0117] In some implementations, in response to the H-BAR message including the HARQ reset request, the one or more interfaces may be configured to obtain an ACK message from the second WLAN device, wherein the ACK message may acknowledge completion of the HARQ reset.
[0118] Another innovative aspect of the subject matter described in the present disclosure may be performed by a device for implementing a HARQ protocol in a second WLAN device. The device may include one or more interfaces and one or more processors. The one or more interfaces may be configured to obtain a first HARQ frame from a first WLAN device. The one or more processors may be configured to determine, based at least in part on the first HARQ frame, whether to generate a first feedback message including HARQ acknowledgment information or non-HARQ acknowledgment information. The one or more interfaces may be configured to output a first feedback message including HARQ acknowledgment information for transmission to the first WLAN device in response to determining that a first feedback message including HARQ acknowledgment information is to be generated.
[0119] In some implementations, the one or more processors may be configured to determine to generate an H-BA message based at least in part on: determining that at least a portion of a codeword associated with a first HARQ frame was successfully received and a remaining portion of the codeword was not successfully received; and determining that a HARQ protocol is to be enabled.
[0120] In some implementations, the one or more processors may be configured to: determine, based at least in part on the first HARQ frame, to disable a HARQ protocol; and determine, in response to determining that the HARQ protocol is to be disabled, to generate a first feedback message including non-HARQ acknowledgment information. The one or more interfaces may be configured to, in response to determining that the first feedback message including non-HARQ acknowledgment information is to be generated, output the first feedback message including non-HARQ acknowledgment information for transmission to the first WLAN device.
[0121] In some implementations, the one or more interfaces may be configured to obtain an H-BAR message from the first WLAN device.The one or more processors may be configured to determine whether the H-BAR message includes an H-BA request or a HARQ reset request.
[0122] Aspects of the subject matter described in this disclosure may be implemented in a device, software program, system, or other means for performing any of the above-mentioned methods.
[0123] Details of one or more implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative sizes of the following drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS
[0125] Figure 1 Depicted is a system diagram of an example wireless local area network (WLAN) for implementing a retransmission protocol, such as a hybrid automatic repeat request (HARQ) protocol.
[0126] Figure 2Depicted are example HARQ transmissions for implementing a HARQ protocol.
[0127] Figure 3 Another example of a HARQ transmission for implementing a HARQ protocol is depicted.
[0128] Figure 4 Depicted is an example message flow diagram associated with a HARQ protocol.
[0129] Figure 5 Depicted are example automatic repeat request (ARQ) transmissions for implementing an ARQ protocol.
[0130] Figure 6 An example message flow diagram associated with the ARQ protocol is depicted.
[0131] Figure 7 A flow diagram with example operations performed by an apparatus in a first WLAN device for implementing a HARQ protocol is depicted.
[0132] Figure 8 A flow diagram with example operations performed by an apparatus in a first WLAN device for implementing a HARQ protocol is depicted.
[0133] Fig. 9 A flow diagram with example operations performed by means of a second WLAN device for implementing a HARQ protocol is depicted.
[0134] Fig.10 Another example of HARQ transmission for implementing a HARQ protocol using a block acknowledgment (ACK) message is depicted.
[0135] Fig.11 Depicted is an example Multi-STA Block ACK (M-BA) frame format for use in HARQ feedback messages.
[0136] Fig.12 An example negative ACK (N-ACK) with an M-BA frame format is depicted.
[0137] Fig.13 An example HARQ block ACK (H-BA) with an M-BA frame format is depicted.
[0138] Fig.14 An example A-Control frame having an M-BA frame format is depicted.
[0139] Fig.15 Depicted is an example frame format of a HARQ BA Request (H-BAR) trigger frame.
[0140] Fig.16Depicted are example downlink (DL) multi-user (MU) physical convergence layer protocol data units (PPDUs) that may include HARQ transmissions and non-HARQ transmissions.
[0141] Fig.17 Depicted are example trigger frames that may trigger an uplink (UL) MU PPDU that may include both HARQ transmissions and non-HARQ transmissions.
[0142] Fig.18 A flow diagram with example operations performed by an apparatus in a first WLAN device for implementing a HARQ protocol using a block ACK message is depicted.
[0143] Fig.19 A flow diagram with example operations performed by an apparatus in a second WLAN device for implementing a HARQ protocol using a block ACK message is depicted.
[0144] Fig. 20 A block diagram of an example wireless communication device is shown.
[0145] Fig.21A A block diagram of an example AP is shown.
[0146] Fig.21B A block diagram of an example STA is shown.
[0147] Fig. 22 A block diagram of an example electronic device for implementing aspects of the present disclosure is shown.
[0148] Like reference numbers and designations in the various drawings indicate like elements.
[0149] Detailed Description
[0150] The following description is directed to certain implementations in order to describe the innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. The examples in the present disclosure are based on wireless local area network (WLAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standards. However, the described implementations can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to one or more of the following: IEEE 802.11 standards, (Bluetooth) standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), global system for mobile communications (GSM), GSM / general packet radio service (GPRS), enhanced data GSM environment (EDGE), terrestrial trunked radio (TETRA), wideband CDMA (W-CDMA), evolution data optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, high speed packet access (HSPA), high speed downlink packet access (HSDPA), high speed uplink packet access (HSUPA), evolved high speed packet access (HSPA+), long term evolution (LTE), AMPS, or other known signals for communication within a wireless network, cellular network, or Internet of Things (IOT) network (such as, a system utilizing 3G, 4G, 5G or 6G or further implementations thereof).
[0151] A wireless local area network (WLAN) in a home, apartment, enterprise, or other area may include one or more WLAN devices. Each WLAN device may have a station (STA) interface, which is an addressable entity that shares a wireless communication medium with other STAs. An access point (AP) is a WLAN device that includes a STA interface and a distribution system access function. For the simplicity of the present disclosure, a WLAN device may be referred to as a STA, regardless of whether the WLAN device is an AP or a non-AP STA. A first WLAN device (acting as a sender STA) may communicate data to a second WLAN device (acting as a receiver STA) via a wireless channel. Due to the nature of wireless communication, a WLAN device may implement a retransmission protocol to provide reliable delivery of a media access control (MAC) protocol data unit (MPDU). In some aspects of the present disclosure, an MPDU may also be referred to as a frame. A physical convergence layer (PHY) protocol data unit (PPDU) may include one or more PHY service data units (PSDUs), each PSDU being addressed to one or more STAs. Each PSDU may include one or more MPDUs in the form of an MPDU or an aggregated MPDU (A-MPDU). In some aspects of the present disclosure, a PPDU may also be referred to as a packet. In some implementations, a PPDU may contain an MPDU or A-MPDU addressed to a recipient. In some implementations, the examples described in this disclosure apply to situations where a transmitted PPDU may contain more than one PSDU, each addressed to an independent recipient or generated by an independent transmitter.
[0152] A conventional retransmission protocol (which may be referred to as a baseline approach, or as an automatic repeat request (ARQ)) may use a first type of feedback message including an acknowledgment (ACK). In some implementations, the absence of an ACK may be interpreted as a negative acknowledgment (NACK). For example, the first type of feedback message may be referred to as a conventional ACK message type. The receiving STA may send a conventional ACK message to the sending STA to indicate whether the receiving STA has successfully received the frame. If the sending STA does not receive a conventional ACK message in response to the frame (such as by the expected time), the sending STA may retransmit the original frame. In some implementations, the sending STA may retransmit the frame at a lower data rate than the initial transmission to increase the likelihood of receiving the frame. In another retransmission protocol, the receiving STA may bundle ACKs or NACKs for multiple MPDUs in a block acknowledgment feedback message, where each MPDU may be sent in a separate frame or as an A-MPDU in a single frame. The block acknowledgment feedback message may be referred to as a block ACK message type. The block acknowledgment message type may indicate which MPDUs in the A-MPDU have been successfully received. The transmitting STA may retransmit those MPDUs that were not indicated as correctly received in the Block ACK feedback message.
[0153] Hybrid automatic repeat request (hybrid ARQ or HARQ) is another retransmission protocol. HARQ has previously been used in wide area wireless communication systems. HARQ uses a combination of error detection and error correction. HARQ transmissions may include error detection bits added to the data to be transmitted using an error detection (ED) code, such as a cyclic redundancy check (CRC). The error detection bits may be used by the receiving STA to determine whether it has correctly decoded the received HARQ transmission. Additionally, HARQ transmissions may utilize error correction techniques. For example, the original data may be encoded using a forward error correction (FEC) code. Both the original data and the parity bits may be sent in a HARQ transmission. The receiving STA may be able to use the parity bits to correct errors in the transmission, thereby avoiding retransmissions. When using a code that can perform both FEC and ED, such as a Reed-Solomon code and a low-density parity check (LDPC) code, the ED code may be omitted.
[0154] Another feature of HARQ is that the receiving STA can combine the first HARQ transmission with the second HARQ transmission. For example, if the receiving STA cannot correctly decode the first HARQ transmission (and cannot correct errors on the first HARQ transmission), the receiving STA can send a HARQ feedback message indicating that at least a portion of the first HARQ transmission was not correctly decoded. The HARQ feedback message is another type of feedback message that is different from the traditional ACK / NACK feedback message type and the block ACK feedback message type (which may also be referred to as a non-HARQ feedback message type). In response to receiving the HARQ feedback message, the transmitting STA may transmit a second HARQ transmission to the receiving STA to convey at least a portion of the first HARQ transmission that was not acknowledged. The combined HARQ transmission can be processed for decoding and error correction. The receiving STA can combine the second HARQ transmission with the first HARQ transmission so that the complete signal associated with the HARQ transmission can be decoded.
[0155] Implementing HARQ in WLAN can improve the reliability of wireless communication. However, because the WLAN device may not have previously implemented HARQ, the WLAN device may not recognize HARQ transmissions or HARQ feedback messages. The HARQ protocol for use in WLAN may involve some changes to the traditional HARQ concept and some changes to the WLAN retransmission concept.
[0156] The present disclosure provides several techniques for using HARQ on WLAN. The various implementations described in the present disclosure can be combined or modified for use with standard-compliant WLAN devices. Some implementations include signaling about HARQ capabilities, HARQ transmissions, and various types of acknowledgements that can be used.
[0157] In some implementations, the HARQ protocol may allow control of various aspects of memory management that are typically used to implement HARQ transmissions between a transmitting STA and a receiving STA. In some implementations, the receiving STA may control the amount of memory allocated for HARQ transmissions on a per PPDU or per transmission opportunity (TXOP) basis. For example, the receiving STA may provide an indication to the transmitting STA about the amount of memory available for processing HARQ transmissions. The transmitting STA may generate HARQ transmissions based on the memory availability at the receiving STA. The receiving STA may also control whether the HARQ protocol is enabled or disabled for a particular PPDU or TXOP (such as based on the amount of available memory). For example, the receiving STA may have little or no memory available for processing HARQ transmissions, and therefore the HARQ protocol may be disabled. In some implementations, the receiving STA may indicate the amount of memory allocated for HARQ transmissions on a per PPDU, per TXOP, per association, or per block ACK setup basis. The receiving STA may implement memory management signaling as part of the HARQ protocol between the receiving STA and the transmitting STA to allow the receiving STA to indicate whether to implement the HARQ protocol and the amount of memory available for HARQ transmissions.
[0158] In some implementations, signaling for the HARQ protocol may be added to the physical (PHY) layer header of the PPDU to implement HARQ transmission. In some implementations, the PHY header may be successfully received even when a large number, most or even all of the MPDUs of the PPDU are destroyed. This is because, in general, the PHY header is usually sent at a lower data rate than the PSDU portion that is usually sent at a higher data rate. Therefore, including signaling in the PHY header for the HARQ protocol can increase the probability of receiving HARQ signaling. In some implementations, HARQ request to send (H-RTS) and HARQ clear to send (H-CTS) messages may also be used to provide HARQ related information and signaling. In some implementations, for reasons similar to the HARQ protocol, signaling may be added to the PHY header of the PPDU to implement the automatic repeat request (ARQ) protocol.
[0159] In some implementations, the HARQ protocol may use a HARQ block ACK (H-BA) message (which may also be referred to as a hybrid block ACK message). The H-BA message may include one or more codeword level bitmaps, one or more MPDU level bitmaps, or both. In some implementations, the one or more codeword level bitmaps may indicate the reception status of a codeword (such as an LDPC codeword). For example, for each LDPC codeword, the codeword level bitmap may indicate the success or failure of decoding the LDPC codeword. In some implementations, the one or more codeword level bitmaps may indicate the reception status of a codeword group. For example, for each codeword group, the codeword level bitmap may indicate the success or failure of decoding the codeword group. In some implementations, the one or more MPDU level bitmaps may indicate the reception status of the MPDU. For example, for each MPDU, the MPDU level bitmap may indicate the success or failure of decoding the MPDU.
[0160] In some implementations, the H-BA message may be generated using a multi-STA block ACK (M-BA) frame format. Other messages, such as compressed block ACK (C-BA) and negative ACK (N-ACK), may also use the M-BA frame format. In some implementations, a HARQ block ACK request (H-BAR) message may be used to request an H-BA or request a HARQ reset.
[0161] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. Implementing a HARQ protocol in a WLAN may improve the reliability of data transmitted from a transmitting STA to a receiving STA. The HARQ protocol may support the establishment of a HARQ session between two WLAN devices. The HARQ protocol may enable the receiving STA to control whether to continue the HARQ process or revert to a non-HARQ retransmission scheme (such as an ARQ protocol). The HARQ protocol may support various HARQ signaling between the transmitting STA and the receiving STA and between the PHY layer and the MAC layer to improve retransmission operations in the WLAN. The HARQ protocol may reduce feedback overhead and increase the flexibility of retransmission by allowing STAs to dynamically switch between ARQ and HARQ protocols during frame exchange. The HARQ protocol may also allow multiplexing of frames using ARQ (such as multi-user frames) and frames using HARQ. In addition, the HARQ protocol may allow the transmitting STA to transmit an initial HARQ transmission at a relatively high data rate, which may improve overall link throughput compared to non-HARQ protocols. The HARQ protocol may improve the overall link throughput even when a signal-to-noise ratio (SNR) level at the receiving STA is lower than the estimated SNR level and the transmitting STA transmits a second HARQ transmission to the receiving STA in order to successfully decode the data.
[0162] Figure 1Depicted is a system diagram of an example WLAN for implementing a retransmission protocol, such as a HARQ protocol. Figure 1 A block diagram of an example wireless communication network 100 is included. According to some aspects, the wireless communication network 100 may be an example of a WLAN (such as a Wi-Fi network) (and will be referred to as WLAN 100 hereinafter). For example, WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of standards defined by the IEEE 802.11-2016 specification or a revision thereof (such as IEEE 802.11ax or IEEE 802.11be). WLAN 100 may include many wireless communication devices, such as an AP 102 having a wireless association with the AP 102 and multiple STAs 104. The IEEE 802.11-2016 specification defines a STA as an addressable unit. An AP is an entity that includes at least one STA and provides access to associated STAs via a wireless medium (WM) to access a distribution service (such as, another network 140). Therefore, the AP includes a STA and a distribution system access function (DSAF). In Figure 1 In the example of FIG. 1 , the AP 102 may be connected to a gateway device (not shown) that provides connectivity to another network 140. The DSAF of the AP 102 may provide access between the STA 104 and the other network 140. Although the AP 102 is described as an access point using an infrastructure mode, in some implementations, the AP 102 may be a traditional STA operating as an AP. For example, the AP 102 may be a STA capable of operating in a peer-to-peer mode or an independent mode. In some other examples, the AP 102 may be a software AP (SoftAP) operating on a computer system.
[0163] Each STA 104 may also be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, etc. STA 104 may represent a variety of devices, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, netbook computers, tablet computers, laptops, display devices (e.g., TVs, computer monitors, navigation systems, etc.), wearable devices, music or other audio or stereo equipment, remote control devices (“remote controls”), printers, kitchen or other home appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.
[0164] The AP 102 and associated STAs 104 may be referred to as a basic service set (BSS), which is managed by the corresponding AP 102. A BSS refers to one STA (such as an AP) that has established service settings and one or more STAs that have successfully synchronized service settings. Alternatively, a BSS may describe a set of STAs that have synchronized matching mesh service profiles. Figure 1 In the example architecture of 100, the BSS may be identified by a service set identifier (SSID) announced by an AP 102. The AP 102 may periodically broadcast a beacon frame ("beacon") to enable any STA 104 within the wireless range of the AP 102 to establish or maintain a corresponding communication link 106 (also referred to as a "Wi-Fi link" or "wireless link") with the AP. "Non-associated STAs" (not shown) may not be considered part of the BSS because they do not have a wireless session established at the AP 102. The various STAs 104 in the WLAN 100 may be able to communicate with external networks and each other via the AP 102 and the corresponding communication links 106. In order to establish a communication link 106 with the AP 102, each STA is configured to perform a passive or active scanning operation ("scan") on a frequency channel in one or more frequency bands (e.g., the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands). To perform passive scanning, the STA listens to beacons transmitted by the corresponding AP 102 at periodic time intervals, referred to as target beacon transmission times (TBTTs), measured in time units (TUs), where one TU is equal to 1024 microseconds (μs). To perform active scanning, the STA 104 generates probe requests and sequentially transmits these probe requests on each channel to be scanned and listens for probe responses from the AP 102. Each STA 104 can be configured to identify or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link with the selected AP.
[0165] Figure 1 Additionally shown is an example coverage area 108 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. Figure 1102, but the WLAN 100 may include multiple APs. As wireless networks become more common, the STA 104 may have the opportunity to select one of many BSSs within the range of the STA 104 or to select among multiple APs 102 that together form an extended service set (ESS) (including multiple connected BSSs). The extended network station associated with the WLAN 100 may be connected to a wired or wireless distribution system that allows multiple APs 102 to be connected in such an ESS. In this way, the STA 104 can be covered by more than one AP 102 and can be associated with different APs at different times for different transmissions. Additionally, after associating with the AP 102, the STA 104 may also be configured to periodically scan its periodic environment to find a more suitable AP to associate with it. For example, a STA 104 that is moving relative to its associated AP 102 may perform a "roaming" scan to find another AP with a more suitable network characteristic (such as a larger received signal strength indicator (RSSI)).
[0166] The AP 102 and the STA 104 may function and communicate (via corresponding communication links 106) according to the IEEE 802.11 family of standards (such as those defined by the IEEE 802.11-2016 specification or its revisions, including but not limited to 802.11aa, 802.11ah, 802.11aq, 802.11ay, 802.11ax, 802.11be, 802.11az, and 802.11ba). These standards define WLAN radio and baseband protocols for the physical (PHY) and media access control (MAC) layers. The AP 102 and the STA 104 transmit and receive packets (which may also be referred to as transmissions, communications, or wireless communications) to and from each other in the form of PPDUs. Each PPDU is a composite frame that includes a PLCP preamble and header (which may also be referred to as a PHY preamble and header) and a data field. The data field may include one or more PSDUs, which may include one or more MPDUs in the form of MPDUs or A-MPDUs. Each MPDU may include a MAC header.
[0167] The AP 102 and STA 104 in the WLAN 100 may transmit PPDUs on an unlicensed spectrum, which may be a portion of a spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some implementations of the AP 102 and STA 104 described herein may also communicate in other frequency bands, such as the 6 GHz band, that may support both licensed and unlicensed communications. The AP 102 and STA 104 may also be configured to communicate on other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.
[0168] Each frequency band may include multiple sub-bands or frequency channels. For example, PPDUs that comply with IEEE 802.11n, 802.11ac, 802.11ax, and 802.11be (which may also be referred to as Extremely High Throughput (EHT)) standard revisions may be transmitted on one or more of the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, each of which is divided into multiple 20 MHz channels. In this way, these PPDUs may be transmitted on a physical channel with a minimum bandwidth of 20 MHz. However, larger channels may be formed by channel bonding, channel aggregation, and the like. For example, PPDUs that comply with IEEE 802.11n, 802.11ac, 802.11ax, and 802.11be standard revisions may be transmitted on a physical channel with a bandwidth of 40 MHz, 80 MHz, 80+80 MHz, 160 MHz, 160+160 MHz, or 320 MHz by bonding two or more 20 MHz channels that may be continuously or non-contiguously allocated. For example, IEEE 802.11n describes the use of up to 2 channels (for a combined 40 MHz bandwidth) and defines a high throughput (HT) transmission format. IEEE 802.11ac describes the use of up to 8 channels (for a maximum combined 160 MHz bandwidth) and defines a very high throughput (VHT) transmission format. IEEE 802.11ax also supports up to a combined 160 MHz bandwidth (which can be a combination of 8 channels each with a width of 20 MHz). IEEE 802.11be can support up to a combined 320 MHz bandwidth (which is a combination of 16 channels each with a width of 20 MHz).
[0169] The AP 102 may be an example of a first WLAN device 110. Whether the first WLAN device 110 is an AP or a legacy STA, it may be referred to as a "sender STA" for the example HARQ process in this disclosure. The STA 104 may be an example of a second WLAN device 120, and may be referred to as a "receiver STA" in the example HARQ process in this disclosure. To be clear, in other example HARQ processes, the designation of the sender STA and the receiver STA may be reversed. In the example HARQ process, the first WLAN device 110 may send a HARQ transmission 116 to the second WLAN device 120, and the second WLAN device 120 may respond with a feedback message 126. In this disclosure, we describe examples of a PPDU that may contain an MPDU or an A-MPDU addressed to a receiver STA. The examples described in this disclosure may also be applicable to situations where the transmitted PPDU may contain more than one PSDU, each PSDU addressed to an independent receiver STA, or generated by an independent sender STA.
[0170] The first WLAN device 110 (as a transmitting device) may include a HARQ protocol unit 112 and a HARQ transmission unit 114. The HARQ protocol unit 112 may implement a HARQ protocol according to aspects of the present disclosure. The HARQ transmission unit 114 may prepare and communicate a HARQ transmission 116. The second WLAN device 120 (as a receiving device) may include a HARQ protocol unit 122, a HARQ receiving unit 123, and a HARQ feedback unit 124. The HARQ protocol unit 122 may implement a HARQ protocol according to aspects of the present disclosure. The HARQ receiving unit 123 may prepare, decode, and process the HARQ transmission 116. The HARQ feedback unit 124 may prepare and communicate feedback 126.
[0171] In some implementations, the HARQ protocol may allow a receiving STA (such as the second WLAN device 120) to control memory management aspects for HARQ transmissions between a sending STA (such as the first WLAN device 110) and a receiving STA. In some implementations, the second WLAN device 120 may control the amount of memory allocated to the HARQ transmission. The second WLAN device 120 may process one HARQ stream or multiple HARQ streams concurrently. Each HARQ stream (as well as other applications and processes executed at the second WLAN device 120) may utilize a portion of the memory available at the second WLAN device 120. In addition, in order to implement the HARQ protocol, the second WLAN device 120 may utilize additional memory to store information (such as, for example, codewords) associated with a failed portion of the HARQ transmission (such as a portion that was not correctly decoded). For example, in the HARQ stream, the second WLAN device 120 may store the information while the second WLAN 120 is waiting to receive a second HARQ transmission having information that can be combined with the stored information to decode the previously failed portion of the first HARQ transmission. In some implementations, for each code bit (such as an information bit or a parity bit) associated with an unsuccessfully decoded codeword, the second WLAN device 120 may store a log-likelihood ratio (LLR), which may take multiple bits. For example, storing an LLR for each code bit may take 5 bits. Therefore, the second WLAN device 120 may allocate storage of multiple bits (such as 5 bits) for each code bit. For a single HARQ stream, when LLR storage is used for each code bit, the second WLAN device 120 may allocate an amount of memory to process HARQ transmissions, which may be equal to a multiple (such as five times) of the payload of the corresponding PPDU. For multiple HARQ streams, when LLR storage is used for each code bit, the amount of memory that can be allocated for processing HARQ transmissions for multiple HARQ streams may be a multiple of the amount of memory allocated to a single HARQ stream. For example, if the second WLAN device 120 is processing eight HARQ streams, the second WLAN device 120 may receive up to eight PPDUs, each PPDU including an A-MPDU with a different MPDU (e.g., one or more MPDUs for each HARQ stream). The memory size for storing information of the PPDUs for eight HARQ streams (and therefore the amount of memory that may be allocated for the HARQ protocol) may be eight times the amount of memory allocated for a single HARQ stream, which may be unmanageable for a receiving STA. For a receiving AP, multiple STAs may send HARQ transmissions to the AP, and each STA may separately send HARQ transmissions for one HARQ stream or multiple HARQ streams, and therefore the memory requirements may also be unmanageable for the AP for similar reasons.
[0172] In some implementations, the second WLAN device 120 (as a receiving STA) may control the amount of memory allocated for each HARQ transmission of one or more HARQ streams. For example, the second WLAN device 120 may control the amount of memory allocated on a per PPDU or per TXOP basis to implement the HARQ protocol. In some implementations, the second WLAN device 120 may send a feedback message 116 (also referred to as a HARQ feedback message) (such as a HARQ acknowledgement (H-ACK) message) to the first WLAN device 110. The feedback message 116 may indicate the amount of memory available at the second WLAN device 120 for processing one or more HARQ transmissions (such as one or more HARQ PPDUs (such as Figure 2 )). In some implementations, the H-ACK may be a HARQ block ACK (H-BA), which may also be referred to as a hybrid block ACK. In some implementations, the H-BA may include an indicator (such as a plurality of bits) in a control field (such as an A-control field) indicating the amount of available memory. The amount of memory available for one or more HARQ streams may be indicated in one or more fields of the H-BA. For example, the amount of available memory may be formatted as HARQ stream 1, HARQ memory 1, HARQ stream 2, HARQ memory 2, and the like, where the memory may be expressed in multiples of bytes (or octets), the number of codewords, and the like. In some implementations, the H-BA may indicate the amount of memory available for each HARQ stream at the second WLAN device 120 by indicating the number of codewords that may be stored at the second WLAN device 120 for each HARQ stream. For example, the H-BA may indicate the number of LDPC codewords that may be stored at the second WLAN device 120 for each HARQ stream. The first WLAN device 110 (as a transmitting STA) may receive the H-ACK (such as an H-BA) and generate a HARQ transmission based on the amount of available memory at the second WLAN device 120 .
[0173] In some implementations, the second WLAN device 120 may indicate in a HARQ clear-to-send (H-CTS) message an amount of memory available for HARQ transmission on a per PPDU basis or a per TXOP basis (e.g., Figure 3). In some implementations, the second WLAN device 120 may indicate the amount of memory available for one or more HARQ streams in a HARQ status report (HSR) that may be included in the A-control field of the H-BA (which may be referred to as an A-control message). In some implementations, the A-control field may be present in the MAC header and may be 4, 8, 16, or 32 octets in length. In some implementations, in addition to the available memory, the HSR may also include signal-to-noise ratio (SNR) information, or a combination of a recommended quadrature amplitude modulation (QAM) and a recommended puncturing ratio for rate adaptation in HARQ in the next transmission or retransmission. Rate adaptation in HARQ may be used to improve a packet error rate (PER), or to reduce the core processing burden of a low-density parity check (LDPC) decoder (such as by suggesting a slower transmission rate).
[0174] In some implementations, the second WLAN device 120 may indicate the amount of memory available for HARQ transmission on a per-association basis. For example, during an association process between the second WLAN device 120 and the first WLAN device 110, the second WLAN device 120 may indicate the amount of memory that will be allocated for each HARQ transmission or for all HARQ transmissions (after the association process) in a management frame (such as an association request / response, a probe request / response, etc.). The indication may be included in an EHT capability element, a HARQ parameter, or a HARQ control element included in the management frame. Such an element may include all information / parameters related to the HARQ protocol (which may be referred to as HARQ control information), such as support / enablement, memory, HARQ mode (such as tracking combining, increased redundancy, HARQ feedback size, fast feedback mechanism support, maximum HARQ PPDU size support, etc.). In some implementations, a control field (such as a HARQ control field or element) included in a MAC header of a frame transmitted by the second WLAN device 120 may include one or more of these parameters. In some implementations, the control field may be carried in an HT control field of a frame or an EHT control field of a frame. In some implementations, the H-ACK frame may include a HARQ control field or element as described herein. The first WLAN device 110 may receive the frame (e.g., a frame including a HARQ control field or element) and determine an amount of memory to be allocated by the second WLAN device 120 for each HARQ transmission. The first WLAN 110 may generate each HARQ transmission (such as a HARQ PPDU) to be sent to the second WLAN device 120 based on the amount of available memory indicated in the most recently received frame including the HARQ control information.
[0175] In some implementations, the second WLAN device 120 may indicate the amount of available memory for HARQ transmissions during a block acknowledgement (which may be referred to as a block ACK or BA) setup message exchange. For example, the second WLAN device 120 may indicate the amount of memory allocated to HARQ transmissions associated with different MPDUs in a block ACK response message (sent in response to receiving a block ACK request message from the first WLAN device 110). For example, the block ACK response message may indicate that the same or different amounts of memory are to be allocated to different PPDUs. Each PPDU may include an A-MPDU having one or more MPDUs, and each PPDU may be associated with a different HARQ stream.
[0176] As described herein, the second WLAN device may indicate the amount of memory allocated for HARQ transmission on a per PPDU, per TXOP, per association, or per block ACK setup basis. In some implementations, the second WLAN device 120 may also use a HARQ feedback message (such as an H-ACK or H-BA message), an H-CTS message, a control frame, a management frame, or a block ACK setup message to specify the amount of memory allocated for HARQ transmission on a per traffic identifier (TID) basis or on a per access category (AC) basis. For example, the four ACs defined in the IEEE 802.11 family of standards are background (BK) traffic, best effort (BE) traffic, voice (VO) traffic, and video (VI) traffic. TIDs may be used to provide additional priority levels (such as for quality of service (QoS)) to the four ACs. For example, each of the BK, BE, VO, and VI traffic ACs may be associated with two TIDs to reach a total of eight TIDs (such as TID0-TID7). Since data sessions can be classified according to different ACs or TIDs, the HARQ transmission for each data session is also associated with the corresponding AC or TID. Therefore, in some implementations, the second WLAN device 120 can indicate the amount of memory (which can be the same or different) to be allocated to each of the different ACs or TIDs in one or more messages (such as HARQ feedback messages, H-CTS messages, management frames, control frames, or block ACK setup messages) transmitted to the first WLAN device 110. In some implementations, ADDBA request and ADDBA response can be example BA setup messages, which can be used to specify the amount of memory allocated for HARQ transmission on a per-TID basis or a per-AC basis. Additionally or alternatively, the STA can use HARQ setup messages (such as ADD HARQ request and ADD HARQ response).
[0177] In some implementations, the second WLAN device 120 may further indicate whether the HARQ protocol is to be enabled or disabled on a per-PPDU or per-TXOP basis. For example, the second WLAN device 120 may further indicate whether the HARQ protocol is to be enabled or disabled in a HARQ feedback message (such as an H-ACK or H-BA message) or in an H-CTS message. In some implementations, if the second WLAN device 120 indicates that the HARQ protocol is to be enabled for one or more transmissions (HARQ PPDUs) between the first WLAN device 110 and the second WLAN device 120, the second WLAN device 120 may also indicate (such as in a HARQ feedback message or an H-CTS message) an amount of memory to be allocated to the one or more HARQ transmissions, as described in the present disclosure. In some implementations, if the second WLAN device 120 indicates that the HARQ protocol is to be disabled for one or more transmissions between the first WLAN device 110 and the second WLAN device 120, the second WLAN device 120 may send a feedback message 116 (such as a negative acknowledgement (N-ACK or NACK) message) indicating to the first WLAN device 110 that the HARQ protocol is to be disabled for subsequent PPDUs and a different retransmission protocol (such as an ARQ protocol) is to be implemented. In some implementations, the transmission of any feedback (except H-ACK) in response to a HARQ transmission (such as an ACK frame, a C-BA frame, a multi-TID BA frame) may be considered as an indication to the first WLAN device 110 not to continue transmitting HARQ PPDUs to the second WLAN device 120 for a certain amount of time (such as for the remainder of the TXOP). In some instances, the second WLAN device 120 may have little or no memory available to process the HARQ transmission, and therefore the second WLAN device 120 may indicate to the first WLAN device 110 that the ARQ protocol is to be enabled. Instead of retransmitting only a portion of the MPDU to the second WLAN device 120, the ARQ protocol may retransmit the complete MPDU to the second WLAN device 120. Such indication of disabling the HARQ protocol and enabling the ARQ protocol may be provided by the second WLAN device 120 to the first WLAN device 110 by sending any feedback message that does not contain HARQ feedback, such as any message other than H-ACK or H-BA.
[0178] In some implementations, signaling for enabling the HARQ protocol may be added to the physical layer (PHY) header (which may also be referred to as a PHY layer header) of the PPDU. In some instances, the HARQ PPDU received by the second WLAN device 120 (as a receiving STA) from the first WLAN device 110 (as a transmitting STA) may include a corrupted MPDU. Since the MPDU is corrupted, the second WLAN device 120 may not be able to decode the MAC header information (such as the transmitter address (TA), the receiver address (RA), and the acknowledgment policy). Without the addressing information, the second WLAN device 120 may not know what device to respond to, and without the acknowledgment policy, the second WLAN device 120 may not know how to respond, such as whether to send an H-ACK message or a non-HARQ feedback message. When the second WLAN device 120 receives a corrupted MPDU (which may have been sent using a high MCS), the PHY header is usually received and successfully decoded (because it may have been sent using a low MCS). Thus, in some implementations, the first WLAN device 110 may include addressing information and an acknowledgment policy in a PHY header of a HARQ transmission (such as in a HARQ PPDU).
[0179] In some implementations, the first WLAN device 110 may generate and transmit a HARQ PPDU including addressing information in a PHY header. In some implementations, the first WLAN device 110 may translate a receiver address (RA) and a transmitter address (TA) included in a MAC header of an MPDU included in the PPDU into a receiver association identifier (RX AID), a transmitter association identifier (TX AID), and include the RX AID, the TX AID, and the BSS color in the PHY header of the HARQ PPDU. In some implementations, the first WLAN device 110 may include coded or randomized addressing information in the PHY header of the HARQ PPDU. For example, the first WLAN device 110 may hash the TX AID with a compressed BSSID to generate coded or randomized addressing information (or pseudo addressing information) about the PHY header. The compressed BSSID may be formed by a portion of the BSSID (such as a plurality of upper or lower bits of the BSSID). In some implementations, the compressed BSSID may be obtained as a function of the BSSID and may be equal to a 32-bit CRC calculated on the BSSID contained in the beacon frame transmitted by an AP (such as the first WLAN device 110) that is generating the HARQ PPDU or an AP associated to the second WLAN device 120 (where the second WLAN device 120 is generating the HARQ PPDU). Since the AID and the BSS color are not unique, encoding or randomizing the addressing information may further reduce the possibility of collisions. The second WLAN device 120 may know how the encoded or randomized address information is generated, such as based on an encoding or randomization scheme defined in the HARQ protocol, or based on information exchange with the first WLAN device 110. Therefore, the second WLAN device 120 may be able to decode and retrieve the addressing information (such as the TX AID) from the PHY header.
[0180] In some implementations, when the first WLAN device 110 and the second WLAN device 120 exchange H-RTS and H-CTS messages (such as to determine the amount of memory to be allocated to HARQ transmission), the devices may include RA and TA in the H-RTS and H-CTS messages. RA and TA may be MAC addresses having 48 bits, and MAC addresses generally do not cause conflict issues because MAC addresses are expected to be unique. In addition, the H-RTS and H-CTS message exchange may precede the HARQ transmission from the first WLAN device 110 to the second WLAN device 120, and thus the second WLAN device 120 may know in advance the addressing information of the device (the first WLAN device 110) that sent the HARQ transmission.
[0181] In some implementations, the first WLAN device 110 may generate and send a HARQ PPDU that includes an acknowledgment policy in a PHY header. For example, the first WLAN device 110 may include an indication (such as one bit) in the PHY header of the HARQ PPDU for requesting an H-ACK message from the second WLAN device 120. The indication in the PHY header may also indicate that the first WLAN device 110 supports the HARQ protocol and may also be used to enable or disable the HARQ protocol for HARQ transmission. For example, when the bit is equal to 1, the first WLAN device 110 may indicate to the second WLAN device that the HARQ protocol is to be enabled and that an H-ACK message may be requested. When the bit is equal to 0, the first WLAN device 110 may indicate to the second WLAN device that the HARQ protocol is to be disabled for the HARQ PPDU. In some implementations, when the second WLAN device 120 receives a HARQ PPDU indicating that the HARQ protocol is to be implemented and an H-ACK message is returned, the MAC layer at the second WLAN device 120 may be bypassed unless all information of the MPDU contained in the PPDU (such as a codeword) is successfully received and decoded.
[0182] As described herein, the first WLAN device 110 and the second WLAN device 120 may support multiple data sessions, and each data session may be associated with a TID or AC. In some implementations, the first WLAN device 110 and the second WLAN device 120 may generate and send a HARQ transmission that includes TID or AC information about each data session in a PHY header. When the device supports multiple data sessions, the TID or AC may be included in the PHY header, and there may be different TIDs or ACs associated with the multiple data sessions.
[0183] In some implementations, the second WLAN device 120 (as a receiving device) may also include signaling in the PHY header to implement the HARQ protocol. As described herein, signaling may be included in the PHY header because the PHY header is generally successfully received and decoded, even when the MAC information is corrupted. In some implementations, the second WLAN device 120 may include an indication (such as a bit) in the PHY header of the feedback message to indicate whether the packet it sends in response to the received PPDU is an H-ACK message or a block ACK information. For example, when the bit is equal to 1, it may indicate that the feedback message is an H-ACK message. In some implementations, based on the indication in the PHY header, when the first WLAN device 110 determines that the feedback message is an H-ACK message, the PHY layer of the first WLAN device 110 may process the H-ACK message and bypass the MAC layer. When the bit is equal to 0, it may indicate that the feedback message is a block ACK message. In some implementations, based on the indication in the PHY header, the PHY layer of the first WLAN device 110 may forward the block ACK message to the MAC layer.
[0184] In some implementations, the second WLAN device 120 may include RA and TA in the H-ACK message. RA and TA may be MAC addresses, and thus it may eliminate any conflicts for the H-ACK message. In some implementations, if the second WLAN device 120 receives RX AID and TX AID information from the first WLAN device 110 in the HARQ PPDU, the second WLAN device 120 may map RX AID and TX AID to RA and TA for use in the address field of the H-ACK message. In some implementations, instead of mapping RX AID and TX AID to RA and TA, the second WLAN device 120 may use RX AID and TX AID (which are included in the HARQ PPDU) in the H-ACK message.
[0185] In some implementations, when the second WLAN device 120 receives a HARQ PPDU including multiple MPDUs (such as A-MPDUs), the second WLAN device 120 may respond with a HARQ feedback message (such as an H-BA message) including one or more MPDU-level BA bit maps, or one or more codeword-level BA bit maps, or both. The MPDU-level BA bit map may indicate the reception status of one or more MPDUs, including the reception status of each MPDU received by the second WLAN device 120 in the HARQ PPDU. In some implementations, the H-BA may also include one or more codeword-level BA bit maps. Each codeword-level BA bit map may indicate the reception status of one or more codeword sets of the HARQ PPDU, wherein each codeword set is identified by a starting codeword index (or codeword start number) and optionally a codeword bit map (which may also be referred to as a CW bit map). In some implementations, if the MPDU-level BA bit map includes the reception status of the MPDU(s) contained in the codeword set, the second WLAN device 120 may not include the reception status of the codeword set, and vice versa. In some implementations, in a second HARQ PPDU sent to the second WLAN device 120, the first WLAN device 110 may include information (such as a codeword) for decoding the failed portion of the first HARQ PPDU, and may also include an additional MPDU (such as an MPDU that has not been previously sent to the second WLAN device 120). The second WLAN device 120 may receive the second HARQ PPDU and determine to respond with an H-BA message including one or more codeword-level BA bitmaps and one or more MPDU-level BA bitmaps. The one or more codeword-level BA bitmaps may be used to indicate successful and unsuccessful reception of a codeword, and the MPDU-level BA bitmap may be used to indicate successful and unsuccessful reception of an additional MPDU. In some implementations, the mapping between each bit of the codeword bitmap and the codeword set may be negotiable during association or during BA setup. For example, the mapping may specify that one bit of the codeword bitmap maps to one codeword, one bit of the codeword bitmap maps to two codewords, and so on. Furthermore, in some implementations, the codeword bit map may provide reception status information about the codeword set, or may include signaling for the codeword set (such as based on one or more bits of the codeword bit map).
[0186] In some implementations, signaling may be added to the PHY header of the PPDU to assist in implementing ARQ or HARQ retransmissions. In some implementations, the first WLAN device 110 may provide a PPDU (such as a HARQ PPDU or a non-HARQ PPDU) to the second WLAN device 120, and the second WLAN device 120 may determine that one or more MPDUs of the PPDU have not been successfully received and decoded. As described herein, the PHY header may be successfully received by the second WLAN device 120 even when reception of all MPDUs has failed. In some implementations, the second WLAN device 120 may use information included in the PHY header of the PPDU (such as TX AID, RX AID, acknowledgment policy, PPDU duration, MCS, NSS, etc.) to generate a negative (N) ACK (N-ACK) for the ARQ protocol. The N-ACK generated by the second WLAN device 120 may improve collision detection, avoid exponential backoff, enable fast link adaptation, and limit lost TXOPs, as will be described in Figure 5 and 6 Described in .
[0187] Figure 2 An example HARQ transmission for implementing a HARQ protocol is depicted. The HARQ process 200 may begin with a first HARQ transmission 210 from the first WLAN device 110 to the second WLAN device 120. The first HARQ transmission 210 (sometimes referred to as an initial transmission) may be an initial PPDU or packet in a HARQ exchange for a particular TXOP 275. The first HARQ transmission 210 may include a HARQ indicator (such as a bit, field, or subfield in a PHY header 211) to indicate that the transmission is a HARQ transmission. For example, a bit in the PHY header 211 may be set to 1 if the first HARQ transmission is a HARQ transmission, or the bit may be set to 0 if the first HARQ transmission is a non-HARQ transmission.
[0188] like Figure 1As described in the foregoing, the first HARQ transmission 210 may also include an indication of an acknowledgment policy. For example, the PHY header 211 may include an ACK policy indicator (such as a bit, field, or subfield in the PHY header 211) to indicate whether the first WLAN device 110 is enabling the HARQ protocol and requesting a HARQ feedback message (such as an H-ACK message 230 or an H-BA message) in response to the first HARQ transmission 210 (which may be a PPDU). The ACK policy indicator may also be used to indicate when the first WLAN device 110 is disabling the HARQ protocol and requesting a non-HARQ feedback message (such as an MPDU level acknowledgment or an MPDU level block acknowledgment or both) for the first HARQ transmission 210. In some implementations, the first WLAN device 110 may use the ACK policy indicator in certain scenarios to dynamically enable or disable the HARQ protocol and HARQ transmission. In these scenarios, due to the non-uniqueness of the identifier, more than one STA may respond to the first HARQ transmission 210. For example, the identifier (TX ID, RX ID, etc.) in the PHY header may enable an overlapping BSS (OBSS) STA to decode a PPDU (such as the first HARQ transmission 210) and generate a HARQ feedback message (such as, for example, an H-ACK or H-BA message). As a result, two STAs (the intended recipient, and the OBSS STA that is expecting a PPDU with the same identifier from its OBSS peer STA) may respond to the PPDU at the same time (such as within a SIFS period after receiving the PPDU), resulting in a collision. In some implementations, if a collision is detected (such as if an H-ACK message is received from a different STA in the OBSS with the same AID (or other identifier or addressing information)), or if an H-ACK message is not received and the first WLAN device 110 determines that the reception failure may be due to a collision (such as the types of collisions described herein), the first WLAN device 110 may disable HARQ transmission. The first WLAN device 110 may then assign a replacement identifier or addressing information to the second WLAN device 120 such that the conflict event is mitigated (such as by assigning another ID to the second WLAN device 120, or changing (or requesting a change to) the ID of the first WLAN device 110, etc.
[0189] In response to the first HARQ transmission 210, the second WLAN device 120 may send an H-ACK message 230 (such as an H-BA message) back to the first WLAN device 110. The H-ACK message 230 may start after a short interframe space (SIFS) 220, which represents a determinable time period for maintaining synchronization in the WLAN. The H-ACK message 230 may include an H-ACK indicator (such as a bit, field, or subfield in the PHY header 211) to indicate whether the ACK is an H-ACK message or a non-HARQ ACK message. Figure 1 As described in , the H-ACK message may also include memory management information (such as in a control field of the H-ACK message) to indicate the amount of memory (or remaining memory, or both) allocated by the second WLAN device 120 for processing HARQ transmissions (such as the second HARQ transmission 240). In some implementations, the second WLAN device 120 may also control the number of HARQ PPDUs that may be transmitted within a TXOP (such as TXOP 275). For example, in addition to the initial PPDU (such as the first HARQ transmission 210), one or more additional HARQ PPDUs may be transmitted from the first WLAN device 110 to the second WLAN device 120 during a particular TXOP to attempt to decode and recover the failed portion of the initial PPDU. The H-ACK message 230 may include a PPDU indicator in the control field to indicate the maximum number of PPDUs (such as a maximum number of two PPDUs) that may be transmitted within the TXOP. In some implementations, the second WLAN device 120 may determine that it has a limited amount of memory or no memory available to process further HARQ transmissions, and therefore the second WLAN device 120 may include an indication in the H-ACK message 230 (or alternatively send a non-HARQ ACK, such as an MPDU level ACK, an N-ACK, or an MPDU level BA) to indicate to the first WLAN device 110 that an ARQ protocol is to be used (such as by retransmitting one or more MPDUs from the initial PPDU) rather than using a HARQ protocol (retransmitting one or more codewords from the initial PPDU).
[0190] In response to receiving the H-ACK message 230, the first WLAN device 110 may send a second HARQ transmission 240 to the second WLAN device 120 (such as after a SIFS period). The second HARQ transmission 240 may represent a retransmission 242 of at least a portion of the first HARQ transmission 210 or information (such as a codeword) to be used to attempt to decode and recover the failed portion of the first HARQ transmission 210. Similar to the first HARQ transmission 210, the second HARQ transmission 240 may also include a HARQ indicator and an ACK policy indicator (such as in a PHY header). In some implementations, the second HARQ transmission 240 may include a shorter PHY header than the first HARQ transmission 210. For example, the second HARQ transmission 240 may not include an identifier and other redundant information that has been included in an initial transmission (such as the first HARQ transmission 210). As an example, an initial HARQ PPDU (such as the first HARQ transmission 210) may include a SIG field with HARQ parameters (identifiers), and a second HARQ PPDU (such as the second HARQ transmission 240) may not include the SIG field.
[0191] After the second HARQ transmission 240, when the second WLAN device 120 has successfully recovered the MPDU from the first HARQ transmission, or when the maximum number of PPDUs has been transmitted within the TXOP 275, the second WLAN device 120 may send an MPDU level ACK or MPDU level block ACK message 250 (such as after a SIFS period). In some implementations, the response message may not contain a codeword level BA bit map. Figure 2 In the example shown in , an ACK or block ACK message 250 may complete the HARQ process 200 .
[0192] In some implementations, the first WLAN device 110 (and the second WLAN device 120) may implement signaling between the PHY layer and the MAC layer to allow the MAC layer to perform traffic prioritization and scheduling during a TXOP, such as TXOP 275. When processing a HARQ sequence, which may be one or more HARQ PPDUs for the same payload (and ending with an ACK or BA), the MAC layer typically instructs the PHY to start HARQ transmissions for the TXOP, such as TXOP 275, later, and the PHY layer reports back to the MAC layer after the entire HARQ sequence has ended, or after each PPDU transmission or reception end time, or both. The latter may be beneficial because it provides the MAC with an opportunity to prioritize the PPDUs sent within the TXOP, thereby allowing higher priority traffic to be delivered. For example, the PHY layer may provide an indication or estimate of the transmit start and end times (TX START and END) and receive start and end times (RX START and END) of the various PPDUs exchanged during TXOP 275. By having an indication or estimate of the timing of the intermediate time periods 222 between the PPDUs of the TXOP 275, the MAC layer can perform traffic prioritization and scheduling for both HARQ and non-HARQ PPDUs. For example, the MAC layer can detect a low-latency transmission 280 that has a higher priority than a HARQ transmission (such as during the transmission of the first HARQ transmission 210). The MAC layer can determine the timing of the first intermediate time period 222 after the first HARQ transmission 210 ends, and can start transmitting the low-latency transmission 280 at the beginning of the intermediate time period 222. In some scenarios, transmitting the low-latency transmission 280 may take longer than the intermediate time period 222, and thus the MAC layer may delay the remaining HARQ transmissions in order to prioritize the scheduling of the low-latency transmission 280. In some implementations, the MAC layer may suspend the HARQ transmission (e.g., by transmitting a PPDU containing low-latency traffic (such as the low-latency transmission 280) or by transmitting a HARQ suspend message (which may also be sent over the air to the peer device to indicate that the HARQ transmission is to be suspended)).
[0193] In some implementations, if an H-ACK message (such as H-ACK message 230) is not received from the second WLAN device 120, the PHY layer may provide an indication to the MAC layer. The MAC layer may then implement an ACK timeout, which may trigger an exponential backoff countermeasure in the presence of a conflict. In some implementations, the PHY layer may provide an indication to the MAC layer when an H-ACK message should be generated, and the MAC layer may provide a parameter (such as a TXVECTOR parameter) to the PHY layer. In some implementations, the PHY layer may provide information to the MAC layer about SIFS, point coordination function (PCF) interframe space (PIFS), and enhanced distributed channel access (EDCA) contention between PPDUs and HARQ PPDUs in a TXOP (such as TXOP 275). This may allow the MAC layer to determine the timing of the TXOP duration and the intermediate time periods (such as the intermediate time period 222), which may allow the MAC layer to schedule both HARQ and non-HARQ PPDUs and truncate excess TXOPs. Fig.10 Additional options and examples regarding traffic prioritization and scheduling, as well as PHY and MAC layer signaling and interaction are described in .
[0194] Figure 3 Another example of a HARQ transmission for implementing a HARQ protocol is depicted. The HARQ process 300 may begin with the first WLAN device 110 sending a HARQ request to send (H-RTS) message 302 to the second WLAN device 120 to request the second WLAN device 120 to grant permission to initiate a HARQ sequence or to indicate the amount of available memory it will allocate for processing HARQ transmissions, or both. For example, the first WLAN device 110 may include an indication (such as one or more bits in a control field) in the H-RTS message 302 to request the amount of available memory from the second WLAN device 120. Alternatively or additionally, the device may indicate the amount of memory it requests the second WLAN device 120 to allocate. The second WLAN device 120 may send an H-CTS message 304 with an indication (such as one or more bits in a control field) of the amount of available memory the second WLAN device 120 will allocate for processing HARQ transmissions. The second device may also indicate that it has no memory allocated for HARQ transmissions. The first WLAN device may then generate and send HARQ transmissions (such as the first HARQ transmission 210 and the second HARQ transmission 240) based on the available memory at the second WLAN device 120. The second WLAN device 120 may also generate and send HARQ transmissions (such as the first HARQ transmission 210 and the second HARQ transmission 240) based on the available memory at the second WLAN device 120. Figure 3 375) during the transmission of an H-ACK message 230 (such as an H-BA message) and an ACK or Block ACK message 250, similar to Figure 2As described in , wherein the message also includes an indication of the remaining memory allocated for HARQ transmission.
[0195] In some implementations, the first WLAN device 110 may send an H-RTS message 302 indicating to the second WLAN device 120 that it will send a HARQ PPDU with a first maximum amount of memory (such as, for example, a maximum of 6MB). The second WLAN device 120 may determine that the amount of available memory it will allocate for processing the HARQ transmission is a second amount of memory (such as, for example, 2MB) that is less than the first maximum amount of memory. Therefore, the second WLAN device 120 may respond with an H-CTS message 304 that accepts the request for the HARQ transmission but limits the amount of memory associated with the HARQ transmission to 2MB (which is the maximum amount of available memory that the second WLAN device 120 will allocate for processing the HARQ transmission). As described herein, the first WLAN device 110 may generate and send a first HARQ transmission 210 and a second HARQ transmission 220 that conform to the memory limit specified by the second WLAN device 120.
[0196] In some implementations, the first WLAN device 110 may generate and send the first HARQ transmission 210 based on the amount of available memory indicated in the H-CTS 304, and the second WLAN device 120 may re-evaluate the amount of memory available for processing the HARQ transmission when preparing the H-ACK message 230. In some implementations, the second WLAN device 120 may indicate a different amount of available memory allocated for processing the HARQ transmission in the H-ACK message 230 (compared to the H-CTS 304), and the first WLAN device may generate and send the second HARQ transmission 240 using this updated amount. For example, the first WLAN device 110 may truncate the HARQ PPDU by cutting off a portion of the codeword that is not stored at the receiving side (such as the second WLAN device 120). For example, if the initial HARQ PPDU has a payload of 2MB, and the second WLAN device 120 indicates an amount of memory of 1MB in the H-ACK message, the second HARQ PPDU may be truncated to the 1MB payload (the lowest portion) and the second 1MB (the upper portion) may be discarded. like Figure 2 As described in , exchanging H-RTS and H-CTS messages may also allow addressing information (such as RA and TA) for subsequent HARQ transmissions to be exchanged and established.
[0197] Figure 4An example message flow diagram associated with a HARQ protocol is depicted. The example message flow 400 shows a first WLAN device 110 (as a transmitting STA) and a second WLAN device 120 (as a receiving STA). The first WLAN device 110 and the second WLAN device 120 may optionally exchange control messages 405 (such as H-RTS and H-CTS messages) for determining an amount of available memory to be allocated for processing HARQ transmissions (and also for establishing addressing information for subsequent HARQ transmissions).
[0198] In process 414, the first WLAN device 110 may encode and buffer a first data set for a HARQ sequence. The first HARQ transmission 422 may include an MPDU or multiple MPDUs or segments of the first data set. The first WLAN device 110 may also determine information to include in a PHY header of the first HARQ transmission 422, such as an ACK policy, such as Figure 1 and 2 In process 432, the second WLAN device 120 may receive and process the first HARQ transmission 422 from the first WLAN device 110. The second WLAN device 120 may also determine information to include in the H-ACK message 434, such as Figure 1 and Figure 2 For example, the second WLAN device 120 may determine an amount of available memory to be allocated for HARQ transmission. The second WLAN device 120 may send an H-ACK message 434 (such as an H-BA message) to the first WLAN device 110. In process 442, the first WLAN device 110 may process the H-ACK message 434 received from the second WLAN device 120, such as Figure 1 and Figure 2 Described in .
[0199] The first WLAN device 110 may generate and send a second HARQ transmission 462. In some implementations, the H-ACK message 434 may include feedback information regarding which portions of the first HARQ transmission 422 were not successfully decoded. Based at least on the feedback information, the first WLAN device 110 may prepare the second HARQ transmission 462.
[0200] At process 464, after the second HARQ transmission 462, the second WLAN device 120 may use information from the second HARQ transmission 462 to decode and recover the previously failed remainder of the first HARQ transmission 422. The second WLAN device 120 may then send an MPDU level ACK or MPDU level block ACK message 468 to the first WLAN device 110, which may end the HARQ sequence.
[0201] Figure 5 An example ARQ transmission for implementing an ARQ protocol is depicted. The ARQ process 500 may begin with a first ARQ transmission 510 from the first WLAN device 110 to the second WLAN device 120. For example, the first ARQ transmission 510 may include at least one or more MPDUs and a PHY header (such as Figure 5 510). As described in the present disclosure, the PHY header is generally successfully received even when one or more MPDUs of the PPDU are not successfully received. Therefore, similar to the HARQ process described in the present disclosure, the first WLAN device 110 may include information in the PHY header 511 of the first ARQ transmission 510, which may be used to improve the ARQ process 500 (such as by improving collision detection, performing fast link adaptation, avoiding performing unnecessary exponential backoff, and limiting lost TXOPs). The first ARQ transmission 510 may include a TX AID, an RX AID, an ACK policy indicator, a PPDU duration indicator, a modulation and coding scheme (MCS) indicator, a number of spatial streams (NSS) indicator, a bandwidth (BW) indicator, a guard interval (GI) indicator, and an FEC indicator, etc. Although these concepts and examples are described for ARQ, in some implementations, these concepts and examples may also be valid for HARQ.
[0202] The second WLAN device 120 may determine that all MPDUs of the PPDU associated with the first ARQ transmission 510 are corrupted or failed to be received. However, the second WLAN device 120 may successfully receive and recover the PHY header 511. After SIFS 220, the second WLAN device 120 may send an N-ACK message 530 to the first WLAN device 110 indicating that the entire PSDU (such as one or more MPDUs) has failed to be correctly received. Since the second WLAN device 120 received and recovered the PHY header 511, the second WLAN device 120 may determine that there is no collision, and may provide the first WLAN device 110 with a recommendation or requirement in the N-ACK message 530 for certain parameters to be used by the first WLAN device 110 in the retransmission 542 to improve the chance that the second WLAN device 120 receives the retransmitted (Re-TX) first ARQ transmission 540 or subsequent transmissions. For example, the second WLAN device 120 may determine that the MCS for the PSDU of the first ARQ transmission 510 is an aggressive MCS. Therefore, the second WLAN device 120 may include in the N-ACK message 530 an indication that a lower MCS is to be used for retransmission 542 (e.g., from the aggressive MCS9 to the lower MCS2). As another example, the second WLAN device 120 may also suggest increasing the GI, decreasing the NSS, decreasing the BW of the PPDU, etc. In some implementations, this information (such as an indication of decreasing the MCS, increasing the GI, decreasing the NSS, decreasing the BW, etc.) may also be included in other types of feedback messages (such as block ACK, ACK, H-BA, etc.).
[0203] In some implementations, the second WLAN device 120 may also include in the N-ACK message 530 a recommended target transmission time, one or more frequency channels, and a transmit power (such as for fast link adaptation) for the retransmission 542. For example, the second WLAN device 120 may indicate that a channel in the upper portion of the frequency band is to be used because the primary channel of the device (where the first ARQ transmission 510 is sent) in the lower portion of the frequency band is not suitable for use due to interference and ongoing traffic. The second WLAN device 120 may also be aware of concurrent OBSS transmissions that may cause interference and may indicate in the N-ACK message 530 a recommended transmission time (which may correspond to the time when the OBSS transmission will end) and the channel that the OBSS transmission is using. The second WLAN device 120 may also recommend in the N-ACK message 530 a transmit power adjustment (or a specific transmit power) to increase the likelihood of reception with limited interference.
[0204] The first WLAN device 110 may receive the N-ACK message 530 from the second WLAN device 120 and determine to retransmit the first ARQ transmission to the second WLAN device 120 (send Re-TX first ARQ transmission 540). Since the first WLAN device 110 receives the N-ACK message 530 (such as within the ACK timeout period), the first WLAN device 110 may determine that there is no collision and therefore may not perform exponential backoff countermeasures. The first WLAN device 110 may then use the recommended information in the N-ACK message 530 to generate and send the Re-TX first ARQ transmission 540. The second WLAN device 120 may successfully receive the Re-TX first ARQ transmission 540 and may then send an ACK or block ACK message 550. The ACK or block ACK message 550 may be the last transmission sent within the TXOP 575 and may be the end of the ARQ process 500, such as Figure 5 shown.
[0205] Figure 6 An example message flow diagram associated with an ARQ protocol is depicted. The example message flow 600 shows a first WLAN device 110 (as a transmitting STA) and a second WLAN device 120 (as a receiving STA).
[0206] In process 614, the first WLAN device 110 may encode and buffer a first data set for an ARQ process. The first ARQ transmission 622 may include an MPDU or multiple MPDUs or segments of the first data set. Figure 5 As described in , the first WLAN device 110 may also determine information to be included in a PHY header of the first ARQ transmission 622, such as an ACK policy indicator, a PPDU duration indicator, an MCS indicator, an NSS indicator, a BW indicator, a GI indicator, and an FEC indicator.
[0207] In process 632, the second WLAN device 120 may determine that one or more MPDUs of the PPDU associated with the first ARQ transmission 622 are corrupted or failed to be received. However, the second WLAN device 120 may successfully receive and recover the PHY header of the first ARQ transmission 622. Figure 5As described in , the second WLAN device 120 uses information in the PHY header of the first ARQ transmission 622 (as well as channel and network conditions) to recommend that the first WLAN device 110 use certain parameters in the retransmission of the first ARQ transmission 622. For example, the second WLAN device 120 may generate an N-ACK message 634 that includes an indication of various recommended parameters for retransmission, such as a lower MCS, a target transmission time, a target channel, and a transmit power (or a transmit power adjustment). The second WLAN device 120 may send the N-ACK message 634 to the first WLAN device 110. In process 642, the first WLAN device 110 may process the N-ACK message 634 received from the second WLAN device 120. In addition, the first WLAN device 110 may determine the recommended parameters and other information in the N-ACK message 634, and may generate and transmit a Re-TX first ARQ transmission 662 based on the recommended parameters.
[0208] At process 664, the second WLAN device may successfully receive the Re-TX first ARQ transmission 662 and may subsequently send an ACK or Block ACK message 668 to the first WLAN device 110, which may end the ARQ process.
[0209] Figure 7 Depicted is a flow chart 700 having example operations performed by an apparatus in a first WLAN device for implementing a HARQ protocol. The first WLAN device may be a transmitting STA and the second WLAN device may be a receiving STA.
[0210] At block 710 , an apparatus of a first WLAN device may output a first HARQ frame for transmission to a second WLAN device.
[0211] At block 720, the apparatus of the first WLAN device may obtain a first feedback message from the second WLAN device. The first feedback message may indicate whether the HARQ protocol is to be enabled.
[0212] At block 730, the apparatus of the first WLAN device may determine that the HARQ protocol is to be enabled based at least in part on the first feedback message indicating that the HARQ protocol is to be enabled. For example, the apparatus of the first WLAN device may determine that the first feedback message is an H-ACK message (such as an H-BA message) indicating that the HARQ protocol is to be enabled.
[0213] In block 740, an apparatus of the first WLAN device may obtain an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission. In some implementations, the apparatus of the first WLAN device may obtain an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission via a first feedback message. For example, the apparatus of the first WLAN device may obtain an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission based on an H-ACK message (such as an H-BA message) received from the second WLAN device. In some implementations, the apparatus of the first WLAN device may determine an amount of memory available at the second WLAN device for processing the HARQ transmission based on a second HARQ-related communication. The second HARQ-related communication may be an H-CTS message (received in response to sending an H-RTS message), a management frame (received during association), or a block ACK setup message. In some implementations, in a first HARQ frame (i.e., Figure 3 Prior to transmission of a first HARQ transmission 210 shown in FIG. 1 ), an apparatus of the first WLAN device may output an H-RTS message for transmission to a second WLAN device. The H-RTS packet may include a request for an amount of memory available at the second WLAN device for processing the HARQ transmission. The apparatus of the first WLAN device may obtain an H-CTS message from the second WLAN device in response to the transmission of the H-RTS. The H-CTS message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission. In some implementations, prior to transmission of the first HARQ frame (such as during association), the apparatus of the first WLAN device may obtain a management frame from the second WLAN device, which management frame may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission. In some implementations, prior to transmission of the first HARQ frame (such as during a block ACK setup message exchange), the apparatus of the first WLAN device may obtain a block ACK setup message from the second WLAN device, which block ACK setup message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0214] At block 750 , the apparatus of the first WLAN device may output a second HARQ frame for transmission to the second WLAN device based at least in part on an amount of memory available at the second WLAN device for processing the HARQ transmission.
[0215] Figure 8 Depicted is a flow chart 800 having example operations performed by an apparatus for implementing a HARQ protocol in a first WLAN device. The first WLAN device may be a transmitting STA and the second WLAN device may be a receiving STA.
[0216] At block 810, an apparatus of the first WLAN device may determine a HARQ acknowledgment policy for HARQ transmission in a HARQ transmission opportunity (TXOP). For example, the HARQ acknowledgment policy may indicate whether to enable a HARQ protocol and whether to request an H-BA message from the second WLAN device.
[0217] At block 820, the apparatus of the first WLAN device may determine timing information of the HARQ transmissions within the HARQ TXOP. For example, the PHY layer of the first WLAN device may determine the start and end time of each HARQ transmission within the HARQ TXOP to determine the intermediate time period between each HARQ transmission within the HARQ TXOP.
[0218] At block 830, the apparatus of the first WLAN device may output the first HARQ frame for transmission to the second WLAN device. The PHY layer header of the first HARQ frame may include at least a HARQ acknowledgment policy.
[0219] At block 840, the apparatus of the first WLAN device may provide signaling from the PHY layer of the first WLAN device to the MAC layer of the first WLAN device indicating timing information of the HARQ transmissions within the HARQ TXOP. The MAC layer of the first WLAN device may use the intermediate time period for traffic prioritization and scheduling purposes, such as prioritizing scheduling of low latency transmissions (e.g., Figure 2 described in ).
[0220] Fig. 9 Depicted is a flow chart 900 having example operations performed by an apparatus for implementing a HARQ protocol in a second WLAN device. The second WLAN device may be a receiving STA, and the first WLAN device may be a transmitting STA.
[0221] At block 910 , an apparatus of a second WLAN device may determine an amount of memory available at the second WLAN device for processing HARQ transmissions associated with a first WLAN device.
[0222] At block 920 , an apparatus of the second WLAN device may determine whether to enable a HARQ protocol with the first WLAN device.
[0223] In response to determining that the HARQ protocol is to be enabled, the apparatus of the second WLAN device may output a HARQ feedback message (such as an H-ACK message or an H-BA message) for transmission to the first WLAN device at block 930. The HARQ feedback message may indicate that the HARQ protocol is to be enabled.
[0224] At block 940, the apparatus of the second WLAN device may provide an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission. In some implementations, the HARQ feedback message may include an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission. In some implementations, the second HARQ-related communication may include an H-CTS message (sent in response to receiving the H-RTS message), a management frame (sent during association), or a block ACK setup message. For example, the apparatus of the second WLAN device may provide an indication of an amount of memory available at the second WLAN device for processing the HARQ transmission in at least one of a HARQ feedback message (such as an H-ACK message or an H-BA message), an H-CTS message, a management frame, or a block ACK setup message.
[0225] At block 950, an apparatus of the second WLAN device may obtain a first HARQ frame from the first WLAN device. The first HARQ frame may be generated by the first WLAN device based at least in part on an amount of memory available at the second WLAN for processing HARQ transmissions.
[0226] Fig.10 Another example of a HARQ transmission for implementing a HARQ protocol using a block ACK message is depicted. Figure 2 , the HARQ process 1000 may begin with a first HARQ transmission 1010 from the first WLAN device 110 to the second WLAN device 120. The first HARQ transmission 1010 may be an initial PPDU or packet in a HARQ exchange for a specific TXOP 1075. The first HARQ transmission 1010 may include a HARQ indicator (such as a bit, field, or subfield) to indicate that the transmission is a HARQ transmission. For example, if the first HARQ transmission is a HARQ transmission, the bit in the PHY header 211 may be set to 1, or if the first HARQ transmission is a non-HARQ transmission, the bit may be set to 0. In some implementations, the MAC of the first WLAN device 110 may select the HARQ indicator indicating that the transmission is a HARQ transmission.
[0227] In some implementations, the first WLAN device 110 may initialize and maintain a codeword list for a first HARQ transmission 1010 (such as a HARQ PPDU). For example, the MAC of the first WLAN device 110 may initialize and maintain the codeword list. The first HARQ transmission 1010 may include one or more codeword bitmaps of contiguous codewords or codeword groups. The codeword list may include a codeword start index and a codeword end index for each codeword bitmap. In some implementations, the codeword may be an LDPC codeword. After initializing the codeword list, the MAC of the first WLAN device 110 may instruct the PHY of the first WLAN device 110 to generate the first HARQ transmission 1010 and store the codeword. The PHY may construct a PHY header for the first HARQ transmission 1010 and may store the codeword of the first HARQ transmission 1010. The PHY header may include HARQ related information described in the present disclosure (such as HARQ indication information, addressing information, acknowledgment strategy information, etc.). When the PHY begins transmitting the first HARQ transmission 1010, the PHY may provide the MAC with an index of the transmitted codeword, such as on the fly. Accordingly, the MAC may maintain and update a codeword scoreboard of transmitted codewords. For example, after receiving an H-BA message, the MAC may update the codeword scoreboard to indicate which codewords were successfully received and which codewords were not successfully received and may be retransmitted.
[0228] In some implementations, the second WLAN device 120 may receive the first HARQ transmission 1010 and may process the PHY header. For example, the PHY of the second WLAN device 120 may determine that the transmission is a HARQ transmission based on the HARQ indicator in the PHY header, and may use addressing information in the PHY header (such as RX AID, TX AID, and BSS color) to determine that the transmission is intended for the second WLAN device 120. In some implementations, the PHY of the second WLAN device 120 may provide a list of codewords associated with the first HARQ transmission 1010 to the MAC. The PHY may also (at runtime) provide the MAC with an index or indication of the codewords of the first HARQ transmission 1010 that were successfully received. The MAC may initialize and maintain a list of codewords for the first HARQ transmission 1010 (including a codeword start index and a codeword end for each codeword bitmap), and may also maintain indications of successfully received (and unsuccessfully received) codewords.
[0229] In response to receiving and processing the first HARQ transmission 1010, the second WLAN device 120 may send an H-BA message 1030 to the first WLAN device 110. The H-BA message 1030 may start after the SIFS 1020. In some implementations, when the second WLAN device 120 successfully receives at least some codewords of the first HARQ transmission 1010, the second WLAN device 120 may generate the H-BA message 1030 for transmission to the first WLAN device 110. In some implementations, the H-BA message 1030 may include one or more codeword-level bit maps indicating a reception status of the codewords of the first HARQ transmission 1010. For example, the one or more codeword-level bit maps may indicate a reception status of an LDPC codeword of the first HARQ transmission 1010. For example, for each LDPC codeword, the codeword-level bit map may indicate a success or failure in decoding the LDPC codeword. In some implementations, the H-BA message 1030 may include one or more codeword level bitmaps indicating a reception status of a codeword group of the first HARQ transmission 1010. For example, for each codeword group, the codeword level bitmap may indicate a success or failure in decoding the codeword group. In some implementations, the H-BA message 1030 may also include one or more MPDU level bitmaps indicating a reception status of an MPDU of the first HARQ transmission 1010. The H-BA message 1030 may include one or more codeword level bitmaps, or one or more MPDU level bitmaps, or both. The H-BA message 1030 may also include an indication of memory available at the second WLAN device 120 for HARQ transmissions, such as Figure 1-4 . In some implementations, instead of sending the H-BA message 1030, the second WLAN device 120 may generate a C-BA message. For example, the second WLAN device 120 may generate a C-BA message when it determines to disable the HARQ protocol and instead follow a baseline acknowledgment procedure (such as an ARQ protocol). In some implementations, the C-BA message may include one or more MPDU level bitmaps indicating the reception status of the MPDU of the first HARQ transmission 1010. In some implementations, instead of sending the H-BA message 1030, the second WLAN device 120 may generate an N-ACK message. For example, when the PHY header of the first HARQ transmission 1010 is successfully received but the MPDU or codeword of the first HARQ transmission 1010 is not correctly received, the second WLAN device 120 may generate an N-ACK message.
[0230] In some implementations, the first WLAN device 110 may not receive feedback or ACK messages (such as H-BA, C-BA, and N-ACK messages) after transmitting the first HARQ transmission 1010. If the first WLAN device 110 does not receive feedback or ACK messages before the ACK time period (or ACK timeout) expires, the first WLAN device 110 may transmit a HARQ block ACK request (HARQ BAR or H-BAR) message to the second WLAN device 120. The H-BAR may include, for example, Fig.15 H-BA request or HARQ reset request further described in.
[0231] In response to receiving the H-BA message 1030, the first WLAN device 110 may transmit a second HARQ transmission 1040 to the second WLAN device 120 (such as after a SIFS period). The second HARQ transmission 1040 may represent a retransmission 1042 of at least a portion of the first HARQ transmission 1010 or information (such as a codeword) to be used to attempt to decode and recover a failed portion of the first HARQ transmission 1010. For example, the first WLAN device 110 may process the H-BA message 1030 and determine a codeword or codeword group that is successfully or unsuccessfully decoded by the second WLAN device 120 based on one or more codeword-level bitmaps included in the H-BA 1030. In some implementations, since the second HARQ transmission 1040 is a retransmission (rather than an initial HARQ transmission), the MAC of the first WLAN device 110 may provide a codeword list of codewords or codeword groups to be included in the second HARQ transmission 1040 to the PHY. For example, the codeword list may indicate a codeword or codeword group that was not successfully decoded by the second WLAN 120 and is to be included in the second HARQ transmission 1040. The PHY may construct the second HARQ transmission 1040 based on the codeword list received from the MAC. In some implementations, when the HARQ transmission is an initial transmission (such as the first HARQ transmission 1010), the MAC may provide an empty codeword list to indicate that the HARQ transmission is an initial HARQ transmission.
[0232] After the second HARQ transmission 1040, when the second WLAN device 120 has successfully recovered the first HARQ transmission 1010, the second WLAN device 120 may send a C-BA message 1050 (such as after a SIFS period). Fig.10In the example shown in , the C-BA message 1050 can complete the HARQ process 1000. In some implementations, if an additional MPDU or codeword is not correctly received after the second HARQ transmission 1040, the second WLAN device 120 can send a second H-BA message indicating the reception status of the MPDU, codeword, or both. The first WLAN device 110 can then respond with a third HARQ transmission similarly as described with reference to the second HARQ transmission 1040.
[0233] In some implementations, a transmitting STA (such as an AP) may generate a transmission with both HARQ and non-HARQ information for different receiving STAs. For example, a transmitting STA may generate a downlink (DL) multi-user (MU) PPDU with a non-HARQ PSDU for a first receiving STA and a HARQ PSDU for a second receiving STA. In some implementations, the transmitting STA may include a trigger frame or a TRS control field in the MPDU of the PSDU, or may send a MU BAR trigger frame. In some implementations, the transmitting STA may transmit a trigger frame to trigger one or more receiving STAs to send an uplink (UL) MU PPDU. Fig.16 and 17 Various features, frame information, and frame formats that may be used for a DL MU PPDU or UL MU PPDU with both HARQ and non-HARQ information are further described in.
[0234] Fig.11 An example M-BA frame format for use in HARQ feedback messages is depicted. As described herein, H-BA, C-BA, and N-ACK messages may be generated using the M-BA frame format. Fig.11 As shown in FIG. 1 , the M-BA frame format 1100 may include a frame control field 1105, a duration field 1110, a RA field 1115, a TA field 1120, a BA control field 1125, a BA information field 1130, and a frame check sequence (FCS) field 1140. In some implementations, the BA information field 1130 may include one or more AID TID information fields 1131. Each AID TID information field 1131 may include an AID TID information subfield 1132, a block ACK start sequence control subfield 1134, and a block ACK bit map subfield 1136. Each AID TID information subfield 1132 may include an AID 111133, an ACK type 1135, and a TID 1137.
[0235] In some implementations, AID11 1133 may include an identifier that identifies the intended recipient of the transmission. For example, if the second WLAN device 120 transmits an H-BA with an M-BA frame format to the first WLAN device 110, AID11 1133 may include the identifier of the first WLAN device 110. The ACK type 1135 may indicate whether the transmission is an ACK or a block ACK. The TID 1137 may identify the type of traffic. Several combinations of the ACK type and the TID may be reserved. In some implementations, some of the reserved combinations of the ACK type and the TID may be assigned to various HARQ-related messages (such as N-ACK, H-BA, A-control messages), as Figure 12-14 described in
[0236] Fig.12 depicts an example N-ACK with an M-BA frame format. The N-ACK 1200 may have the Fig.11 M-BA frame format 1100 shown in. In some implementations, when the second WLAN device 120 does not successfully receive any MPDUs of a HARQ transmission (such as the first HARQ transmission 1010), the second WLAN device 120 may transmit the N-ACK 1200 as a feedback message to the first WLAN device 110. AID11 1133 may include an indication of the intended recipient of the N-ACK 1200 (such as the first WLAN device 110). As Fig.12 shown in, the ACK type 1135 may be set to 1 to indicate that the N-ACK 1200 is an ACK frame, and the TID 1137 may be set to 13. Thus, the <ACK type, TID> combination for which the N-ACK 1200 is <1,13> may use one of the reserved combinations of the ACK type and the TID. As Fig.12 shown in, the block ACK start sequence control subfield 1134 and the block ACK bit map subfield 1136 may not be present in the N-ACK 1200. In some implementations, the N-NACK 1200 may have a total length of 24 octets.
[0237] Fig.13 depicts an example H-BA with an M-BA frame format. The H-BA 1300 may have the Fig.11The M-BA frame format 1100 shown in [Figure]. In some implementations, the second WLAN device 120 may transmit an H-BA 1300 as a feedback message to the first WLAN device 110, the H-BA 1300 including one or more codeword-level bitmaps indicating the reception status of codewords or MPDUs included in a HARQ transmission (such as the first HARQ transmission 1010), or one or more MPDU-level bitmaps, or both (such as one or more codeword-level bitmaps and one or more MPDU-level bitmaps). The AID11 1133 may include an indication of the intended recipient of the H-BA 1300 (such as the first WLAN device 110). As Fig.13 shown in [Figure], the ACK type 1135 may be set to 0 to indicate that the H-BA 1300 is a BA frame, and the TID 1137 may be set to 13. Thus, the <ACK type, TID> combination for which the H-BA 1300 is <0, 13> may use one of the reserved combinations of ACK type and TID. As Fig.13 shown in [Figure], the Block ACK Start Sequence Control subfield 1134 may include a starting sequence number, which may indicate a starting codeword index or indicate a HARQ memory. The Block ACK Start Sequence Control subfield 1134 may also include a fragment number, which may indicate the length of the Block ACK Bitmap subfield 1136 (such as 0, 4, 8, 16, or 32 octets). The Block ACK Bitmap subfield 1136 may include one or more bitmaps. In some implementations, the H-BA 1300 may have a total length between 30 and 58 octets. In some implementations, when the Block ACK Bitmap subfield 1136 is up to 128 octets, the H-BA 1300 may have a total length between 30 and 154 octets.
[0238] Fig.14 depicts an example A-Control frame having an M-BA frame format. The A-Control 1400 may have Fig.11 the M-BA frame format 1100 shown in [Figure]. In some implementations, the second WLAN device 120 may transmit the A-Control 1400 as a feedback message to the first WLAN device 110 to indicate the amount of memory available at the second WLAN device 120 for HARQ transmissions. The AID11 1133 may include an indication of the intended recipient of the A-Control 1400 (such as the first WLAN device 110). As Fig.14 shown in [Figure], the ACK type 1135 may be set to 0 to indicate that the A-Control 1400 is a BA frame, and the TID 1137 may be set to 14. Thus, the <ACK type, TID> combination for which the A-Control 1400 is <0, 14> may use one of the reserved combinations of ACK type and TID. As Fig.14As shown in , the block ACK starting sequence control subfield 1134 may include a fragment number, which may indicate the length of the block ACK bit map (such as 0, 4, 8, 16 or 32 octets). The block ACK bit map subfield 1136 may be used as an A-control field 1150 for A-control 1400. The A-control field 1150 may include one or more control subfields 1152 and a padding subfield 1153. Each of the one or more control subfields 1152 may include a control ID 1154 and control information 1155. In some implementations, the control information 1155 may provide a HARQ status report, which may indicate the amount of memory available for HARQ transmission. Several control IDs associated with the control subfield 1152 may be reserved. In some implementations, one of the reserved control IDs may be assigned to indicate that the control information 1155 includes a HARQ status report. For example, the control ID may be set to 7 to indicate that the control information 1155 includes a HARQ status report. In some implementations, the A-Control 1400 may have a total length of between 30 and 58 octets. In some implementations, when the Block ACK Bitmap subfield 1136 (and the A-Control field 1150) is up to 128 octets, the A-Control 1400 may have a total length of between 30 and 154 octets.
[0239] Fig.15 An example frame format of an H-BAR trigger frame 1500 is depicted. In some implementations, the second WLAN device 120 may transmit the H-BAR trigger frame 1500 as a feedback message to the first WLAN device 110 to request an H-BA or request a HARQ reset. Fig.15 As shown in , the H-BAR trigger frame 1500 may include a frame control field 1105, a duration field 1110, an RA field 1115, a TA field 1120, a common information field 1525, one or more user information fields 1530, and a frame check sequence (FCS) field 1140. In some implementations, each user information field 1530 may include a BAR control subfield 1532 and a BAR information subfield 1534.
[0240] In some implementations, the BAR control subfield 1532 may include an indication that the BAR frame type (or variant) associated with the H-BAR trigger frame is a HARQ BAR frame type. In some implementations, when the H-BAR trigger frame 1500 includes a request for an H-BA, the BAR information subfield 1534 may include a list of codewords associated with the H-BA being requested. When the H-BAR trigger frame 1500 includes a request for a HARQ reset, the BAR information subfield 1534 may include an indication of a HARQ reset. In some implementations, the H-BAR trigger frame 1500 may be a self-contained H-BAR trigger frame, or may be part of a MU BAR trigger frame.
[0241] Fig.16 An example DL MU PPDU 1600 that may include a HARQ transmission and a non-HARQ transmission is depicted. In some implementations, the first WLAN device 110 may transmit the DL MU PPDU 1600 to one or more WLAN devices. For example, the first WLAN device 110 may transmit the DL MU PPDU 1600 to a second WLAN device 120 (such as STA1) and a third WLAN device 130 (such as STA2). The DL MU PPDU 1600 may include a first PSDU for the second WLAN device 120, which may be a HARQ PSDU 1610 with an enabled HARQ indicator, and a second PSDU for the third WLAN device 130, which may be a non-HARQ PSDU 1620 with a disabled HARQ indicator. After a SIFS 1630, the first WLAN device 110 may receive a high efficiency (HE) triggered-based (TB) PPDU 1605 that may include feedback messages from the second WLAN device 120 and the third WLAN device 130. For example, the HE TB PPDU 1605 may include an H-BA 1640 from the second WLAN device 120 and a C-BA 1650 from the third WLAN device 130 .
[0242] In some implementations, the first WLAN device 110 may include a trigger frame or a trigger response schedule (TRS) control field in the MPDU or the non-HARQ PDSU 1620 or both of the HARQ PDSU 1610. The trigger frame or the TRS control field may trigger feedback messages from the second WLAN device 120 and the third WLAN device 130. In some implementations, if the MPDU with the trigger frame or the TRS control field is not successfully received, the first WLAN device 110 may transmit an H-BAR trigger frame or an MU BAR trigger frame to request the second WLAN device 120 and the third WLAN device 130 to transmit an H-BA 1640 and a C-BA 1650, respectively.
[0243] Fig.17 An example trigger frame 1700 is depicted that may trigger a UL MU PPDU 1705 that may include a HARQ transmission and a non-HARQ transmission. In some implementations, the first WLAN device 110 may transmit the trigger frame 1700 (such as an H-BAR trigger frame) to one or more WLAN devices. In some implementations, one or more PSDUs of the trigger frame 1700 with an enabled HARQ indicator may request a HARQ transmission, and one or more PSDUs of the trigger frame 1700 with a disabled HARQ indicator may request a non-HARQ transmission. For example, the first WLAN device 110 may transmit the trigger frame 1700 to a second WLAN device 120 (such as STA1) requesting a HARQ transmission and a third WLAN device 130 (such as STA2) requesting a non-HARQ transmission.
[0244] In some implementations, after SIFS 1701, the first WLAN device 110 may receive a UL MU PPDU 1705 from the second WLAN device 120 and the third WLAN device 130 in response to the trigger frame 1700. The UL MU PPDU 1705 may include a HARQ PSDU 1710 provided by the second WLAN device 120 and a non-HARQ PSDU 1720 provided by the third WLAN device 130. In some implementations, the trigger frame 1700 may include a codeword list to request the second WLAN device 120 to provide a codeword in the codeword list in a response. The second WLAN device 120 may include a codeword in the codeword list in the HARQ PSDU 1710. In some implementations, the trigger frame 1700 may also request the second WLAN device 120 to use certain TX parameters in the response. For example, the trigger frame 1700 may request the second WLAN device 120 to use a modulation and coding scheme (MCS), a number of spatial streams (NSS), a guard interval (GI), a TX power, a bandwidth (BW), etc. in the response. The second WLAN device 120 may generate and transmit a HARQ PSDU 1710 using the TX parameters specified by the first WLAN device 110 in the trigger frame 1700 .
[0245] In some implementations, the first WLAN device 110 may receive the UL MU PPDU 1705 and may respond with an M-BA 1708. For example, after SIFS 1702, the first WLAN device 110 may transmit an M-BA 1708 including an H-BA for the second WLAN device 120 and a C-BA for the first WLAN device 110.
[0246] Fig.18Depicted is a flow chart 1800 having example operations performed by an apparatus in a first WLAN device for implementing a HARQ protocol using a block ACK message. The first WLAN device may be a transmitting STA and the second WLAN device may be a receiving STA.
[0247] At block 1810 , an apparatus of a first WLAN device may output a first HARQ frame for transmission to a second WLAN device.
[0248] At block 1820 , the apparatus of the first WLAN device may determine whether the first feedback message is obtained from the second WLAN device.
[0249] In block 1830, in response to obtaining the first feedback message, the apparatus of the first WLAN device may determine whether the first feedback message includes HARQ acknowledgment information or non-HARQ acknowledgment information. In some implementations, the apparatus of the first WLAN device may determine that it has obtained a first feedback message including HARQ acknowledgment information. The first feedback message including the HARQ acknowledgment information may be an H-BA message including one or more bitmaps. The one or more bitmaps may include one or more codeword-level bitmaps, one or more MPDU-level bitmaps, or both. The codeword-level bitmap may provide a reception status of a codeword associated with the first HARQ frame. The one or more MPDU-level bitmaps may provide a reception status of an MPDU associated with the first HARQ frame. In some implementations, the H-BA message may have an M-BA frame format. The M-BA frame format may include a first indicator for indicating that the first feedback message is an H-BA message. In some implementations, the BA information field of the M-BA frame format may include at least the first indicator and one or more codeword-level bitmaps of the H-BA message.
[0250] In some implementations, the apparatus of the first WLAN device may determine that it has obtained a first feedback message including non-HARQ acknowledgment information. In some implementations, the first feedback message including the non-HARQ acknowledgment information may be a C-BA message including one or more MPDU level bitmaps. In some implementations, the first feedback message including the non-HARQ acknowledgment information may be an N-ACK message.
[0251] In block 1840, the apparatus of the first WLAN device may output a second HARQ frame for transmission to the second WLAN device in response to determining that the first feedback message (such as an H-BA message) includes the HARQ acknowledgment information. In some implementations, the apparatus of the first WLAN device may generate the second HARQ frame based at least in part on the one or more bitmaps included in the H-BA message. In some implementations, in response to determining that the first feedback message including non-HARQ acknowledgment information is received, the apparatus of the first WLAN device may generate a non-HARQ frame for transmission to the second WLAN device. In some implementations, the non-HARQ frame may be a retransmission frame generated using an ARQ (or baseline) protocol.
[0252] In some implementations, if the apparatus of the first WLAN device does not obtain the first feedback message within an ACK time period (such as an ACK timeout period) after transmitting the first HARQ frame, the apparatus of the first WLAN device may retransmit the first HARQ frame to the second WLAN device, may output a different HARQ frame for transmission to the second WLAN device, or may output an H-BAR message for transmission to the second WLAN device. In some implementations, the H-BAR message may include an H-BA request or a HARQ reset request.
[0253] Fig.19 Depicted is a flow chart 1900 having example operations performed by an apparatus in a second WLAN device for implementing a HARQ protocol using a block ACK message. The second WLAN device may be a receiving STA, and the first WLAN device may be a transmitting STA.
[0254] At block 1910 , an apparatus of a second WLAN device may receive a first HARQ frame from a first WLAN device.
[0255] At block 1920, the apparatus of the second WLAN device may determine, based at least in part on the first HARQ frame, whether to generate a first feedback message including HARQ acknowledgment information or non-HARQ acknowledgment information. In some implementations, the first feedback message including the HARQ acknowledgment information may be an H-BA message including one or more bitmaps. In some implementations, the apparatus of the second WLAN device may determine, based at least in part on determining that at least a portion of a codeword associated with the first HARQ frame is successfully received and a remaining portion of the codeword is not successfully received, to generate the H-BA message. The apparatus of the second WLAN device may also determine, based at least in part on determining that a HARQ protocol is to be enabled (such as based on HARQ memory considerations), to generate the H-BA message.
[0256] In block 1930, in response to determining to generate a first feedback message including HARQ acknowledgment information, the apparatus of the second WLAN device may generate a first feedback message for transmission to the first WLAN device. The one or more bitmaps may include one or more codeword-level bitmaps, one or more MPDU-level bitmaps, or both. The codeword-level bitmap may provide a reception status of a codeword associated with the first HARQ frame. One or more MPDU-level bitmaps may provide a reception status of an MPDU associated with the first HARQ frame. In some implementations, after sending the H-BA message, the apparatus of the second WLAN device may obtain a second HARQ frame in response to the H-BA message.
[0257] In some implementations, the apparatus of the second WLAN device may determine to disable the HARQ protocol based at least in part on the first HARQ frame (such as based on HARQ memory considerations). The apparatus of the second WLAN device may determine to generate a first feedback message including non-HARQ acknowledgment information for transmission to the first WLAN device based at least in part on the determination to disable the HARQ protocol. In some implementations, the first feedback message including the non-HARQ acknowledgment information may be a C-BA message including one or more MPDU level bitmaps. In some implementations, the first feedback message including the non-HARQ acknowledgment information may be an N-ACK message, which may indicate a reception failure of the first HARQ frame.
[0258] In some implementations, the apparatus of the second WLAN device may obtain the H-BAR message from the first WLAN device. For example, the first WLAN device may send the H-BAR message when it does not receive a feedback message from the second WLAN device after transmitting the HARQ frame to the second WLAN device. The apparatus of the second WLAN device may determine whether the H-BAR message includes an H-BA request or a HARQ reset request. In response to determining that the H-BAR message includes an H-BA request, the apparatus of the second WLAN device may generate an H-BA message for transmission to the first WLAN device. In response to determining that the H-BAR message includes a HARQ reset request, the apparatus of the second WLAN device may perform a HARQ reset and generate an ACK message for transmission to the first WLAN device to confirm the completion of the HARQ reset. .
[0259] Fig. 20A block diagram of an example wireless communication device 2000 is shown. In some implementations, the wireless communication device 2000 may be an example of a device for use in a STA (such as one of the STAs 104 described herein). In some implementations, the wireless communication device 2000 may be an example of a device for use in an AP (such as the AP 102 described herein). The wireless communication device 2000 is capable of transmitting (or outputting for transmission) and receiving wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device 2000 may be configured to transmit and receive packets in the form of PPDUs and MPDUs that comply with the IEEE 802.11 standard (such as the standard defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).
[0260] The wireless communication device 2000 may be or may include a chip, system on chip (SoC), chipset, package, or device including one or more modems 2002 (e.g., Wi-Fi (IEEE 802.11 compliant) modems). In some implementations, one or more modems 2002 (collectively referred to as "modems 2002") additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compatible modem). In some implementations, the wireless communication device 2000 also includes one or more radios 2004 (collectively referred to as "radios 2004"). In some implementations, the wireless communication device 2000 further includes one or more processors, processing blocks, or processing elements (collectively referred to as "processors 2006") and one or more memory blocks or elements (collectively referred to as "memory 2008"). In some implementations, the processor 2006 and the memory 2008 may be referred to as a processing system.
[0261] The modem 2002 may include intelligent hardware blocks or devices, such as, for example, application specific integrated circuits (ASICs) and the like. The modem 2002 is generally configured to implement the PHY layer. For example, the modem 2002 is configured to modulate packets and output the modulated packets to the radio 2004 for transmission on the wireless medium. The modem 2002 is similarly configured to obtain modulated packets received by the radio 2004 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 2002 may further include digital signal processing (DSP) circuits, automatic gain control (AGC), encoders, decoders, multiplexers, and demultiplexers. For example, when in the transmission mode, the data obtained from the processor 2006 is provided to the encoder, which encodes the data to provide coded bits. The coded bits are then mapped to points in the modulation constellation (using the selected MCS) to provide modulated symbols. Subsequently, the modulated symbols may be mapped to a number (N SS ) spatial streams or several (N STS The modulated symbols in the corresponding spatial or space-time streams may then be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuit for Tx windowing and filtering. The digital signal may then be provided to a digital-to-analog converter (DAC). The resulting analog signal may then be provided to an upconverter and ultimately to the radio 2004. In an implementation involving beamforming, the modulated symbols in the corresponding spatial streams may be precoded via a steering matrix before being provided to the IFFT block.
[0262] In the receive mode, the digital signal received from the radio 2004 is provided to the DSP circuit, which is configured to capture the received signal, for example, by detecting the presence of the signal and estimating the initial timing and frequency offset. The DSP circuit is further configured to digitally adjust the digital signal, for example, using channel (narrowband) filtering, analog impairment adjustment (such as correcting I / Q imbalance), and applying digital gain to finally obtain a narrowband signal. The output of the DSP circuit system can then be fed to the AGC, which is configured to use information extracted from the digital signal, for example, in one or more received training fields, to determine the appropriate gain. The output of the DSP circuit system is also coupled to a demodulator, which is configured to extract modulated symbols from the signal and, for example, calculate the log-likelihood ratio (LLR) of each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which can be configured to process the LLR to provide decoded bits. Subsequently, the decoded bits from all spatial streams are fed to a demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 2006) for processing, evaluation, or interpretation.
[0263] The radio 2004 generally includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which can be combined into one or more transceivers. For example, the RF transmitter and receiver may include various DSP circuit systems, including at least one power amplifier (PA) and at least one low noise amplifier (LNA), respectively. The RF transmitter and receiver may in turn be coupled to one or more antennas. For example, in some implementations, the wireless communication device 2000 may include or be coupled to multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). The codewords output from the modem 2002 are provided to the radio 2004, and the radio 404 then transmits the codewords via the coupled antennas. Similarly, the codewords received via the antennas are obtained by the radio 2004, and the radio 2004 then provides the codewords to the modem 2002. In some implementations, the radio 2004 and the one or more antennas may form one or more network interfaces (which may also be referred to as "interfaces").
[0264] The processor 2006 may include an intelligent hardware block or device designed to perform the functions described herein, such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) (such as a field programmable gate array (FPGA)), discrete gate or transistor logic, discrete hardware components, or any combination thereof. The processor 2006 processes information received through the radio 2004 and the modem 2002, and processes information to be output by the modem 2002 and the radio 2004 for transmission through a wireless medium. For example, the processor 2006 can implement a control plane and a MAC layer, which is configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform or facilitate operations or techniques such as encoding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation. In some implementations, the processor 2006 can generally control the modem 2002 to cause the modem to perform the various operations described above.
[0265] The memory 2008 may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM) or a combination thereof. The memory 2008 may also store non-transient processor or computer executable software (SW) code containing instructions that, when executed by the processor 2006, cause the processor to perform various operations for wireless communication described herein, including the generation, transmission, reception, and interpretation of MDPUs, frames, or packets. For example, the various functions of the various components disclosed herein or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein may be implemented as one or more modules of one or more computer programs.
[0266] In some implementations, the wireless communication device 2000 may include a HARQ protocol unit (not shown). The HARQ protocol unit may be similar to the reference Figure 2 The HARQ protocol unit 112 or HARQ protocol unit 122 described herein may implement any HARQ technology described herein. In some implementations, the HARQ protocol unit may be implemented by a processor 2006 and a memory 2008 (which may be referred to as a processing system). The memory 2008 may include computer instructions that can be executed by the processor 2006 to implement the functionality of the HARQ protocol unit. Any of these functionalities may be implemented partially (or completely) in hardware or on the processor 2006.
[0267] In some implementations, the wireless communication device 2000 may include a HARQ transmission unit (not shown), a HARQ reception unit (not shown), a HARQ feedback unit (not shown), or any combination thereof, which are similar to the HARQ transmission unit 114, the HARQ reception unit 123, and the HARQ feedback unit 124, respectively, as described in reference to Figure 2 As described herein. The HARQ transmission unit, the HARQ receiving unit, or the HARQ feedback unit may implement any HARQ technique described herein. In some implementations, the HARQ transmission unit, the HARQ receiving unit, or the HARQ feedback unit may be implemented by the processor 2006 and the memory 2008 (which may be referred to as a processing system). The memory 2008 may include computer instructions that may be executed by the processor 2006 to implement the functionality of the HARQ transmission unit, the HARQ receiving unit, or the HARQ feedback unit. Any of these functionalities may be implemented partially (or completely) in hardware or on the processor 2006.
[0268] Fig.21A 2 shows a block diagram of an example AP 2102. For example, the AP 2102 can be an example implementation of the AP 102 described herein. The AP 2102 includes a wireless communication device (WCD) 2110. For example, the wireless communication device 2110 can be a reference Fig. 20An example implementation of the wireless communication device 2000 described. The AP 2102 also includes a plurality of antennas 2120 coupled to the wireless communication device 2110 to transmit and receive wireless communications. In some implementations, the AP 2102 additionally includes an application processor 2130 coupled to the wireless communication device 2110, and a memory 2140 coupled to the application processor 2130. The AP 2102 further includes at least one external network interface 2150, which enables the AP 2102 to communicate with a core network or a backhaul network to obtain access to an external network including the Internet. For example, the external network interface 2150 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Some of the aforementioned components may communicate directly or indirectly with other components on at least one bus. The AP 2102 further includes a housing that covers the wireless communication device 2110, the application processor 2130, the memory 2140, and at least some portions of the antennas 2120 and the external network interface 2150.
[0269] Fig.21B 2104. For example, the STA 2104 may be an example implementation of the STA 104 described herein. The STA 2104 includes a wireless communication device 2115. For example, the wireless communication device 2115 may be a reference Fig. 20 An example implementation of the wireless communication device 2000 described. The STA 2104 also includes one or more antennas 2125 coupled to the wireless communication device 2115 to transmit and receive wireless communications. In some implementations, the STA 2104 additionally includes an application processor 2135 coupled to the wireless communication device 2115, and a memory 2145 coupled to the application processor 2135. In some implementations, the STA 2104 further includes a user interface (UI) 2155 (such as a touch screen or keyboard) and a display 2165, which can be integrated with the UI 2155 to form a touch screen display. In some implementations, the STA 2104 may further include one or more sensors 2175, such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Some of the aforementioned components can communicate directly or indirectly with other components on at least one bus. STA2104 further includes a housing that covers the wireless communication device 2115, the application processor 2135, the memory 2145, and at least some portions of the antenna 2125, the UI 2155 and the display 2165.
[0270] Fig. 22A block diagram of an example electronic device for implementing various aspects of the present disclosure is shown. In some implementations, the electronic device 2200 may be one of an access point (including any AP described herein), a range extender, a station (including any of the STAs described herein), or other electronic systems. The electronic device 2200 may include a processor 2202 (possibly including multiple processors, multiple cores, multiple nodes, or implementing multithreading, etc.). The electronic device 2200 may also include a memory 2206. The memory 2206 may be a system memory or any one or more of the possible implementations of the computer-readable medium described herein. The electronic device 2200 may also include a bus 2210 (such as PCI, ISA, PCI-Express, AHB, AXI, etc.) and a network interface 2204, which may include a wireless network interface (such as a WLAN interface, interface, interface, The electronic device 2200 may include at least one of a wireless network interface (such as a wireless USB interface, a wireless USB interface, etc.) and a wired network interface (such as an Ethernet interface, a power line communication interface, etc.). In some implementations, the electronic device 2200 may support multiple network interfaces, each of which is configured to couple the electronic device 2200 to a different communication network.
[0271] The electronic device 2200 may include a HARQ protocol unit 2260, a HARQ transmission unit 2262, a HARQ reception unit 2263, and a HARQ feedback unit 2264. In some implementations, the HARQ protocol unit 2260, the HARQ transmission unit 2262, the HARQ reception unit 2263, and the HARQ feedback unit 2264 may be distributed within the processor 2202, the memory 2206, and the bus 2210. The HARQ protocol unit 2260, the HARQ transmission unit 2262, the HARQ reception unit 2263, and the HARQ feedback unit 2264 may perform some or all of the operations described herein. For example, the HARQ protocol unit 2260 may be similar to Figure 1 The HARQ protocol unit 112 or HARQ protocol unit 122 described in the above. The HARQ transmission unit 2262 may be similar to Figure 1 The HARQ transmission unit 114 described in the above. The HARQ receiving unit 2263 may be similar to Figure 1 The HARQ receiving unit 123 described in the above. The HARQ feedback unit 2264 may be similar to Figure 1Depending on whether the electronic device 2200 is a transmitting STA or a receiving STA for the HARQ process, the electronic device 2200 may use any one of the HARQ transmission unit 2262 or the HARQ reception unit 2263 and the HARQ feedback unit 2264 to perform the features described in the present disclosure.
[0272] Memory 2206 may include computer instructions that are executable by processor 2202 to implement Figure 1-2 1. Any of these functionalities may be implemented partially (or completely) in hardware or on the processor 2202. For example, the functionality may be implemented in a dedicated integrated circuit, in logic implemented in the processor 2202, in a coprocessor on a peripheral device or card, etc. In addition, implementations may include fewer components or include Fig. 22 The processor 2202, memory 2206, and network interface 2204 are coupled to the bus 2210. Although illustrated as being coupled to the bus 2210, the memory 2206 may also be coupled to the processor 2202.
[0273] Figure 1-22 The operations described herein are examples intended to aid in understanding example implementations and should not be used to limit potential implementations or to limit the scope of the claims. Some implementations may perform additional operations, perform fewer operations, perform operations in parallel or in a different order, and perform some operations differently.
[0274] As used herein, a phrase referring to "at least one" of a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc.
[0275] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of their functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described throughout this document. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0276] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed with a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be performed by circuit systems dedicated to a given function.
[0277] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware (including the structures disclosed in this specification and their structural equivalents), or in any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.
[0278] If implemented in software, each function can be stored as one or more instructions or codes on a computer-readable medium or transmitted by it. The process of the method or algorithm disclosed herein can be implemented in a processor executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Any connection may also be appropriately referred to as a computer-readable medium. Disks and discs as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. TM A disk may be a disk, where a disk often reproduces data magnetically, while a disc reproduces data optically with a laser. Combinations may also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one of code and instructions or any combination or set of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.
[0279] Various modifications to the implementations described in this disclosure may be apparent to those skilled in the art, and the universal principles defined herein may be applied to other implementations without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but should be granted the widest scope consistent with the disclosure, the principles and novel features disclosed herein.
[0280] In addition, one of ordinary skill in the art will readily appreciate that the terms "upper" and "lower / lower" are sometimes used for convenience in describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the actual orientation of any device as implemented.
[0281] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. Furthermore, while features may be described as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to a subcombination, or variations of a subcombination.
[0282] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or to perform all the operations described in order to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously or between any illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the described implementation should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations also fall within the scope of the appended claims. In some cases, the actions described in the claims may be performed in different orders and still achieve the desired result.
Claims
1. A method performed by an apparatus for implementing a hybrid automatic repeat request (HARQ) protocol in a first wireless local area network (WLAN) device, comprising: transmitting a first HARQ frame to a second WLAN device; determining whether a first feedback message is received from the second WLAN device; In response to receiving the first feedback message, determining whether the first feedback message includes HARQ acknowledgment information or non-HARQ acknowledgment information; as well as A second frame is transmitted to the second WLAN device, the second frame being a second HARQ frame if the first feedback message includes the HARQ acknowledgment information, or an automatic repeat request (ARQ) frame if the first feedback message includes the non-HARQ acknowledgment information.
2. The method of claim 1, wherein the first feedback message is a HARQ block acknowledgement (H-BA) message, the H-BA message includes the HARQ acknowledgement information, and the HARQ acknowledgement information includes one or more bitmaps.
3. The method of claim 2, wherein the one or more bitmaps of the H-BA message include at least one of: one or more codeword-level bitmaps; and One or more media access control protocol data unit (MPDU) level bits are mapped.
4. The method of claim 3, wherein: The one or more codeword level bitmaps provide a reception status of a codeword associated with the first HARQ frame; and The one or more MPDU level bitmaps provide a reception status of the MPDU.
5. The method of claim 3, wherein the codewords of each of the one or more codeword-level bitmaps are identified by one or more starting codeword indexes.
6. The method of claim 3, wherein the one or more codeword-level bitmaps identify one or more codeword groups.
7. The method of claim 2, wherein transmitting the second HARQ frame to the second WLAN device is based at least in part on the one or more bitmaps included in the H-BA message.
8. The method of claim 1, wherein the first feedback message is a multi-station block ACK (M-BA) message having an H-BA frame format, the M-BA frame format including a first indicator for indicating that the first feedback message is the H-BA message.
9. The method of claim 8, wherein the M-BA frame format includes a BA information field, the BA information field including at least the first indicator and one or more codeword level bit maps of the H-BA message.
10. The method of claim 9, wherein the BA information field comprises one or more BA control fields, and each of the one or more BA control fields comprises the first indicator.
11. The method of claim 8, wherein the M-BA frame format further includes one or more Compressed Block ACK (C-BA) messages from one or more additional WLAN devices.
12. The method of claim 11, wherein the M-BA frame format further includes at least one additional H-BA message from at least one additional WLAN device.
13. The method of claim 1, wherein the first feedback message received from the second WLAN device is a C-BA message, the C-BA message comprising one or more MPDU level bitmaps.
14. The method of claim 1, wherein the first feedback message received from the second WLAN device is a negative ACK (N-ACK) message indicating a reception failure of the first HARQ frame.
15. The method of claim 14, wherein the N-ACK message has an M-BA frame format, and the M-BA frame format includes: a second indicator for indicating that the first feedback message is the N-ACK message, or The bits are set to zero to indicate that the first feedback message is a bit map of the N-ACK message.
16. The method of claim 15, wherein the M-BA frame format includes a BA information field, the BA information field including at least the second indicator.
17. The method of claim 1, further comprising: In response to determining that the first feedback message is not received from the second WLAN device, retransmitting the first HARQ frame to the second WLAN device, transmitting a different HARQ frame to the second WLAN device, or A HARQ Block ACK Request (H-BAR) message is transmitted to the second WLAN device.
18. The method of claim 1, further comprising: In response to determining that the first feedback message is not received from the second WLAN device within a time period after the transmission of the first HARQ frame, An H-BAR message is transmitted to the second WLAN device, where the H-BAR message includes an H-BA request or a HARQ reset request.
19. The method of claim 18, further comprising: In response to the H-BAR message including the H-BA request, obtaining an H-BA message from the second WLAN device.
20. The method of claim 18, further comprising: In response to the H-BAR message including the HARQ reset request, obtaining an ACK message from the second WLAN device, the ACK message acknowledging completion of the HARQ reset.
21. The method of claim 18, wherein the H-BAR message includes a BAR control field having a third indicator indicating that a message type is the H-BAR message.
22. The method of claim 18, wherein transmitting the H-BAR message to the second WLAN device comprises transmitting a multi-user (MU) BAR trigger frame including the H-BAR message.
23. A method performed by an apparatus for implementing a hybrid automatic repeat request (HARQ) protocol in a second wireless local area network (WLAN) device, comprising: receiving a first HARQ frame from a first WLAN device; determining whether to generate a first feedback message associated with the first HARQ frame; as well as In response to determining that the first feedback message is to be generated, transmitting the first feedback message to the first WLAN device, the first feedback message including HARQ acknowledgment information or non-HARQ acknowledgment information associated with the first HARQ frame; as well as A second frame is received from the first WLAN device, the second frame being a second HARQ frame if the first feedback message includes the HARQ acknowledgment information, or an automatic repeat request (ARQ) frame if the first feedback message includes the non-HARQ acknowledgment information.
24. The method of claim 23, wherein the first feedback message is a HARQ Block Acknowledgement (H-BA) message, the H-BA message comprising the HARQ acknowledgment information.
25. The method of claim 24, wherein the H-BA message includes at least one of: one or more codeword-level bitmaps; and One or more media access control protocol data unit (MPDU) level bits are mapped.
26. The method of claim 25, wherein: The one or more codeword level bitmaps provide a reception status of a codeword associated with the first HARQ frame; and The one or more MPDU level bitmaps provide a reception status of the MPDU.
27. The method of claim 24, further comprising: Determining to generate the H-BA message is based at least in part on: determining that at least a portion of a codeword associated with the first HARQ frame was successfully received and a remaining portion of the codeword was not successfully received, and It is determined that the HARQ protocol is to be enabled.
28. The method of claim 23, wherein the first feedback message is a multi-station block ACK (M-BA) message having an H-BA frame format, the M-BA frame format including a first indicator for indicating that the first feedback message is the H-BA message.
29. The method of claim 28, wherein the M-BA frame format includes a BA information field, the BA information field including at least the first indicator and one or more codeword level bitmaps of the H-BA.
30. The method of claim 23, further comprising: determining to disable the HARQ protocol based at least in part on the first HARQ frame; determining to generate the first feedback message including the non-HARQ acknowledgment information in response to determining to disable the HARQ protocol; as well as In response to determining to generate the first feedback message including the non-HARQ acknowledgment information, the first feedback message including the non-HARQ acknowledgment information is transmitted to the first WLAN device.
31. The method of claim 30, wherein the first feedback message including the non-HARQ acknowledgment information is a Compressed Block ACK (C-BA) message, the C-BA message including one or more MPDU level bitmaps.
32. The method of claim 30, wherein the first feedback message including the non-HARQ acknowledgment information is a negative ACK (N-ACK) message indicating a reception failure of the first HARQ frame.
33. The method of claim 32, wherein the N-ACK message has an M-BA frame format, the M-BA frame format comprising: a second indicator for indicating that the first feedback message is the N-ACK message, or The bits are set to zero to indicate that the first feedback message is a bit map of the N-ACK message.
34. The method of claim 33, wherein the M-BA frame format includes a BA information field, the BA information field including at least the second indicator.
35. The method of claim 23, further comprising: Obtaining a HARQ Block ACK Request (H-BAR) message from the first WLAN device; as well as It is determined whether the H-BAR message includes an H-BA request or a HARQ reset request.
36. The method of claim 35, further comprising: In response to determining that the H-BAR message includes the H-BA request, transmitting an H-BA message to the first WLAN device.
37. The method of claim 35, further comprising: In response to determining that the H-BAR message includes the HARQ reset request, performing a HARQ reset at the second WLAN device; And transmitting an ACK message to the first WLAN device to acknowledge completion of the HARQ reset.
38. An apparatus for implementing a hybrid automatic repeat request (HARQ) protocol in a first wireless local area network (WLAN) device, comprising: One or more interfaces, the one or more interfaces being configured to: transmitting a first HARQ frame to a second WLAN device; as well as One or more processors configured to: determining whether a first feedback message is received from the second WLAN device; as well as In response to receiving the first feedback message, determining whether the first feedback message includes HARQ acknowledgment information or non-HARQ acknowledgment information; as well as The one or more interfaces are configured to: A second frame is transmitted to the second WLAN device, the second frame being a second HARQ frame if the first feedback message includes the HARQ acknowledgment information, or an automatic repeat request (ARQ) frame if the first feedback message includes the non-HARQ acknowledgment information.
39. The apparatus of claim 38, wherein the first feedback message is a HARQ block acknowledgement (H-BA) message, the H-BA message includes the HARQ acknowledgement information, and the HARQ acknowledgement information includes one or more bitmaps.
40. The apparatus of claim 39, wherein the one or more bitmaps of the H-BA message include at least one of: one or more codeword-level bitmaps; and One or more media access control protocol data unit (MPDU) level bits are mapped.
41. The apparatus of claim 40, wherein: The one or more codeword level bitmaps provide a reception status of a codeword associated with the first HARQ frame; and The one or more MPDU level bitmaps provide a reception status of the MPDU.
42. The apparatus of claim 41, wherein the codewords of each of the one or more codeword-level bitmaps are identified by one or more starting codeword indexes.
43. The apparatus of claim 41, wherein the one or more codeword-level bitmaps identify one or more codeword groups.
44. The apparatus of claim 38, wherein the first feedback message is a multi-station block ACK (M-BA) message having an H-BA frame format, the M-BA frame format including a first indicator for indicating that the first feedback message is the H-BA message.
45. The apparatus of claim 44, wherein the M-BA frame format comprises a BA information field including at least the first indicator and one or more codeword level bitmaps of the H-BA message.
46. The apparatus of claim 45, wherein the BA information field comprises one or more BA control fields, and each of the one or more BA control fields comprises the first indicator.
47. The apparatus of claim 45, wherein the M-BA frame format further comprises one or more Compressed Block ACK (C-BA) messages from one or more additional WLAN devices.
48. The apparatus of claim 47, wherein the M-BA frame format further comprises at least one additional H-BA message from at least one additional WLAN device.
49. The apparatus of claim 38, wherein the first feedback message received from the second WLAN device is a C-BA message, the C-BA message comprising one or more MPDU level bitmaps.
50. The apparatus of claim 38, wherein the first feedback message received from the second WLAN device is a negative ACK (N-ACK) message indicating a reception failure of the first HARQ frame.
51. The apparatus of claim 38, wherein in response to determining that the first feedback message is not received from the second WLAN device, the one or more interfaces are configured to: retransmitting the first HARQ frame to the second WLAN device, transmitting a different HARQ frame to the second WLAN device, or A HARQ Block ACK Request (H-BAR) message is transmitted to the second WLAN device.
52. The apparatus of claim 38, wherein in response to determining that the first feedback message is not received from the second WLAN device within a time period after transmission of the first HARQ frame, the one or more interfaces are configured to: An H-BAR message is transmitted to the second WLAN device, where the H-BAR message includes an H-BA request or a HARQ reset request.
53. The apparatus of claim 52, wherein in response to the H-BAR message including the H-BA request, the one or more interfaces are configured to: An H-BA message is obtained from the second WLAN device.
54. The apparatus of claim 52, wherein in response to the H-BAR message including the HARQ reset request, the one or more interfaces are configured to: An ACK message is obtained from the second WLAN device, wherein the ACK message acknowledges completion of the HARQ reset.
55. An apparatus for implementing a hybrid automatic repeat request (HARQ) protocol in a second wireless local area network (WLAN) device, comprising: One or more interfaces, the one or more interfaces being configured to: receiving a first HARQ frame from a first WLAN device; as well as One or more processors configured to: determining whether to generate a first feedback message associated with the first HARQ frame; and the one or more interfaces are configured to: In response to determining that the first feedback message is to be generated, transmitting the first feedback message to the first WLAN device, the first feedback message including HARQ acknowledgment information or non-HARQ acknowledgment information associated with the first HARQ frame; as well as A second frame is received from the first WLAN device, the second frame being a second HARQ frame if the first feedback message includes the HARQ acknowledgment information, or an automatic repeat request (ARQ) frame if the first feedback message includes the non-HARQ acknowledgment information.
56. The apparatus of claim 55, wherein the first feedback message is a HARQ Block Acknowledgement (H-BA) message, the H-BA message comprising the HARQ acknowledgment information.
57. The apparatus of claim 56, wherein the H-BA message comprises at least one of: one or more codeword-level bitmaps; and One or more media access control protocol data unit (MPDU) level bits are mapped.
58. The apparatus of claim 56, wherein the one or more processors are configured to: Determining to generate the H-BA message is based at least in part on: determining that at least a portion of a codeword associated with the first HARQ frame was successfully received and a remaining portion of the codeword was not successfully received, and It is determined that the HARQ protocol is to be enabled.
59. The apparatus of claim 55, wherein the first feedback message is a multi-station block ACK (M-BA) message having an H-BA frame format, the M-BA frame format including a first indicator for indicating that the first feedback message is the H-BA message.
60. The apparatus of claim 59, wherein the M-BA frame format comprises a BA information field including at least the first indicator and one or more codeword level bitmaps of the H-BA.
61. The apparatus of claim 55, wherein: The one or more processors are configured to: determining to disable the HARQ protocol based at least in part on the first HARQ frame; as well as determining to generate the first feedback message including the non-HARQ acknowledgment information in response to determining to disable the HARQ protocol; as well as The one or more interfaces are configured to: In response to determining to generate the first feedback message including the non-HARQ acknowledgment information, the first feedback message including the non-HARQ acknowledgment information is transmitted to the first WLAN device.
62. The apparatus of claim 61, wherein the first feedback message including the non-HARQ acknowledgment information is a Compressed Block ACK (C-BA) message, the C-BA message including one or more MPDU Level Bitmaps.
63. The apparatus of claim 61, wherein the first feedback message including the non-HARQ acknowledgment information is a negative ACK (N-ACK) message indicating a reception failure of the first HARQ frame.
64. The apparatus of claim 55, wherein: The one or more interfaces are configured to obtain a HARQ Block ACK Request (H-BAR) message from the first WLAN device; and The one or more processors are configured to determine whether the H-BAR message comprises an H-BA request or a HARQ reset request.
