WO2025121969A1 - Method and device for performing relay transmission in wireless lan system - Google Patents

Abstract

Disclosed are a method and a device for operating in a wireless LAN system. A method performed by a first station (STA) in a wireless LAN system according to an embodiment of the present disclosure may comprise the steps of: receiving a first management frame from an access point (AP); receiving a second management frame from a second STA within a specific time interval after receiving the first management frame; and on the basis of the first STA being a first type of STA, discarding the second management frame or updating at least one type of information included in the first management frame on the basis of the second management frame, wherein the first STA is located within coverage of a basic service set (BSS) of the AP, and the second management frame is based on the first management frame.

Description

Method and device for performing relay transmission in a wireless LAN system

The present disclosure relates to a communication operation in a wireless local area network (WLAN) system, and more specifically, to a method and device for performing relay transmission within a specific time period in a next-generation wireless LAN system.

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

In order to provide a more enhanced wireless communication environment, improved technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for MIMO (Multiple Input Multiple Output) and multi-access point (AP) coordination that support increased bandwidth, efficient utilization of multiple bands, and increased spatial streams are being studied, and 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 technologies.

The technical problem of the present disclosure is to provide a method and device for performing relay transmission in a wireless LAN system.

The technical problem of the present disclosure is to provide a method and device for transmitting a signal transmitted by an AP to at least one STA existing outside the coverage of a basic service set (BSS) in a wireless LAN system.

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

According to one aspect of the present disclosure, a method performed by a first station (STA) in a wireless LAN system includes the steps of: receiving a first management frame from an access point (AP); receiving a second management frame from a second STA within a specific time interval after receiving the first management frame; and discarding the second management frame or updating at least one type of information included in the first management frame based on the second management frame, based on which the first STA is a first type of STA, wherein the first STA is located within the coverage of a basic service set (BSS) of the AP, and the second management frame may be based on the first management frame.

According to another aspect of the present disclosure, a method performed by a second station (STA) in a wireless LAN system comprises the steps of: receiving a first management frame from an access point (AP); and transmitting a second management frame based on the first management frame to at least one STA, wherein based on a first STA included in the at least one STA being a first type of STA, the second management frame is discarded by the first STA or at least one type of information included in the first management frame is updated based on the second management frame, and the second management frame can be transmitted by the second STA to the at least one STA within a specific time interval after receiving the first management frame.

According to various embodiments of the present disclosure, a method and device for performing relay transmission in a wireless LAN system can be provided.

According to various embodiments of the present disclosure, a method and device for transmitting a signal transmitted by an AP to at least one STA located outside the BSS coverage in a wireless LAN system can be provided.

By various embodiments of the present disclosure, ambiguity related to an STA receiving data transmitted by an AP via a relay STA can be reduced, and the range of relay transmission can be expanded.

By various embodiments of the present disclosure, the influence of range and obstacles can be reduced through the relay transmission procedure, and the reception SNR of the STA can be improved, thereby reducing the delay and improving the throughput for signal transmission.

The effects obtainable from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

The accompanying drawings, which are incorporated in and are incorporated in and are intended 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.

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

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

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

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

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

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.

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

FIG. 8 is a drawing for explaining a procedure for performing a relay operation to which the present disclosure can be applied.

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

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

Hereinafter, preferred embodiments according to 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 in order 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.

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

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 relationship, but also an indirect connection relationship in which another component exists between them. Also, 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.

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

The terminology used herein is for the purpose of describing particular embodiments only 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 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 word "/" used between words in this disclosure has the same meaning as "and/or" unless otherwise stated.

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 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 a newly proposed IEEE 802.11bn (or UHR) standard. Additionally, the examples of the present disclosure can be applied to a wireless LAN based on a next-generation standard after IEEE 802.11bn. In addition, 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 a Long Term Evolution (LTE) series technology of the 3rd Generation Partnership Project (3GPP) standard and a New Radio (5G NR) series technology.

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

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

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 Wireless Transmit Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Mobile Subscriber Unit (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), a Wireless terminal (WT), 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 base station (BS), a fixed station, a Node B, a base transceiver system (BTS), a network, an Artificial Intelligence (AI) system, a road side unit (RSU), a repeater, a router, a relay, a gateway, etc.

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 a transmitting device, a receiving device, a transmitting STA, and a receiving STA. For example, the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, the STAs (110, 200) in the present disclosure may perform 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, the APs in the present disclosure may also be indicated as AP STAs.

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 regulations of the IEEE 802.11 standard.

In addition, the first device (100) and the second device (200) may additionally support various communication standards (for example, standards of 3GPP LTE series, 5G NR series, 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 Augmented Reality (AR) device, and a Virtual Reality (VR) device. In addition, the STA of the present specification may support various communication services such as a voice call, a video call, a data communication, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

A first device (100) includes one or more processors (102) and one or more memories (104), and may additionally 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, suggestions, 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). Additionally, 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 codes 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.

The second device (200) includes one or more processors (202), one or more memories (204), and may additionally include one or more transceivers (206) and/or one or more antennas (208). The processor (202) may control the memories (204) and/or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure. For example, the processor (202) may process information in the memory (204) to generate third information/signal, and then transmit a wireless signal including the third information/signal via the transceiver (206). Additionally, the processor (202) may receive a wireless signal including fourth information/signal via the transceiver (206), and then store information obtained from signal processing of the fourth information/signal 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 codes including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operational 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.

