Techniques for 480 and 640 mehz (MHZ) transmission in wi-fi

Abstract

The present disclosure provides methods, components, devices, and systems for 480 and 640 megahertz (MHz) transmission in Wi-Fi. Some aspects are more particularly directed to including a bandwidth field and a bandwidth extension field in a preamble of a physical layer protocol data unit (PPDU), the bandwidth field and the bandwidth extension field jointly indicating that a channel bandwidth of the PPDU is a continuous 480 MHz channel bandwidth or a 640 MHz channel bandwidth. In some aspects, parameters of the PPDU may be defined based on the PPDU occupying a 480 MHz or 640 MHz bandwidth. The parameters may include, for example, a tone plan, an allowed puncturing pattern, signaling of a puncturing plan, signaling of a resource element allocation, a short training field, a long training field, a pilot signal sequence, a phase shift, a segment parser, and / or spectrum masking.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This Patent Application claims priority to U.S. Patent Application No. 18 / 740,815 by CHEN et al., entitled “TECHNIQUES FOR 480 AND 640 MEGAHERTZ (MHZ) TRANSMISSION IN WI-FI,” filed June 12, 2024, which claims the benefit of U.S. Provisional Patent Application No. 63 / 514,256 by CHEN et al., entitled “TECHNIQUES FOR 480 AND 640 MEGAHERTZ (MHZ) TRANSMISSION IN WI-FI,” filed July 18, 2023, and U.S. Provisional Patent Application No. 63 / 510,275 by CHEN et al., entitled “TECHNIQUES FOR 480 AND 640 MEGAHERTZ (MHZ) TRANSMISSION IN WI-FI,” filed June 26, 2023, each of which is assigned to the assignee hereof, and each of which is expressly incorporated by reference herein. TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and more specifically to techniques for 480 and 640 megahertz (MHz) transmission in Wi-Fi. BACKGROUND

[0004] A wireless local area network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices, also referred to as wireless stations (STAs). The basic building block of a WLAN that adheres to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STAs within wireless range of the AP to establish or maintain a communication link with the WLAN.

[0005] In some WLANs, wireless communication devices, such as STAs and APs, transmit and receive wireless communications to and from each other in the form of physical layer (PHY) protocol data units (PPDUs). PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax, and 802.11be standard amendments can be transmitted over a 2.4, 5, or 6 gigahertz (GHz) band. Each band can include multiple channels. 20 megahertz (MHz), 40 MHz, 80 MHz, 160 MHz, or 320 MHz channels can be used, and the channels can be defined by a center frequency index and an operating bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz). A PPDU can include a preamble that provides control information of the PPDU and a payload that carries data. A bandwidth field in a universal signal field (U-SIG) in the preamble can indicate whether the operating bandwidth is 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 320 MHz. SUMMARY

[0006] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device can include one or more memories that store processor-executable code and one or more processors that are coupled with the one or more memories and are configured, individually or collectively, to cause the wireless communication device to, in connection with executing the code: transmit a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmit a payload of the PPDU using the indicated channel bandwidth.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a wireless communication device. The method can include transmitting a preamble of a physical layer protocol data unit (PPDU), where the preamble includes a universal signal (U-SIG) field, where the U-SIG field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 megahertz (MHz) contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmitting a payload of the PPDU using the indicated channel bandwidth.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device can include means for transmitting a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and means for transmitting a payload of the PPDU using the indicated channel bandwidth.

[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code can include instructions executable by a processor to transmit a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmit a payload of the PPDU using the indicated channel bandwidth.

[0011] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicates the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0012] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz, a 320 MHz bandwidth extended to 7225 MHz, a 480 MHz bandwidth extended to 7225 MHz, and a 640 MHz bandwidth extended to 7225 MHz.

[0013] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, and the first value can be different from the third value and the second value can be different from the fourth value.

[0014] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, transmitting the preamble and the payload can include operations, features, means, or instructions for transmitting the preamble and the payload according to a tone plan, the tone plan including one or more of: a set of multiple Extremely High Throughput (EHT) 80 MHz tone plans across a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; a 6 x 996 tone Resource Unit (RU) for the 480 MHz contiguous channel bandwidth; a 4 x 996 tone Multi-RU (MRU) for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; an 8 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 6 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a a6 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 7 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth.

[0015] Some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting a set of multiple pilot signals, where resources used to transmit the set of multiple pilot signals can be based on the tone plan.

[0016] Some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for generating the PPDU according to a segment parser, where the segment parser can be based on the tone plan.

[0017] Some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for transmitting, in the preamble, an indication of a puncturing pattern of the PPDU.

[0018] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the PPDU includes an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0019] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the PPDU includes an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths per 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0020] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the U-SIG field of the triggered PPDU includes a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0021] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes an EHT signal field including a RU allocation subfield, and a number of entries in the RU allocation subfield is based on the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0022] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes a UHR short training field (STF) including a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, and each sequence of the set of multiple sequences can be multiplied by a different coefficient.

[0023] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes a UHR long training field (LTF) including a set of multiple sequences within a 480 MHz contiguous channel bandwidth or a 80 MHz segment of a 640 MHz contiguous channel bandwidth, each sequence of the set of multiple sequences including multiple portions, and each portion of the multiple portions can be multiplied by a different coefficient.

[0024] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, transmitting the legacy portion of the preamble can include operations, features, means, or instructions for applying an 80 MHz subblock-based phase rotation pattern within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0025] Some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for generating the PPDU via encoding a lower frequency tone 3 x 996 RU of a 480 MHz contiguous channel bandwidth or a lower frequency tone 4 x 996 RU of a 640 MHz contiguous channel bandwidth using binary phase shift keying dual-subcarrier modulation; copying the lower frequency tone 3 x 996 RU of the 480 MHz contiguous channel bandwidth or the lower frequency tone 4 x 996 RU of the 640 MHz contiguous channel bandwidth onto a higher frequency tone 3 x 996 RU of the 480 MHz contiguous channel bandwidth or a higher frequency tone 4 x 996 RU of the 640 MHz contiguous channel bandwidth; and applying a phase shift to the higher frequency tone 3 x 966 RU of the 480 MHz contiguous channel bandwidth or the higher frequency tone 4 x 996 RU of the 640 MHz contiguous channel bandwidth.

[0026] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, transmitting the preamble and the payload can include operations, features, means, or instructions for applying a spectral mask to the transmission of the preamble and the payload, where the spectral mask can have one of: for a 480 MHz PPDU, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplication PPDU, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz PPDU, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplication PPDU, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and where the transmitted spectrum can not exceed the maximum of the spectral mask and -39 dBm / MHz at any frequency offset.

[0027] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; within a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 320 MHz channelization and the bandwidth extension field indicates an additional higher 160 MHz sub-band; within a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates one of the first 320 MHz channelization and the additional higher 160 MHz sub-band or a second 320 MHz channelization and an additional lower 160 MHz sub-band; and within a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 320 MHz channelization and the bandwidth extension field indicates an additional lower 160 MHz sub-band.

[0028] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, within the lowest 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with the lowest 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with the middle 160 MHz sub-band, and a third spatial reuse field is associated with the additional higher 160 MHz sub-band; and within the highest 160 MHz sub-band, the first spatial reuse field is associated with the middle 160 MHz sub-band, the second spatial reuse field is associated with the highest 160 MHz sub-band, and the third spatial reuse field is associated with the lowest 160 MHz sub-band.

[0029] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; within a first 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 160 MHz channelization and the bandwidth extension field indicates that the first 160 MHz sub-band is a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; within a second 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 160 MHz channelization and the bandwidth extension field indicates that the second 160 MHz sub-band is a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; and within a third 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a third 160 MHz channelization and the bandwidth extension field indicates that the third 160 MHz sub-band is a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0030] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, within the first 160 MHz sub-band, a first spatial reuse field of the common signal field is associated with a lowest 80 MHz of the first 160 MHz sub-band, a second spatial reuse field of the common signal field is associated with a highest 80 MHz of the first 160 MHz sub-band, a third spatial reuse field of the common signal field is associated with the second 160 MHz sub-band, and a fourth spatial reuse field of the common signal field is associated with the third 160 MHz sub-band; within the second 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the second 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the second 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the third 160 MHz sub-band; and within the third 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the third 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the third 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the second 160 MHz sub-band.

[0031] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; the 480 MHz contiguous channel bandwidth includes a 160 MHz primary channel portion and a remaining 320 MHz portion; and the preamble includes a very high reliability signal field including a RU allocation subfield, where the RU allocation subfield includes a respective 9-bit RU allocation table for each 20 MHz portion of the 160 MHz primary channel portion, and where the RU allocation subfield includes a respective 8-bit RU allocation table for each 80 MHz portion of the remaining 320 MHz portion.

[0032] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; and the preamble includes a very high reliability signal field including a first common field and a first user-specific field associated with a 320 MHz sub-band of the 480 MHz contiguous channel bandwidth and a second common field and a second user-specific field associated with a 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0033] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth, where the 480 MHz contiguous channel bandwidth includes a primary 160 MHz subchannel, a first secondary 160 MHz subchannel, and one of a second secondary 160 MHz subchannel or a third 160 MHz subband.

[0034] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the primary 160 MHz subchannel includes a middle 160 MHz subchannel of the 480 MHz channel bandwidth, and the method, wireless communication device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for communicating with a second wireless communication device via a first 320 MHz subchannel of the 480 MHz channel bandwidth, where the first 320 MHz subchannel includes the primary 160 MHz subchannel and a lower 160 MHz subchannel of the 480 MHz channel bandwidth, and communicating with a third wireless communication device via a second 320 MHz subchannel of the 480 MHz channel bandwidth, where the second 320 MHz subchannel includes the primary 160 MHz subchannel and an upper 160 MHz subchannel of the 480 MHz channel bandwidth, and where the second wireless communication device and the third wireless communication device are 320 MHz limited devices.

[0035] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the wireless communication device is an AP, and the method, wireless communication device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting, to a second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device, and transmitting, to a third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device, where the first 320 MHz operating channel is the first 320 MHz subchannel and the second 320 MHz operating channel is the second 320 MHz subchannel, or receiving, from a second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device, and receiving, from a third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device.

[0036] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories and configured to, individually or collectively, cause the wireless communication device to receive a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within a 640 MHz contiguous channel bandwidth, and receive a payload of the PPDU using the indicated channel bandwidth.

[0037] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a wireless communication device. The method can include receiving a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within a 640 MHz contiguous channel bandwidth, and receiving a payload of the PPDU using the indicated channel bandwidth.

[0038] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device can include means for receiving a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within a 640 MHz contiguous channel bandwidth, and means for receiving a payload of the PPDU using the indicated channel bandwidth.

[0039] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code can include instructions executable by a processor to receive a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within a 640 MHz contiguous channel bandwidth, and receive a payload of the PPDU using the indicated channel bandwidth.

[0040] In some examples of the method, the wireless communication device, and the non-transitory computer-readable medium described herein, a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicates 480 MHz contiguous channel bandwidth or 640 MHz contiguous channel bandwidth.

[0041] In some examples of the method, the wireless communication device, and the non-transitory computer-readable medium described herein, the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz, a 320 MHz bandwidth extended to 7225 MHz, a 480 MHz bandwidth extended to 7225 MHz, and a 640 MHz bandwidth extended to 7225 MHz.

[0042] In some examples of the method, the wireless communication device, and the non-transitory computer-readable medium described herein, within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, and the first value can be different from the third value and the second value can be different from the fourth value.

[0043] In some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein, receiving the preamble can include operations, features, means, or instructions for receiving the preamble and the payload according to a tone plan, the tone plan including one or more of: a set of multiple EHT 80 MHz tone plans across a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; a 6 x 996 tone RU for the 480 MHz contiguous channel bandwidth; a 4 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; an 8 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 6 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a a6 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 7 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth.

[0044] Some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving a set of multiple pilot signals, where resources used to transmit the set of multiple pilot signals can be based on the tone plan.

[0045] Some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for de-parsing the PPDU according to a segment de-parser, where the segment de-parser can be based on the tone plan.

[0046] Some examples of the method, wireless communication device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving, in the preamble, an indication of a puncturing pattern for the PPDU.

[0047] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the PPDU includes an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0048] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the PPDU includes an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths per 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0049] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the U-SIG field of the TB PPDU includes a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0050] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes an EHT signal field including a RU allocation subfield, and a number of entries in the RU allocation subfield is based on the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0051] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes a UHR STF including a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, and each sequence of the set of multiple sequences can be multiplied by a different coefficient.

[0052] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the preamble includes a UHR LTF that includes a set of multiple sequences within an 80 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, each sequence of the set of multiple sequences including multiple portions, and each portion of the multiple portions can be multiplied by a different coefficient.

[0053] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, an 80 MHz subblock-based phase rotation pattern within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth can be applied to a legacy portion of the preamble.

[0054] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, a 480 MHz contiguous channel bandwidth lower frequency tone 3 x 996 RU or a 640 MHz contiguous channel bandwidth lower frequency tone 4 x 996 RU of the PPDU can be encoded using binary phase shift keying dual subcarrier modulation, and the 480 MHz contiguous channel bandwidth lower frequency tone 3 x 996 RU or the 640 MHz contiguous channel bandwidth lower frequency tone 4 x 996 RU can be copied and phase shifted onto a 480 MHz contiguous channel bandwidth higher frequency tone 3 x 996 RU or a 640 MHz contiguous channel bandwidth higher frequency tone 4 x 996 RU of the PPDU.

[0055] In some examples of the method, wireless communication device, and non-transitory computer- readable medium described herein, the spectral mask can be applied to the preamble and the payload, and the spectral mask can have one of: for a 480 MHz PPDU, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz PPDU, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and where the transmitted spectrum can not exceed the maximum of the spectral mask and -39 dBm / MHz at any frequency offset.

[0056] Details of one or more aspects of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following drawings can not be drawn to scale. BRIEF DESCRIPTION OF DRAWINGS

[0057] FIG. 1 A diagram illustrating an example wireless communication network is shown.

[0058] FIG. 2 An example protocol data unit (PDU) capable of being used for communication between a wireless access point (AP) and one or more wireless stations is shown.

[0059] FIG. 3a An example extremely high throughput (EHT) physical layer (PHY) PDU (PPDU) capable of being used for communication between a wireless AP and one or more wireless stations (STAs) is shown.

[0060] FIG. 3b An example ultra-high reliability (UHR) multi-user PPDU capable of being used for communication between a wireless AP or non-AP STA and one or more wireless STAs is shown.

[0061] FIG. 3c An example UHR trigger-based (TB) PPDU capable of being used for communication between a wireless AP and one or more wireless STAs is shown.

[0062] FIG. 4 A layered format of an example PPDU capable of being used for communication between a wireless AP and one or more wireless STAs is shown.

[0063] FIG. 5 An example channelization diagram supporting techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0064] FIG. 6 An example signaling diagram supporting techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0065] FIG. 7 An example channelization diagram supporting techniques for 480 MHz transmissions in Wi-Fi is shown.

[0066] FIG. 8 An example resource unit allocation diagram supporting techniques for 480 MHz transmissions in Wi-Fi is shown.

[0067] FIG. 9 An example process flow supporting techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0068] FIG. 10 An example of transmit spectrum mask that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0069] FIG. 11 and FIG. 12 A block diagram of a device that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0070] FIG. 13 A block diagram of an example wireless communication device that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0071] FIG. 14 and FIG. 15 A flow diagram illustrating an example process that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown.

[0072] The same reference numbers and designations in the various drawings indicate the same elements. DETAILED DESCRIPTION

[0073] The following description relates to certain specific examples and is not intended to be limiting of the disclosure. One of ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some or all of the examples described can be implemented in an access point (AP) that is capable of transmitting and receiving data according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, the IEEE 802.15 standards, the Bluetooth® standards defined by the Bluetooth Special Interest Group (SIG), or other wireless communications standards. ®The described examples can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiplexing (OFDM), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), space division multiple access (SDMA), rate- spreading multiple access (RSMA), multi-user shared access (MUSA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU)-MIMO (MU-MIMO). The described examples can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), a wireless metropolitan area network (WMAN), or an internet of things (IOT) network.

[0074] Various aspects generally relate to supporting 480 and 640 megahertz (MHz) physical layer (PHY) protocol data units (PPDUs) in wireless communications. Some aspects more specifically relate to introducing a bandwidth extension field in a universal signal field (U-SIG) of a preamble of a PPDU that, in conjunction with a bandwidth field in the U-SIG, indicates that a channel bandwidth of the PPDU is a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. In many systems, the bandwidth field in the U-SIG is insufficient to indicate a particular 480 MHz channel bandwidth or 640 MHz channel bandwidth in addition to the possible 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz channel bandwidths while leaving at least one reserved value. Thus, introducing the bandwidth extension field enables a transmitting wireless communication device to indicate that the PPDU is a 480 MHz channel bandwidth or 640 MHz channel bandwidth PPDU. For example, the bandwidth extension field can indicate, in conjunction with the bandwidth field, whether the operating bandwidth is 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320MHz-l, 320MHz-2, 480MHz-l, 480MHz-2, 480MHz-3, 640MHz-l, 640MHz-2, 640MHz-3, or 640MHz-4, where MHz-l, MHz-2, etc. refer to different channelizations. Channelization refers to a set (e.g., one or more) of possible channels (center frequency and channel bandwidth). In some examples, indicating a channel bandwidth can include indicating a channelization for the particular channel bandwidth. For example, a 320 MHz channel can include any two adjacent 160 MHz channels in a 6 GHz band, where two types of channelizations for 320 MHz can be defined: 320MHz-l and 320MHz-2. In such examples, 320MHz-l can be defined as a 320 MHz channel with channel center frequencies numbered 31, 95, and 159, and 320MHz-2 can be defined as a 320 MHz channel with channel center frequencies numbered 63, 127, and 191. In some aspects, a 480 MHz contiguous channel bandwidth can be indicated as a 320 MHz channel bandwidth with an additional 160 MHz channel bandwidth. A receiving wireless communication device can identify an operating channel of the PPDU based on the identified channel bandwidth and a frequency at which the preamble is received by the receiving device.

[0075] In some aspects, parameters of a 480 MHz or 640 MHz PPDU can be defined to account for the larger channel bandwidth of a 480 MHz or 640 MHz PPDU as compared to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz PPDUs. For example, parameters such as tone plan, resource unit (RU) allocation indication, spatial reuse field, short training field, long training field, pilot signal location, phase shift, and spectral mask can be adjusted based on using a 480 MHz or 640 MHz channel bandwidth for a PPDU. In some aspects, some resources within a contiguous 480 MHz channel bandwidth or 640 MHz channel bandwidth can be punctured (e.g., not used). For example, a 640 MHz contiguous channel bandwidth can be punctured to support 480 MHz PPDU transmissions (by puncturing resources of the 160 MHz). Allowed puncturing patterns can be defined for 480 MHz and 640 MHz PPDUs, and a transmitting wireless communication device can signal the puncturing pattern for a 480 MHz or 640 MHz PPDU in a preamble of the PPDU.

[0076] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some aspects, by increasing the channel bandwidth of a PPDU to 480 MHz or 640 MHz, more data can be sent in the PPDU because more RUs are available based on the larger bandwidth compared to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz PPDUs, and correspondingly, higher peak throughput can be achieved. The described techniques can be used to indicate whether a PPDU is a 480 MHz or 640 MHz PPDU. By using a bandwidth extension field in addition to the bandwidth field in the U-SIG that jointly indicates, in combination, whether the channel bandwidth of the PPDU is a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, the bandwidth field in the U-SIG can be backwards compatible to indicate 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz-1, 320 MHz-2, 480 MHz-1 channelization for devices that are not capable of operating using 480 MHz or 640 MHz channel bandwidth. Additionally or alternatively, parameters of 480 MHz and 640 MHz PPDUs can be adjusted to account for the increased bandwidth and corresponding RUs compared to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz PPDUs. For example, a tone plan can be defined to account for additional RUs and multiple RUs (MRUs) in 480 MHz or 640 MHz PPDUs. Using a spatial reuse field can allow multiple basic service sets (BSSs) to operate in the same channel for 480 MHz or 640 MHz PPDUs. Defining short and long training fields can enable accurate channel estimation for 480 MHz or 640 MHz PPDUs. Defining pilot signal locations can enable a receiving wireless communication device to accurately perform phase tracking for 480 MHz or 640 MHz PPDUs. Phase rotation and phase shift can be defined for 480 MHz or 640 MHz PPDUs to reduce peak-to-average power ratio (PAPR), and transmit masking can be defined for 480 MHz or 640 MHz PPDUs to improve spectral efficiency. Using puncturing can enable non-contiguous channels (e.g., a non-contiguous 480 MHz channel bandwidth within a 640 MHz contiguous channel bandwidth), or 480 MHz transmission within a 640 MHz PPDU can be supported. Defining allowed puncturing patterns can enable a transmitting wireless communication device to indicate a puncturing pattern of a PPDU to a receiving wireless communication device. Indicating 480 MHz channel bandwidth as a 320 MHz channel bandwidth with an additional 160 MHz channel bandwidth can allow for backwards compatibility and / or interoperability with legacy wireless communication devices (e.g., Extremely High Throughput (EHT) devices) that do not understand 480 MHz channelization but are capable of understanding 320 MHz channelization.For example, such legacy devices can transmit or receive within a primary channel (e.g., a 320 MHz primary channel) configured for legacy devices.

[0077] FIG. 1 A diagram illustrating an example wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 can be an example of a wireless local area network (WLAN), such as a Wi-Fi network. For example, the wireless communication network 100 can be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards, such as defined by the IEEE 802.11-2020 specification or revisions thereof, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and 802.11bn. In some other examples, the wireless communication network 100 can be an example of a cellular radio access network (RAN), such as a 5G or 6G RAN implementing one or more cellular protocols, such as those specified in one or more 3GPP standards. In some other examples, the wireless communication network 100 can include a WLAN that functions in a manner that is interoperable or convergent with one or more cellular RANs to provide greater or enhanced network coverage to wireless communication devices within the wireless communication network 100, or to enable such devices to connect to a core of a cellular network, such as to access network management capabilities and functions provided by the cellular network core.

[0078] The wireless communication network 100 can include a number of wireless communication devices, including at least one wireless access point (AP) 102 and any number of wireless stations (STAs) 104. While FIG. 1 Only one AP 102 is shown in the example of FIG. 1, but the wireless communication network 100 can include multiple APs 102. The AP 102 can be or represent various different types of network entities, including but not limited to a home networking AP, an enterprise-level AP, a single-band AP, a dual-band simultaneous (DBS) AP, a tri-band simultaneous (TBS) AP, a standalone AP, a non-standalone AP, a software-enabled AP (software AP), and a multi-link AP (also referred to as an AP multi-link device (MLD)), as well as a cellular (such as 3GPP, 4G LTE, 5G, or 6G) base station or other cellular network node, such as a Node B, an evolved Node B (eNB), a gNB, a transmission reception point (TRP), or another type of device or equipment included in a radio access network (RAN), including an open RAN (O-RAN) network entity, such as a central unit (CU), a distributed unit (DU), or a radio unit (RU).

[0079] Each of the STAs 104 can also be referred to as a mobile station (MS), a mobile device, a mobile phone, a wireless phone, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other examples. The STAs 104 can represent various devices, such as mobile phones, other handheld or wearable communication devices, netbooks, notebook computers, tablet computers, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR), or extended reality (XR) wireless headsets or other peripheral devices, wireless earbuds, other wearable devices, display devices (e.g., TVs, computer monitors, or video game consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators), or other home appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, vehicles, among other examples.

[0080] A single AP 102 and associated set of STAs 104 can be referred to as a BSS, which is managed by the respective AP 102. FIG. 1 An example coverage area 108 of an AP 102 is additionally shown, which can represent a basic service area (BSA) of the wireless communication network 100. The BSS can be identified by the STAs 104 and other devices through a service set identifier (SSID), as well as a basic service set identifier (BSSID), which can be a medium access control (MAC) address of the AP 102. The AP 102 can periodically broadcast beacon frames (“beacons”) that include the BSSID to enable any STAs 104 that are within wireless range of the AP 102 to “associate” or re-associate with the AP 102 to establish or maintain a respective communication link 106 (also referred to as a “Wi-Fi link” hereinafter) with the AP 102. For example, the beacons can include an identification or indication of a primary channel used by the respective AP 102, as well as a timing synchronization function (TSF) to establish or maintain timing synchronization with the AP 102. The AP 102 can provide various STAs 104 in the wireless communication network 100 with access to external networks via the respective communication links 106.

[0081] To establish a communication link 106 with an AP 102, each of the STAs 104 is configured to perform passive or active scanning operations ("scanning") on a frequency channel in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform passive scanning, a STA 104 listens for beacons transmitted by a respective AP 102 at periodic time intervals, referred to as target beacon transmission times (TBTTs). To perform active scanning, a STA 104 generates and transmits probe requests in sequence on each channel to be scanned, and listens for probe responses from APs 102. Each STA 104 can identify, determine, discover, or select an AP 102 with which to associate according to scanning information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 106 with the selected AP 102. The selected AP 102 assigns an association identifier (AID) to the STA 104 at the end of the association operations, which the AP 102 uses to track the STA 104.

[0082] As wireless networks become more ubiquitous, a STA 104 can have the opportunity to select among many BSSs within range of the STA 104 or among multiple APs 102 that together form an extended service set (ESS), including multiple connected BSSs. For example, the wireless communication network 100 can be connected to a wired or wireless distribution system that can enable multiple APs 102 to be connected in such an ESS. Thus, a STA 104 can be covered by more than one AP 102 and can associate with different APs 102 at different times for different transmissions. In addition, after associating with an AP 102, a STA 104 can also periodically scan its surroundings for a more appropriate AP 102 with which to associate. For example, a STA 104 that is moving relative to its associated AP 102 can perform a "roaming" scan to find another AP 102 with more desirable network characteristics, such as a greater received signal strength indicator (RSSI) or a reduced traffic load.

