Method and apparatus for allocating resource units in a wireless LAN system

Abstract

A method and apparatus for allocating resource units in a wireless LAN system are disclosed. The method performed by a station (STA) in a wireless LAN system according to an embodiment of the present disclosure may include receiving a PPDU including a SIG field for resource unit allocation related information from another STA, and obtaining a data field in the PPDU based on the resource unit allocation related information. Here, the resource unit allocation related information may be constructed based on one or more multiple RU (MRU) candidates for a bandwidth exceeding 320 MHz.

Description

Technical Field

[0001] The present disclosure relates to a transmission or reception method and apparatus based on allocation of resource units in a wireless local area network (WLAN) system.

Background Art

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

[0003] To provide a more improved wireless communication environment, improvement technologies for EHT (Extremely High Throughput) are being discussed. For example, technologies for increased bandwidth, efficient utilization of multiple bands, MIMO (Multiple Input Multiple Output) that supports increased spatial streams, technologies for multi-access point (AP) coordination are being studied, and in particular, various technologies for supporting traffic with low latency or real-time characteristics are being studied. Furthermore, new technologies for supporting ultra-high reliability (UHR), including improvements or extensions of EHT technology, are being discussed.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The technical problem addressed by this disclosure is to provide a method and apparatus for allocating resource units in a wireless LAN system.

[0005] A further technical challenge of this disclosure is to provide a method and apparatus for performing uplink / downlink transmission and reception in a wireless LAN system by defining and applying resource units / multiplex resource units that take into account wider bandwidth.

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

[0007] A method performed by a station (STA) in a wireless LAN system according to one aspect of this disclosure may include the steps of: receiving a PPDU (physical layer protocol data unit) from another STA that includes a SIG field for resource unit allocation-related information; and acquiring a data field within the PPDU based on the resource unit allocation-related information. Here, the resource unit allocation-related information can indicate a specific candidate within a set that includes a predefined number of multiple RU (MRU) candidates for bandwidths exceeding 320 MHz.

[0008] A method performed by a station (STA) in a wireless LAN system according to a further aspect of this disclosure may include the steps of: configuring a SIG field for resource unit allocation-related information; and transmitting a PPDU (physical layer protocol data unit) containing the SIG field to another STA. Here, the resource unit allocation-related information can indicate a specific candidate within a set of a predefined number of multiple RU (MRU) candidates for bandwidths exceeding 320 MHz. [Effects of the Invention]

[0009] This disclosure provides a method and apparatus for allocating resource units in a wireless LAN system.

[0010] According to this disclosure, a method and apparatus for performing uplink / downlink transmission and reception in a wireless LAN system can be provided by defining and applying resource units / multiplex resource units that take into account wider bandwidth.

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

[0012] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples of the disclosure and illustrate the technical features of the disclosure together with the detailed description.

[0013] [Figure 1] This is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure. [Figure 2] This figure shows an exemplary structure of a wireless LAN system to which this disclosure can be applied. [Figure 3]This diagram illustrates the link setup process to which this disclosure applies. [Figure 4] This diagram illustrates the backoff process to which this disclosure applies. [Figure 5] This diagram illustrates the CSMA / CA baseframe transmission operation to which this disclosure can be applied. [Figure 6] This figure illustrates an example of a frame structure used in a wireless LAN system to which this disclosure can be applied. [Figure 7] This figure shows an example of a PPDU as defined in the IEEE 802.11 standard to which this disclosure applies. [Figure 8] This figure illustrates an example of a resource unit in a wireless LAN system to which this disclosure can be applied. [Figure 9] This figure illustrates an example of a resource unit in a wireless LAN system to which this disclosure can be applied. [Figure 10] This figure illustrates an example of a resource unit in a wireless LAN system to which this disclosure can be applied. [Figure 11] This figure shows an exemplary structure of the HE-SIG-B field. [Figure 12] This diagram illustrates the MU-MIMO scheme, where multiple users / STAs are assigned to a single RU. [Figure 13] This figure shows examples of PPDU formats to which this disclosure can be applied. [Figure 14] This figure shows an exemplary format of a trigger frame to which this disclosure can be applied. [Figure 15] This figure shows an example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure. [Figure 16] This figure shows another example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure. [Figure 17] This figure shows yet another example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure. [Figure 18]A diagram showing yet another example of the MRU pattern in the 640 MHz bandwidth according to an embodiment of the present disclosure. [Figure 19] A diagram showing an example of the MRU pattern in the 480 MHz bandwidth according to an embodiment of the present disclosure. [Figure 20] A diagram showing another example of the MRU pattern in the 480 MHz bandwidth according to an embodiment of the present disclosure. [Figure 21] A flowchart for explaining an exemplary operation based on the resource allocation of a STA according to an embodiment of the present disclosure. [Figure 22] A flowchart for explaining another exemplary operation based on the resource allocation of a STA according to an embodiment of the present disclosure. **Modes for Carrying Out the Invention**

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

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

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

[0017] In this disclosure, terms such as "first," "second," etc., are used solely to distinguish one component from another, and are not used to limit the components, nor do they limit the order or importance of the components unless specifically mentioned. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

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

[0019] The examples in this disclosure may be applied to a variety of wireless communication systems. For example, the examples in this disclosure may be applied to wireless LAN systems. For example, the examples in this disclosure may be applied to IEEE 802.11a / g / n / ac / ax standard-based wireless LANs. Furthermore, the examples in this disclosure may be applied to newly proposed IEEE 802.11be (or EHT) standard-based wireless LANs. The examples in this disclosure may be applied to IEEE 802.11be release-2 standard-based wireless LANs, which represent further improvements to the IEEE 802.11be release-1 standard. In addition, the examples in this disclosure may be applied to next-generation standard-based wireless LANs following IEEE 802.11be. Moreover, the examples in this disclosure may be applied to cellular wireless communication systems. For example, they may be applied to cellular wireless communication systems based on 3GPP® (3rd Generation Partnership Project) standard LTE (Long Term Evolution) series technologies and 5G NR (New Radio) series technologies.

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

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

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

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

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

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

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

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

[0028] The hardware elements of devices 100,200 will be described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 can embodied one or more layers (e.g., layers with the same functionality, such as PHY and MAC). One or more processors 102,202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate messages, control information, data, or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by the functions, procedures, proposals and / or methods of this disclosure and provide them to one or more transceivers 106,206. One or more processors 102,202 can receive signals (e.g., baseband signals) from one or more transceivers 106,206 and obtain PDUs, SDUs, messages, control information, data, or information by the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams of this disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] If STA3 cannot overhear CTS frames from STA2 but can overhear RTS frames from STA1, STA3 can use the duration information contained in the RTS frames to set the NAV timer for subsequent consecutive frame transmission periods (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear RTS frames from STA1 but can overhear CTS frames from STA2, STA3 can use the duration information contained in the CTS frames to set the NAV timer for subsequent consecutive frame transmission periods (e.g., SIFS + data frame + SIFS + ACK frame). In other words, STA3 can set NAV based on overhearing one or more RTS or CTS frames from at least one of STA1 or STA2. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 will not attempt to access the channel until the NAV timer expires.

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

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

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

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

[0078] A basic PPDU frame may include an STF (Short Training Field), an LTF (Long Training Field), a SIG (SIGNAL) field, and a Data field. The most basic (e.g., non-HT (High Throughput)) PPDU frame format may consist only of an L-STF (Legacy-STF), an L-LTF (Legacy-LTF), a SIG field, and a Data field. Depending on the type of PPDU frame format (e.g., HT-mixed format PPDU, HT-greenfield format PPDU, VHT (Very High Throughput) PPDU, etc.), additional (or other types of) STF, LTF, and SIG fields may be included between the SIG field and the Data field (see Figure 7 below for further details).

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

[0080] The SIG field may include fields such as the RATE field and the LENGTH field. The RATE field may contain information about the modulation and coding rate of the data. The LENGTH field may contain information about the length of the data. Furthermore, the SIG field may include a parity bit, a SIG TAIL bit, and so on.

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

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

[0083] The MAC header includes fields such as Frame Control, Duration / ID, and Address. The Frame Control field may contain control information necessary for transmitting / receiving frames. The Duration / ID field may be set to the time required to transmit the frame. For specific details on the Sequence Control, QoS Control, and HT Control subfields of the MAC header, refer to the IEEE 802.11 standard document.

[0084] The Null Data Packet (NDP) frame format refers to a frame format that does not include data packets. That is, an NDP frame is a frame format that includes the PLCP (Physical Layer Convergence Procedure) header portion (i.e., the STF, LTF, and SIG fields) of a typical PPDU frame format, but omits the remaining portion (i.e., the data fields). NDP frames can also be referred to as short frame formats.

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

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

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

[0088] An example of the VHT PPDU format (IEEE 802.11ac) is that it further includes the VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format.

[0089] An example of the HE PPDU format (IEEE 802.11ax) further includes the RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in addition to the basic PPDU format. Depending on the specific example of the HE PPDU format, some fields may be omitted or their lengths may change. For example, the HE-SIG-B field is included in the HE PPDU format for multiple users (MU), while it is not included in the HE PPDU format for single users (SU). Also, the HE trigger-based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field may be changed to 8us. The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may be changed to 16us.

[0090] Figures 8 to 10 illustrate examples of resource units in a wireless LAN system to which this disclosure can be applied.

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

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

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

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

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

[0096] In the example shown in Figure 8, various sizes of RUs are illustrated, such as 26-RU, 52-RU, 106-RU, and 242-RU, but the specific sizes of such RUs may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) is not limited in this disclosure and is illustrative. Also, in this disclosure, the number of RUs within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...) may differ depending on the size of the RU. The same applies to the example in Figure 8 as to the example in Figure 9 and / or Figure 10 described below, in which the size and / or number of RUs may be changed.

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

