Method and device for NDP sounding in a wireless LAN-based system

Abstract

Disclosed are a method and device for NDP sounding in a wireless LAN system. The method according to an embodiment of the present disclosure may comprise the steps in which: an STA receives an NDP announcement frame from a first AP; and the STA transmits a frame including channel state information to the first AP.

Description

NDP sounding method and device in wireless LAN system

[0001] The present disclosure relates to a method and device for sounding null data PPDU (physical protocol data unit) (NDP: null data PPUD) in a wireless local area network (WLAN) system.

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

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

[0004] The technical problem of the present disclosure is to provide an NDP sounding method and device.

[0005] An additional technical challenge of the present disclosure is to provide an NDP sounding method and device for obtaining channel information for an overlapping basic service set (OBSS) STA in a wireless LAN system supporting multi-AP (multi-access point) operation.

[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] A method according to one aspect of the present disclosure may include: receiving, by a station (STA), a null data PPDU (physical protocol data unit) (NDP: null data PPDU) announcement frame from a first access point (AP); and transmitting, by the STA, a frame including channel state information to the first AP. The NDP announcement frame includes a plurality of STA information fields, and a variant of the NDP announcement frame may be identified by at least one STA information field among the plurality of STA information fields.

[0008] A method according to an additional aspect of the present disclosure may include: transmitting, by a first access point (AP), a null data PPDU (physical protocol data unit) (NDP) announcement frame to a station (STA); and receiving, by the first AP, a frame including channel state information from the STA. The NDP announcement frame includes a plurality of STA information fields, and a variant of the NDP announcement frame may be identified by at least one STA information field among the plurality of STA information fields.

[0009] According to the present disclosure, it is possible to obtain channel information for an OBSS STA as well as channel information for a BSS STA.

[0010] In addition, according to the present disclosure, multi-AP (multi access point) operation can be smoothly supported by acquiring channel information for an OBSS STA.

[0011] In addition, according to the present disclosure, frequency resources can be efficiently utilized as they can be recycled according to a spatial reuse technique in which multiple BSSs cooperate.

[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] Figure 8 illustrates an exemplary format of an NDP announcement frame to which the present disclosure can be applied.

[0022] FIG. 9 illustrates an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0023] FIG. 10 illustrates an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0024] FIG. 11 illustrates an STA information field of an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0025] FIG. 12 illustrates an STA information field of an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0026] FIG. 13 is a diagram illustrating the operation of an STA for an NDP sounding method according to one embodiment of the present disclosure.

[0027] FIG. 14 is a diagram illustrating the operation of an AP for an NDP sounding method 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, are not used to limit the components, and do not limit the order or importance of components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

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

[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). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless LAN technology (e.g., IEEE 802.11 series). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[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 restriction 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] Null data PPDU (NDP) announcement (NDPA) frame

[0130] In a wireless LAN system, a sounding procedure / protocol is used to determine channel state information. A beamformer STA requesting channel state information can transmit a training signal to beamformee STA(s). The beamformee STA can measure the channel using the training signal (e.g., sounding NDP) and feed back an estimate of the channel state to the beamformer STA. The beamformer STA can derive a steering matrix or beamforming matrix using the received estimate.

[0131] A beamforming STA can provide feedback on channel status estimates to the beamformer STA via a compressed beamforming / CQI (channel quality indication) reporting frame. The information provided may include single-user (SU) feedback, multi-user (MU) feedback, and CQI feedback.

[0132] The beamformer STA may transmit an NDP announcement and an NDP to the beamformee(s), and receive feedback information from the beamformee STA(s). Additionally or alternatively, the beamformer STA may transmit an NDP announcement and an NDP to the beamformee(s), and transmit a beamforming report poll (BFRP) or a BFRP trigger to the beamformee(s), and receive feedback information from the beamformee(s).

[0133] The NDP Announcement (NDPA) frame can have multiple types / variants. For example, the NDP Announcement frame can be composed of various formats such as the VHT NDP Announcement frame, the HE NDP Announcement frame, and the EHT NDP Announcement frame. These formats can be distinguished by the NDP Announcement Variant subfield within the Sounding Dialog Token field.

[0134] Figure 8 illustrates an exemplary format of an NDP announcement frame to which the present disclosure can be applied.

[0135] An NDP announcement frame may contain one or more STA information (Info) fields. If the NDP announcement frame contains only one STA Info field, the RA (receiver address) field may be set to the address of an STA capable of providing feedback. If the NDP announcement frame contains multiple STA Info fields, the RA field may be set to a broadcast address.

[0136] The TA (transmitter address) field may be set to the address of the STA transmitting the NDP announcement frame, or may be set to the bandwidth signaling TA of the STA transmitting the NDP announcement frame. For example, in a non-HT or non-HT duplicate format, if the scrambling sequence (or the scrambling sequence and service field) includes parameters for the channel bandwidth, the TA field may be set to the bandwidth signaling TA.

[0137] Among the eight bits (B0-B7) of the Sounding Dialog Token field, the first two bits (B0 and B1) can be used to indicate the type / variant of the NDP announcement frame. For example, for VHT or HE, B0 can have a value of 0, and if the value of B1 is 0, it can indicate a VHT NDP announcement frame, and if the value of B1 is 1, it can indicate a HE NDP announcement frame. For example, an EHT NDP announcement frame can correspond to the case where the values ​​of B0 and B1 are both set to 1. If the value of B0 is 1 and the value of B1 is 0, it can correspond to a ranging NDP announcement frame.

[0138] For VHT STA, the first two bits (B0 and B1) of the Sounding Dialog Token field are defined as reserved, so VHT STA can recognize the Sounding Dialog Token Number field of bits B2-B7 regardless of the values ​​of B0 and B1.

[0139] For VHT STAs, the first two bits (B0 and B1) of the Sounding Dialog Token field are defined as reserved. Therefore, VHT STAs can recognize the Sounding Dialog Token Number field of bits B2-B7, regardless of the values ​​of B0 and B1.

[0140] For HE STA, the first bit (B0) of the Sounding Dialog Token field is defined as reserved, and if the value of the second bit (B1) is 0, it indicates a VHT NDP announcement frame, and if the value of B1 is 1, it indicates a HE NDP announcement frame. Therefore, HE STA can recognize the Sounding Dialog Token Number field of bits B2-B7 when the value of B1 is 1, regardless of the value of B0.

[0141] The Sounding Dialog Token Number subfield (bit positions B2-B7) may contain a value to identify the NDP announcement frame selected by the beamformer.

[0142] An NDP announcement frame may contain n STA Info fields, where n is an integer greater than or equal to 1. A single STA Info field has a size of K octets, where K=2 for a VHT NDP announcement frame and K=4 for a HE NDP announcement frame or an EHT NDP announcement frame.

[0143] As in the example of Fig. 8(a), the STA Info field of the VHT NDP announcement frame may include AID12, feedback type, and Nc index subfields.

[0144] The AID12 subfield contains the 12 least significant bits (LSBs) of the AID of the STA that is expected to process the subsequent NDP and prepare sounding feedback.

[0145] The feedback type subfield indicates the type of feedback required, with a value of 0 corresponding to SU and a value of 1 corresponding to MU.

[0146] The Nc index subfield indicates the number of columns (i.e., Nc) in the compressed beamforming feedback matrix minus 1 (i.e., Nc-1) when the feedback type is MU. In the case of SU, the Nc index field is reserved.

