Method and apparatus for reducing hidden node interference in wireless LAN system
By having STAs monitor and report inter-BSS PPDU transmissions to their APs, the method adjusts scheduling to prevent interference, enhancing network performance by addressing hidden node issues in wireless LAN systems.
Patent Information
- Application Number
- PCT/KR2024/006402
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
Wireless LAN systems face interference issues with hidden nodes, where STAs in overlapping BSSs can overhear each other's transmissions, leading to collisions and reduced network performance.
A method where STAs monitor inter-BSS PPDU transmissions and report reception or non-reception to their associated APs, allowing the APs to adjust scheduling information to prevent interference by restricting uplink transmissions or setting silence intervals, thereby protecting against hidden node interference.
This approach effectively reduces hidden node interference by ensuring that STAs do not transmit data that would interfere with other BSSs, improving network performance and reliability in multi-BSS environments.
Smart Images

Figure KR2024006402_21112024_PF_FP_ABST
Abstract
Description
Method and device for reducing hidden node interference in a wireless LAN system
[0001] The present disclosure relates to a method and device for transmitting or receiving for reducing interference to a hidden node in a wireless local area network (WLAN) 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 transmitting or receiving to reduce interference to a hidden node in a wireless LAN system.
[0005] 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 will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.
[0006] A method performed by a first station (STA) in a wireless LAN system according to one aspect of the present disclosure may include: monitoring, by the first STA associated with a first access point (AP) of a first basic service set (BSS), an inter-BSS physical layer protocol data unit (PPDU) transmitted from a second STA belonging to a second BSS or transmitted to the second STA; transmitting, to the first AP, report information including information indicating that the inter-BSS PPDU has been received or not received; and receiving, from the first AP, scheduling information for the first STA based on the report information.
[0007] A method performed by a first access point (AP) in a wireless LAN system according to an additional aspect of the present disclosure may include the steps of: receiving, from a first station (STA) associated with the first AP of a first basic service set (BSS), report information including information indicating that an inter-BSS physical layer protocol data unit (PPDU) transmitted from a second STA belonging to a second BSS or transmitted to the second STA is received or not received by the first STA; and transmitting, to the first STA, scheduling information for the first STA based on the report information.
[0008] According to the present disclosure, a method and device for transmitting or receiving for reducing interference to a hidden node in a wireless LAN system can be provided.
[0009] 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.
[0010] 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.
[0011] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
[0012] FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.
[0013] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.
[0014] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.
[0015] FIG. 5 is a diagram for explaining a CSMA / CA-based frame transmission operation to which the present disclosure can be applied.
[0016] 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.
[0017] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.
[0018] FIG. 8 is a diagram for explaining various transmission and reception techniques in a MAP environment to which the present disclosure can be applied.
[0019] FIG. 9 is a diagram illustrating an example of an individual TWT operation to which the present disclosure can be applied.
[0020] FIG. 10 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.
[0021] FIG. 11 is a diagram showing an exemplary format of a silence element and an exemplary format of a silence channel element to which the present disclosure can be applied.
[0022] FIG. 12 is a diagram illustrating STAs in an OBSS to which the present disclosure can be applied.
[0023] Figure 13 illustrates an example of OBSS R-TWT SP protection to which the present disclosure can be applied.
[0024] FIG. 14 and FIG. 15 are drawings for explaining examples of hidden nodes according to the present disclosure.
[0025] FIG. 16 is a diagram for explaining the operation of an STA according to the present disclosure.
[0026] FIG. 17 is a drawing for explaining the operation of an AP according to the present disclosure.
[0027] 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.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] Below, technical features to which examples of the present disclosure can be applied are described.
[0034] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
[0035] 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.
[0036] 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.
[0037] 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.
[0038] 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).
[0039] 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.
[0040] 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.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] FIG. 2 is a diagram showing an exemplary structure of a wireless LAN system to which the present disclosure can be applied.
[0048] 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.
[0049] 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.
[0050] 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).
[0051] 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.
[0052] 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.
[0053] 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).
[0054] 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.
[0055] Data transmitted from one of the STA(s) associated with an AP to the STA address of that AP is always received on an uncontrolled port and can be processed by an IEEE 802.1X port access entity. In addition, if the controlled port is authenticated, the transmitted data (or frame) can be forwarded to the DS.
[0056] In addition to the structure of the DS described above, an extended service set (ESS) may be established to provide wider coverage.
[0057] 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.
[0058] 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.
[0059] FIG. 3 is a diagram for explaining a link setup process to which the present disclosure can be applied.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] 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.
[0072] FIG. 4 is a diagram for explaining a backoff process to which the present disclosure can be applied.
[0073] 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.
[0074] 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).
[0075] 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, ...).
[0076] 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.
[0077] 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.
[0078] 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.
[0079] 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.
[0080] FIG. 5 is a diagram for explaining a CSMA / CA-based frame transmission operation to which the present disclosure can be applied.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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.
[0097] 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).
[0098] FIG. 7 is a diagram illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure can be applied.
[0099] 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)).
[0100] 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).
[0101] 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)).
[0102] 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.
[0103] 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.
[0104] 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.
[0105] 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.
[0106] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated to allow legacy STAs to attempt demodulation and decoding, and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated to allow STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in the fields, and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.
[0107] 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.
[0108] 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.
[0109] 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.
[0110] 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.
[0111] 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.
[0112] 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.
[0113] 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.
[0114] 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.).
[0115] 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.
[0116] 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.
[0117] 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.
[0118] 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.).
[0119] 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.
[0120] 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.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] 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.
[0125] RUs of different sizes can be defined, such as 26-ton RU, 52-ton RU, 106-ton RU, 242-ton RU, 484-ton RU, 996-ton RU, 2X996-ton RU, 4X996-ton RU, etc. A multiple RU (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.
[0126] 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.
[0127] 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.
[0128] Multi-Access Point (MAP) operation
[0129] Below, examples of the present disclosure for multi-access point (MAP) operation are described.
[0130] MAP operation can be defined as an operation between a master AP (or sharing AP) and a slave AP (or shared AP).
[0131] The master AP initiates and controls MAP operations for transmission and reception between multiple APs. It groups slave APs and manages links with them to enable information sharing. The master AP manages information about the BSS comprised of the slave APs and the STAs associated with that BSS.
[0132] Slave APs can associate with a master AP and share control information, management information, and data traffic. Slave APs perform the same basic functions as APs, establishing a base station service (BSS) in a wireless LAN.
[0133] In MAP operation, an STA can associate with a slave AP or a master AP and form a BSS.
[0134] In a MAP environment, the master AP and slave APs can directly transmit and receive with each other. The master AP and STA may not be able to directly transmit and receive with each other. A slave AP (e.g., a slave AP associated with an STA) can directly transmit and receive with the STA. One of the slave APs can become the master AP.
[0135] MAP operation is a technique in which one or more APs transmit and receive information to one or more STAs. For example, coordinated-time division multiple access (C-TDMA), which divides allocations between APs along the time axis, coordinated-orthogonal frequency division multiple access (C-OFDMA), which divides allocations along the frequency axis, and coordinated-spatial reuse (C-SR) techniques that utilize spatial reuse can be applied for MAP operation. Alternatively, coordinated beamforming (C-BF) or joint beamforming techniques, which cooperatively perform simultaneous transmission and reception, can also be applied to MAP operation.
[0136] FIG. 8 is a diagram for explaining various transmission and reception techniques in a MAP environment to which the present disclosure can be applied.
[0137] As in the conventional method, when a BSS AP transmits to a BSS STA, this can be referred to as STX (single transmission). STX suffers from the problem of reduced transmission and reception performance for users / STAs located at the cell edge due to interference with neighboring APs. For example, as shown in Figure 8(a), if AP1 and AP2 transmit to STA1 and STA2, respectively, at the same time and within the same frequency bandwidth, a collision may occur on the wireless medium.
[0138] In the MAP technique, performance can be improved by reducing inter-symbol interference (ISI) through cooperation between neighboring APs, or by performing joint transmissions. For example, in the C-OFDMA method of Fig. 8(b), interference can be avoided by simultaneously transmitting to STA1 in the first bandwidth and transmitting to STA2 in the second bandwidth. The example of Fig. 8(c) shows a cooperative beamforming or nulling technique in which AP1 nulls the interference to AP2 and / or STA2 while transmitting to STA1, and AP2 nulls the interference to AP1 and / or STA1 while transmitting to STA2. Fig. 8(d) shows an AP selection method in which an AP with a good channel condition among neighboring APs performs transmission. Joint transmission (JTX) or joint reception (JRX) may be applied, in which multiple APs cooperate to transmit or receive simultaneously, as in the example of Fig. 8(e), and further, joint MU-MIMO may be supported.
[0139] In the examples of this disclosure, multi-AP operation is assumed to be performed as follows.
[0140] Step 1: Allocate resource areas to each AP through a trigger frame from the master AP (i.e., AP-to-AP trigger frame, or master trigger frame).
[0141] Step 2: Each AP performs DL (i.e., from AP to STA) data transmission in the resource area allocated to it, or transmits a trigger frame (i.e., AP-to-STA trigger frame) for UL (i.e., from STA to AP) data transmission in the resource area allocated to it.
[0142] Step 3: STA sends a response to DL data or sends UL data (e.g., TB PPDU)
[0143] If the resources distributed between APs are frequency resources, it may correspond to the C-OFDMA method, if it is time resources, it may correspond to the C-TDMA technique, and if it is space resources (or beams), it may correspond to the CBF method. In the examples described below, it is assumed that the C-OFDMA technique, i.e., multi-AP operation is performed using resources distinguished in the frequency domain, is representative. However, the scope of the present disclosure is not limited thereto, and may additionally or alternatively include multi-AP operation using resources distinguished in other domains (e.g., time domain and / or space domain).
[0144] target wake time (TWT)
[0145] Below, we explain TWT (target wake time).
[0146] TWT is a power saving technology that can improve the energy efficiency of non-AP STAs by defining a service period (SP) between an AP and non-AP STAs and sharing information about the SP to reduce contention of the medium. In the TWT setup phase, an STA that performs requests / suggestions / demands, etc., can be called a TWT requesting STA. In addition, an AP that responds to the request with an acceptance / rejection, etc., can be called a TWT responding STA. The setup phase can include a process of determining / defining a TWT request from an STA to the 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.
[0147] FIG. 9 is a diagram illustrating an example of an individual TWT operation to which the present disclosure can be applied.
[0148] Individual TWT is a mechanism in which an AP and a non-AP STA negotiate the awake / doze status of a non-AP STA by sending and receiving TWT request / response frames, and then exchange data. In the example of Fig. 9, the AP and STA1 can form a trigger-enabled TWT agreement through a TWT request frame and a TWT response frame. Here, the method used by STA1 is a solicited TWT method, in which STA1 transmits a TWT request frame to the AP, and STA1 receives information for TWT operation from the AP through a TWT response frame. On the other hand, STA2, which performs the unsolicited TWT method, can receive information about the trigger-enabled TWT agreement setup from the AP through the unsolicited TWT response. Specifically, STA2 can calculate the next TWT by adding a specific number to 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, STA1 can inform the AP of its awake state by transmitting a PS-Poll frame. Additionally, STA2 can inform the AP of its activated state by transmitting a QoS Null frame. Here, the data frames transmitted by STA1 and STA2 can be frames in the TB PPDU format. The AP, which has checked the status of STA1 and STA2, can transmit DL MU PPDU to the activated STAs.When the corresponding TWT SP expires, STA1 and STA2 can enter doze state.
[0149] FIG. 10 is a diagram illustrating an example of a broadcast TWT operation to which the present disclosure can be applied.
[0150] Broadcast TWT is a TWT in which a non-AP STA (or TWT scheduling STA) obtains information such as 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 negotiation operation for TBTT may be performed. Based on this, the AP can define a frame to include TWT scheduling information through a beacon frame. In Fig. 10, STA1 performs a requested TWT operation, and STA2 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 itself. This may be the same as the process of an individual TWT. In broadcast TWT, a trigger-enabled TWT SP including a beacon frame may be repeated multiple times at a regular cycle.
[0151] Transmission of TWT information can be accomplished through a TWT information frame and a TWT information element.
[0152] With the recent explosion in wired and wireless traffic, latency-sensitive traffic has also increased significantly. Latency-sensitive traffic includes real-time audio / video transmission, and the proliferation of multimedia devices has increased the need to support this traffic in wireless environments. However, supporting latency-sensitive traffic in wireless environments requires more considerations than in wired environments. This is because wireless environments have lower transmission speeds and must also consider interference from surrounding environments. In particular, in WLAN systems, multiple STAs must compete equally for medium access in the Industry-Science-Medical (ISM) band, making it relatively more difficult to support latency-sensitive traffic compared to cellular communication networks, which rely on centralized radio resource scheduling. This disclosure describes a novel approach for supporting latency-sensitive traffic in WLAN systems.
[0153] In the present disclosure, latency may refer to latency defined in the IEEE 802.11 series standards. For example, it may refer to the time from when a frame to be transmitted enters the queue of the MAC layer of the transmitting STA, until the transmitting STA successfully completes transmission in the PHY layer, and the transmitting STA receives an ACK / block ACK, etc. from the receiving STA, and the corresponding frame is deleted from the MAC layer queue of the transmitting STA. In addition, in the present disclosure, a non-AP STA that supports transmission of latency-sensitive data may be referred to as a low latency STA. In addition, data other than latency-sensitive data may be referred to as regular data.
[0154] Restricted TWT (r-TWT) can support securing data transmission possibility for low-latency STAs transmitting latency-sensitive data preferentially over other STAs by having the AP set a special broadcast TWT for the low-latency STAs. The STAs can establish membership in one or more r-TWT schedules with respect to the AP. Here, the r-TWT agreement can be established by the same process as the broadcast TWT agreement, and the broadcast TWT element for this can be defined to include an r-TWT parameter set field. For example, the r-TWT parameter set can refer to a specific broadcast TWT parameter set field that is distinct from other broadcast TWT parameter set fields. That is, the r-TWT parameter set field can correspond to a special case of the broadcast TWT parameter set field. In addition, the AP can announce an r-TWT SP.
[0155] Basically, if another STA supporting r-TWT operation is a TXOP holder, the TXOP must end before the start time of the r-TWT SP advertised by the associated AP. Accordingly, the STA related to the r-TWT (i.e., the low-latency STA) can transmit and receive traffic with priority over the other STAs within the r-TWT SP.
[0156] In the present disclosure, a low-latency STA associated with a specific r-TWT, as described above, is referred to as a member r-TWT scheduled STA, and other STAs are referred to as non-member STAs. A non-member STA may be an STA that has the capability to support r-TWT operation but is not a member of any r-TWT, or that supports r-TWT operation but is a member of another r-TWT, or that does not have the capability to support r-TWT operation.
[0157] An STA (e.g., a low-latency STA) that supports limited SP (or r-TWT SP) operation of broadcast TWT can inform the AP that it needs to transmit latency-sensitive data based on r-TWT operation. If the AP supports r-TWT operation / mode, the AP can transmit a frame containing scheduling information of TWTs requested by each STA to the low-latency STA and other STA(s). For example, in order to perform operation for r-TWT, non-AP STAs can obtain r-TWT related information from the AP through a beacon frame, a probe response frame, a (re)association response frame, or other frames in an undefined format (e.g., frames for broadcast, advertisement, or announcement purposes).
[0158] According to the restricted TWT operation, a separate TXOP (i.e., to which access of other STAs is restricted) can be secured within the r-TWT SP by using a NAV such as (MU) RTS / CTS or CTS-to-self, or a quiet interval. Before a specific r-TWT SP starts, if there is a TXOP of another STA (i.e., a non-member STA) other than the STA having the membership for the specific r-TWT schedule, it must be stopped. And the TXOP of the other STA (i.e., the non-member STA) can be additionally performed after the specific r-TWT SP ends.
[0159] Silent interval
[0160] A silent interval can be indicated by a quiet element or a quiet channel element. Essentially, an STA receiving a silent element or a silent channel element may not transmit (or access the channel) on the corresponding channel during the indicated silent interval.
[0161] FIG. 11 is a diagram showing an exemplary format of a silence element and an exemplary format of a silence channel element to which the present disclosure can be applied.
[0162] Fig. 11(a) shows an exemplary format of a silence element.
[0163] A silence element can define an interval during which no transmission is performed on the current channel. This interval can be used to facilitate channel measurements (or channel tests) without interference from other STAs within the BSS.
[0164] The Element ID field may have a value corresponding to the silent element (e.g., 40). The Length field may have a value corresponding to the length of the following fields (e.g., 6 octets).
[0165] The quiet count field may have a value corresponding to the number of TBTTs until the beacon interval at which the next silent interval begins. A value of 0 in this field may be reserved.
[0166] The quiet period field may have a value corresponding to the number of beacon intervals between the start points of regularly scheduled silent intervals defined by the corresponding silence element. A value of 0 in the quiet period field may indicate that no periodic silent intervals are defined.
[0167] The quiet duration field can have a value expressing the duration of the silent interval in time units (TUs). For example, 1 TU can correspond to 1024 microseconds (us).
[0168] The quiet offset field may have a value representing the offset in TU units from the TBTT specified by the silence count field to the start of the silence interval. The value of the quiet offset field may be less than one beacon interval.
[0169] Silence elements can be included in beacon frames, probe response frames, etc. For example, an AP can schedule a silence interval by transmitting a beacon / probe response frame containing a silence element. Multiple independent silence intervals can also be scheduled. An STA can set a NAV (on the silent channel) for the duration of a silence interval.
[0170] Fig. 11(b) shows an exemplary format of a silent channel element.
[0171] The Silence Channel element may be used to indicate that a secondary channel (e.g., a secondary 80MHz channel of a VHT BSS) will be silenced during the silence interval, and may also be used in an infrastructure BSS to indicate that a primary channel (e.g., a primary 80MHz channel of a VHT BSS) may be used during the silence interval. The silence interval may be established using the Silence element, or in an infrastructure BSS, using the Silence Channel element when the value of the AP Silence Mode field is 1.
[0172] Silent channel elements may be included in beacon frames, probe response frames, etc.
[0173] The AP Quiet Mode field can specify the STA behavior in the infrastructure BSS during the quiet interval. If communication to the AP is allowed within the primary 80MHz channel (during the quiet interval), the AP Quiet Mode field can have a value of 1. Otherwise, the AP Quiet Mode field can have a value of 0.
[0174] If the value of the AP Silence Mode field is 1, the Silence Channel element may include a Silence Count field, a Silence Period field, a Silence Duration field, and a Silence Offset field. Otherwise, these fields may not be included in the Silence Channel element.
[0175] The silence count field, silence period field, silence duration field, and silence offset field in the silence channel element are the same as the corresponding fields in the silence element field, so redundant descriptions are omitted.
[0176] Next, silent intervals may be scheduled relative to r-TWT SPs. For example, an AP supporting r-TWT (e.g., an EHT AP or an AP supporting an EHT successor (e.g., UHR) standard) may schedule a silent interval that overlaps the r-TWT SP. This may be referred to as an overlapping silent interval. If scheduled, the overlapping silent interval may be required to have a duration of 1 TU and to start at the same time as the start of the corresponding r-TWT SP.
[0177] Overlapping silence intervals can be established by including one or more silence elements in beacon frames, probe response frames, etc. transmitted by an AP supporting r-TWT (e.g., an EHT AP).
[0178] Non-AP EHT STAs may behave as if no overlapping silence intervals exist.
[0179] Alternatively, the AP may use silent intervals for channel measurement / testing by managing or avoiding overlapping scheduled silent intervals with r-TWT SPs.
[0180] OBSS R-TWT scheduling
[0181] FIG. 12 is a diagram illustrating STAs in an OBSS to which the present disclosure can be applied.
[0182] In a multi-BSS environment, when an STA is located within a range where it can receive beacon frames transmitted from multiple APs, an overlapping BSS (OBSS) range may be formed. For example, as in the example of FIG. 12, the range in which AP1 can signal (e.g., the range corresponding to BSS1) and the range in which AP2 can signal (e.g., the range corresponding to BSS2) may overlap, and the STA at that location may receive beacon frames not only from the AP with which it has formed an association, but also from APs with which it has not formed an association. For example, STA1-2 may receive a beacon frame from AP1 with which it has formed an association, and may also receive (i.e., overhear) a beacon frame from AP2 with which it has not formed an association. For example, STA2-4 can receive a beacon frame from AP2, which it is associated with, and can also receive (i.e., overhear) a beacon frame from AP1, which it is not associated with. For example, AP1 and AP2 may be slave APs (or shared APs) belonging to a MAP having the same master AP (or shared AP).
[0183] A beacon frame may contain restricted-TWT (R-TWT) scheduling information that an AP assigns to STAs associated with it, and STAs receiving the R-TWT scheduling information are required to protect R-TWT SPs of which they are not a member (e.g., terminating a TXOP of the STA if it is in progress before the start time of the R-TWT SP, as described above). That is, an STA receiving a beacon frame including R-TWT scheduling information may mean that it is in a position to protect the corresponding R-TWT SP. On the other hand, it is not yet defined whether an STA should protect the corresponding R-TWT SP or transmit / receive low-latency traffic / data during the corresponding R-TWT SP when it receives R-TWT scheduling information advertised by an AP to which it is not associated (or a neighboring AP). The present disclosure describes the operation of an STA (e.g., STA1-2) based on R-TWT scheduling information of an unassociated (or neighboring) AP (e.g., AP2). In the following description, an R-TWT SP scheduled by another AP (e.g., an unassociated AP or a neighboring AP) is referred to as an OBSS R-TWT SP to distinguish it from an R-TWT SP scheduled by an associated AP. The scope of the present disclosure is not limited by the name OBSS R-TWT.
[0184] In the present disclosure, one of the two APs associated with the OBSS can obtain R-TWT (i.e., OBSS R-TWT) scheduling information of the other AP by one or more of the following methods.
[0185] For example, between APs capable of direct data transmission and reception, either wired or wireless, an AP may transmit its R-TWT scheduling information to one or more other APs, or receive R-TWT scheduling information from one or more other APs. This may occur, for example, when the APs are not located within the same ESS.
[0186] Additionally or alternatively, R-TWT scheduling information can be shared between APs that cannot directly transmit or receive data through a third-party management entity. For example, this may be the case when the APs are located within the same ESS and / or when the APs are slave APs (or shared APs) with the same master AP (or shared AP). For example, the master AP may act as the third-party management entity.
[0187] Additionally or alternatively, an STA that overhears a beacon frame from another AP may forward relevant information to its associated AP. For example, the STA may forward information contained in the overheard beacon frame to the associated AP, or may decode the overheard beacon frame and forward OBSS R-TWT-related information to the associated AP.
[0188] The following different STA types may be considered in relation to R-TWT and / or OBSS R-TWT:
[0189] Depending on the STA type, it may support a wireless LAN technology for which the R-TWT capability itself is not defined, or it may support a wireless LAN technology for which the R-TWT capability is defined. For example, a pre-EHT STA type that does not support the EHT technology may be referred to as a legacy STA type, and such a type of STA may not support the R-TWT operation itself. For example, an EHT STA type that supports the EHT technology for which the R-TWT capability is defined may support the R-TWT operation depending on whether it has the R-TWT capability. Even an EHT STA type that has the R-TWT capability may not support the OBSS R-TWT operation itself.
[0190] For example, an STA (e.g., a UHR STA) supporting a new wireless LAN technology (e.g., a UHR technology) for which an OBSS R-TWT (or enhanced R-TWT) capability is defined may support OBSS R-TWT operation depending on whether it has the OBSS R-TWT (or enhanced R-TWT) capability. For example, there may be a UHR STA type that does not have the R-TWT capability (and the OBSS R-TWT capability), a UHR STA type that only has the R-TWT capability (without any limitation on whether such a type of STA can interpret OBSS R-TWT (or enhanced R-TWT) related information), and a UHR STA type that has the OBSS R-TWT (or enhanced R-TWT) capability (assuming that such a type of STA can perform OBSS R-TWT SP protection operation).
[0191] As a method for protecting the OBSS R-TWT SP, similar to the method for protecting the existing R-TWT SP, overlapping silence intervals, TXOP for R-TWT SP, and backoff procedure rules can be extended and applied. For example, an ongoing TXOP before the start of the OBSS R-TWT SP can be terminated. For example, if there is not enough time to complete frame exchange before the start of the OBSS R-TWT SP, the STA can defer transmission by selecting a random backoff count. For example, a silence interval overlapping with the OBSS R-TWT SP can be set.
[0192] Depending on the STA type described above, the OBSS R-TWT SP protection operation can be applied as follows.
[0193] For pre-EHT STA types or legacy STA types that do not support R-TWT, OBSS R-TWT SPs can be protected through overlapping silence intervals.
[0194] For EHT STA types that do not support R-TWT, OBSS R-TWT SPs can be protected through overlapping silence intervals.
[0195] In case of an EHT STA type supporting R-TWT or a UHR STA type supporting only R-TWT, when an AP (i.e., a BSS AP) notifies the associated STA of information about an R-TWT SP (i.e., an OBSS R-TWT SP) allocated by another AP together with information about an R-TWT SP allocated by the AP, the OBSS R-TWT SP can be protected by terminating the ongoing TXOP before the OBSS R-TWT SP starts based on the TXOP and backoff procedure rules for the R-TWT SP. The associated AP can configure the OBSS R-TWT SP information in the same manner as the R-TWT SP information allocated by the BSS AP. An STA receiving such an R-TWT SP may not distinguish between the OBSS R-TWT SP and the R-TWT SP. Here, the broadcast TWT ID corresponding to the R-TWT SP allocated by the associated AP and the broadcast TWT ID corresponding to the OBSS R-TWT SP may not overlap. Accordingly, the combined STAs that have been notified of multiple R-TWT information including OBSS R-TWT information can interpret the OBSS R-TWT SP as an R-TWT SP allocated to another R-TWT member to which they do not belong.
[0196] For an EHT STA type that supports R-TWT or a UHR STA type that only supports R-TWT, if the AP (i.e., BSS AP) does not notify the associated STA of information about the R-TWT SP (i.e., OBSS R-TWT SP) allocated by another AP together with information about the R-TWT SP allocated by itself, the OBSS R-TWT SP can be protected through overlapping silence intervals.
[0197] For UHR STA types that do not support R-TWT, OBSS R-TWT SPs can be protected through overlapping silence intervals.
[0198] For UHR STA types that support enhanced R-TWT, OBSS R-TWT SPs can be protected based on TXOP and backoff procedure rules for R-TWT SPs. A specific example of this is described with reference to FIG. 13.
[0199] Figure 13 illustrates an example of OBSS R-TWT SP protection to which the present disclosure can be applied.
[0200] AP1 and AP2 can share each other's R-TWT SP information. Accordingly, AP1 can announce information about the R-TWT SP(s) of BSS1 that it assigns and information about the R-TWT SP(s) of BSS2 that it assigns through a beacon frame. In addition, AP2 can announce information about the R-TWT SP(s) of BSS2 that it assigns and information about the R-TWT SP(s) of BSS1 that it assigns through a beacon frame.
[0201] STA1 may be a UHR STA type that is coupled with AP1 and supports enhanced R-TWT. To protect an OBSS R-TWT SP announced by AP1 (e.g., an R-TWT SP of BSS2), STA1 may terminate its TXOP (earlier than the originally acquired TXOP length) before the OBSS R-TWT SP starts. Additionally or alternatively, for a UHR STA type that supports enhanced R-TWT, the OBSS R-TWT SP may be protected via overlapping silence intervals.
[0202] During OBSS R-TWT SP, AP2 transmits trigger information to STA2 associated with it, and in response, STA2 can transmit uplink data.
[0203] Hidden node interference reduction
[0204] FIG. 14 and FIG. 15 are drawings for explaining examples of hidden nodes according to the present disclosure.
[0205] As in the example of Fig. 14, there is no OBSS area where BSS1 and BSS2 overlap (i.e., an area where beacon frames from other APs can be overheard), or even if an OBSS area exists as in the example of Fig. 15, overhearing of beacon frames from other APs may not be possible depending on the location of the STA.
[0206] In the examples of FIGS. 14 and 15, STA1-2 corresponds to a hidden node for AP2, and STA2-4 corresponds to a hidden node for AP1. That is, STA1-2 may not receive a beacon frame from AP2, and STA2-4 may not receive a beacon frame from AP1. In this case, a PPDU transmitted from STA1-2 or a PPDU transmitted from another STA (e.g., AP1 or another non-AP STA within BSS1) to STA1-2 may be overheard by STA2-4. Similarly, a PPDU transmitted from STA2-4 or a PPDU transmitted from another STA (e.g., AP2 or another non-AP STA within BSS2) to STA2-4 may be overheard by STA1-2. That is, PPDUs transmitted to / from STA1-2 and STA2-4 may cause interference to each other.
[0207] This disclosure describes various examples of reducing interference to hidden nodes in situations where STAs belonging to different BSSs but in mutually overhearing locations are hidden nodes to the APs of each BSS. Interference reduction to hidden nodes may include OBSS R-TWT SP protection.
[0208] FIG. 16 is a diagram for explaining the operation of an STA according to the present disclosure.
[0209] In step S1610, the first STA can monitor a PPDU (hereinafter, inter-BSS PPDU) related to a second STA belonging to the second BSS.
[0210] The first STA may correspond to an STA associated with the first AP of the first BSS. Additionally, a beacon frame transmitted by the second AP of the second BSS may not be received / detected by the first STA.
[0211] A PPDU associated with a second STA may correspond to a PPDU transmitted from or to the second STA. The second STA may correspond to an STA associated with a second AP of the second BSS.
[0212] Inter-BSS PPDU monitoring may include determining whether a received or detected PPDU corresponds to an inter-BSS PPDU. That is, the first STA may determine whether the received / detected PPDU is a PPDU associated with itself or a PPDU associated with another STA based on various information included in the received / detected PPDU (e.g., BSS color information, source address information, destination address information, UL / DL direction information, etc.).
[0213] For example, if a PPDU transmitted by a second STA to one or more other entities belonging to a second BSS (e.g., a second AP and / or other non-AP STAs within the second BSS) is received / detected by the first STA, it may be determined that an inter-BSS PPDU has been received / detected. For example, if a PPDU transmitted from another entity belonging to the second BSS (e.g., a second AP and / or other non-AP STAs within the second BSS) to the second STA is received / detected by the first STA, it may be determined that an inter-BSS PPDU has been received / detected.
[0214] In step S1620, the first STA may transmit report information including information indicating whether an inter-BSS PPDU has been received or not to the first AP.
[0215] For example, reporting information may be transmitted from the first STA to the first AP based on a request from the first AP. For example, the request (for transmitting reporting information) from the first AP may be transmitted periodically to the first STA. In response to such a request, reporting information may be transmitted periodically from the first STA to the first AP.
[0216] Additionally or alternatively, the reporting information may be transmitted from the first STA to the first AP without a request from the first AP (i.e., in an unsolicited manner). For example, the first STA may transmit the reporting information to the first AP based on an event. For example, the event may include an event in which an inter-BSS PPDU is received / detected a predetermined number of times and / or with a predetermined reception strength or higher.
[0217] The reporting information may include one or more of BSS color information of the second BSS, source address (SA) information of the inter-BSS PPDU (e.g., MAC address of the transmitting STA), destination address (DA) information of the inter-BSS PPDU (e.g., MAC address of the receiving STA), or uplink / downlink (UL / DL) direction information of the inter-BSS PPDU.
[0218] In step S1630, the first STA may receive scheduling information for the first STA from the first AP based on the reporting information.
[0219] For example, if the reporting information includes information indicating that an inter-BSS PPDU is received, the scheduling information for the first STA may include information indicating that uplink transmission of the first STA is not requested. For example, the information indicating that uplink transmission of the first STA is not requested may include information indicating that a response to downlink transmission from the first AP to the first STA is not requested (e.g., when the ACK policy is noACK). Additionally or alternatively, the information indicating that uplink transmission of the first STA is not requested may not include information triggering uplink transmission from the first STA. Alternatively, the first AP may not provide any scheduling information to the first STA. Alternatively, the first AP may provide the first STA with information to set an overlapping silence interval for a specific time interval, similar to the OBSS R-TWT SP protection scheme, or to schedule the specific time interval as an R-TWT SP for an STA other than the first STA, and / or to schedule the specific time interval as an OBSS R-TWT SP.
[0220] If the reporting information includes information indicating that an inter-BSS PPDU is not received, or if the reporting information including information indicating that an inter-BSS PPDU is received is not transmitted from the first STA to the first AP, the scheduling information for the first STA may include information requesting uplink transmission of the first STA. That is, if the first STA explicitly reports that a hidden node (e.g., the second STA) does not exist, or does not perform a report itself indicating the existence of a hidden node, the first AP may assume that the hidden node does not exist, and request uplink transmission from the first STA when necessary, perform downlink transmission from the first AP to the first STA, or allow or schedule transmission from another STA to the first STA.
[0221] The method described in the example of FIG. 16 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 be configured to monitor inter-BSS PPDUs transmitted from or to a second STA belonging to a second BSS, transmit report information including information indicating whether an inter-BSS PPDU has been received or not to the first AP via one or more transceivers, and receive scheduling information for the first device based on the report information from the first AP via one or more transceivers. Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 16 or the examples described below when executed by one or more processors (102).
[0222] FIG. 17 is a drawing for explaining the operation of an AP according to the present disclosure.
[0223] In step S1710, the first AP may receive, from the first STA associated with the first AP, report information including information indicating that an inter-BSS PPDU related to a second STA belonging to a second BSS has been received or not received by the first STA.
[0224] In step S1720, the first AP may transmit scheduling information for the first STA based on the reporting information to the first STA.
[0225] In the example of Fig. 17, the specific description of whether the first STA receives inter-BSS PPDU, reporting information, scheduling information for the first STA, etc. is the same as the example of Fig. 16, so redundant description is omitted.
[0226] The method described in the example of FIG. 17 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. 1 may be configured to receive, through one or more transceivers, reporting information from a first device coupled with the second device, the reporting information including information indicating that an inter-BSS PPDU transmitted from a second STA belonging to a second BSS or transmitted to the second STA has been received or not received by the first device, and to transmit, through one or more transceivers, scheduling information for the first device based on the reporting information to the first device. Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 17 or the examples described below when executed by one or more processors (202).
[0227] The examples of FIGS. 16 and 17 may correspond to some of the various examples of the present disclosure. Below, various examples of the present disclosure, including the examples of FIGS. 16 and 17, will be described in more detail.
[0228] In the embodiments described below, a representative example is given of a case in which there is one STA monitoring a hidden node within one BSS. However, even if there are multiple STAs monitoring hidden nodes, the embodiments described below can be applied equally to each STA.
[0229] In addition, in the embodiments described below, a representative example is given of a case where a hidden node for an AP of one BSS belongs to another BSS, but even in cases where there are multiple hidden nodes belonging to multiple BSSs, the embodiments described below can be equally applied to an STA that monitors each hidden node of each BSS.
[0230] Example 1
[0231] This embodiment relates to an STA that monitors a hidden node and a scheduling operation for the STA.
[0232] In the example of FIG. 14 or FIG. 15, STA1-2 may interfere with (or cause interference with) data transmission and reception of STA2-4 by performing PPDU transmission and reception (especially, UL PPDU transmission) during the R-TWT SP allocated to it from AP1. Similarly, STA2-4 may interfere with (or cause interference with) data transmission and reception of STA1-2 by performing PPDU transmission and reception (especially, UL PPDU transmission) during the R-TWT SP allocated to it from AP2. In such cases, STA1-2 and / or STA2-4 may reduce or prevent influence / interference on each other by performing the following operations.
[0233] First, assume a situation where an STA can overhear a PPDU involving another STA (i.e., transmitted from or to another STA). Here, the overheard PPDU can be limited to a case where it corresponds to an inter-BSS PPDU. That is, assume a situation where an STA can receive / detect transmission / reception involving an STA belonging to a BSS other than the one to which it belongs, such as STA1-2 or STA2-4 in FIG. 14 or FIG. 15, or a case where an STA exists in such a location.
[0234] An STA that receives / detects an inter-BSS PPDU can report to its associated AP that it has overheard the inter-BSS PPDU. For example, STA1-2 in FIG. 14 or FIG. 15 can report to AP1 that it has overheard a PPDU related to STA2-4, and STA2-4 can report to AP2 that it has overheard a PPDU related to STA1-2.
[0235] Additionally or alternatively, an AP may periodically request its associated STA(s) to report whether it has received / detected inter-BSS PPDUs (e.g., PPDUs associated with STAs belonging to other BSSs and in the UL direction). In response, the STA(s) may periodically report whether it has received / detected inter-BSS PPDUs to the associated AP. For example, AP1 in FIG. 14 or FIG. 15 may request STA1-2 to report inter-BSS PPDU monitoring results, and AP2 may request STA2-4 to report inter-BSS PPDU monitoring results.
[0236] When an STA reports that it has received / detected an inter-BSS PPDU (e.g., a PPDU related to an STA belonging to another BSS and in the UL direction), the AP may not request UL data transmission from the STA that provided the report. For example, the AP may request / schedule the STA to receive only DL data. For example, AP1 in FIG. 14 or FIG. 15 may schedule / configure STA1-2 not to perform UL data transmission, and AP2 may schedule / configure STA2-4 not to perform UL data transmission, thereby avoiding interfering with each other's data transmission and reception.
[0237] Example 2
[0238] This embodiment relates to inter-BSS PPDU monitoring report information.
[0239] Specific fields and / or elements used by an STA to report to an associated AP that an inter-BSS PPDU has been received / detected may include some / all of the information described below. The information included in the reporting information is not limited to the information described below, and may include various forms / types of information that may indicate that it corresponds to an inter-BSS PPDU and / or corresponds to UL data. Specific fields / elements including reporting information for an inter-BSS PPDU may be transmitted / received through a previously defined frame, or may be transmitted / received through a newly defined frame.
[0240] - BSS color: Corresponds to BSS color information (i.e., information that distinguishes BSSs) included in the BSS-to-BSS PPDU (especially UL data) received / detected by the STA.
[0241] - Source Address (SA): Corresponds to the MAC address of the transmitting STA of the inter-BSS PPDU (especially UL data) received / detected by the STA. This may correspond to the value of the address field set to SA or TA (transmitter address) in the PPDU (or in the MAC header).
[0242] - Destination Address (DA): This corresponds to the MAC address of the receiving STA of the inter-BSS PPDU (especially UL data) received / detected by the STA. This may correspond to the value of the address field set to DA or RA (receiver address) in the PPDU (or in the MAC header).
[0243] - Direction: This corresponds to information indicating whether the inter-BSS PPDU received / detected by the STA is in the uplink (UL) or downlink (DL) direction. UL / DL information can indicate whether the PPDU is transmitted from a non-AP STA belonging to a different BSS or from an AP belonging to a different BSS.
[0244] Unlike the method of protecting hidden nodes in existing wireless LAN systems, the hidden node interference reduction operation according to the examples of the present disclosure can achieve a new effect of protecting transmission and reception of hidden nodes by preventing transmission and reception that causes interference to the hidden node by an STA that monitors the hidden node.
[0245] 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.
[0246] 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.
[0247] 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.
[0248] 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 first station (STA) in a wireless LAN system, the method comprising: A step of monitoring an inter-BSS PPDU (physical layer protocol data unit) transmitted from or to a second STA belonging to a second BSS by a first STA associated with a first AP (access point) of a first BSS (basic service set); A step of transmitting report information including information indicating whether the inter-BSS PPDU has been received or not to the first AP; and A method comprising the step of receiving scheduling information for the first STA based on the above reporting information from the first AP.
2. In paragraph 1, A method in which the above reporting information is transmitted from the first STA to the first AP based on a request from the first AP.
3. In paragraph 2, A method in which a request from the first AP is periodically transmitted to the first STA.
4. In paragraph 1, A method in which the above reporting information is transmitted from the first STA to the first AP without a request from the first AP.
5. In paragraph 4, A method wherein the above reporting information is transmitted from the first STA to the first AP based on reception of the inter-BSS PPDU.
6. In paragraph 1, A method wherein, based on the above reporting information including information indicating that the inter-BSS PPDU is received, the scheduling information for the first STA includes information not requesting uplink transmission of the first STA.
7. In paragraph 6, Information that does not request uplink transmission of the above first STA, or includes information indicating that no response is requested for a downlink transmission from the first AP to the first STA, A method that does not include information that triggers uplink transmission from the first STA.
8. In paragraph 1, The above reporting information is, BSS color information of the above 2nd BSS, SA (source address) information of the above BSS-to-PPDU, Destination address (DA) information of the above BSS-to-BSS PPDU, or Uplink or downlink direction information of the above BSS-to-BSS PPDU A method comprising one or more of:
9. In paragraph 1, Based on the fact that the report information includes information indicating that the inter-BSS PPDU is not received, or that the report information including information indicating that the inter-BSS PPDU is received is not transmitted from the first STA to the first AP, A method wherein the scheduling information for the first STA includes information requesting uplink transmission of the first STA.
10. In paragraph 1, The beacon frame transmitted by the second AP of the second BSS is not received by the first STA, A method in which the inter-BSS PPDU transmitted by the second STA to one or more other entities belonging to the second BSS, or the inter-BSS PPDU transmitted from another entity belonging to the second BSS to the second STA, is received by the first STA.
11. In a first station (STA) of a wireless LAN system, the first 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: By the first STA associated with the first AP (access point) of the first BSS (basic service set), monitoring an inter-BSS PPDU (physical layer protocol data unit) transmitted from or to a second STA belonging to a second BSS; Transmitting report information including information indicating whether the inter-BSS PPDU is received or not to the first AP through the one or more transceivers; and A first STA configured to receive scheduling information for the first STA based on the above reporting information from the first AP through the one or more transceivers.
12. A method performed by a first access point (AP) in a wireless LAN system, the method comprising: A step of receiving, from a first station (STA) associated with the first AP of the first BSS (basic service set), report information including information indicating that an inter-BSS PPDU (physical layer protocol data unit) transmitted from a second STA belonging to a second BSS or transmitted to the second STA is received or not received by the first STA; and A method comprising the step of transmitting scheduling information for the first STA based on the above reporting information to the first STA.
13. In a first access point (AP) of 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: Receive, through one or more transceivers, report information including information indicating that an inter-BSS PPDU (physical layer protocol data unit) transmitted from a second STA belonging to a second BSS or transmitted to the second STA is received or not received by the first STA from a first station (STA) associated with the first AP of the first BSS (basic service set); and A first AP configured to transmit scheduling information for the first STA based on the above reporting information to the first STA through the one or more transceivers.
14. In a processing unit configured to control a station (STA) in a wireless LAN system, the processing unit: one or more processors; and A processing unit comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 10 based on execution by said one or more processors.
15. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a station (STA) device in a wireless LAN system to perform a method according to any one of claims 1 to 10.
Citation Information
Patent Citations
A channel contention method and related apparatus
CN107210847B
Power save mode-based operating method and apparatus in wireless LAN
KR1020170030564A
Basic bandwidth device on secondary channel
KR1020180091772A
Station (STA), access point (AP) and method of spatial reuse
US20180027573A1
Information transmission method, information receiving method, and apparatus for wireless communications system
US20210409075A1
Cited By
Wireless communication method, non-AP STA, and AP
US12777523B2
