Method and apparatus for PPDU-based transmission or reception in wireless LAN system

Abstract

A method and an apparatus for PPDU-based transmission or reception in a wireless LAN system are disclosed. The method performed by a first station (STA) in a wireless LAN system, according to one embodiment of the present disclosure, may comprise the steps of: receiving, from a second STA, a trigger frame including resource allocation information for transmission of a TB PPDU for a bandwidth greater than or equal to 80 MHz; and transmitting the TB PPDU to the second STA in a DRU or an RU on the basis of the resource allocation information. Here, DRU-based transmission or RU-based transmission can be applied to the TB PPDU on the basis of an 80 MHz channel unit. At this time, the first STA can be allocated, on the basis of a first STA being allocated to a specific 80 MHz channel to which the DRU-based transmission is applied, to at least one from among a first type DRU in which tones are distributed over an 80 MHz channel, a second type DRU in which tones are distributed over a 40 MHz channel, and a third type DRU in which tones are distributed over a 20 MHz channel.

Description

PPDU-based transmission or reception method and device in a wireless LAN system

[0001] The present disclosure relates to a method and device for transmitting and receiving a PPDU based on application of distributed resource units and / or general resource units in a wireless local area network (WLAN) system.

[0002] 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.

[0003] 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.

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving a PPDU based on application of distributed resource units and / or general resource units in a wireless local area network (WLAN) system.

[0005] 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 will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0006] A method performed by a first station (STA) in a wireless local area network (WLAN) system according to one aspect of the present disclosure may include: receiving, from a second STA, a trigger frame including resource allocation information for transmission of a trigger-based physical layer protocol data unit (TB PPDU) for a bandwidth greater than or equal to 80 MHz; and transmitting, to the second STA, the TB PPDU in a distributed resource unit (DRU) or resource unit (RU) based on the resource allocation information. Here, DRU-based transmission or RU-based transmission may be applied to the TB PPDU based on an 80 MHz channel unit. At this time, based on the first STA being assigned within a specific 80MHz channel to which the DRU-based transmission is applied, the first STA may be assigned to at least one of a first type DRU with tones distributed over an 80MHz channel, a second type DRU with tones distributed over a 40MHz channel, or a third type DRU with tones distributed over a 20MHz channel.

[0007] A method performed by a second station (STA) in a wireless local area network (WLAN) system according to an additional aspect of the present disclosure may include: transmitting, to a first STA, a trigger frame including resource allocation information for transmission of a trigger-based physical layer protocol data unit (TB PPDU) for a bandwidth greater than or equal to 80 MHz; and receiving the TB PPDU from the first STA in a distributed resource unit (DRU) or resource unit (RU) based on the resource allocation information. Here, for the TB PPDU, DRU-based transmission or RU-based transmission may be applied based on an 80 MHz channel unit. In this case, based on the first STA being assigned to a specific 80 MHz channel to which the DRU-based transmission is applied, the first STA may be assigned to at least one of a first type DRU in which tones are distributed on an 80 MHz channel, a second type DRU in which tones are distributed on a 40 MHz channel, or a third type DRU in which tones are distributed on a 20 MHz channel.

[0008] According to the present disclosure, a method and device for transmitting and receiving a PPDU based on application of a distributed resource unit and / or a general resource unit in a wireless local area network (WLAN) system can be provided.

[0009] 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.

[0010] 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.

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

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

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

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

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

[0016] 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.

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

[0018] 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.

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

[0020] FIG. 12 illustrates the operation of a first STA for a PPDU transmission and reception method according to an embodiment of the present disclosure.

[0021] FIG. 13 illustrates the operation of a second STA for a PPDU transmission and reception method according to an embodiment of the present disclosure.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

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

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

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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).

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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) can 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 user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0040] 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.

[0041] 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.

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

[0043] 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.

[0044] 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.

[0045] 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).

[0046] 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.

[0047] 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.

[0048] 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).

[0049] 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.

[0050] 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.

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

[0052] 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.

[0053] 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.

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

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

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

[0068] 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.

[0069] 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).

[0070] Referring to Fig. 4, an operation based on a random backoff period is described. When a medium that was occupied / busy changes to an idle state, multiple STAs can attempt to transmit data (or frames). To minimize collisions, each STA can 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 can 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 given an initial value of CWmin, but can take a value doubled in case of transmission failure (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, data transmission can 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. The CW, CWmin, and CWmax values ​​are 2. n It is desirable to set it to -1 (n=0, 1, 2, ...).

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

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

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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).

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

[0094] 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)).

[0095] 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).

[0096] 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)).

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.).

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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.).

[0114] 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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.

[0123] Resource Unit

[0124] 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.

[0125] 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.

[0126] 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.

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

[0128] 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.

[0129] 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.

[0130] 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.

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

[0132] 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.

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

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

[0135] 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.

[0136] 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.

[0137] 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.

[0138] 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.

[0139] 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.

[0140] 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.

[0141] 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.

[0142] Distributed resource units

[0143] 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.

[0144] 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.

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

[0146] 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).

[0147] 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 increases the transmit power by approximately 11 dB for a 52-tone RU. This increased transmit power allows for a higher MCS and longer range.

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

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 20MHz bandwidth 40MHz bandwidth 80MHz bandwidth 26-tone RU8.1311.1411.1452-tone RU6.378.1311.14106-tone RU3.366.378.13242-tone RU Not applicable 2.695.12484-tone RU Not applicable Not applicable 2.69

[0153] PPDU transmission and reception method applied by DRU and / or RRU

[0154] As mentioned above, in order to overcome PSD limitations and improve power gain, a DRU using distributed tones / subcarriers may be applied instead of an RRU (or RU, considering the distinction from DRU) using continuous tones / subcarriers.