[0147] The example in Fig. 8(b) shows the format of the STA Info field of the HE NDP announcement frame when the value of the AID11 field is not a specific value (e.g., 2047).

[0148] A value of the AID11 subfield other than a specific value (e.g., 2047) contains the 11 LSBs of the AID of the STA that is expected to process the subsequent NDP and prepare sounding feedback.

[0149] The partial bandwidth information (partial BW Info) subfield may include a 7-bit (B0-B6) RU start index and a 7-bit (B7-B13) RU end index. The RU index may be determined according to the bandwidth of the NDP announcement frame, and its unit may be a 26-tone RU. For example, to indicate a 26-tone RU index X, the value of the start / end RU index subfield may be set to X-1.

[0150] The feedback type and Ng subfield, in combination with the codebook size subfield, may indicate whether SU / MU / CQI feedback is requested, Ng=4 or 16, and quantization resolution for trigger-based (TB) sounding. For non-TB sounding, the feedback type and Ng subfield and the codebook size subfield may indicate SU or CQI.

[0151] The disambiguation subfield may be set to 1 to help non-HE STAs (e.g., VHT STAs) avoid misinterpreting the field as an AID field.

[0152] The Nc subfield is set to a value of Nc-1. When the feedback type is SU or MU, Nc corresponds to the number of columns in the compressed beamforming feedback matrix, and when the feedback type is CQI, Nc may correspond to the number of STSs (space-time streams). For NDP announcement frames that have AID11 subfield values ​​other than 2047 and are individually addressed to a single STA, the Nc subfield may be reserved.

[0153] The example in Fig. 8(c) shows the format of the STA Info field of the HE NDP announcement frame when the value of the AID11 field is a specific value (e.g., 2047).

[0154] The disallowed subchannel bitmap subfield indicates the 20 MHz subchannel(s) and 242-tone RU(s) present in the sounding NDPs announced by the NDP announcement frame, and the 242-tone RU(s) to be included in the requested sounding feedback. The lowest numbered bit of the disallowed subchannel bitmap corresponds to the 20 MHz subchannel with the lowest frequency among all 20 MHz subchannels within the BSS bandwidth. Each subsequent bit in the bitmap corresponds to the next higher 20 MHz subchannel. A bit set to 1 in the bitmap may indicate that no energy is present in the sounding NDP associated with the NDP announcement frame. For each disallowed 20 MHz subchannel, the 242-tone RU that is closest in frequency to that 20 MHz subchannel may be disallowed for PPDUs using that particular tone plan. STA(s) addressed by the NDP announcement frame shall not include tones from disallowed 242-tone RUs when determining the average SNR of STS 1 through Nc in generating the requested sounding feedback. If a 20 MHz subchannel and its corresponding 242-tone RU are allowed, the corresponding bit in the bitmap shall be set to 0.

[0155] The example in Fig. 8(d) shows the format of the STA Info field of the EHT NDP announcement frame.

[0156] The AID11 subfield can be defined as shown in Table 1. Basically, the AID11 subfield contains the identifier of the STA that is expected to process the subsequent NDP and prepare sounding feedback.

[0157] AID Subfield Value DescriptionNDP Announcement Frame Type / VariantApplicability0- STA Info field addressed to the associated AP or mesh AP or IBSS STA. Applicable to all variants1-2007- If the NDP announcement frame is not a ranging variant, the STA Info field is addressed to the associated STA that has an AID equal to the value in the AID11 subfield.- If the NDP announcement frame is a ranging variant, the STA Info field is addressed to the non-associated STA or associated STA that has an RSID / AID equal to the value in the RSID11 / AID11 subfield.- The value 2007 is reserved for the EHT variant. Applicable to all variants2008-2042ReservedNot applicable to all variants2043- If the NDP announcement frame is a ranging variant, the STA Info The field contains a sequence authentication code. - Otherwise, the AID11 value is reserved. Applicable to ranging variants only. 2044 - If the NDP announcement frame is a ranging variant, the STA Info field contains a partial timing synchronization function (TSF). - Otherwise, the AID11 value is reserved. Applicable to ranging variants only. 2045 - If the NDP announcement frame is a ranging variant, the STA Info field contains ranging measurement parameters. - Otherwise, the AID11 value is reserved. Applicable to ranging variants only. 2046 Reserved. Not applicable to all variants. 2047 - If the NDP announcement frame is a HE variant, the STA Info field contains a disallowed subchannel bitmap. - Otherwise, the AID11 value is reserved. Applicable to HE variants only.

[0158] The partial bandwidth (BW) subfield may include a 1-bit (B0) resolution subfield and an 8-bit (B1-B8) feedback bitmap. The resolution subfield indicates the resolution bandwidth (e.g., 20 MHz or 40 MHz) for each bit of the feedback bitmap subfield. The feedback bitmap subfield may indicate a request for each resolution bandwidth from low to high frequency, with the first bit (B1) of the bitmap corresponding to the lowest resolution bandwidth. Each bit of the feedback bitmap is set to 1 if feedback is requested for the corresponding resolution bandwidth.

[0159] If the bandwidth of the EHT NDP announcement frame is less than 320 MHz, a resolution of 20 MHz can be indicated by setting the value of the resolution bit (B0) to 0.

[0160] When the bandwidth of the EHT NDP announcement frame is 20 MHz, B1 is set to 1 to indicate that feedback for a 242-tone RU is requested, and B2-B8 are reserved and can be set to 0.

[0161] When the bandwidth of the EHT NDP announcement frame is 40 MHz, B1 and B2 indicate that feedback is requested from each of the two 242-tone RUs from low to high frequency, and B3-B8 are reserved and can be set to 0.

[0162] If the bandwidth of the PPDU carrying the EHT NDP announcement frame is 80 MHz, B0 can be set to 0 to indicate a resolution of 20 MHz. If B1-B4 are all set to 1, this can indicate that feedback is requested for the 996-tone RU. Otherwise, B1-B4 can indicate that feedback is requested for each of the four 242-tone RUs from low to high frequency, and B5-B8 can be reserved and set to 0.

[0163] When the bandwidth of the PPDU carrying the EHT NDP announcement frame is 160 MHz, B0 can be set to 0 to indicate a resolution of 20 MHz. If B1-B4 are all set to 1, this can indicate that feedback is requested for the lower 996-tone RU, otherwise B1-B4 can indicate that feedback is requested for each of the four 242-tone RUs from low to high frequency in the lower 80 MHz. If B5-B8 are all set to 1, this can indicate that feedback is requested for the upper 996-tone RU, otherwise B5-B8 can indicate that feedback is requested for each of the four 242-tone RUs from low to high frequency in the upper 80 MHz.

