WO2025159473A1 - Method and device for single user transmission or reception based on distributed resource unit in wireless lan system - Google Patents

Abstract

Disclosed are a method and device for single user (SU) transmission or reception based on a distributed resource unit in a wireless LAN system. A method according to one aspect of the present disclosure may comprise the steps in which: a first station (STA) generates a physical layer protocol data unit (PPDU) including a data field and one or more signaling fields including first information related to SU transmission and second information related to the application of a distributed resource unit (DRU); and the first STA transmits the PPDU to a second STA. On the basis of the first information indicating the SU transmission and the second information indicating the application of the DRU, a data field in the PPDU may be mapped onto an SU DRU.

Description

Method and device for transmitting or receiving a single user based on a distributed resource unit in a wireless LAN system

The present disclosure relates to a single-user transmission or reception method and device based on distributed resource units in a wireless local area network (WLAN) system.

New technologies have been introduced for wireless local area networks (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and reduce latency. Among WLAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, recently introduced technologies for WLANs include enhancements for Very High Throughput (VHT) in the 802.11ac standard and enhancements for High Efficiency (HE) in the IEEE 802.11ax standard.

To provide a more advanced wireless communication environment, improved technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for Multiple Input Multiple Output (MIMO), which supports increased bandwidth, efficient utilization of multiple bands, and increased spatial streams, and for coordination of multiple access points (APs), are being studied. In particular, various technologies are being studied to support low latency or real-time traffic. Furthermore, new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions of EHT technology.

The technical problem of the present disclosure is to provide a single user (SU) transmission or reception method and device based on a distributed resource unit (DRU) in a wireless LAN system.

The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

A method according to one aspect of the present disclosure may include: generating, by a first station (STA), a physical layer protocol data unit (PPDU) comprising one or more signaling fields, and a data field, wherein the signaling fields include first information related to single user (SU) transmission and second information related to application of a distributed resource unit (DRU); and transmitting, by the first STA, the PPDU to a second STA. Based on the first information indicating the SU transmission and the second information indicating application of the DRU, the data field in the PPDU may be mapped onto an SU DRU.

A method according to an additional aspect of the present disclosure may include receiving, by a second station (STA), from a first STA, a physical layer protocol data unit (PPDU) comprising one or more signaling fields, and a data field, wherein the PPDU comprises first information relating to single user (SU) transmission and second information relating to application of a distributed resource unit (DRU); and decoding, by the second STA, the data field in the PPDU, which is mapped onto an SU DRU, based on the first information indicating the SU transmission and the second information indicating application of the DRU.

According to the present disclosure, a single user (SU) transmission or reception method and device based on a distributed resource unit (DRU) in a wireless LAN system can be provided.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

FIG. 5 is a diagram for explaining a CSMA/CA-based frame transmission operation to which the present disclosure can be applied.

FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

FIGS. 8 to 10 are diagrams for explaining examples of resource units of a wireless LAN system to which the present disclosure can be applied.

FIG. 11 is a drawing illustrating examples of DRUs to which the present disclosure can be applied.

FIG. 12 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

FIG. 13 is a diagram illustrating an example of the operation of the first STA according to the present disclosure.

FIG. 14 is a diagram illustrating an example of the operation of a second STA according to the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and/or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof.

In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and/or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of "/" between words in this disclosure has the same meaning as "and/or" unless otherwise stated.

The examples of the present disclosure can be applied to various wireless communication systems. For example, the examples of the present disclosure can be applied to a wireless LAN system. For example, the examples of the present disclosure can be applied to a wireless LAN based on the IEEE 802.11a/g/n/ac/ax/be standards. Furthermore, the examples of the present disclosure can be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard. Additionally, the examples of the present disclosure can be applied to a wireless LAN based on the next-generation standard after IEEE 802.11bn. Furthermore, the examples of the present disclosure can be applied to a cellular wireless communication system. For example, the examples of the present disclosure can be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series of technologies and the 5G NR (New Radio) series of technologies of the 3rd Generation Partnership Project (3GPP) standard.

Below, technical features to which examples of the present disclosure can be applied are described.

FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

The first device (100) and the second device (200) illustrated in FIG. 1 may be replaced with various terms such as a terminal, a wireless device, a WTRU (Wireless Transmit Receive Unit), a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an MSS (Mobile Subscriber Unit), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), or simply a user. In addition, the first device (100) and the second device (200) may be replaced with various terms such as an access point (AP), a BS (Base Station), a fixed station, a Node B, a BTS (Base Transceiver System), a network, an AI (Artificial Intelligence) system, an RSU (road side unit), a repeater, a router, a relay, a gateway, etc.

The devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs). For example, the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, in the present disclosure, the STAs (110, 200) may perform the functions of an AP and/or a non-AP. When the STAs (110, 200) perform an AP function, they may simply be referred to as APs, and when the STAs (110, 200) perform a non-AP function, they may simply be referred to as STAs. In addition, in the present disclosure, the APs may also be referred to as AP STAs.

Referring to FIG. 1, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless LAN technologies (e.g., IEEE 802.11 series). The first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.11 standard.

In addition, the first device (100) and the second device (200) may additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than wireless LAN technology. In addition, the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

A first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and/or one or more antennas (108). The processor (102) controls the memories (104) and/or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memories (104) to generate first information/signals, and then transmit a wireless signal including the first information/signals via the transceivers (106). Furthermore, the processor (102) may receive a wireless signal including second information/signals via the transceivers (106), and then store information obtained from signal processing of the second information/signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (106) may be connected to the processor (102) and may transmit and/or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and/or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem/circuit/chip.

The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and/or one or more antennas (208). The processor (202) controls the memories (204) and/or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information/signals, and then transmit a wireless signal including the third information/signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information/signals via the transceivers (206), and then store information obtained from signal processing of the fourth information/signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (206) may be connected to the processor (202) and may transmit and/or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and/or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem/circuit/chip.

Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and/or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in the present disclosure.

One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and/or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and/or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.

One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and/or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and/or combinations thereof. The one or more memories (104, 204) may be located internally and/or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

One or more transceivers (106, 206) can transmit user data, control information, wireless signals/channels, etc., as mentioned in the methods and/or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals/channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and/or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals/channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals/channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and/or a filter.

For example, one of the STAs (100, 200) may perform the intended operation of an AP, and the other of the STAs (100, 200) may perform the intended operation of a non-AP STA. For example, the transceivers (106, 206) of FIG. 1 may perform transmission and reception operations of signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.11a/b/g/n/ac/ax/be/bn, etc.). In addition, in the present disclosure, operations in which various STAs generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals may be performed in the processors (102, 202) of FIG. 1. For example, an example of an operation for generating a transmission/reception signal or performing data processing or operation in advance for a transmission/reception signal may include 1) an operation for determining/obtaining/configuring/computing/decoding/encoding bit information of a field (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU, 2) an operation for determining/configuring/obtaining time resources or frequency resources (e.g., subcarrier resources) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 4) a power control operation and/or a power saving operation applied to an STA, 5) an operation related to determining/obtaining/configuring/computing/decoding/encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields/subfields/control fields/parameters/power, etc.) used by various STAs for determining/acquiring/configuring/computing/decoding/encoding transmission/reception signals can be stored in the memory (104, 204) of FIG. 1.

Hereinafter, downlink (DL) refers to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs/packets/signals, etc. can be transmitted and received through the downlink. In downlink communication, the transmitter may be part of an AP STA, and the receiver may be part of a non-AP STA. Uplink (UL) refers to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs/packets/signals, etc. can be transmitted and received through the uplink. In uplink communication, the transmitter may be part of a non-AP STA, and the receiver may be part of an AP STA.

FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports transparent STA mobility to the upper layer can be provided. A Basic Service Set (BSS) corresponds to a basic building block of a wireless LAN. FIG. 2 illustrates, by way of example, the existence of two BSSs (BSS1 and BSS2) and the inclusion of two STAs as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). The oval representing a BSS in FIG. 2 can also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). When an STA moves outside of a BSA, it cannot directly communicate with other STAs within the BSA.

If we do not consider the DS illustrated in Figure 2, the most basic type of BSS in a wireless LAN is an Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For example, assuming other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4, can be representative examples of an IBSS, respectively. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, in this type of WLAN, a LAN can be configured when needed rather than being planned in advance, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems (DS) is not permitted, forming a self-contained network.

An STA's membership in a BSS can dynamically change, for example, when an STA is turned on or off, or when an STA enters or leaves a BSS area. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services in the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may involve the use of a Distribution System Service (DSS).

In a wireless LAN, the direct STA-to-STA distance can be limited by PHY performance. While this distance limit may be sufficient in some cases, communication between STAs over longer distances may be required in other cases. To support extended coverage, a distributed system (DS) can be configured.

DS refers to a structure in which BSSs are interconnected. Specifically, a BSS may exist as an extended component of a network composed of multiple BSSs, as illustrated in Figure 2. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, the Wireless Medium (WM) and DSM can be logically distinguished. Each logical medium is used for a different purpose and by different components. These media are neither limited to being identical nor limited to being different. This logical difference between multiple media explains the flexibility of the WLAN architecture (DS architecture or other network architectures). In other words, the WLAN architecture can be implemented in various ways, and the physical characteristics of each implementation can independently specify the WLAN architecture.

