PPDU transmission and reception method and apparatus in a wireless LAN system

Abstract

A method and apparatus for transmitting and receiving PPDUs in a wireless LAN system are disclosed. A method performed by a first STA according to one embodiment of this disclosure may include the steps of generating a PPDU to be transmitted within an 80 MHz frequency bandwidth to which 20 MHz puncturing is applied, and transmitting the PPDU to a second STA.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting and receiving a PPDU (physical protocol data unit) in a wireless LAN (Wireless Local Area Network, WLAN) system.

Background Art

[0002] New technologies for improving the transmission rate, increasing the bandwidth, improving the reliability, reducing errors, and reducing latency have been introduced for wireless LAN (WLAN). Among wireless LAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, technologies recently introduced into wireless LAN include enhancements for VHT (Very High-Throughput) of the 802.11ac standard, enhancements for HE (High Efficiency) of the IEEE 802.11ax standard, and the like.

[0003] In order to provide a more improved wireless communication environment, improvement technologies for EHT (Extremely High Throughput) have been discussed. For example, technologies for increasing the bandwidth, efficiently utilizing multiple bands, MIMO (Multiple Input Multiple Output) that supports an increased number of spatial streams, and technologies for adjusting multiple access points (APs) have been studied. In particular, various technologies for supporting traffic with low latency or real-time characteristics have been studied. In addition, new technologies for supporting ultra-high reliability (UHR), including improvements or extensions of EHT technology, have been discussed.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technical problem addressed in this disclosure is to provide a method and apparatus for sending and receiving PPDUs that include resource units (RUs) composed of discontinuous subcarriers.

[0005] The technical challenges addressed in this disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be clearly understood by those with ordinary skill in the art to which this disclosure pertains from the following description. [Means for solving the problem]

[0006] A method performed by a first station (STA) according to one aspect of the present disclosure may include (may include; may configure; may construct; may set up; may encompass; may include; may contain; may have) a plurality of first type resource units (RUs) in the 80 MHz frequency bandwidth excluding the punctured 20 MHz, each comprising subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, each of the plurality of first type RUs comprising discontinuous subcarriers at predetermined intervals in the frequency domain, and the position of the PPDU relative to one or more first type RUs may be indicated by an RU assignment subfield in an ascending order arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain.

[0007] A method performed by a second station (STA) according to further aspects of the present disclosure may include the steps of receiving a physical protocol data unit (PPDU) from a first STA within an 80 MHz frequency bandwidth to which 20 MHz puncturing is applied, and processing the PPDU. The plurality of first type resource units (RUs) within the 80 MHz frequency bandwidth to which 20 MHz puncturing is applied consist of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, and each of the plurality of first type RUs consists of discontinuous subcarriers at predetermined intervals in the frequency domain, and the position of the PPDU relative to one or more first type RUs may be indicated by an RU assignment subfield in an ascending order arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain. [Effects of the Invention]

[0008] According to this disclosure, transmission power can be improved by utilizing RUs composed of discontinuous subcarriers, thereby increasing transmission throughput and improving coverage.

[0009] Furthermore, this disclosure makes it possible to reduce the signaling overhead for allocating RUs composed of discontinuous subcarriers.

[0010] Furthermore, according to this disclosure, even within a PPDU bandwidth to which puncturing is applied, the allocation of RUs composed of discontinuous subcarriers can improve the efficiency of frequency resource utilization.

[0011] The effects derived from this disclosure are not limited to those mentioned above, and any other effects not mentioned above will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains from the following description. [Brief explanation of the drawing]

[0012] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples of the disclosure and illustrate the technical features of the disclosure together with the detailed description. [Figure 1] This is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure. [Figure 2] This figure shows an exemplary structure of a wireless LAN system to which this disclosure can be applied. [Figure 3] This diagram illustrates the link setup process to which this disclosure applies. [Figure 4] This diagram illustrates the backoff process to which this disclosure applies. [Figure 5] This diagram illustrates the CSMA / CA baseframe transmission operation to which this disclosure can be applied. [Figure 6] This figure illustrates an example of a frame structure used in a wireless LAN system to which this disclosure can be applied. [Figure 7] This figure shows an example of a PPDU as defined in the IEEE 802.11 standard to which this disclosure applies. [Figure 8] This figure shows an exemplary format of a trigger frame to which this disclosure can be applied. [Figure 9] This figure shows an example of resource unit (RU) configuration used in a 20MHz bandwidth. [Figure 10] This figure shows an example of resource unit (RU) configuration used in a 40MHz bandwidth. [Figure 11] This figure shows an example of resource unit (RU) configuration used in the 80MHz bandwidth. [Figure 12]In a wireless LAN system to which the present disclosure is applicable, it is a diagram illustrating the application of distributed tone RUs. [Figure 13] It is a diagram illustrating the operation of a transmission device for a PPDU transmission / reception method according to an embodiment of the present disclosure. [Figure 14] It is a diagram illustrating the operation of a reception device for a PPDU transmission / reception method according to an embodiment of the present disclosure.

Mode for Carrying Out the Invention

[0013] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is for explaining exemplary embodiments of the present disclosure and is not for showing the only embodiments in which the present disclosure can be implemented. The following detailed description includes specific details in order to provide a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0014] In some cases, in order to avoid the concept of the present disclosure from being ambiguous, known structures and devices may be omitted, or they may be shown in the form of a block diagram centered on the core functions of each structure and device.

[0015] In the present disclosure, when a certain component is "connected", "coupled" or "connected" to another component, this may include not only a direct connection relationship but also an indirect connection relationship in which there are further other components between them. Also, in the present disclosure, the term "including" or "having" identifies the presence of the recited features, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, steps, operations, elements, components and / or groups thereof.

[0016] In this disclosure, terms such as "first," "second," etc., are used solely to distinguish one component from another, and are not used to limit the components, nor do they limit the order or importance of the components unless specifically mentioned. Therefore, 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.

[0017] The terms used in this disclosure are for illustrative purposes relating to specific embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and in the attached claims, singular forms are intended to include plural forms unless otherwise specified in the context. The terms "and / or" used in this disclosure may refer to one of the related enumerated items, or to any and all possible combinations of two or more of them. In this disclosure, a " / " between words has the same meaning as "and / or" unless otherwise specified.

[0018] The examples in this disclosure may be applied to various wireless communication systems. For example, the examples in this disclosure may be applied to wireless LAN systems. For example, the examples in this disclosure may be applied to IEEE 802.11a / g / n / ac / ax standard-based wireless LANs. Furthermore, the examples in this disclosure may be applied to newly proposed IEEE 802.11bn (or UHR) standard-based wireless LANs. In addition, the examples in this disclosure may be applied to next-generation standard-based wireless LANs following IEEE 802.11bn. Moreover, the examples in this disclosure may be applied to cellular wireless communication systems. For example, they may be applied to cellular wireless communication systems based on 3GPP (3rd Generation Partnership Project: registered trademark: hereinafter the same) standard LTE (Long Term Evolution) series technologies and 5G NR (New Radio) series technologies.

[0019] The following describes the technical features to which the examples in this disclosure may apply.

[0020] Figure 1 is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure.

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

[0022] The devices 100 and 200 illustrated in Figure 1 can also be referred to as stations (STA). For example, the devices 100 and 200 illustrated in Figure 1 can be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, STA 110 and 200 can play the role of an AP (access point) or a non-AP. That is, in this disclosure, STA 110 and 200 may have AP and / or non-AP functions. When STA 110 and 200 have AP functions, they can simply be called APs, and when STA 110 and 200 have non-AP functions, they can simply be called STAs. In addition, in this disclosure, AP may be represented as AP STA.

[0023] Referring to Figure 1, the first device 100 and the second device 200 can send and receive wireless signals using various wireless LAN technologies (e.g., the IEEE 802.11 series). The first device 100 and the second device 200 may include interfaces to the medium access control (MAC) layer and the physical layer (PHY) in accordance with the IEEE 802.11 standard.

[0024] Furthermore, the first device 100 and the second device 200 can also further support various communication standards other than Wi-Fi technology (e.g., 3GPP LTE series, 5G NR series standards, etc.). The devices of this disclosure may also be embodied in various devices such as mobile phones, vehicles, personal computers, Augmented Reality (AR) equipment, and Virtual Reality (VR) equipment. In addition, the STA of this specification can support various communication services such as voice calls, video calls, data communication, autonomous driving, Machine-Type Communication (MTC), Machine-to-Machine (M2M), Device-to-Device (D2D), and Internet of Things (IoT).

[0025] The 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 may control the memories 104 and / or the transceivers 106 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation diagrams of this disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals and then transmit a radio signal containing the first information / signals via the transceiver 106. Alternatively, the processor 102 may receive a radio signal containing second information / signals via the transceiver 106 and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be linked to the processor 102 and can store various information relating to the operation of the processor 102. For example, memory 104 may store software code that executes some or all of a process controlled by processor 102, or that contains instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to embody wireless LAN technology (e.g., IEEE 802.11 series). Transceiver 106 may be coupled with processor 102 and can transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be used synonymously with RF (Radio Frequency) unit. In this disclosure, device may also mean communication modem / circuit / chip.

[0026] 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 may control the memories 204 and / or the transceivers 206 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signals and then transmit a radio signal containing the third information / signals via the transceiver 206. Alternatively, the processor 202 may receive a radio signal containing fourth information / signals via the transceiver 206 and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be linked to the processor 202 and can store various information related to the operation of the processor 202. For example, memory 204 may store software code that executes some or all of the processes controlled by processor 202, or that contains instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to embody wireless LAN technology (e.g., IEEE 802.11 series). Transceiver 206 may be coupled with processor 202 and may transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver. Transceiver 206 may be used synonymously with RF unit. In this disclosure, device may also mean communication modem / circuit / chip.

[0027] The hardware elements of devices 100,200 are described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 can embodied one or more layers (e.g., functional layers such as PHY and MAC). One or more processors 102,202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate messages, control information, data, or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by the functions, procedures, proposals and / or methods of this disclosure and provide them 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 by the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams of this disclosure.

[0028] One or more processors 102,202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102,202 may be embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102,202. The descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be contained in 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, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions and / or sets of instructions.

[0029] One or more memories 104,204 may be connected to one or more processors 102,202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104,204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104,204 may be located inside and / or outside of one or more processors 102,202. Furthermore, one or more memories 104,204 may be connected to one or more processors 102,202 by various technologies such as wired or wireless connections.

[0030] One or more transceivers 106,206 can transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or operation sequence diagrams of this disclosure, to one or more other devices. One or more transceivers 106,206 can receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, from one or more other devices. For example, one or more transceivers 106,206 may be coupled with one or more processors 102,202 to transmit and receive radio signals. For example, one or more processors 102,202 can control one or more transceivers 106,206 to transmit user data, control information or radio signals to one or more other devices. Also, one or more processors 102,202 can control one or more transceivers 106,206 to receive user data, control information or radio signals from one or more other devices. Furthermore, one or more transceivers 106,206 may be connected to one or more antennas 108,208, and one or more transceivers 106,206 may be configured to send and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, via one or more antennas 108,208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106,206 may convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102,202. One or more transceivers 106,206 may convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102,202, from baseband signals to RF band signals. To this end, one or more transceivers 106,206 may include (analog) oscillators and / or filters.

[0031] For example, either STA100 or STA200 can perform the intended operation of an AP, and the other STA100 or STA200 can perform the intended operation of a non-AP STA. For example, the transceivers 106 and 206 in Figure 1 can perform the transmission and reception of signals (e.g., packets or PPDUs (Physical Layer Protocol Data Units) conforming to IEEE 802.11a / b / g / n / ac / ax / be / bn, etc.). Furthermore, in this disclosure, the operation of various STAs generating transmission and reception signals or performing data processing and calculations in advance for transmission and reception signals may be performed by the processors 102 and 202 in Figure 1. For example, an example of an operation that generates transmit / receive signals or performs data processing or calculations in advance for transmit / receive signals may include: 1) an operation to determine / acquire / construct / calculate / decode / encode bit information of fields contained within the PPDU (SIG (signal), STF (short training field), LTF (long training field), Data, etc.); 2) an operation to determine / construct / acquire time resources and frequency resources (e.g., subcarrier resources) used for fields contained within the PPDU (SIG, STF, LTF, Data, etc.); 3) an operation to determine / construct / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for fields contained within the PPDU (SIG, STF, LTF, Data, etc.); 4) power control operations and / or power saving operations applied to the STA; and 5) operations related to determining / acquiring / constructing / calculating / decoding / encoding the ACK signal. Furthermore, in the following example, various pieces of information used by various STAs for determining / acquiring / composing / calculating / decoding / encoding the transmit / receive signals (e.g., information about fields / subfields / control fields / parameters / power, etc.) may be stored in memories 104,204 in Figure 1.

[0032] In the following, downlink (DL) refers to the link for communication from AP STA to non-AP STA, and downlink PPDU / packets / signals, etc., may be transmitted and received through the downlink. In downlink communication, the transmitter may be part of AP STA, and the receiver may be part of non-AP STA. Uplink (UL) refers to the link for communication from non-AP STA to AP STA, and uplink PPDU / packets / signals, etc., may be transmitted and received through the uplink. In uplink communication, the transmitter may be part of non-AP STA, and the receiver may be part of AP STA.

[0033] Figure 2 shows an exemplary structure of a wireless LAN system to which this disclosure can be applied.

[0034] The structure of a wireless LAN system may consist of multiple components. A wireless LAN may be provided that supports transparent STA mobility to higher layers through the interaction of multiple components. A BSS (Basic Service Set) corresponds to the basic structural block of a wireless LAN. Figure 2 illustrates the existence of two BSSs (BSS1 and BSS2), with each BSS containing two STAs as members (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). In Figure 2, the ellipses representing the BSSs may be understood as representing the coverage area where the STAs included in that BSS maintain communication. This area can be called a BSA (Basic Service Area). When an STA moves outside a BSA, it can no longer communicate directly with other STAs within that BSA.

[0035] Ignoring the DS shown in Figure 2, the most basic type of BSS in a wireless LAN is the Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For instance, assuming other components are omitted, BSS1 consisting only of STA1 and STA2, or BSS2 consisting only of STA3 and STA4, can each be considered a typical example of an IBSS. Such a configuration is possible when STAs can communicate directly without APs. Furthermore, this type of wireless LAN is not pre-planned and configured, but can be configured when the LAN requires it, and can be called an ad-hoc network. Since an IBSS does not include APs, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In an IBSS, all STAs may be mobile STAs, and connection to a distributed system (DS) is not permitted, forming a self-contained network.

[0036] STA membership in the BSS can change dynamically due to actions such as STAs being added or removed, or STAs entering or leaving the BSS area. To become a member of the BSS, an STA can join the BSS using a synchronization process. To access all services of the BSS-based structure, an STA must be associated with the BSS. Such associations may be configured dynamically and may include the use of Distribution System Services (DSS).

[0037] In a wireless LAN, the direct STA-to-STA distance may be limited by PHY performance. While this distance limit may be sufficient in some cases, there may be situations requiring communication between STAs over longer distances. Distributed systems (DS) may be configured to support extended coverage.

[0038] DS refers to a structure in which BSSs are interconnected. Specifically, as shown in Figure 2, BSSs may exist as components of an extended form of a network composed of multiple BSSs. DS is a logical concept and may be identified by the characteristics of the Distributed System Medium (DSM). In this regard, Wireless Medium (WM) and DSM may be logically distinct. Each logical medium is used for a different purpose and by different components. These mediums are neither limited to being the same nor limited to being different. The flexibility of wireless LAN structures (DS structures or other network structures) can be explained by the fact that multiple mediums are logically distinct from one another. That is, wireless LAN structures can be embodied in various ways, and each embodied example may be identified independently by its physical characteristics.

[0039] DS can support mobile devices by providing seamless integration of multiple BSSs and offering the necessary logical services for handling destination addresses. DS may also include a portal component that acts as a bridge for connecting wireless LANs with other networks (e.g., IEEE 802.X).

[0040] An AP (Application Programming Object) is an entity that enables a coupled non-AP STA (Systematization System) to access the DS (Data Storage System) via the WM (Web Module) and also possesses the functionality of an STA. Data can be moved between the BSS (Base System Storage) and the DS via the AP. For example, STA2 and STA3, shown in Figure 2, possess the functionality of an STA while also providing the ability for coupled non-AP STAs (STA1 and STA4) to access the DS. Furthermore, since all APs are essentially STAs, all APs are addressable entities. The address used by the AP for communication on the WM and the address used by the AP for communication on the DSM (Data Storage System) do not necessarily have to be the same. A BSS consisting of an AP and one or more STAs can be called an infrastructure BSS.

[0041] Data transmitted from one of the STAs connected to an AP to the AP's STA address is always received on an uncontrolled port and may be processed by an IEEE 802.1X port access entity. Alternatively, once a controlled port is authenticated, the transmitted data (or frame) may be forwarded to a DS.

[0042] An Extended Service Set (ESS) may be added to the aforementioned DS structure to provide even broader coverage.

[0043] An ESS (Service Set Network) refers to a network of arbitrary size and complexity composed of DSs (Distributed Service Sets) and BSSs (Broadcasting Service Sets). An ESS can be a collection of BSSs connected to a single DS. However, an ESS cannot contain a DS. A key feature of an ESS network is that it appears as an IBSS (Information Baseline Service Set) at the LLC (Logical Link Control) layer. STAs (Stage Attendants) within an ESS can communicate with each other, and mobile STAs can move transparently to the LLC from one BSS to another (within the same ESS). APs (Access Points) within an ESS may have the same SSID (Service Set Identification). An SSID is distinct from a BSSID, which is the identifier for a BSS.

[0044] In wireless LAN systems, no assumptions are made regarding the relative physical location of BSSs, and any of the following forms are possible: BSSs may partially overlap, which is a commonly used form to provide continuous coverage. BSSs do not have to be physically connected, and logically there is no limit to the distance between BSSs. BSSs may also be located in the same physical location, which may be used to provide redundancy. One (or more) IBSS or ESS networks may physically exist in the same space as one (or more) ESS networks. This may include ESS network configurations when an ad hoc network operates in the location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required at the same location.

[0045] Figure 3 is a diagram illustrating the link setup process to which this disclosure can be applied.

[0046] For an STA to set up a link to a network and send and receive data, it must first discover the network, perform authentication, establish an association, and carry out security authentication procedures. The link setup process can be called the session initiation process or session setup process. Alternatively, the discovery, authentication, association, and security setting processes of the link setup process can be collectively referred to as the association process.

[0047] In step S310, the STA can perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network that it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks in a specific area is called scanning.

[0048] There are two scanning methods: active scanning and passive scanning. Figure 3 illustrates a network discovery operation that includes the active scanning process. In active scanning, the STA performing the scanning sends a probe request frame to search for nearby APs while moving between channels, and waits for a response. The responder sends a probe response frame to the STA that sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. In BSS, APs send beacon frames, so APs become the responders, while in IBSS, STAs within IBSS alternately send beacon frames, so the responders are not constant. For example, an STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 can save the BSS-related information contained in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (i.e., send and receive probe requests / responses on channel 2).

[0049] Although not shown in Figure 3, scanning may also be performed using a passive scanning method. In passive scanning, the STA performing the scanning waits for beacon frames while switching channels. A beacon frame is one of the management frames defined in IEEE 802.11, and is transmitted periodically to announce the presence of a wireless network, allowing the scanning STA to find and join the wireless network. In BSS, APs are responsible for periodically transmitting beacon frames, while in IBSS, STAs within IBSS transmit beacon frames alternately. When the scanning STA receives a beacon frame, it stores the BSS information contained in the beacon frame and records the beacon frame information on each channel while moving to other channels. An STA that has received a beacon frame can store the BSS-related information contained in the received beacon frame and move to the next channel to perform scanning on the next channel in the same way. Comparing active scanning and passive scanning, active scanning has the advantage of less delay and power consumption compared to passive scanning.

[0050] After the STA discovers the network, an authentication process may be performed in step S320. This authentication process can be called the first authentication process to clearly distinguish it from the security setup operation in step S340, which will be described later.

[0051] 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 in the authentication request / response corresponds to the management frame.

