Transmission or reception method and apparatus based on distributed resource unit tone plan in wireless LAN system

Abstract

Disclosed are a transmitting or receiving method and apparatus in a wireless LAN system based on a distributed resource unit tone plan. The method according to an embodiment of the disclosure can include the steps of a first station (STA) generating a physical layer protocol data unit (PPDU) including one or more fields; and the first STA transmitting the PPDU to one or more second STAs over a bandwidth including a 20 MHz channel. Here, the one or more fields can be transmitted over one or more distributed resource units (DRUs).

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for transmitting or receiving based on a distributed resource unit tone scheme in a wireless local area network (WLAN) system. Background Technology

[0002] New technologies have been introduced to Wireless LANs (WLANs) to improve transmission rates, increase bandwidth, improve reliability, reduce errors, and reduce latency. Within WLAN technologies, the IEEE 802.11 series of standards can be referred to as Wi-Fi. For example, recent technologies introduced to WLAN include enhancements to the Very High Throughput (VHT) of the 802.11ac standard and enhancements to the High Efficiency (HE) of the IEEE 802.11ax standard.

[0003] To provide a more robust wireless communication environment, enhancement technologies for EHT (Extreme High Throughput) are being discussed. For example, technologies for supporting multi-access point (AP) coordination and multiple-input multiple-output (MIMO) to increase bandwidth, effectively utilize multiple bands, and increase spatial flow are being investigated. In particular, various technologies are being explored to support low-latency or real-time services. Furthermore, new technologies to support Ultra-High Reliability (UHR) through improvements or extensions to EHT technologies are being discussed. Summary of the Invention

[0004] Technical issues

[0005] The technical problem of this disclosure is to provide a method and apparatus for transmitting or receiving based on a distributed resource unit tone scheme in a WLAN system.

[0006] The technical objectives achieved through this disclosure are not limited to those described above, and those skilled in the art will clearly understand from the following description other technical objectives not described herein.

[0007] Technical solution

[0008] A method according to one aspect of this disclosure may include: a first station (STA) receiving a trigger frame from a second STA, comprising information on resource allocation for one or more Distributed Resource Units (DRUs); and the first STA transmitting trigger-based (TB) Physical Layer Protocol Data Units (PPDUs) to the second STA in a bandwidth comprising a 40 MHz channel, based on one or more DRUs. Here, the one or more DRUs include 26-tone DRUs, which are one of 18 predefined 26-tone DRU candidates, and the 18 26-tone DRU candidates may be defined based on the exclusion of available tones from Direct Conversion (DC) tones, guard tones, the first empty tone group, and the second empty tone group.

[0009] A method according to another aspect of this disclosure may include: a second station (STA) sending a trigger frame to a first STA, including information on resource allocation for one or more Distributed Resource Units (DRUs); and the second STA receiving trigger-based (TB) Physical Layer Protocol Data Units (PPDUs) from the first STA in a bandwidth including a 40 MHz channel, based on one or more DRUs. Here, the one or more DRUs include 26-tone DRUs, which are one of 18 predefined 26-tone DRU candidates, and the 18 26-tone DRU candidates may be defined based on available tones excluding Direct Conversion (DC) tones, guard tones, the first empty tone group, and the second empty tone group.

[0010] Beneficial effects

[0011] According to this disclosure, a method and apparatus for transmitting or receiving based on a distributed resource unit tone scheme in a WLAN system can be provided.

[0012] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art will clearly understand from the following description other effects not described herein. Attached Figure Description

[0013] The accompanying drawings, included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0014] Figure 1 The figure shows a block configuration diagram of a wireless communication device according to an embodiment of the present disclosure.

[0015] Figure 2 This is a diagram illustrating an exemplary structure of a WLAN system to which this disclosure can be applied.

[0016] Figure 3 It is a diagram used to describe the link setup process to which this disclosure can be applied.

[0017] Figure 4 It is a diagram used to describe the retreat process to which this disclosure can be applied.

[0018] Figure 5 This is a diagram used to describe the CSMA / CA-based frame transmission operation to which this disclosure can be applied.

[0019] Figure 6 This is a diagram illustrating an example of a frame structure that can be used in a WLAN system to which this disclosure may be applied.

[0020] Figure 7This is a diagram illustrating an example of a PPDU that can be applied in the IEEE 802.11 standard of this disclosure.

[0021] Figure 8 This is a diagram illustrating an example of a resource unit that can be used in a WLAN system according to this disclosure.

[0022] Figure 9 This is a diagram illustrating another example of a resource unit for a WLAN system to which the present disclosure can be applied.

[0023] Figure 10 This is a diagram illustrating another example of a resource unit for a WLAN system to which the present disclosure can be applied.

[0024] Figure 11 This is a diagram used to describe an example of a DRU to which this disclosure can be applied.

[0025] Figure 12 This is a diagram illustrating an exemplary format of the trigger frame to which the present disclosure may be applied.

[0026] Figure 13 Examples of DRU tone schemes and pilot tones according to embodiments of the present disclosure are shown.

[0027] Figure 14 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0028] Figure 15 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0029] Figure 16 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0030] Figure 17 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0031] Figure 18 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0032] Figure 19 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0033] Figure 20 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0034] Figure 21 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0035] Figure 22 This is a diagram illustrating an example of the operation of the first STA in a PPDU transmission and reception method based on a DRU tone scheme according to this disclosure.

[0036] Figure 23 This is a diagram illustrating an example of the operation of the second STA in a PPDU transmission and reception method based on a DRU tone scheme according to this disclosure.

[0037] Figure 24 This is a diagram illustrating the PPDU transmission and reception process between the transmitting STA and the receiving STA according to embodiments of the present disclosure. Detailed Implementation

[0038] In the following, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of the present disclosure and not to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure may be practiced without these specific details.

[0039] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0040] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections where another element exists therebetween. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0041] In this invention, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0042] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of the embodiments and the appended claims, the singular forms are intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this disclosure has the same meaning as “and / or”.

[0043] The examples disclosed herein can be applied to various wireless communication systems. For example, the examples disclosed herein can be applied to wireless LAN systems. For example, the examples disclosed herein can be applied to wireless LANs based on the IEEE 802.11a / g / n / ac / ax standards. Furthermore, the examples disclosed herein can be applied to wireless LANs based on the newly proposed IEEE 802.11be (or EHT) standard. The examples disclosed herein can be applied to wireless LANs based on the IEEE 802.11be version 2 standard, corresponding to the additional enhancements of the IEEE 802.11be version 1 standard. Additionally, the examples disclosed herein can be applied to next-generation standards-based wireless LANs following IEEE 802.11be. Furthermore, the examples disclosed herein can be applied to cellular wireless communication systems. For example, it can be applied to cellular wireless communication systems based on 3GPP standards using Long Term Evolution (LTE) technology and 5G New Radio (NR) technology.

[0044] The technical features that can be applied to examples of this disclosure will be described below.

[0045] Figure 1 The figure shows a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0046] Figure 1 The first device 100 and the second device 200 illustrated in the diagram can be replaced by various terms, such as terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), mobile subscriber unit (MSU), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT), or simple user, etc. Furthermore, the first device 100 and the second device 200 can include access point (AP), base station (BS), fixed station, node B, base transceiver system (BTS), and network. It can be replaced by various terms such as artificial intelligence (AI) system, roadside unit (RSU), repeater, router, relay, and gateway.

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

[0048] refer to Figure 1 The first device 100 and the second device 200 can transmit and receive radio signals via various wireless LAN technologies (e.g., the IEEE 802.11 series). The first device 100 and the second device 200 may include interfaces for the Media Access Control (MAC) layer and Physical Layer (PHY) conforming to the IEEE 802.11 standard.

[0049] Furthermore, the first device 100 and the second device 200 can additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) besides wireless LAN technology. Additionally, the devices disclosed herein can be implemented in various devices, such as mobile phones, vehicles, personal computers, augmented reality (AR) devices, virtual reality (VR) devices, etc. Furthermore, the STA of this specification can support various communication services, such as voice calls, video calls, data communication, autonomous driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), IoT (Internet of Things), etc.

[0050] The first device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceiver 106 after generating first information / signal by processing information in the memory 104. Additionally, the processor 102 may receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained through signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing all or part of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless LAN technologies (e.g., IEEE 802.11 series). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, "device" may refer to a communication modem / circuit / chip.

[0051] The second device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. For example, the processor 202 may generate third information / signals by processing information in the memory 204, and then transmit a wireless signal including the third information / signals via the transceiver 206. Additionally, the processor 202 may receive wireless signals including fourth information / signals via the transceiver 206, and then store information obtained through 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 store software code including instructions for performing all or part of the processes controlled by the processor 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless LAN technologies (e.g., IEEE 802.11 series). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, "device" may refer to a communication modem / circuit / chip.

[0052] The hardware components of devices 100 and 200 will be described in more detail below. However, they are not limited thereto, but one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY and MAC). One or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure to provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure.

[0053] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In examples, one or more ASICs (Application-Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field-Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this invention may be implemented by firmware or software in the form of code, commands, and / or command sets.

[0054] One or more memories 104, 204 may be connected to one or more processors 102, 202 and are capable of storing data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0055] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected 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. Furthermore, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure via one or more antennas 108, 208. In this invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may process the received wireless signals / channels, etc., by converting them from RF band signals to baseband signals using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0056] For example, one of STAs 100 and 200 can perform the expected operation of an AP, and the other of STAs 100 and 200 can perform the expected operation of a non-AP STA. Figure 1 Transceivers 106 and 206 can perform transmission and reception operations of signals (e.g., packet or physical layer protocol data units (PPDUs) conforming to IEEE 802.11a / b / g / n / ac / ax / be). Furthermore, in this disclosure, the operations of generating transmit / receive signals or performing data processing or calculations on transmit / receive signals in advance by various STAs can be performed by… Figure 1 Processors 102 and 202 perform the following operations: For example, examples of generating transmit / receive signals or performing data processing or calculations on transmit / receive signals in advance may include 1) determining / acquiring / configuring / calculating / decoding / encoding bit information of fields (signals (SIG), short training field (STF), long training field (LTF), data, etc.) included in the PPDU; 2) determining / configuring / acquiring time resources or frequency resources (e.g., subcarrier resources) for the fields (SIG, STF, LTF, data, etc.) included in the PPDU; 3) determining / configuring / acquiring specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the fields (SIG, STF, LTF, data, etc.) included in the PPDU action; 4) power control operations and / or power-saving operations applied to the STA; and 5) operations related to determining / acquiring / configuring / calculating / encoding the ACK signal. Additionally, in the following examples, various information used by various STAs to determine / acquire / configure / calculate / decode / encode transmitted and received signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) can be stored. Figure 1 In memory 104 and 204.

[0057] In the following text, downlink (DL) can refer to a link used for communication from an AP STA to a non-AP STA, and DL PPDUs / packets / signals can be sent and received via DL. In DL communication, the transmitter can be part of an AP STA, and the receiver can be part of a non-AP STA. Uplink (UL) can refer to a link used for communication from a non-AP STA to an AP STA, and UL PPDUs / packets / signals can be sent and received via UL. In UL communication, the transmitter can be part of a non-AP STA, and the receiver can be part of an AP STA.

[0058] Figure 2 This is a diagram illustrating an exemplary structure of a wireless LAN system to which this disclosure can be applied.

[0059] A wireless LAN system can be structured by multiple components. Wireless LANs that support STA mobility transparent to upper layers can be provided through the interaction of these components. The Basic Services Set (BSS) corresponds to the basic building blocks of a wireless LAN. Figure 2 An example is shown where there are two BSSs (BSS1 and BSS2) and two STAs are included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). Figure 2 The ellipse representing the BSS can also be interpreted as representing the coverage area within the corresponding BSS where STAs maintain communication. This area can be called the Basic Service Area (BSA). When a STA moves out of the BSA, it cannot directly communicate with other STAs within the BSA.

[0060] If we do not consider Figure 2 The DS shown represents the most basic type of BSS in a wireless LAN, which is the Independent BSS (IBSS). For example, an IBSS can have a minimal form containing only two STAs. For instance, assuming other components are omitted, BSS1 containing only STA1 and STA2, or BSS2 containing only STA3 and STA4, can respectively correspond to representative examples of IBSS. This configuration is possible when STAs can communicate directly without an AP. Furthermore, in this type of wireless LAN, it is not pre-configured but can be configured when a LAN is needed, and this can be called a self-organizing network. Because 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 an IBSS, all STAs can consist of mobile STAs and are not allowed to access the Distributed System (DS), thus forming a self-contained network.

[0061] A STA's membership in the BSS can be dynamically changed by opening or closing the STA, entering or leaving a BSS zone, etc. To become a member of the BSS, an STA can join the BSS using a synchronization process. To access all services of the BSS infrastructure, an STA should be associated with the BSS. This association can be established dynamically and can include the use of Distributed System Services (DSS).

[0062] Direct STA-to-STA distance in a wireless LAN can be limited by PHY performance. In some cases, this distance limit may be sufficient, but in others, communication between STAs at greater distances may be required. Distributed systems (DS) can be configured to support extended coverage.

[0063] DS refers to the interconnected structure of BSSs. Specifically, such as... Figure 2As shown, a BSS can exist as an extension of a network composed of multiple BSSs. A DS is a logical concept and can be specified by the characteristics of the Distributed System Medium (DSM). In this respect, the Wireless Medium (WM) and the DSM can be logically separated. Each logical medium is used for a different purpose and by different components. These media are not limited to being the same, nor are they limited to being different. Thus, the flexibility of wireless LAN architectures (DS architectures or other network architectures) can be interpreted as multiple media being logically different. That is, wireless LAN architectures can be implemented in various ways, and the corresponding wireless LAN architectures can be independently specified by the physical characteristics of each embodiment.

[0064] DS can support mobile devices by providing seamless integration of multiple BSSs and the logical services necessary for address addressing to the destination. Additionally, DS can further include a component called a portal, which acts as a bridge for connections between the wireless LAN and other networks, such as IEEE 802.X.

[0065] An AP enables access to a DS via WM for its associated non-AP STA, and this implies an entity that also functions as a STA. Data movement between the BSS and DS can be performed through the AP. For example, Figure 2 STA2 and STA3, as shown, possess the functionality of STAs and provide the ability for associated non-AP STAs (STA1 and STA4) to access the DS. Furthermore, since all APs essentially correspond to STAs, all APs are addressable entities. The address used by an AP for communication on the WM is not necessarily the same as the address used by an AP for communication on the DSM. A BSS consisting of APs and one or more STAs can be referred to as an infrastructure BSS.

[0066] Data sent from one of the STAs associated with the AP to the STA address of the corresponding AP can always be received on an uncontrolled port and can be processed by an IEEE 802.1X port access entity. Alternatively, when the controlled port is authenticated, transmitted data (or frames) can be delivered to the DS.

[0067] In addition to the DS structure described above, an Extended Service Set (ESS) can be configured to provide broad coverage.

[0068] An ESS (Service Set Identity) refers to a network of arbitrary size and complexity consisting of DS (Service Controller) and BSS (Service Set Service). An ESS can correspond to a set of BSSs connected to a DS. However, an ESS does not include the DS. An ESS network is characterized by being treated as an IBSS (Independent Service Set Service) within the Logical Link Control (LLC) layer. STAs included in an ESS can communicate with each other, and a mobile STA can move from one BSS to another BSS (within the same ESS), which is transparent to the LLC. APs included in an ESS can have the same Service Set Identity (SSID). The SSID is distinct from the BSSID, which is the identifier of the BSS.

[0069] Wireless LAN systems do not assume anything about the relative physical location of BSSs, and all of the following forms are possible. BSSs can partially overlap, which is a common form used to provide continuous coverage. Additionally, BSSs may not have physical connections, and logically, there is no limit to the distance between BSSs. Furthermore, BSSs may be physically located in the same location, which can be used to provide redundancy. Additionally, one (or more) IBSS or ESS networks can physically exist in the same space as one (or more) ESS networks. This can be analogous to the form corresponding to ESS networks when an ad hoc network operates in a location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location.

[0070] Figure 3 This is a diagram used to explain the link setup process to which this disclosure can be applied.

[0071] For a STA to establish a link to the network and send / receive data, the network must first be discovered, authentication performed, and association established. A security authentication process is also required. This link establishment process can also be called the session initiation process or session setup process. Furthermore, the discovery, authentication, association, and security settings within the link establishment process can be collectively referred to as the association process.

