Method and device for performing target wake time-based communication in wireless LAN system

The method for managing TWT service periods in wireless LAN systems by using BSS color information to protect OBSS R-TWT SPs addresses the challenge of interference in multi-BSS environments, enhancing communication efficiency and reliability by allowing STAs to adjust their operations based on neighboring APs' BSS colors.

WO2024232716A1PCT designated stage expired Publication Date: 2024-11-14LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/006340
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-06-09
Filing Date
2024-05-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current wireless LAN systems face challenges in managing target wake time (TWT) service periods, particularly in multi-BSS environments, where overlapping basic service sets (OBSS) can cause interference and require protection of restricted TWT service periods (SPs) based on BSS color information to ensure efficient communication and reduce latency.

Method used

A method and device for performing TWT-based communication, where a station (STA) transmits and receives BSS color information to/from an access point (AP) to determine whether to protect an overlapping BSS's R-TWT SP, allowing the STA to adjust its operations accordingly, such as terminating transmission opportunities or setting overlapping silence intervals, based on the inclusion of the neighboring AP's BSS color in the STA's BSS color list.

Benefits of technology

This approach enables effective protection of OBSS R-TWT SPs, reducing interference and improving communication efficiency by ensuring that STAs in overlapping BSS areas adjust their operations to avoid conflicts, thereby enhancing the overall performance and reliability of TWT-based communication in wireless LAN systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006340_14112024_PF_FP_ABST
    Figure KR2024006340_14112024_PF_FP_ABST
Patent Text Reader

Abstract

A method and a device for operations in a wireless LAN system are disclosed. A method performed by an STA in a wireless LAN system, according to an embodiment of the present disclosure, may comprise the steps of: transmitting, to a first access point (AP), information related to at least one basic service set (BSS) color; receiving, from the first AP, information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by a second AP; and on the basis that a BSS color of the second AP is included in the at least one BSS color, performing an operation for protection of the second R-TWT SP.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing target wake time-based communication in a wireless LAN system

[0001] The present disclosure relates to a communication operation in a wireless local area network (WLAN) system, and more particularly, to a method and device for performing target wake time (TWT)-based communication in a next-generation wireless LAN system.

[0002] New technologies have been introduced for wireless local area networks (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and reduce latency. Among WLAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, recently introduced technologies for WLANs include enhancements for Very High Throughput (VHT) in the 802.11ac standard and enhancements for High Efficiency (HE) in the IEEE 802.11ax standard.

[0003] To provide a more advanced wireless communication environment, improved technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for Multiple Input Multiple Output (MIMO), which supports increased bandwidth, efficient utilization of multiple bands, and increased spatial streams, and for coordination of multiple access points (APs), are being studied. In particular, various technologies are being studied to support low latency or real-time traffic. Furthermore, new technologies are being discussed to support ultra-high reliability (UHR), including improvements or extensions of EHT technology.

[0004] The technical problem of the present disclosure is to provide a method and device for performing TWT-based communication in a wireless LAN system.

[0005] The technical problem of the present disclosure is to provide a method and device for performing an operation for an R(restricted)-TWT service period (SP) scheduled by a neighboring AP in a multi-BSS (basic service set) environment.

[0006] The technical problem of the present disclosure is to provide a method and device for determining whether to protect an OBSS (overlapping basic service set) R-TWT SP based on BSS color information reported to an AP.

[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0008] According to one embodiment of the present disclosure, a method performed by a station (STA) in a wireless LAN system may include the steps of: transmitting information related to at least one basic service set (BSS) color to a first access point (AP); and receiving information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by a second AP from the first AP; and performing a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in the at least one BSS color.

[0009] In another embodiment of the present disclosure, a method performed by a first access point (AP) in a wireless LAN system includes the steps of: receiving information related to at least one basic service set (BSS) color from a station (STA); and transmitting information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by a second AP to the STA, wherein a protection operation of the second R-TWT SP can be performed based on the BSS color of the second AP being included in the at least one BSS color.

[0010] According to various embodiments of the present disclosure, a method and device for performing TWT-based communication in a wireless LAN system can be provided.

[0011] According to various embodiments of the present disclosure, a method and apparatus for performing an operation for an R-TWT SP scheduled by a neighboring AP in a multi-BSS environment can be provided.

[0012] According to various embodiments of the present disclosure, a method and apparatus for determining whether to protect an OBSS R-TWT SP based on BSS color information reported to an AP may be provided.

[0013] According to various embodiments of the present disclosure, a method and apparatus for protecting an OBSS R-TWT SP announced by an AP may be provided.

[0014] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0015] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0016] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

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

[0018] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

[0019] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

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

[0021] 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.

[0022] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0023] FIG. 8 is a drawing illustrating an example of an individual TWT operation to which the present disclosure can be applied.

[0024] FIG. 9 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.

[0025] Figure 10 is a drawing for explaining an example of a TWT information element format.

[0026] Figure 11 is a diagram illustrating examples of individual TWT parameter set field formats.

[0027] Figure 12 is a diagram illustrating examples of broadcast TWT parameter set field formats.

[0028] Figure 13 is a diagram illustrating examples of field formats related to limited TWT operations.

[0029] FIG. 14 is a diagram for explaining a method for an STA to perform an overhearing operation in a multi-BSS environment according to one embodiment of the present disclosure.

[0030] FIG. 15 is a flowchart for explaining the operation of an STA according to one embodiment of the present disclosure.

[0031] FIG. 16 is a diagram for explaining the operation of the first AP according to one embodiment of the present disclosure.

[0032] FIG. 17 is a diagram for explaining an operation of an STA protecting an OBSS R-TWT SP according to one embodiment of the present disclosure.

[0033] FIG. 18 is a diagram for explaining the configuration of a field including information related to OBSS R-TWT according to one embodiment of the present disclosure.

[0034] FIG. 19 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.

[0035] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

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

[0037] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0038] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0039] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0040] The examples of the present disclosure can be applied to various wireless communication systems. For example, the examples of the present disclosure can be applied to a wireless LAN system. For example, the examples of the present disclosure can be applied to a wireless LAN based on the IEEE 802.11a / g / n / ac / ax / be standards. Furthermore, the examples of the present disclosure can be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard. Additionally, the examples of the present disclosure can be applied to a wireless LAN based on the next-generation standard after IEEE 802.11bn. Furthermore, the examples of the present disclosure can be applied to a cellular wireless communication system. For example, the examples of the present disclosure can be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series of technologies and the 5G NR (New Radio) series of technologies of the 3rd Generation Partnership Project (3GPP) standard.

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

[0042] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

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

[0044] The devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs). For example, the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, in the present disclosure, the STAs (110, 200) may perform the functions of an AP and / or a non-AP. 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. In addition, in the present disclosure, the APs may also be referred to as AP STAs.

[0045] Referring to FIG. 1, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless LAN technologies (e.g., IEEE 802.11 series). The first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.11 standard.

[0046] In addition, the first device (100) and the second device (200) may additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than wireless LAN technology. In addition, the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

[0047] A first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memories (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). Furthermore, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, 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. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0048] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, 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. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0049] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0050] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0051] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0052] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, 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, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can 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 user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0053] For example, 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. For example, 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.). In addition, in the present disclosure, operations in which various STAs generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals may be performed in the processors (102, 202) of FIG. 1. For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include 1) an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of a field (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU, 2) an operation for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (104, 204) of FIG. 1.

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

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

[0056] The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports transparent STA mobility to the upper layer can be provided. A Basic Service Set (BSS) corresponds to a basic building block of a wireless LAN. FIG. 2 illustrates, by way of example, the existence of two BSSs (BSS1 and BSS2) and the inclusion of two STAs as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). The oval representing a BSS in FIG. 2 can also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). When an STA moves outside of a BSA, it cannot directly communicate with other STAs within the BSA.

[0057] If we do not consider the DS illustrated in Figure 2, the most basic type of BSS in a wireless LAN is an Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For example, assuming other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4, can be representative examples of an IBSS, respectively. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, in this type of WLAN, a LAN can be configured when needed rather than being planned in advance, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems (DS) is not permitted, forming a self-contained network.

[0058] An STA's membership in a BSS can dynamically change, for example, when an STA is turned on or off, or when an STA enters or leaves a BSS area. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services in the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may involve the use of a Distribution System Service (DSS).

[0059] In a wireless LAN, the direct STA-to-STA distance can be limited by PHY performance. While this distance limit may be sufficient in some cases, communication between STAs over longer distances may be required in other cases. To support extended coverage, a distributed system (DS) can be configured.

[0060] DS refers to a structure in which BSSs are interconnected. Specifically, a BSS may exist as an extended component of a network composed of multiple BSSs, as illustrated in Figure 2. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, the Wireless Medium (WM) and DSM can be logically distinguished. Each logical medium is used for a different purpose and by different components. These media are neither limited to being identical nor limited to being different. This logical difference between multiple media explains the flexibility of the WLAN architecture (DS architecture or other network architectures). In other words, the WLAN architecture can be implemented in various ways, and the physical characteristics of each implementation can independently specify the WLAN architecture.

[0061] A DS can support mobile devices by providing seamless integration of multiple BSSs and the logical services necessary to handle addresses to destinations. Additionally, a DS may further include a component called a portal, which acts as a bridge for connecting wireless LANs to other networks (e.g., IEEE 802.X).

[0062] 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. For example, STA2 and STA3 illustrated in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS. In addition, since all APs are basically STAs, all APs are addressable entities. The address used by an AP for communication on a WM and the address used by an AP for communication on a DSM do not necessarily have to be the same. A BSS consisting of an AP and one or more STAs can be referred to as an infrastructure BSS.

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

[0064] In addition to the structure of the DS described above, an extended service set (ESS) may be established to provide wider coverage.

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

[0066] In a wireless LAN system, no assumptions are made about the relative physical locations of BSSs, and all of the following configurations are possible: BSSs can be partially overlapping, which is commonly used to provide continuous coverage. BSSs can also be physically disconnected, and there is no logical distance limit between them. BSSs can also be physically co-located, which can be used to provide redundancy. Furthermore, one (or more) IBSS or ESS networks can physically co-exist with one (or more) ESS networks. This can occur in cases where an ad-hoc network operates at the same location as an ESS network, where physically overlapping wireless networks are configured by different organizations, or where two or more different access and security policies are required at the same location.

[0067] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.

[0068] For an STA to set up a link and transmit and receive data on a network, it must first discover the network, perform authentication, establish an association, and complete security authentication procedures. The link setup process can also be referred to as the session initiation process or session setup process. Furthermore, the discovery, authentication, association, and security setup processes of the link setup process can be collectively referred to as the association process.

[0069] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning operations by the STA. That is, for the STA to access a network, it must search for available networks. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning.

