PPDU transmission / reception method and device in wireless LAN system

Abstract

A method and apparatus for transmitting and receiving a PPDU in a wireless LAN system are disclosed. The method, performed by a first station according to an embodiment of the present disclosure, may include generating a PPDU (physical protocol data unit) to be transmitted within an 80 MHz frequency bandwidth and transmitting the PPDU to a second station.

Description

[Technical Field]

[0001] The present disclosure relates to a method and apparatus for transmitting and receiving a physical protocol data unit (PPDU) 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 decrease latency. Among WLAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, technologies recently introduced to WLANs include enhancements to the 802.11ac standard for Very High-Throughput (VHT) and the IEEE 802.11ax standard for High Efficiency (HE).

[0003] To provide a more improved wireless communication environment, improved technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for increased bandwidth, efficient use of multiple bands, and multiple input multiple output (MIMO) that support increased spatial streams, and multiple access point (AP) coordination are being researched. In particular, various technologies for supporting traffic with low latency or real-time characteristics are being researched. In addition, new technologies for supporting ultra high reliability (UHR), including improvements or extensions to EHT technology, are being discussed. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving a PPDU including resource units (RUs) configured with non-contiguous subcarriers.

[0005] The technical problems to be solved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0006] A method performed by a first station (STA) according to one embodiment of the present disclosure may include (may comprise; may comprise; may construct; may establish; may encompass; may contain; may have) a step of generating a physical protocol data unit (PPDU) to be transmitted within a 20 MHz frequency bandwidth and transmitting the PPDU to a second STA. A plurality of first-type resource units (RUs) within the 20 MHz frequency bandwidth may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, and each of the plurality of first-type RUs may be configured with discontinuous subcarriers at predetermined intervals in the frequency domain, and a position of the PPDU relative to one or more first-type RUs may be indicated by an RU allocation subfield in an ascending order of the plurality of first-type RUs based on the lowest subcarrier of each of the plurality of first-type RUs in the frequency domain.

[0007] A method performed by a second station (STA) according to a further aspect of the present disclosure may include receiving a physical protocol data unit (PPDU) within a 20 MHz frequency bandwidth from a first STA and processing the PPDU, wherein a plurality of first-type resource units (RUs) within the 20 MHz frequency bandwidth are configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers, and each of the plurality of first-type RUs is configured with discontinuous subcarriers at predetermined intervals in the frequency domain, and a location of the PPDU for one or more first-type RUs may be indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs in the frequency domain based on the lowest subcarrier of each of the plurality of first-type RUs. [Effects of the Invention]

[0008] According to the present disclosure, transmission power can be increased by using RUs configured with non-contiguous subcarriers, thereby increasing transmission throughput and improving coverage.

[0009] Furthermore, according to the present disclosure, it is possible to reduce the signaling overhead for allocating RUs configured with non-contiguous subcarriers.

[0010] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief explanation of the drawings]

[0011] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples for the present disclosure and, together with the detailed description, explain the technical features of the present disclosure. [Figure 1] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an exemplary structure of a wireless LAN system to which the present disclosure can be applied. [Figure 3] FIG. 1 is a diagram illustrating a link setup process to which the present disclosure can be applied. [Figure 4] FIG. 10 is a diagram illustrating a backoff process to which the present disclosure can be applied. [Figure 5] 10A and 10B are diagrams for explaining a CSMA / CA base frame transmission operation to which the present disclosure can be applied. [Figure 6] 1 is a diagram illustrating an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied. [Figure 7] FIG. 1 illustrates an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure is applicable. [Figure 8] FIG. 1 illustrates an exemplary format of a trigger frame to which the present disclosure can be applied. [Figure 9] FIG. 1 illustrates an exemplary arrangement of resource units (RUs) used on a 20 MHz band. [Figure 10] FIG. 1 illustrates an exemplary arrangement of resource units (RUs) used on a 40 MHz band. [Figure 11] FIG. 1 illustrates an exemplary arrangement of resource units (RUs) used on an 80 MHz band. [Figure 12] A diagram illustrating the application of distributed tone RUs in a wireless LAN system to which the present disclosure can be applied. [Figure 13] 10 is a diagram illustrating the operation of a transmitting device for a PPDU transmission and reception method according to one embodiment of the present disclosure. [Figure 14] A diagram illustrating the operation of a receiving device for a PPDU transmission and reception method according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be practiced. The following detailed description includes (comprises; constitutes; constructs; sets; encompasses; contains; has) specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be practiced without such specific details.

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

[0014] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection as well as an indirect connection where there is another component between them. Also, in this disclosure, the terms "comprise" or "have" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0015] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0016] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular is intended to include the plural unless the context clearly dictates otherwise. The term "and / or" as used in this disclosure means that one of the associated listed items may be included, or that any and all possible combinations of two or more of them are included. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0017] The examples of the present disclosure may be applied to various wireless communication systems. For example, the examples of the present disclosure may be applied to a wireless LAN system. For example, the examples of the present disclosure may be applied to a wireless LAN based on the IEEE 802.11a / g / n / ac / ax standard. Note that the examples of the present disclosure may be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard. Furthermore, the examples of the present disclosure may be applied to a wireless LAN based on a next-generation standard after IEEE 802.11bn. Furthermore, the examples of the present disclosure may be applied to a cellular wireless communication system. For example, the examples of the present disclosure may be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series technology and the 5G NR (New Radio) series technology of the 3GPP (3rd Generation Partnership Project: registered trademark; the same applies hereinafter) standard.

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

[0019] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0020] 1 may be referred to by various terms such as a terminal, a wireless device, a wireless transmit receive unit (WTRU), a user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a mobile subscriber unit (MSS), a subscriber station (SS), an advanced mobile station (AMS), a wireless terminal (WT), or simply a user. In addition, the first device 100 and the second device 200 may be referred to by various terms such as an access point (AP), a base station (BS), a fixed station, a Node B, a base transceiver system (BTS), a network, an artificial intelligence (AI) system, a road side unit (RSU), a repeater, a router, a relay, a gateway, etc.

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

[0022] 1, a first device 100 and a second device 200 may transmit and receive wireless signals using various wireless LAN technologies (e.g., the IEEE 802.11 family). The first device 100 and the second device 200 may include interfaces for a medium access control (MAC) layer and a physical layer (PHY) in accordance with the IEEE 802.11 standard.

[0023] In addition, the first device 100 and the second device 200 may further support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than WLAN technology. Furthermore, the devices of the present disclosure may be embodied as various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) equipment, and virtual reality (VR) equipment. Furthermore, the STAs of the present disclosure may support various communication services such as voice calls, video calls, data communications, autonomous driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), and Internet-of-Things (IoT).

[0024] The first device 100 includes 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 be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts of the present disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceiver 106. The processor 102 may also receive a wireless signal including second information / signals via the transceiver 106, and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts in this disclosure. Here, the processor 102 and the memory 104 may be part of a communications modem / circuit / chip designed to implement wireless LAN technology (e.g., the IEEE 802.11 series). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with an RF (Radio Frequency) unit. In this disclosure, a device may also refer to a communications modem / circuit / chip.

[0025] The second device 200 includes one or more processors 202, 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 be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled 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 executing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 202 and the memory 204 may be part of a communications modem / circuit / chip designed to implement wireless LAN technology (e.g., the IEEE 802.11 series). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a device may also refer to a communications modem / circuit / chip.

[0026] The hardware elements of the devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY and MAC). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in this disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods of this disclosure to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts of this disclosure.

[0027] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

[0028] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0029] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts of the present disclosure, to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and may be configured to transmit or receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, via the one or more antennas 108, 208. In this disclosure, the 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 convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing 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 using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

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

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

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

[0033] The structure of a WLAN system may be composed of multiple components. The interaction of these components may provide a WLAN that supports STA mobility transparent to higher layers. A Basic Service Set (BSS) is a basic building block of a WLAN. FIG. 2 illustrates two BSSs (BSS1 and BSS2), each including two STAs as members (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). The ellipses representing BSSs in FIG. 2 may be understood to represent coverage areas where STAs included in the BSSs maintain communication. This area may be referred to as a Basic Service Area (BSA). If a STA moves outside a BSA, it will no longer be able to directly communicate with other STAs within the BSA.

[0034] Ignoring the DS shown in FIG. 2, the most basic type of BSS in a WLAN is the Independent BSS (IBSS). For example, an IBSS may have a minimal configuration consisting of only two STAs. For example, assuming that other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4, are representative examples of an IBSS. Such a configuration is possible when STAs can communicate directly without an AP. Furthermore, in such a WLAN, a BSS may be configured when needed by the LAN, rather than being configured in advance. This can also be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In an IBSS, all STAs may be mobile, and connection to a distributed system (DS) is not permitted, forming a self-contained network.

[0035] The membership of STAs in a BSS may change dynamically as STAs join and leave the BSS area, etc. To become a member of a BSS, a STA may join the BSS using a synchronization process. To access all the services of the BSS-based architecture, a STA must be associated with the BSS. Such association may be dynamically configured and may include the use of a Distribution System Service (DSS).

[0036] In a wireless LAN, direct STA-to-STA distance may be limited by PHY performance. While such distance limits are sufficient in some cases, other situations may require communication between STAs over longer distances. To support extended coverage, a distributed system (DS) may be configured.

[0037] A DS refers to a structure in which BSSs are interconnected. Specifically, as shown in FIG. 2, a BSS may exist as a component of an expanded network composed of multiple BSSs. A DS is a logical concept and may be specified by the characteristics of a distributed system medium (DSM). In this regard, a wireless medium (WM) and a DSM may be logically distinguished. Each logical medium is used for different purposes and by different components. These media are neither limited to being the same nor limited to being different. The flexibility of a WLAN structure (DS structure or other network structure) can be explained by the fact that multiple media are logically distinct from one another. That is, a WLAN structure may be embodied in various ways, and the WLAN structure may be independently specified according to the physical characteristics of each implementation.

[0038] The DS can support mobile devices by providing seamless integration of multiple BSSs and logical services necessary for addressing destinations. The DS may also include a portal component that acts as a bridge between the wireless LAN and other networks (e.g., IEEE 802.X).

[0039] An AP is an entity that allows associated non-AP STAs to access the DS through the WM and also has the functionality of an STA. Data can be transferred between a BSS and a DS via the AP. For example, STA2 and STA3 shown in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS. Furthermore, since all APs essentially correspond to STAs, all APs are addressable entities. The address used by an AP for communication on the WM does not necessarily have to be the same as the address used by the AP for communication on the DSM. A BSS consisting of an AP and one or more STAs can be called an infrastructure BSS.

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

[0041] In the above-described DS structure, an Extended Service Set (ESS) may be configured to provide wider coverage.

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

[0043] A WLAN system does not make any assumptions about the relative physical locations of BSSs and can have any of the following configurations: BSSs may partially overlap, which is a configuration commonly used to provide continuous coverage; BSSs may not be physically connected, and there is no logical limit to the distance between BSSs; BSSs may be physically located in the same location, which may be used to provide redundancy; and one (or more) IBSS or ESS networks may physically exist in the same space as one (or more) ESS networks. This may apply to ESS network configurations when an ad-hoc network operates in the location where the ESS network exists, when physically overlapping wireless networks are formed by different organizations, or when two or more different access and security policies are required in the same location.

[0044] FIG. 3 is a diagram illustrating a link setup process to which the present disclosure can be applied.

[0045] In order for an STA to set up a link to a network and transmit and receive data, it must first discover the network, perform authentication, establish an association, and perform authentication procedures for security. The link setup process can also be called a session initiation process or a session setup process. In addition, the discovery, authentication, association, and security configuration processes of the link setup process can also be collectively called the association process.

[0046] In step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access a network, the STA must search for a joinable network. Before joining a wireless network, the STA must identify a compatible network. The process of identifying networks present in a specific area is called scanning.

[0047] Scanning methods include active scanning and passive scanning. FIG. 3 illustrates an example of a network discovery operation including an active scanning process. In active scanning, a scanning STA changes channels and transmits a probe request frame to search for nearby APs, and waits for a response. A responder transmits a probe response frame to the STA that transmitted the probe request frame in response to the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In a BSS, the AP transmits beacon frames, so the AP is the responder. In an IBSS, the STAs in the IBSS transmit beacon frames alternately, so the responder is not constant. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store the BSS-related information contained in the received probe response frame, move to the next channel (e.g., channel 2), and perform scanning in the same manner (i.e., send and receive probe requests / responses on channel 2).

[0048] Although not shown in FIG. 3, the scanning operation may be performed in a passive scanning manner. In passive scanning, a scanning STA waits for a beacon frame while changing channels. A beacon frame is a management frame defined in IEEE 802.11 and is periodically transmitted to announce the existence of a wireless network and allow a scanning STA to search for and join the wireless network. In a BSS, the AP is responsible for periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS transmit beacon frames in turn. When a scanning STA receives a beacon frame, it saves the BSS-related information included in the beacon frame and records the beacon frame information on each channel as it moves to other channels. A STA that receives a beacon frame saves the BSS-related information included in the received beacon frame, moves to the next channel, and scans the next channel in the same manner. Comparing active scanning with passive scanning, active scanning has the advantage of having a smaller delay and power consumption than passive scanning.

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

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

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

[0052] The STA can send an authentication request frame to the AP. The AP can determine whether to allow authentication for the STA based on the information contained in the received authentication request frame. The AP can provide the STA with the result of the authentication process using an authentication response frame.

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

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

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

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

[0057] FIG. 4 is a diagram illustrating a backoff process to which the present disclosure can be applied.

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

[0059] The IEEE 802.11 MAC protocol also provides a Hybrid Coordination Function (HCF). HCF is based on the DCF and Point Coordination Function (PCF). PCF is a polling-based synchronous access method that periodically polls all receiving APs and / or STAs to receive data frames. HCF also includes Enhanced Distributed Channel Access (EDCA) and HCF Controlled Channel Access (HCCA). EDCA is a contention-based access method for a provider to provide data frames to multiple users, while HCCA is a non-contention-based channel access method using a polling mechanism. HCF also includes a medium access mechanism for improving the quality of service (QoS) of wireless LANs and can transmit QoS data in both the contention period (CP) and the contention-free period (CFP).