[0052] The authentication frame may include information such as the authentication algorithm number, authentication transaction sequence number, status code, challenge text, Robust Security Network (RSN), and Finite Cyclic Group. This is just an example of some of the information that may be included in the authentication request / response frame, and may be replaced by other information or may contain additional information.

[0053] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can decide whether or not to allow authentication to the STA. The AP can provide the STA with the result of the authentication process using an authentication response frame.

[0054] After the STA has been successfully authenticated, the association process may take place in step S330. The association process includes the STA sending an association request frame to the AP, and the AP sending an association response frame to the STA in response.

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

[0056] After the STA is successfully connected to the network, the security setup process may be performed in step S340. The security setup process in step S340 can also be described as an authentication process using RSNA (Robust Security Network Association) requests / responses, and the authentication process in step S320 can be called the first authentication process, while the security setup process in step S340 can simply be called the authentication process.

[0057] The security setup process in stage S340 may include, for example, a process of private key setup using a four-way handshake with an EAPOL (Extensible Authentication Protocol over LAN) frame. Furthermore, the security setup process may be performed using a security method not defined in the IEEE 802.11 standard.

[0058] Figure 4 is a diagram illustrating the backoff process to which this disclosure can be applied.

[0059] In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism is also called the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and basically employs a "listen before talk" access mechanism. With this type of access mechanism, an AP and / or STA can perform a Clear Channel Assessment (CCA) to sense the radio channel or medium within a predetermined time interval (e.g., DIFS Inter-Frame Space) before initiating transmission. If the sensing determines that the medium is idle, the AP and / or STA will begin transmitting a frame through that medium. On the other hand, if the medium is perceived as occupied or busy, the AP and / or STA will not begin transmitting itself, but will wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit a frame. By applying a random backoff period, multiple STAs are expected to attempt to transmit frames after waiting for different periods of time from each other, thus minimizing collisions.

[0060] Furthermore, the IEEE 802.11 MAC protocol provides HCF (Hybrid Coordination Function). HCF is based on the aforementioned DCF and PCF (Point Coordination Function). PCF is a polling-based synchronous access method that periodically polls so that all receiving APs and / or STAs can receive data frames. HCF also has EDCA (Enhanced Distributed Channel Access) and HCCA (HCF Controlled Channel Access). EDCA is a competition-based access method for a provider to provide data frames to multiple users, while HCCA uses a non-competition-based channel access method with a polling mechanism. In addition, HCF includes a media access mechanism to improve the QoS (Quality of Service) of wireless LANs and can transmit QoS data during both the Contention Period (CP) and the Contention Free Period (CFP).

[0061] Refer to Figure 4 to explain the operation based on the random backoff period. When a medium that was occupied / busy changes to idle, multiple STAs can attempt to transmit data (or frames). As a way to minimize collisions, each STA can select a random backoff count and wait for the corresponding slot time before attempting to transmit. The random backoff count has a pseudo-random integer value and may be determined to any one of the values ​​in the range of 0 to CW, where CW is the Contention Window parameter value. The CW parameter is initially given as CWmin, but can take twice that value in case of transmission failure (e.g., if an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, the STA can attempt to transmit data while maintaining the CWmax value until successful data transmission occurs, at which point it is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are 2 n It is preferable to set it to -1 (n=0,1,2,...).

[0062] Once the random backoff process begins, the STA continues to monitor the media while counting down the backoff slots according to the determined backoff count value. When the media is monitored as occupied, the countdown stops and it waits; when the media becomes idle, the remaining countdown resumes.

[0063] In the example in Figure 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit the frame after confirming that the medium is idle for DIFS only. The remaining STAs monitor the occupied / busy state of the medium and wait. Meanwhile, data to be transmitted may also be generated in STA1, STA2, and STA5. When each STA monitors the medium as idle, after waiting for DIFS only, it can count down the backoff slot using a random backoff count value of its choice. Assume that STA2 selects the minimum backoff count value and STA1 selects the maximum backoff count value. That is, the example illustrates a case where the remaining backoff time for STA5 is shorter than the remaining backoff time for STA1 when STA2 finishes its backoff count and begins transmitting a frame. STA1 and STA5 pause their countdown and wait for a while while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS only before resuming the paused backoff count. In other words, frame transmission can begin after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time was shorter than STA1's, STA5 begins frame transmission. Data to transmit may also occur in STA4 while STA2 is occupying the medium. From STA4's perspective, when the medium becomes idle, it can wait for DIFS, then count down using a random backoff count value of its choosing, and begin frame transmission. The example in Figure 4 shows a case where STA5's remaining backoff time coincidentally matches STA4's random backoff count value, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, and data transmission will fail. In this case, STA4 and STA5 can double their CW value, select a random backoff count value, and then perform the countdown.STA1 waits while the medium is occupied by transmissions from STA4 and STA5. When the medium becomes idle, STA1 waits only for DIFS time, and can start transmitting frames once the remaining backoff time has elapsed.

[0064] As illustrated in Figure 4, data frames are used to transmit data forwarded to higher layers and may be transmitted after a backoff that occurs after DIFS has elapsed, from the time the medium becomes idle. Furthermore, management frames are used to exchange management information that is not forwarded to higher layers and are transmitted after a backoff that occurs after an IFS such as DIFS or PIFS (Point Coordination Function IFS) has elapsed. Subtypes of management frames include beacons, association request / response, re-association request / response, probe request / response, and authentication request / response. Control frames are used to control access to the medium. Subtypes of control frames include RTS (Request-To-Send), CTS (Clear-To-Send), ACK (Acknowledgment), PS-Poll (Power Save-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), NDP Announcement (null data packet announcement), and Trigger. If a control frame is not a response frame to a previous frame, it is sent after a backoff that occurs after DIFS (Distributed Ingress Fault System), and if it is a response frame to a previous frame, it is sent after a short IFS (Shorter Ingress Fault System) without a backoff. The type and subtype of a frame may be identified by the type field and subtype field in the frame control (FC) field.

[0065] A Quality of Service (QoS) STA can transmit a frame after an arbitration IFS (AIFS) for the access category (AC) to which the frame belongs, i.e., after a backoff that occurs after AIFS[i] (where i is a value determined by the AC). Frames for which AIFS[i] is available can be data frames, management frames, or control frames that are not response frames.

[0066] Figure 5 is a diagram illustrating the CSMA / CA baseframe transmission operation to which this disclosure can be applied.

[0067] As mentioned earlier, the CSMA / CA mechanism includes not only physical carrier sensing, where the STA directly senses the medium, but also virtual carrier sensing. Virtual carrier sensing is intended to compensate for problems that can occur in medium access, such as the hidden node problem. For virtual carrier sensing, the STA's MAC can utilize the Network Allocation Vector (NAV). The NAV is a value that indicates to other STAs the time remaining until the medium becomes available, used by an STA that is currently using or authorized to use the medium. Therefore, the value set as the NAV corresponds to the period during which the STA sending the frame is scheduled to use the medium, and STAs receiving the NAV value are prohibited from accessing the medium during that period. For example, the NAV may be set based on the value of the "duration" field in the frame's MAC header.

[0068] In the example shown in Figure 5, we assume that STA1 is attempting to transmit data to STA2, and STA3 is in a position where it can overhear some or all of the frames transmitted and received between STA1 and STA2.

[0069] In CSMA / CA baseframe transmission operation, a mechanism utilizing RTS / CTS frames may be applied to reduce the possibility of collisions between transmissions from multiple STAs. In the example in Figure 5, while STA1 is transmitting, carrier sensing by STA3 may determine that the medium is idle. That is, STA1 may be a hidden node for STA3. Alternatively, in the example in Figure 5, while STA2 is transmitting, carrier sensing by STA3 may determine that the medium is idle. That is, STA2 may be a hidden node for STA3. By exchanging RTS / CTS frames before data transmission and reception between STA1 and STA2, it is possible to prevent STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, from attempting to occupy the channel during data transmission and reception between STA1 and STA2.

[0070] Specifically, STA1 can determine whether a channel is in use or not using carrier sensing. In terms of physical carrier sensing, STA1 can determine the channel's occupied or idle state based on the energy magnitude or signal correlation detected from the channel. In terms of virtual carrier sensing, STA1 can determine the channel's occupied state using a network allocation vector (NAV) timer.

[0071] STA1 can send an RTS frame to STA2 after backoff if the channel is idle during DIFS. STA2, upon receiving an RTS frame, can send a CTS frame, which is a response to the RTS frame, to STA1 after SIFS.

[0072] If STA3 cannot overhear CTS frames from STA2 but can overhear RTS frames from STA1, STA3 can use the duration information contained in the RTS frames to set the NAV timer for subsequent consecutive frame transmission periods (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear RTS frames from STA1 but can overhear CTS frames from STA2, STA3 can use the duration information contained in the CTS frames to set the NAV timer for subsequent consecutive frame transmission periods (e.g., SIFS + data frame + SIFS + ACK frame). In other words, STA3 can set NAV based on overhearing one or more RTS or CTS frames from at least one of STA1 or STA2. 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 will not attempt to access the channel until the NAV timer expires.

[0073] When STA1 receives a CTS frame from STA2, it can send a data frame to STA2 after SIFS from the time the CTS frame reception is complete. If STA2 successfully receives the data frame, it can send an ACK frame, which is a response to the data frame, to STA1 after SIFS. When the NAV timer expires, STA3 can use carrier sensing to determine whether the channel is in use or not. If STA3 determines that the channel is not being used by another terminal between the expiration of the NAV timer and DIFS, it can attempt to access the channel after the random backoff conflict window (CW) has passed.

[0074] Figure 6 is a diagram illustrating an example of a frame structure used in a wireless LAN system to which this disclosure can be applied.

[0075] The PHY layer can prepare the MPDU (MAC PDU) to be transmitted based on instructions or primitives (meaning a set of instructions or parameters) from the MAC layer. For example, when the PHY layer receives an instruction from the MAC layer requesting it to start transmitting, it switches to transmit mode and can assemble the information (e.g., data) provided by the MAC layer into a frame and transmit it. Also, when the PHY layer detects a valid preamble in the frame it is receiving, it monitors the preamble header and sends an instruction to the MAC layer to signal that the PHY layer has started receiving.

[0076] Thus, information transmission and reception in wireless LAN systems are performed in the form of frames, and for this purpose, the Physical Layer Protocol Data Unit (PPDU) frame format is defined.

[0077] A basic PPDU may include an STF (Short Training Field), an LTF (Long Training Field), a SIG (SIGNAL) field, and a Data field. The most basic (e.g., non-HT (High Throughput) PPDU format shown in Figure 7) may consist only of an L-STF (Legacy-STF), an L-LTF (Legacy-LTF), an L-SIG (Legacy-SIG) field, and a Data field. 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 other types of) RL-SIG, U-SIG, non-legacy SIG fields, 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 discussed later, referring to Figure 7.

[0078] STF is a signal used for signal detection, AGC (Automatic Gain Control), diversity selection, and precise time synchronization, while LTF is a signal used for channel estimation and frequency error estimation. In essence, STF and LTF are signals for synchronizing the OFDM physical layer and for channel estimation.

[0079] The SIG field may contain various information related to PPDU transmission and reception. For example, the L-SIG field consists 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 contain information about the data modulation and coding rate. For example, the 12-bit Length field may contain 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 PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the Length field may be determined to be a multiple of 3. For example, for HE PPDUs, the value of the Length field may be determined to be a multiple of 3 + 1 or a multiple of 3 + 2.

[0080] The data field may include a SERVICE field, a PSDU (Physical Layer Service Data Unit), and PPDU TAIL bits, and may also include padding bits if necessary. Some bits of the SERVICE field may be used for synchronizing the descramble at the receiving end. The PSDU corresponds to the MAC PDU defined in the MAC layer and may contain data generated / used in higher layers. The PPDU TAIL bits may be used to return the encoder to a 0 state. Padding bits may be used to adjust the length of the data field to a predetermined unit.

[0081] MAC PDUs are defined by various MAC frame formats, and a basic MAC frame consists of a MAC header, frame body, and FCS (Frame Check Sequence). MAC frames are composed of MAC PDUs and may be transmitted / received by a PSDU, which is the data portion of the PPDU format.

[0082] The MAC header includes fields such as Frame Control, Duration / ID, and Address. The Frame Control field may contain control information necessary for transmitting / receiving frames. The Duration / ID field may be set to the time required to transmit the frame. The Address subfield can indicate the frame's receiver address, transmitter address, destination address, and source address, and some Address subfields may be omitted. Sequence Control, QoS Control, and HT Control subfields are also included, and the specific contents of each subfield of the MAC header can be found in the IEEE 802.11 standard document.

[0083] The null data PPDU (NDP) format refers to a form of PPDU format that does not include data fields. In other words, NDP is a frame format that includes the PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and if present, also non-legacy SIG, non-legacy STF, and non-legacy LTF fields) in a general PPDU format, but does not include the rest (i.e., data fields).

[0084] Figure 7 shows an example of a PPDU as defined in the IEEE 802.11 standard to which this disclosure applies.

[0085] Standards such as IEEE 802.11a / g / n / ac / ax use various forms of PPDU. 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 (Figure 7(a)).

[0086] The HT PPDU format (IEEE 802.11n) further includes the HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format shown in Figure 7(b) can be referred to as the HT-mixed format. The HT-greenfield format PPDU may be further defined, which does not include L-STF, L-LTF, and L-SIG, and consists of the HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not shown).

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

[0088] An example of the HE PPDU format (IEEE 802.11ax) further includes the 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 (Figure 7(d)). Depending on the specific example of the HE PPDU format, some fields may be omitted or their lengths may change. For example, the HE-SIG-B field is included in the HE PPDU format for multiple users (MU), but not in the HE PPDU format for single users (SU). Also, the HE trigger-based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field may be changed to 8us. 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 may be changed to 16us. For example, RL-SIG may be configured identically to L-SIG. Based on the presence of RL-SIG, the receiving STA can determine that the received PPDU is either an HE PPDU or an EHT PPDU, as described later.

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

[0090] The EHT MU PPDU in Figure 7(e) corresponds to a carry PPDU that carries one or more data (or PSDUs) for one or more users. In other words, the EHT MU PPDU may be used for either SU transmission or MU transmission. For example, the EHT MU PPDU may correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0091] The EHT TB PPDU in Figure 7(f) omits the EHT-SIG compared to the EHT MU PPDU. An STA that receives 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.

[0092] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields may be encoded and modulated so that they can be attempted to be demodulated and decoded even by legacy STAs, and may be mapped based on a defined subcarrier frequency interval (e.g., 312.5 kHz). These may be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields may be encoded and modulated so that they can be demodulated and decoded by STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in those fields, and may be mapped based on a defined subcarrier frequency interval (e.g., 78.125 kHz). These may be referred to as EHT modulated fields.

[0093] Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields can be referred to as pre-HE modulated fields, while the HE-STF, HE-LTF, Data, and PE fields can be referred to as HE modulated fields. Furthermore, in the VHT PPDU format, the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields can be referred to as pre-VHT modulated fields, while the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields can be referred to as VHT modulated fields.

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

[0095] U-SIGs may be configured in 20MHz units. For example, when an 80MHz PPDU is configured, identical U-SIGs may be duplicated in 20MHz units. That is, an 80MHz PPDU may contain four identical U-SIGs. When the bandwidth exceeds 80MHz, for example, for a 160MHz PPDU, the first 80MHz U-SIG and the second 80MHz U-SIG may be different from each other.

[0096] In a U-SIG, for example, A uncoded bits may be transmitted, and the first U-SIG symbol (e.g., U-SIG-1 symbol) may transmit the first X bits of the total A bits, while the second U-SIG symbol (e.g., U-SIG-2 symbol) may transmit the remaining Y bits of the total A bits. The A bits (e.g., 52 uncoded bits) may include a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). The tail field may be used to terminate the trellis of the convolution decoder and may be set to 0, for example.

[0097] The A bit information transmitted by U-SIG can be distinguished into version-independent bits and version-dependent bits. For example, a new PPDU format not shown in Figure 7 (e.g., UHR PPDU format) may include U-SIG, and the format of the U-SIG field in the EHT PPDU format and the format of the U-SIG field in the UHR PPDU format may be the same, while the version-independent bits may differ in some or all respects.

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

[0099] For example, the version-independent bits of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier), which can indicate the PHY version of the transmitted and received PPDUs (e.g., EHT, UHR, etc.). 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 relates to DL communication. The version-independent bits of the U-SIG may also include information about the length of the TXOP (transmission opportunity) and information about the BSS color ID.

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

[0101] The U-SIG may include information necessary for transmitting and receiving PPDUs. For example, the U-SIG may further include information about bandwidth, information about the MCS technique applied to non-legacy SIGs (e.g., EHT-SIG or UHR-SIG), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique for reusing the same signal on two subcarriers to achieve an effect similar to frequency diversity) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, and information about whether the non-legacy SIG is generated across the entire bandwidth.

[0102] Some of the information necessary for sending and receiving PPDUs may be included in the U-SIG and / or non-legacy SIGs (e.g., EHT-SIG or UHR-SIG). For example, information regarding the type of non-legacy LTF / STF (e.g., EHT-LTF / EHT-STF or UHR-LTF / UHR-STF), information regarding the length and cyclic prefix (CP) length of non-legacy LTFs, information regarding the guard interval (GI) applicable to non-legacy LTFs, information regarding preamble puncturing applicable to PPDUs, and information regarding resource unit (RU) allocation may be included only in the U-SIG, only in the non-legacy SIG, or indicated by a combination of information included in the U-SIG and information included in the non-legacy SIG.

[0103] Preamble puncturing can mean the transmission of a PPDU in which one or more frequency units within the PPDU's bandwidth are not present. For example, the size of the frequency units (or the resolution of preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to PPDU bandwidths of a certain size or larger.

[0104] In the example shown in Figure 7, non-legacy SIGs such as HE-SIG-B and EHT-SIG may contain control information for the receiving STA. Non-legacy SIGs may be transmitted with at least one symbol, which may have a length of 4us. 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.).

[0105] Non-legacy SIGs such as HE-SIG-B and EHT-SIG may include common fields and user-specific fields. Common fields and user-specific fields may be coded separately.

[0106] In some cases, the common field may be omitted. For example, in a compressed mode where non-OFDMA (orthogonal frequency multiple access) is applied, the common field may be omitted, and multiple STAs can receive PPDUs (e.g., the data fields of the PPDU) in the same frequency band. In an uncompressed mode where OFDMA is applied, multiple users can receive PPDUs (e.g., the data fields of the PPDU) in separate frequency bands.

[0107] The number of user-specific fields may be determined based on the number of users. A single user block field may contain a maximum of two user fields. Each user field may be associated with either MU-MIMO or non-MU-MIMO assignments.

[0108] The common field may include a CRC bit and a Tail bit, the length of the CRC bit may be determined to be 4 bits, and the length of the Tail bit may be determined to be 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 assigned.

[0109] A RU may contain multiple subcarriers (or tones). RUs may be used when transmitting signals to multiple STAs based on the OFDMA method. Alternatively, a RU may be defined when transmitting a signal to a single STA. Resources may be allocated on a RU basis for non-legacy STFs, non-legacy LTFs, and Data fields.

[0110] The applicable size of RUs may be defined by the PPDU bandwidth. RUs may be defined to be identical or different for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, for an 80MHz PPDU, the RU arrangement for HE PPDU and EHT PPDU may differ from each other. The applicable RU size, number of RUs, RU locations, DC (direct current) subcarrier locations and number, null subcarrier locations and number, guard subcarrier locations and number, etc., for each PPDU bandwidth can be called a tone plan. For example, a tone plan for a wide bandwidth may be defined as multiple iterations of a low-bandwidth tone plan.

[0111] RUs of various sizes may be defined as 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, 996-tone RUs, 2×996-tone RUs, 3×996-tone RUs, etc. An MRU (multiple RU) is distinct from multiple individual RUs and corresponds to a group of subcarriers composed of multiple RUs. For example, one MRU may be defined as 52+26 tones, 106+26 tones, 484+242 tones, 996+484 tones, 996+484+242 tones, 2×996+484 tones, 3×996 tones, or 3×996+484 tones. Furthermore, the multiple RUs that make up a single MRU may or may not be consecutive in the frequency domain.

[0112] The specific size of a RU may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in this disclosure is illustrative and not restrictive. Also, in this disclosure, the number of RUs within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...) may vary depending on the size of the RU.

