Method and device for performing channel access operation in wireless LAN system

Abstract

Disclosed are a method and device operating in a wireless LAN system. A method performed by a first station (STA) in a wireless LAN system, according to one embodiment of the present disclosure, comprises the steps in which: the first station switches from a primary channel to a first non-primary channel on the basis that a network allocation vector (NAV) is set on the primary channel; the first STA switches from the first non-primary channel to the primary channel before a target beacon transmission time (TBTT) on the basis of an overlap between the duration of the NAV and the TBTT; and the first STA receives a beacon frame from a second STA within the TBTT, wherein the NAV may be based on an inter-basic service set (BSS) physical layer protocol data unit (PPDU).

Description

Method and device for performing channel access operation in a wireless LAN system

[0001] The present disclosure relates to communication operations in a wireless local area network (WLAN) system, and more particularly, to a method and device for performing channel access operations in a next-generation wireless LAN system.

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

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

[0004] The technical problem of the present disclosure is to provide a method and device for performing a channel access operation in a wireless LAN system.

[0005] The technical problem of the present disclosure is to provide a method and device for performing non-primary channel access.

[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 embodiment of the present disclosure, the method comprises: switching from a primary channel to a first non-primary channel by a first station (STA) based on a network allocation vector (NAV) being set on the primary channel; switching from the first non-primary channel to the primary channel by the first STA before a target beacon transmission time (TBTT) based on an overlap between a duration of the NAV and a target beacon transmission time (TBTT); and receiving a beacon frame from a second STA by the first STA within the TBTT, wherein the NAV may be based on an inter-BSS (basic service set) physical layer protocol data unit (PPDU).

[0008] In one embodiment of the present disclosure, a method is provided, comprising: setting a network allocation vector (NAV) on a primary channel by a second station (STA); and transmitting a beacon frame to a first STA on the primary channel by the second STA within a target beacon transmission time (TBTT), wherein the NAV is based on an inter-BSS (basic service set) physical layer protocol data unit (PPDU), and based on an overlap of the NAV interval and the TBTT, a channel of the first STA can be switched from a first non-primary channel band to the primary channel band.

[0009] According to various embodiments of the present disclosure, a method and device for performing a channel access operation in a wireless LAN system can be provided.

[0010] According to various embodiments of the present disclosure, a method and apparatus for performing non-primary channel access may be provided.

[0011] According to various embodiments of the present disclosure, a method and apparatus for transmitting and receiving a beacon on a target beacon transmission time (TBTT) by STA(s) performing non-primary channel access may be provided.

[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 is a diagram for explaining a channel access method to which the present disclosure can be applied.

[0022] FIG. 9 is a flowchart illustrating a method performed by a first STA according to one embodiment of the present disclosure.

[0023] FIG. 10 is a flowchart illustrating a method performed by a second STA according to one embodiment of the present disclosure.

[0024] FIG. 11 is a diagram illustrating a basic NPCA process according to one embodiment of the present disclosure.

[0025] Figure 12 is a diagram illustrating issues that may arise when performing NPCA.

[0026] FIG. 13 and FIG. 14 are drawings for explaining a process of performing NPCA according to one embodiment of the present disclosure.

[0027] FIG. 15 is a diagram for explaining the operation when OBSS TWT SP and TBTT overlap, according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

[0040] A first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memories (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). Furthermore, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0041] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] Non-primary channel access procedure

[0130] In a basic wireless LAN system, a BSS operating channel may include one primary channel and one or more secondary channels (e.g., non-primary channels). In a basic wireless LAN system, channel access may be performed based on the primary channel. That is, when the primary channel is idle and the back-off counter (e.g., the back-off counter of the primary channel) is 0, frames may be transmitted through the primary channel and at least one secondary channel. To this end, all STAs may preferentially perform CCA based on the primary channel.

[0131] Therefore, the AP always includes the primary channel as an operating channel for transmitting management frames (e.g., beacon frames and probe response frames), and can announce the primary channel of the BSS. The above-described procedure has the advantage of establishing / defining that frame exchanges between all STAs and APs can be performed without interference.

[0132] However, if the above-described procedure is applied, if the state of the primary channel is BUSY or the state of the secondary channel is IDLE, there is a problem that at least one STA cannot perform an access procedure for the secondary channel, and thus efficiency is reduced from the perspective of medium use.

