Distributed resource unit tone plan-based transmission or reception method and device in wireless LAN system

Abstract

Disclosed are a transmission or reception method and device based on a distributed resource unit tone plan in a wireless LAN system. A method according to an embodiment of the present disclosure may comprise the steps of: receiving, from a second STA, a trigger frame including information related to a distributed resource unit (DRU); and transmitting, to the second STA, in a bandwidth, a TB PPDU including a data portion based on the DRU. Here, tones of the DRU may be distributed on the basis of a DRU tone plan for a distributed bandwidth within the bandwidth. The TB PPDU includes an LTF portion configured on the basis of an LTF sequence, and the LTF sequence may be configured on the basis of a specific sequence configured by coefficients according to two fixed values and a DRU tone plan for the distributed bandwidth.

Description

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

[0001] The present disclosure relates to a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless local area network (WLAN) system.

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

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

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless LAN system.

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

[0006] A method according to one aspect of the present disclosure may include: receiving, by a first station (STA), a trigger frame from a second STA, a trigger frame including information related to a distributed resource unit (DRU); and transmitting, by the first STA, a trigger-based (TB) physical layer protocol data unit (PPDU) including a data portion based on the DRU to the second STA over a bandwidth, wherein tones of the DRU may be distributed based on a DRU tone plan for a distributed bandwidth within the bandwidth. The TB PPDU may include an LTF portion configured based on a long training field (LTF) sequence, and the LTF sequence may be configured based on a specific sequence including a DRU tone plan for the distributed bandwidth and a coefficient based on two fixed values.

[0007] A method according to an additional aspect of the present disclosure may include: transmitting, by a second station (STA), a trigger frame to a first STA, a trigger frame including information related to a distributed resource unit (DRU); and receiving, by the second STA, a trigger-based (TB) physical layer protocol data unit (PPDU) including a data portion based on the DRU from the first STA over a bandwidth, wherein tones of the DRU may be distributed based on a DRU tone plan for a distributed bandwidth within the bandwidth. The TB PPDU may include an LTF portion configured based on a long training field (LTF) sequence, wherein the LTF sequence may be configured based on a specific sequence including a DRU tone plan for the distributed bandwidth and a coefficient based on two fixed values.

[0008] According to the present disclosure, a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless LAN system can be provided.

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

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

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

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

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

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

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

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

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

[0018] FIG. 8 is a diagram illustrating an example of a resource unit of a wireless LAN system to which the present disclosure can be applied.

[0019] FIG. 9 is a diagram illustrating another example of a resource unit of a wireless LAN system to which the present disclosure can be applied.

[0020] FIG. 10 is a diagram illustrating another example of a resource unit of a wireless LAN system to which the present disclosure can be applied.

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

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

[0023] FIG. 13 is a diagram for explaining an example of an operation by a first STA in a PPDU transmission and reception method based on a DRU tone plan according to the present disclosure.

[0024] FIG. 14 is a diagram for explaining an example of an operation by a second STA in a PPDU transmission and reception method based on a DRU tone plan according to the present disclosure.

[0025] FIG. 15 is a diagram for explaining a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0105] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated so that even legacy STAs can attempt demodulation and decoding, and can be mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated so that they can be demodulated and decoded by an STA that has successfully decoded a non-legacy SIG (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in the corresponding field, and can be mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] Resource Unit

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0146] Distributed resource units

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

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

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

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

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

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

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

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

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

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

[0157] trigger frame

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

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

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

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

[0162] The DRU / RRU indication subfield indicates whether distributed RU (DRU) or regular RU (RRU) transmission is requested in each 80MHz frequency subblock. The indication by the DRU / RRU indication subfield can be configured in units of 80MHz frequency subblocks. For example, if the DRU / RRU indication subblock format consists of 4 bits (B0, B1, B2, B3), B0 can be used for DRU / RRU indication for the lowest 80MHz frequency subblock, B1 can be used for DRU / RRU indication for the second-lower 80MHz frequency subblock, B2 can be used for DRU / RRU indication for the second-highest 80MHz frequency subblock, and B3 can be used for DRU / RRU indication for the highest 80MHz frequency subblock. When the UL BW is 20 MHz, 40 MHz, or 80 MHz, bits B1-B3 of the DRU / RRU Indication subfield may be reserved. When the UL BW is 160 MHz, bits B2-B3 of the DRU / RRU Indication subfield may be reserved. To request a UHR TB PPDU using DRU transmission in the 80 MHz frequency subblock, the corresponding bit in the DRU / RRU Indication subfield shall be set to 0, otherwise it shall be set to 1.

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

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

[0165] The user information list contains zero or more user information fields. Figure 12 illustrates an example of the UHR variant user information field format.

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

[0167] The RU allocation subfield may indicate the size and location of an RU / MRU. For this purpose, the RU allocation subfield may be interpreted together with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW extension subfield of the special user information field, the UL BW subfield of the common information field, etc. In addition, if an RU allocated in the RU allocation of the user information field is located in an 80MHz frequency subblock in which the corresponding bit in the DRU / RRU indication subfield of the UHR variant common information field is set to 1, or in two or more 80MHz frequency subblocks in which the corresponding bits in the DRU / RRU indication subfields of the UHR variant common information field are all set to 1, the allocated RU may be an RRU or an MRU.

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

[0169]

[0170]

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

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

[0173]

[0174] Additionally, as shown in Tables 4 to 6, the mapping of B7-B1 of the RU allocation subfield can be defined along with the settings of B0 and PS160 subfields of the RU allocation subfield for 20MHz distributed bandwidth (DBW), 40MHz DBW, and 80MHz DBW.

[0175] Table 4 shows an example of encoding of the PS160 subfield and RU allocation subfield of the UHR variant user information field for 20MHz DBW.

[0176]

[0177] Table 5 shows an example of encoding of the PS160 subfield and RU allocation subfield of the UHR variant user information field for 40 MHz DBW.

[0178]

[0179] Table 6 shows an example of encoding of the PS160 subfield and RU allocation subfield of the UHR variant user information field for 80MHz DBW.

[0180]

[0181] The SS allocation subfield may be configured differently depending on whether the subfield is associated with an RRU or a DRU.

[0182] For example, the SS allocation subfield of the UHR variant user information field associated with an RRU may include a starting spatial stream subfield and a number of spatial streams subfield. As another example, the SS allocation subfield of the UHR variant user information field associated with a DRU may include a DRU distributed bandwidth (DBW) subfield and a number of spatial streams subfield. In other words, the SS allocation subfield may indicate the DRU DBW and spatial streams of the requested UHR TB PPDU. The DRU DBW subfield indicates the DBW of the allocated DRU, and when the DRU DBW subfield consists of 2 bits, values ​​0 to 3 may be defined for 20MHz DBW, 40MHz DBW, 80MHz DBW, and 60MHz DBW.

[0183] DRU tone plan-based transmission and reception

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

[0185] In this disclosure, with respect to a method of applying LTF (hereinafter referred to as UHR-LTF to distinguish it from LTF of previous versions / variants) during DRU transmission, a method of defining / applying a UHR-LTF sequence that takes into account the distributed bandwidth of the DRU is proposed.

[0186] The size of the channel across which DRUs are distributed can be referred to as distribution bandwidth (DBW). For example, distribution bandwidths such as 20MHz DBW, 40MHz DBW, 60MHz DBW, 80MHz DBW, and 160MHz DBW can be defined, and the corresponding DRU tone plan can be defined within a bandwidth of essentially the same size.

[0187] In this regard, the present disclosure specifically describes a method for defining a UHR-LTF sequence that can be used when applying a DRU of a 20 MHz distributed bandwidth (hereinafter, Embodiment 1) and a method for defining a UHR-LTF sequence that can be used when applying a DRU of a 40 MHz distributed bandwidth (hereinafter, Embodiment 2).

[0188] Example 1

[0189] This embodiment is about a method for defining / applying a UHR-LTF sequence that can be applied to a 20MHz distributed bandwidth.

[0190] Basically, a UHR-LTF sequence (hereinafter referred to as a 20MHz UHR-LTF sequence) that can be used when applying a DRU of 20MHz distributed bandwidth in a 20MHz bandwidth can be defined.

[0191] In addition, if a DRU tone plan with a 20MHz distributed bandwidth (hereinafter referred to as a 20MHz DRU tone plan) is applied to a specific 20MHz channel in a bandwidth of 40MHz or more, the UHR-LTF sequence defined when applying the DRU with a 20MHz distributed bandwidth in the 20MHz bandwidth can be applied in the same manner. In this case, a specific shift (e.g., a tone index shift) for aligning tone indices and an additional shift for aligning guard tones, etc. can be applied to the 20MHz DRU tone plan. In addition, the specific shift and the additional shift can be equally applied to the UHR-LTF sequence.

[0192] In the case of a method of configuring a 20MHz UHR-LTF sequence, a specific M sequence of length 26 (e.g., a sequence of length 26 consisting of coefficients of 1 and -1) can be applied to the tone indices corresponding to each 26-tone DRU in the 20MHz DRU tone plan, and based on this, a UHR-LTF sequence in a 52-tone DRU and a 106-tone DRU can be configured. Additionally, in the case of a 106-tone configuration, two additional tones are allocated to each 106-tone DRU, and the UHR-LTF coefficients of the corresponding tones can be 1 or -1. That is, a 20MHz UHR-LTF sequence having coefficients for all tones overlapping with a DRU defined within 20MHz (e.g., tone indices of tones of a DRU according to the 20MHz DRU tone plan) can be defined.

[0193] Various M sequences that can be applied to the proposed method of the present disclosure may be as shown in Table 7. This is an example, and the scope of the present disclosure is not limited thereto.

