Terminal device and communication method

Abstract

To achieve efficient communication. [Solution] When the trigger frame is a UHR variant, the terminal device determines the value of N, which indicates the 80MHz frequency subblock where the RUs are placed, from the Bandwidth, the Configuration which indicates the frequency sequence of P80, S80, and S160, the PS160 subfield, and the value set in the bit corresponding to B0 of the RU Allocation subfield. Based on the value of N and the DRU / RRU Indication subfield which indicates the RU type for the 80MHz frequency subblock corresponding to the Bandwidth, the terminal device determines the RU type of the 80MHz frequency subblock corresponding to the value of N.

Description

Technical Field

[0001] The present invention relates to a terminal device and a communication method.

Background Art

[0002] The IEEE (The Institute of Electrical and Electronics Engineers Inc.) is considering accelerating wireless LAN (Local Area Network) communication and improving frequency utilization efficiency. Currently, the standardization of IEEE802.11bn has been started as a successor standard to IEEE802.11be.

Prior Art Documents

Non-Patent Documents

[0003] IEEE802.11-23 / 1919r0, LG Electronics, “dRU proposal”, November 2023.

Summary of the Invention

Problems to be Solved by the Invention

[0004] To provide a terminal device and a communication method capable of efficient communication.

Means for Solving the Problems

[0005] (1) A first aspect is a terminal device including a receiving unit that receives a Trigger frame, and a transmitting unit that transmits a PPDU corresponding to the Trigger frame. When the Trigger frame is a UHR variant, the transmitting unit determines the Bandwidth from the values set in the UL BW subfield and the UL Bandwidth Extension subfield included in the Trigger frame, and the frequency arrangement of P80, S80, and S160 obtained from the Operation element included in the Bandwidth and the Beacon frame The Configuration, PS160 subfield, and RU Allocation subfield corresponding to B0 shown. From the value set in the bit, the value of N, which indicates the 80MHz frequency subblock where the RU used to transmit the PPDU is located, is determined, and the value of N and the Bandwidth are used Based on the DRU / RRU Indication subfield, which indicates the RU type for each of the one or more 80MHz frequency subblocks, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined, and if the RU type indicates RRU, the value of N is used to determine the PHY RU index. If the RU type indicates DRU, the value of N is used to determine the DBW frequency subblock index.

[0006] (2) The second embodiment is a terminal device, wherein the transmitting unit determines the RU type of the 80MHz frequency subblock corresponding to the value of N from the value of the first bit of the bitmap set in the DRU / RRU Indication subfield, and if the value of N is 1 In this case, of the bitmaps set in the DRU / RRU Indication subfield, the second The RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the bit of N. If the value of N is 2, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the third bit of the bitmap set in the DRU / RRU Indication subfield. If the value of N is 3, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the fourth bit of the bitmap set in the DRU / RRU Indication subfield.

[0007] (3) The third embodiment is a terminal device, wherein, when the RU type is DRU, the table of the RU Allocation subfield is determined according to the DBW indicated by the DRU distribution BW subfield included in the SS Allocation subfield.

[0008] (4) The fourth aspect is a terminal device, wherein the transmitting unit is the RU Allocation subfield From the values ​​set in the bits corresponding to B5-B1, the RU size and The RU index is determined and set in the bits corresponding to B7-B6 of the RU Allocation subfield. From the obtained values, the value of M is determined, which indicates the DBW location for distributing the RU within the 80MHz frequency subblock where the RU is located.

[0009] (5) The fifth embodiment is a terminal device, wherein the transmitting unit determines the RU size, RU index, and value of M indicating the location of the DBW to be allocated to the DBW from the values ​​set in the bits corresponding to B7-B1 of the RU Allocation subfield.

[0010] (6) The sixth aspect is a terminal device, wherein the transmitting unit is the DBW frequency subblock The index is determined from the DBW, the value of N, and the value of M, and the subcarrier index in which the RU is located is determined from the constant shift value corresponding to the DBW frequency subblock index and the RU index.

[0011] (7) The seventh aspect is a communication method comprising the steps of receiving a trigger frame, transmitting a PPDU corresponding to the trigger frame, and, if the trigger frame is a UHR variant, determining the Bandwidth from the values ​​set in the UL BW subfield and UL Bandwidth Extension subfield included in the trigger frame, and the Bandwidth, Beacon The steps include determining the value of N, which represents the 80MHz frequency subblock where the RU used to transmit the PPDU is located, from the values ​​set in the bit corresponding to B0 of the Configuration, PS160 subfield, and RU Allocation subfield, which represent the frequency sequences of P80, S80, and S160 obtained from the Operation element contained in the frame, and the steps of determining the value of N and the Bandwidth The method includes the steps of: determining the RU type of an 80MHz frequency subblock corresponding to the value of N, based on a DRU / RRU Indication subfield indicating the RU type for each of the corresponding 80MHz frequency subblocks; using the value of N to determine the PHY RU index if the RU type indicates RRU; and using the value of N to determine the DBW frequency subblock index if the RU type indicates DRU.

Advantages of the Invention

[0012] Efficient communication can be achieved.

Brief Description of the Drawings

[0013] [Figure 1] It is a diagram showing an example of a wireless LAN system according to an aspect of this embodiment. [Figure 2] It is a diagram showing an example of the device configuration of a STA according to an aspect of this embodiment. [Figure 3] It is a diagram showing an example of the device configuration of an AP according to an aspect of this embodiment. [Figure 4] It is a schematic diagram of PDU supported at each layer according to an aspect of this embodiment. [Figure 5] It is a diagram showing an example of the configuration when the MAC frame according to an aspect of this embodiment is a Trigger frame. [Figure 6] It is a diagram showing an example of the User Info field according to an aspect of this embodiment. [Figure 7] It is a diagram showing an example of the arrangement of RUs by the RU Allocation subfield according to an aspect of this embodiment. [Figure 8] It is a diagram showing an example of the maximum number of RUs that can be arranged for the bandwidth (CBW) of each channel according to an aspect of this embodiment. [Figure 9] It is a diagram showing an example of the configuration of an RU according to an aspect of this embodiment. [Figure 10] It is a diagram showing an example of a procedure related to the transmission of a PPDU using the dRU of a STA according to an aspect of this embodiment. [Figure 11] It is a diagram showing an example of the Special User Info field according to an aspect of this embodiment. [Figure 12] It is a diagram showing an example of the BW and BW type indicated by the UL BW subfield and the UL Bandwidth Extension subfield according to an aspect of this embodiment. [Figure 13] FIG. is an example of various fields / subfields included in the Operation element format according to an aspect of the present embodiment. [Figure 14] FIG. is an example of a Bandwidth Indication element according to an aspect of the present embodiment. [Figure 15] FIG. is an example of a procedure related to the transmission of the Capabilities element for UL MU operation according to an aspect of the present embodiment. [Figure 16] FIG. is an example of a procedure of an AP for UL MU operation according to an aspect of the present embodiment. [Figure 17] FIG. is an example of a table used for the RU Allocation subfield when the RU type according to an aspect of the present embodiment is RRU. [Figure 18] FIG. is an example of a table used for the RU Allocation subfield when the RU type according to an aspect of the present embodiment is DRU. [Figure 19] FIG. is an example of a constant shift according to an aspect of the present embodiment. [Figure 20] FIG. is an example of a procedure for determining the RU type according to an aspect of the present embodiment. [Figure 21] FIG. shows the correspondence between the DBW location and the value of M according to an aspect of the present embodiment. [Figure 22] FIG. is an example of a Lookup table regarding the value of N according to an aspect of the present embodiment.

BEST MODE FOR CARRYING OUT THE INVENTION

[0014] Hereinafter, embodiments of the present invention will be described.

[0015] "A, and / or B" may be a term that includes "A", "B", or "A and B".

[0016] The wireless LAN (Local Area Network) system in this embodiment has one or more stations The wireless LAN system may be composed of STAs (Square Attacks). When configured in this way, the wireless LAN system may be referred to as a BSS (Basic Service Set). .

[0017] BSS synchronizes using one STA with START primitive and JOIN service primitive. It may also be a set of one or more successful STAs.

[0018] An STA may be a communication device that uses a wireless medium (WM). Furthermore, an STA may include an AP (Access Point) with base station functionality and / or a non-AP STA with terminal functionality. In other words, an STA may be an AP. Also, an STA may be a non-AP STA. Furthermore, an STA may refer to both an AP and a non-AP STA.

[0019] STA may be a single addressable logical entity for the MAC (Medium Access Control) and PHY (Physical Layer) interfaces to WM (Wireless Medium). Here, STA may be referred to as base station equipment. STA may also be referred to as terminal equipment.

[0020] The STAs that make up the BSS may also be called members (BSS member STAs). The BSS is small It may also consist of two STAs. Even if an STA is a member of a BSS, it does not necessarily mean that it can communicate wirelessly with all member STAs within the BSS. In other words, it depends on the communication conditions and environment. Depending on the circumstances, there may be member STAs within the BSS that cannot perform wireless communication. For example, STA1 and ST2, and STA1 and STA3 may be configured in the BSS using the same BSSID. In this case, STA2 and STA3 will be configured in the same BSS, but STA2 and STA3 do not need to be able to perform wireless communication. The communication area (coverage) covered may also be called the BSA (Basic Service Area). A BSS may be comprised of associations between at least two STAs.

[0021] An AP may be an entity that contains one STA. Also, an AP may be an association For STA(s) that have established access to DSS (distribution system service(s)) via WM It may be an entity that provides access. Also, the AP may constitute an STA and a DSAF (Distributed System Access Function). Here, the AP is a base station device or network. It may also be called a work device.

[0022] A distribution system (DS) may be a system used to interconnect multiple sets of BSSs and integrated LANs in order to construct an Extended Service System (ESS).

[0023] An ESS (Extended Service Set) may have a connection path via a WM between one of the APs that are members of the ESS and a non-AP STA. An ESS may have overlapping coverage areas (areas) composed of multiple BSSs. An ESS may have multiple BSSs that are far apart, and may arrange the coverage covered by multiple BSSs into a wider coverage area. This is also acceptable. In other words, the communication area of ​​ESS may be the same as or larger than the communication area of ​​BSS alone. The communication area formed by ESS may be called ESA (Extended Service Area). stomach.

[0024] An ESS may be a set of one or more interconnected BSSs, represented as one BSS to the LLC (Logical Link Control) layer in any STA associated with one or more BSSs. A STA that has been associated with another STA may also be called an associated STA.

[0025] A non-AP STA may be an STA that does not include AP functionality. A non-AP STA is referred to as a terminal device. It may also be used.

[0026] WM is a Protocol Data Unit (PDU) between one or more PDUs (Protocol Data Units) of PHY entities within a wireless LAN. It may also be a medium used to carry out the transmission.

[0027] A channel may also be a WM used to transmit PPDU (PHY PDU) between two or more STAs.

[0028] A channel may have a primary channel and a secondary channel. In BSS, When operating with a bandwidth of 20 MHz, the channel may be the primary channel. For example, in BSS, when operating with a bandwidth of 40 MHz, a primary channel and a secondary channel may be used. The bandwidth may be defined as the bandwidth of the channel.

[0029] The primary channel is used in common for operations on all BSS member STAs. This is a channel that can be used. For example, in a BSS using bandwidths of 20MHz, 40MHz, 80MHz, 160MHz, 80+80MHz, and 320MHz, the primary channel may be the primary 20MHz channel.

[0030] The secondary channel may be a channel associated with the primary channel used to achieve a wider bandwidth than the primary channel. For example, in a BSS using bandwidths of 40MHz, 80MHz, 160MHz, 80+80MHz, and 320MHz, the secondary channel may be a secondary 20MHz channel. In such a case, the secondary channel may be a secondary 40MHz channel. It may be configured as a channel. In such a case, the secondary channel is a secondary 80MHz channel. It may be configured as a channel. In such a case, the secondary channel is secondary 160MHz. It may be configured as a z channel. For each bandwidth, it may be configured as a combination of a primary channel and a secondary channel. For example, in the case of a bandwidth of 320 MHz, the 320 MHz bandwidth may be configured using a Primary 20 MHz channel, a Secondary 20 MHz channel, a Secondary 40 MHz channel, a Secondary 80 MHz channel, and a Secondary 160 MHz channel.

[0031] For example, if a wide bandwidth such as 80 MHz is used, it may consist of a primary 40 MHz channel and a secondary 40 MHz channel. The primary 40 MHz channel may also be a 40 MHz primary channel. The primary 40 MHz channel may also consist of a primary 20 MHz channel and a secondary 20 MHz channel.

[0032] Figure 1 is a diagram showing an example of a wireless LAN system according to one aspect of this embodiment. In this configuration, BSS101-1 may consist of AP102-1 and non-AP STA 103-1, non-AP STA 103-2, and non-AP STA 103-3. BSS101-2 may consist of AP102-2 and non-AP STA 103-3 and non-AP STA 103-4. In BSS101-2, non-AP STA 103-3 and non-AP STA 103-4 may communicate directly.

[0033] If all STAs in BSS101-1 and BSS101-2 support the ability to receive trigger frames and to send trigger-based (TB) PPDUs in response to trigger frames, then in BSS101-1, AP 102-1 may request non-AP STA 103-1, non-AP STA 103-2, and non-AP STA 103-3 to send TB PPDUs using trigger frames. Similarly, in BSS101-2, AP 102-2 may request non-AP STA 103-3 and non-AP STA 103-4 to send TB PPDUs using trigger frames. In other words, the trigger frame is 1 Alternatively, it may be used to request multiple TB PPDU transmissions and to allocate resources for one or more TB PPDU transmissions. The trigger frame may also be used to transmit other information necessary for responding STA to transmit further TB PPDUs. The STA may also be AP or When a trigger frame is received, a TB is performed based on the information contained in the received trigger frame. You may send a PPDU.

[0034] Within BSS101-1 and BSS101-2, if some STAs support the function of receiving trigger frames and sending TB PPDUs for trigger frames, then AP101-1 and / or AP101-2 sends a trigger frame to an STA that supports the ability to receive a trigger frame and send a TB PPDU for the trigger frame, and sends a TB PPDU. You may request the following: the ability to receive trigger frames and TB PPDU for trigger frames. For STAs that do not support the ability to send, AP101-1 and / or AP101-2 Alternatively, a Control frame different from the Trigger frame may be used to request the transmission of the TB PPDU.

[0035] Furthermore, the trigger frame may be used by the AP to enable UL MU (Multi-User) transmission. The trigger frame may also be used for OFDMA transmission.

[0036] Furthermore, the trigger frame may be used to indicate various parameters of the TB PPDU required for transmission, such as the TB PPDU's Duration, RU (Resource Unit) allocation, target RSSI, and MCS.

[0037] Here, TB PPDU may also be PPDU.

[0038] Here, the trigger frame may also be the triggering frame. The trigger frame may also be defined as one of the triggering frames. The triggering frame may be the trigger frame, Alternatively, it was a frame that transmitted the TRS (Triggered Response Scheduling) Control subfield. This is also possible. The trigger frame described above may also be a frame that transmits the TRS Control subfield.

[0039] Non-AP STA 103-3 may also form a BSS with both AP 102-1 and AP 102-2. The configuration may also be referred to as OBSS (Overlapping BSS). Furthermore, an ESS may be constructed using BSS101-1 and BSS101-2.

[0040] STA is used for transmission and reception to meet predetermined communication speeds and data rates. Frequency band, bandwidth, communication method, access method, MCS method, MIMO (Multiple Input Multiple Access) Output method, beamforming and other functions may be supported / implemented. If enabled, STA may perform processing related to each function.