[0083] In some cases, the STAs 104 can form a network without an AP 102 or without other equipment other than the STAs 104 themselves. One example of such a network is an ad hoc (or wireless ad hoc network). An ad hoc network can alternatively be referred to as a mesh network or a peer-to-peer (P2P) network. In some cases, an ad hoc network can be implemented within a larger network, such as the wireless communication network 100. In such examples, while the STAs 104 can be able to communicate with each other through the AP 102 using the communication links 106, the STAs 104 can also communicate directly with each other via direct wireless communication links 110. Additionally, two STAs 104 can communicate via a direct wireless communication link 110 regardless of whether the two STAs 104 are associated with and served by the same AP 102. In such an ad hoc system, one or more of the STAs 104 can assume the role filled by the AP 102 in a BSS. Such a STA 104 can be referred to as a group owner (GO) and can coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi Direct connections, connections established through the use of Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other P2P group connections.

[0084] In some networks, the AP 102 or the STAs 104, or both, can support applications associated with high throughput or low latency requirements, or can provide lossless audio to one or more other devices. For example, the AP 102 or the STAs 104 can support applications and use cases associated with ultra-low latency (ULL), such as ULL gaming, or the streaming of lossless audio and video to one or more personal audio devices, such as a peripheral device, or an AR, VR, MR, or XR headset device. In scenarios in which a user is using two or more peripheral devices, the AP 102 or the STAs 104 can support an extended personal audio network that enables communication with two or more peripheral devices. Additionally, the AP 102 and the STAs 104 can support additional ULL applications, such as cloud-based applications with ULL and high throughput requirements, such as VR cloud gaming.

[0085] As indicated above, in some implementations, the AP 102 and the STAs 104 can operate and communicate (via respective communication links 106) in accordance with one or more of the IEEE 802.11 family of wireless communication protocol standards. These standards define the WLAN radio and baseband protocol for the physical (PHY) and MAC layers. The AP 102 and the STAs 104 transmit and receive wireless communications (hereinafter also referred to as “Wi-Fi communications” or “wireless packets”) to and from each other in the form of PPDU.

[0086] Each PPDU is a composite structure including a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). Information provided in the preamble can be used by a receiving device to decode the subsequent data in the PSDU. In instances where a PPDU is transmitted on a bonded or wideband channel, the preamble fields can be duplicated and transmitted in each of the multiple component channels. The PHY preamble can include both a legacy portion (or “legacy preamble”) and a non-legacy portion (or “non-legacy preamble”). The legacy preamble can be used for packet detection, automatic gain control, and channel estimation, among other uses. The legacy preamble can also generally be used to maintain compatibility with legacy devices. The format, coding, and information provided in the non-legacy portion of the preamble are associated with the particular IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0087] The APs 102 and STAs 104 in the wireless communication network 100 can transmit PPDUs over an unlicensed spectrum, which can be a portion of spectrum including frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 6 GHz band, the 45 GHz band, and the 60 GHz band. Some examples of the APs 102 and STAs 104 described herein can also communicate in other frequency bands that can support licensed or unlicensed communications. For example, the APs 102 or STAs 104, or both, can also be capable of communicating over a licensed operation band, where multiple operators can have respective licenses to operate in the same or overlapping frequency ranges. Such licensed operation bands can be mapped to or associated with the frequency range designations of FR1 (410-7.125 GHz), FR2 (24.25-52.6 GHz), FR3 (7.125-24.25 GHz), FR4a or FR4-l (52.6-71 GHz), FR4 (52.6-114.25 GHz), and FR5 (114.25-300 GHz).

[0088] Each of the frequency bands can include a number of sub-bands and frequency channels (also referred to as sub-channels). For example, PPDUs conforming to IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn standard amendments can be transmitted on one or more of the 2.4 GHz, 5 GHz, or 6 GHz frequency bands, where each frequency band is divided into a number of 20 MHz channels. Thus, these PPDUs are transmitted on physical channels having a minimum bandwidth of 20 MHz, but can form larger channels through channel bandwidth bonding. For example, a PPDU can be transmitted on a physical channel having a bandwidth of 40 MHz, 80 MHz, 160 MHz, 240 MHz, 320 MHz, 480 MHz, or 640 MHz by bonding bandwidth from multiple 20 MHz channels (e.g., adjacent 20 MHz channels).

[0089] Puncturing is a wireless communication technique that enables a wireless communication device, such as an AP 102 or a STA 104, to transmit and receive wireless communications over a portion of a wireless channel that does not include one or more particular sub-channels (hereinafter also referred to as “punctured sub-channels”). In particular, puncturing can be used to exclude one or more sub-channels from the transmission of a PPDU, including the signaling of the preamble, to avoid interference from static sources, such as existing systems, or to avoid more dynamic in nature interference, such as interference associated with transmissions of other wireless communication devices in an overlapping BSS (OBSS). A transmitting device, such as an AP 102 or a STA 104, can puncture sub-channels over which there is interference and essentially expand the data of the PPDU to cover the remaining portion of the channel bandwidth. For example, if a transmitting device determines (e.g., detects, identifies, ascertains, or calculates) that one or more 20 MHz sub-channels of a wider channel bandwidth are busy or otherwise unavailable in association with a contention operation, the transmitting device implements puncturing to avoid communicating over the unavailable sub-channels while still utilizing the remaining portion of the channel bandwidth. Thus, puncturing enables the transmitting device to improve or maximize throughput by utilizing as much of the available frequency spectrum as possible, and in some cases, reduce latency. Static puncturing in particular makes it possible to consistently use wideband channels in environments or deployments where there can not be enough available contiguous frequency spectrum, such as in the 5 GHz and 6 GHz bands.

[0090] In some examples, the APs 102 or STAs 104 of the wireless communication network 100 can implement EHT or other features that comply with current and future generations of IEEE 802.11 family of wireless communication protocol standards, such as the IEEE 802.1 lbe and 802.1 lbn standard amendments, to provide additional capabilities over other previous systems (e.g., high-efficiency (HE) systems or other legacy systems). For example, the IEEE 802.1 lbe standard amendment introduces a 320 MHz channel bandwidth, which is twice as wide as the bandwidth possible with the IEEE 802.1 lax standard amendment. Thus, the APs 102 or STAs 104 can use the 320 MHz channel bandwidth, enabling a doubling of throughput and network capacity, as well as providing a rate and range gain at high data rates due to the tradeoff of linear bandwidth versus log SNR. EHT and newer wireless communication protocols, such as those referred to as or associated with the IEEE 802.1 lbn standard amendment, can support flexible operating bandwidth enhancements, such as a widened operating bandwidth relative to legacy operating bandwidths or more refined operations relative to legacy operations. For example, EHT systems can allow for communications across operating bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 240 MHz, and 320 MHz. EHT systems can support a variety of bandwidth modes, such as a contiguous 240 MHz bandwidth mode, a contiguous 320 MHz bandwidth mode, a non-contiguous 160+160 MHz bandwidth mode, or a non-contiguous 80+80+80+80 (or “4x80”) MHz bandwidth mode.

[0091] In some examples in which a wireless communication device, such as the AP 102 or a STA 104, operates in a contiguous 320 MHz channel bandwidth mode or a 160+160 MHz channel bandwidth mode, a signal for transmission can be generated by two different transmit chains of the wireless communication device, each having a channel bandwidth of 160 MHz or associated therewith (and each coupled to a different power amplifier). In some other examples, by puncturing a 320 MHz / 160+160 MHz channel bandwidth mode with one or more 80 MHz sub-channels, two transmit chains can be used to support a 240 MHz / 160+80 MHz channel bandwidth mode. For example, a signal for transmission can be generated by two different transmit chains of the wireless communication device, each having a channel bandwidth of 160 MHz, one of the transmit chains outputting a signal having an 80 MHz sub-channel punctured therein. In some other examples in which a wireless communication device can operate in a contiguous 240 MHz channel bandwidth mode or a non-contiguous 160+80 MHz channel bandwidth mode, a signal for transmission can be generated by three different transmit chains of the wireless communication device, each having a channel bandwidth of 80 MHz. In some other examples, a signal for transmission can be generated by four or more different transmit chains of the wireless communication device, each having a channel bandwidth of 80 MHz.

[0092] In non-contiguous examples, the operating bandwidth can span one or more completely different sets of sub-channels. For example, a 320 MHz channel bandwidth can be contiguous and located in the same 6 GHz band, or can be non-contiguous and located in different bands or regions of bands, such as partially in the 5 GHz band and partially in the 6 GHz band.

[0093] In some examples, the AP 102 or a STA 104 can benefit from operational enhancements associated with the EHT and newer generations of IEEE 802.11 family of wireless communication protocol standards. For example, an AP 102 or a STA 104 attempting to gain access to the wireless medium of the wireless communication network 100 can perform techniques such as EHT-enhanced clear channel assessment (CCA) operations, which can include modifications to existing rules, structures, or signaling implemented for legacy systems, such as increased bandwidth, puncturing, or refinements to carrier sensing and signal reporting mechanisms.

[0094] FIG. 2 An example protocol data unit (PDU) 200 that can be used for wireless communications between a wireless AP and one or more wireless STAs is shown. For example, the AP and STAs can be the AP 102 and STAs 104, respectively, of the wireless communication network 100 of FIG. 1. FIG. 1An example of the AP 102 and the STA 104 is described. The PDU 200 can be configured as a PPDU. As shown, the PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, the preamble 202 can include a legacy portion that itself includes a legacy short training field (L-STF) 206 that can consist of two symbols, a legacy long training field (L-LTF) 208 that can consist of two symbols, and a legacy signal field (L-SIG) 210 that can consist of two symbols. The legacy portion of the preamble 202 can be configured in accordance with the IEEE 802.11a wireless communication protocol standard. The preamble 202 can also include a non-legacy portion that includes one or more non-legacy fields 212, e.g., that comply with one or more of the IEEE 802.11 family of wireless communication protocol standards.

[0095] The L-STF 206 generally enables a receiving device, such as the AP 102 or the STA 104, to perform coarse timing and frequency tracking, as well as automatic gain control (AGC). The L-LTF 208 generally enables the receiving device to perform fine timing and frequency tracking, and also to perform an initial estimate of the wireless channel. The L-SIG 210 generally enables the receiving device to determine (e.g., obtain, select, identify, detect, ascertain, derive, or calculate) a duration of the PDU and to use the determined duration to refrain from transmitting over the PDU. The legacy portion of the preamble, including the L-STF 206, the L-LTF 208, and the L-SIG 210, can be modulated in accordance with a binary phase shift keying (BPSK) modulation scheme. The payload 204 can be modulated in accordance with a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another appropriate modulation scheme. The payload 204 can include a PSDU that includes a data field (DATA) 214 that, in turn, can carry higher layer data, e.g., in the form of a MAC protocol data unit (MPDU) or an aggregated MPDU (A-MPDU).

[0096] FIG. 3a An example EHT physical layer PPDU 350 is shown that can be used for communication between a wireless AP and one or more wireless STAs. For example, the AP and the STAs can be the reference FIG. 1An example of the described AP 102 and STA 104. As shown, the PPDU 350 includes a PHY preamble (which includes a legacy portion 352 and a non-legacy portion 354), a payload 356 (which includes a data field 374), and a packet extension 376. The legacy portion 352 of the preamble includes an L-STF 358, an L-LTF 360, and an L-SIG 362. The non-legacy portion 354 of the preamble includes a repetition of the L-SIG (RL-SIG) 364 and a plurality of wireless communication protocol version related signal fields after the RL-SIG 364. For example, the non-legacy portion 354 can include a generic signal field 366 (referred to herein as “U-SIG 366”) and an EHT signal field 368 (referred to herein as “EHT-SIG 368”). The presence of the RL-SIG 364 and the U-SIG 366 can indicate to EHT or later version compatible STAs 104 that the PPDU 350 is an EHT PPDU or a PPDU of any later (post-EHT) version that follows a new wireless communication protocol (following a future IEEE 802.11 wireless communication protocol standard). One or both of the U-SIG 366 and the EHT-SIG 368 can be structured for EHT and beyond other wireless communication protocol versions associated with revisions to the IEEE family of standards and carry version-independent and version-dependent information thereof. For example, the U-SIG 366 can be used by a receiving device (such as the AP 102 or a STA 104) to interpret bits in one or more of the EHT-SIG 368 or the data field 374. In 20, 40, or 80 MHz PPDUs, the information in the U-SIG 366 can be duplicated in each un-punctured 20 MHz subchannel. In 160, 320, 480, or 640 MHz PPDUs, the information in the U-SIG 366 can be duplicated within the entire 80 MHz frequency sub-block, and there can be variations in the content of the U-SIG 366 in different 80 MHz frequency sub-blocks.

[0097] The non-legacy portion 354 also includes an additional short training field 370 (referred to herein as “EHT-STF 370,” but which can also be structured for EHT and beyond other wireless communication protocol versions and carry version-dependent information) and one or more additional long training fields 372 (referred to herein as “EHT-LTF 372,” but which can be structured for EHT and beyond other wireless communication protocol versions and carry version-dependent information). The EHT-STF 370 can be used for timing and frequency tracking as well as AGC, and the EHT-LTF 372 can be used for finer channel estimation.

[0098] EHT-SIG 368 can be used by an AP 102 to identify one or more STAs 104 and to inform the one or more STAs that the AP 102 has scheduled uplink (UL) or downlink (DL) resources for them. EHT-SIG 368 can be decoded by each compatible STA 104 served by the AP 102. EHT-SIG 368 can generally be used by a receiving device to interpret the bits in the data field 374. For example, EHT-SIG 368 can include RU allocation information, spatial stream configuration information, and per-user (e.g., STA-specific) signaling information. Each EHT-SIG 368 can include a common field and at least one user-specific field. In the context of OFDMA, the common field can indicate a distribution of RUs to multiple STAs 104, indicate RU assignments in the frequency domain, indicate which RUs are allocated for MU-MIMO transmissions and which RUs correspond to OFDMA transmissions, and a number of users in the allocation, among other examples. The user-specific fields are assigned to particular STAs 104 and carry STA-specific scheduling information, such as user-specific MCS values and user-specific RU allocation information. Such information enables the corresponding STAs 104 to identify and decode the corresponding RUs in the associated data field 374.

[0099] FIG. 3b An example ultra-high reliability (UHR) multi-user PPDU 380 capable of being used for communications between a wireless AP or non-AP STA and one or more wireless STAs is shown. The UHR multi-user PPDU 380 can be used in the context of OFDMA, MU-MIMO, or a combination of both. The UHR multi-user PPDU 380 can include a preamble 382, a UHR-SIG 384, and a data field 386. FIG. 3aThe EHT PPDU 350 and the UHR multi-user PPDU 380 are the same except that in the UHR multi-user PPDU 380, in the non-legacy portion 354, the EHT-SIG 368 is replaced with a UHR signal field 382 (referred to herein as “UHR-SIG 382”), the EHT-STF 370 is replaced with a UHR-STF 384, and the EHT-LTF 372 is replaced with a UHR-LTF 386. In the UHR multi-user PPDU 380, one or both of the U-SIG 366 and the UHR-SIG 382 can be structured for other wireless communication protocol versions above EHT and UHR that are associated with revisions to IEEE family standards and carry their version-independent and version-dependent information. For example, the U-SIG 366 can be used by a receiving device (such as the AP 102 or a STA 104) to interpret bits in the UHR-SIG 382 or one or more of the data fields 374. In a 20, 40, or 80 MHz PPDU, the information in the U-SIG 366 can be duplicated in each un-punctured 20 MHz subchannel. In a 160, 320, 480, or 640 MHz PPDU, the information in the U-SIG 366 can be duplicated within the entire 80 MHz frequency sub-block, and there can be variations in the content of the U-SIG 366 in different 80 MHz frequency sub-blocks. The UHR-STF 384 can be used for timing and frequency tracking as well as AGC, and the UHR-LTF 386 can be used for finer channel estimation.

[0100] The UHR-SIG 382 can be used by the AP 102 to identify and inform one or more STAs 104 that the AP 102 has scheduled uplink or downlink resources for them. The UHR-SIG 382 can be decoded by every compatible STA 104 served by the AP 102. The UHR-SIG 382 can generally be used by a receiving device to interpret bits in the data fields 374. For example, the UHR-SIG 382 can include RU allocation information, spatial stream configuration information, and per-user (e.g., STA-specific) signaling information. Each UHR-SIG 382 can include a common field and at least one user-specific field. In the context of OFDMA, the common field can indicate RU allocations to multiple STAs 104, indicate RU assignments in the frequency domain, indicate which RUs are allocated for MU-MIMO transmissions and which RUs correspond to OFDMA transmissions and the number of users in the allocation, and so on. The user-specific fields are assigned to specific STAs 104 and carry STA-specific scheduling information, such as user-specific MCS values and user-specific RU allocation information. Such information enables the corresponding STAs 104 to identify and decode the corresponding RUs in the associated data fields 374.

[0101] FIG. 3c An example UHR-based trigger-based (TB) PPDU 390 is shown, which can be used for communication between a wireless AP and one or more wireless STAs. The UHR TB PPDU 390 may be the same as the UHR multi-user PPDU 380, except that the UHR TB PPDU 390 may not include the UHR-SIG 382 within the non-legacy section 354.

[0102] FIG. 4 A hierarchical format of an example PPDU capable of being used for communication between a wireless AP and one or more wireless STAs is shown. For example, the AP and STA can be references. FIG. 1 Examples of AP 102 and STA 104 described. As described, each PPDU 400 includes a PHY preamble 402 and a Physical Layer Convergence Protocol (PLCP) Service Data Unit (PSDU) 404. Each PSDU 404 may represent (or "carry") one or more MAC Protocol Data Units (MPDUs) 416. For example, each PSDU 404 may carry an aggregated MPDU (A-MPDU) 406, which includes an aggregation of multiple A-MPDU subframes 408. Each A-MPDU subframe 406 may include an MPDU frame 410 that includes a MAC delimiter 412 and a MAC header 414 preceding the accompanying MPDU 416, which includes the data portion ("payload" or "frame body") of the MPDU frame 410. Each MPDU frame 410 may also include a Frame Check Sequence (FCS) field 418 for error detection (e.g., the FCS field may include Cyclic Redundancy Check (CRC)) and padding bits 420. MPDU 416 may carry one or more MAC Service Data Units (MSDUs). For example, MPDU 416 may carry an aggregated MSDU (A-MSDU) 422, which comprises multiple A-MSDU subframes 424. Each A-MSDU subframe 424 (e.g., MSDU frame 426) contains a corresponding MSDU 430, which is preceded by a subframe header 428 and followed in some respects by padding bits 432.

[0103] Referring back to the MPDU frame 410, the MAC delimiter 412 can serve as a marker of the beginning of the associated MPDU 416 and indicates the length of the associated MPDU 416. The MAC header 414 can include a plurality of fields containing information defining or indicating characteristics or properties of the data encapsulated within the frame body of the MPDU 416. The MAC header 414 includes a duration field indicating a duration that extends at least from the end of the PPDU until the end of an acknowledgement (ACK) or block ACK (BA) to be transmitted by a receiving wireless communication device for the PPDU. The use of the duration field serves to reserve the wireless medium for the indicated duration and enables the receiving device to establish its network allocation vector (NAV). The MAC header 414 also includes one or more fields indicating addresses of the data encapsulated within the frame body of the MPDU 416. For example, the MAC header 414 can include a combination of source address, transmitter address, receiver address, or destination address. The MAC header 414 can also include a frame control field containing control information. The frame control field can specify a frame type, such as a data frame, a control frame, or a management frame.

[0104] Some APs and STAs (e.g., with reference to FIG. 1) can be configured to support a number of different data rates. For example, a wireless communication device can support a number of different data rates for transmitting data in a PPDU. The data rates can be used to transmit data at different rates, such as to support different quality of service (QoS) levels. The data rates can also be used to support different modulation and coding schemes (MCSs) for transmitting data in a PPDU. The data rates can be used to support different modulation and coding schemes (MCSs) for transmitting data in a PPDU. FIG. 1The described APs 102 and STAs 104 can implement spatial reuse techniques. For example, APs 102 and STAs 104 configured for communicating using protocols defined in the IEEE 802.1 lax or 802.1 lbe standard revisions can be configured with a BSS color. APs 102 associated with different BSSs can be associated with different BSS colors. A BSS color is a numerical identifier of a respective BSS of an AP 102, such as a 6-bit field carried by a SIG field. Each STA 104 can learn its own BSS color upon associating with a respective AP 102. BSS color information is conveyed at both the PHY and MAC sublayers. If an AP 102 or STA 104 detects, obtains, selects, or identifies a wireless packet from another wireless communication device while contending for access, the AP 102 or STA 104 can apply different contention parameters depending on whether the wireless packet was sent by or to another wireless communication device within its BSS, such as another AP 102 or STA 104, or from a wireless communication device from an overlapping BSS (OBSS), as determined, identified, ascertained, or calculated by the BSS color indication in the preamble of the wireless packet. For example, if the BSS color associated with the wireless packet is the same as the BSS color of the AP 102 or STA 104, the AP 102 or STA 104 can use a first RSSI detection threshold when performing a CCA on a wireless channel. However, if the BSS color associated with the wireless packet is different from the BSS color of the AP 102 or STA 104, the AP 102 or STA 104 can use a second RSSI detection threshold instead of the first RSSI detection threshold when performing a CCA on the wireless channel, the second RSSI detection threshold being greater than the first RSSI detection threshold. In this way, the criteria for winning contention is relaxed when interfering transmissions are associated with an OBSS.

[0105] Some APs and STAs (e.g., with reference to FIG. 1The described APs 102 and STAs 104) can implement techniques for spatial reuse that involve participating in a coordinated communication scheme. According to such techniques, an AP 102 can contend for access to a wireless medium to gain control of the medium for a TXOP. The AP that wins contention (hereinafter also referred to as a “sharing AP”) can select one or more other APs (hereinafter also referred to as “shared APs”) to share resources of the TXOP. The sharing AP and the shared APs can be located in proximity to one another such that at least some of their wireless coverage areas at least partially overlap. Some examples can specifically involve coordinated AP TDMA or OFDMA techniques for sharing time or frequency resources of a TXOP. To share time or frequency resources of a TXOP, the sharing AP can divide the TXOP into multiple time segments or frequency segments, each including respective time or frequency resources representing a portion of the TXOP. The sharing AP can allocate the time or frequency segments to itself, or to one or more of the shared APs. For example, each shared AP can utilize the portion of the TXOP assigned by the sharing AP for uplink or downlink communications with STAs associated with it.

[0106] In some examples of such TDMA techniques, each of the multiple portions of the TXOP includes a set of time resources that do not overlap with any time resources of any other of the multiple portions of the TXOP. In such examples, the scheduling information can include an indication of time resources of the multiple time resources of the TXOP that are associated with each portion of the TXOP. For example, the scheduling information can include an indication of time segments of the TXOP, such as an indication of one or more slots or sets of symbol periods associated with each portion of the TXOP, such as for multi-user TDMA.

[0107] In some examples of OFDMA techniques, each of the multiple portions of the TXOP includes a set of frequency resources that do not overlap with any frequency resources of any other of the multiple portions. In such examples, the scheduling information can include an indication of frequency resources of the multiple frequency resources of the TXOP that are associated with each portion of the TXOP. For example, the scheduling information can include an indication of bandwidth parts of a wireless channel, such as an indication of one or more sub-channels or RUs associated with each portion of the TXOP, such as for multi-user OFDMA.

[0108] In this way, the shared AP's acquisition of the TXOP enables communication between one or more additional shared APs and their respective BSSs with proper power control and link adaptation. For example, the shared AP can limit the transmit power of the selected shared APs such that interference from the selected APs does not prevent STAs associated with the TXOP owner from successfully decoding packets transmitted by the shared APs. Such techniques can be used to reduce latency, as the other APs can be able to transmit and receive data according to regular CSMA / CA or enhanced distributed channel access (EDCA) techniques without having to wait to win contention for the TXOP. Additionally, by enabling a group of APs 102 associated with different BSSs to participate in a coordinated AP transmit session during which the group of APs can share at least a portion of a single TXOP acquired by any of the participating APs, such techniques can increase throughput on the BSSs associated with the participating APs and can also enable improvements in throughput fairness. Furthermore, by proper selection of the shared APs and scheduling of their respective time or frequency resources, medium utilization can be maximized or otherwise increased while packet loss due to OBSS interference is minimized or otherwise reduced. Various implementations can achieve these and other advantages without requiring the shared AP or the shared APs to be aware of STAs 104 associated with other BSSs, without requiring a pre-designated or dedicated master AP or a pre-designated group of APs, and without requiring backhaul coordination between the APs participating in the TXOP.

[0109] In some examples in which the signal strength or interference level associated with the selected AP is relatively low, such as less than a given value, or when the decoding error rate of the selected AP is relatively low, such as less than a threshold, the start times of the communications between the different BSSs can be synchronized. Conversely, when the signal strength or interference level associated with the selected AP is relatively high, such as greater than a given value, or when the decoding error rate of the selected AP is relatively high, such as greater than a threshold, the start times can be offset from each other by a time period associated with decoding the preamble of a wireless packet and determining from the decoded preamble whether the wireless packet is an intra-BSS packet or an OBSS packet. For example, the time period between the transmission of an intra-BSS packet and the transmission of an OBSS packet can allow the respective APs (or their associated STAs) to decode the preamble of the wireless packet and obtain the BSS color value carried in the wireless packet to determine whether the wireless packet is an intra-BSS packet or an OBSS packet. In this way, each of the participating APs and their associated STAs can be able to receive and decode intra-BSS packets in the presence of OBSS interference.

[0110] In some examples, the sharing AP can perform polling of a set of non- managed or non-co-managed APs that support coordinated reuse to identify candidates for future spatial reuse opportunities. For example, the sharing AP can transmit one or more spatial reuse poll frames as part of determining one or more spatial reuse criteria and selecting one or more other APs to be part of the shared AP. From the polling, the sharing AP can receive responses from one or more of the polled APs. In some particular examples, the sharing AP can transmit a coordinated AP TXOP indication (CTI) frame to the other APs, the CTI frame indicating time and frequency of resources of a TXOP that can be shared. The sharing AP can select one or more candidate APs upon receiving a coordinated AP TXOP request (CTR) frame from a respective candidate AP indicating that the respective AP desires to participate in the TXOP. The polling response or CTR frame can include a power indication, e.g., a receive (RX) power or RSSI measured by the respective AP. In some other examples, the sharing AP can directly measure potential interference of services supported at one or more APs, such as UL transmissions, and select the shared AP based on the measured potential interference. The sharing AP typically selects APs to participate in the coordinated spatial reuse such that it still protects its own transmissions to and from STAs in its BSS (these transmissions can be referred to as primary transmissions). Then, as described above, resources can be allocated to the selected APs during the TXOP.

