Coding scheme indication for 802.11 bn

Abstract

The invention relates to a coding scheme indication for 802.11 BN. An apparatus and method of communicating coding types are disclosed. The coding types include binary convolutional coding (BBC), legacy boosted low density parity check (LDPC) codes, and boosted LDPC codes whose length is a multiple of a maximum legacy LDPC code. The number of bits in the user information field for indicating the encoding type depends on whether a plurality of lifting LDPC codes are available for encoding, whether the lifting LDPC code is an optional encoding type, or a payload size. A frame containing a user information field is transmitted to another STA, and a response contains a payload encoded with the indicated encoding type.

Description

Technical Field

[0001] Embodiments relate to wireless networks and wireless communications. Some embodiments relate to wireless local area networks (WLANs) and Wi-Fi networks, including networks operating according to the IEEE 802.11 family of standards. Some embodiments relate to coding type indication in Ultra High Reliability (UHR) signals. Background Art

[0002] LDPC codes are linear error correction codes used to provide error correction in noisy channels of communication systems, thereby achieving faster and more robust communications. LDPC codes are functionally defined by a sparse parity check matrix that can be randomly generated. Based on the introduction of new codeword lengths, it is desirable to update the coding mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure is illustrated by way of example and not limitation in the accompanying figures in which like references indicate similar elements, and in which:

[0004] Figure 1 is a block diagram of a radio architecture according to some embodiments;

[0005] Figure 2 illustrates a front end module (FEM) circuit according to some embodiments;

[0006] Figure 3 illustrates a radio integrated circuit (IC) circuit in accordance with some embodiments;

[0007] Figure 4 illustrates a functional block diagram of a baseband processing circuit according to some embodiments;

[0008] Figure 5 illustrates a wireless local area network (WLAN) according to some embodiments;

[0009] Figure 6 is a network diagram illustrating an example network environment according to some embodiments;

[0010] Figure 7 is the format of the user information field of a trigger frame according to some embodiments;

[0011] Figure 8 is a flow chart of an example method for communicating using a coding scheme according to some embodiments;

[0012] Fig. 9 illustrates a block diagram of an example machine on which any one or more of the techniques (eg, methodologies) discussed herein may be performed; and

[0013] Fig.10 Illustrated is a block diagram of an example wireless device upon which any one or more of the techniques (eg, methods, or operations) discussed herein may be performed. DETAILED DESCRIPTION

[0014] The following description and the accompanying drawings sufficiently illustrate the specific embodiments to enable those skilled in the art to implement them. Other embodiments may contain structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in other embodiments, or replace portions and features of other embodiments. The embodiments outlined in the claims cover all available equivalents of these claims.

[0015] Figure 1 1 is a block diagram of a radio architecture 100 according to some embodiments. The radio architecture 100 may include a radio front-end module (FEM) circuit 104, a radio IC circuit 106, and a baseband processing circuit 108. As shown, the radio architecture 100 includes both a wireless local area network (WLAN) function and a Bluetooth (BT) function, although the embodiments are not limited thereto. In the present disclosure, "WLAN" and "Wi-Fi" are used interchangeably.

[0016] The FEM circuit 104 may include a WLAN (or Wi-Fi) FEM circuit 104A and a Bluetooth (BT) FEM circuit 104B. The WLAN FEM circuit 104A may include a receive signal path including circuitry configured to operate on WLAN RF signals received from one or more antennas 101, amplify the received signals, and provide an amplified version of the received signals to the WLAN radio IC circuit 106A for further processing. The BT FEM circuit 104B may include a receive signal path including circuitry configured to operate on BT RF signals received from one or more antennas 101, amplify the received signals, and provide an amplified version of the received signals to the BT radio IC circuit 106B for further processing. The WLAN FEM circuit 104A may also include a transmit signal path including circuitry configured to amplify WLAN signals provided by the WLAN radio IC circuit 106A for wireless transmission by the one or more antennas 101. Additionally, the BT FEM circuit 104B may also include a transmit signal path that may include circuitry configured to amplify BT signals provided by the radio IC circuit 106B for wireless transmission by one or more antennas. Figure 1 In the embodiment of the present invention, although the WLAN FEM circuit 104A and the BT FEM circuit 104B are shown as being distinguished from each other, the embodiments are not limited thereto and include within their scope the use of a FEM (not shown) that includes a transmit path and / or receive path for both WLAN and BT signals, or the use of one or more FEM circuits in which at least some of the FEM circuits share transmit and / or receive signal paths for both WLAN and BT signals.

[0017] The radio IC circuit 106 may include a WLAN radio IC circuit 106A and a BT radio IC circuit 106B as shown. The WLAN radio IC circuit 106A may include a receive signal path that may include circuitry to down-convert a WLAN RF signal received from the WLAN FEM circuit 104A and provide a baseband signal to the WLAN baseband processing circuit 108A. The BT radio IC circuit 106B may in turn include a receive signal path that may include circuitry to down-convert a BT RF signal received from the BT FEM circuit 104B and provide a baseband signal to the BT baseband processing circuit 108B. The WLAN radio IC circuit 106A may also include a transmit signal path that may include circuitry to up-convert a WLAN baseband signal provided by the WLAN baseband processing circuit 108A and provide a WLAN RF output signal to the WLAN FEM circuit 104A for subsequent wireless transmission by one or more antennas 101. The BT radio IC circuit 106B may also include a transmit signal path that may include circuitry to up-convert the BT baseband signal provided by the BT baseband processing circuit 108B and provide a BT RF output signal to the BT FEM circuit 104B for subsequent wireless transmission by one or more antennas 101. Figure 1 In the embodiment of the present invention, although the radio IC circuits 106A and 106B are shown as being distinguished from each other, the embodiments are not limited thereto and include within their scope the use of a radio IC circuit (not shown) that includes a transmit signal path and / or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuits in which at least some of the radio IC circuits share transmit and / or receive signal paths for both WLAN and BT signals.

[0018] The baseband processing circuit 108 may include a WLAN baseband processing circuit 108A and a BT baseband processing circuit 108B. The WLAN baseband processing circuit 108A may include a memory, such as a set of RAM arrays in a fast Fourier transform or inverse fast Fourier transform block (not shown) of the WLAN baseband processing circuit 108A. Each of the WLAN baseband processing circuit 108A and the BT baseband processing circuit 108B may also include one or more processors and control logic to process signals received from the corresponding WLAN or BT receive signal path of the radio IC circuit 106, and also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuit 106. Each of the baseband processing circuits 108A and 108B may also include a physical layer (PHY) and a medium access control layer (MAC) circuit, and may also interface with the application processor 111 to perform baseband signal generation and processing and control operations of the radio IC circuit 106.

[0019] Still reference Figure 1 According to the illustrated embodiment, the WLAN-BT coexistence circuit 113 may include logic to provide an interface between the WLAN baseband processing circuit 108A and the BT baseband processing circuit 108B to implement use cases requiring WLAN and BT coexistence. In addition, a switch 103 may be provided between the WLAN FEM circuit 104A and the BT FEM circuit 104B to allow switching between WLAN and BT radios as required by the application. In addition, while one or more antennas 101 are depicted as being connected to the WLAN FEM circuit 104A and the BT FEM circuit 104B, respectively, embodiments include within their scope sharing one or more antennas between the WLAN and BT FEM, or providing more than one antenna connected to each of the WLAN FEM circuit 104A or the BT FEM circuit 104B.

[0020] In some embodiments, FEM circuitry 104, radio IC circuitry 106, and baseband processing circuitry 108 may be provided on a single radio card, such as wireless radio card 102. In some other embodiments, one or more antennas 101, FEM circuitry 104, and radio IC circuitry 106 may be provided on a single radio card. In some other embodiments, radio IC circuitry 106 and baseband processing circuitry 108 may be provided on a single chip or IC, such as IC 112.

[0021] In some embodiments, wireless radio card 102 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, radio architecture 100 may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multi-carrier communication channel. OFDM or OFDMA signals may include multiple orthogonal subcarriers.

[0022] In some of these multi-carrier embodiments, the radio architecture 100 may be part of a Wi-Fi communication station (STA), such as a wireless access point (AP), a base station, or a mobile device including a Wi-Fi device. In some of these embodiments, the radio architecture 100 may be configured to send and receive signals in accordance with a specific communication standard and / or protocol, such as any standard of the Institute of Electrical and Electronics Engineers (IEEE), including IEEE 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, IEEE 802.11ac, and / or IEEE 802.11ax, and / or IEEE 802.11be standards and / or proposed specifications for WLANs, although the scope of the embodiments is not limited in this regard. The radio architecture 100 may also be adapted to send and / or receive communications in accordance with other technologies and standards.

[0023] In some embodiments, the radio architecture 100 may be configured for high-efficiency Wi-Fi (HEW), extremely high throughput (EHT), and ultra high reliability (UHR) communications in accordance with IEEE 802.11ax, 802.11be, and 802.11bn standards. In these embodiments, the radio architecture 100 may be configured to communicate in accordance with OFDMA technology, although the scope of the embodiments is not limited in this respect.

[0024] In some other embodiments, the radio architecture 100 may be configured to send and receive signals sent using one or more other modulation techniques, such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and / or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and / or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.

[0025] In some embodiments, Figure 1 As further shown, the BT baseband processing circuit 108B may comply with a Bluetooth (BT) connectivity standard, such as Bluetooth, Bluetooth 4.0, or Bluetooth 5.0, or any other iteration of the Bluetooth standard. Figure 1 In the illustrated embodiments including BT functionality, the radio architecture 100 may be configured to establish a BT synchronous connection-oriented (SCO) link and / or a BT low energy (BT LE) link. In some embodiments including functionality, the radio architecture 100 may be configured to establish an extended SCO (eSCO) link for BT communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments including BT functionality, the radio architecture may be configured to participate in BT asynchronous connectionless (ACL) communications, although the scope of the embodiments is not limited in this respect. In some embodiments, such as Figure 1 As shown, the functionality of a BT radio card and a WLAN radio card may be combined on a single wireless radio card, such as wireless radio card 102, although embodiments are not so limited and include separate WLAN and BT radio cards within their scope.

[0026] In some embodiments, the radio architecture 100 may include other radio cards, such as a cellular radio card configured for cellular (e.g., 3GPP such as LTE, LTE Advanced, or 5G communications).