[0194] Type Sequence (Coefficient)M Sequence 1[-1 +1 -1 +1 -1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 -1 -1 -1 +1 +1 -1 -1 -1 -1]M Sequence 2[+1 +1 -1 +1 -1 +1 +1 +1 +1 -1 +1 -1 -1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 -1]M Sequence 3[-1 -1 -1 -1 +1 +1 +1 -1 -1 -1 +1 -1 +1 -1 +1 -1 +1 -1 +1 -1 +1 +1 -1 -1 +1 -1 +1 -1]M Sequence 4[+1 +1 +1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1 +1 +1 -1 -1 +1 +1]M Sequence 5[+1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 +1 +1 +1 +1 -1 +1 -1 -1 -1 +1 +1 -1 -1 -1]M sequence 6[+1 +1 +1 +1 +1 +1 -1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1 -1 +1 -1 +1 -1]M sequence 7[+1 +1 +1 +1 -1 -1 +1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1]M sequence 8[+1 -1 +1 -1 +1 +1 +1 +1 -1 -1 -1 +1 +1 +1 +1 +1 +1 +1 -1 +1 -1 +1 -1 +1 -1]

[0195] Additionally, with respect to Table 7, additional M sequences can be constructed / defined by reversing the order of the coefficients constituting the M sequence, multiplying the coefficients by -1, or reversing the order of the coefficients and multiplying them by -1.

[0196] In this regard, the 20MHz DRU tone plan in the present disclosure may be based on the following two examples.

[0197] Table 8 shows an example of a 20MH DRU tone plan applicable to the proposed method of the present disclosure.

[0198] Data and pilot subcarrier indices for DRUs in 20MHz UHR PPDUs DRU type DRU index and subcarrier range 26-tone DRUi=1:9 DRU 1[-120:9:-12, 6:9:114] DRU 2[-115:9:-7, 11:9:119] DRU 3[-118:9:-10, 8:9:116] DRU 4[-113:9:-5, 4:9:112] DRU 5[-117:9:-9, 9:9:117] DRU 6[-112:9:-4, 5:9:113] DRU 7[-116:9:-8, 10:9:118] DRU 8[-119:9:-11, 7:9:115] DRU 9[-114:9:-6, 12:9:120]52-ton DRUi=1:4DRU 126-ton [DRU 1, DRU 2]DRU 226-ton [DRU 3, DRU 4]DRU 326-ton [DRU 6, DRU 7]DRU 426-ton [DRU 8, DRU 9]106-ton DRUi=1:2DRU 126-ton [DRU 1 to DRU 4], [-3, 2]DRU 226-ton [DRU 6 to DRU 9], [-2, 3]

[0199] Table 9 shows another example of a 20MH DRU tone plan applicable to the proposed method of the present disclosure.

[0200] Data and pilot subcarrier indices for DRUs in 20MHz UHR PPDUs DRU type DRU index and subcarrier range 26-tone DRUi=1:9 DRU 1[-120:9:-12, 6:9:114] DRU 2[-116:9:-8, 10:9:118] DRU 3[-118:9:-10, 8:9:116] DRU 4[-114:9:-6, 12:9:120] DRU 5[-112:9:-4, 5:9:113] DRU 6[-119:9:-11, 7:9:115] DRU 7[-115:9:-7, 11:9:119] DRU 8[-117:9:-9, 9:9:117] DRU 9[-113:9:-5, 4:9:112]52-ton DRUi=1:4DRU 126-ton [DRU 1, DRU 2]DRU 226-ton [DRU 3, DRU 4]DRU 326-ton [DRU 6, DRU 7]DRU 426-ton [DRU 8, DRU 9]106-ton DRUi=1:2DRU 126-ton [DRU 1 to DRU 4], [-3, 3]DRU 226-ton [DRU 6 to DRU 9], [-2, 2]

[0201] In the 20MHz DRU tone plans of Tables 8 and 9, "a:b:c" means the tone indices from the a tone index to the c tone index at intervals of the b tone. Also, 26-tone [DRU a, DRU b] means that it consists of a 26-tone DRU a and a 26-tone DRU b. Also, a 106-tone DRU is configured by allocating four 26-tone DRUs and two additional tones.

[0202] Additionally, in the 20MHz DRU tone plan of Tables 8 and 9, the pilot tone may be defined as [-103:10:-23, 23:10:103], which is an example and the scope of the present disclosure is not limited thereto.

[0203] Below, specific examples of a 20MHz UHR-LTF sequence configured by considering the aforementioned M sequence and 20MHz DRU tone plan and the peak-to-average power ratio (PAPR) at each DRU when the sequence is applied are described.

[0204] With respect to the example of PAPR, PAPR_a denotes the PAPR of a DRU of size a. In each PAPR_a, a row denotes the PAPR of the a-th row a-tone DRU in the 20MHz DRU tone plan. In addition, the first row (column, Col) denotes the PAPR when the value 1 of the P-matrix or the value w^6 (where w = exp(-j*2*pi / 6)) is applied. In this case, the value is applied only to data tones excluding pilot tones, and the same method is applied to other values. The second row denotes the PAPR when the value -1 of the P-matrix or the value w^3 is applied. The third, fourth, fifth, and sixth rows denote the PAPR when the values ​​w, w^2, w^4, and w^5 of the P-matrix are applied, respectively. The last row denotes the maximum PAPR in each DRU, which is equally applicable to various PAPR results of the present disclosure.

[0205] (Example 1-1)

[0206] Example 1-1 is for an optimized 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8.

[0207] A specific 20MHz UHR-LTF sequence is configured as shown in Table 10, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 11.

[0208] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 1 -1 0 0 0 1 -1 -1 1 -1 1 -1 1 1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 1 1 1 -1 1 1 1 1 1 1 -1 1 -1 1 0 0 0 0 0 0]

[0209] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.84622.51323.23083.23082.51323.8462Row 31.98432.64882.98223.32583.32582.98223.3258Row 42.46152.95083.07463.15143.15143.07463.1514Row 52.48592.46152.64062.65242.65242.64062.6524Row 62.46152.95083.07463.15143.15143.07463.1514Row 71.98432.64882.98223.32583.32582.98223.3258Row 82.39883.84622.51323.23083.23082.51323.8462Row 93.17403.40963.46463.17953.17953.46463.4646PAPR_52Row 13.67633.96364.06723.84473.84474.06724.0672Row 24.13403.84873.73453.72783.72783.73454.1340Row 34.13403.84873.73453.72783.72783.73454.1340Row 43.67633.96364.06723.84473.84474.06724.0672PAPR_106Row 13.55883.93393.64033.76593.76593.64033.9339Row 23.55883.93393.64033.76593.76593.64033.9339

[0210] (Example 1-2)

[0211] Examples 1-2 are for alternative 20MHz UHR-LTF sequences in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0212] A specific 20MHz UHR-LTF sequence is configured as shown in Table 12, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 13.

[0213] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 1 -1 0 0 0 1 -1 -1 1 -1 1 -1 -1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 1 1 1 1 1 1 1 1 -1 1 0 0 0 0 0 0]

[0214] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.84622.51323.23083.23082.51323.8462Row 31.98432.64882.98223.32583.32582.98223.3258Row 42.46152.95083.07463.15143.15143.07463.1514Row 52.39883.84623.14523.24793.24793.14523.8462Row 62.46152.95083.07463.15143.15143.07463.1514Row 71.98432.64882.98223.32583.32582.98223.3258Row 82.39883.84622.51323.23083.23082.51323.8462Row 93.17403.40963.46463.17953.17953.46463.4646PAPR_52Row 13.67633.96364.06723.84473.84474.06724.0672Row 24.13403.84873.73453.72783.72783.73454.1340Row 34.13403.84873.73453.72783.72783.73454.1340Row 43.67633.96364.06723.84473.84474.06724.0672PAPR_106Row 13.55883.93393.64033.76593.76593.64033.9339Row 23.55883.93393.64033.76593.76593.64033.9339

[0215] (Example 1-3)

[0216] Examples 1-3 are for alternative 20MHz UHR-LTF sequences in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0217] A specific 20MHz UHR-LTF sequence is configured as shown in Table 14, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 15.

[0218] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 1 -1 0 0 0 1 -1 -1 1 -1 1 -1 -1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 1 -1 1 -1 1 0 0 0 0 0 0]

[0219] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.84622.51323.23083.23082.51323.8462Row 31.98432.64882.98223.32583.32582.98223.3258Row 42.46152.95083.07463.15143.15143.07463.1514Row 52.39883.84623.14523.24793.24793.14523.8462Row 62.46152.95083.07463.15143.15143.07463.1514Row 71.98432.64882.98223.32583.32582.98223.3258Row 82.39883.84622.51323.23083.23082.51323.8462Row 93.17403.40963.46463.17953.17953.46463.4646PAPR_52Row 13.67633.96364.06723.84473.84474.06724.0672Row 24.13403.84873.73453.72783.72783.73454.1340Row 34.13403.84873.73453.72783.72783.73454.1340Row 43.67633.96364.06723.84473.84474.06724.0672PAPR_106Row 13.55883.93393.64033.76593.76593.64033.9339Row 23.55883.93393.64033.76593.76593.64033.9339

[0220] (Example 1-4)

[0221] Examples 1-4 are for an optimized 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9.

[0222] A specific 20MHz UHR-LTF sequence is configured as shown in Table 16, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 17.

[0223] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 1 -1 1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 1 -1 -1 1 1 -1 1 1 1 1 1 1 -1 -1 1 -1 1 1 -1 1 0 0 0 1 1 1 1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 1 -1 -1 0 0 0 0 0 0 0]

[0224] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 12.48592.82842.63423.18713.18712.63423.1871Row 23.84622.87163.32213.04513.04513.32213.8462Row 33.84622.87163.32213.04513.04513.32213.8462Row 42.48592.82842.63423.18713.18712.63423.1871Row 51.99862.40672.62852.99042.99042.62852.9904Row 63.17403.70754.01793.88353.88354.01794.0179Row 73.84623.84623.96543.94053.94053.96543.9654Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.96622.66323.08543.08542.66323.0854PAPR_52Row 13.87193.69073.78464.13514.13513.78464.1351Row 23.89093.62583.76644.07324.07323.76644.0732Row 33.76233.92593.84233.93023.93023.84233.9302Row 43.40863.76923.51843.63743.63743.51843.7692PAPR_106Row 13.77513.40313.50443.69413.69413.50443.7751Row 23.64593.68363.91893.99443.99443.91893.9944

