[go: up one dir, main page]

WO2025121871A1 - Procédé et dispositif de transmission ou de réception dans système lan sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée - Google Patents

Procédé et dispositif de transmission ou de réception dans système lan sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée Download PDF

Info

Publication number
WO2025121871A1
WO2025121871A1 PCT/KR2024/019703 KR2024019703W WO2025121871A1 WO 2025121871 A1 WO2025121871 A1 WO 2025121871A1 KR 2024019703 W KR2024019703 W KR 2024019703W WO 2025121871 A1 WO2025121871 A1 WO 2025121871A1
Authority
WO
WIPO (PCT)
Prior art keywords
dru
drus
tone
distributed
size
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/KR2024/019703
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 WO2025121871A1 publication Critical patent/WO2025121871A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • 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
  • Wi-Fi wireless LAN
  • VHT Very High-Throughput
  • HE High Efficiency
  • EHT Extremely High Throughput
  • technologies for MIMO (Multiple Input Multiple Output) and multi-access point (AP) coordination that support increased bandwidth, efficient utilization of multiple bands, and increased spatial streams are being studied, and in particular, various technologies are being studied to support low latency or real-time traffic.
  • new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions of EHT technologies.
  • the technical problem of the present disclosure is to provide a method and device for transmitting or receiving based on a distributed resource unit (DRU) tone plan in a wireless LAN system.
  • DRU distributed resource unit
  • the technical problem of the present disclosure is to provide a method and device for applying an interleaver and/or a tone mapper to a multiple DRU (M-DRU) composed of a plurality of DRUs in a wireless LAN system.
  • M-DRU multiple DRU
  • 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 a second STA.
  • the one or more fields are transmitted on multiple DRUs (distributed resource units) including N (N>1) DRUs, and DRUs belonging to the N DRUs include a plurality of subcarriers distributed on a frequency domain, and a parameter for an interleaver or a tone mapper for the multiple DRUs may be applied based on at least one of a size of a DRU belonging to the N DRUs or a distributed channel.
  • a method may include: receiving, by a second STA, from a first STA, a physical layer protocol data unit (PPDU) including one or more fields; and decoding, by the second STA, the one or more fields received on multiple DRUs (distributed resource units) comprising N (N>1) DRUs, wherein the DRUs belonging to the N DRUs include a plurality of subcarriers distributed on a frequency domain, and a parameter for an interleaver or a tone mapper for the multiple DRUs may be applied based on at least one of a size of a DRU belonging to the N DRUs or a distributed channel.
  • PPDU physical layer protocol data unit
  • a method and device for transmitting or receiving based on a distributed resource unit (DRU) tone plan in a wireless LAN system can be provided.
  • DRU distributed resource unit
  • a method and device for applying an interleaver and/or a tone mapper to a multiple DRU (M-DRU) composed of a plurality of DRUs 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 reception 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 transmission 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
  • 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 IEEE 802.11a/g/n/ac/ax/be standards.
  • the examples of the present disclosure can be applied to a wireless LAN based on a newly proposed IEEE 802.11bn (or UHR) standard.
  • the examples of the present disclosure can be applied to a wireless LAN based on a 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 a Long Term Evolution (LTE) series technology of the 3rd Generation Partnership Project (3GPP) standard and a New Radio (5G NR) series technology.
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • 5G NR New Radio
  • 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 Wireless Transmit Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Mobile Subscriber Unit (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), a Wireless terminal (WT), or simply a user.
  • WTRU Wireless Transmit Receive Unit
  • UE User Equipment
  • MS Mobile Station
  • UT a 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 base station (BS), a fixed station, a Node B, a base transceiver system (BTS), a network, an Artificial Intelligence (AI) system, a road side unit (RSU), a repeater, a router, a relay, a gateway, etc.
  • AP access point
  • BS base station
  • BTS base transceiver system
  • AI Artificial Intelligence
  • RSU road side unit
  • RSU repeater
  • router a relay
  • gateway a gateway
  • the devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs).
  • STAs stations
  • the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, and a receiving STA.
  • the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, the STAs (110, 200) in the present disclosure may perform 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 in the present disclosure may also be indicated 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 regulations 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 (for example, standards of 3GPP LTE series, 5G NR series, 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 Augmented Reality (AR) device, and a Virtual Reality (VR) device.
  • the STA of the present specification may support various communication services such as a voice call, a video call, a data communication, 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 additionally 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, suggestions, methods, and/or operational flowcharts disclosed in the present disclosure.
  • the processor (102) may process information in the memory (104) to generate first information/signal, and then transmit a wireless signal including the first information/signal via the transceiver (106).
  • the processor (102) may receive a wireless signal including second information/signal via the transceiver (106), and then store information obtained from signal processing of the second information/signal in the memory (104).
  • the memory (104) may be connected to the processor (102) and may store various information 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 codes 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 additionally include one or more transceivers (206) and/or one or more antennas (208).
  • the processor (202) may control the memories (204) and/or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure.
  • the processor (202) may process information in the memory (204) to generate third information/signal, and then transmit a wireless signal including the third information/signal via the transceiver (206).
  • the processor (202) may receive a wireless signal including fourth information/signal via the transceiver (206), and then store information obtained from signal processing of the fourth information/signal in the memory (204).
  • the memory (204) may be 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 codes including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operational 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 this 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 this 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, suggestions and/or methodologies disclosed in this 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, suggestions, methods and/or operational flowcharts disclosed in this disclosure.
  • signals e.g., baseband signals
  • the one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer.
  • the 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, suggestions, methods, and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more of the following: included in one or more processors (102, 202), or stored in one or more memories (104, 204) and driven by one or more of the processors (102, 202).
  • the descriptions, functions, procedures, suggestions, methods and/or operational 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 comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • the one or more memories (104, 204) may be located 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, suggestions, 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. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals/channels, and the like, as described in the description, function, procedure, proposal, method, and/or operational flowchart, etc.
  • 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. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202).
  • One or more transceivers (106, 206) may convert 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 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 of various STAs generating transmission and reception signals or performing 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 transmit/receive signal or performing data processing or calculation in advance for a transmit/receive signal may include: 1) an operation for determining/acquiring/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/acquiring time resources or frequency resources (e.g., subcarrier resources) used for the fields (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining/configuring/acquiring specific sequences (e.g., pilot sequences, STF/LTF sequences, extra sequences applied to SIG) used for the fields (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/acquiring/acquiring/
  • 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 means a link for communication from an AP STA to a non-AP STA, and downlink PPDU/packet/signal, etc. can be transmitted and received through the downlink.
  • a transmitter may be part of an AP STA, and a receiver may be part of a non-AP STA.
  • Uplink (UL) means a link for communication from a non-AP STA to an AP STA, and uplink PPDU/packet/signal, etc. can be transmitted and received through the uplink.
  • a transmitter may be part of a non-AP STA, and a 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 wireless LAN supporting transparent STA mobility to a higher layer can be provided through the interaction of multiple components.
  • a BSS Basic Service Set
  • FIG. 2 illustrates an example in which two BSSs (BSS1 and BSS2) exist and two STAs are included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2).
  • An ellipse 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 BSA (Basic Service Area). If an STA moves out of the BSA, it cannot directly communicate with other STAs within the corresponding 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
  • This configuration is possible when 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.
  • an IBSS does not include an AP, there is no centralized management entity that performs management functions. 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
  • the membership of an STA in a BSS can be dynamically changed by the STA turning on or off, the STA entering or leaving the BSS area, etc.
  • an STA can join the BSS using a synchronization process.
  • an STA In order to access all services of the BSS infrastructure, an STA must be associated with a BSS. This association can be dynamically established and may include the use of a Distribution System Service (DSS).
  • DSS Distribution System Service
  • the direct STA-to-STA distance may be limited by the PHY performance. In some cases, this distance limitation may be sufficient, but in some cases, communication between STAs over longer distances may be required.
  • a distributed system may 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 shown in FIG. 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 distributed system medium
  • Each logical medium is used for a different purpose and is used by different components. These media are neither limited to being the same nor limited to being different.
  • the flexibility of a wireless LAN structure can be explained in that multiple media are logically different.
  • a wireless LAN structure can be implemented in various ways, and each wireless LAN structure can be independently specified by the physical characteristics of each implementation example.
  • a DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary to handle addresses to destinations.
  • a DS can further include a component called a portal that 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 a function that allows 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 need not necessarily be the same.
  • a BSS consisting of an AP and one or more STAs can be called an infrastructure BSS.
  • Data transmitted from one of the STA(s) associated with an AP to the STA address of that AP is always received on an uncontrolled port and can be processed by an IEEE 802.1X port access entity.
  • the transmitted data (or frame) can be forwarded to the DS.
  • An ESS is a network of arbitrary size and complexity consisting of DS and BSS.
  • 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 being seen as an IBSS in the LLC (Logical Link Control) layer. STAs included in an ESS can communicate with each other, and mobile STAs can move from one BSS to another BSS (within the same ESS) transparently to the LLC.
  • APs included in an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is an identifier of the BSS.
  • the BSSs can be partially overlapped, which is a common configuration used to provide continuous coverage.
  • the BSSs can be physically unconnected, and logically there is no limit to the distance between the BSSs.
  • the BSSs can be physically co-located, which can be used to provide redundancy.
  • one (or more) IBSS or ESS networks can physically co-exist in the same space as one (or more) ESS networks. This can correspond to ESS network configurations such as cases where ad-hoc networks operate at locations where ESS networks exist, cases where physically overlapping wireless networks are configured by different organizations, or cases 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 may also be referred to as a session initiation process or a session setup process.
  • the discovery, authentication, association, and security setup processes of the link setup process may be collectively referred to as the association process.
  • the STA may perform a network discovery operation.
  • the network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access the network, it must find a network that it can participate in. The STA must identify a compatible network before participating in the wireless network, and the process of identifying networks existing in a specific area is called scanning.
  • FIG. 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 search for APs in the vicinity while moving between channels and waits for a response thereto.
  • a responder transmits a probe response frame to the STA that transmitted the probe request frame as a response to the probe request frame.
  • the responder may be an STA that last transmitted a beacon frame in the BSS of the channel being scanned.
  • the AP transmits a beacon frame, so the AP becomes the responder, and in the IBSS, 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 request/response on channel 2) in the same manner.
  • the next channel e.g., channel 2
  • scanning i.e., transmitting and receiving probe request/response on channel 2
  • An STA receiving a beacon frame stores information related to the BSS included in the received beacon frame, moves to the next channel, and performs 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 a first authentication process to clearly distinguish it from the security setup operation of step S340 described below.
  • the authentication process includes the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response.
  • 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), a Finite Cyclic Group, etc. These are just some examples of information that may be included in an authentication request/response frame, and may be replaced by other information or may include additional information.
  • RSN Robust Security Network
  • the STA may transmit an authentication request frame to the AP.
  • the AP may determine whether to allow authentication for the STA based on information included in the received authentication request frame.
  • the AP may provide the result of the authentication processing to the STA through 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, RSN, mobility domains, 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., 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., association comeback time
  • overlapping BSS scan parameters e.g., TIM broadcast response
  • a security setup process may be performed in step S340.
  • the security setup process of step S340 may be referred to as an authentication process through a Robust Security Network Association (RSNA) request/response
  • the authentication process of step S320 may be referred to as a first authentication process
  • the security setup process of step S340 may be referred to simply as an authentication process.
  • RSNA Robust Security Network Association
  • the security setup process of step S340 may include a process of performing private key setup, for example, through 4-way handshaking via an Extensible Authentication Protocol over LAN (EAPOL) frame. Additionally, 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 the CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism.
  • the CSMA/CA mechanism is also called the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and basically adopts the "listen before talk" access mechanism.
  • 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 and then attempt to transmit frames.
  • a delay period e.g., a random backoff period
  • the IEEE 802.11 MAC protocol provides a 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 in which all receiving APs and/or STAs periodically poll to receive data frames.
  • the HCF has EDCA (Enhanced Distributed Channel Access) and HCCA (HCF Controlled Channel Access).
  • EDCA is a contention-based access method in which a provider provides data frames to multiple users, and HCCA uses a non-contention-based channel access method using a polling mechanism.
  • the HCF includes a medium access mechanism for improving the QoS (Quality of Service) of a wireless LAN, and can transmit QoS data in both a contention period (CP) and a 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). As a measure 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 CWmin, but may take a double value in case of transmission failure (e.g., when 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, and when the medium becomes idle, the remaining countdown is resumed.
  • STA3 when a packet to be transmitted reaches the MAC of STA3, STA3 can check that the medium is idle for DIFS and transmit the frame right away. The remaining STAs monitor whether the medium is occupied/busy and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can perform a countdown of the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS when 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 the countdown and wait while STA2 occupies the medium.
  • STA1 and STA5 resume the stopped backoff count after waiting for DIFS. That is, they can start frame transmission after counting down the remaining backoff slots by the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. 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, performs a countdown according to the random backoff count value it selected, and starts frame transmission.
  • the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, and in this 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 then starts transmitting frames after the remaining backoff time has elapsed.
  • 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 such as DIFS or PIFS (Point coordination function IFS) elapses.
  • Subtype frames of the 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 RTS (Request-To-Send), CTS (Clear-To-Send), ACK (Acknowledgment), PS-Poll (Power Save-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), NDP notification (null data packet announcement), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after the backoff performed after the DIFS (DIFS), and if it is a response frame to the previous frame, it is transmitted without the backoff performed after the SIFS (short IFS).
  • DIFS DIFS
  • 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, that is, 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 an STA directly senses the medium.
  • Virtual carrier sensing is intended to complement problems that may occur in medium access, such as the hidden node problem.
  • the MAC of the STA may utilize a Network Allocation Vector (NAV).
  • NAV Network Allocation Vector
  • the NAV is a value that indicates to other STAs the remaining time until the medium becomes available, by an STA that is currently using or has the right to use the medium. Therefore, the value set as NAV corresponds to the period during which the medium is scheduled to be used by the STA transmitting the corresponding frame, and the STA that receives the NAV value is prohibited from accessing the medium during the corresponding period.
  • the NAV may be set based on the value of the "duration" field of the MAC header of the frame.
  • STA1 wants to transmit data to STA2, and STA3 is in a position to overhear part 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 carrier sensing result of the medium is idle. That is, STA1 may correspond to a hidden node to STA3.
  • STA2 may transmitting, STA3 may determine that the carrier sensing result of the medium is idle. That is, STA2 may correspond to a hidden node to STA3.
  • STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmission 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 a channel occupied idle state based on energy magnitude or signal correlation detected in the channel.
  • STA1 can determine a channel occupied state 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 DIFS.
  • STA2 can transmit a CTS frame, which is a response to the RTS frame, to STA1 after SIFS if it receives the RTS frame.
  • STA3 can set a NAV timer for the subsequently transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) using the duration information included in the RTS frame.
  • STA3 can set a NAV timer for the subsequently transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame) using the duration information included in the CTS 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.
  • STA3 can update the NAV timer using the duration information contained in the new frame if it receives a new frame before the NAV timer expires. STA3 does not attempt to access the channel 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 reception of the CTS frame is completed. 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 other terminals during DIFS after the expiration of the NAV timer, it can attempt channel access after a contention window (CW) following 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 by 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 information (e.g., data) provided from 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
  • an instruction or primitive meaning a set of instructions or parameters
  • 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
  • PPDU format may consist of only a Legacy-STF (L-STF), a Legacy-LTF (L-LTF), a Legacy-SIG (Legacy-SIG) field, 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 represents HT, VHT, HE, EHT, etc.
  • STF is a signal for signal detection, AGC (Automatic Gain Control), diversity selection, precise time synchronization, etc.
  • LTF is a signal for channel estimation, frequency error estimation, etc. STF and LTF can be said to be signals for OFDM physical layer synchronization and channel estimation.
  • 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 a 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 return the encoder to the 0 state.
  • padding bit may be used to adjust the length of the data field to a predetermined unit.
  • MAC PDU is defined according to various MAC frame formats, and the basic MAC frame consists of a MAC header, frame body, and FCS (Frame Check Sequence).
  • MAC frame consists of MAC PDU and can be transmitted/received through PSDU of the data part of 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 a receiver address, a transmitter address, a destination address, and a 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.
  • Null-Data PPDU (NDP) format refers to a PPDU format that does not include a data field. That is, NDP refers to a frame format that includes a PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and additionally, non-legacy SIG, non-legacy STF, non-legacy LTF if present) in a general PPDU format, and does not include the remaining part (i.e., data field).
  • a PPDU preamble i.e., L-STF, L-LTF, L-SIG fields, and additionally, non-legacy SIG, non-legacy STF, non-legacy LTF if present
  • 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 called a 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 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, and 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 a HE PPDU format for multi-users (MUs), and a HE PPDU format for single users (SUs) does not include the HE-SIG-B.
  • a 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.
  • RL-SIG can be configured identically to L-SIG.
  • the receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU described below based on the presence of 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 it 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 PSDU) 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 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
  • the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz) so that even legacy STAs can attempt to demodulate and decode them. These can be referred to as pre-EHT modulated fields.
  • the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz) so that they can be demodulated and decoded by an STA that successfully decodes a non-legacy SIG (e.g., U-SIG and/or EHT-SIG) and obtains the information included in the corresponding fields.
  • a predetermined subcarrier frequency interval e.g., 78.125 kHz
  • a non-legacy SIG e.g., U-SIG and/or EHT-SIG
  • EHT modulated fields e.g., U-SIG and/or EHT-SIG
  • 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 4us, and the U-SIG can have a total duration of 8us.
  • Each symbol of the U-SIG can be used to transmit 26 bits of information.
  • each symbol of the U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.
  • U-SIG can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be replicated 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-SIG of the first 80MHz unit and the U-SIG of the second 80MHz unit can be different.
  • a uncoded bits can be transmitted, and a first symbol of U-SIG (e.g., U-SIG-1 symbol) can transmit the first X bits of information out of the total A bits of information, and a second symbol of U-SIG (e.g., U-SIG-2 symbol) can transmit the remaining Y bits of information out of the total A bits of information.
  • the A bits of information e.g., 52 uncoded bits
  • the tail field can be used to terminate the trellis of the convolutional decoder and can 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 may 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 may be the same, and some or all of the version-dependent bits may 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 U-SIG may include a 3-bit PHY version identifier, which may indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted and received PPDU.
  • the version-independent bits of 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 U-SIG may include information about the length of a TXOP (transmission opportunity) and information about a BSS color ID.
  • the version-dependent bits of the U-SIG may contain information that directly or indirectly indicates the type of the PPDU (e.g., SU PPDU, MU PPDU, TB PPDU, etc.).
  • the U-SIG may further include information about bandwidth, information about an MCS technique applied to a non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique for achieving an effect similar to frequency diversity by reusing the same signal on two subcarriers) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, information about whether the non-legacy SIG is generated over the entire band, etc.
  • DCM dual carrier modulation
  • Some of the information required for PPDU transmission and reception 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 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) applied to the non-legacy LTF
  • information about the preamble puncturing applicable to the PPDU e.g., information about the resource unit (RU) allocation, etc.
  • RU resource unit
  • Preamble puncturing may mean transmission of a PPDU in which no signal is present in one or more frequency units within the bandwidth of the PPDU.
  • 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 predetermined size.
  • non-legacy SIGs such as HE-SIG-B, EHT-SIG, etc. may include control information for the receiving STA.
  • the non-legacy SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 us.
  • Information about the number of symbols used for 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, EHT-SIG, etc.
  • HE-SIG-B may contain common fields and user-specific fields. Common fields and user-specific fields may be coded separately.
  • the common field may be omitted.
  • the common field may be omitted, and multiple STAs may receive a PPDU (e.g., a data field of a PPDU) over the same frequency band.
  • a PPDU e.g., a data field of a PPDU
  • multiple users may receive a PPDU (e.g., a data field of a PPDU) over different frequency bands.
  • the number of user-specific fields can be determined based on the number of users.
  • One user block field can include at most two user fields.
  • Each user field can be associated with an MU-MIMO allocation or associated with a 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, the length of the Tail bits may be determined as 6 bits and may be 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 may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. An RU may also be defined when transmitting signals to one STA. Resources may be allocated in RU units for non-legacy STFs, non-legacy LTFs, and Data fields.
  • an applicable size of RU 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 tone plan for a low bandwidth.
  • RUs of different sizes can be defined, such as 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, 996-tone RU, 2 ⁇ 996-tone RU, 4 ⁇ 996-tone RU, etc.
  • a multiple RU is distinct from multiple individual RUs and corresponds to a group of subcarriers consisting of multiple RUs.
  • one MRU can be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2 ⁇ 996+484-tones, 3 ⁇ 996-tones, or 3 ⁇ 996+484-tones.
  • multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.
  • the specific size of the 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. In addition, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...) in the present disclosure, the number of RUs may vary depending on the RU size.
  • each field in the PPDU formats of FIG. 7 are exemplary, and the scope of the present disclosure is not limited by the names.
  • 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 a signal to multiple STAs based on an OFDMA technique. An RU may also be defined when transmitting a signal to one STA. An RU may be used for an STF, LTF, data field, etc. 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 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 can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band.
  • seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on the left and right sides of the DC band, respectively.
  • 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for an STA or a user.
  • the RU layout of Fig. 8 can be utilized not only in a situation for multiple users (MUs) but also in a situation 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 i.e., 26-RU, 52-RU, 106-RU, 242-RU, etc. are exemplified, but the specific sizes of these RUs may be reduced or expanded. Accordingly, 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 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc.
  • five DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can 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 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc.
  • the RU layout of HE PPDU and EHT PPDU can be different, and the example of FIG. 10 shows an example of RU layout for 80MHz EHT PPDU.
  • 12 tones are used as guard bands in the leftmost band of 80MHz band, and 11 tones are used as guard bands in the rightmost band of 80MHz band, which is the same for HE PPDU and EHT PPDU.
  • EHT PPDU Unlike HE PPDU where seven DC tones are inserted in the DC band and there is one 26-RU corresponding to 13 tones each on the left and right of the DC band, EHT PPDU has 23 DC tones inserted in the DC band and there is one 26-RU each on the left and right of the DC band. Unlike HE PPDU where there is one null subcarrier between 242-RUs other than the center band, EHT PPDU has five null subcarriers. In HE PPDU, one 484-RU does not contain any null subcarriers, but in 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 160 MHz or higher can be configured with multiple 80 MHz subblocks of FIG. 10.
  • the RU layout for each 80 MHz subblock can be the same as the RU layout of the 80 MHz EHT PPDU of FIG. 10. If an 80 MHz subblock of a 160 MHz or 320 MHz EHT PPDU is not punctured and the entire 80 MHz subblock is used as part of an RU or an MRU (Multiple RU), the 80 MHz subblock can use 996-RU of 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 of 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, 2 ⁇ 996+484-tones, 3 ⁇ 996-tones, or 3 ⁇ 996+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 including a small size RU and a large size RU may not be set/defined. In addition, multiple RUs composing a single MRU may or may not be consecutive in the frequency domain.
  • the 80 MHz 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 TRS (triggered response scheduling)).
  • trigger information e.g., a trigger frame or TRS (triggered response scheduling)
  • 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 1st/2nd TB PPDUs can be transmitted to the AP in the same time interval.
  • an STA e.g., an AP transmitting the DL MU PPDU can allocate the first RU (e.g., 26/52/106/242-RU, etc.) to the first STA, and the second RU (e.g., 26/52/106/242-RU, etc.) to the second STA.
  • the first RU e.g., 26/52/106/242-RU, etc.
  • the second RU e.g., 26/52/106/242-RU, etc.
  • the transmitting STA (e.g., the AP) can transmit the 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 can transmit the X-STF, X-LTF, and Data fields for the second STA through the second RU.
  • Information about the arrangement of RUs can be signaled through the X-SIG (e.g., X is HE, EHT, U) field of the X-PPDU format.
  • BCC applies only to RUs or MRUs with a size of 242 tones or less, the number of spatial streams is 4 or less, and the modulation can be one of BPSK, QPSK, 16-QAM, 64-QAM, or 256-QAM.
  • the BCC encoder can be applied to small RU and MRU.
  • the BCC encoded bits are interleaved across the RU or the entire MRU.
  • the interleaver parameters of the BCC encoded RU can be as shown in Table 1, and the interleaver parameters of the BCC encoded MRU can be as shown in Table 2.
  • the interleaver parameters N COL , N ROW , and N ROT for the data fields may vary depending on the RU size and whether dual (sub-)carrier modulation (DCM) is used.
  • DCM dual (sub-)carrier modulation
  • the interleaver parameters for U-SIG and EHT-SIG can be the same as the interleaver parameters for HE-SIG-A/HE-SIG-B as shown in Table 1. Since DCM is applied only to BPSK and single stream cases, N ROT is not applicable and N ROW can be determined without N BPSCS .
  • N SD represents the number of data tones in the RU or MRU portion
  • N COL and N ROW represent the number of columns and rows of the interleaver
  • N BPSCS represents the number of data bits per subcarrier.
  • N ROT represents a parameter for frequency rotation applied to additional spatial parameters.
  • interleaving can be defined using three permutation operations.
  • the first permutation operation and the second permutation operation can be given by Equations 1 and 2, respectively.
  • N CBPSSI represents a parameter related to the number of data subcarriers. Additionally, in mathematical expression 2, s can be max(1, N BPSCS /2).
  • the third permutation operation is for frequency rotation for each spatial stream. Specifically, when the number of spatial streams is greater than or equal to 2 and less than or equal to 4, the operation of mathematical expression 3 is applied, and when the number of spatial streams is greater than 4, the operation of mathematical expression 4 can be applied.
  • i ss represents a spatial stream index on which the corresponding interleaver operates, and can be defined as a value of [1, 2, ..., N SS ].
  • J(i ss ) is a pre-defined value according to the value of i ss , and for example, the value of J(i ss ) (0, 5, 2, 7, 3, 6, 1, 4) can be defined for the iss values (1, 2, 3, 4, 5, 6, 7, 8).
  • LDPC tone mapping must be performed on all LDPC encoded streams mapped to RUs or MRUs, and is not performed on streams encoded using BCC.
  • D_TM_DCM when DCM is applied to an LDPC encoded stream, D_TM_DCM shall be applied to both the lower half data subcarriers of the RU or MRU and the upper half data subcarriers of the RU or MRU.
  • the LDPC tone mapping distance parameters D_TM and D_TM_DCM are defined as constant values for each RU or MRU size, and the values for other RU or MRU sizes can be as shown in Table 3.
  • Table 3 shows the LDPC tone mapping distances for each RU or MRU size within an 80 MHz frequency subblock.
  • LDPC tone mapping may be performed separately for each frequency subblock in the portion of the RU or MRU within that frequency subblock.
  • the values of the tone mapping parameters D TM_l and D TM_DCM_l for the portion of the RU or MRU within the first frequency subblock may be determined based on Table 3.
  • D TM_l represents the LDPC tone mapping distance for the rth RU or part of MRU located in the first frequency subblock when DCM is not applied.
  • D TM_DCM_l represents the LDPC tone mapping distance for the rth RU or part of MRU located in the lth frequency subblock when DCM is applied.
  • the value of l can be one of 0, 1, 2, and 3 depending on the size of the RU or MRU.
  • the LDPC tone mapping for the LDPC encoded stream for user u in the rth RU or part of the MRU located in the first 80 MHz frequency subblock can be performed by permuting the complex stream generated by the constellation mapper.
  • k can be (0, 1, ..., N SD_l -1) for 26-tone, 52-tone, 52+26-tone, 106-tone, 106+26-tone, 242-tone, 484-tone, 484+242-tone, and 996-tone RU or MRU in the lth frequency subblock.
  • i can be (1, 2, ..., N SS,r,u )
  • n can be (0, 1, ..., N SYM -1).
  • l can be 0 for 26-ton, 52-ton, 52+26-ton, 106-ton, 106+26-ton, 242-ton, 484-ton, 484+242-ton, and 996-ton RU or MRU, (0, 1) for 996+484-ton, 996+484+242-ton, and 2x996-ton RU or MRU, (0, 1, 2) for 2x996+484-ton and 3x996-ton MRU, and (0, 1, 2, 3) for 3x996+484-ton and 4x996-ton RU or MRU.
  • N SD_l represents the number of data tones in the rth RU or MRU part located in the lth frequency subblock
  • t(k,l) can be defined as in mathematical expression 6.
  • D TM_l represents the LDPC tone mapping distance for the rth RU or MRU part located in the lth frequency subblock when DCM is not applied as described above.
  • the LDPC tone mapping for the LDPC encoded stream corresponding to user u in the rth RU or part of the MRU located in the first 80 MHz frequency subblock can be performed by permuting the complex stream generated by the constellation mapper.
  • k can be (0, 1, ..., N SD_l -1) for the RU or MRU portion in the lth frequency subblock corresponding to 26-tone, 52-tone, 52+26-tone, 106-tone, 106+26-tone, 242-tone, 484-tone, 484+242-tone, and 996-tone in the lth frequency subblock.
  • i can be (1, 2, ..., N SS ,r,u )
  • n can be (0, 1, ..., N SYM -1).
  • l can be 0 for 26-ton, 52-ton, 52+26-ton, 106-ton, 106+26-ton, 242-ton, 484-ton, 484+242-ton, and 996-ton RU or MRU, (0, 1) for 996+484-ton, 996+484+242-ton, and 2x996-ton RU or MRU, (0, 1, 2) for 2x996+484-ton and 3x996-ton MRU, and (0, 1, 2, 3) for 3x996+484-ton and 4x996-ton RU or MRU.
  • N SD_l represents the number of data tones of the rth RU or MRU part located in the lth frequency subblock when DCM is applied
  • t(k,l) can be defined as in Equation 8.
  • D DCM_TM_l represents the LDPC tone mapping distance for the rth RU or MRU part located in the lth frequency subblock when DCM is applied as described above.
  • LDPC tone mappers for 26, 52, 52+26, 106, 106+26, 242, 484, 996-tone RU or MRU can be defined within one frequency subblock. LDPC tone mapping can be performed separately for each 80 MHz frequency subblock.
  • mathematical expression 9 can be applied to BCC coded spatial streams.
  • k can be (0, 1, ..., N SD_l -1) for 26-tone, 52-tone, 52+26-tone, 106-tone, 106+26-tone, 242-tone, 484-tone, 484+242-tone, and 996-tone RU or MRU in the lth frequency subblock.
  • i is (1, 2, ..., N SS,r,u )
  • n can be (0, 1, ..., N SYM -1).
  • l can be 0 for 26-tone, 52-tone, 52+26-tone, 106-tone, 106+26-tone, 242-tone RU or MRU.
  • u can be (0, 1, ..., N user,r -1)
  • r can be (0, 1, ..., N RU -1).
  • PSD power spectral density
  • LPI low power indoor
  • Tx maximum transmit
  • a PSD restriction of 10 dBm/MHz may apply in the 2.4 GHz band in EU/China/Japan/Korea. This would result in a maximum Tx power of approximately 17 dBm for a conventional 52-tone RU. If the PSD restriction can be circumvented in the 5 GHz band, the transmit power can be increased. For example, the maximum transmit power for a conventional 52-tone RU is 24 dBm, which is still 6 dBm below the maximum allowable effective isotropic radiated power (EIRP) of 30 dBm.
  • 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 DRUs can use higher power. For example, a 52-tone DRU across 80 MHz has only one tone per MHz, while there are roughly 13 tones per MHz for a 52-tone RRU. Assuming a PSD limit of -1 dBm/MHz in the 6 GHz LPI band, the transmit power for a 52-tone RU can be increased by 11 dB when using DRUs. This increased transmit power allows for higher MCS applications and longer ranges.
  • 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 the DRU.
  • the DRU applies higher transmission power to all tones, and thus the spectral efficiency can be greatly improved. In this way, the DRU can be particularly usefully applied in UL-OFDMA.
  • APs can also utilize DRUs.
  • APs may perform DL-OFDMA transmissions to STAs using only some of DRU1, DRU2, and DRU3, in which case the transmit power boost due to the use of DRUs may be applied.
  • tones within a DRU can be distributed as far apart as possible.
  • a DRU containing one tone per MHz may be considered an optimal example.
  • the size of a DRU (or the number of available tones contained in a DRU, i.e., the number of remaining tones excluding unusable tones such as null tone, guard tone, and DC tone) can be defined to be the same as the size of an RRU (or the number of available tones contained in an RRU). Accordingly, the impact on various technologies defined based on existing RRUs can be minimized.
  • the table below shows examples of achievable power boost (in dB) for various DRUs distributed over different bandwidths.
  • 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 one or more TB PPDU transmissions and may request TB PPDU transmissions.
  • the trigger frame may also include other information required by an STA transmitting a TB PPDU in response thereto.
  • the trigger frame may include common info and user info list fields 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), presence of CS (channel sensing) required, UL BW (bandwidth), etc.
  • Fig. 12 shows 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, BFRP (Beamforming Report Poll), MU-BAR (multi user-block acknowledgement request), MU-RTS (multi user-request to send), BSRP (Buffer Status Report Poll), GCR (groupcast with retries) MU-BAR, BQRP (Bandwidth Query Report Poll), and NFRP (NDP Feedback Report Poll), respectively, 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
  • MU-BAR 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 contains extended common information not provided in the common information field.
  • a user info list contains zero or more user info fields.
  • Figure 12 illustrates an example of an EHT variant user info field format.
  • the AID12 subfield basically indicates that it is a user information field for an STA having 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 info field.
  • the special user info field is a user info field that does not include user specific information but includes extended common information that is not provided in the common information field.
  • the special user info field can be identified by the AID12 value of 2007, and the special user info field flag subfield in the common information field can indicate whether the special user info field is included.
  • the RU allocation subfield can indicate the size and location of 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 Allocation subfield can be defined together with the settings of B0 and PS160 subfields of the RU Allocation subfield as shown in Table 5 below.
  • Table 5 shows an example of encoding of the PS160 subfield and the RU Allocation 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 6.
  • 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.
  • M-DRU Interleaver and tone mapper for transmission and reception based on multiple DRU
  • a DRU using distributed tones/subcarriers rather than an RRU using continuous tones/subcarriers can be applied.
  • a BCC interleaver and an LDPC tone mapper are used as representative examples, but the scope of this disclosure is not limited thereto and may be expanded to cases where other types of interleavers and tone mappers are utilized/applied.
  • the method proposed in the present disclosure may be based on not only a multi-DRU (M-DRU) configured/formed by a combination of DRUs distributed within the same channel, but also a multi-DRU (M-DRU) configured/formed by a combination of (specific) DRUs distributed across different channels.
  • M-DRU multi-DRU
  • M-DRU multi-DRU
  • a multi-DRU consisting of a combination of DRUs distributed within the same channel may include a 106+26-tone M-DRU, a 52+26-tone M-DRU, a 484+242-tone M-DRU, a 996+484-tone M-DRU, or a 996+484+242-tone M-DRU.
  • M-DRU multi-DRU
  • 20MHz+20MHz M-DRU, 40MHz+20MHz M-DRU, 40MHz+40MHz M-DRU, 80MHz+20MHz M-DRU, 80MHz+40MHz M-DRU, 80MHz+40MHz+20MHz M-DRU, 80MHz+80MHz M-DRU, 160MHz+80MHz M-DRU, 160MHz+160MHz M-DRU, etc. can be defined.
  • X MHz+Y MHz M-DRU may mean a combination of a DRU (or component M-DRU) distributed at X MHz and a DRU (or component M-DRU) distributed at Y MHz.
  • a component multi-DRU may mean a multi-DRU included in one channel utilized/included in the configuration of a multi-DRU (M-DRU).
  • 106+26-tone M-DRU 52+26-tone M-DRU, 26+26-tone M-DRU, 52+52-tone M-DRU, 106+106-tone M-DRU, etc.
  • 40MHz+20MHz M-DRU 106+26-tone M-DRU, 52+26-tone M-DRU, 106+52-tone M-DRU, 242+106-tone M-DRU, etc. can be defined.
  • 106+26-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, 52+52-tone M-DRU, 106+106-tone M-DRU, 242+242-tone M-DRU, etc. can be defined.
  • 80MHz+20MHz M-DRU 106+26-tone M-DRU, 242+52-tone M-DRU, 242+106-tone M-DRU, 484+106-tone M-DRU, etc. can be defined.
  • 80MHz+40MHz M-DRU 484+242-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, 106+52-tone M-DRU, 242+106-tone M-DRU, etc. can be defined.
  • 80MHz+40MHz+20MHz M-DRU 106+52+26-tone M-DRU, 242+106+52-tone M-DRU, 484+242+106-tone M-DRU, etc. can be defined.
  • 106+26-tone M-DRU 106+52-tone M-DRU, 52+52-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, etc. can be defined.
  • 484+242-tone M-DRU, 996+484-tone M-DRU, 996+484+242-tone M-DRU (wherein, 484-tone DRU and 242-tone DRU are DRUs (or component M-DRUs) included in one 160MHz channel), 996+996-tone M-DRU, 242+242-tone M-DRU, 484+484-tone M-DRU, 106+106-tone M-DRU, 106+26-tone M-DRU, 106+52-tone M-DRU, 52+52-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, etc. can be defined.
  • FIG. 13 and FIG. 14 illustrate an M-DRU-based PPDU transmission and reception method according to the present disclosure.
  • FIG. 13 is a diagram for explaining an example of a DRU tone plan-based PPDU reception method of a first STA according to the present disclosure.
  • a first STA may generate a PPDU including one or more fields to be transmitted on a multi-DRU (M-DRU) consisting of N (N>1) DRUs.
  • M-DRU multi-DRU
  • one or more fields may contain data fields.
  • step S1320 the first STA can transmit the PPDU to the second STA.
  • the DRUs belonging to the N DRUs may include a plurality of subcarriers distributed in the frequency domain, and parameters for an interleaver (e.g., a BCC interleaver) or a tone mapper (e.g., an LDPC tone mapper) for multiple DRUs may be applied based on at least one of the sizes of the DRUs belonging to the N DRUs or the distributed channels.
  • an interleaver e.g., a BCC interleaver
  • a tone mapper e.g., an LDPC tone mapper
  • the parameters for the interleaver or the tone mapper may be applied based on the entire N DRUs.
  • the parameters for the interleaver or the tone mapper may be applied based on a unit of at least one DRU that is less than or equal to 996 tones (e.g., DRU/M-DRU(s) within each 996-tone).
  • a parameter for the interleaver or the tone mapper may be applied based on a unit of a specific channel size (e.g., 80MHz/160MHz).
  • a unit of a specific channel size e.g. 80MHz/160MHz.
  • the parameter for the interleaver or the tone mapper may be applied based on the unit of the one or more DRUs.
  • the parameter for the interleaver or the tone mapper may be applied based on a unit of at least one DRU that is less than or equal to 996 tones. Additionally or alternatively, for a plurality of DRUs distributed to different channels within the specific channel size among the N DRUs, a parameter for the interleaver or the tone mapper may be applied based on the entirety of the plurality of DRUs.
  • parameters for an interleaver or tone mapper according to the sizes of the first DRU and the second DRU can be defined as in the following examples.
  • the parameters ⁇ N SD , N COL , N ROW , N ROT ⁇ for the BCC interleaver are defined as ⁇ 48, 16, 3*N BPSCS , 11 ⁇ or ⁇ 24, 8, 3*N BPSCS , 2 ⁇ depending on whether DCM is used, and the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 3, 1 ⁇ .
  • the parameters ⁇ N SD , N COL , N ROW , N ROT ⁇ for the BCC interleaver are defined as ⁇ 96, 16, 6*N BPSCS , values within 18 and 29 ⁇ or ⁇ 48, 16, 3*N BPSCS , values within 2 and 11 ⁇ depending on whether there is DCM, and the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 4, 3 ⁇ .
  • the parameters ⁇ N SD , N COL , N ROW , N ROT ⁇ for the BCC interleaver are defined as ⁇ 204, 17, 12*N BPSCS , values within 31 and 58 ⁇ or ⁇ 102, 17, 6*N BPSCS , values within 11 and 29 ⁇ depending on whether DCM is used, and the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 6, 3 ⁇ .
  • the parameters ⁇ N SD , N COL , N ROW , N ROT ⁇ for the BCC interleaver are defined as ⁇ 150, 25, 6*N BPSCS , values within 31 and 58 ⁇ or ⁇ 75, 25, 3*N BPSCS , values within 11 and 29 ⁇ depending on whether DCM is used, and the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 6, 3 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 12, 8 or 12 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 12, 9 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 6, 3 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 15, 5 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 18, 9 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 20, 14 ⁇ .
  • parameters for an interleaver or a tone mapper according to the sizes of the first DRU, the second DRU, and the third DRU may be defined as in the following examples.
  • the parameters ⁇ N SD , N COL , N ROW , N ROT ⁇ for the BCC interleaver are defined as ⁇ 174, 29, 6*N BPSCS , values within 31 and 58 ⁇ or ⁇ 87, 29, 3*N BPSCS , values within 11 and 29 ⁇ depending on whether DCM is used, and the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 6, 3 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 12, 8, or 12 ⁇ .
  • the parameters ⁇ D TM , D TM_DCM ⁇ for the LDPC tone mapper can be defined as ⁇ 12, 6 ⁇ .
  • 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 to be transmitted on multiple DRUs composed of N DRUs, and transmit the corresponding PPDU to the second STA.
  • 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 below when executed by one or more processors (102).
  • FIG. 14 is a diagram for explaining an example of a DRU tone plan-based PPDU transmission 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.
  • the second STA can decode one or more fields received on a multi-DRU (M-DRU) consisting of N (N>1) DRUs.
  • M-DRU multi-DRU
  • the DRUs belonging to the N DRUs may include a plurality of subcarriers distributed in the frequency domain, and parameters for an interleaver (e.g., a BCC interleaver) or a tone mapper (e.g., an LDPC tone mapper) for multiple DRUs may be applied based on at least one of the sizes of the DRUs belonging to the N DRUs or the distributed channels.
  • an interleaver e.g., a BCC interleaver
  • a tone mapper e.g., an LDPC tone mapper
  • 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 a first STA and decode the one or more fields received on a multiple DRU composed of N 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 below when executed by one or more processors (202).
  • FIGS. 13 and 14 may correspond to some of the various examples of the present disclosure.
  • various examples of the present disclosure including the examples of FIGS. 13 and 14, will be described in more detail.
  • M-DRUs multiple DRUs
  • This embodiment relates to a method of applying a BCC interleaver and/or an LDPC tone mapper to an M-DRU configured/formed by combining DRUs distributed within the same channel.
  • the method described in this embodiment can be applied to various M-DRUs configured by combining distributed DRUs (or M-DRUs) within the same channel as described above in the present disclosure.
  • a BCC interleaver and an LDPC tone mapper may be applied to each DRU, respectively.
  • parameters previously defined for RRUs of the same size e.g., see Tables 1 to 3 may be reused.
  • the BCC interleaver and LDPC tone mapper may be applied to the entire multi-DRU (M-DRU). In this case, the parameters previously defined for the RRUs of the same size (e.g., see Tables 1 to 3) may be reused.
  • the BCC interleaver and LDPC tone mapper may be applied to each DRU (or M-DRU) within 996 tones. In this case, the parameters previously defined for the RRUs of the same size (e.g., see Tables 1 to 3) may be reused.
  • the BCC interleaver and LDPC tone mapper can be applied to the entire M-DRU.
  • the LDPC tone mapper can be applied to each of the 996-tone DRU and the 484-tone DRU, and in 996+484+242-tone M-DRU, the LDPC tone mapper can be applied to each of the 996-tone DRU and the 484+242-tone M-DRU.
  • the BCC interleaver and LDPC tone mapper can be applied to the entire multi-DRU (M-DRU) regardless of the size of the multi-DRU (M-DRU).
  • the parameters previously defined for the same-sized RRU e.g., see Tables 1 to 3 can be reused.
  • 996+484-tone M-DRU and 996+484+242-tone M-DRU a new definition is required, and since the size is 242 tones or larger, the LDPC tone mapper parameters as in Table 7 can be defined.
  • This embodiment relates to a method of applying a BCC interleaver and/or an LDPC tone mapper to an M-DRU configured/formed by combining DRUs distributed to different channels.
  • the method described in this embodiment can be applied to various M-DRUs configured by combining DRUs (or M-DRUs) distributed in different channels as described above in this disclosure.
  • a BCC interleaver and an LDPC tone mapper may be applied to each DRU, respectively.
  • previously defined parameters e.g., see Tables 1 to 3
  • RRUs of the same size may be reused. This may be easy to implement in that each DRU is a distributed DRU on a different channel.
  • a BCC interleaver and an LDPC tone mapper may be applied in units of 80MHz channels (or 160MHz channels), respectively.
  • the parameters may be reused, and new parameters may need to be defined for M-DRUs of a specific size.
  • the definition of new parameters is specifically described in Embodiment 3.
  • a separate BCC interleaver and LDPC tone mapper may be applied to the DRU of the 80MHz channel.
  • the BCC interleaver and LDPC tone mapper may be applied to the entire 40MHz+20MHz M-DRU.
  • the BCC interleaver and LDPC tone mapper may be applied to each DRU.
  • separate BCC interleavers and LDPC tone mappers may be applied to the DRUs distributed across the 80MHz channel (or the 160MHz channel).
  • previously defined parameters for the RRUs of the same size may be reused.
  • the BCC interleaver and LDPC tone mapper may be applied to all the DRUs distributed across the remaining channels smaller than 80MHz (or 160MHz).
  • the parameters may be reused, and new parameters may need to be defined for M-DRUs of a specific size. The definition of new parameters is specifically described in Embodiment 3.
  • a separate BCC interleaver and LDPC tone mapper can be applied to the DRU of the 80MHz channel.
  • the BCC interleaver and LDPC tone mapper can be applied to the entire multi-DRU (M-DRU).
  • a BCC interleaver and an LDPC tone mapper may be applied to the entire multi-DRU (M-DRU).
  • M-DRU multi-DRU
  • the parameters may be reused, and new parameters may need to be defined for M-DRUs of a specific size.
  • the definition of new parameters is specifically described in Embodiment 3.
  • a BCC interleaver and an LDPC tone mapper may be applied to each DRU (or M-DRU) within 996 tones.
  • the BCC interleaver and the LDPC tone mapper may be applied to the entire multi-DRU (M-DRU) regardless of the size of the M-DRU.
  • M-DRU multi-DRU
  • the parameters may be reused, and new parameters may need to be defined for M-DRUs of a specific size.
  • the definition of new parameters is specifically described in Embodiment 3.
  • This embodiment is a method for newly defining parameters required to apply a BCC interleaver and/or an LDPC tone mapper to a multi-DRU (M-DRU) configured by combining DRUs located on different channels.
  • M-DRU multi-DRU
  • M-DRU multi-DRU
  • 20MHz+20MHz M-DRU 40MHz+20MHz M-DRU, 40MHz+40MHz M-DRU, 80MHz+20MHz M-DRU, 80MHz+40MHz M-DRU, 80MHz+40MHz+20MHz M-DRU, 80MHz+80MHz M-DRU, 160MHz+80MHz M-DRU, 160MHz+160MHz M-DRU, are described.
  • 106+26-tone M-DRU For 20MHz+20MHz M-DRU, 106+26-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, 52+52-tone M-DRU, 106+106-tone M-DRU, etc. can be defined.
  • Table 8 illustrates new parameters for BCC interleaver operation for 20MHz+20MHz M-DRU
  • Table 9 illustrates new parameters for LDPC tone mapper operation for 20MHz+20MHz M-DRU.
  • the existing defined parameters for the 52-tone RRU can be reused.
  • N COL value when applying DCM may not need to be multiplied by N BPSCS , and N ROT may not be considered.
  • N COL and N ROW can be applied as a pair.
  • N COL is 12
  • N ROW can be 8*N BPSCS .
  • 106+26-tone M-DRU For 40MHz+20MHz M-DRU, 106+26-tone M-DRU, 52+26-tone M-DRU, 106+52-tone M-DRU, 242+106-tone M-DRU, etc. can be defined.
  • the BCC interleaver and the LDPC tone mapper are applied to the entire 106+52-tone M-DRU, the related parameters need to be newly defined as shown in Tables 10 and 11. Additionally, if the LDPC tone mapper is applied to the entire 242+106-tone M-DRU, the related parameters need to be newly defined as shown in Table 11.
  • Table 10 illustrates new parameters for BCC interleaver operation for 40MHz+20MHz M-DRU
  • Table 11 illustrates new parameters for LDPC tone mapper operation for 40MHz+20MHz M-DRU.
  • 106+26-tone M-DRU For 40MHz+40MHz M-DRU, 106+26-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, 52+52-tone M-DRU, 106+106-tone M-DRU, 242+242-tone M-DRU, etc. can be defined.
  • new parameters need to be defined when the BCC interleaver and LDPC tone mapper are applied to the entire 242+242-tone M-DRU.
  • the existing defined parameters for the 484-tone RRU can be reused.
  • 12 can be used for D TM and 9 can be used for D TM_DCM .
  • 106+26-tone M-DRU For 80MHz+20MHz M-DRU, 106+26-tone M-DRU, 242+52-tone M-DRU, 242+106-tone M-DRU, 484+106-tone M-DRU, etc. can be defined.
  • Table 12 illustrates new parameters for LDPC tone mapper operation for 80MHz+20MHz M-DRU.
  • M-DRU For 80MHz+40MHz M-DRU, 484+242-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, 106+52-tone M-DRU, 242+106-tone M-DRU, etc. can be defined.
  • 106+52+26-tone M-DRU For 80MHz+40MHz+20MHz M-DRU, 106+52+26-tone M-DRU, 242+106+52-tone M-DRU, 484+242+106-tone M-DRU, etc. can be defined.
  • the BCC interleaver and the LDPC tone mapper are applied to the entire 106+52+26-tone M-DRU, the related parameters need to be newly defined as shown in Tables 13 and 14. Additionally, if the LDPC tone mapper is applied to the entire 242+106+52-tone M-DRU, 484+242+106-tone M-DRU, the related parameters need to be newly defined as shown in Table 14.
  • Table 13 illustrates new parameters for BCC interleaver operation for 80MHz+40MHz+20MHz M-DRU
  • Table 14 illustrates new parameters for LDPC tone mapper operation for 80MHz+40MHz+20MHz M-DRU.
  • the LDPC tone mapper when the LDPC tone mapper is applied separately to the DRUs distributed in the 80MHz channel and applied to the rest at once (i.e., to the entire remaining channels), the parameters applied to the 242+106+52-tone M-DRU, 484+242+106-tone M-DRU, 106+52-tone M-DRU, and 242+106-tone M-DRU need to be defined.
  • the new parameters described above in the present embodiment e.g., see Table 10 and Table 11
  • Table 15 illustrates new parameters for LDPC tone mapper operation for 80MHz+80MHz M-DRU.
  • 106+26-tone M-DRU 106+52-tone M-DRU, 52+52-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, etc. can be defined.
  • 484+242-tone M-DRU, 996+484-tone M-DRU, 996+484+242-tone M-DRU (wherein, 484-tone DRU and 242-tone DRU are DRUs (or component M-DRUs) included in one 160MHz channel), 996+996-tone M-DRU, 242+242-tone M-DRU, 484+484-tone M-DRU, 106+106-tone M-DRU, 106+26-tone M-DRU, 106+52-tone M-DRU, 52+52-tone M-DRU, 52+26-tone M-DRU, 26+26-tone M-DRU, etc. can be defined.
  • Table 16 illustrates new parameters for LDPC tone mapper operation for 160MHz+160MHz M-DRU.
  • FIG. 15 is a diagram for explaining a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure.
  • the transmitting device and the receiving STA may be APs and/or non-AP STAs.
  • the transmitting STA can obtain control information related to the tone plan (or RU/DRU) described above (S105).
  • the control information related to the tone plan can include the size and location of the RU/DRU, control information related to the RU/DRU, information about the frequency band in which the RU/DRU is included, information about the STA receiving the RU/DRU, 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 U-SIG and UHR-SIG-A/B fields including control information regarding a tone plan.
  • the step of configuring/generating a PPDU may include a step of configuring a field including control information indicating a bandwidth of the PPDU and/or a step of configuring a field including control information (e.g., an N bitmap) indicating a size/position of an RU/DRU and/or a step of configuring a field including an identifier (e.g., AID) of an STA receiving the RU/DRU and/or a coding scheme to be applied.
  • control information e.g., an N bitmap
  • AID e.g., AID
  • the step of configuring/generating a PPDU may include a step of generating an STF/LTF sequence to be transmitted via a specific RU/DRU.
  • the STF/LTF sequence may be generated based on a preset STF generation sequence/LTF generation sequence.
  • the step of configuring/generating a PPDU may include a step of generating a data field (i.e., MPDU) to be transmitted via a specific RU/DRU.
  • a data field i.e., MPDU
  • parameter values of appropriate BCC interleaver and LDPC tone mapper may be applied.
  • 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
  • a receiving STA can decode the PPDU and obtain control information related to the tone plan (or RU/DRU) (S120).
  • a receiving STA can decode L-SIG and U-SIG/UHR-SIG (such as UHR-SIG-A/B) of a PPDU based on L-STF/LTF, and obtain information included in the L-SIG and U-SIG/UHR-SIG (such as UHR-SIG-A/B) fields.
  • Information about various tone plans (i.e., RU/DRU) and coding of the present disclosure can be included in the UHR-SIG (such as UHR-SIG-A/B), and the receiving STA can obtain information about the tone plan (i.e., RU/DRU) and coding through the UHR-SIG.
  • an AP receiving it may already know information about the tone plan (i.e., RU/DRU) and coding.
  • the receiving STA can decode the remaining part of the PPDU based on the acquired tone-plan (i.e., RU/DRU) and coding information (S125). For example, the receiving STA can decode the STF/LTF field of the PPDU based on the tone-plan (i.e., RU/DRU) information. In addition, the receiving STA can decode the data field of the PPDU based on the tone-plan (i.e., RU/DRU) and coding information, and obtain the MPDU included in the data field.
  • the tone-plan i.e., RU/DRU
  • the receiving STA may perform a processing operation to forward the decoded data to a higher layer (e.g., MAC layer). Additionally, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data forwarded to the higher layer, the receiving STA may perform a subsequent operation.
  • a higher layer e.g., MAC layer
  • the efficiency of resource utilization can be improved by transmitting/receiving one or more fields of PPDU based on the data symbol and/or block-based DRU tone plan according to the present disclosure. Additionally, based on the method of configuring multiple DRUs (M-DRU) by utilizing the combination between DRUs according to the present disclosure, there is a technical effect of improving power gain and/or data rate.
  • M-DRU multiple DRUs
  • 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 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 comprises a non-transitory computer-readable storage medium.
  • the features described in this disclosure may be incorporated into software and/or firmware stored on any one of the machine-readable media to control the hardware of the processing system and to 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 has been 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