[0072] In step S310, the STA can perform a network discovery operation. The network discovery operation may include a scanning operation by the STA. That is, in order for the STA to access the network, it needs to find networks it can participate in. Before participating in a wireless network, the STA should identify compatible networks, and the process of identifying networks present in a specific area is called scanning.

[0073] Scanning schemes include active scanning and passive scanning. Figure 3An exemplary illustration depicts a network discovery operation including an active scanning process. In an active scan, the STA performing the scan sends probe request frames while moving channels to discover which APs are present in its vicinity and awaits a response. A responder sends a probe response frame to the STA that sent the probe request frame as a response to the probe request frame. Here, the responder could be the STA that last sent a beacon frame in the BSS of the scanned channel. In the BSS, the AP becomes the responder because it sends a beacon frame, and in the IBSS, STAs in the IBSS take turns sending beacon frames, so the responder is not constant. For example, an STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information included in the received probe response frame and can move to the next channel (e.g., channel 2) and perform a scan in the same manner (i.e., sending / receiving probe requests / responses on channel 2).

[0074] Although Figure 3 Although not shown, scanning operations can be performed passively. In passive scanning, the STA performing the scan waits for beacon frames while moving through different channels. Beacon frames are one of the management frames defined in IEEE 802.11 and are sent periodically to notify of the existence of a wireless network and allow the STA performing the scan to find and participate in the network. In a BSS, the AP uses beacon frames to send them periodically, and in an IBSS, STAs within the IBSS take turns sending beacon frames. When a STA performing the scan receives a beacon frame, it stores the BSS information included in the beacon frame and records the beacon frame information for each channel while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform the scan in the next channel in the same manner. Comparing active and passive scanning, active scanning has the advantages of lower latency and lower power consumption.

[0075] After the STA discovers the network, an authentication process can be performed in step S320. To clearly distinguish this authentication process from the security setup operation in step S340, which will be described later, this authentication process can be referred to as the first authentication process.

[0076] The authentication process includes the STA sending an authentication request frame to the AP, and in response, the AP sending an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to the management frame.

[0077] The authentication frame includes the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and finite cycle group, etc. This corresponds to some examples of information that can be included in the authentication request / response frame, and may be replaced with other information or may include further additional information.

[0078] A STA can send an authentication request frame to an AP. The AP can determine whether to allow the corresponding STA to authenticate based on the information included in the received authentication request frame. The AP can then provide the result of the authentication process to the STA via an authentication response frame.

[0079] After successful STA authentication, the association process can be performed in step S330. The association process includes the STA sending an association request frame to the AP, and in response, the AP sending an association response frame to the STA.

[0080] For example, an association request frame may include information related to various capabilities, beacon listening intervals, service set identifiers (SSIDs), supported rates, supported channels, RSNs, mobile domains, supported operation classes, service indication map broadcast requests (TIM broadcast requests), and interoperability capabilities. Similarly, an association response frame may include information related to various capabilities, status codes, association IDs (AIDs), supported rates, enhanced distributed channel access (EDCA) parameter sets, received channel power indicators (RCPIs), received signal-to-noise ratio indicators (RSNIs), mobile domains, timeout intervals (e.g., association recovery time), overlapping BSS scan parameters, TIM broadcast responses, and quality of service (QoS) maps. These correspond to examples of information that can be included in association request / response frames and may be replaced with other information or further supplementary information.

[0081] After the STA successfully associates with the network, a security setup process can be performed in step S340. The security setup process in step S340 can be referred to as the authentication process via a Robust Secure Network Association (RSNA) request / response, and the authentication process in step S320 is referred to as the first authentication process. The security setup process in step S340 can also be simply referred to as the authentication process.

[0082] The security setup process in step S340 may include, for example, a process of establishing a private key via a four-way handshake using Extensible Authentication Protocol (EAPOL) frames over a LAN. Alternatively, the security setup process may be performed according to a security scheme not defined in the IEEE 802.11 standard.

[0083] Figure 4 This is a diagram used to explain the retreat process to which this disclosure can be applied.

[0084] In wireless LAN systems, the basic access mechanism for Media Access Control (MAC) is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). Also known as the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, CSMA / CA essentially employs a "listen-before-speak" access mechanism. Under this type of access mechanism, the AP and / or STA can perform a sensed free channel assessment (CCA) of the wireless channel or medium within a predetermined time interval (e.g., the DCF inter-frame interval (DIFS)) before initiating transmission. As a result of the sensing, if the medium is determined to be idle, frame transmission begins through the corresponding medium. Conversely, if the medium is detected to be occupied or busy, the corresponding AP and / or STA does not initiate its own transmission and can set a delay period for medium intervention (e.g., a random backoff period) and attempt frame transmission after waiting. By applying a random backoff period, collisions can be minimized because several STAs are expected to attempt frame transmission after waiting for different time periods.

[0085] In addition, the IEEE 802.11 MAC protocol provides Hybrid Coordination Function (HCF). HCF is based on DCF and Point Coordination Function (PCF). PCF is a polling-based synchronous access method, referring to a method in which all receiving APs and / or STAs periodically poll to receive data frames. Furthermore, HCF includes Enhanced Distributed Channel Access (EDCA) and HCF-Controlled Channel Access (HCCA). EDCA is a contention-based access method used by providers to deliver data frames to multiple users, while HCCA uses a polling mechanism to employ a non-contention-based channel access method. Additionally, HCF includes a media access mechanism for improving the QoS (Quality of Service) of wireless LANs and can transmit QoS data in both contention-based (CP) and contention-free (CFP) periods.

