Method and apparatus for accessing secondary channel in wireless LAN system

The secondary channel access method in wireless LAN systems addresses the inefficiency of busy primary channels by allowing limited transmissions in secondary channels, enhancing medium use efficiency and communication reliability.

WO2024253398A1PCT designated stage expired Publication Date: 2024-12-12LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/007575
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-07-04
Filing Date
2024-06-03
Publication Date
2024-12-12

AI Technical Summary

Technical Problem

In wireless LAN systems, when the primary channel is busy, there is inefficiency in medium use due to the inability to access secondary channels, leading to potential channel waste and reduced communication efficiency.

Method used

A method and device for secondary channel access, where a station sets a network allocation vector (NAV) for the primary channel and attempts to transmit frames in one or more secondary channels, with limited attempts to prevent indiscriminate frame transmission and optimize medium use efficiency.

Benefits of technology

This approach allows for efficient use of secondary channels even when the primary channel is busy, improving wireless communication efficiency by preventing channel waste and ensuring reliable frame transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024007575_12122024_PF_FP_ABST
    Figure KR2024007575_12122024_PF_FP_ABST
Patent Text Reader

Abstract

A method and an apparatus for accessing a secondary channel in a wireless LAN system are disclosed. A method performed by a station (STA) according to an embodiment of the present disclosure may comprise the steps of: configuring a network allocation vector (NAV) for a primary channel on the basis of a first frame received via a physical protocol data unit (PPDU) other than an intra basic service set (BSS) PPDU; and attempting to transmit a second frame on one or more secondary channels other than the primary channel.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for accessing secondary channels in wireless LAN systems

[0001] The present disclosure relates to a method and device for secondary channel access 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 accessing a secondary channel when a primary channel is busy.

[0005] In addition, an additional technical task of the present disclosure is to provide a frame transmission / reception method / transmission opportunity (TXOP) setting method for supporting secondary channel access and a device therefor.

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

[0007] In one aspect of the present disclosure, a method performed by a station (STA) may include: setting a network allocation vector (NAV) for a primary channel based on a first frame received via a PPDU (physical protocol data unit) other than an intra basic service set (BSS) PPDU; and attempting to transmit a second frame on one or more secondary channels other than the primary channel. The number of times the second frame is attempted to be transmitted on the one or more secondary channels may be limited within a maximum number of transmissions on the secondary channel.

[0008] A method performed by a station (STA) according to an additional aspect of the present disclosure may include: setting a network allocation vector (NAV) for a primary channel based on a first frame received via a PPDU other than an intra basic service set (BSS) physical protocol data unit (PPDU); and receiving a second frame on one or more secondary channels other than the primary channel.

[0009] According to the present disclosure, even if the medium for the primary channel is busy, the secondary channel can be used, thereby improving the efficiency of medium use and further improving the efficiency of wireless communication.

[0010] Additionally, according to the present disclosure, frame exchange operations on a primary channel can be protected by setting a TXOP for frame transmission on a secondary channel in consideration of a network allocation vector (NAV) for the primary channel.

[0011] In addition, according to the present disclosure, channel waste due to indiscriminate frame transmission can be prevented by limiting the number of frame transmissions according to secondary channel access operation.

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

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

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

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

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

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

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

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

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

[0021] FIG. 8 illustrates an EDCA parameter set element in a wireless LAN system to which the present disclosure can be applied.

[0022] FIG. 9 illustrates an MU EDCA parameter set element in a wireless LAN system to which the present disclosure can be applied.

[0023] FIG. 10 illustrates a channel access operation in a wireless communication system to which the present disclosure can be applied.

[0024] FIG. 11 illustrates a basic procedure of secondary channel access according to one embodiment of the present disclosure.

[0025] FIG. 12 illustrates an operation of an STA for secondary channel access according to one embodiment of the present disclosure.

[0026] FIG. 13 illustrates the operation of an STA receiving a frame transmitted via secondary channel access according to one embodiment of the present disclosure.

[0027] FIG. 14 is a diagram illustrating a multi-BSS topology in a wireless LAN system to which the present disclosure can be applied.

[0028] FIG. 15 illustrates a secondary channel access operation with a maximum number of frame transmissions applied according to one embodiment of the present disclosure.

[0029] FIG. 16 illustrates a secondary channel access operation in a secondary channel according to one embodiment of the present disclosure.

[0030] FIG. 17 illustrates the operation of a transmitting device for a secondary channel access method according to one embodiment of the present disclosure.

[0031] FIG. 18 illustrates the operation of a receiving device for a secondary channel access method according to one embodiment of the present disclosure.

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

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

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

[0035] In this disclosure, terms such as "first," "second," etc. are used only to distinguish one component from another, are not used to limit the components, and do not limit the order or importance of 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.

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

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

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

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

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

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

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

[0043] 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).

[0044] 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 memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software 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.

[0045] 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). In addition, 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.

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

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

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

[0049] 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 this 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.

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

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

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

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

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

[0055] 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).

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

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

[0058] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] 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).

[0080] 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, ...).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] 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).

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

[0104] 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)).

[0105] 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).

[0106] 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)).

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

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

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

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

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

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

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

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

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

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

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

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

[0119] 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.).

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

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

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

[0123] 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.).

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

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

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

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

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

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

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

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

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

[0133] EDCA channel access

[0134] The EDCA Channel Access Protocol adds four independent enhanced distributed channel access functions (EDCAFs) to the DCF procedure to provide differentiated priorities to traffic transmitted using four different access categories (ACs).

[0135] In the EDCA backoff procedure, each EDCAF maintains a MAC variable CW[AC] that is initialized to the value of the parameter CWmin[AC] for the AC of that EDCAF.

[0136] The TXNAV timer is a single timer shared by the EDCAF within an STA. It is initialized to the duration of the Duration / ID field of the most recently successfully transmitted frame by the TXOP holder, excluding PS-Poll frames. The TXNAV timer begins counting down from the end of the PPDU transmission containing the frame.

[0137] The backoff procedure by EDCAF can be performed when the medium is busy in the primary channel, as indicated by physical carrier sensing (CS), virtual CS, etc.

[0138] Three modes of EDCA TXOP are defined: EDCA TXOP initiation, EDCA TXOP sharing, and multi-frame exchange sequence within an EDCA TXOP. The initiation of a TXOP occurs when an EDCA rule grants access to the medium. EDCA TXOP sharing occurs when an EDCAF within an AP supporting DL MU-MIMO gains access to the medium, making that AC the primary AC and including traffic from queues associated with other ACs in the MU PPDUs transmitted during the TXOP. Multi-frame exchange sequence(s) within a TXOP occur when the EDCAF has the right to access the medium.

[0139] Each EDCAF maintains a backoff counter whose values ​​are measured during backoff slots. When the backoff procedure begins, the backoff counter is set to a randomly selected integer value using a uniform distribution ranging from 0 to CW[AC].

[0140] For each EDCAF, at a predefined slot boundary, an EDCAF operation is performed on the primary channel. At a slot boundary, each EDCAF decides to perform only one of the following functions: i) decrement the backoff counter, ii) initialize a TXOP, iii) decide not to transmit and invoke the backoff procedure, iv) invoke the backoff procedure due to an internal collision, or v) perform no action. However, at each slot boundary, if the backoff counter for that EDCAF has a non-zero value, each EDCAF decrements the backoff counter.

[0141] If one of the STA's EDCAFs is allowed to initiate a TXOP, the STA takes one of the following actions:

[0142] a) If the secondary channel, secondary 40MHz channel, and secondary 80MHz channel were idle during the PIFS period immediately before the start of TXOP, the STA transmits a 160MHz or 80+80MHz mask PPDU.

[0143] b) If both the secondary channel and the secondary 40MHz channel were in the IDLE state during the PIFS period immediately before the start of the TXOP, the STA transmits an 80MHz mask PPDU on the primary 80MHz channel.

[0144] c) Immediately before the start of the TXOP, if the secondary channel was IDLE during 1) the DIFS if the PPDU is transmitted within the 2.4 GHz band or 2) the PIFS otherwise, the STA transmits a 40 MHz mask PPDU on the primary 40 MHz channel.