[0027] In some IEEE 802.11 embodiments, the radio architecture 100 can be configured for communication over various channel bandwidths, including bandwidths with center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5 MHz, 8 MHz, 10 MHz, 16 MHz, 20 MHz, 40 MHz, 80 MHz (with continuous bandwidth), or 80+80 MHz (160 MHz) (with non-continuous bandwidth). In some embodiments, a 320 MHz channel bandwidth can be used. However, the scope of the embodiments is not limited to the above center frequencies.

[0028] Figure 2 FIG. 2 shows a FEM circuit 200 according to some embodiments. The FEM circuit 200 is suitable for use as ( Figure 1 ) is one example of a circuit for the WLAN FEM circuit 104A and / or the BT FEM circuit 104B, although other circuit configurations may also be appropriate.

[0029] In some embodiments, the FEM circuit 200 may include a TX / RX switch 202 to switch between transmit mode and receive mode operation. The FEM circuit 200 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 200 may include a low-noise amplifier (LNA) 206 to amplify the received RF signal 203 and provide an amplified received RF signal 207 as an output (e.g., to the radio IC circuit 106 ( Figure 1 )). The transmit signal path of the FEM circuit 200 may include a power amplifier (PA) to amplify an input RF signal 209 (e.g., provided by the radio IC circuit 106), and one or more filters 212, such as a band-pass filter (BPF), a low-pass filter (LPF), or other types of filters, to generate an RF signal 215 for subsequent transmission (e.g., by one or more antennas 101 ( Figure 1) transmission). In some multi-mode embodiments for Wi-Fi communication, the FEM circuit 200 may be configured to operate in any one of the 2.4 GHz spectrum, the 5 GHz spectrum, and the 6 GHz spectrum. In these embodiments, the receive signal path of the FEM circuit 200 may include a receive signal path duplexer 204 to separate the signals from each spectrum and provide a separate LNA 206 for each spectrum, as shown. In these embodiments, the transmit signal path of the FEM circuit 200 may also include a power amplifier 210 and one or more filters 212, such as a BPF, LPF, or another type of filter for each spectrum, and a transmit signal path duplexer 214 to provide a signal of one of the different spectrums onto a single transmit path for subsequent transmission by one or more antennas 101 ( Figure 1 In some embodiments, BT communications may utilize a 2.4 GHz signal path and may utilize the same FEM circuit 200 as used for WLAN communications.

[0030] Figure 3 1 shows a radio integrated circuit (IC) circuit 300 according to some embodiments. The radio IC circuit 300 is suitable for use as ( Figure 1 ) is one example of a circuit for a WLAN radio IC circuit 106A or a BT radio IC circuit 106B, although other circuit configurations may also be appropriate.

[0031] In some embodiments, the radio IC circuit 300 may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuit 300 may include a mixer circuit 302, such as a down-conversion mixer circuit, an amplifier circuit 306, and a filter circuit 308. The transmit signal path of the radio IC circuit 300 may include a filter circuit 312 and a mixer circuit 314, such as an up-conversion mixer circuit. The radio IC circuit 300 may also include a synthesizer circuit 304 for synthesizing a frequency 305 for use by the mixer circuit 302 and the mixer circuit 314. According to some embodiments, the mixer circuits 302 and / or 314 may each be configured to provide a direct conversion function. Compared to a standard superheterodyne mixer circuit, the latter type of circuit presents a much simpler architecture, and any flicker noise introduced therefrom may be mitigated, for example, by using OFDM modulation. Figure 3Only a simplified version of the radio IC circuit is illustrated, and although not shown, embodiments may include that each of the depicted circuits may include more than one component. For example, mixer circuits 302 and / or 314 may each include one or more mixers, and filter circuits 308 and / or 312 may each include one or more filters, such as one or more BPFs and / or LPFs, as required by the application. For example, when the mixer circuits are of the direct conversion type, they may each include two or more mixers.

[0032] In some embodiments, mixer circuit 302 may be configured to generate a frequency signal from FEM circuit 104 ( Figure 1 ) down-converts the received RF signal 207. The amplifier circuit 306 may be configured to amplify the down-converted signal, and the filter circuit 308 may include an LPF configured to remove unwanted signals from the down-converted signal to generate an output baseband signal 307. The output baseband signal 307 may be provided to the baseband processing circuit 108 ( Figure 1 ) for further processing. In some embodiments, output baseband signal 307 may be a zero frequency baseband signal, although this is not a necessary requirement. In some embodiments, mixer circuit 302 may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0033] In some embodiments, mixer circuit 314 may be configured to up-convert baseband signal 311 based on frequency 305 provided by synthesizer circuit 304 to generate RF signal 209 for FEM circuit 104. Baseband signal 311 may be provided by baseband processing circuit 108 and may be filtered by filter circuit 312. Filter circuit 312 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.

[0034] In some embodiments, mixer circuit 302 and mixer circuit 314 may each include two or more mixers and may be arranged for quadrature down-conversion and / or up-conversion, respectively, with the aid of synthesizer circuit 304. In some embodiments, mixer circuit 302 and mixer circuit 314 may each include two or more mixers, each mixer being configured for image rejection (e.g., Hartley image rejection). In some embodiments, mixer circuit 302 and mixer circuit 314 may each be arranged for direct down-conversion and / or direct up-conversion, respectively. In some embodiments, mixer circuit 302 and mixer circuit 314 may be configured for superheterodyne operation, although this is not a necessary requirement.

[0035] According to one embodiment, mixing circuit 302 may include: quadrature passive mixers (eg, for in-phase (I) and quadrature-phase (Q) paths). In such an embodiment, Figure 3 The RF signal 207 may be downconverted to provide I and Q baseband output signals to be sent to a baseband processor.

[0036] The quadrature passive mixers may be driven by zero and ninety degree time varying LO switching signals provided by a quadrature circuit that may be configured to receive LO frequencies (LO) from a local oscillator or synthesizer, such as synthesizer circuit 304 ( Figure 3 ) frequency 305. In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be some fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero-degree and ninety-degree time-varying switching signals may be generated by a synthesizer, although the scope of the embodiments is not limited in this respect.

[0037] In some embodiments, the LO signal can vary in duty cycle (the percentage of a cycle that the LO signal is high) and / or offset (the difference between the start points of the cycle). In some embodiments, the LO signal can have a 25% duty cycle and a 50% offset. In some embodiments, each branch of the mixer circuit (e.g., the in-phase (I) and quadrature-phase (Q) paths) can operate at a 25% duty cycle, which can result in a significant reduction in power consumption.

[0038] RF signal 207( Figure 2 ) may include balanced signals, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to a low noise amplifier, such as amplifier circuit 306 ( Figure 3 ) or filter circuit 308 ( Figure 3 ).

[0039] In some embodiments, output baseband signal 307 and baseband signal 311 may be analog, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, output baseband signal 307 and baseband signal 311 may be digital. In these alternative embodiments, the radio IC circuit may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits.

[0040] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, or for other spectrums not mentioned herein, although the scope of the embodiments is not limited in this respect.

[0041] In some embodiments, synthesizer circuit 304 may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be appropriate. For example, synthesizer circuit 304 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider. According to some embodiments, synthesizer circuit 304 may include a digital synthesizer circuit. One advantage of using a digital synthesizer circuit is that, while it may still include some analog components, its footprint may be much reduced than that of an analog synthesizer circuit. In some embodiments, the frequency input to synthesizer circuit 304 may be provided by a voltage-controlled oscillator (VCO), although this is not a necessary requirement. Depending on the desired output frequency, the divider control input may also be provided by baseband processing circuit 108 ( Figure 1 ) or application processor 111 ( Figure 1 ) is provided. In some embodiments, the divider control input (eg, N) may be determined from a lookup table (eg, within a Wi-Fi card) based on the channel number and channel center frequency determined or indicated by the application processor 111.

[0042] In some embodiments, synthesizer circuit 304 may be configured to generate a carrier frequency as frequency 305, while in other embodiments, frequency 305 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, frequency 305 may be an LO frequency (LO).

[0043] Figure 4 4 is a functional block diagram of a baseband processing circuit 400 according to some embodiments. The baseband processing circuit 400 is a circuit that can be used as the baseband processing circuit 108 ( Figure 1 ) is an example of a circuit that may be used to process signals received by radio IC circuit 106 ( Figure 1 ) and a transmit baseband processor 404 for generating a baseband signal 311 for the radio IC circuit 106. The baseband processing circuit 400 may also include a control logic 406 for coordinating the operation of the baseband processing circuit 400.

[0044] In some embodiments (e.g., when analog baseband signals are exchanged between baseband processing circuitry 400 and radio IC circuitry 106), baseband processing circuitry 400 may include ADC 410 to convert analog baseband signals received from radio IC circuitry 106 into digital baseband signals for processing by receive baseband processor 402. In these embodiments, baseband processing circuitry 400 may also include DAC 412 to convert digital baseband signals from transmit baseband processor 404 into analog baseband signals.

[0045] In some embodiments where an OFDM signal or an OFDMA signal is transmitted, for example, by the WLAN baseband processing circuit 108A, the transmit baseband processor 404 may be configured to generate an OFDM or OFDMA signal suitable for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 402 may be configured to process the received OFDM or OFDMA signal by performing an FFT. In some embodiments, the receive baseband processor 402 may be configured to detect the presence of the OFDM or OFDMA signal by performing an autocorrelation to detect a preamble such as a short preamble, and to detect the presence of the OFDM or OFDMA signal by performing a cross-correlation to detect a long preamble. The preamble may be part of a predetermined frame structure for Wi-Fi communications.

[0046] refer to Figure 1 In some embodiments, one or more antennas 101 ( Figure 1 ) may each include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to exploit spatial diversity and the different channel characteristics that may result. One or more antennas 101 may each include a set of phased array antennas, although embodiments are not limited thereto.

[0047] Although the radio architecture 100 is shown as having several separate functional elements, one or more of these functional elements may be combined and may be implemented by a combination of software-configured elements (e.g., processing elements including digital signal processors (DSPs)) and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements.