[0133] Figure 8 illustrates a channel access scheme based on a primary channel in an 80 MHz bandwidth. In describing the present disclosure, P20, S20, S40, S80, and S160 may each mean a primary 20 MHz channel, a secondary 20 MHz channel, a secondary 80 MHz channel, a 160 MHz channel, and a secondary 160 MHz channel, respectively.

[0134] As illustrated in FIG. 8, if P20 is in a BUSY state due to reasons such as performing CCA or setting NAV, the back-off counter value related to the primary channel does not decrease, and the STA can wait until the state of P20 transitions to idle. If the back-off counter value becomes 0 through the back-off process described above, the STA can transmit a frame after checking the channel states of S20 and S40 through CCA, etc. In FIG. 8, since the state of S40 is busy, the STA can transmit a frame corresponding to a 40 MHz PPDU through P20 and S20.

[0135] As described above, if P20 is in the BUSY state and S20 and S40 are in the IDLE state, the STA must wait even though S20 and S40 are in the IDLE state. This wastes 60 MHz of bandwidth and may reduce the efficiency of medium use. To address this issue, the following describes a method for accessing the secondary channel even when the primary channel is in the BUSY state.

[0136] In describing the present disclosure, a secondary channel may be expressed / replaced by a non-primary channel, and a non-primary channel may be expressed / replaced by an NPCA primary channel. An STA may include an AP (STA) or a non-AP STA.

[0137] FIG. 9 is a flowchart illustrating a method performed by a first STA according to an embodiment of the present disclosure. The first STA in FIG. 9 and FIG. 10 may be either a non-access point (AP) STA or an AP, and the second STA may be another non-AP STA or an AP. However, this is merely an embodiment, and each of the first STA and the second STA may be either a non-AP STA or an AP. For example, each of the first STA and the second STA may be expressed as an NPCA STA or an NPCA AP that performs NPCA.

[0138] Based on the network allocation vector (NAV) set on the primary channel, the first STA can switch from the primary channel to the first non-primary channel (S910). Here, the NAV (e.g., basic NAV) can be based on an inter-BSS PPDU.

[0139] Specifically, the first STA and / or the second STA may be included in the first BSS, and the third STA may be included in the second BSS. The third STA may transmit a specific PPDU to another STA (e.g., the fourth STA)(s) belonging to the second BSS. At this time, the first STA and the second STA may detect (e.g., listen to) the transmission of the specific PPDU by the third STA. That is, the first STA and the second STA may be in an area where they can detect the transmission and reception of the PPDU by the third STA.

[0140] The first STA and / or the second STA may classify a specific PPDU transmitted by the third STA as an inter-BSS PPDU. Based on the classification of the specific PPDU transmitted by the third STA as an inter-BSS PPDU by the first STA and / or the second STA, an NAV may be set on the primary channel. A back-off operation may be performed on the first non-primary channel by the first STA during the NAV.

[0141] Prior to step S910, the first STA may transmit to the second STA at least one of a first time required for the first STA to switch from the primary channel to the first non-primary channel or a second time required for the first STA to switch from the first non-primary channel to the primary channel. As an example of the present disclosure, the first STA may transmit to the second STA a larger value of the first time or the second time, but is not limited thereto.

[0142] Additionally or alternatively, the second STA may transmit to the first STA at least one of a third time required for the second STA to switch from the primary channel to the first non-primary channel or a fourth time required for the second STA to switch from the first non-primary channel to the primary channel. As an example of the present disclosure, the second STA may transmit to the first STA a greater value of the third time or the fourth time, but is not limited thereto.

[0143] At least one of the first time, the second time, the third time and the fourth time may be configured / determined in units of a specific time (e.g., 4 us).

[0144] For example, a first STA or / and a second STA that have activated the NPCA operation may include an NPCA operation information field in the UHR operation element.

[0145] As an example of the present disclosure, a first STA may transmit capability information related to whether the first STA supports an access operation for a first non-primary channel to a second STA. Additionally or alternatively, the first STA may receive capability information related to whether the second STA supports an access operation for the first non-primary channel from the second STA. The capability information may be included in an UHR capability element, and the UHR capability element may be included in a PPDU transmitted by the first STA and / or the second STA.

[0146] Based on the overlap of the NAV duration and the target beacon transmission time (TBTT), the first STA can switch from the first non-primary channel to the primary channel before the TBTT (S920).