[0145] d) STA transmits a 20MHz mask PPDU on the primary 20MHz channel.

[0146] e) The STA invokes the backoff procedure for EDCAF without transmitting anything.

[0147] f) If the secondary TVHT_W channel and secondary TVHT_2W channel were in IDLE state during the PIFS period immediately before the start of TXOP, the STA transmits a TVHT_4W or TVHT_2W+2W mask PPDU.

[0148] g) If the secondary TVHT_W channel was in IDLE state during the PIFS period immediately before the start of TXOP, the STA transmits a TVHT_2W or TVHT_W+W mask PPDU.

[0149] h) STA transmits TVHT_W mask PPDU on primary TVHT_W channel.

[0150] i) If all non-punctured 20MHz subchannels (except the primary 20MHz channel) were IDLE for the PIFS period immediately prior to the start of the TXOP, the STA transmits an 80MHz HE MU PPDU in which the only punctured subchannel in the preamble is the secondary 20MHz channel.

[0151] j) If all non-punctured 20MHz subchannels were IDLE for the PIFS period immediately prior to the start of the TXOP, the STA transmits an 80MHz HE MU PPDU in which the only punctured subchannel in the preamble is one of the two 20MHz subchannels in the secondary 20MHz channel.

[0152] k) If all non-punctured 20MHz subchannels were IDLE for the PIFS period immediately prior to the start of the TXOP, the STA transmits a 160MHz or 80+80MHz HE MU PPDU, where the punctured subchannels in the preamble are the secondary 20MHz channel and 0 to 2 of the 20MHz subchannels of the secondary 80MHz channel.

[0153] If two of the 20MHz subchannels of a secondary 80MHz channel are punctured, this corresponds to either the lower two or the upper two. For a 160MHz preamble, no more than two adjacent 20MHz subchannels are punctured throughout the entire preamble.

[0154] l) If all non-punctured 20MHz subchannels were IDLE for the PIFS period immediately prior to the start of the TXOP, the STA transmits a 160MHz or 80+80MHz HE MU PPDU, where the subchannels punctured in the preamble are 0, 1, or 2 20MHz subchannels in the secondary 40MHz channel and 0 to 2 20MHz subchannels in the secondary 80MHz channel.

[0155] At least one 20MHz subchannel is punctured. If two 20MHz subchannels of a secondary 80MHz channel are punctured, this corresponds to the lower two or upper two. For a 160MHz preamble, no more than two adjacent 20MHz subchannels are punctured throughout the entire preamble.

[0156] If both the STA and the BSS to which it belongs support multiple channel widths, the EDCA TXOP is acquired based solely on the activity of the primary channel. Here, "IDLE medium" may refer to an IDLE primary channel. Similarly, "BUSY medium" may refer to a BUSY primary channel.

[0157] CCAs are sampled according to the DCF timing relationship, and slot boundaries can only be determined by activity on the primary channel. Channel IDLE during the PIFS period can mean that the CCA for that channel is determined to be in the IDLE state whenever a CCA is sampled during the PIFS period that ends at the start of a transmission.

[0158] STAs supporting multiple NAVs update their NAVs. For STAs with two NAV timers, duration information is indicated in the frame as follows:

[0159] ― If the frame has a duration field, duration information is indicated in the Duration field.

[0160] ― If the frame is PS-Poll, the duration information is equal to the time (in microseconds) required to transmit one ACK frame and one SIFS according to the data rate selection rule.

[0161] An STA that receives at least one frame from a PSDU can update its NAV with information in the valid Duration field of the PSDU. If the RA of the received frame is the same as the STA's own MAC address, the STA does not update its NAV. Additionally, if the received frame is a CTS frame and its TA is the same as the STA's own MAC address, the STA does not update its NAV. For all other received frames, the STA updates its NAV when the received Duration is greater than the STA's current NAV value.

[0162] When an STA receives information that the NAV is greater than the STA's current NAV value, the STA updates the NAV to the new NAV value. This information can be received in the Duration field of NDP CTS, NDP ACK, and S1G beacon frames.

[0163] An AP that is not a TXOP holder updates the NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION for the PPDU if all of the following conditions are met, and does not update the NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION if any of the following conditions is not met.

[0164] ― The RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED.

[0165] ― The AP does not receive frames containing a Duration field in the PPDU.

[0166] ― The duration indicated by the RXVECTOR parameter TXOP_DURATION is greater than the current NAV value of the AP.

[0167] An AP that is a TXOP holder updates NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION for the PPDU if all of the following conditions are met, and does not update NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION if any of the following conditions is not met.

[0168] ― The RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED.

[0169] ― The AP does not receive frames containing a Duration field in the PPDU.

[0170] ― The duration indicated by the RXVECTOR parameter TXOP_DURATION is greater than the current NAV value of the AP.

[0171] - The RXVECTOR parameter BSS_COLOR is not identical to the BSS color of the HE AP.

[0172] Non-AP STAs can maintain two NAVs, and APs can maintain two NAVs: an intra-BSS NAV and a basic NAV. The intra-BSS NAV is updated by intra-BSS PPDUs. The basic NAV is updated by inter-BSS PPDUs, or PPDUs that cannot be classified as inter-BSS or inter-BSS.

[0173] The STA updates the intra-BSS NAV with the duration information indicated by the received frame of the PSDU only if all of the following conditions are met:

[0174] - The frame is identified as inter-BSS.

[0175] ― The indicated duration is greater than the current intra-BSS NAV value.

[0176] ― The RA of the received frame is not the MAC address of the STA. Or the STA is not a TXOP holder, and the PPDU carrying the frame does not contain a frame requesting an immediate response from the STA. Or the STA is not a TXOP holder, and the received frame is a trigger frame.

[0177] The STA updates the basic NAV with the duration information indicated by the received frame of the PSDU only if all of the following conditions are met:

[0178] ― The frame is identified as inter-BSS or cannot be identified as inter-BSS or inter-BSS.

[0179] ― The indicated duration is greater than the current basic NAV value.

[0180] ― The RA of the received frame is not the MAC address of the STA.

[0181] An STA that is not a TXOP holder updates the intra-BSS NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION for the PPDU only if all of the following conditions are met:

[0182] ― The RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED.

[0183] ― The PPDU that conveys information about the RXVECTOR parameter is identified as Intra-BSS.

[0184] ― STA does not receive a frame containing a Duration field in the PPDU.

[0185] ― The duration information indicated by the RXVECTOR parameter TXOP_DURATION is greater than the STA's current Intra-BSS NAV.

[0186] The STA updates the basic NAV with the duration information indicated by the RXVECTOR parameter TXOP_DURATION for the PPDU only if all of the following conditions are met:

[0187] ― The RXVECTOR parameter TXOP_DURATION is not UNSPECIFIED.

[0188] ― A PPDU conveying information about the RXVECTOR parameter is identified as inter-BSS or cannot be identified as inter-BSS or inter-BSS.

[0189] ― STA does not receive a frame containing a Duration field in the PPDU.

[0190] ― The duration information indicated by the RXVECTOR parameter TXOP_DURATION is greater than the basic NAV of the current STA.

[0191] FIG. 8 illustrates an EDCA parameter set element in a wireless LAN system to which the present disclosure can be applied.

[0192] For infrastructure BSSs, EDCA parameter set elements are used by APs to establish policies (by modifying default MIB attribute values) and to change policies when accepting new STAs or new traffic, or to adapt to changes in the offered load. The most recent EDCA parameter set element received by an STA is used to update the appropriate management information base (MIB) values.

[0193] Referring to FIG. 8(a), the EDCA parameter set element is configured to include an Element ID field, a Length field, a QoS Info field, an EDCA Info update field, an AC_BE Parameter Record field, an AC_BK Parameter Record field, an AC_VI Parameter Record field, and an AC_VO Parameter Record field.

[0194] The Element ID field indicates the identifier of the element, and the Length field indicates the number of octets in the element, excluding the Element ID and Length fields.

[0195] The QoS Info field contains capability information bits, the contents of which vary depending on whether the STA is contained within the AP.