Hereinafter, 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 this 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 this 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, suggestions and/or methodologies disclosed in this 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, suggestions, methods and/or operational flowcharts disclosed in this disclosure.

The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The 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 the one or more processors (102, 202). The descriptions, functions, procedures, suggestions, 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, suggestions, methods and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more of the following: included in one or more processors (102, 202), or stored in one or more memories (104, 204) and driven by one or more of the processors (102, 202). The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.

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 comprised of 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.

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, suggestions, 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, and the like, as described in the description, function, procedure, proposal, method, and/or operational flowchart, etc. disclosed in this disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas, or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may 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 processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and/or filter.

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 of various STAs generating transmission and reception signals or performing 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 transmit/receive signal or performing data processing or calculation in advance for a transmit/receive signal may include: 1) an operation for determining/acquiring/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/acquiring time resources or frequency resources (e.g., subcarrier resources) used for the fields (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining/configuring/acquiring specific sequences (e.g., pilot sequences, STF/LTF sequences, extra sequences applied to SIG) used for the fields (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/acquiring/configuring/computing/decoding/encoding an ACK signal, etc. In addition, 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.

Hereinafter, downlink (DL) means a link for communication from an AP STA to a non-AP STA, and downlink PPDU/packet/signal, etc. can be transmitted and received through the downlink. In downlink communication, a transmitter may be part of an AP STA, and a receiver may be part of a non-AP STA. Uplink (UL) means a link for communication from a non-AP STA to an AP STA, and uplink PPDU/packet/signal, etc. can be transmitted and received through the uplink. In uplink communication, a transmitter may be part of a non-AP STA, and a receiver may be part of an AP STA.

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

The structure of a wireless LAN system can be composed of multiple components. A wireless LAN supporting transparent STA mobility to a higher layer can be provided through the interaction of multiple components. A BSS (Basic Service Set) corresponds to a basic configuration block of a wireless LAN. FIG. 2 illustrates an example in which two BSSs (BSS1 and BSS2) exist and two STAs are included as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). An ellipse 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 BSA (Basic Service Area). If an STA moves out of the BSA, it cannot directly communicate with other STAs within the corresponding BSA.

If we do not consider the DS illustrated in Fig. 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 that 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. This configuration is possible when STAs can communicate directly without an AP. In addition, in this type of wireless LAN, 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 performs management functions. 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.

The membership of an STA in a BSS can be dynamically changed by the STA turning on or off, the STA entering or leaving the BSS area, etc. To become a member of a BSS, an STA can join the BSS using a synchronization process. In order to access all services of the BSS infrastructure, an STA must be associated with a BSS. This association can be dynamically established and may include the use of a Distribution System Service (DSS).

In wireless LANs, the direct STA-to-STA distance may be limited by the PHY performance. In some cases, this distance limitation may be sufficient, but in some cases, communication between STAs over longer distances may be required. To support extended coverage, a distributed system (DS) may be configured.

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 shown in FIG. 2. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, a wireless medium (WM) and a DSM can be logically distinguished. Each logical medium is used for a different purpose and is used by different components. These media are neither limited to being the same nor limited to being different. In this way, the flexibility of a wireless LAN structure (DS structure or other network structure) can be explained in that multiple media are logically different. In other words, a wireless LAN structure can be implemented in various ways, and each wireless LAN structure can be independently specified by the physical characteristics of each implementation example.

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

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 a function that allows 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 need not necessarily be the same. A BSS consisting of an AP and one or more STAs can be called an infrastructure BSS.

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

In addition to the structure of the DS described above, an Extended Service Set (ESS) may be established to provide wider coverage.

An ESS is a network of arbitrary size and complexity consisting of DS and BSS. 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 being seen as an IBSS in the LLC (Logical Link Control) layer. STAs included in an ESS can communicate with each other, and mobile STAs can move from one BSS to another BSS (within the same ESS) transparently to the LLC. APs included in an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is an identifier of the BSS.

In a wireless LAN system, no assumption is made about the relative physical locations of the BSSs, and all of the following configurations are possible: The BSSs can be partially overlapped, which is a common configuration used to provide continuous coverage. Also, the BSSs can be physically unconnected, and logically there is no limit to the distance between the BSSs. Also, the BSSs can be physically co-located, which can be used to provide redundancy. Also, one (or more) IBSS or ESS networks can physically co-exist in the same space as one (or more) ESS networks. This can correspond to ESS network configurations such as cases where ad-hoc networks operate at locations where ESS networks exist, cases where physically overlapping wireless networks are configured by different organizations, or cases where two or more different access and security policies are required at the same location.

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

In order for an STA to set up a link to a network and send and receive data, it must first discover the network, perform authentication, establish an association, and go through authentication procedures for security. The link setup process may also be referred to as a session initiation process or a session setup process. In addition, the discovery, authentication, association, and security setup processes of the link setup process may be collectively referred to as the association process.

In step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access the network, it must find a network that it can participate in. The STA must identify a compatible network before participating in the wireless network, and the process of identifying networks existing in a specific area is called scanning.

There are two types of scanning methods: active scanning and passive scanning. FIG. 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 search for APs in the vicinity while moving between channels and waits for a response thereto. A responder transmits a probe response frame to the STA that transmitted the probe request frame as a response to the probe request frame. Here, the responder may be an STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, the AP transmits a beacon frame, so the AP becomes the responder, and 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 request/response on channel 2) in the same manner.