[0060] The operation based on the random backoff period will be described with reference to FIG. 4. When an occupied / busy medium changes to an idle state, multiple STAs can attempt to transmit data (or frames). As a method for minimizing collisions, each STA can select a random backoff count and wait for the corresponding slot time before attempting transmission. The random backoff count has a pseudo-random integer value and may be determined to be any one of values ​​ranging from 0 to CW. Here, CW is a contention window parameter value. The CW parameter is given a CWmin as its initial value, but can be doubled in the event of a transmission failure (e.g., if 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 data transmission is successful, and if data transmission is successful, it is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are set to 2. n Preferably it is set to -1 (n=0,1,2,...).

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

[0062] In the example of FIG. 4, when a packet to be transmitted arrives at the MAC of STA3, STA3 confirms that the medium is idle for DIFS and can immediately transmit a frame. The remaining STAs monitor the medium for occupied / busy status and wait. Meanwhile, STA1, STA2, and STA5 may each have data to transmit. If each STA monitors the medium as idle, it waits for DIFS and then counts down its backoff slots according to its random backoff count value. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. That is, this example illustrates a case where, at the time STA2 finishes its backoff count and begins frame transmission, STA5's remaining backoff time is shorter than STA1's remaining backoff time. STA1 and STA5 pause their countdowns and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume their backoff counts. That is, STA5 can start frame transmission after counting down the remaining backoff slots equal to the remaining backoff time. Because STA5's remaining backoff time is shorter than STA1's, STA5 begins frame transmission. While STA2 is occupying the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS, then counts down the random backoff count value it selected, and can begin frame transmission. The example in FIG. 4 shows a case where STA5's remaining backoff time happens to match STA4's random backoff count value, which may result in a collision between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failed data transmission. In this case, STA4 and STA5 can double their CW values, select a random backoff count value, and then count down.STA1 waits while the medium is occupied by transmissions from STA4 and STA5, but when the medium becomes idle, it waits for DIFS and can begin frame transmission once the remaining backoff time has elapsed.

[0063] As shown in the example of Figure 4, a data frame is a frame used for transmitting data to be forwarded to a higher layer, and may be transmitted after a backoff that occurs after a DIFS has elapsed since the medium became idle. Furthermore, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff that occurs after an IFS, such as a DIFS or a PIFS (Point Coordination Function IFS). Subtype frames of management frames include a beacon, an association request / response, a re-association request / response, a probe request / response, and an authentication request / response. A control frame is a frame used to control access to a medium. Subtype frames of control frames include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), BlockAck, BlockACKReq, NDP announcement (null data packet announcement), and Trigger. If a control frame is not a response frame of a previous frame, it is transmitted after a backoff that is performed after a DIFS has elapsed. If a control frame is a response frame of a previous frame, it is transmitted without a backoff after a short IFS (SIFS) has elapsed. The type and subtype of a frame may be identified by the type field and subtype field in the Frame Control (FC) field.

[0064] A Quality of Service (QoS) STA can transmit a frame after backing off after the arbitration IFS (AIFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed. Here, a frame that can use AIFS[i] can be a data frame, a management frame, or a control frame that is not a response frame.

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

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

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

[0068] In order to reduce the possibility of collisions between transmissions from multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, STA3 may determine that the medium is idle as a result of carrier sensing. That is, STA1 may be a hidden node to STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, STA3 may determine that the medium is idle as a result of carrier sensing. That is, STA2 may be a hidden node to 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 outside the carrier sensing range for transmissions from STA1 or STA3, can prevent STAs from attempting to occupy the channel during data transmission and reception between STA1 and STA2.

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

[0070] When the channel is idle in DIFS, STA1 can send an RTS frame to STA2 after backing off. When STA2 receives the RTS frame, it can send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0071] If STA3 cannot overhear the CTS frame from STA2 but can overhear the RTS frame from STA1, STA3 can use the duration information included in the RTS frame to set a NAV timer for the frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) that will be transmitted subsequently. Alternatively, if STA3 cannot overhear the RTS frame from STA1 but can overhear the CTS frame from STA2, STA3 can use the duration information included in the CTS frame to set a NAV timer for the frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame) that will be transmitted subsequently. That is, if STA3 can overhear one or more RTS or CTS frames from at least one of STA1 and STA2, it can set a NAV based thereon. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0072] When STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 SIFS after the completion of reception of the CTS frame. When STA2 successfully receives a data frame, it can transmit an ACK frame, which is a response to the data frame, to STA1 SIFS after the completion of reception of the CTS frame. When STA2 successfully receives a data frame, it can transmit an ACK frame, which is a response to the data frame, to STA1 SIFS after the expiration of the NAV timer. When STA3 determines that the channel is not being used by another terminal during the DIFS period after the expiration of the NAV timer, it can attempt channel access after the contention window (CW) with random backoff has elapsed.

[0073] FIG. 6 is a diagram illustrating an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

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

[0075] Thus, information transmission / reception in a wireless LAN system is performed in the form of frames, and for this purpose, a PHY layer protocol data unit (PPDU) frame format is defined.

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

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

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

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

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

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

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

[0083] FIG. 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure is applicable.

[0084] 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 an L-LTF, an L-STF, an L-SIG, and a Data field. The basic PPDU format can also be called a non-HT PPDU format (see FIG. 7(a)).

[0085] The HT PPDU format (IEEE 802.11n) further includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format shown in Figure 7(b) can be referred to as an HT-mixed format. An HT-greenfield format PPDU may also be defined, which corresponds to a format that does not include L-STF, L-LTF, or L-SIG, but is composed of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a Data field (not shown).

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

[0087] An example of the HE PPDU format (IEEE 802.11ax) further includes the fields Repeated L-SIG (RL-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and Packet Extension (PE) in addition to the basic PPDU format (FIG. 7(d)). Depending 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 multiple users (MU), but not in the HE PPDU format for single users (SU). Also, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may be 8 us. The HE Extended Range (ER) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may be 16 us. For example, the RL-SIG may be configured to be the same as the L-SIG. Based on the presence of the RL-SIG, the receiving STA can determine that the received PPDU is an HE PPDU or an EHT PPDU (described later).

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

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

[0090] The EHT TB PPDU in Figure 7(f) omits the EHT-SIG compared to the EHT MU PPDU. A STA that receives a trigger for UL MU transmission (e.g., a trigger frame or TRS (triggered response scheduling)) can perform UL transmission based on the EHT TB PPDU format.

[0091] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal Signal), and EHT-SIG fields may be encoded and modulated and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz) so that legacy STAs can also attempt demodulation and decoding. These may be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields may be encoded and modulated and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz) so that they can be demodulated and decoded by STAs that successfully decode non-legacy SIGs (e.g., U-SIG and / or EHT-SIG) and obtain the information contained in these fields. These may be referred to as EHT modulated fields.

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

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

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

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

[0096] The A-bit information transmitted by the U-SIG can be divided into version-independent bits and version-dependent bits. For example, the U-SIG may be included in a new PPDU format (e.g., a UHR PPDU format) not shown in Fig. 7. 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, but some or all of the version-dependent bits may be different.

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

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

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

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

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

[0102] Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units in the bandwidth of the PPDU. For example, the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to PPDU bandwidths equal to or larger than a predetermined size.

[0103] 7, non-legacy SIGs such as HE-SIG-B and EHT-SIG may contain control information for receiving STAs. Non-legacy SIGs may be transmitted in at least one symbol, and one symbol may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG may be included in previous SIGs (e.g., HE-SIG-A, U-SIG, etc.).

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

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

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

[0107] The common field may include CRC bits and tail bits, where the length of the CRC bits may be determined to be 4 bits, and the length of the tail bits may be determined to be 6 bits and set to 000000. The common field may include RU allocation information. The RU allocation information may include information regarding the locations of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.

[0108] An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. An RU may also be defined when transmitting a signal to a single STA. Resources may be allocated in RU units for the non-legacy STF, non-legacy LTF, and Data field.