[0070] Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation including an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover any APs in the vicinity while moving between channels and waits for a response. The responder transmits a probe response frame in response to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, the AP transmits the beacon frame, so the AP becomes the responder. In the IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not fixed. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0071] Although not shown in Figure 3, the scanning operation can also be performed in a passive scanning manner. In passive scanning, the STA performing the scanning moves between channels and waits for a beacon frame. A beacon frame is one of the management frames defined in IEEE 802.11. It announces the existence of a wireless network and is periodically transmitted so that the STA performing the scanning can find the wireless network and participate in the wireless network. In the BSS, the AP performs the role of periodically transmitting the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the STA performing the scanning receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. The STA receiving the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel to perform scanning on the next channel in the same manner. Comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

[0072] After the STA discovers the network, an authentication process may be performed in step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below.

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

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

[0075] An STA can send an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

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

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

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

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

[0080] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0081] In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). The CSMA / CA mechanism, also known as the Distributed Coordination Function (DCF) of the IEEE 802.11 MAC, essentially employs a "listen before talk" access mechanism. According to this type of access mechanism, 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. On the other hand, if the medium is detected to be occupied or busy, the AP and / or STA may not start its own transmission, but may wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit frames. By applying a random backoff period, multiple STAs are expected to attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.

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

[0083] Referring to Fig. 4, an operation based on a random backoff period is described. When a medium that was occupied / busy changes to an idle state, multiple STAs can attempt to transmit data (or frames). To minimize collisions, each STA can select a random backoff count, wait for the corresponding slot time, and then attempt transmission. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​in the range of 0 to CW. Here, CW is a contention window parameter value. The CW parameter is given an initial value of CWmin, but can take a value doubled in case of transmission failure (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, data transmission can be attempted while maintaining the CWmax value until data transmission is successful, and if data transmission is successful, it is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are 2. n It is desirable to set it to -1 (n=0, 1, 2, ...).

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

[0085] In the example of FIG. 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit a frame if it confirms that the medium is idle for DIFS. The remaining STAs monitor the medium for occupied / busy states and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can count down the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS if the medium is monitored as idle. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. In other words, this example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission. STA1 and STA5 briefly stop counting down and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, they can start transmitting frames after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time is shorter than STA1's, STA5 starts transmitting frames. While STA2 occupies the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS, counts down according to its selected random backoff count value, and then starts transmitting frames. In the example of Figure 4, the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failure in data transmission.In this case, STA4 and STA5 can select a random backoff count value and perform a countdown after doubling the CW value. STA1 waits while the medium is occupied by transmissions from STA4 and STA5, and when the medium becomes idle, it waits for DIFS and can start transmitting frames after the remaining backoff time elapses.

[0086] As in the example of Fig. 4, 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. Additionally, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS elapses, such as DIFS or PIFS (Point coordination function IFS). Subtype frames of a management frame include a beacon, an association request / response, a re-association request / response, a probe request / response, and an authentication request / response. A control frame is a frame used to control access to the medium. The subtype frames of the control frame include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), Null Data Packet Announcement (NDP), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after a backoff performed after the DIFS (Direct Inverse Frame Stop) has elapsed, and if it is a response frame to the previous frame, it is transmitted without a backoff performed after the SIFS (short IFS). The type and subtype of the frame can be identified by the type field and subtype field in the Frame Control (FC) field.

[0087] A QoS (Quality of Service) STA can transmit a frame after a backoff performed after the AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed. Here, the frames for which AIFS[i] can be used can be data frames, management frames, and also control frames that are not response frames.

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

[0089] As mentioned above, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, in which STAs directly sense the medium. Virtual carrier sensing is intended to address potential issues in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of an STA can utilize a Network Allocation Vector (NAV). The NAV is a value that an STA that is currently using or has the right to use the medium indicates to other STAs the remaining time until the medium becomes available. Therefore, the value set as NAV corresponds to the period during which the STA transmitting the frame is scheduled to use the medium, and an STA receiving the NAV value is prohibited from accessing the medium during that period. For example, the NAV can be set based on the value of the "duration" field in the MAC header of the frame.

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

[0091] In order to reduce the possibility of collisions in transmissions of multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA1 may correspond to a hidden node for STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA2 may correspond to a hidden node for STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0092] Specifically, STA1 can determine whether a channel is occupied through carrier sensing. In terms of physical carrier sensing, STA1 can determine channel occupancy idleness based on the energy level or signal correlation detected in the channel. Furthermore, in terms of virtual carrier sensing, STA1 can determine the channel occupancy status using a network allocation vector (NAV) timer.

[0093] STA1 can transmit an RTS frame to STA2 after performing a backoff if the channel is idle during the DIFS. STA2 can transmit a CTS frame, which is a response to the RTS frame, to STA1 after an SIFS if it receives the RTS frame.

[0094] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can use the duration information contained in the RTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can use the duration information contained in the CTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame). That is, if STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0095] If STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the CTS frame is completely received. If STA2 successfully receives the data frame, it can transmit an ACK frame in response to the data frame to STA1 after SIFS. STA3 can determine whether the channel is in use through carrier sensing if the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during the DIFS after the NAV timer expires, it can attempt channel access after a contention window (CW) based on a random backoff has elapsed.

[0096] 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.

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

[0098] In this way, information transmission / reception in a wireless LAN system is done in the form of frames, and for this purpose, the PHY layer Protocol Data Unit (PPDU) format is defined.

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

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

[0101] The SIG field may include various information related to PPDU transmission and reception. For example, the L-SIG field may consist of 24 bits and may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field. The RATE field may include information about the modulation and coding rate of data. For example, the 12-bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of 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. For example, for HE PPDU, the value of the Length field can be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

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

[0103] MAC PDUs are defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS). A MAC frame is composed of MAC PDUs and can be transmitted / received through the PSDU in the data portion of the PPDU format.

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

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

[0106] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.

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

[0108] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format illustrated in Fig. 7(b) may be referred to as an HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format that does not include L-STF, L-LTF, and L-SIG, but consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).

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

[0110] An example of a 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)). Depending on specific examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-users (MUs), but the HE PPDU format for single users (SUs) does not include the HE-SIG-B. In addition, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us. For example, 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 later, based on the presence of RL-SIG.

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

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

[0113] The EHT TB PPDU of Fig. 7(f) omits the EHT-SIG compared to the EHT MU PPDU. An STA that has received a trigger for UL MU transmission (e.g., a trigger frame or TRS (triggered response scheduling)) can perform UL transmission based on the EHT TB PPDU format.

[0114] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated so that even legacy STAs can attempt demodulation and decoding, and can be mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated so that they can be demodulated and decoded by an STA that has successfully decoded a non-legacy SIG (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in the corresponding field, and can be mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

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

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

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

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

[0119] The A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in a new PPDU format (e.g., UHR PPDU format) not shown in FIG. 7, and in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-dependent bits can be different.

[0120] For example, 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.

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

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

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

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

[0125] Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the PPDU's bandwidth. For example, the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth greater than a certain size.

[0126] In the example of FIG. 7, non-legacy SIGs such as HE-SIG-B and EHT-SIG may include control information for the receiving STA. The non-legacy SIG may be transmitted over at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the EHT-SIG may be included in a previous SIG (e.g., HE-SIG-A, U-SIG, etc.).

[0127] Non-legacy SIGs, such as HE-SIG-B and EHT-SIG, may contain common fields and user-specific fields. Common and user-specific fields may be coded separately.

[0128] In some cases, common fields may be omitted. For example, in a compressed mode where non-OFDMA (orthogonal frequency multiple access) is applied, common fields may be omitted, and multiple STAs may receive PPDUs (e.g., data fields of PPDUs) over the same frequency band. In a non-compressed mode where OFDMA is applied, multiple users may receive PPDUs (e.g., data fields of PPDUs) over different frequency bands.

[0129] The number of user-specific fields can be determined based on the number of users. A single user block field can contain up to two user fields. Each user field can be associated with either MU-MIMO allocation or non-MU-MIMO allocation.

[0130] The common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, and the length of the Tail bits may be determined as 6 bits and set to 000000. The common field may include RU allocation information. The RU allocation information may include information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.

[0131] An RU can contain multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA techniques. RUs can also be defined when transmitting signals to a single STA. Resources can be allocated on an RU basis for non-legacy STFs, non-legacy LTFs, and data fields.

[0132] Depending on the PPDU bandwidth, an applicable RU size can be defined. The RU may be defined identically or differently for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80MHz PPDU, 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. For example, a tone plan for a wide bandwidth can be defined in the form of multiple repetitions of a low bandwidth tone plan.

[0133] RUs of different sizes can be defined, such as 26-ton RU, 52-ton RU, 106-ton RU, 242-ton RU, 484-ton RU, 996-ton RU, 2X996-ton RU, 3X996-ton RU, etc. A multiple RU (MRU) is distinguished from multiple individual RUs and corresponds to a group of subcarriers consisting of multiple RUs. For example, one MRU can be defined as 52+26-tons, 106+26-tons, 484+242-tons, 996+484-tons, 996+484+242-tons, 2X996+484-tons, 3X996-tons, or 3X996+484-tons. Additionally, multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.

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

[0135] The names of each field in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by those names. Furthermore, the examples of the present disclosure can be applied not only to the PPDU format exemplified in FIG. 7, but also to a new PPDU format in which some fields are excluded and / or some fields are added based on the PPDU formats of FIG. 7.

[0136] target wake time (TWT)

[0137] TWT is a PS (Power Saving) technology that can improve the energy efficiency of non-AP STAs by defining a service period (SP) between APs and non-AP STAs and sharing information about the SP to reduce contention of the medium.

[0138] An STA that performs Request / Suggest / Demand operations during the TWT Setup phase can be called a TWT Requesting STA. Additionally, an AP that responds to the request with an Accept / Reject option can be called a TWT Responding STA.

[0139] The setup phase may include a process of determining / defining a TWT request from an STA to an AP, the type of TWT operation to be performed, and the type of frames to be transmitted and received. TWT operations can be divided into individual TWT and broadcast TWT.

[0140] FIG. 8 is a drawing illustrating an example of an individual TWT operation to which the present disclosure can be applied.

[0141] Individual TWT is a mechanism in which an AP and a non-AP STA negotiate the awake / doze status of a non-AP STA through transmission and reception of TWT request / response frames, and then exchange data.

[0142] In the example of FIG. 8, AP and STA 1 can form a trigger-enabled TWT agreement through a TWT request frame and a TWT response frame.

[0143] Here, the method used by STA 1 is a solicited TWT method, in which STA 1 transmits a TWT request frame to the AP, and STA 1 receives information for TWT operation from the AP through a TWT response frame.

[0144] On the other hand, STA 2 performing the unsolicited TWT method can receive information about the setup of a trigger-enabled TWT agreement from the AP through an unsolicited TWT response.

[0145] Specifically, STA 2 can calculate the next TWT by adding a specific number from the current TWT value. During the trigger-enabled TWT SP, the AP can transmit a trigger frame to the STAs. The trigger frame can inform the STAs that the AP has buffered data. In response, STA 1 can inform the AP of its awake state by transmitting a PS-Poll frame. Additionally, STA 2 can inform the AP of its activated state by transmitting a QoS Null frame. Here, the data frames transmitted by STA 1 and STA 2 can be frames in the TB PPDU format. The AP, which has confirmed the states of STA 1 and STA 2, can transmit a DL MU PPDU to the activated STAs. When the corresponding TWT SP expires, STA 1 and STA 2 can transition to a doze state.

[0146] FIG. 9 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.

[0147] Broadcast TWT is a TWT method in which a non-AP STA (or TWT scheduling STA) obtains information such as the target beacon transmission time (TBTT) and listen interval by transmitting and receiving TWT request / response frames with the AP (or TWT scheduled STA). Here, a TBTT negotiation operation may be performed. Based on this, the AP can define a frame that will include TWT scheduling information through a beacon frame.

[0148] In Fig. 9, STA 1 performs a requested TWT operation, and STA 2 performs an unsolicited TWT operation. The AP can transmit a DL MU PPDU after checking the awake status of the STAs through the trigger transmitted by the AP. This can be the same as the process of an individual TWT. In broadcast TWT, a trigger-enabled TWT SP including a beacon frame can be repeated multiple times at a regular cycle.

[0149] Transmission of TWT information can be accomplished via a TWT information frame and a TWT information element. A TWT information frame is transmitted by an STA to request or transmit information about a TWT agreement, and is transmitted by one of the STAs in the existing TWT agreement. The action field of the TWT information frame includes a TWT information field.

[0150] The TWT Information field may include a 3-bit TWT flow identifier subfield, a 1-bit response requested subfield, a 1-bit next TWT request subfield, a 2-bit next TWT subfield size subfield, a 1-bit all TWT subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0151] Here, the TWT Flow Identifier subfield can be used to identify the flow for which TWT information is requested / provided.