[0155] In this disclosure, a specific method for defining the structure and configuration of a PPDU in hybrid mode, in which DRUs and RRUs are simultaneously allocated and transmitted, is proposed. For example, in a PPDU transmission and reception situation of a bandwidth of 40MHz / 80MHz / 160MHz / 320MHz or higher, a PPDU in hybrid mode can be transmitted and received, in which a DRU is applied to a specific channel for transmission, and an RRU, a conventional RU, is applied to another specific channel for transmission. In particular, when applying a DRU to a specific channel, the method / structure for applying the DRU is specifically described.

[0156] In addition, in the present disclosure, in a PPDU transmission situation having a bandwidth greater than or equal to 80 MHz, a specific method of operating the channel by considering the distribution bandwidth (dBW) when DRU is applied to a specific channel (e.g., a specific 80 MHz channel, a specific 40 MHz channel) within the PPDU is proposed.

[0157] FIG. 12 and FIG. 13 illustrate a PPDU transmission and reception method according to the present disclosure.

[0158] For example, in transmitting and receiving a TB PPDU based on a trigger frame, the transmitting device may be a non-AP STA, and the receiving device may be an AP. For convenience of explanation below, the transmitting device may be referred to as a first STA, and the receiving device may be referred to as a second STA.

[0159] In this disclosure, transmission and reception of TB PPDU is described as a representative example for clarity of explanation, but it is not limited thereto, and the proposed method of this disclosure can be extended and applied to other PPDU types.

[0160] FIG. 12 illustrates the operation of a first STA for a PPDU transmission and reception method according to one embodiment of the present disclosure.

[0161] Figure 12 illustrates the operation of a transmitter based on the proposed methods described below. The example in Figure 12 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 12 may be omitted depending on the circumstances and / or settings.

[0162] Referring to FIG. 12, a first STA receives a trigger frame including resource allocation information for transmission of a TB PPDU for a bandwidth greater than or equal to 80 MHz from a second STA (S1210).

[0163] The first STA can construct a PPDU, i.e., a TB PPDU, based on the received trigger frame.

[0164] The TB PPDU may be a PPDU to which either a DRU or an RRU is allocated, or may be a PPDU in hybrid mode to which both DRUs and / or RUs can be allocated simultaneously. For example, the TB PPDU may be configured with a bandwidth that includes one or more channels to which either a DRU tone plan or an RU tone plan is applicable.

[0165] In this regard, for the TB PPDU in question, either DRU-based transmission or RU-based transmission may be applied based on 80MHz channel units. Here, DRU-based transmission may correspond to transmission using DRUs composed of non-contiguous tones, and RU-based transmission may correspond to transmission using RUs composed of contiguous tones.

[0166] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0167] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0168] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0169] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0170] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0171] The above-described STF-part may contain an STF sequence.

[0172] The above-described LTF portion may include a training field (i.e., an LTF sequence) for channel estimation.

[0173] The data-part described above may include user data and may include packets for upper layers.

[0174] A transmitting device (i.e., a first STA) may configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, the step may include a step of configuring one or more fields including control information regarding a tone plan (e.g., a DRU tone plan, a RU tone plan). For example, the step may include a step of configuring a signal field (x-SIG field) including control information regarding a tone plan. That is, the step may include a step of configuring a field including control information indicating a size / position of a DRU / RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the DRU / RU.

[0175] Additionally, the step may include generating an STF / LTF sequence to be transmitted via a specific RU or MRU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0176] Thereafter, the first STA transmits a TB PPDU to the second STA from the DRU or RU to which it is assigned based on the resource allocation information (S1220).

[0177] Here, the transmitting device (i.e., the first STA) may perform at least one of operations such as cyclic shift diversity (CSD), spatial mapping, inverse discrete Fourier transform (IDFT) / inverse fast Fourier transform (IFFT) operation, and guard interval (GI) insertion for the S1220 operation.

[0178] In this regard, for a PPDU having a bandwidth greater than or equal to 80 MHz, if a first STA is allocated within a specific 80 MHz channel to which the aforementioned DRU-based transmission applies, the first STA may be allocated within the specific 80 MHz channel to at least one of a first type DRU in which tones are distributed over an 80 MHz channel, a second type DRU in which tones are distributed over a 40 MHz channel, or a third type DRU in which tones are distributed over a 20 MHz channel. Here, the first type DRU refers to a type of DRU applicable to an 80 MHz distributed channel (80 MHz dBW), i.e., a case where tones are distributed over the entire 80 MHz channel, the second type DRU refers to a type of DRU applicable to a 40 MHz distributed channel (40 MHz dBW), i.e., a case where tones are distributed over the entire 40 MHz channel, and the third type DRU refers to a type of DRU applicable to a 20 MHz distributed channel (20 MHz dBW), i.e., a case where tones are distributed over the entire 20 MHz channel.

[0179] According to an embodiment of the present disclosure, a particular 80 MHz channel may be based on any one of a first type distributed channel configured to be applicable to one type 1 DRU, a second type distributed channel configured to be applicable to one type 2 DRU and two type 3 DRUs, a third type distributed channel configured to be applicable to two type 2 DRUs, or a fourth type distributed channel configured to be applicable to four type 3 DRUs. In this regard, the particular 80 MHz channel may be a non-punctured 80 MHz channel. Furthermore, in this case, the trigger frame may include information indicating a type / mode of a distributed channel for the particular 80 MHz channel (e.g., one of the first type distributed channel, the second type distributed channel, the third type distributed channel, and / or the first type distributed channel).