[0225] (Example 1-5)

[0226] Examples 1-5 are for alternative 20MHz UHR-LTF sequences in the 20MHz DRU tone plan of Table 9. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0227] A specific 20MHz UHR-LTF sequence is configured as shown in Table 18, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 19.

[0228] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 1 -1 1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 1 -1 -1 1 1 -1 1 1 1 1 1 1 -1 -1 1 -1 -1 1 0 0 0 1 1 1 1 1 -1 -1 1 1 -1 -1 1 -1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 -1 0 0 0 0 0 0 0]

[0229] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 12.48592.82842.63423.18713.18712.63423.1871Row 23.84622.87163.32213.04513.04513.32213.8462Row 33.84622.87163.32213.04513.04513.32213.8462Row 42.48592.82842.63423.18713.18712.63423.1871Row 51.98122.61902.71163.05983.05982.71163.0598Row 63.17403.70754.01793.88353.88354.01794.0179Row 73.84623.84623.96543.94053.94053.96543.9654Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.96622.66323.08543.08542.66323.0854PAPR_52Row 13.87193.69073.78464.13514.13513.78464.1351Row 23.89093.62583.76644.07324.07323.76644.0732Row 33.76233.92593.84233.93023.93023.84233.9302Row 43.40863.76923.51843.63743.63743.51843.7692PAPR_106Row 13.77513.40313.50443.69413.69413.50443.7751Row 23.64593.68363.91893.99443.99443.91893.9944

[0230] (Example 1-6)

[0231] Examples 1-6 are for alternative 20MHz UHR-LTF sequences in the 20MHz DRU tone plan of Table 9. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0232] A specific 20MHz UHR-LTF sequence is configured as shown in Table 20, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 21.

[0233] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 1 1 1 1 1 1 -1 1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 -1 -1 0 0 0 -1 1 -1 1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 -1 -1 1 1 -1 1 1 1 1 1 1 -1 1 1 -1 1 -1 -1 1 1 -1 -1 -1 1 -1 1 -1 1 1 1 1 1 -1 1 1 -1 1 1 1 1 -1 1 1 -1 1 1 1 1 -1 1 1 -1 1 1 1 1 -1 1 1 -1 1 1 1 1 1 1 -1 -1 -1 -1 -1 1 1 -1 0 0 0 0 0 0 0]

[0234] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 12.48592.82842.63423.18713.18712.63423.1871Row 23.84622.87163.32213.04513.04513.32213.8462Row 33.84622.87163.32213.04513.04513.32213.8462Row 42.48592.82842.63423.18713.18712.63423.1871Row 51.99862.40672.62852.99042.99042.62852.9904Row 63.17403.70754.01793.88353.88354.01794.0179Row 73.84623.84623.96543.94053.94053.96543.9654Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.96622.66323.08543.08542.66323.0854PAPR_52Row 13.87193.69073.78464.13514.13513.78464.1351Row 23.89093.62583.76644.07324.07323.76644.0732Row 33.76233.92593.84233.93023.93023.84233.9302Row 43.40863.76923.51843.63743.63743.51843.7692PAPR_106Row 13.77513.40313.50443.69413.69413.50443.7751Row 23.64593.68363.91893.99443.99443.91893.9944

[0235] (Example 1-7)

[0236] Example 1-7 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0237] A specific 20MHz UHR-LTF sequence is configured as shown in Table 22, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 23.

[0238] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 -1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 1 -1 1 1 1 1 -1 1 1 1 1 -1 1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 -1 1 -1 -1 1 1 1 1 -1 1 0 0 0 1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 -1 -1 1 0 0 0 0 0 0 0]

[0239] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 12.48592.82842.63423.18713.18712.63423.1871Row 23.84622.87163.32213.04513.04513.32213.8462Row 33.84622.87163.32213.04513.04513.32213.8462Row 42.48592.82842.63423.18713.18712.63423.1871Row 51.99862.40672.62852.99042.99042.62852.9904Row 63.17403.70754.01793.88353.88354.01794.0179Row 73.84623.84623.96543.94053.94053.96543.9654Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.96622.66323.08543.08542.66323.0854PAPR_52Row 13.87193.69073.78464.13514.13513.78464.1351Row 23.89093.62583.76644.07324.07323.76644.0732Row 33.76233.92593.84233.93023.93023.84233.9302Row 43.40863.76923.51843.63743.63743.51843.7692PAPR_106Row 13.77513.40313.50443.69413.69413.50443.7751Row 23.64593.68363.91893.99443.99443.91893.9944

[0240] The aforementioned 20MHz UHR-LTF sequence takes into account all P matrices, and considers a situation where up to 8 spatial streams (SS) are supported in the DRU.

[0241] Additionally, the following describes an optimized 20MHz UHR-LTF sequence and PAPR results based on the application of the sequence, considering a situation where up to 4 SSs are supported in a DRU. In this case, only P matrix values ​​of 1 and -1 can be considered. Since only P matrix values ​​of 1 and -1 are considered, in the examples described below, only the PAPR up to the second row (column, Col) of each DRU can be a valid value.

[0242] (Example 1-8)

[0243] Example 1-8 is for an optimized 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8.

[0244] A specific 20MHz UHR-LTF sequence is configured as shown in Table 24, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 25.

[0245] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 -1 1 1 -1 1 1 -1 1 -1 1 -1 -1 1 1 -1 1 -1 1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 1 -1 1 1 -1 1 1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 -1 1 1 -1 1 1 1 -1 -1 -1 0 0 0 0 0 0 0]

[0246] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.48592.46152.64062.65242.65242.64062.6524Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.63553.54373.87313.83083.83083.87313.8731

[0247] (Example 1-9)

[0248] Examples 1-9 are for different 20MHz UHR-LTF sequences optimized in the 20MHz DRU tone plan of Table 8.

[0249] A specific 20MHz UHR-LTF sequence is configured as shown in Table 26, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 27.

[0250] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 -1 -1 1 1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 1 1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 -1 0 0 0 1 -1 1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 1 -1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 0 0 0 0 0 0]

[0251] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.48592.46152.64062.65242.65242.64062.6524Row 61.99862.40672.62852.99042.99042.62852.9904Row 72.83462.71563.65523.39573.39573.65523.6552Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.41773.82243.50664.18534.18533.50664.1853Row 43.79703.54904.63804.20364.20364.63804.6380PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.87273.35413.66183.79783.79783.66183.8727

[0252] (Example 1-10)

[0253] Examples 1-10 are for another 20MHz UHR-LTF sequence optimized for the 20MHz DRU tone plan of Table 8.

[0254] A specific 20MHz UHR-LTF sequence is configured as shown in Table 28, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 29.

[0255] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 1 1 1 1 1 1 -1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 -1 1 -1 1 1 1 -1 1 -1 0 0 0 0 0 0]

[0256] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.39883.24642.80603.31343.31342.80603.3134Row 41.98122.61902.71163.05983.05982.71163.0598Row 52.48592.46152.64062.65242.65242.64062.6524Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.76923.54964.53524.09524.09524.53524.5352Row 23.58443.41734.10934.17284.17284.10934.1728Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.63553.54373.87313.83083.83083.87313.8731Row 23.63553.54373.87313.83083.83083.87313.8731

[0257] (Example 1-11)

[0258] Example 1-11 is for an alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0259] A specific 20MHz UHR-LTF sequence is configured as shown in Table 30, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 31.

[0260] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 -1 -1 -1 1 -1 1 1 1 1 -1 1 -1 1 1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 1 1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 1 -1 1 1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 1 1 -1 1 -1 -1 -1 -1 -1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 0 0 0 0 0 0 0]

[0261] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.39883.84623.14523.24793.24793.14523.8462Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.63553.54373.87313.83083.83083.87313.8731

[0262] (Example 1-12)

[0263] Example 1-12 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0264] A specific 20MHz UHR-LTF sequence is configured as shown in Table 32, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 33.

[0265] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 1 -1 1 1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 -1 1 1 1 1 1 -1 1 1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 -1 -1 -1 1 1 -1 0 0 0 1 -1 1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 1 1 -1 1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 0 0 0 0 0 0]

[0266] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.39883.84623.14523.24793.24793.14523.8462Row 61.99862.40672.62852.99042.99042.62852.9904Row 72.83462.71563.65523.39573.39573.65523.6552Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.41773.82243.50664.18534.18533.50664.1853Row 43.79703.54904.63804.20364.20364.63804.6380PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.87273.35413.66183.79783.79783.66183.8727

[0267] (Example 1-13)

[0268] Example 1-13 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0269] A specific 20MHz UHR-LTF sequence is configured as shown in Table 34, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 35.

[0270] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 -1 1 -1 1 1 -1 1 1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 1 1 1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 -1 -1 -1 -1 1 1 -1 0 0 0 1 -1 1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 -1 -1 1 1 -1 -1 1 -1 -1 -1 -1 0 0 0 0 0 0]

[0271] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.39883.84623.14523.24793.24793.14523.8462Row 61.99862.40672.62852.99042.99042.62852.9904Row 72.83462.71563.65523.39573.39573.65523.6552Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.41773.82243.50664.18534.18533.50664.1853Row 43.79703.54904.63804.20364.20364.63804.6380PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.87273.35413.66183.79783.79783.66183.8727

[0272] (Example 1-14)

[0273] Example 1-14 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0274] A specific 20MHz UHR-LTF sequence is configured as shown in Table 36, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 37.

[0275] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 1 1 -1 1 1 -1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 1 -1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 0 0 0 0 0 0]

[0276] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.39883.24642.80603.31343.31342.80603.3134Row 41.98122.61902.71163.05983.05982.71163.0598Row 55.53855.53855.71575.84005.84005.71575.8400Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.76923.54964.53524.09524.09524.53524.5352Row 23.58443.41734.10934.17284.17284.10934.1728Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.63553.54373.87313.83083.83083.87313.8731Row 23.63553.54373.87313.83083.83083.87313.8731

[0277] (Example 1-15)