[0113] In the PPDU format shown in Figure 7, the names of the fields are illustrative and do not limit the scope of this disclosure. Furthermore, the examples in this disclosure may apply not only to the PPDU format illustrated in Figure 7, but also to new PPDU formats that are based on the PPDU format in Figure 7 but with some fields excluded and / or some fields added.

[0114] Preamble puncturing may be applied to the PPDU in Figure 7. Preamble puncturing means applying puncturing to a portion of the PPDU's total bandwidth (for example, a secondary 20MHz bandwidth). For example, when an 80MHz PPDU is transmitted, the STA can apply puncturing to the secondary 20MHz bandwidth of the 80MHz band, allowing the PPDU to be transmitted only in the primary 20MHz bandwidth and the secondary 40MHz bandwidth.

[0115] For example, the preamble puncturing pattern may be pre-set. For example, if the first puncturing pattern is applied, puncturing may be applied only to the secondary 20MHz band within the 80MHz band. For example, if the second puncturing pattern is applied, puncturing may be applied only to one of the two secondary 20MHz bands included in the secondary 40MHz band within the 80MHz band. For example, if the third puncturing pattern is applied, puncturing may be applied only to the secondary 20MHz band included in the primary 80MHz band within the 160MHz band (or 80+80MHz band). For example, if the fourth puncturing pattern is applied, the primary 40MHz band included in the primary 80MHz band within the 160MHz band (or 80+80MHz band) is present, and puncturing may be applied to at least one 20MHz channel that does not belong to the primary 40MHz band.

[0116] Information regarding preamble puncturing applicable to the PPDU may be included in the U-SIG and / or EHT-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applicable to the PPDU.

[0117] For example, the U-SIG and EHT-SIG may include information about preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIGs may be configured individually in 80 MHz units. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information about the 160 MHz bandwidth, and the second field of the first U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). The first field of the second U-SIG may include information about the 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). The EHT-SIG following the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern), and the EHT-SIG following the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern).

[0118] As an addition or alternative, the U-SIG and EHT-SIG may include information on preamble puncturing based on the following methods: The U-SIG may include information on preamble puncturing for all bands (i.e., information on preamble puncturing patterns). That is, the EHT-SIG may not include information on preamble puncturing, and only the U-SIG may include information on preamble puncturing (i.e., information on preamble puncturing patterns).

[0119] U-SIGs may be configured in 20MHz units. For example, when an 80MHz PPDU is configured, U-SIGs may be duplicated. That is, an 80MHz PPDU may contain four identical U-SIGs. PPDUs with a bandwidth exceeding 80MHz may contain different U-SIGs.

[0120] The EHT-SIG in Figure 7 may contain control information for the receiving STA. The EHT-SIG may be transmitted with at least one symbol, which may have a length of 4us. Information regarding the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0121] EHT-SIG may include the technical features of HE-SIG-B described above. For example, EHT-SIG may include common fields and user-specific fields. Common fields in EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0122] The common fields and user-specific fields of the EHT-SIG may be coded separately. One user block field contained within a user-specific field contains information for two user fields, but the last user block field contained within a user-specific field may contain one or two user fields. That is, one user block field of the EHT-SIG may contain a maximum of two user fields. Each user field may be related to MU-MIMO assignment or non-MU-MIMO assignment.

[0123] The common field of the EHT-SIG may include a CRC bit and a Tail bit, the length of the CRC bit may be determined to be 4 bits, and the length of the Tail bit may be determined to be 6 bits and set to 000000.

[0124] The common fields of the EHT-SIG may include RU allocation information. RU allocation information can represent information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are assigned. RU allocation information may be composed of 8-bit (or N-bit) units.

[0125] A mode in which the common field of the EHT-SIG is omitted may be supported. This mode in which the common field of the EHT-SIG is omitted may be called compressed mode. When compressed mode is used, multiple users of the EHT PPDU (i.e., multiple receiving STAs) can decode the PPDU (e.g., the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) received in the same frequency band. When non-compressed mode is used, multiple users of the EHT PPDU can decode the PPDU (e.g., the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU can receive the PPDU (e.g., the data field of the PPDU) in different frequency bands.

[0126] The EHT-SIG may be configured based on various MCS techniques. As mentioned above, information related to the MCS technique applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be configured based on a DCM technique. For example, of the N data tones allocated for the EHT-SIG (e.g., 52 data tones), a first modulation technique may be applied to half of the consecutive tones, and a second modulation technique may be applied to the remaining half of the consecutive tones. That is, the transmitting STA can modulate specific control information to a first symbol based on the first modulation technique and assign it to half of the consecutive tones, and modulate the same control information to a second symbol based on the second modulation technique and assign it to the remaining half of the consecutive tones. As mentioned above, information related to whether or not a DCM technique is applied to the EHT-SIG (e.g., a 1-bit field) may be included in the U-SIG. The EHT-STF in Figure 7 may be used to improve automatic gain control (AGC) estimation in a MIMO or OFDMA environment. The EHT-LTF in Figure 7 may be used to estimate the channel in a MIMO or OFDMA environment.

[0127] Information regarding the type of STF and / or LTF (including information regarding the GI (guard interval) applied to the LTF) may be included in the U-SIG field and / or EHT-SIG field in Figure 7, etc.

[0128] The PPDU in Figure 7 (i.e., the EHT PPDU) may be configured based on the example RU configurations shown in Figures 9 to 11.

[0129] For example, an EHT PPDU transmitted over a 20MHz bandwidth, i.e., a 20MHz EHT PPDU, may be configured based on the RUs in Figure 9. That is, the locations of the RUs for the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in Figure 9. An EHT PPDU transmitted over a 40MHz bandwidth, i.e., a 40MHz EHT PPDU, may be configured based on the RUs in Figure 10. That is, the locations of the RUs for the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in Figure 10.

[0130] An EHT PPDU transmitted over the 80 MHz band, i.e., an 80 MHz EHT PPDU, may be constructed based on the RUs in Figure 11. That is, the locations of the RUs for the EHT-STF, EHT-LTF, and data field included in the EHT PPDU may be determined as shown in Figure 11. The tone-plan for 80 MHz in Figure 11 may correspond to two iterations of the tone-plan for 40 MHz in Figure 10.

[0131] The tone plan for 160 / 240 / 320MHz may consist of multiple repetitions of the pattern shown in Figure 10 or Figure 11.

[0132] The PPDU in Figure 7 may be identified as an EHT PPDU based on the following method.

[0133] The receiving STA can determine the type of the received PPDU to be an EHT PPDU based on the following: For example, the received PPDU may be determined to be an EHT PPDU if 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) an RL-SIG is detected in which the L-SIG of the received PPDU is repeated, and 3) the result of applying a modulo 3 operation to the value of the Length field of the L-SIG of the received PPDU (i.e., the remainder when divided by 3) is detected as 0. When the received PPDU is determined to be an EHT PPDU, the receiving STA can determine the type of the EHT PPDU based on the bit information contained in the symbol after the RL-SIG in Figure 7. In other words, the receiving STA can determine the received PPDU to be an EHT PPDU based on 1) the first symbol after the L-LTF signal which is BSPK, 2) an RL-SIG that is consecutive to the L-SIG field and is the same as the L-SIG, and 3) an L-SIG that contains a Length field in which the result of applying modulo 3 is set to 0.

[0134] For example, a receiving STA can determine the type of the received PPDU to be HE PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, 2) an RL-SIG is detected in which L-SIG is repeated, and 3) the result of applying modulo 3 to the Length value of L-SIG is detected as 1 or 2, then the received PPDU may be determined to be HE PPDU.

[0135] For example, the receiving STA can determine the type of the received PPDU to be non-HT, HT, or VHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) no RL-SIG (where L-SIG is repeated) is detected, the received PPDU may be determined to be non-HT, HT, or VHT PPDU. Also, even if the receiving STA detects a repetition of RL-SIG, if the result of applying modulo 3 to the Length value of L-SIG is detected as 0, the received PPDU may be determined to be non-HT, HT, or VHT PPDU.

[0136] The PPDU in Figure 7 may be used to send and receive various types of frames. For example, the PPDU in Figure 7 may be used to send and receive one or more control frames, management frames, or data frames (simultaneously).

[0137] trigger frame

[0138] Figure 8 shows an exemplary format of a trigger frame to which this disclosure may apply.

[0139] A trigger frame can allocate resources for one or more TB PPDU transmissions and request TB PPDU transmissions. The trigger frame may also include other information requested by the STA that will transmit the TB PPDU in response. The trigger frame may include a common info field and a user info list field in its frame body.

[0140] The common information field may include information that applies in common to one or more TB PPDU transmissions requested by a trigger frame, such as the trigger type, UL length, whether or not there is a subsequent trigger frame (e.g., More TF), whether or not a CS (channel sensing) request is made, and UL BW (bandwidth).

[0141] The user information list contains zero or more user info fields. Figure 8 illustrates the EHT variant user info field format.

[0142] The AID12 subfield essentially indicates that it is a user information field for the STA having that AID. It may also be used for other purposes, such as assigning a Random Access (RA)-RU when the AID12 field has a predetermined specific value, or being configured as a special user info field. A special user info field does not contain user-specific information but is a user information field that includes extended common information not provided in the common information field. For example, a special user info field may be identified by the AID12 value 2007, and a special user info field flag subfield within the common information field may indicate whether or not it contains a special user info field.

[0143] The RU allocation subfield can indicate the size and location of the RU / MRU. For this purpose, the RU allocation subfield may be parsed together with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc. For example, as shown in Table 1 below, the mapping of B7-B1 of the RU allocation subfield may be defined together with the settings of the B0 and PS160 subfields of the RU allocation subfield. Table 1 shows an example of encoding for the PS160 subfield and RU allocation subfield of the EHT variant user information field.

[0144] [Table 1]

[0145] JPEG2026513926000003.jpg4593

[0146] JPEG2026513926000004.jpg21494

[0147] JPEG2026513926000005.jpg4188

[0148] If the PS160 subfield is 0 and the RU / MRU size is 996 tones or less, setting B0 in the RU allocation subfield to 0 indicates that the RU / MRU allocation is applied to the primary 80MHz channel, and setting its value to 1 indicates that the RU allocation is applied to the secondary 80MHz channel of the primary 160MHz. On the other hand, if the PS160 subfield is 1 and the RU / MRU size is 996 tones or less, setting B0 in the RU allocation subfield to 0 indicates that the RU / MRU allocation is applied to the lower 80MHz of the secondary 160MHz, and setting its value to 1 indicates that the RU allocation is applied to the upper 80MHz of the secondary 160MHz.

[0149] In the trigger frame RU assignment table in Table 1, the parameter N may be calculated based on the formula N = 2 * X1 + X0. For bandwidths of 80 MHz or less, the PS160, B0, X0, and X1 values ​​may be set to 0. For 160 MHz and 320 MHz bandwidths, the PS160, B0, X0, and X1 values ​​may be set as shown in Table 2. Such settings represent the absolute frequency order for the primary and secondary 80 MHz and 160 MHz channels. The left-to-right order represents the order from lower frequencies to higher frequencies. The primary 80 MHz channel is denoted as P80, the secondary 80 MHz channel as S80, and the secondary 160 MHz channel as S160.

[0150] [Table 2]

[0151] Resource unit (RU) and resource allocation

[0152] Figures 9 to 11 illustrate examples of resource units in a wireless LAN system to which this disclosure can be applied.

[0153] Referring to Figures 9 to 11, a resource unit (RU) defined in a wireless LAN system will be explained. An RU may contain multiple subcarriers (or tones). An RU may be used when transmitting a signal to multiple STAs based on the OFDMA method. An RU may also be defined when transmitting a signal to a single STA. An RU may be used for the STF, LTF, data field, etc., of a PPDU.

[0154] As shown in Figures 9 to 11, RUs corresponding to different numbers of tones (i.e., subcarriers) can be used to constitute some fields of a 20MHz, 40MHz, or 80MHz X-PPDU (where X is HE, EHT, etc.). For example, resources may be allocated in units of RU shown for the X-STF, X-LTF, and Data fields.

[0155] Figure 9 shows an example of resource unit (RU) configuration used in the 20 MHz bandwidth.

[0156] As shown at the top of Figure 9, 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 20MHz band, and five tones may be used as a guard band in the rightmost band of the 20MHz 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 be present on the left and right sides of the DC band. Furthermore, 26, 52, or 106 units may be allocated to the other bands. Each unit may be allocated for the STA or the user.

[0157] The RU configuration in Figure 9 can be used not only for situations involving multiple users (MU) but also for situations involving a single user (SU), in which case it is possible to use one 242 unit, as shown at the bottom of Figure 9. In this case, three DC tones may be inserted.

[0158] In the example in Figure 9, various sizes of RUs are illustrated, namely 26 RU, 52 RU, 106 RU, 242 RU, etc., but the specific sizes of such RUs may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in this disclosure is illustrative and not restrictive. Also, in this disclosure, the number of RUs may be changed depending on the RU size within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...). The fact that the size and / or number of RUs can be changed in the examples in Figure 10 and / or Figure 11 described below is the same as in the example in Figure 9.

[0159] Figure 10 shows an example arrangement of resource units (RUs) used in the 40 MHz bandwidth.

[0160] Just as various sizes of RU are used in the example in Figure 9, 26 RU, 52 RU, 106 RU, 242 RU, 484 RU, etc., may be used in the example in Figure 10. 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.

[0161] Furthermore, as shown in the diagram, 484 RU may be used when it is used for a single user.

[0162] Figure 11 shows an example of resource unit (RU) configuration used in the 80 MHz bandwidth.

[0163] Just as various sizes of RUs were used in the examples in Figures 9 and 10, 26 RUs, 52 RUs, 106 RUs, 242 RUs, 484 RUs, 996 RUs, etc., may be used in the example in Figure 11. Furthermore, in the 80MHz PPDU, the RU arrangement of the HE PPDU and EHT PPDU may differ from each other, and the example in Figure 11 shows an example of the RU arrangement for the 80MHz EHT PPDU. In the example in Figure 11, the leftmost band of the 80MHz bandwidth uses 12 tones as a guard band, and the rightmost band of the 80MHz bandwidth uses 11 tones as a guard band, which is the same for both the HE PPDU and the EHT PPDU. Unlike the HE PPDU, where seven DC tones are inserted into the DC band and there are 13 tones on each side of the DC band (one 26 RU), the EHT PPDU has 23 DC tones inserted into the DC band, with one 26 RU on each side of the DC band. Unlike the HE PPDU, where there is one null subcarrier between the 242 RUs outside the center band, the EHT PPDU has five null subcarriers. In the HE PPDU, one 484 RU does not contain null subcarriers, but in the EHT PPDU, one 484 RU contains five null subcarriers.

[0164] Furthermore, as shown in the diagram, the 996 RU may be used when used for a single user, and in this case, five DC tones are inserted, which is common to both the HE PPDU and the EHT PPDU.

[0165] EHT PPDUs of 160 MHz or higher may be configured as multiple 80 MHz subblocks as shown in Figure 11. The RU configuration for each 80 MHz subblock may be the same as the RU configuration for the 80 MHz EHT PPDU in Figure 11. When the 80 MHz subblock of a 160 MHz or 320 MHz EHT PPDU is not punctured, and the entire 80 MHz subblock is used as part of an RU or MRU (Multiple RU), the 80 MHz subblock can use the 996 RUs shown in Figure 11.

[0166] Here, an MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs constituting an MRU may be of the same size or of 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, 2×996+484 tones, 3×996 tones, or 3×996+484 tones. Here, the multiple RUs constituting a single MRU may be small-sized (e.g., 26, 52, 106) RUs, or large-sized (e.g., 242, 484, 996, etc.) RUs. In other words, a single MRU containing both small-sized and large-sized RUs does not need to be set / defined. Also, the multiple RUs constituting a single MRU may be contiguous or non-contiguous in the frequency domain.

[0167] If the 80MHz subblock contains RUs smaller than 996 tones, or if a portion of the 80MHz subblock is punctured, the 80MHz subblock may use an RU arrangement that excludes the 996-tone RU.

[0168] The location of the RU may be fixed according to the respective PPDU bandwidth, as defined in Tables 3 to 7 below.

[0169] Table 3 illustrates the index of RUs within a 20MHz PPDU, the data for each RU, and the pilot subcarrier index (range).

[0170] [Table 3]

[0171] Table 4 illustrates the RU index within a 40MHz PPDU, along with the data and pilot subcarrier index (range) for each RU.

[0172] [Table 4]

[0173] Table 5 illustrates the RU index within the 80MHz PPDU, along with the data and pilot subcarrier index (range) for each RU.

[0174] [Table 5]

[0175] Table 6 illustrates the RU index within the 160MHz PPDU, along with the data and pilot subcarrier index (range) for each RU.

[0176] [Table 6]

[0177] JPEG2026513926000011.jpg186146

[0178] Table 7 illustrates the RU index within the 320MHz PPDU, along with the data and pilot subcarrier index (range) for each RU.

[0179] [Table 7]

[0180] JPEG2026513926000013.jpg205145

[0181] JPEG2026513926000014.jpg204147

[0182] JPEG2026513926000015.jpg74143

[0183] In Table 3, RU5 corresponds to the middle 26 tone RU.

[0184] Referring to Tables 3 to 7, a subcarrier index of 0 corresponds to a DC tone. Negative subcarrier indices correspond to subcarriers with lower frequencies than the DC tone. Positive subcarrier indices correspond to subcarriers with higher frequencies than the DC tone. A DC subcarrier can be defined as a subcarrier with an energy of 0 that includes subcarrier indices adjacent to the DC tone and subcarrier index 0 (i.e., the DC tone). A guard subcarrier can be defined as a subcarrier located at the edge of the OFDM symbol in the frequency domain and with an energy of 0. A null subcarrier is located near a DC or edge tone, protects against transmission center frequency leakage, receiver DC offset, and interference from adjacent RUs or MRUs, and has an energy of 0.

[0185] Referring to Figures 9 to 11 and Tables 3 to 7, the RU index may be assigned to each RU in order from the lowest frequency to the highest frequency.

[0186] A PPDU in the 160MHz and above range may consist of multiple 80MHz frequency subblocks. The tone plan and RU allocation for each of the 80MHz frequency subblocks may be the same as those for the 80MHz PPDU. When the 80MHz frequency subblock of a 160MHz or 320MHz PPDU is not punctured and the entire 80MHz frequency subblock is used as an RU or as part of an RU / MRU, the 80MHz frequency subblock may use the 996-tone RU as illustrated in Figure 10. If the 80MHz frequency subblock contains fewer than 996 tone RUs, or if part of the 80MHz frequency subblock is punctured, the 80MHz frequency subblock may use a tone plan and RU allocation excluding the 996-tone RU, as illustrated in Figure 10.

[0187] Multiple RUs (MRUs) may be assigned to an STA. The subcarrier index of an MRU may consist of the indices of the RUs that make up the MRU.

[0188] The RUs of this disclosure may be used for uplink (UL) and / or downlink (DL) communication. For example, in the case of trigger-based UL-MU communication, an STA (e.g., AP) transmitting a trigger may use trigger information (e.g., trigger frame or TRS (triggered response scheduling)) to assign a first RU (e.g., 26 / 52 / 106 / 242 RU) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242 RU) to a second STA. The first STA can then 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 and second TB PPDUs may be transmitted to the AP in the same time interval.

[0189] For example, when DL MU PPDU is configured, an STA (e.g., AP) sending the DL MU PPDU can assign the first RU (e.g., 26 / 52 / 106 / 242 RU) to the first STA and the second RU (e.g., 26 / 52 / 106 / 242 RU) to the second STA.

[0190] EHT-SIG Field

[0191] A 20MHz EHT MU PPDU's EHT-SIG field contains one EHT-SIG content channel. For OFDMA transmission and non-OFDMA transmission to multiple users, an EHT MU PPDU that is 40MHz or 80MHz contains two EHT-SIG content channels in its EHT-SIG field. For OFDMA transmission and non-OFDMA transmission to multiple users, an EHT MU PPDU that is 160MHz or higher contains two EHT-SIG content channels per 80MHz frequency subblock in its EHT-SIG field. When the EHT MU PPDU bandwidth for OFDMA transmission is wider than 80MHz, the EHT-SIG content channels per 80MHz frequency subblock can transmit different information from each other.