[0098] Just as various sizes of RU were used in the example in Figure 8, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may be used in the example in Figure 9. In addition, five DC tones may be inserted at the center frequency, twelve tones may be used as a guard band in the leftmost band of the 40MHz bandwidth, and eleven tones may be used as a guard band in the rightmost band of the 40MHz bandwidth.

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

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

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

[0102] Furthermore, as shown in the same figure, the 996-RU may be used when used for a single user, and in this case, the insertion of five DC tones is common to both the HE PPDU and the EHT PPDU.

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

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

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

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

[0107] For example, when a DL MU PPDU is configured, the STA (e.g., AP) sending the DL MU PPDU can assign a first RU (e.g., 26 / 52 / 106 / 242-RU) to the first STA and a second RU (e.g., 26 / 52 / 106 / 242-RU) to the second STA. That is, the sending STA (e.g., AP) can use the first RU to send the HE-STF, HE-LTF, and Data fields for the first STA within a single MU PPDU, and use the second RU to send the HE-STF, HE-LTF, and Data fields for the second STA.

[0108] Information regarding the RU's placement may be signaled via HE-SIG-B in HE PPDU format.

[0109] Figure 11 shows an exemplary structure of the HE-SIG-B field.

[0110] As shown in the figure, the HE-SIG-B field may include a common field and a user-specific field. When HE-SIG-B compression is applied (for example, in full-bandwidth MU-MIMO transmission), the common field may not be included in HE-SIG-B, and the HE-SIG-B content channel may include only the user-specific field. When HE-SIG-B compression is not applied, the common field may be included in HE-SIG-B.

[0111] Common fields may include information related to RU allocation (e.g., RU assignment, RUs allocated for MU-MIMO, number of MU-MIMO users (STAs), etc.).

[0112] The common field may contain N*8 RU allocation subfields, where N is the number of subfields, and may have values ​​such as N=1 for 20 or 40MHz MU PPDU, N=2 for 80MHz MU PPDU, N=4 for 160MHz or 80+80MHz MU PPDU, and so on. One 8-bit RU allocation subfield can indicate the size (26, 52, 106, etc.) and frequency position (or RU index) of RUs included in the 20MHz band.

[0113] For example, if the value of the 8-bit RU allocation subfield is 00000000, nine 26-RUs are arranged sequentially from left to right in the example shown in Figure 8. If the value is 00000001, seven 26-RUs and one 52-RU are arranged sequentially from left to right. If the value is 00000010, five 26-RUs, one 52-RU, and two 26-RUs are arranged sequentially from left to right.

[0114] As an additional example, if the value of the 8-bit RU allocation subfield is 01000y2y1y0, then one 106-RU and five 26-RUs are arranged sequentially from left to right in the example in Figure 8. In this case, multiple users / STAs may be assigned to the 106-RU using the MU-MIMO method. Specifically, up to eight users / STAs may be assigned to the 106-RU, and the number of users / STAs assigned to the 106-RU is determined based on the 3-bit information (i.e., y2y1y0). For example, if the 3-bit information (y2y1y0) corresponds to a decimal value N, then the number of users / STAs assigned to the 106-RU may be N+1.

[0115] Basically, one user / STA may be assigned to each of multiple RUs, and different users / STAs may be assigned to different RUs. For RUs of a certain size or larger (e.g., 106, 242, 484, 996-tones, ...), multiple users / STAs may be assigned to a single RU, and the MU-MIMO scheme may be applied to such multiple users / STAs.

[0116] The set of user-specific fields contains information about how all users (STAs) of the PPDU decode their payload. User-specific fields may contain zero or more user block fields. A non-final user block field contains two user fields (i.e., information used for decoding in two STAs). A final user block field contains one or two user fields. The number of user fields may be indicated by the RU allocation subfield of HE-SIG-B, by the symbol count of HE-SIG-B, or by the MU-MIMO user field of HE-SIG-A. User-specific fields may be encoded separately or independently of common fields.

[0117] Figure 12 is a diagram illustrating the MU-MIMO scheme in which multiple users / STAs are assigned to a single RU.

[0118] In the example in Figure 12, we assume that the value of the RU allocation subfield is 01000010. This corresponds to the case where y2y1y0 = 010 in 01000y2y1y0. 010 corresponds to 2 in decimal (i.e., N=2), and it can be shown that 3 (=N+1) users are assigned to one RU. In this case, one 106-RU and five 26-RUs may be arranged sequentially from the leftmost to the rightmost of a particular 20MHz band / channel. Three users / STAs may be assigned to the 106-RU in a MU-MIMO manner. As a result, a total of 8 users / STAs are assigned to the 20MHz band / channel, and the user-specific field of HE-SIG-B may contain 8 user fields (i.e., 4 user block fields). The 8 user fields may be assigned to RUs as shown in Figure 12.

[0119] User fields may be constructed based on two formats. User fields for MU-MIMO assignments may be constructed in the first format, and user fields for non-MU-MIMO assignments may be constructed in the second format. Referring to an example in Figure 12, user fields 1 to 3 may be based on the first format, and user fields 4 to 8 may be based on the second format. The first and second formats may contain bit information of the same length (e.g., 21 bits).

[0120] The user fields of the first format (i.e., the format for MU-MIMO assignment) may be configured as follows: For example, of the total 21 bits of a single user field, B0 to B10 may contain the user's identification information (e.g., STA-ID, AID, partial AID, etc.), B11 to B14 may contain spatial configuration information such as the number of spatial streams for the user, B15 to B18 may contain MCS (Modulation and coding scheme) information applied to the Data field of the PPDU, B19 may be defined as a reserved field, and B20 may contain coding type information applied to the Data field of the PPDU (e.g., BCC (binary convolutional coding) or LDPC (low-density parity check)).

[0121] The user field of the second format (i.e., the format for non-MU-MIMO assignments) may be configured as follows: For example, of the 21 bits in a single user field, B0 to B10 may contain the user's identification information (e.g., STA-ID, AID, partial AID, etc.), B11 to B13 may contain spatial stream number (NSTS) information applied to the RU, B14 may contain information indicating whether beamforming is possible (or whether a beamforming steering matrix can be applied), B15 to B18 may contain MCS (Modulation and coding scheme) information applied to the Data field of the PPDU, B19 may contain information indicating whether DCM (dual carrier modulation) can be applied, and B20 may contain coding type information applied to the Data field of the PPDU (e.g., BCC or LDPC).

[0122] The terms MCS, MCS information, MCS index, and MCS field used in this disclosure may be represented by specific index values. For example, MCS information may be represented by index 0 to index 11. MCS information may include information about the star modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and information about the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). Information about the channel coding type (e.g., BCC or LDPC) may be omitted from the MCS information.

[0123] Figure 13 shows examples of PPDU formats to which this disclosure can be applied.

[0124] The PPDU in Figure 13 may be referred to by various names such as EHT PPDU, Transmit PPDU, Receive PPDU, Type 1 or Type N PPDU. For example, the PPDU or EHT PPDU of this disclosure can be referred to by various names such as Transmit PPDU, Receive PPDU, Type 1 or Type N PPDU. Furthermore, the EHT PPU can be used in EHT systems and / or new wireless LAN systems that improve upon EHT systems.

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

[0126] In Figure 13, the EHT TB PPDU omits the EHT-SIG compared to the EHT MU PPDU. An STA that receives a trigger for UL MU transmission (e.g., a trigger frame or TRS) can perform the UL transmission based on the EHT TB PPDU format.

[0127] In the example of the EHT PPDU format shown in Figure 13, L-STF to EHT-LTF correspond to the preamble or physical preamble and may be generated / transmitted / received / acquired / decoded at the physical layer.

[0128] The subcarrier frequency spacing for L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields (collectively referred to as pre-EHT modulated fields) may be set to 312.5 kHz. The subcarrier frequency spacing for EHT-STF, EHT-LTF, Data, and PE fields (collectively referred to as EHT modulated fields) may be set to 78.125 kHz. In other words, the tone / subcarrier index for L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields may be displayed in units of 312.5 kHz, while the tone / subcarrier index for EHT-STF, EHT-LTF, Data, and PE fields may be displayed in units of 78.125 kHz.

[0129] The L-LTF and L-STF in Figure 13 may be configured identically to the corresponding fields of the PPDU described in Figures 6 and 7.

[0130] The L-SIG field in Figure 13 consists of 24 bits and may be used to communicate rate and length information. For example, the L-SIG field 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. For example, the 12-bit Length field may contain information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the Length field may be determined to be a multiple of 3. For example, for HE PPDUs, the value of the Length field may be determined to be a multiple of 3 + 1 or a multiple of 3 + 2.

