EHT link adaptation in WLAN

Abstract

The invention provides EHT link adaptation in a WLAN. Methods and apparatus for very high throughput (EHT) link adaptation (ELA) are described herein. A station (STA) may receive a first physical layer protocol data unit (PPDU) that includes a first primary-secondary (PS) 160 subfield and a high efficiency (HE) / EHT subfield. The HT / EHT subfield may indicate whether a second PPDU to be transmitted by the STA is based on an HE-related parameter or an EHT-related parameter. The first PS 160 subfield may indicate a primary 160 MHz channel or a secondary 160 MHz channel. The STA may transmit the second PPDU based on the HE / EHT subfield, the second PPDU including a second PS 160 subfield, an EHT-MCS subfield, and a number of spatial streams (NSS) subfield. The second PS 160 subfield may indicate a 160 MHz channel that is determined based on the indication of the first PS 160 subfield. An index of the EHT-MCS subfield and a value of the NSS subfield may be determined based on a measurement of the determined 160 MHz channel.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 307,141 filed on February 6, 2022, U.S. Provisional Application No. 63 / 318,650 filed on March 10, 2022, Provisional Application No. 63 / 320,917 filed on March 17, 2022, and Provisional Application No. 63 / 415,786 filed on October 13, 2022, the contents of each of which are incorporated herein by reference. Background Art

[0003] IEEE 802.11 Extremely High Throughput (EHT) (or IEEE 802.11be) was formed to explore the possibility of further increasing peak throughput and improving the efficiency of IEEE 802.11 networks. The list of features that achieve the goals of increased peak throughput and improved efficiency may include, but are not limited to, multiple APs, multi-band / multi-links, 320MHz bandwidth, 16 spatial streams, hybrid automatic repeat request (HARQ), AP coordination, and a new design for 6GHz channel access. Link adaptation has been proven to be an effective way to increase overall system throughput without incurring additional overhead. However, the current 802.11be (EHT) does not include any mechanism for EHT link adaptation (e.g., using the A control field). Summary of the invention

[0004] This document describes a method and apparatus for extremely high throughput (EHT) link adaptation (ELA) in a wireless local area network (WLAN). A station (STA) may receive a first physical layer protocol data unit (PPDU) including a first aggregation control (A control) field from another STA, the first aggregation control (A control) field including a high efficiency (HE) / extremely high throughput (EHT) subfield and a first primary and secondary (PS) 160 subfield. The HT / EHT subfield may indicate whether the second PPDU to be sent by the STA is based on HE-related parameters or EHT-related parameters. The first PS160 subfield may indicate the primary 160 MHz channel or the secondary 160 MHz channel to be measured by the STA. The STA may send the second PPDU including a second A control field to the other STA based on the HE / EHT subfield, the second A control field including a second PS160 subfield, an EHT modulation and coding scheme (MCS) subfield, and a number of spatial streams (NSS) subfield. The second PS160 subfield may indicate a 160 MHz channel determined based on the indication of the first PS160 subfield.The index in the EHT-MCS subfield and the value in the NSS subfield may be determined based on measurement of the determined 160 MHz channel.

[0005] The following options are provided:

[0006] 1. A station (STA), the station (STA) comprising:

[0007] A receiver configured to receive a first physical layer protocol data unit (PPDU) including a first aggregation control (A control) field from another STA, the first aggregation control (A control) field including a high efficiency (HE) / extremely high throughput (EHT) subfield and a first primary secondary (PS) 160 subfield, wherein the HT / EHT subfield indicates whether a second PPDU to be sent by the STA is based on HE-related parameters or EHT-related parameters, and the first PS 160 subfield indicates a primary 160 MHz channel or a secondary 160 MHz channel; and

[0008] A transmitter configured to transmit, based on the HE / EHT subfield, the second PPDU including a second A control field to the other STA, the second A control field including a second PS160 subfield, an EHT-modulation and coding scheme (MCS)

[0009] subfield and a number of spatial streams (NSS) subfield, wherein the second PS160 subfield indicates a 160 MHz channel determined from the primary 160 MHz channel and the secondary 160 MHz channel based on an indication of the first PS160 subfield, wherein the index in the EHT-MCS subfield and the value in the NSS subfield are determined based on a measurement of the selected 160 MHz channel.

[0010] 2. The STA according to scheme 1, wherein the second A control field further includes an unrequested MCS feedback (MFB) subfield, a resource unit (RU) allocation subfield, a bandwidth (BW) subfield, and an MCS request sequence index (MSI) / partial PPDU parameter subfield.

[0011] 3. The STA according to solution 2, further comprising:

[0012] A processor, the processor being configured to:

[0013] Determine, based on the one or more RUs indicated in the RU allocation subfield and the BW indicated in the BW subfield, a size and a position of the one or more RUs in the 160 MHz channel to measure channel quality; and

[0014] Based on the channel quality, the index of the EHT-MCS subfield and the value of the NSS subfield are determined for sending the second PPDU to the other STA.

[0015] 4. The STA according to scheme 3, wherein the one or more RUs in the RU allocation subfield are RUs or multiple RUs (MRUs), the index is an EHT MCS index, and the value represents the number of spatial streams.

[0016] 5. The STA according to scheme 2, wherein, under the condition that the unrequired MFB is zero (0) or false, the MSI / partial PPDU parameter subfield includes a sequence number indicating a PPDU received by the STA for an EHT MCS feedback request or a PPDU sent by the STA for an EHT MCS feedback response.

[0017] 6. The STA of scheme 2, wherein, under the condition that the non-required MFB is one (1) or true, the MSI / partial PPDU parameter subfield includes a value indicating an EHT PPDU format and a coding type of the STA for channel quality measurement.

[0018] 7. The STA according to solution 6, wherein the EHT PPDU format includes an EHT multi-user (MU) PPDU and an EHT triggered-based (TB) PPDU, and the decoding type includes a binary convolutional code (BCC) and a low-density parity check (LDPC).

[0019] 8. The STA of scheme 1, wherein the HE / EHT subfield received in the first A-control field indicates to the STA that the EHT-related parameters are indicated in the second A-control field of the second PPDU.

[0020] 9. The STA according to solution 1, wherein the EHT-related parameters include the index, the value, a primary / secondary 160 MHz channel indication, and an EHT PPDU format.

[0021] 10. The STA according to solution 1, wherein the other STA is an access point (AP) or a non-AP STA. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0023] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0024] Figure 1B is an example of an embodiment in which Figure 1AA system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0025] Figure 1C is an example of an embodiment in which Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0026] Figure 1D is an example of an embodiment in which Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0027] Figure 2 is a diagram illustrating an example medium access control (MAC) frame format;

[0028] Figure 3 is a diagram illustrating an example Aggregation Control (A Control) subfield format of a High Efficiency (HE) variant High Throughput (HT) Control field format;

[0029] Figure 4 is a diagram illustrating an example control subfield format;

[0030] Figure 5 is a diagram illustrating an example control information subfield format in a High Efficiency (HE) Link Adaptation (HLA) Control subfield;

[0031] Figure 6 is a diagram illustrating an example MCS Request (MRQ) Sequence Identifier (MSI) / Partial PPDU Parameters subfield format when the Unrequited MCS Feedback (MFB) subfield is 1;

[0032] Figure 7 is a diagram illustrating an example HE MAC Capability Information field format;

[0033] Figure 8 is a diagram illustrating an example trigger frame format in 802.11ax;

[0034] Fig. 9 is a diagram illustrating an example common information field in a trigger frame;

[0035] Fig.10 is a diagram illustrating an example user information field in a trigger frame;

[0036] Fig.11 is a diagram illustrating an example Block Acknowledgement (BA) control field format;

[0037] Fig.12 is a diagram illustrating an example BA information field format (Compressed Block Acknowledgement);

[0038] Fig.13 is a diagram illustrating an example Block Ack Start Sequence Control subfield format;

[0039] Fig.14 is a diagram illustrating an example BA information field format (Multi_STA Block Acknowledgement);

[0040] Fig.15 is a diagram illustrating an example association identifier (AID) traffic identifier (TID) information subfield format;

[0041] Fig.16 is a diagram illustrating an example BA Information field format (Multi_TID Block Acknowledgement);

[0042] Fig.17 is a diagram illustrating an example per-TID information subfield format;

[0043] Fig.18 is a diagram illustrating an example control information subfield format in an Extremely High Throughput (EHT) Link Adaptation (ELA) Control subfield;

[0044] Fig.19 is a diagram illustrating an example MSI / Partial PPDU Parameters subfield format when the Unrequired MFB subfield is 1;

[0045] Fig. 20 is a diagram illustrating an example control information subfield format in the ELA control subfield (without bandwidth (BW));

[0046] Fig.21 is a diagram illustrating an example enhanced EHT MAC capability information field format;

[0047] Fig. 22 is a diagram illustrating an example HLA control field EHT variant;

[0048] Fig.23A is a diagram illustrating an example MCS Feedback on Request (MFB) operating procedure;

[0049] Fig. 23B is a diagram illustrating an example unrequired MFB operating procedure;

[0050] Fig.24A is a diagram illustrating another example MCS feedback on demand (MFB) operation procedure;

[0051] Fig. 24B is a diagram illustrating another example unrequired MFB operating procedure; and

[0052] Fig.25 is a diagram illustrating an example Link Adaptation Enhanced BA Control field. DETAILED DESCRIPTION

[0053] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0054] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0055] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0056] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0057] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0058] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), that may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols, such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​Uplink (UL) Packet Access (HSUPA).