[0192] Each EHT-SIG content channel may consist of a common field and a user-specific field, where the common field may include one or two RU assignment subfields depending on the PPDU frequency bandwidth.

[0193] In OFDMA transmission, the common field of the EHT-SIG content channel may include information regarding RU allocation, such as the RU allocation used in the PPDU's EHT modulation field, the RU allocated to MU-MIMO, and the number of users in the MU-MIMO allocation. When the bandwidth is 20 / 30 / 80 MHz, the common field may consist of one common encoding block, which may contain one or two RU allocation-A subfields. When the bandwidth is 160 MHz, the common field may consist of two common encoding blocks, the first of which may contain two RU allocation-A subfields, and the second of which may contain two RU allocation-B subfields. When the bandwidth is 320 MHz, the common field may consist of two common encoding blocks, the first of which may contain two RU allocation-A subfields, and the second of which may contain six RU allocation-B subfields.

[0194] In Non-OFDMA transmission, the common fields of the EHT-SIG content channel do not need to include RU assignment subfields.

[0195] Each RU assignment A subfield of the EHT-SIG content channel corresponding to the 20MHz frequency subchannel can indicate RU or MRU assignment, including the size of the RU / MRU and its placement in the frequency domain. Each RU assignment A subfield can also indicate the information necessary to calculate the number of users assigned to each RU / MRU.

[0196] Each RU assignment B subfield of the EHT-SIG content channel corresponding to the 20MHz frequency subchannel can indicate RU or MRU assignment, including the size of the RU / MRU and its placement in the frequency domain. Each RU assignment B subfield can also indicate the information necessary to calculate the number of users assigned to each RU / MRU.

[0197] Both RU assignment A subfield and RU assignment B subfield may refer to RU assignment subfields located in different common encoding blocks.

[0198] In OFDMA transmissions wider than 80MHz, the RU allocation subfield per 80MHz frequency subblock can transmit consistent RU or MRU size and placement information for the entire PPDU.

[0199] Table 8 illustrates the number of user fields per RU or MRU related to the user-specific field within the same EHT SIG content channel as the mapping to the RU allocation in the 9-bit RU allocation subfield.

[0200] [Table 8]

[0201] JPEG2026513926000017.jpg208147

[0202] JPEG2026513926000018.jpg199145

[0203] JPEG2026513926000019.jpg194146

[0204] JPEG2026513926000020.jpg44143

[0205] Referring to Table 8, in RU allocation subfields with a value of 64 or more, y2y1y0 = 000 - 111 indicates the number of user fields in the EHT-SIG content channel that contain the 9-bit RU allocation subfield. The binary vector y2y1y0 indicates the number of user fields in the EHT-SIG content channel that contain the 9-bit RU allocation subfield. user (r,c)=2 2 ×y 2 +2 1 ×y 1 +y 0 Specify +1 user field.

[0206] In Table 8, the Number of Entries column can represent the number of RU assignment subfield values ​​that refer to the same RU assignment used in the frequency domain. However, different RU assignment subfield values ​​may result in different numbers of user fields being included in the same EHT-SIG content channel user-specific fields as this RU assignment subfield.

[0207] In Table 8, if there is a value designated as disregard in the RU assignment subfield, STA is N indicated by the subfield value. user (r,c) user fields can be skipped and the EHT-SIG field can be processed continuously.

[0208] Table 9 illustrates the RUs or MRUs associated with each RU allocation subfield for each EHT-SIG content channel and PPDU bandwidth.

[0209] [Table 9]

[0210] JPEG2026513926000022.jpg141145

[0211] Table 10 illustrates the null subcarrier index for each RU size when the channel bandwidth is 20 MHz and 40 MHz.

[0212] [Table 10]

[0213] Table 11 illustrates the null subcarrier indices for each RU size when the channel bandwidth is 80 MHz, 160 MHz, and 320 MHz.

[0214] [Table 11]

[0215] Distributed RU (DRU) allocation method

[0216] Regional regulations limit the power spectral density (PSD) in the 7GHz and below band.

[0217] Here, the PSD limit is even stricter in the 6GHz band, with a PSD limit of -1dBm / MHz for non-AP STA in the low-power indoor (LPI) band. In the case of 52-tone RU, the maximum transmission power is approximately 6dBm. In other words, the PSD limit prevents the transmission power from being increased to the maximum transmission power.

[0218] Regulations in each region can affect the limitations on the 2.4GHz and 5GHz bands. For example, in Europe, China, Japan, and South Korea, a 10dBm / MHz PSD limit is applied to the 2.4GHz band. In this case, with 52 tone RUs, the maximum transmission power is approximately 17dBm.

[0219] If the PSD limit can be avoided even in the 5GHz band, the transmission power can be increased. In the case of 52 tone RU, the maximum transmission power is currently about 24dBm, which is 6dB away from the maximum allowable effective isotropically radiated power (EIRP) of 30dBm.

[0220] As described above, overcoming the PSD limitation can improve transmission power and thus enhance spectral efficiency or range extension.

[0221] Here, the aforementioned PSD limits are defined per MHz and per STA. That is, if small RU tones are distributed across a wide bandwidth, the tones of each STA will no longer be continuous, and therefore each tone may be transmitted at a higher power.

[0222] For the sake of clarity, in this disclosure, RUs defined as continuous tones in existing WLAN systems (e.g., IEEE 802.11ax, IEEE 802.11be, etc.) may be referred to as regular RUs (RRUs), and RUs defined as distributed (i.e., non-continuous) tones may be referred to as distributed tones RUs (DRUs). However, this is merely an example, and this disclosure is not limited to such terminology.

[0223] In the case of an STA transmitting a DRU, it is possible to transmit at higher power compared to an RRU. For example, in an 80MHz bandwidth, a 52-tone DRU requires only one tone per MHz. On the other hand, a 52-tone RRU requires approximately 13 tones per MHz. In the 6GHz LPI bandwidth, the PSD limit is -1dBm / MHz, so with a 52-tone RU, using a DRU can increase the transmission power by up to 11dB. Such a substantial transmission power boost enables higher MCS, allowing the signal to reach over longer ranges.

[0224] Figure 12 illustrates the application of distributed tone RUs in a wireless LAN system to which this disclosure can be applied.

[0225] Referring to Figure 12, STA1 can transmit UL OFDMA PPDU using DRU1, STA2 can transmit UL OFDMA PPDU using DRU2, and STA3 can transmit UL OFDMA PPDU using DRU3. Here, STA1, STA2, and STA3 can all boost their transmission power by using DRUs. Thus, DRUs can be particularly useful for UL-OFDMA.

[0226] To maximize power boost, the tones within a single DRU should be as widely distributed as possible. For example, 1 tone / MHz would suffice. Furthermore, to avoid additional complexity, the DRU size should be kept identical to the RRU size.

[0227] Table 12 illustrates the power boost achievable for various DRUs across different bandwidths.

[0228] [Table 12]

[0229] Thus, DRUs can overcome the PSD limit and provide a considerable gain. For example, in an 80MHz UL-OFDMA transmission with eight users, if each user uses a 106-tone DRU, the overall performance can be improved by 8.13dB compared to each user using a 106-tone RRU. As mentioned above, in wireless LAN systems (802.11), RUs that use distributed tones instead of continuous tones (i.e., distributed tones RU (DRU)) may be defined to overcome the PSD constraint and obtain better power gain.

[0230] This disclosure proposes a method for mapping a DRU tone plan defined on an 80MHz channel, with preamble puncturing taken into account, to an existing tone plan (i.e., an RRU tone plan). This is to reduce implementation complexity by making maximum use of existing signaling during DRU allocation.

[0231] In the following descriptions of this disclosure, "subcarrier" may be interpreted as having the same meaning as "tone" unless explicitly distinguished otherwise.

[0232] Referring again to Figure 11, Figure 11 illustrates an existing 80 MHz tone plan when RRU is used.

[0233] As shown in Figure 11, a relatively large RRU may be constructed from a combination of relatively small RRUs, and similarly, a relatively large DRU may be constructed from a combination of relatively small DRUs. Taking this into consideration, the following DRU tone plan may be applied.

[0234] Hereinafter, this disclosure proposes an 80MHz DRU tone plan in a situation where a specific 20MHz channel is punctured. This defines the DRU with the same RU size and number of tones as when a single 20MHz channel is punctured from an existing 80MHz RRU tone plan (except for 996 DRU), and assumes that the same number and positions of guard / null / DC tones as in the existing plan are used.

[0235] In the following explanation, the notation "DRU-x" means that the DRU index is x.

[0236] A. 26 DRU index (i.e., 26 DRU tone plan)

[0237] 1) In the case of the first 20MHz puncturing: Except for the first 20MHz channel that is punctured in the 80MHz bandwidth, the available tones in the frequency domain may be assigned one tone at a time, starting from the lowest frequency available tone and going up to the highest frequency available tone, for a total of 27 tones of 26 RU each. Here, for example, the first 20MHz channel can mean the first 20MHz channel when considering the four 20MHz channels in the 80MHz bandwidth in ascending frequency order of the frequency domain.

[0238] The following are examples of subcarrier indices (tone indices) that make up each of the 26 DRUs.

[0239] - 26 DRU-1: -252 -225 -196 -169 -141 -113 -86 -57 -30 22 49 78 105 133 161 188 217 244 278 305 334 361 389 417 444 473

[0240] - 26 DRU-2: -251 -224 -195 -168 -140 -112 -85 -56 -29 23 50 79 106 134 162 189 218 245 279 306 335 362 390 418 445 474

[0241] - 26 DRU-3: -250 -223 -194 -167 -139 -111 -84 -55 -28 24 51 80 107 135 163 190 219 246 280 307 336 363 391 419 448 475

[0242] - 26 DRU-4: -249 -222 -193 -166 -138 -110 -83 -54 -27 25 52 81 108 136 164 191 220 247 281 308 337 364 392 420 449 476

[0243] - 26 DRU-5: -248 -221 -192 -165 -137 -109 -82 -53 -26 26 53 82 109 137 165 192 221 248 282 309 338 365 394 421 450 477

[0244] - 26 DRU-6: -247 -220 -191 -164 -136 -108 -81 -52 -25 27 54 83 110 138 166 193 222 249 283 310 339 367 395 422 451 478

[0245] - 26 DRU-7: -246 -219 -190 -163 -135 -107 -80 -51 -24 28 55 84 111 139 167 194 223 250 284 311 340 368 396 423 452 479

[0246] - 26 DRU-8: -245 -218 -189 -162 -134 -106 -79 -50 -23 29 56 85 112 140 168 195 224 251 285 314 341 369 397 424 453 480

[0247] - 26 DRU-9: -244 -217 -188 -161 -133 -105 -78 -49 -22 30 57 86 113 141 169 196 225 252 286 315 342 370 398 425 454 481

[0248] - 26 DRU-10: -243 -216 -187 -160 -132 -104 -77 -48 -21 31 58 87 114 142 170 197 226 260 287 316 343 371 399 426 455 482

[0249] - 26 DRU-11: -242 -215 -186 -159 -131 -103 -76 -47 -20 32 59 88 115 143 171 198 227 261 288 317 344 372 400 427 456 483

[0250] - 26 DRU-12: -241 -214 -185 -158 -130 -102 -75 -46 -19 33 60 89 116 144 172 201 228 262 289 318 345 373 401 428 457 484

[0251] - 26 DRU-13: -240 -213 -184 -157 -129 -101 -74 -45 -18 34 61 90 117 145 173 202 229 263 290 319 346 374 402 429 458 485

[0252] - 26 DRU-14: -239 -212 -183 -156 -128 -100 -73 -44 -17 35 62 91 118 147 174 203 230 264 291 320 347 375 403 430 459 486

[0253] - 26 DRU-15: -238 -211 -182 -155 -127 -99 -72 -43 -16 36 63 92 120 148 175 204 231 265 292 321 348 376 404 431 460 487

[0254] - 26 DRU-16: -237 -210 -181 -154 -126 -98 -71 -42 -15 37 64 93 121 149 176 205 232 266 293 322 349 377 405 432 461 488

[0255] - 26 DRU-17: -236 -209 -180 -153 -125 -97 -70 -41 -14 38 67 94 122 150 177 206 233 267 294 323 350 378 406 433 462 489

[0256] - 26 DRU-18: -235 -208 -179 -152 -124 -96 -69 -40 -13 39 68 95 123 151 178 207 234 268 295 324 351 379 407 434 463 490

[0257] - 26 DRU-19: -234 -207 -178 -151 -123 -95 -68 -39 13 40 69 96 124 152 179 208 235 269 296 325 352 380 408 435 464 491

[0258] - 26 DRU-20: -233 -206 -177 -150 -122 -94 -67 -38 14 41 70 97 125 153 180 209 236 270 297 326 353 381 409 436 465 492

[0259] - 26 DRU-21: -232 -205 -176 -149 -121 -93 -64 -37 15 42 71 98 126 154 181 210 237 271 298 327 354 382 410 437 466 493

[0260] - 26 DRU-22: -231 -204 -175 -148 -120 -92 -63 -36 16 43 72 99 127 155 182 211 238 272 299 328 355 383 411 438 467 494

[0261] - 26 DRU-23: -230 -203 -174 -147 -118 -91 -62 -35 17 44 73 100 128 156 183 212 239 273 300 329 356 384 412 439 468 495

[0262] - 26 DRU-24: -229 -202 -173 -145 -117 -90 -61 -34 18 45 74 101 129 157 184 213 240 274 ​​301 330 357 385 413 440 469 496

[0263] - 26 DRU-25: -228 -201 -172 -144 -116 -89 -60 -33 19 46 75 102 130 158 185 214 241 275 302 331 358 386 414 441 470 497

[0264] - 26 DRU-26: -227 -198 -171 -143 -115 -88 -59 -32 20 47 76 103 131 159 186 215 242 276 303 332 359 387 415 442 471 498

[0265] - 26 DRU-27: -226 -197 -170 -142 -114 -87 -58 -31 21 48 77 104 132 160 187 216 243 277 304 333 360 388 416 443 472 499

[0266] 2) For the second 20 MHz puncturing: Excluding the second 20 MHz channel punctured in the 80 MHz bandwidth, starting from the lowest available tone in the frequency domain to the highest available tone, 27 tones may be assigned one by one to each of the 26 RU tones in sequence. Here, for example, when considering the four 20 MHz channels within the 80 MHz bandwidth in ascending order of frequency in the frequency domain, the second 20 MHz channel can be meant.

[0267] Hereinafter, the subcarrier indices (tone indices) constituting each 26 DRU are exemplified.

[0268] - 26 DRU-1: -499 -472 -443 -416 -388 -360 -333 -304 -277 22 49 78 105 133 161 188 217 244 278 305 334 361 389 417 444 473

[0269] - 26 DRU-2: -498 -471 -442 -415 -387 -359 -332 -303 -276 23 50 79 106 134 162 189 218 245 279 306 335 362 390 418 445 474

[0270] - 26 DRU-3: -497 -470 -441 -414 -386 -358 -331 -302 -275 24 51 80 107 135 163 190 219 246 280 307 336 363 391 419 448 475

[0271] - 26 DRU-4: -496 -469 -440 -413 -385 -357 -330 -301 -274 25 52 81 108 136 164 191 220 247 281 308 337 364 392 420 449 476

[0272] - 26 DRU-5: -495 -468 -439 -412 -384 -356 -329 -300 -273 26 53 82 109 137 165 192 221 248 282 309 338 365 394 421 450 477

[0273] - 26 DRU-6: -494 -467 -438 -411 -383 -355 -328 -299 -272 27 54 83 110 138 166 193 222 249 283 310 339 367 395 422 451 478

[0274] - 26 DRU-7: -493 -466 -437 -410 -382 -354 -327 -298 -271 28 55 84 111 139 167 194 223 250 284 311 340 368 396 423 452 479

[0275] - 26 DRU-8: -492 -465 -436 -409 -381 -353 -326 -297 -270 29 56 85 112 140 168 195 224 251 285 314 341 369 397 424 453 480

[0276] - 26 DRU-9: -491 -464 -435 -408 -380 -352 -325 -296 -269 30 57 86 113 141 169 196 225 252 286 315 342 370 398 425 454 481

[0277] - 26 DRU-10: -490 -463 -434 -407 -379 -351 -324 -295 -268 31 58 87 114 142 170 197 226 260 287 316 343 371 399 426 455 482

[0278] - 26 DRU-11: -489 -462 -433 -406 -378 -350 -323 -294 -267 32 59 88 115 143 171 198 227 261 288 317 344 372 400 427 456 483

[0279] - 26 DRU-12: -488 -461 -432 -405 -377 -349 -322 -293 -266 33 60 89 116 144 172 201 228 262 289 318 345 373 401 428 457 484

[0280] - 26 DRU-13: -487 -460 -431 -404 -376 -348 -321 -292 -265 34 61 90 117 145 173 202 229 263 290 319 346 374 402 429 458 485

[0281] - 26 DRU-14: -486 -459 -430 -403 -375 -347 -320 -291 -264 35 62 91 118 147 174 203 230 264 291 320 347 375 403 430 459 486

[0282] - 26 DRU-15: -485 -458 -429 -402 -374 -346 -319 -290 -263 36 63 92 120 148 175 204 231 265 292 321 348 376 404 431 460 487

[0283] - 26 DRU-16: -484 -457 -428 -401 -373 -345 -318 -289 -262 37 64 93 121 149 176 205 232 266 293 322 349 377 405 432 461 488

[0284] - 26 DRU-17: -483 -456 -427 -400 -372 -344 -317 -288 -261 38 67 94 122 150 177 206 233 267 294 323 350 378 406 433 462 489

[0285] - 26 DRU-18: -482 -455 -426 -399 -371 -343 -316 -287 -260 39 68 95 123 151 178 207 234 268 295 324 351 379 407 434 463 490

[0286] - 26 DRU-19: -481 -454 -425 -398 -370 -342 -315 -286 13 40 69 96 124 152 179 208 235 269 296 325 352 380 408 435 464 491

[0287] - 26 DRU-20: -480 -453 -424 -397 -369 -341 -314 -285 14 41 70 97 125 153 180 209 236 270 297 326 353 381 409 436 465 492

[0288] - 26 DRU-21: -479 -452 -423 -396 -368 -340 -311 -284 15 42 71 98 126 154 181 210 237 271 298 327 354 382 410 437 466 493

[0289] - 26 DRU-22: -478 -451 -422 -395 -367 -339 -310 -283 16 43 72 99 127 155 182 211 238 272 299 328 355 383 411 438 467 494

[0290] - 26 DRU-23: -477 -450 -421 -394 -365 -338 -309 -282 17 44 73 100 128 156 183 212 239 273 300 329 356 384 412 439 468 495

[0291] - 26 DRU-24: -476 -449 -420 -392 -364 -337 -308 -281 18 45 74 101 129 157 184 213 240 274 ​​301 330 357 385 413 440 469 496

[0292] - 26 DRU-25: -475 -448 -419 -391 -363 -336 -307 -280 19 46 75 102 130 158 185 214 241 275 302 331 358 386 414 441 470 497

[0293] - 26 DRU-26: -474 -445 -418 -390 -362 -335 -306 -279 20 47 76 103 131 159 186 215 242 276 303 332 359 387 415 442 471 498

[0294] - 26 DRU-27: -473 -444 -417 -389 -361 -334 -305 -278 21 48 77 104 132 160 187 216 243 277 304 333 360 388 416 443 472 499

[0295] 3) In the case of a third 20MHz puncturing: Except for the third 20MHz channel punctured in the 80MHz bandwidth, the available tones in the frequency domain may be allocated one tone at a time, starting from the lowest frequency available tone and going up to the highest frequency available tone, for a total of 27 26 RU tones. Here, for example, the third 20MHz channel can mean the third 20MHz channel when considering the four 20MHz channels in the 80MHz bandwidth in ascending frequency order of the frequency domain.

[0296] The following are examples of subcarrier indices (tone indices) that make up each of the 26 DRUs.

[0297] - 26 DRU-1: -499 -472 -443 -416 -388 -360 -333 -304 -277 -243 -216 -187 -160 -132 -104 -77 -48 -21 278 305 334 361 389 417 444 473