[0164] When the bandwidth of the PPDU carrying the EHT NDP announcement frame is 320 MHz, B0 may be set to 1 to indicate a resolution of 40 MHz. If both B1 and B2 are set to 1, this may indicate that feedback is requested for the first 996-tone RU, otherwise B1 and B2 may indicate that feedback is requested for each of two 484-tone RUs from low to high frequency in the first 80 MHz. If both B3 and B4 are set to 1, this may indicate that feedback is requested for the second 996-tone RU, otherwise B3 and B4 may indicate that feedback is requested for each of two 484-tone RUs from low to high frequency in the second 80 MHz. If both B5 and B6 are set to 1, this may indicate that feedback is requested for the third 996-tone RU, otherwise B5 and B6 may indicate that feedback is requested from each of two 484-tone RUs from low to high frequency in the third 80 MHz. If both B7 and B8 are set to 1, this may indicate that feedback is requested for the fourth 996-tone RU, otherwise B7 and B8 may indicate that feedback is requested from each of two 484-tone RUs from low to high frequency in the fourth 80 MHz. The feedback tone set for each 484-tone RU may consist of the feedback tone sets of two 242-tone RUs that overlap with the 484-tone RU.

[0165] The partial bandwidth subfield can have values ​​such as the examples in Table 2, depending on the relevant settings.

[0166]

[0167]

[0168] For TB sounding, the feedback type and Ng subfields and the codebook size subfield can be set according to examples as shown in Table 3.

[0169]

[0170] For non-TB sounding, the feedback type and Ng subfields and the codebook size subfield can be set according to examples as shown in Table 4.

[0171]

[0172] The disambiguation subfield may be set to 1 to help non-EHT STAs (e.g., VHT STAs) avoid misinterpreting the field as an AID field.

[0173] In the EHT NDP announcement frame, RA is set to a broadcast address, and the following may apply. If the Feedback Type and Ng subfield and the Codebook Size subfield indicate SU or MU, the Nc index subfield is set to a value of Nc-1, where Nc corresponds to the number of columns in the compressed beamforming feedback matrix, and values ​​greater than 7 in the Nc index subfield are reserved. If the Feedback Type and Ng subfield and the Codebook Size subfield indicate CQI, the Nc index subfield is set to a value of Nc-1, where Nc corresponds to the number of STSs (space-time streams), and values ​​greater than 7 in the Nc index subfield are reserved. There may be more than one STA Info field.

[0174] In an EHT NDP announcement frame with a single STA Info field, the RA field is set to an individual address and the Nc index subfield may be reserved.

[0175] Multi-link (ML) operation

[0176] Below, the multi-link (ML) operation supported by the STA according to the present disclosure is described.

[0177] The STA (AP STA and / or non-AP STA) described in the present disclosure can support multi-link (ML) communication. ML communication may refer to communication that supports multiple links. Links related to ML communication may include channels (e.g., 20 / 40 / 80 / 160 / 240 / 320MHz channels) of a frequency band (e.g., 2.4GHz band, 5GHz band, 6GHz band, etc.) in which the STA operates. The multiple links used for ML communication may be configured in various ways. For example, the multiple links supported for one STA for ML communication may belong to the same frequency band or may belong to different frequency bands. In addition, each link may correspond to a frequency unit of a predetermined size (e.g., a channel, a subchannel, an RU, etc.). In addition, some or all of the multiple links may be frequency units of the same size or may be frequency units of different sizes.

[0178] When one STA supports multiple links, the transmitting and receiving devices supporting each link can operate as one logical STA. That is, a multi-link device (MLD) is a device that has one or more affiliated STAs as a logical entity and a single MAC service access point (SAP) for one MAC data service and logical link control (LLC). A non-AP MLD refers to an MLD in which each STA affiliated with the MLD is a non-AP STA. A multi-radio non-AP MLD refers to a non-AP MLD that supports receiving or exchanging frames on more than one link at a time. An AP MLD refers to an MLD in which each STA affiliated with the MLD is an AP STA.

[0179] Multi-link operation (MLO) can enable a non-AP MLD to discover, authenticate, associate, and set up multiple links with an AP MLD. Based on the supported capabilities exchanged during the association procedure, each link can enable channel access and frame exchange between the non-AP MLD and the AP MLD. An STA affiliated with an MLD can select and manage its capabilities and operating parameters independently from other STA(s) affiliated with the same MLD.

[0180] Through the multi-link setup process, the AP MLD and / or the non-AP MLD can transmit and receive link-related information that the MLD can support. The link-related information may include one or more of information about whether the MLD supports simultaneous transmit and receive (STR) operation or non-simultaneous transmit and receive (NSTR) operation on multiple links, information about the number / upper limit of UL / DL links, information about the location / bandwidth / resource of UL / DL links, information about frame types (e.g., management, control, data, etc.) that are available or preferred on at least one UL / DL link, information about an ACK policy that is available or preferred on at least one UL / DL link, or information about a traffic identifier (TID) that is available on at least one UL / DL link.

[0181] An AP MLD (e.g., NSTR mobile AP MLD) can set one of the multiple links as the primary link. The AP MLD may transmit beacon frames, probe response frames, and group-addressed data frames only on the primary link. The remaining link(s) of the multiple links may be referred to as non-primary links. An AP MLD operating on a non-primary link may operate so as not to transmit beacon frames or probe response frames. In addition, a non-AP MLD may perform frame exchanges during authentication, (re)association, and 4-way handshaking only on the primary link.

[0182] A setup link is defined as enabled if at least one traffic identifier (TID) is mapped to the link through the multi-link setup process, and a setup link can be defined as disabled if no TID is mapped to the link. A TID must always be mapped to at least one setup link unless admission control is used. By default, a TID is mapped to all setup links, so all setup links can be enabled.

[0183] When a link is activated, it can be used for frame exchange, depending on the power state of the non-AP STAs operating on that link. Only MSDUs or A-MSDUs with TIDs mapped to the activated link can be transmitted on that link. Management frames and control frames can only be transmitted on the activated link.

[0184] When a link is disabled, that link may not be used for frame exchange, including management frames for both DL and UL.

[0185] During a multi-link setup, activation / deactivation of individual links can be directed through TID-to-Link mapping. TID-to-Link mapping can be performed in default mapping mode or / and negotiation mapping mode.

[0186] Among the STAs belonging to the MLD, one STA may provide information about one or more links other than the link on which it is located, for multi-link discovery (e.g., obtaining information about multiple links including the corresponding link on one link) or multi-link setup (e.g., simultaneously associating on multiple links by exchanging association request / response frames on one link). A multi-link (ML) element may be defined to provide such information.

[0187] multi-AP operation

[0188] Multi-AP operation to which the method proposed in this disclosure can be applied is described.

[0189] Multi-AP operation is a general term for a technique in which multiple APs / STAs cooperate with each other to transmit and receive data when communicating with STA(s). For example, the following techniques can be used.

[0190] - Type 1: Co-transmission of Multi-APs / STAs: This transmission technique involves multiple APs transmitting simultaneously to STA(s). Co-transmission can be further categorized as follows:

[0191] i) Co-transmission of Multi-APs / STAs to each STA (e.g., cooperative spatial reuse (C-SR)): APs / STAs share channel information (e.g., transmit power (Tx Power), received signal strength indicator (RSSI), etc.) with STA(s), and communication between each AP and STA can be performed at the same time based on the shared channel information.

[0192] ii) Joint transmission of Multi-APs / STAs to the same STA(s) (e.g., joint transmission (J-TX))

[0193] Multiple APs / STAs can share channel information and data with STA(s), and communication can be performed between multiple APs and STA(s) at the same time based on the shared channel information and data.

[0194] - Type 2: Multi-AP / STA coordination: Among multiple APs, an appropriate AP can divide the appropriate area (i.e. frequency / time / space area) and transmit to the appropriate STA(s).