[0086] refer to Figure 4 This section describes the operation based on a random backoff period. When a occupied / busy medium becomes idle, several STAs may attempt to transmit data (or frames). As a method to minimize collisions, each STA can individually select a random backoff count and attempt transmission after waiting for the corresponding time slot. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​from 0 to CW. Here, CW is the contention window parameter value. The CW parameter is assigned an initial value of CWmin, but can take a value twice as large if a transmission failure occurs (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value reaches CWmax, data transmission can be attempted while maintaining the CWmax value until successful data transmission, and the CWmin value is reset when data transmission is successful. The values ​​of CW, CWmin, and CWmax are preferably set to 2.n -1 (n = 0, 1, 2, ...).

[0087] When the random backoff process begins, the STA continuously monitors the medium while counting down the backoff time slot based on the determined backoff count value. When medium occupancy is detected, it stops counting down and waits, and resumes the remaining countdown when the medium becomes free.

[0088] exist Figure 4 In the example, when the packet to be sent arrives at STA3's MAC, STA3 can send the frame immediately after confirming that the medium is free for as long as DIFS. The remaining STAs monitor and wait for the medium to be occupied / busy. Meanwhile, data to be sent may also occur in each of STA1, STA2, and STA5, and when the medium is detected as free, each STA waits for as long as DIFS, and can then count down the backoff slots according to a random backoff count value selected by each STA. Assume that STA2 chooses the minimum backoff count value, and STA1 chooses the maximum backoff count value. That is, the case where STA5's remaining backoff time is less than STA1's remaining backoff time when STA2 completes its backoff count and begins frame transmission is illustrated. STA1 and STA5 temporarily stop the countdown and wait, while STA2 occupies the medium. When STA2 finishes occupying the medium and it becomes free again, STA1 and STA5 wait for DIFS and resume the stopped backoff count. That is, after counting down the remaining backoff slots for the remaining backoff time, frame transmission can begin. Because STA5's remaining backoff time is less than STA1's, STA5 begins frame transmission. While STA2 is occupying the medium, data to be transmitted may also appear in STA4. From STA4's perspective, when the medium becomes idle, STA4 can wait for DIFS, and then execute a countdown based on a random backoff count value selected by STA4 and begin transmitting frames. Figure 4 The example illustrates a scenario where the remaining backoff time of STA5 coincides exactly with the random backoff count of STA4. In this case, a collision may occur between STA4 and STA5. When a collision occurs, neither STA4 nor STA5 receives an ACK, thus data transmission fails. In this situation, STA4 and STA5 can double their CW value, choose a random backoff count, and begin a countdown. STA1 waits while the medium is occupied due to the transmissions of STA4 and STA5, waits for DIFS when the medium becomes idle, and then begins frame transmission after the remaining backoff time has elapsed.

[0089] like Figure 4As shown in the example, data frames are frames used to transmit data forwarded to higher layers and can be sent after a backoff performed after the DIFS (Distributed Access Frame) begins to elapse when the medium becomes idle. Management frames, on the other hand, are frames used to exchange management information that is not forwarded to higher layers and are sent after a backoff performed after an IFS (Initial Point Coordination Function) such as a DIFS or a Point Coordination Function IFS (PIFS). Subtypes of management frames include beacons, association requests / responses, reassociation requests / responses, probe requests / responses, authentication requests / responses, etc. Control frames are frames used to control access to the medium. Subtypes of control frames include request to send (RTS), clear send (CTS), acknowledgment (ACK), power-saving polling (PS-Poll), block ACK (BlockAck), block ACK request (BlockACKReq), null data packet announcement (NDP announcement), and triggers, etc. If a control frame is not a response frame to a previous frame, it is sent after a backoff performed after the DIFS elapses; if it is a response frame to a previous frame, it is sent without a backoff performed after the short IFS (SIFS) elapses. The type and subtype of a frame can be identified by the type field and subtype field in the Frame Control (FC) field.

[0090] The Quality of Service (QoS) ST can perform a backoff following the Arbitration IFS (AIFS) of the Access Class (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), and then the frame can be sent. Here, frames that can use AIFS[i] can be data frames, management frames, or control frames other than response frames.

[0091] Figure 5 This is a diagram used to explain the CSMA / CA-based frame transmission operation to which this disclosure can be applied.

[0092] As mentioned above, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, which is directly sensed by the STA. Virtual carrier sensing is designed to compensate for problems that may arise in media access, such as hidden node issues. For virtual carrier sensing, the STA's MAC can use a Network Allocation Vector (NAV). A NAV is a value that indicates to other STAs the remaining time until the media becomes available for use by the currently using or authorized STA. Therefore, a value set to NAV corresponds to a period of time during which the media is scheduled for use by the STA sending the frame, and a STA receiving the NAV value is prohibited from accessing the media during the corresponding period. For example, NAV can be configured based on the value of the "Duration" field in the frame's MAC header.

[0093] exist Figure 5In the example, assume that STA1 intends to send data to STA2, and STA3 is in a position that allows it to eavesdrop on some or all of the frames being sent and received between STA1 and STA2.

[0094] To reduce the likelihood of transmission conflicts between multiple STAs in CSMA / CA-based frame transmission operations, a mechanism using RTS / CTS frames can be applied. Figure 5 In the example, while STA1 is transmitting, as a result of STA3's carrier sensing, it can be determined that the medium is in an idle state. That is, STA1 can correspond to a hidden node of STA3. Alternatively, in Figure 5 In the example, it can be determined that the carrier sensing result medium of STA3 is idle while the transmission of STA2 is being performed. That is, STA2 can correspond to a hidden node of STA3. By exchanging RTS / CTS frames before 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, can not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0095] Specifically, STA1 can determine whether a channel is in use through carrier sensing. Regarding physical carrier sensing, STA1 can determine the channel occupancy status based on the energy level or signal correlation detected in the channel. Furthermore, regarding virtual carrier sensing, STA1 can use a network allocation vector (NAV) timer to determine the channel occupancy status.

[0096] When the channel is idle during DIFS, STA1 can send an RTS frame to STA2 after performing backoff. When STA2 receives the RTS frame, STA2 can send a CTS frame to STA1 after SIFS as a response to the RTS frame.

[0097] If STA3 cannot eavesdrop on CTS frames from STA2 but can eavesdrop on RTS frames from STA1, STA3 can use the duration information included in the RTS frame to set the NAV timer for subsequent consecutive frame transmission cycles (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame). Alternatively, if STA3 can eavesdrop on CTS frames from STA2, even though STA3 cannot eavesdrop on RTS frames from STA1, STA3 can use the duration information included in the CTS frame to set the NAV timer for subsequent consecutive frame transmission cycles (e.g., SIFS+data frame+SIFS+ACK frame). That is, if STA3 can eavesdrop on one or more RTS or CTS frames from STA1 or STA2, STA3 can set the NAV accordingly. When STA3 receives a new frame before the NAV timer expires, STA3 can use the duration information included in the new frame to update the NAV timer. STA3 does not attempt channel access before the NAV timer expires.

[0098] When STA1 receives a CTS frame from STA2, STA1 can send a data frame to STA2 after the SIFS period starting from the time when the CTS frame reception is completed. When STA2 successfully receives the data frame, STA2 can send an ACK frame to STA1 as a response to the data frame after the SIFS period. When the NAV timer expires, STA3 can determine whether the channel is being used through carrier sensing. When STA3 determines that the channel is not being used by other terminals during the DIFS period after the NAV timer expires, STA3 can attempt channel access after the contention window (CW) for random backoff has elapsed.

[0099] Figure 6 This is a diagram used to explain an example of the frame structure that can be used in a WLAN system to which this disclosure can be applied.

[0100] Using instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare a MAC PDU (MPDU) to be sent. For example, when it receives a command from the MAC layer requesting the PHY layer to begin transmission, the PHY layer switches to transport mode and configures the information (e.g., data) provided from the MAC layer in the form of a frame and sends it. Additionally, when the PHY layer detects a valid preamble to a received frame, it monitors the preamble header and sends a command to the MAC layer notifying the PHY layer of the start of reception.

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

[0102] A basic PPDU frame can include a Short Training Field (STF), a Long Training Field (LTF), a Signal (SIG) field, and a Data field. The most basic PPDU format (e.g., Figure 7 The non-HT (high throughput) fields shown may consist only of legacy STF (L-STF), legacy LTF (L-LTF), legacy SIG (L-SIG) fields, and a data field. Additionally, depending on the PPDU format type (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 fields, non-legacy STF, non-legacy LTF (i.e., xx-SIG, xx-STF, xx-LTF (e.g., xx is HT, VHT, HE, EHT, etc.)) may be included between the L-SIG field and the data field.

[0103] STF is a signal used for signal detection, automatic gain control (AGC), diversity selection, precise time synchronization, etc., while LTF is a signal used for channel estimation and frequency error estimation. STF and LTF can be referred to as signals used for synchronization and channel estimation in the OFDM physical layer.

[0104] The SIG field can include various information related to PPDU transmission and reception. For example, the L-SIG field consists of 24 bits and can 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 can include information about the modulation and coding rate of the data. For example, the 12-bit length field can include information about the length or duration of the PPDU. For example, the value of the 12-bit length field can be determined based on the type of PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the length field can be determined to be a multiple of 3. For example, for HE PPDUs, the value of the length field can be determined to be a multiple of 3 + 1 or 3 + 2.

[0105] The data field may include a SERVICE field, a Physical Layer Service Data Unit (PSDU), and a PPDU TAIL bit, and may also include padding bits if necessary. Some bits of the SERVICE field can be used for synchronization of the descrambler at the receiver. The PSDU corresponds to the MAC PDU defined in the MAC layer and may include data generated / used in the upper layer. The PPDU TAIL bit can be used to return the encoder to a 0 state. Padding bits can be used to adjust the length of the data field in predetermined units.

[0106] 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). MAC frames can be composed of MAC PDUs and are transmitted / received via the PSDU in the data portion of the PPDU frame format.

[0107] The MAC header includes a frame control field, a duration / ID field, and an address field. The frame control field can include control information required for frame transmission / reception. The duration / ID field can be set to the time for transmitting the corresponding frame. For detailed information on the sequence control, QoS control, and HT control subfields of the MAC header, please refer to the IEEE 802.11 standard document.

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

[0109] Figure 7 This is a diagram illustrating an example of a PPDU as defined in the IEEE 802.11 standard that can be applied to this disclosure.

[0110] Various types of PPDUs are used in standards such as IEEE 802.11a / g / n / ac / ax. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and a data field. The basic PPDU format can also be referred to as a non-HT PPDU format (e.g., ...). Figure 7 (as shown in (a)).

[0111] In addition to the basic PPDU format, the HT PPDU format (IEEE 802.11n) also includes the HT-SIG, HT-STF and HT-LFT fields. Figure 7 The HT PPDU format shown in (b) can be called the HT-mixed format. Alternatively, an HT-greenfield format PPDU can be defined, which corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs and a data field, excluding L-STF, L-LTF and L-SIG (not shown).

[0112] Examples of VHT PPDU format (IEEE 802.11ac) include, in addition to the basic PPDU format, VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields (such as...). Figure 7 (as shown in (c)).

[0113] Examples of HE PPDU format (IEEE 802.11ax) include, in addition to the basic PPDU format, repeated L-SIG (RL-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and packet extension (PE) fields (such as...). Figure 7 (as shown in (d)). Based on the detailed example 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-user (MU) applications, but not in the HE PPDU format for single-user (SU) applications. Additionally, the HE trigger (TB) based PPDU format does not include HE-SIG-B, and the length of the HE-STF field may vary to 8µs. The extended range (HE ER) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16µs. For example, RL-SIG can be configured to be the same as L-SIG. The receiving STA can determine whether the received PPDU is an HE PPDU or an EHT PPDU based on the presence of RL-SIG, which will be described later.

[0114] EHT PPDU format can include Figure 7 (e) EHT MU (Multi-user) and Figure 7 (f) EHT TB (trigger-based) PPDU. The EHT PPDU format is similar to the HE PPDU format in that it includes RL-SIG, followed by L-SIG, but may include U (generic)-SIG, EHT-SIG, EHT-STF and EHT-LTF following RL-SIG.

[0115] Figure 7 In (e), the EHT MU PPDU corresponds to a PPDU that carries one or more data (or PSDU) for one or more users. That is, the EHT MU PPDU can be used for both SU and MU transmissions. For example, the EHT MU PPDU can correspond to a PPDU used for one or more receiving STAs.

[0116] Compared to EHT MU PPDU, Figure 7In (f), the EHT-SIG is omitted from the EHT TB PPDU. A STA that receives a trigger (e.g., a trigger frame or trigger response schedule (TRS)) for UL MU transmission can perform UL transmission based on the EHT TB PPDU format.

[0117] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (General 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 determined 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 for demodulation and decoding 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 fields, and can be mapped based on a determined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

[0118] Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields can be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, Data, and PE fields can 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 can be referred to as free VHT modulation fields, and the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields can be referred to as VHT modulation fields.

[0119] Figure 7 The U-SIG included in the EHT PPDU format can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol used for the U-SIG (e.g., an OFDM symbol) can have a duration of 4 µs, and the U-SIG can have a total duration of 8 µs. 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.

[0120] U-SIGs can be constructed in 20MHz units. For example, if an 80MHz PPDU is constructed, the U-SIGs may be repeated. That is, an 80MHz PPDU can include the same four U-SIGs. PPDUs with bandwidths exceeding 80MHz can include different U-SIGs.

[0121] For example, A uncoded bits can be sent via U-SIG. The first symbol of U-SIG (e.g., U-SIG-1) can send the first X bits of the total A bits, and the second symbol of U-SIG (e.g., U-SIG-2) can send the remaining Y bits of the total A bits. The A bits of information (e.g., 52 uncoded bits) can include a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). For example, the tail field can be used to terminate the grid of the convolutional decoder and can be set to 0.

[0122] The bit information sent by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in... Figure 7 In the new PPDU format (e.g., UHR PPDU format) not shown in the figure, 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 may be the same, and some or all of the version-related bits may be different.

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

[0124] For example, the version-independent bits of U-SIG may include a 3-bit Physical Layer Version Identifier (PHY Version Identifier), and this information can indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted / received PPDU. The version-independent bits of U-SIG may include a 1-bit UL / DL Flag field. The first value of the 1-bit UL / DL Flag field is related to UL communication, and the second value is related to DL communication. The version-independent bits of U-SIG may include information about the length of the Transmission Opportunity (TXOP) and information about the BSS color ID.

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

[0126] The information necessary for PPDU transmission and reception can be included in the U-SIG. For example, the U-SIG may further include information about the bandwidth, information about the MCS technique applied to the non-legacy SIG (e.g., EHT-SIG or UHR-SIG), information indicating whether a DCM (dual-carrier modulation) technique (e.g., a technique that achieves a frequency diversity-like effect by repeating 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, and may also include information about whether the non-legacy SIG is generated across the entire band, etc.

[0127] Some information necessary for PPDU transmission and reception can be included in the U-SIG and / or non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.). For example, information about the type of 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 CP (cyclic prefix) length, information about the GI (guard interval) applicable to the non-legacy LTF, information about the preamble perforation applicable to the PPDU, information about RU (resource unit) allocation, etc., can be included only in the U-SIG, only in the non-legacy SIG, or indicated by a combination of information included in the U-SIG and information included in the non-legacy SIG.

[0128] A preamble can refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the bandwidth of the PPDU. For example, the size of the frequency unit (or the resolution of the preamble) can be defined as 20MHz, 40MHz, etc. For example, a preamble can be applied to a PPDU of a predetermined size or larger bandwidth.

[0129] exist Figure 7 In the examples, non-legacy SIGs such as HE-SIG-B and EHT-SIG can include control information for the receiving STA. Non-legacy SIGs can be transmitted on at least one symbol, and a symbol can have a length of 4 µs. Information regarding the number of symbols used for the EHT-SIG can be included in previous SIGs (e.g., HE-SIG-A, U-SIG, etc.).

[0130] Non-legacy SIGs such as HE-SIG-B and EHT-SIG can include public fields and user-specific fields. Public fields and user-specific fields can be encoded separately.

[0131] In some cases, the common field can be omitted. For example, in compressed mode using non-OFDMA (Orthogonal Frequency Multiple Access), the common field can be omitted, and multiple STAs can receive PPDUs (e.g., the data field of the PPDU) through the same frequency band. In uncompressed mode using OFDMA, multiple users can receive PPDUs (e.g., the data field of the PPDU) through different frequency bands.

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

[0133] The common fields may include CRC bits and tail bits, where the length of the CRC bits can be determined to be 4 bits, and the length of the tail bits can be determined to be 6 bits and set to 000000. The common fields may include RU allocation information. RU allocation information may include information about the locations of RUs assigned to multiple users (i.e., multiple receiving STAs).

[0134] An RU can include multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA technology. Additionally, RUs can be defined even when transmitting signals to a single STA. Resources can be allocated in units of RUs for non-legacy STFs, non-legacy LTFs, and data fields.

[0135] The appropriate RU size can be defined based on the PPDU bandwidth. For the applied PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.), the RUs can be defined the same or different. For example, in the case of an 80MHz PPDU, the RU placement for HEPPDU and EHT PPDU may differ. The applicable RU size, number and location, DC (direct current) subcarrier location and number, empty subcarrier location and number, guard subcarrier location and number, etc., for each PPDU bandwidth can be referred to as the tone scheme. For example, a tone scheme for high bandwidth can be defined as multiple iterations of a low bandwidth tone scheme.

[0136] RUs of various sizes can be defined as 26-tone RUs, 52-tone RUs, 106-tone RUs, 242-tone RUs, 484-tone RUs, 996-tone RUs, 2×996-tone RUs, 3×996-tone RUs, etc. An MRU (multiple RUs) is distinguished from multiple individual RUs and corresponds to a group of subcarriers composed of multiple RUs. For example, an MRU can be defined as 52+26-tone, 106+26-tone, 484+242-tone, 996+484-tone, 996+484+242-tone, 2×996+484-tone, 3×996-tone, or 3×996+484-tone. Furthermore, the multiple RUs constituting an MRU can be consecutive or non-consecutive in the frequency domain.

[0137] The specific size of the RU can be reduced or increased. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in this disclosure is not limiting and is illustrative. In addition, in this disclosure, the number of RUs can vary depending on the RU size within a predetermined bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...).

[0138] Figure 7 The names of each field in the PPDU format are exemplary, and the scope of this disclosure is not limited to the names. Furthermore, the examples in this disclosure can be applied to... Figure 7 The PPDU format illustrated in the figure, and its application in... Figure 7 The PPDU format excludes some fields and / or adds some fields to the new PPDU format.

[0139] Resource Unit

[0140] Figures 8 to 10 This is a diagram illustrating an example of a resource unit that can be used in a WLAN system to which this disclosure may be applied.

[0141] refer to Figures 8 to 10 This describes the Resource Unit (RU) defined in a wireless LAN system. An RU can include multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on an OFDMA scheme. Additionally, an RU can be defined even when transmitting a signal to a single STA. RUs can be used in the data fields of STF, LTF, PPDU, etc.

[0142] like Figures 8 to 10 As shown, RUs corresponding to different numbers of tones (i.e., subcarriers) are used to construct some fields of 20MHz, 40MHz, or 80MHz X-PPDUs (where X is HE, EHT, etc.). For example, resources can be allocated to RU cells shown for X-STF, X-LTF, and data fields.

[0143] Figure 8 This is a diagram illustrating an exemplary allocation of resource units (RUs) used on a 20MHz band.

[0144] like Figure 8 As shown at the top, 26 units (i.e., units corresponding to 26 tones) can be allocated. Six tones can be used as guard bands in the leftmost band of the 20MHz band, and five tones can be used as guard bands in the rightmost band of the 20MHz band. Additionally, seven DC tones are inserted in the center band, i.e., the DC band, and 26 units corresponding to each of the 13 tones can exist on the left and right sides of the DC band. Furthermore, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be assigned to a STA or user.

[0145] Figure 8 The RU allocation is utilized not only in multi-user (MU) scenarios but also in single-user (SU) scenarios, and in this case, a 242-unit configuration can be used, such as... Figure 8 As shown at the bottom. In this case, three DC tones can be inserted.

[0146] exist Figure 8 In the examples, various sizes of RUs, i.e., 26-RU, 52-RU, 106-RU, 242-RU, etc., are exemplified, but the specific size of these RUs can be reduced or increased. Therefore, in this disclosure, the specific size of each RU (i.e., the number of corresponding tones) is exemplary and not limiting. Furthermore, within the predetermined bandwidth of this disclosure (e.g., 20, 40, 80, 160, 320 MHz, ...), the number of RUs can vary depending on the size of the RUs. This will be described below. Figure 9 and / or Figure 10 In the example, the fact that the size and / or number of RUs can vary is consistent with... Figure 8 The examples are the same.

[0147] Figure 9 This is a diagram illustrating an exemplary allocation of resource units (RUs) used on a 40MHz band.

[0148] As in Figure 8 The examples use RUs of various sizes, just like in... Figure 9 Examples can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. Additionally, five DC tones can be inserted at the center frequency, twelve tones can be used as guard bands in the leftmost band of the 40MHz band, and eleven tones can be used as guard bands in the rightmost band of the 40MHz band.

[0149] In addition, as shown, a 484-RU can be used when used for a single user.

[0150] Figure 10 This is a diagram illustrating an exemplary allocation of resource units (RUs) used on an 80MHz band.

[0151] Just like in Figure 8 and Figure 9 The examples use RUs of various sizes, just like in... Figure 10 Examples can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. Additionally, in the case of an 80MHz PPDU, the RU allocation for the HE PPDU and EHT PPDU may differ, and... Figure 10 The example shows an instance of RU allocation for an 80MHz EHT PPDU. Figure 10 The scheme of using 12 tones as a guard band in the leftmost band of the 80MHz band and 11 tones as a guard band in the rightmost band of the 80MHz band is the same in both HE PPDU and EHT PPDU. Unlike HE PPDU, where 7 DC tones are inserted in the DC band and there is one 26-RU corresponding to each of the 13 tones on the left and right sides of the DC band, in EHT PPDU, 23 DC tones are inserted in the DC band, and there is one 26-RU on each side of the DC band. Unlike HE PPDU, where there is an empty subcarrier between 242-RUs instead of in the center band, there are five empty subcarriers in EHT PPDU. In HE PPDU, a 484-RU does not include an empty subcarrier, but in EHT PPDU, a 484-RU includes 5 empty subcarriers.

[0152] Additionally, as shown, when used for a single user, the 996-RU can be used, and in this case, five DC tones are inserted together with the HEPPDU and EHT PPDU.

[0153] It can be configured with a 160MHz EHT PPDU. Figure 10 Multiple 80MHz sub-blocks within. RU allocation for each 80MHz sub-block can be... Figure 10 The 80MHz EHT PPDU is the same. If the 80MHz sub-block of the 160MHz or 320MHz EHT PPDU is not perforated and the entire 80MHz sub-block is used as part of an RU or multiple RUs (MRUs), then the 80MHz sub-block can be used. Figure 10 996-RU.

[0154] Here, an MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs that make up an MRU can be RUs of the same size or RUs of different sizes. For example, a single MRU can 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. The multiple RUs that make up an MRU can correspond to small-sized (e.g., 26, 52, or 106) RUs or large-sized (e.g., 242, 484, or 996) RUs. That is, an MRU that includes both small-sized and large-sized RUs can be configured / defined without further configuration. Furthermore, the multiple RUs that make up an MRU can be consecutive or non-consecutive in the frequency domain.

[0155] When the 80MHz subblock includes RUs with fewer than 996 tones or when a portion of the 80MHz subblock is perforated, the 80MHz subblock can use RUs other than the 996-tone RUs.

[0156] The RU disclosed herein can be used for uplink (UL) and / or downlink (DL) communication. For example, when performing trigger-based UL-MU communication, the STA that sends the trigger (e.g., AP) can assign a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) and a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to a second STA via trigger information (e.g., trigger frame or triggered response schedule (TRS)). Subsequently, the first STA can send a first trigger-based (TB) PPDU based on the first RU, and the second STA can send a second TB PPDU based on the second RU. The first / second TB PPDUs can be sent to the AP within the same time period.

[0157] For example, when configuring a DL MU PPDU, the STA (e.g., AP) transmitting the DL MU PPDU can assign 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. In other words, within a MU PPDU, the transmitting STA (e.g., AP) can transmit X-STF (e.g., X is HE, EHT, etc.), X-LTF, or data fields to the first STA via the first RU within the MU PPDU, and transmit X-STF, X-LTF, or data fields to the second STA via the second RU. Information about the RU arrangement can be signaled using the X-SIG field (e.g., X is HE, EHT, or U) in the X-PPDU format.

[0158] Distributed resource unit

[0159] Due to varying regional regulations, power spectral density (PSD) limits may apply in the sub-7GHz (e.g., 6GHz) band. For non-AP STAs in the low-power indoor (LPI) band, the PSD limit might be -1 dBm / MHz. For example, for an existing 52-tone RU, the maximum transmit (Tx) power might be approximately 6 dBm.

[0160] Furthermore, different restrictions may be applied in the 2.4 GHz and 5 GHz bands. For example, in the EU / China / Japan / South Korea, a PSD limit of 10 dBm / MHz may be applied in the 2.4 GHz band. For existing 52-tone RUs, the maximum Tx power is likely to be around 17 dBm. If the PSD limit can be avoided in the 5 GHz band, the transmit power can be increased. For example, for existing 52-tone RUs, the maximum transmit power is 24 dBm, which is always 6 dBm lower than the maximum permissible effective isotropic radiated power (EIRP) of 30 dBm.

[0161] When the PSD limitation is overcome, the transmission power can be increased, thereby enhancing spectral efficiency or extending the range.

[0162] Considering the PSD limit defined for each STA per MHz, when the tones of a small RU are distributed over a wide bandwidth, the tones used for each STA are discontinuous, and therefore each tone may be transmitted at high power. RUs that include tones distributed in this way are called distributed RUs (DRUs), and to distinguish them, RUs that include continuous tones as defined in existing WLAN systems (e.g., systems according to IEEE 802.11ax, 11be, etc.) can be called conventional RUs (RRUs).

[0163] A STA transmitting a DRU can use higher power compared to a STA transmitting an existing RRU. For example, a 52-tone DRU spanning 80MHz has only one tone per MHz, while a 52-tone RRU has approximately 13 tones per MHz. Assuming a PSD limit of -1dBm / MHz in the 6GHz LPI band, the transmission power can be increased by approximately 11dB for a 52-tone RU when using a DRU. Increasing the transmission power in this way allows for a higher MCS and supports a longer range.

[0164] Figure 11 This is a diagram used to describe an example of a DRU to which this disclosure can be applied.

[0165] Figure 11The example illustratively illustrates that STA1 performs a transmission on DRU1, STA2 performs a transmission on DRU2, and STA3 performs a transmission on DRU3. Each STA can apply a transmission power boost by using a DRU. Higher transmission power can be applied to all tones in the DRU compared to using an RRU of the same size, and correspondingly, spectral efficiency can be greatly improved. In this way, DRUs can be usefully applied, particularly in UL-OFDMA.