[0131] For example, a transmitting STA can apply BCC encoding based on half the coding rate to 24 bits of information in the L-SIG field. The transmitting STA can then obtain 48 bits of BCC encoded bits. BPSK modulation may be applied to the 48 bits of encoded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier (e.g., {subcarrier indices -21, -7, +7, +21}) and the DC subcarrier (e.g., {subcarrier index 0}). Consequently, the 48 BPSK symbols may be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can further map the signal {-1, -1, -1, 1} to subcarrier indices {-28, -27, +27, +28}. The signal may be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

[0132] The transmitting STA can generate an RL-SIG that is generated identically to the L-SIG. BPSK modulation is applied to the RL-SIG. Based on the presence of the RL-SIG, the receiving STA can determine that the received PPDU is either an HE PPDU or an EHT PPDU.

[0133] A U-SIG (Universal SIG) may be inserted after the RL-SIG in Figure 13. The U-SIG can be named in various ways, such as first SIG field, first SIG, first type SIG, control signal, control signal field, or first (type) control signal.

[0134] A U-SIG may contain N bits of information, including information to identify the type of EHT PPDU. For example, a U-SIG may consist of two symbols (e.g., two consecutive OFDM symbols). Each symbol for the U-SIG (e.g., an OFDM symbol) may have a duration of 4us, and the U-SIG may have a total duration of 8us. Each symbol of the U-SIG may be used to transmit 26 bits of information. For example, each symbol of the U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.

[0135] In a U-SIG (or U-SIG field), for example, A-bit information (e.g., 52 uncoded bits) may be transmitted. The first symbol of the U-SIG (e.g., U-SIG-1) may transmit the first X bits of the total A-bit information (e.g., 26 uncoded bits), and the second symbol of the U-SIG (e.g., U-SIG-2) may transmit the remaining Y bits of the total A-bit information (e.g., 26 uncoded bits). For example, a transmitting STA can obtain the 26 uncoded bits contained in each U-SIG symbol. The transmitting STA can perform convolution encoding (e.g., BCC encoding) based on a rate of R=1 / 2 to generate 52-coded bits and perform interleaving on the 52-coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52-coded bits to generate 52 BPSK symbols to be assigned to each U-SIG symbol. A single U-SIG symbol may be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers), excluding the pilot tones -21, -7, +7, and +21.

[0136] For example, the A-bit information transmitted by the U-SIG (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 CRC field and tail field may be transmitted in a second symbol of the U-SIG. The CRC field may be generated based on 26 bits assigned to the first symbol of the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be generated based on a conventional CRC calculation algorithm. The tail field may also be used to terminate the trellis of the convolution decoder and may be set to 0, for example.

[0137] The A-bit information transmitted by the U-SIG (or U-SIG field) (e.g., 52 uncoded bits) can be distinguished into version-independent bits and version-dependent bits. For example, the size of the version-independent bits may be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of the U-SIG, or they may be assigned to both the first and second symbols of the U-SIG. For example, the version-independent bits and version-dependent bits may have various names, such as first control bits and second control bits.

[0138] For example, the version-independent bits of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier). For example, the 3-bit PHY version identifier may contain information about the physical layer version (PHY version) of the transmitted and received PPDUs. For example, the first value of the 3-bit PHY version identifier can indicate that the transmitted and received PPDUs are EHT PPDUs. In other words, a transmitting STA can set the 3-bit PHY version identifier to the first value when transmitting an EHT PPDU. In other words, a receiving STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value.

[0139] For example, the version-independent bits of a U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

[0140] For example, the version-independent bits of the U-SIG may include information about the length of the TXOP (transmission opportunity) and information about the BSS color ID.

[0141] For example, if EHT PPDUs are categorized into various types (e.g., EHT PPDUs associated with SU mode, EHT PPDUs associated with MU mode, EHT PPDUs associated with TB mode, EHT PPDUs associated with Extended Range transmission, etc.), information regarding the type of EHT PPDU may be included in version-dependent bits of the U-SIG.

[0142] For example, a U-SIG may include information about: 1) a bandwidth field containing information about bandwidth; 2) a field containing information about the MCS method applied to the EHT-SIG; 3) an indication field containing information about whether or not the DCM method is applied to the EHT-SIG; 4) a field containing information about the number of symbols used for the EHT-SIG; 5) a field containing information about whether or not the EHT-SIG is generated across the entire bandwidth; 6) a field containing information about the type of EHT-LTF / STF; and 7) fields indicating the length of the EHT-LTF and the CP length.

[0143] Preamble puncturing may be applied to the PPDU in Figure 13. Preamble puncturing can mean the transmission of a PPDU in which one or more 20 MHz subchannels within the PPDU bandwidth are not present. Preamble puncturing may be applied to PPDUs transmitted to one or more users. For example, the resolution of preamble puncturing may be 20 MHz for EHT MU PPDUs in OFDMA transmissions with bandwidths greater than 40 MHz and non-OFDMA transmissions with bandwidths of 80 MHz and 160 MHz. That is, in the above case, puncturing of subchannels smaller than 242 tone RU may not be permitted. Also, for EHT MU PPDUs in non-OFDMA transmissions with a bandwidth of 320 MHz, the resolution of preamble puncturing may be 40 MHz. That is, puncturing of subchannels smaller than 484 tone RU in a 320 MHz bandwidth may not be permitted. Furthermore, in EHT MU PPDU, preamble puncturing does not need to be applied to the primary 20MHz channel.

[0144] For example, for an EHT MU PPDU, information regarding preamble puncturing may be included in the U-SIG and / or EHT-SIG. For instance, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding the preamble puncturing applied to the PPDU.

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

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

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

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

[0149] The EHT-SIG may include the technical features of the HE-SIG-B described in Figures 11 and 12. For example, the EHT-SIG may include common fields and user-specific fields, identical to the example in Figure 8. The common fields of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0150] As in the example in Figure 11, the common fields and user-specific fields of the EHT-SIG may be coded separately. One user block field included in the user-specific field contains information for two user fields, but the last user block field included in the user-specific field may contain one or two user fields. That is, one user block field of the EHT-SIG may contain a maximum of two user fields. As in the example in Figure 12, each user field may be related to MU-MIMO assignment or non-MU-MIMO assignment.

[0151] Similar to the example in Figure 11, the common field of the EHT-SIG may include a CRC bit and a Tail bit, the length of the CRC bit may be determined to be 4 bits, and the length of the Tail bit may be determined to be 6 bits and set to 000000.

[0152] As in the example shown in Figure 11, the common fields of the EHT-SIG may include RU allocation information. RU allocation information can represent information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are assigned. RU allocation information may consist of 9-bit (or N-bit) units.

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

[0154] The EHT-SIG may be constructed based on various MCS techniques. As mentioned above, information related to the MCS technique applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be constructed based on the DCM technique. The DCM technique provides an effect similar to frequency diversity by reusing the same signal on two subcarriers, thereby reducing interference and improving coverage. For example, modulation symbols with the same modulation technique applied may be repeatedly mapped on available tones / subcarriers. For example, of the N data tones allocated for the EHT-SIG (e.g., 52 data tones), the first half of the tones (e.g., tones 1-26) may be mapped to modulation symbols with a specific modulation technique applied (e.g., BPSK modulation symbols), and the remaining half of the tones (e.g., tones 27-52) may also be mapped to modulation symbols with the same specific modulation technique applied (e.g., BPSK modulation symbols). In other words, the modulation symbol mapped to the first tone and the modulation symbol mapped to the 27th tone are the same. As mentioned above, information related to whether or not the DCM method is applied to the EHT-SIG (e.g., a 1-bit field) may be included in the U-SIG. The EHT-STF in Figure 13 may be used to improve automatic gain control (AGC) estimation in a MIMO or OFDMA environment. The EHT-LTF in Figure 13 may be used to estimate the channel in a MIMO or OFDMA environment.

[0155] Information regarding the types of STFs and / or LTFs (including information regarding the GI (guard interval) applied to the LTF) may be included in the U-SIG field and / or EHT-SIG field in Figure 13, etc.

[0156] The PPDU in Figure 13 (i.e., the EHT PPDU) may be configured based on the example RU configurations in Figures 8 to 10.

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

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

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

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

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

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

[0163] For example, a receiving STA can determine the type of the received PPDU to be non-HT, HT, or VHT PPDU based on the following: For example, if 1) the first symbol after the L-LTF signal is BPSK, and 2) no RL-SIG (where L-SIG is repeated) is detected, the received PPDU may be determined to be non-HT, HT, or VHT PPDU.

[0164] Furthermore, if the receiving STA detects an RL-SIG in the received PPDU where the L-SIG is repeated, it can determine that it is an HE PPDU or an EHT PPDU. In this case, if the rate (6Mbps) check fails, the received PPDU may be determined to be a non-HT, HT, or VHT PPDU. If the rate (6Mbps) check and parity check pass, and the result of applying modulo 3 to the Length value of the L-SIG is detected as 0, the received PPDU may be determined to be an EHT PPDU; if the result of Length mod 3 is not 0, it may be determined to be an HE PPDU.

[0165] The PPDU in Figure 13 may be used to send and receive various types of frames. For example, the PPDU in Figure 13 may be used for the simultaneous transmission and reception of one or more control frames, management frames, or data frames.

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

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

[0168] The common information field may include information that applies in common to one or more TB PPDU transmissions requested by a trigger frame, such as the trigger type, UL length, presence or absence of a subsequent trigger frame (e.g., More TF), presence or absence of a CS (channel sensing) request, and UL BW (bandwidth). Figure 14 shows an illustrative common information field format for an EHT variant.

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