[0111] In some implementations, the APs 102 and STAs 104 can support various multi-user communications; i.e., concurrent transmissions from one device to each of multiple devices (e.g., multiple simultaneous downlink communications from the AP 102 to the corresponding STAs 104), or concurrent transmissions from multiple devices to a single device (e.g., multiple simultaneous uplink transmissions from the corresponding STAs 104 to the AP 102). As an example, in addition to MU-MIMO, the APs 102 and STAs 104 can support OFDMA. In some aspects, OFDMA is a multi-user version of OFDM.

[0112] In OFDMA schemes, the available spectrum of a wireless channel can be divided into multiple RUs, each comprising multiple frequency subcarriers (also referred to as “tones”). Different RUs can be allocated or assigned by the AP 102 to different STAs 104 at a particular time. The size and distribution of the RUs can be referred to as a RU allocation. In some examples, RUs can be allocated in 2 MHz intervals, and as such, a minimum RU can include 26 tones consisting of 24 data tones and 2 pilot tones. Thus, in a 20 MHz channel, up to 9 RUs (such as 2 MHz, 26 tone RUs) can be allocated (as some tones are reserved for other purposes). Similarly, in a 160 MHz channel, up to 74 RUs can be allocated. Other tone RUs can also be allocated, such as 52 tone, 106 tone, 242 tone, 484 tone, and 996 tone RUs. Adjacent RUs can be separated by empty subcarriers (such as DC subcarriers), for example, to reduce interference between adjacent RUs, to reduce receiver DC offset, and to avoid transmit center frequency leakage.

[0113] For UL MU transmissions, the AP 102 can transmit a trigger frame to initiate and synchronize UL OFDMA or UL MU-MIMO transmissions from multiple STAs 104 to the AP 102. Such a trigger frame can thereby enable multiple STAs 104 to concurrently transmit UL traffic to the AP 102 in time. The trigger frame can address one or more STAs 104 by respective association identifiers (AIDs), and can assign one or more RUs to each AID (and thereby to each STA 104) that can be used to transmit UL traffic to the AP 102. The AP can also specify one or more random access (RA) RUs that unscheduled STAs 104 can contend for.

[0114] In some wireless communication systems, the AP 102 can allocate or assign multiple RUs to a single STA 104 in an OFDMA transmission (also referred to as “multi-RU aggregation” hereinafter). Multi-RU aggregation, which facilitates puncturing and scheduling flexibility, can ultimately reduce latency. As emerging standards, such as the IEEE 802.11be standard amendment supporting 320 MHz and the IEEE 802.11bn standard amendment supporting 480 MHz and 640 MHz, support increasing bandwidths, there can be various multi-RU (multi-RU) combinations. Values indicating the various multi-RU combinations can be provided by suitable standard specifications, such as one or more of the IEEE 802.11 family of wireless communication protocol standards, including the 802.11be standard amendment.

[0115] Since Wi-Fi is not the only technology operating in the 6 GHz band, the use of multiple RUs in conjunction with channel puncturing can enable the use of large bandwidths, making high throughput possible while avoiding transmitting on the local unlicensed frequencies due to existing operations. Puncturing can be used in conjunction with multi-RU transmission to enable the use of non-contiguous blocks of spectrum to establish a wide channel. In such examples, the portion of the bandwidth between two RUs allocated to a particular STA 104 can be punctured. Thus, spectral efficiency and flexibility can be improved.

[0116] As previously described, STA-specific RU allocation information can be included in the signaling field of the preamble of a PPDU, such as the EHT-SIG field for an EHT PPDU. Preamble puncturing can enable transmission of wider bandwidths in the presence of interference from existing technologies and other wireless communication devices to improve throughput and spectral efficiency. Because RUs can be allocated individually in a MU PPDU, the use of a MU PPDU format can indicate preamble puncturing for SU transmissions. While puncturing in the IEEE 802.11ax standard amendment is limited to OFDMA transmissions, the IEEE 802.11be standard amendment extends puncturing to SU transmissions. In some examples, RU allocation information in the common field of the EHT-SIG can be used to individually allocate RUs to a single user, thereby avoiding a punctured channel. In some other examples, the U-SIG can be used to indicate SU preamble puncturing. For example, SU preamble puncturing can be indicated by the value of the EHT-SIG compression field in the U-SIG.

[0117] As described herein, some wireless communication systems can support 480 MHz and / or 640 MHz PPDU. The U-SIG in a PPDU can include a bandwidth field and a bandwidth extension field, where the bandwidth extension field can indicate, in combination with the bandwidth field, whether the operating bandwidth is 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320MHz-1, 320MHz-2, 480MHz-1, 480MHz-2, 480MHz-3, 640MHz-1, 640MHz-2, 640MHz-3, or 640MHz-4. According to some aspects described herein, a bandwidth extension field can be included in a PPDU in addition to the bandwidth field, such as in scenarios where the bandwidth field in the U-SIG alone is not sufficient to indicate a particular 480 MHz channel bandwidth or 640 MHz channel bandwidth in addition to the possible 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz channel bandwidths, leaving at least one reserved value. Additionally, as described herein, parameters of a 480 MHz or 640 MHz PPDU can be defined to account for the larger bandwidth of the 480 MHz or 640 MHz PPDU compared to 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz PPDUs.

[0118] FIG. 5 An example of a channelization diagram 500 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown. The channelization diagram 500 can implement, or be implemented by, aspects of the wireless communication network 100.

[0119] For example, a first example channelization diagram 505 shows possible 160 MHz, 320 MHz, 480 MHz, and 640 MHz channels that can be used for communication of PPDUs between an AP 102 and a STA 104.

[0120] In some aspects, a 480 MHz PPDU can be defined for supporting 480 MHz channel bandwidth transmissions. Some aspects can define a contiguous 480 MHz channel bandwidth. Some aspects can define a 640 MHz PPDU for supporting 640 MHz channel bandwidth transmissions. Within a 640 MHz PPDU, for example, a contiguous 480 MHz channel bandwidth transmission or a non-contiguous 480 channel bandwidth MHz transmission can be supported when a puncturing pattern is employed. A contiguous 480 MHz channel bandwidth transmission within a 640 MHz PPDU can make 480 MHz a redundant channel bandwidth mode, but using a defined 480 MHz channel bandwidth can save signaling overhead compared to a contiguous 480 MHz channel bandwidth transmission within a 640 MHz PPDU. In some aspects, a 640 MHz PPDU can support both 480 MHz channel bandwidth and 640 MHz channel bandwidth transmissions. For example, both contiguous and non-contiguous 480 MHz channel bandwidth transmissions can be supported as puncturing patterns when a 640 MHz PPDU is employed.

[0121] As shown, up to five 480 MHz channels and up to four 640 MHz channels can be defined with overlap. The 480 MHz channels and / or 640 MHz channels can be defined to be in sub-7 GHz. For example, one reserved entry (e.g., reserved entry 138) in the operating class field in the 802.11be specification Appendix E can be used to define the five 480 MHz channels as shown in Table 1. The 480 MHz channels can include any three adjacent 160 MHz channels in the 6 GHz band. As shown, up to three types of channelization for 480 MHz channels can be defined: 480 MHz-1, 480 MHz-2, and 480 MHz-3. The 480 MHz-1 channelization can include 480 MHz channels with channel center frequencies numbered 47 and 143. The 480 MHz-2 channelization can include 480 MHz channels with channel center frequencies numbered 79 and 175. The 480 MHz-3 channelization can include 480 MHz channels with channel center frequencies numbered 111. FIG. 5

[0122] Table 1

[0123] As another example, one reserved entry (e.g., reserved entry 138) in the operating class in the 802.11be specification Appendix E can be used to define the four 640 MHz channels as shown in Table 2. The 640 MHz channels can include any four adjacent 160 MHz channels in the 6 GHz band. As shown, up to three types of channelization for 640 MHz channels can be defined: 640 MHz-1, 640 MHz-2, and 640 MHz-3. The 640 MHz-1 channelization can include 640 MHz channels with channel center frequencies numbered 47 and 143. The 640 MHz-2 channelization can include 640 MHz channels with channel center frequencies numbered 79 and 175. The 640 MHz-3 channelization can include 640 MHz channels with channel center frequencies numbered 111. FIG. 5 ​As shown, up to four types of channelization for 640MHz channels can be defined: 640MHz-1, 640MHz-2, 640MHz-3, and 640MHz-4. The 640MHz-1, 640MHz-2, 640MHz-3, and 640MHz-4 channelization can include 640MHz channels with channel center frequencies numbered 63, 95, 127, and 159, respectively.

[0124] Table 2

[0125] The second example channelization diagram 510 illustrates a scenario in which channels can be extended to 7.225GHz. Extending to 7.225GHz allows for the definition of a new 160MHz channel (channel center frequency index #239). In contrast, 6GHz channels can extend to channel center frequency index #207 in 160MHz channelization. Defining a channel with channel center frequency index #239 and a channel bandwidth of 160MHz can be implemented by defining a fourth channel with channel center frequency index #223 in 320MHz-1 channelization, defining a second channel with channel center frequency index #207 in 480MHz-3 channelization, and / or defining a fifth 640MHz channel with channel center frequency index #191 in the first 640MHz channelization 640MHz-1.

[0126] In some examples, with channel extension to 6GHz, five 480MHz channels can be defined in three 480MHz channelizations (channel center frequency indices #47 and #143 in 480MHz-1, channel center frequency indices #79 and #175 in 480MHz-2, and channel center frequency index #111 in 480MHz-3). In some examples, with channel extension to 7.225GHz, six 480MHz channels can be defined in three 480MHz channelizations (channel center frequency indices #47 and #143 in 480MHz-1, channel center frequency indices #79 and #175 in 480MHz-2, and channel center frequency indices #111 and #207 in 480MHz-3). In some examples, two 480MHz channelizations can be defined, and accordingly four 480MHz channels can be defined (channel center frequency indices #47 and #143 in 480MHz-1 and channel center frequency indices #79 and #175 in 480MHz-2).

[0127] In some examples, such as in UHR, two 480 MHz channelizations can be defined. As shown in Table 3, a reserved entry, such as reserved entry 138, can be used to define four 480 MHz channelizations. In some examples, such as in future generations of communications, another entry can be used to define additional 480 MHz channels. For example, if the channel is extended to 7.225 GHz, a second reserved entry (139) in the operating class in the 802.11be specification Appendix E can be used to define two more 480 MHz channels in the 480 MHz-3 channelization (e.g., channels #111 and #207 in the second example channelization map 510), as shown in Table 4.

[0128] Table 3

[0129] Table 4

[0130] In some examples, such as in UHR, four 640 MHz channelizations can be defined. As shown in Table 5, a reserved entry, such as reserved entry 138, can be used to define four 640 MHz channelizations, where 640 MHz-1 includes two channels and 640 MHz-2, 640 MHz-3, and 640 MHz-4 each include one channel. In examples where 5 640 MHz channels are defined, the channel bandwidth of the PPDU can be signaled using the bandwidth field and the bandwidth extension field, as described herein. In some examples, as shown in Table 6, two non-overlapping 640 MHz channels can be defined. For example, channels with channel center frequency index #63 and channel center frequency index #191 can be defined within the 640 MHz-1 channelization. In such examples, the channel bandwidth can be indicated via the bandwidth field (e.g., the bandwidth extension field is not used because one 640 MHz channelization is defined, which can be indicated via one of the reserved bits of the bandwidth field).

[0131] Table 5

[0132] Table 6

[0133] FIG. 6An example of a signaling diagram 600 supporting techniques for transmitting 480MHz and 640MHz channel bandwidths in Wi-Fi is shown. Signaling diagram 600 may implement, or be implemented by, various aspects of wireless communication network 100. For example, the signaling diagram includes wireless communication devices 602-a and 602-b, which may be examples of AP 102 or STA 104 as described herein. Wireless communication device 602-a may communicate with wireless communication device 602-b via wireless link 604, which may be an example of communication link 106 as described herein.

[0134] For example, wireless communication device 602-a can send PPDU 606 to wireless communication device 602-b. PPDU 606 can be as shown in the reference. FIG. 3a The PPDU 350 described or as referenced FIG. 4 The described PPDU 400 is an example. For example, PPDU 606 may include a preamble 608 and a payload 610. The preamble 608 may be an example of PHY preamble 402, and the payload may be as referenced. FIG. 4 The described PSDU 404 is an example. For example, the preamble 608 may include legacy portion 352 and non-legacy portion 354, and the payload 610 may be as referenced. FIG. 3a The described payload is 356.

[0135] PPDU 606 can be a 480MHz PPDU or a 640MHz PPDU. The U-SIG field in preamble 608 (e.g., FIG. 3a The U-SIG 366 may include a bandwidth field and a bandwidth extension field, which together (e.g., combined) indicate the channel bandwidth. Based on the frequency at which the wireless communication device 602-b receives the preamble 608 and the channel bandwidth indicated by the bandwidth field and the bandwidth extension field, the wireless communication device 602-b may identify the channelization (e.g., center frequency and channel bandwidth) of the PPDU 606.

[0136] The bandwidth field in the U-SIG can be a 3-bit version-independent field. The bandwidth field in the U-SIG can use 6 values to indicate whether the channelization is 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320MHz-l, or 320MHz-2. Thus, the bandwidth field can include two reserved values (values 6 and 7) to indicate channel bandwidths other than 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320MHz. The two reserved values can not be sufficient to indicate two possible 480 MHz channelizations or two possible 640 MHz channelizations in addition to at least one reserved value for a future generation. The two reserved values can not be sufficient to indicate three possible 480 MHz channelizations or four possible 640 MHz channelizations. A bandwidth extension field can be used in the U-SIG to jointly indicate 480 MHz channel bandwidth or 640 MHz channel bandwidth. In some aspects, the bandwidth extension field can be a version-dependent field, which can mean that the presence, location, size, and interpretation of the bandwidth extension field depend on the value in the PHY version identifier field in the preamble 608. In some aspects, the bandwidth extension field can be a version-independent from UHR, which can mean that the presence, location, size, and interpretation of the bandwidth extension field is consistent between PHY versions from UHR and future generations, i.e., the PHY version identifier field in the preamble 608 does not indicate EHT. Both the bandwidth field and the bandwidth extension field can carry different information in different subbands (e.g., in each 160 MHz subband of a 480 MHz or 640 MHz channel bandwidth). An EHT STA 104 can understand the bandwidth field and can ignore the bandwidth extension field, and a UHR STA (e.g., the wireless communication device 602-b) can understand both the bandwidth field and the bandwidth extension field. In some aspects, the preamble 608 can not include the bandwidth extension field, and the two reserved values (6 and 7) can be used to indicate two 480 MHz channelizations (e.g., 480MHz-l and 480MHz-2 channelizations) or two 640 MHz channelizations (e.g., 640MHz-l and 640MHz-2 channelizations). This design without the bandwidth extension field can be easy to implement, but can not be understood by in-BSS and overlapping BSS (OBSS) EHT STAs 104 and thus can break interoperability with such EHT STAs 104. Additionally, in such examples without the bandwidth extension field, the 3-bit bandwidth field can not include any reserved values for future generations.

[0137] For 480 MHz channel bandwidth, the combination of the bandwidth field and the bandwidth extension field can indicate the channel bandwidth to be used for PPDU transmission / reception. In a first aspect related to 480 MHz channel bandwidth, the bandwidth extension field can be a 2-bit field in the U-SIG. In the first aspect related to 480 MHz channel bandwidth, if the bandwidth field value is 0-5 or 7, the bandwidth extension field can be considered to be ignored, as explained in subclause 36.3.12.7 of 802.11be Draft D3.2. For example, a receiving device can continue processing the PPDU regardless of the contents of this field. In the first aspect related to 480 MHz channel bandwidth, if the value in the bandwidth field is 6 (or in some aspects 7), the value in the 2-bit bandwidth extension field can indicate 480 MHz-1 channelization, 480 MHz-2 channelization, or 480 MHz-3 channelization, leaving the remaining value (e.g., set to a validation value). In a second aspect related to 480 MHz channel bandwidth, the bandwidth extension field can be a 1-bit field in the U-SIG. In the second aspect, if the bandwidth field value is 0-3 or 7, the bandwidth extension field can be ignored. In the second aspect related to 480 MHz channel bandwidth, if the bandwidth field value is 4-6, the bandwidth extension field can be set to 0 to indicate 320 MHz-1 channelization, 320 MHz-2 channelization, or a reserved value (e.g., set to a validation value), respectively. In the second aspect related to 480 MHz channel bandwidth, if the bandwidth field value is 4-6, the bandwidth extension field can be set to 1 to indicate 480 MHz-1 channelization, 480 MHz-2 channelization, or 480 MHz-3 channelization. In a third aspect related to 480 MHz channel bandwidth, the bandwidth extension field can be a 1-bit field in the U-SIG. In the third aspect related to 480 MHz channel bandwidth, if the bandwidth field value is 0-5 or 7, the bandwidth extension field can be considered to be ignored, as explained in subclause 36.3.12.7 of 802.11be Draft D3.2. For example, a receiving device can continue processing the PPDU regardless of the contents of this field. In the third aspect related to 480 MHz channel bandwidth, if the value in the bandwidth field is 6 (or in some aspects 7), the value in the 1-bit bandwidth extension field can indicate 480 MHz-1 channelization or 480 MHz-2 channelization.

[0138] Similarly, for 320 MHz channel bandwidths, the combination of the bandwidth field and the bandwidth extension field can indicate the channel bandwidth used for PPDU transmission / reception. In a first aspect related to 320 MHz channel bandwidths, the bandwidth extension field can be a 1-bit field in the U-SIG. In the first aspect related to 320 MHz channel bandwidths, if the bandwidth field value is 0-5 or 7, the bandwidth extension field can be considered to be ignored, as explained in subclause 36.3.12.7 of 802.11be Draft D3.2. For example, a receiving device can proceed with processing the PPDU regardless of the content of this field. In the first aspect related to 320 MHz channel bandwidths, if the value in the bandwidth field is 6 (or in some aspects 7), the value in the 1-bit bandwidth extension field can indicate 320 MHz-1 channelization or 320 MHz-2 channelization. In a second aspect related to 320 MHz channel bandwidths, the bandwidth extension field can be a 2-bit field in the U-SIG. In the second aspect, if the bandwidth field value is 0-3, the bandwidth extension field can be ignored. In the second aspect, if the bandwidth field value is 4-7, the bandwidth extension field can be set to 0 to indicate 160 MHz-1 channelization, 160 MHz-2 channelization, or two reserved values (e.g., set to a verification value), respectively. In the second aspect related to 320 MHz channel bandwidths, if the bandwidth field value is 4-7, the bandwidth extension field can be set to 1 to indicate 320 MHz-1 channelization or 320 MHz-2 channelization. In a third aspect related to 320 MHz channel bandwidths, the bandwidth extension field can be a 1-bit field in the U-SIG. In the third aspect related to 320 MHz channel bandwidths, if the bandwidth field value is 0-5 or 7, the bandwidth extension field can be considered to be ignored, as explained in subclause 36.3.12.7 of 802.11be Draft D3.2. For example, a receiving device can proceed with processing the PPDU regardless of the content of this field. In the third aspect related to 320 MHz channel bandwidths, if the value in the bandwidth field is 6 (or in some aspects 7), the value in the 1-bit bandwidth extension field can indicate 320 MHz-1 channelization or 320 MHz-2 channelization.

[0139] If the PPDU 606 is a 480 MHz PPDU, a tone plan can be defined for 480 MHz PPDUs. The 480 MHz tone plan can be a replication of six EHT 80 MHz tone plans, one in each 80 MHz frequency portion of the 480 MHz channel bandwidth. In some aspects, in addition to the RUs and MRUs defined in 802.11be, a 6 x 996 tone RU can be defined. In such aspects, the RU can span the entire 480 MHz without puncturing and can include six 996 tone RUs, one in each 80 MHz portion of the 480 MHz channel bandwidth. In some aspects, in addition to the RUs and MRUs defined in 802.11be, a non-OFDMA or MRU in OFDMA can be defined. Such MRUs can include a 4 x 996 tone MRU (15 MRUs if arbitrarily formed or 3 MRUs if formed only by two 2 x 996 tone RUs), a 4 x 996 + 484 tone MRU (60 MRUs if arbitrarily formed or 12 MRUs if formed only by two 2 x 996 tone RUs and one 484 tone RU), a 4 x 996 + 484 + 242 tone MRU (120 MRUs if arbitrarily formed or 24 MRUs if formed only by two 2 x 996 tone RUs and one 484 + 242 tone MRU), a 5 x 996 tone MRU (6 MRUs), a 5 x 996 + 484 tone MRU (12 MRUs), or a 5 x 996 + 484 + 242 tone MRU (24 MRUs).

[0140] If the PPDU 606 is a 640 MHz PPDU, a tone plan can be defined for 640 MHz PPDUs. The 640 MHz tone plan can be a replication of eight EHT 80 MHz tone plans, one in each 80 MHz frequency portion of the 640 MHz channel bandwidth. In some aspects, in addition to the RUs and MRUs defined in 802.11be, an 8 x 996 tone RU can be defined. In such aspects, the RU can span the entire 640 MHz without puncturing and can include eight 996 tone RUs, one in each 80 MHz portion of the 640 MHz bandwidth. In some aspects, in addition to the RUs and MRUs defined in 802.11be, a non-OFDMA or MRU in OFDMA can be defined. Such MRUs can include a 4 x 996 tone RU (2 RUs if formed by lower and upper 320 MHz subbands), a 4 x 996 + 484 tone MRU, a 5 x 996 tone MRU (8 MRUs if formed by one 4 x 996 tone RU and one 996 tone RU), a 5 x 996 + 484 tone MRU, a 6 x 996 tone MRU (4 MRUs if formed by three 2 x 996 tone RUs), a 6 x 996 + 484 tone MRU, a 7 x 996 tone RU (8 MRUs), or a 7 x 996 + 484 tone RU (16 MRUs).

[0141] If the PPDU 606 is a 480 MHz PPDU, different allowed puncturing patterns can be defined. For non-OFDMA 480 MHz PPDUs, puncturing patterns with 40 MHz granularity can be defined, where “1” indicates no puncturing for the 40 MHz portion and “x” indicates puncturing of the 40 MHz portion. The first defined puncturing pattern includes no puncturing ([1 1 1 1 1 1 1 1 1 1]). 40 MHz puncturing patterns (12 patterns) can be defined, which correspond to puncturing any portion of the 40 MHz portion (e.g., [x 1 1 1 1 1 1 1 1 1 1], [1 x 1 1 1 1 1 1 1 1 1], etc.), resulting in a 5 x 996 + 484 tone MRU. 80 MHz puncturing patterns (6 patterns) can be defined, which correspond to puncturing any 80 MHz portion (e.g., [xx 1 1 1 1 1 1 1 1 1 1], [1 1 x 1 1 1 1 1 1 1 1], etc.), resulting in a 5 x 996 MRU. Two 80 MHz puncturing patterns concurrently (up to 13 patterns) can be defined: [xx 1 1 x x 1 1 1 1 1], [xx 1 1 1 1 x x 1 1 1 1], [xx 1 1 1 1 1 1 x x 1 1], [xx 1 1 1 1 1 1 1 1 x x], [1 1 x x x x 1 1 1 1 1], [1 1 x x 1 1 x x 1 1 1], [1 1 x x 1 1 1 1 x x 1], [1 1 x x 1 1 1 1 1 1 x x], [1 1 1 1 x x x x 1 1 1 1], [1 1 1 1 x x 1 1 x x 1 1], [1 1 1 1 x x 1 1 1 1 x x], [1 1 1 1 1 x x x 1 1 1 1], [1 1 1 1 1 x x 1 1 1 1 x], resulting in a 4 x 996 tone MRU. 80 MHz and 40 MHz puncturing patterns concurrently (60 patterns) can be defined. For 80 MHz and 40 MHz puncturing patterns concurrently, in each of the 6 patterns where one 80 MHz is punctured, the additional 40 MHz is punctured (e.g., [xxx 1 1 1 1 1 1 1 1], resulting in a 4 x 996 + 484 tone MRU. For OFDMA PPDUs, puncturing patterns can be defined as in EHT. Thus, for 480 MHz OFDMA PPDUs, within each 80 MHz portion of the 480 MHz channel bandwidth, the allowed puncturing patterns are: 1 1 1 1 (no puncturing), x 1 1 1, 1 x 1 1, 1 1 x 1, 1 1 1 x, x x 1 1, 1 1 x x, and 1 x x 1, where each number represents a 20 MHz, “1” means no puncturing, and “x” means puncturing.

[0142] If the PPDU 606 is a 640 MHz PPDU, different allowed puncturing patterns can be defined. Similar to the 480 MHz PPDU, for non-OFDMA 640 MHz PPDUs, puncturing patterns can be defined with 40 MHz granularity, where “1” indicates no puncturing for the 40 MHz portion and “x” indicates puncturing of the 40 MHz portion. The first defined puncturing pattern includes no puncturing ([11111111 1111 1111]). 40 MHz puncturing patterns (16 patterns) can be defined, which correspond to puncturing any portion of the 40 MHz portion (e.g., [x111 1111 1111 111], [1x11 1111 1111 111], etc.), resulting in a 7 x 996 + 484 tone MRU. 80 MHz puncturing patterns (8 patterns) can be defined, which correspond to puncturing any 80 MHz portion (e.g., [xx111111 1111 111], [11xx 1111 1111 1111], etc.), resulting in a 7 x 996 MRU. 160 MHz puncturing patterns (4 patterns) can be defined, which correspond to puncturing any 80 MHz portion (e.g., [xxxx 1111 1111 111], [1111 xxxx 1111 1111], etc.), resulting in a 6 x 996 MRU. Two 80 MHz puncturing patterns concurrently (24 patterns, including the four 160 MHz puncturing patterns) can be defined, which correspond to puncturing any two of the 80 MHz portions (e.g., [xx11 xx11 1111 1111]), resulting in a 6 x 996 tone MRU.Concurrent 160MHz and 80MHz punctured modes can be defined (24 modes if any combination, or 12 modes if puncturing only the first or fourth 160MHz) (e.g., [xxxx xx11 1111 1111], [xxxx 11xx 1111 1111], [xxxx 1111xx11 1111], [xxxx 1111 11xx 1111], [xxxx 1111 1111 xx11], [xxxx 1111 1111 11xx], [xx11 xxxx 1111 1111], [11xx xxxx 1111 1111], [1111 xxxx xx11 1111], [1111 xxxx11xx 1111], [1111 xxxx 1111 xx11], [1111 xxxx 1111 11xx], [xx11 1111 xxxx 1111], [11xx 1111 xxxx 1111], [1111 xx11 xxxx 1111], [1111 11xx xxxx 1111], [1111 1111xxxx xx11], [1111 1111 xxxx 11xx], [xx11 1111 1111 xxxx], [11xx 1111 1111 xxxx], [1111 xx11 1111 xxxx], [1111 11xx 1111 xxxx], [1111 1111 xx11 xxxx], [1111 111111xx xxxx],] resulting in 5 x 996-tone MRU. For OFDMA PPDUs, puncturing modes can be defined as in EHT. Thus, for 640MHz OFDMA PPDUs, the puncturing modes allowed within each 80MHz portion of the 640MHz bandwidth are: 1111 (no puncturing), x111, lxll, lIXl, lllx, xxll, lIXl, and lxxl, where each number represents a 20MHz, “1” means no puncturing, and “x” means puncturing.

[0143] If the PPDU 606 is a trigger-based (TB) PPDU, the preamble 608 can not indicate the puncturing channel information. A 5-7 bit puncturing channel information field can be included in the preamble 608 of the PPDU 606 that is a PPDU type other than a TB PPDU (e.g., a multi-user (MU) PPDU). For non-OFDMA PPDUs, the puncturing channel information field indicates the puncturing pattern for non-OFDMA transmission and the corresponding MRU. For example, for a 480 MHz PPDU, 5 bits of puncturing channel information can be used to indicate no puncturing, 40 MHz puncturing (one of 12 patterns), 80 MHz puncturing (one of 6 patterns), or two 80 MHz puncturing concurrently (one of 13 patterns). As another example, for a 480 MHz PPDU, 7 bits of puncturing channel information can be used to indicate no puncturing, 40 MHz puncturing (one of 12 patterns), 80 MHz puncturing (one of 6 patterns), two 80 MHz puncturing concurrently (one of 13 patterns), or 80 MHz and 40 MHz puncturing concurrently (one of 60 patterns). As another example, for a 640 MHz PPDU, 5 bits of puncturing channel information can be used to indicate no puncturing, 80 MHz puncturing (one of 8 patterns), 160 MHz puncturing (one of 4 patterns), or 160 MHz and 80 MHz puncturing concurrently (one of 12 patterns if puncturing is allowed for only the first or fourth 160 MHz). As another example, for a 640 MHz PPDU, 7 bits of puncturing channel information can be used to indicate no puncturing, 40 MHz puncturing (one of 16 patterns), 80 MHz puncturing (one of 8 patterns), 160 MHz puncturing (one of 4 patterns), 160 MHz and 80 MHz puncturing concurrently (one of 24 patterns if any combination is allowed). For OFDMA PPDUs (same as EHT), 4 bits in the puncturing channel information field can be used to indicate a 4-bit bitmap of the puncturing pattern (referred to as “allowed puncturing pattern”) for the current 80 MHz frequency sub-block, and the remaining bits in the puncturing channel information field can be ignored.

[0144] If the PPDU 606 is a 480 MHz TB PPDU, in some aspects, two spatial reuse fields can be included in the U-SIG in the preamble 608. In such aspects, a spatial reuse 1 field and a spatial reuse 2 field can indicate spatial reuse information for each 20 MHz portion of the lower and upper 240 MHz portions within the 480 MHz bandwidth, respectively. If the PPDU 606 is a 480 MHz TB PPDU, in some aspects, three spatial reuse fields can be included in the U-SIG in the preamble 608. In such aspects, a spatial reuse 1 field, a spatial reuse field 2, and a spatial reuse 3 field can indicate spatial reuse information for each 20 portion MHz of the lowest 160 MHz, the second lowest 160 MHz, and the highest 160 MHz portion within the 480 MHz bandwidth, respectively.

[0145] If the PPDU 606 is a 640 MHz TB PPDU, in some aspects, two spatial reuse fields can be included in the U-SIG in the preamble 608. In such aspects, a spatial reuse 1 field and a spatial reuse 2 field can indicate spatial reuse information for each 20 MHz portion of the lower and upper 320 MHz portions within the 640 MHz bandwidth, respectively. If the PPDU 606 is a 640 MHz TB PPDU, in some aspects, four spatial reuse fields can be included in the U-SIG in the preamble 608. In such aspects, a spatial reuse 1 field, a spatial reuse field 2, a spatial reuse field 3, and a spatial reuse 4 field can indicate spatial reuse information for each 20 portion MHz of the lowest 160 MHz, the second lowest 160 MHz, the third lowest 160 MHz, and the highest 160 MHz portion within the 640 MHz bandwidth, respectively.

[0146] As described herein, the preamble 608 can include an EHT-SIG that indicates RU allocation (e.g., FIG. 3aRU allocation subfields in the EHT-SIG 368). In some aspects, the RU allocation in the EHT-SIG for 480 MHz PPDUs can be backward compatible with the EHT RU allocation subfields. In some such aspects, the EHT 9-bit RU allocation subfield design can be reused with the added entries of new MRUs available based on the increased bandwidth of 480 MHz PPDUs. For example, the EHT RU allocation subfield has 1+8=9 values set to validate and 26x8 values set to ignore. These values set to ignore can be repurposed for new MRUs (e.g., 4x996-tone MRU (15 MRUs formed arbitrarily) and 5x996-tone MRU (6 MRUs), each with 1 to 8 user fields). In some aspects that are backward compatible with the EHT RU allocation subfields, more RU allocation subfields can be added. For example, 480 MHz bandwidth can use a total of 12 RU allocation subfields, one per 20 MHz. There are two 9-bit RU allocation-A subfields and six 9-bit RU allocation-B subfields, and thus four more 9-bit RU allocation-C subfields can be added, followed by a 4-bit CRC and a 6-bit tail field to account for the additional RUs. In some aspects that are backward compatible with the EHT RU allocation subfields, one or more code blocks for common fields in the EHT-SIG can be added. For example, three code blocks can be used for RU allocation of 480 MHz PPDUs, one for other fields and RU allocation-A subfields, one for RU allocation-B subfields, and the last one for RU allocation-C subfields. In some aspects, a new RU allocation design can be implemented in the EHT-SIG. For example, the RU allocation subfields can be designed using more bits to accommodate more new MRUs in 480 MHz bandwidth. As another example, the RU allocation subfields can be designed using a different mapping for larger bandwidths (e.g., 480 MHz bandwidth starts with a minimum 242-tone RU size). As another example, more RU allocation subfields can be added, including a total of 12 RU allocation subfields, one per 20 MHz. As another example, the code blocks can be restructured according to the size of the RU allocation subfields.

[0147] Similarly, for a 640 MHz PPDU, in some aspects, the RU allocation in the EHT-SIG for a 640 MHz PPDU can be backward compatible with the EHT RU allocation subfield. In some such aspects, the EHT 9-bit RU allocation subfield design can be reused with the addition of new MRU entries available based on the increased bandwidth of the 640 MHz PPDU. For example, the EHT RU allocation subfield has 1 + 8 = 9 values set to validate and 26 x 8 values set to ignore. These values set to ignore can be repurposed for new MRU (e.g., 4 x 996-tone RU (2 RUs), 5 x 996-tone MRU (8 MRUs), 6 x 996-tone MRU (4 MRUs), or 7 x 996-tone RU (8 MRUs), each with 1 to 8 user fields). In some aspects that are backward compatible with the EHT RU allocation subfield, more RU allocation subfields can be added. For example, a 640 MHz bandwidth can use a total of 16 RU allocation subfields, one RU allocation subfield per 20 MHz. There are two 9-bit RU allocation-A subfields and six 9-bit RU allocation-B subfields, and thus another six 9-bit RU allocation-C subfields can be added, followed by a 4-bit CRC and a 6-bit tail field to account for additional RUs, and as well as two more 9-bit RU allocation-D subfields, followed by a 4-bit CRC and a 6-bit tail field. In some aspects that are backward compatible with the EHT RU allocation subfield, one or more code blocks for common fields in the EHT-SIG can be added. For example, four code blocks can be used for RU allocation of a 640 MHz PPDU, one for other fields and the RU allocation-A subfield, one for the RU allocation-B subfield, one for the RU allocation-C subfield, and the last one for the RU allocation-D subfield. In some aspects, a new RU allocation design can be implemented in the EHT-SIG. For example, more bits can be used to design the RU allocation subfield to accommodate more new MRU in a 640 MHz bandwidth. As another example, the RU allocation subfield can be designed with a different mapping for larger bandwidths (e.g., 640 MHz bandwidth starts with a minimum 242-tone RU size). As another example, more RU allocation subfields can be added, including a total of 16 RU allocation subfields, one per 20 MHz. As another example, the code blocks can be restructured according to the size of the RU allocation subfield.

[0148] The wireless communication device 602-a can transmit a UHR STF sequence in the preamble 608, which the wireless communication device 602-b can use for channel estimation for the PPDU 606. In some aspects, the UHR STF sequence for a 480 MHz or 640 MHz PPDU can be similar to the UHR STF sequence in 802.11be. In some aspects, a lx UHR STF sequence can be transmitted, and in some aspects, a 2x UHR STF sequence can be transmitted. For example, a lx UHR STF sequence can be used for UHR single-user or multi-user PPDUs, and a 2x UHR STF sequence can be used for UHR trigger-based PPDUs. In some aspects, the 802.11bn 480 MHz or 640 MHz PPDU can reuse the lx EHT-STF and 2x EHT-STF defined for 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz PPDUs.

[0149] For a 480 MHz PPDU, in a first aspect, to generate a UHR STF sequence, the wireless communication device 602-a can repeat a lx or 2x 80 MHz high-efficiency STF sequence (80HES) on the second, third, fourth, fifth, and sixth 80 MHz portions of the 480 MHz bandwidth and multiply the second, third, fourth, fifth, and sixth 80 MHz portions by additional coefficients. For example, the UHR STF sequence can be given by [80HES a 80HES b 80HES c 80HES d 80HES e 80HES]. For a lx UHR STF, 80HES = {M 1 -M 0 -M 1 -M}, and for a 2x UHR STF, 80HES = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M}, where M {-1, -1, -1, +1, +1, +1, -1, +1, +1, +1, -1, +1, +1, -1, +1}. As in 802.11ax or 802.11be, the candidates for a, b, c, d, and e are 1 and -1, which can be optimized by a minimax approach considering all RU and MRU combinations with and without puncturing. For example, for a lx UHR STF of a 480 MHz PPDU, the UHR STF sequence can be given by -3056:16:3056 = {M 1 -M 0 -M 1 -M a (0 M 1 -M 0 -M 1 -M) b (0 M 1 -M 0 -M 1 -M) c (0 M 1 -M 0 -M 1 -M) d (0 M 1 -M 0 -M 1 -M) e (0 M 1 -M 0 -M 1 -M)} (1+j) / sqrt(2), where UHRS -3064 = UHRS -2040 = UHRS -1032 = UHRS -1016 = UHRS -8 = UHRS8=UHRS 1016 = UHRS 1032 = UHRS 2040 = UHRS 3064 = 0. For a 2x UHR STF of a 480 MHz PPDU, UHRS -3064:8:3064 = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M a (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) b (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) c (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) d (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) e (0 M-1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M)} (1+j) / sqrt(2).

[0150] For a 480 MHz PPDU, in a second aspect, to generate a UHR STF sequence, the wireless communication device 602-a can repeat a 1x or 2x 160 MHz sequence (160HES) on the second and third 160 MHz portions of the 480 MHz bandwidth and multiply the second and third 160 MHz portions by an additional coefficient. For example, the UHR STF sequence can be generated by [160HES a 160HES b 160HES} is given. For 1x UHR STF, 160HES = {M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M} and for 2x UHR STF, 160HES = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M} where M = {-1, -1, -1, +1, +1, +1, -1, +1, +1, +1, -1, +1, +1, -1, +1}. As in 802.11ax / be, the candidates for a, b, c, d, and e are 1 and -1, which can be optimized by considering the minimax method for all RU and MRU combinations with and without puncturing. For example, for 1x UHR STF of 480MHz PPDU, UHRS -3056:16:3056 = {M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M a (0 M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M) b (0 M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M)} (1+j) / sqrt(2), where UHRS -3064 = UHRS -2040 = UHRS -1032 = UHRS -1016 = UHRS -8 = UHRS8= UHRS 1016 = UHRS 1032 = UHRS 2040 = UHRS 3064 = 0. For 2x UHR STF of 480MHz PPDU, UHRS -3064:8:3064 = {M-1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M a (0M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M) b (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M)} (1 + j) / sqrt(2).

[0151] Similarly, for a 640MHz PPDU, in a first aspect, to generate a UHR STF sequence, the wireless communication device 602-a can repeat a lx or 2x 80MHz High Efficiency STF sequence (80HES) on the second, third, fourth, fifth, sixth, seventh, and eighth 80MHz portions of the 640MHz bandwidth and multiply the second, third, fourth, fifth, sixth, seventh, and eighth 80MHz portions by additional coefficients. For example, the UHR STF sequence can be given by [80HES a 80HES b 80HES c 80HES d 80HES e 80HES f 80HES g 80HES]. For a lx UHR STF, 80HES = {M 1 -M 0 -M 1 -M} and for a 2x UHR STF, 80HES = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M}, where M {-1, -1, -1, +1, +1, +1, -1, +1, +1, +1, -1, +1, +1, -1, +1}. As in 802.11ax or 802.11be, the candidates for a, b, c, d, and e are 1 and -1, which can be optimized by a minimax approach considering all RU and MRU combinations with and without puncturing. For example, for a lx UHR STF of a 640MHz PPDU, the UHR STF sequence can be given by -4080:16:4080 = {M 1 -M 0 -M 1-M a (0 M 1 -M 0 -M 1 -M) b (0 M 1 -M 0 -M 1 -M) c (0 M 1 -M 0 -M 1 -M) d (0M 1 -M 0 -M 1 -M) e (0 M 1 -M 0 -M 1 -M) f (0 M 1 -M 0 -M 1 -M) g (0 M 1 -M 0-M 1 -M)} (1 + j) / sqrt(2), where UHRS -4088 = UHRS -3064 = UHRS -2040 = UHRS -1032 = UHRS -1016 = UHRS -8 = UHRS8= UHRS 1016 = UHRS 1032 = UHRS 2040 = UHRS 3064 = UHRS 4088 = 0. For a 2x UHR STF of a 480 MHz PPDU, UHRS -4088:8:4088 = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M a (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) b (0 M -1 M -1 -M -1 M 0 -M 1 M1 -M 1 -M) c (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) d (0 M -1 M -1 -M -1 M0 -M 1 M 1 -M 1 -M) e (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M) f (0 M -1 M -1-M -1 M 0 -M 1 M 1 -M 1 -M) g (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M)} (1 + j) / sqrt(2).