[0059] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[0060] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology (such as NR radio access) that may establish the air interface 116 using NR.

[0061] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0062] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0063] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, the base station 114 b may have a direct connection to the Internet 110. Therefore, the base station 114 b may not need to access the Internet 110 via the CN 106.

[0064] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0065] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0066] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0067] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0068] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0069] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0070] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0071] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0072] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, or the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0073] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0074] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0075] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.

[0076] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0077] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0078] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0079] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0080] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0081] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0082] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0083] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0084] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0085] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0086] In a representative embodiment, the other network 112 may be a WLAN.

[0087] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0088] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0089] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0090] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0091] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0092] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, all available bands may be considered busy even if most of the available bands remain idle.

[0093] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0094] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0095] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0096] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths).

[0097] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0098] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0099] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0100] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0101] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0102] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

[0103] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.

[0104] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0105] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communications.

[0106] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be utilized in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit system (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0107] A WLAN in infrastructure basic service set (BSS) mode has an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP typically has access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic originating from outside the BSS and directed to the STA arrives through the AP and is delivered to the STA. Traffic originating from the STA and directed to a destination outside the BSS is transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS can also be transmitted through the AP, where the source STA transmits traffic to the AP, and the AP delivers the traffic to the destination STA.

[0108] When using the 802.11ac infrastructure operating mode, the AP can send beacons on a fixed channel (such as the primary channel). This channel can be 20MHz wide and is the operating channel of the BSS. This channel is also used by STAs to establish a connection with the AP. The basic channel access mechanism in 802.11 systems is carrier sense multiple access / collision avoidance (CSMA / CA). In this operating mode, each STA including the AP can sense the primary channel. If the channel is detected to be busy, the STA can back off. Therefore, one STA (e.g., only one STA) can transmit at any given time in a given BSS.

[0109] High throughput (HT) STAs may also communicate using 40 MHz wide channels. This may be achieved by combining the primary 20 MHz channel with an adjacent 20 MHz channel to form a 40 MHz wide contiguous channel.

[0110] In 802.11ac, very high throughput (VHT) STAs can support 20MHz, 40MHz, 80MHz, and 160MHz wide channels. 40MHz and 80MHz channels are formed by combining continuous 20MHz channels similar to the above-mentioned 802.11n. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-contiguous 80MHz channels. This can also be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data is passed through a segment parser that divides the data into two streams. IFFT and time domain processing are performed on each stream separately. The streams are then mapped to two channels and the data is sent. At the receiver, this mechanism is reversed and the combined data is transmitted to the MAC.

[0111] In order to improve spectral efficiency, 802.11ac has introduced the concept of downlink multi-user MIMO (MU-MIMO) transmission to multiple STAs in the same symbol time frame (for example, during the downlink OFDM symbol). The possibility of using downlink MU-MIMO is currently also being considered for 802.11ah. It is important to note that since downlink MU-MIMO uses the same symbol timing for multiple STAs when it is used in 802.11ac, interference from waveform transmission to multiple STAs is not a problem. However, all STAs involved in the MU-MIMO transmission of the relevant AP may need to use the same channel or frequency band. This may limit the operating bandwidth to the minimum channel bandwidth supported by the STAs included in the MU-MIMO transmission of the relevant AP.

[0112] The STA may construct a subset of frames appropriately for transmission, and decode a (possibly different) subset of frames upon verification after reception. The specific subset of frames that the STA constructs and decodes may be determined by the functionality supported by that particular STA. The STA may use a frame check sequence (FCS) to verify each received frame, and interpret certain fields in the MAC header of all frames.

[0113] Figure 2 2 is a diagram illustrating an example medium access control (MAC) frame format 200, which may be used in conjunction with any of the other embodiments described herein. MAC frame format 200 may include a set of fields that appear in a fixed order in all frames. Specifically, Figure 2As illustrated, the MAC frame 200 may include a MAC header including a frame control field 202, a duration / ID field 204, an address 1 field 206, an address 2 field 208, an address 3 field 210, a sequence control field 212, an address 4 field 214, a QoS control field 216, and a high throughput (HT) control field 218. The MAC frame 200 may also include a frame body 220 and a frame check sequence (FCS) 222. The STA may use Figure 2 Frames are sent using the frame format described in . Figure 2 A general MAC frame format for a protocol version 0 (PV0) MPDU is described as an example.

[0114] The HT Control field 218 may be present in a control encapsulation frame and may be present in QoS Data, (802.11ax) QoS Null, and Management frames determined by the +HTC subfield of the Frame Control field 202 .

[0115] For example, the HT Control field 218 sent by a non-China Millimeter Wave Multi-Gigabit (non-CMMG) STA may include three variants: HT variant, VHT variant, and HE variant. These variant formats are distinguished by the values ​​of B0 and B1 as described in Table 1.

[0116] Table 1: HT Control Field Format

[0117]

[0118] Figure 3 is a diagram of an example aggregation control (A control) subfield format 300 illustrating a high efficiency (HE) variant HT control field format, which may be used in conjunction with any of the other embodiments described herein. Figure 3 As illustrated, the A control subfield 300 may include a control list subfield 305 and padding 310. The length of the A control subfield 300 may be 30 bits. The control list subfield 305 may include one or more control subfields.

[0119] Figure 4 is a diagram illustrating an example control subfield format 400, which may be used in conjunction with any of the other implementations described herein. Figure 4 The format of each control subfield 400 is shown in FIG. For example, the control subfield 400 may include a control ID subfield 405 and a control information subfield 410, such as Figure 4 exemplified.

[0120] The control ID subfield 405 may indicate the type of information carried in the control information subfield 410. The length of the control information subfield 410 may be fixed for each value of the unreserved control ID subfield 405. The values ​​of the control ID subfield 405 and the associated length of the control information subfield 410 are defined in Table 2.

[0121] Table 2: Control ID subfield values

[0122]

[0123]

[0124] Figure 5 5 is a diagram illustrating an example control information subfield format 500 in a high efficiency (HE) link adaptation (HLA) control subfield, which may be used in conjunction with any of the other embodiments described herein. The control information subfield 500 in the HLA control subfield may include information related to HE link adaptation (HLA) or HLA procedures. Figure 5 The format of the control information subfield 500 is illustrated in FIG.

[0125] Table 3: HLA Control Subfields

[0126]

[0127]

[0128]

[0129] Figure 6 is a diagram illustrating an example MCS Request (MRQ) Sequence Identifier (MSI) / Partial PPDU Parameters subfield format 600 when the MCS Feedback Not Required (MFB) subfield is 1 or true, which may be used in conjunction with any of the other embodiments described herein. Figure 6 As illustrated, the MSI / partial PPDU parameters subfield 600 may include a PPDU format subfield 605 and a coding type subfield 610 .

[0130] The PPDU format subfield 605 may indicate the format of the PPDU according to which it is estimated that MCS feedback (MFB) is not required:

[0131] For HE SU PPDU, set to 0;

[0132] For HE MU PPDU, set to 1;

[0133] For HE ER SU PPDU, set to 2; and

[0134] For HE TB PPDU, set to 3.

[0135] The decoding type subfield 610 may include decoding information according to which the PPDU for which the MFB is not required is estimated:

[0136] For binary convolutional codes (BCC), set to 0; and

[0137] For low-density parity check (LDPC), set to 1.

[0138] A STA or HESTA may declare that it is a HESTA by sending a HE capability element. Figure 7 700, which may be used in conjunction with any of the other embodiments described herein. The HE Capability Element may include, but is not limited to, Element ID, Length, Element ID Extension, HE MAC Capability Information 700, HE PHY Capability Information, Supported HE-MCS and NSS Sets, and PHY Packet Extension (PPE) Threshold (optional) subfields. Figure 7 As illustrated, the format of the HE MAC capability information field 700 may include +HTC HE support 702, TWT requester support 704, TWT responder support 706, dynamic segmentation support 708, maximum number of segmented MSDU / A-MSDU index 710, minimum segment size 712, trigger frame MAC padding duration 714, multi-TID aggregation Rx support 716, HE link adaptation support 718, full confirmation support 720, TRS support 722, BSR support 724, broadcast TWT support 726, 32-txt BA bitmap support 728, MU cascading support 730, enable confirmation aggregation support 732, reserved 734, OM control support 736, OFDMA RA support 738, maximum A-MPDU length index extension 740, A-MSDU segmentation support 742, flexible TWT scheduling support 744, Rx control frame to multiple BSS 746, BSRP BORP A-MPDU aggregation 748, QTP support 750, BQR support 752, PSR responder 754, NDP feedback report support 756, OPS support 758, support 760 for A-MSDU not under BA in A-MPDU with acknowledgement enabled, multi-TID aggregation Tx support 762, HE subchannel selective transmission support 764, UL2x996 frequency modulation RU support 766, OM control UL MU data disable RX support 768, HE dynamic SM power saving 770, punching detection support 772, and HT and VHT trigger frame RX support 774 subfields.

[0139] The HE link adaptation support subfield 718 of the HE MAC capability information field 700 may be given in Table 4.

[0140] Table 4HE HE Link Adaptation Support Subfield in the MAC Capability Information Field

[0141]

[0142] Link adaptation using the HLA Control subfield is described herein.The presence of more than one instance of the HLA Control subfield with the MCS Request (MRQ) field equal to 1 within a single PPDU may be interpreted by the receiver as a single request for link adaptation feedback.