Although not shown in FIG. 3, the scanning operation can also be performed in a passive scanning manner. In passive scanning, an STA performing scanning moves through channels and waits for a beacon frame. A beacon frame is one of the management frames defined in IEEE 802.11, and is periodically transmitted to notify the existence of a wireless network and to enable an STA performing scanning to find a wireless network and participate in the wireless network. In a BSS, an AP periodically transmits a beacon frame, and in an IBSS, STAs in the IBSS take turns transmitting beacon frames. When an STA performing scanning receives a beacon frame, it stores information about the BSS included in the beacon frame and moves to another channel, recording beacon frame information on each channel. An STA receiving a beacon frame stores information related to the BSS included in the received beacon frame, moves to the next channel, and performs 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.

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

The authentication process includes the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used for the authentication request/response corresponds to a management frame.

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), a Finite Cyclic Group, etc. These are just some examples of information that may be included in an authentication request/response frame, and may be replaced by other information or may include additional information.

The STA may transmit an authentication request frame to the AP. The AP may determine whether to allow authentication for the STA based on information included in the received authentication request frame. The AP may provide the result of the authentication processing to the STA through an authentication response frame.

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.

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, RSN, mobility domains, 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., association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a Quality of Service (QoS) map, etc. These are just a few examples of the information that may be included in a combined request/response frame, and may be replaced by other information or include additional information.

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

The security setup process of step S340 may include a process of performing private key setup, for example, through 4-way handshaking via an Extensible Authentication Protocol over LAN (EAPOL) frame. Additionally, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.

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

In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is the CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA/CA mechanism is also called the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and basically adopts the "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 and then attempt to transmit frames. By applying the random backoff period, it is expected that multiple STAs will attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.

In addition, the IEEE 802.11 MAC protocol provides a 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 in which all receiving APs and/or STAs periodically poll to receive data frames. In addition, the HCF has EDCA (Enhanced Distributed Channel Access) and HCCA (HCF Controlled Channel Access). EDCA is a contention-based access method in which a provider provides data frames to multiple users, and HCCA uses a non-contention-based channel access method using a polling mechanism. In addition, the HCF includes a medium access mechanism for improving the QoS (Quality of Service) of a wireless LAN, and can transmit QoS data in both a contention period (CP) and a contention-free period (CFP).

Referring to Fig. 4, an operation based on a random backoff period is described. When an occupied/busy medium changes to an idle state, multiple STAs may attempt to transmit data (or frames). As a measure to minimize collisions, each STA may select a random backoff count, wait for the corresponding slot time, and then attempt to transmit. The random backoff count has a pseudo-random integer value and may 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 initially given CWmin, but may take a double value 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 may 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. It is desirable that the CW, CWmin and CWmax values be set to 2 ⁿ -1 (n=0, 1, 2, ...).

When the random backoff process starts, 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, and when the medium becomes idle, the remaining countdown is resumed.

In the example of Fig. 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can check that the medium is idle for DIFS and transmit the frame right away. The remaining STAs monitor whether the medium is occupied/busy and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can perform a countdown of the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS when 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 the countdown and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 resume the stopped backoff count after waiting for DIFS. That is, they can start frame transmission after counting down the remaining backoff slots by the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. 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, performs a countdown according to the random backoff count value it selected, and starts frame transmission. In the example of Fig. 4, the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, and in this 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 then starts transmitting frames after the remaining backoff time has elapsed.

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 such as DIFS or PIFS (Point coordination function IFS) elapses. Subtype frames of the 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 RTS (Request-To-Send), CTS (Clear-To-Send), ACK (Acknowledgment), PS-Poll (Power Save-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), NDP notification (null data packet announcement), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after the backoff performed after the DIFS (DIFS), and if it is a response frame to the previous frame, it is transmitted without the 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.

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, that is, 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.

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

As described above, the CSMA/CA mechanism includes virtual carrier sensing in addition to physical carrier sensing in which an STA directly senses the medium. Virtual carrier sensing is intended to complement problems that may occur in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of the STA may utilize a Network Allocation Vector (NAV). The NAV is a value that indicates to other STAs the remaining time until the medium becomes available, by an STA that is currently using or has the right to use the medium. Therefore, the value set as NAV corresponds to the period during which the medium is scheduled to be used by the STA transmitting the corresponding frame, and the STA that receives the NAV value is prohibited from accessing the medium during the corresponding period. For example, the NAV may be set based on the value of the "duration" field of the MAC header of the frame.

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 part or all of the frames transmitted and received between STA1 and STA2.

In order to reduce the possibility of collision of 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 carrier sensing result of the medium is idle. That is, STA1 may correspond to a hidden node to STA3. Alternatively, while STA2 is transmitting, STA3 may determine that the carrier sensing result of the medium is idle. That is, STA2 may correspond to a hidden node to STA3. Before performing data transmission and reception between STA1 and STA2, by exchanging RTS/CTS frames, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmission from STA1 or STA3 may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