[0196] The Update EDCA Info field includes an Override field that indicates whether the corresponding EDCA parameter set element overrides previously stored EDCA parameters, and a PS-Poll ACI (access category index) field that informs the STA of the access category for transmitting the PS-Poll frame.

[0197] Referring to FIG. 8(b), the formats of the AC_BE Parameter Record field, the AC_BK Parameter Record field, the AC_VI Parameter Record field, and the AC_VO Parameter Record field are the same, and each field includes an ACI / AIFSN subfield, an ECWmin / ECWmax subfield, and a TXOP limit subfield.

[0198] The ACI / AIFSN field contains i) an arbitration interframe space number (AIFSN) subfield indicating the number of slots after SIFS that the STA will delay before invoking backoff or starting transmission, ii) an admission control mandatory (ACM) subfield indicating whether admission control is required for the access category, and iii) an ACI subfield indicating an access category index (ACI) value. The ACI subfield refers to the access category to which all parameters in this record correspond.

[0199] The ECWmin / ECWmax subfields encode the CWmin and CWmax values ​​in exponential form, i.e., CWmin=2 ECWmin -1 and CWmax=2 ECWmax It's -1.

[0200] The TXOP limit subfield specifies an unsigned integer in units. The TXOP limit is advertised by the AP through this subfield, and the TXOP holder must ensure that the TXOP duration does not exceed the TXOP limit if the TXOP duration is non-zero.

[0201] FIG. 9 illustrates an MU EDCA parameter set element in a wireless LAN system to which the present disclosure can be applied.

[0202] For infrastructure BSSs, the MU EDCA parameter set element is used by the AP to control EDCA usage by non-AP STAs following a specific UL MU TB PPDU transmission. The most recent MU EDCA parameter set element received by a non-AP STA is used to update the appropriate MIB value.

[0203] Referring to FIG. 9(a), the MU EDCA parameter set element is configured to include an Element ID field, a Length field, an Element ID Extension field, a QoS Info field, an MU AC_BE Parameter Record field, an MU AC_BK Parameter Record field, an MU AC_VI Parameter Record field, and an MU AC_VO Parameter Record field.

[0204] The Element ID field and the Element ID Extension field indicate the identifier of the corresponding element, and the Length field indicates the number of octets in the element excluding the Element ID and Length fields.

[0205] The QoS Info field contains capability information bits, the contents of which vary depending on whether the STA is contained within the AP.

[0206] Referring to FIG. 9(b), the formats of the MU AC_BE Parameter Record field, the MU AC_BK Parameter Record field, the MU AC_VI Parameter Record field, and the MU AC_VO Parameter Record field are the same, and each field includes an ACI / AIFSN subfield, an ECWmin / ECWmax subfield, and an MU EDCA Timer subfield.

[0207] The description of the ACI / AIFSN subfield and the ECWmin / ECWmax subfield are the same as the description according to Fig. 8(b).

[0208] The MU EDCA Timer subfield indicates the period during which the STA uses the MU EDCA parameters for the corresponding AC.

[0209] Secondary channel access method

[0210] Channel access, as defined in the current 802.11 standard, is performed based on the primary channel. That is, an STA can transmit frames on the medium that includes the primary channel and an idle secondary channel only when the primary channel is idle and the back-off counter (BC) is 0. To this end, all STAs perform Clear Channel Assessment (CCA) with the primary channel as a priority. Accordingly, the AP announces the primary channel of the BSS and always includes the primary channel in the channel used to transmit management frames such as beacon frames and probe response frames. This mechanism can achieve the effect of performing frame exchanges between all STAs and APs without interference, i.e., it is effective for frame protection. However, on the other hand, when only the primary channel is busy, i.e., the STA cannot access the secondary channel that is IDLE, so it is inefficient from the perspective of media use.

[0211] In the present disclosure, the primary channel may refer to a common channel of operation for all STAs that are members of a BSS. For example, in a 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 320 MHz BSS, the primary channel may be the primary 20 MHz channel. Furthermore, in the present disclosure, the secondary channel may refer to one or more channels linked to the primary channel that are used to create a wider channel than the primary channel.

[0212] FIG. 10 illustrates a channel access operation in a wireless communication system to which the present disclosure can be applied.

[0213] Figure 10 illustrates channel access based on the primary channel in an 80 MHz bandwidth.

[0214] Hereinafter, for convenience of explanation, in the present disclosure, the primary channel and secondary channel are referred to as follows, as in FIG. 10.

[0215] - P20: primary 20MHz channel

[0216] - S20: secondary 20MHz channel (i.e., when the bandwidth is 40MHz, it refers to the 20MHz secondary channel excluding P20. In other words, it refers to the 20MHz secondary channel adjacent to P20.)

[0217] - S40: secondary 40MHz channel (i.e., when the bandwidth is 80MHz, it refers to the remaining 40MHz secondary channel excluding P20+S20)

[0218] - S80: secondary 80MHz channel (i.e., when the bandwidth is 160MHz, it refers to the remaining 80MHz secondary channel excluding P20+S20+S40)

[0219] - S160: secondary 160MHz channel (i.e., when the bandwidth is 320MHz, it refers to the remaining 160MHz secondary channels excluding P20+S20+S40+S80)

[0220] - S320: secondary 320MHz channel (i.e., when the bandwidth is 640MHz, it refers to the remaining 320MHz secondary channels excluding P20+S20+S40+S80+S160)

[0221] Referring to Fig. 10, according to the existing operation, if P20 is BUSY due to CCA or NAV, etc., the STA does not decrease the backoff counter (BC) and waits until it becomes IDLE. When the backoff counter becomes 0 through this back-off process, the STA checks the channel status of S20 and S40 (i.e., CCA) and transmits a frame on the IDLE channel. Since the example of Fig. 10 assumes that S40 is BUSY, the STA transmits a frame corresponding to a 40MHz PPDU through P20 and S20.

[0222] As described above, when P20 is BUSY and S20 and S40 are IDLE as in Fig. 10, the bandwidth corresponding to 60 MHz (i.e., S20+S40) is wasted (i.e., not used), so the efficiency of medium use is reduced.

[0223] Therefore, in the present disclosure below, a method for accessing a secondary channel when P20 is BUSY is proposed.

[0224] In the present disclosure, secondary channel access means that an STA accesses a secondary channel (i.e., a medium on the secondary channel) while the primary channel (i.e., a medium on the primary channel) is BUSY (e.g., due to OBSS traffic or other circumstances). Here, an AP or non-AP STA may determine that the primary channel is BUSY based on physical carrier sensing and / or virtual carrier sensing and / or NAV settings, etc.

[0225] For convenience of explanation in this disclosure, the term "secondary channel" is used to collectively refer to one or more channels other than the primary channel. However, the present disclosure is not limited thereto, and may also be referred to as a non-primary channel. In addition, secondary channel access may be referred to as non-primary channel access (NPCA).

[0226] The terms (i.e., designations, names, etc.) used in this disclosure are for convenience of explanation, and the proposed method of this disclosure is not limited thereto, and may be replaced with other terms without altering the method proposed in this disclosure. In addition, the term "STA" in this disclosure may be used to mean either an AP STA or a non-AP STA.

[0227] According to one embodiment of the present disclosure, the capability of an STA for secondary channel access (SCA) may be defined. For example, an STA and an AP may exchange (i.e., inform each other of their capabilities) whether they support SCA capability and / or whether SCA is enabled. The capability of SCA may be determined based on whether the STA can perform a first type of CCA (i.e., referred to as preamble detection (PD)) capable of identifying a wireless LAN frame performed on a primary channel (PCH) on a secondary channel (SCH), i.e., whether the STA can decode the frame on the SCH. Through this, the STA may also set a NAV (e.g., an intra-BSS NAV or a basic NAV) on the SCH.

[0228] - Level 0: An STA with level 0 capability can only perform Type 2 CCA on the SCH as before, and cannot perform Type 1 CCA (i.e., No Back-off on SCH). That is, an STA with level 0 capability can only perform Type 2 CCA, which includes CCA that can detect a wireless LAN signal on the SCH (i.e., referred to as guard interval detection (GID)) and CCA that detects a signal above a certain intensity (i.e., referred to as energy detection (ED)).

