Terminal, base-station device, and communication method

Abstract

To provide a terminal, a base-station device, and a communication method for achieving efficient communication.SOLUTION: The terminal STA includes a reception unit that receives the Operationelement and a transmission unit that determines a resource configuration of the TBPPDU requested to be transmitted on the basis of the Operationelement. In a case where a Bitmapsubfield indicating whether or not the dRUEAllocation is applied to each of one or a plurality of 20MHzsubchannel within the BSSbandwidth is included in the terminal, the transmitter determines a resource configuration for performing the dRUEAllocation using a 20MHzsubchannel corresponding to a bit set to 1 in the Bitmapsubfield.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a base station device, and a communication method. [Background technology]

[0002] The Institute of Electrical and Electronics Engineers Inc. (IEEE) is currently studying ways to increase the speed and efficiency of frequency usage in wireless LAN (Local Area Network) communications. Currently, standardization of IEEE802.11bn, the successor to IEEE802.11be, has begun. Summary of the Invention [Problem to be solved by the invention]

[0003] A terminal device, a base station device, and a communication method that enable efficient communication are provided. [Means for solving the problem]

[0004] (1) A first aspect is a terminal device, comprising: a receiving unit for receiving an Operation element; and a transmitter that determines a resource configuration of a TB PPDU requested to be transmitted based on the Operation element, and when the Operation element includes a Bitmap subfield that indicates whether dRU Allocation is applied to each of one or more 20 MHz subchannels in the BSS bandwidth, the transmitter ... The resource configuration for performing dRU allocation is determined using the corresponding 20 MHz subchannel.

[0005] (2) A second aspect is a base station device, comprising: a transmitter that transmits an Operation element; wherein the transmitter includes, in the Operation element, a Bitmap subfield indicating whether dRU Allocation is applied to each of one or more 20 MHz subchannels within a BSS bandwidth.

[0006] (3) A third aspect is a communication method, comprising: receiving an Operation element; determining a resource configuration for a TB PPDU requested to be transmitted based on the Operation element; and wherein the Operation element includes a Bitmap subfield indicating whether dRU Allocation is applied to each of one or more 20 MHz subchannels in the BSS bandwidth. If so, determining a resource configuration for performing dRU Allocation using the 20 MHz subchannel corresponding to the bit set to 1 in the Bitmap subfield. [Effects of the Invention]

[0007] Efficient communication can be achieved. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a wireless LAN system according to an aspect of the present embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the device configuration of an STA according to one aspect of this embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of a device configuration of an AP according to an aspect of the present embodiment. [Figure 4] FIG. 10 is a schematic diagram of PDUs supported by each tier according to one aspect of the present embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a configuration in which a MAC frame according to an aspect of the present embodiment is a Trigger frame. [Figure 6]FIG. 10 is a diagram illustrating an example of a User Info field according to an aspect of the present embodiment. [Figure 7] A figure showing an example of RU allocation by the RU Allocation subfield according to one aspect of this embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of the maximum number of RUs that can be allocated to the bandwidth (CBW) of each channel according to one aspect of this embodiment. [Figure 9] A figure showing an example of the configuration of an RU related to one aspect of this embodiment. [Figure 10] A figure showing an example of a procedure related to the transmission of a PPDU using a dRU of a STA in one embodiment of this embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a Special User Info field according to an aspect of the present embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of BW and BW type indicated by a UL BW subfield and a UL Bandwidth Extension subfield according to one aspect of the present embodiment. [Figure 13] FIG. 10 is a diagram showing an example of various fields / subfields included in an Operation element format according to one aspect of the present embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a Bandwidth Indication element according to one aspect of the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described.

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

[0011] The wireless LAN (Local Area Network) system in this embodiment is a system that uses one or more stations. The wireless LAN system may be configured by two or more STAs. When configured as follows, the wireless LAN system may be called a BSS (Basic Service Set). .

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

[0013] The STA may be a communication device via a wireless medium (WM). The STA may also include an AP (Access Point) having the functionality of a base station and / or a non-AP STA having the functionality of a terminal. That is, the STA may be an AP. The STA may also be a non-AP STA. The STA may also refer to both an AP and a non-AP STA.

[0014] A STA may be a single addressable logical entity that interfaces with a MAC (Medium Access Control) and PHY (Physical layer) to a WM (Wireless Medium). Here, the STA may be referred to as a base station device or a terminal device.

[0015] The STAs that make up a BSS may be called members (BSS member STAs). A BSS may consist of two STAs. Even if a member STA is part of a BSS, it is not necessarily possible for the member STA to communicate wirelessly with all other member STAs within the BSS. In other words, depending on the communication conditions and environment, Depending on the BSS, there may be member STAs that cannot perform wireless communication. For example, STA1 and ST2, or STA1 and STA3 may configure a BSS using the same BSSID. In this case, STA2 and STA3 may configure the same BSS, but wireless communication may not be possible between STA2 and STA3. The communication area (coverage) may be called a BSA (Basic Service Area). The BSS may be formed by an association between at least two STAs.

[0016] An AP may be an entity that contains one STA. The STA(s) that have established this service are given access to the distribution system service(s) (DSS) via the WM. The AP may also constitute a STA and a Distributed System Access Function (DSAF). It may also be referred to as a network device.

[0017] A distribution system (DS) may be a system used to interconnect multiple sets of BSSs and integrated LANs to form an Extended SS (ESS).

[0018] 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 communication areas (coverage) configured by multiple BSSs that partially overlap. An ESS may have multiple BSSs that are far apart, and may arrange the coverage areas covered by multiple BSSs as a wider coverage area. In other words, the communication area of ​​an ESS may be the same as or larger than the communication area of ​​a single BSS. The communication area formed by an ESS may be called an ESA (Extended Service Area). stomach.

[0019] An ESS may be a set of one or more interconnected BSSs that are represented as a single BSS to the LLC (Logical Link Control) layer in any STA associated with one or more BSSs. The STA that is connected may be referred to as an associated STA.

[0020] A non-AP STA may be a STA that does not include the functionality of an AP. A non-AP STA is called a terminal device. This may be done.

[0021] WM is a protocol data unit (PDU) transport protocol between PHY entities in a wireless LAN. It may also be the medium used to carry out the transmission.

[0022] The channel may be a WM used to transmit PPDUs (PHY PDUs) between two or more STAs.

[0023] The channels may include a primary channel and a secondary channel. When operating with a 20 MHz bandwidth, the channel may be the primary channel. For example, when operating with a 40 MHz bandwidth in a BSS, a primary channel and a secondary channel may be used. Bandwidth may be defined as the bandwidth of the channel.