[0048] Figure 5 A WLAN 500 is illustrated in accordance with some embodiments. The WLAN 500 may include a basis service set (BSS), which may include an EHT access point (AP) 502 (which may be referred to as an AP), a plurality of extremely high throughput (EHT) (e.g., IEEE 802.11be) stations (STAs) 504, and legacy devices 506 (e.g., IEEE 802.11g / n / ac / ax devices). In some aspects, the AP 502 is a UHR AP. In some embodiments, the UHR STA 504 and / or the AP 502 are configured to operate in accordance with IEEE 802.11bn. In some embodiments, the UHR STA 504 and / or the AP 502 are configured to operate in accordance with IEEE 802.11bn. In some embodiments, IEEE 802.11bn UHR may be referred to as the next generation 802.11. In some embodiments, the AP 502 may be configured to operate a UHR BSS, an ER BSS, and / or a BSS. Legacy devices may not be able to operate in a UHR BSS, and beacon frames in a UHR BSS may be sent using UHR PPDUs. An ER BSS may use ER PPDUs to send beacon frames, and legacy devices 506 may not be able to decode the beacon frames and thus may not be able to operate in the ER BSS. BSSs, such as BSSs, ERBSSs, and UHR BSSs, may use different BSSIDs.

[0049] AP 502 may be an AP that uses IEEE 802.11 for transmission and reception. AP 502 may be a base station. AP 502 may use other communication protocols in addition to the IEEE 802.11 protocol. The IEEE 802.11 protocol may be IEEE802.11bn. The IEEE 802.11 protocol may be the next generation of IEEE 802.11. The UHR protocol may be called by different names according to some embodiments. The IEEE 802.11 protocol may include the use of orthogonal frequency division multiple access (orthogonal frequency division multiple-access, OFDMA), time division multiple access (time division multiple access, TDMA), and / or code division multiple access (code division multiple access, CDMA). The IEEE 802.11 protocol may include multiple access technology. For example, the IEEE 802.11 protocol may include space-division multiple access (space-division multiple access, SDMA) and / or multiple-user multiple-input multiple-output (multiple-user multiple-input multiple-output, MU-MIMO). There may be more than one AP 502 that is part of an extended serviceset (ESS). A controller (not shown) may store information common to more than one UHR AP and may control more than one BSS, e.g., assigning primary channels, colors, etc. AP 502 may be connected to the Internet. AP 502 and / or UHR STA 504 may be configured for one or more of: 320 MHz bandwidth, 16 spatial streams, multi-band or multi-stream operation, and 4096QAM. In addition, AP 502 and / or UHR STA 504 may be configured to generate and process UHR PPDUs that include extensions of the PE field (e.g., dummy OFDM symbols) (e.g., as disclosed herein in conjunction with the accompanying drawings) to simultaneously meet PHY and MAC processing time requirements.

[0050] The legacy device 506 may operate in accordance with one or more of IEEE 802.11a / b / g / n / ac / ax / be / ad / af / ah / aj / ay or another legacy wireless communication standard. The legacy device 506 may be a STA or an IEEE STA. In some embodiments, when the AP 502 and the UHR STA 504 are configured to operate in accordance with IEEE 802.11bn UHR, the legacy device 506 may include a device configured to operate in accordance with IEEE 802.11ax or 802.11be. The UHR STA 504 may be a wireless transmitting and receiving device, such as a cellular phone, a portable electronic wireless communication device, a smart phone, a handheld wireless device, wireless glasses, a wireless watch, a wireless personal device, a tablet device, or another device that can transmit and receive using the IEEE 802.11 protocol (e.g., IEEE802.11bn) or another wireless protocol.

[0051] The AP 502 may communicate with the legacy device 506 in accordance with conventional IEEE 802.11 communication techniques. In an example embodiment, the AP 502 may also be configured to communicate with the UHR STA 504 in accordance with conventional IEEE 802.11 communication techniques.

[0052] In some embodiments, the EHT or UHR frame may be configured to have the same bandwidth as the channel. The EHT or UHR frame may be a Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU). In some embodiments, there may be different types of PPDUs, which may have different fields and different physical layers, and / or different medium access control (MAC) layers. For example, a single-user (SU) PPDU, a multi-user (MU) PPDU, an extended-range (ER) SU PPDU, and / or a trigger-based (TB) PPDU. In some embodiments, the UHR PPDU may be the same or similar to the EHT PPDU.

[0053] The bandwidth of the channel can be 20MHz, 40MHz or 80MHz, 80+80MHz, 160MHz, 160+160MHz, 320MHz, 320+320MHz, and 640MHz bandwidth. In some embodiments, the bandwidth of the channel less than 20MHz can be 1MHz, 1.25MHz, 2.03MHz, 2.5MHz, 4.06MHz, 5MHz, and 10MHz, or a combination thereof, or another bandwidth less than or equal to the available bandwidth can also be used. In some embodiments, the bandwidth of the channel can be based on several active data subcarriers. In some embodiments, the bandwidth of the channel is based on 26, 52, 106, 242, 484, 996, or 2x996 active data subcarriers or tones spaced 20MHz apart. In some embodiments, the bandwidth of the channel is 256 tones spaced 20MHz apart. In some embodiments, the channel is a multiple of 26 tones or a multiple of 20MHz. In some embodiments, a 20 MHz channel may include 242 active data subcarriers or tones, which may determine the size of the Fast Fourier Transform (FFT). According to some embodiments, the allocation of bandwidth or number of tones or subcarriers may be referred to as resource unit (RU) allocation.

[0054] In some embodiments, 26 subcarrier RU and 52 subcarrier RU are used in 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz OFDMA EHT or UHR PPDU formats. In some embodiments, 106 subcarrier RU is used in 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz OFDMA and MU-MIMO EHT or UHR PPDU formats. In some embodiments, 242 subcarrier RU is used in 40MHz, 80MHz, 160MHz, and 80+80MHz OFDMA and MU-MIMO EHT or UHR PPDU formats. In some embodiments, 484 subcarrier RU is used in 80MHz, 160MHz, and 80+80MHz OFDMA and MU-MIMO EHT or UHR PPDU formats. In some embodiments, 996 subcarrier RU is used in 160MHz and 80+80MHz OFDMA and MU-MIMO EHT or UHR PPDU formats.

[0055] The UHR or EHT frame may be configured to transmit several spatial streams, which may be in accordance with MU-MIMO or OFDMA. In other embodiments, the AP 502, the UHR STA 504, and / or the legacy device 506 may also implement different technologies, such as code division multiple access (CDMA) 2000, CDMA2000 1X, CDMA 2000 Evolution-Data Optimized (EV-DO), Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Long Term Evolution (LTE), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), Low Power Or other techniques.

[0056] According to some IEEE 802.11 embodiments, such as IEEE 802.11be / bn EHT / UHR embodiments, the AP 502 may operate as a master station that may be arranged to contend for the wireless medium (e.g., during a contention period) to receive exclusive control of the medium for a transmission opportunity (TXOP). The AP 502 may send a UHR / EHT trigger frame that may include a schedule for simultaneous UL transmissions from the UHR STA 504. The AP 502 may send the duration and subchannel information of the TXOP. During the TXOP, the UHR STA 504 may communicate with the AP 502 in accordance with a non-contention-based multiple access technology (e.g., OFDMA or MU-MIMO). This is different from traditional WLAN communications, in which devices communicate in accordance with contention-based communication technologies rather than multiple access technologies. During the UHR or EHT control period, the AP 502 may communicate with the UHR STA 504 using one or more UHR or EHT frames. During the TXOP, the UHR STA 504 may operate on a subchannel that is smaller than the operating range of the AP 502. During the TXOP, legacy stations refrain from communicating. Legacy stations may need to receive communications from the AP 502 to defer communications.

[0057] According to some embodiments, during the TXOP, the UHR STA 504 may contend for the wireless medium, while the legacy device 506 is excluded from contending for the wireless medium during the primary synchronization transmission. In some embodiments, the trigger frame may indicate a UL-MU-MIMO and / or UL OFDMA TXOP. In some embodiments, the trigger frame may include DL MU-MIMO and / or DL ​​OFDMA, whose schedule is indicated in the preamble of the PPDU carrying the trigger frame.

[0058] In some embodiments, the multiple access technology used during the UHR or EHT TXOP may be a scheduled OFDMA technology, although this is not a requirement. In some embodiments, the multiple access technology may be a time-division multiple access (TDMA) technology or a frequency division multiple access (FDMA) technology. In some embodiments, the multiple access technology may be a space-division multiple access (SDMA) technology. In some embodiments, the multiple access technology may be a code division multiple access (CDMA) technology.

[0059] The AP 502 may also communicate with the legacy devices 506 and / or the UHR STA 504 in accordance with conventional IEEE 802.11 communication techniques. In some embodiments, the AP 502 may also be configured to communicate with the UHR STA 504 outside of the UHR TXOP in accordance with conventional IEEE 802.11 or IEEE 802.11be / ax EHT / HE communication techniques, although this is not a requirement.

[0060] In some embodiments, the UHR STA 504 may be a "group owner" (GO) in peer-to-peer operation mode. The wireless device may be a HE or EHT or UHR station or AP 502. In some embodiments, the UHR STA 504 and / or AP 502 may be configured to operate in accordance with IEEE 802.11mc. In an example embodiment, Figure 1 The radio architecture of is configured to implement UHR STA 504 and / or AP 502. In an example embodiment, Figure 2 The front-end module circuit is configured to implement UHR STA 504 and / or AP 502. In an example embodiment, Figure 3 The radio IC circuit is configured to implement UHR STA 504 and / or AP 502. In an example embodiment, Figure 4 The baseband processing circuit is configured to implement UHR STA 504 and / or AP 502.

[0061] In an example embodiment, the UHR STA 504, the AP 502, the apparatus of the UHR STA 504, and / or the apparatus of the AP 502 may include one or more of the following: Figure 1 The radio architecture of Figure 2 Front-end module circuit, Figure 3 Radio IC circuits, and / or Figure 4 Baseband processing circuit.

[0062] In an example embodiment, Figure 1 The radio architecture of Figure 2 Front-end module circuit, Figure 3 Radio IC circuits, and / or Figure 4 The baseband processing circuit may be configured to perform the methods and operations / functions described herein in conjunction with the figures herein or may be implemented as part of a device that performs these methods and operations / functions.

[0063] In an example embodiment, UHR STA 504 and / or AP 502 are configured to perform the methods and operations / functions described herein in conjunction with the figures herein. In an example embodiment, the apparatus of UHR STA 504 and / or the apparatus of AP 502 are configured to perform the methods and functions described herein in conjunction with the figures herein. The term Wi-Fi may refer to one or more of the IEEE 802.11 communication standards. AP and STA may refer to AP 502 and / or UHR STA 504 (or EHT STA) and legacy devices 506.