[0152] The Response Request subfield may indicate whether the transmitter of a frame containing a TWT Information field requests transmission of a TWT Information frame (to be transmitted in response to reception of that frame). To request the receiver not to transmit a TWT Information frame in response to reception of the frame, the Response Request subfield value may be set to 0. To request the receiver to transmit a TWT Information frame in response to reception of the frame, the Response Request subfield value may be set to 1.

[0153] To indicate a request for transmission of a TWT information frame containing the following TWT field (where the length of the TWT information frame is not 0), the value of the Next TWT subfield may be set to 1. Otherwise, the value of the Next TWT subfield may be set to 0.

[0154] The Next TWT Subfield Size subfield can indicate the size of the next TWT subfield. If the size of the next TWT subfield is 0 / 32 / 48 / 64 bits, the value of the Next TWT Subfield Size subfield can be set to 0 / 1 / 2 / 3.

[0155] All TWT subfield values ​​may be set to 1 by the HE STA, which may mean that the TWT information frame has recalculated all TWTs. Otherwise, all TWT subfield values ​​may be set to 0.

[0156] Figure 10 is a drawing for explaining an example of a TWT information element format.

[0157] TWT elements can be transmitted and received in beacons, probe responses, (re)association response frames, etc. TWT elements can include an element identifier (ID) field, a length field, a control field, and a TWT parameter information field.

[0158] The control fields of a TWT element have the same format regardless of whether it is an individual TWT or a broadcast TWT.

[0159] The NDP paging indication subfield can have a value of 1 if the NDP paging field exists, and a value of 0 if the NDP paging field does not exist.

[0160] The responder PM mode subfield may indicate a power management (PM) mode.

[0161] The negotiation type subfield may indicate whether the information contained in the TWT element is about negotiation of parameters of a broadcast TWT or individual TWT(s), or about a wake TBTT interval.

[0162] For example, if the negotiation type subfield has a value of 0, the TWT subfield is for a future individual TWT SP start time, and the TWT element contains one individual set of TWT parameters. This may correspond to an individual TWT negotiation between a TWT requesting STA and a TWT responding STA, or to an individual TWT announcement by a TWT responder.

[0163] For example, if the value of the negotiation type subfield is 1, the TWT subfield is for the next TBTT time, and the TWT element contains one individual set of TWT parameters. This may correspond to the wake TBTT and wake interval negotiation between the TWT scheduled STA and the TWT scheduling AP.

[0164] For example, if the value of the negotiation type subfield is 2, the TWT subfield is for a future broadcast TWT SP start time, and the TWT element contains one or more broadcast TWT parameter sets. This may correspond to providing a broadcast TWT schedule to a TWT-scheduled STA by including the TWT element in a broadcast management frame transmitted by the TWT scheduling AP.

[0165] For example, if the negotiation type subfield has a value of 3, the TWT subfield is for a future broadcast TWT SP start time, and the TWT element contains one or more sets of broadcast TWT parameters. This may correspond to managing membership in a broadcast TWT schedule by including the TWT element in individually addressed management frames transmitted by either the TWT-scheduling STA or the TWT-scheduling AP.

[0166] If the TWT information frame disabled subfield is set to 1, it indicates that reception of TWT information frames by the STA is disabled, otherwise it may be set to 0.

[0167] The wake duration unit subfield indicates the unit of the nominal minimum TWT wake duration field. The wake duration unit subfield may be set to 0 if the unit is 256 us and set to 1 if the unit is TU. For non-HE / EHT STAs, the wake duration unit subfield may be set to 0.

[0168] The most significant bit (MSB) of the negotiation type field may correspond to a broadcast field. If the broadcast field is 1, the TWT element may contain one or more broadcast TWT parameter sets. If the broadcast field is 0, the TWT element may contain only one individual TWT parameter set. A TWT element with the broadcast field set to 1 may be referred to as a broadcast TWT element.

[0169] Also, although FIG. 10 illustrates a case where the reserved field consists of 2 bits, this is only one embodiment. For example, a TWT element may include a Link ID bitmap present field (e.g., 1 bit) and a reserved field (e.g., 1 bit).

[0170] For example, if the Link ID Bitmap Existence field is set to 1, the Link ID Bitmap subfield may be set to exist in the individual TWT parameter set field format described later, and if the Link ID Bitmap Existence field is set to 0, the Link ID Bitmap subfield may be set not to exist in the individual TWT parameter set field format.

[0171] Fig. 11 is a diagram illustrating examples of individual TWT parameter set field formats. Fig. 12 is a diagram illustrating examples of broadcast TWT parameter set field formats.

[0172] The TWT parameter information field included in the TWT element of Fig. 10 may have a different configuration depending on the individual TWT or broadcast TWT.

[0173] For individual TWTs, the TWT parameter information field within the TWT element contains a single individual TWT parameter set field.

[0174] In the case of a broadcast TWT, the TWT parameter information field within the TWT element contains one or more broadcast TWT parameter set fields. Each broadcast TWT parameter set may contain specific information about one broadcast TWT.

[0175] As illustrated in FIGS. 11 and 12, the individual TWT parameter set field and the broadcast TWT parameter set field include common subfields.

[0176] The request type subfield may be the same size as the individual TWT parameter set field and the broadcast TWT parameter set field, but may have different detailed configurations. This will be described later.

[0177] The target wake time subfield indicates the start time of the upcoming individual / broadcast TWT SP.

[0178] The nominal maximum TWT wake duration subfield indicates the minimum interval during which a TWT requesting STA expects to wake up to complete a frame exchange associated with a TWT flow identifier during the TWT wake interval duration. Here, the TWT wake interval may mean the average time between consecutive TWT SPs expected by the TWT requesting STA.

[0179] The TWT Wake Interval Mantissa subfield can be expressed as a binary value of the TWT wake interval value in microseconds.

[0180] Referring to Figure 11, the TWT group assignment subfield, TWT channel, and NDP paging subfield are included only in the individual TWT parameter set fields.

[0181] The TWT Group Assignment subfield provides the TWT requesting STA with information about the TWT group to which the STA is assigned. This information can be used to calculate the TWT value within the TWT group. The TWT value of the STA may be equal to the value of the zero offset multiplied by the value of the TWT offset multiplied by the value of the TWT unit.

[0182] Here, the TWT group information may include a TWT group ID subfield, a zero offset presence subfield, a group zero offset subfield, a TWT unit subfield, and a TWT offset subfield.

[0183] The TWT Group ID subfield indicates the identifier of the TWT group to which the requesting STA is assigned. A TWT group may refer to a group of STAs having a TWT value within a specific interval of TSF values. If the TWT Group ID subfield value is set to 0, this may indicate a unique TWT group that includes all STAs of the BSS.

[0184] The zero offset presence subfield can indicate whether a zero offset subfield exists in the group. For example, if the zero offset presence subfield value is set to 1, this can indicate that a zero offset subfield exists in the group. If the zero offset presence subfield value is set to 0, this can indicate that a zero offset subfield does not exist in the group.

[0185] The zero offset subfield of the group is optional and may indicate the initial TWT value of the TWT group identified by the TWT group ID.

[0186] The TWT Unit subfield may indicate the incremental unit of the TWT value within a TWT group identified by the TWT Group ID. For example, if the TWT Unit time values ​​are 32 μs, 256 μs, 1024 μs, 8.192 ms, 32.768 ms, and 262.144 ms, respectively, the TWT Unit subfield values ​​may be expressed as 0, 1, 2, 3, and 4, respectively.

[0187] The TWT offset subfield may indicate the position within a specified group of an STA corresponding to the RA of a frame containing a TWT element.

[0188] The TWT Channel subfield indicates a bitmap indicating allowed channels. When transmitted by a TWT requesting STA, the TWT Channel subfield may include a bitmap indicating a channel that the STA requests to use as a temporary default channel during the TWT SP. When transmitted by a TWT responding STA, the TWT Channel subfield may include a bitmap indicating a channel on which the TWT request is allowed.

[0189] The NDP paging subfield is optional and may include information such as an identifier of the STA being paged, the maximum number of TWT wake intervals between NDP paging frames, etc.

[0190] Referring to FIG. 12, the broadcast TWT info subfield is included only in the broadcast TWT parameter set field. The broadcast TWT info subfield may include a 3-bit reserved bit, a 5-bit broadcast TWT identifier (ID) subfield, and an 8-bit broadcast TWT persistence subfield. The broadcast TWT identifier subfield indicates the broadcast ID of a specific broadcast TWT for which an STA requests participation or provides TWT parameters, depending on the value of the TWT setup command subfield of the TWT element. The broadcast TWT persistence subfield indicates the number of TBTTs planned in the schedule of the broadcast TWT.

[0191] Next, we will explain the detailed configuration of the request type subfield.

[0192] First, the format of the request type subfield of the individual TWT parameter set field is described with reference to FIG. 11.