[0152] For a 640 MHz PPDU, in a second aspect, to generate a UHR STF sequence, the wireless communication device 602-a can repeat a 1x or 2x 160 MHz sequence (160HES) on the second, third, and fourth 160 MHz portions of the 640 MHz bandwidth and multiply the second, third, and fourth 160 MHz portions by an additional coefficient. For example, the UHR STF sequence can be given by [160HES a 160HES b 160HES c 160HES = {M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M 0 -M 1 M 1 -M 1 -M} for 1x UHR STF, and 160HES = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M} for 2x UHR STF, where M = {-1, -1, -1, +1, +1, +1, -1, +1, +1, +1, -1, +1, +1, -1, +1}. As in 802.11ax or 802.11be, the candidates for a, b, c, d, and e are 1 and -1, which can be optimized by considering the minimax method for all RU and MRU combinations with and without puncturing. For example, for 1x UHR STF of 640MHz PPDU, UHRS -4080:16:4080 = {M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M a (0 M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M) b (0 M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M) c (0 M 1 -M 0 -M 1 -M 0 -M -1 M 0 -M 1 -M)} (1+j) / sqrt(2), where UHRS-4088 = UHRS-3064 = UHRS-2040 = UHRS-1032 = UHRS-1016 = UHRS-8 = UHRS8= UHRS1016 = UHRS1032 = UHRS2040 = UHRS3064 = UHRS4088= 0. For 2x UHR STF of 480MHz PPDU, UHRS -4088:8:4088 = {M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M a (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M) b (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M) c (0 M -1 M -1 -M -1 M 0 -M 1 M 1 -M 1 -M 0 -M 1 -M 1 M 1 -M 0 -M 1 M 1 -M 1 -M) c (1 + j) / sqrt(2).

[0153] The wireless communication device 602-a can transmit the UHR LTF sequence in the preamble 608, which the wireless communication device 602-b can use for channel estimation for the PPDU 606. 802.11bn can support 1x, 2x, and 4x UHR LTF sequences. 802.11bn can reuse the 1x, 2x, and 4x EHT LTF sequences for 1x, 2x, and 4x UHR LTF sequences of 20MHz, 40MHz, 80MHz, 160MHz, 320MHz PPDUs.

[0154] In some aspects, the wireless communication device 602-a can generate a 1x UHR LTF sequence for a 480MHz PPDU or a 640MHz PPDU by repeating an 802.11ax 80MHz LTF sequence and applying coefficient values to a first portion to a second portion of the 80MHz LTF. For example, a 1x UHR LTF sequence for a 480MHz PPDU can be given by UHR LTF 480MHz_1x = {LTF 80MHz_lower1_1x ,0 23 , LTF 80MHz_upper1_1x , 0 23 , LTF 80MHz_lower2_1x , 0 23 , LTF 80MHz_upper2_1x , 0 23 , LTF 80MHz_lower3_1x ,0 23 , LTF 80MHz_upper3_1x} where: LTF 80MHz_lower1_1x = {s(1) LTF 80MHz_left_1x , 0, s(2) LTF 80MHz_right_1x} ; LTF 80MHz_upper1_1x = {s(3) LTF 80MHz_left_1x , 0, s(4) LTF 80MHz_right_1x} ; LTF 80MHz_lower2_1x = {s(5) LTF 80MHz_left_1x , 0, s(6) LTF 80MHz_right_1x};LTF 80MHz_upper2_1x = {s(7) LTF 80MHz_left_1x , 0, s(8) LTF 80MHz_right_1x};LTF 80MHz_lower3_1x = {s(9) LTF 80MHz_left_1x ,0, s(10) LTF 80MHz_right_1x}; and LTF 80MHz_upper3_1x = {s(11) LTF 80MHz_left_1x , 0, s(12) LTF 80MHz_right_1x}. LTF 80MHz_left_1x and LTF 80MHz_right_1x As defined in the 802.11ax specification. The values ​​of s(1) to s(12) can be optimized by minimizing the worst PAPR evaluation of multi-flow under all RU and MRU combinations in both punched and non-punched cases. As another example, the 1×UHR LTF sequence of a 640MHz PPDU can be obtained from UHRLTF. 640MHz_1x ={LTF 80MHz_lower1_1x , 0 23 , LTF 80MHz_upper1_1x , 0 23 , LTF 80MHz_lower2_1x , 0 23 , LTF 80MHz_upper2_1x , 0 23 ,LTF 80MHz_lower3_1x , 0 23 , LTF 80MHz_upper3_1x , 0 23 , LTF 80MHz_lower4_1x , 0 23 , LTF 80MHz_upper4_1x} is given, where: LTF 80MHz_lower1_1x = {s(1) LTF 80MHz_left_1x , 0, s(2) LTF 80MHz_right_1x};LTF 80MHz_upper1_1x = {s(3) LTF 80MHz_left_1x , 0, s(4) LTF 80MHz_right_1x};LTF 80MHz_lower2_1x = {s(5) LTF80MHz_left_1x , 0, s(6) LTF 80MHz_right_1x};LTF 80MHz_upper2_1x = {s(7) LTF 80MHz_left_1x , 0, s(8) LTF 80MHz_right_1x};LTF 80MHz_lower3_1x = {s(9) LTF 80MHz_left_1x , 0, s(10) LTF 80MHz_right_1x};LTF 80MHz_upper3_1x = {s(11) LTF 80MHz_left_1x , 0, s(12) LTF 80MHz_right_1x};LTF 80MHz_lower4_1x ={s(13) LTF 80MHz_left_1x , 0, s(14) LTF 80MHz_right_1x}; and LTF 80MHz_upper4_1x = {s(15) LTF 80MHz_left_1x , 0, s(16) LTF 80MHz_right_1x The values ​​of s(1) to s(16) can be optimized by minimizing the worst PAPR evaluation for multi-flow scenarios, considering all combinations of RU and MRU in both punched and non-punched cases.

[0155] In some aspects, the wireless communication device 602-a can generate a 4×UHRLTF sequence of a 480MHz PPDU or a 640MHz PPDU by repeating the 802.11ax 80MHz LTF sequence and applying coefficient values ​​to the first and second parts of the 80MHz LTF. For example, the 4×UHR LTF sequence of a 480MHz PPDU can be generated from the UHRLTF sequence. 480MHz_4x = {LTF 80MHz_lower1_4x ,0 23 , LTF 80MHz_upper1_4x , 0 23 , LTF 80MHz_lower2_4x , 0 23 , LTF 80MHz_upper2_4x , 0 23 , LTF 80MHz_lower3_4x ,0 23 , LTF 80MHz_upper3_4x} is given, where: LTF 80MHz_lower1_4x = {n(1) LTF80MHz_subblock_left_4x , 05, n(2) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_upper1_4x = {n(3) LTF 80MHz_ subblock_ left_4x , 05, n(4) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_lower2_4x = {n(5) LTF 80MHz_ subblock_ left_4x , 05, n(6) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_upper2_4x = {n(7) LTF 80MHz_ subblock_ left_4x , 05, n(8) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_lower3_4x = {n(9) LTF 80MHz_ subblock_ left_4x , 05, n(10) LTF 80MHz_ subblock_ right_4x}; and LTF 80MHz_upper3_4x = {n(11) LTF 80MHz_ subblock_ left_4x , 05, n(12) LTF 80MHz_ subblock_ right_4x}. LTF 80MHz_ subblock_ left_4x and LTF 80MHz_ subblock_ right_4x As defined in the 802.11be specification. The values ​​of n(1) to n(12) can be optimized by minimizing the worst PAPR evaluation of the multi-flow under all RU and MRU combinations in both punched and non-punched cases. As another example, the 4×UHR LTF sequence of a 640MHz PPDU can be obtained from UHRLTF. 640MHz_4x = {LTF 80MHz_lower1_4x , 0 23 , LTF 80MHz_upper1_4x , 0 23 ,LTF 80MHz_lower2_4x , 0 23 , LTF 80MHz_upper2_4x , 0 23 , LTF 80MHz_lower3_4x , 0 23 , LTF 80MHz_upper3_4x , 0 23 ,LTF 80MHz_lower4_4x , 0 23 , LTF 80MHz_upper4_4x} is given, where: LTF 80MHz_lower1_4x = {n(1) LTF 80MHz_subblock_left_4x, 05, n(2) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_upper1_4x = {n(3) LTF 80MHz_ subblock_ left_4x , 05, n(4) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_lower2_4x = {n(5) LTF 80MHz_ subblock_ left_4x , 05, n(6) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_upper2_4x = {n(7) LTF 80MHz_ subblock_ left_4x , 05, n(8) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_lower3_4x = {n(9) LTF 80MHz_ subblock_ left_4x , 05, n(10) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_upper3_4x = {n(11) LTF 80MHz_ subblock_ left_4x , 05, n(12) LTF 80MHz_ subblock_ right_4x};LTF 80MHz_lower4_4x = {n(13) LTF 80MHz_ subblock_ left_4x , 05, n(14) LTF 80MHz_ subblock_ right_4x}; and LTF 80MHz_upper4_4x = {n(15) LTF 80MHz_ subblock_ left_4x , 05, n(16) LTF 80MHz_ subblock_ right_4x}. LTF 80MHz_ subblock_ left_4x and LTF 80MHz_ subblock_ right_4x As defined in the 802.11be specification. The values ​​of n(1) to n(16) can be optimized by minimizing the worst PAPR evaluation of multi-flow under all RU and MRU combinations in all punched and non-punched cases.

[0156] In some respects, the wireless communication device 602-a can generate a 2×UHRLTF sequence of a 480MHz PPDU or a 640MHz PPDU by repeating the 802.11ax 80MHz LTF sequence and applying coefficient values ​​to the first to fourth parts of the 80MHz LTF. For example, the 2×UHR LTF sequence of a 480MHz PPDU can be generated from the UHRLTF sequence. 480MHz_2x = {LTF80MHz_lower1_2x ,0 23 , LTF 80MHz_upper1_2x , 0 23 , LTF 80MHz_lower2_2x , 0 23 , LTF 80MHz_upper2_2x , 0 23 , LTF 80MHz_lower3_2x ,0 23 , LTF 80MHz_upper3_2x} given by LTF 80MHz_lower1_2x = {c(1) LTF 80_2x (1:245), c(2) LTF 80_2x (246:500), 0, c(3) LTF 80_2x (502:756), c(4) LTF 80_2x (757:1001)}; LTF 80MHz_upper1_2x = {c(5) LTF 80_2x (1:245), c(6) LTF 80_2x (246:500), 0, c(7) LTF 80_2x (502:756), c(8) LTF 80_2x (757:1001)}; LTF 80MHz_lower2_2x = {c(9) LTF 80_2x (1:245), c(10) LTF 80_2x (246:500), 0, c(11) LTF 80_2x (502:756), c(12) LTF 80_2x (757:1001)}; LTF 80MHz_upper2_2x = {c(13) LTF 80_2x (1:245), c(14) LTF 80_2x (246:500), 0, c(15) LTF 80_2x (502:756), c(16) LTF 80_2x (757:1001)}; LTF 80MHz_lower3_2x= {c(17) LTF 80_2x (1:245), c(18) LTF 80_2x (246:500), 0, c(19) LTF 80_2x (502:756), c(20) LTF 80_2x (757:1001)}; and LTF 80MHz_upper3_2x = {c(21) LTF 80_2x (1:245), c(22) LTF 80_2x (246:500), 0, c(23) LTF 80_2x (502:756), c(24) LTF 80_2x (757:1001)}. LTF 80MHz_ 2x may be as defined in the 802.11be specification. The values of c(l) through c(24) can be optimized by minimizing the worst PAPR evaluation of the multiple streams considering all RU and MRU combinations in all punctured and non-punctured cases. As another example, a 2x UHR LTF sequence for a 640 MHz PPDU can be given by UHR LTF 480MHz_2x = {LTF 80MHz_lower1_2x , 0 23 , LTF 80MHz_upper1_2x , 0 23 , LTF 80MHz_lower2_2x , 0 23 , LTF 80MHz_upper2_2x , 0 23 , LTF 80MHz_lower3_2x , 0 23 , LTF 80MHz_upper3_2x , 0 23 , LTF 80MHz_lower4_2x , 0 23 , LTF 80MHz_upper4_2x}, where: LTF 80MHz_lower1_2x = {c(l) LTF 80_2x (1:245), c(2) LTF 80_2x (246:500), 0, c(3) LTF 80_2x (502:756), c(4) LTF 80_2x (757:1001)}. LTF80MHz_upper1_2x = {c(5) LTF 80_2x (1:245),c(6) LTF 80_2x (246:500), 0, c(7) LTF 80_2x (502:756), c(8) LTF 80_2x (757:1001)}; LTF 80MHz_lower2_2x = {c(9) LTF 80_2x (1:245), c(10) LTF 80_2x (246:500), 0, c(11) LTF 80_2x (502:756), c(12) LTF 80_2x (757:1001)}; LTF 80MHz_upper2_2x = {c(13) LTF 80_2x (1:245), c(14) LTF 80_2x (246:500), 0, c(15) LTF 80_2x (502:756), c(16) LTF 80_2x (757:1001)}; LTF 80MHz_lower3_2x = {c(17) LTF 80_2x (1:245), c(18) LTF 80_2x (246:500), 0, c(19) LTF 80_2x (502:756), c(20) LTF 80_2x (757:1001)}; LTF 80MHz_upper3_2x = {c(21) LTF 80_2x (1:245), c(22) LTF 80_2x (246:500), 0, c(23) LTF 80_2x (502:756), c(24) LTF 80_2x (757:1001)}; LTF80MHz_lower4_2x = {c(25) LTF 80_2x (1:245), c(26) LTF 80_2x (246:500), 0, c(27) LTF 80_2x (502:756), c(28) LTF 80_2x (757:1001)}; and LTF 80MHz_upper4_2x = {c(29) LTF 80_2x (1:245), c(30) LTF 80_2x (246:500), 0, c(31) LTF 80_2x (502:756), c(32) LTF 80_2x (757:1001)}. LTF 80MHz_ 2x may be as defined in the 802.11be specification. The values of c(l) through c(32) can be optimized by minimizing the worst PAPR evaluation of the multi-streams considering all RU and MRU combinations in all punctured and non-punctured cases.

[0157] Wireless communication device 602-a can transmit a pilot sequence in preamble 608, which wireless communication device 602-b can use for phase tracking. In some aspects, the pilot index for 26, 52, 106, 242, or 484 tone RUs in OFDMA or non-OFDMA 480 MHz UHR PPDUs can be in each 160 MHz portion of the 480 MHz bandwidth. For example, the pilot index in a 480 MHz PPDU can be: [pilot index in a 160 MHz PPDU] - 2048, [pilot index in a 160 MHz PPDU], [pilot index in a 160 MHz PPDU] + 2048. For example, -468 can be one of the pilot indices for 26, 52, 106, 242, or 484 tone RUs in a 160 MHz PPDU, and thus the corresponding pilot index in a 480 MHz PPDU is -468 - 2048 = 2516 in the lowest 160 MHz, -468 in the middle 160 MHz, and -468 + 2048 = 1580 in the highest 160 MHz. In some aspects, the pilot index for 26, 52, 106, 242, or 484 tone RUs in OFDMA or non-OFDMA 640 MHz UHR PPDUs can be in each 320 MHz portion of the 640 MHz bandwidth. For example, the pilot index in a 640 MHz PPDU can be: [pilot index in a 320 MHz PPDU] - 2048, [pilot index in a 320 MHz PPDU] + 2048. For example, -468 can be one of the pilot indices for 26, 52, 106, 242, or 484 tone RUs in a 320 MHz PPDU, and thus the corresponding pilot index in a 640 MHz PPDU is -468 - 2048 = -2516 in the lowest 320 MHz, and 468 + 2048 = 1580 in the highest 320 MHz.

[0158] Assuming in OFDM or non-OFDMA 80MHz EHT PPDU, pilot indices for 996-tone RU: P996 = {-468, -400, -334, -266, -220, -152, -86, -18, 18, 86, 152, 220, 266, 334, 400, 468}, for n x 996-tone RU (n > 1) with tone plan, a 480MHz PPDU can have the following pilot indices: pilot indices for 996-tone RU: {P996 -2560}, {P996 -1536}, {P996 -512}, {P996 + 512}, {P996 + 1536}, {P996+2560}; pilot indices for 2 x 996-tone RU: {P996 -2560, P996 -1536}, {P996 -512, P996+512}, {P996 + 1536, P996 + 2560}; pilot indices for 3 x 996-tone RU: {P996 -2560, P996 -1536, P996 -512}, {P996 + 512, P996 + 1536, P996+2560}; or pilot indices for 6 x 996-tone RU: {P996 -2560, P996 -1536, P996 -512, P996 + 512, P996 + 1536, P996+2560}.And for tone plans with n x 996 RU (n > 1), a 640 MHz PPDU can have the following pilot indices: 996 tone RU pilot indices: {P996-3584}, {P996-2560}, {P996-1536}, {P996-512}, {P996+512}, {P996+1536}, {P996+2560}, {P996+3584}; 2 x 996 tone RU pilot indices: {P996-3584, P996-2560}, {P996-1536, P996-512}, {P996+512, P996+1536}, {P996+2560, P996+3584}; 4 x 996 tone RU pilot indices: {P996-3584, P996-2560, P996-1536, P996-512}, {P996+512, P996+1536, P996+2560, P996+3584}; or 8 x 996 tone RU pilot indices: {P996-3584, P996-2560, P996-1536, P996-512, P996+512, P996+1536, P996+2560, P996+3584}.

[0159] The pilot subcarriers for each new MRU (due to the additional bandwidth in 480 MHz or 640 MHz PPDUs) can include the pilot subcarriers of each component RU. In some aspects, as in 802.11be, the pilot values can vary symbol by symbol for each RU or MRU on the pilot tones in the data segment.

[0160] In some aspects, for a 480 MHz PPDU or a 640 MHz PPDU, for all sizes of RUs or MRUs under a 4 x 996-tone RU, the pilot mapping and values of 802.11be can be used. In some aspects, for a 480 MHz PPDU or a 640 MHz PPDU, for a 5 x 996-tone RU, the pilot mapping and values of a 996-tone RU can be duplicated five times (once in each component 996-tone RU within the 5 x 996-tone RU). In some aspects, for a 480 MHz PPDU or a 640 MHz PPDU, for a 6 x 996-tone RU, the pilot mapping and values of a 3 x 996-tone RU can be duplicated. In some aspects, for a 640 MHz PPDU, for a 7 x 996-tone RU, the pilot mapping and values of a 996-tone RU can be duplicated seven times (once in each component 996-tone RU within the 7 x 996-tone RU). In some aspects, for a 640 MHz PPDU, for an 8 x 996-tone RU, the pilot mapping and values of a 4 x 996-tone RU can be duplicated. The pilot mapping and values of new MRUs can follow the pilot mapping and values of each component RU for a 480 MHz PPDU or a 640 MHz PPDU.

[0161] Wireless communication device 602-a can generate PPDU 606 using a segment parser, and wireless communication device 602-b can deparse PPDU using a segment deparser. The segment parser maps a transmission to frequency segments before interleaving. For a 480 MHz PPDU, the 802.11be segment parser can be extended to cover new RUs or MRUs with parameters for the proportional cycling scheme shown in Table 7, where s = max(l, N BPSCS / 2). Similarly, for a 640 MHz PPDU, the 802.11be segment parser can be extended to cover new RUs or MRUs with parameters for the proportional cycling scheme shown in Table 8, where s = max(l, N BPSCS / 2).

[0162] Table 7

[0163] Table 8

[0164] The wireless communication device 602-a can apply a phase rotation to the transmission of the legacy portion of the preamble 608 of the PPDU 606 (e.g., the legacy portion of the preamble can include the pre-UHR modulated portion of the preamble 608, which can include the L-STF, L-LTF, L-SIG, RL-SIG, U-SIGN, and UHR-SIG). For example, the legacy portion of the preamble can be any portion of the preamble prior to the UHR-STF. For 480 MHz PPDUs, similar to 320 MHz PPDUs, the phase rotation pattern for 480 MHz is shown in Equation 1, where is an implementation dependent per 80 MHz frequency sub-block rotation coefficient with values of +1 and -1. Similarly, for 640 MHz PPDUs, the phase rotation pattern for 640 MHz is shown in Equation 1, where is an implementation dependent per 80 MHz frequency sub-block rotation coefficient with values of +1 and -1.

[0165]

[0166] In EHT, 80 MHz, 160 MHz, and 320 MHz PPDUs support an EHT duplicate (DUP) mode. The EHT DUP mode can be used in conjunction with binary phase shift keying (BPSK) double carrier modulation (DCM), rate ½ low density parity check decoding, and Nss = 1. For a 480 MHz MU PPDU transmitted in DUP mode, the lower frequency 3 x 996 tone RU can be encoded and modulated, and the lower 3 x 996 tone RU can be duplicated to the higher 3 x 996 tone RU along with a phase rotation (e.g., a partial symbol change) to reduce the PAPR. The DCM operation for the 3 x 996 tone RU can be the same as the DCM operation for the 3 x 996 tone RU described in EHT. For example, the phase rotation can be one phase rotation for every 40 MHz (half of the 996 tone RU) (e.g., corresponding to [1 1 1 1 1 -1 -1 -1 1 1 1]). As another example, the phase rotation can be one phase rotation for every 80 MHz (996 tone RU) (e.g., corresponding to [1 1 1 -1 -1 1] or [1 1 1 -1 1 1]) for six 80 MHz frequency sub-blocks in a 480 MHz bandwidth. For a 640 MHz MUP PDU transmitted in DUP mode, the lower frequency 4 x 996 tone RU can be encoded and modulated, and the lower 4 x 996 tone RU can be copied to the higher 4 x 996 tone RU with a phase rotation (e.g., a partial symbol change) to reduce PAPR. The DCM operation for the 4 x 996 tone RU can be the same as the DCM operation described in EHT for the 4 x 996 tone RU. For example, the phase rotation can be one phase rotation for each 80 MHz (or 996 tone RU) (e.g., corresponding to [1 1 1 1 -1 -1 1 1]).

[0167] The wireless communication device 602-a can apply a transmit mask (also referred to as a spectral mask) to the transmission of the PPDU 606. For a 480 MHz transmit mask, Table 9 shows a transmit mask that can be applied to the transmission of the PPDU 606. For a 640 MHz transmit mask, Table 10 shows a transmit mask that can be applied to the transmission of the PPDU 606.

[0168] Table 9

[0169] Table 10

[0170] FIG. 7 An example of a channelization diagram 700 that supports techniques for 480 MHz and 640 MHz channel bandwidth transmissions in Wi-Fi is shown. The channelization diagram 700 can implement, or be implemented by, aspects of the wireless communication network 100 or the signaling diagram 600.

[0171] In UHR wireless communication systems, some STAs 104 can be restricted to 160 MHz operation, some STAs 104 can be restricted to 320 MHz operation, and some STAs 104 can be capable of 480 MHz and / or 640 MHz operation. Channel utility can depend on channel operation. UHR can use 480 MHz channel bandwidth depending on STAs 104 capable of using 480 MHz operation. A 320 MHz EHT STA 104 can be declared to 320 MHz channel bandwidth, which is treated as an EHT 320 MHz channel (E320) by the EHT STA 104. As shown in the first example channelization diagram 705 and the second example channelization diagram 710, E320 can include a primary 160 MHz sub-band (P160) and a secondary 160 MHz sub-band (S160). As shown in the first example channelization diagram 705 and the second example channelization diagram 710, a 480 MHz contiguous channel bandwidth can be a 320 MHz channel bandwidth (E320) with an additional second or third 160 MHz sub-band (e.g., T160).

[0172] As shown in the first example channelization diagram 705, in some examples, the primary 160 MHz sub-band can be any of the 160 MHz sub-bands of the 480 MHz channel. In such examples, STAs 104 that are not capable of 480 MHz operation can perform up to 320 MHz of channel bandwidth transmission or reception in E320 (e.g., 320-X). If some of the S160 within E320 are not available (e.g., 160-b), the STAs 104 can fall back to 160 MHz channel bandwidth transmission or reception in P160.

[0173] As shown in the second example channelization diagram 710, in some examples, the primary 160 MHz sub-band can always be the center 160 sub-band of the 480 MHz channel. In such examples, two different 320 MHz channels can be formed within the 480 MHz channel, namely 320-X and 320-Y, as shown in the second example channelization diagram 710. 320 MHz restricted STAs 104 can be divided into two groups, with some transmitting or receiving in 320-X and some transmitting or receiving in 320-Y. In the scenario shown in the second example channelization diagram 710, there can be more opportunities for 480 MHz channel bandwidth OFDMA transmission or reception as compared to the scenario shown in the first example channelization diagram 705.

[0174] In scenarios where the primary 160 MHz sub-band is always the center 160 sub-band, there can be multiple options for determining which 320 MHz channel (e.g., 320-X or 320-Y) to use for 320 MHz limited STAs 104. In a first option, the AP 102 can assign each 320 MHz limited non-AP STA 104 to one of the 320 MHz channels (e.g., 320-X or 320-Y) at association. This assignment can be static, or semi-static if the AP 102 reassigns the 320 MHz channel after a period of time. In a second option, the non-AP STAs 104 can semi-statically inform the AP 102 of the working 320 MHz channel for the non-AP STAs 104, and the AP 102 can provide the non-AP STAs 104 with a suggested 320 MHz channel. In downlink and uplink transmissions, the AP 102 can assign RUs or MRUs to the 320 MHz limited non-AP STAs 104 within the assigned 320 MHz channel.

[0175] In P2P communications, where both BSS-internal non-AP STAs 104 are 320 MHz restricted, and P2P signaling passes through the AP 102 in 802.11 TDLS, there can be multiple options for determining which 320 MHz channel (e.g., 320-X or 320-Y) to use for the 320 MHz restricted STAs 104 when the primary 160 MHz subband is always the center 160 subband. In a first option (e.g., static or semi-static blind option), each 320 MHz restricted non-AP STA 104 is not aware of the 320 MHz channel assigned to the other STA 104. In the first option, P2P transmissions can utilize P160. The first option can be easy to implement, but can limit peak throughput because the channel bandwidth is limited to 160 MHz for P2P transmissions. In a second option (e.g., static or semi-static non-blind option), in an initial transmission utilizing P160, a first 320 MHz restricted non-AP STA 104 can inform a second STA 104 of the operating 320 MHz channel of the first 320 MHz restricted non-AP STA 104. If the second non-AP STA 104 operates in the same indicated 320 MHz channel as the first 320 MHz restricted non-AP STA 104, the second 320 MHz restricted non-AP STA 104 can use the indicated 320 MHz channel for the next transmission with the first 320 MHz restricted non-AP STA 104, otherwise the second 320 MHz restricted non-AP STA 104 can use P160 for the next transmission with the first 320 MHz restricted non-AP STA 104. A PPDU with 160 MHz channel bandwidth can indicate the PPDU bandwidth (160 MHz) in the U-SIG, and can also indicate the 320 MHz operating channel of the STA 104 (e.g., via 1 bit in the U-SIG). The second option can enable P2P communications to use 320 MHz, increasing peak throughput compared to the first option. In a third option (e.g., dynamic non-blind option), if the first and second non-AP STAs 104 operate in different 320 MHz channels, one of them can move to the other 320 MHz channel so that P2P communications can use 320 MHz channel bandwidth. In some examples, if the AP 102 determines the operating 320 MHz channels of the first and second non-AP STAs 104, the AP 102 can reassign the operating 320 MHz channel of one of the first and second non-AP STAs 104 so that the first and second non-AP STAs 104 operate in the same 320 MHz channel.In some examples, if the first non-AP STA 104 determines the operating 320 MHz channel of the second non-AP STA 104 after the signal exchange, the first non-AP STA 104 can determine to switch to the 320 MHz channel of the second non-AP STA 104 so as to use the same 320 MHz channel, thereby enabling 320 MHz P2P communication. The third option can enable P2P communication to use 320 MHz even when the non-AP STAs 104 are assigned to different 320 MHz channels, thereby increasing peak throughput.

[0176] As referenced above FIG. 6As described, the preamble 608 of the PPDU 606 can include a bandwidth field and a bandwidth extension field in the U-SIG field that jointly (e.g., combined together) indicate the channel bandwidth of the PPDU 606. In some examples, the bandwidth field and the bandwidth extension field can indicate a 480 MHz channel as a 320 MHz channel with an additional 160 MHz sub-band (e.g., referred to as a “320+160” option). In the “320+160” option, the bandwidth field and the bandwidth extension field can have relative and different indications in the different 160 MHz sub-bands of the 480 MHz channel bandwidth. For example, as shown in the second example channelization diagram 710, the two combinations of 320 MHz + 160 MHz can uniquely determine one 480 MHz channel (e.g., 320-X plus U160 or 320-Y plus L160). In each 160 MHz sub-band, the bandwidth field can indicate a nominal 320 MHz channelization that overlaps the 160 MHz sub-band (e.g., 320 MHz-1 or 320 MHz-2), and the two bits of the bandwidth extension field can indicate the presence and location of the additional 160 MHz to form the 480 MHz PPDU channel bandwidth. For example, one of the two bits of the bandwidth extension field can indicate whether the channel bandwidth is 320 MHz or 480 MHz (e.g., a “320 / 480” indication bit), and if the channel bandwidth is 480 MHz, one of the two bits of the bandwidth extension field can indicate whether the 160 MHz is the immediate 160 MHz lower or higher in frequency relative to the nominal 320 MHz channel (e.g., a “U160 / L160” indication bit, where “U160” refers to a 160 MHz frequency block that is higher than the nominal 320 MHz channel, and “L160” refers to a 160 MHz frequency block that is lower than the nominal 320 MHz channel). The UHR STAs 104 can understand the 480 MHz signaling indicated by the bandwidth field and the bandwidth extension field, and the EHT STAs 104 can interpret the signaling indicated by the bandwidth field as a 320 MHz channel bandwidth and treat the bandwidth extension field as ignored. As described herein and shown in Table 11, the signaling in the bandwidth field and the bandwidth extension field is different for the 160-A sub-band and the 160-C sub-band. The signaling in the bandwidth field and the bandwidth extension field for the 160-B sub-band can depend on what is to be shown to the EHT STAs 104. The “320+160” option can leave at least one reserved value in the bandwidth field, and the EHT STAs 104 can recognize the 320 MHz channel as indicated in the bandwidth field. The “320+160” option can be used for channel operation related signaling.

[0177] In some examples, the bandwidth field and the bandwidth extension field can indicate a 480 MHz channel bandwidth as a 160 MHz channel bandwidth with an additional 320 MHz channel bandwidth (e.g., referred to as a “which 160” option). In the “which 160” option, the value of the bandwidth field can be the same (e.g., uniform) in each 160 MHz sub-band (e.g., 160-A, 160-B, and 160-C), and the value of the two-bit bandwidth extension field can be relative and different in each 160 MHz sub-band. For example, the bandwidth field can indicate a 160 MHz channel bandwidth, and the two-bit bandwidth extension field can indicate “only 160 MHz” (which means the PPDU is a 160 MHz PPDU instead of a 480 MHz PPDU), “lowest 160 MHz in 480 MHz,” “middle 160 MHz in 480 MHz,” or “highest 160 MHz in 480 MHz.” The UHR STAs 104 can understand the 480 MHz signaling indicated by the bandwidth field and the bandwidth extension field, and the EHT STAs 104 can interpret the signaling indicated by the bandwidth field as a 160 MHz channel bandwidth and treat the bandwidth extension field as ignored.

[0178] Table 11

[0179] In some examples, in a 20, 40, 80, or 160 MHz PPDU, when the “uplink / downlink” bit is set to 0 (to indicate a transmission not addressed to the AP 102) and the PPDU indicates a transmission to a single STA (e.g., the PPDU type and compression mode field are set to 1, and the EHT-SIG MCS field and the number of EHT-SIG symbols field are not both set to 0), the PPDU is a transmission addressed to a single non-AP STA 104. In such examples, the bandwidth field can indicate the PPDU channel bandwidth, and the bandwidth extension field can indicate the operating 320 MHz channel (e.g., 320 MHz-1 and 320 MHz-2, with unused values set to validation). If the transmitter device of the PPDU is a 480 MHz capable AP 102 or non-AP STA 104, the bandwidth extension field can be set to the operating 320 MHz channel of the receiver non-AP STA 104 (if the receiver non-AP STA 104 is 320 MHz limited). If the transmitter device of the PPDU is a 320 MHz limited AP 102 or non-AP STA 104, the bandwidth extension field can be set to the operating 320 MHz channel of the transmitter non-AP STA 104.

[0180] In some examples, as referenced to FIG. 6, the bandwidth field and the bandwidth extension field can indicate a 480 MHz channel bandwidth as a 160 MHz channel bandwidth with an additional 320 MHz channel bandwidth (e.g., referred to as a “which 160” option). In the “which 160” option, the value of the bandwidth field can be the same (e.g., uniform) in each 160 MHz sub-band (e.g., 160-A, 160-B, and 160-C), and the value of the two-bit bandwidth extension field can be relative and different in each 160 MHz sub-band. For example, the bandwidth field can indicate a 160 MHz channel bandwidth, and the two-bit bandwidth extension field can indicate “only 160 MHz” (which means the PPDU is a 160 MHz PPDU instead of a 480 MHz PPDU), “lowest 160 MHz in 480 MHz,” “middle 160 MHz in 480 MHz,” or “highest 160 MHz in 480 MHz.” The UHR STAs 104 can understand the 480 MHz signaling indicated by the bandwidth field and the bandwidth extension field, and the EHT STAs 104 can interpret the signaling indicated by the bandwidth field as a 160 MHz channel bandwidth and treat the bandwidth extension field as ignored. FIG. 6As described, the U-SIG of the PPDU preamble 608 may include a spatial reuse field. As shown in Table 12 below, in some examples, the spatial reuse field design may be EHT-like and may include two spatial reuse fields. In some examples, the spatial reuse field design may depend on the PPDU channel bandwidth signaling method (e.g., an indication as per reference). FIG. 6 The described 480MHz channelization (referred to as "480-X"), "320+160" option, or "which 160" option. In such examples, more space reuse fields can be used (e.g., more than two fields). As shown in Table 12, each space reuse field can indicate space reuse information for different bandwidth portions in different design options. In the "which 160" option, "remaining 320MHz" refers to the remaining total bandwidth (320MHz) in the 480MHz range, excluding the bandwidth indicated in the bandwidth field (the indicated 160MHz).

[0181] Table 12

[0182] For reference FIG. 6 As described, preamble 608 may include an EHT-SIG indicating RU allocation (e.g., FIG. 3aThe preamble 608 can include a UHR-SIG including a RU allocation subfield. In some examples, the RU allocation subfield in the UHR-SIG can use an EHT design, which can include a 9-bit RU allocation subfield. In such examples, 1 + 8 = 9 values can be set to “validate,” 26 x 8 values can be set to ignore, and 50 values can be used to indicate RUs or MRUs whose size is less than 242-tone RUs. To add one new MRU, 8 values can be used to indicate 1 to 8 user fields, and thus the values set to ignore can be reused for up to 26 new MRUs, each with 1 to 8 user fields. A 480 MHz tone plan can be a replication of six 80 MHz EHT tone plans, one in each of the 80 MHz frequency sub-blocks. In some examples, MRUs with size < 2 x 996 can not span 160 MHz channel boundaries (e.g., as in EHT). In some examples, MRUs with size < 4 x 996 can not span 320 MHz channel boundaries (e.g., as in EHT). MRUs with size greater than or equal to 4 x 996 (33 MRUs total) can have a potential size of 4 x 996 MRU (3 MRUs if formed from 2 x 996 RUs), 4 x 996 + 484-tone MRU (12 MRUs if formed from two 2 x 996-tone RUs and one 484-tone RU), 5 x 996-tone MRU (6 MRUs), or 5 x 996 + 484-tone MRU (12 MRUs).

[0183] In an example where the RU allocation subfield in the UHR-SIG can use the EHT design, the UHR-SIG can reuse the EHT table and add new MRUs. Reusing the EHT table by adding new MRUs can enable EHT STAs 104 to understand how many user fields to skip for existing channel bandwidth signaling. Reusing the EHT table by adding new MRUs can result in high bit overhead (e.g., in each content channel, 9 x 12 = 108 bits can be used). In a channel bandwidth independent RU allocation subfield suboption, values set to ignore can be repurposed to add up to 26 new MRUs (e.g., 4 x 996-tone MRU (3 MRUs), 5 x 996-tone MRU (6 MRUs), 5 x 996 + 484-tone MRU (12 MRUs)). The bandwidth independent RU allocation subfield suboption can not support all new MRU sizes (e.g., 4 x 996 + 484-tone MRU or other new size MRUs). In a channel bandwidth dependent RU allocation subfield suboption, the EHT table can be used for existing channel bandwidths, and a 9-bit table can be redesigned for 480 MHz. Assuming the smallest RU size in 480 MHz OFDMA is 242-tone RU, 50 values for smaller RUs or MRUs of size < 242, and ignore and / or validation values can be repurposed for a total of 33 new MRUs described herein. A first option of reusing the EHT table can be used to multiplex EHT STAs 104 in 480 MHz transmissions (e.g., 320 MHz limited EHT STAs 104). Other RU allocation subfield options can be used that have less signaling overhead than the first option. Whether to use the first option of reusing the EHT table can accordingly involve a tradeoff between backward compatibility with EHT devices and lower signaling overhead.

[0184] A second UHR-SIG RU allocation subfield design option can be referred to as a compressed mode for 480 MHz. The compressed mode is described herein with respect to FIG. 8 A compressed mode for 480 MHz UHR-SIG RU allocation subfield design options is described.

[0185] A third UHR-SIG RU allocation subfield design option can be referred to as a per RU indication option. In some examples, there can be a small number of users in OFDMA. In such examples, the RU allocation table can not be used, and the RU assignment field in each user information field can be used. The user information field can be uniform for both MU-MIMO and non-MU-MIMO. In the per RU indication option, 9 additional bits can be used. 4 bits can be used to indicate the number of spatial streams (Nss), and 4 bits can be used to indicate the starting stream index of the user, where there is no explicit indication of the total Nss across different users if one RU or MRU is assigned for MU-MIMO transmission to multiple users. In some examples, up to 6 bits can be used to indicate up to 64 (M) RU assignments. Assuming the minimum RU size in 480 MHz OFDMA is a 242-tone RU, 6 bits can be used to indicate a 242-tone RU assignment (4 x 6 = 24 242-tone RUs in total in 480 MHz), a 484-tone RU assignment (2 x 6 = 12 484-tone RUs in total in 480 MHz), a 996-tone RU assignment (6 996-tone RUs in total in 480 MHz), a 2 x 996-tone RU assignment (3 2 x 996-tone RUs in total in 480 MHz), a 3 x 996-tone RU assignment (8 3 x 996-tone MRUs in total in 480 MHz), a 4 x 996-tone RU assignment (3 4 x 996-tone RUs in total in 480 MHz), or a 5 x 996-tone RU assignment (6 5 x 996-tone MRUs in total in 480 MHz). Thus, the additional 9 bits in the user information field is 4 (starting stream index) + 6 (RU assignment) - 1 (reserved bit) = 9 bits. If there are 24 users in OFDMA (e.g., 12 user information fields in each content channel due to parallelization), the per RU indication option can have the same signaling overhead as the UHR-SIG RU allocation subfield design option using a 9-bit table for each 20 MHz. If there are fewer than 24 users in OFDMA, the per RU indication option can reduce the signaling overhead compared to the UHR-SIG RU allocation subfield design option using a 9-bit table for each 20 MHz.

[0186] As described herein, in a UHR wireless communication system, UHR 480 MHz capable STAs 104, UHR 320 MHz limited STAs 104, EHT 320 MHz capable STAs, and EHT smaller channel bandwidth limited STAs can coexist. UHR 320 MHz limited STAs can be multiplexed into 480 MHz OFDMA transmissions. In some examples, EHT STAs can also be multiplexed into UHR 480 MHz OFDMA transmissions.

[0187] When EHT STAs are multiplexed into UHR 320MHz OFDMA transmissions, the PHY revision identifier can be set to “EHT” and the ignore bit in U-SIG can be set to indicate “UHR” (which can be uniform (across the entire channel bandwidth) or a sub-band variant (only in the 80MHz sub-band of the resident EHT STA 104)). When EHT STAs are multiplexed into UHR 320MHz OFDMA transmissions, the bandwidth field can be set to the existing channel bandwidth value (e.g., 320MHz-1), the UHR-SIG field structure and interpretation of the common and user-specific fields can be the same as for EHT-SIG for the PPDU channel bandwidth indicated in the bandwidth field, the RU allocation subfield can use the 9-bit EHT-compatible design for the existing channel bandwidth value, and the user info field can be the same size of 22 bits.

[0188] If EHT STAs 104 and UHR STAs 104 are able to reside on different 160MHz sub-bands through sub-channel selective transmission (SST), several potential methods can be used to serve both EHT and UHR STAs in different 160MHz sub-bands. One method can involve using a multi-generation frequency domain aggregated PPDU (FD-A-PPDU), where EHT STAs can be served in P160 and UHR STAs 104 can be served in the remaining 320MHz. In some cases, EHT STAs 104 and UHR STAs 104 can reside on the primary channel. To multiplex EHT STAs 104 in UHR 480MHz OFDMA transmissions, the UHR 480MHz PPDU can be disguised as an EHT 320MHz PPDU to the EHT STAs 104. In such examples, the 320+160 PPDU channel bandwidth signaling option can be used, and in the sub-band of the resident EHT STAs 104, E320 can be indicated in the bandwidth field (UHR STAs 104 can understand the additional 160MHz, but EHT STAs 104 do not). In such examples, the UHR-SIG field can be changed to inherit the EHT-SIG structure of 320MHz. In such examples, the RU allocation subfield in UHR-SIG can be understood using the EHT-compatible design for E320 of EHT STAs 104 described herein, and a channel bandwidth-independent or channel bandwidth-dependent RU allocation subfield design can be used in the remaining 160MHz for UHR STAs 104.

[0189] The UHR-SIG field can be designed accordingly as several options. In a first example (e.g., Option 1), the design of the UHR-SIG can be EHT-like. In the first example, the same structure of one common field followed by one user-specific field can be used. The detailed UHR-SIG field structure and size can depend on the RU allocation subfield design option. For example, assuming an EHT-compatible 9-bit RU allocation subfield per 20MHz, in each content channel, a 480MHz channel bandwidth uses a total of 12 RU allocation subfields, one per 20MHz. Thus, using 3 code blocks, one for the U-SIG overflow field and 2 RU allocation-A subfields, one for the 6 RU allocation-B subfields, and one for the 4 RU allocation-C subfields. An EHT STA 104 can not understand the 12 RU allocation subfields in the Option 1 design.

[0190] In a second example (e.g., Option 2), the design of the UHR-SIG can be EHT-compatible. The signaling can be split into 320MHz and 160MHz, and two sets of common and user-specific fields can be sequential. The first set of common and user-specific fields corresponds to EHT 320MHz (E320), and the second set of common and user fields corresponds to the remaining 160MHz subband. A channel bandwidth-independent RU allocation sub-option design can be used in E320, and a channel bandwidth-independent RU allocation sub-option design or a channel bandwidth-dependent RU allocation sub-option design can be used in the remaining 160MHz. The number of UHR-SIG symbols in the U-SIG can be set to the length of the entire UHR-SIG such that both EHT STAs 104 and UHR STAs 104 can correctly know the location of the UHR-STF. The second option carries the same information as the first option (if the same RU allocation subfield design option is used), but the fields are reordered such that the EHT-SIG structure for EHT 320MHz is inherited and can be understood by EHT STAs 104. For example, Table 13 shows an example structure of a 320MHz EHT-SIG field, Table 14 shows an example structure of a 480MHz UHR-SIG field according to Option 1, and Table 15 shows an example structure of a 480MHz UHR-SIG field according to Option 2. As shown in Table 15, the structure of the common and user-specific fields for the 320MHz subband of the 480MHz channel bandwidth is the same as the structure of the common and user-specific fields of the 320MHz EHT-SIG field as shown in Table 13. In Tables 13, 14, and 15, RUA refers to the RU allocation subfield for a given subchannel, and UI refers to the user information field for a given subchannel.

[0191] Table 13

[0192] Table 14

[0193] Table 15

[0194] For example, the U-SIG can indicate a PHY version identifier field (which can indicate EHT), a bandwidth field (which can indicate 320-X), a bandwidth extension field (which can indicate U160), and a number of UHR-SIG symbols (which can indicate the amount of UHR-SIG symbols). The common 320-X field can indicate RU allocation subfields for the 320-X channel, and the user-specific 320-X field can indicate UHR user information for the 320-X channel. The common U160 field can indicate RU allocation subfields for the remaining 160 MHz channel, and the user-specific field U160 can indicate UHR user information for the remaining 160 MHz channel. The EHT STA 104 can process the common and user-specific fields of E320 of the 480 MHz UHR-SIG field. Specifically, the EHT STA 104 can process the PHY version identifier field, the bandwidth field, and the number of UHR-SIG symbols field in the U-SIG, the RU allocation subfields in the common 320-X field, and the EHT user information in the user-specific 320-X field. In some aspects, with respect to the 480 MHz UHR-SIG field, the EHT STA 104 can process the common and user-specific fields of E320 of the 480 MHz UHR-SIG field. In some aspects, with respect to the 640 MHz UHR-SIG field, the EHT STA 104 can process the common and user-specific fields of E320 of the 640 MHz UHR-SIG field. FIG. 7 The designs described with reference to the 480 MHz PPDU can be applied to 640 MHz PPDUs.

[0195] FIG. 8 An example of a RU allocation diagram 800 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown. The RU allocation diagram 800 can implement aspects of the wireless communication network 100 or the signaling diagram 600, or can be implemented by those aspects.

[0196] As described herein, the second UHR-SIG RU allocation subfield design option can be referred to as a compressed mode for 480 MHz. In UHR, most bandwidth limited STAs 104 (e.g., 320 MHz limited STAs 104) can receive or transmit in the primary channel, and thus it can be efficient to maintain the current OFDMA (M) RU resolution of P160. Fewer STAs 104 can transmit or receive in the remaining 320 MHz, and thus can use larger OFDMA (M) RUs in the remaining 320 MHz. Thus, in the compressed mode for 480 MHz, the RU allocation signaling can be reordered to start from P160, followed by the remaining 320 MHz. A 9-bit EHT table can be reused for each 20 MHz in P160, and an 8-bit table can be used for each 80 MHz in the remaining 320 MHz, as shown in the first example RU allocation diagram 805, the second example RU allocation diagram 810, and the third example RU allocation diagram 815. In some examples, OFDMA (M) RUs inside and partially overlapping with the remaining 320 MHz can be limited to N x 996 in size, where N = 1, …, 5 (e.g., 996 tone RUs (1 such RU in one 80 MHz frequency sub-block), 2 x 996 tone RUs (1 such RU overlapping with one 80 MHz frequency sub-block), 3 x 996 tone MRUs (8 such MRUs overlapping with one 80 MHz frequency sub-block, with 4 in each contiguous 320 MHz), 4 x 996 tone RUs (2 such RUs overlapping with one 80 MHz frequency sub-block or simply using 3 values to indicate 3 total 4 x 996 RUs in 480 MHz), 5 x 996 tone MRUs (4 such MRUs overlapping with one 80 MHz frequency sub-block or simply using 6 values to indicate 6 total 5 x 996 tone MRUs in 480 MHz), punctured 996 tone RUs, and unassigned 996 tone RUs). In the compressed mode option for 480 MHz UHR-SIG RU allocation subfield design, each content channel can include 9 x 4 + 8 x 2 = 52 bits, which is less than the 320 MHz RU allocation signaling overhead.

[0197] The first example RU allocation diagram 805 illustrates a scenario in which P160 is the lowest 160 MHz sub-band of the 480 MHz channel bandwidth. The second example RU allocation diagram 810 illustrates a scenario in which P160 is the middle 160 MHz sub-band of the 480 MHz channel bandwidth. The third example RU allocation diagram 815 illustrates a scenario in which P160 is the highest 160 MHz sub-band of the 480 MHz channel bandwidth.

[0198] In some aspects, with respect to FIG. 8The design described with reference to 480 MHz PPDUs can be applied to 640 MHz PPDUs.

[0199] FIG. 9 An example of a process flow 900 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown. The process flow includes a first wireless communication device 602-c and a second wireless communication device 602-d, which can be examples of the wireless communication devices 602 as described herein. For example, the first wireless communication device 602-c can be an AP 102 or a STA 104 as described herein, and the second wireless communication device 602-d can be an AP 102 or a STA 104 as described herein. In the following description of the process flow 900, the operations between the first wireless communication device 602-c and the second wireless communication device 602-d can be transmitted in a different order than the example shown, or the operations performed by the first wireless communication device 602-c and the second wireless communication device 602-d can be performed in different orders or at different times. Some operations can also be omitted from the process flow 900, and other operations can be added to the process flow 900.

[0200] At 902, the first wireless communication device 602-c can transmit a preamble of a PPDU to the second wireless communication device 602-d. The preamble can include a U-SIG field, and the U-SIG field can include a bandwidth field and a bandwidth extension field that jointly (e.g., combined together) indicate a channel bandwidth of the PPDU. The indicated channel bandwidth can be one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0201] At 904, the first wireless communication device 602-c can transmit a payload of the PPDU to the second wireless communication device 602-d using the indicated channel bandwidth.

[0202] In some aspects, a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicates the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0203] In some aspects, within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, and within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, where the first value is different from the third value and the second value is different from the fourth value. For example, the bandwidth field and the extension field can indicate different values within different 160 MHz portions of a 480 MHz or 640 MHz channel bandwidth.

[0204] In some aspects, the first wireless communication device 602-c can transmit the preamble and the payload according to a tone plan. The tone plan can be one of: a set of multiple EHT 80 MHz tone plans across a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; a six 996-tone RU for a 480 MHz contiguous channel bandwidth; a 6 x 996-tone RU for a 480 MHz contiguous channel bandwidth; a 4 x 996-tone MRU for a 480 MHz contiguous channel bandwidth; a 4 x 996 + 484-tone MRU for a 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242-tone MRU for a 480 MHz contiguous channel bandwidth; a 5 x 996-tone MRU for a 480 MHz contiguous channel bandwidth; a 5 x 996 + 484-tone MRU for a 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242-tone MRU for a 480 MHz contiguous channel bandwidth; an 8 x 996-tone RU for a 640 MHz contiguous channel bandwidth; a 4 x 996-tone RU for a 640 MHz contiguous channel bandwidth; a 4 x 996 + 484-tone MRU for a 640 MHz contiguous channel bandwidth; a 5 x 996-tone MRU for a 640 MHz contiguous channel bandwidth; a 5 x 996 + 484-tone MRU for a 640 MHz contiguous channel bandwidth; a 6 x 996-tone MRU for a 640 MHz contiguous channel bandwidth; a 6 x 996 + 484-tone MRU for a 640 MHz contiguous channel bandwidth; a 7 x 996-tone MRU for a 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484-tone MRU for a 640 MHz contiguous channel bandwidth. In some aspects, the first wireless communication device 602-c can transmit a set of multiple pilot signals based on the tone plan. In some aspects, the first wireless communication device 602-c can generate the PPDU according to a segment parser, and the segment parser can be based on the tone plan. The second wireless communication device 602-d can parse the PPDU according to a segment parser based on the tone plan.

[0205] In some aspects, the first wireless communication device 602-c can transmit, in the preamble, an indication of a puncturing pattern of the PPDU. In some aspects, the PPDU is a non-OFDMA PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth. In some aspects, the PPDU is an OFDMA PPDU, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths for each 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0206] In some aspects, the U-SIG field in the TB PPDU includes a set of multiple spatial reuse fields that indicate spatial reuse information for each of a set of multiple 20 MHz portions of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0207] In some aspects, the preamble includes an EHT-SIG field that includes a RU allocation subfield, and a number of entries in the RU allocation subfield is based on the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0208] In some aspects, the preamble includes a UHR STF that includes a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, and each sequence in the set of multiple sequences is multiplied by a different coefficient.

[0209] In some aspects, the preamble includes a UHR LTF that includes a set of multiple sequences within an 80 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, each sequence in the set of multiple sequences includes multiple portions, and each portion in the multiple portions is multiplied by a different coefficient.

[0210] In some aspects, the first wireless communication device 602-c can apply an 80 MHz subblock-based phase rotation pattern within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0211] In some aspects, the first wireless communication device 602-c can generate the PPDU according to a replication pattern. For example, the first wireless communication device 602-c can generate the PPDU via encoding a lower frequency tone 3x996 MRU of a 480 MHz contiguous channel bandwidth or a lower frequency tone 4x996 RU of a 640 MHz contiguous channel bandwidth using a BPSK DCM, copying the lower frequency tone 3x996 MRU of the 480 MHz contiguous channel bandwidth or the lower frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth onto a higher frequency tone 3x996 MRU of the 480 MHz contiguous channel bandwidth or a higher frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth, and applying a phase shift to the higher frequency tone RU.

[0212] In some aspects, the first wireless communication device 602-c can apply a spectral mask to the transmission of the preamble and the payload, and if the preamble puncturing is not applied, the temporary transmit spectral mask can have one of: for a 480 MHz PPDU, 0 dBr (dB relative to the maximum spectral density of the signal) bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where the temporary transmit spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to the requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplicate PPDU, 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, where the temporary transmit spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to the requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz PPDU, 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where the temporary transmit spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to the requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplicate PPDU, 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, where the temporary transmit spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to the requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and where the transmit spectrum can not exceed the maximum of the temporary transmit spectral mask and -39 dBm / MHz at any frequency offset.

[0213] FIG. 10 An example of a transmit spectrum mask 1000 for a PPDU that can be applied to support techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown in accordance with one or more aspects of the present disclosure.

[0214] As described herein, the first wireless communication device 602-c can apply a spectrum mask to the transmission of the preamble and the payload. As FIG. 10 As shown, starting from the center frequency, if no puncturing is applied, the 0 dBr (dB relative to the maximum spectral density of the signal) bandwidth is 2a MHz, -20 dBr at a frequency offset of b MHz, -28 dBr at a frequency offset of c MHz, and -40 dBr at a frequency offset of d MHz.

[0215] For a 480 MHz PPDU, a = 239.5 MHz (e.g., 0 dBr bandwidth of 479 MHz), b = 240.5, c = 480 MHz, and d = 720 MHz. The interim transmit spectrum mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to the requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets. The transmit spectrum cannot exceed the interim transmit spectrum mask and a maximum of -39 dBm / MHz at any frequency offset.

[0216] For a 480 MHz non-high throughput duplicate PPDU, a = 239 MHz (e.g., 0 dBr bandwidth of 478 MHz), b = 241, c = 480 MHz, and d = 720 MHz. The interim transmit spectrum mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to the requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets. The transmit spectrum cannot exceed the interim transmit spectrum mask and a maximum of -39 dBm / MHz at any frequency offset.

[0217] For a 640 MHz PPDU, a = 319.5 MHz (e.g., 0 dBr bandwidth of 639 MHz), b = 320.5, c = 640 MHz, and d = 960 MHz. The temporary transmit spectrum mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to the requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets. The transmit spectrum can not exceed the maximum of the temporary transmit spectrum mask and -39 dBm / MHz at any frequency offset.

[0218] For a 640 MHz non-high throughput duplicate PPDU, a = 319 MHz (e.g., 0 dBr bandwidth of 638 MHz), b = 320, c = 640 MHz, and d = 960 MHz. The temporary transmit spectrum mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to the requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets. The transmit spectrum can not exceed the maximum of the temporary transmit spectrum mask and -39 dBm / MHz at any frequency offset.

[0219] FIG. 11 A block diagram 1100 of a device 1105 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown, in accordance with one or more aspects of the present disclosure. The device 1105 can be an example of aspects of an AP or a STA as described herein. The device 1105 can include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105, or one or more components of the device 1105 (e.g., the receiver 1110, the transmitter 1115, and the communications manager 1120), can include at least one processor that can be coupled to at least one memory to individually or collectively support or implement at least portions of the described techniques. Each of these components can communicate with one another (e.g., via one or more buses).

[0220] The receiver 1110 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for 480 MHz and 640 MHz transmissions in Wi-Fi). Information can be passed on to other components of the device 1105. The receiver 1110 can utilize a single antenna or a set of multiple antennas.

[0221] The transmitter 1115 can provide a means for transmitting signals generated by other components of the device 1105. The transmitter 1115 can utilize a single antenna or a set of multiple antennas.

[0222] The communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof can be examples of means for performing various aspects of the techniques for 480 MHz and 640 MHz transmissions in Wi-Fi as described herein. For example, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be capable of performing one or more of the functions described herein.

[0223] In some aspects, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in hardware (e.g., in communications management circuitry). The hardware can include at least one of the processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcode, state machine logic, discrete hardware components, or any combination thereof, which is configured as or otherwise supports a means for performing the functions described in the present disclosure. In some aspects, at least one processor and at least one memory coupled with the at least one processor can be configured to perform one or more of the functions described herein (e.g., the at least one processor executing instructions stored in the at least one memory).

[0224] Additionally or alternatively, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be executed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0225] In some aspects, the communications manager 1120 can be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communications manager 1120 can receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0226] According to examples as disclosed herein, the communication manager 1120 can support wireless communication at a wireless communication device. For example, the communication manager 1120 can enable, be configured as, or be able to operate a means for transmitting a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The communication manager 1120 can enable, be configured as, or be able to operate a means for transmitting a payload of the PPDU using the indicated channel bandwidth.

[0227] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 can support wireless communication at a wireless communication device. For example, the communication manager 1120 can enable, be configured as, or be able to operate a means for receiving a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The communication manager 1120 can enable, be configured as, or be able to operate a means for receiving a payload of the PPDU using the indicated channel bandwidth.

[0228] By including or configuring the communication manager 1120 in accordance with examples as described herein, the device 1105 (e.g., at least one processor of the device 1105 controlling or otherwise

[0229] FIG. 12 A block diagram 1200 of a device 1205 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown, in accordance with one or more aspects of the present disclosure. The device 1205 can be an example of aspects of a device 1105, an AP 102, or a STA 104 as described herein. The device 1205 can include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205, or one or more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, and the communication manager 1220), can include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components can be in communication with one another (e.g., via one or more buses).

[0230] The receiver 1210 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for 480 MHz and 640 MHz transmissions in Wi-Fi). Information can be passed on to other components of the device 1205. The receiver 1210 can utilize a single antenna or a set of multiple antennas.

[0231] The transmitter 1215 can provide means for transmitting signals generated by other components of the device 1205. The transmitter 1215 can utilize a single antenna or a set of multiple antennas.

[0232] Device 1205, or various components thereof, can be an example of means for performing various aspects of techniques for 480 MHz and 640 MHz transmissions in Wi-Fi as described herein. For example, the communication manager 1220 can include a preamble transmitting manager 1225, a payload transmitting manager 1230, a preamble receiving manager 1235, a payload receiving manager 1240, or any combination thereof. The communication manager 1220 can be an example of aspects of the communication manager 1120 as described herein. In some aspects, the communication manager 1220, or various components thereof, can be configured to use or otherwise employ the receiver 1210, the transmitter 1215, or both to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting). For example, the communication manager 1220 can receive information from the receiver 1210, transmit information to the transmitter 1215, or integrate with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0233] According to examples as disclosed herein, the communication manager 1220 can support wireless communication at a wireless communication device. The preamble transmitting manager 1225 can enable, be configured as, or be operable to support means for transmitting a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The payload transmitting manager 1230 can enable, be configured as, or be operable to support means for transmitting a payload of the PPDU using the indicated channel bandwidth.