[0147] For example, assume that the TBTT for transmitting a beacon frame by a second STA is included within the NAV interval. The first STA may end the TXOP before the TBTT and switch from the first non-primary channel to the primary channel. That is, the first STA may switch from the first non-primary channel to the primary channel before the TBTT. Here, the holder of the TXOP on the first non-primary channel may be either the first STA or the second STA.

[0148] And, the first STA can receive a beacon frame from the second STA within the TBTT (S930).

[0149] Since the TXOP on the primary channel is terminated before the TBTT and the first STA also switches to the primary channel, the first STA can receive a beacon frame from the second STA during the TBTT.

[0150] Additionally or alternatively, based on the setting of an overlapping basic service set (OBSS) target wake time (TWT) special period (SP), the first STA may perform a back-off operation on the first non-primary channel during the OBSS target wake time (TWT) SP.

[0151] Here, NAV and OBSS TWT SP may be set simultaneously or with some overlap, but this is not limited thereto. The NAV setting step according to S910 may be omitted and only OBSS TWT SP may be set. If the NAV setting step is omitted, the overlap between NAV and TBTT in step S920 may also be omitted.

[0152] As an example of the present disclosure, switching from a first non-primary channel to a primary channel can be completed within the OBSS TWT SP. Furthermore, as described above, switching from the first non-primary channel to the primary channel can be completed before the TBTT. The first STA can initiate the switching operation by considering the channel switch delay time from the primary channel to the first non-primary channel.

[0153] The method described in the example of FIG. 9 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 switch from the primary channel to a first non-primary channel based on the NAV being set on the primary channel. Based on the overlap of the NAV interval and the TBTT, the one or more processors (102) may switch from the first non-primary channel to the primary channel before the TBTT. The one or more processors (102) may receive a beacon frame from a second STA via one or more transceivers (106) within the TBTT.

[0154] Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 9 or the examples described below when executed by one or more processors (102).

[0155] FIG. 10 is a flowchart illustrating a method performed by a second STA according to one embodiment of the present disclosure.

[0156] The second STA may set an NAV on the primary channel (S1010). As described above, the NAV may be based on an inter-BSS PPDU. For example, the second STA may be included in the first BSS, and a third STA included in the second BSS may transmit a specific PPDU to another STA belonging to the second BSS. Based on whether a specific PPDU listened / detected by the first STA and / or the second STA is classified as an inter-BSS PPDU by the first STA and / or the second STA, the second STA may set an NAV on the primary channel.

[0157] Based on the NAV being set on the primary channel, the channel of the first STA can be switched from the primary channel band to the first non-primary channel band.

[0158] The second STA can transmit a beacon frame to the first STA on the primary channel within the TBTT (S1020).

[0159] Here, based on the overlapping of the NAV interval and TBTT, the channel of the first STA can be switched from the first non-primary channel band to the primary channel band.

[0160] The method described in the example of FIG. 10 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 set an NAV on a primary channel. The one or more processors (202) may transmit a beacon frame to the first STA via one or more transceivers (206) on the primary channel within a TBTT.

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

[0162] Below, we will specifically describe the parameters related to non-primary channels and the procedure for performing non-primary channels.

[0163] Example 1

[0164] Example 1 relates to a capability related to non-primary channel (or secondary channel) access (NPCA) of an STA.

[0165] Non-AP STAs and APs can exchange capability information related to NPCA with each other. For example, a non-AP STA can transmit capability information related to NPCA to an AP via a probe request frame and / or a (re)association request frame. The AP can transmit capability information related to NPCA to the AP via a beacon frame, a probe response frame, and a (re)association request frame. The capability information can be included in the (UHR) capability element / field of each of the above-described frame(s).

[0166] As an example of the present disclosure, a capability related to NPCA of a STA may include information / fields (e.g., an NPCA supported field) related to whether the STA can support NPCA operation.

[0167] Additionally or alternatively, capability information related to NPCA may include information on whether the AP can decode frames on a non-primary channel (or / and information on whether the AP can perform CCA (e.g., preamble detection) to identify wireless LAN frames transmitted and received on the primary channel). Through this, the AP and / or STA can set additional NAVs (e.g., intra-BSS NAV or basic NAV, etc.) even on the non-primary channel. Here, the intra-BSS NAV collectively refers to a NAV that is updated by receiving a frame transmitted by an STA of the intra-BSS.