[0298] - 26 DRU-2: -498 -471 -442 -415 -387 -359 -332 -303 -276 -242 -215 -186 -159 -131 -103 -76 -47 -20 279 306 335 362 390 418 445 474

[0299] - 26 DRU-3: -497 -470 -441 -414 -386 -358 -331 -302 -275 -241 -214 -185 -158 -130 -102 -75 -46 -19 280 307 336 363 391 419 448 475

[0300] - 26 DRU-4: -496 -469 -440 -413 -385 -357 -330 -301 -274 -240 -213 -184 -157 -129 -101 -74 -45 -18 281 308 337 364 392 420 449 476

[0301] - 26 DRU-5: -495 -468 -439 -412 -384 -356 -329 -300 -273 -239 -212 -183 -156 -128 -100 -73 -44 -17 282 309 338 365 394 421 450 477

[0302] - 26 DRU-6: -494 -467 -438 -411 -383 -355 -328 -299 -272 -238 -211 -182 -155 -127 -99 -72 -43 -16 283 310 339 367 395 422 451 478

[0303] - 26 DRU-7: -493 -466 -437 -410 -382 -354 -327 -298 -271 -237 -210 -181 -154 -126 -98 -71 -42 -15 284 311 340 368 396 423 452 479

[0304] - 26 DRU-8: -492 -465 -436 -409 -381 -353 -326 -297 -270 -236 -209 -180 -153 -125 -97 -70 -41 -14 285 314 341 369 397 424 453 480

[0305] - 26 DRU-9: -491 -464 -435 -408 -380 -352 -325 -296 -269 -235 -208 -179 -152 -124 -96 -69 -40 -13 286 315 342 370 398 425 454 481

[0306] - 26 DRU-10: -490 -463 -434 -407 -379 -351 -324 -295 -268 -234 -207 -178 -151 -123 -95 -68 -39 260 287 316 343 371 399 426 455 482

[0307] - 26 DRU-11: -489 -462 -433 -406 -378 -350 -323 -294 -267 -233 -206 -177 -150 -122 -94 -67 -38 261 288 317 344 372 400 427 456 483

[0308] - 26 DRU-12: -488 -461 -432 -405 -377 -349 -322 -293 -266 -232 -205 -176 -149 -121 -93 -64 -37 262 289 318 345 373 401 428 457 484

[0309] - 26 DRU-13: -487 -460 -431 -404 -376 -348 -321 -292 -265 -231 -204 -175 -148 -120 -92 -63 -36 263 290 319 346 374 402 429 458 485

[0310] - 26 DRU-14: -486 -459 -430 -403 -375 -347 -320 -291 -264 -230 -203 -174 -147 -118 -91 -62 -35 264 291 320 347 375 403 430 459 486

[0311] - 26 DRU-15: -485 -458 -429 -402 -374 -346 -319 -290 -263 -229 -202 -173 -145 -117 -90 -61 -34 265 292 321 348 376 404 431 460 487

[0312] - 26 DRU-16: -484 -457 -428 -401 -373 -345 -318 -289 -262 -228 -201 -172 -144 -116 -89 -60 -33 266 293 322 349 377 405 432 461 488

[0313] - 26 DRU-17: -483 -456 -427 -400 -372 -344 -317 -288 -261 -227 -198 -171 -143 -115 -88 -59 -32 267 294 323 350 378 406 433 462 489

[0314] - 26 DRU-18: -482 -455 -426 -399 -371 -343 -316 -287 -260 -226 -197 -170 -142 -114 -87 -58 -31 268 295 324 351 379 407 434 463 490

[0315] - 26 DRU-19: -481 -454 -425 -398 -370 -342 -315 -286 -252 -225 -196 -169 -141 -113 -86 -57 -30 269 296 325 352 380 408 435 464 491

[0316] - 26 DRU-20: -480 -453 -424 -397 -369 -341 -314 -285 -251 -224 -195 -168 -140 -112 -85 -56 -29 270 297 326 353 381 409 436 465 492

[0317] - 26 DRU-21: -479 -452 -423 -396 -368 -340 -311 -284 -250 -223 -194 -167 -139 -111 -84 -55 -28 271 298 327 354 382 410 437 466 493

[0318] - 26 DRU-22: -478 -451 -422 -395 -367 -339 -310 -283 -249 -222 -193 -166 -138 -110 -83 -54 -27 272 299 328 355 383 411 438 467 494

[0319] - 26 DRU-23: -477 -450 -421 -394 -365 -338 -309 -282 -248 -221 -192 -165 -137 -109 -82 -53 -26 273 300 329 356 384 412 439 468 495

[0320] - 26 DRU-24: -476 -449 -420 -392 -364 -337 -308 -281 -247 -220 -191 -164 -136 -108 -81 -52 -25 274 301 330 357 385 413 440 469 496

[0321] - 26 DRU-25: -475 -448 -419 -391 -363 -336 -307 -280 -246 -219 -190 -163 -135 -107 -80 -51 -24 275 302 331 358 386 414 441 470 497

[0322] - 26 DRU-26: -474 -445 -418 -390 -362 -335 -306 -279 -245 -218 -189 -162 -134 -106 -79 -50 -23 276 303 332 359 387 415 442 471 498

[0323] - 26 DRU-27: -473 -444 -417 -389 -361 -334 -305 -278 -244 -217 -188 -161 -133 -105 -78 -49 -22 277 304 333 360 388 416 443 472 499

[0324] 4) In the case of a fourth 20MHz puncturing: Except for the fourth 20MHz channel that is punctured in the 80MHz bandwidth, the available tones in the frequency domain may be allocated one tone at a time, starting from the lowest frequency available tone and going up to the highest frequency available tone, for a total of 27 26 RU tones. Here, for example, the fourth 20MHz channel can mean the fourth 20MHz channel when considering the four 20MHz channels in the 80MHz bandwidth in ascending frequency order of the frequency domain.

[0325] The following are examples of subcarrier indices (tone indices) that make up each of the 26 DRUs.

[0326] - 26 DRU-1: -499 -472 -443 -416 -388 -360 -333 -304 -277 -243 -216 -187 -160 -132 -104 -77 -48 -21 31 58 87 114 142 170 197 226

[0327] - 26 DRU-2: -498 -471 -442 -415 -387 -359 -332 -303 -276 -242 -215 -186 -159 -131 -103 -76 -47 -20 32 59 88 115 143 171 198 227

[0328] - 26 DRU-3: -497 -470 -441 -414 -386 -358 -331 -302 -275 -241 -214 -185 -158 -130 -102 -75 -46 -19 33 60 89 116 144 172 201 228

[0329] - 26 DRU-4: -496 -469 -440 -413 -385 -357 -330 -301 -274 -240 -213 -184 -157 -129 -101 -74 -45 -18 34 61 90 117 145 173 202 229

[0330] - 26 DRU-5: -495 -468 -439 -412 -384 -356 -329 -300 -273 -239 -212 -183 -156 -128 -100 -73 -44 -17 35 62 91 118 147 174 203 230

[0331] - 26 DRU-6: -494 -467 -438 -411 -383 -355 -328 -299 -272 -238 -211 -182 -155 -127 -99 -72 -43 -16 36 63 92 120 148 175 204 231

[0332] - 26 DRU-7: -493 -466 -437 -410 -382 -354 -327 -298 -271 -237 -210 -181 -154 -126 -98 -71 -42 -15 37 64 93 121 149 176 205 232

[0333] - 26 DRU-8: -492 -465 -436 -409 -381 -353 -326 -297 -270 -236 -209 -180 -153 -125 -97 -70 -41 -14 38 67 94 122 150 177 206 233

[0334] - 26 DRU-9: -491 -464 -435 -408 -380 -352 -325 -296 -269 -235 -208 -179 -152 -124 -96 -69 -40 -13 39 68 95 123 151 178 207 234

[0335] - 26 DRU-10: -490 -463 -434 -407 -379 -351 -324 -295 -268 -234 -207 -178 -151 -123 -95 -68 -39 13 40 69 96 124 152 179 208 235

[0336] - 26 DRU-11: -489 -462 -433 -406 -378 -350 -323 -294 -267 -233 -206 -177 -150 -122 -94 -67 -38 14 41 70 97 125 153 180 209 236

[0337] - 26 DRU-12: -488 -461 -432 -405 -377 -349 -322 -293 -266 -232 -205 -176 -149 -121 -93 -64 -37 15 42 71 98 126 154 181 210 237

[0338] - 26 DRU-13: -487 -460 -431 -404 -376 -348 -321 -292 -265 -231 -204 -175 -148 -120 -92 -63 -36 16 43 72 99 127 155 182 211 238

[0339] - 26 DRU-14: -486 -459 -430 -403 -375 -347 -320 -291 -264 -230 -203 -174 -147 -118 -91 -62 -35 17 44 73 100 128 156 183 212 239

[0340] - 26 DRU-15: -485 -458 -429 -402 -374 -346 -319 -290 -263 -229 -202 -173 -145 -117 -90 -61 -34 18 45 74 101 129 157 184 213 240

[0341] - 26 DRU-16: -484 -457 -428 -401 -373 -345 -318 -289 -262 -228 -201 -172 -144 -116 -89 -60 -33 19 46 75 102 130 158 185 214 241

[0342] - 26 DRU-17: -483 -456 -427 -400 -372 -344 -317 -288 -261 -227 -198 -171 -143 -115 -88 -59 -32 20 47 76 103 131 159 186 215 242

[0343] - 26 DRU-18: -482 -455 -426 -399 -371 -343 -316 -287 -260 -226 -197 -170 -142 -114 -87 -58 -31 21 48 77 104 132 160 187 216 243

[0344] - 26 DRU-19: -481 -454 -425 -398 -370 -342 -315 -286 -252 -225 -196 -169 -141 -113 -86 -57 -30 22 49 78 105 133 161 188 217 244

[0345] - 26 DRU-20: -480 -453 -424 -397 -369 -341 -314 -285 -251 -224 -195 -168 -140 -112 -85 -56 -29 23 50 79 106 134 162 189 218 245

[0346] - 26 DRU-21: -479 -452 -423 -396 -368 -340 -311 -284 -250 -223 -194 -167 -139 -111 -84 -55 -28 24 51 80 107 135 163 190 219 246

[0347] - 26 DRU-22: -478 -451 -422 -395 -367 -339 -310 -283 -249 -222 -193 -166 -138 -110 -83 -54 -27 25 52 81 108 136 164 191 220 247

[0348] - 26 DRU-23: -477 -450 -421 -394 -365 -338 -309 -282 -248 -221 -192 -165 -137 -109 -82 -53 -26 26 53 82 109 137 165 192 221 248

[0349] - 26 DRU-24: -476 -449 -420 -392 -364 -337 -308 -281 -247 -220 -191 -164 -136 -108 -81 -52 -25 27 54 83 110 138 166 193 222 249

[0350] - 26 DRU-25: -475 -448 -419 -391 -363 -336 -307 -280 -246 -219 -190 -163 -135 -107 -80 -51 -24 28 55 84 111 139 167 194 223 250

[0351] - 26 DRU-26: -474 -445 -418 -390 -362 -335 -306 -279 -245 -218 -189 -162 -134 -106 -79 -50 -23 29 56 85 112 140 168 195 224 251

[0352] - 26 DRU-27: -473 -444 -417 -389 -361 -334 -305 -278 -244 -217 -188 -161 -133 -105 -78 -49 -22 30 57 86 113 141 169 196 225 252

[0353] B.52 DRU Index (i.e., 52 DRU Tone Plan)

[0354] A 52 DRU may be configured as a combination of two 26 DRUs, and may be defined as follows in order to distribute the tone as much as possible within each RU.

[0355] -52 DRU-1: Combination of 26 DRU-1 and 26 DRU-15

[0356] -52 DRU-2: Combination of 26 DRU-2 and 26 DRU-16

[0357] -52 DRU-3: Combination of 26 DRU-3 and 26 DRU-17

[0358] -52 DRU-4: Combination of 26 DRU-4 and 26 DRU-18

[0359] -52 DRU-5:26 DRU-6 and 26 DRU-19 combination

[0360] -52 DRU-6: Combination of 26 DRU-7 and 26 DRU-20

[0361] -52 DRU-7:26 DRU-8 and 26 DRU-21 combination

[0362] -52 DRU-8:26 DRU-9 and 26 DRU-22 combination

[0363] -52 DRU-9: Combination of 26 DRU-10 and 26 DRU-24

[0364] -52 DRU-10:26 DRU-11 and 26 DRU-25 combination

[0365] -52 DRU-11:26 DRU-12 and 26 DRU-26 combination

[0366] -52 DRU-12:26 DRU-13 and 26 DRU-27 combination

[0367] C.106DRU index (i.e., 106DRU tone plan)

[0368] 106 DRU may be configured with two 52 DRUs and a combination of two null tones from null tone ±{447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel (i.e., the null tones are used as data tones), and may be defined as follows in order to distribute the tones as much as possible.

[0369] Null tones do not need to overlap between DRUs. For example, when defining / setting the mapping rule between DRUs and RRUs proposed in this disclosure, the null tones used in the RRU mapped to the DRU may be the same ones used in the DRU. Alternatively, when defining the 12 null tones, excluding the 4 null tones belonging to the punctured channels within the 80 MHz bandwidth, as null-1 to null-12 in ascending frequency order, the combinations null-1 and null-7, null-2 and null-8, null-3 and null-9, null-4 and null-10, null-5 and null-11, and null-6 and null-12 may be assigned to each of the 106 DRUs.

[0370] -106 DRU-1: i) 52 DRU-1, ii) 52 DRU-7, and iii) a combination of two null tones (e.g., two null tones from ±{447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0371] -106 DRU-2: i) 52 DRU-2, ii) 52 DRU-8, and iii) a combination of two null tones (e.g., two null tones from + / - {447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0372] -106 DRU-3: i) 52 DRU-3, ii) 52 DRU-9, and iii) a combination of two null tones (e.g., two null tones from + / - {447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0373] -106 DRU-4: i) 52 DRU-4, ii) 52 DRU-10, and iii) a combination of two null tones (e.g., two null tones from + / - {447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0374] -106 DRU-5: i) 52 DRU-5, ii) 52 DRU-11, and iii) a combination of two null tones (e.g., two null tones from + / - {447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0375] -106 DRU-6: i) 52 DRU-6, ii) 52 DRU-12, and iii) a combination of two null tones (e.g., two null tones from + / - {447, 446, 313, 312, 200, 199, 66, 65} that do not belong to the punctured 20MHz channel).

[0376] D.242 DRU index (i.e., 242 DRU tone plan)

[0377] 242 DRU may be configured with a combination of two 106 DRUs, one 26 DRU (i.e., one of the 26 DRUs not used in the RU combination for generating the 106 DRU - 5, 14, 23 may be used), and four null tones from null tones ±{500, 393, 366, 259, 253, 146, 119, 12} that do not belong to the punctured 20MHz channel (i.e., the null tones are used as data tones), and may be defined as follows in order to distribute the tones as much as possible.

[0378] Null tones do not need to overlap between DRUs. For example, when defining / setting the mapping rule between DRUs and RRUs proposed in this disclosure, the null tones used in the RRU mapped to the DRU may be the same ones used in the DRU. Alternatively, when defining the 12 null tones, excluding the 4 null tones belonging to the punctured channels within the 80 MHz bandwidth, as null-1 to null-12 in ascending frequency order, the combinations null-1, null-4, null-7, and null-10, null-2, null-5, null-8, and null-11, and null-3, null-6, null-9, and null-12 may be assigned to each of the 242 DRUs.

[0379] -242 DRU-1: i) 106 DRU-1, ii) 106 DRU-4, iii) 26 DRU-5, and iv) combinations of 4 null tones (e.g., 4 null tones from ±{500, 393, 366, 259, 253, 146, 119, 12} that do not belong to the punctured 20MHz channel)

[0380] -242 DRU-2: i) 106 DRU-2, ii) 106 DRU-5, iii) 26 DRU-14, and iv) combinations of 4 null tones (e.g., 4 null tones from ±{500, 393, 366, 259, 253, 146, 119, 12} that do not belong to the punctured 20MHz channel)

[0381] -242 DRU-3: i) 106 DRU-3, ii) 106 DRU-6, iii) 26 DRU-23, and iv) combinations of 4 null tones (e.g., 4 null tones from ±{500, 393, 366, 259, 253, 146, 119, 12} that do not belong to the punctured 20MHz channel)

[0382] E.484 DRU index (i.e., 484 DRU tone plan)

[0383] Since 20MHz of the 80MHz channel is punctured, only one 484 DRU needs to be configured, and it can be configured in various ways as shown below.

[0384] -484 DRU-1: i) combination of 242 DRU-1 and 242 DRU-2, or ii) combination of 242 DRU-1 and 242 DRU-3, or iii) combination of 242 DRU-2 and 242 DRU-3

[0385] Assuming that each 242 DRU is mapped sequentially to each 242 RRU in ascending frequency order, in the case where the first and second 20MHz are punctured, it would be preferable for 484 DRU-1 to be configured as a combination of 242 DRU-2 and 242 DRU-3, and in the case where the third and fourth 20MHz are punctured, it would be preferable for 484 DRU-1 to be configured as a combination of 242 DRU-1 and 242 DRU-2.

[0386] When the aforementioned DRU tone plan is applied, when transmitting DL OFDMA using DRU, the RU assignment fields / subfields defined when transmitting DL OFDMA using RRU (see, for example, Table 8) may be used identically (i.e., without modification). Similarly, when triggering TB PPDU using DRU, the RU assignment subfields defined in the trigger frame that triggers TB PPDU transmission using RRU (see, for example, Table 1) may be used identically (i.e., without modification).

[0387] Thus, in order to use existing defined RU assignment subfields / fields without modification for RU assignment (i.e., specifying the size and placement of RUs) for OFDM transmissions, further mapping between DRUs and RRUs is required.

[0388] This disclosure proposes the following mapping / correspondence relationship between DRUs and RRUs.

[0389] Here, we assume that RRUs are defined as RRU-1, -2, ... in order from the lowest frequency to the highest frequency (see Table 3 above). In this case, the assignment of a specific DRU to a specific STA may be indicated by the mapped / corresponding RRU (i.e., RRU index) as defined below. Here, it may also be indicated that the DRU is applied to the PPDU (i.e., DL OFDMA PPDU, UL TB PPDU, etc.) (i.e., the RU assignment subfield / field is indicated to be analyzed as a DRU assignment).

[0390] Example 1

[0391] Example 1 proposes a mapping method between DRU and RRU as defined by the method described above.

[0392] A. Index mapping / correspondence between 484 DRU and 484 RRU

[0393] The 484 DRU may be mapped to the 484 RRU as follows: Since one 20MHz channel is punctured, the 484 RRU is located at 40MHz where puncture is not applied.

[0394] - 484 DRU-1:484 RRU-1

[0395] B.242 Index mapping / correspondence between DRU and RRU

[0396] The 242 DRUs may be sequentially mapped to the 242 RRUs as follows. That is, the combination of 242 DRUs forming the 484 DRUs may change depending on the position of the punctured 20MHz channel.

[0397] - 242 DRU-1:242 RRU-1

[0398] - 242 DRU-2:242 RRU-2

[0399] - 242 DRU-3:242 RRU-3

[0400] Index mapping / correspondence for C.106 DRU / 26, DRU-5 / 26, DRU-14 / 26, and DRU-23.

[0401] 242 DRU / RRU may be combined as follows:

[0402] - 242 DRU-1 (242 RRU-1) = 106 DRU-1 + 106 DRU-4 + 26 DRU-5 + null tones (106 RRU-1 + 106 RRU-2 + 26 RRU-5 + null tones)

[0403] - 242 DRU-2 (242 RRU-2) = 106 DRU-2 + 106 DRU-5 + 26 DRU-14 + null tones (106 RRU-3 + 106 RRU-4 + 26 RRU-14 + null tones)

[0404] - 242 DRU-3 (242 RRU-3) = 106 DRU-3 + 106 DRU-6 + 26 DRU-23 + null tones (106 RRU-5 + 106 RRU-6 + 26 RRU-23 + null tones)

[0405] Therefore, each 106 DRU / 26 DRU-5 / 26 DRU-14 / 26 DRU-23 may be mapped / corresponded as follows.

[0406] - 106 DRU-1:106 RRU-1

[0407] - 106 DRU-2:106 RRU-3