[0195] i) Distinction by frequency domain (e.g., coordinated OFDMA (C-OFDMA)): APs / STAs share channel information according to frequency bands with STA(s), and based on the shared channel information, each AP selects an appropriate frequency band to perform communication between each AP and STA.

[0196] ii) Distinction by spatial domain (e.g., coordinated beamforming (C-BF)): APs / STAs share channel information with STA(s), and based on the shared channel information, a beamforming (BF) matrix suitable for communication of each AP or that does not cause interference to other APs is calculated to perform communication between each AP and STA.

[0197] iii) Distinction by time domain (e.g., AP selection, relay, virtual BSS (V-BSS)): The representative AP selects APs / STAs suitable for the STA(s) (including the representative AP) and controls communication between the AP / STA and the STA.

[0198] To support multi-AP operations like the above, a representative AP can select and direct an AP / STA (hereinafter referred to as a "participating AP / STA") for communication with the STA. The meanings of the representative AP and participating AP / STA are as follows:

[0199] i) Representative AP (also called master AP or sharing AP)

[0200] - The representative AP initiates and controls Multi-AP operation, a technology for transmission and reception by multiple APs.

[0201] - The representative AP groups the participating APs and manages links with the participating APs to enable sharing of information (e.g., information about channels and / or data) between the participating APs.

[0202] - The representative AP manages information about the BSS composed of participating APs and information about STAs associated with the BSS.

[0203] ii) Participating AP (also called slave AP or shared AP)

[0204] - Participating APs are associated with a representative AP and can share control information, management information, and data traffic with each other.

[0205] - Participating APs basically perform the same functions as APs that can establish a BSS in a conventional WLAN system.

[0206] iii) Participating STA

[0207] - As in existing WLANs, a BSS is formed by association with a representative AP or participating AP.

[0208] Additionally, the Multi-AP operating environment is as follows.

[0209] A representative AP and a participating AP may be capable of direct transmission and reception of data (e.g., control information and / or data) with each other, either wired or wirelessly. Furthermore, a representative AP and an STA may not be capable of direct transmission and reception of wireless signals (e.g., control information and / or data). Furthermore, a participating AP (i.e., associated with an STA) and an STA may be capable of direct transmission and reception of wireless signals (e.g., control information and / or data). Furthermore, one of the participating APs may serve as a representative AP.

[0210] Additionally, a rough example of the DL or UL procedure for multi-AP operation can be performed as follows.

[0211] 1. The representative AP instructs the participating AP(s) (e.g., initiation of multi-AP operation, scheduling information, etc.).

[0212] Here, after receiving acknowledgments (Ack) from participating APs in response to the representative AP's instructions (e.g., initiation of Multi-AP operation, scheduling information, etc.), the representative AP can instruct Multi-AP operation by re-scheduling only the APs that transmitted the Ack.

[0213] 2. Participating AP(s) transmit DL data transmission or DL ​​trigger (i.e., trigger for UL data transmission of STA) to STA(s).

[0214] 3. The receiving STA(s) transmits an Ack (i.e., when DL data is received) or UL data (i.e., when a trigger for UL data transmission is received) to the participating AP(s).

[0215] Here, for UL procedures (i.e., when STA transmits UL data to participating AP(s)), if necessary, participating AP(s) may also transmit Ack to STA(s).

[0216] 4. Participating AP(s) can report the results (or completion of multi-AP operation) to the representative AP.

[0217] Hereinafter, in the description of the present disclosure, for the convenience of explanation, the AP transmitting the trigger frame in step 1 is referred to as a representative AP, but is not limited thereto, and may be referred to as a master AP, a sharing AP, a primary AP, etc. In addition, the AP receiving the trigger frame in step 1 is referred to as a participating AP, but is not limited thereto, and may be referred to as a slave AP, a shared AP, a secondary AP, etc.

[0218] In this disclosure, we propose step 1 of the above-described procedure, i.e., a method in which a representative AP triggers (instructs to initiate) Multi-AP operation.

[0219] With respect to step 1 above, the way in which the representative AP instructs the Multi-AP operation (i.e., the way in which the Multi-AP operation is triggered) may be as follows.

[0220] 1) Direct transmission instructions (or short-term instructions)

[0221] According to this method, the representative AP can directly instruct the participating AP(s) to transmit. In other words, this can mean that the representative AP dynamically instructs the participating AP(s) whenever a multi-AP operation is initiated.

[0222] A frame that triggers a multi-AP operation may be referred to as a multi-AP downlink trigger frame (MAD trigger frame: Multi-AP DL Trigger frame), but the present disclosure is not limited thereto.

[0223] The MAD trigger frame can reuse the existing basic trigger frame structure. Alternatively, the MAD trigger frame can be configured as a new type of trigger frame. In this case, for example, the new type of MAD trigger frame can be indicated in the trigger type subfield. Alternatively, the MAD trigger frame can be defined as a new control frame.

[0224] The existing trigger frame was transmitted for the purpose of triggering UL TB PPDU transmission of non-AP STAs, but the MAD trigger frame is transmitted for the purpose of triggering DL PPDU transmission of participating APs participating in multi-AP operation, so their purposes are different.

[0225] 1) Transmission section indication (or mid-term indication)

[0226] A representative AP can notify the participating AP(s) of the Multi-AP operation period. For example, the MU-RTS TXS trigger frame (i.e., the trigger frame that triggers the TXOP sharing procedure described above) can be used.

[0227] The existing MU-RTS TXS trigger frame notifies the TXOP section with the AP associated with the scheduled STA or another STA when the value of the triggered TXOP sharing mode subfield is set to 1 or 2. As an example of a method of applying the MU-RTS TXS trigger frame to the multi-AP operation in the present disclosure, the values ​​of 1 or 2 of the triggered TXOP sharing mode subfield may be used identically. As another example, the reserved value 3 of the triggered TXOP sharing mode subfield may be used to separately define a TXOP allocation method for the multi-AP procedure. In addition, in order to support such a multi-AP operation, unlike the existing MU-RTS TXS trigger frame, it may be allowed to include one or more User Info fields.

[0228] NDPA Frame Format for OBSS NDP Sounding Procedures

[0229] In the current standard, the NDP sounding procedure means a procedure in which a BSS AP (hereinafter referred to as AP1) transmits a sounding NDP to STAs associated with the AP or STAs belonging to the BSS (hereinafter referred to as STA1), and receives feedback on measured and calculated channel information from STA1.

[0230] If a multi-AP technique is introduced, APs / STAs within a BSS may require channel information with APs / STAs (respectively referred to as AP2 / STA2) of other adjacent BSSs (hereinafter referred to as OBSSs) that are not associated with the BSS AP. In this disclosure, a method for obtaining channel information using an NDP sounding procedure is proposed. However, since the AP and the STA in this disclosure may not be in the same BSS, even if the existing NDP sounding procedure is used, the transmission and reception methods may be different accordingly. In this disclosure, such a channel measurement technique is collectively referred to as OBSS NDP sounding, and an OBSS NDP sounding procedure / configuration is proposed. In particular, a notification method for indicating NDP sounding is proposed.