A DS can support mobile devices by providing seamless integration of multiple BSSs and the logical services necessary to handle addresses to destinations. Additionally, a DS may further include a component called a portal, which acts as a bridge for connecting wireless LANs to other networks (e.g., IEEE 802.X).

An AP is an entity that enables access to a DS through a WM for associated non-AP STAs and also has the functionality of an STA. Data movement between a BSS and a DS can be performed through an AP. For example, STA2 and STA3 illustrated in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS. In addition, since all APs are basically STAs, all APs are addressable entities. The address used by an AP for communication on a WM and the address used by an AP for communication on a DSM do not necessarily have to be the same. A BSS consisting of an AP and one or more STAs can be referred to as an infrastructure BSS.

Data transmitted from one of the STA(s) associated with an AP to the STA address of that AP may always be received on an uncontrolled port and processed by an IEEE 802.1X port access entity. In addition, if the controlled port is authenticated, the transmitted data (or frame) may be forwarded to the DS.

In addition to the structure of the DS described above, an extended service set (ESS) may be established to provide wider coverage.

An ESS is a network of arbitrary size and complexity, consisting of DSs and BSSs. An ESS may correspond to a set of BSSs connected to a DS. However, an ESS does not include a DS. An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs within an ESS can communicate with each other, and mobile STAs can move from one BSS to another (within the same ESS) transparently to the LLC. APs within an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is the identifier of the BSS.

In a wireless LAN system, no assumptions are made about the relative physical locations of BSSs, and all of the following configurations are possible: BSSs can be partially overlapping, which is commonly used to provide continuous coverage. BSSs can also be physically disconnected, and there is no logical distance limit between them. BSSs can also be physically co-located, which can be used to provide redundancy. Furthermore, one (or more) IBSS or ESS networks can physically co-exist with one (or more) ESS networks. This can occur in cases where an ad-hoc network operates at the same location as an ESS network, where physically overlapping wireless networks are configured by different organizations, or where two or more different access and security policies are required at the same location.

FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

For an STA to set up a link and transmit and receive data on a network, it must first discover the network, perform authentication, establish an association, and complete security authentication procedures. The link setup process can also be referred to as the session initiation process or session setup process. Furthermore, the discovery, authentication, association, and security setup processes of the link setup process can be collectively referred to as the association process.

In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning operations by the STA. That is, for the STA to access a network, it must search for available networks. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning.

Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation including an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover any APs in the vicinity while moving between channels and waits for a response. The responder transmits a probe response frame in response to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, the AP transmits the beacon frame, so the AP becomes the responder. In the IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not fixed. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests/responses on channel 2) in the same manner.

Although not shown in Figure 3, the scanning operation can also be performed in a passive scanning manner. In passive scanning, the STA performing the scanning moves between channels and waits for a beacon frame. A beacon frame is one of the management frames defined in IEEE 802.11. It announces the existence of a wireless network and is periodically transmitted so that the STA performing the scanning can find the wireless network and participate in the wireless network. In the BSS, the AP performs the role of periodically transmitting the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the STA performing the scanning receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. The STA receiving the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel to perform scanning on the next channel in the same manner. Comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

After the STA discovers the network, an authentication process may be performed in step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below.

The authentication process involves the STA sending an authentication request frame to the AP, and the AP responding by sending an authentication response frame to the STA. The authentication frame used for the authentication request/response corresponds to a management frame.

The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group. These are just some examples of information that may be included in an authentication request/response frame, and may be replaced with other information or include additional information.

An STA can send an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

After the STA is successfully authenticated, an association process may be performed in step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA.

For example, the association request frame may include information about various capabilities, a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, an RSN, a mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, the association response frame may include information about various capabilities, a status code, an Association ID (AID), supported rates, an Enhanced Distributed Channel Access (EDCA) parameter set, a Received Channel Power Indicator (RCPI), a Received Signal to Noise Indicator (RSNI), a mobility domain, a timeout interval (e.g., an association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a Quality of Service (QoS) map, etc. These are just some examples of information that may be included in a combined request/response frame, and may be replaced by other information or include additional information.

After the STA successfully joins the network, a security setup process may be performed in step S340. The security setup process in step S340 may be referred to as an authentication process through a Robust Security Network Association (RSNA) request/response, the authentication process in step S320 may be referred to as a first authentication process, and the security setup process in step S340 may also be referred to simply as an authentication process.

The security setup process of step S340 may include, for example, a process of establishing a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame. Furthermore, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.

FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA). The CSMA/CA mechanism, also known as the Distributed Coordination Function (DCF) of the IEEE 802.11 MAC, essentially employs a "listen before talk" access mechanism. According to this type of access mechanism, the AP and/or STA may perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time period (e.g., a DCF Inter-Frame Space (DIFS)) before starting transmission. If the sensing result determines that the medium is in an idle state, the AP and/or STA may start transmitting frames through the medium. On the other hand, if the medium is detected to be occupied or busy, the AP and/or STA may not start its own transmission, but may wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit frames. By applying a random backoff period, multiple STAs are expected to attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.

In addition, the IEEE 802.11 MAC protocol provides the Hybrid Coordination Function (HCF). The HCF is based on the DCF and the Point Coordination Function (PCF). The PCF is a polling-based synchronous access method that periodically polls all receiving APs and/or STAs to ensure that they receive data frames. In addition, the HCF has the Enhanced Distributed Channel Access (EDCA) and the HCF Controlled Channel Access (HCCA). The EDCA is a contention-based access method for a provider to provide data frames to multiple users, while the HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, the HCF includes a medium access mechanism to improve the Quality of Service (QoS) of the wireless LAN, and can transmit QoS data in both the Contention Period (CP) and the Contention Free Period (CFP).

Referring to Fig. 4, an operation based on a random backoff period is described. When an occupied/busy medium changes to an idle state, multiple STAs may attempt to transmit data (or frames). To minimize collisions, each STA may select a random backoff count, wait for the corresponding slot time, and then attempt transmission. The random backoff count has a pseudo-random integer value and may be determined as one of the values in the range of 0 to CW. Here, CW is a contention window parameter value. The CW parameter is initially given a value of CWmin, but may double the value in case of a transmission failure (e.g., if an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, data transmission may be attempted while maintaining the CWmax value until data transmission is successful, and if data transmission is successful, it is reset to the CWmin value. It is desirable that the CW, CWmin and CWmax values be set to 2 ⁿ -1 (n=0, 1, 2, ...).

Once the random backoff process begins, the STA continues to monitor the medium while counting down the backoff slots according to the determined backoff count value. If the medium is monitored as occupied, the countdown stops and waits. When the medium becomes idle, the remaining countdown resumes.

In the example of FIG. 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit a frame if it confirms that the medium is idle for DIFS. The remaining STAs monitor the medium for occupied/busy states and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can count down the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS if the medium is monitored as idle. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. In other words, this example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission. STA1 and STA5 briefly stop counting down and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, they can start transmitting frames after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time is shorter than STA1's, STA5 starts transmitting frames. While STA2 occupies the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS, counts down according to its selected random backoff count value, and then starts transmitting frames. In the example of Figure 4, the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failure in data transmission. In this case, STA4 and STA5 can select a random backoff count value and perform a countdown after doubling the CW value. STA1 waits while the medium is occupied by transmissions from STA4 and STA5, and when the medium becomes idle, it waits for DIFS and can start transmitting frames after the remaining backoff time elapses.

As in the example of Fig. 4, a data frame is a frame used for transmitting data forwarded to a higher layer, and can be transmitted after a backoff performed after DIFS elapses from when the medium becomes idle. Additionally, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS elapses, such as DIFS or PIFS (Point coordination function IFS). Subtype frames of a management frame include a beacon, an association request/response, a re-association request/response, a probe request/response, and an authentication request/response. A control frame is a frame used to control access to the medium. The subtype frames of the control frame include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), Null Data Packet Announcement (NDP), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after a backoff performed after the DIFS (Direct Inverse Frame Stop) has elapsed, and if it is a response frame to the previous frame, it is transmitted without a backoff performed after the SIFS (short IFS). The type and subtype of the frame can be identified by the type field and subtype field in the Frame Control (FC) field.

A QoS (Quality of Service) STA can transmit a frame after a backoff performed after the AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed. Here, the frames for which AIFS[i] can be used can be data frames, management frames, and also control frames that are not response frames.

FIG. 5 is a diagram for explaining a CSMA/CA-based frame transmission operation to which the present disclosure can be applied.

As mentioned above, the CSMA/CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, in which STAs directly sense the medium. Virtual carrier sensing is intended to address potential issues in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of an STA can utilize a Network Allocation Vector (NAV). The NAV is a value that an STA that is currently using or has the right to use the medium indicates to other STAs the remaining time until the medium becomes available. Therefore, the value set as NAV corresponds to the period during which the STA transmitting the frame is scheduled to use the medium, and an STA receiving the NAV value is prohibited from accessing the medium during that period. For example, the NAV can be set based on the value of the "duration" field in the MAC header of the frame.

In the example of FIG. 5, it is assumed that STA1 wants to transmit data to STA2, and STA3 is in a position to overhear some or all of the frames transmitted and received between STA1 and STA2.