[0109] Applicable RU sizes may be defined depending on the PPDU bandwidth. RUs may be defined to be the same or different for applicable PPDU formats (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80 MHz PPDU, the RU arrangements for HE PPDU and EHT PPDU may be different from each other. The applicable RU size, number of RUs, RU locations, DC (direct current) subcarrier locations and numbers, null subcarrier locations and numbers, and guard subcarrier locations and numbers for each PPDU bandwidth may be referred to as a tone plan. For example, a tone plan for a wide bandwidth may be defined as multiple repetitions of a tone plan for a low bandwidth.

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

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

[0112] The names of the fields in the PPDU format of Fig. 7 are merely examples, and the scope of the present disclosure is not limited by the names. In addition, examples of the present disclosure may be applied to a new PPDU format in which some fields are excluded and / or some fields are added based on the PPDU format of Fig. 7, in addition to the PPDU format illustrated in Fig. 7.

[0113] trigger frame

[0114] FIG. 8 is a diagram illustrating an exemplary format of a trigger frame to which the present disclosure can be applied.

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

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

[0117] The user info list contains zero or more user info fields. Figure 8 illustrates an example of an EHT variant user info field format.

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

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

[0120] [Table 1]

[0121] JPEG2026506036000003.jpg78161

[0122] JPEG2026506036000004.jpg205162

[0123] JPEG2026506036000005.jpg169161

[0124] JPEG2026506036000006.jpg74161

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

[0126] In the trigger frame RU allocation table of Table 1, the parameter N may be calculated based on the formula N=2*X1+X0. For bandwidths below 80 MHz, the PS160, B0, X0, and X1 values ​​may be set to 0. For bandwidths of 160 MHz and 320 MHz, the PS160, B0, X0, and X1 values ​​may be set as shown in Table 2. This setting represents the absolute frequency order for the primary and secondary 80 MHz and 160 MHz channels. The order from left to right represents the order from lowest frequency to highest frequency. The primary 80 MHz channel is denoted as P80, the secondary 80 MHz channel is denoted as S80, and the secondary 160 MHz channel is denoted as S160.

[0127] [Table 2]

[0128] Resource Unit (RU) and Resource Allocation

[0129] 9 to 11 are diagrams illustrating examples of resource units in a wireless LAN system to which the present disclosure can be applied.

[0130] 9 to 11, a resource unit (RU) defined in a wireless LAN system will be described. An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. An RU may also be defined when transmitting a signal to one STA. An RU may be used for the STF, LTF, data field, etc. of a PPDU.

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

[0132] FIG. 9 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on a 20 MHz band.

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

[0134] The RU arrangement in Figure 9 can be used for a single user (SU) situation as well as a multiple user (MU) situation, in which case one 242 unit can be used, as shown at the bottom of Figure 9. In this case, three DC tones can be inserted.

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

[0136] FIG. 10 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on a 40 MHz band.

[0137] Just as various sizes of RUs are used in the example of Figure 9, 26 RUs, 52 RUs, 106 RUs, 242 RUs, 484 RUs, etc. may be used in the example of Figure 10. Also, five DC tones may be inserted at the center frequency, 12 tones may be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 40 MHz band.

[0138] Also, as shown, when used for a single user, 484 RUs may be used.

[0139] FIG. 11 is a diagram illustrating an exemplary arrangement of resource units (RUs) used on an 80 MHz band.

[0140] 9 and 10, RUs of various sizes may be used in the example of Fig. 11, such as 26 RUs, 52 RUs, 106 RUs, 242 RUs, 484 RUs, and 996 RUs. Furthermore, the RU allocations of the HE PPDU and the EHT PPDU may differ from each other in an 80 MHz PPDU, and the example of Fig. 11 shows an example of the RU allocation for an 80 MHz EHT PPDU. In the example of Fig. 11, the HE PPDU and the EHT PPDU are the same in that 12 tones are used as a guard band in the leftmost band of the 80 MHz band and 11 tones are used as a guard band in the rightmost band of the 80 MHz band. In the HE PPDU, seven DC tones are inserted into the DC band, and there are two 26 RUs on each side of the DC band, corresponding to 13 tones. In contrast, in the EHT PPDU, 23 DC tones are inserted into the DC band, and there are two 26 RUs on each side of the DC band, corresponding to 13 tones. In the HE PPDU, there is one null subcarrier among the 242 RUs outside the center band, but in the EHT PPDU, there are five null subcarriers. In the HE PPDU, one 484 RU does not contain a null subcarrier, but in the EHT PPDU, one 484 RU contains five null subcarriers.

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

[0142] An EHT PPDU of 160 MHz or more may be configured as multiple 80 MHz sub-blocks in Figure 11. The RU allocation for each 80 MHz sub-block may be the same as the RU allocation for the 80 MHz EHT PPDU in Figure 11. If the 80 MHz sub-blocks of a 160 MHz or 320 MHz EHT PPDU are not punctured and the entire 80 MHz sub-block is used as part of an RU or MRU (Multiple RU), the 80 MHz sub-block can use 996 RUs in Figure 11.

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

[0144] If an 80 MHz sub-block contains RUs with fewer than 996 tones or if portions of the 80 MHz sub-block are punctured, the 80 MHz sub-block can use an RU placement that excludes 996-tone RUs.

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

[0146] Table 3 illustrates the indexes of the RUs in a 20 MHz PPDU and the data and pilot subcarrier indexes (ranges) for each RU.

[0147] [Table 3]

[0148] Table 4 illustrates the index of the RUs in a 40 MHz PPDU and the data and pilot subcarrier index (range) for each RU.

[0149] [Table 4]

[0150] Table 5 illustrates the index of the RUs in an 80MHz PPDU and the data and pilot subcarrier index (range) for each RU.

[0151] [Table 5]

[0152] Table 6 illustrates the index of the RUs in a 160 MHz PPDU and the data and pilot subcarrier index (range) for each RU.

[0153] [Table 6]

[0154] JPEG2026506036000012.jpg186146

[0155] Table 7 illustrates the index of the RUs in a 320 MHz PPDU and the data and pilot subcarrier index (range) for each RU.

[0156] [Table 7]

[0157] JPEG2026506036000014.jpg206145

[0158] JPEG2026506036000015.jpg206147

[0159] JPEG2026506036000016.jpg75144

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

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

[0162] Referring to FIGS. 9 to 11 and Tables 3 to 7, RU indices may be assigned to each RU in order from lowest frequency to highest frequency.

[0163] A PPDU in the 160 MHz or higher range may be composed of multiple 80 MHz frequency subblocks. The tone plan and RU allocation for each 80 MHz frequency subblock may be the same as for the 80 MHz PPDU. When an 80 MHz frequency subblock of a 160 MHz or 320 MHz PPDU is not punctured and the entire 80 MHz frequency subblock is used as an RU or as part of an RU / MRU, the 80 MHz frequency subblock can use the 996-tone RU illustrated in Figure 10. When an 80 MHz frequency subblock contains RUs with fewer than 996 tones or when a portion of the 80 MHz frequency subblock is punctured, the 80 MHz frequency subblock can use a tone plan and RU allocation excluding the 996-tone RU, as illustrated in Figure 10.

[0164] A STA may be assigned multiple RUs (MRUs), and the subcarrier index of an MRU may be configured with the index of the RU that makes up the MRU.

[0165] The RUs of the present disclosure may be used for uplink (UL) and / or downlink (DL) communications. For example, when trigger-based UL-MU communications are performed, a STA (e.g., an AP) transmitting a trigger may use trigger information (e.g., a trigger frame or triggered response scheduling (TRS)) to assign a first RU (e.g., 26 / 52 / 106 / 242 RUs, etc.) to a first STA and a second RU (e.g., 26 / 52 / 106 / 242 RUs, etc.) to a second STA. The first STA may then transmit a first trigger-based (TB) PPDU based on the first RU, and the second STA may transmit a second TB PPDU based on the second RU. The first and second TB PPDUs may be transmitted to the AP in the same time interval.

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

[0167] EHT-SIG Field

[0168] The EHT-SIG field of a 20 MHz EHT MU PPDU contains one EHT-SIG content channel. In OFDMA transmission and non-OFDMA transmission for multiple users, the EHT-SIG field of a 40 MHz or 80 MHz EHT MU PPDU contains two EHT-SIG content channels. In OFDMA transmission and non-OFDMA transmission for multiple users, the EHT-SIG field of a 160 MHz or higher EHT MU PPDU contains two EHT-SIG content channels per 80 MHz frequency sub-block. When the EHT MU PPDU bandwidth for OFDMA transmission is wider than 80 MHz, the EHT-SIG content channels per 80 MHz frequency sub-block can carry different information.

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

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

[0171] In non-OFDMA transmissions, the common field of the EHT-SIG content channel may not include the RU allocation subfield.

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

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

[0174] The RU allocation A subfield and the RU allocation B subfield may both refer to RU allocation subfields located in different common encoding blocks.

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

[0176] Table 8 illustrates the mapping of the number of user fields per RU or MRU to RU allocation in the 9-bit RU allocation subfield and associated user specific fields in the same EHT SIG content channel.

[0177] [Table 8]

[0178] JPEG2026506036000018.jpg209146

[0179] JPEG2026506036000019.jpg200146

[0180] JPEG2026506036000020.jpg194146

[0181] JPEG2026506036000021.jpg45144

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

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

[0184] In Table 8, if the RU Allocation subfield has a value specified as disregard, the STA shall user It is possible to skip (r,c) user fields and continue processing the EHT-SIG field.

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

[0186] [Table 9]

[0187] JPEG2026506036000023.jpg141146

[0188] Table 10 illustrates the indexes of null subcarriers for each RU size when the channel bandwidth is 20 MHz and 40 MHz.

[0189] [Table 10]

[0190] Table 11 illustrates the indexes of null subcarriers for each RU size when the channel bandwidth is 80 MHz, 160 MHz, and 320 MHz.

[0191] [Table 11]

[0192] Distributed RU (DRU: distributed tones RU) allocation method

[0193] Regional regulations limit the power spectral density (PSD) in the sub-7 GHz band.

[0194] In the 6 GHz band, the PSD limit is even stricter, with a PSD limit of -1 dBm / MHz for non-AP STAs in the low power indoor (LPI) band. For a 52-tone RU, the maximum transmit power is approximately 6 dBm. This means that the PSD limit prevents the transmit power from reaching its maximum.

[0195] The limits for the 2.4GHz and 5GHz bands may differ depending on the region. For example, Europe, China, Japan, and South Korea apply a 10dBm / MHz PSD limit in the 2.4GHz band. Here, for a 52-tone RU, the maximum transmission power is approximately 17dBm.

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

[0197] As mentioned above, if the PSD limitation can be overcome, the transmission power can be increased, and the spectral efficiency or range can be improved.

[0198] Note that the PSD limits mentioned above are defined per MHz and per STA, i.e., by spreading small magnitude RU tones over a wide bandwidth, the tones for each STA are not contiguous and therefore each tone can be transmitted at a higher power.

[0199] In this disclosure, for convenience of explanation, an RU defined as a continuous tone in an existing WLAN system (e.g., IEEE 802.11ax, IEEE 802.11be, etc.) may be referred to as a regular RU (RRU), and an RU defined as a distributed (i.e., non-contiguous) tone may be referred to as a distributed tones RU (DRU). However, this is merely an example, and the present disclosure is not limited to these terms.

[0200] A STA transmitting a DRU can transmit at a higher power compared to an RRU. For example, in an 80 MHz band, a 52-tone DRU may have only one tone per MHz, whereas a 52-tone RRU has approximately 13 tones per MHz. Because the PSD limit in the 6 GHz LPI band is -1 dBm / MHz, a 52-tone RU can increase its transmit power by up to 11 dB using a DRU. This substantial transmit power boost allows for a higher MCS and longer signal reach.

[0201] FIG. 12 illustrates an example of application of distributed tone RUs in a wireless LAN system to which the present disclosure can be applied.

[0202] 12, STA1 can transmit a UL OFDMA PPDU on DRU1, STA2 can transmit a UL OFDMA PPDU on DRU2, and STA3 can transmit a UL OFDMA PPDU on DRU3. Here, STA1, STA2, and STA3 can all boost their transmission power by using the DRU. Thus, the DRU can be particularly useful for UL-OFDMA.

[0203] To maximize the power boost, the tones within one DRU should be as widely distributed as possible, for example, 1 tone / MHz, and the DRU size should be kept the same as the RRU size to avoid additional complexity.

[0204] Table 12 illustrates the power boost achievable for various DRUs at various bandwidths.

[0205] [Table 12]

[0206] In this way, the DRU can overcome the PSD limitation and provide significant gains. For example, for an 80MHz UL-OFDMA transmission with eight users, if each user uses a 106-tone DRU, the overall performance can be improved by 8.13dB compared to if each user uses a 106-tone RRU.

[0207] As mentioned above, in order to overcome the PSD constraints and obtain better power gain in a wireless LAN system (802.11), an RU that uses distributed tones rather than continuous tones (i.e., a distributed tones RU (DRU)) may be defined.

[0208] This disclosure proposes a method for mapping a DRU tone plan defined in an 80 MHz channel to an existing tone plan (i.e., an RRU tone plan) in order to maximize the use of existing signaling during DRU allocation.

[0209] Hereinafter, in the description of this disclosure, a subcarrier may be interpreted as having the same meaning as a tone, unless explicitly distinguished.

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

[0211] As shown in Figure 11, a relatively large-sized RRU may be configured by combining relatively small-sized RRUs, and similarly, a relatively large-sized DRU may be configured by combining relatively small-sized DRUs.Taking this into consideration, the following DRU tone plan may be applied.

[0212] Hereinafter, the 80 MHz DRU tone plan exemplified in this disclosure defines a DRU with the same RU size and the same number of tones as the existing 80 MHz RRU tone plan (except for the 996 DRU), and it is assumed that the same number and positions of guard / null / DC tones are used as existing ones.

[0213] A.26 DRU Index (i.e., 26 DRU Tone Plan)

[0214] In the following description, the notation "DRU-x" means that the index of the DRU is x.

[0215] Method 1) In the frequency domain, one tone may be assigned to each of the 36 26 RU tones in order from the lowest frequency available tone to the highest frequency available tone.

[0216] - 26 DRU-1:-499,-463,-425,-388,-351,-315,-277,-234,-196,-160,-123,-86,-48,13,49,87,124,161,197,235,278,316,352,389,426,464

[0217] - 26 DRU-2:-498,-462,-424,-387,-350,-314,-276,-233,-195,-159,-122,-85,-47,14,50,88,125,162,198,236,279,317,353,390,427,465

[0218] - 26 DRU-3:-497,-461,-423,-386,-349,-311,-275,-232,-194,-158,-121,-84,-46,15,51,89,126,163,201,237,280,318,354,391,428,466

[0219] - 26 DRU-4:-496,-460,-422,-385,-348,-310,-274,-231,-193,-157,-120,-83,-45,16,52,90,127,164,202,238,281,319,355,392,429,467

[0220] - 26 DRU-5:-495,-459,-421,-384,-347,-309,-273,-230,-192,-156,-118,-82,-44,17,53,91,128,165,203,239,282,320,356,394,430,468

[0221] - 26 DRU-6:-494,-458,-420,-383,-346,-308,-272,-229,-191,-155,-117,-81,-43,18,54,92,129,166,204,240,283,321,357,395,431,469

[0222] - 26 DRU-7:-493,-457,-419,-382,-345,-307,-271,-228,-190,-154,-116,-80,-42,19,55,93,130,167,205,241,284,322,358,396,432,470

[0223] - 26 DRU-8:-492,-456,-418,-381,-344,-306,-270,-227,-189,-153,-115,-79,-41,20,56,94,131,168,206,242,285,323,359,397,433,471

[0224] - 26 DRU-9:-491,-455,-417,-380,-343,-305,-269,-226,-188,-152,-114,-78,-40,21,57,95,132,169,207,243,286,324,360,398,434,472

[0225] - 26 DRU-10:-490,-454,-416,-379,-342,-304,-268,-225,-187,-151,-113,-77,-39,22,58,96,133,170,208,244,287,325,361,399,435,473

[0226] - 26 DRU-11:-489,-453,-415,-378,-341,-303,-267,-224,-186,-150,-112,-76,-38,23,59,97,134,171,209,245,288,326,362,400,436,474

[0227] - 26 DRU-12:-488,-452,-414,-377,-340,-302,-266,-223,-185,-149,-111,-75,-37,24,60,98,135,172,210,246,289,327,363,401,437,475

[0228] - 26 DRU-13:-487,-451,-413,-376,-339,-301,-265,-222,-184,-148,-110,-74,-36,25,61,99,136,173,211,247,290,328,364,402,438,476

[0229] - 26 DRU-14:-486,-450,-412,-375,-338,-300,-264,-221,-183,-147,-109,-73,-35,26,62,100,137,174,212,248,291,329,365,403,439,477

[0230] - 26 DRU-15:-485,-449,-411,-374,-337,-299,-263,-220,-182,-145,-108,-72,-34,27,63,101,138,175,213,249,292,330,367,404,440,478

[0231] - 26 DRU-16:-484,-448,-410,-373,-336,-298,-262,-219,-181,-144,-107,-71,-33,28,64,102,139,176,214,250,293,331,368,405,441,479

[0232] - 26 DRU-17:-483,-445,-409,-372,-335,-297,-261,-218,-180,-143,-106,-70,-32,29,67,103,140,177,215,251,294,332,369,406,442,480

[0233] - 26 DRU-18:-482,-444,-408,-371,-334,-296,-260,-217,-179,-142,-105,-69,-31,30,68,104,141,178,216,252,295,333,370,407,443,481

[0234] - 26 DRU-19:-481,-443,-407,-370,-333,-295,-252,-216,-178,-141,-104,-68,-30,31,69,105,142,179,217,260,296,334,371,408,444,482

[0235] - 26 DRU-20:-480,-442,-406,-369,-332,-294,-251,-215,-177,-140,-103,-67,-29,32,70,106,143,180,218,261,297,335,372,409,445,483

[0236] - 26 DRU-21:-479,-441,-405,-368,-331,-293,-250,-214,-176,-139,-102,-64,-28,33,71,107,144,181,219,262,298,336,373,410,448,484

[0237] - 26 DRU-22:-478,-440,-404,-367,-330,-292,-249,-213,-175,-138,-101,-63,-27,34,72,108,145,182,220,263,299,337,374,411,449,485

[0238] - 26 DRU-23:-477,-439,-403,-365,-329,-291,-248,-212,-174,-137,-100,-62,-26,35,73,109,147,183,221,264,300,338,375,412,450,486

[0239] - 26 DRU-24:-476,-438,-402,-364,-328,-290,-247,-211,-173,-136,-99,-61,-25,36,74,110,148,184,222,265,301,339,376,413,451,487

[0240] - 26 DRU-25:-475,-437,-401,-363,-327,-289,-246,-210,-172,-135,-98,-60,-24,37,75,111,149,185,223,266,302,340,377,414,452,488

[0241] - 26 DRU-26:-474,-436,-400,-362,-326,-288,-245,-209,-171,-134,-97,-59,-23,38,76,112,150,186,224,267,303,341,378,415,453,489

[0242] - 26 DRU-27:-473,-435,-399,-361,-325,-287,-244,-208,-170,-133,-96,-58,-22,39,77,113,151,187,225,268,304,342,379,416,454,490

[0243] - 26 DRU-28:-472,-434,-398,-360,-324,-286,-243,-207,-169,-132,-95,-57,-21,40,78,114,152,188,226,269,305,343,380,417,455,491

[0244] - 26 DRU-29:-471,-433,-397,-359,-323,-285,-242,-206,-168,-131,-94,-56,-20,41,79,115,153,189,227,270,306,344,381,418,456,492

[0245] - 26 DRU-30:-470,-432,-396,-358,-322,-284,-241,-205,-167,-130,-93,-55,-19,42,80,116,154,190,228,271,307,345,382,419,457,493

[0246] - 26 DRU-31:-469,-431,-395,-357,-321,-283,-240,-204,-166,-129,-92,-54,-18,43,81,117,155,191,229,272,308,346,383,420,458,494

[0247] - 26 DRU-32:-468,-430,-394,-356,-320,-282,-239,-203,-165,-128,-91,-53,-17,44,82,118,156,192,230,273,309,347,384,421,459,495

[0248] - 26 DRU-33:-467,-429,-392,-355,-319,-281,-238,-202,-164,-127,-90,-52,-16,45,83,120,157,193,231,274,310,348,385,422,460,496