[0408] - 106 DRU-3:106 RRU-5

[0409] - 106 DRU-4:106 RRU-2

[0410] - 106 DRU-5:106 RRU-4

[0411] - 106 DRU-6:106 RRU-6

[0412] - 26 DRU-5:26 RRU-5

[0413] - 26 DRU-14:26 RRU-14

[0414] - 26 DRU-23:26 RRU-23

[0415] Index mapping / correspondence between D.52 DRU and 52 RRU

[0416] 106 DRU / RRU may be combined as follows:

[0417] - 106 DRU-1 (106 RRU-1) = 52 DRU-1 + 52 DRU-7 + null tones (52 RRU-1 + 52 RRU-2 + null tones)

[0418] - 106 DRU-2 (106 RRU-3) = 52 DRU-2 + 52 DRU-8 + null tones (52 RRU-5 + 52 RRU-6 + null tones)

[0419] - 106 DRU-3 (106 RRU-5) = 52 DRU-3 + 52 DRU-9 + null tones (52 RRU-9 + 52 RRU-10 + null tones)

[0420] - 106 DRU-4 (106 RRU-2) = 52 DRU-4 + 52 DRU-10 + null tones (52 RRU-3 + 52 RRU-4 + null tones)

[0421] - 106 DRU-5 (106 RRU-4) = 52 DRU-5 + 52 DRU-11 + null tones (52 RRU-7 + 52 RRU-8 + null tones)

[0422] - 106 DRU-6 (106 RRU-6) = 52 DRU-6 + 52 DRU-12 + null tones (52 RRU-11 + 52 RRU-12 + null tones)

[0423] Therefore, each 52 DRU may be mapped to each 52 RRU as follows.

[0424] - 52 DRU-1:52 RRU-1

[0425] - 52 DRU-2:52 RRU-5

[0426] - 52 DRU-3:52 RRU-9

[0427] - 52 DRU-4:52 RRU-3

[0428] - 52 DRU-5:52 RRU-7

[0429] - 52 DRU-6:52 RRU-11

[0430] - 52 DRU-7:52 RRU-2

[0431] - 52 DRU-8:52 RRU-6

[0432] - 52 DRU-9:52 RRU-10

[0433] - 52 DRU-10:52 RRU-4

[0434] - 52 DRU-11:52 RRU-8

[0435] - 52 DRU-12:52 RRU-12

[0436] E.26 Index mapping / correspondence between DRU and 26 RRU

[0437] 52 DRU / RRU may be combined as follows:

[0438] - 52 DRU-1 (52 RRU-1) = 26 DRU-1 + 26 DRU-15 (26 RRU-1 + 26 RRU-2)

[0439] - 52 DRU-2 (52 RRU-5) = 26 DRU-2 + 26 DRU-16 (26 RRU-10 + 26 RRU-11)

[0440] - 52 DRU-3 (52 RRU-9) = 26 DRU-3 + 26 DRU-17 (26 RRU-19 + 26 RRU-20)

[0441] - 52 DRU-4 (52 RRU-3) = 26 DRU-4 + 26 DRU-18 (26 RRU-6 + 26 RRU-7)

[0442] - 52 DRU-5 (52 RRU-7) = 26 DRU-6 + 26 DRU-19 (26 RRU-15 + 26 RRU-16)

[0443] - 52 DRU-6 (52 RRU-11) = 26 DRU-7 + 26 DRU-20 (26 RRU-24 + 26 RRU-25)

[0444] - 52 DRU-7 (52 RRU-2) = 26 DRU-8 + 26 DRU-21 (26 RRU-3 + 26 RRU-4)

[0445] - 52 DRU-8 (52 RRU-6) = 26 DRU-9 + 26 DRU-22 (26 RRU-12 + 26 RRU-13)

[0446] - 52 DRU-9 (52 RRU-10) = 26 DRU-10 + 26 DRU-24 (26 RRU-21 + 26 RRU-22)

[0447] - 52 DRU-10 (52 RRU-4) = 26 DRU-11 + 26 DRU-25 (26 RRU-8 + 26 RRU-9)

[0448] - 52 DRU-11 (52 RRU-8) = 26 DRU-12 + 26 DRU-26 (26 RRU-17 + 26 RRU-18)

[0449] - 52 DRU-12 (52 RRU-12) = 26 DRU-13 + 26 DRU-27 (26 RRU-26 + 26 RRU-27)

[0450] Therefore, each of the 26 DRUs may be mapped to each RRU as follows.

[0451] - 26 DRU-1:26 RRU-1

[0452] - 26 DRU-2:26 RRU-10

[0453] - 26 DRU-3:26 RRU-19

[0454] - 26 DRU-4:26 RRU-6

[0455] - 26 DRU-5:26 RRU-5

[0456] - 26 DRU-6:26 RRU-15

[0457] - 26 DRU-7:26 RRU-24

[0458] - 26 DRU-8:26 RRU-3

[0459] - 26 DRU-9:26 RRU-12

[0460] - 26 DRU-10:26 RRU-21

[0461] - 26 DRU-11:26 RRU-8

[0462] - 26 DRU-12:26 RRU-17

[0463] - 26 DRU-13:26 RRU-26

[0464] - 26 DRU-14:26 RRU-14

[0465] - 26 DRU-15:26 RRU-2

[0466] - 26 DRU-16:26 RRU-11

[0467] - 26 DRU-17:26 RRU-20

[0468] - 26 DRU-18:26 RRU-7

[0469] - 26 DRU-19:26 RRU-16

[0470] - 26 DRU-20:26 RRU-25

[0471] - 26 DRU-21:26 RRU-4

[0472] - 26 DRU-22:26 RRU-13

[0473] - 26 DRU-23:26 RRU-23

[0474] - 26 DRU-24:26 RRU-22

[0475] - 26 DRU-25:26 RRU-9

[0476] - 26 DRU-26:26 RRU-18

[0477] - 26 DRU-27:26 RRU-27

[0478] Example 2

[0479] Unlike the mapping rules in Example 1 described above, the DRU index and the RRU index may be mapped to the same value, in which case the tone index of each DRU may be changed.

[0480] To distinguish them from the DRUs defined by the method described above, the DRUs newly defined in Example 2 (i.e., DRUs that have the same DRU index as the RRU index in the mapping rule) are denoted as DRU*.

[0481] First, the mapping rules between the newly defined DRU* and RRU may be defined as follows:

[0482] A. Index mapping / correspondence between 26 DRU* and 26 RRU

[0483] - 26 DRU*-1:26 RRU-1

[0484] - 26 DRU*-2:26 RRU-2

[0485] - 26 DRU*-3:26 RRU-3

[0486] - 26 DRU*-4:26 RRU-4

[0487] - 26 DRU*-5:26 RRU-5

[0488] - 26 DRU*-6:26 RRU-6

[0489] - 26 DRU*-7:26 RRU-7

[0490] - 26 DRU*-8:26 RRU-8

[0491] - 26 DRU*-9:26 RRU-9

[0492] - 26 DRU*-10:26 RRU-10

[0493] - 26 DRU*-11:26 RRU-11

[0494] - 26 DRU*-12:26 RRU-12

[0495] - 26 DRU*-13:26 RRU-13

[0496] - 26 DRU*-14:26 RRU-14

[0497] - 26 DRU*-15:26 RRU-15

[0498] - 26 DRU*-16:26 RRU-16

[0499] - 26 DRU*-17:26 RRU-17

[0500] - 26 DRU*-18:26 RRU-18

[0501] - 26 DRU*-19:26 RRU-19

[0502] - 26 DRU*-20:26 RRU-20

[0503] - 26 DRU*-21:26 RRU-21

[0504] - 26 DRU*-22:26 RRU-22

[0505] - 26 DRU*-23:26 RRU-23

[0506] - 26 DRU*-24:26 RRU-24

[0507] - 26 DRU*-25:26 RRU-25

[0508] - 26 DRU*-26:26 RRU-26

[0509] - 26 DRU*-27:26 RRU-27

[0510] B. Index mapping / correspondence between 52 DRU* and 52 RRU

[0511] - 52 DRU*-1:52 RRU-1

[0512] - 52 DRU*-2:52 RRU-2

[0513] - 52 DRU*-3:52 RRU-3

[0514] - 52 DRU*-4:52 RRU-4

[0515] - 52 DRU*-5:52 RRU-5

[0516] - 52 DRU*-6:52 RRU-6

[0517] - 52 DRU*-7:52 RRU-7

[0518] - 52 DRU*-8:52 RRU-8

[0519] - 52 DRU*-9:52 RRU-9

[0520] - 52 DRU*-10:52 RRU-10

[0521] - 52 DRU*-11:52 RRU-11

[0522] - 52 DRU*-12:52 RRU-12

[0523] C.106 Index mapping / correspondence between DRU* and 106 RRU

[0524] - 106 DRU*-1:106 RRU-1

[0525] - 106 DRU*-2:106 RRU-2

[0526] - 106 DRU*-3:106 RRU-3

[0527] - 106 DRU*-4:106 RRU-4

[0528] - 106 DRU*-5:106 RRU-5

[0529] - 106 DRU*-6:106 RRU-6

[0530] Index mapping / correspondence between D.242 DRU* and 242 RRU

[0531] - 242 DRU*-1:242 RRU-1

[0532] - 242 DRU*-2:242 RRU-2

[0533] - 242 DRU*-3:242 RRU-3

[0534] E.484 DRU* and 484 RRU index mapping / correspondence

[0535] - 484 DRU*-1:484 RRU*-1

[0536] In such cases, the tone index of the new DRU* may be defined as follows:

[0537] A.26 DRU* Tone Index

[0538] - 26 DRU*-1:26 DRU-1

[0539] - 26 DRU*-2:26 DRU-15

[0540] - 26 DRU*-3:26 DRU-8

[0541] - 26 DRU*-4:26 DRU-21

[0542] - 26 DRU*-5:26 DRU-5

[0543] - 26 DRU*-6:26 DRU-4

[0544] - 26 DRU*-7:26 DRU-18

[0545] - 26 DRU*-8:26 DRU-11

[0546] - 26 DRU*-9:26 DRU-25

[0547] - 26 DRU*-10:26 DRU-2

[0548] - 26 DRU*-11:26 DRU-16

[0549] - 26 DRU*-12:26 DRU-9

[0550] - 26 DRU*-13:26 DRU-22

[0551] - 26 DRU*-14:26 DRU-14

[0552] - 26 DRU*-15:26 DRU-6

[0553] - 26 DRU*-16:26 DRU-19

[0554] - 26 DRU*-17:26 DRU-12

[0555] - 26 DRU*-18:26 DRU-26

[0556] - 26 DRU*-19:26 DRU-3

[0557] - 26 DRU*-20:26 DRU-17

[0558] - 26 DRU*-21:26 DRU-10

[0559] - 26 DRU*-22:26 DRU-24

[0560] - 26 DRU*-23:26 DRU-23

[0561] - 26 DRU*-24:26 DRU-7

[0562] - 26 DRU*-25:26 DRU-20

[0563] - 26 DRU*-26:26 DRU-13

[0564] - 26 DRU*-27:26 DRU-27

[0565] B.52 DRU*tone index

[0566] - 52 DRU*-1:52 DRU-1

[0567] - 52 DRU*-2:52 DRU-7

[0568] - 52 DRU*-3:52 DRU-4

[0569] - 52 DRU*-4:52 DRU-10

[0570] - 52 DRU*-5:52 DRU-2

[0571] - 52 DRU*-6:52 DRU-8

[0572] - 52 DRU*-7:52 DRU-5

[0573] - 52 DRU*-8:52 DRU-11

[0574] - 52 DRU*-9:52 DRU-3

[0575] - 52 DRU*-10:52 DRU-9

[0576] - 52 DRU*-11:52 DRU-6

[0577] - 52 DRU*-12:52 DRU-12

[0578] C.106 DRU* Tone Index

[0579] - 106 DRU*-1:106 DRU-1

[0580] - 106 DRU*-2:106 DRU-4

[0581] - 106 DRU*-3:106 DRU-2

[0582] - 106 DRU*-4:106 DRU-5

[0583] - 106 DRU*-5:106 DRU-3

[0584] - 106 DRU*-6:106 DRU-6

[0585] D.242 DRU* Tone Index

[0586] - 242 DRU*-1:242 DRU-1

[0587] - 242 DRU*-2:242 DRU-2

[0588] - 242 DRU*-3:242 DRU-3

[0589] E.484 DRU* Tone Index

[0590] - 484 DRU*-1:484 DRU*-1

[0591] Example 3: The DRU index can be generalized and mapped to each RRU as shown below.

[0592] First, each of the 26 DRU-a / b / c / d / e / f / g / h / i / j / k / l / m / n / o / p / q / r / s / t / u / v / w / x / y / z / aa can be defined as one of the above 26 DRU-1 to 27. Here, 26 DRU-1 to 27 may correspond to DRUs defined by the method described above, or they may not be limited to the definitions described above, and definitions of DRUs to which other tones are assigned may also be considered.

[0593] Furthermore, 52 DRU-a / b / c / d / e / f / g / h / i / j / k / l, 106 DRU-a / b / c / d / e / f, 242 DRU-a / b / c, and 484 DRU-a may be defined, and for this purpose the following combinations may be considered.

[0594] In this embodiment, the alphabetical index order and the frequency order do not need to be related. Furthermore, even if the alphabetical index between each DRU is the same, this does not mean that the order within each DRU is the same.

[0595] -52 DRU-a: Combination of 26 DRU-a and 26 DRU-o

[0596] -52 DRU-b: Combination of 26 DRU-b and 26 DRU-p

[0597] -52 DRU-c: Combination of 26 DRU-c and 26 DRU-q

[0598] -52 DRU-d: Combination of 26 DRU-d and 26 DRU-r

[0599] -52 DRU-e: Combination of 26 DRU-f and 26 DRU-s

[0600] -52 DRU-f: Combination of 26 DRU-g and 26 DRU-t

[0601] -52 DRU-g: 26 DRU-h, 26 DRU-u combination

[0602] -52 DRU-h: Combination of 26 DRU-i and 26 DRU-v

[0603] -52 DRU-i: 26 DRU-j, 26 DRU-x combination

[0604] -52 DRU-j:26 DRU-k, 26 DRU-y combination

[0605] -52 DRU-k: Combination of 26 DRU-l and 26 DRU-z

[0606] -52 DRU-l:26 DRU-m, 26 DRU-aa combination

[0607] -106 DRU-a: A combination of 52 DRU-a, 52 DRU-g, and two null tones.

[0608] -106 DRU-b: A combination of 52 DRU-b, 52 DRU-h, and two null tones.

[0609] -106 DRU-c: A combination of 52 DRU-c, 52 DRU-i, and two null tones.

[0610] -106 DRU-d: 52 DRU-d, 52 DRU-j, and a combination of two null tones

[0611] -106 DRU-e: 52 DRU-e, 52 DRU-k, and a combination of two null tones

[0612] -106 DRU-f: 52 DRU-f, 52 DRU-l, and a combination of two null tones

[0613] -242 DRU-a: A combination of 106 DRU-a, 106 DRU-d, 26 DRU-e, and four null tones.

[0614] -242 DRU-b: A combination of 106 DRU-b, 106 DRU-e, 26 DRU-n, and four null tones.

[0615] -242 DRU-c: A combination of 106 DRU-c, 106 DRU-f, 26 DRU-w, and four null tones.

[0616] In this case, the following combinations and mappings may be considered.

[0617] A. Index mapping / correspondence between 484 DRU and 484 RRU

[0618] - 484 DRU-a:484 RRU-1

[0619] B.242 Index mapping / correspondence between DRU and RRU

[0620] - 242 DRU-a:242 RRU-1

[0621] - 242 DRU-b:242 RRU-2

[0622] - 242 DRU-c:242 RRU-3

[0623] C.106 Index Mapping / Correspondence between DRU and RRU

[0624] - 106 DRU-a:106 RRU-1

[0625] - 106 DRU-b:106 RRU-3

[0626] - 106 DRU-c:106 RRU-5

[0627] - 106 DRU-d:106 RRU-2

[0628] - 106 DRU-e:106 RRU-4

[0629] - 106 DRU-f:106 RRU-6

[0630] Index mapping / correspondence between D.52 DRU and 52 RRU

[0631] - 52 DRU-a:52 RRU-1

[0632] - 52 DRU-b:52 RRU-5

[0633] - 52 DRU-c:52 RRU-9

[0634] - 52 DRU-d:52 RRU-3

[0635] - 52 DRU-e:52 RRU-7

[0636] - 52 DRU-f:52 RRU-11

[0637] - 52 DRU-g:52 RRU-2

[0638] - 52 DRU-h:52 RRU-6

[0639] - 52 DRU-i:52 RRU-10

[0640] - 52 DRU-j:52 RRU-4

[0641] - 52 DRU-k:52 RRU-8

[0642] - 52 DRU-1:52 RRU-12

[0643] E.26 Index mapping / correspondence between DRU and 26 RRU

[0644] - 26 DRU-a:26 RRU-1

[0645] - 26 DRU-b:26 RRU-10

[0646] - 26 DRU-c:26 RRU-19

[0647] - 26 DRU-d:26 RRU-6

[0648] - 26 DRU-e:26 RRU-5

[0649] - 26 DRU-f:26 RRU-15

[0650] - 26 DRU-g:26 RRU-24

[0651] - 26 DRU-h:26 RRU-3

[0652] - 26 DRU-i:26 RRU-12

[0653] - 26 DRU-j:26 RRU-21

[0654] - 26 DRU-k:26 RRU-8

[0655] - 26 DRU-1:26 RRU-17

[0656] - 26 DRU-m:26 RRU-26

[0657] - 26 DRU-n:26 RRU-14

[0658] - 26 DRU-o:26 RRU-2

[0659] - 26 DRU-p:26 RRU-11

[0660] - 26 DRU-q:26 RRU-20

[0661] - 26 DRU-r:26 RRU-7

[0662] - 26 DRU-s:26 RRU-16

[0663] - 26 DRU-t:26 RRU-25

[0664] - 26 DRU-u:26 RRU-4

[0665] - 26 DRU-v:26 RRU-13

[0666] - 26 DRU-w:26 RRU-23

[0667] - 26 DRU-x:26 RRU-22

[0668] - 26 DRU-y:26 RRU-9

[0669] - 26 DRU-z:26 RRU-18

[0670] - 26 DRU-aa:26 RRU-27

[0671] Using the DRU tone mapping described above, signaling overhead can be reduced when assigning a DRU to each STA, which is preferable from a practical standpoint.

[0672] Figure 13 illustrates the operation of a transmitting device for a PPDU transmission and reception method according to one embodiment of the present disclosure.

[0673] Figure 13 illustrates the operation of a transmitting device based on the proposed method described above. The illustration in Figure 13 is for illustrative purposes only and does not limit the scope of this disclosure. Some steps illustrated in Figure 13 may be omitted depending on the circumstances and / or settings.

[0674] Referring to Figure 13, the transmitter generates a PPDU that is transmitted within an 80 MHz frequency bandwidth with 20 MHz puncturing applied (S1301).

[0675] Here, the PPDU transmitter may be an AP or a non-AP STA, and the PPDU receiver may be an AP or a non-AP STA. For the sake of explanation, the transmitter may be referred to as the first STA and the receiver as the second STA.

[0676] The transmitting device can obtain information relating to the tone plan as proposed in this disclosure. As described above, the information relating to the tone plan may include the size and location of the RU, control information associated with the RU, information relating to the frequency band in which the RU is contained, and information relating to the STA receiving the RU.

[0677] The transmitting device can then configure / generate a PPDU based on the acquired control information. The step of configuring / generating a PPDU may include the step of configuring / generating each field of the PPDU. That is, step S1301 includes the step of configuring one or more fields that contain control information relating to the tone plan. For example, step S1301 may include the step of configuring a field that contains control information (e.g., an N-bit map) indicating the size / location of the RU, and / or the step of configuring a field that contains an identifier (e.g., AID) of the STA that receives the RU.

[0678] Furthermore, step S1301 may include a step of generating an STF / LTF sequence to be transmitted by a specific RU. The STF / LTF sequence may be generated based on an already configured STF generation sequence / LTF generation sequence.

[0679] Furthermore, step S1301 may include a step of generating a data field (i.e., MPDU) to be transmitted in a specific RU.