In order to reduce the possibility of collisions in transmissions of multiple STAs in a CSMA/CA-based frame transmission operation, a mechanism using RTS/CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA1 may correspond to a hidden node for STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA2 may correspond to a hidden node for STA3. By exchanging RTS/CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

Specifically, STA1 can determine whether a channel is occupied through carrier sensing. In terms of physical carrier sensing, STA1 can determine channel occupancy idleness based on the energy level or signal correlation detected in the channel. Furthermore, in terms of virtual carrier sensing, STA1 can determine the channel occupancy status using a network allocation vector (NAV) timer.

STA1 can transmit an RTS frame to STA2 after performing a backoff if the channel is idle during the DIFS. STA2 can transmit a CTS frame, which is a response to the RTS frame, to STA1 after an SIFS if it receives the RTS frame.

If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can use the duration information contained in the RTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can use the duration information contained in the CTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame). That is, if STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 does not attempt channel access until the NAV timer expires.

If STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the CTS frame is completely received. If STA2 successfully receives the data frame, it can transmit an ACK frame in response to the data frame to STA1 after SIFS. STA3 can determine whether the channel is in use through carrier sensing if the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during the DIFS after the NAV timer expires, it can attempt channel access after a contention window (CW) based on a random backoff has elapsed.

FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

The PHY layer can prepare an MPDU (MAC PDU) to be transmitted based on an instruction or primitive (meaning a set of instructions or parameters) from the MAC layer. For example, when a command requesting the start of transmission of the PHY layer is received from the MAC layer, the PHY layer can switch to transmission mode and transmit the information (e.g., data) provided by the MAC layer in the form of a frame. In addition, when the PHY layer detects a valid preamble of the received frame, it monitors the header of the preamble and sends a command to the MAC layer notifying the start of reception of the PHY layer.

In this way, information transmission/reception in a wireless LAN system is done in the form of frames, and for this purpose, the PHY layer Protocol Data Unit (PPDU) format is defined.

A basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field. The most basic (e.g., non-HT (High Throughput) as illustrated in FIG. 7) PPDU format may consist of only the Legacy-STF (L-STF), Legacy-LTF (L-LTF), Legacy-SIG (L-SIG) fields, and a Data field. Additionally, depending on the type of PPDU format (e.g., HT-mixed format PPDU, HT-greenfield format PPDU, VHT (Very High Throughput) PPDU, etc.), additional (or different types of) RL-SIG, U-SIG, non-legacy SIG field, non-legacy STF, non-legacy LTF, (i.e., xx-SIG, xx-STF, xx-LTF (e.g., xx is HT, VHT, HE, EHT, etc.)) may be included between the L-SIG field and the data field. More specific details will be described later with reference to FIG. 7.

STF is a signal for signal detection, AGC (Automatic Gain Control), diversity selection, and precise time synchronization, while LTF is a signal for channel estimation, frequency error estimation, etc. STF and LTF can be said to be signals for synchronization and channel estimation of the OFDM physical layer.

The SIG field may include various information related to PPDU transmission and reception. For example, the L-SIG field may consist of 24 bits and may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field. The RATE field may include information about the modulation and coding rate of data. For example, the 12-bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, for HE PPDU, the value of the Length field can be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

The data field may include a SERVICE field, a Physical layer Service Data Unit (PSDU), a PPDU TAIL bit, and, if necessary, padding bits. Some bits of the SERVICE field may be used to synchronize the descrambler at the receiving end. The PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated/used by upper layers. The PPDU TAIL bit may be used to return the encoder to a 0 state. The padding bit may be used to adjust the length of the data field to a predetermined unit.

MAC PDUs are defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS). A MAC frame is composed of MAC PDUs and can be transmitted/received through the PSDU in the data portion of the PPDU format.

The MAC header includes a Frame Control field, a Duration/ID field, an Address field, etc. The Frame Control field may include control information required for frame transmission/reception. The Duration/ID field may be set to a time for transmitting the corresponding frame, etc. The Address subfields may indicate the receiver address, transmitter address, destination address, and source address of the frame, and some Address subfields may be omitted. For specific details of each subfield of the MAC header, including the Sequence Control, QoS Control, and HT Control subfields, refer to the IEEE 802.11 standard document.

The Null-Data PPDU (NDP) format refers to a PPDU format that does not include a data field. In other words, NDP refers to a frame format that includes a PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and, if additionally present, non-legacy SIG, non-legacy STF, and non-legacy LTF) in the general PPDU format, and does not include the remaining part (i.e., data field).

FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

Standards such as IEEE 802.11a/g/n/ac/ax use various PPDU formats. The basic PPDU format (IEEE 802.11a/g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format can also be referred to as the non-HT PPDU format (Fig. 7(a)).

The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format illustrated in Fig. 7(b) may be referred to as an HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format that does not include L-STF, L-LTF, and L-SIG, but consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).

An example of the VHT PPDU format (IEEE 802.11ac) includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format (Fig. 7(c)).

An example of a HE PPDU format (IEEE 802.11ax) additionally includes RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in addition to the basic PPDU format (Fig. 7(d)). Depending on specific examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-users (MUs), but the HE-SIG-B is not included in the HE PPDU format for single users (SUs). In addition, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8 microseconds (us). The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field can vary to 16us. For example, the RL-SIG can be configured identically to the L-SIG. The receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU, described later, based on the presence of the RL-SIG.

The EHT PPDU format may include the EHT MU (multi-user) PPDU of FIG. 7(e) and the EHT TB (trigger-based) PPDU of FIG. 7(f). The EHT PPDU format is similar to the HE PPDU format in that it includes an RL-SIG following an L-SIG, but may include a U (universal)-SIG, an EHT-SIG, an EHT-STF, and an EHT-LTF following the RL-SIG.

The EHT MU PPDU in FIG. 7(e) corresponds to a PPDU that carries one or more data (or PSDUs) for one or more users. That is, the EHT MU PPDU can be used for both SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.

The EHT TB PPDU of Fig. 7(f) omits the EHT-SIG compared to the EHT MU PPDU. An STA that has received a trigger for UL MU transmission (e.g., a trigger frame or TRS (triggered response scheduling)) can perform UL transmission based on the EHT TB PPDU format.

The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated to allow legacy STAs to attempt demodulation and decoding, and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated to allow STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and/or EHT-SIG) and obtained the information contained in the fields, and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields may be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, Data, and PE fields may be referred to as HE modulation fields. Additionally, in the VHT PPDU format, the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields may be referred to as pre-VHT modulation fields, and the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields may be referred to as VHT modulation fields.

The U-SIG included in the EHT PPDU format of FIG. 7 can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG can have a duration of 4 us, and the U-SIG can have a total duration of 8 us. Each symbol of the U-SIG can be used to transmit 26 bits of information. For example, each symbol of the U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

U-SIGs can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be duplicated in 20MHz units. That is, four identical U-SIGs can be included in an 80MHz PPDU. When the bandwidth exceeds 80MHz, for example, for a 160MHz PPDU, the U-SIGs in the first 80MHz unit and the U-SIGs in the second 80MHz unit can be different.

For example, A uncoded bits may be transmitted via U-SIG, and a first symbol of U-SIG (e.g., a U-SIG-1 symbol) may transmit the first X bits of information out of a total A bits of information, and a second symbol of U-SIG (e.g., a U-SIG-2 symbol) may transmit the remaining Y bits of information out of a total A bits of information. The A bits of information (e.g., 52 uncoded bits) may include a CRC field (e.g., a field of 4 bits in length) and a tail field (e.g., a field of 6 bits in length). The tail field may be used to terminate the trellis of the convolutional decoder and may be set to 0, for example.

The A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in a new PPDU format (e.g., UHR PPDU format) not shown in FIG. 7, and in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-dependent bits can be different.

For example, the size of the version-independent bits of U-SIG can be fixed or variable. The version-independent bits can be assigned only to U-SIG-1 symbols, or to both U-SIG-1 symbols and U-SIG-2 symbols. The version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier, which may indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted and received PPDUs. The version-independent bits of the U-SIG may include a 1-bit UL/DL flag field. The first value of the 1-bit UL/DL flag field relates to UL communication, and the second value of the UL/DL flag field relates to DL communication. The version-independent bits of the U-SIG may include information about the length of a transmission opportunity (TXOP) and information about a BSS color ID.

For example, the version-dependent bits of the U-SIG may contain information that directly or indirectly indicates the type of PPDU (e.g., SU PPDU, MU PPDU, TB PPDU, etc.).

Information required for PPDU transmission and reception may be included in the U-SIG. For example, the U-SIG may further include information about bandwidth, information about the MCS technique applied to the non-legacy SIG (e.g., EHT-SIG or UHR-SIG), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique to achieve an effect similar to frequency diversity by reusing the same signal on two subcarriers) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, information about whether the non-legacy SIG is generated across the entire band, etc.

Some of the information required for transmitting and receiving a PPDU may be included in the U-SIG and/or the non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.). For example, information about the type of the non-legacy LTF/STF (e.g., EHT-LTF/EHT-STF or UHR-LTF/UHR-STF, etc.), information about the length of the non-legacy LTF and the cyclic prefix (CP) length, information about the guard interval (GI) applicable to the non-legacy LTF, information about preamble puncturing applicable to the PPDU, information about resource unit (RU) allocation, etc. may be included only in the U-SIG, may be included only in the non-legacy SIG, or may be indicated by a combination of the information included in the U-SIG and the information included in the non-legacy SIG.

Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the PPDU's bandwidth. For example, the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth greater than a certain size.