Sont divulgués un procédé et un dispositif de transmission ou de réception dans un système LAN sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée. Selon un aspect de la présente divulgation, le procédé peut comprendre les étapes consistant à : générer, par une première station (STA), une PPDU comprenant au moins un champ ; et transmettre, par la première STA, la PPDU à une seconde STA. Dans la présente divulgation, le ou les champs sont mappés sur de multiples DRU comprenant N (N > 1) DRU, une DRU appartenant aux N DRU comprend une pluralité de sous-porteuses réparties dans un domaine fréquentiel, et un paramètre pour un entrelaceur ou un mappeur de tonalités pour les multiples DRU peut être appliqué sur la base d'au moins un élément parmi la taille de la DRU appartenant aux N DRU ou un canal distribué.
PCT/KR2024/019703 2023-12-04 2024-12-04 Procédé et dispositif de transmission ou de réception dans système lan sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée Pending WO2025121871A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20230173549 2023-12-04
KR10-2023-0173549 2023-12-04

Publications (1)

Publication Number Publication Date
WO2025121871A1 true WO2025121871A1 (fr) 2025-06-12

Family

ID=95980274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/019703 Pending WO2025121871A1 (fr) 2023-12-04 2024-12-04 Procédé et dispositif de transmission ou de réception dans système lan sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée

Country Status (1)

Country Link
WO (1) WO2025121871A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170126447A1 (en) * 2015-10-30 2017-05-04 Qualcomm Incorporated Systems and methods for channel interleaving in wireless networks
US20230006805A1 (en) * 2021-07-02 2023-01-05 Mediatek Singapore Pte. Ltd. Optimization Of BCC Interleaver And LDPC Tone Mapper For Distributed-Tone Resource Units And Distributed-Tone Multi-Resource Units

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170126447A1 (en) * 2015-10-30 2017-05-04 Qualcomm Incorporated Systems and methods for channel interleaving in wireless networks
US20230006805A1 (en) * 2021-07-02 2023-01-05 Mediatek Singapore Pte. Ltd. Optimization Of BCC Interleaver And LDPC Tone Mapper For Distributed-Tone Resource Units And Distributed-Tone Multi-Resource Units

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
EUNSUNG PARK (LG ELECTRONICS): "Considerations on RU / MRU Designs for UHR", IEEE DRAFT; 11-23-0281-00-0UHR-CONSIDERATIONS-ON-RU-MRU-DESIGNS-FOR-UHR, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 UHR, no. 0, 10 April 2023 (2023-04-10), Piscataway, NJ USA, pages 1 - 18, XP068202162 *
EUNSUNG PARK (LG ELECTRONICS): "dRU Proposal", IEEE DRAFT; 11-23-1919-00-00BN-DRU-PROPOSAL, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 UHR; 802.11bn, no. 0, 10 November 2023 (2023-11-10), Piscataway, NJ USA, pages 1 - 22, XP068206993 *
EUNSUNG PARK (LG ELECTRONICS): "dRU Signaling for UHR", IEEE DRAFT; 11-23-1117-00-0UHR-DRU-SIGNALING-FOR-UHR, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 UHR, no. 0, 10 July 2023 (2023-07-10), Piscataway, NJ USA, pages 1 - 28, XP068204114 *