[0234] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 can support wireless communication at a wireless communication device. The preamble reception manager 1235 can enable, be configured as, or be otherwise accessible for, a component for receiving a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The payload reception manager 1240 can enable, be configured as, or be otherwise accessible for, a component for receiving a payload of the PPDU using the indicated channel bandwidth.

[0235] FIG. 13 A block diagram of an example wireless communication device 1300 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi is shown. In various examples, the wireless communication device 1300 can be a chip, SoC, chipset, package, or a device that can include one or more modems (such as a Wi-Fi (IEEE 802.11) modem or a cellular modem, such as a 3GPP 4G LTE or 5G compliant modem), one or more processors, processing blocks, or processing elements (collectively “at least one processor”), one or more radios (collectively “at least one radio”), and one or more memories or memory blocks (collectively “at least one memory”). In some aspects, the at least one processor can include multiple processors, and the at least one memory can include multiple memories. One or more of the multiple processors can be coupled with one or more of the multiple memories, which can be individually or collectively configured to perform various functions described herein as part of a processing system.

[0236] In some aspects, the wireless communication device 1300 can be for use in a wireless communication device, such as with reference to FIGs. 1-2, 7, and 8. FIG. 11The apparatuses used in the described communication manager 1120. In some other examples, the wireless communication device 1300 can be a communication manager that includes such a chip, SoC, chipset, package, or device, as well as multiple antennas. The wireless communication device 1300 can transmit and receive wireless communications, e.g., in the form of wireless packets. For example, the wireless communication device can be configured or able to operate to transmit and receive packets in the form of physical layer (PHY) and medium access control (MAC) protocol data units (PDUs) that conform to one or more of the IEEE 802.11 family of wireless communication protocol standards. In some aspects, the wireless communication device 1300 also includes or can be coupled with at least one application processor, which can be further coupled with at least one memory. In some aspects, the wireless communication device 1300 also includes at least one external network interface that enables communication with a core network or a backhaul network to attain access to external networks including the Internet.