[0024] The primary channel is used in common for operation by all member STAs of the BSS. For example, in a BSS using a bandwidth of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 80+80 MHz, or 320 MHz, the primary channel may be a primary 20 MHz channel.

[0025] The secondary channel may be a channel associated with the primary channel that is used to achieve a wider bandwidth than the primary channel. For example, in a BSS using a bandwidth of 40 MHz, 80 MHz, 160 MHz, 80+80 MHz, or 320 MHz, the secondary channel may be a secondary 20 MHz channel. In such cases, the secondary channel may be a secondary 40 MHz channel. In such a case, the secondary channel may be configured as a secondary 80 MHz A primary channel may be configured with a secondary 160 MHz channel. In such a case, the secondary channel may be configured with a secondary 160 MHz channel. Each bandwidth may be configured with a combination of a primary channel and a secondary channel. For example, in the case of a 320 MHz bandwidth, 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.

[0026] For example, in the case of a wide bandwidth such as 80 MHz, it may be configured with a primary 40 MHz channel and a secondary 40 MHz channel. The primary 40MHz channel may consist of a primary 20MHz channel and a secondary 20MHz channel.

[0027] FIG. 1 is a diagram showing an example of a wireless LAN system according to an aspect of the present embodiment. In BSS 101-2, non-AP STA 103-3 and non-AP STA 103-4 may communicate directly with each other.

[0028] If all STAs in BSS 101-1 and BSS 101-2 support the function of receiving a trigger frame and the function of transmitting a TB (Trigger based) PPDU in response to the trigger frame, in BSS 101-1, AP 102-1 may use the trigger frame to request each of non-AP STAs 103-1, 103-2, and 103-3 to transmit a TB PPDU. Also, in BSS 101-2, AP 102-2 may use the trigger frame to request each of non-AP STAs 103-3 and 103-4 to transmit a TB PPDU. In other words, the trigger frame is The Trigger frame may also be used to transmit other information necessary for the responding STA to transmit a TB PPDU. When a trigger frame is received from the PPDUs may be transmitted.

[0029] In BSS101-1 and BSS101-2, if some STAs support the function of receiving the Trigger frame and the function of transmitting the TB PPDU for the Trigger frame, AP101-1 and / Or AP101-2 transmits a trigger frame to a STA that supports the function of receiving a trigger frame and the function of transmitting a TB PPDU for the trigger frame, and transmits a TB PPDU. The ability to receive Trigger frames and the TB PPDU for Trigger frames For STAs that do not support the function of transmitting Alternatively, a control frame different from the trigger frame may be used to request transmission of a TB PPDU.

[0030] The trigger frame may also be used by the AP to realize UL multi-user (MU) transmission, and may also be used for OFDMA transmission.

[0031] The Trigger frame may also be used to indicate various parameters required for transmitting the TB PPDU, such as the duration, RU (Resource Unit) allocation, target RSSI, and MCS of the TB PPDU.

[0032] Here, the TB PPDU may be a PPDU.

[0033] The non-AP STA 103-3 may form a BSS with both the AP 102-1 and the AP 102-2. The configuration may be referred to as an overlapping BSS (OBSS). An ESS may be constructed using BSS 101-1 and BSS 101-2.