[0143] The MFB requester (e.g., a transmitter) may specify the RU index and BW for which link adaptation feedback is requested. Upon receiving the HLA control subfield with the MRQ subfield equal to 1, the MFB responder (e.g., a receiver) may calculate the HE-MCS, Nss, and DCM for the RU and BW specified in the MRQ. These estimates may be based on the same RU of the PPDU carrying the MRQ. The PPDU carrying the MRQ may include the RU for the MFB request. The MFB responder may mark the result of the calculation using the MRQ sequence identifier (MSI) value from the HLA control subfield in the received frame carrying the MRQ. The MFB responder may include the received MSI value in the MSI field of the corresponding response frame. In the case of a delayed response, this allows the MFB requester to associate the MFB with the request for the MRQ.

[0144] A STA may provide its feedback on link adaptation to another STA without a request (i.e., MCS request). For example, the unsolicited HE-MCS, Nss, DCM, BW, and RU estimates reported in the HLA Control subfield transmitted by the STA may be calculated based on the most recent PPDU received by the STA that matches the description indicated by the PPDU Format, Tx Beamforming, and Coding Type subfields in the same HLA Control subfield.

[0145] Figure 8 802.11ax introduces trigger frames for the first time. Trigger frames can be used to allocate resources and trigger single-user or multi-user access. Figure 8 As illustrated, the trigger frame may include, but is not limited to, a frame control field 802 , a duration field 804 , an RA field 806 , a TA field 808 , a common information field 810 , a user information field 812 , padding 814 , and a frame control sequence (FCS) field 816 .

[0146] Fig. 9is a diagram illustrating an example common information field 900 in a trigger frame, which may be used in conjunction with any of the other embodiments described herein. Fig. 9 As illustrated, the common information field 900 may include, but is not limited to, trigger type 302, UL length 904, more TF 906, CS required 908, ULBW 910, GI and HE-LTF type 912, MU-MIMO HE-LTF mode 914, number of HE-LTF symbols and midamble periodicity 916, UL STBC 918, LDPC additional symbol segment 920, AP Tx power 922, pre-FEC filling factor 924, PE disambiguation 926, UL spatial multiplexing 928, Doppler 930, reserved UL HE SIG-A2 932, reserved 934, and trigger-related common information 936 subfields.

[0147] The trigger type subfield 302 in the common information field 900 may include possible values ​​as shown in Table 5.

[0148] Table 5 Trigger Type

[0149] Trigger Type subfield value Trigger frame variant 0 Basics 1 BF Report Poll (BFRP) 2 MU-BAR 3 MU-RTS 4 Buffer Status Report Poll (BSRP) 5 GCRMU-BAR 6 Bandwidth Query Report Poll (BQRP) 7 NDP Feedback Report Poll (NFRP) 8 to 15 reserve

[0150] Fig.10 1 is a diagram illustrating an example user information field 1000 in a trigger frame, which can be used in conjunction with any of the other embodiments described herein. The user information field 1000 for all trigger types except the Null Feedback Report Poll (NFRP) trigger can be as shown in FIG. Fig.10 As described. Fig.10 As illustrated, the user information field 1000 may include, but is not limited to, an AID 12 subfield 1002, an RU allocation subfield 1004, a UL FEC decoding type subfield 1006, a UL DCM subfield 1010, an SS allocation / RA-RU information subfield 1012, a UL target received power subfield 1014, a reserved subfield 1016, and a trigger-related user information subfield 1018.

[0151] Fig.11 1 is a diagram illustrating an example block acknowledgement (BA) control field format 1100, which may be used in conjunction with any of the other embodiments described herein. Fig.11 As illustrated, the BA control field 1100 may include, but is not limited to, a BA confirmation policy subfield 1105 , a BA type subfield 1110 , a reserved subfield 1115 , and a TID_INFO subfield 1120 .

[0152] The BA type subfield 1110 in the BA control field 1100 may indicate a block acknowledgement frame variant as defined in Table 6.

[0153] Table 6 Block Ack Frame Variant Coding

[0154]

[0155]

[0156] Fig.12 1 is a diagram illustrating an example BA information field format 1200 (of a compressed block acknowledgement frame), which may be used in conjunction with any of the other embodiments described herein. Fig.12 As illustrated, the BA information field 1200 may include, but is not limited to, a block acknowledgement starting sequence control subfield 1205 and a block acknowledgement bitmap subfield 1210 .

[0157] Fig.13 is a diagram illustrating an example Block Ack Start Sequence Control subfield format 1300, which may be used in conjunction with any of the other embodiments described herein. Fig.13 As illustrated, the block acknowledgement starting sequence control subfield 1300 may include, but is not limited to, a fragment number (0) subfield 1305 and a starting sequence number 1310 .

[0158] The TID_INFO subfield of the BA control field of the compressed block acknowledgement frame may include the TID for which the block acknowledgement frame is transmitted. Fig.12 The BA information field 1200 of the compressed block acknowledgement frame is shown in FIG. Fig.13 The block ACK starting sequence control subfield 1300 is shown in FIG. The starting sequence number subfield 1310 of the block ACK starting sequence control subfield 1300 may include the sequence number of the first MSDU or A-MSDU for which the block ACK frame is transmitted.

[0159] A Multi-STA Block ACK variant is described herein. If UL MU or Multi-TID A-MPDU operation is supported and the MPDUs carried in HETBPPDU or Multi-STA Multi-TID, Multi-STA Single TID or Single-STA Multi-TID A-MPDU are acknowledged, the Multi-STA Block ACK frame may be supported.

[0160] Fig.14 1400, which may be used in conjunction with any of the other embodiments described herein. Fig.14 As illustrated, the BA information field 1400 may include, but is not limited to, a per-AID TIM information subfield 1405. The BA information field 1400 of the multi-STA block acknowledgement frame may include, for example: Fig.14 One or more per-AID TID information subfields 1405 are illustrated.

[0161] Fig.151 is a diagram illustrating an example association identifier (AID) traffic identifier (TID) information subfield format 1500, which may be used in conjunction with any of the other embodiments described herein. Fig.15 As illustrated, the AID TID information subfield 1500 may include, but is not limited to, an AID 11 subfield 1505 , an acknowledgment type subfield 1510 , and a TID subfield 1515 .

[0162] Fig.16 1 is a diagram illustrating an example BA information field format (Multi_TID Block Acknowledgement) 1600, which may be used in conjunction with any of the other embodiments described herein. Fig.16 As illustrated, the BA information field 1600 may include, but is not limited to, a per-TID information subfield 1605 , a block ACK starting sequence control subfield 1610 , and a block ACK bitmap subfield 1615 . Fig.17 is a diagram illustrating an example per-TID information subfield format 1700, which may be used in conjunction with any of the other embodiments described herein. Fig.17 As illustrated, the per-TID information subfield 1700 may include, but is not limited to, a reserved subfield 1705 and a TID value subfield 1710. The TID_INFO subfield 1700 of the BA control field 1600 of the multi-TID block ACK frame may include the number of TIDs whose information is reported in the BA information field minus one. The BA information field of the multi-TID block ACK frame may include one or more instances of the per-TID information 1605, block ACK start sequence control 1610, and block ACK bitmap 1615 subfields, such as Fig.16 shown. Fig.17 The per-TID information subfield 1700 is shown in FIG. Fig.13 The Block Ack Start Sequence Control subfield is shown in FIG.

[0163] IEEE 802.11 Extremely High Throughput (EHT) is considered the next major revision to the IEEE 802.11 standard that follows 802.11ax. EHT was formed to explore the possibility of further increasing peak throughput and improving the efficiency of IEEE 802.11 networks. The main use cases and applications proposed may include, but are not limited to, high throughput and low latency applications such as: video over WLAN; augmented reality (AR); and virtual reality (VR).

[0164] The list of features that achieve the goals of increased peak throughput and improved efficiency may include, but are not limited to: multiple APs; multi-band / multi-link; 320 MHz bandwidth; 16 spatial streams; HARQ; AP coordination; and a new design for 6 GHz channel access.

[0165] Link adaptation is a mechanism by which a transmitter and a receiver communicate to establish optimal parameters, such as a modulation and coding scheme (MCS), given channel conditions or a radio environment. The MCS may include variables such as modulation and the data rate on each spatial stream. The transmitter may need to obtain feedback from the receiver to determine the best MCS based on the channel conditions, and then continuously adjust the selection of the MCS as conditions change due to interference, motion, fading, and other events. Link adaptation has been proven to be an effective way to improve overall system throughput without incurring additional overhead. However, in the current 802.11be (EHT), there is no definition of EHT link adaptation (e.g., using the A control field). Due to the many differences between EHT features and HE features, such as different MCS combinations, operating BW, different Nss parameters, different PPDU types, etc., it is difficult to reuse the existing HLA control subfield to implement link adaptation for EHT devices. Therefore, it is necessary to define EHT link adaptation, for example, via the A control field.

[0166] In 802.11ax, it is indicated that the unrequired HE-MCS, Nss, DCM, BW, and RU estimates reported in the HLA Control subfield transmitted by the STA are calculated based on the most recent PPDU received by the STA, which matches the description indicated by the PPDU Format, Tx Beamforming, and Coding Type subfields in the same HLA Control subfield. When the PPDU format is 1, it indicates that it is a HE MU PPDU. Both OFDMA and MU-MIMO transmissions use the MU-PPDU format. However, the recommended MCS, Nss, DCM may be significantly different between these two types of transmissions. Similar problems may exist in EHT devices. Therefore, an enhanced method is needed to distinguish the recommended HE-MCS, Nss, DCM, etc. for MU-MIMO or OFDMA transmissions of HE devices.