[0168] Additionally or alternatively, capability information related to NPCA may be categorized by level as described below:

[0169] Capability information of level 0 (No Back-off on non-primary channel): This may indicate that the STA performs basic CCA on a non-primary channel. Here, the CCA may include a CCA capable of detecting a wireless LAN signal (e.g., guard interval detection (GID)) and / or a CCA capable of detecting a signal above a certain strength (e.g., energy detection (ED)).

[0170] Level 1 capability information (Back-off on a non-primary channel at a time): This may include information on whether the STA can perform PD on one non-primary channel at a time.

[0171] Level 2 capability information (Back-off on non-primary channels at the same time): This may include information on whether the STA can perform PD on multiple non-primary channels at the same time.

[0172] An STA can perform NPCA based on capability information for each level. For example, if Level 1 capability information is transmitted, the STA can perform PD on one non-primary channel at a time. Furthermore, if Level 2 capability information is transmitted, the STA can perform PD on multiple non-primary channels.

[0173] Example 2

[0174] Example 2 is about the basic procedure of NPCA.

[0175] If an intra-BSS NAV is set on the primary channel, the STA may, but is not limited to, not perform NPCA. For example, when an AP exchanges frames with a specific STA within a TXOP (e.g., a TXOP in which the AP is the TXOP holder), an intra-BSS NAV may be set for the other STA based on the primary channel. In this case, if an STA with an intra-BSS NAV set accesses a non-primary channel and transmits a frame to the AP, the AP may not receive the frame transmitted by the STA with the intra-BSS NAV set during a transmission operation (e.g., DL data, ACK transmission operation, etc.). Therefore, the STA may perform NPCA if a basic NAV is set on the primary channel.

[0176] Figure 11 illustrates the basic NPCA process as an embodiment of the present disclosure.

[0177] If the basic NAV is set while performing back-off at P20, the STA may perform back-off at S20 at the time when the basic NAV is set. When the STA switches from P20 to S20 to perform PD, a switching delay may occur.

[0178] For example, the CCA method in S20 may differ from the CCA method in P20, and STA may perform CCA for all levels described in Example 1.

[0179] If a neighboring STA with the same or similar operating channel as the STA transmits a frame through an idle channel without performing backoff, the frame may collide with the frame transmitted by the STA. Therefore, the STA can prevent channel waste by switching to S20 and then performing backoff. The STA can transmit a PPDU (e.g., a PPDU containing a frame) through S20 and S40 (within the TXOP it has acquired).

[0180] Example 2-1

[0181] Example 2-1 relates to a TXOP setting method related to NPCA in Example 2.

[0182] When the underlying NAV expires on P20, the STA may perform a CCA for P20. Accordingly, the STA may set the end time of the TXOP (on at least one non-primary channel) to a time before the underlying NAV expires.

[0183] If the TXOP end time is set after the basic NAV expires, legacy STAs, etc. can transmit frames via P20, which may cause the AP to not receive frames transmitted by STAs within the TXOP. In addition, if the TBTT is set in the middle of the basic NAV, the AP may have to prepare to transmit a beacon immediately after the basic NAV, which may cause the problem.

[0184] For example, if there is not enough time to set up a TXOP (e.g., if the end time of the TXOP must be set after the time when the underlying NAV expires), the STA may not perform frame transmission (on at least one non-primary channel).

[0185] Example 2-2

[0186] Example 2-2 relates to a frame transmission method according to NPCA in Example 2.

[0187] In a basic wireless LAN system, if P20 is in an idle state, the STA can transmit frames after performing puncturing based on the state of at least one non-primary channel (e.g., busy or idle). Therefore, for NPCA, the busy state of P20 must be considered, and the rules described below can be applied.

[0188] As an example of the present disclosure, if the state of P20 is busy, P20 may be punctured by the STA, and other non-primary channel(s) whose channel state is busy based on S20 may also be punctured by the STA. In addition, the STA may transmit a frame through the non-primary channel(s) whose channel state is idle.

[0189] As an example, FIG. 11 illustrates a case where all three 20 MHz channels (e.g., S20 and S40) are idle, and an STA can transmit an 80 MHz PPDU (including a MAC frame), which may include information / signaling indicating that P20 has been punctured.

[0190] Example 2-3

[0191] Example 2-3 relates to operations related to channel switch delay occurring in the NPCA process described above.