[0034] The STA is used for transmission and reception to meet a given communication speed or data rate. Frequency bands and bandwidth, communication methods, access methods, MCS methods, MIMO (Multiple Input Multiple Functions such as the (output) method and beamforming may be supported / implemented. If enabled, the STA may perform processing related to each function.

[0035] For example, the STA may support / implement the function of HT (High Throughput) STA to achieve a maximum communication speed of 600 Mbps. The HT STA function may be the 2.4 GHz / 5 GHz frequency band or 20 or Supports 40MHz bandwidth, OFDM / 64QAM, MIMO, Channel bonding, and Frame aggregation Channel bonding is a method of communication using one or more channels. Frame aggregation is a process of using one or more frames as one frame. Communication may also be carried out.

[0036] For example, the STA may support / implement the functions of a VHT (Very HT) STA in order to achieve a maximum communication speed of 6.93 Gbps. In addition to the features, a maximum bandwidth of 160 MHz, 256QAM, 8x8 MIMO, MU-MIMO, and LDPC (Low Density Parity Coding) may be supported.

[0037] For example, the STA may support / implement the functions of a High Efficiency (HE) STA to achieve a maximum communication speed of 9.6 Gbps. The functions of an HE STA are the same as those supported by HT STA and VHT STA. In addition to the various functions supported, the 6 GHz frequency band, OFDMA, 1026QAM, TWT (Target Wake Time), Spatial Reuse, and RU (Resource Unit) may be supported.

[0038] For example, the STA must have the EHT (Extremely HT) STA function to achieve a maximum communication speed of 46 Gbps. may be supported / implemented. In addition to the various functions supported by HT STA, VHT STA, and HE STA, EHT functions may also support a maximum bandwidth of 320 MHz, 4096QAM, 16x16 MIMO, Multi-RU, and Multi-Link.

[0039] For example, a STA may not support / implement UHR (Ultra High Reliability) STA functionality. UHR STAs can support various functions supported by HT STAs, VHT STAs, HE STAs, and EHT STAs. In addition, functions related to Multi-AP Operation and dRU (distributed RU) may be supported.

[0040] When multiple STAs configure a Service Set (SS) and / or a BSS or ESS, they may inform each other of the functions they support when associating. SS, BSS, and ESS may be configured to satisfy the communication speeds appropriate for each.

[0041] 2 is a diagram showing an example of the device configuration of an STA according to one aspect of this embodiment. 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 is a unit that includes 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 receives a wireless signal via the antenna unit SU1. The STAs may include APs and / or non-AP STAs.

[0042] 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 function (PHY function) on the converted baseband signal. The signal that has undergone physical layer processing 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 function (MAC function) on the baseband signal. The signal that has undergone MAC layer processing 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 function on the upper layer packets extracted from the received signal.

[0043] The upper layer packet processing unit SU5 performs the processing related to the upper layer functions when transmitting the upper layer packet. The upper layer packet processing unit SU5 sends the upper layer packet to the MAC layer processing unit SU4. The MAC layer processing unit SU4 processes the upper layer packet in relation to the MAC layer functions. The frame that has undergone the MAC layer processing in the MAC layer processing unit SU4 (the upper layer packet that has been processed) is The frame generated by the MAC layer processing is sent to the physical layer processing unit SU3. The physical layer processing unit SU3 processes the frame that has been processed in the MAC layer, and performs processing related to the physical layer functions. The frame sent from U3 to RF unit SU2 is converted into an RF signal and transmitted as a wireless signal via antenna unit SU1.

[0044] 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. The PLME and MLME provide their own layer management service interfaces. The PLME and MLME may be controlled by a Station Management Entity (SME), which is an entity independent of the layers. The PLME, MLME, and SME may be included in the frame processing unit SU7.

[0045] 3 is a diagram showing an example of the device configuration of an AP according to one aspect of this embodiment. The AP may have 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 have a higher layer packet processing function. The AP also has a function for wireless transmission and reception. The wireless transceiver unit AU6 may be configured to include an antenna unit AU1 and an RF unit AU2. The frame processing unit AU7 may be configured to include a physical layer processing unit AU3 and a MAC layer processing unit AU4.

[0046] 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 performs processing related to the physical layer function on the converted baseband signal. The signal that has undergone physical layer processing in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer functions on the baseband signal. The signal that has undergone MAC layer processing in the MAC layer processing unit AU4 is sent to the DSAF unit AU5 as an upper layer packet. The DSAF unit AU5 performs the following on the upper layer packet extracted from the received signal: The DSAF unit AU5 performs processing related to the functions of the upper layer. In addition, the DSAF unit AU5 provides the upper layer packets to the DS. Good too.

[0047] The DSAF unit AU5 may acquire the upper layer packet from the DS. The DSAF unit AU5 performs processing related to the function of the upper layer when transmitting the upper layer packet. The packet is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 processes the upper layer packet for MAC layer functions. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (the 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 physical layer functions on frames that have been processed in the MAC layer. The frames sent from the physical layer processing unit AU3 to the RF unit AU2 are converted into RF signals and transmitted as wireless signals via the antenna unit AU1.

[0048] The processing of the physical layer processing unit AU3 may be controlled by the PLME. The processing of the MAC processing unit AU4 may be controlled by the MLME. The PLME and the MLME are entities independent of each other in terms of layers. The PLME, MLME and SME may be controlled by the frame processing unit AU7. It may be included.

[0049] FIG. 4 is a schematic diagram of PDUs supported in each layer according to one aspect of this embodiment.

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

[0051] An MSDU (MAC Service Data Unit) is a single data packet sent between multiple MAC SAPs (Service Access Points). It may be information transmitted as a unit of

[0052] MPDUs are exchanged between MAC entities using one or more services of the physical layer (PHY). An MPDU may be a unit of data that is transmitted by aggregating one or more MSDUs. One MPDU may be configured.

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

[0054] A PSDU (PHY Service Data Unit) is data encapsulated in the physical layer and consists of one or more MPDUs (i.e., MAC frames), which are data from the MAC layer. In other words, the PSDU may be configured to include an A-MPDU (Aggregate MPDU). The PSDU is configured as a PPDU by adding a PHY preamble and a PHY header, and is used for communication between STAs. It may also be used to communicate at the physical layer.

[0055] A PPDU may be a unit of data exchanged between physical layer (PHY) entities using one or more services of the PHY.

[0056] 5 is a diagram illustrating an example of a configuration when a MAC frame according to one aspect of the present embodiment is a Trigger frame. The MAC frame may include a Frame Control field, a Duration field, an RA field, a TA field, a Common Info field, a User Info List field, Padding, and an FCS.

[0057] The MAC header consists of the Frame Control field, Duration field, RA field, and TA field. This may also be done.

[0058] In Fig. 5, the Frame Control field is a field used to indicate the format and use of the MAC frame. In Fig. 5, the Frame Control field may be used to indicate that the MAC frame is a Trigger frame. In Fig. 5, each field when the MAC frame is a Trigger frame will be described.

[0059] The Duration field indicates the estimated time required to transmit the requested TB PPDU and the required In other words, the Duration field may be used to indicate the time required to transmit the TB PPDU and the time required to transmit the Ack for the TB PPDU.

[0060] The RA field is used by non-AP STAs depending on the Trigger Type of the Trigger frame that contains the RA field. The MAC address of the group, broadcast address, or solicited group is set. That is, the address (for example, the ID of the STA) of the STA that receives the Trigger frame (the STA that transmits the Trigger frame, that is, the AP) may be set in the RA field.

[0061] If the Trigger frame is addressed to a STA belonging to one BSS, the TA field The TA field may be set to the address (e.g., STA ID) of the STA transmitting the Trigger frame. If the Trigger frame is addressed to one or more STAs from at least two different BSSs in a multiple BSSID set, the TA field may be the transmitted BSS ID.

[0062] The AP may decide whether to request a TB PPDU from any STA. The STA with the address matching the value of the field may transmit a TB PPDU to the STA (that is, the AP) that transmitted the Trigger frame, based on the information contained in the received MAC frame.

[0063] The Common Info field is common to one or more STAs that are requested to transmit a TB PPDU. There may be one or more fields in which various information to be used is indicated. 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. The Common Info field may also include an AP Tx Power subfield. The Common Info field may also include a Trigger Dependent Common Info subfield.

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

[0065] The UL Length subfield indicates the value of the L-SIG LENGTH field of the requested TB PPDU. It may also be used for

[0066] The UL BW subfield may be used to indicate the bandwidth of the SIG field of the TB PPDU. That is, the UL BW subfield may be used to determine the bandwidth of the TB PPDU used to respond to the Trigger frame.

[0067] The Trigger Dependent Common Info subfield is populated with subfields corresponding to optional features supported by one or more STAs sharing the same information based on the value of the Trigger Type field. It may be provided in a format that is easy to understand.

[0068] The User Info List field may contain zero or more User Info fields. That is, one or more User Info fields included in the User Info List field may be assigned to associated STAs that can receive the Trigger frame.

[0069] The Padding field may be used to adjust the size of the entire MAC frame.

[0070] The FCS (Frame Check Sequence) field includes a 32-bit CRC (Cyclic Redundancy Check) and may be used to verify whether a received frame is valid. STAs also add the FCS field to indicate that a frame they transmit is valid.

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

[0072] The AID12 subfield may be set to the 12 LSB of the STA's AID. For example, the AID12 subfield If the trigger frame contains the address of the non-AP STA associated with the AP, It may be the 12 LSBs of the AID of a non-AP STA.

[0073] The value set in the AID12 subfield is the value of the associated User Info field. Depending on the value set in the AID12 subfield, the AID12 subfield may indicate that the User Info field is addressed to the associated STA of the AID with the same value as the AID12 subfield. Depending on the value set in the AID12 subfield, the AID12 subfield may indicate that the User Info field is assigned to one or more RA-RUs for one or more unassociated STAs. In response, the AID12 subfield indicates that the RU is not assigned to a specific STA. Also, depending on the value set in the AID12 subfield, the AID12 subfield may indicate the start of a Padding field.

[0074] The RU Allocation subfield, together with the UL BW subfield of the Common Information field, determines the size of the RU. The RU size may be used to identify the size and frequency domain allocation. The RU allocation may be the frequency domain or channel location where the RU corresponding to the UL BW is allocated. The value that cannot be set in the RU Allocation subfield due to the size of the bandwidth indicated by the UL BW subfield. In other words, the value that can be set in the RU Allocation subfield may be related to the value of the UL BW subfield. The AP may decide the bandwidth to set in the UL BW subfield and the transmission speed of the TB PPDU. The number of RU tones and RU index indicated in the RU Allocation subfield may be determined according to the number of non-AP STAs making a transmission request.

[0075] 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 that constitute the RU.

[0076] The UL FEC Coding Type subfield may indicate the code type of the requested TB PPDU, for example, BCC (Binary Convolutional Code) or LDPC (Low Density Parity Check).

[0077] The UL MCS subfield specifies the MCS (Modulation and Coding Scheme) of the requested TB PPDU. may be used to indicate

[0078] The UL DCM subfield may be used to indicate the Dual Carrier Modulation (DCM) of the requested TB PPDU, where DCM is set for each of multiple channels or RUs. This is a procedure for mapping and transmitting the same data.

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

[0080] The SS Allocation subfield specifies the allocation of one or more spatial streams of the requested TB PPDU. may be used to indicate

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

[0082] The UL Target Receive Power subfield specifies the target receive power for the TB PPDU transmitted by the assigned RU. It may be used to indicate the expected received signal power, averaged over one or more antennas and measured at the AP's antenna connector.

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

[0084] 7 is a diagram showing an example of RU allocation by the RU Allocation subfield according to one aspect of this embodiment. The values ​​indicated in the RU Allocation subfield correspond to the RU size and the RU index, respectively. In addition, the range of values ​​that can be set in the RU Allocation subfield may differ depending on the bandwidth indicated in the UL BW subfield. For example, even with the same RU size, there may be RU indexes that can be set at 20 MHz and 40 MHz, and RU indexes that can be set at 40 MHz.

[0085] FIG. 8 shows RUs that can be allocated to each channel bandwidth (CBW) according to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of the maximum number of

[0086] The maximum number of RUs that can be allocated to each channel may vary depending on the bandwidth and RU size. For example, if the bandwidth is 20 MHz and the RU size is 26 tones, 9 RUs can be allocated to a 20 MHz channel. In such a case, the AP may allocate 9RUs to one or more non-AP STAs.

[0087] As shown in Figures 7 and 8, the TB PPDU transmission request is made in the Trigger frame (i.e., the TB PPDU is The transmitting STA may determine the allocation of the frequency domain of the RU to be used to transmit the TB PPDU. For example, if the received UL BW subfield indicates 40 MHz and the received RU Allocation If 7 is indicated in the subfield, the STA uses the frequency corresponding to RU6 for a bandwidth of 40 MHz. The TB PPDU may be transmitted using the RU in the number field, where the TB PPDU may also be referred to as a PPDU.

[0088] 9A and 9B are diagrams illustrating an example of the configuration of an RU according to one aspect of this embodiment. FIG. 9A shows an example of a regular RU (rRU) in which one RU is configured by consecutive tones. FIG. 9B shows an example of a regular RU (rRU) in which one RU is configured by consecutive tones. ) shows an example of a distributed RU (dRU) in which multiple tones that make up one RU are arranged at equal intervals and / or in a distributed manner relative to the maximum bandwidth of the channel or a specified bandwidth. Here, rRU may be referred to as an RU of the first RU Allocation type, and dRU may be referred to as an RU of the second RU Allocation type. The first allocation type RU and the second allocation type RU may be configured with 26-, 52-, 116-, 242-, 448-, or 996-tones, respectively. These tones may be referred to as data subcarriers. An RU may be configured and / or mapped with a predetermined number of data subcarriers and a predetermined number of pilot subcarriers. Here, the data subcarriers may be used for data transmission. The pilot subcarriers may be phase ( Subcarriers not used as data subcarriers or pilot subcarriers may include DC subcarriers, null subcarriers, and guard band subcarriers. Null subcarriers reduce interference between adjacent RUs. The Guard band subcarrier may be used to prevent interference between channels or bands. This may be used to reduce interference.

[0089] Here, the bandwidth (BW) in which rRU Allocation is possible may be referred to as a regular BW. The BW in which dRU Allocation is possible may be referred to as a distribution BW. In other words, the regular BW may be a BW in which rRU Allocation is applied in the UL BW. The distribution BW may be a BW in which dRU Allocation is applied. A subchannel in the regular BW may be a regular subchannel ( A subchannel within a distribution BW may be referred to as a distribution subchannel (i.e., a subchannel to which dRU Allocation is applied). The interval between adjacent tones constituting a dRU allocated in a distribution BW may be determined according to the distribution BW and the tone size of the dRU. For example, if a 26-tone dRU is allocated in a 20 MHz distribution BW, the interval between adjacent tones of the dRU may be determined as follows: For example, a 26-tone dRU in a 40 MHz distribution BW may be used. is arranged, the interval between adjacent tones of the dRU may be 18-tone intervals.

[0090] The RUs indicated by the RU Allocation subfield may be allocated to non-AP STAs indicated by the AID12 subfield of the same User Info field. Also, the RUs indicated by the RU Allocation subfield may be configured so that the same or different RUs are allocated to the non-AP STAs corresponding to the User Info field.

[0091] FIG. 10 is a diagram showing an example of a procedure related to the transmission of a PPDU using a dRU by a 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 uses a dRU in the Trigger frame for the STA in S1001. The STA checks whether the Trigger frame 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 are to be used for a PPDU using a dRU (S1003). In S1003, if the UL BW subfield and the RU Allocation subfield are to be used for a PPDU transmission using a dRU, The STA then transmits a PPDU using the dRU to the AP (S1004).

[0092] When an AP that supports and / or enables dRU-related functionality uses one Trigger frame to request one or more STAs that support and / or enable dRU-related functionality to transmit a PPDU using a dRU, the AP may include a subfield related to the request to transmit a PPDU using a dRU in the Common Info field of the Trigger frame.

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

[0094] For example, a subfield related to a request to transmit a PPDU using a dRU may be included in the Trigger Dependent Common Info subfield. Whether or not a PPDU using a dRU is to be transmitted may be indicated in a Trigger frame corresponding to each Trigger Type. A subfield related to a request to transmit a PPDU using a dRU may not be included in a Trigger frame corresponding to some Trigger Types. Good too.

[0095] If the subfield related to the PPDU transmission request using dRU is included in the Trigger Dependent Common Info subfield, the RU Allocation subfield included in the User Info field is included in the dRU Also, if a subfield related to a PPDU transmission request using dRU is included in the Trigger Dependent Common Info subfield, the tones corresponding to the RU size and RU index indicated by the RU Allocation subfield for the entire bandwidth indicated by the UL BW subfield included in the Common Info field may be used for resource allocation of dRU. The time slots may be allocated at equal intervals.

[0096] For example, the subfield related to the transmission request of the PPDU using the dRU may be the UL Bandwidth Extension subfield. , it may indicate 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, a non-AP STA that supports and / or enables dRU-related functions may The UL Bandwidth Extension subfield of the Special User Info subfield and the UL BW subfield of the Common Info field are used to determine the requested TB PPDU. The bandwidth and bandwidth type (or RU Allocation type) of the RU may be determined.

[0097] When an AP that supports and / or enables a function related to a dRU uses one Trigger frame to request one or more STAs that support and / or enable the function related to a dRU to transmit a PPDU using the dRU, the AP may include a subfield related to the request to transmit a PPDU using the dRU in the User Info field of the Trigger frame. It may also indicate whether to request transmission of a PPDU using a dRU.

[0098] An AP that supports and / or enables a function related to a dRU may indicate to one or more STAs that support and / or enable the function related to a dRU whether the RU Allocation subfield included in the User Info field corresponds to a dRU by using one or more specific bits that configure the RU Allocation subfield. For example, One or more STAs that support and / or enable the feature shall, if a particular bit or bits comprising the received RU Allocation subfield indicate a predetermined value, Alternatively, the STA may determine that the received RU Allocation subfield is used to indicate the resource allocation of the dRU. Otherwise, the STA may determine that the received RU Allocation subfield is used to indicate the resource allocation of the rRU. Also, one or more STAs that support and / or enable the dRU-related functionality may determine that the received RU Allocation subfield is used to indicate the resource allocation of the 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 used for resource allocation of the dRU.

[0099] An AP that supports and / or enables dRU-related functionality shall assign a specific ID to the AID12 subfield in the User Info field when requesting transmission of a PPDU using a dRU to one or more STAs that also support and / or enable dRU-related functionality. A specific ID may be indicated using a Reserved ID. A specific ID may be indicated using a reserved ID. It may be defined by replacing a predetermined ID among the IDs assigned.

[0100] When an AP that supports and / or enables the dRU-related functionality requests one or more STAs that also support and / or enable the dRU-related functionality to transmit a PPDU using the dRU, the AP shall specify in the Trigger Dependent User Info subfield that the PPDU should be transmitted using the dRU. It may contain and set subfields relevant to the request.

[0101] Here, the subfield related to the PPDU transmission request using dRU is either using dRU or using rRU. This may be a subfield used to indicate whether the PPDU is being transmitted using the dRU. The associated subfield may be a subfield used to indicate a channel and / or a bandwidth and / or a frequency offset for which resource allocation is available in the dRU. The subfields related to the transmission request of the PPDU using the UL BW subfield are used for the dRU. For a subfield related to a PPDU transmission request using a dRU, the RU Allocation subfield may be a subfield used to indicate the RU Allocation of a dRU or the RU Allocation of an rRU. The subfield related to the transmission request of the PPDU may be associated with information indicating whether the PPDU using the dRU can be transmitted to the puncturing channel. If a STA that supports and / or enables the dRU-related function indicates that it can transmit a PPDU using the dRU to the puncturing channel, the STA may request a PPDU for the RU Allocation to the puncturing channel. The puncturing channel may determine the resource allocation of the dRU based on the corresponding bandwidth and RU size. Here, the puncturing channel may be used by STAs that do not support and / or enable the dRU-related functions. The puncturing channel may be used to indicate a channel on which PPDUs are not transmitted or received. The puncturing channel may indicate information related to the bandwidth and frequency offset of the puncturing channel.

[0102] In a BSS and / or ESS, the functionality related to the dRU must be supported and / or enabled. If the APs and non-AP STAs that support the dRU-related functions are included, The AP supporting and / or enabling the dRU uses a Trigger frame to request non-AP STAs that support and / or enable the dRU-related functionality to transmit PPDUs using the dRU. In addition, to request the transmission of a PPDU using a dRU, the AP may request the non-AP STA to In contrast, the subfield required to request the transmission of a PPDU using a dRU is set as Trigger Dependent U. May be set using the User Info subfield.

[0103] Here, the AP supports and / or has the functionality related to dRUs within the same BSS and / or ESS. If the Trigger Dependent User Info subfield includes at least one STA that does not support or enable the dRU-related functionality, the Trigger Dependent User Info subfield may not be used to set the subfield for requesting STAs that do not support and / or enable the dRU-related functionality to transmit a PPDU using the dRU.

[0104] The AP must also support and / or include functionality related to dRUs within the same BSS and / or ESS. If the AP includes at least one STA that supports and / or enables the dRU, it may use the Trigger Dependent User Info subfield to set a subfield to request the transmission of a PPDU using the dRU. In this case, the AP may not set the subfield to request the transmission of a PPDU using a dRU in the Trigger Dependent User Info subfield for a STA that does not support and / or enable the dRU-related functionality in one Trigger frame. STAs that do not support and / or enable the functionality related to the User Info field and dRU The AP may request each STA to transmit a PPDU of the corresponding RU allocation type.

[0105] The AP must also support and / or include functionality related to dRUs within the same BSS and / or ESS. If the UE contains at least one STA that has not enabled dRU and has set the UL BW subfield to 20 MHz or narrower, it requests the transmission of PPDUs using dRU. The subfields required for this purpose do not need to be set using the Trigger Dependent User Info subfield.

[0106] STAs that do not support and / or enable the dRU-related features will not be able to use the Trigger frame. If a subfield related to a PPDU transmission request using the dRU included in That's fine.

[0107] A non-AP STA that supports and / or enables dRU-related functionality may determine whether the dRU distributes multiple tones across the entire maximum bandwidth of the channel or across a portion of the bandwidth, depending on the value of the subfield included in the Trigger frame.

[0108] A non-AP STA that supports and / or enables the dRU-related features may further: The AP may indicate to the AP as capability information whether it supports and / or enables a function related to whether distributed allocation is performed over the entire maximum bandwidth of the channel or over a portion of the bandwidth. If the AP supports and / or enables the function, the AP may request transmission of a PPDU by including in the Trigger frame a subfield indicating whether distributed allocation of multiple tones by the dRU is performed over the entire maximum bandwidth of the channel or over a portion of the bandwidth.

[0109] FIG. 11 is a diagram illustrating an example of a Special User Info field according to one aspect of the present embodiment. The Special User Info field may be used to transmit extended common information that is not provided in the Common Info field. The Special User Info field may not 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, the specific value does not have to be set in the AID12 subfield. The Special User Info field may exist as a field to indicate optional features in a Trigger frame generated by an AP. In other words, the AP may optionally add the Special User Info field to the Trigger frame. In other words, the Special User Info field may be used to indicate optional features in a Trigger frame generated by an AP. Whether or not the o field is included in the Trigger frame may be determined based on whether or not the Trigger frame includes a User Info field. If the Special User Info field is present, If necessary, it may be placed immediately after the Common Info field of the Trigger frame. In addition, the Special User Info field is used to transmit information for the U-SIG field of the requested TB PPDU. It may also be used for

[0110] The length (time length or bit length) of the Special User Info field may be the same as the length of other User Info fields included in the same Trigger frame (excluding the case where the Trigger frame is an MU-BAR Trigger frame).

[0111] The Special User Info field may not be included in the Trigger frame unless the Trigger frame includes one or more variant User Info fields. In other words, if the AP transmits a Trigger frame that does not include a User Info field, the Trigger frame does not need to include a Special User Info field.

[0112] The Special User Info field may include a PHY Version Identifier subfield, which is used to indicate the PHY version of the requested TB PPDU. For example, if the TB PPDU requested to be transmitted is an EHT TB PPDU, the PHY Version Identifier subfield may be set to 0. For example, if the TB PPDU requested to be transmitted is a UHR TB PPDU, the PHY Version Identifier subfield may be set to 1. For example, if the TB PPDU requested to be transmitted is a TB PPDU corresponding to a specific function, the PHY Version Identifier subfield may be set to 2. That is, a corresponding value may be set or defined for a TB PPDU corresponding to an added or extended function.

[0113] The PHY Version Identifier subfield is supported / enabled by non-AP STAs and / or APs. The value to be set may be defined depending on the features that the non-AP STA supports. A non-AP STA may set the PHY Version Identifier subfield to a value corresponding to a feature that the non-AP STA does not support. If so, the received Special User Info field may be ignored. A device may ignore a received PPDU if the Version Identifier subfield is set to a value corresponding to a feature it does not support.

[0114] The Special User Info field may include a Spatial Reuse subfield. The Spatial Reuse n subfield carries the value contained in the Spatial Reuse n subfield of the U-SIG field of the TB PPDU. It may also be used to

[0115] The Special User Info field may be used to indicate whether a specific subfield (specific bit) among the various subfields (or bits corresponding to the subfields) included in the U-SIG field of the requested TB PPDU is valid or ignored.

[0116] The U-SIG field is used to transmit information necessary to interpret (decode) the PPDU. The STA that receives the U-SIG field may demodulate and decode the PPDU received with the U-SIG field. The number can be issued.

[0117] The Special User Info field may include a UL Bandwidth Extension subfield (UL BW Ext subfield). The UL BW Ext subfield may be used to indicate that a bandwidth wider than 160 MHz (e.g., 320 MHz) is used in combination with the bandwidth indicated by the UL BW subfield included in the Common Info field. In addition, functions related to the dRU An AP that supports and / or enables the UL BW subfield of the dRU Allocation subfield is allocated to non-AP STAs that also support and / or enable the feature. (or shown as distribution BW) for rRU Allocation For example, for a non-AP STA that supports and / or enables this function, the UL BW and BW type (RU Allocation type) for the requested TB PPDU may be indicated in the combination shown in FIG.

[0118] FIG. 12 is a diagram illustrating an example of BW and BW type indicated by the UL BW subfield and the UL Bandwidth Extension subfield (UL BW Ext subfield) according to one aspect of the present 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. The BW type may also be used 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, the value indicated by the UL BW Ext subfield indicates whether the bandwidth indicated by the UL BW subfield is used as regular BW or distribution BW. Here, if the UL BW Ext subfield is set to 0, the 20 MHz may be used as a regular BW. In this case, a non-AP STA that is requested to transmit a TB PPDU applies rRU Allocation to the RU Allocation used to transmit the TB PPDU, and configures Also, if the UL BW Ext subfield is set to 1, the 20 MHz may be used as the distribution BW. In this case, the non-AP that is requested to transmit the TB PPDU The STA may apply a dRU Allocation to configure the RU Allocation used to transmit the TB PPDU.

[0119] Although FIG. 12 shows a case where the UL BW Ext subfield is configured with 2 bits, it may be configured with a bit size other than 2. For example, the number of bits configuring the UL BW Ext subfield may be changed depending on the value indicated by the PHY Version Identifier subfield. Also, if the UL BW Ext subfield is configured with more than 2 bits, it may be used to indicate that the UL BW is wider than 320 MHz. For example, the PHY Version Identifier subfield may indicate that the dRU supports / enables the relevant features. If the UL BW Ext subfield is set to a value equal to the UL BW Ext subfield, the number of bits that make up the UL BW Ext subfield is To indicate the BW type that applies to It may be a .

[0120] 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 and the UL BW Ext subfield may be modified as shown in FIG.

[0121] The UL BW and BW type may be determined according to the combination of the value set in the UL BW subfield and the value set in the UL BW Ext subfield.

[0122] A non-AP STA may indicate that it supports and / or enables the functionality associated with the dRU. If a subfield with the UL BW is received, the value set in the UL BW subfield and the UL BW subfield are compared as shown in Figure 12. 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.

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

[0124] Information indicating that the dRU-related features are supported and / or enabled is The management frame may be used to transmit frames related to Beacon, Probe, Authentication, and (Re)Association. .

[0125] Information indicating that the dRU-related features are supported and / or enabled is The control frame may be used to transmit frames related to each of the Ack, RTS, CTS, and Trigger frames.

[0126] Information indicating that the dRU-related features are supported and / or enabled is may be included in the Trigger frame.

[0127] Information indicating that the dRU-related features are supported and / or enabled is It may be included in the Management and Extension frame of the

[0128] Supporting and / or enabling the functionality related to dRU is a requirement of a particular Operating It may be indicated by Mode.

[0129] If the dRU-related features are not indicated as supported and / or enabled, the combination of the value set in the UL BW subfield and the value set in the UL BW Ext subfield shall Accordingly, only the UL BW may be determined.

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

[0131] The operation of a STA in a BSS in the 2.4 GHz band is governed by various operation elements (e.g. For example, it may be controlled by a HT / HE / EHT / UHR Operation element.

[0132] The operation of a STA in a BSS in the 5 GHz band is governed by various Operation elements (e.g. , HT / VHT / HE / EHT / UHR Operation element).

[0133] The operation of a STA in a BSS in the 6 GHz band is governed by various Operation elements (e.g. , HE / EHT / UHR Operation element).

[0134] The operation of a STA in a BSS in a frequency band higher than 6 GHz may be controlled by a UHR Operation element.

[0135] FIG. 13 is a diagram showing an example of various fields / subfields included in an Operation element format according to one aspect of this embodiment. FIG. 13(a) is a diagram showing an Element format according to one aspect of this embodiment. FIG. 13(b) is a diagram showing an example of an Operation element format according to one aspect of this embodiment. FIG. 13(c) is a diagram showing Operation Parameters according to one aspect of this embodiment. 13(d) shows an example of an Operation Information field format according to one aspect of the present embodiment. FIG. 13(e) shows an example of a Control subfield format according to one aspect of the present embodiment.

[0136] If the combination of the Element ID and the value set in the Element ID Extension included in the Element format indicates an Operation element, the Element format in Figure 13(a) is 13(b) may be considered to be an Operation element as described in the preceding paragraph.

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

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

[0139] 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 may be set to 0 otherwise. If the Operation Information Present subfield is set to 0, the Distribution Subchannel Bitmap Present subfield may be reserved.

[0140] The Operation Information field is set to 1 if the Operation Information Present subfield is set to 1. If the channel configuration parameters are set, they may be included in the Operation element. If not, the Operation Information field may be omitted. The STA may obtain the set of channel configuration parameters from the Operation Information field.

[0141] Operation Information field is Control subfield, CCFS0 subfield, CCFS1 subfield, Disabled Subchannel Bitmap subfield, Distribution Subchannel Bitmap subfield may include:

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

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

[0144] The CCFS0 subfield is the channel center frequency for BSS bandwidths of 20, 40, and 80 MHz. The CCFS0 subfield may be used to specify a primary 80 MHz channel for a 160 MHz BSS bandwidth. The CCFS0 subfield may be used to specify a primary 160 MHz channel for a 320 MHz BSS bandwidth. The CCFS0 subfield specifies the BSS bandwidth at which the BSS operates, for 20, 40, or 80 MHz. The CCFS0 subfield may be used to indicate the CCF index of the 20, 40, or 80 MHz channel in which the BSS operates. The CCFS0 subfield may also be used to indicate the CCF index of the primary 80 MHz channel in which the BSS operates for a BSS bandwidth of 160 MHz. The CCFS0 subfield may also be used to indicate the CCF index of the primary 160 MHz channel in which the BSS operates for a BSS bandwidth of 320 MHz.

[0145] The CCFS1 subfield may be used to specify the CCF for 160 and 320 MHz BSS bandwidths. The CCFS1 subfield is set to 0 for 20, 40, and 80 MHz BSS bandwidths, i.e., when the Channel Width subfield is set to 20, 40, or 80 MHz BSS bandwidth. The CCFS1 subfield may also be used to indicate the CCF index of the 160 MHz channel on which the BSS operates for a 160 MHz BSS bandwidth. The CCFS1 subfield may also be used to indicate the CCF index of the 320 MHz channel on which the BSS operates for a 320 MHz BSS bandwidth.

[0146] An AP may set the Operation Information Present subfield in the Operation element by satisfying one or more conditions. One or more conditions may include: Alternatively, the one or more conditions may be when the AP announces a BSS operating channel width to one or more non-AP STA(s) via an Operation element, and the BSS operating channel width announced to a non-AP STA of a different type from the non-AP STA in the same Management frame is different from the BSS operating channel width announced to the non-AP STA. Alternatively, the one or more conditions may be that the BSS operating channel width announced to the non-AP STA(s) includes at least one punctured 20 MHz subchannel, and / or that the BSS operating channel width announced to the non-AP STA(s) is 320 MHz. Alternatively, the one or more conditions may be that the BSS operating channel width announced to the non-AP STA(s) includes at least one 20 MHz subchannel to which dRU Allocation is applied (i.e., distribution subchannel). 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 may not include the Operation Information field in the Operation element.

[0147] 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 punctured subchannels within the BSS bandwidth. Otherwise, the Disabled Subchannel Bitmap subfield may not be included in the Operation Information field.

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

[0149] 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 is applied within the BSS bandwidth. Otherwise, the Distribution Subchannel Bitmap subfield may not be included in the Operation Information field.

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

[0151] If the Distribution Subchannel Bitmap subfield indicates whether dRU Allocation is applied in 80MHz frequency subblock units, it should be less than 16 bits ( For example, it may be configured as a bitmap of 4 bits. The Distribution Subchannel Bitmap subfield specifies the number of 20 MHz subchannels included in the 80 MHz frequency subblock. It may also indicate whether the bit is punctured or not.

[0152] The Distribution Subchannel Bitmap subfield is included in the Bandwidth Indication element. This may also be done.

[0153] Bandwidth Indication element is channel bandwidth, CCF, punctured subchannels Furthermore, the Bandwidth Indication element may include information indicating distribution subchannels if the AP and non-AP STAs support and / or enable functionality related to the dRU.

[0154] The Bandwidth Indication element is shown as a subelement contained in various elements. That's fine.

[0155] Fig. 14 is a diagram showing an example of a Bandwidth Indication element according to one aspect of the present embodiment. Fig. 14(a) is a diagram showing an example of a Bandwidth Indication element format according to one aspect of the present embodiment. Fig. 14(b) is a diagram showing an example of a Bandwidth Indication Parameters field format according to one aspect of the present embodiment.

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

[0157] If the Bandwidth Indication Information field includes the Distribution Subchannel Bitmap subfield, the Distribution Subchannel Bitmap Present subfield shall be set to 1. Otherwise, the Distribution Subchannel Bitmap Present subfield may be set to 0.

[0158] The Operation element may be included in a Beacon frame, a Probe Response frame, an Association Response frame, or a Reassociation Response frame.

[0159] The Bandwidth Indication element may be included in a Beacon frame, a Probe Response frame, an Association Response frame, or a Reassociation Response frame.

[0160] The Bandwidth Indication Information field may include the same information and / or subfields as the Operation Information field of the Operation element shown in FIG.

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

[0162] When 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, for one or more 20 MHz subchannels for which the bitmap bits of the Disabled Subchannel Bitmap subfield are set to 1, one or more of those 20 MHz subchannels may be set as distribution subchannels. In such a case, a non-AP STA to which rRU Allocation is applied may determine the punctured subchannel based on the Disabled Subchannel Bitmap subfield and determine the resource configuration of the rRU. In such a case, when dRU Allocation is applied, The non-AP STAs configure the dRU resource based on the Distribution Subchannel Bitmap subfield. The composition of the

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

[0164] Independently 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, If one 20MHz subchannel indicated to be punctured by the Bitmap subfield overlaps with a 40MHz distribution BW, the non-AP STA can transmit the punctured subchannel corresponding to the bit set to 1 by the Disabled Subchannel Bitmap subfield in the 40MHz distribution BW. The resource configuration of the dRU may be determined by puncturing the 20 MHz subchannel.

[0165] The Distribution Subchannel Bitmap subfield is included in the Common Info field of the Trigger frame. The bandwidth indicated by the UL BW subfield included in the Common Info field may be included. The size of the bitmap in the Distribution Subchannel Bitmap subfield is changed accordingly. may be defined as

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

[0167] The Distribution Subchannel Bitmap subfield is included in the User Info field of the Trigger frame. The Distribution Subchannel Bitmap subfield may be configured as a 4-bit bitmap in accordance with the 80 MHz frequency subblock to which the RU Allocation subfield included in the User Info field corresponds.

[0168] The Distribution Subchannel Bitmap subfield may be included in the OM (Operating Mode) Control field. The bitmap included in the Distribution Subchannel Bitmap subfield is set to match the bandwidth indicated by the Channel Width subfield included in the OM Control field. The size of may be defined differently.

[0169] The subfield for indicating the configuration of the distribution BW within the BSS bandwidth may be included in the Common Info field of the Trigger frame. Also, the subfield for indicating the configuration of the distribution BW within the BSS bandwidth must match the bandwidth set in the UL BW subfield within the BSS bandwidth. In this case, the structure of the distribution BW may be shown. may be a subfield for indicating the configuration of the distribution BW within the UL BW.

[0170] The subfield for indicating the configuration of the distribution BW within the BSS bandwidth may be included in the Special User Info field of the Trigger frame. Also, the subfield for indicating the configuration of the distribution BW within the BSS bandwidth may be the value set in the UL BW subfield within the BSS bandwidth and The distribution BW is set according to the bandwidth corresponding to the value set in the UL BW Ext subfield. The configuration may be shown.

[0171] The subfield for indicating the configuration of the distribution BW within the BSS bandwidth may be included in the User Info field of the Trigger frame. Also, the subfield for indicating the configuration of the distribution BW within the BSS bandwidth may indicate the configuration of the distribution BW in accordance with the 80 MHz frequency subblock to which the RU Allocation subfield within the BSS bandwidth corresponds. In other words, in such a case, the subfield is used to indicate the configuration of the distribution BW within the 80 MHz frequency subblock. It may be a subfield for that purpose.

[0172] A subfield for indicating the configuration of the distribution BW within the BSS bandwidth may be included in the OM Control field. The subfield for indicating the configuration of the distribution BW within the BSS bandwidth may indicate the configuration of the distribution BW according to 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 for indicating the configuration of the distribution BW within the bandwidth indicated by the Channel Width subfield.

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

[0174] Note that a part of the STA in the above-described embodiment may be realized by a computer. In this case, the control function may be realized by recording a program for realizing the control function on a computer-readable recording medium, and reading and executing the program recorded on the recording medium into a computer system.

[0175] The "computer system" referred to here is the computer system built into the STA. The term "computer-readable recording medium" refers to a system, including hardware such as an OS and peripheral devices. Also, "computer-readable recording medium" refers to a flexible disk, optical magnetic disk, ROM, CD-ROM, etc. This refers to portable media, hard disks and other storage devices built into computer systems.

[0176] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a certain period of time, such as a volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0177] A non-AP STA may comprise at least one processor and at least one memory containing computer program instructions (computer programs). The memory and computer program instructions (computer programs) may be configured to cause the terminal device 1 to perform the operations and processes described in the above embodiments using a processor. An AP or STA may comprise at least one processor and at least one memory containing computer program instructions. The memory and computer program instructions (computer program) may be used by a processor to cause an AP or STA to perform the operations and processes described in the above embodiments. Such a configuration is also possible.

[0178] Furthermore, the AP in the above-described embodiments can also be realized as a group (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the AP according to the above-described embodiments. The device group only needs to have all of the functions or functional blocks of the AP. Furthermore, the STA according to the above-described embodiments can also communicate with the AP as a group.

[0179] Furthermore, the AP in the above-described embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). In addition, the AP in the above-described embodiment has the function of an upper node for the eNodeB and / or gNB. It may have some or all of the functions.

[0180] Furthermore, a part or all of the STA in the above-described embodiment may be realized as an LSI, which is typically an integrated circuit, or as a chipset. They may be individually chipped, or part or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. If an integrated circuit technology that replaces LSI emerges due to advances in semiconductor technology, It is also possible to use an integrated circuit.

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

[0182] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0183] 101 BSS 102 AP 103 non-AP STA SU1, AU1 antenna section SU2, AU2 RF section SU3, AU3 physical layer processing section SU4, AU4 MAC layer processing section SU5 Upper layer packet processing unit AU5 DSAF SU6, AU6 radio transceiver SU7, AU7 frame processing section

Claims

1. a receiving unit for receiving an operation element; a transmitting unit that determines a resource configuration of a TB PPDU requested to be transmitted based on the Operation element; When the Operation element includes a Bitmap subfield indicating whether dRU Allocation is applied to each of one or more 20 MHz subchannels in the BSS bandwidth, the transmitter Determine the resource configuration for dRU Allocation using subchannels Terminal device.

2. The Operation element includes a Disabled Subchannel Bitmap subfield used to indicate whether one or more 20 MHz subchannels in the BSS bandwidth are punctured. The terminal device according to claim 1.

3. The transmitter unit sets the Disabled Subchannel Bitmap subfield and the Bitmap subfield to 1 for the same 20 MHz subchannel when the Operation element includes the Disabled Subchannel Bitmap subfield and the Bitmap subfield. If the 20 MHz subchannel is specified, puncture the 20 MHz subchannel in the resource configuration. The terminal device according to claim 2.

4. a transmitter that transmits an operation element, The transmitter includes, in the Operation element, a Bitmap subfield indicating whether dRU Allocation is applied to each of one or more 20 MHz subchannels within the BSS bandwidth. Base station equipment.

5. receiving an Operation element; determining a resource configuration for the requested TB PPDU based on the Operation element; If the Operation element includes a Bitmap subfield that indicates whether dRU Allocation is applied to each of one or more 20MHz subchannels within the BSS bandwidth, and if so, determining a resource configuration for performing dRU Allocation using a 20 MHz subchannel corresponding to a bit set to 1 in the Bitmap subfield. Communication method.

Images