[0237] The wireless communications device 1300 includes a preamble transmitting manager 1325, a payload transmitting manager 1330, a preamble receiving manager 1335, a payload receiving manager 1340, a tone planning manager 1345, a puncturing planning indication manager 1350, a phase rotation manager 1355, a copy mode manager 1360, a spectral mask manager 1365, a pilot signal transmitting manager 1370, a segment parser manager 1375, a pilot signal receiving manager 1380, a segment de-parser manager 1385, and a 320 MHz channel bandwidth manager 1390. Portions of one or more of the preamble transmitting manager 1325, the payload transmitting manager 1330, the preamble receiving manager 1335, the payload receiving manager 1340, the tone planning manager 1345, the puncturing planning indication manager 1350, the phase rotation manager 1355, the copy mode manager 1360, the spectral mask manager 1365, the pilot signal transmitting manager 1370, the segment parser manager 1375, the pilot signal receiving manager 1380, the segment de-parser manager 1385, and the 320 MHz channel bandwidth manager 1390 can be implemented at least in part in hardware or firmware. For example, one or more of the preamble transmitting manager 1325, the payload transmitting manager 1330, the preamble receiving manager 1335, the payload receiving manager 1340, the tone planning manager 1345, the puncturing planning indication manager 1350, the phase rotation manager 1355, the copy mode manager 1360, the spectral mask manager 1365, the pilot signal transmitting manager 1370, the segment parser manager 1375, the pilot signal receiving manager 1380, the segment de-parser manager 1385, and the 320 MHz channel bandwidth manager 1390 can be implemented at least in part by at least one modem. In some aspects, at least some of the preamble transmitting manager 1325, the payload transmitting manager 1330, the preamble receiving manager 1335, the payload receiving manager 1340, the tone planning manager 1345, the puncturing planning indication manager 1350, the phase rotation manager 1355, the copy mode manager 1360, the spectral mask manager 1365, the pilot signal transmitting manager 1370, the segment parser manager 1375, the pilot signal receiving manager 1380, the segment de-parser manager 1385, and the 320 MHz channel bandwidth manager 1390 are implemented at least in part by at least one processor and are realized as software stored in at least one memory.For example, portions of one or more of the preamble transmitting manager 1325, the payload transmitting manager 1330, the preamble receiving manager 1335, the payload receiving manager 1340, the tone plan manager 1345, the puncturing plan indication manager 1350, the phase rotation manager 1355, the copy mode manager 1360, the spectral mask manager 1365, the pilot signal transmitting manager 1370, the segment parser manager 1375, the pilot signal receiving manager 1380, the segment de-parser manager 1385, and the 320 MHz channel bandwidth manager 1390 can be implemented as non-transitory instructions (or“code”) executable by at least one processor to perform the functions or operations of the corresponding module.