[0192] When STA(s) switch the channel performing back-off from P20 to S20, a channel switch delay may occur. In describing the present disclosure, "APswichTimeSP" and "STAswitchTimeSP" each mean the time it takes for the AP and STA to switch the channel performing back-off from P20 to S20. However, this is only an example, and the expression indicating the channel switch time may be changed. "APswichTimeSP" and "STAswitchTimeSP" each may be set / indicated as a value (e.g., a multiple of the unit time, etc.) based on a certain unit time (e.g., 32us, 64us).

[0193] Additionally, a channel switch delay may also occur when switching a channel performing a back-off from S20 to P20. If the channel switch delay (or time) from P20 to S20 and the channel switch delay (or time) from S20 to P20 are different, each of the non-AP STAs and / or the AP may announce the channel switch time. For example, the non-AP STA may transmit its channel switch delay from P20 to S20 and its channel switch delay from S20 to P20 to the AP. As another example, the AP may transmit its channel switch delay from P20 to S20 and its channel switch delay from S20 to P20 to the non-AP STA.

[0194] As another example of the present disclosure, each of the STAs and / or the AP can announce a longer value of the channel switch delay from P20 to S20 and the channel switch delay from S20 to P20. That is, each of the non-AP STAs (or / and the AP) only transmits to the AP (or / and the non-AP STA) the longer value of its channel switch delay from P20 to S20 and the channel switch delay from S20 to P20, thereby reducing signaling overhead.

[0195] Example 3

[0196] Example 3 relates to a method for managing TBTT when performing the above-described NPCA.

[0197] When NPCA is performed by an STA, if the TBTT is included in the basic NAV set by the OBSS PPDU transmission, a problem may occur with the AP's beacon frame. Specifically, as illustrated in FIG. 12, if the TBTT is included during the period for which the basic NAV is set, the STA(s) may not recognize the reception of the CF (contention free)-end frame at P20 as they proceed with channel access on the non-primary channel(s) associated with the back-off. Accordingly, a problem may occur in which the AP cannot transmit a beacon frame in the TBTT included in the basic NVA.

[0198] In describing the present disclosure, a CF-END frame may be transmitted to truncate a TXOP interval. Accordingly, the duration field in the CF-END frame may be set to 0, but is not limited thereto. An STA that receives a CF-END frame may reset its NAV.

[0199] The STA(s) performing NPCA may perform at least one of the following embodiments 3-1, 3-2, and 3-3, taking into account TBTT.

[0200] Example 3-1

[0201] Example 3-1 relates to a method in which STA(s) performing NPCA switch from S20 back to P20 before TBTT.

[0202] Specifically, as the STA performs NPCA, a TXOP may be established by the STA on at least one non-primary channel. The STA may switch from at least one non-primary channel back to the primary channel after completing the TXOP before the TBTT (i.e., the first TBTT after the basic NAV is established). If the basic NAV expires or is reset, the AP may transmit a beacon frame to the STA within the scheduled TBTT.

[0203] Additionally or alternatively, an STA performing an EDCA procedure without setting / holding a TXOP may also switch to P20 from at least one non-primary channel.

[0204] Additionally or alternatively, when switching from at least one non-primary channel to P20, the AP may not schedule a beacon frame transmission in the TBTT if the underlying NAV has not expired or been reset.

[0205] Example 3-2

[0206] Example 3-2 relates to a method of not switching to a non-primary channel (e.g., S20) when TBTT is included in the basic NAV.

[0207] As an example of the present disclosure, as illustrated in FIG. 13, if TBTT is included in the basic NAV, the STA(s) may remain on P20 without switching to a non-primary channel (e.g., S20). For example, the STA(s) may reset the configured basic NAV when a CF-End frame is received while performing frame decoding on P20. In addition, the AP may transmit a beacon frame to the STA as it performs a back-off on the TBTT.

[0208] Example 3-3

[0209] Example 3-3 relates to a method of not switching back from a non-primary channel (e.g., S20) to a primary channel (e.g., P20) even if the underlying NAV includes a TBTT.

[0210] Specifically, an STA can perform NPCA until the primary NAV expires without switching back from a non-primary channel (e.g., S20) to the primary channel even if the primary NAV includes a TBTT. The STA can switch back to the primary channel before the primary NAV expires, and the AP can schedule the beacon frame first in its transmission queue.