[0064] In some embodiments, UHR AP STA may refer to AP 502 and / or UHR STA 504 operating as a UHR AP. In some embodiments, when UHR STA 504 does not operate as a UHR AP, it may be referred to as a UHR non-AP STA or a UHR non-AP. In some embodiments, UHR STA 504 may be referred to as a UHR AP STA or a UHR non-AP. UHR may refer to the next generation IEEE 802.11 communication protocol, which may be IEEE 802.11bn or designated by other names.

[0065] Figure 6 6 is a network diagram illustrating an example network environment according to some embodiments. A wireless network 600 may include one or more user devices 620 and at least one access point (AP) 602, which may communicate in accordance with the IEEE 802.11 communication standard. One or more user devices 620 may be non-fixed (e.g., not having a fixed location) mobile devices or may be fixed devices. In some embodiments, one or more user devices 620 and at least one AP 602 may include one or more computer systems, similar to the functional diagrams of other figures shown herein.

[0066] One or more user devices 620 and / or at least one AP 602 may be operated by one or more users 610. It should be noted that any addressable unit may be a station (STA). A STA may present a plurality of different characteristics, each of which shapes its functionality. For example, a single addressable unit may be a portable STA, a quality-of-service (QoS) STA, a subordinate STA, and a hidden STA at the same time. One or more user devices 620 and at least one AP 602 may be STAs. One or more user devices 620 and / or at least one AP 602 may operate as a personal basic service set (PBSS) control point / access point (PBSS control point / access point, PCP / AP). One or more user devices 620 (e.g., user device 624, user device 626, or user device 628) and / or at least one AP 602 may include any suitable processor-driven device, including but not limited to a mobile device or a non-mobile device, such as a static device. For example, one or more user equipment 620 and / or at least one AP 602 may include user equipment (UE), STA, AP, or another device. According to one or more IEEE 802.11 standards and / or 3GPP standards, one or more user equipment 620 and / or at least one AP 602 may also include, for example, a mesh station in a mesh network.

[0067] Any of the one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to communicate with each other via one or more communication networks 630 and / or 635 (which may be wireless or wired networks). The one or more user devices 620 may also communicate with each other peer-to-peer or directly with or without at least one AP 602. Any of the one or more communication networks 630 and / or 635 may include, but are not limited to, any of a combination of different types of suitable communication networks, such as a broadcast network, a cable network, a public network (e.g., the Internet), a private network, a wireless network, a cellular network, or any other suitable private and / or public network.

[0068] Any of the one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may include one or more communication antennas. The one or more communication antennas may be any suitable type of antenna corresponding to the communication protocol used by the one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602. Some non-limiting examples of suitable communication antennas include Wi-Fi antennas, IEEE 802.11 series standard compliant antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, and the like. The one or more communication antennas may be communicatively coupled to a radio component to send and / or receive signals, such as sending and / or receiving communication signals to and / or from the one or more user devices 620 and / or at least one AP 602.

[0069] Any one of one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to perform directional transmission and / or directional reception in conjunction with wireless communication in a wireless network. Any one of one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to perform such directional transmission and / or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays, etc.). Each of the multiple antenna arrays may be used for transmission and / or reception in a specific corresponding direction or range of directions. Any one of one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to perform any given directional transmission toward one or more defined transmission sectors. Any one of one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to perform any given directional reception from one or more defined reception sectors.

[0070] MIMO beamforming in a wireless network may be implemented using RF beamforming and / or digital beamforming. In some embodiments, when performing a given MIMO transmission, any one of the one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may be configured to use all or a subset of its one or more communication antennas to perform MIMO beamforming.

[0071] Any one of the one or more user devices 620 (e.g., user devices 624-628) and at least one AP 602 may include any appropriate radio and / or transceiver to send and / or receive radio frequency (RF) signals in a bandwidth and / or channel corresponding to a communication protocol used by any one of the one or more user devices 620 and at least one AP 602 to communicate with each other. The radio component may include hardware and / or software to modulate and / or demodulate communication signals according to a pre-established transmission protocol. The radio component may also have hardware and / or software instructions to communicate via one or more Wi-Fi and / or Wi-Fi Direct protocols, such as protocols standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. In certain example embodiments, the radio assembly, in cooperation with the communication antenna, may be configured to communicate via a 2.4 GHz channel (e.g., 802.11b, 802.11g, 802.11n, 802.11ax, 802.11be), a 5 GHz channel (e.g., 802.11n, 802.11ac, 802.11ax, 802.11be), a 60 GHz channel (e.g., 802.11ad, 802.11ay), or a 700 MHz channel (e.g., 802.11ah). The communication antenna may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list, and other 802.11 standards (e.g., next generation Wi-Fi, or other standards) may be used. In some embodiments, non-Wi-Fi protocols may be used for communication between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g., IEEE 802.11af, IEEE 702.22), white space frequencies (e.g., white space), or other packetized radio communications. The radio components may include any known receiver and baseband suitable for communicating via a communication protocol. The radio components may also include a low noise amplifier (LNA), an additional signal amplifier, an analog-to-digital (A / D) converter, one or more buffers, and a digital baseband. The IEEE Draft Specification IEEE P802.11be / D4.1, September 2023, is hereby incorporated by reference in its entirety.

[0072] As mentioned above, one of the latest versions of the IEEE 802.11 series for WLAN is 802.11bn, which supports multiple bands (2.4GHz, 5GHz, and 6GHz), a bandwidth as large as 320MHz, and data subcarrier modulation up to 4096 quadrature amplitude modulation (QAM). When data is sent through a physical (PHY) layer protocol data unit (PPDU), low-density parity check (LDPC) coding is also used for error correction. In addition to data, the PPDU also contains a preamble, which has multiple fields that provide demodulation information and other information for reception.

[0073] When using UHR, the PPDU format may be different from when using EHT or HE transmission, or may be similar to EHT and HE. The UHR PPDU format includes a multi-user PHY protocol data unit (UHR MU PPDU) and a trigger-based PHY protocol data unit (UHR TBP PDU).