Similar Documents

Publication Publication Date Title
WO2023191499A1 (fr) Procédé et dispositif d'attribution de canal basée sur le fonctionnement de points d'accès multiples dans un système lan sans fil
WO2024177472A1 (fr) Procédé et dispositif de transmission ou de réception sur la base d'une attribution d'unité de ressources distribuées dans un système de réseau local sans fil
WO2023229312A1 (fr) Procédé et dispositif pour la transmission ou la réception d'une 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
WO2023234720A1 (fr) Procédé et dispositif de commande de mode de fonctionnement pour bande passante étendue dans un système lan sans fil
WO2023204514A1 (fr) Procédé et dispositif d'émission et de réception d'unité de données de protocole de couche physique agrégée dans un système lan sans fil
WO2023182854A1 (fr) Procédé et dispositif de transmission de ppdu dans un système lan sans fil
WO2023018275A1 (fr) Procédé et dispositif d'émission/réception de réponse de compte rendu de rétroaction de ndp dans un système de lan sans fil
WO2025121871A1 (fr) Procédé et dispositif de transmission ou de réception dans système lan sans fil, sur la base d'un plan de tonalité d'unité de ressource distribuée
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
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
WO2024253368A1 (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 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
WO2025100962A1 (fr) Procédé et dispositif pour l'émission et la réception d'une ppdu agrégée dans un système de réseau local sans fil
WO2024181732A1 (fr) Procédé et dispositif de transmission et de réception basés sur un plan de tonalité d'unité de ressource distribuée limité dans un système lan sans fil
WO2024172382A1 (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 lan sans fil
WO2024172582A1 (fr) Procédé et appareil d'attribution d'unités de ressources distribuées dans un système de réseau local sans fil
WO2025147004A1 (fr) Procédé et dispositif pour une opération de relais dans un système de réseau local 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
WO2025095695A1 (fr) Procédé et dispositif pour émission et réception de ppdu dans un système de réseau local sans fil
WO2023204476A1 (fr) Procédé et appareil pour mettre en œuvre une communication basée sur une perforation de préambule dans un système wlan
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
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
WO2024210374A1 (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
WO2024186119A1 (fr) Procédé et dispositif d'émission/de réception de ppdu dans un système de réseau local sansf 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: 24901057

Country of ref document: EP

Kind code of ref document: A1