[0193] The TWT request subfield can indicate whether the STA is a requesting STA or a responding STA. If the value is 1, it indicates that the STA is a TWT requesting STA or a scheduled STA, and if it is 0, it indicates that the STA is a TWT responding STA or a scheduling AP.

[0194] The TWT setup command subfield can represent commands such as Request, Suggest, Demand, Accept, Alternate, Dictate, and Reject.

[0195] The trigger subfield indicates whether a trigger frame is used in the TWT SP. If the value is 1, the trigger is used, and if it is 0, the trigger is not used.

[0196] The implicit subfield can indicate whether the TWT is implicit or explicit. A value of 1 indicates implicit TWT, while a value of 0 indicates explicit TWT.

[0197] The flow type subfield may indicate the type of interaction between a TWT requesting STA (or a TWT-scheduled STA) and a TWT responding STA (or an AP that schedules the TWT). If the value is 1, it may mean announced TWT, in which the STA sends a wake-up signal to the AP by transmitting a PS-Poll or APSD (automatic power save delivery) trigger frame before a non-trigger frame is transmitted from the AP to the STA. If the value is 0, it may mean unannounced TWT.

[0198] The TWT flow identifier subfield may contain a 3-bit value that uniquely identifies specific information about the TWT request in other requests made between the same TWT requesting STA and TWT responding STA pair.

[0199] The TWT wake interval exponent subfield can set the TWT wake interval value in binary microseconds. For individual TWTs, this can mean the interval between individual TWT SPs. The TWT wake interval of the requesting STA can be defined as [TWT Wake Interval Mantissa * 2 * TWT Wake Interval Exponent].

[0200] The TWT protection subfield can indicate whether a TWT protection mechanism is used. If the value is 1, TXOPs within a TWT SP can be initiated with a NAV protection mechanism, such as (MU)RTS / CTS or a CTS-to-self frame. If the value is 0, the NAV protection mechanism may not be applied.

[0201] Referring to FIG. 12, some of the subfields of the request type subfield of the broadcast TWT parameter set field are common to the subfields of the request type subfield of the individual TWT parameter set fields, and therefore, a description thereof is omitted. The subfields included only in the broadcast TWT parameter set are described below.

[0202] The Last Broadcast Parameter Set subfield indicates whether this is the last broadcast TWT parameter set. A value of 1 indicates that this is the last broadcast TWT parameter set, while a value of 0 indicates that there is a next broadcast TWT parameter set.

[0203] The Broadcast TWT Recommendation subfield may indicate recommendations for the frame types transmitted by the AP during a Broadcast TWT SP, with values ​​from 1 to 7.

[0204] For example, when the broadcast TWT recommendation subfield value is set to 4, the corresponding broadcast TWT SP can be referred to as an r-TWT SP. That is, the broadcast TWT parameter set in which the broadcast TWT recommendation subfield value is set to 4 can be referred to as a restricted TWT parameter set. At this time, during the r-TWT SP, the AP and member r-TWT scheduled STAs can specify the transmission priority of QoS data frames, which are delay-sensitive traffic. In addition, a broadcast TWT element that only includes an r-TWT parameter set field can be referred to as a restricted TWT element.

[0205] The last bit of the Request Type subfield of the Broadcast TWT Parameter Set field may be reserved.

[0206] As an example of the present disclosure, the Broadcast TWT Parameter Set field may include a limited TWT Traffic Information (info) subfield. As an example, the TWT Traffic Information subfield may follow the Broadcast TWT Information field of the Broadcast TWT Parameter Set field illustrated in FIG. 12.

[0207] As an example of the present disclosure, as illustrated in (a) of FIG. 13, the broadcast TWT information subfield may include a restricted TWT traffic information present subfield and a restricted TWT schedule full subfield.

[0208] The TWT Traffic Information Existence subfield and the Limited TWT Schedule Full subfield may be set in the first bit (B0) and the second bit (B1) of the Broadcast TWT Information field shown in FIG. 12, respectively.

[0209] For example, if the restricted TWT traffic information field is present on the broadcast TWT parameter set field, the restricted TWT traffic information presence subfield value of the restricted TWT parameter set field may be set to 1. Otherwise, the restricted TWT traffic information presence subfield value may be set to 0. For non-EHT STAs, the restricted TWT traffic information presence subfield may be reserved.

[0210] If the Restricted TWT Schedule Full subfield value is set to 1, this may indicate that the r-TWT scheduling AP is unlikely to accept a request from a STA of the BSS to establish a new membership in that schedule. Otherwise, the Restricted TWT Schedule Full subfield value may be set to 0.

[0211] The Restricted TWT Schedule Full subfield may be valid if the Restricted TWT Parameter Set field is carried in a TWT element with the Negotiation Type subfield set to 2 and the TWT element is transmitted by an EHT AP.

[0212] If the Restricted TWT Traffic Information Presence subfield value of the Broadcast TWT Information subfield is set to 1, the Restricted TWT Traffic Information field may be present in the Restricted TWT Parameter Set field.

[0213] As illustrated in (b) of FIG. 13, the restricted TWT traffic information field may include a traffic information control subfield, a restricted TWT DL TID bitmap subfield, and a restricted TWT UL TID bitmap subfield.

[0214] As illustrated in (c) of FIG. 13, the traffic information control field may include a DL TID bitmap valid subfield and a UL TID bitmap valid subfield.

[0215] The DL TID Bitmap Valid subfield may be set to 1 to indicate that the restricted TWT DL TID bitmap field is valid. The DL TID Bitmap Valid subfield may be set to 0 to indicate that DL traffic of all TIDs mapped to DLs for a link for which r-TWT membership is established is identified as delay-sensitive traffic and the restricted TWT DL TID bitmap field is reserved.

[0216] The UL TID Bitmap Valid subfield may be set to 1 to indicate that the restricted TWT UL TID bitmap field is valid. The UL TID Bitmap Valid subfield may be set to 0 to indicate that UL traffic of all TIDs mapped to the UL for a link for which r-TWT membership is established is identified as delay-sensitive traffic and the restricted TWT UL TID bitmap field is reserved.

[0217] The Restricted TWT DL TID Bitmap and Restricted TWT UL TID Bitmap subfields may specify TIDs identified as delay-sensitive traffic streams in the DL and UL directions, respectively, by an r-TWT scheduling AP or an R-TWT scheduling STA.

[0218] A value of 1 at bit position k in the bitmap may indicate that TID k is classified as a delay-sensitive traffic stream. A value of 0 at bit position k in the bitmap may indicate that TID k is not classified as a delay-sensitive traffic stream.

[0219] R-TWT Membership Setup and R-TWT SP Announcement

[0220] R-TWT membership may be established using the same procedure used to establish broadcast TWT membership, except that the broadcast TWT element carried on the TWT setup frame includes one or more restricted TWT parameter set fields. An R-TWT scheduling AP may set the trigger field to 1 in the R-TWT parameter set field it transmits. When included in an individually addressed TWT setup frame transmitted by an R-TWT scheduling AP or an R-TWT scheduling STA, the R-TWT traffic information present subfield of the broadcast TWT information field included in the R-TWT parameter set field may be set to 1.

[0221] An R-TWT scheduling AP and an R-TWT scheduling STA may set a restricted TWT traffic information field to identify the TIDs carrying latency-sensitive traffic in the DL and UL for the established R-TWT membership.

[0222] When R-TWT membership is established, the EHT AP can advertise R-TWT schedule information by including a restricted TWT parameter set field in the broadcast TWT element included in the transmitted management frame. The membership can be established with the associated EHT AP or a non-transmitting AP belonging to the same multi-BSSID set or co-hosted BSSID set as the transmitting AP. The transmitted BSSID in the multi-BSSID set can include all R-TWT schedules advertised for the transmitting BSSID and all non-transmitting BSSIDs in the same multi-BSSID set.

[0223] An R-TWT scheduling AP that includes an R-TWT Parameter Set field in a broadcast TWT element may set the Restricted TWT Traffic Information Present subfield of the Restricted TWT Parameter Set field to 0 when the Negotiation Type subfield of the TWT element is 2. A non-AP STA may not request membership establishment in an R-TWT schedule advertised by an R-TWT scheduling AP with the Restricted TWT Schedule subfield set to 2. An R-TWT scheduling AP may determine the start time of an R-TWT SP that occurs after the first R-TWT SP (the next R-TWT SP start time) in a periodic R-TWT schedule based on the start time of the first R-TWT SP and the TWT wake interval of the corresponding R-TWT schedule.

[0224] TXOP and backoff procedure rules for R-TWT SP

[0225] A non-AP EHT STA (e.g., a TXOP holder) with "dot11RestrictedTWTOptionImplemented" set to true can ensure that the TXOP ends before the start time of an active R-TWT SP advertised by the associated AP or an AP corresponding to a BSSID transmitted in a multi-BSSID set to which the associated AP belongs.

[0226] Here, TXOP refers to a time interval during which a specific STA has the right to initiate a frame exchange sequence on a wireless medium (WM). TXOP can be defined by a starting time (during which the STA has the right) and a maximum duration value.

[0227] And, a TXOP holder means an STA that has been granted a TXOP by the HC (hybrid coordinator) or has successfully competed for the TXOP. In other words, a TXOP holder means an STA that has the authority to perform a frame exchange sequence within a TXOP. A TXOP respondent means an STA that transmits a frame as a response to a frame received from the TXOP holder during a frame exchange sequence, but has not acquired a TXOP during the process.

[0228] Additionally, before starting a PPDU transmission, a non-AP EHT STA with "dot11RestrictedTWTOptionImplemented" set to true may check if there is enough time to complete frame exchange before the R-TWT SP starts, and if there is not enough time, the STA may postpone transmission by selecting a random backoff count using the current CW (without advancing to the next value in the sequence). An R-TWT schedule that is announced in a beacon or probe response frame and is not in a non-transmitted BSSID profile may include schedules for both transmitted and non-transmitted BSSIDs.

[0229] An EHT AP (i.e., TXOP holder) with "dot11RestrictedTWTOptionImplemented" set to true can ensure that the TXOP ends before the start time of its own advertised active R-TWT SP, as long as the remaining part of the TXOP belonging to the R-TWT SP is not used to deliver DL frames of the R-TWT DL TID or to request UL frames of the R-TWT UL TID.

[0230] When an R-TWT SP starts, member STAs may suspend decrementing backoff counters for ACs without a mapped R-TWT TID until all frames in the R-TWT TID have been delivered, and member STAs may resume decrementing thereafter or when the SP terminates.

[0231] quiet interval associated with R-TWT SP

[0232] An R-TWT scheduling AP may schedule at most one silent interval overlapping an R-TWT SP, wherein the (overlapping) silent interval has a duration of 1 time unit (TU) and may start concurrently with the R-TWT SP.