[0180] For example, the first type distributed channel may correspond to an 80MHz dBW type / mode, the second type distributed channel may correspond to a 20MHz+20MHz+40MHz dBW type / mode or a 40MHz+20MHz+20MHz dBW type / mode, the third type distributed channel may correspond to a 40MHz+40MHz dBW type / mode, and the fourth type distributed channel may correspond to a 20MHz+20MHz+20MHz+20MHz dBW type / mode.

[0181] According to an embodiment of the present disclosure, when 20MHz puncturing is applied to a specific 80MHz channel, the specific 80MHz channel may be based on either a type 5 distributed channel configured to be applicable to one type 2 DRU and one type 3 DRU, or a type 6 distributed channel configured to be applicable to three type 3 DRUs. In this case, the trigger frame may include information indicating a type / mode of a distributed channel (e.g., one of the type 5 distributed channel and / or the type 6 distributed channel) for the specific 80MHz channel to which 20MHz puncturing is applied.

[0182] For example, the Type 5 distributed channel may correspond to a 20MHz+40MHz dBW type / mode or a 40MHz+20MHz dBW type / mode, and the Type 6 distributed channel may correspond to a 20MHz+20MHz+20MHz dBW type / mode.

[0183] According to an embodiment of the present disclosure, when 40MHz puncturing is applied to a specific 80MHz channel, the specific 80MHz channel may be based on either a Type 7 distributed channel configured to be applicable to one Type 2 DRU or a Type 8 distributed channel configured to be applicable to two Type 3 DRUs. In this case, the trigger frame may include information indicating a type / mode of a distributed channel (e.g., one of the Type 7 distributed channel and / or the Type 8 distributed channel) for the specific 80MHz channel to which 40MHz puncturing is applied.

[0184] For example, a Type 7 distributed channel may correspond to a 40MHz dBW type / mode, and a Type 8 distributed channel may correspond to a 20MHz+20MHz dBW type / mode.

[0185] According to an embodiment of the present disclosure, when the bandwidth of a PPDU is 80 MHz, DR)-based transmission or RU-based transmission may be applied based on a 40 MHz channel unit. In this regard, when the aforementioned DRU-based transmission is allocated to a specific 40 MHz channel belonging to a PPDU of an 80 MHz bandwidth, the specific 40 MHz channel may be based on either a Type 9 distributed channel (e.g., 40 MHz dBW) configured to allow one Type 2 DRU to be applied, or a Type 10 distributed channel (e.g., 20 MHz+20 MHz dBW) configured to allow two Type 3 DRUs to be applied. If 20 MHz puncturing is applied to a specific 40 MHz channel, the Type 3 DRU may be applied to a non-punctured 20 MHz channel within the specific 40 MHz. For example, for an 80MHz bandwidth, if a first STA is assigned within a specific 40MHz channel to which DRU-based transmission is applied, and 20MHz puncturing is applied to the specific 40MHz channel, the first STA may be assigned to a DRU whose tones are distributed on a non-punctured 20MHz channel within the specific 40MHz channel.

[0186] The method described in the example of FIG. 12 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 receive a trigger frame including resource allocation information for transmission of a TB PPDU for a bandwidth greater than or equal to 80 MHz, and transmit the TB PPDU from the DRU or RU to the second STA based on the resource allocation information. Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 12 or the examples described below when executed by one or more processors (102).

[0187] FIG. 13 illustrates the operation of a second STA for a PPDU transmission and reception method according to one embodiment of the present disclosure.

[0188] Figure 13 illustrates the operation of a receiving device based on the proposed methods described below. The example in Figure 13 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 13 may be omitted depending on the circumstances and / or settings.

[0189] Referring to FIG. 13, the second STA transmits to the first STA a trigger frame including resource allocation information for transmission of a TB PPDU for a bandwidth greater than or equal to 80 MHz (S1310).

[0190] Thereafter, the second STA receives a TB PPDU from the first STA in the DRU or RU based on the corresponding resource allocation information (S1320).

[0191] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0192] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0193] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0194] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0195] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0196] The above-described STF-part may contain an STF sequence.

[0197] The above-described LTF portion may include a training field (i.e., an LTF sequence) for channel estimation.

[0198] The data-part described above may include user data and may include packets for upper layers.

[0199] Here, the receiving device (i.e., the second STA) may receive all or part of the PPDU through step S1320. Here, for the operation of step S1320, the receiving device (i.e., the second STA) may perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion operation applied by the transmitting device.

[0200] Thereafter, the second STA can process the TB PPDU. For example, the receiving device (i.e., the second STA) can perform decoding of all / part of the TB PPDU.

[0201] For example, a receiving device can decode the x-SIG field of a PPDU based on the legacy STF / LTF and obtain information included in the x-SIG field. For example, information about a tone plan proposed in the present disclosure can be included in the x-SIG field, and a receiving STA can obtain information about a tone plan (e.g., a DRU tone plan, a RU tone plan) through the x-SIG field. Information about a tone plan can be included in the x-SIG, and a receiving STA can obtain information about a tone plan through the x-SIG.

[0202] Then, the receiving device (i.e., the second STA) can decode the remaining portion of the PPDU based on the acquired information about the tone plan. For example, the receiving device (i.e., the second STA) can decode the STF / LTF field of the PPDU based on the information about the tone plan. In addition, the receiving device (i.e., the second STA) can decode the data field of the PPDU based on the information about the tone plan and obtain the MPDU included in the data field.

[0203] Additionally, the receiving device (i.e., the second STA) may perform a processing operation to transmit the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, subsequent operations may be performed.

[0204] In this regard, for the aforementioned TB PPDU, DRU-based transmission or RU-based transmission may be applied based on 80MHz channel units. If the first STA is assigned to a specific 80MHz channel to which DRU-based transmission is applied, the first STA may be assigned to at least one of a first type DRU with tones distributed over an 80MHz channel, a second type DRU with tones distributed over a 40MHz channel, or a third type DRU with tones distributed over a 20MHz channel within the specific 80MHz channel.