[0278] Example 1-15 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0279] A specific 20MHz UHR-LTF sequence is configured as shown in Table 38, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 39.

[0280] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 -1 1 -1 1 1 1 1 1 1 1 1 1 1 -1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 -1 1 -1 -1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 1 1 1 -1 1 -1 0 0 0 0 0 0]

[0281] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.39883.24642.80603.31343.31342.80603.3134Row 41.98122.61902.71163.05983.05982.71163.0598Row 55.53855.53855.71575.84005.84005.71575.8400Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.76923.54964.53524.09524.09524.53524.5352Row 23.58443.41734.10934.17284.17284.10934.1728Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.63553.54373.87313.83083.83083.87313.8731Row 23.63553.54373.87313.83083.83083.87313.8731

[0282] (Example 1-16)

[0283] Example 1-16 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0284] A specific 20MHz UHR-LTF sequence is configured as shown in Table 40, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 41.

[0285] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 -1 1 -1 1 1 1 1 1 1 1 1 1 1 -1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 -1 1 -1 1 -1 -1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 1 1 1 -1 1 -1 0 0 0 0 0 0]

[0286] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.39883.24642.80603.31343.31342.80603.3134Row 41.98122.61902.71163.05983.05982.71163.0598Row 55.53855.53855.71575.84005.84005.71575.8400Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.76923.54964.53524.09524.09524.53524.5352Row 23.58443.41734.10934.17284.17284.10934.1728Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.63553.54373.87313.83083.83083.87313.8731Row 23.63553.54373.87313.83083.83083.87313.8731

[0287] (Example 1-17)

[0288] Example 1-17 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but it may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0289] A specific 20MHz UHR-LTF sequence is configured as shown in Table 42, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 43.

[0290] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 1 1 -1 1 1 -1 -1 1 -1 0 0 0 1 -1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 1 -1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 0 0 0 0 0 0]

[0291] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.39883.24642.80603.31343.31342.80603.3134Row 41.98122.61902.71163.05983.05982.71163.0598Row 55.53855.53855.71575.84005.84005.71575.8400Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.76923.54964.53524.09524.09524.53524.5352Row 23.58443.41734.10934.17284.17284.10934.1728Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.63553.54373.87313.83083.83083.87313.8731Row 23.63553.54373.87313.83083.83083.87313.8731

[0292] (Example 1-18)

[0293] Example 1-18 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0294] A specific 20MHz UHR-LTF sequence is configured as shown in Table 44, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 45.

[0295] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 -1 1 1 -1 -1 -1 1 1 1 -1 1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 1 1 1 1 1 -1 1 -1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 1 -1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 -1 -1 -1 1 -1 1 1 1 -1 1 1 1 -1 -1 -1 1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 1 0 0 0 1 1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 1 1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 1 1 1 -1 1 0 0 0 0 0 0]

[0296] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 53.17402.92723.67673.86903.86903.67673.8690Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.63553.54373.87313.83083.83083.87313.8731

[0297] (Example 1-19)

[0298] Example 1-19 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0299] A specific 20MHz UHR-LTF sequence is configured as shown in Table 46, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 47.

[0300] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 -1 -1 1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 1 1 1 -1 -1 -1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 1 -1 1 -1 1 1 -1 1 1 -1 -1 -1 0 0 0 -1 -1 -1 1 1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 0 0 0 0 0 0]

[0301] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 53.17402.92723.67673.86903.86903.67673.8690Row 61.98122.61902.71163.05983.05982.71163.0598Row 72.39883.24642.80603.31343.31342.80603.3134Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.58443.41734.10934.17284.17284.10934.1728Row 43.76923.54964.53524.09524.09524.53524.5352PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.63553.54373.87313.83083.83083.87313.8731

[0302] (Example 1-20)

[0303] Example 1-20 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0304] A specific 20MHz UHR-LTF sequence is configured as shown in Table 48, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 49.

[0305] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 -1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 1 1 -1 -1 1 -1 -1 1 1 1 1 0 0 0 1 1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 0 0 0 0 0 0]

[0306] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.39883.84623.14523.24793.24793.14523.8462Row 61.99862.40672.62852.99042.99042.62852.9904Row 72.83462.71563.65523.39573.39573.65523.6552Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.41773.82243.50664.18534.18533.50664.1853Row 43.79703.54904.63804.20364.20364.63804.6380PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.87273.35413.66183.79783.79783.66183.8727

[0307] (Example 1-21)

[0308] Example 1-21 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 8. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0309] A specific 20MHz UHR-LTF sequence is configured as shown in Table 50, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 51.

[0310] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 1 1 -1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 1 1 -1 1 -1 1 -1 -1 -1 -1 -1 1 1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 -1 1 1 -1 -1 -1 -1 0 0 0 -1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 1 -1 -1 1 -1 1 -1 0 0 0 0 0 0]

[0311] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.89563.40973.58403.58403.40973.8956Row 23.17403.70754.01793.88353.88354.01794.0179Row 32.83462.71563.65523.39573.39573.65523.6552Row 41.99862.40672.62852.99042.99042.62852.9904Row 52.39883.84623.14523.24793.24793.14523.8462Row 61.99862.40672.62852.99042.99042.62852.9904Row 72.83462.71563.65523.39573.39573.65523.6552Row 83.17403.70754.01793.88353.88354.01794.0179Row 93.84623.89563.40973.58403.58403.40973.8956PAPR_52Row 13.79703.54904.63804.20364.20364.63804.6380Row 23.41773.82243.50664.18534.18533.50664.1853Row 33.41773.82243.50664.18534.18533.50664.1853Row 43.79703.54904.63804.20364.20364.63804.6380PAPR_106Row 13.87273.35413.66183.79783.79783.66183.8727Row 23.87273.35413.66183.79783.79783.66183.8727

[0312] (Example 1-22)

[0313] Example 1-22 is for an optimized 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9.

[0314] A specific 20MHz UHR-LTF sequence is configured as shown in Table 52, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 53.

[0315] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 1 -1 -1 -1 1 -1 1 -1 -1 1 1 1 1 1 -1 -1 1 1 -1 1 1 1 1 1 0 0 0 -1 -1 1 1 -1 -1 1 -1 1 -1 1 1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 0 0 0 0 0 0]

[0316] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.24642.80603.31343.31342.80603.3134Row 32.39883.24642.80603.31343.31342.80603.3134Row 43.17403.40963.46463.17953.17953.46463.4646Row 51.99862.40672.62852.99042.99042.62852.9904Row 62.39883.84622.51323.23083.23082.51323.8462Row 73.17403.23793.17622.85262.85263.17623.2379Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.40672.62852.99042.99042.62852.9904PAPR_52Row 13.70663.79974.03894.24524.24524.03894.2452Row 23.71883.78094.04414.31164.31164.04414.3116Row 33.71703.86304.11033.91283.91284.11034.1103Row 43.41163.59103.89414.20334.20333.89414.2033PAPR_106Row 13.58683.68893.66513.78273.78273.66513.7827Row 23.76963.78724.46654.66964.66964.46654.6696

[0317] (Example 1-23)

[0318] Example 1-23 is for an alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9. For example, this is not optimal from a PAPR perspective for 26-tone DRU 5, but may be an efficient / desirable method when considering transmission in DL OFDMA scenarios.

[0319] A specific 20MHz UHR-LTF sequence is configured as shown in Table 54, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 55.

[0320] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 1 -1 -1 1 1 -1 1 1 1 1 1 -1 -1 -1 1 1 -1 -1 1 1 -1 1 1 1 1 0 0 0 -1 -1 1 -1 -1 1 1 -1 -1 1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 -1 1 -1 -1 -1 1 1 1 1 1 1 -1 1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 0 0 0 0 0 0 0]

[0321] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.24642.80603.31343.31342.80603.3134Row 32.39883.24642.80603.31343.31342.80603.3134Row 43.17403.40963.46463.17953.17953.46463.4646Row 52.46154.39483.71444.64244.64243.71444.6424Row 62.39883.84622.51323.23083.23082.51323.8462Row 73.17403.23793.17622.85262.85263.17623.2379Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.40672.62852.99042.99042.62852.9904PAPR_52Row 13.70663.79974.03894.24524.24524.03894.2452Row 23.71883.78094.04414.31164.31164.04414.3116Row 33.71703.86304.11033.91283.91284.11034.1103Row 43.41163.59103.89414.20334.20333.89414.2033PAPR_106Row 13.58683.68893.66513.78273.78273.66513.7827Row 23.76963.78724.46654.66964.66964.46654.6696

[0322] (Example 1-24)

[0323] Example 1-24 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0324] A specific 20MHz UHR-LTF sequence is configured as shown in Table 56, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 57.

[0325] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 1 -1 0 0 0 1 -1 -1 1 -1 -1 1 1 -1 -1 -1 -1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 -1 1 -1 1 1 0 0 0 0 0 0]

[0326] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.24642.80603.31343.31342.80603.3134Row 32.39883.24642.80603.31343.31342.80603.3134Row 43.17403.40963.46463.17953.17953.46463.4646Row 52.24633.26273.08603.15663.15663.08603.2627Row 62.39883.84622.51323.23083.23082.51323.8462Row 73.17403.23793.17622.85262.85263.17623.2379Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.40672.62852.99042.99042.62852.9904PAPR_52Row 13.70663.79974.03894.24524.24524.03894.2452Row 23.71883.78094.04414.31164.31164.04414.3116Row 33.71703.86304.11033.91283.91284.11034.1103Row 43.41163.59103.89414.20334.20333.89414.2033PAPR_106Row 13.58683.68893.66513.78273.78273.66513.7827Row 23.76963.78724.46654.66964.66964.46654.6696

[0327] (Example 1-25)

[0328] Example 1-25 is for another alternative 20MHz UHR-LTF sequence in the 20MHz DRU tone plan of Table 9. This may be an efficient / desirable method when considering transmission in DL OFDMA scenarios, for example.

[0329] A specific 20MHz UHR-LTF sequence is configured as shown in Table 58, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 59.