Specifically, STA1 can determine whether a channel is occupied through carrier sensing. In terms of physical carrier sensing, STA1 can determine a channel occupied idle state based on energy magnitude or signal correlation detected in the channel. In addition, in terms of virtual carrier sensing, STA1 can determine a channel occupied state using a network allocation vector (NAV) timer.

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

If STA3 cannot overhear the CTS frame from STA2 but can overhear the RTS frame from STA1, STA3 can set a NAV timer for the subsequently transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) using the duration information included in the RTS frame. Alternatively, if STA3 cannot overhear the RTS frame from STA1 but can overhear the CTS frame from STA2, STA3 can set a NAV timer for the subsequently transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame) using the duration information included in the CTS 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. STA3 can update the NAV timer using the duration information contained in the new frame if it receives a new frame before the NAV timer expires. STA3 does not attempt to access the channel until the NAV timer expires.

If STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when reception of the CTS frame is completed. 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 other terminals during DIFS after the expiration of the NAV timer, it can attempt channel access after a contention window (CW) following a random backoff has elapsed.

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.

The PHY layer can prepare an MPDU (MAC PDU) to be transmitted by 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 information (e.g., data) provided from 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.

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.

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 a Legacy-STF (L-STF), a Legacy-LTF (L-LTF), a Legacy-SIG (Legacy-SIG) field, 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 represents HT, VHT, HE, EHT, etc.)) may be included between the L-SIG field and the data field. More specific details are described below with reference to FIG. 7.

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

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 a 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.

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 for synchronization of a descrambler at the receiving end. The PSDU corresponds to a MAC PDU defined at the MAC layer and may include data generated/used at a higher layer. The PPDU TAIL bit may be used to return the encoder to the 0 state. The padding bit may be used to adjust the length of the data field to a predetermined unit.

MAC PDU is defined according to various MAC frame formats, and the basic MAC frame consists of a MAC header, frame body, and FCS (Frame Check Sequence). MAC frame consists of MAC PDU and can be transmitted/received through PSDU of the data part of PPDU format.

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 a receiver address, a transmitter address, a destination address, and a 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.

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

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

Various forms of PPDUs are used in standards such as IEEE 802.11a/g/n/ac/ax. 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 called a non-HT PPDU format (Fig. 7(a)).

The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in 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, and consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).

An example of a 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)).

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 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 a HE PPDU format for multi-users (MUs), and the HE PPDU format for single users (SUs) does not include the HE-SIG-B. In addition, a 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. A 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 know that the received PPDU is a HE PPDU or an EHT PPDU, described later, based on the presence of RL-SIG.

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 it may include a U (universal)-SIG, an EHT-SIG, an EHT-STF, and an EHT-LTF following the RL-SIG.

The EHT MU PPDU in Fig. 7(e) corresponds to a PPDU that carries one or more data (or PSDU) 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.

The EHT TB PPDU of Fig. 7(f) omits 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.

The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz) so that even legacy STAs can attempt to demodulate and decode them. 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 and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz) so that they can be demodulated and decoded by an STA that successfully decodes a non-legacy SIG (e.g., U-SIG and/or EHT-SIG) and obtains the information included in the corresponding fields. These can be referred to as EHT modulated fields.

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.

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 4us, and the U-SIG can have a total duration of 8us. 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.

U-SIG can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be replicated 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-SIG of the first 80MHz unit and the U-SIG of the second 80MHz unit can be different.

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

The A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG may 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 may be the same, and some or all of the version-dependent bits may be different.

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.

For example, the version-independent bits of 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 PPDU. The version-independent bits of 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 U-SIG may include information about the length of a TXOP (transmission opportunity) and information about a BSS color ID.

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

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 an MCS technique applied to a non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique for achieving 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 over the entire band, etc.

Some of the information required for PPDU transmission and reception 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 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) applied to the non-legacy LTF, information about the preamble puncturing applicable to the PPDU, information about the 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.

Preamble puncturing may mean transmission of a PPDU in which no signal is present in one or more frequency units within the bandwidth of the PPDU. 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 predetermined size.

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

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

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

The number of user-specific fields can be determined based on the number of users. One user block field can include at most two user fields. Each user field can be associated with an MU-MIMO allocation or associated with a non-MU-MIMO allocation.

The common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, the length of the Tail bits may be determined as 6 bits and may be 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.

An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. An RU may also be defined when transmitting signals to one STA. Resources may be allocated in RU units for non-legacy STFs, non-legacy LTFs, and Data fields.

According to the PPDU bandwidth, an applicable size of RU 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 case of 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 tone plan for a low bandwidth.

RUs of different sizes can be defined, such as 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, 996-tone RU, 2Х996-tone RU, 3Х996-tone RU, etc. A multiple RU (MRU) is distinct 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-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2Х996+484-tones, 3Х996-tones, or 3Х996+484-tones. Additionally, multiple RUs constituting one MRU may or may not be consecutive in the frequency domain.

The specific size of the 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. In addition, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, ...) in the present disclosure, the number of RUs may vary depending on the RU size.

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 the names. In addition, 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.

Beacon Frames and Related Synchronization Procedures

A beacon frame is a frame that is periodically transmitted to notify the existence of a wireless network and to allow an STA performing scanning to find the wireless network and participate in the wireless network. A beacon frame may include at least one of a timestamp field, a beacon interval field, a capability information field, a service set identifier (SSID) field, an address field, a type field, and a subtype field.