[0205] The specific details regarding the structure of the 80MHz channel or 40MHz channel to which the DRU is applied (e.g., a distribution channel applied to the channel), the structure and application method of the first type DRU, the second type DRU, and / or the third type DRU, the DRU application method depending on whether puncturing (e.g., 20MHz puncturing, 40MHz puncturing) is applied, PPDU in hybrid mode, etc. are the same as those described in FIG. 12, and therefore, overlapping descriptions are omitted in FIG. 13.

[0206] The method described in the example of FIG. 13 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 transmit a trigger frame including resource allocation information for transmission of a TB PPDU for a bandwidth greater than or equal to 80 MHz to the first STA, and receive the TB PPDU from the first STA at a DRU or RU based on the resource allocation information. Furthermore, one or more memories (204) of the second device (200) 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 (202).

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

[0208] In the present disclosure, a method for defining a structure and configuration for a PPDU in a hybrid mode in which DRUs and RRUs are simultaneously allocated and transmitted (hereinafter, Embodiments 1 to 4) and a method for operating a channel in consideration of a distributed bandwidth (dBW) when a DRU is applied to a channel of a specific size within a PPDU (hereinafter, Embodiment 5) are specifically described.

[0209] The embodiments described below are distinguished for clarity of explanation. Each embodiment may be applied independently, or may be combined with or substituted for certain components of other embodiments. For example, the method described in Embodiment 5 may be extended and applied to Embodiments 1 through 4.

[0210] Example 1

[0211] This embodiment relates to a case where, for the sake of signaling advantages, only DRU transmission or RRU transmission is performed / applied within an 80 MHz channel unit in a PPDU transmission situation of 160 MHz and / or 320 MHz bandwidth.

[0212] That is, within the 80MHz channel, DRU and RRU may not be applied simultaneously. However, if the DRU tone is distributed across the entire 160MHz channel and / or 320MHz channel (i.e., if the distribution bandwidth (dBW) is 160MHz and / or 320MHz), the RRU may not be allocated within the channel. In addition, if the DRU tone is distributed across the entire bandwidth, the RRU may not be allocated to the PPDU, and the PPDU may not be referred to as a PPDU of hybrid mode.

[0213] In this case, if a large RU is used, applying a DRU may not provide a large power boosting gain compared to an RRU. On the other hand, if a small RU is used in this case, applying a DRU may provide a large power boosting gain compared to an RRU.

[0214] Accordingly, in a PPDU transmission situation of a hybrid mode according to the present embodiment, when applying a small RU, the DRU may be restricted to be used, and the RRU may be applicable from a 242-tone RU. In this regard, a DRU of 242 or more tones may also be used, or the DRU may be restricted to a small RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU or a 52-tone RU, and the RRU may be available from a 106-tone RU. In this regard, a DRU of 106 or more tones may also be used, or the DRU may be restricted to up to a 52-tone RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU, and the RRU may be available from a 52-tone RU. In this regard, a DRU of 52 or more tones may also be used, or the DRU may be restricted to only a 26-tone RU.

[0215] At this time, within the 80MHz channel to which the DRU is applied, only DRUs with tones distributed over the entire 80MHz channel can be applied, or only DRUs distributed over at least 40MHz channels (i.e., 80MHz channels and / or 40MHz channels) can be applied, or DRUs distributed over up to 20MHz channels (i.e., 80MHz channels, 40MHz channels, and / or 20MHz channels) can be applied.

[0216] Additionally or alternatively, if puncturing is applied to a particular 80 MHz channel to which DRU transmission is applied, then the non-punctured 40 MHz channel and 20 MHz channel within the 80 MHz channel may each have DRUs with tones distributed across the entire channel (i.e., each 40 MHz channel and each 20 MHz channel). This may be the case where, in the PPDU transmission situation of the aforementioned 160 MHz and / or 320 MHz bandwidth, only DRUs with tones distributed across the entire 80 MHz are applied, or only DRUs distributed up to at least 40 MHz channels (i.e., the 80 MHz channel and / or the 40 MHz channel) are applied. In this regard, the DRUs of the non-punctured 80 MHz channel may be considered as either DRUs with tones distributed across the entire channel as described above, or DRUs distributed up to at least 40 MHz channels, or DRUs distributed up to 20 MHz channels.

[0217] Example 2

[0218] This embodiment relates to a case where only DRU transmission or RRU transmission is performed / applied within a 160 MHz channel unit in a PPDU transmission situation of 320 MHz bandwidth.

[0219] That is, within the 160MHz channel, DRU and RRU may not be applied simultaneously. However, if the DRU tone is distributed across the entire 320MHz channel (i.e., if the distributed bandwidth (dBW) is 320MHz), an RRU may not be allocated within the channel. In addition, if the DRU tone is distributed across the entire bandwidth, an RRU may not be allocated to the PPDU, and the PPDU may not be referred to as a PPDU in hybrid mode.

[0220] In a PPDU transmission situation of a hybrid mode according to the present embodiment, when applying a small RU, the DRU may be restricted to be used, and the RRU may be applicable from a 242-tone RU. In this regard, a DRU of 242 or more tones may also be used, or the DRU may be restricted to a small RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU or a 52-tone RU, and the RRU may be available from a 106-tone RU. In this regard, a DRU of 106 or more tones may also be used, or the DRU may be restricted to up to a 52-tone RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU, and the RRU may be available from a 52-tone RU. In this regard, a DRU of 52 or more tones may also be used, or the DRU may be restricted to only a 26-tone RU.