[0170] Among the common information, the trigger-dependent common info subfield may contain information that is selectively included based on the trigger type.

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

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

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

[0174] The RU allocation subfield can indicate the size and location of the RU / MRU. For this purpose, the RU allocation subfield may be analyzed together with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc.

[0175] In addition, in this disclosure, a tone plan may relate to rules for determining the size and / or location of resource units (RUs). Below, a tone plan applicable to an HE PPDU (i.e., a PPDU based on the IEEE 802.11ax standard) is described as an example. Specifically, the size / location of RUs applicable to an HE PPDU and the control information associated with RUs applicable to an HE PPDU are described.

[0176] In this disclosure, the control information associated with the RU (or the control information associated with the tone plan) may include control information relating to the size of the RU, its location, information of the user STA assigned to a particular RU, the frequency bandwidth for the PPDU containing the RU, and / or the modulation technique applied to the particular RU. The control information associated with the RU may be included in the SIG field. For example, the control information associated with the RU may be included in the HE-SIG-B field. That is, in the process of generating a transmit PPDU, the transmit STA can include control information for the RUs included in the PPDU in the HE-SIG-B field. The receive STA can also receive the HE-SIG-B included in the receive PPDU, obtain the control information included in the HE-SIG-B, determine whether or not there is an RU assigned to the receive STA, and decode the assigned RU based on the HE-SIG-B.

[0177] In existing wireless LAN systems (e.g., IEEE 802.11ax standard), the HE-STF, HE-LTF, and data field may be configured in RU units. That is, when a first RU is configured for a first receiving STA, the STF / LTF / data field for the first receiving STA may be transmitted and received by the first RU.

[0178] In existing wireless LAN systems (e.g., IEEE 802.11ax standard), a PPDU for one receiving STA (i.e., SU PPDU) and a PPDU for multiple receiving STAs (i.e., MU PPDU) may be defined separately, and a tone plan may be defined separately for each.

[0179] Specifically, a RU may contain multiple subcarriers. For example, if a RU contains N subcarriers, it may be expressed as an N-tone RU or N RU. The location of a particular RU may be indicated by a subcarrier index. Here, the subcarrier index may be defined in units of subcarrier frequency spacing. For example, in a wireless LAN system, the subcarrier frequency spacing may be 312.5 kHz or 78.125 kHz, and the subcarrier frequency spacing for a RU may be 78.125 kHz. That is, a subcarrier index "+1" for a RU means a position 78.125 kHz further up from the DC tone, and a subcarrier index "-1" for a RU means a position 78.125 kHz further down from the DC tone. For example, if the location of a particular RU is indicated as [-121:-96], the RU is located in the region from subcarrier index -121 to subcarrier index -96, and consequently, the RU may contain 26 subcarriers. Furthermore, N-tone RU may include a pre-set pilot tone.

[0180] Resource unit allocation considering bandwidth exceeding 320MHz

[0181] In existing wireless LAN systems (e.g., systems compatible with IEEE 802.11ax and IEEE 802.11be standards), various methods have been discussed for efficiently utilizing wide bandwidth (e.g., up to 320 MHz), including preamble puncturing in single-user and / or multiple-user transmissions, or multiple RU (MRU) allocation. Here, the MRU allocation method refers to a method of combining multiple RUs and assigning them to a specific STA to improve throughput, efficiency, etc.

[0182] As mentioned above, existing wireless LAN systems define RUs and MRUs used for non-OFDMA / OFDMA transmissions up to a maximum bandwidth of 320MHz (e.g., 20MHz, 40MHz, 80MHz, 160MHz, 320MHz). Assignment information for RUs / MRUs may be transmitted / instructed by being included in the U-SIG in relation to the MU PPDU, or by RU assignment information in a trigger frame that solicits a TB PPDU. In particular, for non-OFDMA transmissions, RUs / MRUs limited for each bandwidth may be applied, taking into account preamble puncturing conditions.

[0183] Specifically, as explained with reference to Figure 13, resource allocation-related information in the EHT MU PPDU format may be included in the U-SIG and / or EHT-SIG.

[0184] As mentioned above, the U-SIG field may include version-independent and version-dependent fields. Version-independent fields may include a 3-bit version identifier indicating the Wi-Fi version of IEEE 802.11be and subsequent standards, a 1-bit DL / UL flag, BSS color, TXOP duration information, etc. Version-dependent fields may include information such as PPDU format type, bandwidth, and MCS. The U-SIG field may consist of two symbols jointly encoded, comprising 52 data tones and 4 pilot tones for each 20MHz channel. The U-SIG may also be modulated at the same BPSK 1 / 2 code rate as HE-SIG-A.

[0185] In connection with this, the puncturing pattern (i.e., RU / MRU pattern) may be indicated by preamble puncturing-related information in the U-SIG field (e.g., punctured channel information field). Here, this information may be set to the same value for all 20MHz channels that are not punctured for non-OFDMA transmissions.

[0186] As mentioned above, the EHT-SIG may include a common field and a user-specific field, and may be encoded with a variable MCS. The common field may indicate information for the spatial stream and RU, and the user-specific field may indicate information for a specific user or STA, such as an information ID, MCS, and coding. Furthermore, the EHT-SIG may contain mutually different information in 80MHz units, and may include two EHT-SIG content channels within 80MHz (for example, EHT-SIG content channel 1 (CC1) and EHT-SIG CC2).

[0187] As mentioned above, the IEEE 802.11be standard allows for the definition and use of various sizes of RU / MRU. For example, 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, and 996-tone RU may be defined. For example, 26+52-tone MRU, 106+26-tone MRU, 484+242-tone MRU, 996+484-tone MRU, 996+484+242-tone MRU (for non-OFDMA transmission only), 2x996+484-tone MRU, 3x996-tone MRU, and 3x996+484-tone MRU may be defined. This allows an 11be standard-compatible STA to be assigned one of the RU / MRUs defined above in OFDMA or non-OFDMA operation, and to transmit or receive signals on the assigned RU / MRU. Small-sized MRUs (i.e., 26+52 tone MRUs, or 106+26 tone MRUs) have RUs within a single MRU adjacent to each other in the frequency domain. Large-sized MRUs (i.e., 484+242 tone MRUs, 996+484 tone MRUs, 996+484+242 tone MRUs, 2x996+484 tone MRUs, 3x996 tone MRUs, or 3x996+484 tone MRUs) may be applied when some subchannels are punctured, and the RUs within a single MRU are adjacent to each other in the remaining frequency domain excluding the punctured subchannels.

[0188] Next-generation wireless LAN systems (e.g., IEEE 802.11be release 2, next Wi-Fi, etc.) may utilize bandwidth exceeding existing broadband (i.e., up to 320 MHz) to improve processing capacity and efficiency.

[0189] Therefore, this disclosure proposes a method for defining and allocating RUs / multiplexed RUs (MRUs) when bandwidth exceeding broadband is defined / applied in existing wireless LAN systems.

[0190] For the sake of clarity, the proposal in this disclosure will be explained assuming a 480MHz / 640MHz case, but it may be extended and applied to various bandwidths usable in next-generation wireless LAN systems.

[0191] For example, future wireless LAN systems may define bandwidths of 640MHz and 480MHz to improve processing capacity. Considering this, various RU / MRU values ​​need to be defined to efficiently use / utilize channels even in these situations / bandwidths.

[0192] In connection with this, new RU / MRUs applying preamble puncturing can be defined for non-OFDMA transmission over wide bandwidths. Furthermore, in addition to the RU / MRUs defined in existing wireless LAN systems (e.g., IEEE 802.11be) for OFDMA transmission, newly defined RU / MRUs for non-OFDMA transmission situations can be defined and utilized.

[0193] Hereafter, for the sake of ease of explanation, some descriptions may be expressed / explained using only the size of the RU / MRU, excluding the expression RU / MRU.

[0194] In addition, while the MRU pattern is described as a representative example in this disclosure, the patterns proposed in this disclosure may be analyzed as RU patterns usable in bandwidths exceeding 320 MHz.

[0195] Example 1

[0196] This embodiment relates to a new RU / MRU available for non-OFDMA and OFDMA transmission at 640MHz, where 480MHz is not defined as a separate bandwidth, but rather as one of the punctured 640MHz bands.

[0197] First, let's explain RU / MRU for non-OFDMA transmission at 640MHz.

[0198] The MRU for Non-OFDMA transmission may be configured in various ways, as shown in the following examples, taking into account preamble puncture conditions.

[0199] For example, an 8x996 tone RU / MRU may be defined when there is no preamble puncturing. Additionally, when one or more 80MHz puncturings are considered, 7x996 tone MRU, 6x996 tone MRU, 5x996 tone MRU, and 4x996 tone MRU may be considered.

[0200] In other words, as mentioned above, an 80MHz (sub)channel / bandwidth can correspond to 996 tones, and preamble puncturing in units of 80MHz channels / bandwidth can mean preamble puncturing in units of 996 tones.

[0201] For the sake of clarity in the following explanation, preamble puncturing on an X MHz (sub) channel / bandwidth basis will be referred to as X MHz channel puncturing.

[0202] Figure 15 shows an example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure.

[0203] Referring to Figure 15, for the sake of clarity, only RUs (Routing Units) that are actually usable for data transmission and reception are illustrated and explained, excluding null subcarriers, guards, and DCs (direct conversion / direct current).