[0229] - Level 1: An STA with level 1 capability can perform PD, the first type of CCA, on only one SCH at a time (i.e., back-off on a SCH at a time). In other words, an STA with level 1 capability cannot perform the first type of CCA on multiple SCHs simultaneously.

[0230] - Level 2: An STA with level 2 capability can perform PD, which is the first type of CCA, on more than one SCH at the same time (i.e., back-off on SCHs at the same time). In other words, an STA with level 2 capability can perform the first CCA on multiple SCHs at the same time.

[0231] These capabilities can be transmitted by being included in fields / elements within a frame (e.g., UHR capability elements / information elements (IEs)). For example, an AP can transmit capabilities by including them in a beacon frame, a probe response frame, a (re)association request frame, etc., and a non-AP STA can transmit capabilities by including them in a probe request frame, a (re)association request frame, etc.

[0232] Below, the basic procedure for secondary channel access is described.

[0233] An STA can set (i.e., maintain / update) two NAVs: a basic NAV and an intra-BSS NAV. The basic NAV can be updated based on a PPDU identified as an inter-BSS PPDU, or based on a PPDU that cannot be identified as an inter-BSS PPDU or an intra-BSS PPDU. On the other hand, the intra-BSS NAV can be updated based on a PPDU identified as an intra-BSS PPDU. Intra-BSS PPDU and inter-BSS PPDU can be distinguished based on the operation defined in the wireless LAN standard.

[0234] For example, if intra-BSS NAV is set in PCH for STA, the following situation may occur:

[0235] When an AP exchanges frames with a TA within a transmission opportunity (TXOP) acquired by the AP, other STAs set intra-BSS NAV based on the primary channel. At this time, when an STA with set intra-BSS NAV accesses the SCH and transmits a frame to the AP, if the AP performs transmission (Tx: transmission) (e.g., DL data, ACK (acknowledgement), etc.), the AP will not receive it (i.e., the frame on the SCH transmitted from the STA to the AP).

[0236] Therefore, to prevent the above situation, the STA can perform SCA only when the Basic NAV from a BSS other than its own BSS (i.e., an overlapping BSS (OBSS)) is set in the PCH.

[0237] That is, STA can perform SCA when Basic NAV is set in PCH.

[0238] The basic procedure for SCA is described with reference to the drawings below.

[0239] FIG. 11 illustrates a basic procedure of secondary channel access according to one embodiment of the present disclosure.

[0240] 1) Frame transmission method

[0241] As in the example of Fig. 10 above, when the back-off counter becomes 0 through back-off at P20, the STA can transmit a frame through i) P20 and ii) one or more SCHs that are IDLE, depending on whether one or more SCHs are IDLE / BUSY.

[0242] In order to implement the SCA proposed in this disclosure, a change in the operation according to the prior art is required because the situation in which P20 is BUSY is taken into account. Accordingly, the back-off operation proposed in this disclosure is as follows.

[0243] - STA can perform back-off on one or more SCHs when P20 is BUSY.

[0244] For example, if a neighboring STA with the same or similar operating channel as a specific STA does not perform back-off on a channel that includes / overlaps with the SCH of the specific STA, the channel may be determined to be IDLE for a predetermined short period of time (e.g., 1 slot) based on the CCA result. In this case, if the specific STA and the neighboring STA transmit frames simultaneously, a collision may occur, which may actually waste the channel. Therefore, back-off also needs to be performed on the SCH.

[0245] Here, if the remaining NAV timer in the current PCH (P20) is not enough time to secure a TXOP in the SCH, the STA may not perform a back-off in the SCH.

[0246] - When the back-off counter becomes 0, the STA can perform a second type of CCA on other SCH(s) other than the one or more SCHs that performed the back-off. For example, the STA can perform CCA on other SCH(s) other than the SCH that performed the back-off during a certain period of time (e.g., PIFS (priority interframe space)) before the time when the back-off counter becomes 0 on the SCH that performed the back-off, to determine whether the channel is IDLE or BUSY.

[0247] - Depending on the CCA result, the STA may transmit frames on a channel that includes one or more SCHs that are IDLE and one or more SCHs that have performed back-off.

[0248] In Fig. 11, an example is provided where STA performs a back-off from S20 when P20 is BUSY. Here, it is assumed that when the back-off counter in S20 becomes 0, both 20MHz channels of S40 are in an IDLE state. Therefore, in this case, the STA can transmit an 80MHz PPDU (including a MAC frame) containing signaling / information that P20 has been punctured.

[0249] 2) How to set TXOP

[0250] Since the STA must perform CCA for P20 by default when the basic NAV on P20 expires, the STA can set the end time of the TXOP so that the TXOP on the SCH ends before the time when the basic NAV on P20 expires.

[0251] If the TXOP on the SCH is set to end after the time when the basic NAV on P20 expires, a problem may arise where the STA cannot receive the frame because legacy STAs, etc., can transmit frames through the P20 after the basic NAV set for the STA (i.e., because the frame transmission is performed on the SCH). In addition, if the target beacon transmission time (TBTT) is set in the middle of the basic NAV, a problem may arise because the AP must prepare to transmit the beacon immediately after the basic NAV, and a problem may arise where non-AP STAs cannot receive the beacon that the AP should transmit in time and wait for a longer time than the scheduled time. Therefore, by setting the end time of the TXOP on the SCH so that the TXOP on the SCH ends before the time when the basic NAV on the P20 expires, the STA can perform normal frame exchange on the P20.

[0252] If there is not enough time to establish a TXOP on the SCH (i.e., the STA cannot secure the time required for frame exchange on the SCH before the basic NAV of P20 expires), the STA may not transmit a frame on the SCH. In other words, if it is difficult to establish a TXOP on the SCH within the interval between the time when the back-off counter on the SCH becomes 0 and the time when the basic NAV on the PCH expires, the STA may not transmit a frame.

[0253] For example, when performing a back-off at S20 as in the example of FIG. 11 and setting a TXOP for the SCH by making the back-off counter 0, the STA can set the TXOP for the SCH to end earlier than the time at which the basic NAV at P20 ends.

[0254] Hereinafter, the STA mentioned in the present method may be a non-AP STA or an AP.

[0255] FIG. 12 illustrates an operation of an STA for secondary channel access according to one embodiment of the present disclosure.

[0256] According to one embodiment of the present disclosure, an STA performing SCA may transmit a frame / PPDU on an SCH even during the time when a NAV is set on the PCH. For example, the STA may transmit a frame / PPDU with the PCH excluded / punctured on i) one or more SCHs that performed backoff and ii) one or more SCHs in an IDLE state determined based on the CCA result among the remaining SCHs that did not perform backoff.

[0257] Referring to FIG. 12, when an STA receives a PPDU including a frame from another BSS, it sets NAV in the PCH (S1201).

[0258] During the time that NAV is set in PCH, the STA performs backoff on one or more 20MHz SCHs (S1202).

[0259] When the backoff counter becomes 0 in the SCH that performed the backoff, the STA can perform CCA in one or more other SCHs (S1203).

[0260] The STA transmits a PPDU including a frame using a bandwidth of a size corresponding to i) one or more SCHs that have performed backoff and ii) one or more other SCHs that are IDLE as a result of performing CCA (S1204).

[0261] Here, additionally or alternatively, a TXOP starting with a frame / PPDU transmission on one or more SCHs may be set to end before the NAV on the PCH ends. The TXOP length may be set / indicated via the duration / ID field of the corresponding frame. For example, the value of the duration / ID field may be set to a value representing the time required for the exchange of a frame / PPDU following the corresponding frame / PPDU (including the interframe gap (IFS)).

[0262] Additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed may be set to the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a newly defined EDCA Parameter Set. Furthermore, the EDCA Parameter Set may be applied equally to all SCHs or may be applied differently for each SCH.

[0263] FIG. 13 illustrates the operation of an STA receiving a frame transmitted via secondary channel access according to one embodiment of the present disclosure.