[0221] At this time, within the 160 MHz channel to which the DRU is applied, only DRUs with tones distributed over the entire 160 MHz channel can be applied, or only DRUs distributed over at least 80 MHz channels (i.e., 160 MHz channels and / or 80 MHz channels) can be applied, or only DRUs distributed over at least 40 MHz channels (i.e., 160 MHz channels, 80 MHz channels, and / or 40 MHz channels) can be applied, or DRUs distributed over up to 20 MHz channels (i.e., 160 MHz channels, 80 MHz channels, 40 MHz channels, and / or 20 MHz channels) can be applied.

[0222] Additionally or alternatively, if puncturing is applied to a particular 160 MHz channel to which DRU transmission is applied, the non-punctured 80 MHz channel, 40 MHz channel and 20 MHz channel within that 160 MHz channel may each have DRUs applied with tones distributed across the entire channel (i.e., each 80 MHz channel, 40 MHz channel and 20 MHz channel). For example, the configuration of the channel to which 20 MHz puncturing is applied may be 80 MHz+40 MHz+20 MHz, and the configuration of the channel to which 40 MHz puncturing is applied may be 80 MHz+40 MHz (in which case the 20 MHz channel is not considered). This may be the case where, in the PPDU transmission situation of the 320MHz bandwidth mentioned above, only DRUs with tones distributed across the entire 160MHz are applied, or only DRUs distributed across at least 80MHz channels (i.e., 160MHz channels and / or 80MHz channels) are applied, or only DRUs distributed across at least 40MHz channels (i.e., 80MHz channels and / or 40MHz channels) are applied. In this case, when DRUs distributed across at least 40MHz channels are applied, the DRUs of the 80MHz channel that are not punctured may correspond to DRUs distributed across the 80MHz channel or the 40MHz channel. In this regard, the DRUs of the 160MHz channel that are not punctured may only be considered as DRUs with tones distributed across the entire channel as mentioned above, or DRUs distributed across at least 80MHz channels, DRUs distributed across at least 40MHz channels, or DRUs distributed across 20MHz channels.

[0223] Example 3

[0224] This embodiment relates to a case where only DRU transmission or RRU transmission is performed / applied within a 40MHz channel unit in a PPDU transmission situation of 80MHz, 160MHz and / or 320MHz bandwidth.

[0225] That is, within the 40MHz channel, DRU and RRU may not be applied simultaneously. However, if the DRU tone is distributed across the entire 80MHz channel, 160MHz channel and / or 320MHz channel (i.e., if the distributed bandwidth (dBW) is 80MHz, 160MHz and / or 320MHz), the RRU may not be allocated within the channel. In addition, if the DRU tone is distributed across the entire bandwidth, the RRU may not be allocated to the PPDU, and the PPDU may not be referred to as a PPDU of hybrid mode.

[0226] In a PPDU transmission situation of a hybrid mode according to the present embodiment, when applying a small RU, the DRU may be restricted to be used, and the RRU may be applicable from a 242-tone RU. In this regard, a DRU of 242 or more tones may also be used, or the DRU may be restricted to a small RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU or a 52-tone RU, and the RRU may be available from a 106-tone RU. In this regard, a DRU of 106 or more tones may also be used, or the DRU may be restricted to up to a 52-tone RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU, and the RRU may be available from a 52-tone RU. In this regard, a DRU of 52 or more tones may also be used, or the DRU may be restricted to only a 26-tone RU.

[0227] At this time, within the 40MHz channel to which the DRU is applied, only DRUs with tones distributed across the entire 40MHz channel can be applied, or DRUs distributed up to the 20MHz channel (i.e., the 40MHz channel and / or the 20MHz channel) can be applied.

[0228] Additionally or alternatively, if puncturing is applied to a specific 80MHz channel, a DRU or an RRU may be applied to each of the non-punctured 40MHz channel and 20MHz channel within the 80MHz channel. That is, in such a case, if a DRU is applied to a 20MHz channel among the non-punctured 40MHz and 20MHz channels, a distributed DRU may be applied to the 20MHz channel. This may be for the case where only the DRU with tones distributed across the entire 40MHz is applied in the PPDU transmission situation of the aforementioned 80MHz, 160MHz, and / or 320MHz bandwidth. In this regard, the DRU of the non-punctured 40MHz channel may be applied as a DRU with tones distributed across the entire 40MHz channel as described above, or a DRU distributed up to the 20MHz channel may be considered.

[0229] Example 4

[0230] This embodiment relates to a case where only DRU transmission or RRU transmission is performed / applied within a 20MHz channel unit in a PPDU transmission situation of 40MHz, 80MHz, 160MHz and / or 320MHz bandwidth.

[0231] That is, within the 20MHz channel, DRU and RRU may not be applied simultaneously. However, if the DRU tone is distributed across the entire 40MHz channel, 80MHz channel, 160MHz channel and / or 320MHz channel (i.e., if the distributed bandwidth (dBW) is 40MHz, 80MHz, 160MHz and / or 320MHz), the RRU may not be allocated within the channel. In addition, if the DRU tone is distributed across the entire bandwidth, the RRU may not be allocated to the PPDU, and the PPDU may not be referred to as a PPDU of hybrid mode.

[0232] In a PPDU transmission situation of a hybrid mode according to the present embodiment, when applying a small RU, the DRU may be restricted to be used, and the RRU may be applicable from a 242-tone RU. In this regard, a DRU of 242 or more tones may also be used, or the DRU may be restricted to a small RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU or a 52-tone RU, and the RRU may be available from a 106-tone RU. In this regard, a DRU of 106 or more tones may also be used, or the DRU may be restricted to up to a 52-tone RU. Alternatively, the DRU may be restricted to be used when applying a 26-tone RU, and the RRU may be available from a 52-tone RU. In this regard, a DRU of 52 or more tones may also be used, or the DRU may be restricted to only a 26-tone RU.