[0204] The 996-tone RUs in Figure 15 may correspond to the 8x996 tone RU / MRU without the aforementioned 80MHz channel puncturing. That is, the 8x996 tone RU / MRU may contain eight consecutive 996 tone RUs.

[0205] Additionally, 7x996 tone MRUs 1-8 illustrate the case of 7x996 tone MRUs where one 80MHz channel puncturing occurs. That is, in this case, one 996 tone RU may be punctured, and eight MRUs may be defined by the puncturing location.

[0206] For example, the MRU shown in Figure 15 may be expressed as shown in Table 1 below.

[0207] Table 1 shows examples of 8x996 tone RU / MRU and 7x996 tone MRU available in a 640 MHz bandwidth.

[0208] [Table 1]

[0209] Referring to Table 1, the channel size corresponding to each "O" and "X" is 80 MHz, and each channel may be mapped from the lowest 80 MHz to the highest 80 MHz within a 640 MHz bandwidth. Here, "O" represents the unpunctured portion, and "X" represents the unpunctured portion.

[0210] If the representation methods in Table 1 are extended to include 6x996 tone MRU, 5x996 tone MRU, and 4x996 tone MRU, they can be represented as shown in Table 2 below.

[0211] Table 2 illustrates the 8x996 tone RU / MRU, 7x996 tone MRU, 6x996 tone MRU, 5x996 tone MRU, and 4x996 tone MRU available in a 640 MHz bandwidth.

[0212] [Table 2]

[0213] Referring to Table 2, various MRU patterns may be defined considering preamble puncturing for each RU / MRU. One MRU pattern may be defined for 8x996 tone RU / MRU. Eight MRU patterns may be defined for 7x996 tone MRU. Twenty-eight MRU patterns may be defined for 6x996 tone MRU. Fifty-six MRU patterns may be defined for 5x996 tone MRU. Seventy MRU patterns may be defined for 4x996 tone MRU.

[0214] The MRU patterns shown in Table 2 consider cases where one or more 80MHz channel punctures occur, so there may be many MRU patterns. In this case, scheduling can become very complex.

[0215] For example, puncturing patterns may be indicated by puncturing-related information within the U-SIG (e.g., the Punctured channel information field). As the number of puncturing patterns increases, the field size of this information also increases, which may lead to increased signaling overhead and implementation complexity.

[0216] Therefore, in order to reduce scheduling overhead and implementation complexity, the available puncturing patterns may be defined in a restricted manner, as exemplified below.

[0217] For example, 8x996 tone RU / MRU may be defined to account for the absence of 80MHz channel puncture. Additionally, 7x996 tone MRU may be defined to account for one 80MHz channel puncture.

[0218] In this case, the 8x996 tone RU / MRU and 7x996 tone MRU may correspond to the patterns shown in Figure 15 above.

[0219] Additionally, a 6x996 tone MRU may be defined to account for one 160MHz channel puncturing (i.e., puncturing in units of 2x996 tones).

[0220] Figure 16 shows another example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure.

[0221] Referring to Figure 16, four 6x996 tone MRU patterns may be defined based on one 160 MHz channel puncturing.

[0222] Additionally, a 5x996 tone MRU may be defined to account for one 80MHz channel puncturing and one 160MHz channel puncturing.

[0223] Figure 17 shows yet another example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure.

[0224] Referring to Figure 17, 24 5x996 tone MRU patterns may be defined based on one 80 MHz channel puncturing and one 160 MHz channel puncturing.

[0225] In this case, 80MHz channel puncturing and 160MHz channel puncturing may be performed on consecutive RUs (i.e., consecutive 996 tones and 2x996 tones) or non-contiguous RUs (i.e., non-contiguous 996 tones and 2x996 tones).

[0226] Additionally, a 4x996 tone MRU may be defined to account for two 160MHz channel punctures.

[0227] Figure 18 shows yet another example of an MRU pattern in a 640 MHz bandwidth according to an embodiment of the present disclosure.

[0228] Referring to Figure 18, six 4x996 tone MRU patterns may be defined based on two 160MHz channel puncturings.

[0229] In this case, the two 160MHz channel puncturings may be performed on consecutive RUs (i.e., two consecutive 2x996 tones) or on non-contiguous RUs (i.e., two non-contiguous 2x996 tones).

[0230] As an addition or alternative, a single 320MHz channel puncturing may be considered in relation to the 4x996 tone MRU pattern. Here, the 320MHz channel puncturing may correspond to channel puncturing of four consecutive 996 tones. In this case, two 4x996 tone MRUs may be defined, such as a pattern like 4x996 tone MRU 1 and a pattern like 4x996 tone MRU 6 in Figure 18.

[0231] When considering the 320MHz channel puncturing, it may be analyzed as a 320MHz non-OFDMA RU / MRU, rather than a 640MHz non-OFDMA RU / MRU. In connection with this, a 4x996 tone MRU may be defined only on the primary 320MHz or secondary 320MHz. In existing wireless LAN systems, transmission on a minimum primary 20MHz channel is mandatory, so in actual transmission, it is not permissible to transmit non-OFDMA PPDUs only on the secondary 320MHz channel excluding the primary channel. Also, the transmission of non-OFDMA PPDUs only on the primary 320MHz may be considered a non-OFDMA PPDU in the 320MHz band. As an addition or alternative, assuming that transmission is permitted only on the secondary channel excluding the primary channel, 320MHz channel puncturing may be defined as a 640MHz non-OFDMA RU / MRU.

[0232] Based on the limitations on available puncturing patterns as described above, 8x996 tone RU / MRU, 7x996 tone MRU, 6x996 tone MRU, 5x996 tone MRU, and 4x996 tone MRU (e.g., Figures 15-18) may be represented as shown in Table 3 below.

[0233] Table 3 provides examples of 8x996 tone RU / MRU, 7x996 tone MRU, 6x996 tone MRU, 5x996 tone MRU, and 4x996 tone MRU, considering signaling overhead at a 640 MHz bandwidth.

[0234] [Table 3]

[0235] Referring to Table 3, one MRU pattern may be defined for 8x996 tone RU / MRU. Eight MRU patterns may be defined for 7x996 tone MRU. Four MRU patterns may be restrictedly defined for 6x996 tone MRU. Twenty-four MRU patterns may be restrictedly defined for 5x996 tone MRU. Six and / or two MRU patterns may be restrictedly defined for 4x996 tone MRU.

[0236] Additionally, for the various RU / MRU patterns described above (e.g., Tables 2 and 3), an additional 40MHz channel puncturing may be considered. Here, the 40MHz channel puncturing may correspond to puncturing in units of 484 tones.

[0237] For example, when considering an additional 40MHz channel puncturing for a given RU / MRU, 7x996+484 tone MRU, 6x996+484 tone MRU, 5x996+484 tone MRU, and 4x996+484 tone MRU may be defined / utilized.

[0238] Here, a 7x996+484 tone MRU may correspond to an RU / MRU configured in which any one of the 40MHz channels in an 8x996 tone RU / MRU is punctured.

[0239] Additionally, a 6x996+484 tone MRU may be equivalent to a RU / MRU configured in a 7x996 tone MRU where any one of the 40MHz channels is punctured.

[0240] Additionally, a 5x996+484 tone MRU may be equivalent to a RU / MRU configured in a 6x996 tone MRU where any one of the 40MHz channels is punctured.

[0241] Additionally, a 4x996+484 tone MRU may be equivalent to a RU / MRU configured in a 5x996 tone MRU where any one of the 40MHz channels is punctured.

[0242] As mentioned earlier, considering an additional 40MHz channel puncturing may increase the number of RU / MRU candidates. Furthermore, using or not using an additional 484 tone RU in a wide bandwidth (e.g., over 320MHz bandwidth) may not significantly impact throughput. For these reasons, considering an additional 40MHz channel puncturing may be excluded.

[0243] Additionally, in the 5x996 tone MRU, 5x996+484 tone MRU, and 4x996+484 tone MRU, the case where the lowest or highest 160 MHz channel within the 640 MHz bandwidth is always punctured may be considered.

[0244] In other words, by removing one of the 160MHz channels at both ends, a 480MHz channel can be formed in which a 320MHz channel and a 160MHz channel are located consecutively. Here, one 80MHz channel may be punctured to form various 5x996 tone MRUs, and an additional 40MHz channel may be punctured to form various 4x996+484 tone MRUs. Also, as mentioned above, one 40MHz channel may be punctured onto the formed 480MHz channel to form various 5x996+484 tone MRUs.

[0245] Additionally, for 6x996 tone MRUs, only two 6x996 tone MRUs may be considered, taking into account the case where the lowest or highest 160MHz channel within the 640MHz bandwidth is always punctured.

[0246] If 480MHz is defined as a single bandwidth (i.e., if 480MHz is assumed to be a separate bandwidth rather than a case of 640MHz), then the 5x996 tone MRU, 5x996+484 tone MRU, and 4x996+484 tone MRU may be excluded from the previously proposed non-OFDMA RU / MRU in the 640MHz bandwidth. Additionally, the exclusion of 6x996 tone MRU and 4x996 tone MRU may also be considered. In this case, the excluded RU / MRU may be redefined as non-OFDMA RU / MRU in the 480MHz bandwidth in the embodiment described later (e.g., Embodiment 2).