[0231] In the present disclosure, a BSS and an OBSS are adjacent to each other, and AP1 (an AP of the BSS) and AP2 (an AP of the OBSS) can hear each other's signals (or a device that transmits each other's signals may exist between AP1 and AP2), STA1 (an AP of the BSS) can hear not only the signals of AP1 but also the signals of AP2, and STA2 (an STA of the OBSS) can hear not only the signals of AP2 but also the signals of AP1. (Some STA1 and STA2 may not be able to hear. Such STA1 and STA2 are hereinafter referred to as STA1' and STA2'.) In addition, AP1, AP2, STA1, and STA2 have the capability for Multi-AP operation and can perform Multi-AP operation depending on the situation or upon instruction. AP1 and AP2 may be a sharing AP or a shared AP depending on the situation, and for example, an AP that has acquired a TXOP may be a sharing AP. Alternatively, a third AP may act as a sharing AP.

[0232] Although the present disclosure mainly describes a method for applying an OBSS NDP sounding procedure to a BSS AP / STA and an OBSS AP / STA for convenience of explanation, the present disclosure is not limited thereto. That is, the OBSS NDP sounding procedure of the present disclosure can be extended to be applied to channel measurement of AP / STA(s) for each link of an MLD or relay AP / STA(s), and in this case, the proposed method of the present disclosure can be referred to as an NDP sounding procedure for adjacent / different links. For example, when the proposed method of the present disclosure is applied to an MLD device, for example, in the description of the present disclosure, AP1 and AP2 can be included in a single MLD, and STA 1 and STA 2 can be included in a single MLD.

[0233] The transmit and receive frames required for the OBSS NDP sounding procedure may be as follows. In addition, trigger frames, BA (block ack) frames, etc. may be required.

[0234] - NDP announcement frame indicating OBSS sounding (hereinafter, for convenience of explanation, may be referred to as ONDPA (OBSS NDP announcement) frame)

[0235] - Sounding NDP

[0236] - Feedback frames (e.g., compressed beamforming / channel quality indication (CQI) reporting frames)

[0237] The operations of the AP and STA for the OBSS sounding procedure of AP 1 (i.e., the method of acquiring channel information from STA 2 of AP 1) are exemplified as follows. These procedures can be equally applied to the OBSS sounding procedure of AP 2 (i.e., the method of acquiring channel information from STA 1 of AP 2).

[0238] - Example of AP operation

[0239] i) AP1 or AP2 or Sharing AP transmits an ONDPA frame.

[0240] ii) AP1 transmits (sounding) NDP after xIFS (e.g. SIFS).

[0241] iii) Under certain circumstances (e.g., when requesting feedback from one or more STAs or when the RA field is broadcast), after xIFS (e.g., SIFS), AP1 or AP2 or the Sharing AP may transmit a beamforming report poll (BFRP) trigger frame.

[0242] iv) After xIFS (e.g., SIFS), AP1 can obtain OBSS channel information by receiving a feedback frame transmitted by STA2(s). Alternatively, AP2 or the Sharing AP can transmit the OBSS channel information obtained after receiving the feedback frame transmitted by STA2(s) to AP1 (or the Sharing AP).

[0243] v) AP1, AP2 or Sharing AP can collect this channel information and perform Multi-AP operation.

[0244] - Example of STA2 operation

[0245] i) STA2(s) receives an ONDPA frame from AP1 or AP2 or Sharing AP.

[0246] ii) If the received ONDPA frame contains information requesting feedback to STA2 (e.g., STA2's AID or OAID (OBSS AID), etc.), STA2(s) receive the (sounding) NDP transmitted after xIFS (e.g., SIFS) and generate channel information as instructed. If the ONDPA frame does not request feedback to itself, STA2(s) can perform NAV setting.

[0247] iii) When a specific situation occurs (for example, when the RA field of the ONDPA frame is broadcast), STA 2(s) can receive a BFRP trigger frame transmitted by AP1 or AP2 or Sharing AP after xIFS (for example, SIFS) to determine resource information to be fed back, etc.

[0248] iv) After xIFS (e.g. SIFS), STA2(s) can transmit the generated channel information to AP1 or AP2 or Sharing AP through a feedback frame.

[0249] Among the above procedures / frames, in particular, the present disclosure proposes the following configuration / format of an NDP announcement frame indicating OBSS sounding. For example, the ONDPA frame may have a different configuration / format from the existing NDP announcement frame in that the AP indicates this to OBSS STA(s) that are not associated with it, or the same configuration / format as the existing NDP announcement frame may be used.

[0250] Example 1: NDPA frame configuration for indicating OBSS sounding

[0251] A new format for NDPA frames to indicate OBSS sounding may be established / defined as follows:

[0252] FIG. 9 illustrates an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0253] Referring to FIG. 9, an NDPA frame for indicating OBSS sounding may be configured to include a frame control field, a duration field, a receiver address (RA) field, a transmitter address (TA) field, a source address (SA) or an AP address (AA) field, a sounding dialog token field, one or more STA information (Info) fields (i.e., a STA information list), and a Frame Check Sequence (FCS).

[0254] The frame control field can be set to Type=01 (i.e., control frame indication), subtype=0101 (i.e., NDPA frame indication). That is, it can be set to the same value as the existing NDPA frame.

[0255] Both the ToDS subfield and the FromDS subfield in the frame control field can be set to 1. In the case of existing NDPA frames, both the ToDS subfield and the FromDS subfield in the frame control field are set to 0, but in an NDPA frame for indicating OBSS sounding, both can be set to 1.

[0256] The SA (source address) or AA (AP address) field can be configured as follows: i) when the ToDS subfield is set to '1', or ii) when the FromDS subfield is set to '1', or iii) when both the ToDS subfield and the FromDS subfield are set to '1', a third address Address3) field can be included in the NDPA frame to indicate OBSS sounding, which can be defined as the SA field or the AA field. This field can separately indicate the MAC address of the AP of the BSS that the receiving STA includes / belongs to.

[0257] For example, the SA field can be set to include the definition described above in the meaning of the existing SA (source address) as follows.

[0258] - SA field: Indicates an individual address that identifies the MAC entity that initiated transmission of the MSDU (MAC service data unit) (or fragment of the MSDU) or A-MSDU (aggregated MSDU) contained in the frame body field. Alternatively, it indicates the address of the AP with which the intended direct recipient STA(s) are associated.

[0259] As another example, a new AA (AP address) field can be defined as follows:

[0260] - AA field: Indicates the address of the AP with which the intended direct recipient STA(s) are associated.

[0261] Here, in addition to the ONDPA frame, there may be cases where an AP supporting Multi-AP operation together with the BSS AP transmits a control frame for supporting Multi-AP operation. Therefore, unlike the conventional case, the control frame for supporting Multi-AP operation may be configured to include a third address (Address3) field in the control frame by setting the ToDS subfield to '1', the FromDS subfield to '1', or both subfields to '1'.

[0262] The last six bits (B2-B7) of the sounding dialog token field can be set as a sounding dialog token number subfield, and the first two bits (B0-B1) can be defined as reserved. Alternatively, a value of '00' in B0-B1 can be set to indicate an ONDPA frame, and other values ​​can be defined as reserved. Alternatively, the values ​​of B0-B1 can also indicate the type of ONDPA frame. Alternatively, as with the existing NDPA frame, the first two bits (B0 and B1) of the eight bits (B0-B7) of the sounding dialog token field can be used to indicate the type / variant of the NDP announcement frame.