[0233] At this time, only DRUs with tones distributed across the entire 20MHz channel can be applied within the 20MHz channel to which the DRU is applied.

[0234] Example 5

[0235] This embodiment relates to a method of operating a channel based on distributed bandwidth (dBW) when DRU is applied to a specific 80MHz channel within a PPDU of 80MHz or more.

[0236] Specifically, when DRU is applied to a specific 80MHz channel in a PPDU of 80MHz or more, the operation method of the channel can be distinguished based on the following factors.

[0237] - Non-puncturing

[0238] - Preamble puncturing

[0239] - PPDU in hybrid mode

[0240] Below, we describe specific channel operation methods based on these elements.

[0241] (Example 5-1)

[0242] First, when DRU is applied in an 80MHz channel without puncturing, various modes / types of distributed bandwidth (dBW) can be considered as follows.

[0243] For example, an 80MHz distributed bandwidth mode may be considered. This mode may be efficient in terms of maximizing power boosting gain and data rate. As another example, a 20MHz+20MHz+40MHz distributed bandwidth mode or a 40MHz+20MHz+20MHz distributed bandwidth mode may be considered. This mode may be efficient for STAs operating at 20MHz and 40MHz. In this regard, the order of 20MHz / 40MHz may always be considered as fixed (i.e., one of the two modes), or both modes may be considered. As another example, a 40MHz+40MHz distributed bandwidth mode may be considered. This mode may be efficient when only STAs operating at 40MHz or higher exist. As another example, a 20MHz+20MHz+20MHz+20MHz distributed bandwidth mode may be considered. This mode can be efficient in situations where multiple 20MHz operating STAs are transmitting / allocating.

[0244] If all four modes described above are considered, or only three modes are considered, each mode can be indicated in the non-punctured 80MHz channel to which the DRU is applied using a specific two-bit designation. Alternatively, if only two modes are considered, each mode can be indicated in the non-punctured 80MHz channel to which the DRU is applied using a specific one-bit designation. Alternatively, if only one mode is considered, a separate mode designation may not be necessary.

[0245] In terms of utility, only the 80MHz distributed bandwidth mode and the 20MHz+20MHz+40MHz distributed bandwidth mode may be considered, in which case 1 bit can be used to indicate the two modes in a non-punctured 80MHz channel where DRU is applied.

[0246] Also, if the order of 20MHz / 40MHz is not fixed in the 20MHz+20MHz+40MHz distributed bandwidth mode (i.e., both 20MHz+20MHz+40MHz distributed bandwidth mode and 40MHz+20MHz+20MHz distributed bandwidth mode are considered), 3 bits or 2 bits or 1 bit may be required to indicate the mode. That is, a total of 5 modes can be defined by considering the 20MHz+20MHz+40MHz distributed bandwidth mode and the 40MHz+20MHz+20MHz distributed bandwidth mode as different modes, and some modes may be excluded. Alternatively, a method may be applied in which the mode is indicated using 2 bits or 1 bit (in which case, the 20MHz+20MHz+40MHz distributed bandwidth mode and the 40MHz+20MHz+20MHz distributed bandwidth mode are classified as one mode in the indication), and an additional 1 bit is used to indicate the position of 40MHz when indicating the 20MHz+20MHz+40MHz distributed bandwidth mode. That is, the 20MHz+20MHz+40MHz distributed bandwidth mode and the 40MHz+20MHz+20MHz distributed bandwidth mode can be distinguished using an additional 1 bit.

[0247] For example, if the aforementioned PPDU transmission is a trigger-based (TB) PPDU transmission, for the indication of the aforementioned mode, one, two, or three bits of the reserved subfield of the user info field of the version / variant (e.g., UHR or beyond-UHR) that supports DRU in the trigger frame, or some bits of the trigger dependent user info or SS allocation subfield may be used. Additionally or alternatively, for the indication of the aforementioned mode, one, two, or three bits of the bits in the same position as a reserved subfield of the common info field of an existing version / variant (e.g., EHT) that does not support DRU in the trigger frame may be used in the common info field of the version / variant that supports DRU (e.g., UHR or beyond-UHR) or in the same position as a reserved subfield of the existing version / variant (e.g., EHT) that does not support DRU may be used. Additionally or alternatively, one, two, or three bits of the bits in the special user info field may be used in the special user info field or in the same position as a reserved subfield of the existing special user info field or in the same position as a U-SIG disregard and validate subfield may be used in the special user info field to indicate the aforementioned mode.

[0248] For another example, if the aforementioned PPDU transmission is a DL (downlink) PPDU transmission, for the indication of the aforementioned mode, 1 bit, 2 bits, or 3 bits of the reserved subfield in the user field in the SIG field of the version / variant that supports DRU (e.g., UHR-SIG, beyond-UHR-SIG), the bits in the same position as the reserved subfield in the user field in the SIG field of the existing version / variant that does not support DRU (e.g., EHT-SIG), some bits in the NSS subfield, bits in the beamformed subfield, or bits in the coding subfield may be used. Additionally or alternatively, for indication of the aforementioned mode, 1-bit, 2-bit, or 3-bits of the same positions as the disregard or validate subfields in the common field of the U-SIG or other SIG field (e.g., UHR-SIG, beyond-UHR-SIG) of the version / variant that supports DRU, or in the common field of the U-SIG or other SIG field (e.g., EHT-SIG) of the existing version / variant that does not support DRU may be used.

[0249] (Example 5-2)

[0250] Next, when DRU is applied in an 80MHz channel with 20MHz puncturing, various modes / types of distributed bandwidth (dBW) can be considered as follows.