[0264] In the present disclosure, an STA receiving a frame transmitted via SCA (i.e., a PPDU carrying the frame) may perform frame detection on the SCH even during the time when a NAV is set in the PCH. For example, the STA may perform backoff on the SCH because there is a frame to be transmitted, or the STA may attempt to receive a frame addressed to itself on the SCA even when there is no frame to be transmitted. In addition, the STA may perform NAV setting / resetting based on the value of the duration / ID field of the frame detected on the SCH.

[0265] Referring to FIG. 13, when an STA receives a PPDU including a frame from another BSS, it sets NAV in the PCH (S1301).

[0266] During the time that NAV is set in PCH, the STA performs backoff on one or more 20MHz SCHs (S1302).

[0267] The STA receives a PPDU containing one or more frames during backoff. Here, it is checked whether the frame is addressed to the STA (i.e., whether the receiver address of the received frame is the STA's own MAC address) (S1303).

[0268] If the receiver address of the received frame is the STA's own MAC address, the STA does not update the NAV and decodes the frame body of the frame (S1304).

[0269] If the receiver address of the received frame is not the STA's own MAC address, the STA sets ( / updates) the NAV with the information in the Duration field of the frame's MAC header (i.e., the duration value) (S1305).

[0270] Here, additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed can be set to the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a new EDCA Parameter Set. Furthermore, the EDCA Parameter Set can be applied equally to all SCHs or applied differently to each SCH.

[0271] Meanwhile, the following issues may occur when transmitting / receiving frames for SCA:

[0272] Issue 1: There may be cases where a frame transmitted by one STA (i.e., TX STA) is not received by the STA addressed in the frame (i.e., RX STA).

[0273] For example, it may be the case that a TX STA is performing SCA at P20 due to NAV, but an RX STA is performing back-off at P20 because NAV is not set at P20 (i.e., the RX STA is not performing SCA).

[0274] FIG. 14 is a diagram illustrating a multi-BSS topology in a wireless LAN system to which the present disclosure can be applied.

[0275] Referring to FIG. 14, AP 2 and STA 2-1 may set Basic NAV when STA 1-2 is transmitting a frame (i.e., when STA 1-2 acquires TXOP). However, STA 2-2 may not set Basic NAV because it is not affected by STA 1-2. Therefore, in this situation, if AP 2 and STA 2-2 support SCA and AP 2 performs SCA on one or more SCHs, the following issue may occur. When AP 2 transmits a frame addressed to STA 2-2 or STA 2-2 transmits a frame addressed to AP 2, STA 2-2 currently performs back-off on PCH while AP 2 performs back-off on SCH, so that neither frame is received.

[0276] Therefore, unnecessarily continuously transmitting frames to the same receiving STA can result in channel waste. In particular, for non-AP STAs, transmitting frames to the AP can cause greater problems than for APs, which can transmit to multiple STAs. Therefore, when frame transmissions continue to fail, it may be desirable to limit the number of frame transmissions, such as RTS frames, for protection. Furthermore, continuous frame transmission failures increase the contention window (CW), which can reduce transmission opportunities for channel access. Solutions to this issue are as follows.

[0277] - Maximum number of frame transmissions (MaxTxFrame): When SCA is performed, the maximum number of frame transmissions, such as RTS frames, on one or more SCHs can be predefined or set. That is, repeated frame transmissions can be restricted through continuous back-off.

[0278] Here, the AP can announce information about the maximum number of frame transmissions (MaxTxFrame) by including it in a management frame such as a beacon or probe response frame.

[0279] Additionally or alternatively, information about the maximum number of frame transmissions can be determined through negotiation between the STA and AP on a request / response basis.

[0280] When the number of frame transmissions of an STA reaches MaxTxFrame, the STA may perform at least one of the following actions thereafter.

[0281] - It can wait for a frame addressed to the STA or a frame that is not addressed to the STA, i.e. a frame for which NAV can be set.

[0282] - Back-off can be performed by stopping SCA and switching back to PCH.

[0283] - Back-off can be performed continuously. When back-off is performed continuously, the STA can select the back-off counter again when the back-off counter = 0.

[0284] FIG. 15 illustrates a secondary channel access operation with a maximum number of frame transmissions applied according to one embodiment of the present disclosure.

[0285] Referring to Fig. 15, an example is given assuming that MaxTxFrame = 2 is announced from the AP via a beacon.

[0286] If an STA performs a backoff at S20 and transmits a frame to another STA (i.e., STA 1) twice, and both of them fail, the STA may not perform a backoff thereafter. While not performing a backoff, the STA may wait for i) a frame addressed to the STA or ii) a frame not addressed to the STA, that is, a frame for which a NAV can be set. Alternatively, the STA may switch to the PCH and perform a backoff again there. In this way, when SCA is performed, unnecessary frame transmission on one or more SCHs can be avoided.

[0287] Meanwhile, a blindness issue (hereinafter, Issue 2) may occur for SCA. A blindness issue refers to a state in which the current situation occurring on the channel to be changed is not recognized. For example, when a first STA in power saving mode changes from a doze state to an awake state, if a second STA, which is currently a hidden node (an STA not within the transmission / reception range), transmits a frame to a third STA within the transmission / reception range of the first STA, the first STA will not be aware of this. Here, since if the first STA transmits a frame, it may affect the third STA, so the first STA starts the NAV synchronization delay timer (NAVSyncDelay Timer). The NAVSyncDelay timer refers to a delay used before transmission when changing from a doze state to an awake state and changing the channel if a frame capable of setting the NAV is not detected. Therefore, the first STA performs CCA until frame detection or timer expiration while this timer is running.

[0288] Similarly, blindness issues that may arise with SCA include:

[0289] - Case #1: When performing channel access by switching to SCH after Basic NAV is set in PCH

[0290] - Case #2: After performing SCA in SCH, switching to PCH to perform channel access

[0291] The steps to address issue 2 described above are as follows:

[0292] A timer can be defined / set for each of PCH and SCH. In this disclosure, for convenience of explanation, case #1 is referred to as SCHTimer, and case #2 is referred to as PCHTimer.

[0293] Here, each Timer can be designated by a value with a certain unit (e.g., 32us, 64us). Additionally or alternatively, the Timer can vary for each SCH on which Back-off is performed. Additionally or alternatively, it can vary depending on the Basic NAV value set in the PCH.

[0294] An STA may terminate a Timer if it receives a frame / PPDU that can set the NAV while each Timer is running or a frame / PPDU addressed to the STA that started the Timer.

[0295] Additionally, back-off is performed while each Timer is operating, and the STA can transmit frames such as RTS, MU-RTS, and BSR (buffer state report) triggers.

[0296] Here, if frame transmissions continue to fail, it may be desirable to limit the number of frame transmissions, such as RTS frames, for protection. Furthermore, continuous frame transmission failures increase the contention window (CW), which can reduce transmission opportunities for channel access. Furthermore, continuous, unnecessary transmissions waste the channel. Solutions (and information for this) to address this issue are as follows.

[0297] - Maximum number of frames to be transmitted for PCH (MaxTxFrame for PCH): (Within the timer operation) If there is a PCH and an IDLE SCH while the PCHTimer is running for case #2, the maximum number of frame transmissions, such as RTS frames, on one or more SCHs can be defined or set. That is, the frames can be prevented from being transmitted repeatedly through continuous back-off.

[0298] - Maximum number of frame transmissions for SCH (MaxTxFrame for SCH): For Case #1, the maximum number of frame transmissions, such as RTS frames, on one or more SCHs can be defined or set while the SCHTimer is running. This means that frames can be prevented from being transmitted repeatedly through continuous back-off.

[0299] If the number of frame transmissions of an STA reaches MaxTxFrame and the Timer is still running, the STA can continuously wait for a frame addressed to the STA or a frame not addressed to the STA, i.e. a frame for which NAV can be set, until the Timer expires through CCA.

[0300] Additionally, back-off may continue to be performed after each Timer expires, in which case the above maximum number of transmissions (MaxTxFrame for PCH / SCH) may not apply.

[0301] Here, additionally or alternatively, frames transmitted in Case #1 and Case #2 may have their Duration set to 0 to prevent other STAs from setting their NAVs in advance.