[0263] The STA Info field(s) included in the STA Info list may use the same format as the field defined in the existing EHT NDPA frame (i.e., see FIG. 8(d)). The AID11 subfield may include the AID value of the STA that must measure and feed back NDP. Here, the AID may be an AID value defined within the BSS and may also be used in the ONDPA frame of the OBSS AP, or may be a newly defined OAID (OBSS AID) value that the OBSS AP can use.

[0264] Fields / subfields not specifically described here may follow the format / structure of a conventional control frame or NDPA frame.

[0265] Meanwhile, the frame control field of the NDPA frame for indicating OBSS sounding may be set to Type=01 (i.e., control frame indication) and subtype=0110 (i.e., control frame extension indication). In addition, the control frame extension subfield may be defined with one of the previously reserved values ​​1100 to 1111, so that the NDPA frame for indicating OBSS sounding may be configured as a new control frame. The configuration of other fields is the same as the description above, so a detailed description is omitted.

[0266] Example 2: NDPA frame configuration for indicating OBSS sounding

[0267] The NDPA frame for indicating OBSS sounding can be set / defined using the same format and structure as the existing NDPA frame.

[0268] FIG. 10 illustrates an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0269] Referring to FIG. 10, an NDPA frame for indicating OBSS sounding may be configured to include a frame control field, a duration field, a receiver address (RA) field, a transmitter address (TA) field, a sounding dialog token field, one or more STA information (Info) fields (i.e., a STA information list), and a Frame Check Sequence (FCS).

[0270] The frame control field can be set to Type=01 (i.e., control frame indication), subtype=0101 (i.e., NDPA frame indication). In addition, both the ToDS subfield and the FromDS subfield can be set to '0'. In other words, they can be set to the same values ​​as the existing NDPA frame.

[0271] - RA field

[0272] If the NDPA frame for indicating OBSS sounding requests OBSS sounding to a single STA, the RA field may be set to the address of that STA. Alternatively, if the NDPA frame requests OBSS sounding to two or more STAs, the RA field may be set to a broadcast address.

[0273] Alternatively, to indicate that the frame is an NDPA frame for indicating OBSS sounding, the RA field may be set to a specific address value (e.g., specifying a group address such as a multicast-group address or a broadcast address). In this case, STAs having OBSS sounding capability (or capability for Multi-AP operation) can identify that the frame is an NDPA frame for indicating OBSS sounding through the specific address value even if the value of the RA field is not their own address, and can determine whether the frame includes an instruction for themselves after decoding the frame.

[0274] - TA field

[0275] The TA field may be set to the address of the AP / STA transmitting the NDPA frame to indicate OBSS sounding or to the bandwidth signaling TA.

[0276] Alternatively, the TA field may be set to a specific address value (e.g., a group address such as a multicast-group address or a broadcast address) to indicate that the frame is an NDPA frame for indicating OBSS sounding. In this case, STAs having OBSS sounding capability (or capability for Multi-AP operation) can determine that the frame is an NDPA frame for indicating OBSS sounding through the specific address value even if the value of the TA field is not the AP address of the BSS to which they belong, and can determine whether the frame includes an instruction after decoding the frame.

[0277] - Sounding dialog token field

[0278] The sounding dialog token field may consist of an NDP announcement variant subfield (first two bits) and a sounding dialog token number subfield (last six bits).

[0279] The existing NDP announcement variant subfield can identify the NDPA frame variant as shown in Table 5.

[0280]

[0281] Referring to Table 5, according to the conventional method, if the value of the NDP Announcement Variant subfield is set to 0, the frame is identified as a VHT NDPA frame, if the value of the NDP Announcement Variant subfield is set to 1, the frame is identified as a Ranging NDPA frame, if the value of the NDP Announcement Variant subfield is set to 2, the frame is identified as a HE NDPA frame, and if the value of the NDP Announcement Variant subfield is set to 3, the frame is identified as an EHT NDPA frame.

[0282] Method 1: When the NDP Announcement Variant Subfield = 1, the frame can be identified as a Ranging NDPA frame or an NDPA frame for indicating OBSS sounding. Here, as an example of a method for distinguishing between a Ranging NDPA frame and an NDPA frame for indicating OBSS sounding, one of the reserved bits of the STA Information (STA Info) field can be used. That is, when the one bit is '0' (or '1'), the frame can be identified as a Ranging NDPA frame, and when it is '1' (or '0'), the frame can be identified as an NDPA frame for indicating OBSS sounding. In this case, the STA Information field can be configured differently depending on whether the frame is a Ranging NDPA frame or an NDPA frame for indicating OBSS sounding. A detailed description thereof will be provided later.

[0283] Method 2: When the NDP announcement variant subfield = 3, the frame can be identified as an EHT NDPA frame or an NDPA frame for indicating OBSS sounding. Here, as an example of a method for distinguishing between an EHT NDPA frame and an NDPA frame for indicating OBSS sounding, a specific value (e.g., one of 2007 to 2047) of the AID11 subfield of the first STA information (STA Info) field (i.e., a subfield carrying the 11 least significant bits (LSBs) of the STA's association identifier (AID)) can be used. For example, when the AID11 subfield is set to the specific value, the frame can be identified as an NDPA frame for indicating OBSS sounding. In this case, the first STA information (STA Info) field can include common information necessary for OBSS sounding. A detailed explanation of this will be provided later.

[0284] - STA info field

[0285] Configuration 1: When following Method 1 for the sounding dialog token field described above, the structure / format of the STA information field of the Ranging NDPA frame can be utilized.

[0286] FIG. 11 illustrates an STA information field of an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0287] Referring to FIG. 11, each STA information field included in the STA information list may be configured to include an AID11 subfield, an LTF offset subfield, an R2I NSTS subfield, an R2I Rep subfield, an I2R NSTS subfield, a reserved bit, a disambiguation subfield, an I2R Rep subfield, and a reserved bit.

[0288] The AP can use the structure of the STA information field of the Ranging NDPA of FIG. 11 to instruct each STA to perform OBSS NDP sounding. For example, if the frame is an NDPA frame for instructing OBSS sounding, the last bit (B31) of the STA information field can be set to '1'. If the STA to which the STA information field points (i.e., the STA identified by the AID11 subfield in the STA information field) is, the STA can read B31 and recognize that the frame is an NDPA frame for instructing OBSS sounding. However, in this case, since it is possible to distinguish whether the frame is a Ranging NDPA frame or an NDPA frame for instructing OBSS sounding only after checking B31 of each STA information field, this may be a decoding burden for the STAs. In this case, the burden can be reduced by notifying in advance that it is an ONDPA frame as another method, and the 'PHY (physical layer) indication' method described later can be used.

[0289] In addition, each subfield in the STA information field of the NDPA frame for indicating OBSS sounding as illustrated in FIG. 11 can be defined with the same structure as each subfield in the STA information field of the Ranging NDPA frame, and a detailed description thereof is omitted.

[0290] Configuration 2: If the STA Information field containing a specific AID11 value (e.g., one of 2007 to 2047) is set as the first STA Information, the frame can be identified as an NDPA frame for indicating OBSS sounding. This can be applied regardless of the NDP Announcement Variant value according to Table 5.

[0291] The STA information field containing this specific AID11 value may contain instructions and information common to all STAs. For convenience of explanation, this may be referred to as the common STA information field in the present disclosure.