[0211] Additionally or alternatively, as illustrated in FIG. 14, the AP may schedule the beacon frame in its transmission queue before other frames (e.g., data frames). Accordingly, even if the AP fails to transmit the beacon frame within the specified / scheduled TBTT, it can transmit the beacon frame first when the STA switches from the non-primary channel to the primary channel.

[0212] Additionally or alternatively, if the DTIM (delivery traffic indication map) count value of the beacon frame is 0, the AP may schedule and transmit the broadcast frame and group-addressed frame along with the beacon frame first on the transmission queue. A DTIM count value of 0 of the beacon frame may mean / indicate that the broadcast or group-addressed frame is transmitted after the beacon frame.

[0213] Example 4

[0214] Example 4 relates to a procedure for OBSS TWT related to NPCA.

[0215] As described above, a TXOP-based NPCA scheme may be applied, in which NPCA is performed only until the primary NAV set by OBSS traffic transmission expires. That is, when an STA receives a PPDU containing a frame from another BSS (e.g., an OBSS PPDU), a NAV may be set on the primary channel.

[0216] As another example, as illustrated in FIG. 15, when SP-based NPCA is applied that performs back-off on a non-primary channel (e.g., S20) rather than a primary channel (e.g., P20) during an OBSS TWT SP period, the STA may perform back-off on the non-primary channel until the OBSS TWT SP ends. Then, the STA may switch from the non-primary channel to the primary channel when the OBSS TWT SP ends.

[0217] However, when the SP-based NPCA described above is applied, there is a problem that the STA can perform backoff on the non-primary channel even when the primary channel is idle. In addition, if the TBTT is included during the OBSS TWT SP, there may be a problem that the AP cannot transmit a beacon frame until the OBSS TWT SP ends.

[0218] Therefore, if a TBTT is included in the OBSS TWT SP section, the STA(s) performing NPCA during the OBSS TWT SP may not switch from the non-primary channel to the primary channel after the OBSS TWT SP ends. The STA(s) may initiate switching to the primary channel by considering the channel switching delay that occurs when switching from their non-primary channel to the primary channel. Accordingly, the STA(s) may complete switching to the primary channel before the TBTT, and the AP may transmit a beacon frame at the scheduled TBTT.

[0219] Example 5

[0220] Example 5 relates to the process of STA for NPCA.

[0221] In one embodiment of the present disclosure, an STA performing NPCA may transmit a frame / PPDU on a non-primary channel even during the time when a NAV is set on the primary channel.

[0222] For example, an STA may transmit a frame / PPDU with the primary channel excluded / punctured on one or more non-primary channels in an IDLE state determined based on i) back-off performed on one or more non-primary channels and ii) CCA results of one or more non-primary channels for which back-off was not performed.

[0223] Additionally or alternatively, a TXOP starting with a frame / PPDU transmission on a non-primary channel may be configured to end before the NAV on the primary channel ends.

[0224] The TXOP length can be set / indicated through the duration / ID field of the corresponding frame. For example, the value of the duration / ID field can be set to a value corresponding to the time required for the exchange of the frame / PPDU following the corresponding frame / PPDU (including the interframe gap (IFS)).

[0225] Additionally or alternatively, the EDCA parameter set for each non-primary channel on which back-off is performed may be set to the EDCA parameter set of the primary channel, the MU EDCA parameter set, or a new EDCA parameter set. The EDCA parameter set may be applied equally or differently to all non-primary channels.

[0226] In the present disclosure, an STA receiving a frame transmitted via NPCA can perform frame detection on a non-primary channel even during the time when NAV is set on the primary channel.

[0227] For example, an STA may perform backoff on a non-primary channel when it has a frame to transmit, or may attempt to receive a frame addressed to it on a non-primary channel even when it has no frame to transmit. Furthermore, an STA may perform NAV setting / resetting based on the value of the interval / ID field of a frame detected on a non-primary channel.

[0228] Additionally or alternatively, the EDCA parameter set for each non-primary channel on which back-off is performed may be set to the EDCA parameter set of the primary channel, the MU EDCA parameter set, or a new EDCA parameter set. The EDCA parameter set may be applied equally or differently to all non-primary channels.

[0229] Additionally or alternatively, as illustrated in FIG. 13, while the basic NAV is set, if a TBTT is scheduled, it may remain at P20 without switching to S20.