[0233] To schedule overlapping silent intervals for one or more R-TWT SPs belonging to one or more periodic or aperiodic R-TWT schedules, an EHT AP may do so by transmitting one or more quiet elements in its beacon and probe response frames.

[0234] An EHT AP associated with an AP MLD may not include any silence elements corresponding to overlapping silence intervals scheduled and advertised by other APs affiliated with the same AP MLD in their transmitted beacon or probe response frames. Non-AP EHT STAs may behave as if the overlapping silence intervals do not exist.

[0235] Multi-Access Point (MAP) operation

[0236] Below, examples of the present disclosure for multi-access point (MAP) operation are described.

[0237] MAP operation may be a general term for a technique in which multiple APs / STAs cooperate with each other to transmit and receive data when communicating with other STA(s). MAP operation may include a first method (i.e., multi-APs / STAs co-transmission method) in which multiple APs simultaneously transmit data to STA(s), and a second method (i.e., multi-APs / STAs coordination method) in which an appropriate AP among multiple APs divides an appropriate area (e.g., frequency / time / spatial area) and then transmits data to specific STA(s) (i.e., appropriate STA(s)).

[0238] Specifically, the first method may include a method in which multiple APs / STAs perform communication with each STA at the same time (e.g., coordinated spatial reuse (C-SR) method) and a method in which multiple APs / STAs perform joint transmission to the same STA(s) (e.g., joint transmission (J-TX) method).

[0239] In the C-SR method, multiple APs / STAs share channel information (e.g., transmit power (Tx power), Received Signal Strength Indicator (RSSI), etc.) with STA(s), and can communicate with STA(s) at the same time based on the channel information. In the J-TX method, multiple APs / STAs share channels and data with STA(s), and can communicate with STA(s) at the same time based on the shared channels and data.

[0240] As described above, the second method refers to a method in which APs / STAs divide a frequency, time, or space domain and communicate with other STA(s) in the divided domain. The frequency domain-based communication method may include the C(coordinated)-OFDMA method, the time domain-based communication method may include AP selection, relay operation, C(coordinated)-TDMA (time division multiple access), V(virtual)-BSS method, etc., and the space domain-based communication method may include the C(coordinated)-BF (beamforming) method, etc.

[0241] For example, in the case of a frequency domain-based communication method, multi-APs / STAs can share channel information according to frequency bands with STA(s), and select an appropriate frequency band based on the shared channel information. Multi-APs / STAs can communicate with STA(s) in the selected frequency band.

[0242] As another example, in the case of a time domain-based communication scheme, a representative AP can be set to take the lead in communication by having the STA(s) select an appropriate AP / STA(s) (here, the representative AP is also included).

[0243] As another example, in the case of a spatial domain-based communication method, multiple APs / STAs can share channel information and other information with STA(s), and calculate a BF matrix suitable for each AP's communication or that does not interfere with other APs. The multiple APs / STAs can communicate with the STA(s) based on the calculated BF matrix.

[0244] To support the MAP operation described above, a representative AP can select and instruct an AP / STA (hereinafter, a participating AP / STA) for communication with an STA.

[0245] The representative AP (here, the representative AP can be replaced with a master AP, a sharing AP, or a primary AP) initiates and controls MAP operations for transmission and reception between multiple APs. The representative AP groups participating APs and manages links with participating APs to enable information sharing among them. The representative AP manages information about the BSS comprised of participating APs and information about STAs associated with the BSS.

[0246] Participating APs (wherein the participating AP can be replaced by a slave AP, a shared AP, or a secondary AP) associate with the primary AP and can share control information, management information, and data traffic. Participating APs perform the same basic functions as APs, which are necessary to establish a base station service (BSS) in a wireless LAN.

[0247] In MAP operation, a participating STA can associate with a participating AP or a representative AP and form a BSS.

[0248] In a MAP environment, a representative AP and a participating AP can directly transmit and receive data with each other. A representative AP and an STA may not be able to directly transmit and receive data with each other. A participating AP (e.g., a participating AP associated with an STA) can directly transmit and receive data with the STA. One of the participating APs can serve as the representative AP.

[0249] How to Protect OBSS R-TWT within a Multi-BSS

[0250] In a multi-BSS environment, the range of an overlapping BSS (hereinafter, OBSS) is formed / set based on the range within which an STA can receive frames (e.g., beacon frames) transmitted from one or more APs.

[0251] For example, as illustrated in FIG. 14 below, the signaling ranges of AP 1 and AP 2 may overlap, and STA(s) (e.g., STA 1-2 or / and STA 2-4) located within that range may receive beacon frames transmitted by AP 1 within the BSS 1 to which it is associated as well as beacon frames transmitted by AP 2 within the BSS 2 to which it is not associated.

[0252] Here, AP 1 and AP 2 may be slave APs belonging to a multi-AP group with the same master AP, but are not limited thereto. Either AP 1 or AP 2 may be the master AP.

[0253] The AP may transmit a beacon frame containing R-TWT scheduling information to the corresponding STA(s). At this time, the STA(s) receiving the beacon frame may be located within the range that protects the R-TWT SP(s). For example, the STA(s) may protect the R-TWT SP based on the R-TWT scheduling information received from the AP according to the above-described method.

[0254] However, the STA(s) located within the range corresponding to the OBSS can receive a beacon frame from a neighboring AP (i.e., an AP of an unassociated BSS to which the STA(s) do not belong) (e.g., AP 2), and the beacon frame can include R-TWT (hereinafter, OBSS R-TWT) scheduling information generated by the neighboring AP. Previously, there was a problem in that not only was there no definition of a method for the STA(s) to protect the OBSS R-TWT SP, but also a method for transmitting and receiving low-latency traffic / data during the OBSS R-TWT SP.

[0255] Below, various operations (e.g., OBSS R-TWT SP protection operation, etc.) based on the R-TWT scheduling information of the neighboring AP (OBSS) by the STA and the AP of the BSS to which the STA is connected (e.g., AP 1) are described.

[0256] As an example of the present disclosure, additional rules for protection of R-TWT SP and OBSS R-TWT SP can be defined / established.

[0257] For example, if an STA (e.g., STA 1-1 and STA 1-3 in FIG. 14) is not located in the OBSS area, the additional rule for protecting the OBSS R-TWT SP may not be applied to the STA. The STA may notify the BSS AP that the STA is not located in the OBSS range. For example, STA 1-1 may notify AP 1 that it has not received data / traffic with a different BSS color from AP 1 for a certain period of time or has received data / traffic at a certain threshold (i.e., does not affect the BSS of AP 1).

[0258] For example, when an AP schedules an SP to a STA connected to the AP based on OBSS R-TWT schedule information, if the R-TWT SP of a neighboring AP affects an STA (e.g., STA 1-2) or the SP of a BSS affects an STA connected to a neighboring AP (e.g., STA 2-4), the SP of the BSS and the R-TWT SP of the OBSS may not overlap.

[0259] In describing the present disclosure, an STA may include a non-AP STA and an AP STA, and an R-TWT SP announced by an AP of a BSS to which the STA is not associated may be referred to as an OBSS R-TWT SP or an R-TWT SP scheduled by another AP. In addition, an associated AP may mean an AP of a BSS to which the STA is associated (i.e., a BSS AP).

[0260] FIG. 15 is a flowchart illustrating the operation of an STA according to one embodiment of the present disclosure. Here, the STA may be associated with the BSS of the first AP. That is, from the perspective of the STA, the second AP may be a neighboring AP. The STA may be located in an area where the BSS of the first AP and the BSS (i.e., OBSS) of the second AP overlap, but is not limited thereto.

[0261] The STA can transmit information related to at least one BSS (basic service set) color to the AP (S1510).

[0262] Specifically, the STA can acquire at least one BSS color based on at least one physical layer protocol data unit (PPDU) received from at least one AP including the second AP during a predefined time period. That is, the STA can collect / acquire the BSS color included in at least one PPDU received during the predefined time period.

[0263] Information about at least one BSS color may be included in an element related to the BSS color (e.g., a BSS color list element). The STA may transmit the element related to the BSS color to the first AP via a TWT setup frame. The element related to the BSS color may include a subfield indicating the number of at least one BSS color and at least one BSS color subfield indicating each of at least one BSS color.

[0264] The STA can receive information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by a first AP and information related to a second R-TWT SP scheduled by a second AP from the first AP (S1520).

[0265] That is, the STA may receive a first frame from the first AP that includes information related to the first R-TWT SP and information related to the second R-TWT SP (e.g., a BSS color associated with the second R-TWT SP). For example, the first frame may be, but is not limited to, a management frame such as a beacon frame.

[0266] Based on the BSS color of the second AP being included in at least one BSS color, the STA can perform a protection operation of the second R-TWT SP (S1530).

[0267] That is, the fact that the BSS color of the second AP is included in at least one BSS may mean that the STA is affected by the BSS (i.e., OBSS) of the second AP. Accordingly, the STA may perform the protection operation of the second R-TWT SP.

[0268] For example, the protection action of the second R-TWT SP may include terminating a transmission opportunity (TXOP) of the STA before the start time of the second R-TWT SP. As another example, the protection action of the second R-TWT SP may include an action according to an overlapping silence interval set by the first AP to overlap with the second R-TWT SP (e.g., not transmitting or receiving data during the overlapping silence interval, etc.).

[0269] As another example, the first R-TWT SP may be assigned to the STA by the first AP based on information related to the second R-TWT SP, and the first R-TWT SP and the second R-TWT SP may not overlap. In this case, the BSS color of the second AP may be included in at least one BSS, but is not limited thereto.

[0270] Additionally or alternatively, the operation in which the first R-TWT SP is allocated to the STA by the first AP based on information related to the second R-TWT SP and the feature that the first R-TWT SP and the second R-TWT SP do not overlap may be independent of at least one of steps S1510 to S1530. That is, regardless of whether the STA has transmitted information related to at least one BSS color to the first AP, the first R-TWT SP may be allocated to the STA by the first AP based on information related to the second R-TWT SP, and the first R-TWT SP and the second R-TWT SP may not overlap.

[0271] For example, based on the fact that the BSS color of the second AP is not included in the at least one BSS color, the STA can perform data transmission and reception within the TXOP regardless of the second R-TWT SP. That is, the fact that the BSS color of the second AP is not included in the at least one BSS color may mean that the STA is not affected by the BSS (i.e., OBSS) of the second AP. Accordingly, the STA can perform data transmission and reception operations regardless of the second R-TWT SP (i.e., OBSS R-TWT AP) scheduled by the second AP.

[0272] Additionally or alternatively, based on the fact that the BSS color of the second AP is not included in the at least one BSS color, the STA may not receive information related to an overlapping silence interval overlapping with the second R-TWT SP from the first AP. That is, since the STA is not affected by the BSS (i.e., OBSS) of the second AP, the STA may not receive information related to an overlapping silence interval from the first AP.