[0249] - 26 DRU-34:-466,-428,-391,-354,-318,-280,-237,-201,-163,-126,-89,-51,-15,46,84,121,158,194,232,275,311,349,386,423,461,497

[0250] - 26 DRU-35:-465,-427,-390,-353,-317,-279,-236,-198,-162,-125,-88,-50,-14,47,85,122,159,195,233,276,314,350,387,424,462,498

[0251] - 26 DRU-36:-464,-426,-389,-352,-316,-278,-235,-197,-161,-124,-87,-49,-13,48,86,123,160,196,234,277,315,351,388,425,463,499

[0252] Method 2) In the frequency domain, one tone is assigned to each of the 36 26 RU tones in order from the lowest frequency available tone to the highest frequency available tone before the DC tone, and then mirror symmetry is applied to assign positive tone indices to each of the 36 26 RU tones.

[0253] - 26 DRU-1:+-{48,86,123,160,196,234,277,315,351,388,425,463,499}

[0254] - 26 DRU-2:+-{47,85,122,159,195,233,276,314,350,387,424,462,498}

[0255] - 26 DRU-3:+-{46,84,121,158,194,232,275,311,349,386,423,461,497}

[0256] - 26 DRU-4:+-{45,83,120,157,193,231,274,310,348,385,422,460,496}

[0257] - 26 DRU-5:+-{44,82,118,156,192,230,273,309,347,384,421,459,495}

[0258] - 26 DRU-6:+-{43,81,117,155,191,229,272,308,346,383,420,458,494}

[0259] - 26 DRU-7:+-{42,80,116,154,190,228,271,307,345,382,419,457,493}

[0260] - 26 DRU-8:+-{41,79,115,153,189,227,270,306,344,381,418,456,492}

[0261] - 26 DRU-9:+-{40,78,114,152,188,226,269,305,343,380,417,455,491}

[0262] - 26 DRU-10:+-{39,77,113,151,187,225,268,304,342,379,416,454,490}

[0263] - 26 DRU-11:+-{38,76,112,150,186,224,267,303,341,378,415,453,489}

[0264] - 26 DRU-12:+-{37,75,111,149,185,223,266,302,340,377,414,452,488}

[0265] - 26 DRU-13:+-{36,74,110,148,184,222,265,301,339,376,413,451,487}

[0266] - 26 DRU-14:+-{35,73,109,147,183,221,264,300,338,375,412,450,486}

[0267] - 26 DRU-15:+-{34,72,108,145,182,220,263,299,337,374,411,449,485}

[0268] - 26 DRU-16:+-{33,71,107,144,181,219,262,298,336,373,410,448,484}

[0269] - 26 DRU-17:+-{32,70,106,143,180,218,261,297,335,372,409,445,483}

[0270] - 26 DRU-18:+-{31,69,105,142,179,217,260,296,334,371,408,444,482}

[0271] - 26 DRU-19:+-{30,68,104,141,178,216,252,295,333,370,407,443,481}

[0272] - 26 DRU-20:+-{29,67,103,140,177,215,251,294,332,369,406,442,480}

[0273] - 26 DRU-21:+-{28,64,102,139,176,214,250,293,331,368,405,441,479}

[0274] - 26 DRU-22:+-{27,63,101,138,175,213,249,292,330,367,404,440,478}

[0275] - 26 DRU-23:+-{26,62,100,137,174,212,248,291,329,365,403,439,477}

[0276] - 26 DRU-24:+-{25,61,99,136,173,211,247,290,328,364,402,438,476}

[0277] - 26 DRU-25:+-{24,60,98,135,172,210,246,289,327,363,401,437,475}

[0278] - 26 DRU-26:+-{23,59,97,134,171,209,245,288,326,362,400,436,474}

[0279] - 26 DRU-27:+-{22,58,96,133,170,208,244,287,325,361,399,435,473}

[0280] - 26 DRU-28:+-{21,57,95,132,169,207,243,286,324,360,398,434,472}

[0281] - 26 DRU-29:+-{20,56,94,131,168,206,242,285,323,359,397,433,471}

[0282] - 26 DRU-30:+-{19,55,93,130,167,205,241,284,322,358,396,432,470}

[0283] - 26 DRU-31:+-{18,54,92,129,166,204,240,283,321,357,395,431,469}

[0284] - 26 DRU-32:+-{17,53,91,128,165,203,239,282,320,356,394,430,468}

[0285] - 26 DRU-33:+-{16,52,90,127,164,202,238,281,319,355,392,429,467}

[0286] - 26 DRU-34:+-{15,51,89,126,163,201,237,280,318,354,391,428,466}

[0287] - 26 DRU-35:+-{14,50,88,125,162,198,236,279,317,353,390,427,465}

[0288] - 26 DRU-36:+-{13,49,87,124,161,197,235,278,316,352,389,426,464}

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

[0290] The 52 DRU may be configured as a combination of two 26 DRUs, and may be defined as follows to distribute tones as much as possible within each RU:

[0291] - 52 DRU-1: Combination of 26 DRU-1 and 26 DRU-19

[0292] - 52 DRU-2: Combination of 26 DRU-2 and 26 DRU-20

[0293] - 52 DRU-3: Combination of 26 DRU-3 and 26 DRU-21

[0294] - 52 DRU-4: a combination of 26 DRU-4 and 26 DRU-22

[0295] - 52 DRU-5: 26 DRU-6 and 26 DRU-24 combination

[0296] - 52 DRU-6: 26 DRU-7 and 26 DRU-25 combination

[0297] - 52 DRU-7, 26 DRU-8, 26 DRU-26 combination

[0298] - 52 DRU-8: 26 DRU-9 and 26 DRU-27 combination

[0299] - 52 DRU-9: 26 DRU-10 and 26 DRU-28 combination

[0300] - 52 DRU-10: Combination of 26 DRU-11 and 26 DRU-29

[0301] - 52 DRU-11: 26 DRU-12 and 26 DRU-30 combination

[0302] - 52 DRU-12: Combination of 26 DRU-13 and 26 DRU-31

[0303] - 52 DRU-13: Combination of 26 DRU-15 and 26 DRU-33

[0304] - 52 DRU-14: 26 DRU-16 and 26 DRU-34 combination

[0305] - 52 DRU-15: 26 DRU-17 and 26 DRU-35 combination

[0306] - 52 DRU-16: 26 DRU-18 and 26 DRU-36 combination

[0307] C.106 DRU Index (i.e., 106 DRU Tone Plan)

[0308] The 106 DRU may be configured as a combination of two 52 DRUs and two null tones, and may be defined as follows to distribute the tones as much as possible.

[0309] - 106 DRU-1: i) 52 DRU-1, ii) 52 DRU-9, and iii) two null tones (for example, in scheme 1, null tones-447, 65 or null tones-65, 447 or null tones-66, 446 or null tones-199, 313 or null tones-200, 312 or null tones-312, 200 or null tones-313, 199 or null tones-446, 66); or i) 52 DRU-1, ii) 52 DRU-9, and iii) a combination of two null tones (e.g., in Method 2, null tones-447, 447 or null tones-65, 65 or null tones-66, 66 or null tones-199, 199 or null tones-200, 200 or null tones-312, 312 or null tones-313, 313 or null tones-446, 446).

[0310] - 106 DRU-2: i) 52 DRU-2, ii) 52 DRU-10, and iii) two null tones (for example, in method 1, null tones-446, 66 or null tones-447, 65 or null tones-65, 447 or null tones-66, 446 or null tones-199, 313 or null tones-200, 312 or null tones-312, 200 or null tones-313, 199); or i) 52 DRU-2, ii) 52 DRU-10, and iii) a combination of two null tones (e.g., in Method 2, null tones-446, 446 or null tones-447, 447 or null tones-65, 65 or null tones-66, 66 or null tones-199, 199 or null tones-200, 200 or null tones-312, 312 or null tones-313, 313).

[0311] - 106 DRU-3: i) 52 DRU-3, ii) 52 DRU-11, and iii) two null tones (for example, in method 1, null tones-313, 199 or null tones-446, 66 or null tones-447, 65 or null tones-65, 447 or null tones-66, 446 or null tones-199, 313 or null tones-200, 312 or null tones-312, 200); or i) 52 DRU-3, ii) 52 DRU-11, and iii) a combination of two null tones (e.g., in Method 2, null tones-313, 313 or null tones-446, 446 or null tones-447, 447 or null tones-65, 65 or null tones-66, 66 or null tones-199, 199 or null tones-200, 200 or null tones-312, 312).

[0312] - 106 DRU-4: i) 52 DRU-4, ii) 52 DRU-12, and iii) two null tones (for example, in method 1, null tones-312, 200 or null tones-313, 199 or null tones-446, 66 or null tones-447, 65 or null tones-65, 447 or null tones-66, 446 or null tones-199, 313 or null tones-200, 312); or i) 52 DRU-4, ii) 52 DRU-12, and iii) a combination of two null tones (e.g., in Method 2, null tones-312, 312 or null tones-313, 313 or null tones-446, 446 or null tones-447, 447 or null tones-65, 65 or null tones-66, 66 or null tones-199, 199 or null tones-200, 200).

[0313] - 106 DRU-5: i) 52 DRU-5, ii) 52 DRU-13, and iii) two null tones (for example, in scheme 1, null tones-200, 312 or null tones-312, 200 or null tones-313, 199 or null tones-446, 66 or null tones-447, 65 or null tones-65, 447 or null tones-66, 446 or null tones-199, 313); or i) 52 DRU-5, ii) 52 DRU-13, and iii) a combination of two null tones (e.g., in Method 2, null tones-200, 200 or null tones-312, 312 or null tones-313, 313 or null tones-446, 446 or null tones-447, 447 or null tones-65, 65 or null tones-66, 66 or null tones-199, 199).

[0314] - 106 DRU-6: i) 52 DRU-6, ii) 52 DRU-14, and iii) two null tones (for example, in scheme 1, null tones-199, 313 or null tones-200, 312 or null tones-312, 200 or null tones-313, 199 or null tones-446, 66 or null tones-447, 65 or null tones-65, 447 or null tones-66, 446); or i) 52 DRU-6, ii) 52 DRU-14, and iii) a combination of two null tones (e.g., in Method 2, null tones-199, 199 or null tones-200, 200 or null tones-312, 312 or null tones-313, 313 or null tones-446, 446 or null tones-447, 447 or null tones-65, 65 or null tones-66, 66).

[0315] - 106 DRU-7: i) 52 DRU-7, ii) 52 DRU-15, and iii) two null tones (for example, in scheme 1, null tones-66, 446 or null tones-199, 313 or null tones-200, 312 or null tones-312, 200 or null tones-313, 199 or null tones-446, 66 or null tones-447, 65 or null tones-65, 447); or i) 52 DRU-7, ii) 52 DRU-15, and iii) a combination of two null tones (e.g., in Method 2, null tones-66, 66 or null tones-199, 199 or null tones-200, 200 or null tones-312, 312 or null tones-313, 313 or null tones-446, 446 or null tones-447, 447 or null tones-65, 65).

[0316] - 106 DRU-8: i) 52 DRU-8, ii) 52 DRU-16, and iii) two null tones (for example, in method 1, null tones-65, 447 or null tones-66, 446 or null tones-199, 313 or null tones-200, 312 or null tones-312, 200 or null tones-313, 199 or null tones-446, 66 or null tones-447, 65); or i) 52 DRU-8, ii) 52 DRU-16, and iii) a combination of two null tones (e.g., in Method 2, null tones-65, 65 or null tones-66, 66 or null tones-199, 199 or null tones-200, 200 or null tones-312, 312 or null tones-313, 313 or null tones-446, 446 or null tones-447, 447).

[0317] D.242 DRU Index (i.e., 242 DRU Tone Plan)

[0318] The 242 DRU may be configured as a combination of two 106 DRUs, one 26 DRU (i.e., any one of the 26 DRUs not used in the RU combination to generate the 106 DRU - 5, 14, 23, or 32 may be used), and four null tones, and may be defined as follows to distribute the tones as much as possible:

[0319] - 242 DRU-1: i) 106 DRU-1, ii) 106 DRU-5, iii) 26 DRU-5 and 4 null tones (for example, in scheme 1, a combination of null tones -500, -253, 12, 259 or null tones -259, -12, 253, 500 or null tones -366, -119, 146, 393 or null tones -393, -146, 119, 366); or i) 106 DRU-1, ii) 106 DRU-5, iii) 26 DRU-5 and a combination of four null tones (e.g., in method 2, null tones -500, -253, 253, 500 or null tones -259, -12, 12, 259 or null tones -366, -119, 119, 366 or null tones -393, -146, 146, 393)

[0320] - 242 DRU-2: i) 106 DRU-2, ii) 106 DRU-6, iii) 26 DRU-14 and four null tones (for example, in scheme 1, null tones -393, -146, 119, 366 or null tones -500, -253, 12, 259 or null tones -259, -12, 253, 500 or null tones -366, -119, 146, 393); or i) 106 DRU-2, ii) 106 DRU-6, iii) 26 A combination of DRU-14 and four null tones (e.g., in method 2, null tones -393, -146, 146, 393 or null tones -500, -253, 253, 500 or null tones -259, -12, 12, 259 or null tones -366, -119, 119, 366)

[0321] - 242 DRU-3: i) 106 DRU-3, ii) 106 DRU-7, iii) 26 DRU-23 and four null tones (for example, in scheme 1, null tones -366, -119, 146, 393 or null tones -393, -146, 119, 366 or null tones -500, -253, 12, 259 or null tones -259, -12, 253, 500); or i) 106 DRU-3, ii) 106 DRU-7, iii) 26 A combination of DRU-23 and four null tones (e.g., in method 2, null tones -366, -119, 119, 366 or null tones -393, -146, 146, 393 or null tones -500, -253, 253, 500 or null tones -259, -12, 12, 259)

[0322] - 242 DRU-4: i) 106 DRU-4, ii) 106 DRU-8, iii) 26 DRU-32 and four null tones (for example, in scheme 1, null tones -259, -12, 253, 500 or null tones -366, -119, 146, 393 or null tones -393, -146, 119, 366 or null tones -500, -253, 12, 259); or i) 106 DRU-4, ii) 106 DRU-8, iii) 26 A combination of DRU-32 and four null tones (e.g., in method 2, null tones -259, -12, 12, 259 or null tones -366, -119, 119, 366 or null tones -393, -146, 146, 393 or null tones -500, -253, 253, 500)

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