The timestamp field may indicate a timing synchronization function timer of the source of the frame. The beacon interval field may indicate the number of time units between TBTTs. The capability field may include information related to the capability (e.g., the number of subfields used to indicate the requested or advertised capability).

STAs in a single infrastructure BSS, PBSS or IBSS can be synchronized to a common clock. The TSF can keep the timers of all STAs in the same BSS in sync. Any STA with "dot11OCBActivated" set to false can maintain a local TSF timer. An STA with "dot11OCBActivated" set to true can maintain the TSF timer for purposes other than synchronization.

In an infrastructure BSS or PBSS, an AP of an infrastructure BSS or a PCP of a PBSS can be the timing master of the TSF. In non-DMG and non-S1G BSS, an AP can periodically transmit a beacon frame. Instead of a beacon frame, an S1G AP can periodically transmit an S1G beacon frame, which provides similar functionality to the beacon frame of a non-S1G BSS.

Within an S1G BSS, the generation and/or reception of a beacon frame and any reference thereto may refer to the generation and/or reception of an S1G beacon frame. In a DMG BSS, an AP or PCP may periodically transmit DMG beacon frames and announcement frames, which may provide similar functionality to the beacon frames of a non-DMG BSS. The beacon, S1G beacon, DMG beacon and announcement frames may include the TSF timer value of the AP or PCP for synchronizing the TSF timers of other STAs in the BSS.

A receiving STA can accept timing information of a beacon frame, an S1G beacon frame, a DMG beacon frame, and an announcement frame sent by an AP or PCP serving a BSS. An S1G STA receiving an S1G beacon frame can update a TSF timer according to an algorithm. If the TSF timer of the STA is different from the timestamp of the received beacon frame, the S1G beacon frame, the DMG beacon frame, and the announcement frame, the receiving STA can set a local TSF timer to the received timestamp value. An STA receiving a frame including a timestamp field from a currently connected AP can update its local TSF by using the reception part of the TSF timer of the AP included in the received field.

Relay transmission procedure

In the next generation wireless LAN system, ultra-high reliability (UHR) can be supported when transmitting signals to STAs. To support UHR, various technologies for high throughput, low delay, and extended range delay can be applied. In addition, transmission and reception procedures using relays can be used in the next generation wireless LAN system.

In order to efficiently support STAs existing outside of AP coverage as well as STAs existing within AP coverage, the relay transmission/reception range can be expanded, and in order to expand the relay transmission/reception range, a management frame (e.g., a beacon frame, etc.) can be transmitted to at least one non-AP STA existing outside of AP coverage through the relay STA.

When transmitting a management frame (e.g., a beacon frame) to a non-AP STA via a relay STA, the MAC header of the management frame may be set to be identical to the MAC header of the legacy management frame in order to support legacy STAs. Accordingly, STAs within the AP coverage can receive both the management frame transmitted by the AP and the management frame transmitted by the relay STA.

Here, since the MAC frames of the two management frames (e.g., beacon frames) received from each of the AP and the relay STA are identical, a legacy STA existing within the AP coverage in a basic wireless LAN system may not be able to determine whether the entity that transmitted the management frame it received is the AP or the relay STA. In addition, ambiguity related to the reception procedure may occur due to the reception of duplicate management frames.

Below, we describe a method to reduce reception ambiguity of STAs within AP coverage during relay operation.

Relay procedure of STA existing at AP coverage boundary

In a next-generation wireless LAN system, a relay STA may be used to transmit and receive signals to and from STAs within the coverage boundary of an AP and to extend the coverage of the AP. The relay STA may transmit data received from an AP to other STA(s), or may transmit data received from other STA(s) to the AP. Here, the relay STA may be an AP or a non-AP STA.

As an example of the present disclosure, as illustrated in FIG. 8, a relay STA can transmit and receive signals with an STA (e.g., a destination STA) (e.g., a non-AP STA 2) that exists outside the AP coverage.

Specifically, assume a case where a relay STA is used to transmit and receive signals to and from STAs that exist outside the AP coverage/range. As illustrated in FIG. 8, a frame transmitted by an AP (e.g., a management frame) can be transmitted to STAs (e.g., non-AP STA 1 and/or non-AP STA 2) via the relay STA.

At this time, the AP cannot directly transmit a management frame (e.g., a beacon frame) to an STA (e.g., a non-AP STA 2) that is outside the coverage/range. Therefore, the relay STA can receive the beacon frame transmitted by the AP and broadcast the received beacon frame. Accordingly, the beacon frame transmitted by the relay STA can be transmitted not only to the non-AP STA 2 that is outside the AP coverage but also to the non-AP STA 1 located near the relay STA (e.g., a non-AP STA located within the AP coverage).

Therefore, a non-AP STA located within the AP coverage (e.g., a non-AP STA located near a relay STA) may repeatedly receive a beacon frame, which may cause ambiguity related to beacon frame reception. Hereinafter, a method for resolving ambiguity in the reception procedure due to duplicate reception of a beacon frame will be described.

FIG. 9 is a flowchart for explaining a method performed by a first STA according to an embodiment of the present disclosure. In FIG. 9 and FIG. 10, the first STA is described as a non-AP STA located within the coverage of the BSS of the AP, but is not limited thereto. For example, the first STA may be located outside the coverage of the BSS of the AP and may be implemented as an AP.