[0041] For example, STA may support / implement the functionality of HT (High Throughput) STA in order to meet the maximum communication speed of 600Mbps. HT STA functionality may include the 2.4GHz / 5GHz frequency band and 20... It supports a 40MHz bandwidth, OFDM / 64QAM, MIMO, channel bonding, and frame aggregation. Channel bonding may be used to communicate using one or more channels. It may be possible. Frame aggregation uses one or more frames as a single frame. Communication is permitted.

[0042] For example, in order to meet the maximum communication speed of 6.93 Gbps, the STA may support / implement the functions of VHT (Very HT) STA. As a function of VHT STA, various functions supported by HT STA are available. In addition to the functionality, support for a maximum bandwidth of 160MHz, 256QAM, 8x8 MIMO, MU-MIMO, and LDPC (Low Density Parity Coding) may also be provided.

[0043] For example, STA may support / implement the functionality of HE (High Efficiency) STA in order to meet the maximum communication speed of 9.6 Gbps. HE STA functionality is supported by HT STA and VHT STA. In addition to the various functions already listed, the 6GHz frequency band, OFDMA, 1026QAM, TWT (Target Wake Time), Spatial Reuse, and RU (Resource Unit) may also be supported.

[0044] For example, STA has the EHT (Extremely HT) STA function to meet the maximum communication speed of 46Gbps. The following may be supported / implemented: In addition to the various features supported by HT STA, VHT STA, and HE STA, EHT may support a maximum bandwidth of 320 MHz, 4096 QAM, 16x16 MIMO, Multi-RU, and Multi-Link.

[0045] For example, even if STA supports / implements the functionality of UHR (Ultra High Reliability) STA... Good. UHR STA supports various functions that are also supported by HT STA, VHT STA, HE STA, and EHT STA. In addition, features related to Multi-AP Operation and dRU (distributed RU) may also be supported.

[0046] When configuring an SS (Service Set) and / or BSS, ESS with multiple STAs, they may inform each other of the functions they support when associating. SS, BSS, and ESS may be configured to meet the appropriate communication speeds for each.

[0047] Figure 2 shows an example of the device configuration of an STA according to one embodiment of this model. The STA may have an antenna unit SU1, an RF (Radio Frequency) unit SU2, a physical layer processing unit (PHY layer processing unit) SU3, a MAC layer processing unit SU4, and an upper layer packet processing unit SU5. The STA may also have a wireless transceiver unit SU6 and a frame processing unit SU7. The wireless transceiver unit SU6 connects the antenna unit SU1 and the RF The frame processing unit SU7 may be configured to include a physical layer processing unit SU3 and a MAC layer processing unit SU4. The RF unit SU2 transmits radio signals via the antenna unit SU1. Receive the number. STA may include AP and / or non-AP STA.

[0048] The signal received by the RF unit SU2 is converted into a baseband signal and sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer functions (PHY functions) on the converted baseband signal. The signal that has undergone processing at the physical layer in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the MAC layer functions (MAC functions) on the baseband signal. The signal that has undergone processing at the MAC layer in the MAC layer processing unit SU4 is sent as an upper layer packet to the upper layer packet processing unit SU5. The upper layer packet processing unit SU5 performs processing related to the upper layer functions on the upper layer packets extracted from the received signal.

[0049] The upper layer packet processing unit SU5, when transmitting upper layer packets, processes information related to the functions of the upper layer. Processing is performed. The upper layer packet to be transmitted is sent from the upper layer packet processing unit SU5 to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing on the upper layer packet related to the MAC layer function. The frame after processing at the MAC layer in the MAC layer processing unit SU4 (the upper layer packet has been processed) The generated frame is sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. The frame sent from the physical layer processing unit SU3 to the RF unit SU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit SU1.

[0050] The processing of the physical layer processing unit SU3 may be controlled by a PLME (Physical Layer Management Entity), which is an entity that controls the physical layer. The processing of the MAC processing unit SU4 may be controlled by an MLME (MAC Layer Management Entity), which is an entity that controls the MAC layer. PLME and MLME provide their respective layer management service interfaces. Furthermore, PLME and MLME may be controlled by an SME (Station Management Entity), which is an entity independent of the layer. PLME, MLME, and SME may be included in the frame processing unit SU7.

[0051] Figure 3 shows an example of the device configuration of an AP according to one aspect of this embodiment. The AP may include an antenna unit AU1, an RF unit AU2, a physical layer processing unit AU3, a MAC layer processing unit AU4, and a DSAF unit AU5. The DSAF unit AU5 may also have a higher layer packet processing function. Furthermore, the AP is capable of wireless transmission and reception. The unit may have a section AU6 and a frame processing section AU7. The wireless transceiver section AU6 may be configured to include an antenna section AU1 and an RF section AU2. The frame processing section AU7 may be configured to include a physical layer processing section AU3 and a MAC layer processing section AU4.

[0052] The signal received by the RF unit AU2 is converted into a baseband signal and sent to the physical layer processing unit AU3. The physical layer processing unit AU3 processes the converted baseband signal to determine the function of the physical layer. Processing is performed. The signal that has undergone processing in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 processes the baseband signal, performing operations related to the MAC layer's functions. The MAC layer processing in MAC layer processing unit AU4 is sent to DSAF unit AU5 as a higher layer packet. DSAF unit AU5 then processes the higher layer packet extracted from the received signal. It performs processing related to the functions of the higher layer. In addition, the DSAF unit AU5 provides higher layer packets to the DS. That's good too.

[0053] The DSAF unit AU5 may acquire upper-layer packets from the DS. When transmitting upper-layer packets, the DSAF unit AU5 performs processing related to the functions of the upper layer. The packet is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer's functions on the upper layer packet. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (a frame generated by processing the upper layer packet) is sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. The frame sent from the physical layer processing unit AU3 to the RF unit AU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit AU1.

[0054] The processing of the physical layer processing unit AU3 may be controlled by PLME. The processing of the MAC processing unit AU4 is M It may be controlled by LME. Also, PLME and MLME are independent of the layer. It may be controlled by the SME, which is a type. PLME, MLME, and SME are connected to the frame processing unit AU7. It may be included.

[0055] Figure 4 is a schematic diagram of the PDUs supported at each level according to one aspect of this embodiment.

[0056] A MAC frame may be a unit of data exchanged between MAC entities. A MAC frame may also be referred to as an MPDU (MAC Protocol Data Unit).

[0057] An MSDU (MAC Service Data Unit) is shared among multiple MAC SAPs (Service Access Points). It may also be information transmitted as a unit.

[0058] An MPDU may be a unit of data exchanged between MAC entities using one or more services of the physical layer (PHY). Furthermore, an MPDU may aggregate one or more MSDUs. One MPDU may be configured.

[0059] A PHY frame may be a unit of data exchanged between PHY entities. A PHY frame may also be referred to as a PPDU.

[0060] A PSDU (PHY Service Data Unit) is encapsulated data at the physical layer and consists of one or more MPDUs (i.e., MAC frames) that are data from the MAC layer. This is also acceptable. In other words, the PSDU may be composed of an A-MPDU (Aggregate MPDU). Furthermore, the PSDU may be composed as a PPDU by adding a PHY preamble and PHY header, and the data between STAs may be It may also be used for communication at the radar layer.

[0061] PPDU may also be a unit of data exchanged between PHY entities using one or more services of the Physical Layer (PHY).

[0062] Figure 5 shows an example of a configuration in which the MAC frame according to one aspect of this embodiment is a Trigger frame. The MAC frame may include a Frame Control field, Duration field, RA field, TA field, Common Info field, User Info List field, Padding, and FCS.

[0063] The MAC header consists of the Frame Control field, Duration field, RA field, and TA field. It's okay.

[0064] In Figure 5, the Frame Control field is used to indicate the format and purpose of the MAC frame. In Figure 5, the Frame Control field may also be used to indicate that the MAC frame is a Trigger frame. Furthermore, Figure 5 explains each field when the MAC frame is a Trigger frame.

[0065] The Duration field shows the estimated time required to send the requested TB PPDU, and the required time. Depending on the context, the Duration field may be set to include the estimated time required to send an Ack for the requested TB PPDU, the applicable SIFS, and a corresponding value (e.g., index). In other words, the Duration field may be used to indicate the time required to send the TB PPDU and the time required to send an Ack for that TB PPDU.

[0066] The RA field is non-AP STA depending on the Trigger Type of the Trigger frame containing the RA field. If any of the following are the address, broadcast address, or MAC address of the group to which the transmission was requested It may also be set to the address of the STA that receives the Trigger frame (the STA that sends the Trigger frame, i.e., the AP) (for example, the ID of the STA).