[0230] Additionally or alternatively, while the basic NAV is being established, if a TBTT is expected, the STA may switch to S20. Furthermore, the STA may complete the TXOP before the expected TBTT and switch from S20 to P20. Additionally or alternatively, STA(s) performing EDCA without catching the TXOP may also switch from S20 to P20 before the expected TBTT.

[0231] A non-AP STA and / or AP may perform at least one of the above-described embodiments 1, 2, 2-1, 2-2, 2-3, 3, 3-1, 3-2, 3-3, 4, and 5. That is, the above-described embodiments may be combined, and only one specific embodiment may be applied.

[0232] By the above-described embodiments of the present disclosure, STA(s) performing NPCA can perform various operations considering TBTT, and accordingly, beacon frame transmission / reception in TBTT of AP can proceed more efficiently.

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

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

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

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

Claims

1. A step of switching from the primary channel to a first non-primary channel by a first station (STA) based on a network allocation vector (NAV) being set on the primary channel; A step of switching from the first non-primary channel to the primary channel before the TBTT by the first STA based on the overlap of the duration of the NAV and the target beacon transmission time (TBTT); and A step of receiving a beacon frame from a second STA by the first STA within the TBTT, The above NAV is a method based on an inter-BSS (basic service set) physical layer protocol data unit (PPDU).

2. In paragraph 1, The above first STA is included in the first BSS, A method in which a specific PPDU transmitted by a third STA included in a second BSS is classified by the inter-BSS by at least one of the first STA or the second STA.

3. In paragraph 2, A method wherein the NAV is set on the primary channel based on the specific PPDU being classified as the inter-BSS PPDU by at least one of the first STA or the second STA.

4. In paragraph 1, A method wherein a back-off operation is performed on the first non-primary channel during the NAV by the first STA.

5. In paragraph 1, The transmission opportunity (TXOP) on the first non-primary channel ends before the TBTT, A method wherein the first STA is a holder of the TXOP.

6. In paragraph 1, A method wherein at least one of a first time required to switch from the primary channel to the first non-primary channel or a second time required to switch from the first non-primary channel to the primary channel is transmitted from the first STA to the second STA.

7. In paragraph 6, A method in which a greater value of the first time or the second time is transmitted from the first STA to the second STA.

8. In paragraph 1, A method in which a back-off operation is performed on the first non-primary channel by the first STA during the OBSS TWT SP based on the setting of an OBSS (overlapping basic service set) target wake time (TWT) special period (SP).

9. In paragraph 8, A method wherein switching from the first non-primary channel to the primary channel is completed within the OBSS TWT SP.

10. In paragraph 1, A method in which capability information related to whether access operation for the first non-primary channel is supported is transmitted from the first STA to the second STA.

11. In paragraph 1, The above first STA is either a non-access point (AP) STA or an AP, The method wherein the second STA is another one of the non-AP STA or the AP.

12. In the first station (STA), the first STA: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Based on a network allocation vector (NAV) set on the primary channel, switching from the primary channel to a first non-primary channel by a first station (STA); Based on the overlap of the duration of the NAV and the target beacon transmission time (TBTT), switching from the first non-primary channel to the primary channel before the TBTT by the first STA; and The beacon frame is set to be received by the first STA from the second STA through the one or more transceivers within the TBTT, The above NAV is a first STA based on an inter-BSS (basic service set) physical layer protocol data unit (PPDU).

13. A step of setting a network allocation vector (NAV) on a primary channel by a second station (STA); and A step of transmitting a beacon frame to the first STA by the second STA on the primary channel within a target beacon transmission time (TBTT), The above NAV is based on the inter-BSS (basic service set) physical layer protocol data unit (PPDU), A method in which, based on the overlapping of the NAV interval and the TBTT, the channel of the first STA is switched from the first non-primary channel band to the primary channel band.

14. In the second station (STA), the second STA: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Setting a network allocation vector (NAV) on the primary channel; and Transmitting a beacon frame to the first STA via the one or more transceivers on the primary channel within the target beacon transmission time (TBTT), The above NAV is based on the inter-BSS (basic service set) physical layer protocol data unit (PPDU), A second STA, wherein the channel of the first STA is switched from the first non-primary channel band to the primary channel band based on the overlapping of the above NAV interval and the above TBTT.

15. In a processing device configured to control a station (STA) in a wireless local area network (WLAN) 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 for performing a method according to any one of claims 1 to 11 based on execution by said one or more processors.

16. 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 11.

Images