[0167] In order to optimize MU-MIMO link adaptation, different MCS and Nss may be required for different paired STAs (e.g., two or more STAs). In addition, if the recommended MCS and / or Nss are used for different paired STAs, the overhead will increase significantly. In the current 802.11ax / 802.11be, there is no such method to indicate which paired STAs the recommended MCS and / or Nss are used for in MU-MIMO transmission. Therefore, enhanced signaling is needed to indicate the recommended MCS and / or Nss for different paired STAs.

[0168] The current ACK or block ACK simply feeds back one bit to indicate whether the packet is received correctly. There is no other information to indicate how well the received PPDU is decoded. Therefore, it is necessary to enhance the current block ACK mechanism so that the transmitter can better understand how the received PPDU is received, such as higher than the required SNR, or lower than the required SNR, etc.

[0169] The TRS control field in the A control subfield of the HE variant HT control field can be used to trigger response scheduling. The TRS control field can carry an 8-bit RU allocation subfield, which is used to identify the RU allocated to the STA in 802.11ax. In 802.11be, due to the support of wider bandwidth (e.g., 320MHz) and the 8-bit RU allocation subfield is not enough to uniquely define the RU. If the TRS control field is reused in 802.11be, it needs to be modified.

[0170] This article describes an implementation of EHT link adaptation via the A control field. The implementation described herein can solve the problem of how to implement EHT link adaptation via A control. Although the implementation described herein is based on EHT devices (e.g., APs and / or STAs), it can be extended to devices belonging to the next generation of WiFi.

[0171] Embodiments of the EHT Link Adaptation Control field are described herein. In one embodiment, the type of control field supporting EHT Link Adaptation may be included in the control information as indicated in Table 7.

[0172] Table 7 Example Control ID Subfield Values ​​with New Control ID

[0173]

[0174]

[0175] Fig.18 1 is a diagram illustrating an example control information subfield format 1800 in an Extremely High Throughput (EHT) Link Adaptation (ELA) Control subfield, which may be used in conjunction with any of the other embodiments described herein. The control information subfield in the EHT Control subfield may include information or control information related to EHT Link Adaptation (ELA) or an EHT Link Adaptation procedure. For example, Fig.18As illustrated, the control information subfield may include, but is not limited to, an unrequested MFB subfield 1802, an MRQ subfield 1804, an NSS subfield 1806, an EHT-MCS subfield 1808, an RU allocation subfield 1810, a BW subfield 1812, a PS160 subfield 1814, an MSI / partial PPDU parameter subfield 1816, a Tx beamforming subfield 1818, and a UL EHT TB PPDUMFB subfield 1820. An example interpretation of the ELA control subfield is as indicated in Table 8.

[0176] Table 8 Exemplary explanation of ELA control subfields

[0177]

[0178]

[0179]

[0180]

[0181] Fig.19 1 is a diagram illustrating an example MSI / partial PPDU parameter subfield format 1900 when the Unrequired MFB subfield is 1, which may be used in conjunction with any of the other embodiments described herein. Fig.19 As illustrated, the MSI / partial PPDU parameter subfield 1900 may include, but is not limited to, a PPDU format subfield 1905 and a coding type subfield 1910. In one example, Fig.19 The illustrated MSI / Partial PPDU Parameters subfield 1900 is when the Unrequired MFB subfield is 1.

[0182] The PPDU format subfield 1905 may indicate the format of the PPDU according to which it is estimated that the MFB is not required:

[0183] For EHT MU PPDU (DL OFDMA), set to 0;

[0184] For EHT MU PPDU (transmission to a single user or NDP), set to 1;

[0185] For EHT MU PPDU (DL MU-MIMO), set to 2; and

[0186] Set to 3 for EHT TB PPDU (when UL EHT TB PPDU MFB is 1) and for UL EHT MU PPDU (when UL EHT TB PPDU MFB is 0).

[0187] NSS subfield ( Fig.18 1806) may be used to show only the recommended NSS (up to 8 spatial stream number values, e.g., 1 to 8, or 1, 2, 3, 4, 8, 12, 14, 16, or any 8 values ​​from 1 to 16). Alternatively or additionally, the NSS subfield 1806 may be combined with the BW subfield 1812 to indicate a recommended number of spatial streams greater than 8. Table 9 depicts an exemplary definition of the recommended number of spatial streams indicated using a combination of the BW subfield 1812 and the NSS subfield 1806.

[0188] Table 9 Exemplary illustration of the recommended number of spatial streams indicated using a combination of the BW subfield and the Nss subfield

[0189]

[0190] Alternatively or additionally, the control information subfield in the EHT control subfield may include Fig. 20 Information about the ELA procedures described. Fig. 20 2 is a diagram illustrating an example control information subfield format 2000 in an ELA control subfield (e.g., without bandwidth (BW)), which may be used in conjunction with any of the other embodiments described herein. Fig. 20 As illustrated, the control information subfield 2000 may include, but is not limited to, an unrequested MFB subfield 2002, an MRQ subfield 2004, an NSS subfield 2006, an EHT-MCS subfield 2008, an RU allocation subfield 2010, a reserved subfield 2012, a PS160 subfield 2014, an MSI / partial PPDU parameter subfield 2016, a Tx beamforming subfield 2018, and a UL EHT TB PPDU MFB subfield 2020. In this example, bandwidth information may not be required, and the NSS subfield 2006 may include multiple bits (e.g., 4 bits). The recommended number of spatial streams may be equal to a value of Nss+1, where the value of Nss is 0 to 15.

[0191] Implementations of EHT capabilities are described herein. In one implementation, EHT link adaptation support is included in the EHT MAC Capability Information field. Fig.21 2 is a diagram illustrating an example enhanced EHT MAC capability information field format 2100, which may be used in conjunction with any of the other embodiments described herein. Fig.21As illustrated, the enhanced EHT MAC capability information field 2100 may include, but is not limited to, a subfield 2102 for supporting EPC priority access, a subfield 2104 for supporting EHT OM control, a subfield 2106 for supporting triggered TXOP sharing mode 1, a subfield 2108 for supporting triggered TXOP sharing mode 2, a subfield 2110 for supporting restricted TWT, a subfield 2112 for supporting SCS traffic description, a subfield 2114 for supporting maximum MODU length, a subfield 2116 for supporting EHT link adaptation, and a subfield 2118 for supporting reserved information.

[0192] Table 10 gives an exemplary illustration of the EHT link adaptation support subfield 2116. It should be noted that the encoding corresponding to the value of the EHT link adaptation support subfield 2116 may not be fixed, as indicated in Table 10. For example, if the STA can receive and provide only unrequested EHT MFB and the value 2 is reserved, the value of the EHT link adaptation support subfield 2116 may be set to 1.

[0193] Table 10 Example of EHT Link Adaptation Subfield

[0194]

[0195] Embodiments of HT control field operations are described herein. In one embodiment, Table 11 depicts exemplary conditions for including control subfield variant ELA.

[0196] Table 11 Conditions for including control subfield variant ELA

[0197]