[0067] If the TA field is addressed to an STA that the trigger frame belongs to a single BSS, then The TA field may contain the address of the STA sending the trigger frame (e.g., the STA's ID). If the trigger frame addresses one or more STAs from at least two different BSSs in a set of multiple BSSIDs, the TA field may contain the transmitted BSS ID.

[0068] The AP may decide which STA to request the transmission of the TB PPDU from. Received RA An STA with an address matching the field value may send a TB PPDU to the STA (i.e., AP) that sent the Trigger frame, based on the information contained in the received MAC frame.

[0069] The Common Info field is common to one or more STAs for which the transmission of a TB PPDU has been requested. It may be one or more fields that indicate various pieces of information used. For example, the Common Info field may include a Trigger Type subfield. The Common Info field may include a UL Length subfield. The Common Info field may also include a UL BW (Uplink Bandwidth) subfield. Furthermore, the Common Info field may include an AP Tx Power subfield. Finally, the Common Info field may include a Trigger Dependent Common Info subfield.

[0070] The Trigger Type subfield may be used to identify the type of Trigger frame.

[0071] The UL Length subfield indicates the value of the L-SIG LENGTH field of the TB PPDU being sent. It may be used for this purpose.

[0072] The UL BW subfield may be used to indicate the bandwidth of the SIG field of the TB PPDU. In other words, the UL BW subfield may be used to determine the bandwidth of the TB PPDU used to respond to the trigger frame.

[0073] The Trigger Dependent Common Info subfield is a subfield that corresponds to one or more optional features supported by STA shares, based on the value of the Trigger Type field. It may be included and provided.

[0074] The User Info List field may contain zero or more User Info fields. In other words, each of the one or more User Info fields included in the User Info List field may be assigned to an associated STA capable of receiving a Trigger frame.

[0075] The padding field may be used to adjust the overall size of the MAC frame.

[0076] The FCS (Frame Check Sequence) field contains a 32-bit CRC (Cyclic Redundancy Check) and may be used to verify whether a received frame is valid. Additionally, the STA (Stand-Aid) adds the FCS field to indicate that the frame being transmitted is valid.

[0077] Figure 6 shows an example of a User Info field according to one aspect of this embodiment. The field may include the AID12 subfield, RU Allocation subfield, UL FEC Coding Type subfield, UL MCS subfield, SS Allocation / RA-RU Information subfield, UL Target Rx Power subfield, Reserved bit, and Trigger Dependent User Info subfield.

[0078] The AID12 subfield may be set to the 12th LSB of the STA's AID. For example, AID12 subfield If it is included in the trigger frame, then the address of the non-AP STA associated with the AP It may also be S (i.e., 12LSB of AID for non-AP STA).

[0079] The value set in the AID12 subfield is the value associated with the User Info field. Alternatively, it may indicate that one or more RA-RUs are assigned to multiple STAs. Furthermore, depending on the value set in the AID12 subfield, the AID12 subfield may indicate that the User Info field is addressed to an associated STA with the same AID value as the AID12 subfield. It is also possible that, depending on the value set in the AID12 subfield, the AID12 subfield may indicate that the User Info field is assigned one or more RA-RUs to one or more unassociated STAs. Accordingly, the AID12 subfield indicates that it is a RU that has not been assigned to a particular STA. This may also be done. Furthermore, depending on the value set in the AID12 subfield, the AID12 subfield may indicate the start of the padding field.

[0080] The RU Allocation subfield, along with the UL BW subfield of the Common Info field, is a RU size It may be used to identify the size of the RU and its frequency domain arrangement. Here, the size of the RU may be the number of tones (i.e., subcarriers) that make up one RU. The arrangement of the RU may be the frequency domain or channel location where the RU corresponding to the UL BW is located. Values ​​that cannot be set in the RU Allocation subfield depending on the size of the bandwidth indicated by the UL BW subfield. It may be possible. In other words, the values ​​that can be set in the RU Allocation subfield may be associated with the values ​​in the UL BW subfield. The AP sets the bandwidth and TB PPDU in the UL BW subfield. Depending on the number of non-AP STAs making requests, the number of tones and RU index for the RUs shown in the RU Allocation subfield may be determined.

[0081] The subcarrier spacing between adjacent subcarriers may be 78.125 kHz. The subcarrier spacing of the subcarriers corresponding to each constituent tone may be 78.125 kHz, regardless of the number of tones constituting the RU.

[0082] The UL FEC Coding Type subfield may indicate the code type of the TB PPDU being submitted. For example, the code type may include BCC (Binary Convolutional Code) or LDPC (Low Density Parity Check).

[0083] The UL MCS subfield is the MCS (Modulation and Coding Scheme) of the TB PPDU being sent. It may be used to indicate [something].

[0084] The UL DCM subfield may be used to indicate the Dual Carrier Modulation (DCM) of the requested TB PPDU. Here, the DCM is for each of multiple channels or RUs. This is a procedure that maps and sends the same data.

[0085] The SS Allocation / RA-RU information subfield may be used as either the SS Allocation subfield or the RA-RU Information subfield, depending on the value set in the AID12 subfield.

[0086] The SS Allocation subfield is one or more spatial streams of the TB PPDU that were requested to be sent. It may be used to indicate [something].

[0087] The RA-RU Information subfield may be used to indicate the number of consecutive RUs assigned to UORA (Uplink Orthogonal frequency division multiple access based Random Access).

[0088] The UL Target Receive Power subfield is for TB PPDUs sent on the assigned RU. It may also be used to indicate the expected power of the received signal, which is averaged across one or more antennas and measured at the AP's antenna connector.

[0089] The Trigger Dependent User Info subfield is determined based on the value of the Trigger Type field for each STA. Subfields corresponding to the supported optional features may be set and provided.

[0090] Additionally, the User Info subfield may include the SS Allocation subfield instead of the SS Allocation / RA-RU information subfield.

[0091] Additionally, the User Info subfield has been modified to accommodate cases where the Bandwidth is 320MHz, and the RU (Router Unit) is set accordingly. The channel or 80MHz frequency subblock to be placed is either the Primary 160MHz channel or the Secondary It may include a PS160 subfield indicating whether it is included in the 160MHz channel. The RU is located as follows: If the channel or 80MHz frequency subblock is included in the Primary 160MHz channel, the value of PS160 subfield may be set to 0. If the channel or 80MHz frequency subblock where the RU is placed is included in the Secondary 160MHz channel, the value of PS160 subfield may be set to 1. If the bandwidth is 160MHz or less, the PS160 subfield may be set to 0. If the bandwidth is 160MHz or less, non-AP STA may ignore the value of PS160 subfield. If the bandwidth is 160MHz or less, the non-AP STA may be considered to have a PS160 subfield value of 0.

[0092] Figure 7 shows an example of RU arrangement using the RU Allocation subfield according to one aspect of this embodiment. The values ​​shown in the RU Allocation subfield correspond to the RU size and RU index, respectively. It may be applied. Furthermore, the range of values ​​that can be set in the RU Allocation subfield may differ depending on the bandwidth indicated by the UL BW subfield. For example, even with the same RU size, there may be RU indices that can be set at 20MHz and 40MHz, and RU indices that can only be set at 40MHz. RU size The RU index is a value given by bits corresponding to B7-B1 of the RU Allocation subfield. This may be indicated by: The bit corresponding to B0 in the RU Allocation subfield is Bandwidth If it is 160MHz, the channel or 80MHz frequency subblock where the RU is located is Primary 80MHz This may be used to indicate whether it is included in the channel or the Secondary 80MHz channel. RU If the channel or 80MHz frequency subblock to which the RU is located is included in the Primary 80MHz channel, the value of the bit corresponding to B0 in the RU Allocation subfield may be set to 0. If the channel or 80MHz frequency subblock where the RU is located is included in the Secondary 80MHz channel, then the value of the bit corresponding to B0 in the RU Allocation subfield is set to 1. That's good too.

[0093] Here, RU size may also be the number of subcarriers (tones) that make up the RU.

[0094] Figure 8 shows the RUs that can be placed for the bandwidth (CBW) of each channel according to one aspect of this embodiment. This figure shows an example of the maximum number.

[0095] The maximum number of RUs that can be placed in each channel may vary depending on the bandwidth and RU size. For example, with a bandwidth of 20 MHz and an RU size of 26-tones, a 20 MHz channel can accommodate 9 RUs. This may also be done. In such cases, the AP can allocate 9RUs to one or more non-AP STAs.

[0096] From Figures 7 and 8, it can be seen that a request to send TB PPDU is made in the Trigger frame (that is, the TB PPDU The transmitting STA may determine the frequency domain allocation of RUs used to transmit the TB PPDU. For example, if 40 MHz is indicated in the received UL BW subfield, the received RU Allocation In the subfield, if 7 is indicated, STA corresponds to the frequency of RU6 for a bandwidth of 40 MHz. A TB PPDU may be transmitted using several RU regions. Here, the TB PPDU may be referred to as PPDU.

[0097] Figure 9 shows an example of the configuration of an RU according to one aspect of this embodiment. Figure 9(a) shows an example of a regular RU (rRU, RRU) in which one RU is composed of consecutive tones. Figure 9(b) shows an example of a distributed RU (dRU, DRU) in which multiple tones constituting one RU are arranged at equal intervals and / or distributedly with respect to the maximum bandwidth of the channel or a predetermined bandwidth. Here, rRU may be referred to as a RU of the first RU allocation type. dRU may be referred to as a RU of the second RU allocation type. The RU of the first RU allocation type and the RU of the second RU allocation type are composed of 26-, 52-, 116-, 242-, 448-, and 996-tones, respectively. These tones may be referred to as data subcarriers. An RU may consist of and / or map a predetermined number of data subcarriers and a predetermined number of pilot subcarriers. Here, data subcarriers may be used for data transmission. Pilot subcarriers may be used for phase (phase shift) information and parameter tracking. Subcarriers not used as data subcarriers or pilot subcarriers may include DC subcarriers, null subcarriers, and guard band subcarriers. Null subcarriers may be used to reduce interference between adjacent RUs. Guard band subcarriers may be used for channel or This may be used to reduce interference between bands.

[0098] dRU may also be called distribution tone RU.

[0099] The RU Allocation type may also be referred to as the RU type.

[0100] The RU Allocation type may also indicate the type of RU being allocated (rRU or dRU).

[0101] The RU Allocation type may also be indicated by the Common Info field in the Trigger frame.

[0102] The RU Allocation type may be shown for each of the 80MHz frequency subblocks.

[0103] The RU Allocation type is determined by the DRU / RRU Indication subfield included in the Common Info field of the Trigger frame, for each of the one or more 80MHz frequency subblocks included in the Bandwidth obtained from the UL BW subfield and UL Bandwidth Extension subfield. It may also be indicated whether it is dRU or rRU. If the bandwidth is 80MHz or less, only the first bit (LSB) in the DRU / RRU Indication subfield is used to indicate the RU Allocation type, and the other bits in the DRU / RRU Indication subfield are treated as reserved. This may be done. If the bandwidth is 160MHz, the first two bits are used to indicate the RU Allocation type for the corresponding 80MHz frequency subblock, and the remaining bits included in the DRU / RRU Indication subfield may be treated as reserved. If the frequency is 320MHz, it may be used to indicate the RU Allocation type for each of the 4 bits corresponding to the 80MHz frequency subblock. In other words, DRU / RRU Indication subfield The number of bits allocated may vary depending on the bandwidth, or the number of valid bits may differ.

[0104] Here, a bandwidth (BW) to which rRU allocation is possible may be called a regular BW. A BW to which dRU allocation is possible may be called a distribution BW. In other words, a regular BW may be a BW to which rRU allocation is applied in a UL BW. A distribution BW may be a BW to which dRU allocation is applied. A subchannel within a regular BW is a regular subchannel. That is, it may be called a subchannel to which rRU Allocation is applied. A subchannel within a distribution BW may be called a distribution subchannel (that is, a subchannel to which dRU Allocation is applied). Depending on the tone size of the distribution BW and the dRU, the spacing between adjacent tones constituting the dRU placed in the distribution BW may be determined. For example, if 26-tone dRUs are placed in a 20MHz distribution BW, the spacing between adjacent tones of the dRUs The intervals may be arranged at 9-tone intervals. For example, 26-tone dRUs in a 40MHz distribution BW. If such arrangement is to be made, the spacing between adjacent tones of the dRU may be 18-tone intervals. In other words, the spacing between adjacent tones of the tone(s) constituting the dRU may be determined based on the distribution BW value and tone size.

[0105] The RUs indicated by the RU Allocation subfield may be assigned to non-AP STAs indicated by the AID12 subfield of the same User Info field. Furthermore, each RU indicated by the RU Allocation subfield may be configured to be assigned to the same or different non-AP STAs corresponding to the User Info field.

[0106] Figure 10 shows an example of a procedure related to the transmission of a PPDU using a dRU by an STA according to one aspect of this embodiment. In a certain BSS, an associated STA receives a trigger frame from an AP (S1001). The STA checks whether the trigger frame for the STA in S1001 contains a request to transmit a PPDU using a dRU (S1002). Based on the value set in the UL Bandwidth Extension subfield included in the trigger frame, the STA determines whether the bandwidth set in the UL BW subfield and the RU Allocation set in the RU Allocation subfield will be used for a PPDU using a dRU (S1003). In S1003, the UL BW subfield and the RU Allocation subfield are used to perform a PPDU transmission using a dRU. The STA then transmits the PPDU using the dRU to the AP (S1004).

[0107] If an AP that supports and / or enables dRU-related functionality requests one or more STAs that support and / or enable dRU-related functionality to send a PPDU using dRU, using a single Trigger frame, it may include a subfield related to the request to send a PPDU using dRU in the Common Info field of the Trigger frame.

[0108] For example, a subfield related to a PPDU transmission request using a dRU may be indicated as one of the Trigger Types in the Trigger Type subfield. In other words, if the Trigger Type subfield indicates a PPDU transmission request using a dRU (i.e., indicates the Trigger Type index corresponding to the PPDU transmission request using a dRU), then each RU Allocation subfield contained in each User Info field may be used to perform resource allocation of dRUs. Also, if the Trigger Type subfield indicates a PPDU transmission request using a dRU (i.e., using a dRU) If the Trigger Type index corresponding to the PPDU transmission request is shown, then the tones corresponding to the RU size and RU index shown by the RU Allocation subfield are equal in length for the entire bandwidth shown by the UL BW subfield in the Common Info field, as shown in Figure 9(b). It may be assigned to intervals.

[0109] For example, a subfield related to a request to send a PPDU using a dRU may be included in the Trigger Dependent Common Info subfield. The trigger frame corresponding to each trigger type may indicate whether or not to send a PPDU using a dRU. For some trigger types, the trigger frame may not include a subfield related to a request to send a PPDU using a dRU. That's good too.

[0110] If the subfield related to the PPDU transmission request using dRU is included in the Trigger Dependent Common Info subfield, then the RU Allocation subfield included in the User Info field is the dRU It may also be used for resource allocation. Furthermore, if the subfield related to the PPDU transmission request using dRU is included in the Trigger Dependent Common Info subfield, then for the entire bandwidth indicated by the UL BW subfield included in the Common Info field, the tones corresponding to the RU size and RU index indicated by the RU Allocation subfield are as shown in Figure 9(b). They may be allocated at equal intervals.

[0111] For example, a subfield related to a PPDU transmission request using dRU may be a UL Bandwidth Extension subfield. Depending on the value set in the UL Bandwidth Extension subfield It may also be indicated whether the corresponding bandwidth (i.e., the bandwidth set by the UL BW subfield) is used for dRU Allocation or rRU Allocation. In other words, non-AP STAs that support and / or enable dRU-related features. The requested TB PPDU is determined based on the values ​​set in the UL BW subfield of the Common Info field and the UL Bandwidth Extension subfield of the Special User Info subfield. The bandwidth and bandwidth type (or RU Allocation type) may be determined.

[0112] If an AP that supports and / or enables dRU-related functionality requests one or more STAs that support and / or enable dRU-related functionality to send a PPDU using dRU, using a single Trigger frame, it may include a subfield related to the request to send a PPDU using dRU in the User Info field of the Trigger frame. The AP may also indicate to each STA in the BSS whether to request the sending of a PPDU using dRU.

[0113] APs that support and / or enable features related to dRUs may indicate to one or more STAs that support and / or enable features related to dRUs whether the RU Allocation subfield in the User Info field corresponds to a dRU using one or more bits that make up the RU Allocation subfield. For example, related to dRUs One or more STAs that support and / or enable the function will receive the RU Allocation subfield if certain bits constituting that subfield indicate a predetermined value. The STA may determine that the received RU Allocation subfield is used to indicate the resource allocation of a dRU. Otherwise, the STA may determine that the received RU Allocation subfield is used to indicate the resource allocation of an rRU. In addition, one or more STAs that support and / or enable dRU-related functionality may determine that the received RU Allocation subfield is used to indicate the resource allocation of a rRU. If one or more specific bits constituting the subfield indicate a predetermined value, it may be determined that the received UL BW subfield is to be used for resource allocation of the dRU.

[0114] APs that support and / or enable dRU-related features will assign a specific ID from the AID12 subfield included in the User Info field when requesting the transmission of a PPDU using dRU to one or more STAs that support and / or enable dRU-related features. This is also acceptable. A specific ID may be indicated using a Reserved ID. A specific ID may already be assigned The specified ID among the IDs may be reinterpreted and defined.

[0115] If an AP that supports and / or has enabled dRU-related features requests the transmission of a PPDU using dRU to one or more STAs that also support and / or have enabled dRU-related features, the Trigger Dependent User Info subfield will be set to "Transmission of PPDU using dRU". You may also include subfields related to the request when setting it.

[0116] Here, the subfield related to the PPDU transmission request using dRU is whether to use dRU or rRU. It may also be a subfield used to indicate whether or not. Related to PPDU transmission requests using dRU The following subfields may be used to indicate the channels and / or bandwidths and / or frequency offsets for which resource allocation is possible in the dRU. The subfield related to the PPDU transmission request using the UL BW subfield is used for dRU. A subfield may be used to indicate whether it is used for rRU or dRU. A subfield related to a PPDU transmission request using dRU may be a subfield used to indicate whether the RU Allocation subfield is for dRU or rRU. The subfield associated with the PPDU transmission request may be associated with information indicating whether it is possible to transmit PPDUs using dRU to the Puncturing channel. STAs that support and / or enable dRU-related functionality can transmit PPDUs using dRU to the Puncturing channel. If it is shown that transmission is possible, then for the Puncturing channel, for RU Allocation The resource allocation of the dRU may be determined based on the corresponding bandwidth and RU size. Here, the puncturing channel is used for STAs that do not support and / or enable the functions related to the dRU. Conversely, it may be used to indicate channels that do not transmit or receive PPDU. The Puncturing channel may also show information related to the bandwidth and frequency offset of the Puncturing channel.

[0117] In some BSS and / or ESS, support and / or have dRU-related functionality. If it includes enabled AP and non-AP STA, then it supports the functions related to dRU. APs that support and / or enable dRUs use a trigger frame to require non-AP STAs that support and / or enable dRU-related functions to send PPDUs using dRUs. It may be requested. Also, in order to request the transmission of a PPDU using a dRU, the AP will send the non-AP STA to the STA. Alternatively, you can set the subfield necessary to request the transmission of PPDU using dRU using the Trigger Dependent User Info subfield.

[0118] Here, AP supports and / or functions related to dRU within the same BSS and / or ESS. If at least one STA is not enabled, you do not need to set a subfield using the Trigger Dependent User Info subfield to request STAs that do not support and / or have enabled dRU-related features to send PPDUs using dRU.

[0119] Furthermore, AP supports and / or dRU-related functions within the same BSS and / or ESS. Alternatively, if at least one STA is not enabled, you may set a subfield using the Trigger Dependent User Info subfield to request the transmission of PPDUs using dRU. In this case, the AP must support and / or enable the dRU-related functionality. For STAs that do not support and / or have dRU-related functionality, it is not necessary to set a subfield in the Trigger Dependent User Info subfield to request the transmission of PPDUs using dRU. In such cases, the AP will send a first trigger frame to STAs that support and / or have dRU-related functionality enabled. STA does not support and / or enable features related to the User Info field and dRU. It may also include a second User Info field. The AP may request each STA to send a PPDU of the corresponding RU allocation type.

[0120] Furthermore, AP supports and / or dRU-related functions within the same BSS and / or ESS. If at least one STA is not enabled, and the UL BW subfield is set to a bandwidth of 20 MHz or narrower, then it requests the transmission of a PPDU using dRU. You do not need to set the necessary subfields using the Trigger Dependent User Info subfield.

[0121] STAs that do not support and / or enable features related to dRU will trigger frame Even if a subfield related to a PPDU transmission request using a dRU included in is received, it will be ignored. That's fine.

[0122] Non-AP STAs that support and / or enable dRU-related features may determine whether the dRU-based distribution of multiple tones is performed across the entire maximum bandwidth of the channel or on a portion of the bandwidth, depending on the value of the subfield included in the trigger frame.

[0123] Non-AP STAs that support and / or enable dRU-related features also: The AP may be shown capability information indicating whether it supports and / or enables features related to whether distributed placement is performed across the entire maximum bandwidth of the channel or on a portion of the bandwidth. In this case, the trigger frame may include a subfield indicating whether the dRU distributes multiple tones across the entire maximum bandwidth of the channel or across a portion of the bandwidth when requesting transmission of the PPDU.

[0124] Figure 11 shows an example of a Special User Info field according to one aspect of this embodiment. The Special User Info field may be used to transmit extended common information not provided in the Common Info field. The Special User Info field does not have to be used to transmit user-specific information. The Special User Info field may be identified by a specific value in the AID12 subfield. However, for non-AP STAs associated with the AP, it is not necessary to set this specific value in the AID12 subfield. The Special User Info field may exist as a field to indicate optional functionality in the Trigger frame generated by the AP. That is, the AP may optionally add the Special User Info field to the Trigger frame. That is, whether or not the Special User Info field is included in the Trigger frame may be determined based on whether or not the User Info field is included in the Trigger frame. Therefore, it may be placed immediately after the Common Info field of the Trigger frame. Also, the Special User Info field is used to transmit information for the U-SIG field of the requested TB PPDU. It may be used for this purpose.

[0125] The length (time length or bit length) of a Special User Info field may be the same as the length of other User Info fields in the same Trigger frame (except when the Trigger frame is a MU-BAR Trigger frame).

[0126] The Special User Info field does not need to be included in the Trigger frame unless the Trigger frame contains one or more variant User Info fields. In other words, if an AP sends a Trigger frame that does not contain a User Info field, it does not need to include the Special User Info field in that Trigger frame.

[0127] The Special User Info field may include a PHY Version Identifier subfield. The PHY Version Identifier subfield is used to indicate the PHY version of the TB PPDU being sent. It is permissible to set the PHY Version Identifier subfield to 0 if the TB PPDU being requested to be sent is an EHT TB PPDU. For example, if the TB PPDU being requested to be sent is a UHR TB PPDU, the PHY Version Identifier subfield may be set to 1. For example, if the TB PPDU being requested to be sent is a TB PPDU corresponding to a specific function, the PHY Version Identifier subfield may be set to 2. In other words, a corresponding value may be set or defined for TB PPDUs corresponding to additional or extended functions.

[0128] The PHY Version Identifier subfield indicates whether non-AP STA and / or AP are supported / enabled. The values ​​to be set may be defined according to the features being enabled. For non-AP STA, the PHY Version Identifier subfield is set to a value corresponding to features that it does not support. If present, the received Special User Info field can be ignored. non-AP STA is PHY If the Version Identifier subfield is set to a value corresponding to a feature that the system does not support, the received PPDU may be ignored.

[0129] The Special User Info field may include the Spatial Reuse subfield. The subfield transmits the values ​​contained in the Spatial Reuse n subfield of the U-SIG field of the TB PPDU. It may be used for that purpose.

[0130] The Special User Info field is the U-SIG Disregard And Validate subfield, and the U-SIG Disregard And Validate subfield is the various subfields (or subfields) included in the U-SIG field of the requested TB PPDU. It may be used to indicate whether a particular subfield (a particular bit) of the corresponding bits is valid or ignored.

[0131] The U-SIG field is used to transmit information necessary for interpreting (decoding) PPDUs. The STA that receives the U-SIG field may demodulate the PPDU received along with the U-SIG field. You can perform the action.

[0132] The Special User Info field may include a UL Bandwidth Extension subfield (UL BW Ext subfield). The UL BW Ext subfield may be used in combination with the bandwidth indicated by the UL BW subfield included in the Common Info field to indicate that a bandwidth wider than 160 MHz (e.g., 320 MHz) is being used. Also, dRU-related functions... APs that support and / or enable this feature will determine whether the bandwidth indicated by the UL BW subfield is used for dRU Allocation (or indicated as distribution BW) or rRU Allocation for non-AP STAs that support and / or enable this feature. It may be used to indicate whether it is used for (or shown as regular BW). For example, for a non-AP STA that supports and / or enables this function, the UL BW and BW type for a TB PPDU requested for transmission may be shown in the combination shown in Figure 12. Therefore, the BW type may also be called the RU Allocation type.

[0133] Figure 12 shows an example of BW and BW type indicated by the UL BW subfield and UL Bandwidth Extension subfield (UL BW Ext subfield) according to one aspect of this embodiment. The BW type may indicate regular BW or distribution BW. The BW type is also used to indicate whether the bandwidth indicated by the UL BW subfield is regular BW. It is also possible to use the BW type to indicate whether the bandwidth indicated by the UL BW subfield is a distribution BW. For example, if the UL BW subfield indicates 20 MHz In this case, depending on the value indicated by the UL BW Ext subfield, it is indicated whether the bandwidth indicated by the UL BW subfield is used as regular BW or distribution BW. This may be done. Here, if the UL BW Ext subfield is set to 0, the 20MHz may be used as the regular BW. In such a case, the non-AP STA that has been requested to transmit the TB PPDU applies rRU Allocation to the RU Allocation used to transmit the TB PPDU and configures This may also be done. Furthermore, if the UL BW Ext subfield is set to 1, the 20MHz may be used as the distribution BW. In such a case, the non-AP that was requested to transmit the TB PPDU... The STA may configure the RU Allocation used to transmit the TB PPDU by applying dRU Allocation.

[0134] Figure 12 shows the case where the UL BW Ext subfield consists of 2 bits, but it may also consist of a number of bits other than 2. For example, the number of bits that make up the UL BW Ext subfield may vary depending on the value indicated by the PHY Version Identifier subfield. It may change. Also, if the UL BW Ext subfield consists of more than 2 bits, it may be used to indicate a bandwidth wider than 320 MHz for the UL BW. For example, the PHY Version Identifier subfield may indicate that it supports / enables features related to dRU. If it is set to a value, the number of bits that make up the UL BW Ext subfield is UL BW To indicate the applicable BW type, use a number of bits greater than 2 bits (for example, 3 bits). (It may also be a .)

[0135] Depending on the value indicated by the PHY Version Identifier subfield, the UL BW subfield and The table corresponding to the UL BW Ext subfield may be modified as shown in Figure 12.

[0136] The UL BW and BW type may be determined based on the combination of the values ​​set in the UL BW subfield and the values ​​set in the UL BW Ext subfield.

[0137] non-AP STA indicates that it supports and / or enables features related to dRU. If a subfield is received, as shown in Figure 12, the value set in the UL BW subfield and UL The UL BW and BW type of the requested TB PPDU may be determined based on the combination of values ​​set in the BW Ext subfield.

[0138] Information indicating that features related to dRU are supported and / or enabled is specific. It may be included in the element.

[0139] Information indicating that features related to dRU are supported and / or enabled is specific. It may be included in the Management frame. The Management frame may be used to send frames related to Beacon, Probe, Authentication, and (Re)Association, respectively. .

[0140] Information indicating that features related to dRU are supported and / or enabled is specific. It may be included in the Control frame. The Control frame may be used to send the frames associated with the Ack, RTS, CTS, and Trigger frames, respectively.

[0141] Information indicating that features related to dRU are supported and / or enabled is specific. It may be included in the trigger frame.

[0142] Information indicating that features related to dRU are supported and / or enabled is specific. It may be included in the Management and Extension frame.

[0143] Supporting and / or enabling features related to dRU is a specific Operating It may also be indicated by the Mode.

[0144] If the dRU-related features are supported and / or enabled but not indicated, then the combination of the values ​​set in the UL BW subfield and the values ​​set in the UL BW Ext subfield will be... Accordingly, only UL BW may be determined.

[0145] Next, an Operation element according to one aspect of this embodiment will be described.

[0146] STA operation in a BSS in the 2.4GHz band involves various operation elements (for example) Alternatively, it may be controlled by an HT / HE / EHT / UHR Operation element.

[0147] STA operation in a BSS in the 5GHz band involves various operation elements (for example) It may be controlled by an HT / VHT / HE / EHT / UHR Operation element.

[0148] STA operation in a BSS in the 6GHz band involves various operation elements (for example) It may be controlled by the HE / EHT / UHR Operation element.

[0149] In BSSs with frequency bands higher than 6GHz, STA operation may be controlled by a UHR Operation element.

[0150] Figure 13 shows an example of various fields / subfields included in the Operation element format according to one aspect of this embodiment. Figure 13(a) shows the Element format according to one aspect of this embodiment. Figure 13(b) shows an example of the Operation element format according to one aspect of this embodiment. Figure 13(c) shows the Operation Parameters according to one aspect of this embodiment. An example of a field format is shown. Figure 13(d) shows Operation Inf according to one aspect of this embodiment. An example of the configuration field format is shown. Figure 13(e) shows an example of the control subfield format according to one aspect of this embodiment.

[0151] If the combination of the Element ID and the value set in the Element ID Extension included in the Element format represents the Operation element, then the Element format in Figure 13(a) is, It may be considered an Operation element as described in 13(b).

[0152] The Operation Information Present subfield is set to 1 if the Operation Information field is included in the Operation element, and may be set to 0 otherwise.

[0153] The Disabled Subchannel Bitmap Present subfield is set to 1 if the Disabled Subchannel Bitmap subfield is included in the Operation Information field, and may be set to 0 otherwise. If it is set, the Disabled Subchannel Bitmap Present subfield will be reserved. That's fine.

[0154] The Distribution Subchannel Bitmap Present subfield may be set to 1 if the Distribution Subchannel Bitmap subfield is included in the Operation Information field, and to 0 otherwise. If the Operation Information Present subfield is set to 0, the Distribution Subchannel Bitmap Present subfield may be reserved.

[0155] The Operation Information field is set to 1 in the Operation Information Present subfield. If it is included, it may be included in the Operation element. Otherwise, the Operation Information field is optional. The STA may obtain a set of channel configuration parameters from the Operation Information field.

[0156] Operation Information field is Control subfield, CCFS0 subfield, CCFS1 subfield, Disabled Subchannel Bitmap subfield, Distribution Subchannel Bitmap subfield It may include.

[0157] The Control subfield includes the Channel Width subfield and / or the Reserved subfield. That's fine.

[0158] The Channel Width subfield may be used to indicate the BSS bandwidth.

[0159] The CCFS0 subfield is the channel center frequency for BSS bandwidths of 20, 40, and 80 MHz. It may be used to define (CCF). Furthermore, the CCFS0 subfield may be used to indicate the primary 80MHz channel for a 160MHz BSS bandwidth. Also, the CCFS0 subfield may be used to indicate the primary 160MHz channel for a 320MHz BSS bandwidth. This is also good. The CCFS0 subfield allows BSS to operate for BSS bandwidths of 20, 40, and 80 MHz. It may also be used to show the CCF index for 20, 40, and 80 MHz channels. Furthermore, the CCFS0 subfield may be used to show the CCF index of the primary 80 MHz channel operated by the BSS for a 160 MHz BSS bandwidth. Additionally, the CCFS0 subfield may be used to show the CCF index of the primary 160 MHz channel operated by the BSS for a 320 MHz BSS bandwidth.

[0160] The CCFS1 subfield may be used to define the CCF for 160 and 320 MHz BSS bandwidths. The CCFS1 subfield may also be used for 20, 40, and 80 MHz BSS bandwidths, i.e., Channel If the Width subfield sets the BSS bandwidth to 20, 40, or 80 MHz, then setting it to 0 will result in a value of 0. It may also be used to indicate the CCF index of the 160MHz channel operated by the BSS for a 160MHz BSS bandwidth. Furthermore, the CCFS1 subfield may be used to indicate the CCF index of the 320MHz channel operated by the BSS for a 320MHz BSS bandwidth.

[0161] An AP may set the Operation Information Present subfield in the Operation element by satisfying one or more conditions. One or more conditions are that the AP is at 5GHz. Alternatively, the operation may be in the 6GHz or higher frequency band. Furthermore, one or more conditions apply if the AP announces the BSS operating channel width to one or more non-AP STA(s) via the Operation element, and the BSS operating channel width announced to a different type of non-AP STA in the same Management frame is different from the BSS operating channel width announced to the non-AP STA. It may also be the case that one or more conditions are that the BSS operating channel width announced to non-AP STA(s) includes at least one punctured 20MHz subchannel and / or the BSS operating channel width announced to non-AP STA(s) is 320MHz. It may also be the case that the BSS operating channel width announced to non-AP STA(s) includes at least one 20MHz subchannel (i.e., distribution subchannel) to which dRU Allocation is applied. Alternatively, if all of the conditions are not met, the AP may set the Operation Information Present subfield to 0. In other words, the AP does not need to include an Operation Information field in the Operation element.

[0162] The Disabled Subchannel Bitmap subfield may be included in the Operation Information field if the Disabled Subchannel Bitmap Present subfield is set to 1. The Disabled Subchannel Bitmap subfield may be used to provide a list of subchannels that have been punctured within the BSS bandwidth. Otherwise, the Disabled Subchannel Bitmap subfield does not need to be included in the Operation Information field.

[0163] Disabled Subchannel Bitmap subfield may consist of a 16-bit bitmap. The least significant bit of the bitmap may correspond to the lowest frequency 20MHz subchannel among all 20MHz subchannels included within the BSS bandwidth. Each of the consecutive bits corresponds to each 20MHz subchannel included within the BSS bandwidth. The bits of the bitmap may be set to 1 if the 20MHz subchannel corresponding to the bits of the bitmap is punctured. If the corresponding 20MHz subchannel is not punctured, the bits of the bitmap may be set to 0. Bits of the bitmap corresponding to a 20MHz subchannel outside the BSS bandwidth may be reserved.

[0164] The Distribution Subchannel Bitmap subfield may be included in the Operation Information field if the Distribution Subchannel Bitmap Present subfield is set to 1. The Distribution Subchannel Bitmap subfield may be used to provide a list of subchannels to which dRU Allocation has been applied within the BSS bandwidth. Otherwise, the Distribution Subchannel Bitmap subfield does not need to be included in the Operation Information field.

[0165] The Distribution Subchannel Bitmap subfield consists of a 16-bit bitmap. The least significant bit of the bitmap may correspond to the lowest frequency 20MHz subchannel among all 20MHz subchannels included within the BSS bandwidth. Each consecutive bit within the bit corresponds to each 20MHz subchannel contained within the BSS bandwidth. This may be done. If dRU Allocation is applied to the 20MHz subchannel corresponding to the bits of the bitmap, the bits of the bitmap may be set to 1. If dRU Allocation is not applied to a 20MHz subchannel corresponding to a bit in a bitmap, that bit in the bitmap may be set to 0. Bits in a bitmap corresponding to a 20MHz subchannel outside the BSS bandwidth may be reserved.

[0166] The Distribution Subchannel Bitmap subfield indicates whether dRU Allocation is applied in units of 80MHz frequency subblocks, if it has fewer than 16 bits. For example, it may consist of a 4-bit bitmap. The Distribution Subchannel Bitmap subfield is used for each 20MHz subchannel contained in the 80MHz frequency subblock. It may be indicated whether or not it is punctured.

[0167] The Distribution Subchannel Bitmap subfield is contained within the Bandwidth Indication element. It's okay.

[0168] Bandwidth Indication element is channel bandwidth, CCF, punctured subchannels The Bandwidth Indication element may also include information indicating each of these. Furthermore, if the AP and non-AP STA support and / or enable features related to dRU, the Bandwidth Indication element may also include information indicating distribution subchannels.

[0169] The Bandwidth Indication element is shown as a subelement included in various other elements. That's fine.

[0170] Figure 14 shows an example of a Bandwidth Indication element according to one aspect of this embodiment. Figure 14(a) shows an example of a Bandwidth Indication element format according to one aspect of this embodiment. Figure 14(b) shows an example of a Bandwidth Indication Parameters field format according to one aspect of this embodiment.

[0171] Disabled Subchannel Bitmap subfield in Bandwidth Indication Information field If included, Disabled Subchannel Bitmap Present subfield may be set to 1. Otherwise, Disabled Subchannel Bitmap Present subfield may be set to 0.

[0172] If the Bandwidth Indication Information field contains a Distribution Subchannel Bitmap subfield, then the Distribution Subchannel Bitmap Present subfield is set to 1. It may be set to 0. Otherwise, Distribution Subchannel Bitmap Present subfield may be set to 0.

[0173] Operation elements may be included in Beacon frames, Probe Response frames, Association Response frames, and Reassociation Response frames.

[0174] The Bandwidth Indication element may be included in the Beacon frame, Probe Response frame, Association Response frame, or Reassociation Response frame.

[0175] The Bandwidth Indication Information field may contain the same information and / or subfields as the Operation Information field of the Operation element shown in Figure 13.

[0176] If both a Disabled Subchannel Bitmap subfield and a Distribution Subchannel Bitmap subfield are set, the values ​​set in the bitmaps contained within each of the Disabled Subchannel Bitmap subfield and the Distribution Subchannel Bitmap subfield will be set individually. It may be set. If each subfield is set to 1 for the same 20MHz subchannel, the resource configuration of the dRU is determined by puncturing the 20MHz subchannel. good.

[0177] If both the Disabled Subchannel Bitmap subfield and the Distribution Subchannel Bitmap subfield are set, the Distribution Subchannel Bitmap subfield may be a subset of the Disabled Subchannel Bitmap subfield. For example, one or more 20MHz subchannels that are set to 1 in the bits of the Disabled Subchannel Bitmap subfield may be set as distribution subchannels. In such a case, a non-AP STA to which rRU Allocation is applied may determine the punctured subchannels based on the Disabled Subchannel Bitmap subfield and determine the resource configuration of the rRU. In such a case, dRU Allocation is applied. A non-AP STA may determine the resource configuration of the dRU based on the Distribution Subchannel Bitmap subfield.

[0178] If the Distribution Subchannel Bitmap subfield is set to 1 for multiple consecutive 20MHz subchannels within the BSS bandwidth, the Operation element may include a subfield indicating whether the multiple consecutive 20MHz subchannels constitute a single distribution BW. For example, if 1 is set for two consecutive 20MHz subchannels, the Operation element may include a subfield indicating whether dRU Allocation is performed as two 20MHz distribution BWs or as a single 40MHz distribution BW. For example, if 1 is set for four consecutive 20MHz subchannels... If so, dRU Allocation will be performed as four 20MHz distribution BWs or two The Operation element may include a subfield to indicate whether dRU Allocation is performed as a 40MHz distribution BW, as a single 80MHz distribution BW, or as two 20MHz distribution BWs and one 40MHz distribution BW.

[0179] Independent of the Distribution Subchannel Bitmap subfield, a subfield may be defined to indicate the configuration of the distribution BW within the BSS bandwidth. For example, Disabled Subchannel If a puncture indicated by a bitmap subfield overlaps with a 40MHz distribution BW, then the non-AP STA corresponds to the bits in the 40MHz distribution BW that are set to 1 by the disabled subchannel bitmap subfield. Alternatively, the 20MHz subchannel may be punctured to determine the resource configuration of the dRU.

[0180] The Distribution Subchannel Bitmap subfield is in the Common Info field of the Trigger frame. May be included. Bandwidth indicated by the UL BW subfield included in the Common Info field. Accordingly, the size of the bitmap in the Distribution Subchannel Bitmap subfield will be changed. It can also be defined and used.

[0181] The Distribution Subchannel Bitmap subfield may be included in the Special User Info field of the Trigger frame.

[0182] The Distribution Subchannel Bitmap subfield is included in the User Info field of the Trigger frame. It may be included. The Distribution Subchannel Bitmap subfield may consist of a 4-bit bitmap, corresponding to the 80MHz frequency subblock of the RU Allocation subfield included in the User Info field.

[0183] The Distribution Subchannel Bitmap subfield may be included in the OM (Operating Mode) Control field. It is indicated by the Channel Width subfield included in the OM Control field. The bitmaps included in the Distribution Subchannel Bitmap subfield are adjusted to match the bandwidth. The size may be changed and redefined.

[0184] A subfield indicating the configuration of the distribution BW within the BSS bandwidth may be included in the Common Info field of the Trigger frame. Furthermore, the subfield indicating the configuration of the distribution BW within the BSS bandwidth may match the bandwidth set in the UL BW subfield within the BSS bandwidth. The configuration of the distribution BW may be shown. In other words, in such a case, the subfield This may be a subfield to indicate the structure of the distribution BW within the UL BW.

[0185] A subfield indicating the configuration of the distribution BW within the BSS bandwidth may be included in the Special User Info field of the Trigger frame. Furthermore, the subfield indicating the configuration of the distribution BW within the BSS bandwidth may be included in the value set in the UL BW subfield within the BSS bandwidth. The distribution BW will adjust to the bandwidth corresponding to the value set in the UL BW Ext subfield. The configuration may be shown.

[0186] A subfield indicating the configuration of the distribution BW within the BSS bandwidth may be included in the User Info field of the Trigger frame. Alternatively, the subfield indicating the configuration of the distribution BW within the BSS bandwidth may be aligned with the 80MHz frequency subblock corresponding to the RU Allocation subfield within the BSS bandwidth. In other words, in such cases, the subfield indicates the configuration of the distribution BW within the 80MHz frequency subblock. It can also be a subfield.

[0187] A subfield indicating the configuration of distribution BW within the BSS bandwidth may be included in the OM Control field. The subfield indicating the configuration of distribution BW within the BSS bandwidth may show the configuration of distribution BW in accordance with the bandwidth indicated by the Channel Width subfield included in the OM Control field. In other words, in such a case, the subfield may be a subfield indicating the configuration of distribution BW within the bandwidth indicated by the Channel Width subfield.

[0188] Next, a Capabilities element according to one aspect of this embodiment will be described.

[0189] An STA (AP, non-AP STA) declares that it is the STA corresponding to a Capabilities element by sending a Capabilities element.

[0190] For example, an STA may declare that it is an HT STA by transmitting an HT Capabilities element. It may do so.

[0191] For example, an STA may declare that it is a non-HT STA by transmitting a non-HT Capabilities element.

[0192] For example, an STA may declare that it is a VHT STA by transmitting a VHT Capabilities element.

[0193] For example, an STA may declare that it is an HE STA by transmitting an HE Capabilities element.

[0194] For example, an STA may declare that it is an EHT STA by transmitting an EHT Capabilities element.

[0195] For example, an STA may declare that it is an UHR STA by transmitting an UHR Capabilities element.

[0196] The Capabilities element may include one or more fields used to notify the functions supported by the STA. For example, the Capabilities element may include a MAC Capabilities Information field related to the functions supported at the MAC layer, and a PHY Capabilities Information field related to the functions supported at the PHY layer. It may include them.

[0197] Next, we will describe an UL MU (multi-user) operation according to one aspect of this embodiment.

[0198] An AP according to one aspect of this embodiment may transmit a trigger frame for initiating a UL MU operation using UL OFDMA and / or UL MU-MIMO transmission, or a frame containing a TRS Control subfield for initiating UL OFDMA transmission. These in the uplink direction The frame that initiates transmission may be a triggering frame. In other words, an AP may use a triggering frame to initiate a UL MU operation. The triggering frame identifies one or more non-AP STAs participating in the UL MU operation and sends one or more RU(s) to these STAs. And / or may be used to allocate spatial stream(s), where the Triggering frame does not have to be sent from a non-AP STA.

[0199] UL MU-MIMO enables multiple STAs to transmit simultaneously to the receiver on the same frequency resource. It refers to the technology that enables this. The UL MU-MIMO concept involves multiple transmitters and receivers. This is similar to SU-MIMO, where multiple space-time streams are transmitted simultaneously on the same frequency resource with spatial multiplexing enabled via the antenna. The difference between UL MU-MIMO and SU-MIMO is that the multiple transmitted streams originate from multiple STAs.

[0200] OFDMA is an OFDMA-based multiple access scheme in which different subsets of subcarriers are assigned to different users. This scheme allows simultaneous data access to one or more users. It enables data transmission and simultaneous data transmission from one or more users. Users may be assigned to different subsets of subcarriers, which can be changed per PPDU. OFDMA uses multiple subcarriers, and each of these subcarriers participates as a RU (Rules of Use). They may be divided into several groups. That is, in OFDMA, different users may occupy different RUs with the same PPDU. In OFDMA, different transmit powers may be applied to different RUs.

[0201] UL MU operation allows the AP to receive immediate response frames from one or more non-AP STAs. This allows simultaneous requests. Non-AP STA follows predetermined rules for sending response frames in HE TB PPDU unless the trigger frame is a MU-RTS trigger frame. If a frame is a MU-RTS trigger frame, its response frame may be a non-HT PPDU CTS frame. EHT UL MU operation may extend the UL MU functionalities inherited from HE by adding the ability to respond with EHT TB PPDU in bandwidths up to 320 MHz. Furthermore, UHR UL MU operation may extend the UL MU functionalities inherited from HE / EHT by providing additional capabilities that respond with UHR TB PPDU.

[0202] UL MU operation enables an AP to simultaneously receive information from more than one non-AP STA. In this case, the non-AP STA may transmit using TB PPDU format with UL OFDMA, UL MU-MIMO, or both.

[0203] A mesh STA, such as an HE STA, does not need to send or receive one or more HE TB PPDUs.

[0204] A mesh STA, which is an EHT STA, does not need to send and receive one or more EHT TB PPDUs. stomach.

[0205] A mesh STA, which is a UHR STA, does not need to send or receive one or more UHR TB PPDUs.

[0206] If a non-AP HE STA supports transmitting HE TB PPDUs using UL MU-MIMO within a RU that spans the entire PPDU bandwidth, the STA sets dot11HEFullBWULMUMIMOImplemented to true and sets the Full Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field within the HE Capabilities element transmitted by the STA to 1. Otherwise, the STA sets dot11HEFullBWULMUMIMOImplemented to false and sets the Full Bandwidth UL MU-MIMO subfield to 0.

[0207] If a non-AP STA with dot11HEFullBWULMUMIMOImplemented set to true (i.e., set to true) further supports transmitting an HE TB PPDU using UL MU-MIMO within a RU that does not span (spread) across the entire PPDU bandwidth, the STA sets dot11HEPartialBWULMUMIMOImplemented to true and sets the Partial Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field within the HE Capabilities element transmitted by the STA to 1. Otherwise, the STA sets dot11HEPartialBWULMUMIMOImplemented to false and sets the Partial Bandwidth UL MU-MIMO subfield to 0.

[0208] "Does not span across the entire PPDU bandwidth" may mean using a part of the bandwidth within the PPDU bandwidth. That is also acceptable.

[0209] The PPDU bandwidth may be the bandwidth used for the Triggering frame. The PPDU bandwidth may be the bandwidth indicated by the U-SIG signal. The PPDU bandwidth may be determined by the CH_BANDWIDTH parameter.

[0210] The AP sets the Partial Bandwidth UL in the HE PHY Capabilities Information field where the AP is 1. For non-AP STAs that have not received an HE Capabilities element with a MU-MIMO subfield, the AP will not send a trigger frame requesting the transmission (or OFDMA transmission) of an HE TB PPDU using UL MU-MIMO within a RU that does not span the entire PPDU bandwidth. In other words, if an AP receives an HE Capabilities element with a Partial Bandwidth UL MU-MIMO subfield set to 1 from a non-AP STA, it may send a trigger frame to that non-AP STA requesting the transmission of an HE TB PPDU using UL MU-MIMO within a RU of partial bandwidth. .

[0211] APs require non-AP STAs that did not receive an HE Capabilities element with a Full Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field (where AP is 1) to transmit an HE TB PPDU using UL MU-MIMO within a RU that spans the entire PPDU bandwidth. The trigger frame will not be sent. In other words, if the AP receives an HE Capabilities element with a Full Bandwidth UL MU-MIMO subfield set to 1 from a non-AP STA, Alternatively, a trigger frame may be sent to the non-AP STA requesting the transmission of an HE TB PPDU using UL MU-MIMO with a Full bandwidth RU.

[0212] If an AP sets the Partial Bandwidth UL MU-MIMO subfield of the HE PHY Capabilities Information field of the HE Capabilities element transmitted by the AP to 1, then in a certain RU, MU-MIMO The HE TB PPDU supports receiving the RU. The size of the RU is 106 tones or more, and the RU does not span the entire PPDU bandwidth.

[0213] HE PHY Capabilities Information f of the HE Capabilities element sent by non-AP STA A non-AP STA that sets the ield's Partial Bandwidth UL MU-MIMO subfield to 1 supports transmitting a RU in an HE TB PPDU where UL MU-MIMO is used in that RU. The size of the RU is 10⁶ tones or greater, and the RU is allocated across the entire PPDU bandwidth. I can't.

[0214] The Full Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field indicates to the AP support for MU-MIMO reception of HE TB PPDUs in RUs allocated across the entire PPDU bandwidth (i.e., it indicates UL MU-MIMO support). If the capability indicated by this subfield is supported, it is set to 1, and support If it is not set, it will be set to 0.

[0215] The Full Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field indicates support for MU-MIMO transmission of HE TB PPDUs in RUs allocated across the entire PPDU bandwidth for non-AP STAs (i.e., support for UL MU-MIMO). The capability indicated by this subfield is set to 1 if supported, and to 0 if not supported.

[0216] The Partial Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field indicates to the AP that it is capable of receiving HE TB PPDUs in RUs where MU-MIMO is used. This indicates support for UL MU-MIMO in OFDMA. The RU is allocated not across the entire PPDU bandwidth (i.e., partially). The capability indicated is set to 1 if it is supported, and to 0 if it is not supported. Here, the RU is 106-tone or greater.

[0217] The Partial Bandwidth UL MU-MIMO subfield in the HE PHY Capabilities Information field transmits HE TB PPDUs to non-AP STAs in RUs where MU-MIMO is used. This indicates support for (i.e., support for UL MU-MIMO in OFDMA). It is allocated not across the entire PPDU bandwidth (i.e., partially). If the capability indicated by the subfield is supported, it is set to 1 and supports If not, it is set to 0. Here, the RU is 106-tone or greater. It is iRU.

[0218] The STA that sets the Partial Bandwidth UL MU-MIMO subfield to 1 is HE PHY Capabilities. Set the Full Bandwidth UL MU-MIMO subfield of the Information field to 1.

[0219] An EHT STA with dot11EHTPartialBWULMUMIMOImplemented that is true (i.e., set to true) sets the Partial Bandwidth UL MU-MIMO subfield of the EHT PHY Capabilities Information field within the EHT Capabilities element to 1. An EHT STA with dot11EHTPartialBWULMUMIMOImplemented that is false sets the Partial Bandwidth UL MU-MIMO subfield of the EHT PHY Capabilities Information field within the EHT Capabilities element to 0. do.

[0220] For non-AP STAs that did not receive an EHT Capabilities element with a Partial Bandwidth UL MU-MIMO subfield in the EHT PHY Capabilities Information field where the AP is 1, the AP uses UL MU-MIMO within a RU or MRU that does not extend across the entire PPDU bandwidth. Do not send a trigger frame requesting transmission (or OFDMA transmission) using EHT TB PPDU. In other words, if an AP receives an EHT Capabilities element with a Partial Bandwidth UL MU-MIMO subfield set to 1 from a non-AP STA, it will request that the non-AP STA to send an EHT TB PPDU using UL MU-MIMO with a Partial Bandwidth RU or MRU. You may send a rigger frame.

[0221] The AP sets the Partial Bandwidth UL MU-MIMO subfield of the EHT PHY Capabilities Information field of the EHT Capabilities element transmitted by the AP to 1. It supports receiving the RU or MRU in EHT TB PPDU where MU-MIMO is used. The subfield is determined by dot11EHTPartialBWULMUMIMOImplemented. The size of the RU or MRU is 242 tones or more, and there are multiple RUs or MRUs within the PPDU bandwidth. ru.

[0222] EHT PHY Capabilities Information of the EHT Capabilities element transmitted by non-AP STA The non-AP STA, which sets the Partial Bandwidth UL MU-MIMO subfield of a field to 1, transmits a RU or MRU in an EHT TB PPDU where UL MU-MIMO is used in that RU or MRU. It supports the following. The subfield is determined by dot11EHTPartialBWULMUMIMOImplemented. The size of the RU or MRU is 242 tones or greater, and there are multiple RUs or MRUs within the PPDU bandwidth.

[0223] The non-AP EHT STA supports non-OFDMA UL MU-MIMO transmission where the size of all RUs or MRUs is 242 tones or larger within the supported bandwidth.

[0224] The Partial Bandwidth UL MU-MIMO subfield in the EHT PHY Capabilities Information field indicates support for the AP to receive EHT TB PPDUs in RUs or MRUs where MU-MIMO is used (i.e., it indicates support for UL MU-MIMO within OFDMA). The RU or MRU is allocated without extending across the entire PPDU bandwidth (i.e., partially). If the capability indicated by the subfield is supported, it will be set to 1. If not supported, it is set to 0. Here, the RU or MRU is 242-tone or greater.

[0225] The Partial Bandwidth UL MU-MIMO subfield in the EHT PHY Capabilities Information field indicates support for sending EHT TB PPDUs in RUs or MRUs where MU-MIMO is used to non-AP STAs (i.e., support for UL MU-MIMO within OFDMA). (This indicates...). The RU or MRU is allocated without extending across the entire PPDU bandwidth. The capability indicated by the subfield is set to 1 if supported, and to 0 if not supported. Here, the RU or MRU is a 242-tone or larger RU.

[0226] The combined total of all users' spatial streams for UL MU-MIMO in HE TB PPDU The total is 8 or less.

[0227] The total number of spatial streams for UL MU-MIMO across all users in EHT TB PPDU is 8 or less.

[0228] For DL ​​and UL, the maximum number of EHT STAs that can be multiplexed using one RU or MRU is 8. Yes. This applies to both non-OFDMA UL MU-MIMO transmissions and MU-MIMO transmissions within EHT PPDUs consisting of more than one RU or MRU within the PPDU bandwidth.

[0229] Next, UL MU when dRU is added (or supported) to RU Allocation type Let's explain the operation.

[0230] A UHR STA with dot11UHRPartialBWULMUMIMOImplemented that is true (i.e., set to true) is in the UHR PHY Capabilities Information field within the UHR Capabilities element. Set the Partial Bandwidth UL MU-MIMO subfield of eld to 1. For UHR STAs with dot11UHRPartialBWULMUMIMOImplemented which is false, set the Partial Bandwidth UL MU-MIMO subfield of the UHR PHY Capabilities Information field within the UHR Capabilities element to 0. do.

[0231] An AP will not send a trigger frame to a non-AP STA that has not received a UHR Capabilities element with a Partial Bandwidth UL MU-MIMO subfield in the UHR PHY Capabilities Information field set to 1, requesting transmission (or OFDMA transmission) using UHR TB PPDU with UL MU-MIMO within the rRU or MrRU and / or dRU or MdRU that do not span the entire PPDU bandwidth. In other words, if an AP receives a UHR Capabilities element with a Partial Bandwidth UL MU-MIMO subfield set to 1 from a non-AP STA, To the non-AP STA, send a trigger frame requesting the transmission of a UHR TB PPDU using UL MU-MIMO on a Partial bandwidth rRU or MrRU and / or dRU or MdRU. That's good too.

[0232] The AP sets the Partial Bandwidth UL MU-MIMO subfield of the UHR PHY Capabilities Information field of the UHR Capabilities element transmitted by the AP to 1, and then a certain rRU or MrRU It supports receiving the rRU or MrRU and / or dRU or MdRU in a UHR TB PPDU where MU-MIMO is used in the dRU or MdRU. The subfield may be determined by dot11UHRPartialBWULMUMIMOImplemented. The size of the rRU or MrRU may be 242 tones or more, and the size of the dRU or MdRU may be M-tones or more. There may be multiple rRUs or MrRUs and / or dRUs or MdRUs within the PPDU bandwidth.

[0233] UHR PHY Capabilities Information of the UHR Capabilities element sent by non-AP STA A non-AP STA that sets the Partial Bandwidth UL MU-MIMO subfield of a field to 1 supports transmitting a certain rRU or MrRU and / or dRU or MdRU in a UHR TB PPDU where UL MU-MIMO is used in that rRU or MrRU and / or dRU or MdRU. The subfield is determined by dot11UHRPartialBWULMUMIMOImplemented. The rRU also The size of MrRU is 242 tones or more, and the size of the corresponding dRU or MdRU is M tones or more. This is also acceptable. Furthermore, there may be multiple rRUs or MrRUs and / or dRUs or MdRUs within the PPDU bandwidth.

[0234] Non-AP UHR STA may support non-OFDMA UL MU-MIMO transmission where the size of all rRUs or MrRUs is 242 tones or greater within the supported bandwidth. Support may be indicated by the UL MU-MIMO subfield.

[0235] A non-AP UHR STA may support non-OFDMA UL MU-MIMO transmissions where the size of all dRUs or MdRUs is greater than or equal to M tones within the supported bandwidth. This support may be indicated by the Non-OFDMA UL MU-MIMO subfield.

[0236] The Partial Bandwidth UL MU-MIMO subfield in the UHR PHY Capabilities Information field may indicate to the AP support for receiving UHR TB PPDUs in rRUs or MrRUs and / or dRUs or MdRUs where MU-MIMO is used (i.e., it may indicate support for UL MU-MIMO within OFDMA). The rRUs or MrRUs and / or dRUs or MdRUs may be allocated without extending across the entire PPDU bandwidth (i.e., partially). The capability indicated by the subfield is set to 1 if supported, and to 0 if not supported.

[0237] Partial Bandwidth UL MU-MIMO s included in the UHR PHY Capabilities Information field ubfield may indicate support for sending UHR TB PPDUs in rRU or MrRU and / or dRU or MdRU where MU-MIMO is used to non-AP STAs (i.e. (and may indicate support for UL MU-MIMO within OFDMA). The rRU or MrRU and / or dRU or MdRU are allocated not across the entire PPDU bandwidth (i.e., partially). It may be set to 1 if the capability indicated by the subfield is supported, and to 0 if it is not supported.

[0238] MU-MIMO within OFDMA is used for all RU Allocation types: rRU / MrRU / dRU / MdRU. The ported AP and / or non-AP STA may set the Partial Bandwidth UL MU-MIMO subfield in the UHR PHY Capabilities Information field to 1. , UL MU-MIMO support in rRU by one Partial Bandwidth UL MU-MIMO subfield Support for UL MU-MIMO in the t and dRU may be indicated.

[0239] The rRU or MrRU may be 242-tone or larger.

[0240] The dRU or MdRU may be an M-tone or a larger RU.

[0241] Here, the value of M may be less than 242. For example, the value of M may be 26. For example, the value of M may be 52. For example, the value of M may be 106. Unless additional conditions are met, the RU size M of dRU can be defined similarly. For example, an AP does not need to send a trigger frame requesting the transmission (or OFDMA transmission) of dRUs less than M-tones using UL MU-MIMO. Also, if such a trigger frame is received, a non-AP STA may ignore the received trigger frame.

[0242] Here, if the value of M is 242 or greater, then the distribution BW is 40MHz or 80MHz or The bandwidth may be wider than 80 MHz. In such cases, the distribution BW including dRU using UL MU-MIMO may have a bandwidth wider than 40 MHz or 80 MHz or 80 MHz. That is, if the distribution BW is 20 MHz, the AP does not need to send a trigger frame requesting the transmission (or OFDMA transmission) of dRU using UL MU-MIMO. Also, if a non-AP STA receives such a trigger frame, it may ignore the received trigger frame.

[0243] A UHR STA with dot11UHRPartialBWULMUMIMOForRRUImplemented that is true (i.e., set to true) sets the Partial Bandwidth UL MU-MIMO for rRU subfield in the UHR PHY Capabilities Information field within the UHR Capabilities element to 1. A UHR STA with dot11UHRPartialBWULMUMIMOForRRUImplemented that is false sets the Partial Bandwidth UL MU-MIMO for rRU subfield in the UHR PHY Capabilities Information field within the UHR Capabilities element to 0.

[0244] A UHR STA with dot11UHRPartialBWULMUMIMOForDRUImplemented that is true (i.e., set to true) sets the Partial Bandwidth UL MU-MIMO for dRU subfield of the UHR PHY Capabilities Information field within the UHR Capabilities element to 1. A UHR STA with dot11UHRPartialBWULMUMIMOForDRUImplemented that is false sets the Partial Bandwidth UL MU-MIMO for dRU subfield of the UHR PHY Capabilities Information field within the UHR Capabilities element to 0.

[0245] Depending on whether the RU Allocation type is rRU or dRU, a PHY capability information subfield for UL MU-MIMO may be defined accordingly.

[0246] APs that did not receive a UHR Capabilities element with a Partial Bandwidth UL MU-MIMO for rRU subfield in the UHR PHY Capabilities Information field where AP is 1 are non-AP S The AP does not send a trigger frame to the TA requesting the transmission (or OFDMA transmission) of a UHR TB PPDU using UL MU-MIMO within an rRU or MrRU that does not span the entire PPDU bandwidth. In other words, if the AP receives a UHR Capabilities element with a Partial Bandwidth UL MU-MIMO for rRU subfield set to 1 from a non-AP STA, it will not send a trigger frame to the non-AP STA requesting the transmission of a UHR TB PPDU using UL MU-MIMO within a Partial Bandwidth rRU or MrRU. You may send a trigger frame to make the request.

[0247] An AP will not send a trigger frame to a non-AP STA that has not received a UHR Capabilities element with the Partial Bandwidth UL MU-MIMO for dRU subfield set to 1 in the UHR PHY Capabilities Information field, requesting the transmission (or OFDMA transmission) of a UHR TB PPDU using UL MU-MIMO within a dRU or MdRU that does not span the entire PPDU bandwidth. In other words, if an AP receives a UHR Capabilities element with the Partial Bandwidth UL MU-MIMO for dRU subfield set to 1 from a non-AP STA, it will not send a trigger frame to that non-AP STA requesting the transmission of a UHR TB PPDU using UL MU-MIMO within a dRU or MdRU of partial bandwidth. You may send a trigger frame to make the request.

[0248] The AP sets the Partial Bandwidth UL MU-MIMO for rRU subfield to 1 in the UHR PHY Capabilities Information field of the UHR Capabilities element transmitted by the AP, and if there is an rRU, In MrRU, MU-MIMO is used to receive the rRU or MrRU in UHR TB PPDU. It is ported. The subfield may be determined by dot11UHRPartialBWULMUMIMOForRRUImplemented. The size of the rRU or MrRU may be 242 tones or more. Also, there may be multiple rRUs or MrRUs within the PPDU bandwidth.

[0249] The AP sets the Partial Bandwidth UL MU-MIMO for dRU subfield to 1 in the UHR PHY Capabilities Information field of the UHR Capabilities element transmitted by the AP, and a certain dRU In MdRU, MU-MIMO is used in UHR TB PPDU to receive the dRU or MdRU. It is ported. The subfield may be determined by dot11UHRPartialBWULMUMIMOForDRUImplemented. The size of the dRU or MdRU may be M-tones or greater. Also, PPDU There may be multiple dRUs or MdRUs within the bandwidth.

[0250] UHR PHY Capabilities Information of the UHR Capabilities element sent by non-AP STA The non-AP STA sets the Partial Bandwidth UL MU-MIMO for rRU subfield of a field to 1, and in a UHR TB PPDU where UL MU-MIMO is used in a certain rRU or MrRU, It supports sending the following subfield, which is determined by dot11UHRPartialBWULMUMIMOForRRUImplemented. The size of the rRU or MrRU may be 242 tones or more. There may also be multiple rRUs or MrRUs within the PPDU bandwidth.

[0251] UHR PHY Capabilities Information of the UHR Capabilities element sent by non-AP STA The non-AP STA sets the Partial Bandwidth UL MU-MIMO for dRU subfield of a field to 1, and in a UHR TB PPDU where UL MU-MIMO is used in a certain dRU or MdRU, It supports sending the following subfield, which is determined by dot11UHRPartialBWULMUMIMOForDRUImplemented. The size of the dRU or MdRU may be M tones or greater. There may also be multiple dRUs or MdRUs within the PPDU bandwidth.

[0252] Non-AP UHR STAs may support non-OFDMA UL MU-MIMO transmissions at all rRU or MrRU sizes, each of 242 tones or greater, within the supported bandwidth. This support may be indicated by the Non-OFDMA UL MU-MIMO for rRU subfield.

[0253] non-AP UHR STA supports all dRUs with a supported bandwidth of M tones or more. Alternatively, it may support non-OFDMA UL MU-MIMO transmission at MdRU size. This is Non-OFD Support may be indicated by the MA UL MU-MIMO for dRU subfield.

[0254] non-AP UHR STA is all dRU with a supported bandwidth of less than M tones. Alternatively, OFDMA transmission without UL MU-MIMO at MdRU size may be supported.

[0255] The Partial Bandwidth UL MU-MIMO for rRU subfield in the UHR PHY Capabilities Information field may indicate to the AP support for receiving UHR TB PPDUs in an rRU or MrRU where MU-MIMO is used (i.e., it may indicate support for UL MU-MIMO within OFDMA in the rRU). The rRU or MrRU may spread across the entire PPDU bandwidth. It may be assigned without being fully supported (i.e., partially supported). The capability is set to 1 if it is supported, and to 0 if it is not supported.

[0256] The Partial Bandwidth UL MU-MIMO for rRU subfield in the UHR PHY Capabilities Information field may indicate support for non-AP STAs to transmit UHR TB PPDUs in an rRU or MrRU where MU-MIMO is used (i.e., it may indicate support for UL MU-MIMO within OFDMA in the rRU). The rRU or MrRU is PPDU bandwidth It may be allocated only partially, not spread across the entire area. If the capability is supported, it is set to 1; if not, it is set to 0.

[0257] The Partial Bandwidth UL MU-MIMO for dRU subfield in the UHR PHY Capabilities Information field may indicate to the AP support for receiving UHR TB PPDUs in a dRU or MdRU where MU-MIMO is used (i.e., it may indicate support for UL MU-MIMO within OFDMA in the dRU). The dRU or MdRU may spread across the entire PPDU bandwidth. It may be assigned without being fully supported (i.e., partially supported). The capability is set to 1 if it is supported, and to 0 if it is not supported.

[0258] The Partial Bandwidth UL MU-MIMO for dRU subfield in the UHR PHY Capabilities Information field may indicate support for non-AP STAs to transmit UHR TB PPDUs in dRUs or MdRUs where MU-MIMO is used (i.e., it may indicate support for UL MU-MIMO within OFDMA in the dRU). The dRU or MdRU is PPDU bandwidth It may be allocated only partially, not spread throughout. If the capability indicated by the subfield is supported, it will be set to 1; if not supported, it will be set to 1. If so, it may be set to 0.

[0259] If an AP sets both the Partial Bandwidth UL MU-MIMO for rRU subfield and the Partial Bandwidth UL MU-MIMO for dRU subfield of the UHR PHY Capabilities Information field of the UHR Capabilities element transmitted by the AP to 1, then the AP will use MU-MIMO in a UHR TB PPDU where MU-MIMO is used in a given rRU or MrRU and dRU or MdRU. It sometimes supports receiving data.

[0260] If the AP indicates support for receiving UHR TB PPDUs that include both rRU (or MrRU) and dRU (or MdRU) within the PPDU bandwidth using UL MU-MIMO, for example, Both Partial Bandwidth UL MU-MIMO for rRU subfield and Partial Bandwidth UL MU-MIMO for dRU subfield may be set to 1.

[0261] If the AP indicates support for receiving UHR TB PPDUs that include both rRU (or MrRU) and dRU (or MdRU) within the PPDU bandwidth using UL MU-MIMO, then 1 may be set for both the subfield indicating support for receiving rRU or MrRU using UL MU-MIMO and the subfield indicating support for receiving dRU or MdRU using UL MU-MIMO.

[0262] If the AP indicates support for receiving UHR TB PPDUs that include both rRU (or MrRU) and dRU (or MdRU) within the PPDU bandwidth using UL MU-MIMO, for example, The subfield indicating support for receiving hybrid mode TB PPDU using UL MU-MIMO may be set to 1.

[0263] Here, a UHR TB PPDU that includes both rRU (or MrRU) and dRU (or MdRU) within the PPDU bandwidth may be referred to as a hybrid mode TB PPDU.

[0264] The AP sets the Full Bandwidth UL MU-MIMO for dRU subfield to 1 in the UHR PHY Capabilities Information field of the UHR Capabilities element transmitted by the AP, which supports receiving a dRU or MdRU in a UHR TB PPDU where MU-MIMO is used in that dRU or MdRU. The subfield is determined by dot11UHRFullBWULMUMIMOForDRUImplemented. This is also possible. The size of the dRU or MdRU may be M-tones or greater. Furthermore, there may be multiple dRUs or MdRUs within the PPDU bandwidth.

[0265] UHR PHY Capabilities Information of the UHR Capabilities element sent by non-AP STA The non-AP STA sets the field's Full Bandwidth UL MU-MIMO for dRU subfield to 1. , in a UHR TB PPDU where UL MU-MIMO is used in a certain dRU or MdRU, It supports sending. The subfield is determined by dot11UHRFullBWULMUMIMOForDRUImplemented. The size of the dRU or MdRU may be greater than or equal to M tones. Furthermore, there may be multiple dRUs or MdRUs within the PPDU bandwidth.

[0266] APs did not receive a UHR Capabilities element with a Full Bandwidth UL MU-MIMO for dRU subfield in the UHR PHY Capabilities Information field where the AP is 1. (non-AP STA) In contrast, UL MU-MIMO is used within a dRU or MdRU that spans the entire PPDU bandwidth. It does not send a trigger frame requesting the transmission of a UHR TB PPDU. In other words, the AP is a non-AP. If a UHR Capabilities element with a Full Bandwidth UL MU-MIMO for dRU subfield set to 1 is received from an STA, a trigger frame may be sent to the non-AP STA requesting it to transmit a UHR TB PPDU using UL MU-MIMO with a Full Bandwidth dRU or MdRU.

[0267] The Full Bandwidth UL MU-MIMO for dRU subfield in the UHR PHY Capabilities Information field indicates the UHR TB PPDU for dRUs or MdRUs where MU-MIMO is used, for APs. Support for receiving may be indicated (i.e., support for UL MU-MIMO within OFDMA in the dRU). The dRU or MdRU may have its constituent resources (subcarriers, tones) spread across the entire PPDU bandwidth. The capability may be set to 1 if supported, and to 0 if not supported.

[0268] The Full Bandwidth UL MU-MIMO for dRU subfield in the UHR PHY Capabilities Information field may indicate support for transmitting UHR TB PPDUs in a dRU or MdRU where MU-MIMO is used to a non-AP STA (i.e., it may indicate support for UL MU-MIMO within OFDMA in the dRU). The dRU or MdRU is configured The resulting resources (subcarriers, tones) may be allocated across the entire PPDU bandwidth. This capability may be set to 1 if supported, and to 0 if not supported.

[0269] Next, the PHY Capabilities Information field or MAC Capabilities Information field of the UHR Capabilities element indicates whether it supports dRU for RU Allocation type. This document describes UL MU operations when the dRU Support subfield is included.

[0270] AP sets a value (e.g., 1) from a non-AP STA to indicate that it supports dRU. If an AP receives a UHR Capabilities element containing a dRU Support subfield, the AP may send a Trigger frame to the non-AP STA requesting it to send (or OFDMA send) a UHR TB PPDU using UL MU-MIMO in the dRU or MdRU.

[0271] For non-AP STAs that did not receive a UHR Capabilities element with a dRU Support subfield in the UHR PHY Capabilities Information field where the AP is 1, the AP will use a UHR TB PPDU that uses UL MU-MIMO within a dRU or MdRU that does not extend across the entire PPDU bandwidth. Do not send a trigger frame requesting transmission (or OFDMA transmission).

[0272] An AP does not need to send a trigger frame requesting the transmission of a UHR TB PPDU using UL MU-MIMO to a non-AP STA that does not allocate a dRU (i.e., allocates an rRU). Whether an AP sends a trigger frame requesting the transmission of a UHR TB PPDU using UL MU-MIMO (or OFDMA transmission) to a non-AP STA that allocates an rRU is determined based on whether the non-AP STA has set the Partial Bandwidth UL MU-MIMO subfield for the rRU to 1. You may do so.

[0273] The AP requires non-AP STAs that did not receive a UHR Capabilities element with the dRU Support subfield in the UHR PHY Capabilities Information field where the AP is 1 to transmit a UHR TB PPDU using UL MU-MIMO within the dRU or MdRU across the entire PPDU bandwidth. Do not send the requested Trigger frame.

[0274] The AP sends a trigger frame to non-AP STAs that do not allocate dRUs with a RU size of M-tones or larger (i.e., allocate dRUs with a RU size of less than M-tones), requesting the transmission of a UHR TB PPDU using UL MU-MIMO within a dRU that does not span the entire PPDU bandwidth or within an MdRU. I don't believe it.

[0275] For non-AP STAs that do not allocate dRUs with a RU size of M-tones or more (i.e., allocate dRUs with a RU size of less than M-tones), the AP will allocate dRUs across the entire PPDU bandwidth. It does not send a trigger frame requesting the transmission of a UHR TB PPDU using UL MU-MIMO within the MdRU.

[0276] The dRU Support subfield may indicate to the AP support for receiving UHR TB PPDUs using dRU or MdRU. The capability indicated by the subfield may be set to 1 if it is supported, and to 0 if it is not supported.

[0277] The dRU Support subfield may indicate support for sending UHR TB PPDUs using dRU or MdRU to non-AP STAs. The capability indicated by the subfield may be set to 1 if supported, and to 0 if not supported.

[0278] When an AP assigns a dRU to a non-AP STA, if the RU size of the dRU is less than M-tones, it sends a trigger frame requesting OFDMA transmission of a UHR TB PPDU without using UL MU-MIMO. That's fine.

[0279] When an AP assigns a dRU to a non-AP STA, if the RU size of the dRU is M-tones or greater, it sends a trigger frame requesting OFDMA transmission of a UHR TB PPDU using UL MU-MIMO. That's good too.

[0280] The Non-OFDMA UL MU-MIMO (BW ≤ 80 MHz) subfield indicates support for non-OFDMA UL MU-MIMO reception of TB PPDU for APs with 20, 40, and 80 MHz PPDU bandwidths. If the subfield is set to 1, the AP does not need to send a trigger frame requesting the transmission of a hybrid mode TB PPDU within the PPDU bandwidth. If the subfield is set to 0, the AP may send a trigger frame requesting the transmission of a hybrid mode TB PPDU within the PPDU bandwidth.

[0281] The Non-OFDMA UL MU-MIMO (BW = 160 MHz) subfield indicates to the AP support for non-OFDMA UL MU-MIMO reception of TB PPDU within a 160 MHz PPDU bandwidth. If the subfield is set to 1, the AP does not need to send a trigger frame requesting the transmission of hybrid mode TB PPDU within the PPDU bandwidth. If the subfield is set to 0, the AP may send a trigger frame requesting the transmission of hybrid mode TB PPDU within the PPDU bandwidth.

[0282] The Non-OFDMA UL MU-MIMO (BW = 320 MHz) subfield indicates to the AP support for non-OFDMA UL MU-MIMO reception of TB PPDU within a 320 MHz PPDU bandwidth. If the subfield is set to 1, the AP does not need to send a trigger frame requesting the transmission of hybrid mode TB PPDU within the PPDU bandwidth. If the subfield is set to 0, the AP may send a trigger frame requesting the transmission of hybrid mode TB PPDU within the PPDU bandwidth.

[0283] Figure 15 shows a Capabilities element for UL MU operation according to one aspect of this embodiment. This figure shows an example of the procedure related to transmission. The AP or non-AP STA sets a value in the subfield corresponding to the capability information for UL MU-MIMO in the dRU (S1501). For example, if the capability is supported, it is set to 1 and supports If not, it may be set to 0. AP or non-AP STA each transmits a Capabilities element with a Capabilities Information field that includes the subfield (S1 502).

[0284] Figure 16 shows an example of an AP procedure for UL MU operation according to one aspect of this embodiment. The AP receives a Capabilities element from a non-AP STA (S1601). The AP decides whether to apply UL MU-MIMO when assigning a dRU to the non-AP STA. Determined based on the received Capabilities element. Apply UL MU-MIMO to the dRU. If so, the RU size of the dRU is determined to be M-tones or greater (S1602). The AP sends a trigger frame (triggering frame) containing one or more subfields related to the dRU to the non-AP STA (S1603).

[0285] Thus, for dRU or MdRU, UL MU-MIMO or UL MU-MIMO within OFDMA (UL Both MU-MIMO and UL OFDMA may be applied.

[0286] Next, we will describe the RU Allocation procedure when dRU is added (or applicable) to the RU Allocation type.

[0287] An AP according to one aspect of this embodiment uses a trigger frame to perform one or more non-AP STA Resources (RUs) may be allocated to enable UL MU operations. For non-AP STAs, the tones that make up the RU within a specific DBW (distribution bandwidth) By diffusing (i.e., dispersing), the limitations on power spectral density (PSD) are removed. Furthermore, to boost the transmit power, dRU may be applied to the RU Allocation type. When transmitting using dRU, dRU transmission may be applied to OFDMA UHR TB PPDU to maximize the power boost gain of each dRU. When transmitting using dRU, UL MU-MIMO may not be applied. When dRU is applied, the maximum number of spatial streams may be 2.

[0288] Furthermore, AP uses the Trigger frame to target one or more non-AP STAs. RUs may be placed. The AP may indicate the determined RU type (DRU or RRU) for each of the 80MHz frequency subblocks included in the Bandwidth using the DRU / RRU Indication subfield included in the Common Info subfield of the Trigger frame.

[0289] Furthermore, when the AP applies RRU mode to a UL TB PPDU, it may set all bits in the DRU / RRU Indication subfield to 0. In other words, the AP may implement RRU mode by setting all bits in the DRU / RRU Indication subfield to 0.

[0290] Furthermore, when the AP applies DRU mode to an UL TB PPDU, it may set all bits in the DRU / RRU Indication subfield to 1. In other words, the AP may implement hybrid mode by including bits set to 0 and bits set to 1 in the DRU / RRU Indication subfield.

[0291] Furthermore, when the AP applies a hybrid mode including DRU and RRU to a UL TB PPDU, at least one bit among all the bits in the DRU / RRU Indication subfield may be set to a different value from the other bits. In other words, the AP may implement RRU mode by setting all the bits in the DRU / RRU Indication subfield to 0.

[0292] If the Bandwidth indicated by the UL BW subfield and / or UL Bandwidth Extension subfield is 80 MHz, the last three bits of the four bits in the DRU / RRU Indication subfield may be reserved. In other words, the first bit in the DRU / RRU Indication subfield may be used to indicate the 80 MHz RU type.

[0293] If the Bandwidth indicated by the UL BW subfield and / or UL Bandwidth Extension subfield is 160MHz, then of the 4 bits contained in the DRU / RRU Indication subfield, the last 2 bits The first entry in the DRU / RRU Indication subfield may be reserved. The two bits may be used to indicate the RU type of the corresponding 80MHz frequency subblock.

[0294] If the Bandwidth indicated by the UL BW subfield and / or UL Bandwidth Extension subfield is 320MHz, the four bits contained in the DRU / RRU Indication subfield may be used to indicate the RU type of the corresponding 80MHz frequency subblock.

[0295] non-AP STA is obtained from the Bandwidth and DRU / RRU Indication subfields for TB PPDU. , RRU mode where all of the 80MHz frequency subblocks included in the Bandwidth consist only of RRUs, or , You may also need to determine whether it is a DRU mode consisting entirely of DRUs, or a hybrid mode in which the bandwidth includes at least one 80MHz frequency subblock corresponding to both RRUs and DRUs.

[0296] For non-AP STA, in RRU mode, the RU size and the corresponding RU index are determined from the values ​​set in the bits corresponding to B7-B1 of the Bandwidth and RU Allocation subfields. The non-AP STA also determines the PS160 subfield and the value of the bit corresponding to B0 of the RU Allocation subfield, as well as the Primary 80 MHz channel, Secondary 80 MHz channel, and Secondary 160 MHz channel. From the configuration showing the frequency sequence of the z channel, the N value associated with the 80MHz frequency subblock to which the RU is assigned is determined. The non-AP STA uses the N value and the RU index to determine the Bandwidth Determine the corresponding PHY RU index and allocate resources from the subcarrier index (tone index) indicated by that PHY RU index.

[0297] If a non-AP STA indicates that a frame is a trigger frame based on the Type subfield and subtype subfield in the Frame Control field of the received MAC header, it will determine whether the Common Info field and User Info field of the trigger frame are HE / EHT / UHR variants. The non-AP STA may also determine (judge, determine) whether a frame is one of the HE / EHT / UHR variants based on the combination of values ​​set in the various subfields contained in the Common Info field and / or User Info field.

[0298] If non-AP STA determines that the trigger frame is an EHT variant, it determines the bandwidth from the values ​​set in the UL BW subfield and UL Bandwidth Extension subfield included in the Common Info field.

[0299] The non-AP STA determines the Bandwidth, the value of N corresponding to the 80MHz frequency subblock for locating the RU from the bit corresponding to B0 in the RU Allocation subfield included in the User Info field, the value set in the PS160 subfield, and the Configuration which shows the frequency sequence of Primary 80MHz channel, Secondary 80MHz channel, and Secondary 160MHz channel obtained from the Operation element of the Beacon frame.

[0300] The non-AP STA determines the RU size and the corresponding RU index from the values ​​set in bits B7-B1 of the Bandwidth and RU Allocation subfields.

[0301] The non-AP STA determines the PHY RU index from the RU index and the N value.

[0302] The non-AP STA determines a table for Data and pilot subcarrier indices corresponding to the bandwidth, and then determines the subcarrier index to which RUs are allocated from that table, the RU size, and the PHY RU index.

[0303] If non-AP STA determines (judges, confirms) that the trigger frame is a UHR variant, it determines the bandwidth from the values ​​set in the UL BW subfield and UL Bandwidth Extension subfield included in the Common Info field.

[0304] The non-AP STA determines the Bandwidth, the value of N corresponding to the 80MHz frequency subblock for locating the RU from the bit corresponding to B0 in the RU Allocation subfield included in the User Info field, the value set in the PS160 subfield, and the Configuration which shows the frequency sequence of Primary 80MHz channel, Secondary 80MHz channel, and Secondary 160MHz channel obtained from the Operation element of the Beacon frame.

[0305] If the non-AP STA determines that the trigger frame is a UHR variant, it determines the RU type of each 80MHz frequency subblock in the Bandwidth from the DRU / RRU Indication subfield included in the Common Info field. The non-AP STA determines the RU type of the 80MHz frequency subblock where the RU is located from the value of N and the said DRU / RRU Indication subfield.

[0306] The non-AP STA applies a table to the RU Allocation subfield according to the RU type and determines the RU size of the allocated RU and the corresponding RU index.

[0307] If the RU type of the 80MHz frequency subblock where the RU is located is RRU, then non-AP STA is... The table used for the RU Allocation subfield is the same as the table used for the EHT variant. You may use the same table.

[0308] Here, Figure 17 shows an example of a table used for the RU Allocation subfield when the RU type is RRU according to one aspect of this embodiment. The table used in contrast is used to determine the RU or MRU size and RU or MRU index from the PS160 subfield, bits B7-B0 of the RU Allocation subfield, and Bandwidth.

[0309] Non-AP STA may determine the RU size and the corresponding RU index using the table shown in Figure 17, based on the values ​​set in bits B7-B1 of the Bandwidth and RU Allocation subfields.

[0310] The non-AP STA determines the PHY RU index from the RU index and the N value.

[0311] The non-AP STA determines a table for Data and pilot subcarrier indices corresponding to the bandwidth, and then determines the subcarrier index to which RUs are allocated from that table, the RU size, and the PHY RU index.

[0312] If the RU type of the 80MHz frequency subblock where the RUs are located is DRU, non-AP STA determines the DBW from the value set in the DRU distribution BW subfield included in the User Info field, and then applies a table of RU Allocation subfields that is different from EHT according to the determined DBW. The RU size and corresponding RU index shown by the table may correspond to the RU size and RU index included in the table for Data and pilot subcarrier indices.

[0313] Here, Figure 18 shows an example of a table used for the RU Allocation subfield when the RU type is DRU according to one aspect of this embodiment. There is a table for each DBW size. It is acceptable to do so. An example table showing the DBW sizes for 20MHz, 40MHz, and 80MHz is provided. Yes, they are.

[0314] non-AP STA is derived from the values ​​set in cells B5-B1 of the RU Allocation subfield, and the RU included in the DBW is derived from these values. Determine the RU index corresponding to the size and RU size. Furthermore, determine the RU within the 80MHz frequency subblock based on the value of N set in B7B6 of the RU Allocation subfield. You may also decide on the location of the DBW to be deployed.

[0315] Alternatively, the non-AP STA may determine the RU size of the RUs included in the DBW, the RU index corresponding to the RU size, and the value of M corresponding to the location within the 80MHz frequency subblock of the DBW where the RUs are placed, from the values ​​set in B7-B1 of the RU Allocation subfield.

[0316] Non-AP STA may determine a DBW frequency subblock index indicating the location of DBWs within the bandwidth from the values ​​of N and M.

[0317] Non-AP STA may determine the DBW frequency subblock index, which indicates the DBW's location within the bandwidth, from the value set in the DBW location subfield included in the User Info field. The number of bits included in the DBW location subfield is determined from the bandwidth and the size of the DBW. It may be up to 4 bits. The number of bits included in the DBW location subfield may be changed depending on the Bandwidth and DBW size. For example, if the DBW is 20MHz and the Bandwidth is 20 For MHz or 40MHz, the DBW location subfield does not need to be included in the User Info subfield. Or, all bits included in the DBW location subfield may be reserved. Good. If DBW is 20MHz and Bandwidth is 80MHz, the DBW location subfield is 2 bits. The two bits may indicate the DBW location. The bits other than the two bits included in the DBW location subfield may be reserved. If the DBW is 20MHz and the Bandwidth is 160MHz, the DBW location subfield is 3 bits, and the DBW The location may be indicated. Other bits included in the DBW location subfield are not the three bits mentioned above. The bit may be reserved. If DBW is 20MHz and Bandwidth is 320MHz, the DBW location subfield may be 4 bits. If DBW is 40MHz and Bandwidth is 40MHz, the DBW location subfield may not be included in the User Info subfield. Alternatively, all bits included in the DBW location subfield may be reserved. If DBW is 40MHz and Bandwidth is 80MHz, the DBW location subfield is 1 bit, and that 1 bit The DBW location may be indicated by bits. If the DBW is 40MHz and the Bandwidth is 160MHz, the DBW location subfield may be 2 bits, and the DBW location may be indicated by these 2 bits. If the DBW is 40MHz and the Bandwidth is 320MHz, the DBW location subfield may be 3 bits, and the DBW location may be indicated by these 3 bits. If the DBW is 80MHz and the Bandwidth is 80MHz In this case, the DBW location subfield does not need to be included in the User Info subfield. Alternatively, all bits included in the DBW location subfield may be reserved. If the DBW is 80MHz and the Bandwidth is 160MHz, the DBW location subfield may be 1 bit, and that 1 bit may indicate the DBW location. If the DBW is 80MHz and the Bandwidth is 320MHz, the DBW location subfield may be 2 bits, and that 2 bits may indicate the DBW location.

[0318] The non-AP STA may determine the constant shift of the subcarrier index corresponding to the RU index from the Bandwidth, DBW, N values, and the DBW location. The constant shift is Bandwidth Even if determined from the value of N, DBW, and the location of the DBW within the 80MHz frequency subblock Good. For example, the constant shift may be determined based on a table like the one in Figure 19, using the Bandwidth, the value of N, the DBW, and the location of the DBW within the 80MHz frequency subblock. Figure 19 shows an example of the constant shift according to one aspect of this embodiment.

[0319] The non-AP STA determines the constant shift value used for the RU index from a table containing DBW, DBW frequency subblock index, Bandwidth, and constant shift value. You may do so.

[0320] Alternatively, the non-AP STA can be calculated by determining the DBW frequency subblock index from the DBW, N, and M values ​​using the formula (80 / DBW)*N+M.

[0321] Non-AP STA may determine a table from the DBW regarding data and pilot subcarrier indices corresponding to the DBW.

[0322] A non-AP STA may determine the subcarrier index to which RUs are allocated from the RU index corresponding to the RU size shown by the table of Data and pilot subcarrier indices corresponding to DBW, and from the constant shift (constant tone shift).

[0323] If the RU type of the 80MHz frequency subblock where the RU is located is RRU, the non-AP STA further determines whether the DRU / RRU Indication subfield contains bits indicating DRU (i.e., whether it is hybrid mode). If the bit is not included, the non-AP STA may apply the same table to the RU Allocation subfield as the table used for the EHT variant. If the DRU / RRU Indication subfield does not contain a bit indicating DRU, the non-AP STA applies the same table to the RU Allocation subfield as the table used for the EHT variant, but may recognize the B7-B1 values ​​indicating the RU index corresponding to a RU size equal to or greater than 242 tones as valid values. In other words, under these conditions... Furthermore, if non-AP STA determines from the values ​​set in B7-B1 of the RU Allocation subfield that the RU size is less than 242 tones, it may determine that the trigger frame is invalid.

[0324] Figure 20 shows an example of a procedure for determining the RU type according to one aspect of this embodiment. The non-AP STA receives a Trigger frame from the AP (S2001). The non-AP STA determines which variant (HE / EHT / UHR variant) the received Trigger frame corresponds to based on the values ​​set in the various Common Info fields and User Info fields of the Trigger frame, and performs reception processing (S2002). The non-AP STA then processes the UL BW contained in the Trigger frame. The Bandwidth is calculated from the values ​​set in the subfield and the UL Bandwidth Extension subfield. The non-AP STA determines the value of N corresponding to the 80MHz frequency subblock where the RU is placed, based on the Configuration for Bandwidth and frequency arrangement, the PS160 subfield, and the value set in B0 of the RU Allocation subfield (S2004). If the trigger frame is a UHR variant, the DRU / RRU Indication subfield is set. From the obtained values, the RU type for the 80MHz frequency subblock corresponding to the value of N is determined (S2005).

[0325] Figure 21 is a diagram showing the correspondence between DBW location and the value of M according to one aspect of this embodiment. 21(a) shows an example of the DBW location within the 80MHz frequency subblock where the RU is located. Figure 21(b) shows an example of DBW location when Bandwidth and DBW are the same. This shows that if DBW is 20MHz, there are four locations within the 80MHz frequency subblock. There is. If DBW is 40MHz, there are two locations within the 80MHz frequency subblock. The values ​​of M may be associated with each of these, such as 0, 1, 2, 3 or 0, 1. In this case, the value of M may be 0.

[0326] In cases where the RU type is DRU, the constant shift value may be determined using the N and M values.

[0327] Figure 22 is a diagram showing an example of a lookup table relating to the value of N according to one aspect of this embodiment. The value of N is obtained from the values ​​of X0 and X1 in the Lookup table using 2*X1+X0. When the bandwidth is 80MHz or less, PS160, B0, X0, and X1 are set to 0. When the bandwidth is 160MHz X0 indicates that RU allocation is applied to the lower 80MHz frequency subblock. If the bandwidth is 320MHz, X1 is set to 0 to indicate that the RU allocation is applied to the lower 160MHz segment, and may be set to 1 if it is applied to the upper 80MHz frequency subblock. If so, it may be set to 1. Within the indicated 160MHz segment, if X0 is to indicate that RU allocation is applied to the lower 80MHz frequency subblock, it is set to 0. If applied to the upper 80MHz frequency subblock, it may be set to 1. The Configuration may also indicate the frequency sequence of the Primary 80MHz channel (P80), Secondary 80MHz channel (S80), and Secondary 160MHz channel (S160).

[0328] The program that operates on STA according to the embodiment of the present invention is the program according to the embodiment of the present invention The program may be a program that controls the CPU (Central Processing Unit), etc. (a program that makes the computer function) in order to realize the functions of the embodiment described above. The information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing. Afterward, the data is stored in various types of ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive). The data is then read, modified, and written by the CPU as needed.

[0329] Furthermore, some of the STA components in the above-described embodiment may be implemented using a computer. i. In that case, the program to implement this control function is recorded on a computer-readable recording medium, and the program recorded on this recording medium is then installed on the computer system. This can also be achieved by loading and executing the code.

[0330] Furthermore, the term "computer system" used here refers to the computer system built into STA. This includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording media" refers to flexible disks, magneto-optical disks, ROMs, CD-ROMs, etc. This refers to portable media, such as hard disks and other storage devices built into computer systems.

[0331] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory within a computer system that acts as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0332] A non-AP STA may consist of at least one processor and at least one memory containing computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the terminal device 1 to perform the operations and processing described in the above embodiment using the processor. An AP or STA consists of at least one processor and computer program instructions It may consist of at least one memory containing instructions (computer program). The memory and the computer program instructions (computer program) are used by a processor to cause the AP or STA to perform the operations and processing described in the above embodiment. An eel-based composition would also be acceptable.

[0333] Furthermore, the AP in the above-described embodiment can also be implemented as an assembly (device group) composed of multiple devices. Each device constituting the device group may have some or all of the functions or functional blocks of the AP related to the above-described embodiment. The device group only needs to have a complete set of functions or functional blocks of the AP. In addition, the STA related to the above-described embodiment can also communicate with the AP as an assembly.

[0334] Furthermore, the AP in the above-described embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGen RAN, NR RAN). Furthermore, the AP in the above-described embodiment is a higher-level node for eNodeB and / or gNB. It may have some or all of the ability.

[0335] Furthermore, some or all of the STA in the above-described embodiment may be implemented as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the STA is The components may be individually chipped, or some or all of them may be integrated into a single chip. Furthermore, the integrated circuit implementation method is not limited to LSIs; it may also be implemented using dedicated circuits or general-purpose processors. If advances in semiconductor technology lead to the emergence of integrated circuit technologies that can replace LSIs, It is also possible to use integrated circuits.

[0336] Furthermore, although the above-described embodiment mentions a terminal device as an example of a communication device, the present invention is not limited to this and can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0337] The embodiments of this invention have been described in detail above with reference to the drawings, but the specific configuration is as follows: The present invention is not limited to the embodiments described herein, and includes design modifications and the like that do not depart from the spirit of the invention. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of symbols]