[0292] FIG. 12 illustrates an STA information field of an NDPA frame for indicating OBSS sounding according to one embodiment of the present disclosure.

[0293] Referring to FIG. 12, the first one (or two or more) STA information fields in the STA information list may be configured as common STA information fields containing common information. Subsequent subsequent STA information fields(s) may contain individual STA information.

[0294] Although FIG. 12 illustrates a case where the first two STA information fields constitute a common STA field, the present disclosure is not limited thereto. That is, the first STA information field may also be configured as a common STA field.

[0295] Here, as an example of a common STA information field, the common STA information field may include common information by configuring some or all of the other subfields differently, except for the AID11 subfield and the Disambiguation subfield (i.e., including them equally).

[0296] Here, as an example of common information, at least one of the BSSID or part thereof of the STA or AP transmitting the NDPA frame for indicating OBSS sounding, the BSSID or part thereof of the BSS AP to which the STA that must perform OBSS sounding belongs, or multi-AP group information may be included. Here, instead of the BSSID, when multi-AP is operated, the representative information / number of the corresponding AP (e.g., group ID, BSS color (i.e., 6-bit identifier for distinguishing BSSs operating on the same channel)) may also be included.

[0297] To include the entire BSSID, for example, the common STA information field may be defined to consist of two or more consecutive STA information fields as shown in FIG. 12. Referring to FIG. 12, one BSSID may be expressed / indicated by consecutively starting from BSSID(1) to BSSID(4).

[0298] The STA information field(s) following the common STA information field may include instructions and information individually required for each STA. As an example of its configuration, the configuration / format of the STA information field of the existing EHT NDPA frame (see FIG. 8(d)) may be used in the same manner as in FIG. 12.

[0299] Meanwhile, for both configuration 1 and configuration 2 of the STA information field described above, when transmitting the STA information field individually to each STA, the value included in the AID11 subfield may vary depending on the transmitting entity of the NDPA frame for indicating OBSS sounding.

[0300] For example, in the case of OBSS NDP sounding to determine channel information between AP1 and STA2, the (sounding) NDP can be transmitted by AP1. Here, the NDPA frame indicating OBSS NDP sounding can be transmitted by AP2. In this case, the same AID as before can be used for STA2.

[0301] Alternatively, in the case of OBSS NDP sounding to determine channel information between AP1 and STA2, the (sounding) NDP may be transmitted by AP1, and AP1 may also transmit an NDPA frame indicating OBSS NDP sounding. In this case, STA2's AID may be configured differently from before. That is, since the AID is generally a value defined within the BSS to which the STA belongs, the same value may refer to different STAs in different BSSs, so a method to prevent this is required. An example of such a method is as follows.

[0302] For example, AIDs can be assigned to STAs between BSSs performing multi-AP operations together to avoid overlapping AIDs. In this case, the ONDPA frame can also include the AID11 subfield in the conventional manner.

[0303] As another example, a new AID for an OBSS STA may be assigned. For example, a separate AID may be defined for use when AP1 indicates STA2, or when AP2 indicates STA1. In this case, the ONDPA frame may include the OAID in the AID11 subfield.

[0304] 'PHY (physical layer) instruction' method

[0305] ONDPA frames can be in Non-HT DUP (duplicated) format or UHR PPDU format.

[0306] Here, in addition to the above-described methods, a PHY signal in the UHR PPDU format may be used for faster recognition of the ONDPA frame. That is, by setting the PPDU format of the ONDPA frame to the UHR PPDU format and setting the BSS color of the U-SIG to a specific value, it is possible to indicate that it is an ONDPA frame. Here, the specific value may be defined / set as a fixed single value for multi-AP operation, or the specific value may be allocated one by one for each AP group that performs multi-AP operation together. In the former case, one value may be designated, and in the latter case, signaling for allocation may be required before OBSS sounding.

[0307] FIG. 13 is a diagram illustrating the operation of an STA for an NDP sounding method according to one embodiment of the present disclosure.

[0308] In FIG. 13, the first AP and the second AP correspond to different APs, and the BSS of the first AP and the BSS of the second AP operate on the same channel and may overlap. Additionally, the STA may correspond to an STA belonging to the BSS of the first AP (and / or associated with the first AP).

[0309] Referring to FIG. 13, the STA receives an NDP announcement frame from the first AP (S1301).

[0310] Here, the NDP announcement frame includes a plurality of STA information fields, and a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) can be identified by the first one or more STA information fields among the plurality of STA information fields.

[0311] Additionally, a first STA information field among the one or more STA information fields includes an AID11 subfield, and based on the AID11 subfield being set to a specific value (e.g., 2047), a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) can be identified.

[0312] In addition, the NDP announcement frame may further include a sounding dialog token field, and the sounding dialog token field may include an NDP announcement variant subfield and a sounding dialog token number subfield. Here, even if the NDP announcement variant subfield value is set to 3, the NDP announcement frame may be distinguished from an EHT (extremely high throughput) NDP announcement frame based on the AID11 subfield being set to a specific value. That is, a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) may be identified.

[0313] Additionally, the one or more STA information fields (e.g., two STA information fields) may include common information for multiple STAs associated with the NDP announcement frame.

[0314] Here, the common information may include a basic service set (BSS) color of the first AP and / or identification information (e.g., AID, BSSID, etc. of the AP) for the second AP transmitting the NDP to the STA.

[0315] Additionally, the remaining STA information fields following the one or more STA information fields may contain individual information for each STA.

[0316] The STA transmits a frame containing channel state information to the first AP (S1302).

[0317] As described above, the STA may belong to the BSS of the first AP, but the STA may not belong to the BSS of the second AP. Although not illustrated in FIG. 13, the STA may receive an NDP from the second AP. That is, the STA may receive an NDPA from the first AP for the BSS to which it belongs, but may receive an NDP from the second AP for the BSS to which it does not belong. In this case, the channel state information may be generated based on the NDP. Alternatively, although not illustrated in FIG. 13, the STA may receive an NDP from the first AP. In this case, the channel state information may be generated based on the NDP.

[0318] Additionally, although not illustrated in FIG. 13, the STA may receive a BFRP trigger frame from the first AP. In this case, the frame including the channel state information may be transmitted through resources allocated by the BFRP trigger frame.

[0319] A PPDU containing / carrying an NDP announcement frame in step S1301 and / or a frame in step S1302 may be configured to include a legacy-part, a SIG-part (e.g., U-SIG, UHR-SIG, etc.), an STF-part (e.g., UHR-STF), an LTF-part (e.g., UHR-LTF), and a data-part.

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

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

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

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

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

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

[0326] The data-part described above may include user data and may include packets for upper layers (e.g., MPDUs).

[0327] The method described in the example of FIG. 13 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may be configured to receive an NDP announcement frame from a second device (200) (i.e., an AP) through the transceiver(s) (106), and transmit a frame including channel state information to the second device (200) through the transceiver(s) (106). Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 13 or the examples described above when executed by one or more processors (102).

[0328] FIG. 14 is a diagram illustrating the operation of an AP for an NDP sounding method according to one embodiment of the present disclosure.

[0329] In FIG. 14, the first AP and the second AP correspond to different APs, and the BSS of the first AP and the BSS of the second AP operate on the same channel and may overlap. Additionally, the STA may correspond to an STA belonging to the BSS of the first AP (and / or associated with the first AP).