[0074] The fields of the UHR PPDU may include, in sequence, a legacy short training field (L-STF), a legacy long training field (L-LTF), a legacy signal field (L-SIG), a repeated legacy signal field (RL-SIG), a universal signal field (U-SIG), a UHR signal field (UHR signal field (UHR-SIG), a UHR short training field (UHR-STF), a UHR long training field (UHR-LTF), a data field (which carries a protocol data service unit (PSDU)), and a packet extension field (PE).

[0075] The UHR PPDU format may include a multi-user PHY protocol data unit (UHR MU PPDU) and a trigger-based PHY protocol data unit (UHR TBP PDU). The UHR MU PPDU can be sent to a single user or to multiple users. The related UHR-SIG field, together with the U-SIG, provides resource unit (RU) / multiple resource unit (MRU) allocation and other information used by the STA to understand the UHR MU packet. The TB PPDU does not contain the UHR-SIG preamble field, and the UHR-STF field is twice as long as in the UHR MU PPDU to improve the performance and reliability of uplink transmission. The EHT structure can be copied to the UHR.

[0076] In operation, a STA (e.g., an AP) uses a trigger frame to assign resources and solicit responses from one or more STAs. The STA responds to the trigger frame with a UHR TB PPDU. The non-multi-user request to send (Multi-User Request ToSend, MU-RTS) trigger frame allocates resources for one or more TB PPDU transmissions from one or more STAs and solicits these TB PPDU transmissions. The MU-RTS trigger frame allocates resources for one or more PPDUs that are not TB PPDUs. The trigger frame also carries other information used by the STA to send a PPDU in response to the trigger frame. The PPDU can be a high-efficiency (HE) TB PPDU, a non-high-throughput (HT) PPDU, or a non-HT duplicate PPDU, a HE ranging null data packet (NDP), or a HETB ranging NDP, or a UHR TB PPDU.

[0077] As described above, the format of the trigger frame may differ depending on whether UHR is used. The trigger frame includes a user information field, which may be a special user information field, a HE variant user information field, an EHT variant user information field, or a UHR variant user information field. All user information fields in the user information list field of the trigger frame have the same length (unless the trigger frame is a MU-BAR (Multi-User Block Acknowledgement Request) trigger frame).

[0078] The User Information field addressed to a non-AP STA is either a HE variant, an EHT variant, or a UHR variant. If B39 of the User Information field is set to 0 and B54 of the General Information field is set to 1 in the trigger frame, the User Information field is a HE variant addressed to a non-AP EHT STA; otherwise, it is an EHT variant. B39 of the HE variant User Information field is reserved for non-EHT HE STAs. For the HE variant User Information field, B39 is set to 0 by the EHT AP, while for the EHT variant User Information field, B39 is a PS160 subfield. Table 9-45a (Valid combinations of B54 and B55 in the General Information field, B39 in the User Information field, and solicitation TB PPDU format) defines the valid combinations of B54 and B55 in the General Information field, B39 in the User Information field, the presence of special user information fields in the trigger frame, variants of the User Information field, and the corresponding TB PPDU types. Figure 7 is the format of the User Information Field 700 of a Trigger Frame according to some embodiments.

[0079] The trigger frame format includes a MAC header, followed by a general information field, followed by a user information list field or a user information field list, followed by padding, and finally a frame check sequence (FCS) field. The MAC header includes a frame control field with a length of 2 octets, followed by a duration field with a length of 2 octets, followed by a receiver address (RA) field with a length of 6 octets, and then a transmitting address (TA) field with a length of 6 octets. The frame control field sets the frame control information and includes protocol version, type, subtype, to DS, from DS, more fragments, retry, power management, more data, protected frame, and sequence subfields. The duration field sets the duration of the trigger frame. The RA and TA subfields are the addresses of the STAs that receive and send the trigger frame, respectively. The length of the general information field is 8 or more octets, the user information field list and padding each have a variable length, and the length of the FCS is 4 octets.

[0080] like Figure 7 As shown, the user information field includes multiple subfields in the EHT variant user information field 700 in the trigger frame that is not a MU-RTS trigger frame. The association identifier 12 (AID12) subfield of the EHT variant user information field is encoded and has a value between 1 and 2006. The AID12 subfield indicates the AID to which the RU is assigned. The length of the AID12 subfield is 12 bits.

[0081] The RU allocation subfield, together with the uplink (UL) bandwidth (BW) subfield in the general information field, the UL BW extension subfield in the special user information field, and the PS160 subfield in the EHT variant user information field, identifies the size and location of the RU or MRU. The mapping of B7-B1 of the RU allocation subfield and the setting of B0 of the PS160 subfield and the RU allocation subfield in the EHT variant user information field are defined in Table 9-45l (Coding of the RU allocation subfield and PS160 in the EHT variant user information field), where the bandwidth is obtained from the combination of the UL BW subfield and the UL bandwidth extension subfield defined in Table 9-45l (Coding of PS160 and RU). The length of the RU allocation field is 8 bits.

[0082] The UL FEC Coding Type subfield indicates the code type of the solicited EHT TB PPDU. In standards prior to 802.11bn, the single-bit UL FEC Coding Type subfield was set to 0 to indicate binary convolutional coding (BCC) and was set to 1 to indicate LDPC.

[0083] The UL EHT-MCS subfield indicates the EHT-MCS of the solicited EHT TB PPDU. The coding of the UL EHT-MCS subfield is defined in 36.3.8 (EHT Modulation and Coding Scheme (EHT-MCS)), and its setting is as defined in 35.5.2 (EHT UL MU Operation). The length of the UL EHT-MCS subfield is 4 bits.

[0084] The single bit B25 is reserved.

[0085] The Spatial Stream (SS) Allocation subfield indicates the spatial stream of the solicited EHT TB PPDU, and the format is defined in the SS Allocation subfield format of the EHT Variant User Information field. The 4-bit Start SS subfield of the SS Allocation subfield indicates the starting spatial stream and is set to the starting spatial stream minus 1, and the maximum value of the Start SS subfield is 7. SS Stream subfield values ​​exceeding 7 are reserved for STAs and are set to 0 if the corresponding RU or MRU is not allocated for MU-MIMO. The 2-bit SS Number subfield of the SS Allocation subfield indicates the number of spatial streams and is set to the number of spatial streams minus 1. The length of the SS Allocation subfield is 6 bits.

[0086] The UL Target Received Power subfield indicates the expected received signal power for the EHT portion of the EHT TB PPDU sent on the assigned RU, measured at the antenna connector of the AP and averaged over the antennas, and is defined in Table 9-45k (UL Target Received Power subfield in Trigger Frame). The length of the UL Target Received Power subfield is 7 bits.

[0087] The Primary / Secondary 160 (PS160) subfield is a single bit. If the size of the RU or MRU is less than or equal to 2x996 tones, the PS160 subfield is set to 0 to indicate that the RU or MRU allocation applies to the primary 160 MHz channel, and is set to 1 to indicate that the RU or MRU allocation applies to the secondary 160 MHz channel. Otherwise, the PS160 subfield is used together with the RU Allocation subfield to indicate the RU or MRU index. The settings of the PS160 subfield are as defined in Table 9-45l (Coding of the RU Allocation Subfield and PS160 in the EHT Variant User Information Field).

[0088] The configuration of the variable length Trigger Related User Information subfield is as defined in 9.3.1.22.4 (HE variant User Information field). The RA-RU Information subfield is reserved in the EHT variant User Information field.

[0089] As described above, the current IEEE 802.11ax / be standard uses 1 bit in the UL FEC coding type subfield to indicate the coding type, which indicates which of the BCC and LDPC codes are used for the trigger frame. Similarly, in Table 36-40 of 802.11be draft D.4.1—User field format for non-MU-MIMO allocation, bit 21 of the user field of the EHT-SIG indicates the coding type. Similarly, in Table 36-41 of 802.11be draft D.4.1—User field format for MU-MIMO allocation, bit 15 of the user field of the EHT-SIG indicates the coding type.

[0090]

[0091]

[0092] Table 36-40 — Non-MU-MIMO Assigned User Field Format

[0093]

[0094]

[0095] Table 36-41 —MU-MIMO Assigned User Field Format

[0096] LDPC promotion is being considered for the IEEE 802.11bn standard. The block size of the new LDPC code enhanced by the LDPC promotion technology may be twice or four times the original block size, that is, the original maximum size is 1944 bits, and the new maximum size is 3888 or 7776 bits. Since these increased block sizes will add implementation costs, LDPC codes may not be enforced for all devices operating according to the IEEE 802.11bn standard. For example, low-end products or first-generation products may not implement new LDPC codes. Therefore, three or more types of encoding, that is, BCC, LDPC, and new LDPC codes with promotion, can be selected by devices operating using the IEEE 802.11bn standard. As mentioned above, the UL FEC coding type subfield is currently limited to a single bit. However, it is obvious that a single bit may not be enough to indicate a new coding type in a PPDU preamble, a trigger frame, and other frames. Instead, multiple bits can be used in the coding type subfield to indicate which of the four different coding types are being used. An example is illustrated in Table 1.

[0097] Table 1. Two bits are used to indicate the encoding type. The values ​​of these two bits indicate

[0098] BCC, LDPC, and boosted LDPC.

[0099] Coded field value describe 0 BCC 1 LDPC 2 2x LDPC boost 3 4x LDPC boost

[0100] It is possible that the IEEE 802.11bn standard adopts a single (i.e., only one) type of boosted LDPC code. For example, a 2x boosted LDPC code or a 4x boosted LDPC code may be adopted, with a block length of 2 times and 4 times that of the corresponding original LDPC code, respectively. As shown in Table 2, this may in turn result in the use of two bits in the coding type subfield to indicate which of the three coding types is being used. Since only three coding types are used, one or more of the values ​​provided by multiple bits may be retained for later use (e.g., to indicate another coding type or another parameter of transmission).

[0101] Table 2. Two bits are used to indicate the encoding type. The values ​​of these two bits indicate

[0102] BCC, LDPC, and boosted LDPC.

[0103] Coded field value describe 0 BCC 1 LDPC 2 Boosted LDPC or Long LDPC 3 reserve

[0104] If one or more boosted LDPC codes are used as mandatory coding schemes in the IEEE 802.11bn standard and there is no optional coding scheme, the selection of a specific LDPC coding scheme can be determined according to the size of the payload (PPDU payload or MAC payload). This is similar to the existing IEEE 802.11ac / ax / be standards. For example, when the PPDU payload size exceeds a first threshold, a 2x boosted LDPC code is used; when the PPDU payload size exceeds a second threshold that is higher than the first threshold, another 2x boosted LDPC code or a 4x boosted LDPC code with a payload size greater than the previous one is used. If this is the case, a 1-bit indication is sufficient as shown in Table 3.

[0105] Table 3. One bit is used to indicate the coding type. The value of this bit indicates BCC and various LDPC respectively.

[0106] Coded field value describe 0 BCC 1 LDPC tradition and improvement

[0107] However, if a new LDPC code is adopted as optional (in addition, there are multiple mandatory coding schemes), then single-bit indication is not enough. That is, multiple bits are used, an example of which is shown in Table 4. The mandatory LDPC code may include a traditional LDPC code. In addition, the mandatory LDPC code may also include one or more lifting LDPC codes (e.g., 2x lifting LDPC codes), and the optional LDPC code may include one or more lifting LDPC codes (e.g., 4x lifting LDPC codes). In this case, if a single mandatory LDPC code type and a single optional LDPC code type are used, as described above, since only three coding types are used, one or more of the values ​​provided by multiple bits can be retained for later use (e.g., to indicate another coding type or another parameter of transmission).

[0108] Table 4. Two bits are used to indicate the encoding type. The values ​​of these two bits indicate

[0109] BCC, LDPC, and boosted LDPC.

[0110] Coded field value describe 0 BCC 1 Forced LDPC 2 Optional LDPC 3 reserve

[0111] Due to the large block size, the boosted LDPC code may be limited to being used for PPDU payload sizes exceeding a predetermined threshold (i.e., the boosted LDPC code may not be used for PPDU payload sizes below a predetermined threshold). The transmitter may therefore appropriately set the indication bit(s) of the coding type taking into account the PPDU payload size.

[0112] As an alternative to the coding type subfield, a new subfield can be introduced to the trigger frame and the PPDU preamble to indicate whether the LDPC code is promoted. The new subfield may be referred to as LDPC promotion or long LDPC. It is used together with the traditional coding type subfield. This indication maximizes the backward compatibility with the existing indication. For example, when the existing subfield of the coding type indicates the use of LDPC, the new subfield may further indicate whether the adopted LDPC has a longer block size than the existing LDPC, for example, twice as long. If the new subfield indicates that promotion is not used or non-long LDPC codes are used, traditional LDPC codes are used. The exact block size of the traditional or promoted LDPC code used may be further determined according to the indicated MCS, the number of OFDM symbols, and the allocated RU size. When the existing subfield of the coding type indicates the use of BCC, the new subfield may be retained, or ignored, or not considered, or set to a fixed value, such as 0.

[0113] Table 5. One bit is used to indicate whether the LDPC code is boosted. The value of this bit indicates LDPC without boosting and LDPC with boosting, respectively.

[0114] LDPC boost field value describe 0 No improvement 1 Apply LDPC to improve

[0115] As an alternative to the coding type subfield, the modulation and coding scheme (MCS) subfield in the PPDU preamble and trigger frame can be used to indicate the coding type of the boosted LDPC code. For example, some entries of the MCS table that maps the subfield value to the MCS indicate an MCS with a boosted LDPC code.

[0116] In some embodiments, the indication method of the new coding type may be different in the PPDU preamble and the trigger frame, because the payload of the MAC frame is larger than the payload of the PPDU preamble, so simplicity is more considered than efficiency in the MAC frame. For example, the PPDU preamble may use Table 2, while the trigger frame may use Table 5 together with the traditional coding type subfield.

[0117] Figure 8 is a flow chart of an example method 800 for communicating using a coding scheme in accordance with some embodiments. The method 800 includes operations 802, 804, and 806, which may be performed by processing circuitry in any device (eg, STA, AP) described herein.

[0118] At operation 802, the processing circuit may set a value in the UL FEC Coding Type field of the trigger frame for the coding scheme to be used. The value may depend on whether only mandatory coding schemes are used, or whether both mandatory and optional coding schemes can be used. In addition, the value may depend on either or both of the number of mandatory coding schemes used and the PPDU payload size of the UL data to be sent.

[0119] In operation 804, after setting a value in the UL FEC Coding Type field of the trigger frame, the STA may transmit the trigger frame to another STA.

[0120] In response to the trigger frame transmitted to the other STA, a response frame may be received at operation 806. The response frame may include data encoded based on the code scheme indicated in the trigger frame.

[0121] In other embodiments, the processing circuitry may set the value of the code scheme to be used in the User field of the UHR-SIG field of the UHR MU PPDU.

[0122] As described above, the AP sends a trigger frame, while the STA may only send an uplink frame or a PPDU. The STA sets the coding type in the PPDU preamble. In contrast, the AP sends both a trigger frame and other PPDUs in the PPDU. In each PPDU, the AP sets the coding type in the PPDU preamble. The coding type in the PPDU preamble specifies the coding type of the PPDU itself. The coding type in the uplink trigger frame specifies the coding type of the uplink PPDU of the STA. The two different PPDUs thus come from two different devices. The coding type subfield of the preamble specifies the coding type of the PPDU of the trigger frame. In the payload of the PPDU, there is a trigger frame with a user information field. In the user information field, the coding type subfield specifies the coding type of the uplink PPDU of the trigger frame or the STA solicited by the AP. In this example, there are two coding type subfields in the PPDU of the trigger frame.

[0123] In some embodiments, the PPDU preamble of each downlink PPDU may indicate the coding type of the downlink PPDU, and / or the user information field in the trigger frame may indicate the coding type of the uplink PPDU. The trigger frame may be sent by a legacy PHY mode (i.e., a mode other than UHR) such as non-HT, HT, VHT, HE, and EHT. In some embodiments, the coding type indication in the PPDU preamble of the uplink PPDU may be used in a non-trigger-based uplink PPDU.

[0124] Fig. 9A block diagram of an example machine 900 on which any one or more techniques (e.g., methods) discussed herein may be executed is illustrated. In alternative embodiments, the machine 900 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 900 may operate as a server machine, a client machine, or both in a server-client network environment. In an example, the machine 900 may act as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 900 may be an AP 502, a UHR station (STA) 504, a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a portable communication device, a mobile phone, a smart phone, a web appliance, a network router, a switch or a bridge, or any machine capable of executing instructions (sequential or otherwise) specifying the actions to be taken by the machine. Further, while a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

[0125] The machine (e.g., a computer system) 900 may include a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination of these), a main memory 904, and a static memory 906, some or all of which may communicate with each other via an interconnection link (e.g., a bus) 908.