[0338] 101 BSS 102 AP 103 non-AP STA SU1, AU1 Antenna Section SU2, AU2 RF section SU3, AU3 Physical Layer Processing Unit SU4, AU4 MAC layer processing unit SU5 Upper Layer Packet Processing Unit AU5 DSAF SU6, AU6 Wireless Transceiver Unit SU7, AU7 Frame Processing Unit

Claims

1. A receiving unit that receives the trigger frame, Transmitter unit that transmits the PPDU corresponding to the trigger frame. And, equipped with, The aforementioned transmitting unit If the trigger frame is a UHR variant, the bandwidth is determined from the values ​​set in the UL BW subfield and UL Bandwidth Extension subfield included in the trigger frame. 、 From the Bandwidth, the Configuration which shows the frequency sequence of P80, S80, and S160 obtained from the Operation element included in the Beacon frame, the PS160 subfield, and the value set in the bit corresponding to B0 of the RU Allocation subfield, the RU used to transmit the PPDU is determined. Determine the value of N that indicates the 80MHz frequency subblock where it will be placed. Based on the value of N and the DRU / RRU Indication subfield indicating the RU type for each of the one or more 80MHz frequency subblocks corresponding to the Bandwidth, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined. If the RU type indicates RRU, the value of N is used to determine the PHY RU index. 、 If the RU type indicates DRU, the value of N is determined by the DBW frequency subblock index. Used to determine Terminal device.

