[go: up one dir, main page]

WO2025063505A1 - Commutation de sous-canal pour réseau local sans fil - Google Patents

Commutation de sous-canal pour réseau local sans fil Download PDF

Info

Publication number
WO2025063505A1
WO2025063505A1 PCT/KR2024/012078 KR2024012078W WO2025063505A1 WO 2025063505 A1 WO2025063505 A1 WO 2025063505A1 KR 2024012078 W KR2024012078 W KR 2024012078W WO 2025063505 A1 WO2025063505 A1 WO 2025063505A1
Authority
WO
WIPO (PCT)
Prior art keywords
txop
frame
duration
ppdu
response
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/012078
Other languages
English (en)
Inventor
Jeong Soo Lee
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.)
Frontside LLC
Original Assignee
Frontside LLC
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 Frontside LLC filed Critical Frontside LLC
Publication of WO2025063505A1 publication Critical patent/WO2025063505A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • 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 wireless local area network (WLAN), and more particularly, to a method for switching a subchannel in the WLAN and a device using the same.
  • WLAN wireless local area network
  • a wireless local area network may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by a number of client devices also referred to as stations (STAs).
  • APs access points
  • STAs stations
  • Orthogonal frequency division multiple access is a multiple access scheme where different subsets of subcarriers are allocated to different users, and this scheme allows simultaneous data transmission to or from one or more users.
  • a physical layer protocol data unit is a data unit (or data packet) to carry various information in the WLAN.
  • PPDU physical layer protocol data unit
  • OFDMA OFDMA
  • users are allocated different subsets of subcarriers that can change from one PPDU to the next.
  • an AP may allocate different resource units (RUs) for STAs.
  • the AP can simultaneously transmit various formats of PPDUs to multiple STAs.
  • a network allocation vector is an indicator, maintained by each STA, of time periods when transmission onto the wireless medium (WM) is not initiated by the STA regardless of whether the STA's clear channel assessment (CCA) function senses that the WM is busy.
  • Transmission opportunity is an interval of time during which a particular STA has the right to initiate frame exchange sequences onto the WM.
  • the present disclosure provides a method for transmission opportunity (TXOP) operation in a wireless local area network.
  • TXOP transmission opportunity
  • the present disclosure further provides a device for TXOP operation in a wireless local area network.
  • a method performed by a station (STA) operating as a transmission opportunity (TXOP) responder includes receiving, from a TXOP owner, a control frame to initiate a frame exchange, and transmitting, to the TXOP owner, a response frame as a response to the control frame.
  • the response frame includes pause information which indicates a pause duration during which the TXOP owner ceases to transmit a frame to the TXOP responder.
  • a device operating as a transmission opportunity (TXOP) responder includes a processor, and a memory operatively coupled with the processor and configured to store instructions that, when executed by the processor, cause the device to perform functions.
  • the functions include receiving, from a TXOP owner, a control frame to initiate a frame exchange, and transmitting, to the TXOP owner, a response frame as a response to the control frame.
  • the response frame includes pause information which indicates a pause duration during which the TXOP owner ceases to transmit a frame to the TXOP responder.
  • non-primary channel access mechanism is provided to support signaling regarding features and resource allocations.
  • FIG. 1 shows a block diagram of an example wireless communication network.
  • FIG. 2 shows a block diagram of an example wireless communication device.
  • FIGs. 3 and 4 show various examples of PPDUs usable for wireless communication between an AP and a number of STAs.
  • FIG. 5 shows an example of UL MU transmission.
  • FIG. 6 shows an example of multi-link operation.
  • FIG. 7 shows an example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • FIG. 8 shows another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • FIG. 9 shows still another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • FIG. 10 shows still another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • FIG. 11 shows an example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • FIG. 12 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • FIG. 13 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • FIG. 14 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • FIG. 15 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • the following description is directed to certain implementations for the purposes of describing innovative aspects of this disclosure.
  • RF radio frequency
  • IEEE 802.11 the Institute of Electrical and Electronics Engineers
  • the IEEE 802.15 the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G or 5G (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), among others.
  • SIIG Bluetooth Special Interest Group
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • the described implementations can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) MIMO.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • SU single-user
  • MIMO multiple-input multiple-output
  • MU multi-user
  • the described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an internet of things (I
  • OFDMA is an OFDM-based multiple access scheme where different subsets of subcarriers are allocated to different users, and this scheme allows simultaneous data transmission to or from one or more users.
  • OFDMA users are allocated different subsets of subcarriers that can change from one PPDU to the next. Similar to OFDM, OFDMA employs multiple subcarriers, but the subcarriers are divided into several groups where each group is referred to as a resource unit (RU).
  • RU resource unit
  • a physical layer protocol data unit may span one or more subchannels and may include a preamble portion and a data portion. Signaling refers to control fields or information in the preamble portion that can be used by a wireless communication device to interpret another field or portion of the preamble portion or the data portion of the PPDU.
  • a wireless channel may be formed from multiple subchannels.
  • a subchannel may include a set of subcarriers. Portions of the wireless channel bandwidth can be divided or grouped to form different resource units (RUs).
  • An RU may be a unit for resource allocation and may include one or more subcarriers.
  • a preamble portion of a PPDU may include signaling to indicate which RUs are allocated to different devices.
  • signaling include indicators regarding which subchannels include further signaling or which subchannels may be punctured.
  • PPDUs and related structures defined for current wireless communication protocols. As new wireless communication protocols enable enhanced features, new preamble designs are needed support signaling regarding features and resource allocations. Furthermore, it desirable to define a new preamble signaling protocol that can support future wireless communication protocols.
  • FIG. 1 shows a block diagram of an example wireless communication network.
  • the wireless communication network 10 can be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will hereinafter be referred to as WLAN 10).
  • WLAN 10 can be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as that defined by the IEEE 802.11-2016 specification or amendments thereof including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).
  • the WLAN 10 may include numerous wireless communication devices such as an access point (AP) 11 and multiple stations (STAs) 12. While only one AP 11 is shown, the WLAN network 10 also can include multiple APs.
  • Each of the STAs 12 also may be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other possibilities.
  • the STAs 12 may represent various devices such as mobile phones, personal digital assistant (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (for example, TVs, computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices (“remotes”), printers, kitchen or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), among other possibilities.
  • PDAs personal digital assistant
  • netbooks notebook computers
  • tablet computers laptops
  • display devices for example, TVs, computer monitors, navigation systems, among others
  • music or other audio or stereo devices for example, remote control devices (“remotes”), printers, kitchen or other household appliances
  • key fobs
  • a single AP 11 and an associated set of STAs 12 may be referred to as a basic service set (BSS), which is managed by the respective AP 11.
  • the BSS may be identified to users by a service set identifier (SSID), as well as to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP 11.
  • the AP 11 periodically broadcasts beacon frames (“beacons”) including the BSSID to enable any STAs 12 within wireless range of the AP 11 to “associate” or re-associate with the AP 11 to establish a respective communication link (hereinafter also referred to as a “Wi-Fi link”), or to maintain a communication link, with the AP 11.
  • beacon frames including the BSSID to enable any STAs 12 within wireless range of the AP 11 to “associate” or re-associate with the AP 11 to establish a respective communication link (hereinafter also referred to as a
  • the beacons can include an identification of a primary channel used by the respective AP 11 as well as a timing synchronization function for establishing or maintaining timing synchronization with the AP 11.
  • the AP 11 may provide access to external networks to various STAs 12 in the WLAN via respective communication link.
  • each of the STAs 12 is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (for example, the 2.4 GHz, 5 GHz, 6 GHz or 60 GHz bands).
  • scans passive or active scanning operations
  • a STA 12 listens for beacons, which are transmitted by respective APs 11 at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to 1024 microseconds ( ⁇ s)).
  • TBTT target beacon transmission time
  • TUs time units
  • ⁇ s microseconds
  • Each STA 12 may be configured to identify or select an AP 11 with which to associate based on the scanning information obtained through the passive or active scans, and to perform authentication and association operations to establish a communication link with the selected AP 11.
  • the AP 11 assigns an association identifier (AID) to the STA 12 at the culmination of the association operations, which the AP 11 uses to track the STA 104.
  • AID association identifier
  • STAs 12 may form networks without APs 11 or other equipment other than the STA.
  • a network is an ad hoc network (or wireless ad hoc network).
  • Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks.
  • P2P peer-to-peer
  • ad hoc networks may be implemented within a larger wireless network such as the WLAN 10.
  • the STAs 12 may be capable of communicating with each other through the AP 11 using communication links, STAs 12 also can communicate directly with each other via direct wireless links. Additionally, two STAs 12 may communicate via a direct communication link regardless of whether both STAs 12 are associated with and served by the same AP 11.
  • one or more of the STAs 12 may assume the role filled by the AP 11 in a BSS.
  • Such a STA may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network.
  • GO group owner
  • the AP 11 and STAs 12 may function and communicate (via the respective communication links) according to the IEEE 802.11 family of wireless communication protocol standards (such as that defined by the IEEE 802.11-2016 specification or amendments thereof including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be). These standards define the WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers.
  • the AP 11 and STAs 12 transmit and receive wireless communications (hereinafter also referred to as “Wi-Fi communications”) to and from one another in the form of PPDUs.
  • Wi-Fi communications wireless communications
  • the AP 11 and STAs 12 in the WLAN 10 may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some implementations of the AP 11 and STAs 12 described herein also may communicate in other frequency bands, such as the 6 GHz band, which may support both licensed and unlicensed communications. The AP 11 and STAs 12 also can be configured to communicate over other frequency bands such as shared licensed frequency bands, where multiple operators may have a license to operate in the same or overlapping frequency band or bands.
  • Each of the frequency bands may include multiple channels (which may be used as subchannels of a larger bandwidth channel).
  • PPDUs conforming to the IEEE 802.11n, 802.11ac and 802.11ax standard may be transmitted over the 2.4 and 5 GHz bands, each of which is divided into multiple 20 MHz channels.
  • these PPDUs are transmitted over a physical channel having a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding.
  • PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 or 320 MHz by bonding together multiple 20 MHz channels (which may be referred to as subchannels).
  • Uplink means that the signal (or message or PPDU) is transmitted by a STA to an AP
  • downlink means that the signal (or message or PPDU) is transmitted by the AP to one or more STAs.
  • FIG. 2 shows a block diagram of an example wireless communication device.
  • the wireless communication device 50 can be an example of a device for use in a STA such as one of the STAs 12 described above with reference to FIG. 1. In some implementations, the wireless communication device 50 can be an example of a device for use in an AP such as the AP 11 described above with reference to FIG. 1. The wireless communication device 50 is capable of transmitting (or outputting for transmission) and receiving wireless communications (for example, in the form of wireless packets).
  • the wireless communication device can be configured to transmit and receive packets in the form of PPDUs and/or medium access control (MAC) protocol data units (MPDUs) conforming to an IEEE 802.11 wireless communication protocol standard, such as that defined by the IEEE 802.11-2016 specification or amendments thereof including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be.
  • MAC medium access control
  • the wireless communication device 50 can be, or can include, a chip, system on chip (SoC), chipset, package or device that includes one or more processor 51.
  • the processor 51 can include an intelligent hardware block or device such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) such as a field programmable gate array (FPGA), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • the processor 51 processes information received through a transceiver 53, and processes information to be output through the transceiver 53 through the wireless medium.
  • the processor 806 may implement a physical (PHY) layer and/or a MAC layer configured to perform various operations related to the generation and transmission of PPDUs, MPDUs, frames or packets.
  • a memory 52 can include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof.
  • the memory 808 also can store non-transitory processor- or computer-executable software code containing instructions that, when executed by the processor 51, cause the wireless communication device 50 to perform various operations described herein for wireless communication, including the generation, transmission, reception and interpretation of PPDUs, MPDUs, frames or packets.
  • various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs.
  • the transceiver 53 generally includes at least one radio frequency (RF) transmitter (or “transmitter chain”) for transmitting radio signals and at least one RF receiver (or “receiver chain”) for receiving radio signals.
  • RF transmitters and receivers may include various DSP circuitry including at least one power amplifier (PA) and at least one low-noise amplifier (LNA), respectively.
  • PA power amplifier
  • LNA low-noise amplifier
  • the RF transmitters and receivers may, in turn, be coupled to one or more antennas.
  • the wireless communication device 50 can include, or be coupled with, multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain).
  • VHT Very high throughput
  • HE high efficiency
  • EHT extremely high throughput
  • EHT STA may be used to represent a STA supporting at least EHT.
  • EHT STA can further support VHT and/or HE.
  • Ultra High Reliability is used to represent any later (post-EHT) version of a new wireless communication protocol conforming to a future IEEE 802.11 wireless communication protocol standard or other standard, and is for illustration purpose only.
  • 'UHR' may be referred to as other terms, for example, Ultra Low Latency (ULL), High Reliability (HR), etc.
  • the UHR PPDU may support future amendments to the IEEE 802.11 wireless communication standard.
  • FIGs. 3 and 4 show various examples of PPDUs usable for wireless communication between an AP and a number of STAs.
  • An PPDU may include a preamble portion and a data portion.
  • ‘Data’ of FIGs. 3-4 denotes the data portion which includes one or more PSDUs and appears after the preamble portion.
  • the data portion may be referred to as a payload.
  • a non-high-throughput (non-HT) PPDU supporting IEEE 802.11a/g includes a Legacy-Short Training Field (L-STF), a Legacy-Long Training Field (L-LTF), a Legacy-Signal (L-SIG) and a data portion.
  • L-SIG may be called as non-HT Signal.
  • a high-throughput (HT) PPDU supporting IEEE 802.11n includes an L-STF, a HT-SIG, a HT-STF, a HT-LTF and a data portion.
  • a VHT PPDU supporting IEEE 802.11ac includes an L-STF, L-SIG, a VHT-SIG-A, a VHT-STF, a VHT-LTF, a VHT-SIG-B and a data portion.
  • a HE PPDU supporting IEEE 802.11ax may include an HE single-user (SU) PPDU for SU transmission and an HE multi-user (MU) PPDU for MU transmission.
  • An extremely high throughput (EHT) PPDU supporting IEEE 802.11be may include an EHT MU PPDU for MU transmission and an EHT trigger based (TB) PPDU.
  • the preamble portion of a PPDU may include a first portion (or "legacy preamble") and a second portion (or “non-legacy preamble”).
  • the first portion may include L-STF, L-LTF and L-SIG.
  • the second portion may include at least one of HT-SIG, HT-STF, HT-LTF, VHT-SIG-A, VHT-STF, VHT-LTF, VHT-SIG-B, RL-SIG, HE-SIG-A, HE-STF, HE-LTF, HE-SIG-B, EHT-SIG, EHT-STF, EHT-LTF and U-SIG.
  • the L-STF may be used for frame detection, Automatic Gain Control (AGC), diversity detection, and coarse frequency/time synchronization.
  • the L-LTF may be used for fine frequency/time synchronization and channel estimation.
  • the L-SIG may include information indicating a total length of a corresponding PPDU (or information indicating a transmission time of a PSDU).
  • the VHT-SIG-A field carries information required to interpret VHT PPDUs.
  • the VHT-STF field is used to improve automatic gain control estimation in a MIMO.
  • the VHT-LTF field provides a means for the receiver to estimate the MIMO channel between the set of constellation mapper outputs and the receive chains.
  • the VHT-SIG-B field may be used for MU transmissions and may contain as signaling information usable by the STAs to decode data received in the DATA field, including, for example, a modulation and coding scheme (MCS) and beamforming information.
  • MCS modulation and coding scheme
  • the repeated legacy (RL)-SIG field in the HE PPDU and EHT PPDU is a repeat of the L-SIG field and is used to differentiate the HE PPDU and the EHT PPDU from non-HT PPDU, HT PPDU, and VHT PPDU.
  • HE-SIG-A carries information necessary to interpret HE PPDUs.
  • HE-SIG-A may indicate locations and lengths of HE-SIG-Bs, available channel bandwidths, etc.
  • HE-SIG-B may carry STA-specific scheduling information such as, for example, per-user MCS values and per-user RU allocation information. In the context of DL MU-OFDMA, such information enables the respective STA to identify and decode corresponding RUs in the associated data field.
  • VHT-STF, HE-STF or EHT-STF may be used to improve an AGC estimation in a MIMO transmission.
  • VHT-LTF, HE-LTF or EHT-LTF may be used to estimate a MIMO channel.
  • the universal signal field (U-SIG) field of EHT PPDU carries information necessary to interpret EHT PPDUs.
  • the U-SIG may include version independent fields and version dependent fields.
  • the version independent fields may include at least one of a version identifier, a PPDU bandwidth, an indication of whether the PPDU is a UL or a DL PPDU, a BSS color identifying a BSS, and a transmission opportunity (TXOP).
  • the PPDU bandwidth in the version independent fields indicates a transmission bandwidth of the PPDU, for example, 20 MHz, 40 MHz, 80 MHz, 160 MHz or 320 MHz.
  • the version identifier in the version independent fields may indicate a version (and associated format) for the version dependent fields.
  • a PPDU format may determine which other indicators are included in the version dependent fields as well as the version identifier. In some implementations, if the PPDU format indicates that the PPDU is an EHT TB PPDU, then the EHT-SIG may be omitted as shown in EHT TB PPDU of FIG. 4.
  • the version dependent fields of U-SIG may include punctured channel Information and EHT-SIG MCS.
  • the EHT-SIG MCS may Indicate an MCS used for modulating the EHT-SIG.
  • the PPDU bandwidth and the punctured channel information may be referred to collectively as frequency occupation indications.
  • the frequency occupation indications may permit WLAN devices on the wireless channel to determine the utilization of the various parts of the wireless channel. For example, the frequency occupation information may be used to indicate puncturing of some subchannels.
  • the EHT-SIG field provides additional signaling to the U-SIG field for STAs to interpret an EHT MU PPDU.
  • the EHT-SIG may carry STA-specific scheduling information such as, for example, per-user MCS values and per-user RU allocation information.
  • EHT-SIG includes a common field and at least one STA-specific field ("user specific field”).
  • the common field can indicate RU distributions to multiple STAs, indicate the RU assignments in the frequency domain, indicate which RUs are allocated for MU-MIMO transmissions and which RUs correspond to MU-OFDMA transmissions, and the number of users in allocations.
  • the user specific fields are assigned to particular STAs 104 and may be used to schedule specific RUs and to indicate the scheduling to other WLAN devices.
  • the EHT-SIG field of a 20 MHz EHT MU PPDU contains one EHT-SIG content channel.
  • the EHT-SIG field of an EHT MU PPDU that is 40 MHz or 80 MHz contains two EHT-SIG content channels.
  • the EHT-SIG field of an MU PPDU that is 160 MHz or wider contains two EHT-SIG content channels per 80 MHz.
  • the EHT-SIG content channels per 80 MHz are allowed to carry different information when EHT MU PPDU bandwidth for OFDMA transmission is wider than 80 MHz.
  • the EHT-SIG field of an EHT MU PPDU sent to a single user and the EHT-SIG field of an EHT sounding NDP contains one EHT-SIG content channel and it is duplicated in each non-punctured 20 MHz when the EHT PPDU is equal to or wider than 40 MHz
  • the Common field of an EHT-SIG content channel contains information regarding the resource unit allocation such as the RU assignment to be used in the EHT modulated fields of the PPDU, the RUs allocated for MU-MIMO and the number of users in MU-MIMO allocations.
  • the Common field of the EHT-SIG content channel does not contain the RU allocation.
  • the User Specific fields in the EHT-SIG content channels contains information for all users in the PPDU on how to decode their payload.
  • a device receiving an PPDU may initially begin or continue its determination of the wireless communication protocol version used to transmit the PPD based on the presence of RL-SIG and the modulation scheme used to modulate the symbols in U-SIG (or HE-SIG-A).
  • the receiving device may initially determine that the wireless communication protocol used to transmit the PPDU is an HE or later version based on the presence of RL-SIG (that is, a determination that the first symbol of the second portion of the preamble is identical to L-SIG) and a determination that both the first symbol and the second symbol following RL-SIG are modulated according to a BPSK modulation scheme.
  • FIG. 5 shows an example of UL MU transmission.
  • UL MU operation allows an AP to solicit simultaneous immediate response frames from one or more STAs.
  • the AP may send a trigger frame to one or more STAs (for example, STA1 and STA2).
  • the trigger frame may be sent as MU PPDU (for example, HE MU PPDU or EHT MU PPDU).
  • the STA1 and STA2 may send response PDUs (for example, HE TB PPDU or EHT TB PPDU) in response to the trigger frame.
  • the interframe space between a PPDU that contains a triggering frame and the TB PPDU is a Short Interframe Space (SIFS).
  • SIFS Short Interframe Space
  • the AP sends an Ack or BlockAck frame acknowledging the one or more TB PPDUs to the response STAs (for example, STA1 and STA2).
  • the trigger frame allocates resources for and solicits one or more PPDU transmissions.
  • the trigger frame also carries other information required by the responding STA to send a TB PPDU or a non-HT PPDU.
  • the trigger frame may be sent as various types such as a basic trigger frame, multi-user request to send (MU-RTS) frame, multi-user block ack request (MU-BAR) frame, Beamforming Report Poll (BFRP) Trigger frame, etc.
  • the trigger frame may include a UL bandwidth field, an CS required field, one or more STA IDs and one or more resource unit (RU) Allocation field.
  • the UL bandwidth field indicates the bandwidth of the response PPDU.
  • the CS required field indicate whether the response STAs are required to use energy detection (ED) to sense the medium and to consider the medium state and the network allocation vector (NAV) in determining whether or not to respond.
  • the one or more STA IDs identifies the one or more response STAs.
  • the RU Allocation subfield indicates RU allocation for the response PPDU.
  • a NAV is an indicator, maintained by each STA, of time periods when transmission onto the wireless medium (WM) is not initiated by the STA regardless of whether the STA's clear channel assessment (CCA) function senses that the WM is busy.
  • Transmission opportunity (TXOP) is an interval of time during which a particular STA has the right to initiate frame exchange sequences onto the WM.
  • a WLAN device classify a received PPDU as an inter-PPDU if (i) the received PPDU is transmitted by an AP which is not associated with the WLAN device, (ii) the received PPDU’s BSS is not the BSS of the WLAN device, or (iii) the received PPDU is a downlink MU PPDU and the WLAN device is an AP.
  • a WLAN device classify a received PPDU as an intra-PPDU if (i) the received PPDU is transmitted by an AP which is associated with the WLAN device, (ii) the received PPDU's BSS is the BSS of the WLAN device, or (iii) the received PPDU is a downlink MU PPDU and the WLAN device is an AP.
  • Timing synchronization function keeps TSF timers for all stations in the same BSS synchronized.
  • STAs can maintain a local TSF timer.
  • Each STA can maintain a TSF timer with modulus 2 64 counting in increments of microseconds.
  • the AP is the timing master for the TSF.
  • the AP can periodically transmit beacon frames which contain the value of the AP's TSF timer in order to synchronize the TSF timers of other STAs in a BSS.
  • a receiving STA can accept the timing information in the beacon frames and can update the receiving STA's TSF timer. If the receiving STA's TSF timer is different from the timestamp in the received beacon frame, the receiving STA can set its local TSF timer to the received timestamp value.
  • FIG. 6 shows an example of multi-link operation.
  • the IEEE 802.11be has defined multi-link operation (MLO) to support sending data frames concurrently on multiple links.
  • MLO allows the users to enjoy the multilink benefits unavailable for a simple noncontiguous wide spectrum on a single link, such as asynchronous channel access and enhanced power save.
  • the MLO can aggregate a various number of links of different widths. For example, Link1 has a bandwidth of 160 MHz and Link2 has a bandwidth of 40 MHz.
  • MLD has a single MAC address and uses this MAC address as its own identity. MLO enables frame transmission and retransmission on any link regardless of the link of the initial transmission of the frame.
  • a multi-link device may be a logical entity that is capable of supporting more than one affiliated STA and can operate using one or more affiliated STAs, and that presents one medium access control (MAC) data service and a single MAC-service access point (SAP) to the logical link control (LLC) sublayer.
  • An affiliated AP is an affiliated STA that is an AP STA and the corresponding MLD is an AP MLD.
  • An affiliated STA is a STA, which can be an AP STA or non-AP STA, that provides link-specific, lower MAC and physical layer (PHY) services within an MLD.
  • An enabled link is a setup link of a non-AP MLD to which at least one traffic identifier (TID) is mapped either in downlink or in uplink.
  • a disabled link is a setup link of a non-AP MLD to which no TID is mapped neither in downlink nor in uplink.
  • a TID is any of the identifiers usable by higher layer entities to distinguish MAC service data units (MSDUs) to MAC entities that support quality of service (QoS) within the MAC data service.
  • multilink multiradio MLD If an MLD implements multiple radios and uses these multiple radios concurrently for the MLO, these devices are defined as multilink multiradio (MLMR) MLD. If an MLD only implements single radio and still wants to operate multiple links, then these devices are called multilink single-radio (MLSR) MLD.
  • MLMR multilink multiradio
  • MLR multilink single-radio
  • An AP MLD may include multiple APs each capable of communicating on multiple communication links and may establish a BSS on the multiple communication links.
  • a STA MLD may include multiple STAs capable of communicating with other devices (such as an AP MLD) on multiple communication links. If congestion on a first communication link is above a certain level, the MLDs may switch from communicating on the first communication link to communicating on a second communication link. In some implementations, associating with one another on one communication link allows the MLDs to use the same association configuration, encryption keys, and other ML communication parameters when communicating on one or more of the other communication links associated with the MLDs.
  • a TXOP holder is an AP (or a STA) that has either been granted a TXOP or successfully contended for a TXOP.
  • a TXOP responder is a STA (or an AP) that transmits a frame in response to a frame received from a TXOP holder during a frame exchange sequence, but that does not acquire a TXOP in the process.
  • FIG. 7 shows an example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • An AP as a TXOP owner can send an initial control frame (ICF) to initiate a frame exchange.
  • the ICF can include a trigger frame.
  • the trigger frame may be sent as various types such as a basic trigger frame, multi-user request to send (MU-RTS) trigger frame, multi-user block ack request (MU-BAR) trigger frame, Beamforming Report Poll (BFRP) trigger frame, Buffer Status Report Poll (BSRP) trigger frame, etc.
  • a STA as a TXOP responder can send a initial control response frame (ICR) as response to the ICF.
  • the ICR can include at least one of CTS frame, Ack frame, BlockAck (BA) frame and Buffer Status Report (BSR) frame.
  • the BA frame may be sent as various types such as a Compressed BA frame, Multi-STA BA frame, etc.
  • the AP can indicate an initial TXOP duration by using ICF.
  • the STA can obtain the initial TXOP duration based on the received ICF.
  • the STA can indicate an adjusted TXOP duration by using ICR.
  • the AP can complete the frame exchange within the adjusted TXOP duration.
  • the ICF can include duration information to indicate a TXOP duration.
  • the duration information can be included in a Duration field (or may be called as Duration/ID field) in an MAC header of a frame.
  • single protection the Duration field of the frame can set a NAV value at receiving STAs that protects up to the end of any following frame plus any additional overhead frames.
  • multiple protection the Duration field of the frame can set a NAV that protects up to the estimated end of a sequence of multiple frames.
  • the Duration field can be set to the estimated time, in microseconds, required to transmit the pending frame(s), plus one Clear-to-Send (CTS) frame, plus the time to transmit the solicited HE TB PPDU if required, plus the time to transmit the acknowledgment for the solicited HE TB PPDU if required, plus applicable IFSs.
  • CTS Clear-to-Send
  • the Duration field can be set to the time required to transmit the solicited HE TB PPDU plus one SIFS.
  • the Duration field can be set to the estimated time required to transmit the solicited HE TB PPDU, plus the estimated time required to transmit the acknowledgment for the solicited HE TB PPDU if required, plus applicable SIFSs.
  • the TXVECTOR parameter TXOP_DURATION of a PPDU indicates TXOP duration for NAV setting and protection of the TXOP, except that the TXVECTOR parameter TXOP_DURATION is set to 'UNSPECIFIED' (e.g., 127) to indicate no NAV value specified.
  • a STA that transmits a frame with a Duration field in a PPDU with the TXVECTOR parameter TXOP_DURATION not set to UNSPECIFIED can set the TXVECTOR parameter TXOP_DURATION to the smaller of the duration information indicated by the Duration field.
  • the TXVECTOR parameter TXOP_DURATION can be converted to a value in a TXOP field in a SIG field of a PPDU.
  • the TXOP responder can calculate duration information equal to the duration information indicated by the Duration field of the frame that solicits the response minus the time, in microseconds, between the end of the PPDU carrying the frame that is soliciting the TB PPDU and the end of the TB PPDU. If the calculated duration information is smaller than 8448 ⁇ s, the TXVECTOR parameter TXOP_DURATION can be set to the calculated duration information. Otherwise, the TXVECTOR parameter TXOP_DURATION can be set to 8448.
  • a STA transmits either an TB feedback Null Data PPDU (NDP) or an TB PPDU carrying a power save (PS)-Poll frame with the TXVECTOR parameter TXOP_DURATION not set to UNSPECIFIED, the STA can calculate the duration information and set the TXVECTOR parameter TXOP_DURATION for the TB feedback NDP or TB PPDU to the value of the computed duration information.
  • NDP Null Data PPDU
  • PS power save
  • a TXOP responder When a TXOP responder transmits a response frame (e,g., ICR) that includes a Duration field in the MAC header, the TXOP responder can set the Duration field to a second duration value that is less than a first duration value.
  • a response frame e,g., ICR
  • the first duration value can be a value obtained from the Duration field of the RTS frame that elicited the response minus the time, in microseconds, between the end of the PPDU carrying the RTS frame and the end of the PPDU carrying the CTS frame.
  • the first duration value is a value obtained from the Duration field of the MU-RTS Trigger frame that elicited the CTS frame minus the time, in microseconds, between the end of the PPDU carrying the MU-RTS Trigger frame and the end of the PPDU carrying the CTS frame.
  • the first duration value is a value obtained from the Duration field of the frame that elicited the response minus the time, in microseconds between the end of the PPDU carrying the frame that elicited the response and the end of the PPDU carrying the Ack frame.
  • the first duration value is a value obtained from the Duration field of the frame that elicited the response minus the time, in microseconds between the end of the PPDU carrying the frame that elicited the response and the end of the PPDU carrying the BlockAck frame.
  • the first duration value is a value obtained from the Duration field of the frame that elicited the response minus the time, in microseconds, between the end of the PPDU carrying the frame that elicited the response and the end of the PPDU carrying the frame.
  • the TXOP field in the SIG field of the preamble is not set to UNSPECIFIED (i.e., 127)
  • the TXOP field can be set to a third duration value.
  • the third duration value can be derived from the first duration value which has a value obtained from the TXVECTOR parameter TXOP_DURATION of the TB PPDU carrying the response frame.
  • An ICR can be carried in a TB PPDU.
  • FIG. 8 shows another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • An AP sends a BSRP trigger frame as an ICF.
  • STA1 sends a BSR as an ICR and STA2 sends a BSR.
  • STA1 can obtain the AP's TXOP duration based on the BSRP trigger frame and can send STA1's TXOP duration in the BSR.
  • STA2 can obtain the AP's TXOP duration based on the BSRP trigger frame and can send STA2's TXOP duration in the BSR.
  • STA2's TXOP duration ends at the end of the AP's TXOP duration but STA1's TXOP duration is shorter than AP's TXOP duration.
  • the TXOP holder receives the response frame whose the Duration field value is less than the first duration value.
  • the TXOP holder can receive the response frame whose the Duration field value is less than the first duration field value in the frame elicited the response frame. Then, the TXOP holder can transmits a subsequent frame (e.g., group addressed frame, frame with No Ack policy) that does not solicit any response frame. The TXOP holder can ensure that the PPDU carrying the subsequent frame does not exceed the TXOP duration indicated by the Duration field in the response frame.
  • a subsequent frame e.g., group addressed frame, frame with No Ack policy
  • FIG. 9 shows still another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • An AP as a TXOP holder can receives a BSR as a response frame.
  • STA1's TXOP duration is shorter than AP's TXOP duration.
  • the TXOP holder receives the response frame whose the Duration field value is less than the first duration value.
  • the TXOP holder can transmit a subsequent frame (e.g., a frame with Normal Ack/Implicit BAR/HETB Ack policy) that solicits a control response frame (e.g., Ack frame, BA frame).
  • a subsequent frame e.g., a frame with Normal Ack/Implicit BAR/HETB Ack policy
  • a control response frame e.g., Ack frame, BA frame.
  • the TXOP holder can ensure that the PPDU carrying the solicited control response frame does not exceed the TXOP duration indicated by the Duration field in the response frame.
  • FIG. 10 shows still another example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • An AP as a TXOP holder receives an BSR as a first response frame from STA1.
  • the TXOP duration indicated by the Duration field in the first response frame is shorter than the TXOP duration value is indicated by the Duration field in a first control frame.
  • the TXOP holder receives the first response frame whose the Duration field value is less than the first duration value of the first control frame.
  • the TXOP holder can transmits a second control frame (e.g., Trigger frame) that solicits a second response frame. If the second response frame does not solicit a control response (e.g., BlockAck) from the TXOP holder, the TXOP holder can ensure that the TB PPDU carrying the second response frame does not exceed the TXOP duration indicated by the Duration field in the first response frame.
  • a control response e.g., BlockAck
  • the TXOP can ensure that the TB PPDU carrying the solicited second response frame and the PPDU carrying the following control response frame do not exceed the TXOP duration indicated by the Duration field in the first response frame.
  • a TXOP holder When a TXOP holder receives from a peer STA (or a TXOP responder) a response frame whose the Duration field value is less than the first duration value, the TXOP holder cannot initiate a frame exchange with the peer STA unless the TXOP holder receives another frame sent by the peer STA. If the TXOP holder wants to initiate a frame exchange with the peer STA, the TXOP holder can start with a control frame (e.g., RTS/CTS).
  • a control frame e.g., RTS/CTS
  • FIG. 11 shows an example illustrating TXOP operation in accordance with an embodiment of the present disclosure.
  • An AP as a TXOP owner can send a control frame to a STA.
  • the control frame may be an ICF to initiate a frame exchange.
  • the STA as a TXOP responder sends a response frame (e.g., ICR) to the AP.
  • the response frame can include information on the adjusted TXOP duration.
  • the response frame can include pause information which indicates a pause duration during which the TXOP holder ceases to transmit frames to the TXOP responder.
  • the AP does not send any DL frame to the STA within the pause duration. After pause duration, the AP can send a DL frame to the STA.
  • a Pause A-Control field as the pause information can define the pause duration.
  • the pause duration is configured, if the STA receives another pause information from the peer STA, the previous pause duration can be disregarded. For example, the peer STA indicated that the channel is unavailable during a first duration, but the peer STA sends another pause information that indicates that the channel is available during a second duration, then the previous unavailability can be ignored.
  • the pause duration information can be encoded based on the TSF.
  • FIG. 12 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • An AP sends an MU-RTS Trigger frame to STA1. After transmitting the MU-RTS Trigger frame, the AP can wait for a CTSTimeout interval.
  • the CTSTimeout interval begins when a MAC entity in the AP receives the PHY-TXEND.confirm primitive for the transmitted MU-RTS Trigger frame.
  • the PHY-TXEND.confirm primitive can be issued by the PHY layer to the MAC entity to confirm the completion of a transmission.
  • the CTSTimeout interval can have a value of aSIFSTime+aSlotTime+aRxPHYStartDelay.
  • 'aSIFSTime' is a time that the MAC and PHY require from reception of the end of a PPDU on the WM until the MAC and PHY have processed any frame(s) therein, and responded with the start on the WM of the PPDU containing the earliest possible response frame.
  • 'aSlotTime' has a value of a predefined time.
  • 'aRxPHYStartDelay' is the delay from the start of the PPDU at the receiver's antenna to the issuance of the PHY-RXSTART.indication primitive.
  • the PHY-RXSTART.indication primitive is an indication by the PHY to the MAC entity that the PHY has received a valid start of a PPDU, including a valid PHY header (or valid PHY preamble).
  • the AP can conclude that the transmission of the MU-RTS Trigger frame has failed. If the MU-RTS Trigger frame initiated a TXOP, the AP can invoke a backoff procedure.
  • the MAC entity of the AP can wait for the corresponding PHY-RXEND.indication primitive to determine whether the MU-RTS Trigger frame transmission was successful.
  • the PHY-RXEND.indication primitive is an indication by the PHY to the MAC entity that the PPDU currently being received is complete.
  • the receipt of a frame which is not a CTS frame can be interpreted as a failure of the MU-RTS Trigger frame transmission.
  • the AP may process the received frame and, if the MU-RTS Trigger frame initiated a TXOP, the AP can invoke a backoff procedure at the PHY-RXEND.indication primitive.
  • a STA2 which overhears the MU-RTS Trigger frame can set NAV.
  • the STA2 can use information in the MU-RTS Trigger frame as the most recent basis to update its NAV setting.
  • the STA2 can be permitted to reset its NAV if no PHY-RXSTART.indication primitive is received from the PHY during a NAVTimeout period.
  • the NAVTimeout period can start when the MAC receives a PHY-RXEND.indication primitive corresponding to the detection of the frame (i.e., MU-RTS Trigger frame).
  • the NAVTimeout period can be equal to (2 ⁇ aSIFSTime)+(CTS_Time)+aRxPHYStartDelay+(2 ⁇ aSlotTime). If an RTS frame is used for the most recent NAV update, the CTS_Time can be calculated using the length of the CTS frame and/or the data rate at which the RTS frame used for the most recent NAV update was received. If an MU-RTS Trigger frame was used for the most recent NAV update, CTS_Time can be calculated using the length of the CTS frame and/or the 6 Mb/s data rate. The CTS_Time can be calculated using the time required to transmit a Null Data PPDU (NDP) CTS frame that is equal to NDPTxTime. NDPTxTime can be the time required to transmit a predefined PPDU format.
  • NDP Null Data PPDU
  • FIG. 13 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • STA2 After receiving an ICF from STA1 (which is AP or non-AP STA), STA2 (which is non-AP STA or AP) sends an ICR.
  • the ICR can include variable length information.
  • the variable length information can include an availability duration or an unavailability duration.
  • the ICF can be a variant of a BSRP Trigger frame and/or MU-RTS Tigger frame.
  • the ICR can be a variant of the Multi-STA BA frame and/or CTS frame.
  • the ICF and/or the ICR can have TXOP duration information as shown in the embodiments shown in FIGs. 7-11.
  • the availability duration is a duration during which a STA can be available to receive and/or transmit a frame.
  • the unavailability duration is a duration during which a STA can be unavailable to receive and/or transmit a frame.
  • the unavailability duration may include the pause information.
  • the STA1 can wait for an Timeout interval.
  • the Timeout interval can be called as ICRTimeout interval and can begin when the MAC of STA1 receives the PHY TXEND.confirm primitive for the transmitted ICF.
  • the ICRTimeout interval can have a value of aSIFSTime+aSlotTime+aRxPHYStartDelay.
  • the STA1 can conclude that the transmission of the ICF has failed. If the ICF initiated a TXOP, the STA1 can invoke a backoff procedure. After the backoff procedure, STA1 sends a retransmission ICF.
  • the duration information indicating a second TXOP by the retransmission ICF i.e., second ICF
  • the duration information indicating a first TXOP of the failed ICF i.e., first ICF).
  • the MAC of STA1 can wait for the corresponding PHY-RXEND.indication primitive to determine whether the ICF transmission was successful.
  • the receipt of any other type of frame can be interpreted as a failure of the ICF transmission.
  • the STA1 may process the received frame and, if the 2nd ICF initiated a TXOP, can invoke a backoff procedure at the PHY-RXEND.indication primitive.
  • the duration information indicating a TXOP by the new ICF cannot be greater than the duration information indicating a TXOP of the failed second ICF.
  • STA3 can uses information from the ICF as the most recent basis to update its NAV setting.
  • the STA3 can be permitted to reset its NAV unless PHY-RXSTART.indication primitive is received from the PHY during a NAVTimeout period.
  • the NAVTimeout period can start when the MAC receives a PHY-RXEND.indication primitive corresponding to the detection of the ICF.
  • the NAVTimeout period can be equal to (2 ⁇ aSIFSTime)+(ICR_Time)+aRxPHYStartDelay+(2 ⁇ aSlotTime).
  • the ICR_Time can be calculated using the length of the maximum ICR size and/or the data rate at which the ICF used for the most recent NAV update was received. Or, the ICF can indicates the length of ICR, and the ICR_Time can be calculated using the ICR length information indicated in the received ICF.
  • STA3 cannot reset its NAV even though the first ICF was failed because the NAVTimeout is quite long.
  • the STA3 can misclassify the following frame transmissions as valid.
  • FIG. 14 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • STA3 can uses information from the ICF as the most recent basis to update its NAV setting.
  • the STA3 can be permitted to reset its NAV unless PHY-RXSTART.indication primitive is received from the PHY before the NAVTimeout period and after the NAVTimeout minus a ResponseTolerance.
  • the NAVTimeout period can start when the MAC receives a PHY-RXEND.indication primitive corresponding to the detection of the ICF.
  • STA3 can overhear the second ICF before the NAVTimeout period and after the NAVTimeout minus a ResponseTolerance, STA3 can reset its NAV based on duration informaton in the second ICF.
  • the STA3 can be permitted to reset its NAV if no PHY-RXSTART.indication primitive is received from the PHY during a last part of a NAVTimeout period.
  • the last part of the NAVTimeout period have a length of the ResponseTolerance.
  • the ResponseTolerance may have a predefined value.
  • the ResponseTolerance may have a value greater than or equal to aRxPHYStartDelay.
  • the ResponseTolerance may be equal to aRxPHYStartDelay+(2 ⁇ aSlotTime).
  • FIG. 15 shows an example illustrating NAV reset in accordance with an embodiment of the present disclosure.
  • the STA2 sends an ICR with the availability duration (and/or unavailability duration).
  • the STA1 which is the TXOP holder may need to terminate the TXOP earlier than the TXOP duration indicated in the ICF.
  • the duration information for the TXOP in the following transmission can be set to a smaller value than the NAV value that was updated from the immediately preceding ICF.
  • STA3 can reset NAV since the following transmission's duration information is less than STA3's NAV value that was updated from the immediately preceding ICF.
  • the NAV can be reset.
  • the STA3 can update the NAV from on the duration information of the TXOP that is obtained from the following transmission.
  • the STA3 can use information from the ICF as the most recent basis to update its NAV setting.
  • the STA3 can be permitted to reset its NAV if no PHY-RXSTART.indication primitive is received from the PHY before a NAVTimeout period starting when the MAC receives a PHY-RXEND.indication primitive corresponding to the detection of the ICF.
  • the STA3 can be permitted to reset its NAV if the PHY-RXSTART.indication primitive is received from the PHY but the duration information of the TXOP (e.g., TXOP field value in PHY header or Duration field value in the MAC header) is not matched with current STA3's NAV value. If the TXOP field value in the PHY header is less than the STA3's NAV value, the NAV can be reset and can be updated based on the TXOP field value.
  • a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those item, including single members.
  • “at least one of: a, b, and c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