[0166] In the case of the AP, DRUs can also be utilized. In some cases, the AP can perform DL-OFDMA transmission to the STA using only some of DRU1, DRU2, and DRU3, and in this case, the transmission power boost due to the use of DRUs can be applied.

[0167] To maximize power gains, tones can be distributed as widely as possible within a single DRU. For example, a DRU comprising one tone per MHz is considered an optimal example. The size of a DRU (or the number of available tones included in a DRU, i.e., the number of remaining tones after excluding unavailable tones such as zero tones, guard tones, DC tones, etc.) can be defined to be the same as the size of an RRU (or the number of available tones included in an RRU). Therefore, the impact on various techniques previously defined based on RRUs can be minimized. Examples of power gains (in dB) achievable with various DRUs distributed across different bandwidths are shown below. The examples in the table assume a 6 GHz LPI band, and power gains 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 with 8 users, the overall performance can be improved by approximately 8.13 dB when each user uses a 106-tone DRU compared to using a 106-tone RRU per user. In this way, DRUs can be used to overcome the limitations of PSD and achieve significant benefits.

[0168] [Table 1]

[0169] Trigger Frame

[0170] Figure 12 This is a diagram of an exemplary format of the trigger frame that can be applied to this disclosure.

[0171] A trigger frame can allocate resources and request the transmission of at least one TB PPDU. The trigger frame may also include additional information required by the STA in response to its transmission of the TB PPDU. The trigger frame may include public information and user information list fields in the frame body.

[0172] The common information field may include information that is commonly applied to the transmission of one or more TB PPDUs requested by the trigger frame, such as trigger type, UL length, whether there are subsequent trigger frames (e.g., more TFs), whether channel sensing (CS) is required, UL bandwidth (BW), DRU / RRU indication, etc. Figure 12 The UHR variant public information field format is shown as an example.

[0173] The 4-bit trigger type subfield can have values ​​from 0 to 15. Among them, values ​​0, 1, 2, 3, 4, 5, 6, and 7 are defined to correspond to Basic, Beamforming Report Polling (BFRP), Multi-User Block Acknowledgment Request (MU-BAR), Multi-User Request Transmission (MU-RTS), Buffer Status Report Polling (BSRP), Multicast with Retry (GCR) MU-BAR, Bandwidth Query Report Polling (BQRP), and NDP Feedback Report Polling (NFRP), and values ​​8-15 are defined as reserved.

[0174] The DRU / RRU indicator subfield indicates whether a distributed RU (DRU) or regular RU (RRU) transfer is requested in each 80MHz frequency subblock. The indication via the DRU / RRU indicator subfield can be configured on an 80MHz frequency subblock basis. For example, when the DRU / RRU indicator subfield format consists of 4 bits (B0, B1, B2, B3), B0 can be used for the lowest 80MHz frequency subblock, B1 for the next lowest 80MHz frequency subblock, B2 for the next highest 80MHz frequency subblock, and B3 for the highest 80MHz frequency subblock. When the UL BW is 20MHz, 40MHz, or 80MHz, bits B1 through B3 of the DRU / RRU indicator subfield can be reserved. When the UL BW is 160MHz, bits B2 through B3 of the DRU / RRU indicator subfield can be reserved. To request a UHR TB PPDU by sending a DRU in an 80MHz frequency subblock, the corresponding bit in the DRU / RRU indicator subfield can be configured to 0; otherwise, the corresponding bit can be configured to 1.

[0175] Within the public information, the trigger-related public information subfields can include information selectively included based on the trigger type.

[0176] Special user information fields can be included in the trigger frame. These fields do not include user-specific information, but do include extended public information not provided in the public information fields.

[0177] The user information list includes one or more user information fields. Figure 12 The UHR variant user information field format is shown as an example.

[0178] This indicates that the AID12 subfield is essentially a user information field for STAs with the corresponding AID. Additionally, when an AID12 field has a pre-determined specific value, it can be used for other purposes, including assigning Random Access (RA)-RUs or configuring it as a special user information field. A special user information field is a user information field that does not include user-specific information but includes extended public information not provided in the public information field. For example, a special user information field can be identified by the AID12 value of 2007, and the special user information field flag subfield in the public information field can indicate whether a special user information field is included.

[0179] The RU allocation subfield can indicate the size and location of the RU / MRU. Therefore, the RU allocation subfield can be interpreted in conjunction with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW extension subfield of the special user information field, and the ULBW subfield of the public information field. Furthermore, when the RU allocated according to the RU allocation in the user information field is located in an 80MHz frequency subblock where the corresponding bit in the DRU / RRU indicator subfield of the UHR variant public information field is set to 1, or in two or more 80MHz frequency subblocks where all corresponding bits in the DRU / RRU indicator subfield of the UHR variant public information field are set to 1, the allocated RU can be either an RRU or an MRU.

[0180] For example, as shown in Table 2 below, 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. Table 2 shows an example of the encoding of the PS160 subfield and RU allocation subfield of the UHR variant user information field.

[0181] [Table 2]

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

[0183] In the trigger frame RU allocation table in Table 2, the parameter N can be based on N=2. The formula X1+X0 is used for calculation. For bandwidths of 80MHz or less, the values ​​of PS160, B0, X0, and X1 can be set to 0. For bandwidths of 160MHz and 320MHz, the values ​​of PS160, B0, X0, and X1 can be set as shown in Table 2. This configuration represents the absolute frequency order for the primary and secondary 80MHz and 160MHz channels. The order from left to right represents the order from low frequency to high frequency. The primary 80MHz channel is denoted as P80, the secondary 80MHz channel is denoted as S80, and the secondary 160MHz channel is denoted as S160.

[0184] [Table 3]

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

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

[0187] Table 4

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

[0189] Table 5

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

[0191] Table 6

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

[0193] For example, the SS allocation subfield of the UHR variant user information field associated with an RRU may include an initial spatial stream subfield and a spatial stream quantity 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 spatial stream quantity subfield. In other words, the corresponding SS allocation subfield may indicate the DRU DBW and spatial stream 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 ​​from 0 to 3 can be defined for 20MHz DBW, 40MHz DBW, 80MHz DBW, and 160MHz DBW, respectively.

[0194] DRU tone scheme-based transmission and reception

[0195] As mentioned above, in order to overcome the PSD limitation and improve power gain, a DRU using distributed tone / subcarriers can be applied instead of an RRU using continuous tone / subcarriers.

[0196] This disclosure proposes various DRU tone schemes for a 40MHz bandwidth / channel (hereinafter referred to as Embodiment 1) and a method for configuring pilot tones uniformly distributed across all DRUs for various DRU tone schemes for a 40MHz bandwidth / channel (hereinafter referred to as Embodiment 2). Furthermore, this disclosure proposes a method for defining a DRU tone index when applying DRUs within each 40MHz segment of a bandwidth / channel exceeding 40MHz (hereinafter referred to as Embodiment 3).

[0197] In the embodiments described below, the DRU index (i.e., DRU n) or the nth DRU may correspond to a position in the frequency domain, or may be assigned regardless of the position in the frequency domain. In the embodiments described below, for clarity, it is described by assuming that a relatively low DRU index includes a relatively low tone / subcarrier; however, the scope of this disclosure is not limited thereto, and DRU indices may be assigned in various ways to distinguish different DRUs.

[0198] Additionally, in the following description, subcarrier indices may assume that the index of the DC subcarrier is 0 and corresponds to a position in the frequency domain, and the term subcarrier may be replaced with tone. For example, "-a" means a tone with an index of -a, and the corresponding tone may be located on the upper left based on the center of the bandwidth / channel (e.g., the low-frequency domain based on the corresponding center). Similarly, "+a" means a tone with an index of +a, and the corresponding tone may be located on the upper right based on the center of the bandwidth / channel (e.g., the high-frequency domain based on the corresponding center).

[0199] In this disclosure, “a:b:c” means the tone at the position corresponding to the tone units from the tone with index a to the tone with index c, and means that the corresponding tone can be assigned / assigned to each DRU.

[0200] Example 1

[0201] This embodiment relates to a method for defining tone plans for 26-tone DRUs, 52-tone DRUs, 106-tone DRUs, and 242-tone DRUs with respect to DRU tone plans in a bandwidth / channel of 40 MHz or greater.

[0202] In this disclosure, each DRU tone scheme within 40MHz is proposed in the context of a bandwidth / channel of 40MHz or greater, and is essentially described under the premise of defining the same number of DRUs of the same size as each existing 40MHz RRU tone scheme in a bandwidth / channel of 40MHz or greater (however, excluding 484-tone DRUs). In the following description of the method, the same number of guard tones and / or DC tones at the same locations as before can be based on the above. Figure 9 The 40MHz tone plan in the middle.

[0203] Additionally, empty tones need to be defined, and when configuring a 106-tone DRU, a portion of the corresponding empty tones can be converted to data tones, and when configuring a 242-tone DRU, the remaining empty tones can be converted to data tones. In the following text, for ease of description, the empty tones converted to data tones when configuring a 106-tone DRU are named Empty Tone Type 1, and the empty tones converted to data tones when configuring a 242-tone DRU are named Empty Tone Type 2.

[0204] In this regard, this disclosure proposes a DRU pitch scheme by considering the following four empty pitch groups ( / methods). Each empty pitch group may include pitches of empty pitch type 1 and pitches of empty pitch type 2. When using new empty pitch groups that exclude traditional empty pitch groups (e.g., based on...) Figure 9(The tone plan in the DRU) can obtain the maximum power boost gain from all DRUs.

[0205] - Traditional empty tone group

[0206] Empty tone type 1: Tone index [-191, -190, -57, -56, 56, 57, 190, 191]

[0207] Empty tone type 2: Tone index [-244, -137, -110, -3, 3, 110, 137, 244]

[0208] - The proposed empty tone group 1

[0209] Empty tone type 1: Tone index [-10, -9, -8, -7, 7, 8, 9, 10]

[0210] Empty tone type 2: Tone index [-6, -5, -4, -3, 3, 4, 5, 6]

[0211] - The proposed empty tone group 2

[0212] Empty tone type 1: Tone index [-244, -243, -242, -241, 241, 242, 243, 244]

[0213] Empty tone type 2: Tone index [-6, -5, -4, -3, 3, 4, 5, 6]

[0214] - The proposed empty tone group 3

[0215] Empty tone type 1: Tone index [-240, -239, -238, -237, 237, 238, 239, 240]

[0216] Empty tone type 2: Tone index [-244, -243, -242, -241, 241, 242, 243, 244]

[0217] In the aforementioned empty tone groups (specifically, in proposed empty tone group 1, proposed empty tone group 2, and proposed empty tone group 3), empty tone type 1 and empty tone type 2 can be used interchangeably. However, since the interference effects of adjacent channels and DC offset can be overcome more easily in a 242-tone DRU than in a 106-tone DRU, proposed empty tone type 1 and empty tone type 2 as described above can be considered. In other words, empty tone type 1 assigned to a 106-tone DRU can be configured further away from the 20MHz boundary or further away from the DC than empty tone type 2 assigned to a 242-tone DRU. Specifically, since DC offset may be a more influential factor in performance in proposed empty tone group 2, empty tone type 2 can be configured as a tone around the DC, rather than the 20MHz boundary. In other words, a tone type 2 can be assigned to the 242-tone DRU for tone configurations around the more influential DC, and a tone type 1 can be assigned to the 106-tone DRU for tone configurations around the less influential 20MH boundary.

[0218] (Example 1-1)

[0219] This embodiment relates to various methods for defining tone plans for 26-tone DRUs with bandwidths / channels of 40 MHz or greater. At least one of the following methods can be applied to DRU tone plans for bandwidths / channels of 40 MHz or greater.

[0220] The 26-tone DRU tone plan can be defined by taking into account the remaining available tones (e.g., available tones) after excluding guard tones, DC tones, and empty tones, and can be defined based on the empty tone group used as follows. Starting with the lowest available tone, each tone can be assigned to each of the 18 26-tone DRUs.

[0221] (Method 1-1)

[0222] The specific tone plan for 18 26-tone DRUs based on the proposed empty tone group 1 can be as follows.

[0223] - 26-Pitch DRU 1: Pitch Index [-244:18:-28, 11:18:227]

[0224] - 26-Pitch DRU 2: Pitch Index [-243:18:-27, 12:18:228]

[0225] - 26-Pitch DRU 3: Pitch Index [-242:18:-26, 13:18:229]

[0226] - 26-Pitch DRU 4: Pitch Index [-241:18:-25, 14:18:230]

[0227] - 26-Pitch DRU 5: Pitch Index [-240:18:-24, 15:18:231]

[0228] - 26-Pitch DRU 6: Pitch Index [-239:18:-23, 16:18:232]

[0229] - 26-Pitch DRU 7: Pitch Index [-238:18:-22, 17:18:233]

[0230] - 26-Pitch DRU 8: Pitch Index [-237:18:-21, 18:18:234]

[0231] - 26-Pitch DRU 9: Pitch Index [-236:18:-20, 19:18:235]

[0232] - 26-Pitch DRU 10: Pitch Index [-235:18:-19, 20:18:236]

[0233] - 26-Pitch DRU 11: Pitch Index [-234:18:-18, 21:18:237]

[0234] - 26-Pitch DRU 12: Pitch Index [-233:18:-17, 22:18:238]

[0235] - 26-Pitch DRU 13: Pitch Index [-232:18:-16, 23:18:239]

[0236] - 26-Pitch DRU 14: Pitch Index [-231:18:-15, 24:18:240]

[0237] - 26-Pitch DRU 15: Pitch Index [-230:18:-14, 25:18:241]

[0238] - 26-Pitch DRU 16: Pitch Index [-229:18:-13, 26:18:242]

[0239] - 26-Pitch DRU 17: Pitch Index [-228:18:-12, 27:18:243]

[0240] - 26-Pitch DRU 18: Pitch Index [-227:18:-11, 28:18:244]

[0241] (Method 1-2)

[0242] The specific tone plan for 18 26-tone DRUs based on the proposed empty tone group 2 can be as follows.

[0243] - 26-Pitch DRU 1: Pitch Index [-240:18:-24, 07:18:223]

[0244] - 26-Pitch DRU 2: Pitch Index [-239:18:-23, 08:18:224]

[0245] - 26-Pitch DRU 3: Pitch Index [-238:18:-22, 09:18:225]

[0246] - 26-Pitch DRU 4: Pitch Index [-237:18:-21, 10:18:226]

[0247] - 26-Pitch DRU 5: Pitch Index [-236:18:-20, 11:18:227]

[0248] - 26-Pitch DRU 6: Pitch Index [-235:18:-19, 12:18:228]

[0249] - 26-Pitch DRU 7: Pitch Index [-234:18:-18, 13:18:229]

[0250] - 26-Pitch DRU 8: Pitch Index [-233:18:-17, 14:18:230]

[0251] - 26-Pitch DRU 9: Pitch Index [-232:18:-16, 15:18:231]

[0252] - 26-Pitch DRU 10: Pitch Index [-231:18:-15, 16:18:232]

[0253] - 26-Pitch DRU 11: Pitch Index [-230:18:-14, 17:18:233]

[0254] - 26-Pitch DRU 12: Pitch Index [-229:18:-13, 18:18:234]

[0255] - 26-Pitch DRU 13: Pitch Index [-228:18:-12, 19:18:235]

[0256] - 26-Pitch DRU 14: Pitch Index [-227:18:-11, 20:18:236]

[0257] - 26-Pitch DRU 15: Pitch Index [-226:18:-10, 21:18:237]

[0258] - 26-Pitch DRU 16: Pitch Index [-225:18:-9, 22:18:238]

[0259] - 26-Pitch DRU 17: Pitch Index [-224:18:-8, 23:18:239]

[0260] - 26-Pitch DRU 18: Pitch Index [-223:18:-7, 24:18:240]

[0261] (Methods 1-3)

[0262] The specific tone plan for 18 26-tone DRUs based on the proposed empty tone group 3 can be as follows.

[0263] - 26-Pitch DRU 1: Pitch Index [-236:18:-20, 03:18:219]

[0264] - 26-Pitch DRU 2: Pitch Index [-235:18:-19, 04:18:220]

[0265] - 26-Pitch DRU 3: Pitch Index [-234:18:-18, 05:18:221]

[0266] - 26-Pitch DRU 4: Pitch Index [-233:18:-17, 06:18:222]