2. The aforementioned transmitting unit If the value of N is 0, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the first bit in the bitmap set in the DRU / RRU Indication subfield. If the value of N is 1, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the second bit of the bitmap set in the DRU / RRU Indication subfield. If the value of N is 2, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the third bit of the bitmap set in the DRU / RRU Indication subfield. If the value of N is 3, the RU type of the 80MHz frequency subblock corresponding to the value of N is determined from the value of the fourth bit in the bitmap set in the DRU / RRU Indication subfield. The terminal device according to claim 1.

3. The aforementioned transmitting unit If the RU type is DRU, the table in the RU Allocation subfield is SS Allocation Determined according to the DBW indicated by the DRU distribution BW subfield included in the subfield. The terminal device according to claim 2.

4. The aforementioned transmitting unit The RU size and RU index to be allocated to the DBW are determined from the values ​​set in the bits corresponding to B5-B1 of the RU Allocation subfield. From the values ​​set in bits B7-B6 of the RU Allocation subfield, the RU Determine the value of M which indicates the DBW location for distributing the RUs within the 80MHz frequency subblock where they are located. The terminal device according to claim 3.

5. The aforementioned transmitting unit The RU size, RU index, and the value of M indicating the location of the DBW are determined from the values ​​set in the bits corresponding to B7-B1 of the RU Allocation subfield. ru The terminal device according to claim 3.