[0680] In embodiments of the present disclosure, a plurality of first type RUs (i.e., DRUs) within an 80 MHz frequency bandwidth excluding a punctured 20 MHz may consist of available subcarriers, where the available subcarriers may consist of one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, and the available subcarriers may vary depending on the size of the RU. For example, a 26-subcarrier first type RU, a 52-subcarrier first type RU, and / or a 106-subcarrier first type RU may consist of one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see Figure 11 and Table 11). As another example, a 242-subcarrier first type RU and / or a 484-subcarrier first type RU may consist of one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see Figure 11 and Table 11). As yet another example, a 996 subcarrier first type RU may consist of subcarriers excluding one or more DC subcarriers and one or more guard subcarriers (see Figure 11 and Table 11). Furthermore, each of the plurality of first type RUs may consist of (or be located at) discontinuous subcarriers at predetermined intervals in the frequency domain (for example, 27 subcarrier intervals in the case of a 26 subcarrier RU) (i.e., at uniform intervals). In other words, the plurality of first type RUs within an 80 MHz frequency bandwidth excluding the punctured 20 MHz may be defined in the manner described above.

[0681] Furthermore, in embodiments of this disclosure, the position of the PPDU relative to one or more first type RUs may be indicated by an RU assignment subfield in an ascending order of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain. Here, the RU assignment subfield may be included in the PPDU or in a trigger frame that triggers the transmission of the PPDU.

[0682] Furthermore, each of the multiple second type RUs (i.e., RRUs) within the 80 MHz frequency bandwidth excluding the punctured 20 MHz consists of a continuous subcarrier in the frequency domain, and the RU allocation subfield may be fully available for the allocation of first type RUs and second type RUs.

[0683] Here, information indicating whether the RU assignment subfield is used to instruct the assignment of a first type RU or a second type RU may be transmitted within the PPDU or within the trigger frame for triggering the PPDU.

[0684] Furthermore, within the aforementioned 80MHz frequency bandwidth, excluding the punctured 20MHz, both the first type RU and the second type RU may be used. In other words, all of the first type RU and the second type RU may be allocated within the 80MHz range.

[0685] Furthermore, within the 80MHz frequency bandwidth excluding the punctured 20MHz, the plurality of first type RUs may include 26 subcarrier first type RUs, 52 subcarrier first type RUs, 106 subcarrier first type RUs, 242 subcarrier first type RUs, and 484 subcarrier first type RUs. Furthermore, within the 80MHz frequency bandwidth excluding the punctured 20MHz, the plurality of second type RUs may include 26 subcarrier second type RUs, 52 subcarrier second type RUs, 106 subcarrier second type RUs, 242 subcarrier second type RUs, and 484 subcarrier second type RUs.

[0686] Here, each of the relatively large second type RUs in the frequency domain may be configured to contain multiple relatively small second type RUs. That is, a relatively large second type RU may be generated based on a combination of multiple relatively small second type RUs (null subcarriers may be added). Similarly, each of the relatively large first type RUs in the frequency domain may be configured to contain multiple relatively small first type RUs. That is, a relatively large first type RU may be generated based on a combination of multiple relatively small first type RUs (null subcarriers may be added).

[0687] Furthermore, according to Example 1, the plurality of second type RUs may be indexed in ascending order in the frequency domain by size, and the plurality of first type RUs may be indexed in ascending order of the lowest subcarrier of each of the plurality of first type RUs in the frequency domain by size. In this case, the mapping relationship between the index of the first type RU and the index of the second type RU may be determined such that the spacing between the subcarriers of the plurality of relatively small first type RUs contained within a relatively large single first type RU is as far apart as possible. Also, in this case, the value for the RU allocation subfield for the allocation of the second type RU may be used identically for the allocation of the first type RU. Furthermore, based on the mapping relationship between the index of the first type RU and the index of the second type RU, the index of the PPDU for one or more first type RUs may be indicated by the value of the RU allocation subfield. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending frequency order, or to a second type 484-RRU set to an unpunctured channel.

[0688] Furthermore, in Embodiment 2, the plurality of second type RUs may be indexed in ascending order in the frequency domain by size, and the plurality of first type RUs may be indexed such that the index for the first type RU is indicated in the same way as the index for the second type RU is indicated by the value for the RU assignment subfield. That is, the plurality of first type RUs do not have to be indexed in ascending order in the frequency domain. In this case, the subcarrier positions for each index of the plurality of first type RUs may be determined such that the subcarrier spacing between the subcarriers of a plurality of relatively small first type RUs contained within a relatively large single first type RU is as far apart as possible. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending order of frequency, or to a second type 484-RRU set to an unpunctured channel.

[0689] Furthermore, in Embodiment 3, the plurality of first type RUs may be indexed according to a predetermined rule. In this case, the value for the RU allocation subfield for the allocation of the second type RU may be used identically for the allocation of the first type RU. Based on the mapping relationship between the index of the first type RU and the index of the second type RU, the value of the RU allocation subfield may indicate the index of the PPDU for one or more first type RUs. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending frequency order, or to a second type 484-RRU set to an unpunctured channel.

[0690] The transmitting device (i.e., the first STA) transmits the PPDU to the receiving device (i.e., the second STA) within an 80 MHz frequency bandwidth excluding the punctured 20 MHz (S1302).

[0691] Here, the transmitting device (i.e., the first STA) can perform at least one of the following operations for the S1302 operation: cyclic shift diversity (CSD), spatial mapping, inverse discrete fourier transform (IDFT) / inverse fast fourier transform (IFFT) operation, or guard interval (GI) insertion.

[0692] The method illustrated in the example in Figure 13 may be performed by the first device 100 in Figure 1. For example, one or more processors 102 of the first device 100 in Figure 1 may be configured to generate a PPDU and transmit the PPDU via the transceiver 106. One or more memories 104 of the first device 100 may store instructions for performing the method illustrated in Figure 13 or the above-mentioned example when executed by one or more processors 102.

[0693] Figure 14 illustrates the operation of a receiving device for a PPDU transmission / reception method according to one embodiment of the present disclosure.

[0694] Figure 14 illustrates the operation of a receiving device based on the proposed method described above. The illustration in Figure 14 is for illustrative purposes only and does not limit the scope of this disclosure. Some steps illustrated in Figure 14 may be omitted depending on the circumstances and / or settings.

[0695] Referring to Figure 14, the receiving device receives the PPDU within an 80 MHz frequency bandwidth, excluding the punctured 20 MHz (S1401).

[0696] Here, the PPDU transmitter may be an AP or a non-AP STA, and the PPDU receiver may be an AP or a non-AP STA. For the sake of convenience in the following explanation, the transmitter may be referred to as the first STA, and the receiver as the second STA.

[0697] Here, the receiving device (i.e., the second STA) can receive all or part of the PPDU in step S1401. For the operation in step S1401, the receiving device (i.e., the second STA) can perform operations to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion operation applied by the transmitting device (for example, applied in step S1302 above).

[0698] The receiving device (i.e., the second STA) processes a PPDU with an 80 MHz frequency bandwidth to which 20 MHz puncturing is applied (S1402).

[0699] Here, the receiving device (i.e., the second STA) can decode all or part of the PPDU. The receiving device (i.e., the second STA) can also obtain control information related to the tone plan (i.e., RU) from the decoded PPDU.

[0700] More specifically, the receiving device can decode the x-SIG field of the PPDU based on the Legacy STF / LTF and obtain the information contained in the x-SIG field. For example, information regarding the various tone plans (i.e., RUs) proposed in this disclosure may be contained in the x-SIG field, and the receiving STA can obtain information regarding the tone plans (i.e., RUs) from the x-SIG field.

[0701] The receiving device (i.e., the second STA) can then decode the rest of the PPDU based on the information obtained regarding the tone plan (i.e., the RU). For example, the receiving device (i.e., the second STA) can decode the STF / LTF fields of the PPDU based on the information regarding the tone plan (i.e., the RU). The receiving device (i.e., the second STA) can also decode the data fields of the PPDU based on the information regarding the tone plan (i.e., the RU) and obtain the MPDU contained in the data fields.

[0702] Furthermore, the receiving device (i.e., the second STA) can perform processing operations to transmit the decoded data to a higher layer (e.g., the MAC layer). It can also perform subsequent operations if the higher layer instructs the PHY layer to generate a signal in response to the data transmitted to the higher layer.

[0703] In embodiments of the present disclosure, multiple first type RUs (i.e., DRUs) within an 80 MHz frequency bandwidth excluding a punctured 20 MHz may consist of usable subcarriers, where the usable subcarriers may consist of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, and the usable subcarriers may vary depending on the size of the RU. For example, a 26-subcarrier first type RU, a 52-subcarrier first type RU, and / or a 106-subcarrier first type RU may consist of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see Figure 11 and Table 11). As another example, a 242-subcarrier first type RU and / or a 484-subcarrier first type RU may consist of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see Figure 11 and Table 11). As yet another example, a 996 subcarrier first type RU may consist of subcarriers excluding one or more DC subcarriers and one or more guard subcarriers (see Figure 11 and Table 11). Furthermore, each of the plurality of first type RUs may consist of (or be located at) discontinuous subcarriers at predetermined intervals in the frequency domain (for example, 27 subcarrier intervals in the case of a 26 subcarrier RU) (i.e., at uniform intervals). In other words, the plurality of first type RUs within an 80 MHz frequency bandwidth excluding the punctured 20 MHz may be defined in the manner described above.

[0704] Furthermore, in embodiments of this disclosure, the position of the PPDU relative to one or more first type RUs may be indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain. Here, the RU assignment subfield may be included in the PPDU or in a trigger frame that triggers the transmission of the PPDU.

[0705] Furthermore, each of the multiple second type RUs (i.e., RRUs) within the 80 MHz frequency bandwidth, excluding the punctured 20 MHz, consists of continuous subcarriers in the frequency domain, and the RU allocation subfield may be fully available for the allocation of first type RUs and second type RUs.

[0706] Here, information indicating whether the RU assignment subfield is used to instruct the assignment of a first type RU or a second type RU may be transmitted within the PPDU or within the trigger frame for triggering the PPDU.

[0707] Furthermore, within the aforementioned 80MHz frequency bandwidth, excluding the punctured 20MHz, both the first type RU and the second type RU may be used. In other words, all of the first type RU and the second type RU may be allocated within the 80MHz range.

[0708] Furthermore, within the 80MHz frequency bandwidth excluding the punctured 20MHz, the plurality of first type RUs may include 26 subcarrier first type RUs, 52 subcarrier first type RUs, 106 subcarrier first type RUs, 242 subcarrier first type RUs, and 484 subcarrier first type RUs. Furthermore, within the 80MHz frequency bandwidth excluding the punctured 20MHz, the plurality of second type RUs may include 26 subcarrier second type RUs, 52 subcarrier second type RUs, 106 subcarrier second type RUs, 242 subcarrier second type RUs, and 484 subcarrier second type RUs.

[0709] Here, each of the relatively large second type RUs in the frequency domain may be configured to contain multiple relatively small second type RUs. That is, a relatively large second type RU may be generated based on a combination of multiple relatively small second type RUs (null subcarriers may be added). Similarly, each of the relatively large first type RUs in the frequency domain may be configured to contain multiple relatively small first type RUs. That is, a relatively large first type RU may be generated based on a combination of multiple relatively small first type RUs (null subcarriers may be added).

[0710] Furthermore, according to Example 1, the plurality of second type RUs may be indexed in ascending order in the frequency domain by size, and the plurality of first type RUs may be indexed in ascending order of the lowest subcarrier of each of the plurality of first type RUs in the frequency domain by size. In this case, the mapping relationship between the index of the first type RU and the index of the second type RU may be determined such that the spacing between the subcarriers of the plurality of relatively small first type RUs contained within a relatively large single first type RU is as far apart as possible. Also, in this case, the value for the RU allocation subfield for the allocation of the second type RU may be used identically for the allocation of the first type RU. Furthermore, based on the mapping relationship between the index of the first type RU and the index of the second type RU, the index of the PPDU for one or more first type RUs may be indicated by the value of the RU allocation subfield. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending frequency order, or to a second type 484-RRU set to an unpunctured channel.

[0711] Furthermore, in Embodiment 2, the plurality of second type RUs may be indexed in ascending order in the frequency domain by size, and the plurality of first type RUs may be indexed such that the index for the first type RU is indicated in the same way as the index for the second type RU is indicated by the value for the RU assignment subfield. That is, the plurality of first type RUs do not have to be indexed in ascending order in the frequency domain. In this case, the subcarrier positions for each index of the plurality of first type RUs may be determined such that the subcarrier spacing between the subcarriers of a plurality of relatively small first type RUs contained within a relatively large single first type RU is as far apart as possible. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending order of frequency, or to a second type 484-RRU set to an unpunctured channel.

[0712] Furthermore, in Embodiment 3, the plurality of first type RUs may be indexed according to a predetermined rule. In this case, the value for the RU allocation subfield for the allocation of the second type RU may be used identically for the allocation of the first type RU. Based on the mapping relationship between the index of the first type RU and the index of the second type RU, the value of the RU allocation subfield may indicate the index of the PPDU for one or more first type RUs. Here, the first type 484-DRU may be mapped to the first second type 484-RRU in ascending frequency order, or to a second type 484-RRU set to an unpunctured channel.

[0713] The method illustrated in the example in Figure 14 may be performed by the second device 200 in Figure 1. For example, one or more processors 202 of the second device 200 in Figure 1 may be configured to receive and process PPDUs via the transceiver 106. One or more memories 204 of the second device 200 may store instructions for performing the method illustrated in Figure 14 or the above-mentioned examples when executed by one or more processors 202.

[0714] In existing wireless LAN systems, the RUs (i.e., RRUs) assigned to each STA for OFDMA transmission consist only of continuous subcarriers in the frequency domain. In contrast, for OFDMA transmission as illustrated in this disclosure, RUs (i.e., DRUs) consisting of discontinuous subcarriers may be assigned. This allows for improved transmission power by assigning RUs composed of discontinuous subcarriers, thereby achieving increased wireless communication efficiency. Furthermore, existing RU assignment subfields may be used identically for DRU assignment. This eliminates the need to define new fields for RU assignment and requires no additional signaling, thus reducing signaling overhead. Additionally, even within a PPDU bandwidth where puncturing in 20MHz units is applied, setting RUs composed of discontinuous subcarriers improves the efficiency of frequency resource usage.

[0715] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly mentioned. Each component or feature may be implemented in a form that does not combine with other components or features. It is also possible to combine some components and / or features to constitute embodiments of the present disclosure. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in other embodiments, or replaced by corresponding components or features of other embodiments. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to constitute embodiments, or may be included as new claims by amendment after filing.

[0716] It will be obvious to those skilled in the art that this disclosure can be embodied in other specific forms, provided that the essential features of this disclosure are not deviated from. Therefore, the above-mentioned detailed description should not be constrained in any way and should be considered illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of this disclosure are included within the scope of this disclosure.

[0717] The scope of this disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause an apparatus or computer to perform operations according to the methods of various embodiments, and non-transitory computer-readable medium on which such software or instructions are stored and executable on the apparatus or computer. Instructions available for programming a processing system that performs the features described in this disclosure may be stored on / in a storage medium or computer-readable storage medium, and the features described in this disclosure may be embodied using a computer program product including such storage medium. The storage medium may 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 may 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. Memory optionally includes one or more storage devices located remotely from the processor. Memory, or alternatively, non-volatile memory devices within memory, includes non-transitory computer-readable storage medium. The features described in this disclosure may be stored on any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of the processing system and cause the processing system to interact with other mechanisms that utilize the results relating to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems and execution environments / containers.

[0718] [Industrial applicability] Although the method proposed in this disclosure has been described primarily in terms of its application to IEEE 802.11-based systems, it can be applied to various other wireless LAN or wireless communication systems as well.