[0324] A 484 DRU may be configured as a combination of two 242 DRUs, and may be defined as follows to distribute the tones as much as possible:

[0325] - 484 DRU-1: Combination of 242 DRU-1 and 242 DRU-3

[0326] - 484 DRU-2: Combination of 242 DRU-2 and 242 DRU-4

[0327] If the above-described DRU tone plan is applied, when transmitting DL OFDMA using a DRU, the RU allocation field / subfield (e.g., see Table 8) defined when transmitting DL OFDMA using an RRU may be used in the same manner (i.e., without modification). Similarly, when triggering a TB PPDU using a DRU, the RU allocation subfield (e.g., see Table 1) defined in the trigger frame that triggers TB PPDU transmission using an RRU may be used in the same manner (i.e., without modification).

[0328] Thus, to use the existing defined RU allocation subfield / field without modification for RU allocation (i.e., indicating the size and placement of RUs) for OFDAM transmission, further mapping between DRUs and RRUs is required.

[0329] In this disclosure, we propose a mapping / correspondence relationship between DRUs and RRUs as follows:

[0330] Here, it is assumed that the RRUs are defined as RRU-1, -2, ... in order from the lowest frequency to the highest frequency (see Table 3 above). In this case, the allocation of a specific DRU to a specific STA may be indicated by a mapped / associated RRU (i.e., RRU index) as defined below. Here, it may further be indicated that the DRU is applied to the PPDU (i.e., DL OFDMA PPDU, UL TB PPDU, etc.) (i.e., an indication that the RU allocation subfield / field is interpreted as the allocation of the DRU).

[0331] Example 1

[0332] In the first embodiment, a mapping method between DRUs and RRUs determined by one of the above-described methods 1 and 2 is proposed.

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

[0334] Each of the 484 DRUs may be mapped / corresponding to each of the 484 RRUs in turn as follows:

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

[0336] - 484 DRU-2:484 RRU-2

[0337] B.242 DRU and 242 RRU index mapping / correspondence

[0338] 484 DRU / RRU may be combined as follows:

[0339] - 484 DRU-1(484 RRU-1) = 242 DRU-1 + 242 DRU-3(242 RRU-1 + 242 RRU-2)

[0340] - 484 DRU-2(484 RRU-2) = 242 DRU-2 + 242 DRU-4(242 RRU-3 + 242 RRU-4)

[0341] Therefore, each of the 242 DRUs may be mapped / corresponding to each of the 242 RRUs as follows:

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

[0343] - 242 DRU-2:242 RRU-3

[0344] - 242 DRU-3:242 RRU-2

[0345] - 242 DRU-4:242 RRU-4

[0346] Index mapping / correspondence for C.106 DRU / 26 DRU-5 / 26 DRU-14 / 26 DRU-23 / 26 DRU-32

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

[0348] - 242 DRU-1(242 RRU-1) = 106 DRU-1 + 106 DRU-5 + 26 DRU-5 + Null Tone(106 RRU-1 + 106 RRU-2 + 26 RRU-5 + Null Tone)

[0349] - 242 DRU-2(242 RRU-3) = 106 DRU-2 + 106 DRU-6 + 26 DRU-14 + Null Tone(106 RRU-5 + 106 RRU-6 + 26 RRU-23 + Null Tone)

[0350] - 242 DRU-3(242 RRU-2) = 106 DRU-3 + 106 DRU-7 + 26 DRU-23 + Null Tone(106 RRU-3 + 106 RRU-4 + 26 RRU-14 + Null Tone)

[0351] - 242 DRU-4(242 RRU-4) = 106 DRU-4 + 106 DRU-8 + 26 DRU-32 + Null Tone(106 RRU-7 + 106 RRU-8 + 26 RRU-32 + Null Tone)

[0352] Therefore, each 106 DRU / 26 DRU-5 / 26 DRU-14 / 26 DRU-23 / 26 DRU-32 may be mapped / corresponded as follows:

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

[0354] - 106 DRU-2:106 RRU-5

[0355] - 106 DRU-3:106 RRU-3

[0356] - 106 DRU-4:106 RRU-7

[0357] - 106 DRU-5:106 RRU-2

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

[0359] - 106 DRU-7:106 RRU-4

[0360] - 106 DRU-8:106 RRU-8

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

[0362] - 26 DRU-14:26 RRU-23

[0363] - 26 DRU-23:26 RRU-14

[0364] - 26 DRU-32:26 RRU-32

[0365] D.52 DRU and 52 RRU index mapping / correspondence

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

[0367] - 106 DRU-1(106 RRU-1) = 52 DRU-1 + 52 DRU-9 + Null Tone(52 RRU-1 + 52 RRU-2 + Null Tone)

[0368] - 106 DRU-2(106 RRU-5) = 52 DRU-2 + 52 DRU-10 + Null Tone(52 RRU-9 + 52 RRU-10 + Null Tone)

[0369] - 106 DRU-3(106 RRU-3) = 52 DRU-3 + 52 DRU-11 + Null Tone(52 RRU-5 + 52 RRU-6 + Null Tone)

[0370] - 106 DRU-4(106 RRU-7) = 52 DRU-4 + 52 DRU-12 + Null Tone(52 RRU-13 + 52 RRU-14 + Null Tone)

[0371] - 106 DRU-5(106 RRU-2) = 52 DRU-5 + 52 DRU-13 + Null Tone(52 RRU-3 + 52 RRU-4 + Null Tone)

[0372] - 106 DRU-6(106 RRU-6) = 52 DRU-6 + 52 DRU-14 + Null Tone(52 RRU-11 + 52 RRU-12 + Null Tone)

[0373] - 106 DRU-7(106 RRU-4) = 52 DRU-7 + 52 DRU-15 + Null Tone(52 RRU-7 + 52 RRU-8 + Null Tone)

[0374] - 106 DRU-8(106 RRU-8) = 52 DRU-8 + 52 DRU-16 + Null Tone(52 RRU-15 + 52 RRU-16 + Null Tone)

[0375] Therefore, each of the 52 DRUs may be mapped / corresponding to each of the 52 RRUs as follows:

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

[0377] - 52 DRU-2:52 RRU-9

[0378] - 52 DRU-3:52 RRU-5

[0379] - 52 DRU-4:52 RRU-13

[0380] - 52 DRU-5:52 RRU-3

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

[0382] - 52 DRU-7:52 RRU-7

[0383] - 52 DRU-8:52 RRU-15

[0384] - 52 DRU-9:52 RRU-2

[0385] - 52 DRU-10:52 RRU-10

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

[0387] - 52 DRU-12:52 RRU-14

[0388] - 52 DRU-13:52 RRU-4

[0389] - 52 DRU-14:52 RRU-12

[0390] - 52 DRU-15:52 RRU-8

[0391] - 52 DRU-16:52 RRU-16

[0392] E.26 DRU and 26 RRU index mapping / correspondence

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

[0394] - 52 DRU-1(52 RRU-1) = 26 DRU-1 + 26 DRU-19(26 RRU-1 + 26 RRU-2)

[0395] - 52 DRU-2(52 RRU-9) = 26 DRU-2 + 26 DRU-20(26 RRU-19 + 26 RRU-20)

[0396] - 52 DRU-3(52 RRU-5) = 26 DRU-3 + 26 DRU-21(26 RRU-10 + 26 RRU-11)

[0397] - 52 DRU-4(52 RRU-13) = 26 DRU-4 + 26 DRU-22(26 RRU-28 + 26 RRU-29)

[0398] - 52 DRU-5(52 RRU-3) = 26 DRU-6 + 26 DRU-24(26 RRU-6 + 26 RRU-7)

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

[0400] - 52 DRU-7(52 RRU-7) = 26 DRU-8 + 26 DRU-26(26 RRU-15 + 26 RRU-16)

[0401] - 52 DRU-8(52 RRU-15) = 26 DRU-9 + 26 DRU-27(26 RRU-33 + 26 RRU-34)

[0402] - 52 DRU-9(52 RRU-2) = 26 DRU-10 + 26 DRU-28(26 RRU-3 + 26 RRU-4)

[0403] - 52 DRU-10(52 RRU-10) = 26 DRU-11 + 26 DRU-29(26 RRU-21 + 26 RRU-22)

[0404] - 52 DRU-11(52 RRU-6) = 26 DRU-12 + 26 DRU-30(26 RRU-12 + 26 RRU-13)

[0405] - 52 DRU-12(52 RRU-14) = 26 DRU-13 + 26 DRU-31(26 RRU-30 + 26 RRU-31)

[0406] - 52 DRU-13(52 RRU-4) = 26 DRU-15 + 26 DRU-33(26 RRU-8 + 26 RRU-9)

[0407] - 52 DRU-14(52 RRU-12) = 26 DRU-16 + 26 DRU-34(26 RRU-26 + 26 RRU-27)

[0408] - 52 DRU-15(52 RRU-8) = 26 DRU-17 + 26 DRU-35(26 RRU-17 + 26 RRU-18)

[0409] - 52 DRU-16(52 RRU-16) = 26 DRU-18 + 26 DRU-36(26 RRU-35 + 26 RRU-36)

[0410] Therefore, each of the 26 DRUs may be mapped / corresponded to each RRU as follows:

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

[0412] - 26 DRU-2:26 RRU-19

[0413] - 26 DRU-3:26 RRU-10

[0414] - 26 DRU-4:26 RRU-28

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

[0416] - 26 DRU-6:26 RRU-6

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

[0418] - 26 DRU-8:26 RRU-15

[0419] - 26 DRU-9:26 RRU-33

[0420] - 26 DRU-10:26 RRU-3

[0421] - 26 DRU-11:26 RRU-21

[0422] - 26 DRU-12:26 RRU-12

[0423] - 26 DRU-13:26 RRU-30

[0424] - 26 DRU-14:26 RRU-23

[0425] - 26 DRU-15:26 RRU-8

[0426] - 26 DRU-16:26 RRU-26

[0427] - 26 DRU-17:26 RRU-17

[0428] - 26 DRU-18:26 RRU-35

[0429] - 26 DRU-19:26 RRU-2

[0430] - 26 DRU-20:26 RRU-20

[0431] - 26 DRU-21:26 RRU-11

[0432] - 26 DRU-22:26 RRU-29

[0433] - 26 DRU-23:26 RRU-14

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

[0435] - 26 DRU-25:26 RRU-25

[0436] - 26 DRU-26:26 RRU-16

[0437] - 26 DRU-27:26 RRU-34

[0438] - 26 DRU-28:26 RRU-4

[0439] - 26 DRU-29:26 RRU-22

[0440] - 26 DRU-30:26 RRU-13

[0441] - 26 DRU-31:26 RRU-31

[0442] - 26 DRU-32:26 RRU-32

[0443] - 26 DRU-33:26 RRU-9

[0444] - 26 DRU-34:26 RRU-27

[0445] - 26 DRU-35:26 RRU-18

[0446] - 26 DRU-36:26 RRU-36

[0447] Example 2

[0448] Unlike the mapping rule in the first embodiment, the DRU index and the RRU index may be mapped to the same index, in which case the tone index of each DRU may be changed.

[0449] In contrast to the DRU defined by either one of the above methods 1 or 2, the DRU newly defined in Example 2 (i.e., the DRU having the same DRU index as the RRU index in the mapping rule) is denoted as DRU*.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0479] - 26 DRU*-28:26 RRU-28

[0480] - 26 DRU*-29:26 RRU-29

[0481] - 26 DRU*-30:26 RRU-30

[0482] - 26 DRU*-31:26 RRU-31

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0501] - 52 DRU*-13:52 RRU-13

[0502] - 52 DRU*-14:52 RRU-14

[0503] - 52 DRU*-15:52 RRU-15

[0504] - 52 DRU*-16:52 RRU-16

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

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

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

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

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

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

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

[0512] - 106 DRU*-7:106 RRU-7

[0513] - 106 DRU*-8:106 RRU-8

[0514] D.242 DRU* and 242 RRU index mapping / correspondence

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

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

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

[0518] - 242 DRU*-4:242 RRU-4

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

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

[0521] - 484 DRU*-2:484 RRU*-2

[0522] In such a case, the tone index of the new DRU* may be defined as follows:

[0523] A.26 DRU* Tone Index

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

[0525] - 26 DRU*-2:26 DRU-19

[0526] - 26 DRU*-3:26 DRU-10

[0527] - 26 DRU*-4:26 DRU-28

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

[0529] - 26 DRU*-6:26 DRU-6

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

[0531] - 26 DRU*-8:26 DRU-15

[0532] - 26 DRU*-9:26 DRU-33

[0533] - 26 DRU*-10:26 DRU-3

[0534] - 26 DRU*-11:26 DRU-21

[0535] - 26 DRU*-12:26 DRU-12

[0536] - 26 DRU*-13:26 DRU-30

[0537] - 26 DRU*-14:26 DRU-23

[0538] - 26 DRU*-15:26 DRU-8

[0539] - 26 DRU*-16:26 DRU-26

[0540] - 26 DRU*-17:26 DRU-17

[0541] - 26 DRU*-18:26 DRU-35

[0542] - 26 DRU*-19:26 DRU-2

[0543] - 26 DRU*-20:26 DRU-20

[0544] - 26 DRU*-21:26 DRU-11

[0545] - 26 DRU*-22:26 DRU-29

[0546] - 26 DRU*-23:26 DRU-14

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

[0548] - 26 DRU*-25:26 DRU-25

[0549] - 26 DRU*-26:26 DRU-16

[0550] - 26 DRU*-27:26 DRU-34

[0551] - 26 DRU*-28:26 DRU-4

[0552] - 26 DRU*-29:26 DRU-22

[0553] - 26 DRU*-30:26 DRU-13

[0554] - 26 DRU*-31:26 DRU-31

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

[0556] - 26 DRU*-33:26 DRU-9

[0557] - 26 DRU*-34:26 DRU-27

[0558] - 26 DRU*-35:26 DRU-18

[0559] - 26 DRU*-36:26 DRU-36

[0560] B.52 DRU*tone index

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