[0198] Embodiments of enhanced HLA (eg, using HLA) are described herein. In one embodiment, the HEHLA control field may be modified for EHT link adaptation. Fig. 22 2200, which may be used in conjunction with any of the other embodiments described herein. Fig. 22 As illustrated, the ELA 2200 may include, but is not limited to, an unrequired MFB subfield 2202, an MRQ subfield 2204, an EHT NSS coding subfield 2206, an EHT-MCS subfield 2208, a PS160 subfield 2210, an EHT RU allocation subfield 2212, a BW subfield 2214, an MSI / partial PPDU parameter subfield 2216, a Tx beamforming subfield 2218, an UL EHT TB PPDU MFB subfield 2220, and a HE / EHT subfield 2222. Reserved bits in the HEHLA control field (e.g., in Figure 5The bit in (in) may be used to indicate that this is an HLA control field EHT variant using, for example, the HE / EHT subfield 2222. When this bit is set, the format of the HLA control field EHT variant (ELA) 2200 may be depicted as Fig. 22 Note that the number of bits allocated to each subfield may be examples and other numbers of bits are possible.

[0199] In one embodiment, the EHT NSS Coding subfield 2206 may be multiple bits (e.g., 4 bits) and may use direct mapping to indicate the recommended Nss spatial stream (i.e., the value of this subfield is set to Nss-1). In one embodiment, the EHT NSS Coding subfield 2206 may use 3 bits and may recommend the selected Nss spatial stream in the HLA Control field. Table 12 shows an exemplary encoding of the EHT NSS subfield.

[0200] Table 12: Encoding of EHT NSS Encoding Subfield

[0201] EHTNSS Encoded Field Value Nss 0 1 1 2 2 4 3 6 4 8 5 10 6 12 7 16

[0202] The EHT MCS 2208 subfield may indicate the recommended EHT MCS.

[0203] The PS160 subfield 2210 and the EHT RU allocation subfield 2212 may be used together to indicate the RU and / or multiple RUs (MRUs) for which the MCS / Nss is recommended or requested. The PS160 subfield 2210 set to 1 may indicate a RU / MRU located in or partially located in the primary 160MHz subchannel. The PS160 subfield 2210 set to 0 may indicate a RU / MRU located in or partially located in the secondary 160MHz subchannel. The encoding of the PS160 subfield 2210 and the EHT RU allocation subfield 2212 may follow the PPDU type defined for the EHT trigger frame in 802.11be. The PPDU type may correspond to the recommended MCS and Nss. In one embodiment, the EHT RU allocation subfield 2212, the BW subfield 2214, and the PS160 subfield 2210 may identify the size and location of the RU / MRU.

[0204] In one embodiment, the BW subfield 2214 may be reserved in the EHT variant (ELA). Alternatively or additionally, these 2 bits may be used by other methods or procedures described in this disclosure.

[0205] In one embodiment, the MSI / Partial PPDU Parameters subfield 2216 may indicate the parameters of the measured PPDU for which the MCS and Nss are recommended when it is required feedback (e.g., the Unrequired MFB 2202 is 0), and may also indicate the parameters of the PPDU for which the MCS and Nss are recommended when it is not required feedback (e.g., the Unrequired MFB 2202 is 1). In one embodiment, if the Unrequired MFB subfield 2202 is 1 or true, the MSI / Partial PPDU Parameters subfield 2216 may include the EHT PPDU Format and Coding Type subfield. The encoding of the first two bits of the MSI / Partial PPDU Parameters subfield 2216 is given in Table 13.

[0206] Table 13: Coding of the first two bits of the MSI / Partial PPDU Parameters subfield

[0207] value EHTPPDU format PPDU Type Notes 0 EHTMUPPDU 0 DLOFDMA 1 EHTMUPPDU 1 DL / UL transmission to a single user or NDP 2 EHTMUPPDU 2 DLMU-MIMO 3 EHTTB Any TB Send

[0208] The UL EHT TB PPDU MFB subfield 2220 may indicate that the Nss, EHT-MCS, BW, and RU allocation fields represent the recommended MFB for the EHT TB PPDU transmitted from the STA. For example, when the unrequired MFB subfield 2202 is 1, the value 1 in the UL EHT TB PPDU MFB subfield 2220 may indicate that the EHT NSS coding subfield 2206, the EHT-MCS subfield 2208, the BW subfield 2214, and the EHT RU allocation subfield 2212 represent the recommended MCS feedback (MFB) for the EHT TB PPDU transmitted from the STA. When the Unrequired MFB subfield 2202 is 1, a value of 0 in the UL EHT TB PPDU MFB subfield 2220 may indicate that the EHT NSS Coding subfield 2206, the EHT-MCS subfield 2208, the BW subfield 2214, and the EHT RU Allocation subfield 2212 represent the recommended MFB for the EHT MU PPDU transmitted from the STA.

[0209] The HE / EHT subfield 2222 may indicate whether it is a HE variant (HLA) or an EHT variant (ELA). In other words, the HE / EHT subfield 2222 may indicate whether the STA provides feedback (or PPDU) in HE format or EHT format. The HE / EHT subfield 2222 may also indicate whether the A control field is HLA or ELA. For example, when the HE / EHT subfield 2222 is set to 0, it may indicate HLA. When the HE / EHT subfield 2222 is set to 1, it may indicate ELA. Alternatively or additionally, there may be N bits, where N>=1, for indicating different versions of link adaptation.

[0210] Embodiments of enhanced unsolicited MCS feedback (MFB) requirements are described herein. In one embodiment, a STA may transmit an unsolicited MFB for a received PPDU within a certain amount of time xμs (e.g., xμs=SIFS duration) after receiving a PPDU measured / estimated for a recommended MCS / Nss, etc. Alternatively or additionally, the STA may transmit an unsolicited MFB for a received PPDU measured / estimated within the same TXOP. Alternatively or additionally, the STA may transmit an unsolicited MFB when the measured PPDU is sent to a single user or a null data packet (NDP) transmission. In other words, one bit of the MCS request (MRQ) sequence identifier (MSI) / partial PPDU parameter subfield may be used to indicate that the estimated PPDU is an EHT MUPPDU or an EHT TB PPDU. For example, when the one bit is set to 1, the bit may indicate that the estimated PPDU is an EHT MUPPDU; and / or when the bit is set to 0, the bit may indicate that the estimated PPDU is an EHT TB PPDU.

[0211] Embodiments of ELA operations are described herein. Fig.23A is a diagram illustrating an example requested MCS feedback operating procedure 2300, which may be used in conjunction with any of the other embodiments described herein. Fig. 23B 2350, which may be used in conjunction with any of the other embodiments described herein. These example ELA operation procedures may use an ELA Control subfield including a Requested MCS Feedback (MFB) indication and / or an Unrequested MFB indication. In one embodiment, a frame exchange sequence may include a PPDU that includes a HE variant HT Control field (i.e., an ELA Control subfield). An example ELA operation sequence using the ELA Control subfield is shown in FIG. Fig.23A and Fig. 23B Described in.

[0212] exist Fig.23AIn the illustrated case of requested MFB, the MFB requester STA12302 may transmit a PPDU 2310 to the MFB responder STA22304, specifying the RU index and BW for requesting link adaptation feedback. Upon receiving the ELA control subfield with the MRQ subfield equal to 1, STA22304 may calculate the EHT-MCS and Nss for the RU and BW specified in the MRQ, and these estimates may be based on the same RU of the PPDU carrying the MRQ. The PPDU 2310 carrying the MRQ may include the RU for the MFB request. STA22304 may include the estimated EHT-MCS, Nss for the RU and BW specified in the received MRQ in the ELA control subfield carried in the PPDU 2315. The MFB responder STA22304 may mark the result of the calculation using the MSI value of the ELA control subfield from the received frame carrying the MRQ. The MFB responder STA22304 may include the received MSI value in the MSI field of the corresponding response frame. Fig. 23B In the illustrated case of unsolicited MFB, STA22354 may transmit an unsolicited MFB, where the unsolicited MFB subfield (in the ELA Control subfield) is equal to 1. The unsolicited EHT-MCS, Nss, BW, and RU estimates reported in the ELA Control subfield transmitted by STA22354 may be calculated based on the most recent PPDU received by STA22354 (e.g., transmitted by STA12352), which matches the description indicated by the PPDU Format, Tx Beamforming, and Coding Type subfields in the ELA Control subfield. For example, STA22354 may determine estimates of EHT-MCS, Nss, BW, and RU based on the most recently received PPDU (e.g., PPDU 2360 received from STA12352), and report these estimates in the ELA Control subfield to the STA (e.g., STA12352) that transmitted the PPDU (e.g., PPDU 2360). Estimates of EHT-MCS, Nss, BW, and RU may be included in the PPDU 2365. The PPDU 2365 transmitted by the STA2 2364 may indicate the PPDU format, Tx beamforming, and coding type of the most recently received PPDU (eg, the PPDU 2360 received from the STA1 2352).

[0213] In one embodiment, if Fig.23AAs illustrated, STA12302 (i.e., MFB requester) may send a first PPDU 2310 to STA22304 (i.e., MFB responder), the first PPDU including an A control field with an ELA control subfield. The ELA control subfield may include an unrequested MFB subfield, an MRQ subfield, an EHT NSS coding subfield, an EHT-MCS subfield, a PS160 subfield, an EHTRU allocation subfield, a BW subfield, an MSI / partial PPDU parameter subfield, a Tx beamforming subfield, a ULEHTTBPDUMFB subfield, and a HE / EHT subfield. STA12302 may set the unrequested MFB subfield to 0 (i.e., false), set the MRQ subfield to 1 (i.e., true), and set the HE / EHT subfield to 1 (i.e., true) to indicate to STA22304 that the first PPDU 2310 will request / require ELA feedback from STA22304 for link adaptation. The EHT RU Allocation subfield of the first PPDU 2310 may include one or more RUs that the STA 22304 will measure for ELA feedback. The BW subfield of the first PPDU 2310 may include the BW that the STA 22304 will measure for ELA feedback. The PS160 subfield of the first PPDU 2310 may indicate that the STA 22304 will measure the primary 160 MHz channel and the secondary 160 MHz channel for ELA feedback.

[0214] Once STA22304 receives the first PPDU 2310 from STA12302, STA22304 may measure the channel condition / quality based on one or more RUs of the EHTRU allocation subfield, the BW of the BW subfield, and / or the 160MHz channel indicated by the PS160 subfield. In one example, STA22304 may identify the size and location of the RU / MRU based on these three subfields or at least one of these three subfields. Then, STA22304 may determine the recommended EHT-MCS and the recommended number of spatial streams (Nss) for ELA feedback to STA12302 based on the channel condition / quality. STA22304 may send a second PPDU2315 with the recommended EHT-MCS and the recommended Nss to STA12302. Specifically, similar to the first PPDU2310, the second PPDU2315 may include an A control field with an ELA control subfield. The ELA control subfield may include an unrequested MFB subfield, an MRQ subfield, an EHTNSS coding subfield, an EHT-MCS subfield, a PS160 subfield, an EHT RU allocation subfield, a BW subfield, an MSI / partial PPDU parameter subfield, a Tx beamforming subfield, a ULEHT TB PPDUMFB subfield, and a HE / EHT subfield. STA22304 may set the EHT-MCS subfield and the EHT NSS coding subfield to the recommended EHT-MCS and the recommended Nss, respectively. STA22304 may set the unrequested MFB subfield to 0 (ie, false), the MRQ subfield to 0 (ie, false), and the HE / EHT subfield to 1 (ie, true) to indicate to STA12302 that the second PPDU 2315 is a response to the ELA feedback request from STA12302.

[0215] In one embodiment, if Fig. 23BAs illustrated, STA22354 may send PPDU2365 to STA12352 without any request / requirement from STA12352, which PPDU includes ELA feedback for link adaptation. Specifically, STA22354 may receive PPDU 2360 from STA12352. PPDU 2360 may not include any indication of MFB and / or ELA request. Regardless of the received PPDU 2360, STA22354 may determine the primary / secondary 160MHz channel, one or more RUs and / or BW to measure channel conditions / quality. Then, STA22304 may determine the recommended EHT-MCS and the recommended number of spatial streams (Nss) for ELA feedback to STA12352 based on the channel conditions / quality. STA22354 may send PPDU2365 with the recommended EHT-MCS and the recommended Nss to STA12352. Specifically, the PPDU 2365 may include an A control field with an ELA control subfield. The ELA control subfield may include an unrequested MFB subfield, an MRQ subfield, an EHT NSS coding subfield, an EHT-MCS subfield, a PS160 subfield, an EHT RU allocation subfield, a BW subfield, an MSI / partial PPDU parameter subfield, a Tx beamforming subfield, an UL EHT TB PPDU MFB subfield, and a HE / EHT subfield. STA2 2354 may set the EHT-MCS subfield and the EHT NSS coding subfield to the recommended EHT-MCS and the recommended Nss, respectively. STA2 2354 may set the unrequested MFB subfield to 1 (i.e., true) to indicate to STA1 2352 that the PPDU 2365 is unrequested ELA feedback. STA22354 may set the PS160 subfield to the determined 160MHz channel, the EHTRU allocation subfield to the determined one or more RUs, and the BW subfield to the determined BW for channel measurement. PPDU 2365 may include these three subfields to indicate to STA12360 which part of the channel STA22365 measured. Specifically, STA22354 may use these three subfields to indicate to STA12352 the RU / MRU measured by STA22354 for the recommended EHTMCS and the recommended Nss. Based on these three subfields, STA22354 may indicate the recommended EHT MCS and the recommended Nss corresponding to the RU / MRU measured by STA22354. STA22354 may provide the recommended EHT MCS and the recommended Nss based on the measurement of the most recently received PPDU or the previously received PPDU. STA22354 may provide the recommended EHTMCS and recommended Nss periodically or when STA22353 senses a change in channel conditions / quality.

[0216] Fig.24A 2400, which may be used in conjunction with any of the other embodiments described herein. In step 2405, a STA (i.e., a receiver or responder) may receive a first PPDU including an A control field. The A control field may include a control subfield, which may include an ELA control subfield. The ELA control subfield may include an unrequested MFB subfield, an MRQ subfield, an EHTNSS coding subfield, an EHT-MCS subfield, a PS160 subfield, an EHT RU allocation subfield, a BW subfield, an MSI / partial PPDU parameters subfield, a Tx beamforming subfield, a UL EHT TB PPDU MFB subfield, and a HE / EHT subfield, as shown in FIG. Fig. 22 As illustrated. The HT / EHT subfield may indicate whether the second PPDU to be sent by the STA is generated based on HE-related parameters or EHT-related parameters. EHT-related parameters may include, but are not limited to, EHT-MCS index, number of spatial streams for EHT transmission, primary / secondary 160MHz channel indication, EHTPPDU format, etc. The first PS160 subfield may indicate the primary 160MHz channel or secondary 160MHz channel that the STA will measure. For example, the first PS160 subfield may include a bit indicating the primary 160MHz channel or the secondary 160MHz channel. The STA may determine the 160MHz channel from the primary 160MHz channel and the secondary 160MHz channel based on the PS160 subfield. In one embodiment, the STA may measure the channel quality of the determined 160MHz channel. The STA (i.e., the transmitter or requester) that sends the first PPDU may be an access point (AP) or a non-AP STA.

[0217] In step 2410, the STA may determine the channel conditions based on the PS160 subfield, the EHTRU allocation subfield, and the BW subfield in the ELA control subfield. Specifically, based on the RU / MRU of the EHTRU allocation subfield and the BW indicated by the BW subfield, the STA may identify the size and location of one or more resources that the STA will measure for the channel conditions. The STA may determine, together with the PS160 subfield, that the one or more resources to be measured are located in the primary 160MHz channel or the secondary 160MHz channel. In one embodiment, the STA may read the preamble of the PPDU and measure the signal strength (e.g., RSRP, RSSI, RSRQ, etc.) or SINR of the PPDU to determine the channel conditions. In step 2415, the STA may determine the MCS index and number of spatial streams for link adaptation based on the channel conditions. These MCS indexes and the number of spatial streams may be used by another STA to encode or send data. In the case of MFB operation as required, the MSI / partial PPDU parameter subfield may include a sequence number in the range of 0 to 6 that identifies a specific EHT MCS feedback request. For example, the sequence number may indicate a PPDU received by the STA in response to an EHT MCS feedback request, and may also indicate a PPDU sent by the STA in response to an EHT MCS feedback response.

[0218] In step 2420, the STA may transmit a second PPDU with the determined MCS index and number of spatial streams. The second PPDU may include an A control field with an ELA control subfield. The ELA control subfield may include an unrequested MFB subfield, an MRQ subfield, an EHT NSS coding subfield, an EHT-MCS subfield, a PS160 subfield, an EHT RU allocation subfield, a BW subfield, an MSI / partial PPDU parameter subfield, a Tx beamforming subfield, an UL EHT TB PPDU MFB subfield, and a HE / EHT subfield. The STA may set the EHT-MCS subfield to the MCS index and the EHT NSS coding subfield to the number of spatial streams. In the second PPDU, the PS160 subfield, the EHT RU allocation subfield, and the BW subfield may indicate to another STA which part of the channel the STA measured. Specifically, the PS160 subfield may indicate that the primary or secondary 160MHz channel is selected for measurement. The EHT RU allocation and BW may indicate the size and location of one or more resources measured on the selected 160 MHz channel.

[0219] Fig. 24Bis a diagram illustrating another example unsolicited MFB operation procedure 2450, which may be used in conjunction with any of the other embodiments described herein. In step 2450, the STA may autonomously determine the channel condition based on the most recently received PPDU or one or more of the previously received PPDUs. In step 2455, the STA may determine the MCS index and the number of spatial streams based on the channel conditions. In step 2460, the STA may send a PPDU including an A control field. The A control field may include a control subfield, which may include an ELA control subfield. The ELA control subfield may include an unsolicited MFB subfield, an MRQ subfield, an EHT NSS encoding subfield, an EHT-MCS subfield, a PS160 subfield, an EHT RU allocation subfield, a BW subfield, an MSI / partial PPDU parameter subfield, a Tx beamforming subfield, a UL EHT TB PPDUMFB subfield, and a HE / EHT subfield, such as Fig. 22 As illustrated. The SAT may set the EHT-MCS subfield to the determined MCS index and the EHT NSS coding subfield to the determined number of spatial streams. The STA may set the HT / EHT subfield to a value / bit / indication indicating that the PPDU sent by the STA is generated based on EHT-related parameters. EHT-related parameters may include, but are not limited to, EHT-MCS, the number of spatial streams used for EHT transmission, primary / secondary 160 MHz channel indication, EHT PPDU format, etc. The STA may set the PS160 subfield, the EHT RU allocation subfield, and the BW subfield to indicate to another STA the portion of the channel measured by the STA. Specifically, the PS160 subfield may indicate whether the primary or secondary 160 MHz channel is selected for measurement. The EHT RU allocation and BW may indicate the size and location of one or more resources measured by the STA on the selected 160 MHz channel. In the case where MFB operation is not required, the STA may set the MSI / partial PPDU parameter subfield to one or more values / bits / indications indicating the type / format of the PPDU measured by the STA and / or the type of decoding applied by the STA. For example, the type / format of the PPDU may be a TB PPDU or a MU PPDU. The decoding type may be a binary convolutional code (BCC) and / or a low-density parity check (LDPC). The STA that sends the PPDU with the MCS index and the number of spatial streams may be an access point (AP) or a non-AP STA.

[0220] An implementation of an enhanced unsolicited MFB in a HE device is described herein. In this implementation, it is described how to enhance the current unsolicited MFB to differentiate between MCS / SS feedback for MU-MIMO and OFDMA for HE devices. B25 in the control information subfield in the HLA control subfield may be used to indicate whether the estimated PPDU is being transmitted using MU-MIMO or OFDMA. In other words, when the unsolicited MFB subfield is equal to 1, this bit may be used to indicate whether the recommended HE-MCS, Nss, DCM, BW, and RU estimates reported in the HLA control subfield are for the most recently received PPDU transmitted using OFDMA or MU-MIMO. For example, in the case of an unsolicited MFB (i.e., the unsolicited MFB subfield is equal to 1), when the PPDU format is HE_MU and B25=1, it may refer to an estimate based on a PPDU transmitted via MU-MIMO; when the PPDU format is HE_MU and B25=0, it may refer to an estimate based on a PPDU transmitted via OFDMA. Note that the actual B25 value corresponding to MU-MIMO transmission or OFDMA transmission may vary.

[0221] Embodiments for enhanced MU-MIMO link adaptation are described herein. In these embodiments, MU-MIMO link adaptation via feedback indication is described. In one embodiment, when the Unrequired MFB subfield is equal to 1, one bit (e.g., B25) in the Control Information subfield in the HLA Control subfield may be used to indicate which group of STAs are paired with the receiving STA of the estimated PPDU with HE-MU format. For example, in the case where MFB is not requested (i.e., the MFB not requested subfield is equal to 1), when the most recently received PPDU format is HE_MU and B25=1, the estimated receiver as the transmitter of the estimated PPDU can understand that the estimation is based on the PPDU transmitted via MU-MIMO, and the MU-MIMO transmission is grouped by the STA belonging to group 1 and the transmitter without MFB requested; when the most recently received PPDU format is HE_MU and B25=0, the estimated receiver as the transmitter of the estimated PPDU can understand that the estimation is based on the PPDU transmitted via MU-MIMO, and the MU-MIMO transmission is grouped by the STA belonging to group 0 and the transmitter without MFB requested. If the estimated PPDU format is HE_MU and most of the received PPDUs are transmitted via OFDMA, B25 can be retained. In other words, when the estimated PPDU format is HE_MU and the PPDU most recently transmitted to the estimated transmitter is transmitted via OFMDA, the receiver of the transmitter of the most recent PPDU of the recommended MCS, Nss, DCM, BW, and RU may not ignore B25. Fig. 20 When the Unrequired MFB subfield is equal to 1, the Control Information subfield in the ELA Control subfield may be used to indicate which group of STAs are paired with the receiving STA of the estimated PPDU with the EHT-MU format.

[0222] Embodiments of enhanced confirmation transmission are described herein. In one embodiment, one or more bits in the confirmation frame may be used to indicate a suggested or requested increase and / or decrease in the MCS or information related to link adaptation. This may be referred to as simplified link adaptation. In one example, in a downlink transmission, the AP may use MCS n to send a frame to the STA. By successfully or correctly detecting the DL transmission, the STA may suggest that the AP use MCS n+1 (i.e., one level higher) or higher MCS or MCS n-1 (i.e., one level lower) or lower MCS for the next transmission in the confirmation frame. The AP may follow the suggestion or reject the suggestion in the next transmission.

[0223] In one example, in a non-trigger-based (non-TB) uplink transmission, a non-AP STA may send a frame to the AP using MCS n. By successfully detecting the UL transmission, the AP may suggest / request the STA to use MCS n+1 (i.e., one level higher) or MCS n-1 (i.e., one level lower) in the confirmation frame. The STA may follow the suggestion or reject the suggestion in the next transmission.

[0224] The suggested MCS may be used for any TID sent or TID indicated in an acknowledgement frame, for example, the TID Information subfield in the BA Control field in a Block Acknowledgement frame.

[0225] Implementations of a modified BA Control field are described herein. Fig.25 2 is a diagram illustrating an example Link Adaptation Enhanced BA Control field 2500, which may be used in conjunction with any of the other embodiments described herein. Fig.25 As illustrated, the enhanced BA control field may include, but is not limited to, a BA confirmation policy subfield 2505, a BA type subfield 2510, a link adaptation indication (LAI) subfield 215, a reserved subfield 2520, and a TID-INFO subfield 2525. In one embodiment, the enhanced BA control field may include, but is not limited to, a BA confirmation policy subfield 2505, a BA type subfield 2510, a link adaptation indication (LAI) subfield 215, a reserved subfield 2520, and a TID-INFO subfield 2525. Fig.25 The BA control field in the block confirmation frame is modified as shown. The LAI subfield 2515 may be included in the enhanced BA control field 2500. The LAI subfield 2515 may indicate that the BA frame carries link adaptation related information.

[0226] In one embodiment, the LAI subfield 2515 may be a 1-bit subfield. If the STA transmitting the BA frame may suggest the BA receiving STA to increase the MCS for the next transmission, the LAI subfield may be set to 1 (or 0). If the STA transmitting the BA frame may suggest the BA receiving STA to reuse the same MCS for the next transmission, the LAI subfield may be set to 0 (or 1).

[0227] In one embodiment, the LAI subfield 2515 may be a 1-bit subfield. If the STA transmitting the BA frame may suggest the BA receiving STA to reduce the MCS for the next transmission, the LAI subfield may be set to 1 (or 0). If the STA transmitting the BA frame may suggest the BA receiving STA to reuse the same MCS for the next transmission, the LAI subfield may be set to 0 (or 1).

[0228] In one embodiment, the LAI subfield 2515 may be a 2-bit (or multi-bit) subfield with four or more possible values. If the STA transmitting the BA frame may suggest the BA receiving STA to increase the MCS for the next transmission, the LAI subfield may be set to a value of 1. If the STA transmitting the BA frame may suggest the BA receiving STA to decrease the MCS for the next transmission, the LAI subfield may be set to a value of 2. If the STA transmitting the BA frame may suggest the BA receiving STA to reuse the same MCS for the next transmission, the LAI subfield may be set to a value of 3.

[0229] In this embodiment, the LAI subfield 2515 may be located in the BA Control field, which is carried in all Block Acknowledgement variants, and thus all Block Acknowledgement variants may be used to simplify link adaptation.

[0230] This document describes an implementation scheme of a modified multi-STA block confirmation variant. In one embodiment, the multi-STA block confirmation frame may be modified to carry a link adaptation indication. For example, when the AID11 subfield is not 2045, the per-AID TID information subfield in the BA information field for the multi-STA block confirmation variant may be modified, and a new combination of the confirmation type subfield and the TID subfield value may be used to carry a link adaptation indication. Table 14 shows an example in which a new combination of confirmation type subfield = 0 and TID subfield = 14 may be used to indicate all confirmation contexts and a higher MCS level is recommended for the next transmission. The existing combination of confirmation type subfield = 1 and TID subfield = 14 may be modified to indicate all confirmation contexts and to recommend that the MCS for the next transmission not be changed. Note that the combinations described here are by way of example, and other reserved combinations may be used for the same purpose.

[0231] Table 14: Context and optional subfields of the per-AID TID information subfield when the AID11 subfield is not 2045 Exemplary new and modified combinations exist

[0232]

[0233] Embodiments of modified compressed block acknowledgments are described herein. The BA information field of the block acknowledgment compressed block acknowledgment variant may include a block acknowledgment starting sequence control subfield and a block acknowledgment bitmap subfield. The block acknowledgment starting sequence control subfield may include a 4-bit (or multiple-bit) fragment number subfield and a 12-bit (or multiple-bit) starting sequence number subfield. In one embodiment, one or more reserved values ​​in the fragment number subfield may be used to indicate simplified link adaptation information. One or more of the methods described below may be used:

[0234] (1) One reserved value in the fragment number subfield (eg, [B0:B3]=

[1001] ) may indicate all acknowledgement contexts, and a higher MCS level is suggested for the next transmission.

[0235] A reserved value in the Fragment Number subfield (e.g., [B0:B3] =

[1011] ) may indicate all acknowledgement contexts and the same MCS level is recommended for the next transmission. In both cases, the Block Acknowledgement Bitmap field may not be present;

[0236] (2) A reserved value in the Fragment Number subfield (e.g., [B0:B3]=

[1001] ) may indicate that a higher MCS level is recommended for the next transmission. A reserved value in the Fragment Number subfield (e.g., [B0:B3]=

[1011] ) may indicate that the same MCS level is recommended for the next transmission.

[0237] =

[1101] ) may indicate that a lower MCS level is suggested for the next transmission. In all cases, the Block Ack Bitmap field may be present; and / or