[0126] Specific examples of main memory 904 include random access memory (RAM) and semiconductor memory devices, which in some embodiments may include storage locations in a semiconductor, such as registers. Specific examples of static memory 906 include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices); magnetic disks (e.g., internal hard disks and removable disks); magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0127] The machine 900 may also include a display device 910, an input device 912 (e.g., a keyboard), and a user interface (UI) navigation device 914 (e.g., a mouse). In one example, the display device 910, the input device 912, and the UI navigation device 914 may be a touch screen display. The machine 900 may also include a storage device (e.g., a drive unit) 916, a signal generating device 918 (e.g., a speaker), a network interface device 920, and one or more sensors 921 (e.g., a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors). The machine 900 may include an output controller 928, such as a serial bus (e.g., a universal serial bus (USB)), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with one or more peripheral devices (e.g., a printer, a card reader, etc.) or control one or more peripheral devices. In some embodiments, processor 902 and / or instructions 924 may include processing circuitry and / or transceiver circuitry.

[0128] The storage device 916 may include a machine-readable medium 922 on which is stored one or more sets of data structures or instructions 924 (e.g., software) embodying or utilized by any one or more of the techniques or functionality described herein. The instructions 924 may also reside, completely or at least partially, within the main memory 904, within the static memory 906, or within the hardware processor 902 during execution thereof by the machine 900. In an example, one or any combination of the hardware processor 902, the main memory 904, the static memory 906, or the storage device 916 may constitute a machine-readable medium.

[0129] Specific examples of machine-readable media may include nonvolatile memory, such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0130] Although machine-readable medium 922 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database, and / or associated caches and servers) configured to store instructions 924 .

[0131] The device of the machine 900 may be one or more of the following: a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 904 and a static memory 906, a sensor 921, a network interface device 920, one or more antennas 960, a display device 910, an input device 912, a UI navigation device 914, a storage device 916, instructions 924, a signal generation device 918, and an output controller 928. The device may be configured to perform one or more methods and / or operations disclosed herein. The device may be a component of the machine 900 to perform one or more methods and / or operations disclosed herein, and / or a part of performing one or more methods and / or operations disclosed herein. In some embodiments, the device may include a pin or other device to receive power. In some embodiments, the device may include power regulation hardware.

[0132] The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 900 and causing the machine 900 to perform any one or more techniques of the present disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memory and optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the machine-readable medium may include non-transitory machine-readable media. In some examples, the machine-readable medium may include machine-readable media that are not transient propagation signals.

[0133] The instructions 924 may also be sent or received over a communication network 926 using a transmission medium via the network interface device 920 using any of a number of transmission protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile phone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, and a wireless data network (e.g., a wireless network known as a WLAN). The IEEE 802.11 series of standards is known as ), IEEE 802.16 series of standards), IEEE 802.15.4 series of standards, Long Term Evolution (LTE) series of standards, Universal Mobile Telecommunications System (UMTS) series of standards, peer-to-peer (P2P) networks, and so on.

[0134] In one example, the network interface device 920 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 926. In one example, the network interface device 920 may include one or more antennas 960 to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. In some examples, the network interface device 920 may communicate wirelessly using multi-user MIMO technology. The term "transmission medium" should be understood to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the machine 900, and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.

[0135] Examples as described herein may include logic or several components, modules, or mechanisms, or may operate on logic or several components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that can perform a specified operation and can be configured or arranged in a certain manner. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or with respect to an external entity, such as other circuits). In one example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured as a module by firmware or software (e.g., instructions, application parts, or applications), and the module operates to perform specified operations. In one example, software may reside on a machine-readable medium. In one example, software, when executed by the underlying hardware of a module, causes the hardware to perform specified operations.

[0136] Thus, the term "module" is understood to encompass a tangible entity, whether the entity is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., temporarily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operations described herein. Considering the example of temporarily configured modules, each module need not be instantiated at any one time. For example, where a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as various different modules at different times. The software may accordingly configure the hardware processor to, for example, constitute a particular module at one time and constitute a different module at a different time.

[0137] Some embodiments may be implemented in whole or in part in software and / or firmware. This software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. These instructions may then be read and executed by one or more processors to enable the operations described herein to be performed. The instructions may take any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in one or more computer-readable forms, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, and the like.

[0138] Fig.10 A block diagram of an example wireless device 1000 is illustrated on which any one or more of the techniques (e.g., methods or operations) discussed herein may be performed. The wireless device 1000 may be a UHR device or a UHR wireless device. The wireless device 1000 may be a UHR STA 504, an AP 502, and / or a UHR STA or a UHR AP. The UHR STA 504, the AP 502, and / or a UHR AP or a UHR STA may include some or all of the components shown in the figures herein. The wireless device 1000 may be a UHR device or a UHR wireless device. Fig. 9 An example of a machine 900 is disclosed.

[0139] The wireless device 1000 may include processing circuitry 1008. The processing circuitry 1008 may include a transceiver 1002, a physical layer circuitry (PHY circuitry) 1004, and a MAC layer circuitry (MAC circuitry) 1006, one or more of which may use one or more antennas 1012 to enable signal transmission and reception with other wireless devices (e.g., AP 502, UHR STA 504, and / or legacy device 506). As an example, the PHY circuitry 1004 may perform various encoding and decoding functions, which may include forming baseband signals for transmission and decoding received signals. As another example, the transceiver 1002 may perform various transmission and reception functions, such as signal conversion between a baseband range and a radio frequency (RF) range.

[0140] Thus, the PHY circuit 1004 and the transceiver 1002 may be separate components, or may be part of a combined component, such as the processing circuit 1008. In addition, some of the functions described in connection with the transmission and reception of signals may be performed by a combination, which may include one, any, or all of the PHY circuit 1004, the transceiver 1002, the MAC circuit 1006, the memory 1010, and other components or layers. The MAC circuit 1006 may control access to the wireless medium. The wireless device 1000 may also include a memory 1010 arranged to perform the operations described herein, for example, some of the operations described herein may be performed by instructions stored in the memory 1010.

[0141] One or more antennas 1012 (some embodiments may include only one antenna) may include one or more directional or omnidirectional antennas, such as dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, one or more antennas 1012 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0142] One or more of the memory 1010, the transceiver 1002, the PHY circuit 1004, the MAC circuit 1006, the one or more antennas 1012, and / or the processing circuit 1008 may be coupled to each other. In addition, although the memory 1010, the transceiver 1002, the PHY circuit 1004, the MAC circuit 1006, the one or more antennas 1012 are illustrated as separate components, one or more of the memory 1010, the transceiver 1002, the PHY circuit 1004, the MAC circuit 1006, the one or more antennas 1012 may be integrated into an electronic package or chip.

[0143] In some embodiments, the wireless device 1000 may be a combination of Fig. 9In some embodiments, the wireless device 1000 may be configured to operate under one or more wireless communication standards as described herein. In some embodiments, the wireless device 1000 may include a Fig. 9 One or more components described herein (e.g., display device 910, input device 912, etc.). Although wireless device 1000 is illustrated as having several separate functional elements, one or more of these functional elements may be combined and may be implemented by a combination of software-configured elements (e.g., processing elements including digital signal processors (DSPs)) and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs), and combinations of various hardware and logic circuits for performing at least the functions described herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements.

[0144] In some embodiments, an apparatus of or used by the wireless device 1000 may include various components of the wireless device 1000 as shown in the figures herein. Thus, in some embodiments, the techniques and operations described herein involving the wireless device 1000 may be applicable to an apparatus of the wireless device 1000 (e.g., the AP 502 and / or the UHR STA 504). In some embodiments, the wireless device 1000 is configured to decode and / or encode signals, packets, and / or frames as described herein, such as PPDUs.

[0145] In some embodiments, the MAC circuit 1006 may be arranged to contend for the wireless medium during the contention period to receive control of the medium in the UHR TXOP and encode or decode the UHR PPDU. In some embodiments, the MAC circuit 1006 may be arranged to contend for the wireless medium based on a channel contention setting, a transmit power level, and a clear channel assessment level (e.g., an energy detection level).

[0146] The PHY circuit 1004 may be arranged to send signals in accordance with one or more communication standards described herein. For example, the PHY circuit 1004 may be configured to send HE PPDUs. The PHY circuit 1004 may include circuits for modulation / demodulation, up-conversion / down-conversion, filtering, amplification, and the like. In some embodiments, the processing circuit 1008 may include one or more processors. The processing circuit 1008 may be configured to perform functions based on instructions stored in a RAM or ROM or based on a dedicated circuit. The processing circuit 1008 may include a processor, such as a general-purpose processor or a dedicated processor. The processing circuit 1008 may implement one or more functions associated with one or more antennas 1012, transceivers 1002, PHY circuits 1004, MAC circuits 1006, and / or memory 1010. In some embodiments, the processing circuit 1008 may be configured to perform one or more of the functions / operations and / or methods described herein.