[0251] For example, a 60MHz distributed bandwidth mode may be considered. This mode may be efficient in terms of maximizing power boosting gain and data rate. As another example, a 20MHz+40MHz distributed bandwidth mode or a 40MHz+20MHz distributed bandwidth mode may be considered. This mode may be efficient for STAs operating at 20MHz and 40MHz. In this regard, since the 20MHz+40MHz distributed bandwidth mode or the 40MHz+20MHz distributed bandwidth mode is determined based on the location of the punctured 20MHz channel, no additional method is required to distinguish between them. As another example, a 20MHz+20MHz+20MHz distributed bandwidth mode may be considered. This mode may be efficient in situations where multiple 20MHz operating STAs are transmitting / allocating.

[0252] If all three modes described above are considered, each mode can be indicated in a 20MHz punctured 80MHz channel to which DRU is applied using a specific 2-bit. Alternatively, if only two modes are considered, each mode can be indicated in a 20MHz punctured 80MHz channel to which DRU is applied using a specific 1-bit. Alternatively, if only one mode is considered, a separate mode indication may not be necessary. For implementation and / or usability reasons, only the 20MHz+40MHz distributed bandwidth mode may be considered, in which case the mode indication described above may not be necessary. If an indication is required, the indication may be performed using some of the bits defined for mode indication in an 80MHz channel to which puncturing is not applied (e.g., the bits described in Embodiment 5-1). If such bits are insufficient, the mode indication may be performed using some of the bits available in the TB PPDU transmission or DL ​​PPDU transmission described in Embodiment 5-1.

[0253] (Example 5-3)

[0254] Next, when DRU is applied in an 80MHz channel with 40MHz puncturing, various modes / types of distributed bandwidth (dBW) can be considered as follows.

[0255] For example, a 40MHz distributed bandwidth mode may be considered. This mode may be efficient in terms of maximizing power boosting gain and data rate. Another example is a 20MHz+20MHz distributed bandwidth mode. This mode may be efficient in situations where multiple 20MHz operating STAs are transmitting / allocating.

[0256] If both of the above-mentioned two modes are considered, each mode can be indicated using a specific 1-bit in the 40MHz punctured 80MHz channel to which the DRU is applied. Conversely, if only one mode is considered, a separate mode indication may not be necessary. From an implementation perspective, only the 40MHz distributed bandwidth mode may be considered, in which case the above-mentioned mode indication may not be necessary. If an indication is required, the indication may be performed using some of the bits defined for mode indication in the 80MHz channel without puncturing (e.g., the bits described in Embodiment 5-1). If the corresponding bits are insufficient, the mode indication may be performed using some of the bits available in the TB PPDU transmission or DL ​​PPDU transmission described in Embodiment 5-1.

[0257] (Example 5-4)

[0258] In addition, for PPDUs transmitted together / simultaneously by DRU and RRU, i.e., PPDUs in hybrid mode, the application of distributed bandwidths in various modes and the mode indication method related thereto can be defined.

[0259] For example, for a PPDU in hybrid mode with bandwidths of 80 MHz, 160 MHz, and / or 320 MHz, a scheme in which DRUs and RRUs are not used simultaneously within 80 MHz may be considered for implementation gains. In this case, the distributed bandwidths of the various modes proposed above may be applied in the 80 MHz channel to which the DRUs are applied, and the mode indication schemes related thereto may be applied in the same / similar manner (e.g., see Embodiments 5-1 to 5-3).

[0260] For another example, for a PPDU in hybrid mode with an 80 MHz bandwidth, a scheme in which DRUs and RRUs are not used simultaneously within 40 MHz may be considered for implementation gains. In this case, within the 40 MHz channel where DRUs are applied, various modes / types of distributed bandwidth (dBW) may be considered, as follows:

[0261] For example, a 40MHz distributed bandwidth mode may be considered. This mode may be efficient in terms of maximizing power boosting gain and data rate. Another example is a 20MHz+20MHz distributed bandwidth mode. This mode may be efficient in situations where multiple 20MHz operating STAs are transmitting / allocating.

[0262] If both of the above-mentioned two modes are considered, each mode can be indicated using a specific 1-bit in the 40MHz channel to which the DRU is applied. Conversely, if only one mode is considered, a separate mode indication may not be necessary. In terms of implementation, the 20MHz+20MHz distributed bandwidth mode may not be suitable, in which case the above-mentioned mode indication may be unnecessary. If an indication is required, the indication may be performed using some of the bits defined for mode indication in the 80MHz channel to which puncturing is not applied (e.g., the bits described in Example 5-1). If the corresponding bits are insufficient, the mode indication may be performed using some of the bits available in the TB PPDU transmission or DL ​​PPDU transmission described in Example 5-1.

[0263] In this regard, for a PPDU in hybrid mode with an 80 MHz bandwidth, if 20 MHz puncturing is applied to a 40 MHz channel to which DRU is applied, a 20 MHz distributed bandwidth may be applied to the non-punctured 20 MHz channel. In this case, additional instructions (e.g., mode instructions) may be unnecessary.

[0264] 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.

[0265] 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.

[0266] 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.

[0267] 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

1. A method performed by a first station (STA) in a wireless local area network (WLAN) system, the method comprising: A step of receiving, from a second STA, a trigger frame including resource allocation information for transmission of a TB PPDU (trigger based physical layer protocol data unit) for a bandwidth greater than or equal to 80 MHz; and A step of transmitting the TB PPDU to the second STA from a distributed resource unit (DRU) or resource unit (RU) based on the resource allocation information, For the above TB PPDU, DRU-based transmission or RU-based transmission is applied based on 80MHz channel units. A method wherein, based on the first STA being assigned within a specific 80MHz channel to which the DRU-based transmission is applied, the first STA is assigned to at least one of a first type DRU having tones distributed over an 80MHz channel, a second type DRU having tones distributed over a 40MHz channel, or a third type DRU having tones distributed over a 20MHz channel.