[0562] - 52 DRU*-2:52 DRU-9

[0563] - 52 DRU*-3:52 DRU-5

[0564] - 52 DRU*-4:52 DRU-13

[0565] - 52 DRU*-5:52 DRU-3

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

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

[0568] - 52 DRU*-8:52 DRU-15

[0569] - 52 DRU*-9:52 DRU-2

[0570] - 52 DRU*-10:52 DRU-10

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

[0572] - 52 DRU*-12:52 DRU-14

[0573] - 52 DRU*-13:52 DRU-4

[0574] - 52 DRU*-14:52 DRU-12

[0575] - 52 DRU*-15:52 DRU-8

[0576] - 52 DRU*-16:52 DRU-16

[0577] C.106 DRU*tone index

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

[0579] - 106 DRU*-2:106 DRU-5

[0580] - 106 DRU*-3:106 DRU-3

[0581] - 106 DRU*-4:106 DRU-7

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

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

[0584] - 106 DRU*-7:106 DRU-4

[0585] - 106 DRU*-8:106 DRU-8

[0586] D.242 DRU* Tone Index

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

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

[0589] - 242 DRU*-3:242 DRU-2

[0590] - 242 DRU*-4:242 DRU-4

[0591] E.484 DRU* Tone Index

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

[0593] - 484 DRU*-2:484 DRU*-2

[0594] Example 3: The DRU index may be generalized and mapped to each RRU as follows:

[0595] First, each of the 26 DRUs-a / b / c / d / e / f / g / h / i / j / k / l / m / n / o / p / q / r / s / t / u / v / w / x / y / z / aa / ab / ac / ad / ae / af / ag / ah / ai / aj can be defined as one of the above 26 DRUs-1 to 36. Here, the 26 DRUs-1 to 18 may correspond to DRUs defined by one of the above-mentioned methods 1 and 2. Alternatively, the definitions are not limited to the above-mentioned methods 1 and 2, and definitions of DRUs to which other tones are assigned may also be considered.

[0596] Also, 52 DRU-a / b / c / d / e / f / g / h / i / j / k / l / m / n / o / p, 106 DRU- a / b / c / d / e / f / g / h, 242 DRU-a / b / c / d, 484 DRU-a / b may be defined, for which the following combinations can be considered:

[0597] In this embodiment, the alphabet index order and the frequency order may be unrelated, and even if the alphabet indexes between the DRUs are the same, this does not mean that the order in each DRU is the same.

[0598] - 52 DRU-a: a combination of 26 DRU-a and 26 DRU-s

[0599] - 52 DRU-b: combination of 26 DRU-b and 26 DRU-t

[0600] - 52 DRU-c: a combination of 26 DRU-c and 26 DRU-u

[0601] - 52 DRU-d: combination of 26 DRU-d and 26 DRU-v

[0602] - 52 DRU-e: 26 DRU-f and 26 DRU-x combination

[0603] - 52 DRU-f: 26 DRU-g and 26 DRU-y combination

[0604] - 52 DRU-g: combination of 26 DRU-h and 26 DRU-z

[0605] - 52 DRU-h: 26 DRU-i and 26 DRU-aa combination

[0606] - 52 DRU-i: 26 DRU-j and 26 DRU-ab combinations

[0607] - 52 DRU-j: combination of 26 DRU-k and 26 DRU-ac

[0608] - 52 DRU-k: combination of 26 DRU-l and 26 DRU-ad

[0609] - 52 DRU-l: 26 DRU-m and 26 DRU-ae combination

[0610] - 52 DRU-m: combination of 26 DRU-o and 26 DRU-ag

[0611] - 52 DRU-n: 26 DRU-p and 26 DRU-ah combination

[0612] - Combination of 52 DRU-o, 26 DRU-q and 26 DRU-ai

[0613] - 52 DRU-p: 26 DRU-r and 26 DRU-aj combination

[0614] - 106 DRU-a: combination of 52 DRU-a, 52 DRU-i, and 2 null tones

[0615] - 106 DRU-b: combination of 52 DRU-b, 52 DRU-j, and two null tones

[0616] - 106 DRU-c: 52 DRU-c, 52 DRU-k, and 2 null tones combination

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

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

[0619] - 106 DRU-f: Combination of 52 DRU-f, 52 DRU-n, and 2 null tones

[0620] - 106 DRU-g: a combination of 52 DRU-g, 52 DRU-o, and two null tones

[0621] - 106 DRU-h: 52 DRU-h, 52 DRU-p, and 2 null tones combination

[0622] - 242 DRU-a: combination of 106 DRU-a, 106 DRU-e, 26 DRU-e, and 4 null tones

[0623] - 242 DRU-b: a combination of 106 DRU-b, 106 DRU-f, 26 DRU-n, and 4 null tones

[0624] - 242 DRU-c: a combination of 106 DRU-c, 106 DRU-g, 26 DRU-w, and 4 null tones

[0625] - 242 DRU-d: 106 DRU-d, 106 DRU-h, 26 DRU-af, and 4 null tones combination

[0626] - 484 DRU-a: 242 DRU-a, 242 DRU-c combination

[0627] - 484 DRU-b: combination of 242 DRU-b and 242 DRU-d

[0628] In this case, the following combinations and mappings may be considered:

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

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

[0631] - 484 DRU-b:484 RRU-2

[0632] B.242 DRU and 242 RRU index mapping / correspondence

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

[0634] - 242 DRU-b:242 RRU-3

[0635] - 242 DRU-c:242 RRU-2

[0636] - 242 DRU-d:242 RRU-4

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

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

[0639] - 106 DRU-b:106 RRU-5

[0640] - 106 DRU-c:106 RRU-3

[0641] - 106 DRU-d:106 RRU-7

[0642] - 106 DRU-e:106 RRU-2

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

[0644] - 106 DRU-g:106 RRU-4

[0645] - 106 DRU-h:106 RRU-8

[0646] D.52 DRU252 RRU

[0647] - 52 DRUs:52 RRU-1

[0648] - 52 DRU-b:52 RRU-9

[0649] - 52 DRU-c:52 RRU-5

[0650] - 52 DRU-D:52 RRU-13

[0651] - 52 DRU-e:52 RRU-3

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

[0653] - 52 DRU-g:52 RRU-7

[0654] - 52 DRU-h:52 RRU-15

[0655] - 52 DRU-i:52 RRU-2

[0656] - 52 DRU-j:52 RRU-10

[0657] - 52 DRU-k:52 RRU-6

[0658] - 52 DRU-l:52 RRU-14

[0659] - 52 DRU-m:52 RRU-4

[0660] - 52 DRU-n:52 RRU-12

[0661] - 52 DRU-o:52 RRU-8

[0662] - 52 DRU-p:52 RRU-16

[0663] E.26 DRU26 RRU Registration Information

[0664] - 26 DRUs:26 RRU-1

[0665] - 26 DRU-b:26 RRU-19

[0666] - 26 DRU-c:26 RRU-10

[0667] - 26 DRU-D:26 RRU-28

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

[0669] - 26 DRU-f:26 RRU-6

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

[0671] - 26 DRU-h:26 RRU-15

[0672] - 26 DRU-i:26 RRU-33

[0673] - 26 DRU-j:26 RRU-3

[0674] - 26 DRU-k:26 RRU-21

[0675] - 26 DRU-l:26 RRU-12

[0676] - 26 DRU-m:26 RRU-30

[0677] - 26 DRU-n:26 RRU-23

[0678] - 26 DRU-o:26 RRU-8

[0679] - 26 DRU-p:26 RRU-26

[0680] - 26 DRU-q:26 RRU-17

[0681] - 26 DRU-r:26 RRU-35

[0682] - 26 DRU-s:26 RRU-2

[0683] - 26 DRU-t:26 RRU-20

[0684] - 26 DRU-u:26 RRU-11

[0685] - 26 DRU-v:26 RRU-29

[0686] - 26 DRU-w:26 RRU-14

[0687] - 26 DRU-x:26 RRU-7

[0688] - 26 DRU-y:26 RRU-25

[0689] - 26 DRU-z:26 RRU-16

[0690] - 26 DRU-aa:26 RRU-34

[0691] - 26 DRU-ab:26 RRU-4

[0692] - 26 DRU-ac:26 RRU-22

[0693] - 26 DRU-ad:26 RRU-13

[0694] - 26 DRU-ae:26 RRU-31

[0695] - 26 DRU-af:26 RRU-32

[0696] - 26 DRU-ag:26 RRU-9

[0697] - 26 DRU-ah:26 RRU-27

[0698] - 26 DRU-ai:26 RRU-18

[0699] - 26 DRU-aj:26 RRU-36

[0700] Using the above DRU tone mapping can reduce signaling overhead when allocating a DRU to each STA, which is preferable from an implementation perspective.

[0701] FIG. 13 illustrates an operation of a transmitting device for a PPDU transmitting and receiving method according to an embodiment of the present disclosure.

[0702] Fig. 13 illustrates an example of the operation of a transmitting device based on the above-described proposed method. The illustration in Fig. 13 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in Fig. 13 may be omitted depending on the situation and / or setting.

[0703] Referring to FIG. 13, a transmitting device generates a PPDU to be transmitted within an 80 MHz frequency bandwidth (S1301).

[0704] Here, the PPDU transmitting device may be an AP or a non-AP STA, and the PPDU receiving device may be an AP or a non-AP STA. Hereinafter, for convenience of explanation, the transmitting device may be referred to as a first STA, and the receiving device may be referred to as a second STA.

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

[0706] The transmitting device can then configure / generate a PPDU based on the acquired control information. Configuring / generating a PPDU may include configuring / generating each field of the PPDU. That is, step S1301 may include configuring one or more fields containing control information related to a tone plan. For example, step S1301 may include configuring a field containing control information indicating the size / location of an RU (e.g., an N-bitmap) and / or configuring a field containing an identifier (e.g., an AID) of a STA receiving the RU.

[0707] Step S1301 may also include generating an STF / LTF sequence to be transmitted in a specific RU. The STF / LTF sequence may be generated based on a previously set STF generation sequence / LTF generation sequence.

[0708] Step S1301 may also include generating a data field (ie, an MPDU) to be transmitted in a specific RU.

[0709] According to an embodiment of the present disclosure, multiple Type 1 RUs (i.e., DRUs) within an 80 MHz frequency bandwidth may be configured with available subcarriers. Here, the available subcarriers may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. The available subcarriers may vary depending on the size of the RU. For example, a 26-subcarrier Type 1 RU, a 52-subcarrier Type 1 RU, and / or a 106-subcarrier Type 1 RU may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see FIG. 11 and Table 11). As another example, a 242-subcarrier Type 1 RU and / or a 484-subcarrier Type 1 RU may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see FIG. 11 and Table 11). As another example, a 996-subcarrier type 1 RU may be composed of subcarriers excluding one or more DC subcarriers and one or more guard subcarriers (see FIG. 11 and Table 11). Each of the multiple type 1 RUs may be composed of (or positioned at) non-contiguous subcarriers at predetermined intervals (e.g., 36 subcarrier intervals for a 26-subcarrier RU) in the frequency domain (i.e., at uniform intervals). That is, the multiple type 1 RUs may be defined according to Schemes 1 and 2 described above.

[0710] According to an embodiment of the present disclosure, the location of one or more first-type RUs in the PPDU may be indicated by an RU allocation subfield in an ascending order of the first-type RUs based on the lowest subcarrier of each of the first-type RUs in the frequency domain, where the RU allocation subfield may be included in the PPDU or in a trigger frame that triggers transmission of the PPDU.

[0711] Furthermore, each of the multiple second-type RUs (i.e., RRUs) may be configured with consecutive subcarriers in the frequency domain, and the RU allocation subfields may all be available for allocation of the first-type RUs and the second-type RUs.

[0712] Here, information for indicating whether the RU allocation subfield is used to indicate allocation of a first type RU or a second type RU may be included and transmitted within the PPDU or within a trigger frame for triggering the PPDU.

[0713] Additionally, both type 1 RUs and type 2 RUs may be used within an 80 MHz unit, i.e., both type 1 RUs and type 2 RUs may be allocated within an 80 MHz unit.

[0714] Furthermore, the plurality of first type RUs may include 26-subcarrier first type RUs, 52-subcarrier first type RUs, 106-subcarrier first type RUs, 242-subcarrier first type RUs, and 484-subcarrier first type RUs, and the plurality of second type RUs may include 26-subcarrier second type RUs, 52-subcarrier second type RUs, 106-subcarrier second type RUs, 242-subcarrier second type RUs, and 484-subcarrier second type RUs.

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

[0716] Also, according to embodiment 1, the multiple second-type RUs may be indexed in ascending order in the frequency domain by size, and the multiple first-type RUs may be indexed in ascending order of the lowest subcarrier of each of the multiple first-type RUs by size in the frequency domain. In this case, a mapping relationship between the indexes of the first-type RUs and the indexes of the second-type RUs may be determined so that the subcarriers of multiple relatively small first-type RUs included in a single relatively large first-type RU are spaced as far apart as possible. In this case, the value of the RU Allocation subfield for allocating the second-type RUs may be used in the same way for allocating the first-type RUs. Furthermore, based on the mapping relationship between the indexes of the first-type RUs and the indexes of the second-type RUs, the indexes of the one or more first-type RUs in the PPDU may be indicated by the value of the RU Allocation subfield.

[0717] Also, according to embodiment 2, the multiple second-type RUs may be indexed in ascending order in the frequency domain by size, and the multiple first-type RUs may be indexed such that the indexes of the first-type RUs are indicated in the same way as the indexes of the second-type RUs are indicated by the value of the RU allocation subfield. That is, the multiple first-type RUs do not need to be indexed in ascending order in the frequency domain. In this case, the subcarrier positions for the indexes of the multiple first-type RUs may be determined so that the subcarriers of multiple relatively small first-type RUs included in a single relatively large first-type RU are spaced as far apart as possible.

[0718] Also, according to embodiment 3, the plurality of first-type RUs may be indexed according to a predetermined rule. In this case, the value of the RU Allocation subfield for allocating the second-type RUs may be used in the same manner for allocating the first-type RUs. Based on a mapping relationship between the index of the first-type RU and the index of the second-type RU, the index of the one or more first-type RUs in the PPDU may be indicated by the value of the RU Allocation subfield.