6. The aforementioned transmitting unit The DBW frequency subblock index is determined from the DBW, the value of N, and the value of M. Determine the constant shift value corresponding to the DBW frequency subblock index and the RU From the index, determine the subcarrier index where the RU will be placed. The terminal device according to claim 4.

7. Steps include receiving a trigger frame and Steps to transmit the PPDU corresponding to the Trigger frame. and, If the trigger frame is a UHR variant, the bandwidth is determined from the values ​​set in the UL BW subfield and UL Bandwidth Extension subfield included in the trigger frame. The steps, From the Bandwidth, the Configuration which shows the frequency sequence of P80, S80, and S160 obtained from the Operation element included in the Beacon frame, the PS160 subfield, and the value set in the bit corresponding to B0 of the RU Allocation subfield, the RU used to transmit the PPDU is determined. The steps include determining the value of N that indicates the 80MHz frequency subblock in which the subblock is located, Based on the value of N and the DRU / RRU Indication subfield indicating the RU type for each of the one or more 80MHz frequency subblocks corresponding to the Bandwidth, the value of N The steps include determining the RU type of the corresponding 80MHz frequency subblock, If the RU type indicates RRU, the value of N is used to determine the PHY RU index. The steps, If the RU type indicates DRU, the value of N is determined by the DBW frequency subblock index. Steps used to determine, Communication method.

Images