[0267] - 26-Pitch DRU 5: Pitch Index [-232:18:-16, 07:18:223]

[0268] - 26-Pitch DRU 6: Pitch Index [-231:18:-15, 08:18:224]

[0269] - 26-Pitch DRU 7: Pitch Index [-230:18:-14, 09:18:225]

[0270] - 26-Pitch DRU 8: Pitch Index [-229:18:-13, 10:18:226]

[0271] - 26-Pitch DRU 9: Pitch Index [-228:18:-12, 11:18:227]

[0272] - 26-Pitch DRU 10: Pitch Index [-227:18:-11, 12:18:228]

[0273] - 26-Pitch DRU 11: Pitch Index [-226:18:-10, 13:18:229]

[0274] - 26-Pitch DRU 12: Pitch Index [-225:18:-9, 14:18:230]

[0275] - 26-Pitch DRU 13: Pitch Index [-224:18:-8, 15:18:231]

[0276] - 26-Pitch DRU 14: Pitch Index [-223:18:-7, 16:18:232]

[0277] - 26-Pitch DRU 15: Pitch Index [-222:18:-6, 17:18:233]

[0278] - 26-Pitch DRU 16: Pitch Index [-221:18:-5, 18:18:234]

[0279] - 26-Pitch DRU 17: Pitch Index [-220:18:-4, 19:18:235]

[0280] - 26-Pitch DRU 18: Pitch Index [-219:18:-3, 20:18:236]

[0281] (Examples 1-2)

[0282] This embodiment relates to a method for defining a tone schedule for a 52-tone DRU for a bandwidth / channel of 40 MHz or greater.

[0283] The 52-tone DRU can be configured as a combination of two 26-tone DRUs (e.g., refer to Example 1-1) and can be defined as follows to maximize power boost gain by allocating as many tones as possible.

[0284] - 52-Tone DRU 1: A combination of 26-Tone DRU 1 and 26-Tone DRU 10

[0285] - 52-Tone DRU 2: A combination of 26-Tone DRU 2 and 26-Tone DRU 11

[0286] - 52-Tone DRU 3: A combination of 26-Tone DRU 3 and 26-Tone DRU 12

[0287] - 52-Pitch DRU 4: A combination of 26-Pitch DRU 4 and 26-Pitch DRU 13

[0288] - A combination of 52-tone DRU 5, 26-tone DRU 6, and 26-tone DRU 15

[0289] - A combination of 52-tone DRU 6, 26-tone DRU 7, and 26-tone DRU 16

[0290] - A combination of 52-tone DRU 7, 26-tone DRU 8, and 26-tone DRU 17

[0291] - A combination of 52-tone DRU 8, 26-tone DRU 9, and 26-tone DRU 18

[0292] (Examples 1-3)

[0293] This embodiment relates to a method for defining a tone schedule for a 106-tone DRU for a bandwidth / channel of 40 MHz or greater. A 106-tone DRU can be configured by combining two 52-tone DRUs and two of the empty tones of empty tone type 1. The 106-tone DRU tone schedule can be defined to maximize power boost gain based on the empty tone group used.

[0294] (Method 1-A)

[0295] The specific tone plan for the four 106-tone DRUs based on the proposed empty tone group 1 can be as follows.

[0296] - Combination of 106-Pitch DRU 1: 52-Pitch DRU 1, 52-Pitch DRU 5, and pitch index [-10, 7].

[0297] - 106-Pitch DRU 2: A combination of 52-Pitch DRU 2, 52-Pitch DRU 6, and pitch index [-9, 8].

[0298] - 106-Pitch DRU 3: A combination of 52-Pitch DRU 3, 52-Pitch DRU 7, and pitch index [-8, 9].

[0299] - 106-Pitch DRU 4: Combination of 52-Pitch DRU 4, 52-Pitch DRU 8, and pitch index [-7, 10]

[0300] (Method 1-B)

[0301] The specific tone plan for the four 106-tone DRUs based on the proposed empty tone group 2 can be as follows.

[0302] - 106-Pitch DRU 1: Combination of 52-Pitch DRU 1, 52-Pitch DRU 5, and pitch index [-244, 241]

[0303] - 106-Pitch DRU 2: A combination of 52-Pitch DRU 2, 52-Pitch DRU 6, and pitch index [-243, 242].

[0304] - 106-Pitch DRU 3: A combination of 52-Pitch DRU 3, 52-Pitch DRU 7, and pitch index [-242, 243].

[0305] - 106-Pitch DRU 4: Combination of 52-Pitch DRU 4, 52-Pitch DRU 8, and pitch index [-241, 244]

[0306] (Method 1-C)

[0307] The specific tone plan for the four 106-tone DRUs based on the proposed empty tone group 3 can be as follows.

[0308] - 106-Pitch DRU 1: Combination of 52-Pitch DRU 1, 52-Pitch DRU 5, and pitch index [-240, 237]

[0309] - 106-Pitch DRU 2: A combination of 52-Pitch DRU 2, 52-Pitch DRU 6, and pitch index [-239, 238].

[0310] - 106-Pitch DRU 3: A combination of 52-Pitch DRU 3, 52-Pitch DRU 7, and pitch index [-238, 239].

[0311] - 106-Pitch DRU 4: Combination of 52-Pitch DRU 4, 52-Pitch DRU 8, and pitch index [-237, 240]

[0312] (Examples 1-4)

[0313] This embodiment relates to a method for defining a tone schedule for a 242-tone DRU for a bandwidth / channel of 40 MHz or greater. The 242-tone DRU can be configured by combining two 106-tone DRUs, one 26-tone DRU (e.g., one of 26-tone DRU 5 and 26-tone DRU 14 not used in the DRU configuration), and four empty tones of empty tone type 2. The 242-tone DRU tone schedule can be defined as follows to maximize power gain based on the empty tone group used.

[0314] (Method 1-D)

[0315] The specific tone plan for the two 242-tone DRUs based on the proposed empty tone group 1 can be as follows.

[0316] - 242-Pitch DRU 1: A combination of 106-Pitch DRU 1, 106-Pitch DRU 3, 26-Pitch DRU 5 (or 26-Pitch DRU 14) and pitch indices [-6, -4, 3, 5].

[0317] - 242-Pitch DRU 2: A combination of 106-Pitch DRU 2, 106-Pitch DRU 4, 26-Pitch DRU 14 (or 26-Pitch DRU 5) and pitch indices [-5, -3, 4, 6].

[0318] (Method 1-E)

[0319] The specific tone plan for the two 242-tone DRUs based on the proposed empty tone group 2 can be as follows.

[0320] - 242-Pitch DRU 1: A combination of 106-Pitch DRU 1, 106-Pitch DRU 3, 26-Pitch DRU 5 (or 26-Pitch DRU 14) and pitch indices [-6, -4, 3, 5].

[0321] - 242-Pitch DRU 2: A combination of 106-Pitch DRU 2, 106-Pitch DRU 4, 26-Pitch DRU 14 (or 26-Pitch DRU 5) and pitch indices [-5, -3, 4, 6].

[0322] (Method 1-F)

[0323] The specific tone scheme for the two 242-tone DRUs based on the proposed empty tone group 3 can be as follows.

[0324] - 242-Pitch DRU 1: A combination of 106-Pitch DRU 1, 106-Pitch DRU 3, 26-Pitch DRU 5 (or 26-Pitch DRU 14) and pitch indices [-244, -242, 241, 243].

[0325] - 242-Pitch DRU 2: A combination of 106-Pitch DRU 2, 106-Pitch DRU 4, 26-Pitch DRU 14 (or 26-Pitch DRU 5) and pitch indices [-243, -241, 242, 244].

[0326] (Examples 1-5)

[0327] Instead of predefining the 52-tone DRU in Examples 1-2 above as a combination of two 26-tone DRUs in a fixed combination, various 52-tone DRUs can be generated by combining the tones of any combination of two 26-tone DRUs. Here, the 26-tone DRU can be defined in Example 1-1, or it can be defined in other ways.

[0328] Alternatively, instead of predefining the 106-tone DRU in Examples 1-3 as including a fixed combination of two 52-tone DRUs (or a fixed combination of four 26-tone DRUs), various 106-tone DRUs can be generated by combining any combination of two 52-tone DRUs (or any combination of four 26-tone DRUs). Here, the 26-tone DRU / 52-tone DRU can be defined in Examples 1-1 / 1-2, or it can be defined in other ways. Furthermore, two empty tone combinations additionally included in the 106-tone DRU can be defined as described in Examples 1-3.

[0329] Alternatively, instead of predefining the 242-tone DRU in Examples 1-4 as comprising a fixed combination of two 106-tone DRUs and one 26-tone DRU (or a fixed combination of four 52-tone DRUs and one 26-tone DRU, or a fixed combination of nine 26-tone DRUs), various 242-tone DRUs can be generated by combining any combination of two 106-tone DRUs and one 26-tone DRU (or any combination of four 52-tone DRUs and one 26-tone DRU, or any combination of nine 26-tone DRUs). Here, the 26-tone DRU / 52-tone DRU / 106-tone DRU can be defined in Examples 1-1 / 1-2 / 1-3, or can be defined in other ways. Furthermore, for the 242-tone DRU, empty tones can be additionally combined by selecting four tones from Empty Tone Type 1 (e.g., defining eight empty tones sequentially as empty-1 to empty-8 and assigning combinations of odd and even numbers to each 242-tone DRU) and selecting four tones from Empty Tone Type 2 (e.g., defining eight empty tones sequentially as empty-1 to empty-8 and assigning combinations of odd and even numbers to each 242-tone DRU).

[0330] When applying symbol-shifted DRUs to obtain diversity gain (e.g., when the subcarrier index included in a particular DRU index in the first symbol is different from the subcarrier index included in the same particular DRU index in the second symbol), methods for generating 52-tone DRUs, 106-tone DRUs, and / or 242-tone DRUs in this manner (e.g., methods for dynamically transmitting the tones included in the respective DRUs with signals) can be usefully applied.

[0331] When signaling the DRU index assigned to the STA using existing RU allocation information (e.g., SIG fields for DL ​​OFDMA PPDUs, such as U-SIG and / or UHR-SIG fields), a predefined mapping rule between 26-tone RRU indices and 26-tone DRU indices can be applied. For example, the mapping rule could be to map DRU index-1, which includes the lowest tone, to RRU-1, which includes the lowest tone, and to map DRUs including the next lowest tone in ascending order of RRU indices. When the RRU-to-DRU mapping rule is defined in this way, multiple 26-tone RRU indices can be indicated to the STA for allocating 52-tone DRUs, 106-tone DRUs, or 242-tone DRUs, and accordingly, the STA can determine which 26-tone DRU includes the tone included in the 52-tone, 106-tone, or 242-tone DRUs to which it is assigned.

[0332] For example, an STA can be indicated to a 2 / 4 / 9 26-tone RRU index corresponding to 2 / 4 / 9 26-tone DRUs corresponding to 52-DRU / 106-tone DRU / 242-tone DRUs via RU allocation information, and the STA ID value included in the user information of such 2 / 4 / 9 26-tone RRUs (e.g., the user field of the U-SIG / UHR-SIG field of the DL OFDMA PPDU (e.g., MU PPDU) or the UHR variant user information field of the trigger frame) can be configured to be the same as the ID of the corresponding STA. Additionally, information indicating the DRU allocation and / or indicating whether it is the last of a plurality of 26-tone RRU indices corresponding to the DRU allocated to the corresponding STA can be defined within the user information (e.g., the user field of the U-SIG / UHR-SIG field of the DL OFDMA PPDU (e.g., MU PPDU) or the UHR variant user information field of the trigger frame).

[0333] (Examples 1-6)

[0334] As in Embodiments 1-2 above, the predefined 52-tone DRU includes the tones of two 26-tone DRUs in a fixed combination; as in Embodiments 1-3 above, the predefined 106-tone DRU includes the tones of two 52-tone DRUs (or four 26-tone DRUs in a fixed combination) in a fixed combination; and as in Embodiments 1-4 above, the predefined 242-tone DRU includes the tones of two 106-tone DRUs and one additional 26-tone DRU (or four 52-tone DRUs and one additional 26-tone DRU, or nine 26-tone DRUs in a fixed combination), but by summarizing the DRU index and mapping it to each RRU index, it corresponds to a specific 52-tone DRU / 106-tone DRU / 242-tone DRU. It can also be flexibly configured as a 26-tone DRU / 52-tone DRU / 242-tone DRU.

[0335] For example, 26-tone DRU-a / b / c / d / e / f / g / h / i / j / k / l / m / n / o / p / q / r can be defined to correspond in any way to 26-tone DRU-1 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 10 / 11 / 12 / 13 / 14 / 15 / 16 / 17 / 18 (e.g., indices a to r correspond one-to-one with indices 1 to 18, but the numerical indices corresponding to each alphabetical index are determined in ascending order or in any order). Here, the example of Embodiment 2-1 can be applied to the position of the tones included in the 26-tone DRU, or other methods can be applied. Based on this, 52-tone DRU-a / b / c / d / e / f / g / h, 106-tone DRU-a / b / c / d, and 242-tone DRU-a / b can be defined to correspond to combinations of DRU indices of smaller size as shown in the examples below.

[0336] - 52-tone DRU-a: 26-tone DRU-a and 26-tone DRU-j

[0337] - 52-tone DRU-b: 26-tone DRU-b and 26-tone DRU-k

[0338] - 52-tone DRU-c: 26-tone DRU-c and 26-tone DRU-l

[0339] - 52-pitch DRU-d = 26-pitch DRU-d and 26-pitch DRU-m

[0340] - 52-tone DRU-e: 26-tone DRU-f and 26-tone DRU-o

[0341] - 52-tone DRU-f: 26-tone DRU-g and 26-tone DRU-p

[0342] - 52-tone DRU-g: 26-tone DRU-h and 26-tone DRU-q

[0343] - 52-tone DRU-h = 26-tone DRU-i and 26-tone DRU-r

[0344] - 106-Pitch DRU-a: 52-Pitch DRU-a, 52-Pitch DRU-e, and two of the pitches in Empty Pitch Type 1.

[0345] - 106-Pitch DRU-b: 52-Pitch DRU-b, 52-Pitch DRU-f, and two of the pitches in Empty Pitch Type 1.

[0346] - 106-Pitch DRU-c: 52-Pitch DRU-c, 52-Pitch DRU-g, and two of the pitches in Empty Pitch Type 1.

[0347] - 106-Pitch DRU-d: 52-Pitch DRU-d, 52-Pitch DRU-h, and two of the pitches in Empty Pitch Type 1.

[0348] - 242-Pitch DRU-a: 106-Pitch DRU-a, 106-Pitch DRU-c, 26-Pitch DRU-e, and four of the pitches in Empty Pitch Type 2.

[0349] - 242-Pitch DRU-b: 106-Pitch DRU-b, 106-Pitch DRU-d, 26-Pitch DRU-n, and four of the pitches in Empty Pitch Type 2.

[0350] In the above generalized / flexible method, two of the tones of empty tone type 1 used for combination can be defined as described in Examples 1-3, and four of the tones of empty tone type 2 can be defined as described in Examples 1-4.

[0351] Alternatively, gaps can be used between multiple smaller DRU indices corresponding to a larger DRU index. The value of this gap can be explicitly signaled to the STA, or implicitly signaled based on other information (e.g., bandwidth information, BSS color information, etc.) without separate signaling. For example, 52-tone DRUs and 106-tone DRUs can include subcarriers of smaller DRUs.

[0352] - 52-Pitch DRU-a: 26-Pitch DRU-a and 26-Pitch DRU-(a+gap)

[0353] - 52-Pitch DRU-b: 26-Pitch DRU-b and 26-Pitch DRU-(b+gap)

[0354] - 52-Pitch DRU-c: 26-Pitch DRU-c and 26-Pitch DRU-(c + gap)

[0355] - 52-pitch DRU-d = 26-pitch DRU-d and 26-pitch DRU-(d + gap)

[0356] - 52-tone DRU-e: 26-tone DRU-f and 26-tone DRU-(f+gap)

[0357] - 52-Pitch DRU-f: 26-Pitch DRU-g and 26-Pitch DRU-(g+gap)

[0358] - 52-Pitch DRU-g: 26-Pitch DRU-h and 26-Pitch DRU-(h+gap)

[0359] - 52-Pitch DRU-h = 26-Pitch DRU-i and 26-Pitch DRU-(i + gap)