In the example of FIG. 7, non-legacy SIGs such as HE-SIG-B and EHT-SIG may include control information for the receiving STA. The non-legacy SIG may be transmitted over at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG may be included in a previous SIG (e.g., HE-SIG-A, U-SIG, etc.).

Non-legacy SIGs, such as HE-SIG-B and EHT-SIG, may contain common fields and user-specific fields. Common and user-specific fields may be coded separately.

In some cases, common fields may be omitted. For example, in a compressed mode where non-OFDMA (orthogonal frequency multiple access) is applied, common fields may be omitted, and multiple STAs may receive PPDUs (e.g., data fields of PPDUs) over the same frequency band. In a non-compressed mode where OFDMA is applied, multiple users may receive PPDUs (e.g., data fields of PPDUs) over different frequency bands.

The number of user-specific fields can be determined based on the number of users. A single user block field can contain up to two user fields. Each user field can be associated with either MU-MIMO allocation or non-MU-MIMO allocation.

The common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, and the length of the Tail bits may be determined as 6 bits and set to 000000. The common field may include RU allocation information. The RU allocation information may include information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.

An RU can contain multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA techniques. RUs can also be defined when transmitting signals to a single STA. Resources can be allocated on an RU basis for non-legacy STFs, non-legacy LTFs, and data fields.

Depending on the PPDU bandwidth, an applicable RU size can be defined. The RU may be defined identically or differently for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80MHz PPDU, the RU arrangements of HE PPDU and EHT PPDU may be different. The applicable RU size, RU number, RU position, DC (direct current) subcarrier position and number, null subcarrier position and number, guard subcarrier position and number, etc. for each PPDU bandwidth can be referred to as a tone plan. For example, a tone plan for a wide bandwidth can be defined in the form of multiple repetitions of a low bandwidth tone plan.

RUs of different sizes can be defined, such as 26-ton RU, 52-ton RU, 106-ton RU, 242-ton RU, 484-ton RU, 996-ton RU, 2X996-ton RU, 4X996-ton RU, etc. A multiple RU (MRU) is distinguished from multiple individual RUs and corresponds to a group of subcarriers consisting of multiple RUs. For example, one MRU can be defined as 52+26-tons, 106+26-tons, 484+242-tons, 996+484-tons, 996+484+242-tons, 2X996+484-tons, 3X996-tons, or 3X996+484-tons. Additionally, multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.

The specific size of an RU may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. Furthermore, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, etc.) in the present disclosure, the number of RUs may vary depending on the RU size.

The names of each field in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by those names. Furthermore, the examples of the present disclosure can be applied not only to the PPDU format exemplified in FIG. 7, but also to a new PPDU format in which some fields are excluded and/or some fields are added based on the PPDU formats of FIG. 7.

Resource Unit

FIGS. 8 to 10 are diagrams for explaining examples of resource units of a wireless LAN system to which the present disclosure can be applied.

Referring to FIGS. 8 to 10, a resource unit (RU) defined in a wireless LAN system is described. An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on OFDMA techniques. An RU may also be defined when transmitting signals to a single STA. An RU may be used for the STF, LTF, and data fields of a PPDU.

As illustrated in FIGS. 8 to 10, RUs corresponding to different numbers of tones (i.e., subcarriers) may be used to configure some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X represents HE, EHT, etc.). For example, resources may be allocated in units of RUs illustrated for the X-STF, X-LTF, and Data fields.

Figure 8 is a diagram showing an exemplary arrangement of resource units (RUs) used on a 20 MHz band.

As shown at the top of Fig. 8, 26 units (i.e., units corresponding to 26 tones) may be allocated. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones may be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for an STA or a user.

The RU arrangement of Fig. 8 can be utilized not only in situations for multiple users (MUs) but also in situations for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of Fig. 8. In this case, three DC tones can be inserted.

In the example of FIG. 8, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are exemplified, but the specific sizes of these RUs may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. In addition, in the present disclosure, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...), the number of RUs may vary depending on the RU size. In the examples of FIG. 9 and/or FIG. 10 described below, the fact that the size and/or number of RUs may be changed is the same as the example of FIG. 8.

Figure 9 is a diagram showing an exemplary arrangement of resource units (RUs) used on a 40 MHz band.

As in the example of FIG. 8 where RUs of various sizes were used, the example of FIG. 9 may also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, five DC tones may be inserted at the center frequency, 12 tones may be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 40 MHz band.

Additionally, as shown, when used for a single user, 484-RU may be used.

Figure 10 is a diagram showing an exemplary arrangement of resource units (RUs) used on the 80 MHz band.

As in the examples of FIGS. 8 and 9 where RUs of various sizes were used, the example of FIG. 10 may also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. In addition, in the case of 80MHz PPDU, the RU arrangement of HE PPDU and EHT PPDU may be different, and the example of FIG. 10 shows an example of the RU arrangement for 80MHz EHT PPDU. In the example of FIG. 10, 12 tones are used as guard bands in the leftmost band of the 80MHz band, and 11 tones are used as guard bands in the rightmost band of the 80MHz band, which is the same for HE PPDU and EHT PPDU. Unlike the HE PPDU, which has seven DC tones inserted into the DC band and one 26-RU corresponding to 13 tones on each side of the DC band, the EHT PPDU has 23 DC tones inserted into the DC band and one 26-RU corresponding to 13 tones on each side of the DC band. Unlike the HE PPDU, which has one null subcarrier between the 242-RUs other than the center band, the EHT PPDU has five null subcarriers. In the HE PPDU, one 484-RU does not contain a null subcarrier, but in the EHT PPDU, one 484-RU contains five null subcarriers.

Also, as shown, when used for a single user, 996-RU can be used, in which case the insertion of 5 DC tones is common in both HE PPDU and EHT PPDU.

An EHT PPDU of 160MHz or higher may be configured with multiple 80MHz subblocks as shown in FIG. 10. The RU layout for each 80MHz subblock may be the same as the RU layout of the 80MHz EHT PPDU as shown in FIG. 10. If an 80MHz subblock of a 160MHz or 320MHz EHT PPDU is not punctured and the entire 80MHz subblock is used as part of an RU or MRU (Multiple RU), the 80MHz subblock may use 996-RU as shown in FIG. 10.

Here, an MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs constituting an MRU may be RUs of the same size or different sizes. For example, a single MRU may be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2X996+484-tones, 3X996-tones, or 3X996+484-tones. Here, the multiple RUs constituting one MRU may correspond to RUs of small size (e.g., 26, 52, 106) or RUs of large size (e.g., 242, 484, 996, etc.). That is, a single MRU containing both small-sized RUs and large-sized RUs may not be configured/defined. Furthermore, multiple RUs constituting a single MRU may or may not be consecutive in the frequency domain.

If an 80MHz subblock contains RUs smaller than 996 tones, or portions of the 80MHz subblock are punctured, the 80MHz subblock may use RU layouts other than the 996-tone RUs.

The RU of the present disclosure can be used for uplink (UL) and/or downlink (DL) communication. For example, when trigger-based UL-MU communication is performed, an STA (e.g., an AP) transmitting a trigger can allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA and a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA through trigger information (e.g., a trigger frame or triggered response scheduling (TRS)). Thereafter, the first STA can transmit a first trigger-based (TB) PPDU based on the first RU, and the second STA can transmit a second TB PPDU based on the second RU. The first/second TB PPDU can be transmitted to the AP in the same time interval.

For example, when a DL MU PPDU is configured, an STA (e.g., an AP) transmitting a DL MU PPDU may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA, and a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA. That is, the transmitting STA (e.g., the AP) may transmit X-STF (e.g., X is HE, EHT, etc.), X-LTF, and Data fields for the first STA through the first RU within one MU PPDU, and may transmit X-STF, X-LTF, and Data fields for the second STA through the second RU. Information about the arrangement of RUs may be signaled through an X-SIG (e.g., X is HE, EHT, U) field of the X-PPDU format.

Distributed resource units

Regulations in various regions may impose power spectral density (PSD) limitations in the sub-7GHz (e.g., 6GHz) band. For non-AP STAs in the low power indoor (LPI) band, the PSD limitation may be -1dBm/MHz. For example, for a conventional 52-tone RU, the maximum transmit (Tx) power may be approximately 6dBm.

Additionally, different restrictions may apply in the 2.4 GHz and 5 GHz bands. For example, a PSD restriction of 10 dBm/MHz may apply in the EU/China/Japan/Korea in the 2.4 GHz band. This would result in a maximum Tx power of approximately 17 dBm for a conventional 52-tone RU. Bypassing the PSD restriction in the 5 GHz band would allow for higher transmit power. For example, the maximum transmit power for a conventional 52-tone RU is 24 dBm, which is still 6 dBm below the maximum allowable effective isotropic radiated power (EIRP) of 30 dBm.

Overcoming PSD limitations can increase transmit power, thereby improving spectral efficiency or extending range.