[0238] In some aspects, the at least one processor can be a component of a processing system. A processing system can generally refer to a system or series of machines or components that receives input and processes those inputs to produce a set of outputs (which can be passed to other systems or components of, for example, the wireless communication device 1300). For example, a processing system of the wireless communication device 1300 can refer to a system that includes various other components or subcomponents of the wireless communication device 1300, such as the at least one processor, or the at least one transceiver, or the at least one communication manager, or a combination of other components or components of the wireless communication device 1300. The processing system of the wireless communication device 1300 can interface with other components of the wireless communication device 1300 and can process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the wireless communication device 1300 can include a processing system, a first interface to output information, and a second interface to obtain information. In some aspects, the first interface can refer to an interface between the processing system of the chip or modem and a transmitter, such that the wireless communication device 1300 can transmit information output from the chip or modem. In some aspects, the second interface can refer to an interface between the processing system of the chip or modem and a receiver, such that the wireless communication device 1300 can obtain information or signal inputs, and that information can be passed to the processing system. One of ordinary skill in the art would readily recognize that the first interface can also obtain information or signal inputs, and that the second interface can also output information or signal outputs.

[0239] According to examples as disclosed herein, the communication manager 1320 can support wireless communication at a wireless communication device. The preamble transmitting manager 1325 can enable, be configured to, or be operable to support a component for transmitting a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The payload transmitting manager 1330 can enable, be configured to, or be operable to support a component for transmitting a payload of the PPDU using the indicated channel bandwidth.

[0240] In some aspects, the first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz. In some aspects, the second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation. In some aspects, the second set of values in combination with the bandwidth extension field indicates a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0241] In some aspects, the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz and a 320 MHz bandwidth extended to 7225 MHz, and the indicated channel bandwidth is one of a 480 MHz bandwidth extended to 7225 MHz or a 640 MHz bandwidth extended to 7225 MHz.

[0242] In some aspects, for a preamble transmitted within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value. In some aspects, for a preamble transmitted within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value. In some aspects, the first value is different from the third value, and the second value is different from the fourth value.

[0243] In some aspects, to support transmitting the preamble and the payload, the tone plan manager 1345 can enable, be configured as, or comprise means for supporting transmission of the preamble and the payload in accordance with a tone plan comprising one or more of: a set of multiple EHT 80 MHz tone plans across a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; a 6 x 996 tone RU for the 480 MHz contiguous channel bandwidth; a 4 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; an 8 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 6 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a a6 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 7 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth.

[0244] In some aspects, the pilot signal transmitting manager 1370 can enable, be configured as, or comprise means for transmitting a set of multiple pilot signals, where resources for transmitting the set of multiple pilot signals are based on a tone plan.

[0245] In some aspects, the segment parser manager 1375 can enable, be configured as, or comprise means for generating a PPDU in accordance with a segment parser, where the segment parser is based on a tone plan.

[0246] In some examples, the puncturing plan indication manager 1350 can enable, be configured as, or comprise means for transmitting an indication of a puncturing pattern for a PPDU in a preamble.

[0247] In some aspects, the PPDU is a non-OFDMA PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0248] In some aspects, the PPDU comprises an OFDMA PPDU. In some aspects, the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths for each 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0249] In some aspects, the U-SIG of the TB PPDU comprises a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0250] In some aspects, the preamble comprises an EHT-SIG field that comprises an RU allocation subfield. In some aspects, a number of entries in the RU allocation subfield is based on the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0251] In some aspects, the preamble comprises a UHR STF. In some aspects, the UHR STF comprises a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. In some aspects, each sequence in the set of multiple sequences is multiplied by a different coefficient.

[0252] In some aspects, the preamble comprises a UHR LTF. In some aspects, the UHR LTF comprises a set of multiple sequences within an 80 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. In some aspects, each sequence in the set of multiple sequences comprises multiple portions. In some aspects, each portion in the multiple portions is multiplied by a different coefficient.

[0253] In some aspects, to support transmitting the preamble and the payload, the phase rotation manager 1355 can enable, be configured as, or working with a component for applying an 80 MHz subblock-based phase rotation pattern within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0254] In some aspects, the replication pattern manager 1360 can be able to, configured to, or operable to support means for generating the PPDU via encoding using BPSK-DCM on the lower frequency tones 3 x 996 RU of a 480 MHz contiguous channel bandwidth or 4 x 996 RU of a 640 MHz contiguous channel bandwidth. In some aspects, the replication pattern manager 1360 can be able to, configured to, or operable to support means for replicating the lower frequency tones 3 x 996 RU of a 480 MHz contiguous channel bandwidth or 4 x 996 RU of a 640 MHz contiguous channel bandwidth onto the higher frequency tones 3 x 996 RU of a 480 MHz contiguous channel bandwidth or 4 x 996 RU of a 640 MHz contiguous channel bandwidth. In some aspects, the replication pattern manager 1360 can be able to, configured to, or operable to support means for applying a phase shift to the higher frequency tones 3 x 996 RU of a 480 MHz contiguous channel bandwidth or 4 x 996 RU of a 640 MHz contiguous channel bandwidth.

[0255] In some aspects, to support transmitting the preamble and the payload, the spectrum mask manager 1365 can be able to, configured to, or operable to support means for applying a spectrum mask to the transmission of the preamble and the payload, wherein the spectrum mask has one of: for a 480 MHz physical layer protocol data unit, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz offset, -28 dBr at a 480 MHz offset, and -40 dBr at a 720 MHz offset; for a 480 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz offset, -28 dBr at a 480 MHz offset, and -40 dBr at a 720 MHz offset; for a 640 MHz physical layer protocol data unit, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz offset, -28 dBr at a 640 MHz offset, and -40 dBr at a 960 MHz offset; for a 640 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz offset, -28 dBr at a 640 MHz offset, and -40 dBr at a 960 MHz offset.

[0256] In some aspects, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; within a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 320 MHz channelization and the bandwidth extension field indicates an additional higher 160 MHz sub-band; within a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates one of the first 320 MHz channelization and the additional higher 160 MHz sub-band or a second 320 MHz channelization and an additional lower 160 MHz sub-band; and within a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 320 MHz channelization and the bandwidth extension field indicates an additional lower 160 MHz sub-band.

[0257] In some aspects, within the lowest 160 MHz sub-band, a first spatial reuse field of the U-SIG field is associated with the lowest 160 MHz sub-band, a second spatial reuse field of the U-SIG field is associated with the middle 160 MHz sub-band, and a third spatial reuse field is associated with the additional higher 160 MHz sub-band; and within the highest 160 MHz sub-band, the first spatial reuse field is associated with the middle 160 MHz sub-band, the second spatial reuse field is associated with the highest 160 MHz sub-band, and the third spatial reuse field is associated with the lowest 160 MHz sub-band.

[0258] In some aspects, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; within a first 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 160 MHz channelization and the bandwidth extension field indicates that the first 160 MHz sub-band is a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; within a second 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 160 MHz channelization and the bandwidth extension field indicates that the second 160 MHz sub-band is a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; and within a third 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a third 160 MHz channelization and the bandwidth extension field indicates that the third 160 MHz sub-band is a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0259] In some aspects, within the first 160 MHz sub-band, a first spatial reuse field of the U-SIG field is associated with a lowest 80 MHz of the first 160 MHz sub-band, a second spatial reuse field of the U-SIG field is associated with a highest 80 MHz of the first 160 MHz sub-band, a third spatial reuse field of the U-SIG field is associated with the second 160 MHz sub-band, and a fourth spatial reuse field of the U-SIG field is associated with the third 160 MHz sub-band; within the second 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the second 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the second 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the third 160 MHz sub-band; and within the third 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the third 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the third 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the second 160 MHz sub-band.

[0260] In some aspects, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; the 480 MHz contiguous channel bandwidth includes a 160 MHz primary channel portion and a remaining 320 MHz portion; and the preamble includes a UHR signal field that includes a RU allocation subfield, where the RU allocation subfield includes a respective 9-bit RU allocation table for each 20 MHz portion of the 160 MHz primary channel portion, and where the RU allocation subfield includes a respective 8-bit RU allocation table for each 80 MHz portion of the remaining 320 MHz portion.

[0261] In some aspects, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth; and the preamble includes a UHR signal field that includes a first common field and a first user-specific field associated with a 320 MHz sub-band of the 480 MHz contiguous channel bandwidth and a second common field and a second user-specific field associated with a 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0262] In some aspects, the indicated channel bandwidth is a 480 MHz contiguous channel bandwidth, where the 480 MHz contiguous channel bandwidth includes a primary 160 MHz subchannel, a first secondary 160 MHz subchannel, and one of a second secondary 160 MHz subchannel or a third 160 MHz subband.

[0263] In some aspects, where the primary 160 MHz subchannel is a middle 160 MHz subchannel of a 480 MHz channel bandwidth, the 320 MHz channel bandwidth manager can be configured, be configured to, or be operable with components to support communicating with a second wireless communication device via a first 320 MHz subchannel of the 480 MHz channel bandwidth, where the first 320 MHz subchannel includes the primary 160 MHz subchannel and a lower 160 MHz subchannel of the 480 MHz channel bandwidth, and communicating with a third wireless communication device via a second 320 MHz subchannel of the 480 MHz channel bandwidth, where the second 320 MHz subchannel includes the primary 160 MHz subchannel and an upper 160 MHz subchannel of the 480 MHz channel bandwidth, where the second wireless communication device and the third wireless communication device are 320 MHz limited devices. In some aspects, where the wireless communication device is an AP, the 320 MHz channel bandwidth manager can be configured, be configured to, or be operable with components to support transmitting, to the second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device, and transmitting, to the third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device, where the first 320 MHz operating channel is the first 320 MHz subchannel and the second 320 MHz operating channel is the second 320 MHz subchannel, or receiving, from the second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device, and receiving, from the third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device.

[0264] Additionally or alternatively, the communication manager 1320 can support wireless communication at a wireless communication device in accordance with examples as disclosed herein. The preamble reception manager 1335 can be configured, be configured to, or be operable with components to support receiving a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The payload reception manager 1340 can be configured, be configured to, or be operable with components to support receiving a payload of the PPDU using the indicated channel bandwidth.

[0265] In some aspects, a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz. In some aspects, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation. In some aspects, the second set of values in combination with the bandwidth extension field indicates a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0266] In some aspects, for a preamble received within a first sub-band of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value. In some aspects, for a preamble received within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value. In some aspects, the first value is different from the third value, and the second value is different from the fourth value.

[0267] In some aspects, to support receiving the preamble, the tone plan manager 1345 can enable, be configured as, or can operate a component to support receiving the preamble and the payload in accordance with a tone plan comprising one or more of: a set of multiple EHT 80 MHz tone plans across a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; a 6x996 tone RU for a 480 MHz contiguous channel bandwidth; a 4x996 tone MRU for a 480 MHz contiguous channel bandwidth; a 4x996+484 tone MRU for a 480 MHz contiguous channel bandwidth; a 4x996+484+242 tone MRU for a 480 MHz contiguous channel bandwidth; a 5x996 tone MRU for a 480 MHz contiguous channel bandwidth; a 5x996+484 tone MRU for a 480 MHz contiguous channel bandwidth; a 5x996+484+242 tone MRU for a 480 MHz contiguous channel bandwidth; an 8x996 tone RU for a 640 MHz contiguous channel bandwidth; a 4x996 tone RU for a 640 MHz contiguous channel bandwidth; a 4x996+484 tone MRU for a 640 MHz contiguous channel bandwidth; a 5x996 tone MRU for a 640 MHz contiguous channel bandwidth; a 5x996+484 tone MRU for a 640 MHz contiguous channel bandwidth; a 6x996 tone MRU for a 640 MHz contiguous channel bandwidth; a 6x996+484 tone MRU for a 640 MHz contiguous channel bandwidth; a 7x996 tone MRU for a 640 MHz contiguous channel bandwidth; or a 7x996+484 tone MRU for a 640 MHz contiguous channel bandwidth.

[0268] In some aspects, the pilot signal reception manager 1380 can enable, be configured as, or can operate a component to support receiving a set of multiple pilot signals, where resources for transmitting the set of multiple pilot signals are based on a tone plan.

[0269] In some aspects, the segment de-parser manager 1385 can enable, be configured as, or can operate a component to support de-parsing the PPDU in accordance with a segment de-parser, where the segment de-parser is based on a tone plan.

[0270] In some examples, the puncturing plan indication manager 1350 can be, be configured as, or be operable to support a means for receiving an indication of a puncturing pattern for a PPDU in a preamble.

[0271] In some aspects, the PPDU comprises a non-OFDMA PPDU. In some aspects, the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0272] In some aspects, the PPDU comprises an OFDMA PPDU. In some aspects, the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths per 80 MHz bandwidth within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0273] In some aspects, the U-SIG of the TB PPDU comprises a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0274] In some aspects, the preamble comprises an EHT-SIG field comprising a RU allocation subfield. In some aspects, a number of entries in the RU allocation subfield is based on the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth.

[0275] In some aspects, the preamble comprises a UHR STF. In some aspects, the UHR STF comprises a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. In some aspects, each sequence in the set of multiple sequences is multiplied by a different coefficient.

[0276] In some aspects, the preamble comprises a UHR LTF. In some aspects, the UHR LTF comprises a set of multiple sequences within an 80 MHz segment of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. In some aspects, each sequence in the set of multiple sequences comprises multiple portions. In some aspects, each portion in the multiple portions is multiplied by a different coefficient.

[0277] In some aspects, an 80 MHz subblock-based phase rotation pattern within a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth is applied to the PPDU.

[0278] In some aspects, a 480 MHz contiguous channel bandwidth lower frequency tone 3x996 RU or a 640 MHz contiguous channel bandwidth lower frequency tone 4x996 RU of the PPDU is encoded using BPSK-DCM, and the 480 MHz contiguous channel bandwidth lower frequency tone 3x996 RU or the 640 MHz contiguous channel bandwidth lower frequency tone 4x996 RU is copied and phase shifted onto a 480 MHz contiguous channel bandwidth higher frequency tone 3x996 RU or a 640 MHz contiguous channel bandwidth higher frequency tone 4x99x RU of the PPDU.

[0279] In some aspects, spectral mask is applied to the preamble and the payload. In some aspects, the spectral mask has one of: for a 480 MHz physical layer protocol data unit, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz offset, -28 dBr at a 480 MHz offset, and -40 dBr at a 720 MHz offset; for a 480 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz offset, -28 dBr at a 480 MHz offset, and -40 dBr at a 720 MHz offset; for a 640 MHz physical layer protocol data unit, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz offset, -28 dBr at a 640 MHz offset, and -40 dBr at a 960 MHz offset; for a 640 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz offset, -28 dBr at a 640 MHz offset, and -40 dBr at a 960 MHz offset.

[0280] In some aspects, the preamble can include one or more user fields indicating one or more RU assignments within the indicated channel bandwidth for one or more respective users associated with the one or more user fields. In such examples where each user field includes an RU assignment, the UHR-SIG common field can not include an RU allocation subfield.

[0281] FIG. 14A flow diagram illustrating a method 1400 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi in accordance with one or more aspects of the present disclosure is shown. The operations of method 1400 can be implemented by a AP or a STA or its components as described herein. For example, the operations of method 1400 can be performed by a AP or a STA as described with reference to FIGs. 1 through 3 and 6 through 9. In some aspects, a AP or a STA can execute a set of instructions to control the functional elements of the wireless AP or wireless STA to perform the described functions. Additionally or alternatively, the wireless AP or wireless STA can perform aspects of the described functions using special-purpose hardware. FIG. 2 to FIG. 13

[0282] In some aspects, at block 1405, the wireless AP or wireless STA can transmit a preamble of the PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The operations of block 1405 can be performed according to the examples disclosed herein, such as transmitting a PHY preamble including a legacy portion 352 and a non-legacy portion 354 of FIG. 3a FIG. 4 a PHY preamble 402 of FIG. 4, or FIG. 6 a preamble 608 of FIG. 6. In some aspects, aspects of the operations of block 1405 can be performed by a preamble transmitting manager 1325 as described with reference to FIG. 13 FIG. 13.

[0283] In some aspects, at block 1410, the wireless AP or wireless STA can transmit a payload of the PPDU using the indicated channel bandwidth. The operations of block 1410 can be performed according to the examples as disclosed herein, such as transmitting a payload 356 of FIG. 3a FIG. 4 a PSDU 404 of FIG. 4, or FIG. 6 a payload 610 of FIG. 6. In some aspects, aspects of the operations of block 1410 can be performed by a payload transmitting manager 1330 as described with reference to FIG. 13 FIG. 13.

[0284] FIG. 15 A flow diagram illustrating a method 1500 that supports techniques for 480 MHz and 640 MHz transmissions in Wi-Fi in accordance with one or more aspects of the present disclosure is shown. The operations of method 1500 can be implemented by a AP or a STA or its components as described herein. For example, the operations of method 1500 can be performed by a AP or a STA as described with reference to FIGs. 1 through 3 and 6 through 9. In some aspects, a AP or a STA can execute a set of instructions to control the functional elements of the wireless AP or wireless STA to perform the described functions. Additionally or alternatively, the wireless AP or wireless STA can perform aspects of the described functions using special-purpose hardware. FIG. 2 to FIG. 13 ​​​The described AP or STA to perform. In some aspects, the AP or STA can execute a set of instructions to control the functional elements of the wireless AP or wireless STA to perform the described functions. Additionally or alternatively, the wireless AP or wireless STA can perform aspects of the described functions using special-purpose hardware.

[0285] In some aspects, in block 1505, the wireless AP or wireless STA can receive a preamble of a PPDU, where the preamble includes a U-SIG, where the U-SIG includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth. The operations of block 1505 can be performed according to the examples disclosed herein, such as receiving a PHY preamble including a legacy portion 352 and a non-legacy portion 354 of FIG. 3a FIG. 4 a PHY preamble 402 of FIG. 4, or FIG. 6 a preamble 608 of FIG. 6. In some aspects, aspects of the operations of block 1505 can be performed by a preamble reception manager 1335 as described with reference to FIG. 13

[0286] In some aspects, in block 1510, the wireless AP or wireless STA can receive a payload of the PPDU using the indicated channel bandwidth. The operations of block 1510 can be performed according to the examples as disclosed herein, such as receiving a payload 356 of FIG. 3a FIG. 4 a PSDU 404 of FIG. 4, or FIG. 6 a payload 610 of FIG. 6. In some aspects, aspects of the operations of block 1510 can be performed by a payload reception manager 1340 as described with reference to FIG. 13

[0287] Implementation examples are described in the following numbered clauses: Clause 1 : A method for wireless communication by a wireless communication device, comprising: transmitting a preamble of a PPDU, where the preamble includes a U-SIG field, where the U-SIG field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmitting a payload of the PPDU using the indicated channel bandwidth.

[0288] ​​​​Aspect 2: The method of aspect 1, wherein a first set of values of the bandwidth field indicate a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicate 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicate the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0289] Aspect 3: The method of aspect 2, wherein the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz and a 320 MHz bandwidth extended to 7225 MHz, and wherein the indicated channel bandwidth is one of a 480 MHz bandwidth extended to 7225 MHz or a 640 MHz bandwidth extended to 7225 MHz.

[0290] Aspect 4: The method of any of aspects 1 to 3, wherein for the preamble transmitted within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, for the preamble transmitted within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, and the first value is different from the third value and the second value is different from the fourth value.

[0291] Aspect 5: The method of any of aspects 1-4, wherein transmitting the preamble and the payload comprises: transmitting the preamble and the payload according to a tone plan, the tone plan comprising one or more of: a plurality of EHT 80 MHz tone plans across the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth; a 6 x 996 tone RU for the 480 MHz contiguous channel bandwidth; a 4 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; an 8 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 6 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a a 6 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 7 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth.

[0292] Aspect 6: The method of aspect 5, further comprising: transmitting a set of a plurality of pilot signals, wherein resources used to transmit the set of a plurality of pilot signals are based at least in part on the tone plan.

[0293] Aspect 7: The method of any of aspects 5-6, further comprising: generating the PPDU according to a segment parser, wherein the segment parser is based at least in part on the tone plan.

[0294] Aspect 8: The method of any of aspects 1-7, further comprising: transmitting an indication of a puncturing pattern of the PPDU in the preamble.

[0295] Aspect 9: The method of aspect 8, wherein the PPDU comprises a non-orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0296] Aspect 10: The method of any one of aspects 8 through 9, wherein the PPDU comprises an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths per 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0297] Aspect 11: The method of any one of aspects 1 through 10, wherein the U-SIG field of a TB PPDU comprises a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0298] Aspect 12: The method of any one of aspects 1 through 11, wherein the preamble comprises an EHT signal field, the EHT signal field comprises a RU allocation subfield, and a number of entries in the RU allocation subfield is based at least in part on the indicated channel bandwidth being one of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0299] Aspect 13: The method of any one of aspects 1 through 12, wherein the preamble comprises a UHR STF, the UHR STF comprises a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, and each sequence in the set of multiple sequences is multiplied by a different coefficient.

[0300] Aspect 14: The method of any one of aspects 1-13, wherein the preamble comprises a UHR LTF comprising a set of a plurality of sequences within the 480 MHz contiguous channel bandwidth or the 80 MHz segment of the 640 MHz contiguous channel bandwidth, each sequence of the set of the plurality of sequences comprising a plurality of parts, and each part of the plurality of parts being multiplied by a different coefficient.

[0301] Aspect 15: The method of any one of aspects 1-14, wherein transmitting the legacy portion of the preamble comprises applying an 80 MHz subblock-based phase rotation pattern within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0302] Aspect 16: The method of any one of aspects 1-15, the method further comprising: generating the PPDU via encoding a lower frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or a lower frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth using binary phase-shift keying dual-subcarrier modulation; copying the lower frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or the lower frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth onto a higher frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or a higher frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth; and applying a phase shift to the higher frequency tone 3x966 RU of the 480 MHz contiguous channel bandwidth or the higher frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth.

[0303] Aspect 17: The method of any of aspects 1-16, wherein transmitting the preamble and the payload comprises: applying a spectral mask to the transmission of the preamble and the payload, wherein the spectral mask has one of: for a 480 MHz PPDU, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz PPDU, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and wherein the transmitted spectrum cannot exceed the maximum of the spectral mask and -39 dBm / MHz at any frequency offset.

[0304] Aspect 18: The method of any of aspects 1-16, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 320 MHz channelization and the bandwidth extension field indicates an additional higher 160 MHz sub-band; within a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates one of the first 320 MHz channelization and the additional higher 160 MHz sub-band or a second 320 MHz channelization and an additional lower 160 MHz sub-band; and within a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates the second 320 MHz channelization and the bandwidth extension field indicates the additional lower 160 MHz sub-band.

[0305] Aspect 19: The method of aspect 18, wherein: within the lowest 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with the lowest 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with the middle 160 MHz sub-band, and a third spatial reuse field is associated with the additional higher 160 MHz sub-band; and within the highest 160 MHz sub-band, the first spatial reuse field is associated with the middle 160 MHz sub-band, the second spatial reuse field is associated with the highest 160 MHz sub-band, and the third spatial reuse field is associated with the lowest 160 MHz sub-band.

[0306] Aspect 20: The method of any of aspects 1-16, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within a first 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 160 MHz channelization and the bandwidth extension field indicates that the first 160 MHz sub-band is a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; within a second 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 160 MHz channelization and the bandwidth extension field indicates that the second 160 MHz sub-band is a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; and within a third 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a third 160 MHz channelization and the bandwidth extension field indicates that the third 160 MHz sub-band is a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0307] Aspect 21 : The method of aspect 20, wherein: within the first 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with a lowest 80 MHz of the first 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with a highest 80 MHz of the first 160 MHz sub-band, a third spatial reuse field of the general signal field is associated with the second 160 MHz sub-band, and a fourth spatial reuse field of the general signal field is associated with the third 160 MHz sub-band; within the second 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the second 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the second 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the third 160 MHz sub-band; and within the third 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the third 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the third 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the second 160 MHz sub-band.

[0308] Aspect 22: The method of any one of aspects 1-16, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; the 480 MHz contiguous channel bandwidth includes a 160 MHz primary channel portion and a remaining 320 MHz portion; and the preamble includes a UHR-SIG field that includes a RU allocation subfield, wherein the RU allocation subfield includes a respective 9-bit RU allocation table for each 20 MHz portion of the 160 MHz primary channel portion, and wherein the RU allocation subfield includes a respective 8-bit RU allocation table for each 80 MHz portion of the remaining 320 MHz portion.

[0309] Aspect 23: The method of any one of aspects 1-16, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; and the preamble includes a UHR-SIG field that includes a first common field and a first user-specific field associated with a 320 MHz sub-band of the 480 MHz contiguous channel bandwidth and a second common field and a second user-specific field associated with a 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0310] Aspect 24: The method of any of aspects 1-16, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth, wherein the 480 MHz contiguous channel bandwidth comprises a primary 160 MHz subchannel, a first secondary 160 MHz subchannel, and one of a second secondary 160 MHz subchannel or a third 160 MHz subband.

[0311] Aspect 25: The method of aspect 24, wherein the primary 160 MHz subchannel comprises a middle 160 MHz subchannel of the 480 MHz channel bandwidth, and the method further comprises: communicating with a second wireless communication device via a first 320 MHz subchannel of the 480 MHz channel bandwidth, wherein the first 320 MHz subchannel comprises the primary 160 MHz subchannel and a lower 160 MHz subchannel of the 480 MHz channel bandwidth; and communicating with a third wireless communication device via a second 320 MHz subchannel of the 480 MHz channel bandwidth, wherein the second 320 MHz subchannel comprises the primary 160 MHz subchannel and an upper 160 MHz subchannel of the 480 MHz channel bandwidth, wherein the second wireless communication device and the third wireless communication device are 320 MHz limited devices.