[0330] 20MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 1 1 1 -1 1 1 1 -1 1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 1 0 0 0 -1 1 1 -1 -1 1 1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 1 1 -1 1 1 1 -1 1 1 1 -1 -1 1 -1 -1 1 1 -1 1 -1 -1 0 0 0 0 0 0]

[0331] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.17403.40963.46463.17953.17953.46463.4646Row 22.39883.24642.80603.31343.31342.80603.3134Row 32.39883.24642.80603.31343.31342.80603.3134Row 43.17403.40963.46463.17953.17953.46463.4646Row 52.24633.26273.08603.15663.15663.08603.2627Row 62.39883.84622.51323.23083.23082.51323.8462Row 73.17403.23793.17622.85262.85263.17623.2379Row 82.83462.77193.05032.93262.93263.05033.0503Row 91.99862.40672.62852.99042.99042.62852.9904PAPR_52Row 13.70663.79974.03894.24524.24524.03894.2452Row 23.71883.78094.04414.31164.31164.04414.3116Row 33.71703.86304.11033.91283.91284.11034.1103Row 43.41163.59103.89414.20334.20333.89414.2033PAPR_106Row 13.58683.68893.66513.78273.78273.66513.7827Row 23.76963.78724.46654.66964.66964.46654.6696

[0332] Example 2

[0333] This embodiment is about a method for defining / applying a UHR-LTF sequence that can be applied to a 40MHz distributed bandwidth.

[0334] Basically, a UHR-LTF sequence (hereinafter referred to as a 40MHz UHR-LTF sequence) that can be used when applying a DRU of 40MHz distributed bandwidth in a 40MHz bandwidth can be defined.

[0335] In addition, if a DRU tone plan with a 40MHz distributed bandwidth (hereinafter referred to as a 40MHz DRU tone plan) is applied to a specific 40MHz channel in a bandwidth of 40MHz or more, the UHR-LTF sequence defined when applying the DRU with a 40MHz distributed bandwidth in the 40MHz bandwidth can be applied in the same manner. In this case, a specific shift (e.g., a tone index shift) for aligning tone indices and an additional shift for aligning guard tones, etc. can be applied to the 40MHz DRU tone plan. In addition, the specific shift and the additional shift can be equally applied to the UHR-LTF sequence.

[0336] In the case of a method of configuring a 40MHz UHR-LTF sequence, a specific M sequence (e.g., ) of length 26 can be applied to the tone indices corresponding to each 26-tone DRU in the 40MHz DRU tone plan, and based on this, UHR-LTF sequences in 52-tone DRU, 106-tone DRU, and 242-tone DRU can be configured. Additionally, when configuring 106-tone / 242-tone, additional 2 / 4 tones are allocated to each 106-tone DRU / 242-tone DRU, and the UHR-LTF coefficient of the corresponding tone can be 1 or -1. That is, a 40MHz UHR-LTF sequence having coefficients for all tones overlapping with DRUs defined within 40MHz (e.g., tone indices of tones of DRUs according to the 40MHz DRU tone plan) can be defined.

[0337] Various M sequences that can be applied to the proposed method of the present disclosure may be as shown in Table 60. This is an example, and the scope of the present disclosure is not limited thereto.

[0338] Type Sequence (Coefficient)M Sequence 1[-1 +1 -1 +1 -1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 -1 -1 -1 +1 +1 -1 -1 -1 -1]M Sequence 2[+1 +1 -1 +1 -1 +1 +1 +1 +1 -1 +1 -1 -1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 -1]M Sequence 3[-1 -1 -1 -1 +1 +1 +1 -1 -1 -1 +1 -1 -1 +1 -1 +1 -1 +1 -1 +1 +1 -1 -1 +1 +1 -1 -1 +1 -1]M Sequence 4[+1 +1 +1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1 +1 +1 -1 -1 +1 +1]M Sequence 5[+1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 +1 +1 +1 +1 -1 +1 -1 -1 -1 +1 +1 -1 -1 -1]M sequence 6[+1 +1 +1 +1 +1 +1 -1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1 -1 +1 -1 +1 -1]M sequence 7[+1 +1 +1 +1 -1 -1 +1 +1 +1 +1 -1 +1 +1 -1 -1 +1 -1 -1 -1 +1 -1 -1 +1 -1 -1 +1 -1 +1 -1]M sequence 8[+1 -1 +1 -1 +1 +1 +1 +1 -1 -1 -1 +1 +1 +1 +1 +1 +1 +1 -1 +1 -1 +1 -1 +1 -1]

[0339] Additionally, with respect to Table 60, additional M sequences can be constructed / defined by reversing the order of the coefficients constituting the M sequence, multiplying the coefficients by -1, or reversing the order of the coefficients and multiplying them by -1.

[0340] In this regard, the 40MHz DRU tone plan in the present disclosure may be as an example in Table 61.

[0341] Table 61 shows an example of a 20MH DRU tone plan applicable to the proposed method of the present disclosure.

[0342] Data and pilot subcarrier indices for DRUs in 40MHz UHR PPDUs DRU type DRU index and subcarrier range 26-tone DRUi=1:18 DRU 1[-242:18:-26, 10:18:226] DRU 2[-233:18:-17, 19:18:235] DRU 3[-238:18:-22, 14:18:230] DRU 4[-229:18:-13, 23:18:239] DRU 5[-225:18:-9, 27:18:243] DRU 6[-240:18:-24, 12:18:228] DRU 7[-231:18:-15, 21:18:237] DRU 8[-236:18:-20, 16:18:232]DRU 9[-227:18:-11, 25:18:241]DRU 10[-241:18:-25, 11:18:227]DRU 11[-232:18:-16, 20:18:236]DRU 12[-237:18:-21, 15:18:231]DRU 13[-228:18:-12, 24:18:240]DRU 14[-234:18:-18, 18:18:234]DRU 15[-239:18:-23, 13:18:229]DRU 16[-230:18:-14; 22:18:238]DRU 17[-235:18:-19, 17:18:233]DRU 18[-226:18:-10, 26:18:242]52-ton DRUi=1:8DRU 1[-242:9:-17, 10:9:235]DRU 2[-238:9:-13, 14:9:239]DRU 3[-240:9:-15, 12:9:237]DRU 4[-236:9:-11, 16:9:241]DRU 5[-241:9:-16, 11:9:236]DRU 6[-237:9:-12, 15:9:240]DRU 7[-239:9:-14, 13:9:238]DRU 8[-235:9:-10, 17:9:242]106-ton DRUi=1:4DRU 126-ton [DRU 1 - DRU 4], [8, -5]DRU 226-ton [DRU 6 - DRU 9], [-6, 7]DRU 326-ton [DRU 10 - DRU 13], [-7, 6]DRU 426-ton [DRU 15 - DRU 18], [-5,8]242-ton DRUi=1:2DRU 1106-ton [DRU 1 - DRU 2],26-ton DRU 5, [-244, -4, 3, 9]DRU 2106-ton [DRU 3 - DRU 4],26-ton DRU 14, [-243, -3, 4, 244],

[0343] In the 40MHz DRU tone plan of Table 61, "a:b:c" means the tone indices from the a tone index to the c tone index at intervals of b tone. Also, in a 106-tone DRU, 26-tone [DRU a - DRU b], [c, d] means that the 106-tone DRU is composed of the 26-tone DRU a to the 26-tone DRU b and two additional tones with tone indices c and d. Also, in a 242-tone DRU, 106-tone [DRU a - DRU b], 26-tone DRU c, [d, e, f, g] means that the 242-tone DRU is composed of the 106-tone DRU a to the 16-tone DRU b, the 26-tone DRU c and four additional tones with tone indices d, e, f, g.

[0344] Additionally, in the 40MHz DRU tone plan of Table 61, the pilot tones may be defined as [-214:11:-27, 38:11:225], which is an example and the scope of the present disclosure is not limited thereto. Additionally, some of the pilots may be used in a 106-tone DRU or a 242-tone DRU. [-214, -181, -170, -137, -115, -82, -71, -38, 38, 71, 82, 115, 137, 170, 181, 214] may be an example.

[0345] Considering the aforementioned tone plan and the positions of the pilot tones, UHR-LTF can be optimized from a PAPR perspective, and the PAPR optimization can be based on minimizing the maximum PAPR across all DRUs, considering that each DRU is transmitted in a TB PPDU. Additionally, PAPR optimization can be performed considering a situation where multiple streams are transmitted and a P matrix is ​​applied to UHR-LTF. For example, PAPR optimization can be performed considering a situation where a specific coefficient is multiplied to data tones but not to pilot tones by the P matrix. For example, experiments / simulations for PAPR calculation can be performed considering a situation where a specific coefficient is multiplied to pilot tones, but the coefficient is not multiplied to pilot tones by considering the value multiplied to data tones and canceling it out.

[0346] Below, specific examples of a 40MHz UHR-LTF sequence configured by considering the aforementioned M sequence and 40MHz DRU tone plan and PAPR in each DRU when the sequence is applied are described.

[0347] With respect to the example of PAPR, PAPR_a denotes the PAPR of a DRU of size a. In each PAPR_a, a row denotes the PAPR of the a-th row a-tone DRU in the 40MHz DRU tone plan. In addition, the first row (column, Col) denotes the PAPR when the value 1 of the P-matrix or the value w^6 (where w = exp(-j*2*pi / 6)) is applied. In this case, the value is applied only to data tones excluding pilot tones, and the same method is applied to other values. The second row denotes the PAPR when the value -1 of the P-matrix or the value w^3 is applied. The third, fourth, fifth, and sixth rows denote the PAPR when the values ​​w, w^2, w^4, and w^5 of the P-matrix are applied, respectively. The last row denotes the maximum PAPR in each DRU, which is equally applied to various PAPR results of the present disclosure.

[0348] First, examples are described that consider a case where the maximum number of spatial streams (SS) that can be transmitted in each DRU of the aforementioned 40MHz DRU tone plan is 5 or more.

[0349] (Example 2-1)

[0350] Example 2-1 is for an optimized 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0351] A specific 40MHz UHR-LTF sequence is configured as shown in Table 62, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 63.

