[go: up one dir, main page]

WO2025170270A1 - Procédé et dispositif basés sur un plan de tonalité d'unité de ressource distribuée pour transmission ou réception dans un système lan sans fil - Google Patents

Procédé et dispositif basés sur un plan de tonalité d'unité de ressource distribuée pour transmission ou réception dans un système lan sans fil

Info

Publication number
WO2025170270A1
WO2025170270A1 PCT/KR2025/001449 KR2025001449W WO2025170270A1 WO 2025170270 A1 WO2025170270 A1 WO 2025170270A1 KR 2025001449 W KR2025001449 W KR 2025001449W WO 2025170270 A1 WO2025170270 A1 WO 2025170270A1
Authority
WO
WIPO (PCT)
Prior art keywords
tone
dru
tones
ton
drus
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/KR2025/001449
Other languages
English (en)
Korean (ko)
Inventor
박은성
천진영
최진수
임동국
정인식
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2025170270A1 publication Critical patent/WO2025170270A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present disclosure relates to a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless local area network (WLAN) system.
  • WLAN wireless local area network
  • WLANs wireless local area networks
  • IEEE 802.11 series of standards can be referred to as Wi-Fi.
  • WLANs include enhancements for Very High Throughput (VHT) in the 802.11ac standard and enhancements for High Efficiency (HE) in the IEEE 802.11ax standard.
  • VHT Very High Throughput
  • HE High Efficiency
  • EHT Extremely High Throughput
  • MIMO Multiple Input Multiple Output
  • APs multiple access points
  • UHR ultra-high reliability
  • the technical problem of the present disclosure is to provide a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless LAN system.
  • a method may include: generating, by a first station (STA), a physical layer protocol data unit (PPDU) including one or more fields; and transmitting, by the first STA, the PPDU to one or more second STAs on a bandwidth including a 20 MHz channel, wherein the one or more fields may be transmitted on one or more distributed resource units (DRUs).
  • STA first station
  • PPDU physical layer protocol data unit
  • DRUs distributed resource units
  • a method may include: receiving, by a second STA, a physical layer protocol data unit (PPDU) from a first STA, a PPDU including one or more fields on a bandwidth including a 20 MHz channel; and decoding, by the second STA, the one or more fields received on one or more distributed resource units (DRUs).
  • PPDU physical layer protocol data unit
  • DRUs distributed resource units
  • the available tones in the 20 MHz channel can be configured based on excluding 18 tones corresponding to DC (direct current) tones and guard tones, and 4 tones corresponding to null tones from among 256 tones in the 20 MHz channel.
  • a method and device for transmitting or receiving based on a distributed resource unit tone plan in a wireless LAN system can be provided.
  • FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
  • FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.
  • FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.
  • FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.
  • FIG. 5 is a diagram for explaining a CSMA/CA-based frame transmission operation to which the present disclosure can be applied.
  • FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.
  • FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.
  • FIGS. 8 to 10 are diagrams for explaining examples of resource units of a wireless LAN system to which the present disclosure can be applied.
  • FIG. 11 is a drawing illustrating examples of DRUs to which the present disclosure can be applied.
  • FIG. 12 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.
  • FIG. 13 is a diagram for explaining an example of a DRU tone plan-based PPDU transmission method of a first STA according to the present disclosure.
  • FIG. 14 is a diagram for explaining an example of a DRU tone plan-based PPDU reception method of a second STA according to the present disclosure.
  • FIG. 15 is a diagram for explaining a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to an example of the present disclosure.
  • first in one embodiment
  • second component in another embodiment
  • first component in another embodiment may be referred to as a first component in another embodiment
  • first component in another embodiment may be referred to as a second component in another embodiment
  • second component in one embodiment may be referred to as a first component in another embodiment
  • the examples of the present disclosure can be applied to various wireless communication systems.
  • the examples of the present disclosure can be applied to a wireless LAN system.
  • the examples of the present disclosure can be applied to a wireless LAN based on the IEEE 802.11a/g/n/ac/ax/be standards.
  • the examples of the present disclosure can be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard.
  • the examples of the present disclosure can be applied to a wireless LAN based on the next-generation standard after IEEE 802.11bn.
  • the examples of the present disclosure can be applied to a cellular wireless communication system.
  • the examples of the present disclosure can be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series of technologies and the 5G NR (New Radio) series of technologies of the 3rd Generation Partnership Project (3GPP) standard.
  • LTE Long Term Evolution
  • 5G NR New Radio
  • FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
  • the first device (100) and the second device (200) illustrated in FIG. 1 may be replaced with various terms such as a terminal, a wireless device, a WTRU (Wireless Transmit Receive Unit), a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an MSS (Mobile Subscriber Unit), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), or simply a user.
  • a terminal a wireless device
  • a 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
  • first device (100) and the second device (200) may be replaced with various terms such as an access point (AP), a BS (Base Station), a fixed station, a Node B, a BTS (Base Transceiver System), a network, an AI (Artificial Intelligence) system, an RSU (road side unit), a repeater, a router, a relay, a gateway, etc.
  • AP access point
  • BS Base Station
  • BTS Base Transceiver System
  • AI Artificial Intelligence
  • RSU road side unit
  • repeater a router, a relay, a gateway, etc.
  • the devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs).
  • the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA.
  • the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, in the present disclosure, the STAs (110, 200) may perform the functions of an AP and/or a non-AP.
  • the STAs (110, 200) When the STAs (110, 200) perform an AP function, they may simply be referred to as APs, and when the STAs (110, 200) perform a non-AP function, they may simply be referred to as STAs.
  • the APs may also be referred to as AP STAs.
  • the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless LAN technologies (e.g., IEEE 802.11 series).
  • the first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.11 standard.
  • MAC medium access control
  • PHY physical layer
  • the first device (100) and the second device (200) may additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than wireless LAN technology.
  • the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc.
  • the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).
  • a first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and/or one or more antennas (108).
  • the processor (102) controls the memories (104) and/or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure.
  • the processor (102) may process information in the memories (104) to generate first information/signals, and then transmit a wireless signal including the first information/signals via the transceivers (106).
  • the processor (102) may receive a wireless signal including second information/signals via the transceivers (106), and then store information obtained from signal processing of the second information/signals in the memory (104).
  • the memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in the present disclosure.
  • the processor (102) and the memory (104) may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series).
  • the transceiver (106) may be connected to the processor (102) and may transmit and/or receive wireless signals via one or more antennas (108).
  • the transceiver (106) may include a transmitter and/or a receiver.
  • the transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit.
  • a device may also mean a communication modem/circuit/chip.
  • the second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and/or one or more antennas (208).
  • the processor (202) controls the memories (204) and/or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure.
  • the processor (202) may process information in the memory (204) to generate third information/signals, and then transmit a wireless signal including the third information/signals via the transceivers (206).
  • the processor (202) may receive a wireless signal including fourth information/signals via the transceivers (206), and then store information obtained from signal processing of the fourth information/signals in the memory (204).
  • the memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in the present disclosure.
  • the processor (202) and the memory (204) may be part of a communication modem/circuit/chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series).
  • the transceiver (206) may be connected to the processor (202) and may transmit and/or receive wireless signals via one or more antennas (208).
  • the transceiver (206) may include a transmitter and/or a receiver.
  • the transceiver (206) may be used interchangeably with an RF unit.
  • a device may also mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors (102, 202).
  • one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC).
  • One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure.
  • One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and/or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206).
  • One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in the present disclosure.
  • signals e.g., baseband signals
  • One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer.
  • One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc.
  • the descriptions, functions, procedures, proposals, methods and/or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202).
  • the descriptions, functions, procedures, proposals, methods and/or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.
  • One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and/or commands.
  • the one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and/or combinations thereof.
  • the one or more memories (104, 204) may be located internally and/or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.
  • One or more transceivers (106, 206) can transmit user data, control information, wireless signals/channels, etc., as mentioned in the methods and/or flowcharts of the present disclosure, to one or more other devices.
  • One or more transceivers (106, 206) can receive user data, control information, wireless signals/channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and/or flowcharts of the present disclosure, from one or more other devices.
  • one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals.
  • one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices.
  • one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals/channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208).
  • 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 received user data, control information, wireless signals/channels, etc.
  • One or more transceivers (106, 206) may convert processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using one or more processors (102, 202).
  • one or more transceivers (106, 206) may include an (analog) oscillator and/or a filter.
  • one of the STAs (100, 200) may perform the intended operation of an AP, and the other of the STAs (100, 200) may perform the intended operation of a non-AP STA.
  • the transceivers (106, 206) of FIG. 1 may perform transmission and reception operations of signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.11a/b/g/n/ac/ax/be/bn, etc.).
  • signals e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.11a/b/g/n/ac/ax/be/bn, etc.
  • operations in which various STAs generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals may be performed in the processors (102, 202) of FIG. 1.
  • an example of an operation for generating a transmission/reception signal or performing data processing or operation in advance for a transmission/reception signal may include 1) an operation for determining/obtaining/configuring/computing/decoding/encoding bit information of a field (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU, 2) an operation for determining/configuring/obtaining time resources or frequency resources (e.g., subcarrier resources) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining/configuring/obtaining a specific sequence (e.g., a pilot sequence, an STF/LTF sequence, an extra sequence applied to SIG) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 4) a power control operation and/or a power saving operation applied to an STA, 5) an operation related to determining/obtaining/obtaining
  • various information e.g., information related to fields/subfields/control fields/parameters/power, etc.
  • various information e.g., information related to fields/subfields/control fields/parameters/power, etc.
  • various STAs for determining/acquiring/configuring/computing/decoding/encoding transmission/reception signals can be stored in the memory (104, 204) of FIG. 1.
  • downlink refers to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs/packets/signals, etc. can be transmitted and received through the downlink.
  • the transmitter may be part of an AP STA, and the receiver may be part of a non-AP STA.
  • Uplink refers to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs/packets/signals, etc. can be transmitted and received through the uplink.
  • the transmitter may be part of a non-AP STA, and the receiver may be part of an AP STA.
  • FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.
  • a Basic Service Set corresponds to a basic building block of a wireless LAN.
  • FIG. 2 illustrates, by way of example, the existence of two BSSs (BSS1 and BSS2) and the inclusion of two STAs as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2).
  • the oval representing a BSS in FIG. 2 can also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA).
  • BSA Basic Service Area
  • an IBSS can have a minimal form consisting of only two STAs.
  • BSS1 consisting of only STA1 and STA2
  • BSS2 consisting of only STA3 and STA4
  • IBSS Independent BSS
  • Such a configuration is possible when the STAs can communicate directly without an AP.
  • a LAN can be configured when needed rather than being planned in advance, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems (DS) is not permitted, forming a self-contained network.
  • DS distributed systems
  • An STA's membership in a BSS can dynamically change, for example, when an STA is turned on or off, or when an STA enters or leaves a BSS area.
  • an STA can join the BSS using a synchronization process.
  • an STA To access all services in the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may involve the use of a Distribution System Service (DSS).
  • DSS Distribution System Service
  • the direct STA-to-STA distance can be limited by PHY performance. While this distance limit may be sufficient in some cases, communication between STAs over longer distances may be required in other cases.
  • a distributed system can be configured.
  • DS refers to a structure in which BSSs are interconnected.
  • a BSS may exist as an extended component of a network composed of multiple BSSs, as illustrated in Figure 2.
  • DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM).
  • DSM distributed system medium
  • WM Wireless Medium
  • DSM can be logically distinguished.
  • Each logical medium is used for a different purpose and by different components. These media are neither limited to being identical nor limited to being different.
  • This logical difference between multiple media explains the flexibility of the WLAN architecture (DS architecture or other network architectures).
  • the WLAN architecture can be implemented in various ways, and the physical characteristics of each implementation can independently specify the WLAN architecture.
  • a DS can support mobile devices by providing seamless integration of multiple BSSs and the logical services necessary to handle addresses to destinations. Additionally, a DS may further include a component called a portal, which acts as a bridge for connecting wireless LANs to other networks (e.g., IEEE 802.X).
  • a portal acts as a bridge for connecting wireless LANs to other networks (e.g., IEEE 802.X).
  • An AP is an entity that enables access to a DS through a WM for associated non-AP STAs and also has the functionality of an STA. Data movement between a BSS and a DS can be performed through an AP.
  • STA2 and STA3 illustrated in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS.
  • all APs are basically STAs, all APs are addressable entities.
  • the address used by an AP for communication on a WM and the address used by an AP for communication on a DSM do not necessarily have to be the same.
  • a BSS consisting of an AP and one or more STAs can be referred to as an infrastructure BSS.
  • Data transmitted from one of the STA(s) associated with an AP to the STA address of that AP may always be received on an uncontrolled port and processed by an IEEE 802.1X port access entity.
  • the transmitted data (or frame) may be forwarded to the DS.
  • an extended service set may be established to provide wider coverage.
  • An ESS is a network of arbitrary size and complexity, consisting of DSs and BSSs.
  • An ESS may correspond to a set of BSSs connected to a DS. However, an ESS does not include a DS.
  • An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs within an ESS can communicate with each other, and mobile STAs can move from one BSS to another (within the same ESS) transparently to the LLC.
  • APs within an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is the identifier of the BSS.
  • BSSs can be partially overlapping, which is commonly used to provide continuous coverage. BSSs can also be physically disconnected, and there is no logical distance limit between them. BSSs can also be physically co-located, which can be used to provide redundancy.
  • IBSS or ESS networks can physically co-exist with one (or more) ESS networks. This can occur in cases where an ad-hoc network operates at the same location as an ESS network, where physically overlapping wireless networks are configured by different organizations, or where two or more different access and security policies are required at the same location.
  • FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.
  • the link setup process can also be referred to as the session initiation process or session setup process.
  • the discovery, authentication, association, and security setup processes of the link setup process can be collectively referred to as the association process.
  • the STA may perform a network discovery operation.
  • This network discovery operation may include scanning operations by the STA. That is, for the STA to access a network, it must search for available networks. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning.
  • Scanning methods include active scanning and passive scanning.
  • Figure 3 illustrates a network discovery operation including an active scanning process as an example.
  • active scanning an STA performing scanning transmits a probe request frame to discover any APs in the vicinity while moving between channels and waits for a response.
  • the responder transmits a probe response frame in response to the STA that transmitted the probe request frame.
  • the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned.
  • the AP transmits the beacon frame, so the AP becomes the responder.
  • the STAs within the IBSS take turns transmitting beacon frames, so the responder is not fixed.
  • an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests/responses on channel 2) in the same manner.
  • the next channel e.g., channel 2
  • scanning i.e., transmitting and receiving probe requests/responses on channel 2
  • the scanning operation can also be performed in a passive scanning manner.
  • passive scanning the STA performing the scanning moves between channels and waits for a beacon frame.
  • a beacon frame is one of the management frames defined in IEEE 802.11. It announces the existence of a wireless network and is periodically transmitted so that the STA performing the scanning can find the wireless network and participate in the wireless network.
  • the AP performs the role of periodically transmitting the beacon frame
  • the IBSS the STAs within the IBSS take turns transmitting the beacon frame.
  • the STA performing the scanning receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel.
  • the STA receiving the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel to perform scanning on the next channel in the same manner. Comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.
  • step S320 After the STA discovers the network, an authentication process may be performed in step S320.
  • This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below.
  • the authentication process involves the STA sending an authentication request frame to the AP, and the AP responding by sending an authentication response frame to the STA.
  • the authentication frame used for the authentication request/response corresponds to a management frame.
  • the authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group. These are just some examples of information that may be included in an authentication request/response frame, and may be replaced with other information or include additional information.
  • RSN Robust Security Network
  • An STA can send an authentication request frame to an AP.
  • the AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame.
  • the AP can provide the result of the authentication process to the STA via an authentication response frame.
  • an association process may be performed in step S330.
  • the association process includes a process in which the STA transmits an association request frame to the AP, and in response, the AP transmits an association response frame to the STA.
  • the association request frame may include information about various capabilities, a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, an RSN, a mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, interworking service capabilities, etc.
  • the association response frame may include information about various capabilities, a status code, an Association ID (AID), supported rates, an Enhanced Distributed Channel Access (EDCA) parameter set, a Received Channel Power Indicator (RCPI), a Received Signal to Noise Indicator (RSNI), a mobility domain, a timeout interval (e.g., an association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a Quality of Service (QoS) map, etc.
  • AID Association ID
  • EDCA Enhanced Distributed Channel Access
  • RCPI Received Channel Power Indicator
  • RSNI Received Signal to Noise Indicator
  • timeout interval e.g., an association comeback time
  • overlapping BSS scan parameters e.g.,
  • a security setup process may be performed in step S340.
  • the security setup process in step S340 may be referred to as an authentication process through a Robust Security Network Association (RSNA) request/response
  • the authentication process in step S320 may be referred to as a first authentication process
  • the security setup process in step S340 may also be referred to simply as an authentication process.
  • RSNA Robust Security Network Association
  • the security setup process of step S340 may include, for example, a process of establishing a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame. Furthermore, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.
  • EAPOL Extensible Authentication Protocol over LAN
  • FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.
  • the basic access mechanism of MAC is Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA).
  • CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
  • DCF Distributed Coordination Function
  • the AP and/or STA may perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time period (e.g., a DCF Inter-Frame Space (DIFS)) before starting transmission. If the sensing result determines that the medium is in an idle state, the AP and/or STA may start transmitting frames through the medium.
  • CCA Clear Channel Assessment
  • DIFS DCF Inter-Frame Space
  • the AP and/or STA may not start its own transmission, but may wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit frames.
  • a delay period e.g., a random backoff period
  • multiple STAs are expected to attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.
  • the IEEE 802.11 MAC protocol provides the Hybrid Coordination Function (HCF).
  • the HCF is based on the DCF and the Point Coordination Function (PCF).
  • the PCF is a polling-based synchronous access method that periodically polls all receiving APs and/or STAs to ensure that they receive data frames.
  • the HCF has the Enhanced Distributed Channel Access (EDCA) and the HCF Controlled Channel Access (HCCA).
  • EDCA is a contention-based access method for a provider to provide data frames to multiple users, while the HCCA uses a non-contention-based channel access method that utilizes a polling mechanism.
  • the HCF includes a medium access mechanism to improve the Quality of Service (QoS) of the wireless LAN, and can transmit QoS data in both the Contention Period (CP) and the Contention Free Period (CFP).
  • QoS Quality of Service
  • a random backoff period When an occupied/busy medium changes to an idle state, multiple STAs may attempt to transmit data (or frames). To minimize collisions, each STA may select a random backoff count, wait for the corresponding slot time, and then attempt to transmit.
  • the random backoff count has a pseudo-random integer value and may be determined as one of the values in the range of 0 to CW.
  • CW is a contention window parameter value.
  • the CW parameter is initially given a value of CWmin, but may double the value in case of a transmission failure (e.g., if an ACK for a transmitted frame is not received).
  • the STA continues to monitor the medium while counting down the backoff slots according to the determined backoff count value. If the medium is monitored as occupied, the countdown stops and waits. When the medium becomes idle, the remaining countdown resumes.
  • STA3 when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit a frame if it confirms that the medium is idle for DIFS. The remaining STAs monitor the medium for occupied/busy states and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can count down the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS if the medium is monitored as idle. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value.
  • this example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission.
  • STA1 and STA5 briefly stop counting down and wait while STA2 occupies the medium.
  • STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, they can start transmitting frames after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time is shorter than STA1's, STA5 starts transmitting frames. While STA2 occupies the medium, STA4 may also have data to transmit.
  • STA4 From STA4's perspective, when the medium becomes idle, it waits for DIFS, counts down according to its selected random backoff count value, and then starts transmitting frames.
  • the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failure in data transmission. In this case, STA4 and STA5 can select a random backoff count value and perform a countdown after doubling the CW value.
  • STA1 waits while the medium is occupied by transmissions from STA4 and STA5, and when the medium becomes idle, it waits for DIFS and can start transmitting frames after the remaining backoff time elapses.
  • a data frame is a frame used for transmitting data forwarded to a higher layer, and can be transmitted after a backoff performed after DIFS elapses from when the medium becomes idle.
  • a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS elapses, such as DIFS or PIFS (Point coordination function IFS).
  • Subtype frames of a management frame include a beacon, an association request/response, a re-association request/response, a probe request/response, and an authentication request/response.
  • a control frame is a frame used to control access to the medium.
  • the subtype frames of the control frame include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), Null Data Packet Announcement (NDP), and Trigger.
  • RTS Request-To-Send
  • CTS Clear-To-Send
  • ACK Acknowledgment
  • PS-Poll Power Save-Poll
  • Block ACK Block ACK
  • BlockACKReq Block ACK Request
  • NDP Null Data Packet Announcement
  • Trigger Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after a backoff performed after the DIFS (Direct Inverse Frame Stop) has elapsed, and if it is a response frame to the previous frame, it is transmitted without a backoff performed after the SIFS (short IFS).
  • DIFS Direct Inverse Frame Stop
  • SIFS Short IFS
  • a QoS (Quality of Service) STA can transmit a frame after a backoff performed after the AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed.
  • AIFS aromatic IFS
  • the frames for which AIFS[i] can be used can be data frames, management frames, and also control frames that are not response frames.
  • FIG. 5 is a diagram for explaining a CSMA/CA-based frame transmission operation to which the present disclosure can be applied.
  • the CSMA/CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, in which STAs directly sense the medium.
  • Virtual carrier sensing is intended to address potential issues in medium access, such as the hidden node problem.
  • the MAC of an STA can utilize a Network Allocation Vector (NAV).
  • NAV Network Allocation Vector
  • the NAV is a value that an STA that is currently using or has the right to use the medium indicates to other STAs the remaining time until the medium becomes available. Therefore, the value set as NAV corresponds to the period during which the STA transmitting the frame is scheduled to use the medium, and an STA receiving the NAV value is prohibited from accessing the medium during that period.
  • the NAV can be set based on the value of the "duration" field in the MAC header of the frame.
  • STA1 wants to transmit data to STA2, and STA3 is in a position to overhear some or all of the frames transmitted and received between STA1 and STA2.
  • a mechanism using RTS/CTS frames may be applied.
  • STA3 may determine that the medium is idle based on carrier sensing results. That is, STA1 may correspond to a hidden node for STA3.
  • STA2 may correspond to a hidden node for STA3.
  • STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.
  • STA1 can determine whether a channel is occupied through carrier sensing.
  • STA1 can determine channel occupancy idleness based on the energy level or signal correlation detected in the channel.
  • STA1 can determine the channel occupancy status using a network allocation vector (NAV) timer.
  • NAV network allocation vector
  • STA1 can transmit an RTS frame to STA2 after performing a backoff if the channel is idle during the DIFS.
  • STA2 can transmit a CTS frame, which is a response to the RTS frame, to STA1 after an SIFS if it receives the RTS frame.
  • STA3 can use the duration information contained in the RTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame).
  • STA3 can use the duration information contained in the CTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame).
  • STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 does not attempt channel access until the NAV timer expires.
  • STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the CTS frame is completely received. If STA2 successfully receives the data frame, it can transmit an ACK frame in response to the data frame to STA1 after SIFS.
  • STA3 can determine whether the channel is in use through carrier sensing if the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during the DIFS after the NAV timer expires, it can attempt channel access after a contention window (CW) based on a random backoff has elapsed.
  • CW contention window
  • FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.
  • the PHY layer can prepare an MPDU (MAC PDU) to be transmitted based on an instruction or primitive (meaning a set of instructions or parameters) from the MAC layer. For example, when a command requesting the start of transmission of the PHY layer is received from the MAC layer, the PHY layer can switch to transmission mode and transmit the information (e.g., data) provided by the MAC layer in the form of a frame. In addition, when the PHY layer detects a valid preamble of the received frame, it monitors the header of the preamble and sends a command to the MAC layer notifying the start of reception of the PHY layer.
  • MPDU MPDU
  • PPDU PHY layer Protocol Data Unit
  • a basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field.
  • STF Short Training Field
  • LTF Long Training Field
  • SIG SIGNAL
  • Data field e.g., Data field
  • PPDU format may consist of only the Legacy-STF (L-STF), Legacy-LTF (L-LTF), Legacy-SIG (L-SIG) fields, and a Data field.
  • RL-SIG RL-SIG
  • U-SIG non-legacy SIG field
  • non-legacy STF non-legacy LTF
  • xx-SIG xx-SIG
  • xx-LTF e.g., xx is HT, VHT, HE, EHT, etc.
  • STF is a signal for signal detection, AGC (Automatic Gain Control), diversity selection, and precise time synchronization
  • LTF is a signal for channel estimation, frequency error estimation, etc.
  • STF and LTF can be said to be signals for synchronization and channel estimation of the OFDM physical layer.
  • the SIG field may include various information related to PPDU transmission and reception.
  • the L-SIG field may consist of 24 bits and may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field.
  • the RATE field may include information about the modulation and coding rate of data.
  • the 12-bit Length field may include information about the length or time duration of the PPDU.
  • the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3.
  • the value of the Length field can be determined as a multiple of 3 + 1 or a multiple of 3 + 2.
  • the data field may include a SERVICE field, a Physical layer Service Data Unit (PSDU), a PPDU TAIL bit, and, if necessary, padding bits.
  • PSDU Physical layer Service Data Unit
  • PPDU TAIL bit may be used to synchronize the descrambler at the receiving end.
  • the PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated/used by upper layers.
  • the PPDU TAIL bit may be used to return the encoder to a 0 state.
  • the padding bit may be used to adjust the length of the data field to a predetermined unit.
  • MAC PDUs are defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS).
  • a MAC frame is composed of MAC PDUs and can be transmitted/received through the PSDU in the data portion of the PPDU format.
  • the MAC header includes a Frame Control field, a Duration/ID field, an Address field, etc.
  • the Frame Control field may include control information required for frame transmission/reception.
  • the Duration/ID field may be set to a time for transmitting the corresponding frame, etc.
  • the Address subfields may indicate the receiver address, transmitter address, destination address, and source address of the frame, and some Address subfields may be omitted. For specific details of each subfield of the MAC header, including the Sequence Control, QoS Control, and HT Control subfields, refer to the IEEE 802.11 standard document.
  • NDP Null-Data PPDU
  • L-STF L-STF
  • L-LTF L-SIG fields
  • non-legacy SIG non-legacy STF
  • non-legacy LTF in the general PPDU format, and does not include the remaining part (i.e., data field).
  • FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.
  • the basic PPDU format (IEEE 802.11a/g) includes L-LTF, L-STF, L-SIG, and Data fields.
  • the basic PPDU format can also be referred to as the non-HT PPDU format (Fig. 7(a)).
  • the HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format.
  • the HT PPDU format illustrated in Fig. 7(b) may be referred to as an HT-mixed format.
  • an HT-greenfield format PPDU may be defined, which corresponds to a format that does not include L-STF, L-LTF, and L-SIG, but consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).
  • VHT PPDU format includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format (Fig. 7(c)).
  • HE PPDU format (IEEE 802.11ax) additionally includes RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in addition to the basic PPDU format (Fig. 7(d)).
  • RL-SIG Repeated L-SIG
  • HE-SIG-A HE-SIG-B
  • HE-STF HE-LTF(s)
  • PE Packet Extension
  • some fields may be excluded or their lengths may vary.
  • the HE-SIG-B field is included in the HE PPDU format for multi-users (MUs), but the HE-SIG-B is not included in the HE PPDU format for single users (SUs).
  • the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8 microseconds (us).
  • the HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field can vary to 16us.
  • the RL-SIG can be configured identically to the L-SIG.
  • the receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU, described later, based on the presence of the RL-SIG.
  • the EHT PPDU format may include the EHT MU (multi-user) PPDU of FIG. 7(e) and the EHT TB (trigger-based) PPDU of FIG. 7(f).
  • the EHT PPDU format is similar to the HE PPDU format in that it includes an RL-SIG following an L-SIG, but may include a U (universal)-SIG, an EHT-SIG, an EHT-STF, and an EHT-LTF following the RL-SIG.
  • the EHT MU PPDU in FIG. 7(e) corresponds to a PPDU that carries one or more data (or PSDUs) for one or more users. That is, the EHT MU PPDU can be used for both SU transmission and MU transmission.
  • the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.
  • the EHT TB PPDU of Fig. 7(f) omits the EHT-SIG compared to the EHT MU PPDU.
  • An STA that has received a trigger for UL MU transmission e.g., a trigger frame or TRS (triggered response scheduling)
  • TRS triggered response scheduling
  • L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated to allow legacy STAs to attempt demodulation and decoding, and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields.
  • EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated to allow STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and/or EHT-SIG) and obtained the information contained in the fields, and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.
  • non-legacy SIGs e.g., U-SIG and/or EHT-SIG
  • a predetermined subcarrier frequency interval e.g., 78.125 kHz
  • the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields may be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, Data, and PE fields may be referred to as HE modulation fields.
  • the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields may be referred to as pre-VHT modulation fields
  • the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields may be referred to as VHT modulation fields.
  • the U-SIG included in the EHT PPDU format of FIG. 7 can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG can have a duration of 4 us, and the U-SIG can have a total duration of 8 us. Each symbol of the U-SIG can be used to transmit 26 bits of information. For example, each symbol of the U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.
  • U-SIGs can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be duplicated in 20MHz units. That is, four identical U-SIGs can be included in an 80MHz PPDU. When the bandwidth exceeds 80MHz, for example, for a 160MHz PPDU, the U-SIGs in the first 80MHz unit and the U-SIGs in the second 80MHz unit can be different.
  • a uncoded bits may be transmitted via U-SIG, and a first symbol of U-SIG (e.g., a U-SIG-1 symbol) may transmit the first X bits of information out of a total A bits of information, and a second symbol of U-SIG (e.g., a U-SIG-2 symbol) may transmit the remaining Y bits of information out of a total A bits of information.
  • the A bits of information (e.g., 52 uncoded bits) may include a CRC field (e.g., a field of 4 bits in length) and a tail field (e.g., a field of 6 bits in length). The tail field may be used to terminate the trellis of the convolutional decoder and may be set to 0, for example.
  • the A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits.
  • U-SIG can be included in a new PPDU format (e.g., UHR PPDU format) not shown in FIG. 7, and in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-dependent bits can be different.
  • the size of the version-independent bits of U-SIG can be fixed or variable.
  • the version-independent bits can be assigned only to U-SIG-1 symbols, or to both U-SIG-1 symbols and U-SIG-2 symbols.
  • the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.
  • the version-independent bits of the U-SIG may include a 3-bit PHY version identifier, which may indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted and received PPDUs.
  • the version-independent bits of the U-SIG may include a 1-bit UL/DL flag field. The first value of the 1-bit UL/DL flag field relates to UL communication, and the second value of the UL/DL flag field relates to DL communication.
  • the version-independent bits of the U-SIG may include information about the length of a transmission opportunity (TXOP) and information about a BSS color ID.
  • TXOP transmission opportunity
  • the version-dependent bits of the U-SIG may contain information that directly or indirectly indicates the type of PPDU (e.g., SU PPDU, MU PPDU, TB PPDU, etc.).
  • the U-SIG may further include information about bandwidth, information about the MCS technique applied to the non-legacy SIG (e.g., EHT-SIG or UHR-SIG), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique to achieve an effect similar to frequency diversity by reusing the same signal on two subcarriers) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, information about whether the non-legacy SIG is generated across the entire band, etc.
  • DCM dual carrier modulation
  • Some of the information required for transmitting and receiving a PPDU may be included in the U-SIG and/or the non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.).
  • information about the type of the non-legacy LTF/STF e.g., EHT-LTF/EHT-STF or UHR-LTF/UHR-STF, etc.
  • information about the length of the non-legacy LTF and the cyclic prefix (CP) length e.g., EHT-LTF/EHT-STF or UHR-LTF/UHR-STF, etc.
  • information about the length of the non-legacy LTF and the cyclic prefix (CP) length e.g., information about the guard interval (GI) applicable to the non-legacy LTF
  • information about preamble puncturing applicable to the PPDU e.g., information about resource unit (RU) allocation, etc.
  • RU resource unit
  • Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the PPDU's bandwidth.
  • the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc.
  • preamble puncturing may be applied to a PPDU bandwidth greater than a certain size.
  • non-legacy SIGs such as HE-SIG-B and EHT-SIG may include control information for the receiving STA.
  • the non-legacy SIG may be transmitted over at least one symbol, and each symbol may have a length of 4 us.
  • Information regarding the number of symbols used for the EHT-SIG may be included in a previous SIG (e.g., HE-SIG-A, U-SIG, etc.).
  • Non-legacy SIGs such as HE-SIG-B and EHT-SIG, may contain common fields and user-specific fields. Common and user-specific fields may be coded separately.
  • common fields may be omitted.
  • non-OFDMA orthogonal frequency multiple access
  • common fields may be omitted, and multiple STAs may receive PPDUs (e.g., data fields of PPDUs) over the same frequency band.
  • PPDUs e.g., data fields of PPDUs
  • multiple users may receive PPDUs (e.g., data fields of PPDUs) over different frequency bands.
  • the number of user-specific fields can be determined based on the number of users.
  • a single user block field can contain up to two user fields.
  • Each user field can be associated with either MU-MIMO allocation or non-MU-MIMO allocation.
  • the common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, and the length of the Tail bits may be determined as 6 bits and set to 000000.
  • the common field may include RU allocation information.
  • the RU allocation information may include information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.
  • An RU can contain multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA techniques. RUs can also be defined when transmitting signals to a single STA. Resources can be allocated on an RU basis for non-legacy STFs, non-legacy LTFs, and data fields.
  • an applicable RU size can be defined.
  • the RU may be defined identically or differently for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.).
  • the RU arrangements of HE PPDU and EHT PPDU may be different.
  • the applicable RU size, RU number, RU position, DC (direct current) subcarrier position and number, null subcarrier position and number, guard subcarrier position and number, etc. for each PPDU bandwidth can be referred to as a tone plan.
  • a tone plan for a wide bandwidth can be defined in the form of multiple repetitions of a low bandwidth tone plan.
  • RUs of different sizes can be defined, such as 26-ton RU, 52-ton RU, 106-ton RU, 242-ton RU, 484-ton RU, 996-ton RU, 2X996-ton RU, 4X996-ton RU, etc.
  • a multiple RU is distinguished from multiple individual RUs and corresponds to a group of subcarriers consisting of multiple RUs.
  • one MRU can be defined as 52+26-tons, 106+26-tons, 484+242-tons, 996+484-tons, 996+484+242-tons, 2X996+484-tons, 3X996-tons, or 3X996+484-tons.
  • multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.
  • the specific size of an RU may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. Furthermore, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, etc.) in the present disclosure, the number of RUs may vary depending on the RU size.
  • a given bandwidth e.g. 20, 40, 80, 160, 320 MHz, etc.
  • each field in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by those names. Furthermore, the examples of the present disclosure can be applied not only to the PPDU format exemplified in FIG. 7, but also to a new PPDU format in which some fields are excluded and/or some fields are added based on the PPDU formats of FIG. 7.
  • FIGS. 8 to 10 are diagrams for explaining examples of resource units of a wireless LAN system to which the present disclosure can be applied.
  • An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on OFDMA techniques. An RU may also be defined when transmitting signals to a single STA. An RU may be used for the STF, LTF, and data fields of a PPDU.
  • RUs corresponding to different numbers of tones may be used to configure some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X represents HE, EHT, etc.).
  • X represents HE, EHT, etc.
  • resources may be allocated in units of RUs illustrated for the X-STF, X-LTF, and Data fields.
  • Figure 8 is a diagram showing an exemplary arrangement of resource units (RUs) used on a 20 MHz band.
  • 26 units i.e., units corresponding to 26 tones
  • Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band.
  • seven DC tones may be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on each side of the DC band.
  • 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for an STA or a user.
  • the RU arrangement of Fig. 8 can be utilized not only in situations for multiple users (MUs) but also in situations for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of Fig. 8. In this case, three DC tones can be inserted.
  • RUs of various sizes such as 26-RU, 52-RU, 106-RU, and 242-RU, are exemplified, but the specific sizes of these RUs may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. In addition, in the present disclosure, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...), the number of RUs may vary depending on the RU size. In the examples of FIG. 9 and/or FIG. 10 described below, the fact that the size and/or number of RUs may be changed is the same as the example of FIG. 8.
  • Figure 9 is a diagram showing an exemplary arrangement of resource units (RUs) used on a 40 MHz band.
  • the example of FIG. 9 may also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc.
  • five DC tones may be inserted at the center frequency, 12 tones may be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones may be used as a guard band in the rightmost band of the 40 MHz band.
  • 484-RU when used for a single user, 484-RU may be used.
  • Figure 10 is a diagram showing an exemplary arrangement of resource units (RUs) used on the 80 MHz band.
  • RUs resource units
  • the example of FIG. 10 may also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc.
  • the RU arrangement of HE PPDU and EHT PPDU may be different, and the example of FIG. 10 shows an example of the RU arrangement for 80MHz EHT PPDU.
  • 12 tones are used as guard bands in the leftmost band of the 80MHz band, and 11 tones are used as guard bands in the rightmost band of the 80MHz band, which is the same for HE PPDU and EHT PPDU.
  • the EHT PPDU has 23 DC tones inserted into the DC band and one 26-RU corresponding to 13 tones on each side of the DC band.
  • the EHT PPDU has five null subcarriers.
  • one 484-RU does not contain a null subcarrier, but in the EHT PPDU, one 484-RU contains five null subcarriers.
  • 996-RU when used for a single user, 996-RU can be used, in which case the insertion of 5 DC tones is common in both HE PPDU and EHT PPDU.
  • An EHT PPDU of 160MHz or higher may be configured with multiple 80MHz subblocks as shown in FIG. 10.
  • the RU layout for each 80MHz subblock may be the same as the RU layout of the 80MHz EHT PPDU as shown in FIG. 10. If an 80MHz subblock of a 160MHz or 320MHz EHT PPDU is not punctured and the entire 80MHz subblock is used as part of an RU or MRU (Multiple RU), the 80MHz subblock may use 996-RU as shown in FIG. 10.
  • an MRU corresponds to a group of subcarriers (or tones) composed of multiple RUs, and the multiple RUs constituting an MRU may be RUs of the same size or different sizes.
  • a single MRU may be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2X996+484-tones, 3X996-tones, or 3X996+484-tones.
  • the multiple RUs constituting one MRU may correspond to RUs of small size (e.g., 26, 52, 106) or RUs of large size (e.g., 242, 484, 996, etc.). That is, a single MRU containing both small-sized RUs and large-sized RUs may not be configured/defined. Furthermore, multiple RUs constituting a single MRU may or may not be consecutive in the frequency domain.
  • the 80MHz subblock may use RU layouts other than the 996-tone RUs.
  • the RU of the present disclosure can be used for uplink (UL) and/or downlink (DL) communication.
  • an STA e.g., an AP
  • transmitting a trigger can allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA and a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA through trigger information (e.g., a trigger frame or triggered response scheduling (TRS)).
  • trigger information e.g., a trigger frame or triggered response scheduling (TRS)
  • the first STA can transmit a first trigger-based (TB) PPDU based on the first RU
  • the second STA can transmit a second TB PPDU based on the second RU.
  • the first/second TB PPDU can be transmitted to the AP in the same time interval.
  • an STA e.g., an AP transmitting a DL MU PPDU may allocate a first RU (e.g., 26/52/106/242-RU, etc.) to a first STA, and a second RU (e.g., 26/52/106/242-RU, etc.) to a second STA.
  • a first RU e.g., 26/52/106/242-RU, etc.
  • a second RU e.g., 26/52/106/242-RU, etc.
  • the transmitting STA may transmit X-STF (e.g., X is HE, EHT, etc.), X-LTF, and Data fields for the first STA through the first RU within one MU PPDU, and may transmit X-STF, X-LTF, and Data fields for the second STA through the second RU.
  • X-STF e.g., X is HE, EHT, etc.
  • X-LTF e.g., X is HE, EHT, etc.
  • Data fields for the first STA through the first RU within one MU PPDU and may transmit X-STF, X-LTF, and Data fields for the second STA through the second RU.
  • Information about the arrangement of RUs may be signaled through an X-SIG (e.g., X is HE, EHT, U) field of the X-PPDU format.
  • X-SIG e.g., X is HE, EHT
  • PSD power spectral density
  • the PSD limitation may be -1dBm/MHz.
  • the maximum transmit (Tx) power may be approximately 6dBm.
  • a PSD restriction of 10 dBm/MHz may apply in the EU/China/Japan/Korea in the 2.4 GHz band. This would result in a maximum Tx power of approximately 17 dBm for a conventional 52-tone RU.
  • Bypassing the PSD restriction in the 5 GHz band would allow for higher transmit power.
  • the maximum transmit power for a conventional 52-tone RU is 24 dBm, which is still 6 dBm below the maximum allowable effective isotropic radiated power (EIRP) of 30 dBm.
  • EIRP effective isotropic radiated power
  • Overcoming PSD limitations can increase transmit power, thereby improving spectral efficiency or extending range.
  • DRU distributed RU
  • RRU regular RU
  • STAs transmitting on DRUs can use higher power. For example, a 52-tone DRU across 80 MHz has only one tone per MHz, whereas a 52-tone RRU has approximately 13 tones per MHz. Assuming a PSD limit of -1 dBm/MHz in the 6 GHz LPI band, using a DRU increases the transmit power by approximately 11 dB for a 52-tone RU. This increased transmit power allows for a higher MCS and longer range.
  • FIG. 11 is a drawing illustrating examples of DRUs to which the present disclosure can be applied.
  • STA1 transmits on DRU1
  • STA2 transmits on DRU2
  • STA3 transmits on DRU3.
  • Each STA can apply a transmission power boost by using a DRU.
  • the DRU applies higher transmission power to all tones, and thus, spectral efficiency can be significantly improved. In this way, the DRU can be applied particularly usefully in UL-OFDMA.
  • APs can also utilize DRUs.
  • the AP may use only some of DRUs (DRU1, DRU2, and DRU3) to transmit DL-OFDMA to STAs, in which case the transmit power boost due to the use of DRUs may be applied.
  • tones within a single DRU can be distributed as far apart as possible.
  • a DRU containing one tone per MHz may be considered optimal.
  • the size of a DRU (or the number of available tones contained in a DRU, i.e., the number of tones excluding unusable tones such as null tones, guard tones, and DC tones) can be defined to be the same as the size of an RRU (or the number of available tones contained in an RRU). This can minimize the impact on various technologies that are already defined based on RRUs.
  • the table below shows examples of achievable power boost (in dB) for various DRUs distributed over different bandwidths.
  • the examples in the table below assume the 6 GHz LPI band, and power boost can also be achieved in the 2.4 GHz and 5 GHz bands in other regions.
  • the overall performance can be improved by approximately 8.13 dB compared to when each user uses a 106-tone RRU.
  • the PSD limitation can be overcome and significant gains can be obtained.
  • FIG. 12 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.
  • a trigger frame may allocate resources for the transmission of one or more TB PPDUs and request the transmission of TB PPDUs.
  • the trigger frame may also include other information required by the STA transmitting the TB PPDU in response.
  • the trigger frame may include common information and a user information list field in the frame body.
  • the common information field may include information that is common to one or more TB PPDU transmissions requested by a trigger frame, such as trigger type, UL length, presence of a subsequent trigger frame (e.g., More TF), whether CS (channel sensing) is required, UL BW (bandwidth), etc.
  • Fig. 12 illustrates an example of an EHT variant common information field format.
  • the 4-bit trigger type subfield can have values from 0 to 15. Among them, the values 0, 1, 2, 3, 4, 5, 6, and 7 of the trigger type subfield are defined to correspond to basic, Beamforming Report Poll (BFRP), multi user-block acknowledgement request (MU-BAR), multi user-request to send (MU-RTS), Buffer Status Report Poll (BSRP), groupcast with retries (GCR), MU-BAR, Bandwidth Query Report Poll (BQRP), and NDP Feedback Report Poll (NFRP), respectively, and the values 8 to 15 are defined as reserved.
  • 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
  • BQRP Bandwidth Query Report Poll
  • NFRP NDP Feedback Report Poll
  • the trigger dependent common info subfield may include information that is optionally included based on the trigger type.
  • a special user info field may be included within the trigger frame.
  • the special user info field does not contain user-specific information, but rather extended common information not provided in the common information field.
  • a user information list contains zero or more user information fields.
  • Figure 12 illustrates an example of an EHT variant user information field format.
  • the AID12 subfield basically indicates that it is a user information field for an STA with the corresponding AID.
  • the AID12 field has a predetermined specific value, it may be utilized for other purposes, such as allocating a random access (RA)-RU, or being configured in the form of a special user information field.
  • the special user information field is a user information field that does not contain user-specific information, but contains extended common information not provided in the common information field.
  • the special user information field can be identified by the AID12 value of 2007, and the special user information field flag subfield within the common information field can indicate whether the special user information field is included.
  • the RU allocation subfield can indicate the size and location of an RU/MRU.
  • the RU allocation subfield can be interpreted together with the PS160 (primary/secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc.
  • mapping of B7-B1 of the RU Assignment subfield can be defined together with the settings of the B0 and PS160 subfields of the RU Assignment subfield as shown in Table 2 below.
  • Table 2 shows an example of encoding of the PS160 subfield and the RU Assignment subfield of the EHT Variant User Information Field.
  • B0 of the RU Allocation subfield When B0 of the RU Allocation subfield is set to 0, it may indicate that the RU/MRU allocation is applied to the primary 80 MHz channel, and when its value is set to 1, it may indicate that the RU allocation is applied to the secondary 80 MHz channel of the primary 160 MHz.
  • B0 of the RU Allocation subfield When B0 of the RU Allocation subfield is set to 0, it may indicate that the RU/MRU allocation is applied to the lower 80 MHz of the secondary 160 MHz, and when its value is set to 1, it may indicate that the RU allocation is applied to the upper 80 MHz of the secondary 160 MHz.
  • the values of PS160, B0, X0, and X1 can be set to 0.
  • the values of PS160, B0, X0, and X1 can be set as shown in Table 3.
  • These settings represent the absolute frequency order for the primary and secondary 80 MHz and 160 MHz channels. The order from left to right represents the order from low frequency to high frequency.
  • the primary 80 MHz channel is represented as P80
  • the secondary 80 MHz channel is represented as S80
  • the secondary 160 MHz channel is represented as S160.
  • a DRU using distributed tones/subcarriers rather than an RRU using continuous tones/subcarriers can be applied.
  • tone plans for the 26-tone DRU, 52-tone DRU, and 106-tone DRU are specifically described with respect to the DRU tone plans at 20 MHz bandwidth/channel.
  • the DRU index (i.e., DRU n) or the nth DRU may correspond to a position in the frequency domain, or may be assigned regardless of the position in the frequency domain.
  • DRU index may correspond to a position in the frequency domain, or may be assigned regardless of the position in the frequency domain.
  • a relatively low DRU index includes a relatively low tone/subcarrier, but the scope of the present disclosure is not limited thereto, and the DRU index may be assigned in various ways to distinguish different DRUs.
  • the subcarrier index is assumed to correspond to the position in the frequency domain, assuming that the index of the DC subcarrier is 0, and the term subcarrier can be replaced with a tone.
  • '-a' means a tone with an index of -a, and the tone can be located to the left of the center of the bandwidth/channel (e.g., in a low frequency range relative to the center).
  • '+a' means a tone with an index of +a, and the tone can be located to the right of the center of the bandwidth/channel (e.g., in a high frequency range relative to the center).
  • 'a:b:c' means tones at positions corresponding to b tone units, from a tone having an index a to a tone having an index c, and means that the tones can be assigned/designated to each DRU.
  • This embodiment describes various methods for defining a tone plan for a 26-tone DRU for a 20 MHz bandwidth/channel. Regarding the DRU tone plan for a 20 MHz bandwidth/channel, at least one of the following methods may be applied.
  • the following description assumes that the same size and number of DRUs as the existing 20MHz RRU tone plan are defined (excluding the 242-tone DRU).
  • the guard tones, null tones, and DC tones in the same number and positions as the existing ones may be based on the 20MHz tone plan of FIG. 8 described above.
  • a tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones, null tones, and DC tones as before.
  • the tones of each of the nine 26-tone DRUs can be allocated one tone at a time, from the lowest available tone to the highest available tone. This assumes that the existing guard tone, null tone, and DC tone are maintained.
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This approach may be implementation-efficient in that it uses the same null tone as the existing 20MHz tone plan (e.g., see Fig. 8).
  • a tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones and DC tones as before, plus four additional DC tones or null tones (e.g., [-5, -4, +4, +5]).
  • the tones of each of the nine 26-tone DRUs can be allocated one tone at a time, from the lowest available tone to the highest available tone. This assumes that the existing guard tones and DC tones are maintained, and four additional DC tones or null tones are considered.
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This method can be efficient in smoothing gain, etc., as it can obtain a relatively even tone plan. In addition, this method can be efficient in terms of DC offset, etc.
  • a tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones and DC tones as before, plus two additional guard tones and DC tones, or four null tones (e.g., [-122, -4, +4, +122] or [-4, -3, +3, +4]).
  • the tones of each of the nine 26-tone DRUs can be allocated one tone each, from the lowest available tone to the highest available tone. This assumes that the existing guard tones and DC tones are maintained, and two additional guard tones and DC tones, or four additional null tones, are considered.
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This method can be efficient in terms of smoothing gain, etc., as it can obtain a relatively even tone plan. Furthermore, this method may be suitable in terms of trade-offs when considering interference from adjacent channels and DC offset.
  • a tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones and DC tones as before, plus four additional guard tones or null tones (e.g., [-122, -121, +121, +122] or [-3, -2, +2, +3]).
  • the tones of each of the nine 26-tone DRUs can be allocated one tone at a time, from the lowest available tone to the highest available tone. This assumes that the existing guard tones and DC tones are maintained, and that four additional guard tones or null tones are considered.
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This method can be efficient in terms of smoothing gain, etc., as it can obtain a relatively even tone plan. Furthermore, this method can be efficient when considering interference from adjacent channels.
  • the tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones and DC tones as before, and an additional eight guard tones or null tones (e.g., [-122, -121, -120, -119, +119, +120, +121, +122]).
  • guard tones or null tones e.g., [-122, -121, -120, -119, +119, +120, +121, +122]
  • the tones of each of the nine 26-tone DRUs can be allocated one tone at a time, from the lowest available tone to the highest available tone. This assumes that the existing guard tones and DC tones (e.g., DC in non-OFDMA) are maintained, and an additional eight guard tones or null tones are considered.
  • DC tones e.g., DC in non-OFDMA
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This method can be efficient in terms of smoothing gain, etc., as it can obtain a relatively even tone plan. Furthermore, this method can be efficient when considering interference from adjacent channels.
  • a tone plan for a 26-tone DRU can be defined assuming the same number and locations of guard tones and DC tones as before, and an additional eight guard tones or null tones (e.g., [-122, -121, -120, -2, +2, +120, +121, +122]).
  • guard tones or null tones e.g., [-122, -121, -120, -2, +2, +120, +121, +122]
  • the tones of each of the nine 26-tone DRUs can be allocated one tone at a time, from the lowest available tone to the highest available tone. This assumes that the existing guard tones and DC tones (e.g., DC in non-OFDMA) are maintained, and an additional eight guard tones or null tones are considered.
  • DC tones e.g., DC in non-OFDMA
  • a specific tonnage plan for nine 26-ton DRUs based on this method could be as follows:
  • This method can be efficient in terms of smoothing gain, etc., as it can obtain a relatively even tone plan. Furthermore, this method can be efficient when considering interference from adjacent channels.
  • the tone plan of the method is applied as is to a specific 20MHz channel within a bandwidth/channel of 40MHz or more, there is a technical effect of reducing the number of overlapping 26-tone DRUs and guard tones of 40MHz bandwidth/channel, and also reducing the DC offset effect.
  • This embodiment describes a method for defining a tone plan for a 52-tone DRU for a 20 MHz bandwidth/channel.
  • a 52-tone DRU can be configured as a combination of two 26-tone DRUs (see, for example, Example 1) and can be defined as follows to maximize tones distribution.
  • This embodiment relates to a method for defining a tone plan for a 106-tone DRU for a 20 MHz bandwidth/channel.
  • a method for defining a tone plan for a 106-tone DRU for a 20 MHz bandwidth/channel With respect to the DRU tone plan for a 20 MHz bandwidth/channel, at least one of the following methods may be applied.
  • a 106-tone DRU can be configured by combining two 52-tone DRUs with two of the four null tones [-122, -69, +69, +122].
  • the power boosting gain cannot be maximized, and in particular, no power boosting gain may be obtained when assigning null tones of -69 and +69.
  • the present disclosure may be applied to a method of using a tone having an index of -3 or -2 instead of -69 as a sine tone, and using a tone having an index of +3 or +2 instead of +69.
  • These tones may correspond to tones used as DC tones in an OFDMA tone plan, or as data tones in a non-OFDMA tone plan.
  • two 106-tone DRUs can be defined as follows:
  • - 106-tone DRU 1 combination of 52-tone DRU 1, 52-tone DRU 3, null tone -3 or -2, and null tone +122
  • - 106-ton DRU 2 combination of 52-ton DRU 2, 52-ton DRU 4, null tone -122, and null tone +3 or +2
  • null tone +3 it may be efficient to assign null tone +3 to 106-tone DRU 2 when null tone -3 is assigned to 106-tone DRU 1.
  • null tone +2 it may be efficient to assign null tone +2 to 106-tone DRU 2 when null tone -2 is assigned to 106-tone DRU 1.
  • a 106-tone DRU can be configured with a combination of two 52-tone DRUs and either a DC tone or four null tones [-5, -4, +4, +5].
  • two 106-tone DRUs can be defined as follows:
  • a 106-tone DRU can be configured with two combinations of two 52-tone DRUs and either a guard tone/DC tone or four null tones [-122, -4, +4, +122] or [-4, -3, +3, +4].
  • two 106-tone DRUs can be defined as follows:
  • - 106-tone DRU 2 combination of 52-tone DRU 2, 52-tone DRU 4, null tone [-122, +4] or [-3, +4]
  • a 106-tone DRU can be configured with a combination of two 52-tone DRUs and two of the guard tones or four null tones [-122, -121, +121, +122] or [-3, -2, +2, +3] or [-121, -3, +3, +121].
  • two 106-tone DRUs can be defined as follows:
  • - 106-tone DRU 1 combination of 52-tone DRU 1, 52-tone DRU 3, null tone [-122, +121] or [-3, +2] or [-3, +121]
  • - 106-tone DRU 2 combination of 52-tone DRU 2, 52-tone DRU 4, null tone [-121, +122] or [-2, +3] or [-121, +3]
  • a 106-tone DRU can be configured with a combination of two 52-tone DRUs and either a guard tone or four null tones [-120, -119, +119, +120].
  • two 106-tone DRUs can be defined as follows:
  • a 106-tone DRU can be configured with a combination of two 52-tone DRUs and either a guard tone or four null tones [-120, -2, +2, +120] or [-121, -120, +120, +121].
  • two 106-tone DRUs can be defined as follows:
  • - 106-tone DRU 1 combination of 52-tone DRU 1, 52-tone DRU 3, null tone [-2, +120] or [-121, +120]
  • - 106-tone DRU 2 combination of 52-tone DRU 2, 52-tone DRU 4, null tone [-120, +2] or [-120, +121]
  • a method of generating various 52-tone DRUs by combining two arbitrary 26-tone DRUs rather than a fixed combination may be applied.
  • a method of generating various 106-tone DRUs by combining four arbitrary 26-tone DRUs rather than a fixed combination may be applied.
  • the method may be equally applied to the tone index of the 26-tone DRU defined in the aforementioned embodiment 1 as well as the tone index of the 26-tone DRU formed in a different manner.
  • additional tone combinations of the 106-tone DRU may be configured in the same manner as described in the aforementioned embodiment 3.
  • the method of generating DRUs in this manner can be usefully applied when DRUs shifted symbol-by-symbol are applied to obtain diversity gain (for example, when the tone index included in a specific DRU index in the first symbol is different from the tone index included in the same specific DRU index in the second symbol).
  • a predefined mapping rule between the 26-tone RRU index and the 26-tone DRU index may be applied.
  • the mapping rule may be that the DRU index-1 containing the lowest tone in the frequency domain is mapped to the RRU-1 containing the lowest tone, and then the DRU containing the next lowest tone is mapped sequentially in ascending order of the RRU index.
  • a 52-tone DRU or a 106-tone DRU can allocate and instruct the STA of multiple 26-tone RRU indexes based on the mapping rule. Accordingly, the STA can determine which 52-tone DRU or 106-tone DRU assigned to it contains tones included in which 26-tone DRUs.
  • 2/4 26-tone RRU indexes corresponding to 2/4 26-tone DRUs corresponding to 52-tone DRU/106-tone DRU can be indicated to one STA through RU allocation information, and the STA ID values included in the user information (e.g., the user field of the U-SIG/UHR-SIG field of a DL OFDMA PPDU (e.g., MU PPDU), or the UHR variant user information field of a trigger frame) corresponding to such 2/4 26-tone RRUs can be set to the same value as the ID of the corresponding STA.
  • the STA ID values included in the user information e.g., the user field of the U-SIG/UHR-SIG field of a DL OFDMA PPDU (e.g., MU PPDU), or the UHR variant user information field of a trigger frame
  • information indicating that a DRU is allocated, and/or information indicating whether the DRU allocated to the STA is the last of a plurality of 26-tone RRU indices may be defined in the user information (e.g., a user field of a U-SIG/UHR-SIG field of a DL OFDMA PPDU (e.g., an MU PPDU), or a UHR variant user information field of a trigger frame).
  • a user field of a U-SIG/UHR-SIG field of a DL OFDMA PPDU e.g., an MU PPDU
  • UHR variant user information field of a trigger frame e.g., a UHR variant user information field of a trigger frame.
  • the 52-tone DRU includes tones of two 26-tone DRUs in a fixed combination
  • the 106-tone DRU includes tones of two 52-tone DRUs in a fixed combination (or four 26-tone DRUs in a fixed combination)
  • by generalizing the DRU index and mapping it to each RRU index it is also possible to flexibly set a 26-tone DRU/52-tone DRU corresponding to a specific 52-tone DRU/106-tone DRU.
  • 26-tone DRU-a/b/c/d/e/f/g/h/i can be defined to correspond to 26-tone DRU-1/2/3/4/5/6/7/8/9 in any manner (for example, indices a to i and indices 1 to 9 correspond one-to-one, but the numeric indices corresponding to each alphabetic index are determined in ascending order or in any order).
  • the positions of the tones included in the 26-tone DRU may be applied in the examples of Embodiment 1 or in another manner.
  • 52-tone DRU-a/b/c/d and 106-tone DRU-a/b can be defined to correspond to combinations of lower-size DRU indices as in the examples below.
  • two additional tones for the 106-tone DRU can be defined based on the description in Example 3.
  • a gap between multiple lower-sized DRU indices corresponding to a single upper-sized DRU index may be utilized.
  • the value of this gap may be explicitly signaled to the STA, or may be implicitly signaled based on other information (e.g., bandwidth information, BSS color information, etc.) without separate signaling.
  • a 52-tone DRU and a 106-tone DRU may include tones of lower-sized DRUs as follows:
  • two additional tones for the 106-tone DRU can be defined based on the description in Example 3.
  • the order of the alphabetic indices of DRUs may be unrelated to the order of their positions in the frequency domain. Furthermore, even if the alphabetic indices of DRUs of different sizes are identical, this does not imply that the order within DRU indices of the same size is identical.
  • the Gap value may have the same or different values depending on the DRU size.
  • the Gap value may have independent values depending on the DRU size, or it may have associated values.
  • This embodiment is for the tone index of each DRU when the DRU is applied within each 20 MHz in a bandwidth exceeding 40 MHz (e.g., a bandwidth of 80 MHz or more).
  • the set of tone indices contained in each of the one or more DRUs for a channel of x MHz in a bandwidth of y MHz may be denoted as S_x_y.
  • a separate tone shift value may be additionally applied to take into account performance improvements, tone plans/layouts of existing 242-tone RRUs, etc.
  • the tone index (S_20_40) at a specific 20 MHz within the 40 MHz bandwidth can be defined as follows.
  • the second S_20_40 S_20_20 + 128.
  • the tone index (S_20_80) at a specific 20 MHz within the 80 MHz bandwidth can be defined as follows.
  • Tone index of each 20 MHz within the first 40 MHz (first S_20_80 and second S_20_80): DRU tone index of each 20 MHz defined in the aforementioned 40 MHz (first S_20_40 and second S_20_40) - 256
  • 2nd S_20_80 2nd S_20_40 - 256;
  • 3rd S_20_80 1st S_20_40 + 256;
  • the tone index (S_20_160) at a specific 20 MHz within the 160 MHz bandwidth can be defined as follows.
  • 3rd S_20_160 3rd S_20_80 - 512;
  • the tone index (S_20_240) at a specific 20 MHz within the 240 MHz bandwidth can be defined as follows.
  • 3rd S_20_240 3rd S_20_80 - 1024;
  • the tone index (S_20_320) at a specific 20 MHz in the 320 MHz bandwidth can be defined as follows.
  • 3rd S_20_320 3rd S_20_160 - 1024;
  • 4th S_20_320 4th S_20_160 - 1024;
  • 5th S_20_320 5th S_20_160 - 1024;
  • 6th S_20_320 6th S_20_160 - 1024;
  • 8th S_20_320 8th S_20_160 - 1024;
  • 16th S_20_320 8th S_20_160 + 1024.
  • the tone index (S_20_480) at a specific 20 MHz in the 480 MHz bandwidth can be defined as follows.
  • 2nd S_20_480 2nd S_20_160 - 2048;
  • 3rd S_20_480 3rd S_20_160 - 2048;
  • 4th S_20_480 4th S_20_160 - 2048;
  • 5th S_20_480 5th S_20_160 - 2048;
  • 6th S_20_480 6th S_20_160 - 2048;
  • 8th S_20_480 8th S_20_160 - 2048;
  • 16th S_20_480 8th S_20_160;
  • 21st S_20_480 5th S_20_160 + 2048;
  • the tone index (S_20_640) at a specific 20 MHz in the 640 MHz bandwidth can be defined as follows.
  • 2nd S_20_640 2nd S_20_320 - 2048;
  • 3rd S_20_640 3rd S_20_320 - 2048;
  • 4th S_20_640 4th S_20_320 - 2048;
  • 5th S_20_640 5th S_20_320 - 2048;
  • 6th S_20_640 6th S_20_320 - 2048;
  • 8th S_20_640 8th S_20_320 - 2048;
  • 9th S_20_640 9th S_20_320 - 2048;
  • 10th S_20_640 10th S_20_320 - 2048;
  • 11th S_20_640 11th S_20_320 - 2048;
  • 13th S_20_640 13th S_20_320 - 2048;
  • 15th S_20_640 15th S_20_320 - 2048;
  • 16th S_20_640 16th S_20_320 - 2048;
  • 21st S_20_640 5th S_20_320 + 2048;
  • 26th S_20_640 10th S_20_320 + 2048;
  • DRUs of different sizes can be allocated and used to different STAs within a 20MHz space, similar to the use of existing RRUs.
  • the RU allocation field in DL OFDMA transmission and the RU allocation subfield within the trigger frame for TB PPDU transmission can be utilized in the same manner as in RRU transmission.
  • a mapping rule needs to be defined from the RU allocation field and RU allocation subfield to the DRU.
  • FIGS. 13 and 14 STA operations based on various examples of the present disclosure described above are described with reference to FIGS. 13 and 14 .
  • the examples in FIGS. 13 and 14 may correspond to some of the various examples of the present disclosure.
  • FIG. 13 is a diagram for explaining an example of a DRU tone plan-based PPDU transmission method of a first STA according to the present disclosure.
  • the first STA may generate a PPDU including one or more fields.
  • the one or more fields may be mapped/transmitted on one or more DRUs.
  • the PPDU may be a PPDU transmitted/received over a bandwidth including a 20 MHz channel.
  • one or more fields may contain a data field. That is, the data field of a PPDU may be generated by mapping onto one or more DRUs of different sizes.
  • one or more DRUs include any one 26-ton DRU, that 26-ton DRU may be one of the nine predefined 26-ton DRUs.
  • the available tones in a 20MHz channel can be configured based on excluding 18 tones corresponding to DC (direct current) tones and guard tones, and 4 tones corresponding to null tones from among 256 tones within the 20MHz channel.
  • the DC tone and guard tone may be identical to the DC tone and guard tone in the RRU tone plan in the existing 20MHz channel (e.g., see Fig. 8).
  • the null tone may correspond to the tones with tone indices [-122, -4, +4, +122] or [-4, -3, +3, +4].
  • nine predefined 26-tone DRUs can be defined as follows:
  • a first 26-tone DRU includes tones with tone indices [-121:9:-13] and [5:9:113]
  • a second 26-tone DRU includes tones with tone indices [-120:9:-12] and [6:9:114]
  • a third 26-tone DRU includes tones with tone indices [-119:9:-11] and [7:9:115]
  • a fourth 26-tone DRU includes tones with tone indices [-118:9:-10] and [8:9:116]
  • a fifth 26-tone DRU includes tones with tone indices [-117:9:-9] and [9:9:117]
  • a sixth 26-tone DRU includes tones with tone indices [-116:9:-8] and
  • the seventh 26-tone DRU may include tones with tone indices [-115:9:-7] and [11:9:119]
  • the eighth 26-tone DRU may include tones with tone indices [-114:9:-6
  • predefined 52-ton DRUs can be defined as follows:
  • a first 52-ton DRU may include tones included in the first 26-ton DRU and the sixth 26-ton DRU
  • a second 52-ton DRU may include tones included in the second 26-ton DRU and the seventh 26-ton DRU
  • a third 52-ton DRU may include tones included in the third 26-ton DRU and the eighth 26-ton DRU
  • a fourth 52-ton DRU may include tones included in the fourth 26-ton DRU and the ninth 26-ton DRU.
  • two predefined 106-ton DRUs can be defined as follows:
  • a first 106-tone DRU may include a first group corresponding to tones included in the first 52-tone DRU and the third 52-tone DRU, and two of the four null tones
  • a second 106-tone DRU may include a second group corresponding to tones included in the second 52-tone DRU and the fourth 52-tone DRU, and the other two of the four null tones.
  • the four null tones correspond to tones with tone indices [-4, -3, +3, +4]
  • the first group may include tones with tone indices [-4, +3]
  • the second group may include tones with tone indices [-3, +4].
  • the one or more DRUs may be indicated based on resource unit (RU) allocation information included in the PPDU, or the one or more DRUs may be indicated based on RU allocation information included in a trigger frame that triggers transmission of the PPDU.
  • the PPDU may be a downlink PPDU or an uplink TB (trigger-based) PPDU.
  • the indication to the one or more DRUs may be based on a mapping rule between nine predefined 26-tone DRUs and nine predefined 26-tone RUs for the 20 MHz channel (e.g., a mapping rule between RRUs and DRUs).
  • the tone indices included in each of the one or more DRUs for a 20 MHz channel may be tone shifted according to their positions within a bandwidth of 40 MHz or more.
  • a set of subcarrier indices included in each of the one or more DRUs for a channel of x MHz in a bandwidth of y MHz may be denoted as S_x_y.
  • the DRU tone index (first S_20_40) for the left 20MHz channel in the 40MHz bandwidth may correspond to a value obtained by subtracting 128 from the DRU tone index (S_20_20) for the 20MHz channel.
  • the DRU tone index (second S_20_40) for the right 20MHz channel in the 40MHz bandwidth may correspond to a value obtained by adding 128 to the DRU tone index (S_20_20) for the 20MHz channel.
  • the DRU tone indices (first S_20_80 and second S_20_80) for each 20 MHz channel within one 40 MHz channel on the left side of two 40 MHz channels in an 80 MHz bandwidth may correspond to values obtained by subtracting 256 from the DRU tone indices (first S_20_40 and second S_20_40) for each 20 MHz channel defined in the 40 MHz bandwidth.
  • the DRU tone indices (third S_20_80 and fourth S_20_80) for each 20 MHz channel within one 40 MHz channel on the right side of the 80 MHz bandwidth may correspond to values obtained by adding 256 to the DRU tone indices (first S_20_40 and second S_20_40) for each 20 MHz channel defined in the 40 MHz bandwidth.
  • the DRU tone index (the first S_20_160 to the fourth S_20_160) for each 20 MHz channel in the left 80 MHz channel may correspond to a value obtained by subtracting 512 from the DRU tone index (the first S_20_80 to the fourth S_20_80) for each 20 MHz channel defined in the 80 MHz bandwidth.
  • the DRU tone index (the fifth S_20_160 to the eighth S_20_160) for each 20 MHz in the right 80 MHz channel in the 160 MHz bandwidth may correspond to a value obtained by adding 512 to the DRU tone index (the first S_20_80 to the fourth S_20_80) for each 20 MHz channel defined in the 80 MHz bandwidth.
  • the DRU tone index (the first S_20_240 to the fourth S_20_240) for each 20 MHz channel in the left 80 MHz channel may correspond to a value obtained by subtracting 1024 from the DRU tone index (the first S_20_80 to the fourth S_20_80) for each 20 MHz channel defined in the 80 MHz bandwidth.
  • the DRU tone index (the fifth S_20_240 to the eighth S_20_240) for each 20 MHz channel in the middle 80 MHz channel in the 240 MHz bandwidth may correspond to the same value as the DRU tone index (the first S_20_80 to the fourth S_20_80) for each 20 MHz channel defined in the 80 MHz bandwidth.
  • the DRU tone index (9th S_20_240 to 12th S_20_240) for each 20MHz channel within the right 80MHz channel in the 240MHz bandwidth may correspond to a value obtained by adding 1024 to each DRU tone index (1st S_20_80 to 4th S_20_80) for each 20MHz channel defined in the 80MHz bandwidth.
  • the DRU tone indices (the first S_20_320 to the eighth S_20_320) for each 20 MHz channel within the left 160 MHz channel among two 160 MHz channels in the 320 MHz bandwidth may correspond to a value obtained by subtracting 1024 from the DRU tone indices (the first S_20_160 to the eighth S_20_160) for each 20 MHz channel defined in the 160 MHz bandwidth.
  • the DRU tone indices (the ninth S_20_320 to the sixteenth S_20_320) for each 20 MHz channel within the right 160 MHz channel in the 320 MHz bandwidth may correspond to a value obtained by adding 1024 to the DRU tone indices (the first S_20_160 to the eighth S_20_160) for each 20 MHz channel defined in the 160 MHz bandwidth.
  • the DRU tone indices (the first S_20_480 to the eighth S_20_480) for each 20 MHz channel within the left 160 MHz channel may correspond to a value obtained by subtracting 2048 from the DRU tone indices (the first S_20_160 to the eighth S_20_160) for each 20 MHz channel defined in the 160 MHz bandwidth.
  • the DRU tone indices (the ninth S_20_480 to the sixteenth S_20_480) for each 20 MHz channel within the middle 160 MHz channel in the 480 MHz bandwidth may correspond to the same value as the DRU tone indices (the first S_20_160 to the eighth S_20_160) for each 20 MHz channel defined in the 160 MHz bandwidth.
  • the DRU tone index (17th S_20_480 to 24th S_20_480) for each 20MHz channel within the right 160MHz channel in the 480MHz bandwidth may correspond to a value obtained by adding 2048 to the DRU tone index (1st S_20_160 to 8th S_20_160) for each 20MHz channel defined in the 160MHz bandwidth.
  • the DRU tone index (the first S_20_640 to the sixteenth S_20_640) for each 20 MHz channel within the left 320 MHz channel among two 320 MHz channels in the 640 MHz bandwidth may correspond to a value obtained by subtracting 2048 from the DRU tone index (the first S_20_320 to the sixteenth S_20_320) for each 20 MHz channel defined in the 320 MHz bandwidth.
  • the DRU tone index (17th S_20_640 to 32nd S_20_640) for each 20MHz channel within the right 320MHz channel in the 640MHz bandwidth may correspond to a value obtained by adding 2048 to each DRU tone index (1st S_20_320 to 16th S_20_320) for each 20MHz channel defined in the 320MHz bandwidth.
  • additional tone shift values may be applied to each of the first S_20_40 and the second S_20_40.
  • the first STA may transmit a PPDU to one or more second STAs over a bandwidth including a 20 MHz channel.
  • the one or more DRUs may be indicated based on resource unit (RU) allocation information included in the PPDU.
  • the PPDU may be a downlink PPDU (or DL-OFDMA PPDU).
  • the one or more DRUs may be indicated based on RU allocation information included in a trigger frame that triggers transmission of the PPDU.
  • the PPDU may be a TB PPDU (or UL-OFDMA PPDU).
  • the indication to the one or more DRUs may be based on a mapping rule between nine predefined 26-tone DRUs and nine predefined 26-tone RUs for the 20 MHz channel (e.g., a mapping rule between RRUs and DRUs).
  • the method described in the example of FIG. 13 may be performed by the first device (100) of FIG. 1.
  • one or more processors (102) of the first device (100) of FIG. 1 may be configured to generate a PPDU including one or more fields and transmit the PPDU to one or more second STAs over a bandwidth including a 20 MHz channel.
  • one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 13 or the examples described above when executed by one or more processors (102).
  • FIG. 14 is a diagram for explaining an example of a DRU tone plan-based PPDU reception method of a second STA according to the present disclosure.
  • the second STA may receive a PPDU including one or more fields from the first STA over a bandwidth including a 20 MHz channel.
  • the second STA may decode one or more fields received on one or more DRUs.
  • the second STA may determine the number and position (e.g., index) of tones of one or more DRUs to which one or more fields (e.g., data fields) in the PPDU transmitted by the first STA are mapped based on RU allocation information included in the PPDU or based on RU allocation information included in a trigger frame that triggers transmission of the PPDU. Based on this, the second STA may decode one or more fields mapped to the one or more DRUs.
  • tone plans for one or more DRUs e.g., various sizes and tone indices of DRUs
  • signaling for DRU indication, etc. are the same as those described in the example of Fig. 13, and therefore, redundant descriptions are omitted.
  • the method described in the example of FIG. 14 may be performed by the second device (200) of FIG. 1.
  • one or more processors (202) of the second device (200) of FIG. 1 may be configured to receive a PPDU including one or more fields from the first STA over a bandwidth including a 20 MHz channel, and to decode the one or more fields received on one or more DRUs.
  • one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 14 or the examples described above when executed by one or more processors (202).
  • FIG. 15 is a diagram illustrating a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure. Some of the steps shown in FIG. 15 may be omitted depending on circumstances and/or settings.
  • the transmitting device and the receiving STA may be APs and/or non-AP STAs.
  • the transmitting STA may obtain control information related to the aforementioned tone plan (or RU/DRU) (S105).
  • the control information related to the tone plan may include the size and location of the RU, control information related to the RU, information about the frequency band in which the RU is included, information about the STA receiving the RU, etc.
  • the transmitting STA may configure/generate a PPDU based on the acquired control information (S110).
  • Configuring/generating a PPDU may mean configuring/generating each field of the PPDU. That is, the step of configuring/generating a PPDU may include a step of configuring EHT-SIG-A/B/C fields that include control information regarding a tone plan.
  • the step of configuring/generating a PPDU may include a step of configuring a field including control information (e.g., N bitmap) indicating the size/position of the RU and/or a step of configuring a field including an identifier (e.g., AID) of an STA receiving the RU.
  • control information e.g., N bitmap
  • AID an identifier
  • the step of configuring/generating a PPDU may include a step of generating an STF/LTF sequence to be transmitted via a specific RU.
  • the STF/LTF sequence may be generated based on a preset STF generation sequence/LTF generation sequence.
  • the step of constructing/generating a PPDU may include a step of generating a data field (i.e., an MPDU) to be transmitted via a specific RU.
  • a data field i.e., an MPDU
  • the transmitting STA can transmit the configured/generated PPDU to the receiving STA (S115).
  • the transmitting STA can perform at least one of cyclic shift diversity (CSD), spatial mapping, inverse discrete Fourier transform (IDFT)/inverse fast Fourier transform (IFFT) operation, and guard interval (GI) insertion operation.
  • CSD cyclic shift diversity
  • IDFT inverse discrete Fourier transform
  • IFFT inverse fast Fourier transform
  • GI guard interval
  • the receiving STA can decode the PPDU and obtain control information related to the tone-plan (or RU) (S120).
  • the receiving STA can decode the L-SIG and EHT-SIG of the PPDU based on the L-STF/LTF, and obtain information included in the L-SIG and EHT SIG fields.
  • Information about various tone plans (i.e., RUs) of the present disclosure can be included in the EHT-SIG (EHT-SIG-A/B/C, etc.), and the receiving STA can obtain information about the tone plan (i.e., RU) through the EHT-SIG.
  • the receiving STA can decode the remaining portion of the PPDU based on the information about the acquired tone plan (i.e., RU) (S125). For example, the receiving STA can decode the STF/LTF field of the PPDU based on the information about the tone plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.
  • the receiving STA may perform a processing operation to forward the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data forwarded to the higher layer, the receiving STA may perform a subsequent operation.
  • a higher layer e.g., the MAC layer
  • the efficiency of resource utilization can be improved by transmitting/receiving one or more fields of PPDU based on various sizes of DRU tone plans applicable to PPDU of 20 MHz bandwidth according to the present disclosure.
  • the scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer.
  • Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on/in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure.
  • the storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory optionally includes one or more storage devices remotely located from the processor(s).
  • the memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium.
  • the features described in this disclosure may be incorporated into software and/or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure.
  • Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments/containers.
  • the method proposed in this disclosure is described with a focus on examples applied to IEEE 802.11-based systems, but can be applied to various wireless LANs or wireless communication systems in addition to IEEE 802.11-based systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un dispositif basés sur un plan de tonalité d'unité de ressource distribuée (DRU) pour la transmission ou la réception dans un système LAN sans fil. Le procédé selon un mode de réalisation de la présente divulgation peut comprendre des étapes dans lesquelles une première station (STA) : génère une unité de données de protocole de couche physique (PPDU) comprenant un ou plusieurs champs ; et transmet la PPDU à une ou plusieurs secondes STA sur une largeur de bande comprenant un canal de 20 MHz. Le ou les champs peuvent être transmis sur une ou plusieurs DRU.
PCT/KR2025/001449 2024-02-06 2025-01-24 Procédé et dispositif basés sur un plan de tonalité d'unité de ressource distribuée pour transmission ou réception dans un système lan sans fil Pending WO2025170270A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
KR10-2024-0018434 2024-02-06
KR20240018434 2024-02-06
KR20240020537 2024-02-13
KR10-2024-0020537 2024-02-13
KR10-2024-0035333 2024-03-13
KR20240035333 2024-03-13
KR10-2024-0041348 2024-03-26
KR20240041348 2024-03-26
KR10-2024-0065382 2024-05-20
KR20240065382 2024-05-20

Publications (1)

Publication Number Publication Date
WO2025170270A1 true WO2025170270A1 (fr) 2025-08-14

Family

ID=96700197

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2025/001449 Pending WO2025170270A1 (fr) 2024-02-06 2025-01-24 Procédé et dispositif basés sur un plan de tonalité d'unité de ressource distribuée pour transmission ou réception dans un système lan sans fil

Country Status (1)

Country Link
WO (1) WO2025170270A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101928447B1 (ko) * 2014-09-13 2018-12-12 엘지전자 주식회사 무선랜에서 자원 단위를 할당하는 방법 및 장치
KR102053237B1 (ko) * 2014-10-06 2020-01-07 엘지전자 주식회사 무선랜에서 파일롯 톤을 포함하는 자원 단위 상에서 데이터를 전송하는 방법 및 장치
US20230035113A1 (en) * 2021-07-30 2023-02-02 Qualcomm Incorporated Distributed resource unit signaling
US20230048884A1 (en) * 2021-07-30 2023-02-16 Qualcomm Incorporated Pilot tones in distributed resource unit (dru) transmission
KR20230043135A (ko) * 2020-09-03 2023-03-30 엘지전자 주식회사 무선랜 시스템에서 20mhz에서만 동작하는 sta에 대해 ru 및 mru를 제한하여 자원을 할당하는 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101928447B1 (ko) * 2014-09-13 2018-12-12 엘지전자 주식회사 무선랜에서 자원 단위를 할당하는 방법 및 장치
KR102053237B1 (ko) * 2014-10-06 2020-01-07 엘지전자 주식회사 무선랜에서 파일롯 톤을 포함하는 자원 단위 상에서 데이터를 전송하는 방법 및 장치
KR20230043135A (ko) * 2020-09-03 2023-03-30 엘지전자 주식회사 무선랜 시스템에서 20mhz에서만 동작하는 sta에 대해 ru 및 mru를 제한하여 자원을 할당하는 방법 및 장치
US20230035113A1 (en) * 2021-07-30 2023-02-02 Qualcomm Incorporated Distributed resource unit signaling
US20230048884A1 (en) * 2021-07-30 2023-02-16 Qualcomm Incorporated Pilot tones in distributed resource unit (dru) transmission

Similar Documents

Publication Publication Date Title
WO2024019386A1 (fr) Procédé et appareil de mise en œuvre de procédure de sondage dans un système lan sans fil
WO2023219386A1 (fr) Procédé et dispositif d'émission/réception de ppdu basée sur une trame de déclenchement dans un système lan sans fil
WO2023191475A1 (fr) Procédé et dispositif pour une attribution d'unité de ressources dans un système lan sans fil
WO2025170270A1 (fr) Procédé et dispositif basés sur un plan de tonalité d'unité de ressource distribuée pour transmission ou réception dans un système lan sans fil
WO2025193068A1 (fr) Procédé et appareil de transmission ou de réception reposant sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2025211619A1 (fr) Procédé et dispositif de transmission ou de réception reposant sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2025183414A1 (fr) Procédé et dispositifs de transmission ou de réception basés sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2024186044A1 (fr) Procédé et dispositif de transmission ou de réception basés sur un plan de tonalité d'unité de ressource distribuée dans un système de réseau local sans fil
WO2024181759A1 (fr) Procédé et dispositif de transmission ou de réception sur la base d'un plan de tonalité d'unité de ressource distribuée et d'une tonalité pilote dans un système lan sans fil
WO2025234746A1 (fr) Procédé et appareil de transmission ou de réception reposant sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2024172353A1 (fr) Procédé et dispositif de transmission ou de réception basés sur une unité de ressource distribuée dans un système lan sans fil
WO2025254429A1 (fr) Procédé et dispositif de transmission ou de réception reposant sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2024172339A1 (fr) Procédé et appareil de transmission ou de réception sur la base d'une unité de ressource distribuée dans un système lan sans fil
WO2025198354A1 (fr) Procédé et dispositifs de transmission ou de réception basés sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2024262917A1 (fr) Procédé et dispositif d'émission ou de réception basés sur un plan de tonalités d'une unité de ressources réparties dans un système lan sans fil
WO2025075333A1 (fr) Procédé et dispositif basés sur un plan de tonalités d'une unité de ressources réparties pour émettre ou recevoir dans un système de réseau local sans fil
WO2024210669A1 (fr) Procédé et dispositif pour émission et réception de ppdu dans un système de réseau local sans fil
WO2024172570A1 (fr) Procédé et dispositif de transmission et de réception de ppdu dans un système de réseau local sans fil
WO2025084755A1 (fr) Procédé et dispositif de transmission ou de réception basée sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2025206855A1 (fr) Procédé et appareil d'estimation et de détermination d'accessibilité dans un système lan sans fil
WO2025170276A1 (fr) Procédé et appareil de transmission ou de réception basés sur un plan de tonalité d'unité de ressource distribuée dans un système wlan
WO2024228518A1 (fr) Procédé et appareil d'émission ou de réception reposant sur un plan de tonalité d'unité de ressource distribuée dans un système lan sans fil
WO2025234774A1 (fr) Procédé et appareil d'émission ou de réception d'informations relatives à la coexistence dans un dispositif dans un système lan sans fil
WO2025143851A1 (fr) Procédé et dispositif d'émission/réception de trafic dans un système lan sans fil
WO2025084748A1 (fr) Procédé et dispositif de transmission/réception de trafic dans un système lan sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25752318

Country of ref document: EP

Kind code of ref document: A1