[0719] The transmitting device (ie, the first STA) transmits a PPDU to the receiving device (ie, the second STA) within the 80 MHz frequency bandwidth (S1302).

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

[0721] The method described in the example of Figure 13 may be performed by the first device 200 of Figure 1. For example, the one or more processors 202 of the first device 200 of Figure 1 may be configured to generate a PPDU and transmit the PPDU via the transceiver 106. Note that the one or more memories 204 of the first device 200 may store instructions for performing the method described in the example of Figure 13 or the above examples when executed by the one or more processors 202.

[0722] FIG. 14 illustrates an operation of a receiving device for a PPDU transmission and reception method according to an embodiment of the present disclosure.

[0723] Fig. 14 illustrates an example of the operation of a receiving device based on the above-described proposed method. The illustration in Fig. 14 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in Fig. 14 may be omitted depending on the situation and / or setting.

[0724] Referring to FIG. 14, the receiving device receives a PPDU within an 80 MHz frequency bandwidth (S1401).

[0725] Here, the PPDU transmitting device may be an AP or a non-AP STA, and the PPDU receiving device may be an AP or a non-AP STA. For convenience of description, the transmitting device may be referred to as a first STA, and the receiving device may be referred to as a second STA.

[0726] Here, the receiving device (i.e., the second STA) may receive all or part of the PPDU in step S1401. For the operation of step S1401, the receiving device (i.e., the second STA) may perform an operation to restore the results of the CSD, spatial mapping, IDFT / IFFT operations, and GI insertion operations applied by the transmitting device (e.g., applied in the above step S1302).

[0727] The receiving device (ie, the second STA) processes the PPDU (S1402).

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

[0729] More specifically, the receiving device can decode the x-SIG field of the PPDU based on the legacy STF / LTF to obtain information included in the x-SIG field. For example, information about various tone plans (i.e., RUs) proposed in the present disclosure may be included in the x-SIG field, and the receiving STA can obtain information about the tone plan (i.e., RU) from the x-SIG field.

[0730] The receiving device (i.e., the second STA) can then decode the remaining portion of the PPDU based on the acquired information about the tone plan (i.e., the RU). For example, the receiving device (i.e., the second STA) can decode the STF / LTF field of the PPDU based on the information about the tone plan (i.e., the RU). The receiving device (i.e., the second STA) can also decode the data field of the PPDU based on the information about the tone plan (i.e., the RU) to obtain the MPDU included in the data field.

[0731] The receiving device (i.e., the second STA) may also perform a processing operation of transmitting the decoded data to an upper layer (e.g., MAC layer) and may perform subsequent operations when the upper layer instructs the PHY layer to generate a signal corresponding to the data transmitted to the upper layer.

[0732] According to an embodiment of the present disclosure, multiple Type 1 RUs (i.e., DRUs) within an 80 MHz frequency bandwidth may be configured with usable subcarriers. Here, the usable subcarriers may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers. The usable subcarriers may vary depending on the size of the RU. For example, a 26-subcarrier Type 1 RU, a 52-subcarrier Type 1 RU, and / or a 106-subcarrier Type 1 RU may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see FIG. 11 and Table 11). As another example, a 242-subcarrier Type 1 RU and / or a 484-subcarrier Type 1 RU may be configured with subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and one or more null subcarriers (see FIG. 11 and Table 11). As another example, a 996-subcarrier type 1 RU may be composed of subcarriers excluding one or more DC subcarriers and one or more guard subcarriers (see FIG. 11 and Table 11). Each of the multiple type 1 RUs may be composed of (or positioned at) non-contiguous subcarriers at predetermined intervals (e.g., 36 subcarrier intervals for a 26-subcarrier RU) in the frequency domain (i.e., at uniform intervals). That is, the multiple type 1 RUs may be defined according to Schemes 1 and 2 described above.

[0733] According to an embodiment of the present disclosure, the location of one or more first-type RUs in the PPDU may be indicated by an RU allocation subfield in an ascending order of the first-type RUs based on the lowest subcarrier of each of the first-type RUs in the frequency domain, where the RU allocation subfield may be included in the PPDU or in a trigger frame that triggers transmission of the PPDU.

[0734] Furthermore, each of the multiple second-type RUs (i.e., RRUs) may be configured with consecutive subcarriers in the frequency domain, and the RU allocation subfields may all be available for allocation of the first-type RUs and the second-type RUs.

[0735] Here, information for indicating whether the RU allocation subfield is used to indicate allocation of a first type RU or a second type RU may be included and transmitted within the PPDU or within a trigger frame for triggering the PPDU.

[0736] Additionally, both type 1 RUs and type 2 RUs may be used within an 80 MHz unit, i.e., both type 1 RUs and type 2 RUs may be allocated within an 80 MHz unit.

[0737] Furthermore, the plurality of first type RUs may include a 26-subcarrier first type RU, a 52-subcarrier first type RU, a 106-subcarrier first type RU, a 242-subcarrier first type RU, and a 484-subcarrier first type RU, and the plurality of second type RUs may include a 26-subcarrier second type RU, a 52-subcarrier second type RU, a 106-subcarrier second type RU, a 242-subcarrier second type RU, and a 484-subcarrier second type RU.

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

[0739] Also, according to embodiment 1, the multiple second-type RUs may be indexed in ascending order in the frequency domain by size, and the multiple first-type RUs may be indexed in ascending order of the lowest subcarrier of each of the multiple first-type RUs by size in the frequency domain. In this case, a mapping relationship between the indexes of the first-type RUs and the indexes of the second-type RUs may be determined so that the subcarriers of multiple relatively small first-type RUs included in a single relatively large first-type RU are spaced as far apart as possible. In this case, the value of the RU Allocation subfield for allocating the second-type RUs may be used in the same way for allocating the first-type RUs. Furthermore, based on the mapping relationship between the indexes of the first-type RUs and the indexes of the second-type RUs, the indexes of the one or more first-type RUs in the PPDU may be indicated by the value of the RU Allocation subfield.

[0740] Also, according to embodiment 2, the multiple second-type RUs may be indexed in ascending order in the frequency domain by size, and the multiple first-type RUs may be indexed such that the indexes of the first-type RUs are indicated in the same way as the indexes of the second-type RUs are indicated by the value of the RU allocation subfield. That is, the multiple first-type RUs do not need to be indexed in ascending order in the frequency domain. In this case, the subcarrier positions for the indexes of the multiple first-type RUs may be determined so that the subcarriers of multiple relatively small first-type RUs included in a single relatively large first-type RU are spaced as far apart as possible.

[0741] Also, according to embodiment 3, the plurality of first-type RUs may be indexed according to a predetermined rule. In this case, the value of the RU Allocation subfield for allocating the second-type RUs may be used in the same manner for allocating the first-type RUs. Based on a mapping relationship between the index of the first-type RU and the index of the second-type RU, the index of the one or more first-type RUs in the PPDU may be indicated by the value of the RU Allocation subfield.

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

[0743] In existing WLAN systems, RUs (i.e., RRUs) allocated to each STA for OFDMA transmission are configured with only contiguous subcarriers in the frequency domain. However, in the exemplary embodiment of the present disclosure, RUs (i.e., DRUs) configured with discontinuous subcarriers may be allocated for OFDMA transmission. By allocating RUs configured with discontinuous subcarriers, transmission power can be increased, thereby achieving the effect of improving wireless communication efficiency. Furthermore, the existing RU allocation subfield may also be used for DRU allocation. This eliminates the need to define a new field for RU allocation and the need for additional signaling, thereby reducing signaling overhead.

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

[0745] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0746] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, as well as non-transitory computer-readable media on which such software or instructions are stored and executable on a device or computer. Instructions usable for programming a processing system to perform features described in this disclosure may be stored on or in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in this disclosure. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. The memory, or alternatively, a non-volatile memory device within the memory, comprises a non-transitory computer-readable storage medium. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0747] [Industrial Applicability] The method proposed in this disclosure has been described mainly as being applied to an IEEE 802.11-based system, but it can also be applied to various wireless LANs or wireless communication systems other than the IEEE 802.11-based system.