[0352] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 1 -1 1 -1 1 1 -1 1 1 1 -1 -1 -1 1 -1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 1 1 -1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 1 -1 -1 1 0 0 0 0 0 1 -1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 -1 -1 1 1 -1 1 1 1 1 -1 1 -1 -1 -1 -1 -1 1 -1 -1 1 1 1 1 -1 1 -1-1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 -1 -1 1 -1 1 1 -1 1 1 1 1 -1 -1 1 -1 -1 1 1 -1 1 -1 -1 0 0 0 0 0 0 0 0 0 0 0]

[0353] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 12.39883.84622.51323.23083.23082.51323.8462Row 23.17403.40963.46463.17953.17953.46463.4646Row 32.39883.36703.45323.68353.68353.45323.6835Row 43.17402.65352.90642.47342.47342.90643.1740Row 53.84624.06824.03244.29534.29534.03244.2953Row 63.84623.84623.95723.92873.92873.95723.9572Row 73.17403.23793.17622.85262.85263.17623.2379Row 81.98433.68932.65263.23753.23752.65263.6893Row 92.48592.96162.84623.05553.05552.84623.0555Row 102.48592.96162.84623.05553.05552.84623.0555Row 111.98433.68932.65263.23753.23752.65263.6893Row 123.17403.23793.17622.85262.85263.17623.2379Row 133.84623.84623.95723.92873.92873.95723.9572Row 143.84623.84623.28923.67873.67873.28923.8462Row 153.17402.65352.90642.47342.47342.90643.1740Row 162.39883.36703.45323.68353.68353.45323.6835Row 173.17403.40963.46463.17953.17953.46463.4646Row 182.39883.84622.51323.23083.23082.51323.8462PAPR_52Row 13.32523.76923.91183.62993.62993.91183.9118Row 23.32523.45453.65853.33843.33843.65853.6585Row 33.13153.39223.76643.75413.75413.76643.7664Row 43.29003.68093.83093.81453.81453.83093.8309Row 53.29003.68093.83093.81453.81453.83093.8309Row 63.13153.39223.76643.75413.75413.76643.7664Row 73.32523.45453.65853.33843.33843.65853.6585Row 83.32523.76923.91183.62993.62993.91183.9118PAPR_106Row 13.76033.86493.62693.66493.66493.62693.8649Row 23.87803.49193.95913.93663.93663.95913.9591Row 33.87803.49193.95913.93663.93663.95913.9591Row 43.76033.86493.62693.66493.66493.62693.8649PAPR_242Row 14.34824.25554.60974.59404.59404.60974.6097Row 24.44994.28014.44174.46754.46754.44174.4675.

[0354] (Example 2-2)

[0355] Example 2-2 is for an alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0356] A specific 40MHz UHR-LTF sequence is configured as shown in Table 64, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 63.

[0357] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 1 -1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 1 1 1 -1 1 1 1 -1 1 1 -1 1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 1 1 1 -1 1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 1 0 0 0 0 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 -1 1 -1 -1 1 1 1 1 1 1 1 1 1 -1 1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 1 -1 -1 1 -1 1 -1 -1 1 1 1 -1 -1 1 1 -1 1 -1 -1 -1 -1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 11 -1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 1 1 1 1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 -1 -1 -1 -1 1 -1 1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 0 0 0 0 0 0 0 0 0 0 0]

[0358] (Example 2-3)

[0359] Example 2-3 is for another alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0360] A specific 40MHz UHR-LTF sequence is configured as shown in Table 65, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 63.

[0361] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 -1 -1 -1 -1 1 -1 1 -1 1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 1 1 1 1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 1 1 1 1 1 1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 1 -1 1 1 -1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 1 1 1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 1 1 1 1 1 1 1 1 1 -1 -1 0 0 0 0 0 1 1 1 -1 -1 1 1 1 -1 -1 1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 -1 1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 11 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 1 -1 1 1 -1 -1 -1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 -1 1 1 -1 -1 1 1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 -1 -1 1 1 1 1 1 -1 -1 1 1 1 1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 -1 1 -1 -1 0 0 0 0 0 0 0 0 0 0 0]

[0362] (Example 2-4)

[0363] Example 2-4 is for another alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0364] A specific 40MHz UHR-LTF sequence is configured as shown in Table 66, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 63.

[0365] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 0 0 0 0 -1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 1 1 -1 -1-1 1 -1 -1 1 -1 1 1 1 1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 1 1 -1 1 1 -1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 1 0 0 0 0 0 0 0 0 0 0 0]

[0366] Next, examples are described that consider a case where the maximum number of spatial streams (SS) that can be transmitted in each DRU of the aforementioned 40MHz DRU tone plan is 4 or less.

[0367] (Example 2-5)

[0368] Example 2-5 is for an optimized 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0369] A specific 40MHz UHR-LTF sequence is configured as shown in Table 67, and the PAPR of each DRU based on the application of the sequence can be calculated as shown in Table 68.

[0370] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 0 1 -1 1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 1 1 1 1 1 1 -1 1 1 1 1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 -1 1 -1 1 1 1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 1 1 -1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 1 - ... 1 1 1 1 1 -1 1 1 -1 -1 1 -1 -1 -1 0 0 0 0 0 1 1 1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 1 1 1 1 -1 -1 1 -1 -1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 1 1 1 -1 1 1 1 1 -1 1 1-1 -1 -1 -1 -1 1 1 -1 1 -1 -1 1 -1 1 1 1 1 1 -1 1 1 -1 1 1 -1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 1 1 -1 -1 -1 -1 -1 1 -1 -1 1 1 1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 1 0 0 0 0 0 0 0 0 0 0 0]

[0371] Col 1Col 2Col 3Col 4Col 5Col 6Col 7PAPR_26Row 13.84623.84623.96543.94053.94053.96543.9654Row 22.48592.82842.63423.18713.18712.63423.1871Row 32.48592.96162.84623.05553.05552.84623.0555Row 43.84623.84623.95723.92873.92873.95723.9572Row 51.98434.04143.06874.05934.05933.06874.0593Row 63.84623.84623.95723.92873.92873.95723.9572Row 73.17403.23793.17622.85262.85263.17623.2379Row 81.98433.68932.65263.23753.23752.65263.6893Row 92.48592.96162.84623.05553.05552.84623.0555Row 102.48592.96162.84623.05553.05552.84623.0555Row 111.98433.68932.65263.23753.23752.65263.6893Row 123.17403.23793.17622.85262.85263.17623.2379Row 133.84623.84623.95723.92873.92873.95723.9572Row 143.17402.92723.67673.86903.86903.67673.8690Row 153.84623.84623.95723.92873.92873.95723.9572Row 162.48592.96162.84623.05553.05552.84623.0555Row 172.48592.82842.63423.18713.18712.63423.1871Row 183.84623.84623.96543.94053.94053.96543.9654PAPR_52Row 13.77983.76923.98183.93983.93983.98183.9818Row 23.77983.43184.84314.66964.66964.84314.8431Row 33.13153.39223.76643.75413.75413.76643.7664Row 43.29003.68093.83093.81453.81453.83093.8309Row 53.29003.68093.83093.81453.81453.83093.8309Row 63.13153.39223.76643.75413.75413.76643.7664Row 73.77983.43184.84314.66964.66964.84314.8431Row 83.77983.76923.98183.93983.93983.98183.9818PAPR_106Row 13.63533.45783.98813.71663.71663.98813.9881Row 23.79133.58573.99893.87063.87063.99893.9989Row 33.79133.58573.99893.87063.87063.99893.9989Row 43.63533.55214.03333.67383.67384.03334.0333PAPR_242Row 14.49274.54945.06164.99964.99965.06165.0616Row 24.62624.23255.41095.21405.21405.41095.4109.

[0372] (Example 2-6)

[0373] Example 2-6 is for an alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0374] A specific 40MHz UHR-LTF sequence is configured as shown in Table 69, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 68.

[0375] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1 1 -1 -1 1 -1 1 1 1 -1 -1 1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 1 1 1 -1 1 -1 -1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 1 1 1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 1 1 1 1 -1 1 -1 1 1 1 1 1 -1 1 -1 1 1 1 1 -1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 1 -1 1 -1 -1 -1 1 -1 0 0 0 0 -1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 -1 1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 1 1 1 1 -1 -1 1 1 1 1-1 -1 -1 1 1 -1 1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 1 1 -1 1 1 1 -1 1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 0 0 0 0 0 0 0 0 0 0 0 0]

[0376] (Example 2-7)

[0377] Example 2-7 is for another alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0378] A specific 40MHz UHR-LTF sequence is configured as shown in Table 70, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 68.

[0379] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 -1 1 1 1 -1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 1 1 -1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 1 -1 1 -1 -1 -1 1 -1 1 1 1 -1 1 0 0 0 0 0 1 -1 1 1 1 -1 -1 -1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 -1 -1 1 -1 1 1 -1 1 1 -1 -1 -1 1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 -1 -1 -1 -1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1-1 -1 1 1 -1 -1 -1 -1 1 1 1 -1 -1 1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 -1 1 -1 -1 -1 -1 1 1 1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 0 0 0 0 0 0 0 0 0 0 0]

[0380] (Example 2-8)

[0381] Example 2-8 is for another alternative 40MHz UHR-LTF sequence in the 40MHz DRU tone plan of Table 61.

[0382] A specific 40MHz UHR-LTF sequence is configured as shown in Table 71, and the PAPR of each DRU based on the application of the sequence can be the same as the PAPR of Table 68.

[0383] 40MHz UHR-LTF sequence[0 0 0 0 0 0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 1 -1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 1 -1 -1 1 1 -1 1 1 0 0 0 0 -1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 1 -1 -1 1 1 1 -1 1 1 1 -1 1 1 1 -1 -11 -1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 0 0 0 0 0 0 0 0 0 0]

[0384] Additionally or alternatively, a sequence may be used that is constructed by multiplying all (e.g., all coefficients) of the various sequences proposed in the present disclosure (e.g., the UHR-LTF sequence proposed in Embodiments 1 and / or 2) by a specific value (e.g., -1). In such a case, the PAPR may be obtained as the same value as the PAPR before multiplying by the specific value.