[0147] In millimeter wave technology, stations (e.g. Figure 5 UHR station 504 or wireless device 1000) and an access point (e.g., Figure 5 Communications between two devices (AP 502 or wireless device 1000) can use an associated effective wireless channel that is highly dependent on directionality. In order to adapt to the directionality, beamforming technology can be used to radiate energy in a specific direction with a certain beam width to communicate between the two devices. Directional propagation focuses the transmitted energy to the target device to compensate for the significant energy loss in the channel between the two communicating devices. Compared with using the same transmission energy in omnidirectional propagation, the use of directional transmission can extend the range of millimeter wave communication.

[0148] Examples as described herein may include logic or several components, modules, or mechanisms, or may operate on logic or several components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) that can perform a specified operation and can be configured or arranged in a certain manner. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or with respect to an external entity, such as other circuits). In one example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured as a module by firmware or software (e.g., instructions, application parts, or applications), and the module operates to perform specified operations. In one example, software may reside on a machine-readable medium. In one example, software, when executed by the underlying hardware of a module, causes the hardware to perform specified operations.

[0149] Thus, the term "module" is understood to encompass a tangible entity, whether the entity is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., temporarily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operations described herein. Considering the example of temporarily configured modules, each module need not be instantiated at any one time. For example, where a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as various different modules at different times. The software may accordingly configure the hardware processor to, for example, constitute a particular module at one time and constitute a different module at a different time.

[0150] Some embodiments may be implemented in whole or in part in software and / or firmware. This software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. These instructions may then be read and executed by one or more processors to enable the operations described herein to be performed. The instructions may take any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in one or more computer-readable forms, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, and the like.

[0151] The above detailed description includes reference to the accompanying drawings, which form a part of the detailed description. The accompanying drawings illustrate specific embodiments that can be implemented. These embodiments are also referred to as "examples" in this article. Such examples may include additional elements other than those shown or described. However, examples including the elements shown or described are also contemplated. In addition, examples (or one or more aspects thereof) using any combination or arrangement of these elements shown or described are also contemplated, whether with respect to a specific example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.

[0152] Publications, patents, and patent documents cited in this document are hereby incorporated by reference in their entirety, as if each were incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) supplements that of this document; for irreconcilable inconsistencies, the usage in this document controls.

[0153] In this document, as is common in patent documents, the terms "one" or "an" are used to include one or more than one, independent of any other instance or use of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive or, so that "A or B" includes "A but not B", "B but not A", and "A and B", unless otherwise indicated. In the appended claims, the terms "including" and "wherein" are used as the plain English equivalents of the corresponding terms "comprising" and "wherein". In addition, in the appended claims, the terms "including" and "comprising" are open-ended, that is, systems, devices, articles, or processes that include other elements in addition to those listed after such terms in the claims are still considered to fall within the scope of the claim. In addition, in the appended claims, the terms "first", "second", and "third", etc. are used only as labels and are not intended to imply a numerical order to their objects.

[0154] The embodiments described above may be implemented in various hardware configurations, which may include a processor for executing instructions that perform the described techniques. Such instructions may be included in a machine-readable medium, such as a suitable storage medium or memory or other processor-executable medium.

[0155] The embodiments as described herein may be implemented in a number of environments, such as a wireless local area network (WLAN), a 3rd Generation Partnership Project (3GPP) Universal Terrestrial Radio Access Network (UTRAN), or a Long-Term-Evolution (LTE) or part of a Long Term Evolution (LTE) communication system, although the scope of the present disclosure is not limited in this respect.

[0156] The antennas mentioned herein may include one or more directional or omnidirectional antennas, such as dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for the transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered as a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, antennas may be effectively separated to utilize spatial diversity and different channel characteristics may be generated between each antenna and the antenna of the transmitting station. In some MIMO embodiments, antennas may be separated by up to 1 / 10 of a wavelength or more.

[0157] Implementations of the described subject matter may include one or more of the features, alone or in combination, as described below by way of example.

[0158] Example

[0159] Example 1 is a device of an access point (AP), comprising: a memory; and a processing circuit coupled to the memory, the processing circuit configuring the AP to: determine at least one of a first coding type for a payload of an ultra-high reliability (UHR) downlink physical (PHY) layer downlink protocol data unit (PPDU) or a second coding type for an uplink PPDU from a station (STA); indicate at least one of the following: indicate the first coding type in a coding type subfield in a user field in a preamble of the downlink PPDU or indicate the second coding type in a user information field of a trigger frame in the uplink PPDU, the coding types that can be indicated include boosted low-density parity-check (LDPC) codes, the number of bits in the user field used to indicate the coding type depends on whether multiple types of boosted LDPC codes are available for coding or at least one of the payload size; and send the downlink PPDU to the STA.

[0160] In Example 2, the subject matter of Example 1 includes, wherein the processing circuit configures the AP to use a plurality of bits to indicate at least one of the first encoding type or the second encoding type.

[0161] In Example 3, the subject matter as described in Examples 1-2 includes, wherein the processing circuit configures the AP to use multiple bits to indicate at least one of the first encoding type or the second encoding type in response to determining that lifted LDPC codes with different bit lengths are available for encoding.

[0162] In Example 4, the subject matter of Examples 1-3 includes, wherein the processing circuit configures the AP to indicate at least one of the first encoding type or the second encoding type using a plurality of bits in response to determining that a single boosted LDPC code type is available for encoding.

[0163] In Example 5, the subject matter of Example 4 includes, wherein at least one value of the bit is reserved for later use.

[0164] In Example 6, the subject matter as described in Examples 1-5 includes, wherein the processing circuit configures the AP to use a single bit to indicate at least one of the first coding type or the second coding type in response to determining that a traditional LDPC code and at least one type of boosted LDPC code are available for encoding and the at least one type of boosted LDPC code is not an optional coding type, and the selection of a specific coding type using one of the boosted LDPC codes is determined by the size of a physical layer convergence procedure (PLCP) protocol data unit (PPDU) payload or a medium access control layer (MAC) payload of a response to the frame.

[0165] In Example 7, the subject matter as described in Example 6 includes, wherein the selection of the particular encoding type includes using a conventional LDPC code for a PPDU payload or a MAC payload less than a first threshold, using a first boosted LDPC code having a first bit length for a PPDU payload or a MAC payload that is at least the first threshold and less than a second threshold, and using a second boosted LDPC code having a second bit length for a PPDU payload or a MAC payload that is at least the second threshold, the second bit length being longer than the first bit length.

[0166] In Example 8, the subject matter as described in Examples 1-7 includes, wherein the processing circuit configures the AP to use multiple bits to indicate at least one of the first coding type or the second coding type in response to determining that at least one LDPC code is not an optional coding type and at least one boosted LDPC code is available for encoding and is an optional coding type.

[0167] In Example 9, the subject matter of Examples 1-8 includes, wherein the at least one LDPC code includes a conventional LDPC and a boosted LDPC code.

[0168] In Example 10, the subject matter as described in Example 9 includes, wherein the selection between the conventional LDPC and boosted LDPC codes is determined by the size of a physical layer convergence procedure (PLCP) protocol data unit (PPDU) payload or a medium access control layer (MAC) payload of a response to the frame, such that the conventional LDPC is used for a PPDU payload or MAC payload less than a threshold and the boosted LDPC code is used for a PPDU payload or MAC payload of at least the threshold.

[0169] In Example 11, the subject matter of Examples 1-10 includes, wherein the user field is in an ultra high reliability signal (UHR-SIG) field.

[0170] In Example 12, the subject matter of Examples 1-11 includes, wherein the processing circuit configures the AP to send a multi-user PPDU to a plurality of STAs, the multi-user PPDU including a different coding type subfield in a user field for each STA.

[0171] In Example 13, the subject matter of Examples 1-12 includes indicating binary convolutional coding (BBC) and setting to a non-zero value to indicate the boosted LDPC code.

[0172] Example 14 is a device of a station (STA), comprising: a memory; and a processing circuit coupled to the memory, the processing circuit configuring the STA to send one of the following to an access point (AP): a non-trigger-based frame, the frame being included in an ultra-high reliability (UHR) payload of a physical (PHY) layer protocol data unit (PPDU) having a first payload encoded using a first coding type selected from a set of coding types, the set of coding types including binary convolutional coding (BCC), traditional low-density parity check (LDPC) coding, and boosted LDPC coding, for indicating that the number of bits of the first coding type depends on whether multiple types of boosted LDPC codes are available for encoding or at least one of the payload size of the first payload, or a trigger-based frame, the frame being included in a UHR payload of a PPDU having a second payload, the second payload being encoded using a second coding type selected from the set of coding types as indicated by a user information field of a trigger frame from the AP, for indicating that the number of bits of the second coding type depends on whether multiple types of boosted LDPC codes are available for encoding or at least one of the payload size of the second payload.

[0173] In Example 15, the subject matter as described in Example 14 includes, wherein, based on the availability of multiple boosted LDPC codes with different bit lengths or a single boosted LDPC code for encoding, multiple bits are used to indicate at least one of the first encoding type or the second encoding type.

[0174] In Example 16, the subject matter as described in Examples 14-15 includes, wherein, based on conventional LDPC codes and at least one type of boosted LDPC codes being available for encoding and the at least one type of boosted LDPC code being not an optional coding type, a single bit is used to indicate at least one of the first coding type or the second coding type, and selection of a specific coding type using one of the boosted LDPC codes is determined by the size of a PPDU payload or a medium access control layer (MAC) payload of a response to the frame.

[0175] In Example 17, the subject matter as described in Example 16 includes, wherein the selection of the particular encoding type includes using the conventional LDPC code for a PPDU payload or MAC payload less than a first threshold, using a first boosted LDPC code having a first bit length for a PPDU payload or MAC payload that is at least the first threshold and less than a second threshold, and using a second boosted LDPC code having a second bit length for a PPDU payload or MAC payload that is at least the second threshold, the second bit length being longer than the first bit length.

[0176] In Example 18, the subject matter as described in Examples 14-17 includes, wherein, in response to at least one LDPC code being not an optional coding type and at least one boosted LDPC code being available for encoding and being an optional coding type, multiple bits are used to indicate at least one of the first coding type or the second coding type, the at least one LDPC code comprising a conventional LDPC and the boosted LDPC code.