[0360] - 106-Pitch DRU-a: 52-Pitch DRU-a, 52-Pitch DRU-(a+gap), and two of the pitches in Empty Pitch Type 1.

[0361] - 106-Pitch DRU-b: 52-Pitch DRU-b, 52-Pitch DRU-(b+gap), and two of the pitches in Empty Pitch Type 1.

[0362] - 106-Pitch DRU-c: 52-Pitch DRU-c, 52-Pitch DRU-(c+gap), and two of the pitches in Empty Pitch Type 1.

[0363] - 106-Pitch DRU-d: 52-Pitch DRU-d, 52-Pitch DRU-(d+gap), and two of the pitches in Empty Pitch Type 1.

[0364] - 242-Pitch DRU-a: 106-Pitch DRU-a, 106-Pitch DRU-(a+gap), 26-Pitch DRU-e, and four of the pitches in Empty Pitch Type 2.

[0365] - 242-Pitch DRU-b: 106-Pitch DRU-b, 106-Pitch DRU-(b+gap), 26-Pitch DRU-n, and four of the pitches in Empty Pitch Type 2.

[0366] Here, two of the tones of empty tone type 1 for 106-tone DRU can be defined as described in Examples 1-3, and four of the tones of empty tone type 2 for 242-tone DRU can be defined as described in Examples 1-4.

[0367] In the example above, the order of the DRU's alphabetical index and its position in the frequency domain can be irrelevant. Furthermore, even if DRUs of different sizes have the same alphabetical index, it does not mean that the order within the index of DRUs of the same size is the same.

[0368] In the example above, the gap value can have the same or different values ​​for each DRU size. For example, the gap value can have an independent value for each DRU size or it can have an associated value.

[0369] Example 2

[0370] This embodiment relates to a method for defining pilot tones for various DRU tone plans for a 40MHz bandwidth / channel in Embodiment 1 above.

[0371] Specifically, this embodiment proposes a method for configuring / defining pilot tones that are uniformly distributed (e.g., fully distributed) across all DRUs based on the corresponding DRU tone plan.

[0372] In this regard, the pilot tones of all DRUs can be defined based on the pilot tones of the 26-tone DRUs. In this case, a method is proposed to define the pilot tones of the 26-tone DRUs by applying a shift to the tones at specific locations, so as to configure pilot tones that are sufficiently distributed not only within each DRU but also between DRUs.

[0373] In other words, in a 26-tone DRU, the pilot tone can be defined by applying a shift value based on a specific location (e.g., the tone position defined as the pilot tone within an existing (IEEE 802.11ax / be) 26-tone RRU). For example, a specific location could correspond to the tone at positions [6th, 20th], [7th, 21st], or [7th, 20th] in each 26-tone DRU.

[0374] Additionally, for ease of description, it is assumed that one of the four pilot tone shift values ​​is applied to each 26-tone DRU, and the corresponding four pilot tone shift values ​​are referred to as p1, p2, p3, and p4. When the specific position is [7th, 20th], each pilot tone shift value can be greater than or equal to -6 or less than or equal to +6. Furthermore, when the specific position is [6th, 20th], each pilot tone shift value can be greater than or equal to -5 or less than or equal to +6. Additionally, when the specific position is [7th, 21st], each pilot tone shift value can be greater than or equal to -6 or less than or equal to +5. Furthermore, the four pilot tone shift values ​​can be configured to satisfy additional constraints (e.g., p1). <p2<p3<p4)。

[0375] For example, pilot tone shift values ​​can be applied to each 26-tone DRU as follows. For a corresponding example, to take into account the generalized combinations, the above-described alphabetical index (e.g., refer to Examples 2-6) can be used instead of the numeric index in each DRU index. As a specific example, an alphabetical index in the same order as the numeric index can be used (when the numeric index is 1, 2, 3…, the alphabetical index is a, b, c…).

[0376] - p1: 26-Pitch DRU 1, 26-Pitch DRU 2, 26-Pitch DRU 6, 26-Pitch DRU 7

[0377] - p2: 26-Pitch DRU 3, 26-Pitch DRU 4, 26-Pitch DRU 8, 26-Pitch DRU 9

[0378] - p3: 26-Pitch DRU 10, 26-Pitch DRU 11, 26-Pitch DRU 15, 26-Pitch DRU 16

[0379] - p4: 26-Pitch DRU 12, 26-Pitch DRU 13, 26-Pitch DRU 17, 26-Pitch DRU 18

[0380] Arbitrary pilot tone shift values ​​can be applied to 26-tone DRU 5 and 26-tone DRU 14, but they can be defined such that the tone at the aforementioned specific position is used as the pilot tone.

[0381] In each of the pilot tone shift values ​​described above, 26-tone DRUs positioned in the same order as p1 and p3 can exchange pilot tone shift values ​​with each other. For example, 26-tone DRU 1 and 26-tone DRU 10 can exchange pilot tone shift values ​​with each other, and therefore p3 can be used in 26-tone DRU 1 and p1 can be used in 26-tone DRU 10. For another example, 26-tone DRU 2 and 26-tone DRU 11 can exchange pilot tone shift values ​​with each other, and therefore p3 can be used in 26-tone DRU 2 and p1 can be used in 26-tone DRU 11. Similarly, 26-tone DRUs positioned in the same order in p2 and p4 can exchange pilot tone shift values ​​with each other.

[0382] In each pilot tone shift value, odd-numbered 26-tone DRUs (e.g., 26-tone DRU 1 and 26-tone DRU 6 for p1, and 26-tone DRU 3 and 26-tone DRU 8 for p2) can be used to configure 242-tone DRU 1, and even-numbered 26-tone DRUs (e.g., 26-tone DRU 2 and 26-tone DRU 7 for p1, and 26-tone DRU 4 and 26-tone DRU 9 for p2) can be used to configure 242-tone DRU 2. In other words, each 242-tone DRU can consist of two 26-tone DRUs with the same pilot tone shift value. In this configuration, during the setup of the 106-tone DRU, the pilot tone corresponding to one of the two identical pilot tone shift values ​​is converted to a data tone, and ultimately, the pilot tone in each 242-tone DRU uses only the pilot tone of one 26-tone DRU for each pilot tone shift value. In other words, the pilot tones within the 242-tone DRU and other DRUs can have sufficient spacing.

[0383] For the following method: some pilot tones of the small DRU are converted into data tones, and other pilot tones are used as pilot tones in the 106-tone DRU. Among the odd-indexed 106-tone DRUs, the pilot tones of the lower-indexed DRU among the DRUs of the next smaller size configured therein can be used as the pilot tones for the 106-tone DRU. In addition, in the even-indexed 106-tone DRU, the pilot tones of the higher-indexed DRU among the DRUs of the next smaller size configured therein can be used as the pilot tones for the 106-tone DRU. For the corresponding pilot tones, under the condition of p1<p2<p3<p4, compared with the pilot tones proposed below, since the pilot tones located at sufficiently distributed positions can be guaranteed not only within the DRU but also between DRUs, it may be effective / preferable in terms of performance.

[0384] Alternatively, in the odd-indexed 106-tone DRU, the pilot tones of the higher-indexed DRU among the DRUs of the next smaller size configured therein can be used as the pilot tones for the 106-tone DRU. In addition, in the even-indexed 106-tone DRU, the pilot tones of the lower-indexed DRU among the DRUs of the next smaller size configured therein can be used as the pilot tones for the 106-tone DRU.

[0385] Alternatively, among the odd-indexed 106-tone DRUs and the even-indexed 106-tone DRUs, among the DRUs of their own next smaller size configured, the pilot tones of the lower-indexed DRU can be used as the pilot tones for the 106-tone DRU in negative subcarriers. In this regard, the pilot tones of the higher-indexed DRU can be used as the pilot tones for the 106-tone DRU in positive subcarriers.

[0386] Alternatively, among the odd-indexed 106-tone DRUs and the even-indexed 106-tone DRUs, among the DRUs of their own next smaller size configured, the pilot tones of the higher-indexed DRU can be used as the pilot tones for the 106-tone DRU in negative subcarriers. In this regard, the pilot tones of the lower-indexed DRU can be used as the pilot tones for the 106-tone DRU in positive subcarriers.

[0387] Alternatively, among the odd-indexed 106-tone DRUs and the even-indexed 106-tone DRUs, among the DRUs of their own next smaller size configured, the pilot tones may be alternately configured in the order of lower index and higher index according to each pilot shift order.

[0388] Alternatively, in both odd-indexed and even-indexed 106-tone DRUs, in DRUs configured to their own smaller size, pilot tones can be configured alternately in the order of higher and lower indices according to each pilot shift order.

[0389] Regarding the above method, when the pilot tone shift values ​​differ only in sign, and are symmetrically configured with the tones at positions [7th, 20th] in a 26-tone DRU arranged from lowest to highest value, a pilot tone index that is DC symmetrical (e.g., differing only in sign) can be formed when each pilot tone is mapped to a tone index across the entire bandwidth. For example, the values ​​of p1 to p4 can be considered as -5, -2, +2, +5, or -4, -2, +2, +4, or -6, -3, +3, +6. Therefore, symmetrically configuring the pilot tone shift values ​​may be effective / preferred in terms of implementation.

[0390] Hereinafter, considering the various pilot tone shift values ​​described above, specific examples of tone planning and pilot tones will be described based on the proposed empty tone group 1, proposed empty tone group 2 and proposed empty tone group 3 described in Example 1.

[0391] In the following examples, DRU tone plans for 26-tone DRUs, 52-tone DRUs, 106-tone DRUs, and 242-tone DRUs can be configured based on the method described in Example 1 above.

[0392] In the corresponding example, for the pilot tone shift values ​​[p1, p2, p3, p4], it is assumed that p1 is applied to 26-tone DRU 1, 26-tone DRU 2, 26-tone DRU 6, and 26-tone DRU 7; p2 is applied to 26-tone DRU 3, 26-tone DRU 4, 26-tone DRU 8, and 26-tone DRU 9; p3 is applied to 26-tone DRU 10, 26-tone DRU 11, 26-tone DRU 15, and 26-tone DRU 16; and p4 is applied to 26-tone DRU 12, 26-tone DRU 13, 26-tone DRU 17, and 26-tone DRU 18. Furthermore, the corresponding example is based on a DRU tone scheme that takes into account existing DC tones and guard tones. Additionally, in the corresponding example, the tone index marked with a box refers to the pilot tone used for the corresponding DRU.

[0393] (Example 1: Based on the proposed empty tone group 1)

[0394] Figure 13 Examples of DRU tone schemes and pilot tones according to embodiments of the present disclosure are shown.

[0395] Figure 13 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-5, -2, 2, 5] and is based on the proposed empty tone group 1.

[0396] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{226, 220, 170, 164, 91, 85, 35, 29}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-10, -9, -8, -7, 7, 8, 9, 10} can be added to each DRU. For example, each of {-10, 7}, {-9, 8}, {-8, 9}, and {-7, 10} can be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, it may be effective / preferred to assign {-10, 7} to 106-tone DRU 1, {-9, 8} to 106-tone DRU 2, {-8, 9} to 106-tone DRU 3, and {-7, 10} to 106-tone DRU 4.

[0397] Additionally, regarding the 242-tone DRU, excluding +-{123, 132} from each 242-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{123, 132} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{226, 220, 170, 164, 91, 85, 35, 29}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0398] (Example 2: Based on the proposed empty tone group 1)

[0399] Figure 14 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0400] Figure 14 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-4, -2, 2, 4] and is based on the proposed empty tone group 1.

[0401] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined by using tone indices +-{208, 202, 170, 164, 91, 85, 53, 47}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-10, -9, -8, -7, 7, 8, 9, 10} can be added to each DRU. For example, each of {-10, 7}, {-9, 8}, {-8, 9}, and {-7, 10} can be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, it may be effective / preferred to assign {-10, 7} to 106-tone DRU 1, {-9, 8} to 106-tone DRU 2, {-8, 9} to 106-tone DRU 3, and {-7, 10} to 106-tone DRU 4.

[0402] Additionally, regarding the 242-tone DRU, excluding +-{123, 132} from each 242-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{123, 132} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{208, 202, 170, 164, 91, 85, 53, 47}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0403] (Example 3: Based on the proposed empty tone group 1)

[0404] Figure 15 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0405] Figure 15 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-6, -3, 3, 6] and is based on the proposed empty tone group 1.

[0406] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{244, 238, 188,182, 73, 67, 17, 11}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-10, -9, -8, -7, 7, 8, 9, 10} can be added to each DRU. For example, each of {-10, 7}, {-9, 8}, {-8, 9}, and {-7, 10} can be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, it may be effective / preferred to assign {-10, 7} to 106-tone DRU 1, {-9, 8} to 106-tone DRU 2, {-8, 9} to 106-tone DRU 3, and {-7, 10} to 106-tone DRU 4.

[0407] Additionally, regarding the 242-tone DRU, excluding +-{123, 132} from each 242-tone DRU, within the same box (e.g., the box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{123, 132} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{244, 238, 188, 182, 73, 67, 17, 11}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0408] (Example 4: Based on the proposed empty tone group 2)

[0409] Figure 16 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0410] Figure 16 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-5, -2, 2, 5] and is based on the proposed empty tone group 2.

[0411] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{222, 216, 166, 160, 87, 81, 31, 25}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, 241}, {-243, 242}, {-242, 243}, and {-241, 244} could be assigned to a different 106-tone DRU. In this case, from a power boost gain perspective, assigning {-244, 241} to 106-tone DRU 1, {-243, 242} to 106-tone DRU 2, {-242, 243} to 106-tone DRU 3, and {-241, 244} to 106-tone DRU 4 might be effective / preferred.

[0412] Additionally, regarding the 242-tone DRU, excluding +-{119, 128} from each 242-tone DRU, within the same box (e.g., the box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{119, 128} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{222, 216, 166, 160, 87, 81, 31, 25}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0413] (Example 5: Based on the proposed empty tone group 2)

[0414] Figure 17 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0415] Figure 17 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-4, -2, 2, 4] and is based on the proposed empty tone group 2.

[0416] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{204, 198, 166, 160, 87, 81, 49, 43}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, 241}, {-243, 242}, {-242, 243}, and {-241, 244} could be assigned to a different 106-tone DRU. In this case, from a power boost gain perspective, assigning {-244, 241} to 106-tone DRU 1, {-243, 242} to 106-tone DRU 2, {-242, 243} to 106-tone DRU 3, and {-241, 244} to 106-tone DRU 4 might be effective / preferred.

[0417] Additionally, regarding the 242-tone DRU, excluding +-{119, 128} from each 242-tone DRU, within the same box (e.g., the box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{119, 128} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{204, 198, 166, 160, 87, 81, 49, 43}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0418] (Example 6: Based on the proposed empty tone group 2)

[0419] Figure 18 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0420] Figure 18 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-6, -3, 3, 6] and is based on the proposed empty tone group 2.

[0421] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{240, 234, 184, 178, 69, 63, 13, 7}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, 241}, {-243, 242}, {-242, 243}, and {-241, 244} could be assigned to a different 106-tone DRU. In this case, from a power boost gain perspective, assigning {-244, 241} to 106-tone DRU 1, {-243, 242} to 106-tone DRU 2, {-242, 243} to 106-tone DRU 3, and {-241, 244} to 106-tone DRU 4 might be effective / preferred.

[0422] Additionally, regarding the 242-tone DRU, excluding +-{119, 128} from each 242-tone DRU, within the same box (e.g., the box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{119, 128} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{240, 234, 184, 178, 69, 63, 13, 7}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Additionally, every four tones from the empty tones {-6, -5, -4, -3, 3, 4, 5, 6} can be added to each DRU. For example, each of {-6, -4, 3, 5} and {-5, -3, 4, 6} can be assigned to a different 242-tone DRU. In this case, from the perspective of power boost gain, assigning {-6, -4, 3, 5} to 242-tone DRU 1 and {-5, -3, 4, 6} to 242-tone DRU 2 may be effective / preferred.

[0423] (Example 7: Based on the proposed empty tone group 3)

[0424] Figure 19 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0425] Figure 19 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-5, -2, 2, 5] and is based on the proposed empty tone group 3.

[0426] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{218, 212, 162, 156, 83, 77, 27, 21}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-240, -239, -238, -237, 237, 238, 239, 240} can be added to each DRU. For example, {-240, 237}, {-239, 238}, {-238, 239}, and {-237, 240} can each be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, assigning {-240, 237} to 106-tone DRU 1, {-239, 238} to 106-tone DRU 2, {-238, 239} to 106-tone DRU 3, and {-237, 240} to 106-tone DRU 4 might be effective / preferred.