[0330] Referring to FIG. 14, the first AP transmits an NDP announcement frame to the STA(s) (S1401).

[0331] Here, the NDP announcement frame includes a plurality of STA information fields, and a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) can be identified by the first one or more STA information fields among the plurality of STA information fields.

[0332] Additionally, a first STA information field among the one or more STA information fields includes an AID11 subfield, and based on the AID11 subfield being set to a specific value (e.g., 2047), a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) can be identified.

[0333] In addition, the NDP announcement frame may further include a sounding dialog token field, and the sounding dialog token field may include an NDP announcement variant subfield and a sounding dialog token number subfield. Here, even if the NDP announcement variant subfield value is set to 3, the NDP announcement frame may be distinguished from an EHT (extremely high throughput) NDP announcement frame based on the AID11 subfield being set to a specific value. That is, a variant of the NDP announcement frame (e.g., an NDP announcement frame indicating OBSS sounding) may be identified.

[0334] Additionally, the one or more STA information fields (e.g., two STA information fields) may include common information for multiple STAs associated with the NDP announcement frame.

[0335] Here, the common information may include a basic service set (BSS) color of the first AP and / or identification information (e.g., AID, BSSID, etc. of the AP) for the second AP transmitting the NDP to the STA.

[0336] Additionally, the remaining STA information fields following the one or more STA information fields may contain individual information for each STA.

[0337] The first AP receives a frame containing channel state information from the STA(s) (S1402).

[0338] As described above, the STA may belong to the BSS of the first AP, but the STA may not belong to the BSS of the second AP. Although not illustrated in FIG. 14, the second AP may transmit an NDP to the STA(s). That is, the STA may receive an NDPA from the first AP for the BSS to which it belongs, but may receive an NDP from the second AP for the BSS to which it does not belong. In this case, the channel state information may be generated based on the NDP. Alternatively, although not illustrated in FIG. 14, the first AP may transmit an NDP to the STA(s). In this case, the channel state information may be generated based on the NDP.

[0339] Additionally, although not illustrated in FIG. 14, the first AP may transmit a BFRP trigger frame to the STA. In this case, the frame including the channel state information may be transmitted via resources allocated by the BFRP trigger frame.

[0340] A PPDU containing / carrying an NDP announcement frame in step S1401 and / or a frame in step S1402 may be configured to include a legacy-part, a SIG-part (e.g., U-SIG, UHR-SIG, etc.), an STF-part (e.g., UHR-STF), an LTF-part (e.g., UHR-LTF), and a data-part.

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

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

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

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

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

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

[0347] The data-part described above may include user data and may include packets for upper layers (e.g., MPDUs).

[0348] The method described in the example of FIG. 14 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may be configured to transmit an NDP announcement frame via the transceiver(s) (106) and receive a frame including channel state information from the first device (200) via the transceiver(s) (206). Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 14 or the examples described below when executed by one or more processors (202).

[0349] Unlike NDP sounding methods in existing wireless LAN systems, the NDP sounding method according to the examples of the present disclosure supports OBSS sounding as described above. Accordingly, channel information for OBSS STAs can be acquired, enabling smooth multi-AP operation. Furthermore, since frequency resources can be reused through a spatial reuse technique where multiple BSSs cooperate, the effect of efficiently utilizing frequency resources can be achieved.

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

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

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

[0353] 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 method comprising the steps of receiving, by a station (STA), a notification frame on physical protocol data units (PPDUs) with zero data (NDP) from a first access point (AP); and transmit, by means of the STA, a frame including the channel state information to the first AP, wherein the NDP notification frame includes a plurality of STA information fields, and wherein the format of the NDP notification frame is identified by a first STA information field of the plurality of STA information fields.

2. The method according to claim 1, wherein the information field of the first STA includes an AID11 subfield, and wherein the format of the NDP notification frame is identified based on the AID11 subfield being set equal to a specific value.

3. The method of claim 2, wherein the NDP notification frame further includes a probe dialog token field, wherein the probe dialog token field includes a subfield of NDP notification options and a subfield of the number of probe dialog tokens, and However, even if the NDP Alert Options subfield value is set to 3, the NDP Alert frame is distinguished from the Extremely High Throughput (EHT) NDP Alert frame based on the AID11 subfield being set to a specific value.

4. The method of claim 1, wherein one or more STA information fields, including the first STA information field, include common information for a plurality of STAs associated with the NDP notification frame.

5. The method of claim 4, wherein the common information includes a basic service set (BSS) color of the first AP and / or identification information for the second AP that transmits the NDP to the STA.

6. The method of claim 4, wherein the remaining STA information fields following the one or more STA information fields include separate information for each STA.

7. The method according to claim 1, also comprising the step of receive, via STA, NDP from the second AP, in this case, the STA belongs to the BSS of the first AP, but the STA does not belong to the BSS of the second AP, and In this case, the channel state information is generated based on NDP.

8. The method according to claim 1, also comprising the step of receive, via STA, NDP from the first AP, in this case, the STA belongs to the BSS of the first AP, but the STA does not belong to the BSS of the second AP, and In this case, the channel state information is generated based on NDP.

9. The method according to claim 1, also comprising the step of receive, by the STA, a triggering polling frame for beamforming messages (BFRP) from the first AP, In this case, the frame including the channel state information is transmitted through the resources allocated by the triggering BFRP frame.

10. The method of claim 1, wherein the STA is an STA belonging to a basic service set (BSS) of the first AP.

11. A station device (STA) in a wireless local area network (WLAN) based system, wherein the device comprises at least one transmitting and receiving device; and at least one processor connected to at least one transmitting and receiving device, wherein at least one processor is configured to receive a zero data point (NDP) physical protocol data unit (PPDU) notification frame from the first access point (AP); and transmit a frame including link state information to the first AP, wherein the NDP notification frame includes a plurality of STA information fields, and wherein the format of the NDP notification frame is identified by a first STA information field of the plurality of STA information fields.

12. A method comprising the steps of transmitting, by a first access point (AP), a notification frame over physical protocol data units (PPDUs) with zero data (NDP) to a station (STA); and receive, by the first AP, a frame including channel state information from the STA, wherein the NDP notification frame includes a plurality of STA information fields, and wherein the format of the NDP notification frame is identified by a first STA information field of the plurality of STA information fields.

13. A first access point (AP) device in a wireless local area network (WLAN) based system, wherein the device comprises at least one transmitting and receiving device; and at least one processor connected to at least one transmitting and receiving device, wherein at least one processor is configured to transmit a notification frame over physical protocol data units (PPDUs) with zero data points (NDPs) to the station (STA); and receive a frame including channel state information from the STA, wherein the NDP notification frame includes a plurality of STA information fields, and wherein the format of the NDP notification frame is identified by a first STA information field of the plurality of STA information fields.

14. A processing device configured to control a station (STA) in a system based on a wireless local area network (WLAN), wherein the processing device comprises at least one processor; and at least one computer memory device operatively connected to at least one processor and, upon execution by at least one processor, storing instructions for implementing the method according to any one of claims 1-10.

15. At least one non-volatile machine-readable medium storing at least one instruction, wherein at least one instruction controls the device in such a way as to implement the method according to any one of claims 1-10 in a system based on a wireless local area network (WLAN) by execution by at least one processor.