[0177] Example 19 is a non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a device of an access point (AP), the instructions causing the one or more processors to: determine at least one of a first coding type for a payload of an ultra-high reliability (UHR) downlink physical (PHY) layer downlink protocol data unit (PPDU) or a second coding type for an uplink PPDU from a station (STA); indicate at least one of the following: indicate the first coding type in a coding type subfield in a user field in a preamble of the downlink PPDU or indicate the second coding type in a user information field of a trigger frame in the uplink PPDU, the coding types that can be indicated include boosted low-density parity-check (LDPC) codes, the number of bits in the user field used to indicate the coding type depends on whether multiple types of boosted LDPC codes are available for coding or at least one of the payload size; and send the downlink PPDU to the STA.

[0178] In Example 20, the subject matter of Example 19 includes, wherein the instructions further cause the one or more processors to indicate at least one of the first encoding type or the second encoding type using a plurality of bits.

[0179] Example 21 is at least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of Examples 1-20.

[0180] Example 22 is an apparatus comprising means for implementing any of Examples 1-20.

[0181] Example 23 is a system for implementing any one of Examples 1-20.

[0182] Example 24 is a method for implementing any one of Examples 1-20.

[0183] In some examples, frames may be transmitted using bandwidths up to 320 MHz or 480 MHz and 4096 quadrature amplitude modulation (QAM).

[0184] Although the embodiments have been described with reference to specific example embodiments, it will be appreciated that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Therefore, the description and the drawings should be considered illustrative, rather than restrictive. The drawings forming part of this article illustrate, by way of illustration and not limitation, specific embodiments in which the subject matter may be implemented. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to implement the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. This "specific implementation" section should therefore not be understood in a limiting sense, and the scope of the various embodiments is limited only by the appended claims and the full equivalent scope to which such claims are authorized.

[0185] Subject matter may be referred to herein individually and / or collectively by the term "embodiment", which is merely for convenience and is not intended to actively limit the scope of the present application to any single inventive concept, if more than one is actually disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be understood that any arrangement intended to achieve the same purpose may replace the specific embodiments shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art after reading the above description.

[0186] In this document, as is common in patent documents, the term "one" is used to indicate one or more than one, independent of any other instance or use of "at least one" or "one or more". In this document, the term "or" is used to refer to non-exclusive or, so that "A or B" includes "A, but not B", "B, but not A" and "A and B", unless otherwise indicated. In this document, the terms "including" and "wherein" are used as the plain English equivalents of the corresponding terms "including" and "wherein". In addition, in the appended claims, the terms "including" and "comprising" are open, that is, systems, UEs, articles, compositions, formulas or processes that include other elements in addition to those listed after such terms in the claims are still considered to fall within the scope of the claim. In addition, in the appended claims, the terms "first", "second" and "third" and the like are used only as labels, and are not intended to impose numerical requirements on their objects. As shown herein, although the term "one" is used herein, one or more associated elements may be used in different embodiments. For example, the term "processor" configured to perform a specific operation includes both a single processor configured to perform all operations and multiple processors that are individually configured to perform some or all operations (possibly overlapping), so that the combination of processors performs all operations. In addition, it can be considered that the term "comprising" is interpreted as "including at least" the following elements.

[0187] The Abstract of the present disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description section, it can be seen that in order to streamline the present disclosure, various features are grouped together in a single embodiment. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as reflected in the appended claims, the subject matter of the invention resides in less than all of the features of a single disclosed embodiment. Thus, the appended claims are hereby incorporated into the "Detailed Description" section, with each claim standing alone as a separate embodiment.

Claims

1. An access point (AP) device, the device comprising: Memory; as well as a processing circuit coupled to the memory, the processing circuit being configured to: determining at least one of a first coding type for a payload of an ultra high reliability (UHR) downlink physical (PHY) layer downlink protocol data unit (PPDU) or a second coding type for an uplink PPDU from a station (STA); Indicating at least one of the following: indicating the first coding type in the coding type subfield in the user field of the preamble of the downlink PPDU or indicating the second coding type in the user information field of the trigger frame in the uplink PPDU, the coding type that can be indicated includes an enhanced low-density parity check (LDPC) code, and the number of bits in the user field used to indicate the coding type depends on at least one of the following: whether multiple types of enhanced LDPC codes are available for encoding, or the payload size; and The downlink PPDU is encoded for transmission to the STA.

2. The device according to claim 1, wherein: The processing circuit is configured to use a plurality of bits to indicate at least one of the first encoding type or the second encoding type.

3. The device according to claim 1 or 2, wherein: The processing circuit is configured to, in response to determining that a lifting LDPC code having a different bit length is available for encoding, indicate at least one of the first encoding type or the second encoding type using a plurality of bits.

4. The device according to claim 1 or 2, wherein: The processing circuit is configured to, in response to determining that a single boosted LDPC code type is available for encoding, indicate at least one of the first encoding type or the second encoding type using a plurality of bits.

5. The device according to claim 4, wherein: At least one value of the bit is reserved for later use.

6. The device according to claim 1 or 2, wherein: The processing circuit is configured to: in response to determining that a traditional LDPC code and at least one type of enhanced LDPC code are available for encoding and the at least one type of enhanced LDPC code is not an optional coding type, use a single bit to indicate at least one of the first coding type or the second coding type, and the selection of a specific coding type using one of the enhanced LDPC codes is determined by the size of a physical layer convergence procedure (PLCP) protocol data unit (PPDU) payload or a medium access control layer (MAC) payload in response to the trigger frame.

7. The device according to claim 6, wherein: The selection of the specific encoding type includes using a conventional LDPC code for a PPDU payload or MAC payload less than a first threshold, using a first boosted LDPC code having a first bit length for a PPDU payload or MAC payload that is at least the first threshold and less than a second threshold, and using a second boosted LDPC code having a second bit length for a PPDU payload or MAC payload that is at least the second threshold, the second bit length being longer than the first bit length.

8. The device according to claim 1 or 2, wherein: The processing circuit is configured to, in response to determining that at least one LDPC code is not a selectable coding type and at least one boosted LDPC code is available for encoding and is a selectable coding type, indicate at least one of the first coding type or the second coding type using a plurality of bits.

9. The device according to claim 1 or 2, wherein: The at least one LDPC code includes a conventional LDPC code and the boosted LDPC code.

10. The device of claim 9, wherein: The selection between the conventional LDPC and the enhanced LDPC codes is determined by the size of a physical layer convergence procedure (PLCP) protocol data unit (PPDU) payload or a medium access control layer (MAC) payload in response to the trigger frame, such that the conventional LDPC is used for a PPDU payload or a MAC payload that is less than a threshold and the enhanced LDPC code is used for a PPDU payload or a MAC payload that is at least the threshold.

11. The device according to claim 1 or 2, wherein: The user field is in an ultra high reliability signal (UHR-SIG) field.

12. The device according to claim 1 or 2, wherein: The processing circuit is configured to send a multi-user PPDU to a plurality of STAs, the multi-user PPDU including a different coding type subfield in a user field for each STA.

13. The device according to claim 1 or 2, wherein: The processing circuit is configured to set the value in the user information field to zero to indicate binary convolutional coding (BBC) and to a non-zero value to indicate the boosted LDPC code.

14. A station (STA) device, the device comprising: Memory; as well as A processing circuit coupled to the memory, the processing circuit configured to encode for transmission to an access point (AP) one of: A non-trigger-based frame, the frame being contained in an ultra-high reliability (UHR) payload of a physical (PHY) layer protocol data unit (PPDU) having a first payload encoded using a first coding type selected from a set of coding types, the set of coding types including binary convolutional coding (BBC), conventional low-density parity-check (LDPC) coding, and boosted LDPC coding, the number of bits used to indicate the first coding type depending on at least one of: whether multiple types of boosted LDPC codes are available for encoding, or a payload size of the first payload, or A triggered frame is included in a UHR payload of a PPDU having a second payload, wherein the second payload is encoded using a second coding type selected from the set of coding types indicated by a user information field of the trigger frame from the AP, and the number of bits used to indicate the second coding type depends on at least one of: whether multiple types of boosted LDPC codes are available for encoding, or the payload size of the second payload.

15. The device of claim 14, wherein: Based on the availability of multiple boosted LDPC codes with different bit lengths or a single boosted LDPC code for encoding, multiple bits are used to indicate at least one of the first encoding type or the second encoding type.

16. The device according to claim 14 or 15, wherein: Based on that traditional LDPC codes and at least one type of boosted LDPC codes can be used for encoding and the at least one type of boosted LDPC code is not an optional coding type, a single bit is used to indicate at least one of the first coding type or the second coding type, and the selection of a specific coding type using one of the boosted LDPC codes is determined by the size of the PPDU payload or the medium access control layer (MAC) payload of the response to the trigger frame.

17. The device of claim 16, wherein: The selection of the specific encoding type includes using the traditional LDPC code for a PPDU payload or MAC payload less than a first threshold, using a first boosted LDPC code with a first bit length for a PPDU payload or MAC payload that is at least the first threshold and less than a second threshold, and using a second boosted LDPC code with a second bit length for a PPDU payload or MAC payload that is at least the second threshold, the second bit length being longer than the first bit length.

18. The device according to claim 14 or 15, wherein: In response to at least one LDPC code being not an optional coding type and at least one boosted LDPC code being available for encoding and being an optional coding type, a plurality of bits are used to indicate at least one of the first coding type or the second coding type, the at least one LDPC code comprising a conventional LDPC and the boosted LDPC code.

19. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of an access point (AP) device, the instructions causing the one or more processors to: determining at least one of a first coding type for a payload of an ultra high reliability (UHR) downlink physical (PHY) layer downlink protocol data unit (PPDU) or a second coding type for an uplink PPDU from a station (STA); Indicating at least one of the following: indicating the first coding type in the coding type subfield in the user field of the preamble of the downlink PPDU or indicating the second coding type in the user information field of the trigger frame in the uplink PPDU, the coding type that can be indicated includes an enhanced low-density parity check (LDPC) code, and the number of bits in the user field used to indicate the coding type depends on at least one of the following: whether multiple types of enhanced LDPC codes are available for encoding, or the payload size; and The downlink PPDU is encoded for transmission to the STA.

20. The medium of claim 19, wherein: The instructions also cause the one or more processors to indicate at least one of the first encoding type or the second encoding type using a plurality of bits.

Images