Landscapes

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

Abstract

Une station fonctionnant en tant que répondeur d'opportunité de transmission (TXOP) reçoit une trame de commande pour initier un échange de trames à partir d'un propriétaire de TXOP, et transmet une trame de réponse en tant que réponse à la trame de commande. La trame de réponse comprend des informations de pause qui indiquent la durée de la pause pendant laquelle le propriétaire du TXOP cesse de transmettre une trame au répondeur du TXOP.
PCT/KR2024/012078 2023-09-21 2024-08-13 Commutation de sous-canal pour réseau local sans fil Pending WO2025063505A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20230126324 2023-09-21
KR10-2023-0126324 2023-09-21

Publications (1)

Publication Number Publication Date
WO2025063505A1 true WO2025063505A1 (fr) 2025-03-27

Family

ID=95071568

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/012078 Pending WO2025063505A1 (fr) 2023-09-21 2024-08-13 Commutation de sous-canal pour réseau local sans fil

Country Status (1)

Country Link
WO (1) WO2025063505A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10863502B1 (en) * 2014-12-05 2020-12-08 Nxp Usa, Inc. Methods and apparatus for carrying out backoff operations
WO2022032150A1 (fr) * 2020-08-06 2022-02-10 Interdigital Patent Holdings, Inc. Direction et commande à liaisons multiples dans un réseau local sans fil
KR20220141866A (ko) * 2020-04-01 2022-10-20 소니그룹주식회사 시간 도메인에서 공유 txop를 갖는 코디네이션된 wifi 스테이션들
US20230179686A1 (en) * 2020-05-04 2023-06-08 Wilus Institute Of Standards And Technology Inc. Wireless communication method using multiple links, and wireless communication terminal using same

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10863502B1 (en) * 2014-12-05 2020-12-08 Nxp Usa, Inc. Methods and apparatus for carrying out backoff operations
KR20220141866A (ko) * 2020-04-01 2022-10-20 소니그룹주식회사 시간 도메인에서 공유 txop를 갖는 코디네이션된 wifi 스테이션들
US20230179686A1 (en) * 2020-05-04 2023-06-08 Wilus Institute Of Standards And Technology Inc. Wireless communication method using multiple links, and wireless communication terminal using same
WO2022032150A1 (fr) * 2020-08-06 2022-02-10 Interdigital Patent Holdings, Inc. Direction et commande à liaisons multiples dans un réseau local sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LAURENT CARIOU (INTEL): "Improved reliability in presence of interference", IEEE DRAFT; 11-23-0298-00-0UHR-IMPROVED-RELIABILITY-IN-PRESENCE-OF-INTERFERENCE, vol. 802.11 UHR, no. 0, 10 April 2023 (2023-04-10), US, pages 1 - 13, XP068202141 *