[0238] (3) One reserved value in the fragment number subfield (eg, [B0:B3]=

[1001] ) may indicate all acknowledgement contexts, and the block acknowledgement bitmap field may not be present.

[0239] Embodiments of modified multi-TID block acknowledgements are described herein. The BA information field of the multi-TID block acknowledgement variant may include a 2-octet per-TID information subfield and a 2-octet block acknowledgement start sequence control subfield and a block acknowledgement bitmap subfield. In one embodiment, the block acknowledgement start sequence control may be modified as described above. In one embodiment, the per-TID information subfield may be modified to carry simplified link adaptation information. One or more of the methods described below may be used:

[0240] (1) One reserved value in each TID Information subfield may indicate all acknowledgement contexts, and a higher MCS level is recommended for the next transmission with or without regard to the TID identified in the TID Value subfield. One reserved value in each TID Information subfield may indicate all acknowledgement contexts, and the same MCS level is recommended for the next transmission with or without regard to the TID identified in the TID Value subfield. In both cases, the Block Ack Bitmap field may not be present;

[0241] (2) A reserved value in each TID Information subfield may indicate that a higher MCS level is recommended for the next transmission with or without the TID identified in the TID Value subfield. A reserved value in each TID Information subfield may indicate that the same MCS level is recommended for the next transmission with or without the TID identified in the TID Value subfield. A reserved value in each TID Information subfield may indicate that a lower MCS level is recommended for the next transmission with or without the TID identified in the TID Value subfield. In all cases, the Block Ack Bitmap field may be present; and / or