[0273] Additionally or alternatively, the protection operation of the second R-TWT SP may not be performed by the STA based on the PD (packet detection) value associated with the BSS (i.e., OBSS) of the second AP corresponding to the transmission power of the STA being set higher than a first threshold value (e.g., a reference PD value). And, the protection operation of the second R-TWT SP may be performed by the STA based on the PD value associated with the BSS of the second AP corresponding to the transmission power of the STA being set lower than the first threshold value. In this case, the STA may not separately transmit information related to the BSS color to the AP. That is, regardless of whether the operation according to step S1510 (i.e., the operation of transmitting information related to at least one BSS color) is performed, the STA may determine whether to perform the protection operation of the second R-TWT SP based on whether the PD value associated with the BSS of the second AP corresponding to the transmission power of the STA is higher than the first threshold value. And, the first threshold value means a value that serves as a reference for determining whether an OBSS PD value matching the transmission power of the STA affects OBSS transmission.

[0274] Additionally or alternatively, the protection operation of the second R-TWT SP may not be performed by the STA based on whether the strength of a signal received from the second AP or at least one of the other STAs included in the BSS of the second AP is less than the second threshold. And, the protection operation of the second R-TWT SP may be performed by the STA based on whether the strength of a signal received from the second AP or at least one of the other STAs included in the BSS of the second AP is greater than the second threshold. In this case, the STA may not separately transmit information related to the BSS color to the AP. That is, regardless of whether the operation according to step S1510 (i.e., the operation of transmitting information related to at least one BSS color) is performed, the STA may determine whether to perform the protection operation of the second R-TWT SP based on whether the strength of a signal received from the second AP or at least one of the other STAs included in the BSS of the second AP is greater than the second threshold. And, the second threshold value means a reference value related to the signal strength for determining whether the STA should protect the second R-TWT SP.

[0275] The method performed by the STA described in the example of FIG. 15 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may transmit information related to at least one BSS color to the first AP through one or more transceivers (106). The one or more processors (102) may receive information related to a first R-TWT SP scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP from the first AP through one or more transceivers (106). The one or more processors (102) may perform a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in at least one BSS color.

[0276] The above memory (104) can store instructions for performing the method described in the example of FIG. 15 when executed by one or more processors (102).

[0277] FIG. 16 is a diagram for explaining the operation of the first AP according to one embodiment of the present disclosure.

[0278] The first AP can receive information related to at least one BSS color from the STA (S1610).

[0279] The first AP can determine whether the STA is affected by the BSS of the second AP based on information related to at least one BSS color.

[0280] The first AP may transmit information related to the first R-TWT SP scheduled by the first AP and information related to the second R-TWT SP scheduled by the second AP to the STA (S1620). Specifically, the first AP may obtain information related to the second R-TWT SP from the second AP or / and a third party (e.g., an STA, etc.).

[0281] For example, a protection operation of a second R-TWT SP may be performed based on whether the BSS color of the second AP is included in at least one BSS color. The protection operation of the second R-TWT SP has been described with reference to FIG. 15, so a redundant description will be omitted.

[0282] The method performed by the second STA described in the example of FIG. 16 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 10 may receive information related to at least one BSS color from the STA through one or more transceivers (206). The one or more processors (202) may transmit information related to a first R-TWT SP scheduled by a first AP and information related to a second R-TWT SP scheduled by a second AP to the STA through one or more transceivers (206).

[0283] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 16 when executed by one or more processors (202).

[0284] Hereinafter, the method by which the STA and the first AP process OBSS R-TWT scheduling information will be specifically described with reference to FIGS. 15 and 16.

[0285] Example 1

[0286] Embodiment 1 relates to a method for an Associated AP to obtain OBSS R-TWT scheduling information. As an example of the present disclosure, an Associated AP may obtain OBSS R-TWT scheduling information using at least one of the following methods.

[0287] Method 1: If direct wired / wireless data transmission and reception between APs (i.e., Associated AP and neighboring AP(s)) is possible, the Associated AP can transmit its R-TWT scheduling information to neighboring AP(s) or receive OBSS R-TWT scheduling information from neighboring AP(s).

[0288] Method 2: If direct wired / wireless data transmission and reception between APs is not possible, APs can share R-TWT scheduling information through a third-party management entity. That is, APs can share R-TWT scheduling information using the third-party management entity as a relay entity.

[0289] For example, APs can be located within the same ESS. Within the same ESS, where multiple BSSs are connected to a single DS, a third-party management entity can provide the same service (e.g., a centralized service). Accordingly, the third-party management entity relaying APs within the same ESS can serve a role similar to a master AP or network controller.

[0290] As another example, APs may be slaves (i.e., Shared AP or / and Scheduled AP) with the same AP as the master AP (i.e., Sharing AP or / and Scheduling AP). In this case, the third management entity may be the master AP.

[0291] Method 3: The STA can overhear a beacon frame announced by a neighboring AP and decode the overheard beacon frame. Then, the STA can transmit information related to the OBSS R-TWT SP included in the decoded beacon frame to the associated AP.

[0292] Example 2

[0293] Example 2 relates to a method for protecting OBSS R-TWT by STA type classified according to whether R-TWT is supported.

[0294] Depending on whether R-TWT is supported, STA types can be classified as follows.

[0295] - Pre-EHT STA that does not support R-TWT: This refers to an STA with Pre-EHT capability and may correspond to a legacy STA.

[0296] - EHT STA that does not support R-TWT: This is an STA with EHT capability, and may correspond to an STA that does not support R-TWT.

[0297] - EHT STA supporting R-TWT: This is an STA with EHT capability and may correspond to an STA supporting R-TWT. In this case, an EHT STA supporting R-TWT may be defined / configured not to consider protection operations for OBSS R-TWT SP.

[0298] Additionally, UHR STAs (or STAs on wireless LAN systems subsequent to IEEE 802.11 be-based wireless LAN systems) can be classified based on whether they support R-TWT and / or OBSS R-TWT. For example, a UHR STA can transmit capability information indicating whether it supports R-TWT and / or OBSS R-TWT to another STA (e.g., an AP), and the type of UHR STA can be classified based on the capability information.

[0299] - UHR STA that does not support R-TWT: This is an STA with UHR capability, and may correspond to an STA that does not support R-TWT.

[0300] - UHR STA supporting only R-TWT: This may correspond to an STA that has UHR capability but supports only R-TWT (i.e., operations and parameters related to R-TWT as illustrated in FIGS. 8 to 13). A UHR STA supporting only R-TWT may, but is not limited to, be unable to decode information related to OBSS R-TWT (e.g., information related to enhanced R-TWT). A UHR STA supporting only R-TWT may also be able to decode information related to OBSS R-TWT.

[0301] - UHR STA supporting enhanced R-TWT: This may correspond to an STA that supports UHR capability and enhanced R-TWT operation. Enhanced R-TWT operation may include protection operations for OBSS R-TWT SPs, etc.

[0302] Example 2-1

[0303] Embodiment 2-1 relates to a method for an STA classified in Embodiment 2 to protect an OBSS R-TWT SP. The method for protecting an OBSS R-TWT SP can be defined / applied by extending the above-described methods for an STA to report an R-TWT SP (e.g., overlapping quiet intervals and / or TXOP and backoff procedure rules of an R-TWT SP, etc.).

[0304] Here, the TXOP and backoff procedure rules of the R-TWT may include a rule for an STA (i.e., a TXOP holder) transmitting and receiving data during a TXOP that started before the R-TWT start time to stop the TXOP. The TXOP and backoff procedure rules of the R-TWT may also be applied to the OBSS R-TWT SP in the same manner. That is, a rule may be defined for an STA (i.e., a TXOP holder) transmitting and receiving data during a TXOP that started before the OBSS R-TWT start time to stop the TXOP.

[0305] Additionally, the overlapping silence interval may mean a silence interval allocated to overlap with an R-TWT SP for the same period of time. The BSS AP may set the silence interval to overlap with an OBSS R-TWT SP obtained through the method of obtaining OBSS R-TWT scheduling information disclosed in Embodiment 1. For example, the R-TWT scheduling AP (e.g., BSS AP) may set at least one (or at most one) overlapping interval that overlaps with an R-TWT SP and / or an OBSS R-TWT SP.

[0306] Below, a method for protecting OBSS R-TWT SP by STA type classified in Example 2 is described.

[0307] - Pre-EHT STA that does not support R-TWT: The STA can protect the OBSS R-TWT SP through overlapping silence intervals. For example, a Pre-EHT STA that does not support R-TWT can protect the OBSS R-TWT SP (through overlapping silence intervals set by the BSS AP to include the OBSS R-TWT SP).

[0308] - EHT STAs that do not support R-TWT: The STAs can protect OBSS R-TWT SPs through overlapping silence intervals. For example, an EHT STA that does not support R-TWT can protect OBSS R-TWT SPs (through overlapping silence intervals set by the BSS AP to include the OBSS R-TWT SPs).

[0309] - EHT STA supporting R-TWT: The behavior of an EHT STA supporting R-TWT may be determined depending on whether the BSS AP announces information about an OBSS R-TWT SP (i.e., an R-TWT SP scheduled / allocated by a neighboring AP) together with information about an R-TWT SP allocated by the BSS AP. Option 1 below relates to the case where the BSS AP announces an OBSS R-TWT SP to the STA (i.e., an EHT STA supporting R-TWT) together with information about an R-TWT SP allocated by the BSS AP, and option 2 relates to the case where the BSS AP does not announce an OBSS R-TWT SP to the STA together with information about an R-TWT SP allocated by the BSS AP.

[0310] - Option 1: If the BSS AP announces the OBSS R-TWT SP to the STA along with the information of the R-TWT SP it has allocated, the STA can protect the OBSS R-TWT SP by stopping the TXOP in progress before the OBSS R-TWT SP based on the TXOP and back-off procedure rules of the R-TWT SP.

[0311] The BSS AP may configure the OBSS R-TWT SP information in the same manner as the R-TWT SP information, so that the STA may not be able to distinguish between the OBSS R-TWT SP and the R-TWT SP. However, the BSS AP may configure the OBSS R-TWT SP information to correspond to the value of a specific broadcast TWT ID. In this case, the broadcast TWT ID corresponding to the OBSS R-TWT SP information may not overlap with the broadcast TWT ID corresponding to the R-TWT SP information allocated / scheduled by the BSS AP (i.e., the R-TWT SP information allocated by the BSS AP within its BSS).

[0312] For example, a non-AP EHT STA (i.e., a TXOP holder) with "dot11RestrictedTWTOptionImplemented" set to true may ensure that the TXOP ends before the start time of an active R-TWT SP, which may include an R-TWT SP scheduled / advertised by an AP corresponding to a BSSID transmitted by the associated AP or a multi-BSSID set to which the associated AP belongs and / or an R-TWT SP scheduled / advertised by an (other) AP included in the multi-AP set.