[0302] The above information (SCHTimer, PCHTimer, MaxTxFrame for PCH, MaxTxFrame for SCH) can be determined using at least one of the following methods.

[0303] The AP can announce the above information by including it in a management frame such as a beacon or probe response frame.

[0304] Additionally or alternatively, the above information may be determined through negotiation between the STA and the AP on a request / response basis.

[0305] FIG. 16 illustrates a secondary channel access operation in a secondary channel according to one embodiment of the present disclosure.

[0306] Referring to Figure 16, an example is provided assuming that SCHTimer = 50 (32us units) (i.e., total timer time is 1600us) and MaxTxFrame = 2 are announced via a beacon from the AP.

[0307] When an STA performs SCA, the first RTS frame transmitted on one or more SCHs (S20 and S40 in FIG. 16) may fail to be transmitted through backoff in S20 while the SCHTimer is running. In this case, while the SCHTimer is running, the STA can transmit a second RTS frame through backoff again, and obtain a TXOP when the transmission of the second RTS frame is successful. If MaxTxFrame for SCH = 1 in the example of FIG. 16, the second RTS frame will not be transmitted.

[0308] When the number of frame transmissions on the SCH of an STA reaches the maximum number of frame transmissions, the STS may wait until the timer (i.e., SCHTimer) expires for either i) a frame addressed to the STA or ii) a frame not addressed to the STA, i.e., a frame for which a NAV can be set.

[0309] 1) The operation according to one embodiment of the present disclosure for the above-described issue 1 is as follows.

[0310] In the present disclosure, an STA performing SCA may transmit a frame / PPDU on an SCH even during the time when a NAV is set on the PCH. For example, the STA may transmit a frame / PPDU with the PCH excluded / punctured on one or more SCHs in an IDLE state as determined by the CCA results of i) one or more SCHs on which backoff has been performed and ii) one or more SCHs on which backoff has not been performed.

[0311] Additionally or alternatively, a TXOP initiated by transmitting a frame / PPDU on the SCH may be configured to end before the NAV on the PCH ends. Here, the TXOP length may be configured / indicated via the duration / ID field of the corresponding frame. For example, the value of the duration / ID field may be set to a value corresponding to the time required for the exchange of a frame / PPDU following the corresponding frame / PPDU (including the interframe interval (IFS)).

[0312] Additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed may be configured as the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a new EDCA Parameter Set. This EDCA Parameter Set may be applied equally to all SCHs, or may be applied differently for each SCH.

[0313] Additionally or alternatively, information regarding the maximum number of times a frame / PPDU can be transmitted on the SCH may be transmitted in a management frame (e.g., a beacon frame) transmitted by the AP. If the STA performing SCA is an AP, it may utilize the information transmitted by itself (information regarding the maximum number of times a frame / PPDU can be transmitted).

[0314] Additionally or alternatively, the maximum number of times a frame / PPDU can be transmitted may be determined through negotiation between the AP and the STA.

[0315] Additionally or alternatively, if the number of times an STA has transmitted a frame / PPDU reaches the maximum number of times it can transmit a frame / PPDU, then the STA may wait for i) a frame addressed to the STA or ii) a frame not addressed to the STA, i.e., a frame for which a NAV can be set.

[0316] Additionally or alternatively, if the number of times an STA has transmitted a frame / PPDU reaches the maximum number of times it can transmit a frame / PPDU, the STA may then perform a back-off by aborting the SCA and switching back to the PCH.

[0317] Additionally or alternatively, if the number of times an STA has transmitted a frame / PPDU reaches the maximum number of times it can transmit a frame / PPDU, the STA may perform back-off continuously thereafter.

[0318] According to an embodiment of the present disclosure, an STA receiving a frame transmitted via an SCA may perform frame detection on the SCH even during the time when a NAV is set in the PCH. For example, if the STA has a frame to transmit, the STA may perform a backoff on the SCH, and if the STA does not have a frame to transmit, the STA may attempt to receive a frame addressed to itself on the SCH. Furthermore, the STA may perform NAV setting / resetting based on the value of the duration / ID field of the frame detected on the SCH.

[0319] Additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed may be configured as the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a new EDCA Parameter Set. This EDCA Parameter Set may be applied equally to all SCHs, or may be applied differently for each SCH.

[0320] 2) With respect to the above-described issue 2, the operation according to one embodiment of the present disclosure is as follows.

[0321] In the present disclosure, an STA performing SCA may transmit a frame / PPDU on an SCH even during the time when a NAV is set on the PCH. For example, the STA may transmit a frame / PPDU with the PCH excluded / punctured on one or more SCHs in an IDLE state as determined by the CCA results of i) one or more SCHs on which backoff has been performed and ii) one or more SCHs on which backoff has not been performed.

[0322] Additionally or alternatively, a TXOP initiated by transmitting a frame / PPDU on the SCH may be configured to end before the NAV on the PCH ends. Here, the TXOP length may be configured / indicated via the duration / ID field of the corresponding frame. For example, the value of the duration / ID field may be set to a value corresponding to the time required for the exchange of a frame / PPDU following the corresponding frame / PPDU (including the interframe interval (IFS)).

[0323] Additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed may be configured as the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a new EDCA Parameter Set. This EDCA Parameter Set may be applied equally to all SCHs, or may be applied differently for each SCH.

[0324] Additionally or alternatively, a timer may be set for one or more SCHs performing backoff. Here, the timer may be set from the start of the backoff. This timer may be transmitted from a management frame (e.g., a beacon frame) transmitted by the AP.

[0325] Additionally or alternatively, the maximum number of times a frame / PPDU can be transmitted may be determined through negotiation between the AP and the STA.

[0326] Additionally or alternatively, information about the maximum number of times a frame / PPDU can be transmitted on the SCH while the Timer is running (and / or information about the maximum number of times a frame / PPDU can be transmitted on the PCH) may be transmitted in a management frame (e.g., a beacon frame) transmitted by the AP. If the STA performing SCA is an AP, it can utilize the information transmitted by itself (information about the maximum number of times a frame / PPDU can be transmitted).

[0327] Additionally or alternatively, the maximum number of times a frame / PPDU can be transmitted may be determined through negotiation between the AP and the STA.

[0328] Additionally or alternatively, back-off may continue to occur when the Timer for each channel expires, in which case the maximum number of frame transmissions set / defined for that channel may not apply.

[0329] Additionally or alternatively, if the number of times an STA has transmitted a frame / PPDU reaches the maximum number of times it can transmit a frame / PPDU, then the STA may wait for i) a frame addressed to the STA or ii) a frame not addressed to the STA, i.e., a frame for which it can set a NAV.

[0330] Additionally or alternatively, frames transmitted in Case #1 and Case #2 may have their Duration set to 0 to prevent other STAs from setting their NAVs in advance.

[0331] In addition, according to an embodiment of the present disclosure, an STA receiving a frame transmitted via an SCA may perform frame detection on the SCH even during the time when a NAV is set in the PCH. For example, if the STA has a frame to transmit, the STA may perform a backoff on the SCH, and if the STA does not have a frame to transmit, the STA may attempt to receive a frame addressed to itself on the SCH. In addition, the STA may perform NAV setting / resetting based on the value of the duration / ID field of the frame detected on the SCH.

[0332] Additionally or alternatively, the EDCA Parameter Set for each SCH on which back-off is performed may be configured as the EDCA Parameter Set in the PCH, the MU EDCA Parameter Set, or a new EDCA Parameter Set. This EDCA Parameter Set may be applied equally to all SCHs, or may be applied differently for each SCH.

[0333] Additionally or alternatively, a timer may be set for one or more SCHs performing backoff. In this case, different timers may be set individually for the transmitting STA (for transmitting frames via SCA) and the receiving STA (for receiving frames via SCA), or a common timer may be set. Here, the timer may be set from the start of the backoff. This timer may be transmitted from a management frame (e.g., a beacon frame) transmitted by the AP.

[0334] Additionally or alternatively, the maximum number of times a frame / PPDU can be transmitted may be determined through negotiation between the AP and the STA.