[0247] As an additional or alternative approach, one may also consider applying the RU / MRU in 320MHz non-OFDMA as defined in existing wireless LAN systems (e.g., IEEE 802.11be) to the two 320MHz channels that constitute the 640MHz channel.

[0248] A method may be applied to define the RU / MRU pattern for a 640MHz bandwidth based on the RU / MRU pattern defined in an existing wireless LAN system. In other words, unlike existing wireless LAN systems, a method may be considered in which existing defined RU / MRU patterns for a relatively small bandwidth are combined to define the RU / MRU pattern for a relatively large bandwidth.

[0249] Specifically, the RU / MRU in 320MHz non-OFDMA may be applied independently depending on the preamble puncturing pattern within each 320MHz, and consequently, the RU / MRU in 640MHz non-OFDMA may be constructed from combinations of these.

[0250] For example, in an existing wireless LAN system with a 320MHz bandwidth, 4x996 tone RU / MRU, 3x996 tone RU / MRU, 3x996+484 tone RU / MRU, and 2x996+484 tone RU / MRU are defined based on 80MHz / 40MHz channel puncturing.

[0251] At this time, the RU / MRU in the 640MHz non-OFDMA configured based on the existing RU / MRU for the aforementioned 320MHz bandwidth is as shown in Table 4 below.

[0252] Table 4 illustrates RU / MRU combinations in 640 MHz non-OFDMA using existing defined RU / MRU combinations.

[0253] [Table 4]

[0254] Referring to Table 4, {x} represents the x-tone RU / MRU within the 320MHz channel, and the order is independent of frequency. Furthermore, in each combination, various forms of RU / MRU may exist depending on the preamble puncturing pattern of each channel.

[0255] Here, some RU / MRU may overlap with the RU / MRU proposed in this embodiment.

[0256] As an additional or alternative, considering the case where the lowest or highest 160MHz channel at 640MHz is punctured, one method may also be considered to apply the RU / MRU for 320MHz non-OFDMA and 160MHz non-OFDMA as defined in existing wireless LAN systems (e.g., IEEE 802.11be, etc.) to the one 320MHz channel and one 160MHz channel that make up the remaining 480MHz channel.

[0257] Specifically, the RU / MRU in 320MHz non-OFDMA and the RU / MRU in 160MHz non-OFDMA may be applied independently depending on the preamble puncturing pattern within each 320MHz and 160MHz, and consequently, the RU / MRU in 640MHz non-OFDMA may be constructed by a combination of these.

[0258] For example, in an existing wireless LAN system, for a 160MHz bandwidth, 2x996 tone RU / MRU, 996+484+242 tone RU / MRU, and 996+484 tone RU / MRU are defined based on 40MHz / 20MHz channel puncturing. Additionally, for a 320MHz bandwidth, 4x996 tone RU / MRU, 3x996 tone RU / MRU, 3x996+484 tone RU / MRU, and 2x996+484 tone RU / MRU are defined based on 80MHz / 40MHz channel puncturing.

[0259] In this case, the RU / MRU for a 640MHz non-OFDMA (when one 160MHz channel is punctured at both ends) configured based on the existing RU / MRU for the 320MHz bandwidth and 160MHz bandwidth is as shown in Table 5 below.

[0260] Table 5 illustrates RU / MRU combinations in 640 MHz non-OFDMA using existing defined RU / MRU combinations.

[0261] [Table 5]

[0262] Referring to Table 5, {x} represents the x-tone RU / MRU within the 320MHz channel, and [y] represents the y-tone RU / MRU within the 160MHz channel; the order is independent of frequency. Furthermore, various forms of RU / MRU can exist in each combination depending on the preamble puncturing pattern of each channel.

[0263] Here, some RU / MRU may overlap with the RU / MRU proposed in this embodiment.

[0264] If 480MHz is defined as a single bandwidth (i.e., if 480MHz is assumed to be a separate bandwidth rather than a case of 640MHz), then the RU / MRU in 640MHz non-OFDMA formed by the combination of the RU / MRU in 320MHz non-OFDMA and the RU / MRU in 160MHz non-OFDMA may be excluded. In this case, the excluded RU / MRU may be redefined as the non-OFDMA RU / MRU in the 480MHz bandwidth in the embodiment described later (for example, Embodiment 2).

[0265] Additionally, as mentioned above, various RU / MRU candidates are proposed, but in practice, when transmitting non-OFDMA, channels containing the primary 20MHz must not be punctured, and the RU / MRU in question may be excluded in such non-OFDMA transmissions.

[0266] Next, we will explain RU / MRU for OFDMA transmission at 640MHz.

[0267] In this regard, methods for applying RU / MRU defined in existing wireless LAN systems (e.g., IEEE 802.11be) may be considered.

[0268] For example, in the case of MRU, combinations are only possible within a specific channel, as defined by existing definitions.

[0269] Specifically, small MRUs (i.e., 52+26 tone MRU, 106+26 tone MRU) may be defined only within a 20 MHz channel, 484+242 tone MRU may be defined only within an 80 MHz channel, and 996+484 tone MRU may be defined only within a 160 MHz channel. Additionally, 2x996 tone MRU may be defined only within a 160 MHz channel, and 2x996+484 tone MRU, 3x996 tone MRU, and 3x996+484 tone MRU may be defined only within a 320 MHz channel.

[0270] Additionally, the MRUs defined for non-OFDMA transmission described above in this embodiment may be further defined and used for OFDMA transmission as well. In this regard, 8x996 tone RU / MRU may be excluded, and 4x996 tone MRU may be defined only within a 320 MHz channel.

[0271] In case 480 MHz is assumed as an independent bandwidth rather than one case of 640 MHz, some cases (i.e., some RU / MRU patterns) in non-OFDMA transmission may be excluded, but in OFDMA transmission, these cases may not be excluded and may always be defined. However, the RU / MRU may be applied only within the remaining 480 MHz excluding the first 160 MHz or the last 160 MHz of 640 MHz. That is, the RU / MRU may have no relation to the puncturing in the first 160 MHz channel or the last 160 MHz channel. As an alternative, in a situation where the first 160 MHz channel or the last 160 MHz channel of 640 MHz is punctured, the RU / MRU may be applied only within the remaining 480 MHz.

[0272] Example 2

[0273] This embodiment relates to new RUs / MRUs available for non-OFDMA transmission and OFDMA transmission at 480 MHz, considering the case where 480 MHz is defined as one bandwidth (i.e., assuming 480 MHz as one independent bandwidth rather than one case of 640 MHz).

[0274] First, the RUs / MRUs for non-OFDMA transmission at 480 MHz will be described.

[0275] The MRUs for non-OFDMA transmission may be configured in various ways as follows, considering the preamble puncturing situation.

[0276] For example, when there is no preamble puncturing, a 6x996 tone RU / MRU may be defined. Additionally, when considering one or more 80 MHz puncturings, a 5x996 tone MRU and a 4x996 tone MRU may be considered.

[0277] That is, as in the aforementioned Embodiment 1, an 80 MHz channel / bandwidth may correspond to 996 tones, and an 80 MHz channel preamble puncturing may mean preamble puncturing in units of 996 tones.

[0278] FIG. 19 shows an example of an MRU pattern in a 480 MHz bandwidth according to an embodiment of the present disclosure.

[0279] Referring to FIG. 19, for clarity of explanation, only the RUs available for actual data transmission and reception are illustrated and described, excluding null subcarriers, guards, and DC (direct conversion / direct current).

[0280] The 996-tone RUs in Figure 19 may correspond to the 6x996 tone RU / MRU without the aforementioned 80MHz channel puncturing. That is, 6x996 tone RU / MRU may contain six consecutive 996 tone RUs.

[0281] Additionally, 5x996 tone MRUs 1-6 illustrate the case of 5x996 tone MRUs where one 80MHz channel puncturing occurs. That is, in this case, one 996 tone RU may be punctured, and six MRUs may be defined by the puncturing location.

[0282] Additionally, 4x996 tone MRUs 1-15 illustrate the case of a 4x996 tone MRU where two 80MHz channel puncturings are performed. In this case, the two 80MHz channel puncturings may be performed on consecutive RUs (i.e., two consecutive 996 tones) or non-consecutive RUs (i.e., two non-consecutive 996 tones).

[0283] For example, the MRU shown in Figure 19 may be expressed as shown in Table 6 below.

[0284] Table 6 illustrates 6x996 tone RU / MRU, 5x996 tone MRU, and 4x996 tone MRU available in a 480 MHz bandwidth.

[0285] [Table 6]

[0286] Referring to Table 6, the channel size corresponding to each "O" and "X" is 80 MHz, and each channel may be mapped from the lowest 80 MHz to the highest 80 MHz within a 480 MHz bandwidth. Here, "O" represents the unpunctured portion, and "X" represents the unpunctured portion.

[0287] Referring to Table 6, various MRU patterns may be defined considering preamble puncturing for each RU / MRU. One MRU pattern may be defined for 6x996 tone RU / MRU. Six MRU patterns may be defined for 5x996 tone MRU. Fifteen MRU patterns may be defined for 4x996 tone MRU.

[0288] The MRU patterns shown in Table 6 consider cases where one or more 80MHz channel puncturings occur, so there may be many MRU patterns. In this case, the scheduling aspect can become very complex.

[0289] Therefore, similar to Example 1 described above, in order to reduce scheduling overhead and implementation complexity, the available puncturing patterns may be defined in a restricted manner as shown in the following example.