[0242] (3) One reserved value in each TID Information subfield may indicate all ACK contexts, and the Block ACK Bitmap field may not be present.

[0243] It should be noted that all confirmation contexts described in this embodiment may be confirmations of an A-MPDU that includes an MPDU requiring an immediate response and all MPDUs included in the A-MPDU are successfully received.

[0244] Embodiments of enhanced triggered response scheduling are described herein. In one embodiment, the existing HE TRS control field may be modified and reused for EHT triggered response scheduling.

[0245] In one embodiment, a reserved bit in the HE TRS Control field may be used to indicate whether the RU Allocation subfield carried in the TRS Control field is primarily located in the primary 160 MHz or the secondary 160 MHz. This bit may be denoted as the PS160 subfield. Using the RU Allocation subfield and the PS160 subfield, the STA may be able to determine the RU and / or MRU allocated for the response transmission.

[0246] In one embodiment, the PS160 subfield may not be present in the TRS control field. Instead, the RXVECTOR parameter PS160 may be defined. A first STA may send the TRS control field to a second STA in an EHT MU PPDU. In the EHT MU PPDU, if the first STA uses a 4x996 tone RU, the second STA may set the RXVECTOR parameter PS160 to 0, which may indicate the primary 160 MHz or the lower frequency 160 MHz subchannel. Alternatively or additionally, the second STA may set the RXVECTOR parameter PS160 to 1, which may indicate the secondary 160 MHz or the higher frequency 160 MHz subchannel.