[0719] [Claims when filing an international application] [Claim 1] A method performed by a first station (STA) in a wireless LAN system, The process involves generating a PPDU (physical protocol data unit) to be transmitted within an 80MHz frequency bandwidth with 20MHz puncturing applied, and The process includes the step of transmitting the PPDU to the second STA, Multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A method in which the position of one or more first type RUs of the PPDU is indicated by an RU assignment subfield in an ascending order arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain. [Claim 2] Each of the multiple second type RUs within the 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied consists of continuous subcarriers in the frequency domain. The method according to claim 1, wherein the RU assignment subfield is fully available for the assignment of first type RUs and second type RUs. [Claim 3] The aforementioned plurality of first type RUs include 26 subcarrier first type RUs, 52 subcarrier first type RUs, 106 subcarrier first type RUs, 242 subcarrier first type RUs, and 484 subcarrier first type RUs. The method according to claim 2, wherein the plurality of second type RUs include 26 subcarrier second type RUs, 52 subcarrier second type RUs, 106 subcarrier second type RUs, 242 subcarrier second type RUs, and 484 subcarrier second type RUs. [Claim 4] The method according to claim 3, wherein each relatively large first type RU in the frequency domain is configured to include a plurality of different relatively small first type RUs. [Claim 5] The values ​​for the RU assignment subfield for the assignment of the second type RU are used identically for the assignment of the first type RU. The method according to claim 4, wherein the index of the PPDU for one or more first type RUs is indicated by the value of the RU assignment subfield, based on the mapping relationship between the index of a first type RU and the index of a second type RU. [Claim 6] The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mappings, the following 52 subcarrier RU mappings, the following 106 subcarrier RU mappings, the following 242 subcarrier RU mappings, and the following 484 subcarrier RU mappings. [26 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 10, Type 1 RU-Index 3: Type 2 RU-Index 19, Type 1 RU-Index 4: Type 2 RU-Index 6, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 15, Type 1 RU-Index 7: Type 2 RU-Index 24, Type 1 RU-Index 8: Type 2 RU-Index 3, Type 1 RU-Index 9: Type 2 RU-Index 12, Type 1 RU-Index 10: Type 2 RU-Index 21, Type 1 RU-Index 11: Type 2 RU-Index 8, Type 1 RU-Index 12: Type 2 RU-Index 17, Type 1 RU-Index 13: Type 2 RU-Index 26, Type 1 RU-Index 14: Type 2 RU-Index 14, Type 1 RU-Index 15: Type 2 RU-Index 2, Type 1 RU-Index 16: Type 2 RU-Index 11, Type 1 RU-Index 17: Type 2 RU-Index 20, Type 1 RU-Index 18: Type 2 RU-Index 7, Type 1 RU-Index 19: Type 2 RU-Index 16, Type 1 RU-Index 20: Type 2 RU-Index 25, Type 1 RU-Index 21: Type 2 RU-Index 4, Type 1 RU-Index 22: Type 2 RU-Index 13, Type 1 RU-Index 23: Type 2 RU-Index 23, Type 1 RU-Index 24: Type 2 RU-Index 22, Type 1 RU-Index 25: Type 2 RU-Index 9, Type 1 RU-Index 26: Type 2 RU-Index 18, Type 1 RU-Index 27: Type 2 RU-Index 27 [52 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 5, Type 1 RU-Index 3: Type 2 RU-Index 9, Type 1 RU-Index 4: Type 2 RU-Index 3, Type 1 RU-Index 5: Type 2 RU-Index 7, Type 1 RU-Index 6: Type 2 RU-Index 11, Type 1 RU-Index 7: Type 2 RU-Index 2, Type 1 RU-Index 8: Type 2 RU-Index 6, Type 1 RU-Index 9: Type 2 RU-Index 10, Type 1 RU-Index 10: Type 2 RU-Index 4, Type 1 RU-Index 11: Type 2 RU-Index 8, Type 1 RU-Index 12: Type 2 RU-Index 12 [106 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 3, Type 1 RU-Index 3: Type 2 RU-Index 5, Type 1 RU-Index 4: Type 2 RU-Index 2, Type 1 RU-Index 5: Type 2 RU-Index 4, Type 1 RU-Index 6: Type 2 RU-Index 6 [242 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3 [484 subcarrier RU mapping] Type 1 RU-Index 1: Type 1 RU-Index 1 The method according to claim 5, wherein the aforementioned ":" signifies mapping. [Claim 7] The aforementioned plurality of second type RUs are indexed in ascending order in the frequency domain according to their size. The plurality of first type RUs are indexed in the frequency domain according to their size in ascending order of the lowest subcarrier of each of the plurality of first type RUs. The method according to claim 5, wherein the mapping relationship between the index of a first type RU and the index of a second type RU is determined such that the spacing between a plurality of relatively small, distinct subcarriers of first type RUs contained within a single relatively large first type RU is as far apart as possible. [Claim 8] The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mappings, the following 52 subcarrier RU mappings, the following 106 subcarrier RU mappings, the following 242 subcarrier RU mappings, and the following 484 subcarrier RU mappings. [26 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6, Type 1 RU-Index 7: Type 2 RU-Index 7, Type 1 RU-Index 8: Type 2 RU-Index 8, Type 1 RU-Index 9: Type 2 RU-Index 9, Type 1 RU-Index 10: Type 2 RU-Index 10, Type 1 RU-Index 11: Type 2 RU-Index 11, Type 1 RU-Index 12: Type 2 RU-Index 12, Type 1 RU-Index 13: Type 2 RU-Index 13, Type 1 RU-Index 14: Type 2 RU-Index 14, Type 1 RU-Index 15: Type 2 RU-Index 15, Type 1 RU-Index 16: Type 2 RU-Index 16, Type 1 RU-Index 17: Type 2 RU-Index 17, Type 1 RU-Index 18: Type 2 RU-Index 18, Type 1 RU-Index 19: Type 2 RU-Index 19, Type 1 RU-Index 20: Type 2 RU-Index 20, Type 1 RU-Index 21: Type 2 RU-Index 21, Type 1 RU-Index 22: Type 2 RU-Index 22, Type 1 RU-Index 23: Type 2 RU-Index 23, Type 1 RU-Index 24: Type 2 RU-Index 24, Type 1 RU-Index 25: Type 2 RU-Index 25, Type 1 RU-Index 26: Type 2 RU-Index 26, Type 1 RU-Index 27: Type 2 RU-Index 27 [52 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6, Type 1 RU-Index 7: Type 2 RU-Index 7, Type 1 RU-Index 8: Type 2 RU-Index 8, Type 1 RU-Index 9: Type 2 RU-Index 9, Type 1 RU-Index 10: Type 2 RU-Index 10, Type 1 RU-Index 11: Type 2 RU-Index 11, Type 1 RU-Index 12: Type 2 RU-Index 12 [106 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6 [242 subcarrier RU mappings] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3 [484 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1 The method according to claim 5, wherein the aforementioned ":" signifies mapping. [Claim 9] The ascending order of the lowest subcarrier within the first type RU, based on the index of the first type RU, for each of the multiple first type RU sizes, is determined by the following 26-subcarrier RU order, 52-subcarrier RU order, 106-subcarrier RU order, 242-subcarrier RU order, and 484-subcarrier RU order. [26 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The 15th Type 1 RU, Type 1 RU - Index 3: The 8th Type 1 RU, Type 1 RU - Index 4: 21st Type 1 RU, Type 1 RU - Index 5: The 5th Type 1 RU, Type 1 RU - Index 6: The 4th Type 1 RU, Type 1 RU - Index 7: The 18th Type 1 RU, Type 1 RU - Index 8: The 11th Type 1 RU, Type 1 RU - Index 9: 25th Type 1 RU, Type 1 RU - Index 10: Second Type 1 RU, Type 1 RU - Index 11: The 16th Type 1 RU, Type 1 RU - Index 12: The 9th Type 1 RU, Type 1 RU - Index 13: 22nd Type 1 RU, Type 1 RU - Index 14: The 14th Type 1 RU, Type 1 RU - Index 15: The 6th Type 1 RU, Type 1 RU - Index 16: The 19th Type 1 RU, Type 1 RU - Index 17: The 12th Type 1 RU, Type 1 RU - Index 18: 26th Type 1 RU, Type 1 RU - Index 19: The third Type 1 RU, Type 1 RU - Index 20: 17th Type 1 RU, Type 1 RU - Index 21: The 10th Type 1 RU, Type 1 RU - Index 22: The 24th Type 1 RU, Type 1 RU - Index 23: The 23rd Type 1 RU, Type 1 RU - Index 24: The 7th Type 1 RU, Type 1 RU - Index 25: The 20th Type 1 RU, Type 1 RU - Index 26: 13th Type 1 RU, Type 1 RU - Index 27: The 27th Type 1 RU [52 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The 7th Type 1 RU, Type 1 RU - Index 3: The 4th Type 1 RU, Type 1 RU - Index 4: The 10th Type 1 RU, Type 1 RU - Index 5: Second Type 1 RU, Type 1 RU - Index 6: The 8th Type 1 RU, Type 1 RU - Index 7: The 5th Type 1 RU, Type 1 RU - Index 8: The 11th Type 1 RU, Type 1 RU - Index 9: The third Type 1 RU, Type 1 RU - Index 10: The 9th Type 1 RU, Type 1 RU - Index 11: The 6th Type 1 RU, Type 1 RU - Index 12: The 12th Type 1 RU [106 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The 4th Type 1 RU, Type 1 RU - Index 3: Second Type 1 RU, Type 1 RU - Index 4: The 5th Type 1 RU, Type 1 RU - Index 5: The third Type 1 RU, Type 1 RU - Index 6: The 6th Type 1 RU [242 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The second Type 1 RU, Type 1 RU - Index 3: The third Type 1 RU [484 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU The method according to claim 8, wherein the aforementioned ":" signifies mapping. [Claim 10] The aforementioned plurality of second type RUs are indexed in ascending order in the frequency domain according to their size. The plurality of first type RUs are indexed such that the index for the first type RU is indicated in the same way that the index for the second type RU is indicated by the value for the RU assignment subfield, The method according to claim 5, wherein the subcarrier positions for each index of a plurality of relatively large first type RUs are determined such that the spacing between the subcarriers of a plurality of different, relatively small first type RUs contained within a single relatively large first type RU is as far apart as possible. [Claim 11] The method according to claim 1, wherein the RU assignment subfield is included in the PPDU or in a trigger frame that triggers the transmission of the PPDU. [Claim 12] A first station (STA) device in a wireless LAN system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: Generate a PPDU (physical protocol data unit) to be transmitted within an 80MHz frequency bandwidth with 20MHz puncturing applied; The PPDU is configured to be transmitted to the second STA; Multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A first STA device in which, in the frequency domain, the position of one or more first type RUs of the PPDU is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs. [Claim 13] A method performed by a second station (STA) in a wireless LAN system, The first stage involves receiving a PPDU (physical protocol data unit) within an 80MHz frequency bandwidth to which 20MHz puncturing is applied from the first STA, The process includes the step of processing the PPDU, Multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A method in which the position of one or more first type RUs of the PPDU is indicated by an RU assignment subfield in an ascending order arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs in the frequency domain. [Claim 14] A second station (STA) device in a wireless LAN system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: Receive PPDU (physical protocol data unit) within an 80MHz frequency bandwidth with 20MHz puncturing applied from the 1st STA; The PPDU is configured to process the aforementioned PPDU; Multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A second STA device in which, in the frequency domain, the position of one or more of the PPDU relative to one or more of the first type RUs is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs. [Claim 15] A processing device configured to control a station (STA) in a wireless LAN system, One or more processors, A processing device comprising: one or more computer memories operably connected to one or more processors, which store instructions for performing the method according to any one of claims 1 to 10, based on that they are executed by the one or more processors. [Claim 16] One or more non-transitory computer-readable media for storing one or more instructions, A computer-readable medium in which one or more instructions are executed by one or more processors and control a device in a wireless LAN system to perform the method according to any one of claims 1 to 10.

Claims

1. A method performed by a first station (STA) in a wireless LAN system, The steps include generating a PPDU (physical protocol data unit) to be transmitted within an 80 MHz frequency bandwidth with 20 MHz puncturing applied, The process includes the step of transmitting the PPDU to the second STA, The multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A method in which, in a frequency domain, the position of one or more of the PPDU relative to one or more of the first type RUs is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs.

2. Each of the multiple second type RUs within the 80 MHz frequency bandwidth to which the aforementioned 20 MHz puncturing is applied consists of continuous subcarriers in the frequency domain. The method according to claim 1, wherein the RU assignment subfield is fully available for the assignment of first type RUs and second type RUs.

3. The aforementioned plurality of first type RUs include 26 subcarrier first type RUs, 52 subcarrier first type RUs, 106 subcarrier first type RUs, 242 subcarrier first type RUs, and 484 subcarrier first type RUs. The method according to claim 2, wherein the plurality of second type RUs include 26 subcarrier second type RUs, 52 subcarrier second type RUs, 106 subcarrier second type RUs, 242 subcarrier second type RUs, and 484 subcarrier second type RUs.

4. The method according to claim 3, wherein each relatively large first type RU in the frequency domain is configured to include a plurality of mutually distinct relatively small first type RUs.

5. The values ​​for the RU assignment subfield for the assignment of the second type RU are used identically for the assignment of the first type RU. The method according to claim 4, wherein the index of the PPDU for one or more first type RUs is indicated by the value of the RU assignment subfield, based on the mapping relationship between the index of the first type RU and the index of the second type RU.

6. The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mappings, the following 52 subcarrier RU mappings, the following 106 subcarrier RU mappings, the following 242 subcarrier RU mappings, and the following 484 subcarrier RU mappings. [26 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 10, Type 1 RU-Index 3: Type 2 RU-Index 19, Type 1 RU-Index 4: Type 2 RU-Index 6, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 15, Type 1 RU-Index 7: Type 2 RU-Index 24, Type 1 RU-Index 8: Type 2 RU-Index 3, Type 1 RU-Index 9: Type 2 RU-Index 12, Type 1 RU-Index 10: Type 2 RU-Index 21, Type 1 RU-Index 11: Type 2 RU-Index 8, Type 1 RU-Index 12: Type 2 RU-Index 17, Type 1 RU-Index 13: Type 2 RU-Index 26, Type 1 RU-Index 14: Type 2 RU-Index 14, Type 1 RU-Index 15: Type 2 RU-Index 2, Type 1 RU-Index 16: Type 2 RU-Index 11, Type 1 RU-Index 17: Type 2 RU-Index 20, Type 1 RU-Index 18: Type 2 RU-Index 7, Type 1 RU-Index 19: Type 2 RU-Index 16, Type 1 RU-Index 20: Type 2 RU-Index 25, Type 1 RU-Index 21: Type 2 RU-Index 4, Type 1 RU-Index 22: Type 2 RU-Index 13, Type 1 RU-Index 23: Type 2 RU-Index 23, Type 1 RU-Index 24: Type 2 RU-Index 22, Type 1 RU-Index 25: Type 2 RU-Index 9, Type 1 RU-Index 26: Type 2 RU-Index 18, Type 1 RU-Index 27: Type 2 RU-Index 27 [52 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 5, Type 1 RU-Index 3: Type 2 RU-Index 9, Type 1 RU-Index 4: Type 2 RU-Index 3, Type 1 RU-Index 5: Type 2 RU-Index 7, Type 1 RU-Index 6: Type 2 RU-Index 11, Type 1 RU-Index 7: Type 2 RU-Index 2, Type 1 RU-Index 8: Type 2 RU-Index 6, Type 1 RU-Index 9: Type 2 RU-Index 10, Type 1 RU-Index 10: Type 2 RU-Index 4, Type 1 RU-Index 11: Type 2 RU-Index 8, Type 1 RU-Index 12: Type 2 RU-Index 12 [106 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 3, Type 1 RU-Index 3: Type 2 RU-Index 5, Type 1 RU-Index 4: Type 2 RU-Index 2, Type 1 RU-Index 5: Type 2 RU-Index 4, Type 1 RU-Index 6: Type 2 RU-Index 6 [242 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3 [484 subcarrier RU mapping] Type 1 RU-Index 1: Type 1 RU-Index 1 The method according to claim 5, wherein the aforementioned ":" signifies mapping.

7. The aforementioned plurality of second type RUs are indexed in ascending order in the frequency domain according to their size. The plurality of first type RUs are indexed in the frequency domain according to their size in ascending order of the lowest subcarrier of each of the plurality of first type RUs. The method according to claim 5, wherein the mapping relationship between the index of a first type RU and the index of a second type RU is determined such that the spacing between the subcarriers of a plurality of different, relatively small first type RUs contained within a relatively large single first type RU is as far apart as possible.

8. The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mappings, the following 52 subcarrier RU mappings, the following 106 subcarrier RU mappings, the following 242 subcarrier RU mappings, and the following 484 subcarrier RU mappings. [26 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6, Type 1 RU-Index 7: Type 2 RU-Index 7, Type 1 RU-Index 8: Type 2 RU-Index 8, Type 1 RU-Index 9: Type 2 RU-Index 9, Type 1 RU-Index 10: Type 2 RU-Index 10, Type 1 RU-Index 11: Type 2 RU-Index 11, Type 1 RU-Index 12: Type 2 RU-Index 12, Type 1 RU-Index 13: Type 2 RU-Index 13, Type 1 RU-Index 14: Type 2 RU-Index 14, Type 1 RU-Index 15: Type 2 RU-Index 15, Type 1 RU-Index 16: Type 2 RU-Index 16, Type 1 RU-Index 17: Type 2 RU-Index 17, Type 1 RU-Index 18: Type 2 RU-Index 18, Type 1 RU-Index 19: Type 2 RU-Index 19, Type 1 RU-Index 20: Type 2 RU-Index 20, Type 1 RU-Index 21: Type 2 RU-Index 21, Type 1 RU-Index 22: Type 2 RU-Index 22, Type 1 RU-Index 23: Type 2 RU-Index 23, Type 1 RU-Index 24: Type 2 RU-Index 24, Type 1 RU-Index 25: Type 2 RU-Index 25, Type 1 RU-Index 26: Type 2 RU-Index 26, Type 1 RU-Index 27: Type 2 RU-Index 27 [52 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6, Type 1 RU-Index 7: Type 2 RU-Index 7, Type 1 RU-Index 8: Type 2 RU-Index 8, Type 1 RU-Index 9: Type 2 RU-Index 9, Type 1 RU-Index 10: Type 2 RU-Index 10, Type 1 RU-Index 11: Type 2 RU-Index 11, Type 1 RU-Index 12: Type 2 RU-Index 12 [106 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3, Type 1 RU-Index 4: Type 2 RU-Index 4, Type 1 RU-Index 5: Type 2 RU-Index 5, Type 1 RU-Index 6: Type 2 RU-Index 6 [242 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1, Type 1 RU-Index 2: Type 2 RU-Index 2, Type 1 RU-Index 3: Type 2 RU-Index 3 [484 subcarrier RU mapping] Type 1 RU-Index 1: Type 2 RU-Index 1 The method according to claim 5, wherein the aforementioned ":" signifies mapping.

9. The ascending order of the lowest subcarriers within the first type RU, based on the index of the first type RU, is determined by the following 26-subcarrier RU order, 52-subcarrier RU order, 106-subcarrier RU order, 242-subcarrier RU order, and 484-subcarrier RU order, according to the size of the multiple first type RUs. [26 subcarriers in RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The 15th Type 1 RU, Type 1 RU - Index 3: The 8th Type 1 RU, Type 1 RU - Index 4: The 21st Type 1 RU, Type 1 RU - Index 5: The fifth Type 1 RU, Type 1 RU - Index 6: The fourth Type 1 RU, Type 1 RU - Index 7: The 18th Type 1 RU, Type 1 RU - Index 8: The 11th Type 1 RU, Type 1 RU - Index 9: The 25th Type 1 RU, Type 1 RU - Index 10: The second Type 1 RU, Type 1 RU - Index 11: The 16th Type 1 RU, Type 1 RU - Index 12: The 9th Type 1 RU, Type 1 RU - Index 13: The 22nd Type 1 RU, Type 1 RU - Index 14: The 14th Type 1 RU, Type 1 RU - Index 15: The 6th Type 1 RU, Type 1 RU - Index 16: The 19th Type 1 RU, Type 1 RU - Index 17: The 12th Type 1 RU, Type 1 RU - Index 18: The 26th Type 1 RU, Type 1 RU - Index 19: The third Type 1 RU, Type 1 RU - Index 20: The 17th Type 1 RU, Type 1 RU - Index 21: The 10th Type 1 RU, Type 1 RU - Index 22: The 24th Type 1 RU, Type 1 RU - Index 23: The 23rd Type 1 RU, Type 1 RU - Index 24: The 7th Type 1 RU, Type 1 RU - Index 25: The 20th Type 1 RU, Type 1 RU - Index 26: The 13th Type 1 RU, Type 1 RU - Index 27: The 27th Type 1 RU [52 subcarriers in RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The 7th Type 1 RU, Type 1 RU - Index 3: The fourth Type 1 RU, Type 1 RU - Index 4: The 10th Type 1 RU, Type 1 RU - Index 5: The second Type 1 RU, Type 1 RU - Index 6: The 8th Type 1 RU, Type 1 RU - Index 7: The 5th Type 1 RU, Type 1 RU - Index 8: The 11th Type 1 RU, Type 1 RU - Index 9: The third Type 1 RU, Type 1 RU - Index 10: The 9th Type 1 RU, Type 1 RU - Index 11: The 6th Type 1 RU, Type 1 RU - Index 12: The 12th Type 1 RU [106 subcarriers in RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The fourth Type 1 RU, Type 1 RU - Index 3: The second Type 1 RU, Type 1 RU - Index 4: The 5th Type 1 RU, Type 1 RU - Index 5: The third Type 1 RU, Type 1 RU - Index 6: The 6th Type 1 RU [242 subcarriers in RU order] Type 1 RU - Index 1: The first Type 1 RU, Type 1 RU - Index 2: The second Type 1 RU, Type 1 RU - Index 3: The third Type 1 RU [484 subcarrier RU order] Type 1 RU - Index 1: The first Type 1 RU The method according to claim 8, wherein the aforementioned ":" signifies mapping.

10. The aforementioned plurality of second type RUs are indexed in ascending order in the frequency domain according to their size. The plurality of first type RUs are indexed such that the index for the first type RU is indicated in the same way that the index for the second type RU is indicated by the value for the RU assignment subfield, The method according to claim 5, wherein the subcarrier positions for each index of a plurality of relatively large first type RUs are determined such that the subcarriers of a plurality of different relatively small first type RUs contained within a single relatively large first type RU are spaced as far apart as possible.

11. The method according to claim 1, wherein the RU assignment subfield is included in the PPDU or in a trigger frame that triggers the transmission of the PPDU.

12. A first station (STA) device in a wireless LAN system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: Generate a PPDU (physical protocol data unit) that is transmitted within an 80 MHz frequency bandwidth with 20 MHz puncturing applied; The PPDU is configured to be transmitted to the second STA; The multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A first STA device in which, in the frequency domain, the position of one or more of the PPDUs relative to one or more first type RUs is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs.

13. A method performed by a second station (STA) in a wireless LAN system, The first stage involves receiving a PPDU (physical protocol data unit) within an 80 MHz frequency bandwidth to which 20 MHz puncturing is applied from the first STA, The process includes the step of processing the PPDU, The multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A method in which, in a frequency domain, the position of one or more of the PPDU relative to one or more of the first type RUs is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs.

14. A second station (STA) device in a wireless LAN system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The PPDU (physical protocol data unit) is received within an 80 MHz frequency bandwidth with 20 MHz puncturing applied from the 1st STA; It is configured to process the PPDU; The multiple first type resource units (RUs) within an 80 MHz frequency bandwidth to which the 20 MHz puncturing is applied are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. Each of the aforementioned plurality of first type RUs is composed of discontinuous subcarriers at predetermined intervals in the frequency domain. A second STA device in which, in the frequency domain, the position of one or more of the PPDUs relative to one or more of the first type RUs is indicated by an RU assignment subfield in an ascending arrangement of the plurality of first type RUs with respect to the lowest subcarrier of each of the plurality of first type RUs.

15. A processing device configured to control a station (STA) in a wireless LAN system, One or more processors, A processing device comprising: one or more computer memories operably connected to one or more processors, which store instructions for performing the method according to any one of claims 1 to 10, based on that they are executed by the one or more processors.

16. One or more non-transitory computer-readable media for storing one or more instructions, A computer-readable medium in which one or more instructions are executed by one or more processors and control a device in a wireless LAN system to perform the method according to any one of claims 1 to 10.

Images