[0748] [Claims at the time of international application] [Claim 1] A method performed by a first station (STA) in a wireless LAN system, comprising: generating a physical protocol data unit (PPDU) to be transmitted within an 80 MHz frequency bandwidth; and transmitting the PPDU to a second STA; a plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with non-contiguous subcarriers at a predetermined interval in the frequency domain; A method in which the location of one or more first-type RUs of the PPDU is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on the lowest subcarrier of each of the plurality of first-type RUs in the frequency domain. [Claim 2] each of the plurality of second-type RUs is configured with contiguous subcarriers in the frequency domain; The method of claim 1 , wherein the RU allocation subfields are all available for allocation of first-type RUs and second-type RUs. [Claim 3] the plurality of first-type RUs include a 26-subcarrier first-type RU, a 52-subcarrier first-type RU, a 106-subcarrier first-type RU, a 242-subcarrier first-type RU, and a 484-subcarrier first-type RU; 3. The method of claim 2, wherein the plurality of second-type RUs include a 26-subcarrier second-type RU, a 52-subcarrier second-type RU, a 106-subcarrier second-type RU, a 242-subcarrier second-type RU, and a 484-subcarrier second-type RU. [Claim 4] 4. The method of claim 3, wherein each relatively large first-type RU in the frequency domain is configured to include a plurality of different relatively small first-type RUs. [Claim 5] a value for the RU assignment subfield for the assignment of the second type RU is used in the same way as for the assignment of the first type RU; The method of claim 4, wherein the value of the RU assignment subfield indicates an index for the one or more first-type RUs of the PPDU based on a mapping relationship between an index of a first-type RU and an index of a second-type RU. [Claim 6] The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26-subcarrier RU mapping, the following 52-subcarrier RU mapping, the following 106-subcarrier RU mapping, the following 242-subcarrier RU mapping, and the following 484-subcarrier RU mapping: [26 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 19, First type RU-index 3: Second type RU-index 10, First type RU-index 4: Second type RU-index 28, 1st type RU-index 5: 2nd type RU-index 5, 1st type RU-index 6: 2nd type RU-index 6, First type RU-index 7: Second type RU-index 24, First type RU-index 8: Second type RU-index 15, First type RU-index 9: Second type RU-index 33, First type RU-index 10: Second type RU-index 3, First type RU-index 11: Second type RU-index 21, First type RU-index 12: Second type RU-index 12, First type RU-index 13: Second type RU-index 30, First type RU-index 14: Second type RU-index 23, First type RU-index 15: Second type RU-index 8, First type RU-index 16: Second type RU-index 26, 1st type RU-index 17: 2nd type RU-index 17, First type RU-index 18: Second type RU-index 35, First type RU-index 19: Second type RU-index 2, First type RU-index 20: Second type RU-index 20, First type RU-index 21: Second type RU-index 11, First type RU-index 22: Second type RU-index 29, First type RU-index 23: Second type RU-index 14, First type RU-index 24: Second type RU-index 7, First type RU-index 25: Second type RU-index 25, First type RU-index 26: Second type RU-index 16, First type RU-index 27: Second type RU-index 34, 1st type RU-index 28: 2nd type RU-index 4, First type RU-index 29: Second type RU-index 22, First type RU-index 30: Second type RU-index 13, First type RU-index 31: Second type RU-index 31, First type RU-index 32: Second type RU-index 32, First type RU-index 33: Second type RU-index 9, First type RU-index 34: Second type RU-index 27, First type RU-index 35: Second type RU-index 18, 1st type RU-index 36: 2nd type RU-index 36 [52 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 9, First type RU-index 3: Second type RU-index 5, First type RU-index 4: Second type RU-index 13, First type RU-index 5: Second type RU-index 3, First type RU-index 6: Second type RU-index 11, 1st type RU-index 7: 2nd type RU-index 7, First type RU-index 8: Second type RU-index 15, 1st type RU-index 9: 2nd type RU-index 2, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 6, First type RU-index 12: Second type RU-index 14, 1st type RU-index 13: 2nd type RU-index 4, First type RU-index 14: Second type RU-index 12, First type RU-index 15: Second type RU-index 8, 1st type RU-index 16: 2nd type RU-index 16 [106 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 5, 1st type RU-index 3: 2nd type RU-index 3, First type RU-index 4: Second type RU-index 7, First type RU-index 5: Second type RU-index 2, 1st type RU-index 6: 2nd type RU-index 6, 1st type RU-index 7: 2nd type RU-index 4, 1st type RU-index 8: 2nd type RU-index 8 [242 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 3, First type RU-index 3: Second type RU-index 2, 1st type RU-index 4: 2nd type RU-index 4 [484 subcarrier RU mapping] 1st type RU-index 1: 1st type RU-index 1, 1st type RU-index 2: 1st type RU-index 2 The method of claim 5 , wherein the “:” denotes a mapping. [Claim 7] the plurality of second-type RUs are indexed in ascending order in the frequency domain by size; the plurality of first-type RUs are indexed in the frequency domain by size in ascending order of the lowest subcarrier of each of the plurality of first-type RUs; The method of claim 5, wherein the mapping relationship between the indexes of the first type RUs and the indexes of the second type RUs is determined so that the subcarriers of multiple different, relatively small first type RUs included in a single, relatively large first type RU are spaced as far apart as possible. [Claim 8] The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26-subcarrier RU mapping, the following 52-subcarrier RU mapping, the following 106-subcarrier RU mapping, the following 242-subcarrier RU mapping, and the following 484-subcarrier RU mapping: [26 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2, 1st type RU-index 3: 2nd type RU-index 3, 1st type RU-index 4: 2nd type RU-index 4, 1st type RU-index 5: 2nd type RU-index 5, 1st type RU-index 6: 2nd type RU-index 6, 1st type RU-index 7: 2nd type RU-index 7, 1st type RU-index 8: 2nd type RU-index 8, 1st type RU-index 9: 2nd type RU-index 9, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 11, First type RU-index 12: Second type RU-index 12, 1st type RU-index 13: 2nd type RU-index 13, First type RU-index 14: Second type RU-index 14, First type RU-index 15: Second type RU-index 15, First type RU-index 16: Second type RU-index 16, 1st type RU-index 17: 2nd type RU-index 17, First type RU-index 18: Second type RU-index 18, 1st type RU-index 19: 2nd type RU-index 19, First type RU-index 20: Second type RU-index 20, First type RU-index 21: Second type RU-index 21, First type RU-index 22: Second type RU-index 22, First type RU-index 23: Second type RU-index 23, First type RU-index 24: Second type RU-index 24, First type RU-index 25: Second type RU-index 25, First type RU-index 26: Second type RU-index 26, First type RU-index 27: Second type RU-index 27, First type RU-index 28: Second type RU-index 28, First type RU-index 29: Second type RU-index 29, First type RU-index 30: Second type RU-index 30, First type RU-index 31: Second type RU-index 31, First type RU-index 32: Second type RU-index 32, First type RU-index 33: Second type RU-index 33, First type RU-index 34: Second type RU-index 34, First type RU-index 35: Second type RU-index 35, 1st type RU-index 36: 2nd type RU-index 36 [52 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2, 1st type RU-index 3: 2nd type RU-index 3, 1st type RU-index 4: 2nd type RU-index 4, 1st type RU-index 5: 2nd type RU-index 5, 1st type RU-index 6: 2nd type RU-index 6, 1st type RU-index 7: 2nd type RU-index 7, 1st type RU-index 8: 2nd type RU-index 8, 1st type RU-index 9: 2nd type RU-index 9, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 11, First type RU-index 12: Second type RU-index 12, 1st type RU-index 13: 2nd type RU-index 13, First type RU-index 14: Second type RU-index 14, First type RU-index 15: Second type RU-index 15, 1st type RU-index 16: 2nd type RU-index 16 [106 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2, 1st type RU-index 3: 2nd type RU-index 3, 1st type RU-index 4: 2nd type RU-index 4, 1st type RU-index 5: 2nd type RU-index 5, 1st type RU-index 6: 2nd type RU-index 6, 1st type RU-index 7: 2nd type RU-index 7, 1st type RU-index 8: 2nd type RU-index 8 [242 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2, 1st type RU-index 3: 2nd type RU-index 3, 1st type RU-index 4: 2nd type RU-index 4; [484 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2 The method of claim 5 , wherein the “:” denotes a mapping. [Claim 9] the plurality of second-type RUs are indexed in ascending order in the frequency domain by size; The plurality of first-type RUs are indexed such that an index for the first-type RU is indicated in the same manner as an index for the second-type RU is indicated by a value for the RU assignment subfield; 6. The method of claim 5, wherein the subcarrier positions for the indexes of the plurality of first-type RUs are determined so that the subcarriers of the plurality of different, relatively small, first-type RUs contained in a single, relatively large first-type RU are spaced as far apart as possible. [Claim 10] The method of claim 1 , wherein the RU allocation subfield is included in the PPDU or in a trigger frame that triggers transmission of the PPDU. [Claim 11] A first station (STA) device in a wireless LAN system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: Generates PPDUs (physical protocol data units) transmitted within an 80 MHz frequency bandwidth; transmit the PPDU to a second STA; a plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with non-contiguous subcarriers at a predetermined interval in the frequency domain; The apparatus, wherein a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs relative to a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain. [Claim 12] 1. A method performed by a second station (STA) in a wireless LAN system, comprising: receiving a physical protocol data unit (PPDU) within an 80 MHz frequency bandwidth from a first STA; and processing the PPDU; a plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with non-contiguous subcarriers at a predetermined interval in the frequency domain; A method in which the location of one or more first-type RUs of the PPDU is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on the lowest subcarrier of each of the plurality of first-type RUs in the frequency domain. [Claim 13] A second station (STA) device in a wireless LAN system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: Receive a PPDU (physical protocol data unit) from the first STA within the 80 MHz frequency bandwidth; configured to process the PPDU; a plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with non-contiguous subcarriers at a predetermined interval in the frequency domain; The apparatus, wherein a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs relative to a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain. [Claim 14] 1. A processing device configured to control a station (STA) in a wireless LAN system, comprising: one or more processors; A processing device comprising: one or more computer memories operably coupled to the one or more processors and storing instructions that, when executed by the one or more processors, perform the method of any one of claims 1 to 10. [Claim 15] one or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, the one or more instructions being executed by one or more processors to control a device in a wireless LAN system to perform the method of any one of claims 1 to 10.

Claims

1. A method performed by a first station (STA) in a wireless LAN system, comprising: generating a physical protocol data unit (PPDU) to be transmitted within an 80 MHz frequency bandwidth; and transmitting the PPDU to a second STA; A plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with discontinuous subcarriers at predetermined intervals in the frequency domain; A method in which a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain.

2. each of the plurality of second-type RUs is configured with consecutive subcarriers in the frequency domain; The method of claim 1 , wherein the RU allocation subfields are all available for allocation of first-type RUs and second-type RUs.

3. the plurality of first type RUs include a 26 subcarrier first type RU, a 52 subcarrier first type RU, a 106 subcarrier first type RU, a 242 subcarrier first type RU, and a 484 subcarrier first type RU; 3. The method of claim 2, wherein the plurality of second-type RUs include a 26-subcarrier second-type RU, a 52-subcarrier second-type RU, a 106-subcarrier second-type RU, a 242-subcarrier second-type RU, and a 484-subcarrier second-type RU.

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

5. a value for the RU allocation subfield for allocation of the second-type RU is used the same as for allocation of the first-type RU; 5. The method of claim 4, wherein the value of the RU assignment subfield indicates an index for the one or more first-type RUs of the PPDU based on a mapping relationship between an index of a first-type RU and an index of a second-type RU.

6. The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mapping, the following 52 subcarrier RU mapping, the following 106 subcarrier RU mapping, the following 242 subcarrier RU mapping, and the following 484 subcarrier RU mapping: [26 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 19, First type RU-index 3: Second type RU-index 10, First type RU-index 4: Second type RU-index 28, First type RU-index 5: Second type RU-index 5, First type RU-index 6: Second type RU-index 6, First type RU-index 7: Second type RU-index 24, First type RU-index 8: Second type RU-index 15, First type RU-index 9: Second type RU-index 33, First type RU-index 10: Second type RU-index 3, First type RU-index 11: Second type RU-index 21, First type RU-index 12: Second type RU-index 12, First type RU-index 13: Second type RU-index 30, First type RU-index 14: Second type RU-index 23, First type RU-index 15: Second type RU-index 8, First type RU-index 16: Second type RU-index 26, First type RU-index 17: Second type RU-index 17, First type RU-index 18: Second type RU-index 35, First type RU-index 19: Second type RU-index 2, First type RU-index 20: Second type RU-index 20, First type RU-index 21: Second type RU-index 11, First type RU-index 22: Second type RU-index 29, First type RU-index 23: Second type RU-index 14, First type RU-index 24: Second type RU-index 7, First type RU-index 25: Second type RU-index 25, First type RU-index 26: Second type RU-index 16, First type RU-index 27: Second type RU-index 34, First type RU-index 28: Second type RU-index 4, First type RU-index 29: Second type RU-index 22, First type RU-index 30: Second type RU-index 13, First type RU-index 31: Second type RU-index 31, First type RU-index 32: Second type RU-index 32, First type RU-index 33: Second type RU-index 9, First type RU-index 34: Second type RU-index 27, First type RU-index 35: Second type RU-index 18, First type RU-index 36: Second type RU-index 36; [52 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 9, First type RU-index 3: Second type RU-index 5, First type RU-index 4: Second type RU-index 13, First type RU-index 5: Second type RU-index 3, First type RU-index 6: Second type RU-index 11, First type RU-index 7: Second type RU-index 7, First type RU-index 8: Second type RU-index 15, First type RU-index 9: Second type RU-index 2, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 6, First type RU-index 12: Second type RU-index 14, First type RU-index 13: Second type RU-index 4, First type RU-index 14: Second type RU-index 12, First type RU-index 15: Second type RU-index 8, First type RU-index 16: Second type RU-index 16; [106 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 5, First type RU-index 3: Second type RU-index 3, First type RU-index 4: Second type RU-index 7, First type RU-index 5: Second type RU-index 2, First type RU-index 6: Second type RU-index 6, First type RU-index 7: Second type RU-index 4, First type RU-index 8: Second type RU-index 8; [242 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 3, First type RU-index 3: Second type RU-index 2, First type RU-index 4: Second type RU-index 4; [484 subcarrier RU mapping] 1st type RU-index 1: 1st type RU-index 1, 1st type RU-index 2: 1st type RU-index 2; The method of claim 5 , wherein the “:” denotes a mapping.

7. the plurality of second-type RUs are indexed in ascending order in the frequency domain by size; the plurality of first-type RUs are indexed in ascending order of their respective least significant subcarriers in the frequency domain by size; 6. The method of claim 5, wherein the mapping relationship between the index of the first type RU and the index of the second type RU is determined so that the intervals between the subcarriers of a plurality of relatively small first type RUs that are different from each other and included in a single relatively large first type RU are as far apart as possible.

8. The mapping relationship between the index of the first type RU and the index of the second type RU is determined by the following 26 subcarrier RU mapping, the following 52 subcarrier RU mapping, the following 106 subcarrier RU mapping, the following 242 subcarrier RU mapping, and the following 484 subcarrier RU mapping: [26 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 2, First type RU-index 3: Second type RU-index 3, First type RU-index 4: Second type RU-index 4, First type RU-index 5: Second type RU-index 5, First type RU-index 6: Second type RU-index 6, First type RU-index 7: Second type RU-index 7, First type RU-index 8: Second type RU-index 8, First type RU-index 9: Second type RU-index 9, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 11, First type RU-index 12: Second type RU-index 12, First type RU-index 13: Second type RU-index 13, First type RU-index 14: Second type RU-index 14, First type RU-index 15: Second type RU-index 15, First type RU-index 16: Second type RU-index 16, First type RU-index 17: Second type RU-index 17, First type RU-index 18: Second type RU-index 18, First type RU-index 19: Second type RU-index 19, First type RU-index 20: Second type RU-index 20, First type RU-index 21: Second type RU-index 21, First type RU-index 22: Second type RU-index 22, First type RU-index 23: Second type RU-index 23, First type RU-index 24: Second type RU-index 24, First type RU-index 25: Second type RU-index 25, First type RU-index 26: Second type RU-index 26, First type RU-index 27: Second type RU-index 27, First type RU-index 28: Second type RU-index 28, First type RU-index 29: Second type RU-index 29, First type RU-index 30: Second type RU-index 30, First type RU-index 31: Second type RU-index 31, First type RU-index 32: Second type RU-index 32, First type RU-index 33: Second type RU-index 33, First type RU-index 34: Second type RU-index 34, First type RU-index 35: Second type RU-index 35, First type RU-index 36: Second type RU-index 36; [52 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 2, First type RU-index 3: Second type RU-index 3, First type RU-index 4: Second type RU-index 4, First type RU-index 5: Second type RU-index 5, First type RU-index 6: Second type RU-index 6, First type RU-index 7: Second type RU-index 7, First type RU-index 8: Second type RU-index 8, First type RU-index 9: Second type RU-index 9, First type RU-index 10: Second type RU-index 10, First type RU-index 11: Second type RU-index 11, First type RU-index 12: Second type RU-index 12, First type RU-index 13: Second type RU-index 13, First type RU-index 14: Second type RU-index 14, First type RU-index 15: Second type RU-index 15, First type RU-index 16: Second type RU-index 16; [106 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 2, First type RU-index 3: Second type RU-index 3, First type RU-index 4: Second type RU-index 4, First type RU-index 5: Second type RU-index 5, First type RU-index 6: Second type RU-index 6, First type RU-index 7: Second type RU-index 7, First type RU-index 8: Second type RU-index 8; [242 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, First type RU-index 2: Second type RU-index 2, First type RU-index 3: Second type RU-index 3, First type RU-index 4: Second type RU-index 4; [484 subcarrier RU mapping] First type RU-index 1: Second type RU-index 1, 1st type RU-index 2: 2nd type RU-index 2; The method of claim 5 , wherein the “:” denotes a mapping.

9. the plurality of second-type RUs are indexed in ascending order in the frequency domain by size; The plurality of first-type RUs are indexed such that an index for the first-type RU is indicated in the same manner as an index for the second-type RU is indicated by a value for the RU assignment subfield; 6. The method of claim 5, wherein the subcarrier positions for the indexes of the plurality of first-type RUs are determined so that the subcarriers of the plurality of relatively small first-type RUs that are different from each other and included in a single relatively large first-type RU are spaced as far apart as possible.

10. The method of claim 1 , wherein the RU allocation subfield is included in the PPDU or in a trigger frame that triggers transmission of the PPDU.

11. A first station (STA) device in a wireless LAN system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: generating a physical protocol data unit (PPDU) to be transmitted within an 80 MHz frequency bandwidth; transmit the PPDU to a second STA; A plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with discontinuous subcarriers at predetermined intervals in the frequency domain; The apparatus, wherein a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain.

12. A method performed by a second station (STA) in a wireless LAN system, comprising: receiving a physical protocol data unit (PPDU) within an 80 MHz frequency bandwidth from a first STA; and processing the PPDU; A plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with discontinuous subcarriers at predetermined intervals in the frequency domain; A method in which a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain.

13. A second station (STA) device in a wireless LAN system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving a physical protocol data unit (PPDU) within an 80 MHz frequency bandwidth from the first STA; process the PPDU; A plurality of first-type resource units (RUs) within the 80 MHz frequency bandwidth are composed of subcarriers excluding one or more DC subcarriers, one or more guard subcarriers, and / or one or more null subcarriers; each of the plurality of first-type RUs is configured with discontinuous subcarriers at predetermined intervals in the frequency domain; The apparatus, wherein a position of the PPDU for one or more first-type RUs is indicated by an RU assignment subfield in an ascending order of the plurality of first-type RUs based on a lowest subcarrier of each of the plurality of first-type RUs in the frequency domain.

14. 1. A processing device configured to control a station (STA) in a wireless LAN system, comprising: one or more processors; and one or more computer memories operably coupled to the one or more processors and storing instructions that, when executed by the one or more processors, perform the method of any one of claims 1 to 10.

15. one or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more instructions are executed by one or more processors to control devices in a wireless LAN system to perform the method of any one of claims 1 to 10.

Images