[0290] Figure 20 shows another example of an MRU pattern in a 480 MHz bandwidth according to an embodiment of the present disclosure.

[0291] Referring to Figure 20, one 6x996 tone RU / MRU may be defined to account for the absence of 80MHz channel puncture.

[0292] Additionally, considering one 80MHz channel puncture, six 5x996 tone MRUs may be defined based on the puncture location.

[0293] Additionally, considering one 160MHz channel puncture, three 4x996 tone MRUs may be defined based on the puncture location. That is, unlike in Figure 19, in this case, four 4x996 tone MRUs may be defined considering one 160MHz channel puncture, i.e., puncture in units of 2x996 tones.

[0294] As an addition or alternative, a 2x996 tone MRU considering one 320 MHz channel puncturing may be considered. Here, the 320 MHz channel puncturing may correspond to the channel puncturing for four consecutive 996 tones.

[0295] When 480 MHz is composed of 160 MHz in the relatively low frequency band and 320 MHz in the relatively high frequency band, the 2x996 tone MRU may correspond to an MRU composed of the first two consecutive 996 tones at 480 MHz, where four consecutive 996 tones corresponding to 320 MHz are punctured. On the other hand, when 480 MHz is composed of 320 MHz in the relatively low frequency band and 160 MHz in the relatively high frequency band, the 2x996 tone MRU may correspond to an MRU composed of the last two consecutive 996 tones at 480 MHz, where four consecutive 996 tones corresponding to 320 MHz are punctured.

[0296] When considering the 320 MHz channel puncturing, it may be analyzed as a 160 MHz non - OFDMA RU / MRU instead of a 480 MHz band non - OFDMA RU / MRU. In this regard, the 2x996 tone MRU may be defined only at the Primary 160 MHz or Secondary 160 MHz. In an existing wireless LAN system, since transmission on a minimum Primary 20 MHz channel is essential, it may not be allowed to transmit non - OFDMA PPDUs only at the Secondary 160 MHz except for the Primary channel in actual transmission. Also, the fact that non - OFDMA PPDUs are transmitted only at the Primary 160 MHz may correspond to non - OFDMA PPDUs in the 160 MHz band. As an addition or alternative, assuming that transmission on the Secondary channel except for the Primary channel is allowed, the 320 MHz channel puncturing may be defined as a non - OFDMA RU / MRU in the 480 MHz band.

[0297] Based on the limitations on available puncturing patterns as described above, 6x996 tone RU / MRU, 5x996 tone MRU, and 4x996 tone MRU (e.g., Figure 20) may be represented as shown in Table 7 below.

[0298] Table 7 shows examples of 6x996 tone RU / MRU, 5x996 tone MRU, and 4x996 tone MRU considering signaling overhead in a 480 MHz bandwidth.

[0299] [Table 7]

[0300] Referring to Table 7, one MRU pattern may be defined for 6x996 tone RU / MRU. Six MRU patterns may be defined for 5x996 tone MRU. Three and / or two MRU patterns may be restrictedly defined for 4x996 tone MRU.

[0301] Additionally, for the various RU / MRU patterns described above (e.g., Tables 6 and 7), an additional 40MHz channel puncturing may be considered. Here, the 40MHz channel puncturing may correspond to puncturing in units of 484 tones.

[0302] For example, when considering an additional 40MHz channel puncturing for a specific RU / MRU, 5x996+484 tone MRU and 4x996+484 tone MRU may be defined / utilized.

[0303] Here, a 5x996+484 tone MRU may correspond to an RU / MRU configured in which any one of the 40MHz channels in a 6x996 tone RU / MRU is punctured.

[0304] Additionally, a 4x996+484 tone MRU may be equivalent to a RU / MRU configured in a 5x996 tone MRU where any one of the 40MHz channels is punctured.

[0305] As mentioned earlier, considering an additional 40MHz channel puncturing may increase the number of RU / MRU candidates. Furthermore, using or not using an additional 484 tone RU in a wide bandwidth (e.g., over 320MHz bandwidth) may not significantly impact throughput. For these reasons, considering an additional 40MHz channel puncturing may be excluded.

[0306] As an additional or alternative approach, it may also be considered to apply the RU / MRU for 320MHz non-OFDMA and 160MHz non-OFDMA defined in existing wireless LAN systems (e.g., IEEE 802.11be) to one 320MHz channel and one 160MHz channel that constitute the 480MHz channel, respectively.

[0307] In other words, unlike existing wireless LAN systems, a method may be considered in which existing defined RU / MRU patterns are combined for relatively small bandwidths, and RU / MRU patterns are defined for relatively large bandwidths.

[0308] Specifically, the RU / MRU in 320MHz non-OFDMA and the RU / MRU in 160MHz non-OFDMA may be applied independently depending on the preamble puncturing pattern within each 320MHz and 160MHz, and consequently, the RU / MRU in 480MHz non-OFDMA may be constructed by a combination of these.

[0309] For example, in an existing wireless LAN system with a 160MHz bandwidth, 2x996 tone RU / MRU, 996+484+242 tone RU / MRU, and 996+484 tone RU / MRU are defined based on 40MHz / 20MHz channel puncturing. Additionally, for a 320MHz bandwidth, 4x996 tone RU / MRU, 3x996 tone RU / MRU, 3x996+484 tone RU / MRU, and 2x996+484 tone RU / MRU are defined based on 80MHz / 40MHz channel puncturing.

[0310] At this time, the RU / MRU in the 480MHz non-OFDMA configured based on the existing RU / MRU defined for the 320MHz bandwidth and 160MHz bandwidth are as shown in Table 8 below.

[0311] Table 8 illustrates RU / MRU combinations in 480 MHz non-OFDMA using existing defined RU / MRU combinations.

[0312] [Table 8]

[0313] Referring to Table 8, {x} represents the x-tone RU / MRU within the 320MHz channel, and [y] represents the y-tone RU / MRU within the 160MHz channel, with the order being independent of frequency. Furthermore, within each combination, various forms of RU / MRU may exist depending on the preamble puncturing pattern of each channel.

[0314] Here, some RU / MRU may overlap with the RU / MRU proposed in this embodiment.

[0315] Additionally, as mentioned above, various RU / MRU cases / candidates are proposed, but in practice, when transmitting non-OFDMA, channels containing primary 20MHz should not be punctured, and such RU / MRU may be excluded in such non-OFDMA transmissions.

[0316] Next, we will explain RU / MRU for OFDMA transmission at 480MHz.

[0317] In this regard, methods for applying RU / MRU defined in existing wireless LAN systems (e.g., IEEE 802.11be) may be considered.

[0318] For example, in the case of MRU, combinations are only possible within a specific channel, as defined by existing definitions.

[0319] Specifically, smaller MRUs (i.e., 52+26 tone MRU, 106+26 tone MRU) may be defined only within a 20MHz channel, 484+242 tone MRUs may be defined only within an 80MHz channel, and 996+484 tone MRUs may be defined only within a 160MHz channel. Additionally, 2x996 tone MRUs may be defined only within a 160MHz channel, and 2x996+484 tone MRUs, 3x996 tone MRUs, and 3x996+484 tone MRUs may be defined only within a 320MHz channel.

[0320] Additionally, the MRU defined in this embodiment for non-OFDMA transmission may also be further defined and used for OFDMA transmission. In connection with this, 6x996 tone RU / MRU may be excluded, and 4x996 tone MRU may be defined only within a 320MHz channel.

[0321] Figure 21 is a flowchart illustrating exemplary operation based on resource allocation of the STA according to the embodiment of this disclosure.

[0322] In step S2110, an STA can receive a PPDU (physical layer protocol data unit) from another STA that includes a SIG field for resource unit allocation-related information.

[0323] For example, the resource unit allocation information may be information related to preamble puncturing, and such information may be indicated in the U-SIG field within the (MU)PPDU.

[0324] In connection with this, the resource unit allocation-related information can indicate a specific candidate within a set that includes a predefined number of multiple RU (MRU) candidates for bandwidths exceeding 320 MHz.

[0325] For example, if the bandwidth exceeding 320 MHz corresponds to a 480 MHz bandwidth, the predefined number of MRU candidates may include at least one of the following: a first MRU without 80 MHz channel puncturing (e.g., 6x996 tone RU / MRU), a second MRU with one 80 MHz channel puncturing applied (e.g., 5x996 tone MRU), and a third MRU with one 160 MHz channel puncturing applied (e.g., 4x996 tone MRU).

[0326] For example, the first MRU may consist of six consecutive 996-tone RUs. Additionally or alternatively, the predefined number of candidate MRUs may further include one or more fourth MRUs configured by applying 40 MHz channel puncturing corresponding to 484-tone RUs to the first MRU, where the size of the one or more fourth MRUs may correspond to 5 x 996 + 484 tones.

[0327] For example, the second MRU may consist of five 996-tone RUs. The second MRU may be distinguished as one or more second MRU candidates by applying the 80MHz channel puncturing corresponding to the 996-tone RUs to six 996-tone RUs included in the 480MHz bandwidth. Additionally or alternatively, the predefined number of MRU candidates may further include one or more fifth MRUs configured by applying 40MHz channel puncturing corresponding to 484-tone RUs to one or more of the second MRU candidates. Here, the size of the one or more fifth MRUs may correspond to 4 x 996 + 484 tones.