[0313] At this time, the broadcast TWT element including OBSS R-TWT SP information may include a broadcast TWT information (Info) subfield, and the broadcast TWT information subfield may include a restricted TWT schedule information subfield. The BSS AP may set the value of the restricted TWT schedule information subfield to a value indicating a full R-TWT schedule. At this time, the full R-TWT schedule indicated by the restricted TWT schedule information subfield may mean an R-TWT schedule that cannot accept a new membership request from an STA. Through this, the STA may be prevented from requesting membership based on a broadcast TWT ID including OBSS R-TWT SP information.

[0314] Additionally or alternatively, the BSS AP may set the value of the restricted TWT schedule information subfield to a value (e.g., 3) indicating that the corresponding R-TWT SP is an R-TWT SP scheduled by an AP corresponding to a nontransmitted BSSID. This allows an STA associated with an AP corresponding to the transmitted BSSID to recognize that the corresponding R-TWT SP (i.e., OBSS R-TWT SP) is not an R-TWT SP scheduled by an AP of the BSS to which it belongs.

[0315] According to the above-described method, an STA associated with a BSS that has been notified of an R-TWT SP can recognize the OBSS R-TWT SP information as information about an SP allocated by another R-TWT member (e.g., an AP of a BSS to which the STA itself does not belong).

[0316] Option 2: If the BSS AP does not advertise the OBSS R-TWT SP (i.e., the OBSS R-TWT SP scheduled by the neighboring AP) to the STA along with the information of the R-TWT SP it has allocated, the EHT STA supporting R-TWT can protect the OBSS R-TWT SP through the overlapping silence interval set by the BSS AP to include the OBSS R-TWT SP.

[0317] - UHR STAs that do not support R-TWT: The STAs can protect the OBSS R-TWT SPs through overlapping silence intervals set by the BSS AP to include the OBSS R-TWT SPs.

[0318] - UHR STA supporting only R-TWT: The behavior of UHR STA supporting only R-TWT may be determined depending on whether the BSS AP announces information about OBSS R-TWT SPs (i.e., R-TWT SPs scheduled / allocated by neighboring APs) together with information about R-TWT SPs allocated by the BSS AP.

[0319] As an example of the present disclosure, when a BSS AP notifies an OBSS R-TWT SP to a corresponding STA along with information on an R-TWT SP allocated by the BSS AP, the corresponding STA can protect the OBSS R-TWT SP by stopping a TXOP that was in progress before the OBSS R-TWT SP based on the TXOP and back-off procedure rules of the R-TWT SP.

[0320] The BSS AP may configure the OBSS R-TWT SP information in the same manner as the R-TWT SP information, so that the STA may not be able to distinguish between the OBSS R-TWT SP and the R-TWT SP. However, the BSS AP may configure the OBSS R-TWT SP information to correspond to the value of a specific broadcast TWT ID. In this case, the broadcast TWT ID corresponding to the OBSS R-TWT SP information may not overlap with the broadcast TWT ID corresponding to the R-TWT SP information allocated / scheduled by the BSS AP (i.e., the R-TWT SP information allocated by the BSS AP within its BSS).

[0321] At this time, the broadcast TWT element including OBSS R-TWT SP information may include a broadcast TWT information subfield, and the broadcast TWT information subfield may include a restricted TWT schedule information subfield. The BSS AP may set the value of the restricted TWT schedule information subfield to a value indicating a full R-TWT schedule. At this time, the full R-TWT schedule indicated by the restricted TWT schedule information subfield may mean an R-TWT schedule that cannot accept a new membership request from an STA. Through this, the STA may be prevented from requesting membership based on a broadcast TWT ID including OBSS R-TWT SP information.

[0322] As another example of the present disclosure, if a BSS AP does not notify the STA of information about an R-TWT SP allocated by a neighboring AP (i.e., an OBSS R-TWT SP) together with information about an R-TWT SP allocated by the BSS AP, the STA may protect the OBSS R-TWT SP through an overlapping silence interval set by the BSS AP to include the OBSS R-TWT SP.

[0323] Additionally or alternatively, the BSS AP may set the value of the restricted TWT schedule information subfield to a value (e.g., 3) indicating that the corresponding R-TWT SP is an R-TWT SP scheduled by an AP corresponding to a nontransmitted BSSID. This allows an STA associated with an AP corresponding to the transmitted BSSID to recognize that the corresponding R-TWT SP (i.e., OBSS R-TWT SP) is not an R-TWT SP scheduled by an AP of the BSS to which it belongs.

[0324] As another example of the present disclosure, if a BSS AP does not notify the STA of information about an R-TWT SP allocated by a neighboring AP (i.e., an OBSS R-TWT SP) together with information about an R-TWT SP allocated by the BSS AP, the STA may protect the OBSS R-TWT SP through an overlapping silence interval set by the BSS AP to include the OBSS R-TWT SP.

[0325] According to the above-described method, an STA associated with a BSS that has been notified of an R-TWT SP can recognize the OBSS R-TWT SP information as information about an SP allocated by another R-TWT member (e.g., an AP of a BSS to which the STA itself does not belong).

[0326] As an example of the present disclosure, assume that the STA requests membership based on a broadcast TWT ID corresponding to OBSS R-TWT SP information. In this case, the AP may reject the membership request based on the broadcast ID corresponding to the OBSS R-TWT SP.

[0327] - UHR STA supporting enhanced R-TWT: The STA can protect the OBSS R-TWT SP based on the TXOP and back-off procedure rules of the R-TWT SP.

[0328] As an example of the present disclosure, a UHR STA supporting enhanced R-TWT can protect an OBSS R-TWT SP via overlapping silence intervals. For example, as illustrated in FIG. 17, a UHR STA supporting enhanced R-TWT (e.g., STA 1) can terminate its TXOP before the start time of an OBSS R-TWT SP in order to protect an R-TWT SP (i.e., an OBSS R-TWT SP) scheduled by a neighboring AP (e.g., AP 2) that is announced by a BSS AP (i.e., an AP of a BSS to which STA 1 is associated) (e.g., AP 1). As another example, a UHR STA supporting enhanced R-TWT can protect an OBSS R-TWT SP via overlapping silence intervals.

[0329] Example 3

[0330] Example 3 relates to a procedure for not performing a protection operation for an OBSS R-TWT SP when the STA is not affected by the OBSS.

[0331] An STA may notify the BSS AP (i.e., the AP of the BSS to which the STA is associated) that it is not affected by the OBSS. For example, when the STA does not receive any other data or / and traffic (e.g., a beacon frame having a BSS color different from the BSS color of the BSS AP) after a certain period of time (e.g., SIFS, PIFS, AIFS[AC], EIFS, 1 / 4 beacon interval, 1 / 2 beacon interval, 3 / 4 beacon interval, etc.), the STA may notify the BSS AP that it has not received any other data or / and traffic.

[0332] That is, when the intensity (e.g., SINR, etc.) of the received or decoded signal (e.g., other data or / and traffic) does not exceed a detection threshold defined in the system (e.g., packet detection level or energy detection level), the STA can notify the BSS AP that it is not affected by the OBSS. Accordingly, the BSS AP can recognize that the STA is not affected by the OBSS.

[0333] Additionally or alternatively, if the STA overhears data related to the OBSS but the value related to the signaling power for transmitting and receiving the data is very small and / or the data transmission and reception of the BSS AP is not affected, the STA may inform the BSS AP that it is not affected by the OBSS.

[0334] When an STA notifies the BSS AP that it is not affected by the OBSS, the BSS AP and various types of STAs may perform operations for the OBSS R-TWT SP according to at least one of the following options.

[0335] Option 1: Option 1 relates to the behavior of Pre-EHT STAs not supporting R-TWT, EHT STAs not supporting R-TWT, EHT STAs supporting R-TWT, and UHR STAs not supporting R-TWT that protect OBSS R-TWT SPs through overlapping quiet intervals. A BSS AP that recognizes that the STAs are not affected by the OBSS does not transmit information related to the overlapping quiet intervals that overlap with the OBSS R-TWT SP to the STAs.

[0336] Option 2: Option 2 relates to the operation of a UHR STA that supports only R-TWT. For example, if the STA can recognize information about an OBSS R-TWT SP, the STA can notify the BSS AP that it is not affected by the OBSS and can continue to transmit and receive data without stopping its TXOP before the start time of the OBSS R-TWT SP. For another example, if the STA cannot recognize information about an OBSS R-TWT SP, the STA can notify the BSS AP that it is not affected by the OBSS and can continue to transmit and receive data. In this case, the BSS AP may not transmit information related to an overlapping silence interval that overlaps with the OBSS R-TWT SP to the STA.

[0337] Option 3: Option 3 relates to the behavior of a UHR STA supporting enhanced R-TWT. The STA may notify the BSS AP that it is not affected by OBSS and may continue to transmit and receive data without stopping its TXOP before the start time of the OBSS R-TWT SP. If the STA notifies the BSS AP that it is not affected by OBSS, the BSS AP may not transmit information about the overlapping silence interval that overlaps with the OBSS R-TWT SP to the STA.

[0338] Example 3-1

[0339] As described in Example 3, an STA associated with a BSS may notify the BSS AP of the receipt of other data / traffic (e.g., a beacon frame having a BSS color of another AP (e.g., a neighboring AP) other than the BSS color of the BSS AP) in at least one manner described below.

[0340] Method 1: An STA may transmit to a BSS AP a list of BSS color(s) included in PPDU(s) received during a certain period of time. The BSS AP may determine, based on the BSS color(s) included in the list of BSS color(s), whether the STA is affected by the BSS of an AP (e.g., a neighboring AP) that schedules an OBSS R-TWT SP.

[0341] For example, if i) only the BSS color of the BSS AP is included in the list of BSS color(s), or ii) the BSS color of an AP other than the BSS AP is included in the list of BSS color(s) but does not match the BSS color of the AP that scheduled the OBSS R-TWT SP to be announced, the STA may not perform protection operations for the OBSS R-TWT SP.

[0342] As another example, if the BSS color of an AP (e.g., a neighboring AP) that scheduled an OBSS R-TWT SP to be announced by the BSS AP is included in the list of BSS color(s), the STA may perform a protection operation for the OBSS R-TWT SP.

[0343] Method 2: A list of BSS colors including information on the BSS color(s) of the PPDU(s) received by the STA may be transmitted to the BSS AP via a specific frame (e.g., a TWT setup frame, etc.). For example, as illustrated in FIG. 18, elements related to the BSS color(s) (e.g., a BSS color list element) may be included in the TWT setup frame.