The first STA can receive the first management frame from the AP (S910).

Here, the first management frame may be, but is not limited to, a beacon frame. The first STA may receive various types of management frames from the AP within the BSS.

The first STA can receive a second management frame from the second STA within a specific time interval after receiving the first management frame (S920).

For example, the particular time interval may be a target beacon transmission time (TBTT) or a beacon interval.

For example, a second STA (e.g., a relay STA) may generate a second management frame based on a first management frame (or, a separate management frame, etc.) received from the AP. That is, the second STA may generate a second management frame based on the first management frame in order to forward the first management frame received from the AP to another STA (e.g., an STA located inside or outside the coverage of the AP). In this case, the second STA may transmit the second management frame in a broadcast manner, but is not limited thereto.

As an example of the present disclosure, the second management frame transmitted by the second STA (e.g., a relay STA) may be a relay beacon frame (i.e., a beacon frame for relay transmission) or an action frame related to relay transmission.

For example, the type field included in the second management frame may be set to a first number, and the subtype field included in the second management frame may be set to a second number. Here, the first number may be “00” or “11”, and the second number may be one of “0010” to “1111”. However, this is only one embodiment, and each of the first number and the second number may be set to different values.

Additionally or alternatively, the address 1 field included in the second management frame may be set to an ID or broadcast ID associated with the destination STA, and the address 2 field included in the second management frame may be set to an ID (identifier) of the second STA, an ID of the BSS of the AP, or an ID of the AP.

Through the type field, subtype field and/or address 1/2 field of the second management frame described above, the first STA can identify that the second management frame is a management frame transmitted by the relay STA.

At this time, the first STA may be a first type STA. The first type STA may include a capability capable of decoding a second management frame transmitted by the second STA. That is, the first type STA may decode a frame related to a relay operation.

The first STA can determine whether i) a type field, a subtype field, at least one address field, and an SSID (service set identifier) value included in the first management frame and ii) a type field, a subtype field, at least one address field, and an SSID value included in the second management frame are identical.

Based on the first STA being a first type STA, the first STA may discard or ignore the second management frame or update at least one type of information included in the first management frame based on the second management frame (S930).

Here, if i) the type field, the subtype field, the at least one address field and the SSID value included in the first management frame and ii) the type field, the subtype field, the at least one address field and the SSID value included in the second management frame are determined to be the same by the first STA, the operation according to step S930 and the operation described below may be performed.

For example, the first STA may update at least one type of information included in the first management frame through information included in the second management frame. For example, the information about the at least one type may include information about a timing synchronization function (TSF) timer associated with a timestamp field. That is, the first STA may update a TSF timer associated with the first management frame according to a timestamp field value included in the second management frame.

As another example, the first STA may ignore or discard a second management frame received later.

As an example of the present disclosure, if the first STA is a second type of STA (e.g., an STA that does not include a capability to decode a second management frame transmitted by the second STA), the first STA may not be able to recognize and decode the second management frame transmitted by the second STA. Accordingly, the first STA can only decode and use the first management frame transmitted by the AP.

The method described in the example of FIG. 9 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may receive a first management frame from an AP through one or more transceivers (106). The one or more processors (102) may receive a second management frame from a second STA through one or more transceivers (106) within a specific time interval after receiving the first management frame. The one or more processors (102) may discard the second management frame or update at least one type of information included in the first management frame based on the second management frame.

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

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

The second STA can receive a first management frame from the AP (S1010). That is, the second STA can receive a management frame to be transmitted to another STA from the AP.

The second STA can transmit a second management frame based on the first management frame to at least one STA (S1020).

For example, the second STA may generate a second management frame (e.g., a second management frame including information of the first management frame) based on the first management frame. Then, the second STA may transmit the second management frame in a broadcast manner, and at least one STA may receive the second management frame transmitted in a broadcast manner.

At least one STA may include a non-AP STA located outside the BSS coverage of the AP and/or a first STA within the BSS coverage of the AP.

The second management frame may be ignored or discarded by the first STA, or may be used to update information in the first management frame.

The method described in the example of FIG. 10 can 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 can receive a first management frame from an AP through one or more transceivers (206). The one or more processors (102) can transmit a second management frame based on the first management frame to at least one STA through one or more transceivers (206).

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

Below, the operation and composition of the management frame when an STA within AP coverage repeatedly receives management frames from an AP or/and relay STA are specifically described.

Example 1

Embodiment 1 relates to an operation when an STA within AP coverage repeatedly receives management frames (e.g., beacon frames) from the AP and/or relay STAs. As an example, a management frame transmitted (e.g., broadcasted) by a relay STA to STAs within AP coverage may include a frame transmitted by the AP to the relay STA, etc.

Example 1-1

In one embodiment of the present disclosure, if an STA (located within AP coverage) repeatedly receives the same beacon frame, the STA may ignore or discard the beacon frame.

For example, assume that an STA (e.g., a legacy STA located within the AP coverage) successfully receives a beacon frame from the AP. After receiving the beacon frame from the AP, the STA may ignore or discard other beacon frames received within the target beacon transmission time (TBTT) or beacon interval. That is, the STA may not perform a reception procedure for the other beacon frames. Here, the beacon interval may mean the time interval between two consecutive TBTTs.