Considering that the PSD limit is defined per MHz for each STA, when distributing tones of small RUs over a wide bandwidth, the tones for each STA are non-contiguous, so each tone can be transmitted at high power. An RU containing such distributed tones is called a distributed RU (DRU), and to distinguish it from an RU containing continuous tones defined in a conventional wireless LAN system (e.g., a system according to IEEE 802.11ax, 11be, etc.) can be called a regular RU (RRU).

Compared to STAs transmitting on conventional RRUs, STAs transmitting on DRUs can use higher power. For example, a 52-tone DRU across 80 MHz has only one tone per MHz, whereas a 52-tone RRU has approximately 13 tones per MHz. Assuming a PSD limit of -1 dBm/MHz in the 6 GHz LPI band, using a DRU can increase the transmit power by 11 dB for a 52-tone RU. This increased transmit power allows for a higher MCS and longer range.

FIG. 11 is a drawing illustrating examples of DRUs to which the present disclosure can be applied.

In the example of Fig. 11, STA1 transmits on DRU1, STA2 transmits on DRU2, and STA3 transmits on DRU3. Each STA can apply a transmission power boost by using a DRU. Compared to cases where RRUs of the same size are used, the DRU applies higher transmission power to all tones, and thus, spectral efficiency can be significantly improved. In this way, the DRU can be applied particularly usefully in UL-OFDMA.

APs can also utilize DRUs. In some cases, the AP may use only some of DRUs (DRU1, DRU2, and DRU3) to transmit DL-OFDMA to STAs, in which case the transmit power boost due to the use of DRUs may be applied.

To maximize power boost, tones within a single DRU can be distributed as far apart as possible. For example, a DRU containing one tone per MHz may be considered optimal. The size of a DRU (or the number of available tones contained in a DRU, i.e., the number of tones excluding unusable tones such as null tones, guard tones, and DC tones) can be defined to be the same as the size of an RRU (or the number of available tones contained in an RRU). This can minimize the impact on various technologies that are already defined based on RRUs. The table below shows examples of achievable power boost (in dB) for various DRUs distributed over different bandwidths. The examples in the table below assume the 6 GHz LPI band, and power boost can also be achieved in the 2.4 GHz and 5 GHz bands in other regions. For example, in an 80 MHz UL-OFDMA transmission by 8 users, if each user uses a 106-tone DRU, the overall performance can be improved by approximately 8.13 dB compared to when each user uses a 106-tone RRU. Thus, by using DRUs, the PSD limitation can be overcome and significant gains can be obtained.

20MHz bandwidth 40MHz bandwidth 80MHz bandwidth 26-ton RU 8.13 11.14 11.14 52-ton RU 6.37 8.13 11.14 106-ton RU 3.36 6.37 8.13 242-ton RU Not applicable 2.69 5.12 484-ton RU Not applicable Not applicable 2.69

FIG. 12 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

A trigger frame may allocate resources for the transmission of one or more TB PPDUs and request the transmission of TB PPDUs. The trigger frame may also include other information required by the STA transmitting the TB PPDU in response. The trigger frame may include common information and a user information list field in the frame body.

The common information field may include information that is common to one or more TB PPDU transmissions requested by a trigger frame, such as trigger type, UL length, presence of a subsequent trigger frame (e.g., More TF), whether CS (channel sensing) is required, UL BW (bandwidth), etc. Fig. 12 illustrates an example of an EHT variant common information field format.

The 4-bit trigger type subfield can have values from 0 to 15. Among them, the values 0, 1, 2, 3, 4, 5, 6, and 7 of the trigger type subfield are defined to correspond to basic, Beamforming Report Poll (BFRP), multi user-block acknowledgement request (MU-BAR), multi user-request to send (MU-RTS), Buffer Status Report Poll (BSRP), groupcast with retries (GCR), MU-BAR, Bandwidth Query Report Poll (BQRP), and NDP Feedback Report Poll (NFRP), respectively, and the values 8 to 15 are defined as reserved.

Among the common information, the trigger dependent common info subfield may include information that is optionally included based on the trigger type.

A special user info field may be included within the trigger frame. The special user info field does not contain user-specific information, but rather extended common information not provided in the common information field.

A user information list contains zero or more user information fields. Figure 12 illustrates an example of an EHT variant user information field format.

The AID12 subfield basically indicates that it is a user information field for an STA with the corresponding AID. In addition, if the AID12 field has a predetermined specific value, it may be utilized for other purposes, such as allocating a random access (RA)-RU, or being configured in the form of a special user information field. The special user information field is a user information field that does not contain user-specific information, but contains extended common information not provided in the common information field. For example, the special user information field can be identified by the AID12 value of 2007, and the special user information field flag subfield within the common information field can indicate whether the special user information field is included.