[0427] Additionally, regarding the 242-tone DRU, excluding +-{115, 124} from each 242-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{115, 124} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{218, 212, 162, 156, 83, 77, 27, 21}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute that 242-tone DRU. Alternatively, every four tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, -242, 241, 243} and {-243, -241, 242, 244} can be assigned to a different 242-tone DRU. In this case, from a power boost gain perspective, assigning {-244, -242, 241, 243} to 242-tone DRU 1 and {-243, -241, 242, 244} to 242-tone DRU 2 might be effective / preferred.

[0428] (Example 8: Based on the proposed empty tone group 3)

[0429] Figure 20 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0430] Figure 20 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-4, -2, 2, 4] and is based on the proposed empty tone group 3.

[0431] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{200, 194, 162, 156, 83, 77, 45, 39}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-240, -239, -238, -237, 237, 238, 239, 240} can be added to each DRU. For example, {-240, 237}, {-239, 238}, {-238, 239}, and {-237, 240} can each be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, assigning {-240, 237} to 106-tone DRU 1, {-239, 238} to 106-tone DRU 2, {-238, 239} to 106-tone DRU 3, and {-237, 240} to 106-tone DRU 4 might be effective / preferred.

[0432] Additionally, regarding the 242-tone DRU, excluding +-{115, 124} from each 242-tone DRU, a tone can be converted to a data tone within the same box (e.g., a box including two consecutive tone indices). In this case, +-{115, 124} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{200, 194, 162, 156, 83, 77, 45, 39}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute it. Alternatively, every four tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, -242, 241, 243} and {-243, -241, 242, 244} can be assigned to a different 242-tone DRU. In this case, from a power boost gain perspective, assigning {-244, -242, 241, 243} to 242-tone DRU 1 and {-243, -241, 242, 244} to 242-tone DRU 2 might be effective / preferred.

[0433] (Example 9: Based on the proposed empty tone group 3)

[0434] Figure 21 Another example of a DRU tone scheme and pilot tone according to an embodiment of the present disclosure is shown.

[0435] Figure 21 The example shown involves pilot tone shift values ​​[p1, p2, p3, p4] of [-6, -3, 3, 6] and is based on the proposed empty tone group 3.

[0436] Specifically, regarding the 106-tone DRU, within the same box (e.g., a box containing two consecutive tone indices), one can be used as a pilot tone, and the other can be used as / converted to a data tone. In this case, the pilot tone to be used can be selected to establish mirror symmetry. For example, the pilot tone of the 106-tone DRU can be defined using tone indices +-{236, 230, 180, 174, 65, 59, 9, 3}. Additionally, regarding the 106-tone DRU, every two tones from the empty tones {-240, -239, -238, -237, 237, 238, 239, 240} can be added to each DRU. For example, {-240, 237}, {-239, 238}, {-238, 239}, and {-237, 240} can each be assigned to a different 106-tone DRU. In this case, from the perspective of power boost gain, assigning {-240, 237} to 106-tone DRU 1, {-239, 238} to 106-tone DRU 2, {-238, 239} to 106-tone DRU 3, and {-237, 240} to 106-tone DRU 4 might be effective / preferred.

[0437] Additionally, regarding the 242-tone DRU, excluding +-{115, 124} from each 242-tone DRU, within the same box (e.g., a box including two consecutive tone indices), one can be converted to a data tone in a 106-tone DRU configuration. In this case, +-{115, 124} can always be converted to a data tone. For example, the pilot tone of the 242-tone DRU can be defined using tone indices +-{236, 230, 180, 174, 65, 59, 9, 3}. Furthermore, regarding the 242-tone DRU, empty tones can be added from the 106-tone DRUs that constitute that 242-tone DRU. Alternatively, every four tones from the empty tones {-244, -243, -242, -241, 241, 242, 243, 244} can be added to each DRU. For example, each of {-244, -242, 241, 243} and {-243, -241, 242, 244} can be assigned to a different 242-tone DRU. In this case, from a power boost gain perspective, assigning {-244, -242, 241, 243} to 242-tone DRU 1 and {-243, -241, 242, 244} to 242-tone DRU 2 might be effective / preferred.

[0438] Regarding the methods and examples described above in this disclosure, the pilot coefficients and symbol-by-symbol shifting methods can be applied to each DRU by reusing methods defined in an existing RRU of the same size.

[0439] Example 3

[0440] This embodiment relates to the tone index of each DRU when a DRU is applied within each 40MHz of a bandwidth exceeding 40MHz (e.g., 80MHz or greater).

[0441] In the following example, the set of tone indices included in each of one or more DRUs for an x ​​MHz channel in a y MHz bandwidth can be represented as S_x_y. For example, it can be assumed that S_40_40 corresponds to the tone indices included in various sizes of DRUs for a 40 MHz channel in a 40 MHz bandwidth in the examples described in Embodiments 1 and 2 above.

[0442] First, the tone index (S_40_80) at a specific 40MHz point in an 80MHz bandwidth can be defined as follows.

[0443] The first 40MHz tone index (1 S_40_80): The DRU tone index (S_40_40) defined at the aforementioned 40MHz -256

[0444] The second 40MHz tone index (2 S_40_80): The DRU tone index (S_40_40) defined at the aforementioned 40MHz + 256

[0445] For example, it can also be expressed as follows.

[0446] The first S_40_80 = S_40_40 - 256; and

[0447] The second S_40_80 = S_40_40 + 256.

[0448] Next, the tone index (S_40_160) at a specific 40MHz of the 160MHz bandwidth can be defined as follows.

[0449] Tone indices for each 40MHz within the first 80MHz (1st S_40_160 and 2nd S_40_160): DRU tone indices for each 40MHz defined at the aforementioned 80MHz (1st S_40_80 and 2nd S_40_80) -512

[0450] The tone index for each 40MHz within the second 80MHz (3rd S_40_160 and 4th S_40_160): the DRU tone index for each 40MHz defined at the aforementioned 80MHz (1st S_40_80 and 2nd S_40_80) + 512

[0451] For example, it can also be expressed as follows.

[0452] The first S_40_160 = the first S_40_80-512; The second S_40_160 = the second S_40_80-512; The 3rd S_40_160 = the 1st S_40_80 + 512; and The 4th S_40_160 = the 2nd S_40_80 + 512.

[0453] Next, the tone index (S_40_240) at a specific 40MHz of the 240MHz bandwidth can be defined as follows.

[0454] Tone indices for each 40MHz within the first 80MHz (1st S_40_240 and 2nd S_40_240): DRU tone indices for each 40MHz defined at the aforementioned 80MHz (1st S_40_80 and 2nd S_40_80) - 1024

[0455] The tone index for each 40MHz within the second 80MHz (3rd S_40_240 and 4th S_40_240): The DRU tone index for each 40MHz defined at the aforementioned 80MHz (1st S_40_80 and 2nd S_40_80).

[0456] The tone index for each 40MHz within the third 80MHz (5th S_40_240 and 6th S_40_240): the DRU tone index for each 40MHz defined at the aforementioned 80MHz (1st S_40_80 and 2nd S_40_80) + 1024

[0457] For example, it can also be expressed as follows.

[0458] The first S_40_240 = the first S_40_80 - ​​1024; The second S_40_240 = the second S_40_80 - ​​1024; The 3rd S_40_240 = the 1st S_40_80; The 4th S_40_240 = the 2nd S_40_80; The 5th S_40_240 = the 1st S_40_80 + 1024; and The 6th S_40_240 = the 2nd S_40_80 + 1024.

[0459] Next, the tone index (S_40_320) at a specific 40MHz of the 320MHz bandwidth can be defined as follows.

[0460] Tone index within each 40MHz range of the first 160MHz (1st S_40_320 to 4th S_40_320): DRU tone index for each 40MHz range defined at the aforementioned 160MHz (1st S_40_160 to 4th S_40_160) - 1024

[0461] The tone index for each 40MHz within the second 160MHz (5th S_40_320 to 8th S_40_320): The DRU tone index for each 40MHz defined at the aforementioned 160MHz (1st S_40_160 to 4th S_40_160) + 1024

[0462] For example, it can also be expressed as follows.

[0463] The first S_40_320 = the first S_40_160-1024; The second S_40_320 = the second S_40_160-1024; The 3rd S_40_320 = The 3rd S_40_160-1024; The 4th S_40_320 = The 4th S_40_160-1024; The 5th S_40_320 = the 1st S_40_160 + 1024; The 6th S_40_320 = the 2nd S_40_160 + 1024; The 7th S_40_320 = the 3rd S_40_160 + 1024; and The 8th S_40_320 = the 4th S_40_160 + 1024.

[0464] Next, the tone index (S_40_480) at a specific 40MHz in the 480MHz bandwidth can be defined as follows.

[0465] Tone indices for each 40MHz within the first 160MHz (from 1st S_40_480 to 4th S_40_480): DRU tone indices for each 40MHz defined at the aforementioned 160MHz (from 1st S_40_160 to 4th S_40_160) - 2048

[0466] Tone indices for each 40MHz within the second 160MHz (5th S_40_480 to 8th S_40_480): DRU tone indices for each 40MHz defined at the aforementioned 160MHz (1st S_40_160 to 4th S_40_160).

[0467] Tone index within each 40MHz of the third 160MHz (9th S_40_480 to 12th S_40_480): DRU tone index for each 40MHz defined at the aforementioned 160MHz (1st S_40_160 to 4th S_40_160) + 2048

[0468] For example, it can also be expressed as follows.

[0469] The first S_40_480 = the first S_40_160 - 2048; The second S_40_480 = the second S_40_160 - 2048; The 3rd S_40_480 = The 3rd S_40_160 - 2048; The 4th S_40_480 = The 4th S_40_160 - 2048; The 5th S_40_480 = the 1st S_40_160; The 6th S_40_480 = the 2nd S_40_160; The 7th S_40_480 = the 3rd S_40_160; The 8th S_40_480 = the 4th S_40_160; The 9th S_40_480 = the 1st S_40_160 + 2048; The 10th S_40_480 = the 2nd S_40_160 + 2048; The 11th S_40_480 = the 3rd S_40_160 + 2048; and The 12th S_40_480 = the 4th S_40_160 + 2048.

[0470] Next, the tone index (S_40_640) at a specific 40MHz of the 640MHz bandwidth can be defined as follows.

[0471] Tone indexes for each 40MHz within the first 320MHz (1st S_40_640 to 8th S_40_640): DRU tone indexes for each 40MHz defined at the aforementioned 320MHz (1st S_40_320 to 8th S_40_320) - 2048

[0472] The tone index for each 40MHz within the second 320MHz (9th S_40_640 to 16th S_40_640): The DRU tone index for each 40MHz defined at the aforementioned 320MHz (1st S_40_320 to 8th S_40_320) + 2048

[0473] For example, it can also be expressed as follows.

[0474] The first S_40_640 = the first S_40_320-2048; The second S_40_640 = the second S_40_320-2048; The 3rd S_40_640 = The 3rd S_40_320 - 2048; The 4th S_40_640 = The 4th S_40_320 - 2048; The 5th S_40_640 = The 5th S_40_320-2048; The 6th S_40_640 = The 6th S_40_320 - 2048; The 7th S_40_640 = The 7th S_40_320-2048; The 8th S_40_640 = The 8th S_40_320-2048; The 9th S_40_640 = the 1st S_40_320 + 2048; The 10th S_40_640 = the 2nd S_40_320 + 2048; The 11th S_40_640 = the 3rd S_40_320 + 2048; The 12th S_40_640 = The 4th S_40_320 + 2048; The 13th S_40_640 = the 5th S_40_320 + 2048; The 14th S_40_640 = the 6th S_40_320 + 2048; The 15th S_40_640 = the 7th S_40_320 + 2048; and The 16th S_40_640 = the 8th S_40_320 + 2048.

[0475] When using the DRU tone scheme proposed in this disclosure, DRUs of different sizes can be allocated and used for different STAs within a 20MHz bandwidth / channel or a 40MHz bandwidth / channel, in a manner similar to that used with existing RRUs. Additionally, the RU allocation field in DL OFDMA transmission and the RU allocation subfield in the trigger frame for TB PPDU transmission can be utilized in the same manner as in RRU transmission. In this regard, when sending / allocating DRUs, it is necessary to define mapping rules from the RU allocation field and the RU allocation subfield to the DRUs.

[0476] In the following text, through Figure 22 and Figure 23 Describe STA operations based on the various examples of this disclosure described above. Figure 22 and Figure 23 The examples can correspond to some of the examples in the various publicly available examples.

[0477] For example, in Figure 22 and Figure 23 In this context, the first STA can correspond to a non-AP STA that receives the trigger frame of the request TB PPDU, and the second STA can correspond to an AP that sends the corresponding trigger frame.

[0478] Figure 22 This is a diagram illustrating an operational example of the first STA in the PPDU transmission and reception method based on the DRU tone scheme according to this disclosure.

[0479] Reference Figure 22 The first STA can receive a trigger frame (S2210) from the second STA, which includes information on resource allocation for one or more Distributed Resource Units (DRUs).

[0480] For example, information regarding resource allocation for one or more DRUs may include first information regarding whether a DRU or a regular RU (RRU) is applied (e.g., a DRU / RRU indicator subfield) and second information regarding the distributed bandwidth to which the DRU is applied (e.g., a DRU distributed bandwidth indicator subfield).

[0481] Here, the first information may be included in a public 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 multiple subfields indicating whether a DRU or RRU is applied in a frequency subblock unit of a specific size (e.g., 80 MHz). Additionally, the user information field for the first STA may further include an RU allocation subfield for allocating one or more DRUs within the distributed bandwidth.

[0482] The first STA can send a TB PPDU (S2220) to the second STA based on one or more corresponding DRUs within a bandwidth including a 40MHz channel.

[0483] In this regard, when one or more DRUs include 26-tone DRUs, the corresponding 26-tone DRU can be one of 18 predefined 26-tone DRU candidates. Here, the 18 26-tone DRU candidates can be defined based on available tones excluding DC tones, guard tones, the first empty tone group, and the second empty tone group.

[0484] The corresponding 18 26-tone DRU candidates can be defined based on the method described in Embodiments 1-1 of this disclosure.

[0485] According to this disclosure, the first empty tone group may include a tone adjacent to the guard tone, and the second empty tone group may include a tone adjacent to the DC tone. In this respect, the first empty tone group may be a tone index {-244, -243, -242, -241, +241, +242, +243, +244}, and the second empty tone group may be a tone index {-6, -5, -4, -3, +3, +4, +5, +6} (e.g., the proposed empty tone group 2).

[0486] For example, for 18 26-tone DRU candidates, the first 26-tone DRU may include tones with tone indices {-240:18:-24} and {7:18:223}, the second 26-tone DRU may include tones with tone indices {-239:18:-23} and {8:18:224}, the third 26-tone DRU may include tones with tone indices {-238:18:-22} and {9:18:225}, the fourth 26-tone DRU may include tones with tone indices {-237:18:-21} and {10:18:226}, the fifth 26-tone DRU may include tones with tone indices {-236:18:-20} and {11:18:227}, and the sixth... The 26-tone DRU can include tones with tone indices {-235:18:-19} and {12:18:228}, the 7th 26-tone DRU can include tones with tone indices {-234:18:-18} and {13:18:229}, the 8th 26-tone DRU can include tones with tone indices {-233:18:-17} and {14:18:230}, the 9th 26-tone DRU can include tones with tone indices {-232:18:-16} and {15:18:231}, the 10th 26-tone DRU can include tones with tone indices {-231:18:-15} and {16:18:232}, and the 11th... The 26-tone DRU may include tones with tone indices {-230:18:-14} and {17:18:233}, the 12th 26-tone DRU may include tones with tone indices {-229:18:-13} and {18:18:234}, the 13th 26-tone DRU may include tones with tone indices {-228:18:-12} and {19:18:235}, the 14th 26-tone DRU may include tones with tone indices {-227:18:-11} and {20:18:236}, the 15th 26-tone DRU may include tones with tone indices {-226:18:-10} and {21:18:237}, and the 16th A 26-tone DRU may include tones with tone indices {-225:18:-9} and {22:18:238}, a 17th 26-tone DRU may include tones with tone indices {-224:18:-8} and {23:18:239}, and an 18th 26-tone DRU may include tones with tone indices {-223:18:-7} and {24:18:240}. Here, the tone index {x:y:z} is the tone index of the tones selected from the tone with index x to the tone with index z in units of y tones.