In order to perform the above-described reception procedure, a non-AP STA that repeatedly receives a beacon frame can check the values of the type field, subtype field, and address field included in the MAC header of the received beacon frame. The non-AP STA can check whether the received beacon frame is a repeatedly received frame through the type field, subtype field, and address field included in the MAC header.

For example, if the type field, subtype field, and address field are set as described below, a non-AP STA may ignore or discard a frame (e.g., a repeatedly received frame) containing the type field, subtype field, and address field:

- The type field and subtype field are each set to "00" and "1000" respectively.

- The Address 1 field is set to the broadcast ID (e.g., destination ID) and the Address 2 field is set to the BSS ID or AP_ID (e.g., source ID) with the Type field and Subtype field each set to "00" and "1000" respectively.

Additionally or alternatively, the non-AP STA may verify the SSID of the received beacon frame. If the SSID of the verified beacon frame is the same as the SSID of a previously received beacon frame, the non-AP STA may ignore or discard the previously received beacon frame.

Example 1-2

In one embodiment of the present disclosure, information of a previously received beacon frame can be overlaid based on repeatedly received beacon frame information.

For example, assume that an STA (e.g., a legacy non-AP STA located within the AP coverage) successfully receives a beacon frame from an AP. After receiving the beacon frame, if a relay STA transmits a beacon frame within the beacon interval or TBTT, the STA (e.g., a non-AP STA) may perform at least one of the following actions:

- The STA can detect/identify information (e.g., type field, subtype field, address field, SSID, etc.) included in the most recently received beacon frame, and check whether the detected/identified information is identical to the corresponding information included in the previously received beacon frame.

- If it is determined that the information included in the most recently received beacon frame and the corresponding information included in the previously received beacon frame are identical, the STA may perform becoding on the most recently received beacon frame to obtain the information of the beacon frame.

- The STA can perform an update on the information and content of the previously received beacon frame using the information and content of the most recently received beacon frame.

At this time, if the timestamp field value included in the most recently received beacon frame is greater than the timestamp field value included in the previously received beacon frame, the STA can update the TSF timer using the timestamp field value included in the most recently received beacon frame. That is, if the TSF timer corresponding to the timestamp field included in the most recently received beacon frame is later (later) than the TSF timer corresponding to the timestamp field included in the previously received beacon frame, the STA can update the TSF timer using the timestamp field value included in the most recently received beacon frame.

Otherwise (e.g., if the TSF timer corresponding to the timestamp field included in the most recently received beacon frame is equal to or earlier than the TSF timer of the previously received beacon frame), the STA may not update the TSF timer.

Example 2

Embodiment 2 relates to the configuration of a beacon frame transmitted by a relay STA. Information of a beacon frame transmitted by a relay STA can be transmitted through another action frame, and thus ambiguity regarding duplicate reception of a beacon frame by an STA (e.g., a non-AP STA within the coverage of an AP) can be reduced. Transmission support for an STA existing outside the coverage of an AP by using a relay procedure can be applied to an STA of an IEEE 802.11 bn-based wireless LAN system or a STA of a later version, but is not limited thereto.

Example 2-1

In one embodiment of the present disclosure, a beacon frame transmitted by a relay STA can be defined as a new type/version of beacon frame.

A beacon frame transmitted by a relay STA may be defined as a new relay beacon frame. The type field and the subtype field in the frame control field of the relay beacon frame may be set to specific values, which may indicate that the corresponding beacon frame is a relay beacon frame. For example, if the type field value is set to "11" and the subtype field value is set to one of "0010" to "1111", this may indicate that the corresponding beacon frame is a relay beacon frame.

Additionally or alternatively, the address field of a relay beacon frame may be set according to the example described below, which may indicate that the beacon frame is a relay beacon frame:

- Address 1 field is set to broadcast address

- Address 2 field is set to the relay STA ID that transmits the relay beacon frame.

- The Address 3 field is set to the BSS ID of the AP that transmitted the beacon frame transmitted by the relay STA (i.e., the AP that transmits the beacon frame through the relay STA) or the transmitted BSSID.

Since the relay beacon frame defined as described above is transmitted through the relay STA, legacy STAs (e.g., STAs of versions prior to UHR STA) cannot recognize and decode the relay beacon frame. Therefore, reception errors due to duplicate reception of beacon frames by legacy STAs can be prevented.

Example 2-2

In one embodiment of the present disclosure, a relay STA can transmit information of a beacon frame through a new type of action frame.

A relay STA may use a newly defined action frame to transmit a beacon frame received from an AP. The category field value of the newly defined action frame may be set to a specific value among 33 to 125 or 128 to 255. When the category field is set to a specific value, this may mean that the action frame (e.g., category name/meaning) is related to a relay operation. An action frame with the category field set to a specific value may be expressed/defined as a relay operation action frame, but is not limited thereto.

For example, the relay operation action frame may include the same information as the information in the beacon frame received from the AP. As another example, the relay operation action frame may be constructed based on the remainder of the information in the beacon frame received from the AP, excluding some of the information.

In the embodiments described above (e.g., Embodiment 1, Embodiment 2, and detailed embodiments of Embodiments 1 and 2, etc.), the beacon frame may be replaced with another type of management frame. That is, the method described in the embodiments described above may be applied not only to the beacon frame but also to another type of management frame.