The RU allocation subfield can indicate the size and location of an RU/MRU. For this purpose, the RU allocation subfield can be interpreted together with the PS160 (primary/secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc.

For example, the mapping of B7-B1 of the RU Allocation subfield can be defined together with the settings of the B0 and PS160 subfields of the RU Allocation subfield as shown in Table 2 below. Table 2 shows an example of encoding of the PS160 subfield and the RU Allocation subfield of the EHT Variant User Information Field.

When B0 of the RU Allocation subfield is set to 0, it may indicate that the RU/MRU allocation is applied to the primary 80 MHz channel, and when its value is set to 1, it may indicate that the RU allocation is applied to the secondary 80 MHz channel of the primary 160 MHz. When B0 of the RU Allocation subfield is set to 0, it may indicate that the RU/MRU allocation is applied to the lower 80 MHz of the secondary 160 MHz, and when its value is set to 1, it may indicate that the RU allocation is applied to the upper 80 MHz of the secondary 160 MHz.

In the trigger frame RU allocation table of Table 2, the parameter N can be calculated based on the formula N=2*X1+X0. For a bandwidth of 80 MHz or less, the values of PS160, B0, X0, and X1 can be set to 0. For a bandwidth of 160 MHz and a bandwidth of 320 MHz, the values of PS160, B0, X0, and X1 can be set as shown in Table 3. These settings represent the absolute frequency order for the primary and secondary 80 MHz and 160 MHz channels. The order from left to right represents the order from low frequency to high frequency. The primary 80 MHz channel is represented as P80, the secondary 80 MHz channel is represented as S80, and the secondary 160 MHz channel is represented as S160.

UL/DL information and PPDU type information

The aforementioned U-SIG field may include a field for UL/DL flags and a field containing PPDU type information. Specifically, the field containing information about the PPDU type is defined as a 2-bit PPDU type and compression mode field.

In this case, the combination of the values of the UL/DL field and the PPDU type and compression mode fields can indicate information about the EHT PPDU format, whether EHT-SIG is present, whether RU allocation subfield is present, and the total number of user fields in MU PPDU or transmitters in TB PPDU.

For example, in case of DL OFDMA transmission using MU PPDU format, UL/DL field may be set to a value indicating DL (i.e., 0), and PPDU type and compression mode fields may be set to 0. For example, in case of DL single user (SU) transmission using MU PPDU format, UL/DL field may be set to a value indicating DL (i.e., 0), and PPDU type and compression mode fields may be set to 1. For example, in case of DL non-OFDMA MU-MIMO transmission using MU PPDU format, UL/DL field may be set to a value indicating DL (i.e., 0), and PPDU type and compression mode fields may be set to 2.

For example, in case of UL OFDMA or UL non-OFDMA transmission using TB PPDU format, the UL/DL field may be set to a value indicating UL (i.e., 1), and the PPDU type and compression mode fields may be set to 0. For example, in case of UL single user (SU) transmission using MU PPDU format, the UL/DL field may be set to a value indicating UL (i.e., 1), and the PPDU type and compression mode fields may be set to 1.

DRU-based single user (SU) transmission or reception

As mentioned above, to overcome PSD limitations and improve power gain, a DRU using distributed tones/subcarriers rather than an RRU using continuous tones/subcarriers can be applied.

This disclosure describes a single user (SU) transmission/reception based on a DRU. For example, this disclosure proposes a SU transmission/reception scheme using a DRU in an MU PPDU. More specifically, this disclosure describes a new scheme (hereinafter referred to as an SU DRU transmission/reception scheme) for performing SU transmission/reception by allocating a DRU to one STA (i.e., SU) in a PPDU supporting MU transmission/reception (e.g., MU PPDU and/or TB PPDU supporting UL/DL MU transmission), and various examples for supporting SU DRU transmission/reception.

PPDUs supporting conventional MU transmission (e.g., EHT MU PPDU as in the example of FIG. 7(e) or EHT TB PPDU as in the example of FIG. 7(f)) may support OFDMA transmission in which multiple STAs (or users) are allocated to multiple RUs/MRUs (e.g., RRUs/MRRUs as distinguished from DRUs/MDRUs). PPDUs supporting various MU transmissions (e.g., UHR MU PPDUs, UHR TB PPDUs, etc.) may also be defined in UHR or new/improved PHY versions to be discussed in the future. OFDMA transmission in which multiple STAs are allocated to multiple RUs/MRUs (e.g., DRUs/MDRUs and/or RRUs/MRRUs) may also be supported in UHR MU PPDUs and/or UHR TB PPDUs.

For example, a UHR MU PPDU may basically include fields in the following order: L-STF field, L-LTF field, L-SIG field, RL-SIG field, U-SIG field, UHR-SIG field, UHR-STF, UHR-LTF field, Data field, (PE field), similar to FIG. 7(e). Signaling information for transmission of a UHR MU PPDU may be included in the U-SIG and/or UHR-SIG fields within the UHR MU PPDU.

For example, a UHR TB PPDU may basically include fields in the following order: L-STF field, L-LTF field, L-SIG field, RL-SIG field, U-SIG field, UHR-STF, UHR-LTF field, Data field, (PE field), similar to Fig. 7(f). Signaling information for transmission of a UHR TB PPDU may be included in the common information field and/or the user information (list) field of the trigger frame in the PPDU preceding the UHR TB PPDU.

In the MU PPDU/TB PPDU of a future PHY version, a basic MU PPDU/TB PPDU format may be defined that includes SIG/STF/LTF fields with new names corresponding to the future PHY version instead of the fields indicated as UHR. In the following description, the terms UHR-SIG/UHR-STF/UHR-LTF fields are only exemplary and may be replaced by the SIG/STF/LTF fields with new names of the future PHY version. The SIG/STF/LTF fields corresponding to UHR or future PHY versions may also be referred to as non-legacy SIG/STF/LTF fields. New fields may be added to the basic format of the MU PPDU/TB PPDU, or some field(s) may be excluded from the basic format. In the basic format of these MU PPDU/TB PPDUs, the format of the U-SIG field and/or the non-legacy-SIG field may be the same as the format of the U-SIG field and/or the EHT-SIG field of the existing EHT MU PPDU, or some components may be changed or improved. In addition or alternatively, the format of the non-legacy-STF field and/or the non-legacy-LTF field in the basic format of the MU PPDU/TB PPDU may be the same as the format of the existing EHT-STF field and/or EHT-LTF field, or some components may be changed or improved.

When supporting DRU-based transmission/reception in MU PPDU/TB PPDU, multiple DRUs can be allocated to multiple STAs similar to RRUs to perform OFDMA transmission/reception. In this case, since there is a limit to obtaining power boosting gain, it is possible to consider performing SU transmission/reception in which one STA, rather than multiple STAs, is allocated to one DRU. Here, a transmission/reception method that supports DRU transmission/reception for one STA (i.e., a single user) based on a PPDU format that supports MU transmission (e.g., MU PPDU/TB PPDU) is called SU DRU transmission/reception.

According to examples of the present disclosure, MU PPDU/TB PPDU formats supporting SU DRU transmission/reception can be defined, and various examples of signaling for supporting SU DRU transmission/reception or related to SU DRU transmission/reception are described.

FIG. 13 is a diagram illustrating an example of the operation of the first STA according to the present disclosure.

In the examples of FIGS. 13 and 14, the first STA corresponds to an STA that performs SU DRU transmission, and may be an AP STA or a non-AP STA. Furthermore, in the examples of FIGS. 13 and 14, the second STA corresponds to an STA that performs SU DRU reception, and may be an AP STA or a non-AP STA. For example, SU DRU transmission may be performed by an AP STA to a non-AP STA, or may be performed by a non-AP STA to an AP STA.

In step S1310, the first STA may generate a PPDU including one or more signaling fields including information about SU transmission and DRU application, and a data field.

If one or more signaling fields indicate that this is a SU transmission and also indicate that a DRU applies, the data fields in the PPDU may be mapped onto the SU DRU.

In the present disclosure, information regarding SU transmission and DRU application may be signaled/indicated based on a single field or a combination of multiple fields (or multiple bits). For example, the information may be separately defined as first information related to SU transmission and second information related to DRU application, or may be defined as a single piece of information indicating that SU transmission is performed while DRU is applied.

For example, first information (or first field) related to SU transmission and second information (or second field) related to DRU application may be defined separately (or independently). If the first information/field indicates SU transmission and the second information/field indicates DRU application, SU DRU transmission may be applied and the data field may be mapped onto the SU DRU. Various examples of information/fields indicating other SU transmissions and/or DRU application are described below.

SU DRU allocation information may or may not be present (or included) in the PPDU. For example, one or more signaling fields may include allocation information indicating which DRUs are to be allocated as SU DRUs. Various examples of information regarding DRU allocation in the present disclosure are described below.

Alternatively, if the DRUs to be allocated as SU DRUs are predefined (or fixed as one DRU), one or more signaling fields may not include RU allocation information. For example, depending on the bandwidth (e.g., distributed bandwidth (DBW)) size of the channel to which the DRU is applied, one DRU (e.g., the largest available DRU) may be predefined as the SU DRU. For example, DBW may be 20 MHz, 40 MHz, 60 MHz, 80 MHz, etc.

For example, the maximum size of a DBW supporting SU DRU transmission can be set/defined to a specific bandwidth. For example, the maximum size of a DBW supporting SU DRU transmission can be set/defined to 80 MHz.

SU DRU transmission can be performed when puncturing is applied or not applied. If puncturing is applied and SU DRU transmission is applied are linked (e.g., SU DRU transmission is not applied when puncturing is applied, and SU DRU transmission is applied when puncturing is not applied), if information about SU DRU application is included in one or more signaling fields, puncturing-related information may not be included or may be set to a value indicating that puncturing is not applied. If SU DRU is supported even when puncturing is applied, puncturing-related information may be included in one or more signaling fields. For example, if a 20MHz channel is punctured in an 80MHz bandwidth, a PPDU including a data field mapped to an SU DRU in a 60MHz DBW may be transmitted.

Transmission of a PPDU may be an UL transmission (e.g., from a non-AP STA to an AP STA) or a DL transmission (e.g., from an AP STA to a non-AP STA). Information indicating such UL/DL may be included in one or more signaling fields of the PPDU.

One or more signaling fields may include a U-SIG. One or more signaling fields may further include a non-legacy-SIG (e.g., UHR-SIG).

The generated PPDU can be configured according to the MU PPDU format (e.g., UHR MU PPDU).

In step S1320, the first STA can transmit the generated PPDU to the second STA.

The method described in the example of FIG. 13 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may be configured to generate a PPDU including one or more signaling fields and data fields including information about SU transmission and DRU application, and to transmit the generated PPDU to the second device (200) via one or more transceivers (106). Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 13 or the examples described below when executed by one or more processors (102).

FIG. 14 is a diagram illustrating an example of the operation of a second STA according to the present disclosure.

In step S1410, the second STA may receive a PPDU including one or more signaling fields including information related to SU transmission and DRU application, and a data field, from the first STA.

In step S1420, the second STA may decode a data field mapped on the SU DRU based on one or more signaling fields of the received PPDU indicating SU transmission and DRU application.

In the example of Fig. 14, one or more signaling fields including information related to SU transmission and/or information related to DRU application, and the contents of the PPDU supporting SU DRU are the same as in the example of Fig. 13, so redundant description is omitted.

The method described in the example of FIG. 14 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may be configured to receive, from the first device (100) via one or more transceivers (206), a PPDU including one or more signaling fields including information related to SU transmission and DRU application, and a data field, and to decode the data field mapped on the SU DRU based on the one or more signaling fields indicating SU transmission and DRU application. Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 14 or the examples described below when executed by one or more processors (202).

In the examples of FIGS. 13 and 14, a transmitting STA corresponding to the first STA (non-AP STA or AP STA) can obtain information about a tone plan and a DRU/RRU. In the case of a non-AP STA, this information can be obtained through a trigger frame, etc., and in the case of an AP STA, this information can be obtained from a higher layer. The information about the tone plan can include the size and location of the DRU/RRU, signaling information related to the DRU/RRU, information about a frequency band in which the DRU/RRU is included, information about an STA that transmits and receives the DRU/RRU, etc. The transmitting STA can configure/generate a PPDU based on the obtained information. The step of configuring/generating the PPDU can include the step of configuring/generating each field of the PPDU. For example, the transmitting STA can configure/generate a U-SIG and/or UHR-SIG (e.g., UHR-SIG-A/B) field that includes/is based on information about the tone plan. For example, a transmitting STA may configure/generate a field including signaling information indicating a bandwidth of a PPDU, and/or a field including signaling information indicating a size/location of a DRU/RRU (e.g., an N bitmap), and/or a field including an identifier of an STA receiving the DRU/RRU (e.g., an AID). A TB PPDU transmitted by a Non-AP STA may include some of the signaling information described above. A transmitting STA may also generate an STF/LTF sequence to be transmitted through a specific DRU/RRU. Such an STF/LTF sequence may be generated based on a preset STF generation sequence/LTF generation sequence. A transmitting STA may also generate a data field (i.e., an MPDU) to be transmitted through a specific DRU/RRU. A transmitting STA may transmit a PPDU including fields configured/generated in this manner to a receiving STA. PPDU transmission operations can perform operations such as CSD (cyclic shift diversity), spatial mapping, IDFT (inverse discrete Fourier transform)/IFFT (inverse fast Fourier transform), and GI insertion.

For example, in the examples of FIGS. 13 and 14, a receiving STA (non-AP STA or AP STA) corresponding to the second STA can receive a PPDU configured/generated by a transmitting STA as described above. The receiving STA can receive part or all of the PPDU and restore the original symbol/data/signal from the results of CSD, spatial mapping, IDFT/IFFT, and GI insertion. The receiving STA can decode part or all of the PPDU and obtain signaling information related to a tone plan (e.g., information related to DRU/RRU) from the decoding result. For example, the receiving STA can decode L-SIG and U-SIG of the PPDU based on L-STF/L-LTF and obtain information included in the L-SIG and U-SIG fields. Signaling information for various tone plans of the present disclosure (e.g., information for DRU/RRU) may be included in U-SIG/UHR-SIG (e.g., UHR-SIG-A/B). Accordingly, a receiving STA may obtain information about a tone plan based on the information included in U-SIG/UHR-SIG. If the receiving STA receives the TB PPDU as an AP STA, it may already know some/all of the signaling information about the tone plan. The receiving STA may decode the remaining portion of the PPDU based on the obtained information about the tone plan. For example, the receiving STA may decode the STF/LTF field (e.g., UHR-STF/UHR-LTF) of the PPDU and decode the data field to obtain an MPDU based on the information about the tone plan. The receiving STA may also forward the decoded data to a higher layer (e.g., MAC layer). In addition, when the generation of a signal is instructed from the upper layer to the PHY layer in response to data transmitted to the upper layer, the receiving STA can perform subsequent operations such as signal generation accordingly.

The examples of FIGS. 13 and 14 may correspond to some of the various examples of the present disclosure. Below, various examples of the present disclosure, including the examples of FIGS. 13 and 14, will be described in more detail.

Example 1

This embodiment relates to a method for indicating information about puncturing in relation to SU DRU transmission.

Basically, SU DRU transmission can be performed on both punctured and non-punctured channels.

If a DRU tone plan is defined for a channel to which puncturing is applied, SU DRU transmission may be performed for the punctured channel. For example, SU DRU transmission may be supported on a 60MHz channel with 20MHz puncturing applied among 80MHz channels.

It can be assumed that a DRU tone plan is not defined for a channel to which puncturing is applied. For example, if puncturing is applied to MU PPDU transmission in a specific bandwidth transmission, additional DRU tone plans may not be defined. For example, in a DRU transmission in an 80MHz MU PPDU, if one 20MHz channel is punctured, the unpunctured 60MHz DRU tone plan may not be applied, and the 20MHz DRU tone plan and the 40MHz DRU tone plan may be applied. Therefore, the MU PPDU for SU DRU transmission may not be punctured, and a higher power gain can be expected. Accordingly, SU DRU transmission may be limited to being performed in MU PPDUs to which puncturing is not applied.

Example 2

This embodiment relates to a method for indicating a PPDU type in relation to SU DRU transmission.

Referring to Table 4 described above, various PPDU types can be indicated depending on the combination of the UL/DL field and the PPDU type and compression mode fields in the U-SIG field in the EHT MU PPDU.

To indicate SU DRU transmission, a value defined as reserved or validated among the combinations of the UL/DL field and the PPDU type and compression mode field can be used. For example, if the UL/DL field indicates DL (value 0) and the PPDU type and compression mode field has a value of 3, or if the UL/DL field indicates UL (value 1) and the PPDU type and compression mode field has a value of 2 or 3, SU DRU transmission can be defined as being indicated.

Alternatively, if a combination of values indicates a description different from the existing description (e.g., a combination of the states of the PPDU format, the presence of non-legacy-SIG, the presence of RU allocation subfield, and the total number of user fields/transmitters) for a specific combination of values, or if the bit size of the field(s) is different, a value other than 3 in the DL case or 2 or 3 in the UL case may indicate SU DRU transmission. For example, DL SU DRU transmission may be newly defined as a state distinct from the existing DL MU PPDU-based DL OFDMA (including MU-MIMO transmission or non-MU-MIMO transmission), DL SU transmission, DL NDP transmission, and DL non-OFDMA MU-MIMO transmission. For example, UL SU DRU transmission can be newly defined as a state that is distinct from existing UL MU PPDU-based UL SU transmission or UL NDP transmission, or UL TB PPDU-based UL OFDMA transmission or UL non-OFDMA transmission (including MU-MIMO transmission or non-MU-MIMO transmission).

Alternatively, SU DRU transmission may be indicated in combination with the UL/DL field by a field other than the PPDU type and compression mode fields (e.g., if the PPDU type is indicated by a new field). Alternatively, SU DRU transmission may be indicated by a separate field indicating SU DRU transmission.

If the application of SU DRU transmission is limited to cases where puncturing is not applied, the receiving STA may determine that puncturing is not applied if it confirms that SU DRU transmission is applied. Accordingly, puncturing indication information may not be necessary when SU DRU transmission is indicated. For example, the punctured channel information field (or puncturing-related information of another name) in the U-SIG of the PPDU may be reserved, set to validate, set to disregard, or used for purposes/uses other than puncturing-related information.

For example, if the information about the PPDU type indicates DL OFDMA (e.g., in the case of DL, the values of the PPDU Type and Compression Mode fields indicate OFDMA transmission (e.g., 0 or another value if a field state other than Table 4 is defined)), or UL/DL SU transmission (e.g., in the case of UL and in the case of DL, the values of the PPDU Type and Compression Mode fields indicate SU transmission (e.g., 1 or another value if a field state other than Table 4 is defined)), the puncturing-related information (e.g., the punctured channel information field) may indicate that puncturing is not applied. Here, the puncturing indication method may be defined/applied in different ways for the PPDU types (e.g., SU transmission and OFDMA transmission).

Additionally or alternatively, to indicate SU DRU transmission, separate indication information (or field) for whether DRU is applied may be newly defined. If the PPDU type is indicated as SU transmission, and the DRU application field (e.g., a 1-bit field) indicates DRU application, SU DRU transmission may be indicated. In this case, whether SU transmission is applied may be indicated by PPDU type-related information (e.g., PPDU type and compression mode fields), and whether DRU is applied may be indicated by a new field.

If the application of SU DRU transmission is limited to cases where puncturing is not applied, and DRU application is indicated while SU transmission is indicated, puncturing indication information may not be required. For example, the punctured channel information field (or other name of puncturing-related information) in the U-SIG of the PPDU may be reserved, or set to validate, or set to disregard, or may be used for purposes/uses other than puncturing-related information.

Additionally or alternatively, SU DRU transmission may be indicated by indicating that DRU is to be applied to the entire bandwidth for DL OFDMA.

Example 3

This embodiment relates to a method for directing DRU allocation in relation to SU DRU transmission.

DRU allocation information may be required to indicate which DRU is used for SU DRU transmission. For this purpose, the RU allocation subfield included in a non-legacy-SIG field, such as the UHR-SIG field similar to the legacy EHT-SIG, may be used, or the RU allocation subfield included in the trigger frame may be used.

When signaling DRU allocation information, it may be considered that, fundamentally, RUs of a size (or number of tones) corresponding to the entire bandwidth cannot be used in DRU transmission (e.g., 242-tone DRU is not defined in 20 MHz bandwidth, 484-tone DRU is not defined in 40 MHz bandwidth, and 996-tone DRU is not defined in 80 MHz bandwidth), and this also applies to SU DRUs. It may also be considered that the smaller the size of the DRU used, the greater the power gain.

Example 3-1

The RU allocation subfield included in the non-legacy-SIG field (e.g., the UHR-SIG field) can indicate the RU configuration/structure in units of 20 MHz, and there can be a user field corresponding to each indicated RU. In the case of SU DRU, since only one RU is actually used, it is necessary to indicate which RU is used or not, and since there are user fields corresponding to the corresponding RUs, the overhead may be large. In this case, resource efficiency may be low because unused signaling information is transmitted, but since the same format as the PPDU format for DL OFDMA (in particular, the format of the U-SIG field and/or the UHR-SIG field) can be used, the STA implementation complexity can be reduced because a separate PPDU format is not defined for SU DRU. The structure of the RU allocation subfield described above can be used in the same way even when the SU DRU transmission instruction method in the examples described above, or the SU transmission instruction and DRU application instruction method are applied (i.e., when a new PPDU format is defined for this).

In this case, the STA-ID subfield in the user field corresponding to the RU used for SU DRU transmission may be set to the ID value of the STA actually assigned to the corresponding RU (i.e., SU DRU). Other subfields in the user field including the STA-ID subfield set to the actually assigned value may indicate information related to the SU DRU transmission.

The STA-ID subfield within the user field corresponding to a RU that is not used for SU DRU transmission may be set to a value indicating unassigned (or unused) (e.g., 2046). Other subfields within the user field that include the STA-ID subfield set to a value indicating unassigned may be reserved or used for other purposes/uses.

The examples of the RU allocation subfield (and user field) of the non-legacy-SIG field related to the SU DRU transmission described above can also be applied to the method of indicating SU DRU transmission, or the method of indicating SU transmission and DRU application, or the method of indicating that DRU is applied to the entire bandwidth for DL OFDMA (e.g., when no puncturing is applied).

Example 3-2

The RU allocated for SU DRU transmission in the MU PPDU may also be indicated in a manner similar to the RU allocation subfield included in the user information list of the trigger frame (see the example of FIG. 12). For this purpose, the RU allocation subfield included in the MU PPDU may be newly defined. The newly defined RU allocation subfield is distinct from the RU allocation subfield in the EHT/UHR-SIG field of Example 3-1, and may be defined in a manner similar to the RU allocation subfield in the trigger frame.

The newly defined RU allocation subfield may be included in a common field within a U-SIG or a non-legacy-SIG (e.g., UHR-SIG). In this case, one user field (or user information field) may exist within the non-legacy-SIG (e.g., UHR-SIG). For example, since there is no user (information) field for STAs other than the one STA performing the SU DRU transmission, the example of the present embodiment may have lower overhead than the example of the aforementioned embodiment 3-1.

The newly defined RU allocation subfield can directly indicate the DRU (i.e., SU DRU) allocated for SU DRU transmission. The user (information) field includes information indicating the ID of the STA allocated to the SU DRU, and may further include other information required for SU DRU transmission.

The examples of RU allocation subfields (and user (information) fields) related to the SU DRU transmission described above may be applied to the SU DRU transmission instruction method, or the SU transmission instruction and DRU application instruction method, and may not be applied to the instruction method that DRU is applied to the entire bandwidth for DL OFDMA (e.g., when no puncturing is applied).

Example 3-3

In the existing PPDU type indication (e.g., see Table 4), TB PPDU-based UL OFDMA transmission is defined, but MU PPDU-based UL OFDMA transmission is not defined. In the present disclosure, MU PPDU-based UL OFDMA transmission can be newly defined with respect to SU DRU transmission. For example, MU PPDU-based UL OFDMA transmission can be indicated by using the UL/DL field indicating UL (e.g., 1) and the currently reserved value (e.g., 2 or 3) of the PPDU type and compression mode fields. Alternatively, similar to the DL OFDMA indication, MU PPDU-based UL OFDMA is newly defined as being indicated when the UL/DL field indicates UL (e.g., 1) and the PPDU type and compression mode fields indicate a value of 0. In this case, TB PPDU-based UL OFDMA or UL non-OFDMA can also be defined by changing it to be indicated by another value (e.g., 2 or 3). Alternatively, in the PPDU type, UL OFDMA may be indicated without distinguishing between MU PPDU and TB PPDU, and TB PPDU and MU PPDU may be distinguished through a specific field or in a specific manner. In addition, even if the sizes of the existing UL/DL fields and PPDU type and compression mode fields are changed, or the state indicated by a specific value is changed, a specific value of the PPDU type field may be defined as indicating MU PPDU-based UL OFDMA transmission.

In this case, similar to how SU DRU transmission is indicated by indicating that DRU is applied to the entire bandwidth for MU PPDU-based DL OFDMA, SU DRU transmission can be indicated by indicating that DRU is applied to the entire bandwidth for MU PPDU-based UL OFDMA. Unlike in the case of DL, it can be assumed that SU DRU transmission is always allocated to only one STA in the case of UL. Therefore, the indication that DRU is applied to the entire bandwidth in UL OFDMA with or without PPDU type indication can be defined in the same way as the indication method for SU DRU transmission. Alternatively, the indication that DRU is applied to the entire bandwidth in UL OFDMA with or without PPDU type indication can be defined in the same way as the SU transmission indication and DRU application indication methods.

Example 3-4

When DL non-OFDMA MU-MIMO is indicated, DL SU DRU transmission may be implicitly indicated when additional DRU application is indicated.

An indication of DL non-OFDMA MU-MIMO may correspond to, for example, the case where the UL/DL field in Table 4 indicates DL(0) and the values of the PPDU Type and Compression Mode fields are set to 2, but is not limited to these examples and may also include cases where DL non-OFDMA MU-MIMO is indicated even when the size of the corresponding field is different or a different state is mapped to the value of the field.

Information indicating whether DRU is applied can be defined as a 1-bit field. In this case, other signaling information and signaling methods, excluding information about the PPDU type, can be defined in the same way as the SU transmission indication and DRU application indication methods.

In the case of UL, if additional DRU application is indicated along with a specific transmission method (e.g., UL non-OFDMA MU-MIMO), UL SU DRU transmission may be implicitly indicated. In this case, other signaling information and signaling methods, excluding information about the PPDU type, may be defined in the same way as the SU transmission indication and DRU application indication methods. Alternatively, a UL-specific transmission method that includes or does not include a PPDU type indication and additional DRU application is indicated may be defined in the same way as the indication method for SU DRU transmission.

Example 3-5

The DRU used for SU DRU transmission may be fixed. For example, the DRU used for SU DRU transmission (i.e., SU DRU) may be predefined as one of the candidate DRU(s). In this case, RU allocation information for the SU DRU may not be required.

For example, a fixed DRU to be used as an SU DRU may correspond to the DRU with the largest size (or the largest number of tones) available in the bandwidth (e.g., distributed bandwidth (DBW), which is the bandwidth of the channel to which the DRU is applied). For example, a 106-tone DRU may be predefined as an SU DRU at 20 MHz, and a 242-tone DRU may be predefined as an SU DRU at 40 MHz. For example, a 484-tone DRU may be predefined as an SU DRU at 80 MHz. Alternatively, considering that power gain decreases as the DRU size increases, a 242-tone DRU may also be defined as an SU DRU at 40 MHz or higher (e.g., 60 MHz or 80 MHz).

Alternatively, if the PPDU type of DL OFDMA is indicated, it is defined as a format that includes an RU allocation subfield (see Table 4), so the RU allocation subfield may be included in the PPDU but may not be used. In the case of SU DRU transmission, since a predefined (fixed) SU DRU is used, it can be defined as a format that does not include an RU allocation subfield, and overhead can be reduced.

Unlike existing wireless LAN systems that only support RRUs, when supporting DRUs, a new signaling method may be defined to apply SU DRU transmission for purposes such as maximizing power gain. For example, when an MU PPDU is defined as an SU transmission and does not include RU allocation information, the DRU to be used when SU DRU transmission is applied is predefined, so that SU DRU can be performed accurately and efficiently without the signaling overhead of RU allocation. In addition, various examples for reducing signaling overhead for SU DRUs may be provided by the present disclosure even when an MU PPDU includes RU allocation information.

The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and/or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on/in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and/or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments/containers.

The method proposed in this disclosure is described with a focus on examples applied to IEEE 802.11-based systems, but can be applied to various wireless LANs or wireless communication systems in addition to IEEE 802.11-based systems.

Claims (19)

A step of generating, by a first station (STA), a physical layer protocol data unit (PPDU) including one or more signaling fields including first information related to single user (SU) transmission and second information related to application of a distributed resource unit (DRU), and a data field; and comprising a step of transmitting the PPDU to the second STA by the first STA, A method in which a data field in the PPDU is mapped onto the SU DRU based on the first information indicating the SU transmission and the second information indicating the application of the DRU. In the first paragraph, The above SU DRU is a method in which a specific DRU is predefined among a plurality of DRU candidates. In the second paragraph, A method wherein said particular DRU corresponds to one DRU of the largest size in a channel containing said DRU. In the third paragraph, A method wherein the distributed bandwidth (DBW) of the channel including the DRU is one of 20 MHz, 40 MHz, 60 MHz, or 80 MHz. In the third paragraph, A method in which puncturing is applied to a channel including the above DRU. In the first paragraph, A method wherein RU allocation information for the SU DRU is not present in one or more of the signaling fields. In the first paragraph, A method wherein the first information is indicated by a field related to a PPDU type within the one or more signaling fields. In paragraph 7, Method wherein the fields related to the above PPDU type are PPDU type and compression mode fields. In the first paragraph, A method wherein the one or more signaling fields further include a field indicating downlink (DL). In the first paragraph, A method wherein the one or more signaling fields further include a field indicating uplink (UL). In the first paragraph, A method wherein the one or more signaling fields include one or more of a U-SIG (universal-signal) field or a non-legacy SIG field. In the first paragraph, A method wherein the above PPDU has a multi-user (MU) PPDU format. In the first paragraph, A method wherein the first STA is an AP (access point) STA and the second STA is a non-AP STA. In the first paragraph, A method wherein the first STA is a non-AP STA and the second STA is an AP STA. one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: A first station (STA) generates a physical layer protocol data unit (PPDU) including one or more signaling fields including first information related to single user (SU) transmission and second information related to application of a distributed resource unit (DRU), and a data field; and The PPDU is set to be transmitted from the first STA to the second STA through the one or more transceivers, A device wherein a data field in the PPDU is mapped onto the SU DRU based on the first information indicating the SU transmission and the second information indicating the application of the DRU. A step of receiving, by a second station (STA), from a first STA, a physical layer protocol data unit (PPDU) including one or more signaling fields including first information related to single user (SU) transmission and second information related to application of a distributed resource unit (DRU), and a data field; and A method comprising a step of decoding, by the second STA, the data field mapped on the SU DRU in the PPDU based on the first information indicating the transmission of the SU and the second information indicating the application of the DRU. one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: A physical layer protocol data unit (PPDU) including one or more signaling fields including first information related to single user (SU) transmission and second information related to application of distributed resource units (DRUs), and a data field, is received by a second station (STA) from a first STA through one or more transceivers; and A device configured to decode, at the second STA, the data field mapped on the SU DRU in the PPDU based on the first information indicating the SU transmission and the second information indicating the application of the DRU. one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 14 based on execution by said one or more processors. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the performance of a method according to any one of claims 1 to 14.