[0328] For example, the third MRU may consist of four 996-tone RUs. The second MRU may be distinguished as one or more third MRU candidates by applying the 160MHz channel puncturing corresponding to 2x996-tone RUs to six 996-tone RUs included in the 480MHz bandwidth.

[0329] As an addition or alternative, if the bandwidth exceeding 320 MHz corresponds to a 480 MHz bandwidth, the 480 MHz bandwidth may include 320 MHz channels and 160 MHz channels. In connection with this, the predefined number of MRU candidates may consist of a combination of existing defined 320 MHz MRU candidates and existing defined 160 MHz MRU candidates. Here, the size of the existing defined 320 MHz MRU candidate may be one or more of 4x996 tones, 3x996 tones, 3x996+484 tones, or 2x996+484 tones. The size of the existing defined 160 MHz MRU candidate may be one or more of 2x996 tones, 996+484+242 tones, or 996+484 tones.

[0330] As an additional or alternative, the aforementioned predefined number of MRU candidates may be associated with non-OFDMA transmission in the 480 MHz bandwidth.

[0331] In step S2120, the STA can retrieve the data fields within the PPDU based on the resource unit allocation-related information.

[0332] For example, an STA can receive all or part of a PPDU transmitted by another STA. For example, the received signal / field / sequence may take the form shown in Figure 13. The STA can perform operations to reconstruct the CSD, spatial mapping, IDFT / IFFT, and GI insertion results.

[0333] An STA can decode all or part of a PPDU. Furthermore, an STA can obtain control information for the tone plan (or RU-related information) from the decoded PPDU. For example, another STA can decode the L-SIG / RL-SIG / U-SIG / EHT-SIG of a PPDU based on the L-STF / L-LTF and obtain the information contained therein. Various RU allocation-related information (or information regarding the tone plan) in this disclosure may be contained in the U-SIG / EHT-SIG, and an STA can decode the U-SIG / EHT-SIG to obtain the tone plan (or RU-related information).

[0334] The STA can decode the rest of the PPDU based on the acquired tone plan (or RU-related information). For example, the STA can perform AGC (automatic gain control) / channel estimation using the STF / LTF (e.g., EHT-STF / EHT-LTF) field of the PPDU based on information about one plan (or RU). The STA can also decode the data field of the PPDU based on the tone plan (or RU-related information) and obtain the MPDU contained in the data field.

[0335] Furthermore, the STA can transmit the decoded data to a higher layer (e.g., the MAC layer). If the higher layer instructs the PHY layer to generate a signal in response to the data transmitted to the higher layer, it can perform subsequent operations.

[0336] Figure 22 is a flowchart illustrating other exemplary operations based on resource allocation of the STA according to the embodiments of this disclosure.

[0337] In step S2210, the STA can configure the SIG field for resource unit allocation-related information.

[0338] The explanation regarding resource unit allocation-related information is the same as that explained with reference to Figure 21, and any redundant explanations will be omitted.

[0339] In step S2220, the STA can transmit the PPDU (physical layer protocol data unit) containing the SIG field to another STA.

[0340] For example, an STA can obtain information about the tone plan. This information may include the RU size, RU location, control information associated with the RU, the frequency unit / frequency band in which the RU is contained, and information about the STA receiving the RU.

[0341] The STA can configure / generate a PPDU based on the acquired control information. The PPDU configuration / generation step may include the configuration / generation of each field of the PPDU. For example, the STA can configure a SIG (e.g., U-SIG / EHT-SIG) containing control information for the tone plan. The STA can configure a field containing control information (e.g., an N-bitmap) indicating the size / location of the RU, and / or a field containing the identifier of the STA receiving the RU (e.g., AID). The STA can also generate an STF / LTF sequence to be transmitted in a particular RU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence. The STA can also generate a data field (i.e., an MPDU) to be transmitted in a particular RU.

[0342] An STA can transmit a PPDU configured in this way to another STA. An STA can perform operations such as CSD (cyclic shift diversity), spatial mapping, IDFT (inverse discrete Fourier transform) / IFFT (inverse fast Fourier transform) operation, and GI (guard interval) insertion. The signal / field / sequence configured in this way may be transmitted in the form shown in Figure 13 and / or Figure 14, for example.

[0343] The examples described in Figures 21 and 22 specifically illustrate the case where the bandwidth exceeding 320 MHz is 480 MHz (for example, Example 2). However, it goes without saying that the operation described in Figures 21 and 22 can be extended and applied to other examples described above (for example, the case of a 640 MHz bandwidth corresponding to Example 1).

[0344] In Figures 21 and 22 mentioned above, STA corresponds to non-AP STA, and other STA may correspond to AP STA. Alternatively, STA may correspond to AP STA, and other STA may correspond to non-AP STA. Alternatively, both STA and other STA may correspond to AP STA, or both may correspond to non-AP STA.

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

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

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

[0348] Although the method proposed in this disclosure has been described primarily in the context of its application to IEEE 802.11-based systems, it can be applied to a variety of other wireless LAN or wireless communication systems.

Claims

1. The step of receiving a PPDU (physical layer protocol data unit) from another STA, which includes a SIG field for resource unit (RU) allocation-related information, The step includes decoding the data fields in the PPDU based on the RU allocation-related information, The aforementioned RU allocation-related information indicates one MRU selected from a predefined set of candidate MRUs (multiple RUs) for a 480 MHz bandwidth. The aforementioned predefined set of candidate MRUs is: The first type of MRU corresponds to the unpunctured bandwidth, A second type of MRU corresponding to the bandwidth in which one 80MHz channel is punctured, A method comprising a third type of MRU corresponding to the bandwidth in which one 160 MHz channel is punctured.

2. The method according to claim 1, wherein the first type MRU includes six consecutive 996-tone RUs.

3. The predefined set of candidate MRUs further includes a fourth type of MRU configured by applying 40 MHz channel puncturing corresponding to a 484 tone RU to the first type of MRU, The method according to claim 1, wherein the size of the fourth type MRU corresponds to 5 x 996 + 484 tones.

4. The second type of MRU includes five 996 tone RUs, The method according to claim 1, wherein the second type of MRU is distinguished as one or more candidates by applying 80 MHz channel puncturing corresponding to a 996 tone RU to six 996 tone RUs included in the 480 MHz bandwidth.

5. The predefined set of candidate MRUs further includes a fifth type of MRU configured by applying 40 MHz channel puncturing corresponding to a 484 tone RU to the second type of MRU, The method according to claim 4, wherein the size of the fifth type MRU corresponds to 4 x 996 + 484 tones.

6. The third type of MRU includes four 996 tone RUs, The method according to claim 1, wherein the third type of MRU is distinguished as one or more candidates by applying 160 MHz channel puncturing corresponding to 2 x 996 tone RUs to six 996 tone RUs included in the 480 MHz bandwidth.

7. The method according to claim 1, wherein the 480 MHz bandwidth includes a 320 MHz channel and a 160 MHz channel.

8. The method according to claim 7, wherein the predefined set of candidate MRUs includes a combination of a predefined MRU for a 320 MHz bandwidth and a predefined MRU for a 160 MHz bandwidth.

9. The predefined MRU size for the 320 MHz bandwidth corresponds to one or more of 4 x 996 tones, 3 x 996 tones, 3 x 996 + 484 tones, or 2 x 996 + 484 tones. The method according to claim 8, wherein the predefined size of the MRU for the 160 MHz bandwidth is one or more of 2 x 996 tones, 996 + 484 + 242 tones, or 996 + 484 tones.

10. The method according to claim 1, wherein the predefined set of candidate MRUs is defined to be used for non-OFDMA (non-orthogonal frequency division multiple access) transmission in the 480 MHz bandwidth.

11. STA (station), At least one transceiver and, The system comprises at least one processor connected to the at least one transceiver, The aforementioned at least one processor is From another STA, receive a PPDU (physical layer protocol data unit) containing a SIG field for resource unit (RU) allocation-related information. Based on the RU assignment-related information, the system is configured to decode the data fields within the PPDU. The aforementioned RU allocation-related information indicates one MRU selected from a predefined set of candidate MRUs (multiple RUs) for a 480 MHz bandwidth. The aforementioned predefined set of candidate MRUs is: The first type of MRU corresponds to the unpunctured bandwidth, A second type of MRU corresponding to the bandwidth in which one 80MHz channel is punctured, A STA, including a third type of MRU corresponding to the bandwidth in which one 160 MHz channel is punctured.

12. STA (station), At least one processor, STA comprising: at least one memory that stores instructions causing the STA to perform the method according to at least one of claims 1 to 10 when executed by the at least one processor.

13. A non-temporary computer-readable medium comprising stored program instructions for performing at least one of the methods described in any one of claims 1 to 10.

14. STA (station), At least one transceiver and, The system comprises at least one processor connected to the at least one transceiver, The aforementioned at least one processor is Configure the SIG field for RU (resource unit) allocation-related information. The system is configured to transmit the PPDU (physical layer protocol data unit) containing the aforementioned SIG field to another STA. The aforementioned RU allocation-related information indicates one MRU selected from a predefined set of candidate MRUs (multiple RUs) for a 480 MHz bandwidth. The aforementioned predefined set of candidate MRUs is: The first type of MRU corresponds to the unpunctured bandwidth, A second type of MRU corresponding to the bandwidth in which one 80MHz channel is punctured, A STA, including a third type of MRU corresponding to the bandwidth in which one 160 MHz channel is punctured.

Images