[0312] Aspect 26: The method of aspect 25, wherein the wireless communication device is an access point, the method further comprising: transmitting, to the second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device, and transmitting, to the third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device, wherein the first 320 MHz operating channel is the first 320 MHz subchannel and the second 320 MHz operating channel is the second 320 MHz subchannel; or receiving, from the second wireless communication device, an indication of the first 320 MHz operating channel for the second wireless communication device, and receiving, from the third wireless communication device, an indication of the second 320 MHz operating channel for the third wireless communication device.

[0313] Aspect 27: A method for wireless communication by a wireless communication device, the method comprising: receiving a preamble of a PPDU, wherein the preamble comprises a U-SIG field, wherein the U-SIG field comprises a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the PPDU, the indicated channel bandwidth being one of a 480 MHz contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within the 640 MHz contiguous channel bandwidth; and receiving a payload of the PPDU using the indicated channel bandwidth.

[0314] Aspect 28: The method of aspect 27, wherein a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicates the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0315] Aspect 29: The method of aspect 28, wherein the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz, a 320 MHz bandwidth extended to 7225 MHz, a 480 MHz bandwidth extended to 7225 MHz, and a 640 MHz bandwidth extended to 7225 MHz.

[0316] Aspect 30: The method of any one of aspects 27 to 29, wherein for the preamble received within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, for the preamble received within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, and the first value is different from the third value and the second value is different from the fourth value.

[0317] Aspect 31 : The method of any one of Aspects 27-30, wherein receiving the preamble comprises: receiving the preamble and the payload according to a tone plan, the tone plan comprising one or more of: a set of multiple EHT 80 MHz tone plans across the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth; a 6 x 996 tone RU for the 480 MHz contiguous channel bandwidth; a 4 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 4 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 480 MHz contiguous channel bandwidth; a 5 x 996 + 484 + 242 tone MRU for the 480 MHz contiguous channel bandwidth; an 8 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 tone RU for the 640 MHz contiguous channel bandwidth; a 4 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a 5 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 6 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; a a 6 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth; a 7 x 996 tone MRU for the 640 MHz contiguous channel bandwidth; or a 7 x 996 + 484 tone MRU for the 640 MHz contiguous channel bandwidth.

[0318] Aspect 32: The method of Aspect 31, further comprising: receiving a set of multiple pilot signals, wherein resources used to transmit the set of multiple pilot signals are based at least in part on the tone plan.

[0319] Aspect 33: The method of any one of Aspects 31 -32, further comprising: de-parsing the PPDU according to a segment de-parser, wherein the segment de-parser is based at least in part on the tone plan.

[0320] Aspect 34: The method of any one of Aspects 27-33, further comprising: receiving an indication of a puncturing pattern of the PPDU in the preamble.

[0321] Aspect 35: The method of aspect 34, wherein the PPDU comprises a non-orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0322] Aspect 36: The method of any one of aspects 34-35, wherein the PPDU comprises an orthogonal frequency division multiple access PPDU, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths per 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0323] Aspect 37: The method of any one of aspects 27-36, wherein the U-SIG field of a TB PPDU comprises a set of multiple spatial reuse fields indicating spatial reuse information for each of a set of multiple 20 MHz portions of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0324] Aspect 38: The method of any one of aspects 27-37, wherein the preamble comprises an EHT signal field, the EHT signal field comprises a RU allocation subfield, and a number of entries in the RU allocation subfield is based at least in part on the indicated channel bandwidth being one of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

[0325] Aspect 39: The method of any one of aspects 27-38, wherein the preamble comprises a UHR STF, the UHR STF comprises a set of multiple sequences within an 80 MHz segment or a 160 MHz segment of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, and each sequence in the set of multiple sequences is multiplied by a different coefficient.

[0326] Aspect 40: The method of any one of aspects 27-39, wherein the preamble comprises a UHR LTF comprising a set of a plurality of sequences within the 480 MHz contiguous channel bandwidth or the 80 MHz segment of the 640 MHz contiguous channel bandwidth, each sequence of the set of the plurality of sequences comprising a plurality of parts, and each part of the plurality of parts being multiplied by a different coefficient.

[0327] Aspect 41 : The method of any one of aspects 27-40, wherein an 80 MHz subblock based phase rotation pattern within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth is applied to a legacy portion of the preamble.

[0328] Aspect 42: The method of any one of aspects 27-41, wherein a lower frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or a lower frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth of the PPDU is encoded using binary phase shift keying dual subcarrier modulation, and the lower frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or the lower frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth is copied and shifted onto a higher frequency tone 3x996 RU of the 480 MHz contiguous channel bandwidth or a higher frequency tone 4x996 RU of the 640 MHz contiguous channel bandwidth of the PPDU.

[0329] Aspect 43: The method of any of aspects 27-42, wherein spectral mask is applied to the preamble and the payload, and the spectral mask has one of: for a 480 MHz PPDU, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz PPDU, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplicate PPDU, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and wherein the transmit spectrum cannot exceed the maximum of the spectral mask and -39 dBm / MHz at any frequency offset.

[0330] Aspect 44: The method of any of aspects 27-42, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 320 MHz channelization and the bandwidth extension field indicates an additional higher 160 MHz sub-band; within a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates one of the first 320 MHz channelization and the additional higher 160 MHz sub-band or a second 320 MHz channelization and an additional lower 160 MHz sub-band; and within a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates the second 320 MHz channelization and the bandwidth extension field indicates the additional lower 160 MHz sub-band.

[0331] Aspect 45: The method of aspect 44, wherein: within the lowest 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with the lowest 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with the middle 160 MHz sub-band, and a third spatial reuse field is associated with the additional higher 160 MHz sub-band; and within the highest 160 MHz sub-band, the first spatial reuse field is associated with the middle 160 MHz sub-band, the second spatial reuse field is associated with the highest 160 MHz sub-band, and the third spatial reuse field is associated with the lowest 160 MHz sub-band.

[0332] Aspect 46: The method of any of aspects 27-42, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within a first 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 160 MHz channelization and the bandwidth extension field indicates that the first 160 MHz sub-band is a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; within a second 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 160 MHz channelization and the bandwidth extension field indicates that the second 160 MHz sub-band is a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; and within a third 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a third 160 MHz channelization and the bandwidth extension field indicates that the third 160 MHz sub-band is a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0333] Aspect 47: The method of aspect 46, wherein: within the first 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with a lowest 80 MHz of the first 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with a highest 80 MHz of the first 160 MHz sub-band, a third spatial reuse field of the general signal field is associated with the second 160 MHz sub-band, and a fourth spatial reuse field of the general signal field is associated with the third 160 MHz sub-band; within the second 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the second 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the second 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the third 160 MHz sub-band; and within the third 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the third 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the third 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the second 160 MHz sub-band.

[0334] Aspect 48: The method of any one of aspects 27-42, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; the 480 MHz contiguous channel bandwidth comprises a 160 MHz primary channel portion and a remaining 320 MHz portion; and the preamble comprises a UHR-SIG field that includes a RU allocation subfield, wherein the RU allocation subfield includes a respective 9-bit RU allocation table for each 20 MHz portion of the 160 MHz primary channel portion, and wherein the RU allocation subfield includes a respective 8-bit RU allocation table for each 80 MHz portion of the remaining 320 MHz portion.

[0335] Aspect 49: The method of any one of aspects 27-42, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; and the preamble comprises a UHR-SIG field that includes a first common field and a first user-specific field associated with a 320 MHz sub-band of the 480 MHz contiguous channel bandwidth and a second common field and a second user-specific field associated with a 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

[0336] Aspect 50: The method of any of aspects 27-42, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth, wherein the 480 MHz contiguous channel bandwidth comprises a primary 160 MHz subchannel, a first secondary 160 MHz subchannel, and one of a second secondary 160 MHz subchannel or a third 160 MHz subband.

[0337] Aspect 51: A wireless communication device, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured to, individually or collectively, cause the wireless communication device to perform the method of any of aspects 1-26 in association with executing the code.

[0338] Aspect 52: A wireless communication device for wireless communication, comprising at least one means for performing the method of any of aspects 1-26.

[0339] Aspect 53: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of any of aspects 1-26.

[0340] Aspect 54: A wireless communication device, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured to, individually or collectively, cause the wireless communication device to perform the method of any of aspects 27-50 in association with executing the code.

[0341] Aspect 55: A wireless communication device for wireless communication, comprising at least one means for performing the method of any of aspects 27-50.

[0342] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of any of aspects 27-50.

[0343] As used herein, the term “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, inferring, looking up (such as via a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and other such similar actions.

[0344] As used herein, the phrase “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c. As used herein, “or” is intended to be interpreted as an inclusive or meaning at least one, unless explicitly indicated otherwise (e.g., “either a or b” or “either a or b but not both”). Further, as used herein, the phrase “one or more of’ a list of items refers to any combination of those items, including single members. In addition, as used herein, the phrase referring to “at least one of’ a list of items should be construed to mean that at least one of the individual items composing the collection of items is present (or “one or more” of the items from a list of items is present). Further, “set” refers to one or more items, and “subset” refers to fewer than the total number of items in the set but not empty.

[0345] As used herein, “or” is intended to be interpreted in an inclusive sense unless otherwise indicated. For example, “a or b” can include a, b, or a combination of a and b. Further, as used herein, the phrase “one or more of’ a list of items refers to any combination of those items, including single members. In addition, as used herein, the phrase referring to “at least one of’ a list of items should be construed to mean that at least one of the individual items composing the collection of items is present (or “one or more” of the items from a list of items is present). Further, “set” refers to one or more items, and “subset” refers to fewer than the total number of items in the set but not empty.

[0346] As used herein, including in the claims, the article "a" preceding a noun is open, and is understood to refer to "at least one" or "one or more" of the noun. Thus, the terms "a," "at least one," "one or more," and "at least one of one or more" are interchangeable. For example, where a claim recites "a component" of performing one or more functions, it is understood that each function of the individual function can be performed by a single component or by any combination of more components. Thus, "a component" having a particular property or performing a particular function can refer to "at least one or more components" having that particular property or performing that particular function. A subsequent reference to "the component" in the claim, where the component is introduced by an article "the" or "a" and the antecedent is a plural component, can refer to any or all of the components. For example, a component introduced by the article "a" in a claim can be understood to mean "one or more components," and a subsequent reference in the claim to "the component" can be understood as a reference to "at least one of the one or more components." Similarly, a subsequent reference in the claim to "the component," where the component is introduced by the article "the" or "a" and the antecedent is "one or more components," can mean any or all of the components. For example, a subsequent reference in the claim to "the one or more components" can be understood as a reference to "at least one of the one or more components."

[0347] The various illustrative components, logic, blocks, modules, circuits, operations and algorithm processes described in connection with the examples disclosed herein can be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been generalized above and described in terms of various illustrative components, blocks, modules, circuits and processes. This generalization applies not only to structural equivalents but also to functional equivalents. The generalization applies even when the functional equivalent does not take the same structure as disclosed in this specification and its structural equivalents.

[0348] Various modifications to the examples described in this disclosure will be readily apparent to those of ordinary skill, and the general principles defined herein can be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the claims are not intended to be limited to the examples shown herein, but are to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0349] Additionally, various features that are described in the context of separate examples can also be implemented as combined in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple examples separately or in any suitable sub-combination. As such, although features can be described above as acting in particular combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a sub-combination or variations of a sub-combination.

[0350] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring such an order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings can schematically depict one more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the illustrated example processes. For example, one or more additional operations can be performed before, after, simultaneously with, or between any of the illustrated operations. In some environments, multitasking and parallel processing can be advantageous. Moreover, the separation of various system components in the examples described above should not be understood as requiring such separation in all examples, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products.

Claims

1. A wireless communication device, the wireless communication device comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured individually or collectively to cause, associated with executing the code, the wireless communication device to: transmit a preamble of a physical layer protocol data unit, wherein the preamble includes a general signal field, wherein the general signal field includes a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the physical layer protocol data unit, the indicated channel bandwidth being one of a 480 megahertz (MHz) contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmit a payload of the physical layer protocol data unit using the indicated channel bandwidth.

2. The wireless communication device of claim 1, wherein: a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values in combination with the bandwidth extension field indicates the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

3. The wireless communication device of claim 2, wherein the corresponding set of channel bandwidths includes a 160 MHz bandwidth extended to 7225 MHz and a 320 MHz bandwidth extended to 7225 MHz, and wherein the indicated channel bandwidth is one of a 480 MHz bandwidth extended to 7225 MHz or a 640 MHz bandwidth extended to 7225 MHz.

4. The wireless communication device of claim 1, wherein: for the preamble transmitted within a first sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a first value and the bandwidth extension field indicates a second value, for the preamble transmitted within a second sub-band of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, the bandwidth field indicates a third value and the bandwidth extension field indicates a fourth value, and the first value is different from the third value and the second value is different from the fourth value.

5. The wireless communication device of claim 1, wherein to transmit the preamble and the payload, the processor-executable code is configured to cause the wireless communication device to: transmit the preamble and the payload according to a tone plan, the tone plan comprising one or more of: a plurality of Extremely High Throughput (EHT) 80 MHz tone plans across the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth; 6 x 996 tone resource units for the 480 MHz contiguous channel bandwidth; 4 x 996 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 4 x 996 + 484 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 4 x 996 + 484 + 242 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 5 x 996 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 5 x 996 + 484 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 5 x 996 + 484 + 242 tone multi-resource units for the 480 MHz contiguous channel bandwidth; 8 x 996 tone resource units for the 640 MHz contiguous channel bandwidth; 4 x 996 tone resource units for the 640 MHz contiguous channel bandwidth; 4 x 996 + 484 tone multi-resource units for the 640 MHz contiguous channel bandwidth; 5 x 996 tone multi-resource units for the 640 MHz contiguous channel bandwidth; 5 x 996 + 484 tone multi-resource units for the 640 MHz contiguous channel bandwidth; 6 x 996 tone multi-resource units for the 640 MHz contiguous channel bandwidth; a6 x 996 + 484 tone multi-resource units for the 640 MHz contiguous channel bandwidth; 7 x 996 tone multi-resource units for the 640 MHz contiguous channel bandwidth; or 7 x 996 + 484 tone multi-resource units for the 640 MHz contiguous channel bandwidth.

6. The wireless communication device of claim 5, wherein the processor-executable code is configured to cause the wireless communication device to: transmit a plurality of pilot signals, wherein resources used to transmit the plurality of pilot signals are based at least in part on the tone plan.

7. The wireless communication device of claim 5, wherein the processor-executable code is configured to cause the wireless communication device to: generate the physical layer protocol data unit according to a segment parser, wherein the segment parser is based at least in part on the tone plan.

8. The wireless communication device of claim 1, wherein the processor-executable code is configured to cause the wireless communication device to: transmit, in the preamble, an indication of a puncturing pattern of the physical layer protocol data unit.

9. The wireless communication device of claim 8, wherein the physical layer protocol data unit comprises a non-orthogonal frequency division multiple access physical layer protocol data unit, and wherein the indication of the puncturing pattern indicates one or more of: no puncturing, a punctured 40 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, a punctured 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, two concurrent punctured 80 MHz bandwidths within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, or a concurrent 40 MHz bandwidth and 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

10. The wireless communication device of claim 8, wherein: the physical layer protocol data unit comprises an orthogonal frequency division multiple access physical layer protocol data unit, and the indication of the puncturing pattern indicates zero or one or two punctured 20 MHz bandwidths for each 80 MHz bandwidth within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

11. The wireless communication device of claim 1, wherein the generic signal field of a triggered physical layer protocol data unit comprises a plurality of spatial reuse fields indicating spatial reuse information for each of a plurality of 20 MHz portions of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

12. The wireless communication device of claim 1, wherein: the preamble comprises an extremely high throughput signal field, the extremely high throughput signal field comprising a resource unit allocation subfield, and a number of entries in the resource unit allocation subfield is based at least in part on the indicated channel bandwidth being one of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

13. The wireless communication device of claim 1, wherein: the preamble comprises an ultra-high reliability short training field, the ultra-high reliability short training field comprises a plurality of sequences within an 80 MHz segment or a 160 MHz segment of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, and each sequence of the plurality of sequences is multiplied by a different coefficient.

14. The wireless communication device of claim 1, wherein: the preamble comprises an ultra-high reliability long training field, the ultra-high reliability long training field comprises a plurality of sequences within an 80 MHz segment of the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth, each sequence of the plurality of sequences comprises a plurality of portions, and each portion of the plurality of portions is multiplied by a different coefficient.

15. The wireless communication device of claim 1, wherein to transmit the legacy portion of the preamble, the processor executable code is configured to cause the wireless communication device to: apply a 80 MHz sub-block based phase rotation pattern within the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

16. The wireless communication device of claim 1, wherein the processor-executable code is configured to cause the wireless communication device to: generate the physical layer protocol data unit via encoding a lower frequency tone 3x966 resource unit of the 480 MHz contiguous channel bandwidth or a lower frequency tone 4x996 resource unit of the 640 MHz contiguous channel bandwidth using binary phase shift keying dual subcarrier modulation; copy the lower frequency tone 3x966 resource unit of the 480 MHz contiguous channel bandwidth or the lower frequency tone 4x996 resource unit of the 640 MHz contiguous channel bandwidth onto a higher frequency tone 3x996 resource unit of the 480 MHz contiguous channel bandwidth or a higher frequency tone 4x996 resource unit of the 640 MHz contiguous channel bandwidth; and apply a phase shift to the higher frequency tone 3x966 resource unit of the 480 MHz contiguous channel bandwidth or the higher frequency tone 4x996 resource unit of the 640 MHz contiguous channel bandwidth.

17. The wireless communication device of claim 1, wherein to transmit the preamble and the payload, the processor-executable code is configured to cause the wireless communication device to: applying a spectral mask to transmission of the preamble and the payload, wherein the spectral mask has one of: for a 480 MHz physical layer protocol data unit, a 0 dBr bandwidth of 479 MHz, -20 dBr at a 240.5 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239.5 MHz and 240.5 MHz, 240.5 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239.5 MHz, 240.5 MHz, 480 MHz, and 720 MHz frequency offsets; for a 480 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 478 MHz, -20 dBr at a 241 MHz frequency offset, -28 dBr at a 480 MHz frequency offset, and -40 dBr at a 720 MHz frequency offset, wherein the spectral mask for frequency offsets between 239 MHz and 241 MHz, 241 MHz and 480 MHz, and 480 MHz and 720 MHz can be linearly interpolated in the decibel domain according to requirements for 239 MHz, 241 MHz, 480 MHz, and 720 MHz frequency offsets; for a 640 MHz physical layer protocol data unit, a 0 dBr bandwidth of 639 MHz, -20 dBr at a 320.5 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319.5 MHz and 320.5 MHz, 320.5 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319.5 MHz, 320.5 MHz, 640 MHz, and 960 MHz frequency offsets; for a 640 MHz non-high throughput duplicate physical layer protocol data unit, a 0 dBr bandwidth of 638 MHz, -20 dBr at a 320 MHz frequency offset, -28 dBr at a 640 MHz frequency offset, and -40 dBr at a 960 MHz frequency offset, wherein the spectral mask for frequency offsets between 319 MHz and 320 MHz, 320 MHz and 640 MHz, and 640 MHz and 760 MHz can be linearly interpolated in the decibel domain according to requirements for 319 MHz, 320 MHz, 640 MHz, and 960 MHz frequency offsets, and wherein a transmit spectrum cannot exceed the spectral mask and a maximum of -39 dBm / MHz at any frequency offset.

18. The wireless communication device of claim 1, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within the middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates one of the first 320 MHz channelization and the additional higher 160 MHz sub-band or a second 320 MHz channelization and an additional lower 160 MHz sub-band; and within the highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates the second 320 MHz channelization, and the bandwidth extension field indicates the additional lower 160 MHz sub-band.

19. The wireless communication device of claim 18, wherein: within the lowest 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with the lowest 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with the middle 160 MHz sub-band, and a third spatial reuse field is associated with the additional higher 160 MHz sub-band; and within the highest 160 MHz sub-band, the first spatial reuse field is associated with the middle 160 MHz sub-band, the second spatial reuse field is associated with the highest 160 MHz sub-band, and the third spatial reuse field is associated with the lowest 160 MHz sub-band.

20. The wireless communication device of claim 1, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; within a first 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a first 160 MHz channelization, and the bandwidth extension field indicates that the first 160 MHz sub-band is a lowest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; within a second 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a second 160 MHz channelization, and the bandwidth extension field indicates that the second 160 MHz sub-band is a middle 160 MHz sub-band of the 480 MHz contiguous channel bandwidth; and within a third 160 MHz sub-band of the 480 MHz contiguous channel bandwidth, the bandwidth field indicates a third 160 MHz channelization, and the bandwidth extension field indicates that the third 160 MHz sub-band is a highest 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

21. The wireless communication device of claim 20, wherein: ​ within the first 160 MHz sub-band, a first spatial reuse field of the general signal field is associated with a lowest 80 MHz of the first 160 MHz sub-band, a second spatial reuse field of the general signal field is associated with a highest 80 MHz of the first 160 MHz sub-band, a third spatial reuse field of the general signal field is associated with the second 160 MHz sub-band, and a fourth spatial reuse field of the general signal field is associated with the third 160 MHz sub-band; within the second 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the second 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the second 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the third 160 MHz sub-band; and within the third 160 MHz sub-band, the first spatial reuse field is associated with a lowest 80 MHz of the third 160 MHz sub-band, the second spatial reuse field is associated with a highest 80 MHz of the third 160 MHz sub-band, the third spatial reuse field is associated with the first 160 MHz sub-band, and the fourth spatial reuse field is associated with the second 160 MHz sub-band.

22. The wireless communication device of claim 1, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; the 480 MHz contiguous channel bandwidth includes a 160 MHz primary channel portion and a remaining 320 MHz portion; and the preamble includes a very high reliability signal field that includes a resource unit allocation subfield, wherein the resource unit allocation subfield includes a respective 9-bit resource unit allocation table for each 20 MHz portion of the 160 MHz primary channel portion, and wherein the resource unit allocation subfield includes a respective 8-bit resource unit allocation table for each 80 MHz portion of the remaining 320 MHz portion.

23. The wireless communication device of claim 1, wherein: the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth; and the preamble includes a very high reliability signal field that includes a first common field and a first user-specific field associated with a 320 MHz sub-band of the 480 MHz contiguous channel bandwidth and a second common field and a second user-specific field associated with a 160 MHz sub-band of the 480 MHz contiguous channel bandwidth.

24. The wireless communication device of claim 1, wherein the indicated channel bandwidth is the 480 MHz contiguous channel bandwidth, wherein the 480 MHz contiguous channel bandwidth includes a primary 160 MHz subchannel, a first secondary 160 MHz subchannel, and one of a second secondary 160 MHz subchannel or a third 160 MHz sub-band.

25. The wireless communication device of claim 24, wherein the primary 160 MHz subchannel comprises a middle 160 MHz subchannel of the 480 MHz channel bandwidth, and wherein the processor-executable code is configured to cause the wireless communication device to: communicate with a second wireless communication device via a first 320 MHz subchannel of the 480 MHz channel bandwidth, wherein the first 320 MHz subchannel comprises the primary 160 MHz subchannel and a lower 160 MHz subchannel of the 480 MHz channel bandwidth; and communicate with a third wireless communication device via a second 320 MHz subchannel of the 480 MHz channel bandwidth, wherein the second 320 MHz subchannel comprises the primary 160 MHz subchannel and an upper 160 MHz subchannel of the 480 MHz channel bandwidth, wherein the second wireless communication device and the third wireless communication device are 320 MHz limited devices.

26. The wireless communication device of claim 25, wherein the wireless communication device is an access point, and wherein the processor-executable code is configured to cause the wireless communication device to: transmit, to the second wireless communication device, an indication of a first 320 MHz operating channel for the second wireless communication device and transmit, to the third wireless communication device, an indication of a second 320 MHz operating channel for the third wireless communication device, wherein the first 320 MHz operating channel is the first 320 MHz subchannel and the second 320 MHz operating channel is the second 320 MHz subchannel; or receive, from the second wireless communication device, an indication of the first 320 MHz operating channel for the second wireless communication device and receive, from the third wireless communication device, an indication of the second 320 MHz operating channel for the third wireless communication device.

27. A wireless communication device, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and configured individually or collectively to cause the wireless communication device, in association with executing the code, to: receive a preamble of a physical layer protocol data unit, wherein the preamble comprises a general signal field, wherein the general signal field comprises a bandwidth field and a bandwidth extension field jointly indicating a channel bandwidth of the physical layer protocol data unit, the indicated channel bandwidth being one of a 480 megahertz (MHz) contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and receive a payload of the physical layer protocol data unit using the indicated channel bandwidth.

28. The wireless communication device of claim 27, wherein: a first set of values of the bandwidth field indicates a corresponding set of channel bandwidths other than 480 MHz or 640 MHz, a second set of values of the bandwidth field indicates 480 MHz bandwidth operation or 640 MHz bandwidth operation, and the second set of values, in combination with the bandwidth extension field, indicates the 480 MHz contiguous channel bandwidth or the 640 MHz contiguous channel bandwidth.

29. A method for wireless communication by a wireless communication device, the method comprising: transmitting a preamble of a physical layer protocol data unit, wherein the preamble includes a universal signal field, wherein the universal signal field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the physical layer protocol data unit, the indicated channel bandwidth being one of a 480 megahertz (MHz) contiguous channel bandwidth or a 640 MHz contiguous channel bandwidth; and transmitting a payload of the physical layer protocol data unit using the indicated channel bandwidth.

30. A method for wireless communication by a wireless communication device, the method comprising: receiving a preamble of a physical layer protocol data unit, wherein the preamble includes a universal signal field, wherein the universal signal field includes a bandwidth field and a bandwidth extension field that jointly indicate a channel bandwidth of the physical layer protocol data unit, the indicated channel bandwidth being one of a 480 megahertz (MHz) contiguous channel bandwidth, a 640 MHz contiguous channel bandwidth, or a 480 MHz punctured bandwidth within the 640 MHz contiguous channel bandwidth; and receiving a payload of the physical layer protocol data unit using the indicated channel bandwidth.

Images