[0247] For other RUs or MRUs, the second STA may determine the number of subcarriers / tone in the RU / MRU in the primary (or lower) and secondary (or higher) 160 MHz subchannels, represented by N_(p,160) and N_(s,160) respectively. If N_(p,160) > N_(s,160), the second STA may set the RXVECTOR parameter PS160 to 0, which may indicate the primary 160 MHz or the lower frequency 160 MHz subchannel. If N_(p,160) < N_(s,160), the second STA may set the RXVECTOR parameter PS160 to 1, which may indicate the secondary 160 MHz or the higher frequency 160 MHz subchannel. If N_(p,160) = N_(s,160), the second STA may set the RXVECTOR parameter PS160 to 0, which may indicate the primary 160 MHz or the lower frequency 160 MHz subchannel. Alternatively or additionally, the second STA may set the RXVECTOR parameter PS160 to 1, which may indicate the secondary 160 MHz or the higher frequency 160 MHz subchannel.

[0248] In an alternative or additional embodiment, the RXVECTOR parameter PS160 may not be defined. Instead, the TXVECTOR parameter PS160 may be defined. The second STA may directly set the TXVECTOR parameter PS160 based on the allocated RU / MRU and the Np,160 and Ns,160 values following the above rules.

[0249] In an alternative or additional embodiment, the PS160 subfield may not be present in the Trigger Response Scheduling (TRS) control field. Instead, the RXVECTOR parameter PS160 (or internal parameter PS160) may be defined. Alternatively or additionally, the RXVECTOR parameters N_P160 and N_S160 may be defined. The first STA may send the TRS control field to the second STA in the EHT MU PPDU.

[0250] In an EHT MU PPDU, if the size of the RU / MRU carrying the TRS Control subfield is less than or equal to 2x996 tones, the RXVECTOR parameter PS160 may be set to 0 if the RU / MRU is allocated to a primary 160 MHz channel. The RXVECTOR parameter PS160 may be set to 1 if the RU / MRU is allocated to a secondary 160 MHz channel. The RXVECTOR parameters N_P160 and N_S160 may be set to the number of tones of the RU / MRU carrying the TRS Control subfield in the primary 160 MHz channel and the secondary 160 MHz channel, respectively.

[0251] In an EHT MU PPDU, if the size of the RU / MRU carrying the TRS Control subfield is greater than 2x996 tones, the RXVECTOR parameters N_P160 (or internal parameter N_P160) and N_S160 (or internal parameter N_S160) may be set to the number of tones of the RU / MRU carrying the TRS Control subfield in the lower 160 MHz channel and the upper 160 MHz channel, respectively. If N_P160 is greater than or equal to N_S160, the RXVECTOR parameter PS160 may be set to 0. If N_P160 is less than N_S160, the RXVECTOR parameter PS160 may be set to 1.

[0252] Alternatively or additionally, Table 15 may be used to determine the RXVECTOR parameter PS160 (or internal parameter PS160). In the case where the RU allocation subfield may not be carried in the PPDU carrying the TRS control subfield, the receiver (e.g., the second STA) may determine the location of the RU / MRU through the BW field and the perforated channel information field carried in the U-SIG field of the PPDU. In the case where the PPDU may be a legacy PPDU (e.g., any revision before 802.11be), PS160 may be set to 0. If more RUs or MRUs are defined or allowed in the future, the table may be extended and the PS160 value may be uniquely determined by the location of the RU / MRU.

[0253] Table 15: Example table for obtaining PS160 when the bandwidth of the PPDU carrying the TRS Control subfield is 320 MHz

[0254]

[0255] The second STA may send an EHT TB PPDU in response to a frame with a TRS Control subfield. The second STA may set the TXVECTOR parameter RU_ALLOCATION to the value of the RU Allocation subfield of the TRS Control subfield. The second STA may set the TXVECTOR parameter PS160 to the value of the RXVECTOR parameter PS160. The second STA may determine the allocated RU by using the TXVECTOR parameter RU_ALLOCATION parameter and the RXVECTOR parameter PS160 together.

[0256] Alternatively or additionally, the second STA may set the first part (e.g., the first 8 bits) of the TXVECTOR parameter RU_ALLOCATION to the value of the RU allocation subfield of the TRS control subfield. The second STA may set the second part (e.g., the 9th bit) of the TXVECTOR parameter RU_ALLOCATION to the value of the RXVECTOR parameter PS160 (or internal parameter PS160). Note that the bit index is described herein as an example. It may include any value, bit, or number representing an index or multiple indexes. Alternatively or additionally, the second STA may set the TXVECTOR parameter RU_ALLOCATION based on the RU allocation subfield of the TRS control subfield and the RXVECTOR parameter PS160 (or internal parameter PS160).

[0257] The above embodiments may be used for an EHT TB PPDU response to a frame carrying a TRS control field. In one embodiment, the TXVECTOR parameter PS160 may be used in a procedure for an EHT TB PPDU response to a trigger frame. For example, a second STA may receive a trigger frame from a first STA. The second STA may set the TXVECTOR parameter PS160 to the value of the PS160 subfield in the trigger frame. In another embodiment, the second STA may set the first part (e.g., the first 8 bits) of the TXVECTOR parameter RU_ALLOCATION to the value of the RU allocation subfield of the trigger frame. The second STA may set the second part (e.g., the 9th bit) of the TXVECTOR parameter RU_ALLOCATION to the value of the PS160 subfield of the trigger frame.

[0258] In one embodiment, the first STA may be an AP and the second STA may be a non-AP STA. In another embodiment, the first STA may be a non-AP STA and the second STA may be an AP. In another embodiment, the first STA may be a non-AP STA and the second STA may be another non-AP STA.

[0259] Although features and elements of the invention are described in particular combinations in the preferred embodiments, each feature or element can be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements of the invention.

[0260] Although the embodiments described herein consider the 802.11 specific protocol, it should be understood that the embodiments described herein are not limited to this scenario and are also applicable to other wireless systems.

[0261] Although SIFS is used in the design and program examples to represent various interframe spacings, all other interframe spacings such as RIFS, AIFS, DIFS, or other agreed time intervals are applicable to the same solution.

[0262] Although four RBs per triggered TXOP are shown as an example in some figures, the actual number of RBs / channels / bandwidth used may vary.

[0263] For example, although specific bits are used to signal in-BSS / OBSS, other bits may be used to signal this information.

[0264] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method used in a station (STA), the method include: receiving, from another STA, a first physical layer protocol data unit (PPDU) including a first aggregation control (A Control) field, the first aggregation control (A Control) field including a high efficiency (HE) / extremely high throughput (EHT) subfield and a first primary secondary (PS) 160 subfield, wherein the HT / EHT subfield indicates whether a second PPDU to be sent by the STA is based on HE-related parameters or EHT-related parameters, and the first PS 160 subfield indicates a primary 160 MHz channel or a secondary 160 MHz channel; as well as Based on the HE / EHT subfield, a second PPDU including a second A control field is sent to the other STA, wherein the second A control field includes a second PS160 subfield, an EHT-modulation and coding scheme (MCS) subfield, and a number of spatial streams (NSS) subfield, wherein the second PS160 subfield indicates a 160 MHz channel determined from the primary 160 MHz channel and the secondary 160 MHz channel based on the indication of the first PS160 subfield, wherein the index in the EHT-MCS subfield and the value in the NSS subfield are determined based on measurement of the determined 160 MHz channel.

2. The method of claim 1, wherein the second A control field further comprises an unsolicited MCS feedback (MFB) subfield, a resource unit (RU) allocation subfield, a bandwidth (BW) subfield, and an MCS request sequence index (MSI) / partial PPDU parameter subfield.

3. The method according to claim 2, further comprising: include: Determine, based on the one or more RUs indicated in the RU allocation subfield and the BW indicated in the BW subfield, a size and a position of the one or more RUs in the 160 MHz channel to measure channel quality; as well as Based on the channel quality, the index of the EHT-MCS subfield and the value of the NSS subfield are determined for sending the second PPDU to the other STA.

4. The method of claim 3, wherein the one or more RUs in the RU allocation subfield are RUs or multiple RUs (MRUs), the index is an EHT MCS index, and the value represents the number of spatial streams.

5. The method according to claim 2, in, Under the condition that the unrequested MFB is zero (0) or false, the MSI / partial PPDU parameter subfield includes a sequence number indicating a PPDU received by the STA for an EHT MCS feedback request or a PPDU sent by the STA for an EHT MCS feedback response.

6. The method according to claim 2, in, Under the condition that the Unrequired MFB is one (1) or true, the MSI / Partial PPDU Parameters subfield includes a value indicating the EHT PPDU format and coding type for channel quality measurement of the STA. 7 . The method of claim 6 , wherein the EHT PPDU format comprises an EHT multi-user (MU) PPDU and an EHT triggered-based (TB) PPDU, and the coding type comprises a binary convolutional code (BCC) and a low-density parity check (LDPC).

8. The method of claim 1, wherein the HE / EHT subfield received in the first A-Control field indicates to the STA that the EHT-related parameters are indicated in the second A-Control field of the second PPDU. 9 . The method according to claim 1 , wherein the EHT-related parameters include the index, the value, a primary / secondary 160 MHz channel indication, and an EHT PPDU format.

10. The method of claim 1, wherein the another STA is an access point (AP) or a non-AP STA.

Images