[0385] Additionally or alternatively, a sequence constructed by inverting the sequence proposed in the present disclosure (e.g., the UHR-LTF sequence proposed in Embodiment 1 and / or Embodiment 2) may be used. For example, the last coefficient of the sequence may be sequentially mapped to a tone of lower index.

[0386] Additionally or alternatively, only the UHR-LTF coefficients of tones that overlap with the DRUs used for transmission may be used for transmission in the same manner as before when transmitting a PPDU. That is, the UHR-LTF coefficients of non-overlapping tones may be set to 0.

[0387] Additionally or alternatively, with respect to the aforementioned UHR-LTF configuration, the number of UHR-LTF symbols may be determined by the number of spatial streams (SS) transmitted in the DRU of the data field. For example, in one spatial stream (e.g., 1 SS), UHR-LTF may consist of 1 symbol, in two spatial streams (e.g., 2 SS), UHR-LTF may consist of 2 symbols, in three / four spatial streams (e.g., 3 SS / 4 SS), UHR-LTF may consist of 4 symbols, in five / six spatial streams (e.g., 5 SS / 6 SS), UHR-LTF may consist of 6 symbols, and in seven / eight spatial streams (e.g., 7 SS / 8 SS), UHR-LTF may consist of 8 symbols. Additionally or alternatively, the number of symbols in UHR-LTF may be greater than the number of symbols determined by the spatial stream by the LTF extension, and may be 2 symbols, 4 symbols, or 8 symbols. Additionally or alternatively, the number of symbols in UHR-LTF may be set to the number of symbols in the DRU that requires the longest length of LTF symbols in OFDMA transmission.

[0388] Below, STA operations based on various examples of the present disclosure described above are described with reference to FIGS. 13 and 14 . The examples in FIGS. 13 and 14 may correspond to some of the various examples of the present disclosure.

[0389] For example, in FIGS. 13 and 14, the first STA may correspond to a non-AP STA that receives a trigger frame requesting a TB PPDU, and the second STA may correspond to an AP that transmits the trigger frame. Here, the non-AP STA corresponding to the first STA may be an STA associated with the AP corresponding to the second STA.

[0390] FIG. 13 is a diagram for explaining an example of an operation by a first STA in a PPDU transmission and reception method based on a DRU tone plan according to the present disclosure.

[0391] Referring to FIG. 13, a first STA may receive a trigger frame including information related to a distributed resource unit (DRU) from a second STA (S1310).

[0392] For example, information related to a DRU may include first information about whether a DRU or a regular RU (RRU) is applied (e.g., a DRU / RRU indication subfield) and second information about the distributed bandwidth to which the DRU is applied (e.g., a DRU distributed bandwidth indication subfield).

[0393] Here, the first information may be included in a common information field within the trigger frame, and the second information may be included in a user information field for the first STA within the trigger frame. In this regard, the first information may include one or more subfields indicating whether to apply a DRU or RRU in units of frequency subblocks of a certain size (e.g., 80 MHz). In addition, the user information field for the first STA may further include an RU allocation subfield for allocating one or more DRUs within a distributed bandwidth.

[0394] The first STA can transmit a TB PPDU including a data portion based on the corresponding DRU to the second STA over the bandwidth (S1320).

[0395] In this regard, the tones of the corresponding DRU may be distributed based on the DRU tone plan for the distributed bandwidth within the bandwidth. The corresponding TB PPDU may include an LTF portion configured based on an LTF sequence. In this case, the LTF sequence may be configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient based on two fixed values.

[0396] According to the present disclosure, the DRU tone plan may include a large-sized DRU composed of a combination of small-sized DRUs. In this case, the LTF sequence for the large-sized DRU may be composed based on the LTF sequence for the small-sized DRUs.

[0397] Additionally, according to the present disclosure, a specific sequence may be applied to 26 tone indices of each 26-tone DRU of the DRU tone plan. Additionally, for the specific sequence for composing the aforementioned LTF sequence, at least one of a first process of reversing the order of coefficients of the specific sequence or a second process of multiplying the specific sequence by a value of -1 may be applied.

[0398] For example, the two values ​​that make up a particular sequence are 1 and -1, and that particular sequence can be based on one of the following eight sequences:

[0399] - Sequence 1 = [-1 1 -1 1 -1 1 1 1 -1 1 1 1 -1 -1 1 -1 -1 -1 -1 -1 1 1 -1 -1 -1 -1],

[0400] - Sequence 2 = [1 1 -1 1 -1 1 1 1 1 -1 1 -1 -1 1 1 -1 1 1 1 1 -1 -1 1 -1 -1 -1],

[0401] - Sequence 3 = [-1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 1 1 1 -1 -1 1 -1],

[0402] - Sequence 4 = [1 1 1 1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 1 -1 -1 1 1 1],

[0403] - Sequence 5 = [1 1 1 1 -1 1 1 -1 -1 1 -1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1],

[0404] - Sequence 6 = [1 1 1 1 1 1 -1 1 1 1 -1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 1 -1],

[0405] - Sequence 7 = [1 1 1 1 -1 -1 1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1],

[0406] - Sequence 8 = [1 -1 1 -1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 1 -1 -1 1 1 -1].

[0407] For example, if the size of the distributed bandwidth of the DRU is 20 MHz, the LTF sequence according to the examples described above in the present disclosure (e.g., examples 1-1 to 1-25) may be used. As a concrete example, the LTF sequence for that DRU is [0 0 0 0 0 0 0 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 1 -1 -1 -1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 1 1 1 1 -1 -1 1 1 -1 1 1 1 1 0 0 0 -1 -1 1 1 -1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 -1 1 1 -1 1 -1 -1 1 -1 1 1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 -1 -1 1 0 0 0 0 0 0 0]. The LTF sequence can be applied to tone indices [-128 to 127].

[0408] For another example, if the size of the distributed bandwidth of the DRU is 40 MHz, the LTF sequence according to the examples described above in the present disclosure (e.g., examples 2-1 to 2-8) may be used. As a concrete example, the LTF sequence for that DRU is [0 0 0 0 0 0 0 0 0 0 0 0 -1 1 -1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 -1 1 -1 1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 -1 1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 0 0 0 0 -1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 1 -1 -1 1 1 1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 -1 1 1 1 1 1 -1 -1 1-1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 1 1 -1 -1 -1 1 -1 1 1 1 1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 -1 -1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 -1 1 1 1 1 -1 1 -1 1 -1 1 1 1 -1 0 0 0 0 0 0 0 0 0 0 0]. The corresponding LTF sequence can be applied to tone indices [-256 to 255].

[0409] Additionally, according to the present disclosure, the number of symbols in the LTF portion may be set based on the number of spatial streams transmitted from the DRU. For example, when the number of spatial streams is 1, the number of symbols in the LTF portion may be 1, and when the number of spatial streams is 2, the number of symbols in the LRF portion may be 2.

[0410] The method described in the example of FIG. 13 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may be configured to receive, via one or more transceivers (106), a trigger frame including information related to a DRU, and transmit, on a bandwidth, a TB PPDU including a data portion based on the corresponding DRU. Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 13 or the examples described above when executed by one or more processors (102).

[0411] FIG. 14 is a diagram for explaining an example of an operation by a second STA in a PPDU transmission and reception method based on a DRU tone plan according to the present disclosure.

[0412] Referring to FIG. 14, the second STA may transmit a trigger frame including information related to a distributed resource unit (DRU) to the first STA (S1410).

[0413] For example, information related to a DRU may include first information about whether a DRU or a regular RU (RRU) is applied (e.g., a DRU / RRU indication subfield) and second information about the distributed bandwidth to which the DRU is applied (e.g., a DRU distributed bandwidth indication subfield).

[0414] Here, the first information may be included in a common information field within the trigger frame, and the second information may be included in a user information field for the first STA within the trigger frame. In this regard, the first information may include one or more subfields indicating whether to apply a DRU or RRU in units of frequency subblocks of a certain size (e.g., 80 MHz). In addition, the user information field for the first STA may further include an RU allocation subfield for allocating one or more DRUs within a distributed bandwidth.

[0415] The second STA can receive a TB PPDU including a data portion based on the corresponding DRU from the first STA over the bandwidth (S1420).

[0416] In this regard, the tones of the corresponding DRU may be distributed based on the DRU tone plan for the distributed bandwidth within the bandwidth. The corresponding TB PPDU may include an LTF portion configured based on an LTF sequence. In this case, the LTF sequence may be configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient based on two fixed values.

[0417] Specific details regarding the setting / instruction for the distributed bandwidth of the DRU, the configuration / application / specific example of a specific sequence for the LTF sequence, the number of symbols in the LTF portion, and the DRU-related instructions / signaling are the same as those described in the example of Fig. 13, so any duplicate description will be omitted.

[0418] The method described in the example of FIG. 14 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may be configured to transmit, via one or more transceivers (106), a trigger frame including information related to a DRU, and receive, over a bandwidth, a TB PPDU including a data portion based on the corresponding DRU. Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 14 or the examples described above when executed by one or more processors (202).

[0419] FIG. 15 is a diagram illustrating a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure. Some of the steps shown in FIG. 15 may be omitted depending on circumstances and / or settings. The transmitting device and the receiving STA may be APs and / or non-AP STAs.

[0420] The transmitting STA may obtain control information related to the aforementioned tone plan (or RU / DRU) (S105). The control information related to the tone plan may include the size and location of the RU, control information related to the RU, information about the frequency band in which the RU is included, information about the STA receiving the RU, etc.

[0421] The transmitting STA may configure / generate a PPDU based on the acquired control information (S110). Configuring / generating a PPDU may mean configuring / generating each field of the PPDU. That is, the step of configuring / generating a PPDU may include a step of configuring a SIG field (e.g., U-SIG / UHR-SIG) that includes control information regarding a tone plan.