[0335] Additionally or alternatively, information about the maximum number of times a frame / PPDU can be transmitted on the SCH while the Timer is running (and / or information about the maximum number of times a frame / PPDU can be transmitted on the PCH) may be transmitted in a management frame (e.g., a beacon frame) transmitted by the AP. If the STA performing SCA is an AP, it can utilize the information transmitted by itself (information about the maximum number of times a frame / PPDU can be transmitted).

[0336] Additionally or alternatively, the maximum number of times a frame / PPDU can be transmitted may be determined through negotiation between the AP and the STA.

[0337] Additionally or alternatively, back-off may continue to occur when the Timer for each channel expires, in which case the maximum number of frame transmissions set / defined for that channel may not apply.

[0338] FIG. 17 illustrates the operation of a transmitting device for a secondary channel access method according to one embodiment of the present disclosure.

[0339] Figure 17 illustrates the operation of a transmitter based on the previously proposed methods. The example in Figure 17 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 17 may be omitted depending on the circumstances and / or settings.

[0340] Here, the transmitting device may be an AP or a non-AP STA, and the receiving device may be an AP or a non-AP STA. For convenience of explanation below, the transmitting device may be referred to as a first STA, and the receiving device may be referred to as a second STA.

[0341] Additionally, STA capability supporting secondary channel access operation can be defined (e.g., level 1, 2), in which case, the first STA and / or the second STA of FIG. 17 are assumed to be STAs having STA capability supporting secondary channel access operation.

[0342] Referring to FIG. 17, the first STA sets the NAV for the primary channel (i.e., sets / updates the NAV timer) based on the first frame received via a PPDU that is not an intra-BSS PPDU (e.g., i) an inter-BSS PPDU or ii) a PPDU that cannot be identified as an intra-BSS PPDU or an intra-BSS PPDU) (S1701).

[0343] The first STA attempts to transmit the second frame on one or more secondary channels other than the primary channel (S1702).

[0344] The number of times the second frame is attempted to be transmitted on the one or more secondary channels may be limited within a maximum number of transmissions on the secondary channel. Here, the first STA (i.e., in the case of a non-AP STA) may receive information on the maximum number of transmissions on the secondary channel from the AP through a beacon frame or a probe response frame. Alternatively, the first STA (i.e., in the case of an AP) may transmit information on the maximum number of transmissions on the secondary channel through a beacon frame or a probe response frame, and in this case, the information on the maximum number of transmissions on the secondary channel transmitted by the first STA may be applied.

[0345] In addition, the one or more secondary channels may include a first secondary channel on which a back-off procedure is performed by the first STA. That is, the first STA may perform a back-off procedure on the first secondary channel when the primary channel is in a BUSY state. In addition, the one or more secondary channels may further include a second secondary channel determined to be in an IDLE state based on a Clear Channel Assessment (CCA) after the back-off procedure for the first secondary channel.

[0346] Additionally, the second frame may include information that the primary channel has been punctured.

[0347] Additionally, the duration of the TXOP may be set so that the TXOP of the one or more secondary channels ends before the time at which the NAV for the primary channel expires. Here, if the time at which the NAV for the primary channel expires is not sufficient to set the TXOP of the one or more secondary channels, the first STA may not perform secondary channel access. That is, in this case, the first STA may not perform the backoff procedure for the first secondary channel.

[0348] If all attempts to transmit the second frame on the one or more secondary channels fail for the maximum number of transmissions of the secondary channels, the first STA may i) wait for reception of the frame and / or ii) perform a back-off procedure by switching to the primary channel.

[0349] In addition, a secondary channel timer may be set for the secondary channel, in which case the number of times the second frame is attempted to be transmitted on the one or more secondary channels may be limited within the maximum number of transmissions on the secondary channel before the secondary channel timer expires. Here, the first STA (i.e., in the case of a non-AP STA) may receive information on the maximum number of transmissions on the secondary channel and information on the secondary channel timer from the AP through a beacon frame or a probe response frame. Alternatively, the first STA (i.e., in the case of an AP) may transmit information on the maximum number of transmissions on the secondary channel and information on the secondary channel timer through a beacon frame or a probe response frame, in which case the information on the secondary channel timer transmitted by the first STA and the information on the maximum number of transmissions on the secondary channel may be applied.

[0350] If all attempts to transmit the second frame on the one or more secondary channels have failed for the maximum number of transmissions on the secondary channel and the secondary channel timer is running, the first STA may wait to receive the frame until the secondary channel timer expires.

[0351] Additionally, when the secondary channel timer expires, the first STA performs a back-off procedure for transmitting the second frame within the one or more secondary channels, and the maximum number of secondary channel transmissions may not be applied.

[0352] Meanwhile, if the NAV for the primary channel expires, secondary channel access may be terminated. In this case, after the NAV for the primary channel expires, the first STA may attempt to transmit the third frame on the primary channel within the maximum number of primary channel transmissions. In this case, the number of attempts to transmit the third frame on the primary channel may be limited within the maximum number of primary channel transmissions before the primary channel timer for the primary channel expires. In addition, here, the first STA (i.e., in the case of a non-AP STA) may receive information on the maximum number of primary channel transmissions from the AP through a beacon frame or a probe response frame. Alternatively, the first STA (i.e., in the case of an AP) may transmit information on the maximum number of primary channel transmissions through a beacon frame or a probe response frame, and in this case, the information on the maximum number of primary channel transmissions transmitted by the first STA may be applied.

[0353] Meanwhile, when the first STA attempts to transmit the second frame, it means that it constructs a PPDU including the second frame and attempts to transmit the PPDU.

[0354] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0355] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0356] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0357] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0358] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0359] The above-described STF-part may contain an STF sequence.

[0360] The above-described LTF portion may include a training field (i.e., an LTF sequence) for channel estimation.

[0361] The data portion described above contains user data and may contain packets for upper layers. That is, an MPDU (i.e., a second frame) may be included in the data portion.

[0362] For example, when supporting channel access operation on a secondary channel, the duration / ID field in the MAC header of a frame included in an MPDU (i.e., the second frame) may be set to a value including the time length of the frame exchange following the frame / PPDU transmitted excluding / puncturing the PCH. For example, the TXOP end time determined based on the value of the duration / ID field may be set before the end time of the NAV set on the primary channel.

[0363] The method described in the example of FIG. 17 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 receive a first frame via the transceiver(s) (106), set a NAV, and attempt to transmit a second frame on one or more secondary channels. Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 17 or the examples described above when executed by one or more processors (102).

[0364] FIG. 18 illustrates the operation of a receiving device for a secondary channel access method according to one embodiment of the present disclosure.

[0365] Figure 18 illustrates the operation of a receiving device based on the previously proposed methods. The example in Figure 18 is provided for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in Figure 18 may be omitted depending on the circumstances and / or settings.

[0366] Here, the transmitting device may be an AP or a non-AP STA, and the receiving device may be an AP or a non-AP STA. For convenience of explanation below, the transmitting device may be referred to as a first STA, and the receiving device may be referred to as a second STA.

[0367] Additionally, STA capability supporting secondary channel access operation can be defined (e.g., level 1, 2), in which case, the first STA and / or the second STA of FIG. 18 are assumed to be STAs having STA capability supporting secondary channel access operation.

[0368] Referring to FIG. 18, the second STA sets the NAV for the primary channel (i.e., sets / updates the NAV timer) based on the first frame received via a PPDU that is not an intra-BSS PPDU (e.g., i) an inter-BSS PPDU or ii) a PPDU that cannot be identified as an intra-BSS PPDU or an intra-BSS PPDU) (S1801).

[0369] The second STA receives a second frame on one or more secondary channels other than the primary channel (S1802).

[0370] Here, the first STA may attempt to transmit the second frame on one or more secondary channels excluding the primary channel. The number of times the second frame is attempted to be transmitted on the one or more secondary channels may be limited within the maximum number of transmissions on the secondary channel. Here, the first STA (i.e., in the case of a non-AP STA) may receive information on the maximum number of transmissions on the secondary channel from the AP through a beacon frame or a probe response frame. Alternatively, the first STA (i.e., in the case of an AP) may transmit information on the maximum number of transmissions on the secondary channel through a beacon frame or a probe response frame, and in this case, the information on the maximum number of transmissions on the secondary channel transmitted by the first STA may be applied.