[0487] Furthermore, according to this disclosure, when one or more of the aforementioned DRUs include 106-tone DRUs, the corresponding 106-tone DRU may include the tones of four of the 18 26-tone DRU candidates and two tones within the first empty tone group (e.g., see Examples 1-3). In other words, a 106-tone DRU may consist of two 52-tone DRUs and two additional empty tones. In this case, each 52-tone DRU may consist of two of the 18 26-tone DRU candidates, and the two additional empty tones may correspond to the two tones within the first empty tone group.

[0488] Furthermore, according to this disclosure, when one or more of the aforementioned DRUs include 242-tone DRUs, the corresponding 242-tone DRU may include the tones of nine of the eighteen 26-tone DRU candidates, four tones in the first empty tone group, and four tones in the second empty tone group (for example, see Examples 1-4). In other words, a 242-tone DRU may consist of two 106-tone DRUs, one 26-tone DRU, and four additional empty tones. In this case, each 106-tone DRU may consist of four 26-tone DRU candidates and two tones in the first empty tone group, and the four additional empty tones may correspond to the four tones in the second empty tone group.

[0489] Furthermore, according to this disclosure, the two pilot tones of a 26-tone DRU can be defined by applying a shift value to two tone indices in a specific order among the 26 tones of the corresponding 26-tone DRU. For example, the specific order can be one of (7th, 20th), (6th, 20th), or (7th, 21st) among the 26 tones.

[0490] Additionally, the corresponding shift value can be one of four different shift values ​​used for the 18 26-tone DRU candidates. For example, for the 18 26-tone DRU candidates, the shift value for the 1st, 2nd, 6th, and 7th 26-tone DRUs is p1; the shift value for the 3rd, 4th, 8th, and 9th 26-tone DRUs is p2; the shift value for the 10th, 11th, 15th, and 16th 26-tone DRUs is p3; and the shift value for the 12th, 13th, 17th, and 18th 26-tone DRUs is p3. The shift value of the 26-tone DRU is p4, and p1, p2, p3, and p4 can be different integer values ​​from each other (e.g., [p1, p2, p3, p4] = [-4, -2, +2, +4]).

[0491] Additionally, according to this disclosure, when the aforementioned bandwidth corresponds to a bandwidth exceeding 40 MHz, the DRU tone index in a specific 40 MHz channel within the corresponding bandwidth can be defined by applying a predefined tone shift value to the DRU tone index for the 40 MHz distributed bandwidth (DBW) (see, for example, Example 3).

[0492] Figure 22 The methods described in the examples can be derived from... Figure 1 The first device 100 in the process executes. For example, Figure 1 One or more processors 102 of the first device 100 may be configured to receive trigger frames including information on resource allocation for DRUs via one or more transceivers 106, and to transmit TB PPDUs based on one or more DRUs in a bandwidth including a 40MHz channel. Furthermore, one or more memories 104 of the first device 100 may store data for execution by one or more processors 102. Figure 22 The methods described in the examples or the instructions in the examples above.

[0493] Figure 23 This is a diagram illustrating an operational example of the second STA in the PPDU transmission and reception method based on the DRU tone scheme according to this disclosure.

[0494] Reference Figure 23 The second STA can send a trigger frame (S2310) to the first STA, which includes information on resource allocation for one or more Distributed Resource Units (DRUs).

[0495] For example, information regarding resource allocation for one or more DRUs may include first information regarding whether a DRU or a regular RU (RRU) is applied (e.g., a DRU / RRU indicator subfield) and second information regarding the distributed bandwidth to which the DRU is applied (e.g., a DRU distributed bandwidth indicator subfield).

[0496] Here, the first information may be included in a public 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 multiple subfields indicating whether a DRU or RRU is applied in a frequency subblock unit of a specific size (e.g., 80 MHz). Additionally, the user information field for the first STA may further include an RU allocation subfield for allocating one or more DRUs within the distributed bandwidth.

[0497] The second STA can receive TB PPDU (S2320) from the first STA based on one or more corresponding DRUs within a bandwidth including a 40MHz channel.

[0498] In this regard, when one or more DRUs include 26-tone DRUs, the corresponding 26-tone DRU can be one of 18 predefined 26-tone DRU candidates. Here, the 18 26-tone DRU candidates can be defined based on available tones excluding DC tones, guard tones, the first empty tone group, and the second empty tone group.

[0499] Due to the specific details regarding DRU tone plans for various DRU sizes, first and second empty tone groups, defining pilot tones based on tone index shifting, DRU tone indexes in bandwidths exceeding 40MHz, DRU-related indications / signaling, etc., and Figure 22 The examples described are the same, so repeated descriptions are omitted.

[0500] Figure 23 The methods described in the examples can be derived from... Figure 1 The second device 200 in the process is executed. For example, Figure 1 One or more processors 202 of the second device 200 can be configured to transmit trigger frames including information on resource allocation for DRUs via one or more transceivers 206, and to receive TB PPDUs based on one or more DRUs in a bandwidth including a 40MHz channel. Furthermore, one or more memories 204 of the second device 200 can store data for execution when performed by one or more processors 202. Figure 23 The methods described in the examples or the instructions in the examples above.

[0501] Figure 24This is a diagram illustrating the PPDU transmission or reception process between the transmitting STA and the receiving STA according to embodiments of this disclosure. Depending on the situation and / or configuration, etc., certain parts may be omitted. Figure 24 Some of the steps are shown below. The transmitting device and the receiving STA can be an AP and / or a non-AP STA.

[0502] Sending a STA can 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 including the RU, information about the STA receiving the RU, etc.

[0503] The STA can configure / generate a PPDU based on the obtained control information (S110). The configuration / generation of the PPDU can refer to each field of the configuration / generation. In other words, the configuration / generation of the PPDU may include the EHT-SIG-A / B / C field, which configures control information regarding tone planning.

[0504] In other words, configuring / generating a PPDU may include configuring fields that include control information (e.g., an N-bitmap) indicating the size / location of the RU and / or configuring fields that include the identifier (e.g., AID) of the STA receiving the RU.

[0505] Additionally, configuring / generating PPDUs can include generating STF / LTF sequences transmitted via a specific RU. STF / LTF sequences can be generated based on pre-configured STF / LTF generation sequences.

[0506] Additionally, configuring / generating PPDUs may include generating data fields (i.e., MPDUs) sent through a specific RU.

[0507] The sending STA can send the configured / generated PPDU to the receiving STA (S115).

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

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

[0510] Specifically, the receiving STA can decode the L-SIG and EHT-SIG of the PPDU based on the L-STF / LTF and obtain the information included in the L-SIG and EHT SIG fields. Information about the various tone schemes (i.e., RUs) of this disclosure can be included in the EHT-SIG (EHT-SIG-A / B / C, etc.), and the receiving STA can obtain information about the tone scheme (i.e., RU) through the EHT-SIG.

[0511] The receiving STA can decode the remaining part of the PPDU based on information about the obtained tone plan (i.e., RU) (S125). For example, the receiving STA can decode the STF / LTF field of the PPDU based on information about the tone plan (i.e., RU). In addition, 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.

[0512] Additionally, the receiving STA can perform processing operations to deliver decoded data to a higher layer (e.g., the MAC layer). Furthermore, when an indication signal is generated from the higher layer to the PHY layer in response to data being delivered to a higher layer, the receiving STA can perform subsequent operations.

[0513] Unlike existing WLAN systems that only use RRUs, when DRUs are supported, according to this disclosure, resource utilization efficiency can be improved by transmitting / receiving one or more fields of a PPDU based on a DRU tone schedule of various sizes applicable to PPDUs with bandwidths of 40 MHz or higher.

[0514] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature can be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure may include combinations of certain elements and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. It is clear that embodiments may include combinations of claims where there is no explicit dependency in the claims, or may be included as new claims by amendment after the application.

[0515] It will be apparent to those skilled in the art that this disclosure may be practiced in other specific forms without departing from the essential characteristics of this disclosure. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of the invention should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within the scope of the invention.

[0516] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that store such software or commands and are executable in the device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. Alternatively, the non-volatile memory devices in the memory may include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0517] [Industrial Applicability]

[0518] The method proposed in this disclosure is mainly described based on examples applied to IEEE 802.11-based systems and 5G systems, but it can also be applied to various WLAN or wireless communication systems other than those based on IEEE 802.11.

Claims

1. A method comprising: A trigger frame is received by the first station (STA) from the second STA, the trigger frame including information on resource allocation for one or more distributed resource units (DRUs); as well as The first STA transmits triggered (TB) physical layer protocol data units (PPDUs) to the second STA based on one or more DRUs within a bandwidth including a 40MHz channel. Wherein, the one or more DRUs include 26-tone DRUs, wherein the 26-tone DRU is one of 18 predefined 26-tone DRU candidates, and The 18 26-tone DRU candidates are defined based on the exclusion of available tones from the Direct Conversion (DC) tone, the Guard tone, the first empty tone group, and the second empty tone group.

2. The method according to claim 1, wherein: The first empty tone group includes the tone adjacent to the guard tone, and The second empty tone group includes the tone adjacent to the DC tone.

3. The method according to claim 2, wherein: The first empty tone group is the tone index {-244, -243, -242, -241, +241, +242, +243, +244}, and The second empty tone group is the tone index {-6, -5, -4, -3, +3, +4, +5, +6}.

4. The method according to claim 3, wherein: For the 18 26-tone DRU candidates The 126th tone DRU includes the tones indexed by tone {-240:18:-24} and {7:18:223}. The 26th tone DRU includes the tones indexed by tone {-239:18:-23} and {8:18:224}. The 326th tone DRU includes the tones indexed by tone {-238:18:-22} and {9:18:225}. The 426-tone DRU includes the tones indexed by the tones {-237:18:-21} and {10:18:226}. The 526th tone DRU includes the tones indexed by tone {-236:18:-20} and {11:18:227}. The 6th 26th tone DRU includes the tones indexed by tone {-235:18:-19} and {12:18:228}. The 7th 26th tone DRU includes the tones indexed by tone {-234:18:-18} and {13:18:229}. The 8th 26th tone DRU includes the tones indexed by tone {-233:18:-17} and {14:18:230}. The 9th 26th tone DRU includes the tones indexed by tone {-232:18:-16} and {15:18:231}. The 10th 26th tone DRU includes the tones indexed by tone {-231:18:-15} and {16:18:232}. The 11th 26th tone DRU includes the tones indexed by tone {-230:18:-14} and {17:18:233}. The 12th and 26th tone DRUs include the tones indexed by tone indices {-229:18:-13} and {18:18:234}. The 13th 26th tone DRU includes the tones indexed by tone {-228:18:-12} and {19:18:235}. The 14th and 26th tone DRUs include the tones indexed by tone indices {-227:18:-11} and {20:18:236}. The 15th and 26th tone DRUs include the tones indexed by tone {-226:18:-10} and {21:18:237}. The 16th and 26th tone DRUs include the tones indexed by tone {-225:18:-9} and {22:18:238}. The 17th and 26th tone DRUs include the tones indexed by tone {-224:18:-8} and {23:18:239}, and The 18th and 26th tone DRUs include the tones indexed by tone {-223:18:-7} and {24:18:240}. The pitch index [x:y:z] is the pitch index of the pitch selected from the pitch at index x to the pitch at index z, in units of pitch y.

5. The method according to claim 1, wherein: The one or more DRUs include 106-tone DRUs, which include the tones of four of the 18 26-tone DRU candidates and two tones within the first empty tone group.

6. The method according to claim 1, wherein: The one or more DRUs include the 242-tone DRUs, which include the tones of nine of the 18 26-tone DRU candidates, four tones in the first empty tone group, and four tones in the second empty tone group.

7. The method according to claim 1, wherein: The two pilot tones for the 26-tone DRU are defined by applying shift values ​​to two tone indices in a specific order among the 26 tones of the 26-tone DRU, and The shift value is one of four different shift values ​​used for the 18 26-tone DRU candidates.

8. The method according to claim 7, wherein: The specific order is one of the 26 tones: (7th, 20th), (6th, 20th), or (7th, 21st).

9. The method according to claim 7, wherein: For the 18 26-tone DRU candidates The shift value used for the 1st 26-tone DRU, the 2nd 26-tone DRU, the 6th 26-tone DRU, and the 7th 26-tone DRU is p1. The shift value used for the 3rd 26-tone DRU, 4th 26-tone DRU, 8th 26-tone DRU, and 9th 26-tone DRU is p2. The shift value for the 10th 26-tone DRU, the 11th 26-tone DRU, the 15th 26-tone DRU, and the 16th 26-tone DRU is p3, and The shift value for the 12th 26-tone DRU, 13th 26-tone DRU, 17th 26-tone DRU, and 18th 26-tone DRU is p4. p1, p2, p3, and p4 are distinct integer values.

10. The method according to claim 9, wherein: [p1, p2, p3, p4] is [-4, -2, +2, +4].

11. The method according to claim 1, wherein: Based on the bandwidth corresponding to a bandwidth of more than 40MHz, the DRU tone index in a specific 40MHz channel within the bandwidth is defined by applying a predefined tone shift value to the DRU tone index for the 40MHz distributed bandwidth.

12. The method according to claim 1, wherein: The information regarding the resource allocation for the one or more DRUs includes first information regarding whether a DRU or a regular RU (RRU) is applied, and second information regarding the distributed bandwidth to which the DRU is applied.

13. The method according to claim 12, wherein: The first information is included in the public information field within the trigger frame, and The second information is included in the user information field for the first STA within the trigger frame.

14. The method of claim 13, wherein: The first information includes multiple subfields that indicate whether the DRU or the RRU is applied at a frequency subblock unit of a specific size.

15. The method according to claim 13, wherein: The user information field further includes a RU allocation subfield for allocating the one or more DRUs within the distributed bandwidth.

16. An apparatus comprising: One or more transceivers; as well as One or more processors, said one or more processors being connected to said one or more transceivers, Wherein, the one or more processors are configured as follows: Receive a trigger frame that includes information on resource allocation for one or more Distributed Resource Units (DRUs); and Within a bandwidth including a 40MHz channel, trigger-based (TB) physical layer protocol data units (PPDUs) are transmitted based on one or more DRUs. Wherein, the one or more DRUs include 26-tone DRUs, wherein the 26-tone DRU is one of 18 predefined 26-tone DRU candidates, and The 18 26-tone DRU candidates are defined based on the exclusion of available tones from the Direct Conversion (DC) tone, the Guard tone, the first empty tone group, and the second empty tone group.

17. A method comprising: A trigger frame is sent from the second station (STA) to the first STA, the trigger frame including information on resource allocation for one or more distributed resource units (DRUs); as well as The second STA receives triggered (TB) physical layer protocol data units (PPDUs) from the first STA within a bandwidth including a 40MHz channel, based on one or more DRUs. Wherein, the one or more DRUs include 26-tone DRUs, wherein the 26-tone DRU is one of 18 predefined 26-tone DRU candidates, and The 18 26-tone DRU candidates are defined based on the exclusion of available tones from the Direct Conversion (DC) tone, the Guard tone, the first empty tone group, and the second empty tone group.

18. An apparatus comprising: One or more transceivers; as well as One or more processors, said one or more processors being connected to said one or more transceivers, Wherein, the one or more processors are configured as follows: Sending a trigger frame that includes information on resource allocation for one or more Distributed Resource Units (DRUs); and Within a bandwidth including a 40MHz channel, triggered (TB) physical layer protocol data units (PPDUs) are received based on one or more DRUs. Wherein, the one or more DRUs include 26-tone DRUs, wherein the 26-tone DRU is one of 18 predefined 26-tone DRU candidates, and The 18 26-tone DRU candidates are defined based on the exclusion of available tones from the Direct Conversion (DC) tone, the Guard tone, the first empty tone group, and the second empty tone group.

19. A processing apparatus configured to control a station (STA) in a wireless local area network (WLAN) system, the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively connected to the at least one processor and storing instructions for performing the method according to any one of claims 1 to 15, based on execution by the at least one processor.

20. At least one non-transitory computer-readable medium, said non-transitory computer-readable medium storing at least one instruction, wherein: The at least one instruction is executed by at least one processor to control the device to perform the method according to any one of claims 1 to 15 in a wireless local area network (WLAN) system.

Images