[0344] For example, a BSS color list element may include an element ID field, a length field, an element ID extension field, an amount of BSS color field, and a BSS color info field. For example, the amount of BSS color field may indicate the total number of BSS color subfields included in the BSS color info field. The BSS color info field may include information about BSS color(s) included in PPDUs received by the STA during a specific period. For example, the BSS color info field may include a BSS color subfield corresponding to each of one or more BSS colors. The BSS color subfield may include corresponding BSS color information. When the BSS color info field includes one or more BSS color information, one or more BSS color subfields corresponding to each of the one or more BSS color information may be configured consecutively. To match the octet length, the BSS color info field may include a reserved field.

[0345] Example 3-2

[0346] In one embodiment of the present disclosure, a BSS AP may assign SPs to STA(s) (e.g., one or more STAs associated with the BSS) based on OBSS R-TWT scheduling information. That is, the BSS AP may assign SPs to STA(s) affected by the OBSS (i.e., affected by OBSS R-TWT SPs scheduled by neighboring APs) such that they do not overlap with OBSS R-TWT SPs.

[0347] For example, AP 1 illustrated in FIG. 14 can set the SP of STA 1-2 so that the SP does not overlap with the OBSS R-TWT SP when scheduling it. As another example, AP 1 illustrated in FIG. 14 can set the SP of STA 1-1 so that the SP does not overlap with the (OBSS R-TWT) SP assigned to STA 2-4 when scheduling it.

[0348] Example 4

[0349] In one embodiment of the present disclosure, STA(s) coupled to a BSS may apply a spatial reuse scheme based on OBSS packet detection (PD) as well as the schemes illustrated in Embodiments 1 to 3. Specifically, the STA(s) and / or AP may perform a protection operation for an OBSS R-TWT SP using at least one of the options described below.

[0350] Option 4: When a BSS AP is included in a multi-AP environment, the OBSS PD value can be set based on the value announced by the master AP to the slave AP (e.g., the BSS AP). Accordingly, the BSS AP can determine whether the STA is affected by the OBSS based on the above setting. If the STA may be affected by data transmission and reception of a neighboring AP, the STA and / or the BSS AP can perform a protection operation for the OBSS R-TWT SP.

[0351] Option 5: An STA (i.e., an STA associated with a BSS) can set an OBSS PD value to apply when it receives OBSS data based on its transmit power. In a basic WLAN system (e.g., a WLAN system based on IEEE 802.11 ax or be), the lower the STA's transmit power value, the higher the OBSS PD value can be, and the higher the transmit power value, the lower the OBSS PD value can be.

[0352] Accordingly, if the OBSS PD value matching the transmission power of the STA is set higher than the reference OBSS PD value (i.e., OBSS PD_Ref) (i.e., if the transmission power is small enough not to affect OBSS transmission), the STA and / or BSS AP may not perform a protection operation for the OBSS R-TWT SP. However, if the OBSS PD value matching the transmission power of the STA is set lower than the reference OBSS PD value (i.e., OBSS PD_Ref) (i.e., if the transmission power is large enough to affect OBSS transmission), the STA and / or BSS AP may perform a protection operation for the OBSS R-TWT SP.

[0353] Option 6: An STA (i.e., an STA associated with a BSS) may set a threshold based on OBSS channel information obtained from neighboring APs and neighboring STAs. For example, if the strength of a received or decoded signal (e.g., a signal received from an OBSS) is less than the threshold, the STA and / or BSS AP may not perform a protection operation for the OBSS R-TWT SP. In another example, if the strength of a received or decoded signal (e.g., a signal received from an OBSS) is greater than the threshold, the STA and / or BSS AP may perform a protection operation for the OBSS R-TWT SP.

[0354] FIG. 19 is a diagram illustrating a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure. Some of the steps shown in FIG. 19 may be omitted depending on circumstances and / or settings. The transmitting device and the receiving STA may be APs and / or non-AP STAs.

[0355] A transmitting STA may obtain control information related to the aforementioned tone plan (or RU) (S105). The control information related to the tone plan may include the size and location of the RU, control information related to the RU, information about the frequency band in which the RU is included, information about the STA receiving the RU, and the like.

[0356] The transmitting STA may configure / generate a PPDU based on the acquired control information (S110). Configuring / generating a PPDU may mean configuring / generating each field of the PPDU. That is, the step of configuring / generating a PPDU may include a step of configuring EHT-SIG-A / B / C fields that include control information regarding a tone plan.

[0357] That is, the step of configuring / generating a PPDU may include a step of configuring a field including control information (e.g., N bitmap) indicating the size / position of the RU and / or a step of configuring a field including an identifier (e.g., AID) of an STA receiving the RU.

[0358] Additionally, the step of configuring / generating a PPDU may include a step of generating an STF / LTF sequence to be transmitted via a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0359] Additionally, the step of constructing / generating a PPDU may include a step of generating a data field (i.e., an MPDU) to be transmitted via a specific RU.

[0360] The transmitting STA can transmit the configured / generated PPDU to the receiving STA (S115).

[0361] Specifically, 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.

[0362] The receiving STA can decode the PPDU and obtain control information related to the tone-plan (or RU) (S120).

[0363] Specifically, the receiving STA can decode the L-SIG and EHT-SIG of the PPDU based on the L-STF / LTF, and obtain information included in the L-SIG and EHT SIG fields. Information about various tone plans (i.e., RUs) of the present disclosure can be included in the EHT-SIG (EHT-SIG-A / B / C, etc.), and the receiving STA can obtain information about the tone plan (i.e., RU) through the EHT-SIG.

[0364] The receiving STA can decode the remaining portion of the PPDU based on the information about the acquired tone plan (i.e., RU) (S125). For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about the tone plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.

[0365] Additionally, the receiving STA may perform a processing operation to forward the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data forwarded to the higher layer, the receiving STA may perform subsequent operations. Accordingly, the receiving STA can determine whether the transmitting STA is affected by the BSS of a neighboring AP through the received / decoded data.

[0366] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0367] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

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

[0369] The method proposed in this disclosure is described with a focus on examples applied to IEEE 802.11-based systems, but can be applied to various wireless LANs or wireless communication systems in addition to IEEE 802.11-based systems.

Claims

1. A method performed by a station (STA) in a wireless LAN system, the method comprising: A step of transmitting information related to at least one basic service set (BSS) color to a first access point (AP); and A step of receiving, from the first AP, information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP; and A method comprising the step of performing a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in the at least one BSS color.

2. In paragraph 1, A method wherein the protection operation of the second R-TWT SP includes an operation of terminating a TXOP (transmission opportunity) of the STA before the start time of the second R-TWT SP.

3. In paragraph 1, Information about at least one BSS color is included in an element related to the BSS color, A method in which an element related to the above BSS color is transmitted from the STA to the first AP via a TWT setup frame.

4. In paragraph 3, A method wherein the element related to the BSS color comprises a subfield indicating the number of the at least one BSS color and at least one BSS color subfield indicating each of the at least one BSS color.

5. In paragraph 1, A method wherein the at least one BSS color is obtained based on at least one physical layer protocol data unit (PPDU) received from at least one AP including the second AP during a predefined time period.

6. In paragraph 1, A method in which data transmission and reception is performed by the STA within a TXOP regardless of the second R-TWT SP based on the BSS color of the second AP not being included in the at least one BSS color.

7. In paragraph 1, A method in which information related to an overlapping quiet interval overlapping with the second R-TWT SP is not transmitted from the first AP to the STA based on the BSS color of the second AP not being included in the at least one BSS color.

8. In paragraph 1, A method wherein the protection operation of the second R-TWT SP includes an operation according to an overlapping silence interval set by the first AP to overlap with the second R-TWT SP.

9. In paragraph 1, A method in which information related to the first R-TWT SP and information related to the second R-TWT SP are transmitted to the STA via a beacon frame.

10. In paragraph 1, The first R-TWT SP is allocated by the first AP based on information related to the second R-TWT SP, A method wherein the first R-TWT SP and the second R-TWT SP do not overlap.

11. In paragraph 1, Based on the PD (packet detection) value related to the BSS of the second AP corresponding to the transmission power of the STA being set higher than the first threshold, the protection operation of the second R-TWT SP is not performed by the STA, A method in which a protection operation of the second R-TWT SP is performed by the STA based on a PD value related to the BSS of the second AP corresponding to the transmission power of the STA being set lower than the first threshold value.

12. In paragraph 1, Based on the strength of a signal received from the second AP or at least one of the other STAs included in the BSS of the second AP being less than a second threshold, the protection operation of the second R-TWT SP is not performed by the STA, A method in which a protection operation of the second R-TWT SP is performed by the STA based on the strength of a signal received from the second AP or at least one of other STAs included in the BSS of the second AP being greater than the second threshold.

13. In paragraph 1, A method in which the STA is associated with the BSS of the first AP.

14. In a station (STA) operating in a wireless LAN system, the STA: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting information related to at least one basic service set (BSS) color to a first access point (AP) via the one or more transceivers; and Receiving information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP from the first AP through the one or more transceivers; and A STA configured to perform a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in the at least one BSS color.

15. A method performed by a first access point (AP) in a wireless LAN system, the method comprising: A step of receiving information related to at least one basic service set (BSS) color from a station (STA); and A step of transmitting information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP to the STA, A method in which a protection operation of the second R-TWT SP is performed based on the BSS color of the second AP being included in at least one BSS color.

16. In a first access point (AP) operating in a wireless LAN system, the first AP: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving information related to at least one basic service set (BSS) color from a station (STA) through one or more transceivers; and Information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP are set to be transmitted to the STA through the one or more transceivers, A first AP, wherein a protection operation of the second R-TWT SP is performed based on the BSS color of the second AP being included in the at least one BSS color.

17. A processing device configured to control a first station (STA) operating in a wireless LAN system, wherein the processing device: one or more processors; and One or more computer memories operatively connected to said one or more processors and storing instructions that perform operations based on being executed by said one or more processors, The above actions are: An operation of transmitting information related to at least one basic service set (BSS) color to a first access point (AP); and An operation of receiving, from the first AP, information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP; and A processing device comprising an operation for performing a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in the at least one BSS color.

18. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, so that the device operating in the wireless LAN system: Transmitting information related to at least one basic service set (BSS) color to a first access point (AP); and Receive information related to a first restricted target wake time (R-TWT) service period (SP) scheduled by the first AP and information related to a second R-TWT SP scheduled by the second AP from the first AP; and A computer-readable medium controlled to perform a protection operation of the second R-TWT SP based on the BSS color of the second AP being included in the at least one BSS color.

Citation Information

Patent Citations

  • Communication device, communication method, and program

    EP4152879A1

  • Nanofiber sheet for healing tear of rotator cuff containing recombinant parathyroid hormone and method for manufacturing the same

    KR1020240012269A

  • Coordinated scheduling and signaling of restricted target wake time (r-TWT) service periods

    US20230140312A1

Cited By

  • Wireless communication method, non-AP STA, and AP

    US12777523B2