By the above-described embodiments, even if the management frame transmitted by the AP and the relay STA is repeatedly transmitted, the ambiguity due to the repeated transmission of the management frame by the STA can be resolved. Accordingly, the influence of the transmission and reception operation of the relay STA on the legacy STA can be reduced, and the range extension through the relay operation can be achieved.

The embodiments described above are combinations of components and features of the present disclosure in a given form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, it is also possible to combine some components and/or features to form an embodiment of the present disclosure. 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 obvious that claims that do not have an explicit citation relationship in the scope of the patent may be combined to form an embodiment or may be included as a new claim by post-application amendment.

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 of the present disclosure. Accordingly, the above detailed description should not be construed as limiting in all respects but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present disclosure are intended to be included in the scope of the present disclosure.

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 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 comprises a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and/or firmware stored on any one of the machine-readable media to control the hardware of the processing system and to 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.

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 (15)

A step of receiving a first management frame from an access point (AP) by a first station (STA); A step of receiving a second management frame from a second STA by the first STA within a specific time interval after receiving the first management frame; and A step of discarding the second management frame by the first STA based on the first STA being a first type STA or updating at least one type of information included in the first management frame based on the second management frame, The above first STA is located within the coverage of the BSS (basic service set) of the AP, A method wherein the second management frame is based on the first management frame. In the first paragraph, The type field included in the above second management frame is set to the first number, The subtype field included in the above second management frame is set to a second number, The address 1 field included in the above second management frame is set to a broadcast ID or an ID associated with the destination STA, A method in which the address 2 field included in the second management frame is set to the ID (identifier) of the second STA, the ID of the BSS of the AP, or the ID of the AP. In the second paragraph, The above first number is "00" or "11", A method wherein the second numerical value is one of "0010" to "1111". In the first paragraph, A method wherein it is determined by the first STA whether i) a type field, a subtype field, at least one address field and an SSID (service set identifier) value included in the first management frame and ii) a type field, a subtype field, at least one address field and an SSID value included in the second management frame are identical. In the first paragraph, A method wherein the information about at least one type includes information about a timing synchronization function (TSF) timer associated with a timestamp field. In the first paragraph, The above first type of STA includes a capability capable of decoding the second management frame transmitted by the second STA, A method wherein a second type of STA does not include a capability for decoding the second management frame transmitted by the second STA. In Article 6, A method wherein the second management frame is not decoded by the first STA based on the first STA being an STA of the second type. In the first paragraph, A method wherein the second management frame is a relay beacon frame or an action frame related to relay transmission. In the first paragraph, The second management frame is generated based on the first management frame transmitted from the AP to the second STA, A method, wherein the second management frame is broadcast by the second STA. In the first paragraph, A method wherein the specific time interval is a target beacon transmission time (TBTT) or beacon interval. In a first station (STA), the first STA: one or more transmitters and receivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receiving a first management frame from an access point (AP) via one or more of the transceivers; After receiving the first management frame, receiving a second management frame from a second STA through the one or more transceivers within a specific time interval; and Based on the first STA being a first type STA, the second management frame is set to be discarded by the first STA or at least one type of information included in the first management frame is updated based on the second management frame. The above first STA is located within the coverage of the BSS (basic service set) of the AP, The second management frame is based on the first management frame, the first STA. A step of receiving a first management frame from an access point (AP) by a second station (STA); and Comprising a step of transmitting a second management frame based on the first management frame to at least one STA by the second STA, Based on the first STA included in the at least one STA being a first type STA, the second management frame is discarded by the first STA or at least one type of information included in the first management frame is updated based on the second management frame. A method wherein the second management frame is transmitted by the second STA to the at least one STA within a specific time interval after receiving the first management frame. In a second station (STA), the second STA: one or more transmitters and receivers; and comprising one or more processors coupled to said one or more transceivers; One or more of the above processors: Receiving a first management frame from an access point (AP) via one or more of said transceivers; and It is set to transmit a second management frame based on the first management frame to at least one STA through the one or more transceivers, Based on the first STA included in the at least one STA being a first type STA, the second management frame is discarded by the first STA or at least one type of information included in the first management frame is updated based on the second management frame. The second management frame is transmitted by the second STA to the at least one STA within a specific time interval after receiving the first management frame. A processing device configured to control a first station (STA) operating in a wireless LAN system, the processing device comprising: one or more processors; and One or more computer memories operatively connected to said one or more processors and storing instructions that perform operations based on execution by said one or more processors, The above actions are: An action of receiving a first management frame from an access point (AP); An operation of receiving a second management frame from a second STA within a specific time interval after receiving the first management frame; and An operation of discarding the second management frame or updating at least one type of information included in the first management frame based on the second management frame, based on the first STA being a first type STA, The above first STA is located within the coverage of the BSS (basic service set) of the AP, A processing device, wherein the second management frame is based on the first management frame. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, so that the device operating in the wireless LAN system: Receive a first management frame from an access point (AP); After receiving the first management frame, receiving a second management frame from the second STA within a specific time interval; and Based on the first STA being a first type STA, the second management frame is controlled to be discarded or at least one type of information included in the first management frame is updated based on the second management frame. The above first STA is located within the coverage of the BSS (basic service set) of the AP, A computer-readable medium wherein the second management frame is based on the first management frame.

Images