[0371] In addition, the one or more secondary channels may include a first secondary channel on which a back-off procedure is performed by the first STA. That is, the first STA may perform a back-off procedure on the first secondary channel when the primary channel is in a BUSY state. In addition, the one or more secondary channels may further include a second secondary channel determined to be in an IDLE state based on a Clear Channel Assessment (CCA) after the back-off procedure for the first secondary channel.

[0372] Additionally, the second frame may include information that the primary channel has been punctured.

[0373] Additionally, the duration of the TXOP may be set so that the TXOP of the one or more secondary channels ends before the time at which the NAV for the primary channel expires. Here, if the time at which the NAV for the primary channel expires is not sufficient to set the TXOP of the one or more secondary channels, the first STA may not perform secondary channel access. That is, in this case, the first STA may not perform the backoff procedure for the first secondary channel.

[0374] Meanwhile, the second STA receiving the second frame means receiving a PPDU including the second frame.

[0375] Here, the PPDU may be configured to include a legacy part, a SIG part (e.g., U-SIG, UHR-SIG, etc.), an STF part (e.g., UHR-STF), an LTF part (e.g., UHR-LTF), and a data part.

[0376] All or part of any part (i.e., field) may be divided into multiple sub-parts / sub-fields. Each field (and its sub-fields) may be transmitted in units of 4us * N (where N is an integer). Additionally, a guard interval (GI) may be included. A common subcarrier frequency spacing value (delta_f=312.5 kHz / N or 312.5 kHz * N, where N=integer) may be applied to all of the fields, or a first delta_f may be applied to the first part (e.g., all legacy part, all / part of SIG part), and a second delta_f (e.g., a value smaller than the first delta_f) may be applied to all / part of the remaining parts.

[0377] Some of the fields described above may be omitted, and the order of the fields may be changed in various ways. For example, the subfields of the signal part may be placed before the STF part, and the remaining subfields of the SIG part may be placed after the STF part.

[0378] The legacy portion described above may include at least one of a conventional L-STF (Non-HT Short Training Field), L-LTF (Non-HT Long Training Field), and L-SIG (Non-HT Signal Field).

[0379] The SIG portion described above (e.g., including the U-SIG field, UHR-SIG field, etc.) may include various control information for the transmitted PPDU. For example, it may include the STF portion, the LTF portion, and control information for decoding data.

[0380] The above-described STF-part may contain an STF sequence.

[0381] The above-described LTF portion may include a training field (i.e., an LTF sequence) for channel estimation.

[0382] The data-part described above may include user data and may include packets for upper layers.

[0383] For example, when supporting channel access operation on a secondary channel, the duration / ID field in the MAC header of a frame included in an MPDU (i.e., the second frame) may be set to a value including the time length of the frame exchange following the frame / PPDU transmitted excluding / puncturing the PCH. For example, the TXOP end time determined based on the value of the duration / ID field may be set before the end time of the NAV set on the primary channel.

[0384] The method described in the example of FIG. 18 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 a first frame via the transceiver(s) (206) to set a NAV, and receive a second frame on one or more secondary channels. Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 18 or the examples described above when executed by one or more processors (202).

[0385] In conventional wireless LAN systems, if the medium for the primary channel is in a busy state (BUSY), the STA cannot use the secondary channel. However, in contrast, according to the secondary channel access method according to the examples of the present disclosure, the medium for the secondary channel can be used even if the medium for the primary channel is in a busy state (BUSY). Accordingly, the efficiency of medium use can be improved, and further, the effect of increasing wireless communication efficiency can be achieved.

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

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

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

[0389] 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. In a method performed by a station (STA: station) in a wireless LAN system, the method: A step of setting a network allocation vector (NAV) for a primary channel based on a first frame received via a PPDU (physical protocol data unit) other than an intra basic service set (BSS) PPDU (basic service set); and A step of attempting to transmit a second frame on one or more secondary channels other than the primary channel, A method wherein the number of attempts to transmit the second frame on the one or more secondary channels is limited to a maximum number of transmissions on the secondary channels.

2. In paragraph 1, A method wherein the one or more secondary channels include a first secondary channel on which a back-off procedure is performed by the STA.

3. In paragraph 2, A method wherein the at least one secondary channel further includes a second secondary channel determined to be in an IDLE state based on a Clear Channel Assessment (CCA) after the backoff procedure for the first secondary channel.

4. In paragraph 1, A method wherein the second frame includes information that the primary channel has been punctured.

5. In paragraph 1, A method wherein the duration of the transmission opportunity (TXOP) of the one or more secondary channels is set so that the transmission opportunity (TXOP) of the one or more secondary channels ends before the NAV for the primary channel expires.

6. In paragraph 1, A method wherein, based on all attempts to transmit the second frame on the one or more secondary channels failing for the maximum number of transmissions on the secondary channel, the STA i) waits for reception of the frame and / or ii) performs a back-off procedure by switching to the primary channel.

7. In paragraph 1, A method further comprising the step of receiving information on the maximum number of transmissions of the secondary channel from an access point (AP) through a beacon frame or a probe response frame.

8. In paragraph 1, A method wherein the number of attempts to transmit the second frame on the one or more secondary channels is limited to a maximum number of transmissions on the secondary channel before the secondary channel timer expires.

9. In paragraph 8, A method wherein, based on all attempts to transmit the second frame on the one or more secondary channels for the maximum number of transmissions on the secondary channel and the secondary channel timer being running, the STA waits to receive the frame until the secondary channel timer expires.

10. In paragraph 8, A method wherein, based on the expiration of the secondary channel timer, the STA performs a back-off procedure for transmitting the second frame within the one or more secondary channels, and the secondary channel maximum transmission number is not applied.

11. In paragraph 8, A method further comprising the step of receiving information about the maximum number of transmissions of the secondary channel and information about the secondary channel timer from an access point (AP) through a beacon frame or a probe response frame.

12. In paragraph 1, A method further comprising the step of: after the NAV for the primary channel expires, the STA attempts to transmit a third frame on the primary channel within the primary channel maximum transmission number.

13. In paragraph 12, A method wherein the number of attempts to transmit the third frame on the primary channel is limited to a maximum number of transmissions on the primary channel before the primary channel timer for the primary channel expires.

14. In paragraph 12, A method further comprising the step of receiving information on the maximum number of transmissions of the primary channel from an access point (AP) through a beacon frame or a probe response frame.

15. In a station (STA) device in a wireless LAN system, the device: 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: Set the network allocation vector (NAV) for the primary channel based on the first frame received via a PPDU (physical protocol data unit) other than the intra basic service set (BSS) PPDU (basic service set), and It is set to attempt transmission of the second frame on one or more secondary channels other than the primary channel, A device wherein the number of attempts to transmit the second frame on the one or more secondary channels is limited to a maximum number of transmissions on the secondary channels.

16. In a method performed by a station (STA) in a wireless LAN system, the method: A step of setting a network allocation vector (NAV) for a primary channel based on a first frame received via a PPDU (physical protocol data unit) other than an intra basic service set (BSS) PPDU (basic service set); and A method comprising the step of receiving a second frame on one or more secondary channels other than the primary channel.

17. In a station (STA) device in a wireless LAN system, the device: 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: Set the network allocation vector (NAV) for the primary channel based on the first frame received via a PPDU (physical protocol data unit) other than the intra basic service set (BSS) PPDU (basic service set), and A device configured to receive a second frame on one or more secondary channels other than the primary channel.

18. In a processing device configured to control a station (STA: station) in a wireless LAN system, the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions that, when executed by said one or more processors, perform a method according to any one of claims 1 to 13.

19. 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 device in a wireless LAN system to perform a method according to any one of claims 1 to 13.

Citation Information

Patent Citations

  • Transmission With Partial Bandwidth Spectrum Reuse In Wireless Communications

    US20210266960A1

  • Backoff management for intra-queue priority transmission in communication networks

    US20220174730A1

  • Communication apparatus and communication method

    US20230079334A1

Cited By

  • Communication method and communication devices

    WO2026137445A1

  • Communication method, communication device, and communication system

    WO2026148555A1