2. In paragraph 1, The above specific 80MHz channel is, A type 1 distribution channel configured to enable one type 1 DRU to be applied; A Type 2 distributed channel configured to be applicable to one Type 2 DRU and two Type 3 DRUs; A Type 3 distributed channel configured to allow application of two Type 2 DRUs, or A method based on any one of a type 4 distributed channel configured to be applicable to four type 3 DRUs.

3. In paragraph 2, A method wherein the above specific 80MHz channel is a non-punctured 80MHz channel.

4. In paragraph 2, A method wherein the trigger frame includes information indicating the type of distributed channel for the specific 80 MHz channel.

5. In paragraph 1, Based on the 20MHz puncturing applied to the above specific 80MHz channel, The above specific 80MHz channel is, A Type 5 distributed channel configured to be applicable to one Type 2 DRU and one Type 3 DRU, or A method based on any one of the sixth type distributed channels configured to be applicable to three third type DRUs.

6. In paragraph 5, A method wherein the trigger frame includes information indicating the type of distributed channel for the specific 80 MHz channel to which 20 MHz puncturing is applied.

7. In paragraph 1, Based on the 40MHz puncturing applied to the above specific 80MHz channel, The above specific 80MHz channel is, A Type 7 distributed channel configured to allow application of one Type 2 DRU, or A method based on any one of the eighth type distributed channels configured to be applicable to two third type DRUs.

8. In paragraph 7, A method wherein the trigger frame includes information indicating the type of distributed channel for the specific 80 MHz channel to which 40 MHz puncturing is applied.

9. In paragraph 1, A method wherein the above TB PPDU is set to a bandwidth including one or more channels to which a DRU tone plan or a RU tone plan is applicable.

10. In paragraph 1, Based on the above bandwidth being 80MHz and the DRU-based transmission being assigned to a specific 40MHz channel belonging to the above bandwidth, The above specific 40MHz channel is, A Type 9 distributed channel configured to allow application of one Type 2 DRU, or A method based on any one of the Type 10 distributed channels configured to be applicable to two Type 3 DRUs.

11. In paragraph 1, A method wherein the bandwidth is 80 MHz, the first STA is allocated within a specific 40 MHz channel to which the DRU-based transmission is applied, and based on 20 MHz puncturing being applied to the specific 40 MHz channel, the first STA is allocated to a DRU whose tones are distributed on a non-punctured 20 MHz channel within the specific 40 MHz channel.

12. In paragraph 1, The above DRU-based transmission corresponds to transmission using a DRU composed of non-contiguous tones. The above RU-based transmission is a method corresponding to transmission using RUs composed of contiguous tones.

13. In a first station (STA) device in a wireless local area network (WLAN) system, the device: one or more transmitters and receivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receive, from a second STA, a trigger frame including resource allocation information for transmission of a TB PPDU (trigger based physical layer protocol data unit) for a bandwidth greater than or equal to 80 MHz; Based on the above resource allocation information, the TB PPDU is set to be transmitted to the second STA from a distributed resource unit (DRU) or resource unit (RU). For the above TB PPDU, DRU-based transmission or RU-based transmission is applied based on 80MHz channel units. A device wherein, based on the first STA being assigned within a specific 80MHz channel to which the DRU-based transmission is applied, the first STA is assigned to at least one of a first type DRU having tones distributed over an 80MHz channel, a second type DRU having tones distributed over a 40MHz channel, or a third type DRU having tones distributed over a 20MHz channel.

14. A method performed by a second station (STA) in a wireless local area network (WLAN) system, the method comprising: A step of transmitting, to a first STA, a trigger frame including resource allocation information for transmission of a TB PPDU (trigger based physical layer protocol data unit) for a bandwidth greater than or equal to 80 MHz; and A step of receiving the TB PPDU from the first STA in a distributed resource unit (DRU) or resource unit (RU) based on the resource allocation information, For the above TB PPDU, DRU-based transmission or RU-based transmission is applied based on 80MHz channel units. A method wherein, based on the first STA being assigned within a specific 80MHz channel to which the DRU-based transmission is applied, the first STA is assigned to at least one of a first type DRU having tones distributed over an 80MHz channel, a second type DRU having tones distributed over a 40MHz channel, or a third type DRU having tones distributed over a 20MHz channel.

15. In a second station (STA) device in a wireless local area network (WLAN) system, the device: one or more transmitters and receivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Transmitting, to a first STA, a trigger frame including resource allocation information for transmission of a TB PPDU (trigger based physical layer protocol data unit) for a bandwidth greater than or equal to 80 MHz; Set the TB PPDU to be received from the first STA in a distributed resource unit (DRU) or resource unit (RU) based on the resource allocation information. For the above TB PPDU, DRU-based transmission or RU-based transmission is applied based on 80MHz channel units. A device wherein, based on the first STA being assigned within a specific 80MHz channel to which the DRU-based transmission is applied, the first STA is assigned to at least one of a first type DRU having tones distributed over an 80MHz channel, a second type DRU having tones distributed over a 40MHz channel, or a third type DRU having tones distributed over a 20MHz channel.

16. A processing device configured to control a station (STA) in a wireless local area network (WLAN) system, wherein the processing device: 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 that, when executed by said one or more processors, perform a method according to any one of claims 1 to 12.

17. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein said one or more commands are executed by one or more processors to control a device in a wireless LAN system to perform a method according to any one of claims 1 to 12.

Images