[0422] That is, the step of configuring / generating a PPDU may include a step of configuring a field including control information (e.g., N bitmap) indicating the size / position of the RU and / or a step of configuring a field including an identifier (e.g., AID) of an STA receiving the RU.

[0423] Additionally, the step of configuring / generating a PPDU may include a step of generating an STF / LTF sequence to be transmitted via a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence. For example, the LTF portion (e.g., LTF field) included in the PPDU may be configured based on the UHR-LTF sequence proposed in the present disclosure.

[0424] Additionally, the step of constructing / generating a PPDU may include a step of generating a data field (i.e., an MPDU) to be transmitted via a specific RU.

[0425] The transmitting STA can transmit the configured / generated PPDU to the receiving STA (S115).

[0426] Specifically, the transmitting STA can perform at least one of cyclic shift diversity (CSD), spatial mapping, inverse discrete Fourier transform (IDFT) / inverse fast Fourier transform (IFFT) operation, and guard interval (GI) insertion operation.

[0427] The receiving STA can decode the PPDU and obtain control information related to the tone-plan (or RU) (S120).

[0428] Specifically, the receiving STA can decode the L-SIG and SIG fields (e.g., U-SIG / UHR-SIG) of the PPDU based on the L-STF / LTF, and obtain information included in the L-SIG and SIG fields. Information about various tone plans (i.e., RUs) of the present disclosure can be included in the SIG field (e.g., U-SIG / UHR-SIG), and the receiving STA can obtain information about the tone plan (i.e., RU) through the corresponding SIG field.

[0429] The receiving STA can decode the remaining portion of the PPDU based on the acquired tone plan (i.e., RU) information (S125). For example, the receiving STA can decode the STF / LTF portion (e.g., the STF / LTF field) of the PPDU based on the tone plan (i.e., RU) information. In particular, the LTF portion can be configured by the UHR-LTF sequence proposed in the present disclosure and can be used for channel estimation purposes for decoding the data portion (e.g., the data field).

[0430] Additionally, the receiving STA can decode the data field of the PPDU based on information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.

[0431] Additionally, the receiving STA may perform a processing operation to forward the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data forwarded to the higher layer, the receiving STA may perform a subsequent operation.

[0432] Unlike the existing wireless LAN system where only RRU is applied, in the case where application of DRU is supported, the efficiency of resource utilization can be improved by transmitting / receiving one or more fields of PPDU based on DRU tone plans of various sizes applicable to PPDUs of a bandwidth of 40 MHz or more according to the present disclosure.

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

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

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

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

Claims

1. A step of receiving, by a first station (STA), a trigger frame including information related to a distributed resource unit (DRU) from a second STA; and A step of transmitting, by the first STA, a trigger-based (TB) PPDU (physical layer protocol data unit) including a data portion based on the DRU to the second STA over a bandwidth, The tones of the above DRU are distributed based on the DRU tone plan for the distributed bandwidth within the above bandwidth, The above TB PPDU includes an LTF (long training field) portion that is constructed based on an LTF sequence, A method wherein the LTF sequence is configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient according to two fixed values.

2. In paragraph 1, The above DRU tone plan includes a large-sized DRU composed of a combination of smaller-sized DRUs, A method wherein the LTF sequence for the large-sized DRU is constructed based on the LTF sequence for the small-sized DRUs.

3. In paragraph 1, A method wherein the above specific sequence is applied to 26 tone indices of each 26-tone DRU of the DRU tone plan.

4. In paragraph 1, A method in which, for the specific sequence for composing the LTF sequence, at least one of a first process of reversing the order of coefficients of the specific sequence or a second process of multiplying the specific sequence by a value of -1 is applied.

5. In paragraph 1, The two fixed values ​​above are 1 and -1, The above specific sequence is based on one of the following eight sequences, Sequence 1 = [-1 1 -1 1 -1 1 1 1 -1 1 1 1 -1 -1 1 -1 -1 -1 -1 -1 1 1 -1 -1 -1 -1], Sequence 2 = [1 1 -1 1 -1 1 1 1 1 -1 1 -1 -1 1 1 -1 1 1 1 1 -1 -1 1 -1 -1 -1], Sequence 3 = [-1 -1 -1 -1 1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 1 1 1 -1 -1 1 -1], Sequence 4 = [1 1 1 1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 1 1 1 -1 -1 1 1 1], Sequence 5 = [1 1 1 1 -1 1 1 -1 -1 1 -1 1 1 1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1], Sequence 6 = [1 1 1 1 1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 1 -1 1 1 -1 1 -1], Sequence 7 = [1 1 1 1 -1 -1 1 1 1 1 1 -1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 1], Sequence 8 = [1 -1 1 -1 1 1 1 1 -1 -1 -1 1 1 1 1 1 1 1 1 -1 1 -1 -1 1 1 -1].

6. In paragraph 1, The size of the above distributed bandwidth is 20MHz, The above LTF sequence is [0 0 0 0 0 0 0 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 1 1 -1 -1 -1 -1 1 1 -1 -1 1 1 1 1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 1 1 1 -1 -1 -1 1 1 -1 1 1 1 1 1 0 0 0 -1 -1 1 1 -1 -1 1 -1 1 -1 1 1 -1 -1 -1 1 1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 1 -1 1 1 -1 1 -1 -1 -1 1 -1 1 1 -1 1 -1 -1 1 1 1 -1 1 1 -1 1 -1 -1 1 1 1 -1 1 1 -1 -1 -1 -1 1 0 0 0 0 0 0 0], A method in which the above LTF sequence is applied to tone indices [-128 to 127].

7. In paragraph 1, The size of the above distributed bandwidth is 40MHz, The above LTF sequence is [0 0 0 0 0 0 0 0 0 0 0 0 -1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 -1 1 -1 -1 -1 1 1 -1 -1 -1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 -1 1 -1 1 -1 -1 -1 1 -1 -1 1 1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 1 1 -1 -1 1 1 -1 1 -1 1 -1 1 1 1 1 -1 -1 1 1 1 1 -1 -1 -1 1 1 -1 -1 1 1 -1 -1 -1 1 -1 -1 1 1 -1 -1 1 1 -1 -1 1 -1 -1 1 1 -1 -1 1 -1 1 -1 1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 -1 1 -1 1 -1 -1 1 -1 1 1 -1 0 0 0 0 -1 1 -1 -1 1 1 -1 -1 -1 1 1 -1 -1 -1 -1 1 -1 -1 1 -1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 1 1 1 1 1 -1 -1 -1 -1 -1 -1 -1 1 1 1 1 -1 1 1 1 1 -1 1 1 1 1 1 -1 -1 1 -1 -1 -1 1 -1 -1 1 -1 -1 1 1 1 1 -1 -1 1 1 -1 1 1 -1 -1 1 -1 -1 -1 -1 1 -1 1 1 -1 1 1 1 -1 1 1 -1 -1 -1 1-1 -1 1 -1 1 1 1 1 -1 1 -1 -1 1 1 1 -1 1 -1 -1 1 -1 -1 -1 1 1 -1 1 1 -1 1 1 1 1 -1 1 1 -1 -1 -1 1 1 1 1 1 -1 -1 -1 1 1 1 -1 -1 -1 1 1 -1 1 -1 -1 1 1 -1 1 1 -1 -1 1 1 -1 1 1 -1 1 1 -1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 -1 1 1 1 -1 1 0 0 0 0 0 0 0 0 0 0 0 0], A method in which the above LTF sequence is applied to tone indices [-256 to 255].

8. In paragraph 1, A method in which the number of symbols in the above LTF portion is set based on the number of spatial streams transmitted from the DRU.

9. In paragraph 8, Based on the number of the above spatial streams being 1, the number of symbols of the LTF portion is 1, A method in which the number of symbols of the LTF portion is 2, based on the number of the spatial streams being 2.

10. In paragraph 1, A method wherein the information related to the DRU includes first information on whether the DRU or regular RU (RRU) is applied and second information on the distributed bandwidth to which the DRU is applied.

11. In paragraph 10, The above first information is included in the common information field within the trigger frame, A method wherein the second information is included in a user information field for the first STA in the trigger frame.

12. In paragraph 11, A method wherein the first information includes a subfield for indicating whether to apply a DRU or an RRU in units of frequency subblocks of a certain size.

13. In paragraph 11, A method wherein the user information field further includes an RU allocation subfield for allocating one or more DRUs within the distributed bandwidth.

14. One or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receive a trigger frame containing information related to a distributed resource unit (DRU); Set to transmit a trigger-based (TB) PPDU (physical layer protocol data unit) containing a data portion based on the above DRU over the bandwidth, The tones of the above DRU are distributed based on the DRU tone plan for the distributed bandwidth within the above bandwidth, The above TB PPDU includes an LTF (long training field) portion that is constructed based on an LTF sequence, A method wherein the LTF sequence is configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient according to two fixed values.

15. A step of transmitting a trigger frame including information related to a distributed resource unit (DRU) to a first STA by a second station (STA); and A step of receiving, by the second STA, a trigger-based (TB) PPDU (physical layer protocol data unit) including a data portion based on the DRU from the first STA over a bandwidth, The tones of the above DRU are distributed based on the DRU tone plan for the distributed bandwidth within the above bandwidth, The above TB PPDU includes an LTF (long training field) portion that is constructed based on an LTF sequence, A method wherein the LTF sequence is configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient according to two fixed values.

16. One or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting a trigger frame containing information related to a distributed resource unit (DRU); Set to receive a trigger-based (TB) PPDU (physical layer protocol data unit) containing a data portion based on the above DRU over the bandwidth, The tones of the above DRU are distributed based on the DRU tone plan for the distributed bandwidth within the above bandwidth, The above TB PPDU includes an LTF (long training field) portion that is constructed based on an LTF sequence, A device wherein the LTF sequence is configured based on a specific sequence consisting of a DRU tone plan for the distributed bandwidth and a coefficient according to two fixed values.

17. In a processing device configured to control a station (STA) in a wireless local area network (WLAN) system, the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions that, when executed by said one or more processors, perform a method according to any one of claims 1 to 13.

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

Images