Patent Grant
11374698
The present disclosure relates generally to wireless communication systems, and more particularly to physical layer (PHY) data unit formats for hybrid automatic repeat request (HARQ) transmissions.
In a wireless local area network (WLAN), communication devices exchange control information in media access control (MAC) protocol data units (MPDUs), sometimes referred to as “frames”. Typically, multiple MPDUs are aggregated together and transmitted within one physical layer (PHY) protocol data unit (PPDU). If a receiver is unable to decode an MPDU within the PPDU, a transmitter of the MPDU will retransmit the MPDU within another PPDU.
Hybrid automatic repeat request (HARQ) is a technique for improving throughput in communication systems. With HARQ, when a receiver is not able to decode a received communication frame, the receiver stores the transmission in a buffer. Then, a transmitter retransmits the communication frame and the receiver decodes the communication frame using both the original transmission stored in the buffer and the retransmission, e.g., using “soft combining.”
One example of a HARQ technique is referred to as “chase combining.” In chase combining, the transmitter retransmits the same identical communication frame one or more times, and the receiver “soft combines” the original transmission and the one or more retransmissions to decode the communication frame.
Another example of a HARQ technique is referred to as “incremental redundancy.” In incremental redundancy, the original transmission omits some bits (e.g., “puncturing” is used) from an encoded frame, and each retransmission omits different bits and includes some bits that were not included in the previous transmissions. Thus, with each retransmission, the receiver incrementally receives additional information that was not previously transmitted. The receiver then “soft combines” the original transmission and the one or more retransmissions to decode the communication frame.
PPDU formats defined by current WLAN protocols make the use of HARQ impractical. For example, current WLAN protocols specify that when multiple MPDUs are aggregated together and transmitted within one PPDU, the multiple MPDUs are jointly encoded. Thus, even if only one MPDU in the PPDU was not correctly received, all of the MPDUs in the PPDU would need to be retransmitted to implement HARQ in this context. In contrast, not performing HARQ and simply re-encoding the one MPDU and retransmitting the one MPDU is significantly more efficient.
In an embodiment, a method for generating a physical layer (PHY) data unit for transmission in a wireless local area network (WLAN) includes determining, at a communication device, that the PHY data unit is to be transmitted according to a hybrid automatic repeat request (HARQ) process, and generating, at the communication device, a PHY data portion of the PHY data unit. Generating the PHY data portion comprises generating one or more PHY protocol service data units (PSDUs), and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating one or more HARQ coding units of a common length, each of the one or more HARQ coding units generated to include a respective set of one or more PSDUs among the one or more PSDUs, and individually encoding HARQ coding units among the one or more HARQ coding units. The method also includes generating, at the communication device, a PHY preamble of the PHY data unit, including generating a HARQ signal field with HARQ information regarding the PHY data unit, wherein generating the HARQ signal field includes i) generating a common information subfield to indicate one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units and ii) generating a respective HARQ coding unit information subfield for each of the one or more HARQ coding units to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units.
In another embodiment, a wireless communication device comprises a network interface device associated with a first communication device, wherein the network interface device is implemented on one or more integrated circuit (IC) devices, and wherein the one or more IC devices are configured to: determine that the PHY data unit is to be transmitted according to a hybrid automatic repeat request (HARQ) process; generate a PHY data portion of the PHY data unit, comprising: generating one or more PHY protocol service data units (PSDUs), and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating one or more HARQ coding units of a common length, each of the one or more HARQ coding units generated to include a respective set of one or more PSDUs among the one or more PSDUs, and individually encoding HARQ coding units among the one or more HARQ coding units. The one or more IC devices are further configured to generate a PHY preamble of the PHY data unit, including generating a HARQ signal field with HARQ information regarding the PHY data unit, wherein generating the HARQ signal field includes i) generating a common information subfield to indicate one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units and ii) generating a respective HARQ coding unit information subfield for each of the one or more HARQ coding units to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units.
As discussed above, physical layer (PHY) protocol data unit (PPDU) formats defined by current wireless local area network (WLAN) protocols make the use of Hybrid automatic repeat request (HARQ) prohibitive. For instance, the current WLAN protocols mandate that multiple media access control (MAC) protocol data units (MPDUs) aggregated together (referred to as an aggregate MPDU (A-MPDU)) within one PPDU are all encoded as one entity. As a result, there is no mechanism to ensure that the coded bits corresponding to each MPDU in a first transmission and in subsequent retransmissions are identical unless the entire A-MPDU is retransmitted. But retransmitting the entire A-MPDU if only a small fraction of MPDUs are not correctly received wastes radio resource, which will offset the benefits of using HARQ in many cases.
In embodiments disclosed herein, efficient A-MPDU PHY preamble designs for PPDUs and/or other PPDU format changes facilitate using HARQ with WLAN communications. For instance, in some embodiments described below, when multiple MPDUs are to be aggregated as an A-MPDU within one PPDU and when HARQ is to be used, each MPDU is individually encoded. In another embodiment, a plurality of HARQ coding units is generated, each HARQ coding unit including a respective set of one or more MPDUs, and each of the plurality of HARQ coding units is individually encoded. Because each MPDU or coding unit is individually encoded, a receiver needs to know boundaries between the encoded MPDUs or coding units in order to decode the MPDUs correctly, according to embodiments described below. Therefore, in some embodiments described below, an additional signal field is included in a PHY preamble of the PPDU, where the additional signal field includes HARQ-related information regarding the PPDU, such as indications of boundaries between encoded MPDUs or coding units in the PPDU, according to an embodiment. A receiver uses information in the additional signal field to process the individual MPDUs within the PPDU as part of a HARQ process, according to an embodiment.
The network interface 122 is implemented using one or more integrated circuits (ICs) configured to operate as discussed below. For example, the MAC processor 126 may be implemented, at least partially, on a first IC, and the PHY processor 130 may be implemented, at least partially, on a second IC. As another example, at least a portion of the MAC processor 126 and at least a portion of the PHY processor 130 may be implemented on a single IC. For instance, the network interface 122 may be implemented using a system on a chip (SoC), where the SoC includes at least a portion of the MAC processor 126 and at least a portion of the PHY processor 130.
In an embodiment, the host processor 118 includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a random access memory (RAM), a read-only memory (ROM), a flash memory, etc. In an embodiment, the host processor 118 may be implemented, at least partially, on a first IC, and the network device 122 may be implemented, at least partially, on a second IC. As another example, the host processor 118 and at least a portion of the network interface 122 may be implemented on a single IC.
In various embodiments, the MAC processor 126 and/or the PHY processor 130 of the AP 114 are configured to generate data units, and process received data units, that conform to a WLAN communication protocol such as a communication protocol conforming to the IEEE 802.11 Standard or another suitable wireless communication protocol. For example, the MAC processor 126 is configured to implement MAC layer functions, including MAC layer functions of the WLAN communication protocol, and the PHY processor 130 is configured to implement PHY functions, including PHY functions of the WLAN communication protocol. For instance, the MAC processor 126 is configured to generate MAC layer data units such as MAC service data units (MSDUs), MPDUs, A-MPDUs, etc., and provide the MAC layer data units to the PHY processor 130.
In an embodiment, the MAC processor 126 includes a padding unit that is configured to determine a number of padding bits to be added to an MPDU, and to add the determined number of padding bits to the MPDU. In an embodiment, the padding unit comprises a logic circuit that is configured to determine the number of padding bits to be added to the MPDU, and/or to add the determined number of padding bits to the MPDU. In an embodiment, the padding unit is implemented at least partially by a processor of the MAC processor 126, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to determine the number of padding bits to be added to the MPDU, and/or to add the determined number of padding bits to the MPDU, and/or control a logic circuit of the MAC processor 126 to add the determined number of padding bits to the MPDU.
The PHY processor 130 is configured to receive MAC layer data units from the MAC processor 126 and encapsulate the MAC layer data units to generate PHY data units such as PHY protocol data units (PPDUs), PHY protocol service data units (PSDUs), etc., for transmission via the antennas 138. Similarly, the PHY processor 130 is configured to receive PHY data units that were received via the antennas 138, and extract MAC layer data units encapsulated within the PHY data units. The PHY processor 130 may provide the extracted MAC layer data units to the MAC processor 126, which processes the MAC layer data units.
In an embodiment, the PHY processor 130 includes one or more forward error correction (FEC) encoders that are configured to encode bits in a MAC layer data unit according to one or more FEC coding schemes. For example, the PHY processor 130 includes a binary convolutional code (BCC) encoder, according to an embodiment. As another example, the PHY processor 130 additionally or alternatively includes a low density parity check (LDPC) encoder, according to another embodiment. In an embodiment, the FEC encoder comprises a logic circuit that is configured to encode bits in a MAC layer data unit according to an FEC coding scheme. In an embodiment, the FEC encoder is implemented at least partially by a processor of the PHY processor 130, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to encode bits in a MAC layer data unit according to an FEC coding scheme.
Similarly, in an embodiment, the PHY processor 130 includes one or more FEC decoders that are configured to decode bits in a PHY data unit according to one or more FEC coding schemes. For example, the PHY processor 130 includes a BCC decoder, according to an embodiment. As another example, the PHY processor 130 additionally or alternatively includes an LDPC decoder, according to another embodiment. In an embodiment, the FEC decoder comprises a logic circuit that is configured to decode bits in a PHY data unit according to an FEC coding scheme. In an embodiment, the FEC decoder is implemented at least partially by a processor of the PHY processor 130, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to decode bits in a PHY data unit according to an FEC coding scheme.
In an embodiment, the PHY processor 130 includes a padding unit that is configured to determine a number of padding bits to be added to a PHY data unit, and to add the determined number of padding bits to the PHY data unit. In an embodiment, some padding bits are added to the PHY data unit prior to the PHY processor 130 performing FEC encoding of the PHY data unit, and some padding bits are added to the PHY data unit after the PHY processor 130 performs FEC encoding of the PHY data unit. Accordingly, the padding unit is configured to determine a first number of padding bits to be added to a PHY data unit prior to performing FEC encoding of the PHY data unit, and to determine a second number of padding bits to be added to the PHY data unit after performing FEC encoding of the PHY data unit, in an embodiment.
In an embodiment, the padding unit comprises a logic circuit that is configured to determine the number of padding bits to be added to the PHY data unit, and/or to add the determined number of padding bits to the PHY data unit. In an embodiment, the padding unit is implemented at least partially by a processor of the PHY processor 130, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to determine the number of padding bits to be added to the PHY data unit, and/or to add the determined number of padding bits to the PHY data unit, and/or control a logic circuit of the PHY processor 130 to add the determined number of padding bits to the PHY data unit.
In various embodiments, the MAC processor 126 is configured to generate and process MAC layer data units such as described herein. In various embodiments, the PHY processor 130 is configured to generate and process PHY data units such as described herein.
The PHY processor 130 is configured to downconvert one or more radio frequency (RF) signals received via the one or more antennas 138 to one or more baseband analog signals, and convert the analog baseband signal(s) to one or more digital baseband signals, according to an embodiment. The PHY processor 130 is further configured to process the one or more digital baseband signals to demodulate the one or more digital baseband signals and to generate a PPDU. The PHY processor 130 includes amplifiers (e.g., a low noise amplifier (LNA), a power amplifier, etc.), a radio frequency (RF) downconverter, an RF upconverter, a plurality of filters, one or more analog-to-digital converters (ADCs), one or more digital-to-analog converters (DACs), one or more discrete Fourier transform (DFT) calculators (e.g., a fast Fourier transform (FFT) calculator), one or more inverse discrete Fourier transform (IDFT) calculators (e.g., an inverse fast Fourier transform (IFFT) calculator), one or more modulators, one or more demodulators, etc.
The PHY processor 130 is configured to generate one or more RF signals that are provided to the one or more antennas 138. The PHY processor 130 is also configured to receive one or more RF signals from the one or more antennas 138.
The MAC processor 126 is configured to control the PHY processor 130 to generate one or more RF signals by, for example, providing one or more MAC layer data units (e.g., MPDUs) to the PHY processor 130, and optionally providing one or more control signals to the PHY processor 130, according to some embodiments. In an embodiment, the MAC processor 126 includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a read ROM, a flash memory, etc. In an embodiment, the MAC processor 126 includes a hardware state machine that is configured to perform MAC layer functions, control the PHY processor 130, etc.
In an embodiment, the PHY processor 130 includes a HARQ PPDU generator 142 that is configured to generate PPDUs that are formatted for HARQ transmissions (sometimes referred to herein as “HARQ PPDUs”), according to an embodiment. For example, the HARQ PPDU generator 142 is configured to generate HARQ PPDUs to include individually encoded MPDUs, or individually encoded common-length HARQ coding units each including one or multiple MPDUs, such as described herein. In an embodiment, the HARQ PPDU generator 142 includes a HARQ signal (SIG) field generator 144 that is configured to generate SIG fields in PHY preambles of HARQ PPDUs, wherein the SIG field includes HARQ-related information regarding the HARQ PPDUs, such as information needed to properly decode the individually encoded MPDUs, or the individually encoded HARQ coding units, included in a PPDU, according to an embodiment. Such SIG fields are sometimes referred to herein as “HARQ SIG fields.” For example, the HARQ PPDU generator 144 is configured to generate HARQ SIG fields such as described herein.
In an embodiment, the HARQ PPDU generator 142 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ PPDU generator 142 additionally or alternatively includes a hardware state machine that is configured to generate HARQ PPDUs such as described herein. Similarly, the HARQ SIG field generator 144 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ SIG field generator 144 additionally or alternatively includes a hardware state machine that is configured to generate delimiter fields such as described herein.
In an embodiment, the PHY processor 130 also includes a HARQ decoder 146 that is configured to decode an MPDU by “soft combining” an original transmission of the MPDU and one or more retransmissions of the MPDU. The HARQ decoder 146 is configured to use HARQ-related information in a HARQ SIG field of a HARQ PPDU to identify within the HARQ PPDU a beginning of an individually encoded MPDU, or a beginning of an individually encoded HARQ coding unit that includes one or multiple MPDUS, and an end of the individually encoded MPDU or the individually encoded HARQ coding unit that includes one or multiple MPDUs, so that the received one or more MPDUs can be “soft combined” with another transmission of the one or more MPDUs, according to an embodiment.
In an embodiment, the HARQ decoder 146 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ decoder 146 additionally or alternatively includes a hardware state machine that is configured to process HARQ SIG fields such as described herein and/or identify MPDUs within HARQ PPDUs such as described herein.
The WLAN 110 includes a plurality of client stations 154 that are configured to transmit and receive HARQ PPDUs. Although three client stations 154 are illustrated in
The network interface 162 is implemented using one or more ICs configured to operate as discussed below. For example, the MAC processor 166 may be implemented on at least a first IC, and the PHY processor 170 may be implemented on at least a second IC. As another example, at least a portion of the MAC processor 166 and at least a portion of the PHY processor 170 may be implemented on a single IC. For instance, the network interface 162 may be implemented using an SoC, where the SoC includes at least a portion of the MAC processor 166 and at least a portion of the PHY processor 170.
In an embodiment, the host processor 158 includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the host processor 158 may be implemented, at least partially, on a first IC, and the network device 162 may be implemented, at least partially, on a second IC. As another example, the host processor 158 and at least a portion of the network interface 162 may be implemented on a single IC.
In various embodiments, the MAC processor 166 and the PHY processor 170 of the client device 154-1 are configured to generate data units, and process received data units, that conform to the WLAN communication protocol or another suitable communication protocol. For example, the MAC processor 166 is configured to implement MAC layer functions, including MAC layer functions of the WLAN communication protocol, and the PHY processor 170 is configured to implement PHY functions, including PHY functions of the WLAN communication protocol. The MAC processor 166 is configured to generate MAC layer data units such as MSDUs, MPDUs, A-MPDUs, etc., and provide the MAC layer data units to the PHY processor 170.
In an embodiment, the MAC processor 166 includes a padding unit that is configured to determine a number of padding bits to be added to an MPDU, and to add the determined number of padding bits to the MPDU. In an embodiment, the padding unit comprises a logic circuit that is configured to determine the number of padding bits to be added to the MPDU, and/or to add the determined number of padding bits to the MPDU. In an embodiment, the padding unit is implemented at least partially by a processor of the MAC processor 166, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to determine the number of padding bits to be added to the MPDU, and/or to add the determined number of padding bits to the MPDU, and/or control a logic circuit of the MAC processor 166 to add the determined number of padding bits to the MPDU.
The PHY processor 170 is configured to receive MAC layer data units from the MAC processor 166 and encapsulate the MAC layer data units to generate PHY data units such as PPDUs, PSDUs, etc., for transmission via the antennas 178. Similarly, the PHY processor 170 is configured to receive PHY data units that were received via the antennas 178, and extract MAC layer data units encapsulated within the PHY data units. The PHY processor 170 may provide the extracted MAC layer data units to the MAC processor 166, which processes the MAC layer data units.
In an embodiment, the PHY processor 170 includes one or more FEC encoders that are configured to encode bits in a MAC layer data unit according to one or more FEC coding schemes. For example, the PHY processor 170 includes a BCC encoder, according to an embodiment. As another example, the PHY processor 170 additionally or alternatively includes an LDPC encoder, according to another embodiment. In an embodiment, the FEC encoder comprises a logic circuit that is configured to encode bits in a MAC layer data unit according to an FEC coding scheme. In an embodiment, the FEC encoder is implemented at least partially by a processor of the PHY processor 170, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to encode bits in a MAC layer data unit according to an FEC coding scheme.
Similarly, in an embodiment, the PHY processor 170 includes one or more FEC decoders that are configured to decode bits in a PHY data unit according to one or more FEC coding schemes. For example, the PHY processor 170 includes a BCC decoder, according to an embodiment. As another example, the PHY processor 130 additionally or alternatively includes an LDPC decoder, according to another embodiment. In an embodiment, the FEC decoder comprises a logic circuit that is configured to decode bits in a PHY data unit according to an FEC coding scheme. In an embodiment, the FEC decoder is implemented at least partially by a processor of the PHY processor 170, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to decode bits in a PHY data unit according to an FEC coding scheme.
In an embodiment, the PHY processor 170 includes a padding unit that is configured to determine a number of padding bits to be added to a PHY data unit, and to add the determined number of padding bits to the PHY data unit. In an embodiment, some padding bits are added to the PHY data unit prior to the PHY processor 170 performing FEC encoding of the PHY data unit, and some padding bits are added to the PHY data unit after the PHY processor 170 performs FEC encoding of the PHY data unit. Accordingly, the padding unit is configured to determine a first number of padding bits to be added to a PHY data unit prior to performing FEC encoding of the PHY data unit, and to determine a second number of padding bits to be added to the PHY data unit after performing FEC encoding of the PHY data unit, in an embodiment.
In an embodiment, the padding unit comprises a logic circuit that is configured to determine the number of padding bits to be added to the PHY data unit, and/or to add the determined number of padding bits to the PHY data unit. In an embodiment, the padding unit is implemented at least partially by a processor of the PHY processor 170, wherein the processor executes machine readable instructions that, when executed by the processor, cause the processor to determine the number of padding bits to be added to the PHY data unit, and/or to add the determined number of padding bits to the PHY data unit, and/or control a logic circuit of the PHY processor 170 to add the determined number of padding bits to the PHY data unit.
The PHY processor 170 is configured to downconvert one or more RF signals received via the one or more antennas 178 to one or more baseband analog signals, and convert the analog baseband signal(s) to one or more digital baseband signals, according to an embodiment. The PHY processor 170 is further configured to process the one or more digital baseband signals to demodulate the one or more digital baseband signals and to generate a PPDU. The PHY processor 170 includes amplifiers (e.g., an LNA, a power amplifier, etc.), an RF downconverter, an RF upconverter, a plurality of filters, one or more ADCs, one or more DACs, one or more DFT calculators (e.g., an FFT calculator), one or more IDFT calculators (e.g., an IFFT calculator), one or more modulators, one or more demodulators, etc.
The PHY processor 170 is configured to generate one or more RF signals that are provided to the one or more antennas 178. The PHY processor 170 is also configured to receive one or more RF signals from the one or more antennas 178.
The MAC processor 166 is configured to control the PHY processor 170 to generate one or more RF signals by, for example, providing one or more MAC layer data units (e.g., MPDUs) to the PHY processor 170, and optionally providing one or more control signals to the PHY processor 170, according to some embodiments. In an embodiment, the MAC processor 166 includes a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the MAC processor 166 includes a hardware state machine that is configured to perform MAC layer functions, control the PHY processor 170, etc.
In an embodiment, the PHY processor 170 includes a HARQ PPDU generator 192 that is configured to generate HARQ PPDUs, according to an embodiment. For example, the HARQ PPDU generator 192 is configured to generate HARQ PPDUs such as described herein. In an embodiment, the HARQ PPDU generator 192 includes a HARQ SIG field generator 194 that is configured to generate HARQ SIG fields in PHY preambles of HARQ PPDUs, according to an embodiment. For example, the HARQ PPDU generator 194 is configured to generate HARQ SIG fields such as described herein.
In an embodiment, the HARQ PPDU generator 192 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ PPDU generator 192 additionally or alternatively includes a hardware state machine that is configured to generate HARQ PPDUs such as described herein. Similarly, the HARQ SIG field generator 194 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ SIG field generator 194 additionally or alternatively includes a hardware state machine that is configured to generate delimiter fields such as described herein.
In an embodiment, the PHY processor 170 also includes a HARQ decoder 196 that is configured to decode an MPDU by “soft combining” an original transmission of the MPDU and one or more retransmissions of the MPDU. The HARQ decoder 196 is configured to use HARQ-related information in a HARQ SIG field of a HARQ PPDU to identify within the HARQ PPDU a beginning of an individually encoded MPDU, or a beginning of an individually encoded HARQ coding unit that includes one or multiple MPDUS, and an end of the individually encoded MPDU or the individually encoded HARQ coding unit that includes one or multiple MPDUs, so that the received one or more MPDUs can be “soft combined” with another transmission of the one or more MPDUs, according to an embodiment.
In an embodiment, the HARQ decoder 196 is implemented by a processor configured to execute machine readable instructions stored in a memory device (not shown) such as a RAM, a ROM, a flash memory, etc. In an embodiment, the HARQ decoder 196 additionally or alternatively includes a hardware state machine that is configured to process HARQ SIG fields such as described herein and/or identify MPDUs within HARQ PPDUs such as described herein.
In an embodiment, each of the client stations 154-2 and 154-3 has a structure that is the same as or similar to the client station 154-1. Each of the client stations 154-2 and 154-3 has the same or a different number of transceivers and antennas. For example, the client station 154-2 and/or the client station 154-3 each have only two transceivers and two antennas (not shown), according to an embodiment.
PPDUs are sometimes referred to herein as packets. MPDUs are sometimes referred to herein as frames.
The process 200 involves generating a HARQ PPDU 204 using an A-MPDU 208. In an embodiment, the network interface 122/162 is configured to generate the HARQ PPDU 204. In an embodiment, the PHY processor 130/170 is configured to generate the HARQ PPDU 204. In an embodiment, the HARQ PPDU generator 142/192 is configured to generate the HARQ PPDU 204.
In an embodiment, a MAC processor, such as the MAC processor 126 or the MAC processor 166, generates the A-MPDU 208. The A-MPDU 208 includes a plurality of A-MPDU subframes 212, where each A-MPDU subframe 212 corresponds to a PSDU. Each A-MPDU subframe 212 includes an MPDU delimiter 216, an MPDU 220, and optional padding bits 224. Each A-MPDU subframe 212 is individually encoded by an FEC encoder to generate a coded HARQ PSDU 232, in an embodiment. For example, an FEC encoder of a PHY processor, such as the PHY processor 130 or the PHY processor 170, individually encodes each A-MPDU subframe 212 to generate a coded HARQ PSDU 232, according to an embodiment. Individually encoding each A-MPDU subframe 212 facilitates a receiver to perform “soft combining” of an original transmission of the A-MPDU subframe 212 and one or more retransmissions of the A-MPDU subframe 212 as part of a HARQ scheme without having to retransmit the entire A-MPDU 208. In an embodiment, the FEC encoder is a BCC encoder. In another embodiment, the FEC encoder is an LDPC encoder.
The HARQ PPDU 204 is generated to include the HARQ PSDUs 232 and a PHY preamble 236. The PHY preamble 236 includes training signals (not shown) for performing one or more of packet detection, synchronization, automatic gain control (AGC) adjustment, channel estimation, etc. Additionally, the PHY preamble 236 includes a plurality of signal (SIG) fields that include indications of PHY parameters corresponding to a PHY data portion 240 of the PPDU 204 and which a receiver uses to demodulate and decode the PHY data portion 240. Examples of PHY parameters indicated by the plurality of SIG fields includes one or more of a modulation and coding scheme (MCS) applied to the PHY data portion 240 by a transmitter, a duration of the PHY data portion 240, a type of FEC encoding employed, etc.
The plurality of SIG fields includes a SIG field 244 that is included in PPDUs even when HARQ is not being used. Accordingly, the SIG field 244 includes indications of PHY parameters that are not related to HARQ transmission. The plurality of SIG fields also includes a SIG field 248 that includes indications of HARQ-related parameters (sometimes referred to herein as a “HARQ SIG field”) and is only included in PPDUs for which HARQ is being used. Because the HARQ SIG field 248 is only included in PPDUs for which HARQ is being used, the SIG field 244 is configured to indicate whether the PPDU 204 includes the HARQ SIG field 248. For example, the SIG field 244 includes an indicator 252 that indicates whether the PPDU 204 includes the HARQ SIG field 248.
In some embodiments, the SIG field 244 is configured to indicate whether the PPDU 204 includes the HARQ SIG field 248. In other embodiments, the SIG field 244 is additionally configured to indicate one or more other parameters regarding the HARQ SIG field 248. For example, in various embodiments, the SIG field 244 is additionally configured to indicate one of, or any suitable combination of two or more of, i) a modulation scheme used to transmit the HARQ SIG field 248, ii) an FEC encoding scheme used to encode the HARQ SIG field 248, iii) an MCS used for the HARQ SIG field 248, iv) a length in bits of the HARQ SIG field 248, v) a duration of the HARQ SIG field 248 (e.g., indicated as a number of OFDM symbols), etc. In embodiments in which the SIG field 244 is additionally configured to indicate one or more other parameters (such as described above) regarding the HARQ SIG field 248, a receiver uses the indicated one or more other parameters in the SIG field 244 to properly process (e.g., one or more of demodulate, decode, etc.) the HARQ SIG field 248.
In some embodiments, PPDUs have different formats corresponding to different transmission modes or types. As an illustrative example, two or more PPDU formats correspond to two or more of the following example transmission modes: a single user (SU) mode, a multi-user (MU) mode, a trigger-based transmission mode, an extended range transmission mode, etc. Thus, in some embodiments, the PHY preamble 236 and/or the PHY data portion 240 have different formats depending on a particular transmission mode according to which the HARQ PPDU 204 is to be transmitted.
In some embodiments, the SIG field 244 is defined by a new wireless communication protocol. For example, the SIG field defined by the new wireless communication protocol includes one or more fields that are used to indicate whether the PPDU 204 includes the HARQ SIG field 248 and/or to indicate one or more other parameters related to the HARQ SIG field 248. As another example, when the SIG field 244 indicates that the PPDU 204 includes the HARQ SIG field 248, one or more bits and/or one or more subfields of the SIG field are repurposed to indicate one or more other parameters related to the HARQ SIG field 248. For example, when a PPDU is a non-HARQ PPDU, an MCS subfield in the SIG field 244 indicates an MCS used for the PHY data portion of the PPDU, whereas when the PPDU is a HARQ PPDU, the MCS subfield in the SIG field 244 indicates an MCS used for the HARQ SIG field 248, according to an embodiment. Similarly, one or more other subfields related to one or more other PHY parameters that are relevant for non-HARQ PPDUs but are not relevant for HARQ PPDUs are repurposed to provide one or more HARQ-related parameters such as i) a modulation scheme used to transmit the HARQ SIG field 248, ii) an FEC encoding scheme used to encode the HARQ SIG field 248, iii) a length in bits of the HARQ SIG field 248, iv) a duration of the HARQ SIG field 248 (e.g., indicated as a number of OFDM symbols), etc., in some embodiments. Similarly, one or more other subfields related to one or more other PHY parameters that are relevant for a PHY data portion of a HARQ PPDU are repurposed to provide one or more HARQ-related parameters such as i) a modulation scheme used to transmit the HARQ SIG field 248, ii) an FEC encoding scheme used to encode the HARQ SIG field 248, iii) a length in bits of the HARQ SIG field 248, iv) a duration of the HARQ SIG field 248 (e.g., indicated as a number of OFDM symbols), etc., and the PHY parameters that are relevant for the PHY data portion of a HARQ PPDU are indicated in the HARQ SIG field 248, according to some embodiments. Examples of subfields that are repurposed in various embodiments include one or more of i) a dual carrier modulation (DCM) field that indicates whether DCM is used for the PHY data portion, ii) a pre-FEC padding factor subfield that indicates a segment boundary in a last-occurring OFDM symbol of the PHY data portion, wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol (in an embodiment, four segment boundaries are defined for an OFDM symbol, corresponding to four segments in the OFDM symbol; in other embodiments, another suitable quantity of segment boundaries are defined, such as 2, 3, 5, etc.), iii) a packet extension (PE) field disambiguity subfield which includes a parameter related to a PE field added to the PPDU (the parameter is used by a receiver to calculate a number of OFDM symbols in the PPDU), iv) an LDPC extra symbol segment subfield that indicates whether an extra OFDM symbol segment is present for pre-FEC padding when LDPC is used for encoding the PHY data portion, v) a space-time block code (STBC) subfield that is used to indicate whether STBC is used for the PHY data portion, etc.
In some embodiments, the SIG field 244 has a format based on a SIG field defined by a legacy wireless communication protocol. For example, the SIG field defined by the legacy wireless communication protocol may define one or more bits, and/or one or more fields that are designated as “reserved,” and one or more of such reserved bits/fields are used to indicate whether the PPDU 204 includes the HARQ SIG field 248 and/or to indicate one or more other parameters related to the HARQ SIG field 248. As another example, when the SIG field 244 indicates that the PPDU 204 includes the HARQ SIG field 248, one or more bits and/or one or more subfields of the SIG field defined by the legacy wireless communication protocol are repurposed to indicate one or more other parameters related to the HARQ SIG field 248.
In an embodiment, the SIG field 244 has a format based on a SIG field defined by the current draft of the IEEE 802.11ax Standard. In another embodiment, the SIG field 244 has a format based on a SIG field format defined by another suitable standard (e.g., the IEEE 802.11be Standard, currently under development). In such embodiments, the SIG field 244 may have format that is the same as or is different from a SIG field defined by the current draft of the IEEE 802.11ax Standard. For exemplary purposes, Table 1 is a listing of subfields in the HE-SIG-A field for SU PPDUs and extended range (ER) SU PPDUs according to the current draft of the IEEE 802.11ax Standard. The SU PPDU format defined by the current draft of the IEEE 802.11ax Standard may be considered to correspond to a non-ER transmission mode, and thus the term “SU PPDU” may be considered to cover both the non-ER SU PPDU format and the ER SU PPDU format.
In various embodiments, one or more of the bits designated as “reserved” in Table 1 are used to indicate whether the PPDU 204 includes the HARQ SIG field 248, and optionally to indicate one or more other parameters regarding the HARQ SIG field 248.
The current draft of the IEEE 802.11ax Standard defines the values 12-15 for the 4-bit MCS subfield as reserved. Thus, in an embodiment, the MCS subfield is set to any value in the range 12-15 to indicate that the PPDU 204 includes the HARQ SIG field 248, whereas when the MCS subfield is set to any value in the range 0-11, the PPDU 204 does not include the HARQ SIG field 248.
In an embodiment in which the HARQ SIG field 248 can be modulated/encoded according to different MCSs, the MCS subfield is set to a value that indicates the MCS according to which the HARQ SIG field 248 is modulated/encoded. As an illustrative example, the MCS subfield is set to any value in the range 12-15 to indicate that the PPDU 204 includes the HARQ SIG field 248 and the MCS according to which the HARQ SIG field 248 is modulated/encoded is the value in the MCS subfield minus 12, according to an embodiment. In such embodiments, the MCS according to which the PHY data portion is modulated/encoded is indicated in the HARQ SIG field 248, as is discussed below.
In an embodiment in which DCM can optionally be used for the HARQ SIG field 248, the DCM subfield is set to a value that indicates whether DCM is used for the HARQ SIG field 248. In such embodiments, whether DCM is used for the PHY data portion is modulated/encoded is indicated in the HARQ SIG field 248, as is discussed below.
In an embodiment in which different types of HARQ can be used (e.g., chase combining (CC), incremental redundancy (IR), etc.), one or more bits of the SIG field 244 are used to indicate the type of HARQ used for the PPDU 204. In an illustrative embodiment, when the SIG field 244 indicates that the HARQ SIG field 248 is included in the PPDU 204, the LDPC Extra Symbol Segment subfield is repurposed to indicate the type of HARQ used for the PPDU 204.
In an embodiment in which a length or duration of the HARQ SIG field 248 is variable, one or more bits of the SIG field 244 are used to indicate the length/duration of the HARQ SIG field 248. In an illustrative embodiment, when the SIG field 244 indicates that the HARQ SIG field 248 is included in the PPDU 204, bits 37-40 (e.g., the Pre-FEC Padding Factor, the PE Disambiguity, and the Reserved subfields) are repurposed to indicate a number of OFDM symbols of the HARQ SIG field 248. In such embodiments, Pre-FEC Padding Factor and PE Disambiguity information is included in the HARQ SIG field 248, as is discussed below.
In some embodiments, bit B14 (Reserved) is set to zero to indicate that the HARQ SIG field 248 is included in the PPDU 204. In some embodiments in which bit B14 (Reserved) is set to zero to indicate that the HARQ SIG field 248 is included in the PPDU 204 and a length or duration of the HARQ SIG field 248 is variable, one or more bits of the SIG field 244 are used to indicate the length/duration of the HARQ SIG field 248. In an illustrative embodiment, when bit B14 (Reserved) is set to zero, bits 37-40 (e.g., the Pre-FEC Padding Factor, the PE Disambiguity, and the Reserved subfields) are repurposed to indicate a number of OFDM symbols of the HARQ SIG field 248. In such embodiments, Pre-FEC Padding Factor and PE Disambiguity information is included in the HARQ SIG field 248, as is discussed below. In some embodiments in which bit B14 (Reserved) is set to zero to indicate that the HARQ SIG field 248 is included in the PPDU 204, the MCS used for the HARQ SIG field 248 is fixed, and the MCS subfield indicates the MCS used for the PHY data portion of the PPDU 204. In some embodiments in which bit B14 (Reserved) is set to zero to indicate that the HARQ SIG field 248 is included in the PPDU 204, DCM is never used for the HARQ SIG field 248, and the DCM subfield indicates whether DCM is used for the PHY data portion of the PPDU 204. In some embodiments in which bit B14 (Reserved) is set to zero to indicate that the HARQ SIG field 248 is included in the PPDU 204, DCM is always used for the HARQ SIG field 248, and the DCM subfield indicates whether DCM is used for the PHY data portion of the PPDU 204.
In an embodiment, the network interface 122/162 is configured to generate the HARQ SIG field 300. In an embodiment, the PHY processor 130/170 is configured to generate the HARQ SIG field 300. In an embodiment, the HARQ PPDU generator 142/192 is configured to generate the HARQ SIG field 300. In an embodiment, the HARQ SIG field generator 144/194 is configured to generate the HARQ SIG field 300.
In embodiments in which an MCS subfield in the SIG field 244 is repurposed to indicate an MCS used for the HARQ SIG field 300 and/or to indicate that the HARQ PPDU includes the HARQ SIG field 300, the HARQ SIG field 300 includes an MCS subfield 304 that indicates an MCS used for the PHY data portion of the HARQ PPDU. In embodiments in which the MCS subfield in the SIG field 244 is not so repurposed, the HARQ SIG field 300 does not include the MCS subfield 304. The MCS subfield 304 includes a suitable number of bits for specifying an MCS from a suitable set of different MCSs. For example, when the MCS subfield 304 consists of four bits, the set of different MCSs can include up to sixteen different MCSs. As another example, when the MCS subfield 304 consists of three bits, the set of different MCSs can include up to eight different MCSs. Other suitable numbers of bits are used in other embodiments.
The HARQ SIG field 300 includes a respective HARQ PSDU information subfield 312 for each HARQ PSDU included in the HARQ PPDU, according to an embodiment. For instance, in embodiments in which the HARQ SIG field 300 is included in the PPDU 204 of
In some embodiments in which a PE field may be added to a PPDU, the HARQ SIG field 300 also includes a PE disambiguity subfield 316. The PE disambiguity subfield 316 includes a parameter related to a PE field added to the PPDU (the parameter is used by a receiver to calculate a number of OFDM symbols in the PPDU).
In some embodiments, the HARQ SIG field 300 also includes an error detection (e.g., a cyclic redundancy check (CRC)) subfield 320. A value of the CRC subfield 320 is generated by applying an error detection code (e.g., a CRC code) to information from the other subfields of the HARQ SIG field 300.
The HARQ PSDU information subfield 350 includes an MPDU index subfield 352 and a transmission version subfield 354. In an embodiment, the MPDU index subfield 352 uniquely identifies an MPDU, and the transmission version subfield 354 indicates whether the uniquely identified MPDU is an initial transmission (also referred herein as “new MPDU”), a first retransmission of the particular MPDU, a second retransmission of the particular MPDU, etc. For example, the transmission version subfield 354 is set to a value of zero to indicate an initial transmission of the MPDU, and is set to a number greater to zero to indicate the corresponding number of the retransmission of the MPDU, in an embodiment. The MPDU index subfield 352 for a particular MPDU remains the same in every (re)transmission of the MPDU, in an embodiment.
The HARQ PSDU information subfield 350 includes a number of OFDM symbols subfield 358 that indicates a number of OFDM symbols in the corresponding HARQ PSDU (e.g., the corresponding coded HARQ PSDU 232), according to an embodiment. The duration subfield 358 consists of a suitable number, N, of bits, such as six bits or another suitable number of bits. The total number of OFDM symbols in a HARQ PSDU will depend on an error correcting encoding rate that is used, a modulation scheme that is used, and a frequency bandwidth that is used. The MAC processor 126/166 is configured to ensure that an appropriate MAC layer data unit length is used for the error correcting encoding rate, the modulation scheme, and the frequency bandwidth so that the number of OFDM symbols in the HARQ PSDU can be represented by N bits. In another embodiment the number of OFDM symbols subfield 358 is replaced with a time duration field that indicates a time duration value for the corresponding HARQ PSDU (e.g., the corresponding coded HARQ PSDU 232).The HARQ PSDU information subfield 350 also includes a pre-FEC padding factor subfield 362 that indicates a segment boundary in a last-occurring OFDM symbol of the corresponding HARQ PSDU (e.g., the corresponding coded HARQ PSDU 232), wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of the corresponding HARQ PSDU (e.g., the corresponding coded HARQ PSDU 232). In other embodiments, the pre-FEC padding factor subfield 362 is omitted from the HARQ PSDU information subfield 350.
The HARQ PSDU information subfield 350 also includes an LDPC extra symbol segment subfield 364 that indicates whether an extra OFDM symbol segment is present in the last-occurring OFDM symbol of the corresponding HARQ PSDU (e.g., the corresponding coded HARQ PSDU 232) for pre-FEC padding when LDPC is used. In other embodiments, the LDPC extra symbol segment subfield 362 is omitted from the HARQ PSDU information subfield 350.
The HARQ PSDU information subfield 350 also includes a punctured ratio/IR rate subfield 368, in an embodiment. The punctured ratio/IR rate subfield 368 indicates a puncturing ratio (if comb combining is utilized) or IR rate (if incremental redundancy is utilized) that indicates data that is retransmitted in the corresponding HARQ PSDU, in an embodiment. In an embodiment, if comb combining is utilized, a value of 0 of the punctured ratio/IR rate subfield 368 indicates that all coded bits are retransmitted, a value of 1 of the punctured ratio/IR rate subfield 368 indicates that ½ of the coded bits are retransmitted, a value of 2 of the punctured ratio/IR rate subfield 368 indicates that ⅓ of the coded bits are retransmitted, and a value of 3 of the punctured ratio/IR rate subfield 368 indicates that ¼ of the coded bits are retransmitted. In an embodiment, if incremental redundancy is utilized, a value of 0 of the punctured ratio/IR rate subfield 368 indicates that the bits that are retransmitted are encoded at ¾ rate of the initial coding rate, a value of 1 of the punctured ratio/IR rate subfield 368 indicates that the bits that are retransmitted are encoded at ⅔ rate of the initial coding rate, a value of 2 of the punctured ratio/IR rate subfield 368 indicates that the bits that are retransmitted are encoded at ½ rate of the initial coding rate, and a value of 3 of the punctured ratio/IR rate subfield 368 indicates that that the bits that are retransmitted are encoded at ⅓ rate of the initial coding rate. In an embodiment, the punctured ratio/IR rate subfield 368 is included in the HARQ PSDU information subfield 350 if the HARQ PSDU information subfield 350 corresponds to a retransmission HARQ PDSU (e.g., as indicated by a value of greater than zero of the transmission version subfield 354), and is excluded from the HARQ PSDU information subfield 350 if the HARQ PSDU information subfield 350 corresponds to an initial HARQ PDSU (e.g., as indicated by a value of zero of the transmission version subfield 354).
The number above a subfield of the HARQ SIG field 300 indicated in
The process 400 is similar to the process 200 of
Unlike the process 200 of
The HARQ PPDU 404 is generated to include HARQ coding units 430 and a PHY preamble 436. The preamble 436 is generally similar to the preamble 226 of the HARQ PPDU 204 of
In an embodiment, the network interface 122/162 is configured to generate the HARQ SIG field 500. In an embodiment, the PHY processor 130/170 is configured to generate the HARQ SIG field 500. In an embodiment, the HARQ PPDU generator 142/192 is configured to generate the HARQ SIG field 500. In an embodiment, the HARQ SIG field generator 144/194 is configured to generate the HARQ SIG field 500.
In an embodiment, the HARQ SIG field 500 includes a common information subfield that indicates one or more parameters that commonly apply to each of at least some of one or more HARQ coding units, and a respective HARQ coding unit information subfield 512 to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units.
In embodiments in which an MCS subfield in the SIG field 244 is repurposed to indicate an MCS used for the HARQ SIG field 500 and/or to indicate that the HARQ PPDU includes the HARQ SIG field 500, the HARQ SIG field 500 includes, in the common information subfield 502, an MCS subfield 504 that indicates an MCS used for the PHY data portion of the HARQ PPDU. In embodiments in which the MCS subfield in the SIG field 244 is not so repurposed, the HARQ SIG field 500 does not include the MCS subfield 504. The MCS subfield 504 includes a suitable number of bits for specifying an MCS from a suitable set of different MCSs. For example, when the MCS subfield 504 consists of four bits, the set of different MCSs can include up to sixteen different MCSs. As another example, when the MCS subfield 504 consists of three bits, the set of different MCSs can include up to eight different MCSs. Other suitable numbers of bits are used in other embodiments.
The common information subfield 502 includes a number of OFDM symbols in new coding unit subfield 506 that indicates a number of OFDM symbols in each HARQ coding unit that corresponds to an initial HARQ transmission (i.e., also referred to herein as “new HARQ coding unit” or simply “new coding unit”), in an embodiment. In an embodiment, if the HARQ PPDU does not include any new coding units (e.g., of all coding units included in the HARQ PPDU correspond to retransmission coding units), the number of OFDM symbols in new coding unit subfield 506 is set to a value of zero. The common information subfield 502 also includes a pre-FEC padding factor subfield 508 that indicates a segment boundary in a last-occurring OFDM symbol of each HARQ coding unit that corresponds to an initial HARQ transmission, wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of the corresponding HARQ coding unit. In an embodiment, the pre-FEC padding factor subfield 508 is omitted from the common information subfield 502 if the number of OFDM symbols in new coding unit subfield 506 is set to a value of zero indicating that the HARQ PPDU does not include any new coding units.
The common information subfield 502 also includes an LDPC extra symbol segment subfield 510 that indicates whether an extra OFDM symbol segment is present in the last-occurring OFDM symbol of each HARQ coding unit that corresponds to an initial HARQ transmission for pre-FEC padding when LDPC is used. In an embodiment, the LDPC extra symbol segment subfield 510 is omitted from the common information subfield 502 if the number of OFDM symbols in new coding unit subfield 506 is set to a value of zero indicating that the HARQ PPDU does not include any new coding units.
The HARQ SIG field 500 includes a respective HARQ coding unit information subfield 512 for each HARQ coding unit included in the HARQ PPDU, according to an embodiment. For instance, in embodiments in which the HARQ SIG field 500 is included in the PPDU 404 of
In some embodiments in which a PE field may be added to a PPDU, the HARQ SIG field 500 also includes a PE disambiguity subfield 516. The PE disambiguity subfield 516 includes a parameter related to a PE field added to the PPDU (the parameter is used by a receiver to calculate a number of OFDM symbols in the PPDU).
In some embodiments, the HARQ SIG field 500 also includes an error detection (e.g., a cyclic redundancy check (CRC)) subfield 520. A value of the CRC subfield 520 is generated by applying an error detection code (e.g., a CRC code) to information from the other subfields of the HARQ SIG field 500.
The HARQ coding unit information subfield 550 includes an MPDU index subfield 552 and a transmission version subfield 554. In an embodiment, the MPDU index subfield 552 uniquely identifies an MPDU, and the transmission version subfield 554 indicates whether the uniquely identified MPDU is an initial transmission, a first retransmission of the particular MPDU, a second retransmission of the particular MPDU, etc. For example, the transmission version subfield 554 is set to a value of zero to indicate an initial transmission of the MPDU, and is set to a number greater to zero to indicate the corresponding number of the retransmission of the MPDU, in an embodiment. The MPDU index subfield 552 for a particular MPDU remains the same in every (re)transmission of the MPDU, in an embodiment.
The HARQ coding unit information subfield 550 includes a number of OFDM symbols subfield 558 that indicates a number of OFDM symbols in the corresponding HARQ coding unit (e.g., the corresponding coded HARQ PSDU 432), according to an embodiment. The number of OFDM symbols 558 consists of a suitable number, N, of bits, such as six bits or another suitable number of bits. The total number of OFDM symbols in a HARQ coding unit will depend on an error correcting encoding rate that is used, a modulation scheme that is used, and a frequency bandwidth that is used. The MAC processor 126/166 is configured to ensure that an appropriate MAC layer data unit length is used for the error correcting encoding rate, the modulation scheme, and the frequency bandwidth so that the number of OFDM symbols in the HARQ coding unit can be represented by N bits. In another embodiment the number of OFDM symbols subfield 558 is replaced with a time duration field that indicates a time duration value for the corresponding HARQ coding unit (e.g., the corresponding coded HARQ PSDU 432).
The HARQ coding unit information subfield 550 also includes a pre-FEC padding factor subfield 562 that indicates a segment boundary in a last-occurring OFDM symbol of the corresponding HARQ coding unit (e.g., the corresponding coded HARQ PSDU 432), wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of the corresponding HARQ coding unit (e.g., the corresponding coded HARQ coding unit 432). In other embodiments, the pre-FEC padding factor subfield 562 is omitted from the HARQ coding unit information subfield 550.
The HARQ coding unit information subfield 550 also includes a punctured ratio/IR rate subfield 564, in an embodiment. The punctured ratio/IR rate subfield 564 indicates a puncturing ratio (if comb combining is utilized) or IR rate (if incremental redundancy is utilized) that indicates data that is retransmitted in the corresponding HARQ PSDU, in an embodiment. The punctured ratio/IR rate subfield 564 is generally the same as the punctured ratio/IR rate subfield 368 described with reference to
The number indicated above a subfield of the HARQ SIG field 500 in
In some embodiments, the HARQ PPDU is an MU PPDU that includes independent information for multiple communication devices. For example, the MU PPDU is to be transmitted using orthogonal frequency division multiple access (OFDMA), MU multiple input, multiple output (MU-MIMO), or a hybrid of both OFDMA and MU-MIMO. Referring now to
In some embodiments, MU PPDUs include a further SIG field (not shown in
In an embodiment, the network interface 122/162 is configured to generate the HARQ SIG field 600. In an embodiment, the PHY processor 130/170 is configured to generate the HARQ SIG field 600. In an embodiment, the HARQ PPDU generator 142/192 is configured to generate the HARQ SIG field 600. In an embodiment, the HARQ SIG field generator 144/194 is configured to generate the HARQ SIG field 600.
The HARQ SIG field 600 includes a respective HARQ user information subfield 612 for each of one or more client stations to which the MU PPDU is to be transmitted, according to an embodiment. As described in more detail below, the HARQ user information subfield 612 includes HARQ-related information for one or more PSDUs to be transmitted to a respective client station.
In an embodiment, an order of the HARQ user information subfields 612 corresponds to an ordering of client stations specified in the MU SIG field (e.g., in an HE-SIG-B field). For example, the MU SIG field (e.g., the HE-SIG-B field) includes allocation information that allocates RUs to client stations, and the allocation information includes a listing of client stations in an order; the order of the HARQ user information subfields 612 corresponds to the order of the listing of client stations in the MU SIG field.
In some embodiments in which a PE field may be added to a PPDU, the HARQ SIG field 600 also includes a PE disambiguity subfield 616. The PE disambiguity subfield 616 includes a parameter related to a PE field added to the PPDU (the parameter is used by a receiver to calculate a number of OFDM symbols in the PPDU).
In some embodiments, the HARQ SIG field 600 also includes an error detection (e.g., a cyclic redundancy check (CRC)) subfield 620. A value of the CRC subfield 620 is generated by applying an error detection code (e.g., a CRC code) to information from the other subfields of the HARQ SIG field 600.
In some embodiments and/or scenarios, the HARQ SIG field 600 also includes padding 624, which will be described in more detail below.
The HARQ user information subfield 650 includes an MCS subfield 652 that indicates an MCS used for the PHY data portion of the HARQ PPDU, in an embodiment. The MCS subfield 652 includes a suitable number of bits for specifying an MCS from a suitable set of different MCSs. For example, when the MCS subfield 652 consists of four bits, the set of different MCSs can include up to sixteen different MCSs. As another example, when the MCS subfield 652 consists of three bits, the set of different MCSs can include up to eight different MCSs. Other suitable numbers of bits are used in other embodiments.
The HARQ user information subfield 650 includes a respective HARQ PSDU information subfield 662 for each HARQ PSDU included in the HARQ PPDU for the corresponding client station, according to an embodiment. In an embodiment, an ordering of the HARQ PSDU information subfields 662 corresponds to an ordering of the HARQ PSDUs in the HARQ PPDU for the corresponding client station. For example, a first occurring HARQ PSDU information subfield 662 corresponds to a first occurring HARQ PSDU, a second occurring HARQ PSDU information subfield 662 corresponds to a second occurring HARQ PSDU, and so on. In an embodiment, the HARQ PSDU information subfield 662 is generally the same as the HARQ PSDU information subfield 350 of
In some embodiments in which a PE field may be added to a PPDU, the HARQ user information subfield 650 also includes a PE disambiguity subfield 616. The PE disambiguity subfield 616 includes a parameter related to a PE field added to the PPDU (the parameter is used by a receiver to calculate a number of OFDM symbols in the PPDU).
In some embodiments, the HARQ user information subfield 650 also includes an error detection (e.g., a cyclic redundancy check (CRC)) subfield 620. A value of the CRC subfield 660 is generated by applying an error detection code (e.g., a CRC code) to information from the other subfields of the HARQ user information subfield 650.
The HARQ user information subfield 670 includes a data MCS subfield 672 to that indicates an MCS used for the client station in the PHY data portion of the MU HARQ PPDU.
A number of OFDM symbols for new coding units subfield 674 indicates a number of OFDM symbols in the HARQ PPDU for the new coding unit for the client station, except for the last-occurring new coding unit in the HARQ PPDU for the client station. A pre-FEC padding factor subfield 678 indicates a segment boundary in a last-occurring OFDM symbol of the new coding unit, wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of each new HARQ coding unit except for the last-occurring new HARQ coding unit. An LDPC extra symbol segment subfield for new coding unit 680 indicates whether an extra OFDM symbol segment is included for pre-FEC padding when LDPC is used for the HARQ PPDU.
A number of OFDM symbols for last coding unit subfield 682 indicates a number of OFDM symbols used for the last-occurring new coding unit included for the client station in the HARQ PPDU. A pre-FEC padding factor for last coding unit subfield 684 indicates a segment boundary in a last-occurring OFDM symbol of the last-occurring new coding unit, wherein padding bits are added prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of the last-occurring new HARQ coding unit.
An LDPC extra symbol segment for last coding unit subfield 688 indicates whether an extra OFDM symbol segment for pre-FEC padding is included in the last-occurring coding unit when LDPC is used for the HARQ PPDU. A number of retransmission coding units subfield 690 indicates a number of retransmission HARQ coding units included for the client station in the HARQ PPDU. A respective HARQ coding unit index subfield 692 identifies a respective HARQ coding unit included for the client station in the HARQ PPDU. A respective transmission version subfield 694 indicates a transmission number of the retransmission HARQ coding unit included for the client station in the HARQ PPDU. A respective number of OFDM symbols subfield 696 indicates a number of OFDM symbols for each respective retransmission HARQ coding unit, in an embodiment.
A respective punctured ratio/IR rate subfield 698 is included in the HARQ user information subfield 670 for a respective retransmission HARQ coding unit, and is omitted from the HARQ user information subfield 670 for a respective new coding unit, in an embodiment. The punctured ratio/IR rate subfield 698 indicates a puncturing ratio (if comb combining is utilized) or IR rate (if incremental redundancy is utilized) that indicates data that is retransmitted in the corresponding HARQ PSDU, in an embodiment. The punctured ratio/IR rate subfield 698 is generally the same as the punctured ratio/IR rate subfield 368 described with reference to
The number indicated above a subfield of the HARQ SIG field 600 in
In the example illustrated in
The MU HARQ PPDU 700 comprises a PHY preamble portion 708 and a PHY data portion 712. The PHY preamble portion 708 comprises a plurality of suitable training signals (not shown). Additionally, the PHY preamble portion 708 comprises a SIG field (SIGA field) 716. An instance of the SIGA field 716 is transmitted in each frequency subchannel 704, according to an embodiment. The SIGA field 716 corresponds to the SIG field 244 discussed above, according to an embodiment.
Additionally, the PHY preamble portion 708 comprises a SIG field (SIGB field) 720. The SIGB field 720 corresponds to the MU SIG field discussed above, according to an embodiment. In the example illustrated in
The SIGB field 720 includes allocation information that indicates an allocation of frequency RUs 724. In an embodiment, each version of the SIGB field 720 includes allocation information for frequency RUs 724 that overall the frequency subchannels in which the version of the SIGB field 720 is transmitted. For instance, in the illustrative example of
In the illustrative example of
The PHY data portion 712 includes a plurality of HARQ PSDUs 728 for multiple client stations. In the illustrative example of
The PHY preamble portion 708 comprises a plurality of HARQ SIG fields 740. In the example illustrated in
In an embodiment, each RU HARQ SIG field 740 includes HARQ-related information for HARQ PSDUs to be transmitted within the corresponding frequency subchannel 704, but does not include HARQ-related information for HARQ PSDUs to be transmitted within other frequency subchannels 704. For example, HARQ SIG field 740-1 includes HARQ-related information for HARQ PSDU(s) 728-1 and HARQ PSDU(s) 728-2; HARQ SIG field 740-2 includes HARQ-related information for HARQ PSDUs 728-3; and HARQ SIG field 740-3 and HARQ SIG field 740-4 include HARQ-related information for HARQ PSDUs 728-4 (for example, the HARQ-related information for HARQ PSDUs 728-4 is divided between HARQ SIG field 740-3 and HARQ SIG field 740-4).
In another embodiment, the same HARQ SIG field 740 is transmitted in each subchannel 704, and the HARQ SIG field 740 includes HARQ-related information for all HARQ PSDUs to be transmitted within the HARQ PPDU 700.
In the illustrative example of
Trigger-based PPDUs are transmitted in response to a trigger frame. For example, an AP transmits a trigger frame to prompt one or more client stations to transmit one or more trigger-based PPDUs. Transmission of a trigger-based PPDU begins a defined time period (e.g., a short interface space (SIFS) as defined by the IEEE 802.11 Standard, or another suitable time period) after receipt of an end of a PPDU that includes the trigger frame, in an embodiment.
The trigger frame 800 includes a trigger type field 804 that indicates a type of trigger frame from a plurality of different trigger types. For example, the current draft of the IEEE 802.11ax Standard defines eight different trigger types indicated by values 0-7 of a trigger type field, with values 8-15 reserved. In an embodiment, an additional trigger type is defined for a trigger frame that prompts one or more client stations to transmit one or more trigger-based HARQ PPDUs. In an illustrative embodiment, a value 8 of the trigger type field indicates that the trigger frame 800 is for prompting one or more client stations to transmit one or more trigger-based HARQ PPDUs. In other embodiments, another suitable value other than 8 is used, such as any of 9-15, or any other suitable value.
An uplink (UL) length field 808 indicates a duration of the trigger-based HARQ PPDU that is to be transmitted in response to the trigger frame 800. The AP 114 determines (e.g., the network interface 122 determines, the MAC processor 126 determines, etc.) the duration based on client station data buffer sizes known to the AP 114, the client station data buffer sizes indicating how much data each client station has to transmit to the AP 114. Since AP 114 has knowledge of the data buffer size of each client station, but the AP does not know a number of MPDUs each STA will include in the trigger-based HARQ PPDU, it is difficult for AP 114 to calculate an accurate UL length when each MPDU is individually encoded (as in a HARQ PPDU). In one embodiment, the AP 114 calculates (e.g., the network interface 122 calculates, the MAC processor 126 calculates, etc.) the UL length based on i) the data buffer sizes of the client stations and ii) any extra OFDM symbols when taking extra pre-FEC padding and post-FEC padding of each coded PSDU into account. In one embodiment, if a client station cannot fit all PSDUs into the trigger-based HARQ PPDU duration specified by the UL length field 808, the client station will aggregate as many PSDUs that can be included in the trigger-based HARQ PPDU, and then add padding to reach the duration specified by the UL length field 808. In another embodiment, if a client station cannot fit all PSDUs into the trigger-based HARQ PPDU duration specified by the UL length field 808, the client station fragments a last-occurring MPDU into two segments; the client station includes a first segment in the trigger-based HARQ PPDU, and includes a second segment in a subsequent HARQ PPDU.
In an embodiment, the trigger frame 800 includes a trigger dependent common information field 820 that is specific to trigger frames that are for prompting one or more client stations to transmit one or more trigger-based HARQ PPDUs. In an embodiment, the trigger dependent common information field 820 includes i) a duration subfield that specifies a number of OFDM symbols to be included in the trigger-based HARQ PPDU that is to be transmitted in response to the trigger frame 800, ii) a pre-FEC padding factor subfield that indicates to client station(s) a segment boundary in a last-occurring OFDM symbol of the trigger-based HARQ PPDU, wherein the client stations add padding bits prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol, and iii) an LDPC extra symbol segment subfield that indicates whether client station(s) should include an extra OFDM symbol segment for pre-FEC padding when LDPC is used for the trigger-based HARQ PPDU.
In an embodiment, the trigger frame 800 includes allocation information that indicates which client station(s) are to transmit trigger-based HARQ PPDUs in response to the trigger frame 800. In an embodiment, the allocation information also indicates the RUs assigned to the client station(s) for the trigger-based HARQ PPDUs.
In an embodiment, only one client station is assigned to each RU. In another embodiment, multiple client stations are permitted to be assigned to a single RU.
In an embodiment, the trigger frame 800 also includes a respective trigger dependent user information subfield 822 for each of the client station(s).
A number of new coding units subfield 852 indicates a number of initial HARQ coding units to be included in the trigger-based HARQ PPDU. A number of OFDM symbols for new coding units subfield 854 indicates a number of OFDM symbols to be used for each of the new HARQ coding units to be included in the trigger-based HARQ PPDU except for the last-occurring new coding unit to be included in the trigger-based HARQ PPDU. A pre-FEC padding factor subfield 858 indicates a segment boundary in a last-occurring OFDM symbol of the new coding unit, wherein the client station adds padding bits prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of each new HARQ coding unit except for the last-occurring new HARQ coding unit.
An LDPC extra symbol segment subfield 860 indicates whether the client station should include an extra OFDM symbol segment for pre-FEC padding when LDPC is used for the trigger-based HARQ PPDU. In an embodiment, to facilitate symbol alignment among different STAs for the trigger-based HARQ PPDU (the AP does not have knowledge of number of MPDUs each client station will include in the trigger-based HARQ PPDU), the LDPC Extra Segment subfield 860 is set to one, according to an embodiment. In response to the LDPC Extra Segment subfield 860 being set to one, a client station receiving the trigger frame 800 will include an extra OFDM symbol segment in a last-occurring OFDM symbol of a last-occurring coded HARQ PSDU in the trigger-based HARQ PPDU, according to an embodiment.
A number of OFDM symbols for last coding unit subfield 862 indicates a number of OFDM symbols to be used for the last-occurring new coding unit to be included in the trigger-based HARQ PPDU. A pre-FEC padding factor for last coding unit subfield 864 indicates a segment boundary in a last-occurring OFDM symbol of the last-occurring new coding unit, wherein the client station adds padding bits prior to FEC encoding so that the FEC encoded bits end at the indicated segment boundary in the last-occurring OFDM symbol of the last-occurring new HARQ coding unit.
An LDPC extra symbol segment for last coding unit subfield 868 indicates whether the client station should include an extra OFDM symbol segment for pre-FEC padding in the last-occurring coding unit when LDPC is used for the trigger-based HARQ PPDU. In an embodiment, to facilitate symbol alignment among different STAs for the trigger-based HARQ PPDU (the AP does not have knowledge of number of MPDUs each client station will include in the trigger-based HARQ PPDU), the LDPC Extra Segment subfield 860 is set to one, according to an embodiment. In response to the LDPC Extra Segment subfield 860 being set to one, a client station receiving the trigger frame 800 will include an extra OFDM symbol segment in a last-occurring OFDM symbol of a last-occurring coded HARQ PSDU in the trigger-based HARQ PPDU, according to an embodiment.
A number of retransmission coding units subfield 870 indicates a number of retransmission HARQ coding units to be included in trigger-based HARQ PPDU. In an embodiment, the client station includes the number of retransmission HARQ coding units indicated in the number of retransmission coding units subfield 870 at the beginning of the trigger-based HARQ PPDU, followed by the number of new HARQ coding units indicated in the number of new coding units subfield 852. A respective HARQ coding unit index subfield 872 identifies a HARQ coding unit to be included in trigger-based HARQ PPDU. A respective transmission version subfield 874 indicates a transmission number of the retransmission HARQ coding unit to be included in trigger-based HARQ PPDU. A respective number of OFDM symbols subfield 876 indicates a number of OFDM symbols for each respective retransmission HARQ coding unit. A respective punctured ratio/IR rate subfield 876 indicates a puncturing ratio or IR rate that determines data that is retransmitted in each respective retransmission HARQ coding unit, in an embodiment.
The number indicated above a subfield of the trigger dependent user information subfield 850 in
In an embodiment, the network interface 122/162 is configured to generate the trigger-based HARQ PPDU 900. In an embodiment, the PHY processor 130/170 is configured to generate the trigger-based HARQ PPDU 900. In an embodiment, the HARQ PPDU generator 142/192 is configured to generate the trigger-based HARQ PPDU 900.
As discussed above, a trigger frame indicates the RU(s) via which the trigger-based HARQ PPDU 900 is to be transmitted. In the example illustrated in
In the illustrative example of
The PHY preamble portion 908 also comprises a HARQ SIG field 940. In an embodiment, the HARQ SIG field 940 is transmitted within the frequency subchannel 904. In an embodiment, a duration of the HARQ SIG field 940 corresponds to a duration indicated in the trigger frame that prompts transmission of the trigger-based HARQ PPDU 900, and the SIG field 916 does not indicate a duration of the HARQ SIG field 940. In another embodiment, the SIG field 916 indicates a duration of the HARQ SIG field 940 such as the SIG field 244 described above.
In an embodiment, the HARQ SIG field 940 has a format similar to the HARQ SIG field 300 discussed with reference to
In an embodiment, the HARQ SIG field 940 has a format similar to the HARQ SIG field 300 discussed with reference to
The A-MPDU 208 is the same as the A-MPDU 208 discussed with reference to
As illustrated in
In some embodiments, determining an amount of pre-FEC padding bits includes determining whether an extra OFDM symbol segment is to be added to a last-occurring OFDM symbol of the coded HARQ PSDU/HARQ coding unit when LDPC encoding is used, and indicating in a corresponding LDPC extra symbol segment subfield in the HARQ SIG field whether the extra OFDM symbol segment is added in the last-occurring OFDM symbol, as discussed above.
After the PSDU 1004 and the pre-FEC padding bits 1008 are FEC encoded, post-FEC padding bits 1024 are added after a last-occurring coded HARQ PSDU/HARQ coding unit 1232 so that the HARQ PPDU/HARQ coding unit ends at an OFDM symbol boundary.
In various embodiments, an indication of the selected pre-FEC padding boundary 1012 for each coded HARQ PSDU/HARQ coding unit 1032 is indicated in a corresponding pre-FEC padding factor subfield in the HARQ SIG field, as discussed above.
At block 1104, a communication device determines (e.g., the network interface 122/162 determines, the MAC processor determines 126/166 determines, the PHY processor 130/170 determines, etc.) that a PHY data unit is to be transmitted according to a HARQ process. For example, the communication device performs a negotiation with another communication and agrees that the communication device is to transmit a HARQ PPDU to the other communication device based on the negotiation, according to an embodiment. As another example, the communication device receives a trigger frame from another communication where the trigger frame instructs the communication device to transmit trigger-based HARQ PPDU, according to another embodiment.
At block 1108, the communication device generates (e.g., the network interface 122/162 generates, the PHY processor 130/170 generates, the HARQ PPDU generator 142/192 generates, etc.) a PHY data portion of the PHY data unit. In an embodiment, generating the PHY data portion at block 1108 includes generating one or more PHY protocol service data units (PSDUs). In another embodiment, generating the PHY data portion at block 1108 includes generating a plurality of PSDUs.
In an embodiment, generating the PHY data portion of the PHY data unit at block 1108 additionally includes, in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating one or more HARQ coding units of a common length, each of the one or more HARQ coding units generated to include a respective set of one or more PSDUs among the one or more PSDUs, and individually encoding HARQ coding units among the one or more HARQ coding units. In an embodiment, individually encoding each HARQ coding unit at block 1108 comprises individually encoding each HARQ coding unit with a BCC encoder. In another embodiment, individually encoding each HARQ coding unit at block 1208 comprises individually encoding each PSDU with an LDPC encoder.
At block 1112, the communication device generates (e.g., the network interface 122/162 generates, the PHY processor 130/170 generates, the HARQ PPDU generator 142/192 generates, etc.) a PHY preamble of the PHY data unit. Generating the PHY preamble at block 812 includes generating a HARQ signal field with HARQ information regarding the PHY data unit. In an embodiment, generating the HARQ signal field includes i) generating a common information subfield to indicate one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units and ii) generating a respective HARQ coding unit information subfield for each of the one or more HARQ coding units to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units. Generating the common-length HARQ coding units at block 1108, and including the one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units in the common information subfield of the HARQ signal field at block 1112, rather than including corresponding parameters (that do not commonly apply to each of at least some coding units, for example) in each respective HARQ coding unit information subfield, generally reduces overhead associated with transmission of the HARQ signal field, in at least some embodiments.
In an embodiment, a method for generating a physical layer (PHY) data unit for transmission in a wireless local area network (WLAN) includes determining, at a communication device, that the PHY data unit is to be transmitted according to a hybrid automatic repeat request (HARQ) process, and generating, at the communication device, a PHY data portion of the PHY data unit. Generating the PHY data portion comprises generating one or more PHY protocol service data units (PSDUs), and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating one or more HARQ coding units of a common length, each of the one or more HARQ coding units generated to include a respective set of one or more PSDUs among the one or more PSDUs, and individually encoding HARQ coding units among the one or more HARQ coding units. The method also includes generating, at the communication device, a PHY preamble of the PHY data unit, including generating a HARQ signal field with HARQ information regarding the PHY data unit, wherein generating the HARQ signal field includes i) generating a common information subfield to indicate one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units and ii) generating a respective HARQ coding unit information subfield for each of the one or more HARQ coding units to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units.
In other embodiments, the method also includes one of, or any suitable combination of two or more of, the following features.
Generating the common information subfield field comprises generating the common information subfield to include a duration indication to indicate the common length of the one or more HARQ coding units.
Generating the common information subfield field comprises generating the common information subfield to include padding information that indicates a number of padding bits that were added to each of the one or more HARQ coding units.
Generating the common information subfield field comprises generating the common information subfield to include an indicator of whether an extra OFDM symbol segment was included for each of the one or more HARQ coding unit in connection with low density parity check (LDPC) encoding of information in the HARQ coding unit.
Generating the respective HARQ coding unit information subfields comprises generating a particular HARQ coding unit information subfield to include i) an index uniquely identifying the corresponding HARQ coding unit and ii) a transmission version indicator indicating a) that the corresponding HARQ coding unit is an initial transmission of the HARQ coding unit or b) a transmission number corresponding to a retransmission of the corresponding HARQ coding unit.
Generating the one or more HARQ coding unit comprises generating at least one HARQ coding unit to include an initial transmission of one or more PSDUs and at least one HARQ coding unit to include a HARQ retransmission of one or more PSDUs.
Generating a particular HARQ coding unit information subfield among the respective HARQ coding unit information subfields comprises: determining whether the corresponding HARQ coding unit includes an initial transmission of the corresponding one or more PSDUs or a HARQ retransmission of the corresponding one or more PSDUs, in response to determining that the corresponding HARQ coding unit includes a HARQ retransmission of the corresponding one or more PSDUs, generating the particular HARQ coding specific subfield to include one or more retransmission specific subfields to indicate one or more parameters that are specific to the retransmission of the corresponding one or more PSDUs, and in response to determining that the corresponding HARQ coding unit is an initial transmission of the HARQ coding retransmission, generating the particular HARQ coding unit information subfield to exclude the one or more retransmission specific subfields.
Generating the PHY preamble further comprises: generating a regular signal field to be transmitted in the PHY preamble prior to transmission of the HARQ signal field in the PHY preamble, and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating the regular signal field to include in an indicator to indicate that the PHY preamble includes the HARQ signal field following the regular signal field.
The PHY data unit is a multi-user (MU) PHY data unit to be transmitted to a plurality of other communication devices.
Generating the PHY preamble further includes generating an additional signal field that includes allocation information that allocates multiple frequency resource units (RUs) among the multiple other communication devices.
Generating the HARQ signal field comprises generating a respective HARQ user information subfield for one or more respective other communication devices, wherein each HARQ user information subfield includes a HARQ coding unit information subfield for each of one or more HARQ coding units for the respective other communication device, wherein each HARQ coding unit information subfield includes indications of respective one or respective PSDU.
The second signal field is generated to be transmitted within a first frequency subchannel.
The second signal field includes HARQ information only for PSDUs to be transmitted in one or more RUs that overlap with the first frequency subchannel.
Generating the PHY preamble further comprises generating one or more other HARQ signal fields corresponding to one or more respective second frequency subchannels, wherein each of the one or more other second signal fields are generated to include HARQ information only for HARQ coding units to be transmitted within one or more respective RUs that overlap with the respective second frequency subchannel.
In another embodiment, a wireless communication device comprises a network interface device associated with a first communication device, wherein the network interface device is implemented on one or more integrated circuit (IC) devices, and wherein the one or more IC devices are configured to: determine that the PHY data unit is to be transmitted according to a hybrid automatic repeat request (HARQ) process; generate a PHY data portion of the PHY data unit, comprising: generating one or more PHY protocol service data units (PSDUs), and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generating one or more HARQ coding units of a common length, each of the one or more HARQ coding units generated to include a respective set of one or more PSDUs among the one or more PSDUs, and individually encoding HARQ coding units among the one or more HARQ coding units. The one or more IC devices are further configured to generate a PHY preamble of the PHY data unit, including generating a HARQ signal field with HARQ information regarding the PHY data unit, wherein generating the HARQ signal field includes i) generating a common information subfield to indicate one or more parameters that commonly apply to each of at least some of the one or more HARQ coding units and ii) generating a respective HARQ coding unit information subfield for each of the one or more HARQ coding units to indicate one or more parameters that apply to only the corresponding HARQ coding unit among the one or more HARQ coding units.
In other embodiments, the wireless communication device also comprises one of, or any suitable combination of two or more of, the following features.
The one or more IC devices are configured to generate the common information subfield to include a duration indication to indicate the common length of the one or more HARQ coding units.
The one or more IC devices are configured to generate the common information subfield to include padding information that indicates a number of padding bits that were added to each of the one or more HARQ coding units.
The one or more IC devices are configured to generate the common information subfield to include an indicator of whether an extra OFDM symbol segment was included for each of the one or more HARQ coding unit in connection with low density parity check (LDPC) encoding of information in the HARQ coding unit.
The one or more IC devices are configured to generate the respective HARQ coding unit information subfields to include, in a particular HARQ coding unit information subfield, i) an index uniquely identifying the corresponding HARQ coding unit and ii) a transmission version indicator indicating a) that the corresponding HARQ coding unit is an initial transmission of the HARQ coding unit or b) a transmission number corresponding to a retransmission of the corresponding HARQ coding unit.
The one or more IC devices are configured to generate the one or more HARQ coding unit at least by generating at least one HARQ coding unit to include an initial transmission of one or more PSDUs and at least one HARQ coding unit to include a HARQ retransmission of one or more PSDUs.
The one or more IC devices are further configured to: determine whether the corresponding HARQ coding unit includes an initial transmission of the corresponding one or more PSDUs or a HARQ retransmission of the corresponding one or more PSDUs, in response to determining that the corresponding HARQ coding unit includes a HARQ retransmission of the corresponding one or more PSDUs, generate the particular HARQ coding specific subfield to indicate one or more retransmission specific subfields to indicate one or more parameters that are specific to the retransmission of the HARQ coding unit, and in response to determining that the corresponding HARQ coding unit is an initial transmission of the HARQ coding retransmission, generate the particular HARQ coding information subfield to exclude the one or more retransmission specific subfields.
The one or more IC devices are further configured to: generate a regular signal field to be transmitted in the PHY preamble prior to transmission of the HARQ signal field in the PHY preamble, and in response to determining that the PHY data unit is to be transmitted according to the HARQ process, generate the regular signal field to include in an indicator to indicate that the PHY preamble includes the HARQ signal field following the regular signal field.
The PHY data unit is a multi-user (MU) PHY data unit to be transmitted to a plurality of other communication devices.
The one or more IC devices are further configured to: generate the PHY preamble to include an additional signal field that includes allocation information that allocates multiple frequency resource units (RUs) among the multiple other communication devices, and generate a respective HARQ user information subfield for one or more respective other communication devices, wherein each HARQ user information subfield includes a HARQ coding unit information subfield for each of one or more HARQ coding units for the respective other communication device, wherein each HARQ coding unit information subfield includes indications of respective one or respective PSDU.
The HARQ signal field is generated to be transmitted within a first frequency subchannel.
The HARQ signal field includes HARQ information only for PSDUs to be transmitted in one or more RUs that overlap with the first frequency subchannel.
The one or more IC devices are further configured to generate the PHY preamble to further include one or more other HARQ signal fields corresponding to one or more respective second frequency subchannels, wherein each of the one or more other second signal fields are generated to include HARQ information only for HARQ coding units to be transmitted within one or more respective RUs that overlap with the respective second frequency subchannel.
At least some of the various blocks, operations, and techniques described above may be implemented utilizing hardware, a processor executing firmware instructions, a processor executing software instructions, or any combination thereof. When implemented utilizing a processor executing software or firmware instructions, the software or firmware instructions are stored in a computer readable memory such as a random access memory (RAM), a read only memory (ROM), a flash memory, etc. The software or firmware instructions include machine readable instructions that, when executed by one or more processors, cause the one or more processors to perform various acts.
When implemented in hardware, the hardware may comprise one or more of discrete components, an integrated circuit, an application-specific integrated circuit (ASIC), a programmable logic device (PLD), etc.
While the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, changes, additions and/or deletions may be made to the disclosed embodiments without departing from the scope of the invention.
This application claims the benefit of U.S. Provisional Patent Application No. 62/857,666, entitled “Hybrid ARQ (HARQ) Transmission Enabler-Encoder and Preamble Design,” filed on Jun. 5, 2019, which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6718497 | Whitby-Strevens | Apr 2004 | B1 |
| 7054296 | Sorrells et al. | May 2006 | B1 |
| 8175015 | Chowdhuri et al. | May 2012 | B1 |
| 8599803 | Zhang et al. | Dec 2013 | B1 |
| 9319174 | Merlin et al. | Apr 2016 | B2 |
| 9351333 | Zhang et al. | May 2016 | B1 |
| 9369240 | Pirskanen et al. | Jun 2016 | B2 |
| 9876614 | Sun | Jan 2018 | B1 |
| 10135582 | Sun et al. | Nov 2018 | B1 |
| 20050180315 | Chitrapu et al. | Aug 2005 | A1 |
| 20060050742 | Grandhi et al. | Mar 2006 | A1 |
| 20070186134 | Singh et al. | Aug 2007 | A1 |
| 20070245205 | Popovski et al. | Oct 2007 | A1 |
| 20080165670 | Tao et al. | Jul 2008 | A1 |
| 20090031185 | Xhafa et al. | Jan 2009 | A1 |
| 20090074088 | Tao et al. | Mar 2009 | A1 |
| 20090219851 | Abraham et al. | Sep 2009 | A1 |
| 20090219870 | Wengerter et al. | Sep 2009 | A1 |
| 20090259915 | Livshitz et al. | Oct 2009 | A1 |
| 20100054189 | Chang et al. | Mar 2010 | A1 |
| 20110038332 | Liu et al. | Feb 2011 | A1 |
| 20110134816 | Liu et al. | Jun 2011 | A1 |
| 20110199971 | Kim et al. | Aug 2011 | A1 |
| 20110305176 | Wentink | Dec 2011 | A1 |
| 20120140753 | Lee et al. | Jun 2012 | A1 |
| 20130229996 | Wang et al. | Sep 2013 | A1 |
| 20130315139 | Abraham et al. | Nov 2013 | A1 |
| 20140079016 | Dai et al. | Mar 2014 | A1 |
| 20140126580 | Sampath et al. | May 2014 | A1 |
| 20140185695 | Kenney et al. | Jul 2014 | A1 |
| 20140293868 | Levanen et al. | Oct 2014 | A1 |
| 20150049677 | Lin et al. | Feb 2015 | A1 |
| 20150063233 | Choi et al. | Mar 2015 | A1 |
| 20160380727 | Ryu et al. | Dec 2016 | A1 |
| 20170230149 | Wang et al. | Aug 2017 | A1 |
| 20180102929 | Lin et al. | Apr 2018 | A1 |
| 20180302256 | Huang et al. | Oct 2018 | A1 |
| 20190222680 | Chu | Jul 2019 | A1 |
| 20200136753 | Zhang | Apr 2020 | A1 |
| 20200136764 | Zhang | Apr 2020 | A1 |
| 20200195376 | Zhang | Jun 2020 | A1 |
| 20200280399 | Kim | Sep 2020 | A1 |
| 20200329519 | Cao | Oct 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-2009120460 | Oct 2009 | WO |
| Entry |
|---|
| International Search Report and Written Opinion in International Patent Application No. PCT/US2020/036502, dated Sep. 30, 2020 (18 pages). |
| Fang et al., “Efficient channel access scheme for multiuser parallel transmission under channel bonding in IEEE 802.11ac,” The Institution of Engineering and Technology, IET Commun., vol. 9, Issue 13, pp. 1591-1597 (Apr. 12, 2015). |
| IEEE Draft 802.11ax D3.2, “Draft Standard for Information Technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific rqeuirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications—Amendment 1: Enhancements for High . . . ” vol. 802.11ax drafts, No. D3.2, pp. 1-698 (Oct. 16, 2018). |
| IEEE P802.11axTM/D5.0, “Draft Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 1: Enhancements for High Efficiency WLAN,” IEEE Computer Society, 772 pages (Oct. 2019). |
| IEEE P802.15.4m/D3, May 2013 IEEE Standard for Local metropolitan area networks—“Part 15.4: Low Rate Wireless Personal Area Networks (LR-WPANs)”, Amendment 6: TV White Space Between 54 MHz and 862 MHz Physical Layer, Excerpt, 2 pages (May 2013). |
| IEEE Std 802.11-REVmcTM/D8.0 (revision of IEEE Std. 802.11TM-2012) “Draft Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements” Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, The Institute of Electrical and Electronics Engineers, Inc., 3774 pages (Aug. 2016). |
| Kwon et al., “SIG Structure for UL PPDU,” IEEE Draft, doc. IEEE 802.11-15/0574r0, vol. 802.11ax, 18 pages (May 11, 2015). |
| U.S. Appl. No. 16/912,643, Zhang et al., “Physical Layer (PHY) Data Unit Encoding for Hybrid Automatic Repeat Request (HARQ) Transmission,” filed Jun. 25, 2020. |
| Number | Date | Country | |
|---|---|---|---|
| 20200389259 A1 | Dec 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62857666 | Jun 2019 | US |