Similar Documents

Publication Publication Date Title
US12069723B2 (en) Scheduling wireless stations within a target wake time service period
US12075355B2 (en) Low-latency enhancements for a wireless network
US12284717B2 (en) Context updates for multi-link devices
US12262411B2 (en) Coordinated scheduling and signaling of restricted target wake time (r-TWT) service periods
WO2024025340A1 (fr) Dispositif et procédé d'accès à un canal
WO2017057990A1 (fr) Procédé permettant le fonctionnement de bss multiples dans un système de réseau local sans fil et dispositif s'y rapportant
WO2022216086A1 (fr) Procédé et dispositif de fonctionnement de mlsr dans un lan sans fil
WO2021162945A1 (fr) Mécanismes d'économie d'énergie pour point d'accès activé par logiciel (softap)
WO2024071665A1 (fr) Dispositif et procédé de transmission de trame de balise
WO2025063505A1 (fr) Commutation de sous-canal pour réseau local sans fil
WO2024034925A1 (fr) Procédé et appareil pour l'émission ou la réception d'informations de canal concernant une bande de fonctionnement dans un système lan sans fil
WO2025053601A1 (fr) Dispositif et procédé de partage d'opportunité de transmission
WO2025018818A1 (fr) Commutation de sous-canal pour réseau local sans fil
WO2025033912A1 (fr) Opération pour dispositif multilien
WO2024090854A1 (fr) Dispositif et procédé de protection de trame de commande dans un réseau local sans fil
WO2024090853A1 (fr) Dispositif et procédé de protection de trame dans un réseau local sans fil
WO2024080558A1 (fr) Dispositif et procédé de commutation de canal
WO2024196186A1 (fr) Dispositif et procédé d'accès à un canal
WO2024025339A1 (fr) Dispositif et procédé de transmission de ppdu
WO2019017590A1 (fr) Procédé de transmission ou de réception de trame dans un système lan sans fil, et dispositif correspondant
WO2025249833A1 (fr) Procédé et dispositif de négociation de durée de partage de txop sur la base d'un partage de txop entre des points d'accès dans un réseau lan sans fil
WO2016186476A1 (fr) Procédé de planification basé sur des informations de canal en repos dans un système de réseau local sans fil et dispositif correspondant
WO2025225945A1 (fr) Procédé et dispositif pour effectuer une transmission et une réception de signal sur la base d'un partage txop entre des points d'accès dans un réseau lan sans fil
WO2024101790A1 (fr) Procédé et dispositif de mise en œuvre de transmission et de réception de ppdu sur la base d'une sélection de numérologie dans un système lan sans fil
WO2024034921A1 (fr) Procédé et dispositif de transmission et de réception d'une ppdu basée sur un intervalle de garde dans un système lan sans fil

Legal Events

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

Ref document number: 24868484

Country of ref document: EP

Kind code of ref document: A1