Method and device for transmitting or receiving in-device coexistence-related information in wireless LAN system

Abstract

Disclosed are a method and a device for transmitting or receiving in-device coexistence-related information in a wireless LAN system. A method according to an embodiment of the present disclosure may comprise the steps of: transmitting, by a first station (STA), a first frame including first information related to an unavailability operation to a second STA; and transmitting a second frame to the second STA by the first STA on the basis of timing of the period of an i-th unavailability operation, among the periods of one or more unavailability operations related to the first information, having been changed, wherein the second frame includes second information related to whether the timing of the period of the i-th unavailability operation has been changed and third information related to an identifier of the period of the i-th unavailability operation, and the period of the i-th unavailability operation is determined on the basis of the second frame.

Description

Method and device for transmitting or receiving information related to internal coexistence of a terminal in a wireless LAN system

[0001] The present disclosure relates to a method and device for transmitting or receiving information related to in-device coexistence (IDC) in a wireless local area network (WLAN) system.

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

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

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting or receiving information related to in-device coexistence (IDC) in a wireless LAN system.

[0005] The technical challenge of the present disclosure is to provide a method and device for signaling information related to aperiodic events of IDC through a new frame.

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

[0007] A method according to one embodiment of the present disclosure comprises the steps of: transmitting, by a first station (STA), a first frame including first information related to an unavailability operation to a second STA; and transmitting, by the first STA, a second frame to the second STA based on a change in timing of a period of an i-th unavailability operation among periods of at least one unavailability operation related to the first information, wherein the second frame includes second information related to whether the timing of the period of the i-th unavailability operation has changed and third information related to an identifier of the period of the i-th unavailability operation, wherein the period of the i-th unavailability operation can be determined based on the second frame.

[0008] According to another embodiment of the present disclosure, a method comprises the steps of: receiving, by a second station (STA), from a first STA a first frame including first information related to an unavailability operation; and receiving, by the second STA, a second frame from the first STA based on a change in timing of a period of an i-th unavailability operation among periods of at least one unavailability operation related to the first information, wherein the second frame includes second information related to whether the timing of the period of the i-th unavailability operation has changed and third information related to an identifier of the period of the i-th unavailability operation, wherein the period of the i-th unavailability operation can be determined based on the second frame.

[0009] According to various embodiments of the present disclosure, a method and device for transmitting or receiving IDC-related information in a wireless LAN system can be provided.

[0010] According to various embodiments of the present disclosure, a method and apparatus for signaling information related to an aperiodic event of an IDC through a new frame may be provided.

[0011] By various embodiments of the present disclosure, performance degradation that may occur due to an IDC event can be prevented.

[0012] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0013] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

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

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

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

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

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

[0019] FIG. 6 is a drawing for explaining an example of a frame structure used in a wireless LAN system to which the present disclosure can be applied.

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

[0021] FIG. 8 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

[0022] FIG. 9 is a diagram illustrating a procedure for performing IDC event signaling using IDC TWT setup request and response frames.

[0023] Figure 10 is a diagram for explaining a situation in which the IDC TWT SP timing changes.

[0024] FIG. 11 is a drawing for explaining an example of a method performed by a first STA according to the present disclosure.

[0025] FIG. 12 is a diagram illustrating an example of a method performed by a second STA according to the present disclosure.

[0026] FIG. 13 and FIG. 14 are diagrams for explaining the configuration of IDC information according to one embodiment of the present disclosure.

[0027] FIG. 15, FIG. 16, FIG. 17, FIG. 18 and FIG. 19 relate to a method of transmitting information for an IDC using A-control according to one embodiment of the present disclosure.

[0028] FIG. 20 is a diagram illustrating control information subfields on IDCS, IDCD, and IDCCN subfields according to one embodiment of the present disclosure.

[0029] FIG. 21 is a diagram for explaining a control information subfield on an IDCR subfield according to one embodiment of the present disclosure.

[0030] FIG. 22 is a diagram illustrating a BSRP trigger frame with a general response according to one embodiment of the present disclosure.

[0031] FIG. 23 is a diagram illustrating a method for transmitting IDC information via an unsolicited control frame and / or action frame according to one embodiment of the present disclosure.

[0032] FIG. 24 is a diagram for explaining an action frame response of a BSRP trigger frame according to one embodiment of the present disclosure.

[0033] FIG. 25 is a diagram for explaining the configuration and related procedures of a compressed BA frame according to one embodiment of the present disclosure.

[0034] FIG. 26 and FIG. 27 are diagrams for explaining the configuration and related procedures of IDC information in a multi-STA BA frame according to one embodiment of the present disclosure.

[0035] FIG. 28 is a diagram illustrating a situation in which a periodic IDC event occurs according to one embodiment of the present disclosure.

[0036] FIG. 29 is a diagram for explaining a method for instructing a timing change of a TWT SP based on a BA frame according to one embodiment of the present disclosure.

[0037] FIG. 30 is a diagram illustrating a method for instructing a timing change of a TWT SP based on a QoS null frame according to one embodiment of the present disclosure.

[0038] FIG. 31 is a diagram illustrating a method for notifying periodic IDC information according to one embodiment of the present disclosure.

[0039] FIG. 32 is a diagram illustrating a method for instructing a timing change of a TWT SP based on a new control frame according to one embodiment of the present disclosure.

[0040] FIG. 33 is a diagram for explaining a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure.

[0041] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

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

[0043] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

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

[0045] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0046] The examples of the present disclosure can be applied to various wireless communication systems. For example, the examples of the present disclosure can be applied to a wireless LAN system. For example, the examples of the present disclosure can be applied to a wireless LAN based on the IEEE 802.11a / g / n / ac / ax / be standards. Furthermore, the examples of the present disclosure can be applied to a wireless LAN based on the newly proposed IEEE 802.11bn (or UHR) standard. Additionally, the examples of the present disclosure can be applied to a wireless LAN based on the next-generation standard after IEEE 802.11bn. Furthermore, the examples of the present disclosure can be applied to a cellular wireless communication system. For example, the examples of the present disclosure can be applied to a cellular wireless communication system based on the LTE (Long Term Evolution) series of technologies and the 5G NR (New Radio) series of technologies of the 3rd Generation Partnership Project (3GPP) standard.

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

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

[0049] The first device (100) and the second device (200) illustrated in FIG. 1 may be replaced with various terms such as a terminal, a wireless device, a WTRU (Wireless Transmit Receive Unit), a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an MSS (Mobile Subscriber Unit), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), or simply a user. In addition, the first device (100) and the second device (200) may be replaced with various terms such as an access point (AP), a BS (Base Station), a fixed station, a Node B, a BTS (Base Transceiver System), a network, an AI (Artificial Intelligence) system, an RSU (road side unit), a repeater, a router, a relay, a gateway, etc.

[0050] The devices (100, 200) illustrated in FIG. 1 may also be referred to as stations (STAs). For example, the devices (100, 200) illustrated in FIG. 1 may be referred to by various terms such as transmitting device, receiving device, transmitting STA, and receiving STA. For example, the STAs (110, 200) may perform an AP (access point) role or a non-AP role. That is, in the present disclosure, the STAs (110, 200) may perform the functions of an AP and / or a non-AP. When the STAs (110, 200) perform an AP function, they may simply be referred to as APs, and when the STAs (110, 200) perform a non-AP function, they may simply be referred to as STAs. In addition, in the present disclosure, the APs may also be referred to as AP STAs.

[0051] Referring to FIG. 1, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless LAN technologies (e.g., IEEE 802.11 series). The first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.11 standard.

[0052] In addition, the first device (100) and the second device (200) may additionally support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) other than wireless LAN technology. In addition, the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

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

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

[0055] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0056] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0057] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

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

[0059] For example, one of the STAs (100, 200) may perform the intended operation of an AP, and the other of the STAs (100, 200) may perform the intended operation of a non-AP STA. For example, the transceivers (106, 206) of FIG. 1 may perform transmission and reception operations of signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.11a / b / g / n / ac / ax / be / bn, etc.). In addition, in the present disclosure, operations in which various STAs generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals may be performed in the processors (102, 202) of FIG. 1. For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include 1) an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of a field (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in a PPDU, 2) an operation for determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 3) an operation for determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a field (SIG, STF, LTF, Data, etc.) included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (104, 204) of FIG. 1.

[0060] Hereinafter, downlink (DL) refers to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. can be transmitted and received through the downlink. In downlink communication, the transmitter may be part of an AP STA, and the receiver may be part of a non-AP STA. Uplink (UL) refers to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. can be transmitted and received through the uplink. In uplink communication, the transmitter may be part of a non-AP STA, and the receiver may be part of an AP STA.

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

[0062] The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports transparent STA mobility to the upper layer can be provided. A Basic Service Set (BSS) corresponds to a basic building block of a wireless LAN. FIG. 2 illustrates, by way of example, the existence of two BSSs (BSS1 and BSS2) and the inclusion of two STAs as members of each BSS (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2). The oval representing a BSS in FIG. 2 can also be understood as representing a coverage area in which STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). When an STA moves outside of a BSA, it cannot directly communicate with other STAs within the BSA.

[0063] If we do not consider the DS illustrated in Figure 2, the most basic type of BSS in a wireless LAN is an Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For example, assuming other components are omitted, BSS1 consisting of only STA1 and STA2, or BSS2 consisting of only STA3 and STA4, can be representative examples of an IBSS, respectively. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, in this type of WLAN, a LAN can be configured when needed rather than being planned in advance, and this can be called an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. That is, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems (DS) is not permitted, forming a self-contained network.

[0064] An STA's membership in a BSS can dynamically change, for example, when an STA is turned on or off, or when an STA enters or leaves a BSS area. To become a member of a BSS, an STA can join the BSS using a synchronization process. To access all services in the BSS infrastructure, an STA must be associated with the BSS. This association can be dynamically established and may involve the use of a Distribution System Service (DSS).

[0065] In a wireless LAN, the direct STA-to-STA distance can be limited by PHY performance. While this distance limit may be sufficient in some cases, communication between STAs over longer distances may be required in other cases. To support extended coverage, a distributed system (DS) can be configured.

[0066] DS refers to a structure in which BSSs are interconnected. Specifically, a BSS may exist as an extended component of a network composed of multiple BSSs, as illustrated in Figure 2. DS is a logical concept and can be specified by the characteristics of a distributed system medium (DSM). In this regard, the Wireless Medium (WM) and DSM can be logically distinguished. Each logical medium is used for a different purpose and by different components. These media are neither limited to being identical nor limited to being different. This logical difference between multiple media explains the flexibility of the WLAN architecture (DS architecture or other network architectures). In other words, the WLAN architecture can be implemented in various ways, and the physical characteristics of each implementation can independently specify the WLAN architecture.

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

[0068] An AP is an entity that enables access to a DS through a WM for associated non-AP STAs and also has the functionality of an STA. Data movement between a BSS and a DS can be performed through an AP. For example, STA2 and STA3 illustrated in FIG. 2 have the functionality of an STA and provide the function of allowing associated non-AP STAs (STA1 and STA4) to access the DS. In addition, since all APs are basically STAs, all APs are addressable entities. The address used by an AP for communication on a WM and the address used by an AP for communication on a DSM do not necessarily have to be the same. A BSS consisting of an AP and one or more STAs can be referred to as an infrastructure BSS.

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

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

[0071] An ESS is a network of arbitrary size and complexity, consisting of DSs and BSSs. An ESS may correspond to a set of BSSs connected to a DS. However, an ESS does not include a DS. An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs within an ESS can communicate with each other, and mobile STAs can move from one BSS to another (within the same ESS) transparently to the LLC. APs within an ESS may have the same SSID (service set identification). The SSID is distinct from the BSSID, which is the identifier of the BSS.

[0072] In a wireless LAN system, no assumptions are made about the relative physical locations of BSSs, and all of the following configurations are possible: BSSs can be partially overlapping, which is commonly used to provide continuous coverage. BSSs can also be physically disconnected, and there is no logical distance limit between them. BSSs can also be physically co-located, which can be used to provide redundancy. Furthermore, one (or more) IBSS or ESS networks can physically co-exist with one (or more) ESS networks. This can occur in cases where an ad-hoc network operates at the same location as an ESS network, where physically overlapping wireless networks are configured by different organizations, or where two or more different access and security policies are required at the same location.

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

[0074] For an STA to set up a link and transmit and receive data on a network, it must first discover the network, perform authentication, establish an association, and complete security authentication procedures. The link setup process can also be referred to as the session initiation process or session setup process. Furthermore, the discovery, authentication, association, and security setup processes of the link setup process can be collectively referred to as the association process.

[0075] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning operations by the STA. That is, for the STA to access a network, it must search for available networks. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning.

[0076] Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation including an active scanning process as an example. In active scanning, an STA performing scanning transmits a probe request frame to discover any APs in the vicinity while moving between channels and waits for a response. The responder transmits a probe response frame in response to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame in the BSS of the channel being scanned. In the BSS, the AP transmits the beacon frame, so the AP becomes the responder. In the IBSS, the STAs within the IBSS take turns transmitting beacon frames, so the responder is not fixed. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning (i.e., transmitting and receiving probe requests / responses on channel 2) in the same manner.

[0077] Although not shown in Figure 3, the scanning operation can also be performed in a passive scanning manner. In passive scanning, the STA performing the scanning moves between channels and waits for a beacon frame. A beacon frame is one of the management frames defined in IEEE 802.11. It announces the existence of a wireless network and is periodically transmitted so that the STA performing the scanning can find the wireless network and participate in the wireless network. In the BSS, the AP performs the role of periodically transmitting the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the STA performing the scanning receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. The STA receiving the beacon frame stores the BSS-related information included in the received beacon frame and moves to the next channel to perform scanning on the next channel in the same manner. Comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

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

[0079] The authentication process involves the STA sending an authentication request frame to the AP, and the AP responding by sending an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0080] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group. These are just some examples of information that may be included in an authentication request / response frame, and may be replaced with other information or include additional information.

[0081] An STA can send an authentication request frame to an AP. The AP can determine whether to grant authentication to the STA based on the information contained in the received authentication request frame. The AP can provide the result of the authentication process to the STA via an authentication response frame.

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

[0083] For example, the association request frame may include information about various capabilities, a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, an RSN, a mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, interworking service capabilities, etc. For example, the association response frame may include information about various capabilities, a status code, an Association ID (AID), supported rates, an Enhanced Distributed Channel Access (EDCA) parameter set, a Received Channel Power Indicator (RCPI), a Received Signal to Noise Indicator (RSNI), a mobility domain, a timeout interval (e.g., an association comeback time), overlapping BSS scan parameters, a TIM broadcast response, a Quality of Service (QoS) map, etc. These are just some examples of information that may be included in a combined request / response frame, and may be replaced by other information or include additional information.

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

[0085] The security setup process of step S340 may include, for example, a process of establishing a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame. Furthermore, the security setup process may be performed according to a security method not defined in the IEEE 802.11 standard.

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

[0087] In wireless LAN systems, the basic access mechanism of MAC (Medium Access Control) is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). The CSMA / CA mechanism, also known as the Distributed Coordination Function (DCF) of the IEEE 802.11 MAC, essentially employs a "listen before talk" access mechanism. According to this type of access mechanism, the AP and / or STA may perform a Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time period (e.g., a DCF Inter-Frame Space (DIFS)) before starting transmission. If the sensing result determines that the medium is in an idle state, the AP and / or STA may start transmitting frames through the medium. On the other hand, if the medium is detected to be occupied or busy, the AP and / or STA may not start its own transmission, but may wait for a delay period (e.g., a random backoff period) for medium access before attempting to transmit frames. By applying a random backoff period, multiple STAs are expected to attempt to transmit frames after waiting for different periods of time, thereby minimizing collisions.

[0088] In addition, the IEEE 802.11 MAC protocol provides the Hybrid Coordination Function (HCF). The HCF is based on the DCF and the Point Coordination Function (PCF). The PCF is a polling-based synchronous access method that periodically polls all receiving APs and / or STAs to ensure that they receive data frames. In addition, the HCF has the Enhanced Distributed Channel Access (EDCA) and the HCF Controlled Channel Access (HCCA). The EDCA is a contention-based access method for a provider to provide data frames to multiple users, while the HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, the HCF includes a medium access mechanism to improve the Quality of Service (QoS) of the wireless LAN, and can transmit QoS data in both the Contention Period (CP) and the Contention Free Period (CFP).

[0089] Referring to Fig. 4, an operation based on a random backoff period is described. When a medium that was occupied / busy changes to an idle state, multiple STAs can attempt to transmit data (or frames). To minimize collisions, each STA can select a random backoff count, wait for the corresponding slot time, and then attempt transmission. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​in the range of 0 to CW. Here, CW is a contention window parameter value. The CW parameter is given an initial value of CWmin, but can take a value doubled in case of transmission failure (e.g., when an ACK for a transmitted frame is not received). When the CW parameter value becomes CWmax, data transmission can be attempted while maintaining the CWmax value until data transmission is successful, and if data transmission is successful, it is reset to the CWmin value. The CW, CWmin, and CWmax values ​​are 2. n It is desirable to set it to -1 (n=0, 1, 2, ...).

[0090] Once the random backoff process begins, the STA continues to monitor the medium while counting down the backoff slots according to the determined backoff count value. If the medium is monitored as occupied, the countdown stops and waits. When the medium becomes idle, the remaining countdown resumes.

[0091] In the example of FIG. 4, when a packet to be transmitted reaches the MAC of STA3, STA3 can immediately transmit a frame if it confirms that the medium is idle for DIFS. The remaining STAs monitor the medium for occupied / busy states and wait. In the meantime, data to be transmitted may also occur in each of STA1, STA2, and STA5, and each STA can count down the backoff slot according to a random backoff count value selected by each STA after waiting for DIFS if the medium is monitored as idle. Assume that STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. In other words, this example shows a case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 finishes the backoff count and starts frame transmission. STA1 and STA5 briefly stop counting down and wait while STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the backoff count that they had stopped. That is, they can start transmitting frames after counting down the remaining backoff slots equal to the remaining backoff time. Since STA5's remaining backoff time is shorter than STA1's, STA5 starts transmitting frames. While STA2 occupies the medium, STA4 may also have data to transmit. From STA4's perspective, when the medium becomes idle, it waits for DIFS, counts down according to its selected random backoff count value, and then starts transmitting frames. In the example of Figure 4, the remaining backoff time of STA5 coincidentally matches the random backoff count value of STA4, in which case a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 will receive an ACK, resulting in a failure in data transmission.In this case, STA4 and STA5 can select a random backoff count value and perform a countdown after doubling the CW value. STA1 waits while the medium is occupied by transmissions from STA4 and STA5, and when the medium becomes idle, it waits for DIFS and can start transmitting frames after the remaining backoff time elapses.

[0092] As in the example of Fig. 4, a data frame is a frame used for transmitting data forwarded to a higher layer, and can be transmitted after a backoff performed after DIFS elapses from when the medium becomes idle. Additionally, a management frame is a frame used for exchanging management information that is not forwarded to a higher layer, and is transmitted after a backoff performed after an IFS elapses, such as DIFS or PIFS (Point coordination function IFS). Subtype frames of a management frame include a beacon, an association request / response, a re-association request / response, a probe request / response, and an authentication request / response. A control frame is a frame used to control access to the medium. The subtype frames of the control frame include Request-To-Send (RTS), Clear-To-Send (CTS), Acknowledgment (ACK), Power Save-Poll (PS-Poll), Block ACK (BlockAck), Block ACK Request (BlockACKReq), Null Data Packet Announcement (NDP), and Trigger. If the control frame is not a response frame to the previous frame, it is transmitted after a backoff performed after the DIFS (Direct Inverse Frame Stop) has elapsed, and if it is a response frame to the previous frame, it is transmitted without a backoff performed after the SIFS (short IFS). The type and subtype of the frame can be identified by the type field and subtype field in the Frame Control (FC) field.

[0093] A QoS (Quality of Service) STA can transmit a frame after a backoff performed after the AIFS (arbitration IFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC), has elapsed. Here, the frames for which AIFS[i] can be used can be data frames, management frames, and also control frames that are not response frames.

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

[0095] As mentioned above, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, in which STAs directly sense the medium. Virtual carrier sensing is intended to address potential issues in medium access, such as the hidden node problem. For virtual carrier sensing, the MAC of an STA can utilize a Network Allocation Vector (NAV). The NAV is a value that an STA that is currently using or has the right to use the medium indicates to other STAs the remaining time until the medium becomes available. Therefore, the value set as NAV corresponds to the period during which the STA transmitting the frame is scheduled to use the medium, and an STA receiving the NAV value is prohibited from accessing the medium during that period. For example, the NAV can be set based on the value of the "duration" field in the MAC header of the frame.

[0096] In the example of FIG. 5, it is assumed that STA1 wants to transmit data to STA2, and STA3 is in a position to overhear some or all of the frames transmitted and received between STA1 and STA2.

[0097] In order to reduce the possibility of collisions in transmissions of multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism using RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA1 may correspond to a hidden node for STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, STA3 may determine that the medium is idle based on carrier sensing results. That is, STA2 may correspond to a hidden node for STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of either STA1 or STA2, or STAs outside the carrier sensing range for transmissions from STA1 or STA3, may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0098] Specifically, STA1 can determine whether a channel is occupied through carrier sensing. In terms of physical carrier sensing, STA1 can determine channel occupancy idleness based on the energy level or signal correlation detected in the channel. Furthermore, in terms of virtual carrier sensing, STA1 can determine the channel occupancy status using a network allocation vector (NAV) timer.

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

[0100] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can use the duration information contained in the RTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame). Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can use the duration information contained in the CTS frame to set a NAV timer for the subsequent consecutively transmitted frame transmission period (e.g., SIFS + data frame + SIFS + ACK frame). That is, if STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. If STA3 receives a new frame before the NAV timer expires, it can update the NAV timer using the duration information contained in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0101] If STA1 receives a CTS frame from STA2, it can transmit a data frame to STA2 after SIFS from the time when the CTS frame is completely received. If STA2 successfully receives the data frame, it can transmit an ACK frame in response to the data frame to STA1 after SIFS. STA3 can determine whether the channel is in use through carrier sensing if the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during the DIFS after the NAV timer expires, it can attempt channel access after a contention window (CW) based on a random backoff has elapsed.

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

[0103] The PHY layer can prepare an MPDU (MAC PDU) to be transmitted based on an instruction or primitive (meaning a set of instructions or parameters) from the MAC layer. For example, when a command requesting the start of transmission of the PHY layer is received from the MAC layer, the PHY layer can switch to transmission mode and transmit the information (e.g., data) provided by the MAC layer in the form of a frame. In addition, when the PHY layer detects a valid preamble of the received frame, it monitors the header of the preamble and sends a command to the MAC layer notifying the start of reception of the PHY layer.

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

[0105] A basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a SIGNAL (SIG) field, and a Data field. The most basic (e.g., non-HT (High Throughput) as illustrated in FIG. 7) PPDU format may consist of only the Legacy-STF (L-STF), Legacy-LTF (L-LTF), Legacy-SIG (L-SIG) fields, and a Data field. Additionally, depending on the type of PPDU format (e.g., HT-mixed format PPDU, HT-greenfield format PPDU, VHT (Very High Throughput) PPDU, etc.), additional (or different types of) RL-SIG, U-SIG, non-legacy SIG field, non-legacy STF, non-legacy LTF, (i.e., xx-SIG, xx-STF, xx-LTF (e.g., xx is HT, VHT, HE, EHT, etc.)) may be included between the L-SIG field and the data field. More specific details will be described later with reference to FIG. 7.

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

[0107] The SIG field may include various information related to PPDU transmission and reception. For example, the L-SIG field may consist of 24 bits and may include a 4-bit Rate field, a 1-bit Reserved bit, a 12-bit Length field, a 1-bit Parity field, and a 6-bit Tail field. The RATE field may include information about the modulation and coding rate of data. For example, the 12-bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, for a non-HT, HT, VHT, or EHT PPDU, the value of the Length field may be determined as a multiple of 3. For example, for HE PPDU, the value of the Length field can be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0108] The data field may include a SERVICE field, a Physical layer Service Data Unit (PSDU), a PPDU TAIL bit, and, if necessary, padding bits. Some bits of the SERVICE field may be used to synchronize the descrambler at the receiving end. The PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated / used by upper layers. The PPDU TAIL bit may be used to return the encoder to a 0 state. The padding bit may be used to adjust the length of the data field to a predetermined unit.

[0109] MAC PDUs are defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a Frame Check Sequence (FCS). A MAC frame is composed of MAC PDUs and can be transmitted / received through the PSDU in the data portion of the PPDU format.

[0110] The MAC header includes a Frame Control field, a Duration / ID field, an Address field, etc. The Frame Control field may include control information required for frame transmission / reception. The Duration / ID field may be set to a time for transmitting the corresponding frame, etc. The Address subfields may indicate the receiver address, transmitter address, destination address, and source address of the frame, and some Address subfields may be omitted. For specific details of each subfield of the MAC header, including the Sequence Control, QoS Control, and HT Control subfields, refer to the IEEE 802.11 standard document.

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

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

[0113] Standards such as IEEE 802.11a / g / n / ac / ax use various PPDU formats. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format can also be referred to as the non-HT PPDU format (Fig. 7(a)).

[0114] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT(s) fields in addition to the basic PPDU format. The HT PPDU format illustrated in Fig. 7(b) may be referred to as an HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format that does not include L-STF, L-LTF, and L-SIG, but consists of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTF, and Data fields (not illustrated).

[0115] An example of the VHT PPDU format (IEEE 802.11ac) includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields in addition to the basic PPDU format (Fig. 7(c)).

[0116] An example of a HE PPDU format (IEEE 802.11ax) additionally includes RL-SIG (Repeated L-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF(s), and PE (Packet Extension) fields in addition to the basic PPDU format (Fig. 7(d)). Depending on specific examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-users (MUs), but the HE PPDU format for single users (SUs) does not include the HE-SIG-B. In addition, the HE trigger-based (TB) PPDU format does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The HE ER (Extended Range) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us. For example, RL-SIG can be configured identically to L-SIG. The receiving STA can determine that the received PPDU is a HE PPDU or an EHT PPDU, described later, based on the presence of RL-SIG.

[0117] The EHT PPDU format may include the EHT MU (multi-user) PPDU of FIG. 7(e) and the EHT TB (trigger-based) PPDU of FIG. 7(f). The EHT PPDU format is similar to the HE PPDU format in that it includes an RL-SIG following an L-SIG, but may include a U (universal)-SIG, an EHT-SIG, an EHT-STF, and an EHT-LTF following the RL-SIG.

[0118] The EHT MU PPDU in FIG. 7(e) corresponds to a PPDU that carries one or more data (or PSDUs) for one or more users. That is, the EHT MU PPDU can be used for both SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0119] The EHT TB PPDU of Fig. 7(f) omits the EHT-SIG compared to the EHT MU PPDU. An STA that has received a trigger for UL MU transmission (e.g., a trigger frame or TRS (triggered response scheduling)) can perform UL transmission based on the EHT TB PPDU format.

[0120] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated to allow legacy STAs to attempt demodulation and decoding, and mapped based on a predetermined subcarrier frequency interval (e.g., 312.5 kHz). These can be referred to as pre-EHT modulated fields. Next, the EHT-STF, EHT-LTF, Data, and PE fields can be encoded and modulated to allow STAs that have successfully decoded non-legacy SIGs (e.g., U-SIG and / or EHT-SIG) and obtained the information contained in the fields, and mapped based on a predetermined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

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

[0122] The U-SIG included in the EHT PPDU format of FIG. 7 can be configured based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., OFDM symbol) for the U-SIG can have a duration of 4 us, and the U-SIG can have a total duration of 8 us. Each symbol of the U-SIG can be used to transmit 26 bits of information. For example, each symbol of the U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0123] U-SIGs can be configured in 20MHz units. For example, when an 80MHz PPDU is configured, the same U-SIG can be duplicated in 20MHz units. That is, four identical U-SIGs can be included in an 80MHz PPDU. When the bandwidth exceeds 80MHz, for example, for a 160MHz PPDU, the U-SIGs in the first 80MHz unit and the U-SIGs in the second 80MHz unit can be different.

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

[0125] The A bit information transmitted by U-SIG can be divided into version-independent bits and version-dependent bits. For example, U-SIG can be included in a new PPDU format (e.g., UHR PPDU format) not shown in FIG. 7, and in the format of the U-SIG field included in the EHT PPDU format and the format of the U-SIG field included in the UHR PPDU format, the version-independent bits can be the same, and some or all of the version-dependent bits can be different.

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

[0127] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier, which may indicate the PHY version (e.g., EHT, UHR, etc.) of the transmitted and received PPDUs. The version-independent bits of the U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field relates to UL communication, and the second value of the UL / DL flag field relates to DL communication. The version-independent bits of the U-SIG may include information about the length of a transmission opportunity (TXOP) and information about a BSS color ID.

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

[0129] Information required for PPDU transmission and reception may be included in the U-SIG. For example, the U-SIG may further include information about bandwidth, information about the MCS technique applied to the non-legacy SIG (e.g., EHT-SIG or UHR-SIG), information indicating whether a dual carrier modulation (DCM) technique (e.g., a technique to achieve an effect similar to frequency diversity by reusing the same signal on two subcarriers) is applied to the non-legacy SIG, information about the number of symbols used for the non-legacy SIG, information about whether the non-legacy SIG is generated across the entire band, etc.

[0130] Some of the information required for transmitting and receiving a PPDU may be included in the U-SIG and / or the non-legacy SIG (e.g., EHT-SIG or UHR-SIG, etc.). For example, information about the type of the non-legacy LTF / STF (e.g., EHT-LTF / EHT-STF or UHR-LTF / UHR-STF, etc.), information about the length of the non-legacy LTF and the cyclic prefix (CP) length, information about the guard interval (GI) applicable to the non-legacy LTF, information about preamble puncturing applicable to the PPDU, information about resource unit (RU) allocation, etc. may be included only in the U-SIG, may be included only in the non-legacy SIG, or may be indicated by a combination of the information included in the U-SIG and the information included in the non-legacy SIG.

[0131] Preamble puncturing may refer to the transmission of a PPDU in which no signal is present in one or more frequency units within the PPDU's bandwidth. For example, the size of the frequency unit (or the resolution of the preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth greater than a certain size.

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

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

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

[0135] The number of user-specific fields can be determined based on the number of users. A single user block field can contain up to two user fields. Each user field can be associated with either MU-MIMO allocation or non-MU-MIMO allocation.

[0136] The common field may include CRC bits and Tail bits, the length of the CRC bits may be determined as 4 bits, and the length of the Tail bits may be determined as 6 bits and set to 000000. The common field may include RU allocation information. The RU allocation information may include information about the location of RUs to which multiple users (i.e., multiple receiving STAs) are allocated.

[0137] An RU can contain multiple subcarriers (or tones). RUs can be used when transmitting signals to multiple STAs based on OFDMA techniques. RUs can also be defined when transmitting signals to a single STA. Resources can be allocated on an RU basis for non-legacy STFs, non-legacy LTFs, and data fields.

[0138] Depending on the PPDU bandwidth, an applicable RU size can be defined. The RU may be defined identically or differently for the applicable PPDU format (e.g., HE PPDU, EHT PPDU, UHR PPDU, etc.). For example, in the case of an 80MHz PPDU, the RU arrangements of HE PPDU and EHT PPDU may be different. The applicable RU size, RU number, RU position, DC (direct current) subcarrier position and number, null subcarrier position and number, guard subcarrier position and number, etc. for each PPDU bandwidth can be referred to as a tone plan. For example, a tone plan for a wide bandwidth can be defined in the form of multiple repetitions of a low bandwidth tone plan.

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

[0140] The specific size of an RU may be reduced or expanded. Therefore, the specific size of each RU (i.e., the number of corresponding tones) in the present disclosure is not limited and is exemplary. Furthermore, within a given bandwidth (e.g., 20, 40, 80, 160, 320 MHz, etc.) in the present disclosure, the number of RUs may vary depending on the RU size.

[0141] The names of each field in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by those names. Furthermore, the examples of the present disclosure can be applied not only to the PPDU format exemplified in FIG. 7, but also to a new PPDU format in which some fields are excluded and / or some fields are added based on the PPDU formats of FIG. 7.

[0142] FIG. 8 is a drawing showing an exemplary format of a trigger frame to which the present disclosure can be applied.

[0143] A trigger frame may allocate resources for the transmission of one or more TB PPDUs and request the transmission of TB PPDUs. The trigger frame may also include other information required by the STA transmitting the TB PPDU in response. The trigger frame may include common information and a user information list field in the frame body.

[0144] The common information field may include information that is common to one or more TB PPDU transmissions requested by a trigger frame, such as trigger type, UL length, presence of a subsequent trigger frame (e.g., More TF), whether CS (channel sensing) is required, UL BW (bandwidth), etc. Fig. 8 illustrates an example of an EHT variant common information field format.

[0145] The 4-bit trigger type subfield can have values ​​from 0 to 15. Among them, the values ​​0, 1, 2, 3, 4, 5, 6, and 7 of the trigger type subfield are defined to correspond to basic, Beamforming Report Poll (BFRP), multi user-block acknowledgement request (MU-BAR), multi user-request to send (MU-RTS), Buffer Status Report Poll (BSRP), groupcast with retries (GCR), MU-BAR, Bandwidth Query Report Poll (BQRP), and NDP Feedback Report Poll (NFRP), respectively, and the values ​​8 to 15 are defined as reserved.

[0146] Among the common information, the trigger dependent common info subfield may include information that is optionally included based on the trigger type.

[0147] A special user info field may be included within the trigger frame. The special user info field does not contain user-specific information, but rather extended common information not provided in the common information field.

[0148] A user information list contains zero or more user information fields. Figure 8 illustrates an example of an EHT variant user information field format.

[0149] The AID12 subfield basically indicates that it is a user information field for an STA with the corresponding AID. In addition, if the AID12 field has a predetermined specific value, it may be utilized for other purposes, such as allocating a random access (RA)-RU, or being configured in the form of a special user information field. The special user information field is a user information field that does not contain user-specific information, but contains extended common information not provided in the common information field. For example, the special user information field can be identified by the AID12 value of 2007, and the special user information field flag subfield within the common information field can indicate whether the special user information field is included.

[0150] The RU allocation subfield can indicate the size and location of an RU / MRU. For this purpose, the RU allocation subfield can be interpreted together with the PS160 (primary / secondary 160MHz) subfield of the user information field, the UL BW subfield of the common information field, etc.

[0151] Signaling procedures for IDC events and related information

[0152] Wi-Fi technology (e.g., wireless LAN system-based technology) can be used together with non-Wi-Fi technologies in similar frequency bands (e.g., 2.4 GHz, 5 to 6 GHz, etc.). Various devices (e.g., smartphones, smart watches, VR / AR devices, etc.) use / apply non-Wi-Fi technologies (e.g., Bluetooth (BT), Zigbee, UWB (Ultra-wideband), etc.) together with Wi-Fi technology, and the IDC that occurs when the above-mentioned technologies operate simultaneously has a significant impact on mutual wireless communication.

[0153] For example, when Wi-Fi and BT / UWB interfere with each other's signals, packet loss and rate degradation can occur, which can lead to performance degradation due to transmission throughput and delay. In other words, when data from a non-Wi-Fi technology is transmitted and received on a single device, it can affect Wi-Fi transmission and reception.

[0154] IDC events / situations can occur in smart devices (e.g., smartphones, smartwatches, VR / AR devices, etc.) that can use / apply both Wi-Fi and non-Wi-Fi technologies. Additionally, IDC events / situations can occur in devices that utilize non-simultaneous transmit and receive (NSTR) in multi-link devices (MLDs). Devices that generate IDC events can signal information related to the IDC event via trigger frames.

[0155] As illustrated in FIG. 9, IDC events may occur periodically, and a device in which an IDC situation occurs may transmit information about the periodic IDC event to another device, similar to a target wake time (TWT) procedure or through another request / response procedure.

[0156] TWT is a power saving technology that can improve the energy efficiency of non-AP STAs by defining a service period (SP) between APs and non-AP STAs and sharing information about the SP to reduce contention on the medium. An STA that performs requests / suggestions / demands during the TWT setup phase can be called a TWT requesting STA. Additionally, an AP that responds to the request with an Accept / Reject option can be called a TWT responding STA.

[0157] The setup phase may include a process of determining / defining a TWT request from an STA to an AP, the type of TWT operation to be performed, and the type of frames to be transmitted and received. TWT operations can be divided into individual TWT and broadcast TWT.

[0158] Wi-Fi devices that may encounter IDC situations (e.g., devices utilizing Wi-Fi technology) may generate periodic IDC TWT service periods (SPs) by utilizing TWT or transmitting IDC-related information.

[0159] For example, if it is detected that data exchange with another non-Wi-Fi device is periodically initiated, STA 1 may request IDC TWT SP generation by transmitting a request frame containing information related to IDC (e.g., IDC TWT request frame, channel usage request frame, etc.) to the AP.

[0160] Here, TWT SP refers to a specific time period during which an STA is awake to transmit and receive data. In other words, TWT SP refers to a service period during which a station is active and transmits and receives data only for a predetermined period of time, negotiated between the AP and the STA, and switches to sleep mode for power conservation at other times.

[0161] For example, information related to an IDC may include information such as IDC SP start time, interval, gap, bandwidth (or channel, resource unit, multiple resource unit, distributed resource unit, etc.), IDC indication (or / and status), number of available spatial streams (NSS), etc.

[0162] The AP may generate an IDC SP based on information related to the IDC included in a request frame received from STA 1. Then, the AP may transmit a response frame including the result of generating the IDC SP to STA 1. Additionally or alternatively, the AP may transmit the information related to the IDC received / obtained from STA 1 to another STA in a non-solicited manner via a response frame while generating the IDC TWT SP.

[0163] The above-described procedure may not be limited to operations between APs and non-AP STAs. That is, in the above-described procedure, operations of the AP may be performed by non-AP STAs, and operations of non-AP STAs may be performed by the AP. Furthermore, the above-described procedure may be configured for operations between APs or between non-AP STAs.

[0164] Here, a phenomenon such as clock drift may occur for devices reporting IDC-related information, which may change the timing of IDC event occurrence (or / and the periodicity of the IDC event). Another example is that during an IDC event, a new event (e.g., a retransmission) may occur during communication with a non-Wi-Fi device, resulting in a non-periodic IDC event. Consequently, an AP unaware of the changed time (e.g., the IDC period) may attempt to exchange data based on the existing IDC period.

[0165] For example, referring to FIG. 10, STA 1 can transmit information about IDC TWT SP to AP through IDC TWT request frame. Based on the information about IDC TWT SP information, AP can determine that STA 1 is unavailable during a certain period. That is, AP can schedule transmission and reception operations so as not to attempt data exchange with STA 1 during the certain period, or can attempt data exchange using another available method (e.g., switching to an available channel and / or subchannel, adjusting Tx / Rx parameters, etc.).

[0166] At this time, after STA 1 transmits information about the IDC TWT SP to the AP, the timing information of the IDC TWT SP may change depending on certain circumstances (e.g., clock drift, etc.). Additionally, if a retransmission procedure, etc. is performed as a non-Wi-Fi data exchange procedure during the IDC TWT SP, the timing or duration of the IDC TWT SP may change, and thus the unavailable period may change. If the AP attempts to exchange Wi-Fi data without being aware of this situation, data exchange failure may occur in the relevant period.

[0167] In the following, in order to solve the above-described problem, a method is described in which STA 1 transmits the above-described information (e.g., information about the changed timing of the IDC TWT SP or / and a new event, etc.) to the AP, etc. when the timing of the periodic IDC TWT SP changes or a new event occurs during the IDC TWT SP.

[0168] FIG. 11 is a diagram illustrating an example of a method performed by a first STA according to the present disclosure. In FIGS. 11 and 12 , each of the first STA and the second STA may be either a non-AP STA or an AP. In addition, the first STA may be either a TXOP holder or a TXOP responder, and the second STA may be either a TXOP responder or a TXOP holder. Referring to FIGS. 11 and 12 , signaling operations between the first STA and the second STA may be performed within a TXOP.

[0169] In describing the present disclosure, the unavailability operation may be replaced with an IDC event or an unavailability event, etc. In addition, the unavailability operation may include an operation in which an operating channel of the first STA or at least one subchannel of the operating channel becomes unavailable.

[0170] The first STA can transmit a first frame containing first information related to an unavailable operation to the second STA (S1110).

[0171] Here, the first information may include at least one of the time at which the unavailable operation starts, the period of the unavailable operation, the length of the period of the unavailable operation (e.g., a time interval), the channel or bandwidth on which the unavailable operation occurred, the number of spatial streams associated with the unavailable operation, or the antennas available during the period of the unavailable operation.

[0172] Here, the time at which the unavailable operation starts may include a partial timing synchronization function (TSF) time at which the unavailable operation is expected to start.

[0173] Additionally, the first frame may include a target wake time (TWT) setup frame, and the first information may be included in a TWT element of the TWT setup frame.

[0174] The first STA may receive a response frame (e.g., a TWT response frame) to the first frame from the second STA. Accordingly, data exchange between the first STA and the second STA may not be performed within a period associated with a periodically set unavailable operation (e.g., an IDC TWT SP).

[0175] Based on a change in the timing of the duration of the i-th unavailable operation among the durations of at least one unavailable operation related to the first information, the first STA may transmit a second frame to the second STA (S1120).

[0176] For example, if a period of at least one unavailable operation is set based on the first information, the timing (e.g., cycle or start time, etc.) of the period of the i-th unavailable operation may be changed depending on circumstances such as clock drift.

[0177] At this time, the first STA may transmit a second frame to the second STA, which includes second information related to whether the timing of the period of the i-th unavailable operation has changed (e.g., information on the period change of the period of the unavailable operation) and / or third information related to an identifier (e.g., an index, etc.) of the period of the i-th unavailable operation. Through this, the second STA may confirm that the timing of the period of the i-th unavailable operation has changed.

[0178] Here, the second frame may be one of various types of BA frames (e.g., compressed block acknowledgment (BA) frames, multi-STA BA frames, etc.), quality of service (QoS) null / data frames, frames containing aggregated control fields related to the unavailable operation, new control frames related to the unavailable operation, initial control response (ICR), or action frames related to the unavailable operation.

[0179] And, the third information may include an identifier of the period of the i-th unavailable operation and / or ID information included in the first frame (or first information) that sets the i-th unavailable operation.

[0180] And, the second frame may be a response frame to the third frame received by the first STA from the second STA. For example, if the third frame is an initial control frame (ICF), the second frame may be an ICR. For another example, if the third frame is a trigger frame (e.g., a BSRP trigger frame), the second frame may be a QoS null frame. For another example, if the third frame is a PPDU containing downlink data, the second frame may be a BA frame or a multi-STA BA frame.

[0181] As an example of the present disclosure, the duration of the i-th unavailable operation can be determined based on the second frame. That is, information related to the duration of the i-th unavailable operation can be (aperiodically) determined by the second frame.

[0182] For example, the second frame may include at least one of a start time and a length of a period of the i-th unavailable operation. That is, the i-th unavailable operation may be set based on the time and / or length of the period of the unavailable operation included in the second frame.

[0183] The first STA may transmit a fourth frame containing fourth information for updating the first information to the second STA after the i-th unavailable operation period. Specifically, the first STA may update information related to the periodic unavailable operation through a TWT setup frame after obtaining channel access rights. For example, the first STA may generate a fourth frame containing fourth information of the same type as the type of the first information. As another example, the first STA may generate a fourth frame containing information of a type to be updated (e.g., the fourth information) among the first information. The first STA may transmit the generated fourth frame to the second STA, thereby setting a period related to the periodic unavailable operation.

[0184] The method described in the example of FIG. 11 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 transmit a first frame including first information related to an unavailable operation to a second STA via one or more transceivers (106). Based on a change in the timing of the duration of the ith unavailable operation among the durations of at least one unavailable operation related to the first information, the one or more processors (102) may transmit a second frame to the second STA via one or more transceivers (106).

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

[0186] FIG. 12 is a diagram illustrating an example of a method performed by a second STA according to the present disclosure.

[0187] The second STA can receive a first frame containing first information related to an unavailable operation from the first STA (S1210).

[0188] The second STA may identify a period of unavailability associated with the first STA (e.g., IDC TWT SP) through the first information. The second STA may transmit a response frame to the first frame (e.g., a response frame including information acknowledging the first information) to the first STA. In addition, the second STA may not communicate with the first STA during the period of unavailability associated with the first information.

[0189] Based on a change in the timing of the period of the i-th unavailable operation among the periods of at least one unavailable operation related to the first information, the second STA can receive the second frame from the first STA (S1220).

[0190] Here, the second frame may include second information on whether the timing of the period of the i-th unavailable operation among the periods of at least one unavailable operation related to the first information has changed and third information related to an identifier of the period of the i-th unavailable operation.

[0191] The second STA may identify that the timing of the duration of the i-th unavailable operation has changed through the second frame. For example, the second STA may identify the timing of the duration of the i-th unavailable operation based on the start time and duration of the i-th unavailable operation included in the second frame. In addition, the second STA may not communicate with the first STA during the duration of the i-th unavailable operation.

[0192] The method described in the example of FIG. 12 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may receive a first frame including first information related to an unavailable operation from a first STA through one or more transceivers (206). Based on a change in the timing of the duration of the ith unavailable operation among the durations of at least one unavailable operation related to the first information, the one or more processors (202) may receive a second frame from the first STA through one or more transceivers (206).

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

[0194] Below, we will specifically describe how to update information related to IDC and / or periodic IDC-related information (e.g., timing, etc.).

[0195] Example 1

[0196] Embodiment 1 relates to information related to IDC (e.g., IDC information). As an example of the present disclosure, the information related to IDC may include at least one of IDC type, IDC start time (ST), IDC duration, IDC interval, IDC continuity, IDC channel / BW, IDC NSS / antenna, periodicity change, and ID (index or identifier).

[0197] IDC type

[0198] As an example of the present disclosure, the IDC type may indicate whether information about the IDC is information about a periodic IDC event or an aperiodic event. For example, if the field value associated with the IDC type is 0 (or 1), this may indicate that the information about the IDC is information about a periodic IDC event. As another example, if the field value associated with the IDC type is 1 (or 0), this may indicate that the information about the IDC is information about an aperiodic IDC event.

[0199] IDC start time (ST)

[0200] As an example of the present disclosure, the IDC ST may include information about when the IDC occurs (e.g., when “unavailability” occurs). Additionally, “unavailability” may mean that the entire channel on which the STA operates or some subchannels of the channel (e.g., X subchannels of 20 MHz) are unavailable. That is, “unavailability” may mean that the entire channel on which the STA operates is unavailable or some portion of the channel is unavailable.

[0201] Additionally or alternatively, the IDC ST may be used as the entire (e.g., 8 octets) or part of the timestamp (TSF) received from the AP or the AP itself (e.g., partial TSF). For example, when partial TSF is applied, similar to the basic broadcast TWT, starting from a specific bit value of the TSF up to X octets (e.g., 2 octets) may be used.

[0202] Additionally or alternatively, the IDC ST may be indicated based on a duration (e.g., us) value from the start or end of transmission of a frame containing / transmitting the current IDC ST information.

[0203] Additionally or alternatively, the IDC ST may be indicated using the interval field of the MAC header. For example, the interval value of the interval field of the frame may mean / indicate the interval up to the IDC ST (based on the time of transmission or reception of the frame).

[0204] Additionally or alternatively, if the IDC ST is indicated via the interval field of the above frame, separate indication / information for the IDC ST may be omitted.

[0205] IDC section

[0206] An IDC interval can refer to the time period during which an IDC (or IDC event) persists. For example, an IDC interval can be designated based on a specific unit of time (e.g., us). Information associated with an IDC interval can include information about a specific unit of time (e.g., a unit of time used to designate the duration of an IDC).

[0207] For example, information related to an IDC interval may include a specific unit of time (e.g., 1 us, 8 us, 32 us, 64 us, etc.) and / or a time interval value for which the IDC lasts based on the specific unit of time. For example, if the time interval value is indicated as 1000 and the unit of time value is indicated as 1 us, this may mean that the IDC interval is 1 ms. As another example, if the time interval value is indicated as 1000 and the unit of time value is indicated as 8 us, this may mean that the IDC interval is 8 ms.

[0208] For example, the IDC interval field (e.g., a field in which information related to the IDC interval is set) may consist of 2 octets, like the interval field of the MAC header, but is not limited thereto and may have a smaller size.

[0209] IDC interval

[0210] The IDC interval can refer to the interval between consecutive IDCs when the IDCs occur periodically. For example, the IDC interval can refer to the interval between the start times of consecutive IDCs.

[0211] For example, the IDC interval may be indicated based on a specific unit of time (e.g., microseconds). Information associated with the IDC interval may include information regarding the specific unit of time (e.g., a unit of time indicating the duration of the IDC).

[0212] For example, information related to the IDC interval may include a specific unit time (e.g., 1 us, 8 us, 32 us, 64 us, etc.) and / or an IDC interval value based on a specific unit time. For example, if 1000 is indicated as the interval value and 1 us is indicated as the unit time value, this may mean that the IDC interval is 1 ms. As another example, if 1000 is indicated as the interval value and 8 us is indicated as the unit time value, this may mean that the IDC interval is 8 ms.

[0213] For example, the IDC interval field (i.e., a field in which information related to the IDC interval is set) may consist of 2 octets, like the interval field of the MAC header, but is not limited thereto, and may have a smaller size.

[0214] IDC Continuity

[0215] IDC continuity may contain / indicate information about how long an IDC lasts. IDC continuity may indicate the number of each IDC (e.g., an integer).

[0216] Additionally or alternatively, the IDC continuity may indicate the total duration of the IDC ST or the point at which the continuous IDC ends. The total duration of the IDC ST and the point at which the continuous IDC ends may be indicated based on information related to the IDC interval and information related to the IDC ST.

[0217] Additionally or alternatively, the number of beacon frames, target beacon transmission time (TBTT), and / or beacon interval may be utilized.

[0218] For example, based on information about the number of beacon frames, TBTT, and / or beacon interval, it may be indicated how many times a beacon frame is transmitted within a period that lasts from the time the IDC first occurs. As another example, based on information about the number of beacon frames, TBTT, and / or beacon interval, it may be indicated how many beacon intervals an IDC lasts from the time the IDC first occurs.

[0219] For example, information about IDC continuity may be present when information about IDC spacing exists as IDC-related information. If information about IDC spacing does not exist as IDC-related information, information about IDC continuity may be omitted.

[0220] IDC Channel / BW

[0221] The IDC channel / BW may refer to the channel / BW where IDC occurs. For example, the IDC channel / BW may be indicated via a bitmap. For example, each bit in the bitmap related to the STA's operating channel and BW may indicate whether a 20 MHz subchannel is available (e.g., whether IDC has occurred).

[0222] Additionally or alternatively, since the BW per STA (e.g., the BW of the STA's operating channel or / and the BW where IDC may occur) may be different, information about the IDC channel / BW may include the BW information of each STA or may be indicated separately. For example, if the BW is indicated as 20, 40, 80, 160, or 320 MHz, etc., as many bitmaps as the number of 20 MHz subchannels corresponding to each BW may be configured.

[0223] Additionally or alternatively, the IDC BW information may indicate a limited BW that the STA can transmit and receive due to the IDC. In this case, information about the IDC channel may not exist as information related to the IDC.

[0224] Additionally or alternatively, the IDC BW information may include information about available or unavailable bandwidth due to IDC conditions. In this case, the IDC BW information may include the center frequency and bandwidth of the BW, and / or start and end information of the bandwidth.

[0225] Additionally or alternatively, IDC BW information may be indicated / set by a table value of the RU allocation subfield of the frame. When IDC BW information is indicated by the RU allocation subfield, the frequency band used by non-Wi-Fi wireless technologies in the IDC situation may be converted based on the RU allocation subfield according to Wi-Fi operation. As an example, the subfield indicating IDC BW information may be configured as shown in Table 1.

[0226] Bit: 0-1 Bit: 2-7 Octet: 1 or 2 Octet: 1 or 2 BW Type Reserved Start Frequency / Center Frequency / BW End Frequency / Frequency Bandwidth / RU Allocation

[0227] Here, field values ​​related to the BW type can be defined as in Table 2. All or only some of the types disclosed in Table 2 can be defined, and the values ​​corresponding to each type can be configured differently from Table 2.

[0228] Value Meaning 0 Frequency Range 1 Center Frequency 2 Resource Units 3 Reserved

[0229] For example, if the field value related to the BW type is set to 0, the second subfield within the (IDC) BW subfield may indicate the start frequency, and the third subfield may indicate the end frequency. For example, the second subfield may be set to 2,400(*106) as the start frequency. 2.4GHz) can be indicated, and the third subfield is the end frequency, 2483(*106 2.48GHz). For example, if the field value related to the BW type is set to 1, the second subfield within the (IDC) BW subfield can indicate the center frequency, and the third subfield can indicate the frequency bandwidth. For example, the second subfield can be set to 7,987(*106) as the start frequency. The first subfield can indicate 7.9 GHz), and the third subfield can indicate 500 (*106 == 500 MHz) as the end frequency.

[0230] For example, if the field value related to the BW type is set to 2, the second subfield within the (IDC) BW subfield may indicate BW. If the field / bit value indicating the BW indicates 0, 1, 2, 3, or 4 respectively, this may mean 20 MHz, 40 MHz, 80+80 MHz, 160 MHz, 320 MHz-1, or 320 MHz-2, and the remaining values ​​may be reserved. That is, the size of the field / bit indicating the BW may be 1 octet. The third subfield within the (IDC) BW subfield may indicate BW based on the RU allocation subfield value.

[0231] Additionally or alternatively, if an available or unavailable channel is indicated by the TWT channel subfield, the (IDC) BW subfield described above may be omitted.

[0232] IDC NSS / Antenna

[0233] IDC NSS / Antenna information may refer to the NSS / antenna that is available or unavailable when an IDC occurs.

[0234] The IDC NSS value can indicate the number of available spatial streams. The IDC NSS value can indicate the number of spatial streams that are available or unavailable due to IDC, so that the STA can use the actual available spatial streams.

[0235] Additionally or alternatively, the field related to the IDC NSS / antenna may indicate the index of an antenna (or the number of antennas or a numerical value associated with the antenna) that is available or unavailable in the IDC situation. For example, the antenna with the lowest index may be indicated based on the MSB or LSB of the field related to the IDC NSS / antenna.

[0236] Change the cycle

[0237] Information related to periodic changes may indicate whether the timing of periodic IDC information (or / and the periodic IDC event period, etc.) changes after information about the periodic IDC is transmitted and received. For example, if the field value related to periodic changes is 0 (or 1), this may indicate that the timing of the periodic IDC information has not changed. As another example, if the field value related to periodic changes is 1 (or 0), this may indicate that the timing of the periodic IDC information has changed.

[0238] ID

[0239] When there are multiple periodic IDC intervals (e.g., periodic IDC SPs), an ID may be assigned to each IDC interval. That is, the ID information may include an ID value for each periodic IDC interval. For example, the ID value for the first periodic IDC SP may be indicated by the ID information as 0, and the ID value for the second periodic IDC SP may be indicated by the ID information as 1.

[0240] At this time, the ID value may correspond to a specific application. For example, an ID value of 0 may correspond to a Bluetooth music application, and an ID value of 1 may correspond to a Bluetooth low energy advertisement application, but is not limited thereto.

[0241] In one embodiment of the present disclosure, the presence and / or configuration of information related to the IDC described with reference to Embodiment 1 may be determined according to the IDC scenario.

[0242] For example, if an IDC affects the primary channel of the BSS to which the STA belongs, the STA may not be able to use all channels due to the IDC, and thus information related to the IDC channel / BW may not exist or may be reserved.

[0243] As another example, if an IDC affects the entire spatial stream or operating channel of an STA, the STA may not be able to use all channels and / or spatial streams due to the IDC, and information related to the IDC channel / BW or / and spatial stream may not exist or may be reserved.

[0244] As another example, if IDCs occur episodically rather than periodically, information about IDC intervals and / or IDC continuity may not exist or may be reserved.

[0245] Below, we describe the composition and examples of IDC-related information for each IDC scenario.

[0246] Example 1-1

[0247] In one embodiment of the present disclosure, an existence field may be present for at least one piece of information related to the IDC described in Embodiment 1. For example, if the existence field value corresponding to a specific piece of information related to the IDC is set to 1, this indicates that a field related to the specific piece of information may be present.

[0248] Additionally or alternatively, the presence field, which indicates whether each piece of information related to the IDC exists, may be configured in the form of a bitmap (e.g., an presence bitmap). If the presence bitmap exists / is set, each bit of the presence bitmap may correspond to information related to each type of IDC. The remaining bits of the presence bitmap (e.g., bits other than each bit corresponding to information related to the IDC) may be reserved.

[0249] As an example, (a) of FIG. 13 illustrates an IDC information field (e.g., a field containing / configuring information related to IDC) utilizing an existence bitmap. As an example, each bit of the existence bitmap (e.g., B0, B1, and B2) may correspond to IDC ST information, IDC section information, and IDC channel, respectively. For example, if the first and second bits of the existence bitmap are each set to 1, this may mean that IDC ST information and IDC section information are included in the IDC information field.

[0250] Example 1-2

[0251] In one embodiment of the present disclosure, if an STA is unable to perform all transmission and reception operations during a given period due to an IDC, information indicating full unavailability may be transmitted and received via the IDC information field. If an STA is unable to perform transmission and reception operations on an operating channel due to an IDC, information indicating full unavailability may be indicated.

[0252] For example, if the information / subfield value indicating overall unavailability is set to 1 (e.g., if it is indicated that full transmit / receive operations cannot be performed during that time), information such as the IDC channel may not be included in the IDC information field.

[0253] For example, if the information / subfield value indicating overall unavailability is set to 0 (e.g., an IDC situation occurs but transmission and reception are indicated to be possible through other means), this may indicate partial unavailability. Here, the other means may include performing transmission and reception operations through other available channels, including subchannels. In this case, the IDC information field may include information such as the IDC channel.

[0254] Additionally or alternatively, a field may be defined and indicated as "fully unavailable", such as "partially unavailable." For example, if an IDC condition occurs but transmission and reception are indicated to be possible in another way (e.g., via another available channel, including a subchannel), the field value associated with "partially unavailable" may be set to 1. In this case, information related to the IDC channel may be included in the IDC information field. If the field value associated with "partially unavailable" is set to 0, this may indicate fully available, and the IDC information field may not include information related to the IDC channel.

[0255] Example 1-2-3

[0256] In one embodiment of the present disclosure, if an IDC occurring in an STA occurs continuously and periodically, a periodicity associated with the IDC may be indicated. For example, if the field value containing information related to the periodicity is set to 0, the IDC interval and IDC continuity may not be included in the IDC information field.

[0257] Figure 13(b) illustrates IDC information (or a field containing IDC information) that includes overall unavailability and a periodicity associated with the IDC. For example, if overall unavailability is not indicated, IDC channel information may be included in the IDC information field. Additionally, if the generated IDC does not have a periodicity, IDC interval and IDC continuity may not be included in the IDC information field.

[0258] Additionally or alternatively, complete unavailability may be indicated by a field associated with partial unavailability. The field associated with partial unavailability may be set to 1. In this case, the IDC information field may contain information related to the IDC channel. If the field associated with partial unavailability is set to 0, this may indicate complete availability, and the IDC information field may not contain information related to the IDC channel.

[0259] Additionally or alternatively, as illustrated in (c) of FIG. 13, the IDC information field may include a length field indicating the length of the IDC information field. When information related to a new type of IDC is added to the IDC information field, an STA that cannot decode the information related to the new type of IDC can use the length field to determine which field (e.g., the field containing information related to the new type of IDC) to ignore.

[0260] Additionally or alternatively, as illustrated in (c) of FIG. 13, the IDC information field may include an ID for the corresponding IDC information field (e.g., a subfield indicating the ID). The ID for the corresponding IDC information field may be used to convey control information. If the ID of the corresponding IDC information field is indicated through the subfield indicating the ID, the STA may recognize / decode the corresponding IDC information field. If the ID of information other than the IDC information field (e.g., another ID) is indicated, the STA may recognize that the corresponding field is a control field associated with an ID other than the IDC information.

[0261] Additionally or alternatively, as illustrated in (d) of FIG. 13, the IDC information field may be included in the generalized control information field. Control fields corresponding to one or more IDs may be included together / contiguously in the generalized control information field. For example, the IDC information field may be included in the generalized control information field together with other control information fields.

[0262] Additionally or alternatively, as illustrated in (d) of FIG. 13, a field related to the number of control information fields may be included in the generalized control information field. For example, if the number of control information fields is 2, the ID of the IDC information is 0, and the ID of the BSR information is 1, the generalized control information field may include an IDC information field and a BSR information field. Additionally or alternatively, the above-described field(s) may be configured in the form of an element including a length field.

[0263] As another example of the present disclosure, an IDC information field or a control information field including one or more IDC information and a method for configuring the same may be included in an A-control field of an HT control field of a MAC header. For example, an A-control field for IDC information may include a control ID (e.g., a control ID for IDC information) field, an IDC information field, another control information field, or / and a padding field. Additionally, the A-control field may be included in a QoS data frame, a QoS null frame, or a management frame.

[0264] Example 2

[0265] Embodiment 2 relates to a periodic IDC signaling method. To signal an IDC TWT element containing IDC information, at least one of the methods described below may be used.

[0266] As an example of the present disclosure, an IDC TWT element may be included in a TWT setup frame. As an example, the TWT setup frame action field may be defined as shown in Table 5. In this case, the IDC TWT element may be defined to be configured based on the TWT element. However, this is only one embodiment, and the IDC TWT element may be newly defined.

[0267] Order information 1 Category 2 Unprotected S1G action 3 Dialog token 4 One or more TWTs (e.g., TWT elements) 5 One or more IDC TWTs (e.g., IDC TWT elements)

[0268] For example, the sequence 5 of the TWT setup frame action field may correspond to an IDC TWT element, but is not limited thereto. When the TWT setup frame action field is defined as described above, the exchange of TWT elements for SP generation and the exchange of IDC TWT elements for generation of IDC TWT SP for unusable sections of IDC may be performed simultaneously. Additionally or alternatively, a modified TWT element may be included on the TWT setup frame. For example, the IDC TWT setup frame may be a frame for generating an IDC TWT SP and may be configured as shown in Table 4.

[0269] Order information 1 Category 2 Unprotected S1G action 3 Dialog token 4 One or more IDC TWTs (e.g., IDC TWT elements)

[0270] Additionally or alternatively, a channel usage request / response frame may be used. That is, an IDC TWT SP may be generated and utilized based on the channel usage request / response frame and TWT elements. Devices supporting IDC may generate and utilize IDC TWT SPs, etc. by exchanging channel usage request / response frames and TWT elements. Embodiment 2-1

[0271] In one embodiment of the present disclosure, the IDC TWT element including information about the IDC described in Embodiment 1 may use at least one of the methods described below to distinguish it from the TWT element of the basic wireless LAN system.

[0272] As an example of the present disclosure, when an individual TWT element is reused, the NDP Paging Indicator subfield / Disabled Mode subfield value of the Control Field Format may be set to 1, thereby implicitly indicating an IDC TWT element.

[0273] In a basic wireless LAN system, when an individual TWT is used, the NDP paging indicator / unavailable mode subfield value of the corresponding control field can be set to 0. At this time, if the IDC information subfield value of the NDP paging indicator / unavailable mode subfield of the corresponding control field is set to 1, it can be used as an IDC information indicator. That is, the IDC TWT element can be indicated by the IDC information subfield of the NDP paging indicator / unavailable mode subfield of the corresponding control field. The control field format can be reused as the control field of the basic wireless LAN system.

[0274] For example, the IDC TWT element may be configured as in Table 5, and the control field may be configured as in Table 6. In Table 6, the first bit (B0) of the control field may correspond to the NDP paging, unavailable mode, or / and IDC information indicator subfields described above.

[0275] Octet: 1 Octet: 1 Octet: 1 Octet: 1 Octet: Changeable Element ID Length Element ID Extension Control TWT Parameter Information

[0276] Bit: B0 Bit: B1 Bit: B2-B3 Bit: B4 Bit: B5 Bit: B6 Bit: B7 NDP Paging Responder PM Mode Negotiation Type TWT Information Frame Disabled Wake Period Unit Link ID Bitmap Existence Aligned TWT

[0277] Additionally or alternatively, the control field format for the IDC TWT element may be configured as shown in Table 7. That is, the control field format may be configured to suit the IDC individual TWT based on the individual TWT elements of the basic wireless LAN system. In Table 7, the first bit (B0) of the control field may correspond to the NDP paging, unavailable mode, or / and IDC information indicator subfields described above.

[0278] Bit: B0 Bit: B1 Bit: B2-B3 Bit: B4 Bit: B5 Bit: B6 Bit: B7 NDP Paging Reserved IDC Type Reserved Wake Period Unit Link ID Bitmap Existence Reserved

[0279] And, the IDC type subfield can be configured as in Table 8 for IDC TWT. For example, if the IDC type subfield value is 0, this may mean that an individual IDC is performed. If the IDC type subfield value is 1, this may mean that a broadcast IDC is performed.

[0280] Value Meaning 0 Individual IDC 1 Broadcast IDC 2 Reserved 3 Reserved

[0281] As an example of the present disclosure, at least one of the methods described below may be used to define the IDC TWT element described above. As an example, an individual TWT parameter set field including information about the IDC may be configured as shown in Table 9. That is, the NDP paging field within the individual TWT parameter set field format may be replaced with the IDC information field. As the NDP paging field within the individual TWT parameter set field format is replaced with the IDC information field, the size of the IDC information field may be adjusted.

[0282] Octet: 2 Octet: 0 or 8 Octet: 0, 3 or 9 Octet: 1 Octet: 2 Request Type TWTTWT Group Assignment Nominal Minimum TWT Wake Interval TWT Wake Interval Mantissa Octet: 1 Octet: 0 or changeable Octet: 0 or 2 Octet: 0 or 2 TWT Channel IDC Information Link ID Bitmap Aligned TWT Link Bitmap

[0283] As another example of the present disclosure, IDC information may be newly added within the individual TWT parameter set field format, as disclosed in Table 10. The size of the IDC information field may be defined / determined (e.g., defined as in Table 14) based on the type of IDC information described in Embodiment 1, but the size of the IDC information field may increase as IDC information is added.

[0284] Octet: 2 Octet: 0 or 8 Octet: 0, 3 or 9 Octet: 1 Octet: 2 Request Type TWTTWT Group Assignment Nominal Minimum TWT Wake Interval TWT Wake Interval Mantissa Octet: 1 Octet: 0 or 4 Octet: 0 or 2 Octet: 0 or 2 Octet: 0 or changeable TWT Channel NDP Paging (optional) Link ID Bitmap Aligned TWT Link Bitmap IDC Information

[0285] As an example of the present disclosure, as disclosed in Table 11, the request type field of the individual TWT parameter set field may indicate whether the IDC information is provided in full or partial form. In addition, the request type may be commonly redefined for defining the setup command of the individual IDC TWT.

[0286] Bit: B0 Bit: B1-B3 Bit: B4 Bit: B5 Bit: B6 Bit: B7-B9 Bit: B10-B14 Bit: B15 Overall unavailable IDC setup command Trigger Implicit Flow type TWT flow indicator TWT Wake interval Exponent TWT protection

[0287] Additionally or alternatively, fields not required for the IDC individual TWT within the request type field may be defined as reserved as shown in Table 12.

[0288] Bit: B0 Bit: B1-B3 Bit: B4 Bit: B5 Bit: B6 Bit: B7-B9 Bit: B10-B14 Bit: B15 Overall unavailable IDC setup command Reserved Reserved Reserved TWT Flow indicator TWT Wake Interval Exponent Reserved

[0289] For example, if the fully unavailability subfield value is 1, this may mean that the unavailability time interval or the entire IDC SP provided through the information about the IDC is fully unavailable. In the case of fully unavailability, other types of information about the IDC other than time domain information (e.g., IDC start time, interval, etc.) may be omitted. For example, if the fully unavailability subfield value is 0, this may mean that the unavailability time interval or the entire IDC SP is partially unavailable. For example, if the fully unavailability subfield value is 0, this may mean that transmission and reception are possible through other available channels including a specific subchannel.

[0290] For example, if the value of the unavailable subfield as a whole is 0 (or 1), this may mean that some of the unavailable time intervals or the entire IDC SPs are partially unavailable (e.g., transmission and reception are possible through other available channels including a specific subchannel). In addition, whether the interval is available for use can be confirmed and utilized through an initial control frame, etc. for each interval (e.g., some of the unavailable time intervals or the entire IDC SPs).

[0291] Additionally or alternatively, a field that is completely unavailable may be defined to mean the same thing as a field that is partially unavailable. For example, a field that is completely unavailable may have a value of 0, which may mean that the unavailable time interval provided in the information about the IDC and / or the entire IDC SP are completely unavailable. A field that is completely unavailable may have a value of 1, which may mean that some of the unavailable time intervals provided in the information about the IDC and / or the entire IDC SP are partially unavailable.

[0292] As an example of the present disclosure, the IDC setup command subfield may be configured as shown in Table 13.

[0293] Value Meaning 0 Request 1 Update 2 Suspend 3 Teardown

[0294] For example, if the IDC setup command subfield value is 0, this may mean a command requesting an IDC individual TWT. If the IDC setup command subfield value is 1, this may mean a command to update an existing IDC SP. If the IDC setup command subfield value is 2, this may mean a command to reserve an existing IDC SP. If the IDC setup command subfield value is 3, this may mean a command to terminate an existing IDC SP. If the TWT teardown frame is transmitted / used separately, the IDC setup command value may be omitted or reserved. Each IDC setup command may be assigned an ID of a TWT including IDC SPs through a TWT flow identifier. That is, the IDC setup command may be managed with the corresponding ID.

[0295] The IDC information fields included in Tables 11 and 12 can be defined as in Table 14. In Table 14, some of the subfields of the IDC information fields may be omitted or new information may be added.

[0296] Octet: 1 Octet: 1 Octet: 0, 2 or 8 Octet: 0 or 8 Octet: 0 or 3 Octet: 0 or 5 Octet: 0 or 1 Length Control Start Time Interval BW Available NSS

[0297] As an example of the present disclosure, the length subfield may be used to indicate the total length of the IDC information. This may be used to define that the size of the subfield of the IDC information is changeable or to ensure forward compatibility. As an example, the control subfield of the IDC information field may be configured as shown in Table 15. As an example, the control subfield may indicate the presence or absence of each control field within the parameter set field. However, this is only an example, and the configuration of the control subfield may be changed.

[0298] Bit: 0 Bit: 1 Bit: 2 Bit: 3 Bit: 4 Bit: 5-7 Start Time Existence Interval Existence BW Existence Available NSS Existence Reserved

[0299] Here, the start time subfield can indicate the interval from the current time to the start time of the IDC SP in microseconds. Additionally or alternatively, the start time subfield can indicate the start time using a partial TSF (Timing Synchronization Function). The interval subfield can indicate the time interval (time duration) of the IDC SP. The interval subfield can be expressed in microseconds. The size of the interval subfield can be determined (e.g., 2 octets, etc.) based on the application to which the IDC SP is applied.

[0300] The interval subfield can indicate the interval time between SPs when the IDC SP is repeated periodically. Here, the interval can be expressed in microseconds. The size of the interval subfield can be determined depending on the application to which the IDC SP is applied.

[0301] Time domain information (e.g., start time, interval, and so on) may be explicitly included in the IDC information field. For example, if the IDC SP is generated based on TWT parameters (e.g., TWT wake time, TWT wake interval, nominal minimum TWT wake interval, and so on), time domain information may be omitted.

[0302] The subfields described above may be included in the IDC information field or may be partially omitted. When time domain information is used among the information about the IDC, information such as the TWT wake time, TWT wake interval, nominal minimum TWT wake interval, and TWT wake interval Mantissa within the TWT element may be omitted or reserved.

[0303] The BW subfield can indicate available or unavailable bandwidth due to an IDC event / condition. For example, the BW subfield can indicate the center frequency and bandwidth. As another example, the BW subfield can indicate the start or end of the BW.

[0304] Additionally or alternatively, the BW subfield may be configured based on the table values ​​of the RU allocation subfield. The frequency band used in IDC situations involving non-Wi-Fi technologies may be converted based on the RU allocation according to the Wi-Fi operating bandwidth. The BW subfield may be configured as shown in Table 16.

[0305] Bit: 0-1 Bit: 2-7 Octet: 1 or 2 Octet: 1 or 2 BW Type Reserved Start Frequency / Center Frequency / BW End Frequency / Frequency Bandwidth / RU Allocation

[0306] As an example of the present disclosure, the BW type subfield may be configured as shown in Table 17. Table 17 is merely an example, and some information may be omitted or new information may be added to the BW type subfield.

[0307] Value Meaning 0 Frequency Range 1 Center Frequency 2 Resource Unit 3 Reserved

[0308] For example, if the field value related to the BW type is set to 0, the second subfield will be 2,400(*106) as the starting frequency. 2.4GHz) can be indicated, and the third subfield is the end frequency, 2483(*106 2.48GHz). For example, if the field value related to the BW type is set to 1, the second subfield within the (IDC) BW subfield can indicate the center frequency, and the third subfield can indicate the frequency bandwidth. For example, the second subfield can be set to 7,987(*106) as the start frequency. The first subfield can indicate 7.9 GHz), and the third subfield can indicate 500 (*106 == 500 MHz) as the end frequency.

[0309] For example, if the field value related to the BW type is set to 2, the second subfield within the (IDC) BW subfield may indicate BW. If the field / bit value indicating the BW indicates 0, 1, 2, 3, or 4 respectively, this may mean 20 MHz, 40 MHz, 80+80 MHz, 160 MHz, 320 MHz-1, or 320 MHz-2, and the remaining values ​​may be reserved. That is, the size of the field / bit indicating the BW may be 1 octet. The third subfield within the (IDC) BW subfield may indicate BW based on the RU allocation subfield value.

[0310] Additionally or alternatively, if an available or unavailable channel is indicated by the TWT channel subfield, the (IDC) BW subfield described above may be omitted.

[0311] As an example of the present disclosure, the available NSS subfield may indicate the number of available spatial streams. The IDC NSS value may indicate the number of spatial streams that are available or unavailable due to the IDC, thereby allowing the STA to use the actually available spatial streams.

[0312] Additionally or alternatively, the available NSS subfield may indicate the index of antennas (or the number of antennas or a numerical value associated with the antennas) that are available or unavailable in the IDC situation. For example, antennas with lower indices may be indicated based on the MSB or LSB of the available NSS subfield, starting with the antennas with higher indices.

[0313] Example 3

[0314] Embodiment 2 relates to a periodic IDC signaling method. To signal an IDC TWT element containing IDC information, at least one of the methods described below may be used.

[0315] As an example of the present disclosure, an IDC TWT element may be included in a TWT setup frame. As an example, the TWT setup frame action field may be defined as shown in Table 18. In this case, the IDC TWT element may be defined based on the TWT element. However, this is only one embodiment, and the IDC TWT element may be newly defined.

[0316] Order information 1 Category 2 Unprotected S1G action 3 Dialog token 4 One or more TWTs (e.g., TWT elements) 5 One or more IDC TWTs (e.g., IDC TWT elements)

[0317] For example, the sequence 5 of the TWT setup frame action field may correspond to an IDC TWT element, but is not limited thereto. When the TWT setup frame action field is defined as described above, the exchange of TWT elements for SP generation and the exchange of IDC TWT elements for IDC TWT SP generation for the unusable section of IDC may be performed simultaneously. Additionally or alternatively, a new frame including an action field may be used to define a new IDC TWT setup frame. The IDC TWT element may have a reusable field format of the TWT element, or the TWT element may be newly defined. For example, an unprotected S1G action field (e.g., an action field for an IDC TWT setup frame) may be defined as shown in Table 19.

[0318] Value Meaning 0 AID Switch Request 1 AID Switch Response 2 Synchronization Control 3 STA Information Announcement 4 EDCA Parameter Set 5 EL Operation 6 TWT Setup 7 TWT Decommissioning 8 Sectorized Group ID List 9 Sector ID Feedback 10 Reserved 11 TWT Information 12 IDC TWT Setup 13 IDC TWT Decommissioning 14-255 Reserved

[0319] As an example of the present disclosure, the IDC TWT setup frame may be a frame for generating an IDC TWT SP, and the IDC TWT setup frame action field may be defined as in Table 20.

[0320] Sequence information 1 Category 2 Unprotected S1G action 3 Dialog token 4 At least one IDC TWT

[0321] The IDC TWT setup teardown frame can be a frame for terminating the IDC TWT SP and can be defined as in Table 21.

[0322] Sequence information 1 Category 2 Unprotected S1G Action 3 IDC TWT Flow

[0323] For example, if the IDC type subfield value is 0, the IDC TWT flow field can be defined as in Table 22.

[0324] Bit: B0-B2 Bit: B3-B6 Bit: B7 IDC Flow Identifier Reserved Disassemble All IDC TWT

[0325] For example, if a TWT element contains an IDC type field (e.g., request, update, reservation, teardown, etc.) or a field related to IDC TWT persistence (e.g., an end time indication of an IDC SP) information, the IDC TWT teardown subfield may be replaced with or omitted.

[0326] Example 3-1

[0327] In one embodiment of the present disclosure, the IDC TWT element including information about the IDC described in Embodiment 1 may use at least one of the methods described below to distinguish it from the TWT element of the basic wireless LAN system.

[0328] Depending on how TWT elements for IDC are distinguished, TWT elements for IDC purposes may be redefined. For example, the IDC TWT element ID field may be defined as shown in Table 23. However, this is only an example, and the IDC TWT element ID may be defined with a different value.

[0329] ElementElement IDElement ID ExtensionExtensibleSplittable...IDC TWT255117YesNo...

[0330] As an example of the present disclosure, at least one of the methods described below may be used to define an IDC TWT element. For example, an IDC TWT element may be redefined as a new element. An ID for the IDC TWT element may need to be assigned. A newly defined order (e.g., order 5) may be defined in the TWT setup frame. Additionally or alternatively, an IDC TWT element may be included in the new IDC TWT setup frame as shown in Table 19.

[0331] For example, the IDC TWT element format can be configured as shown in Table 24. And, the control field of the IDC TWT element can be configured as shown in Table 25.

[0332] Octet: 1 Octet: 1 Octet: 1 Octet: 1 Octet: Changeable Element ID Length Element ID Extension Control TWT Parameter Information

[0333] Bit: B0 Bit: B1 Bit: B2 Bit: B3 Bit: B4 Bit: B5 Bit: B6-B7 Start time Existence section Existence interval Existence IDC continuity Existence BW Existence Available NSS Existence Reserved

[0334] Here, the start time presence subfield may indicate whether a start time field exists on the IDC individual TWT parameter set field. The interval presence subfield may indicate whether an interval field exists on the IDC individual TWT parameter set field. The interval presence subfield may indicate whether an interval field exists on the IDC individual TWT parameter set field. The IDC TWT persistence (or continuity) presence subfield may indicate whether a TWT persistence (or continuity) field exists on the IDC individual TWT parameter set field. The BW presence subfield may indicate whether a BW field exists on the IDC individual TWT parameter set field. The available NSS presence subfield may indicate whether a maximum NSS field exists on the IDC individual TWT parameter set field. As an example of the present disclosure, the IDC individual TWT parameter set field may be configured as in Table 26, but is not limited thereto.

[0335] Octet: 2 Octet: 0, 2, 8 Octet: 0 or 8 Octet: 0 or 3 Octet: 0 or 1 Octet: 0 or 4 Octet: 0 or 1 Request Type Start Time Interval Interval IDC Continuity BW Available NSS

[0336] Additionally or alternatively, the IDC individual TWT parameter set may be defined as in Table 27, and the IDC information field may be defined as described above. In addition, the request type field of the IDC individual TWT parameter set field may be configured as in Table 28.

[0337] Octet: 2 Octet: 0 or variable Request type IDC information

[0338] Bits: B0-B1 Bits: B2 Bits: B3-B5 Bits: B6-B7 Bits: B7 IDC Type Not available overall IDC Setup Command IDC Flow Identifier Reserved

[0339] As an example of the present disclosure, the IDC type field may be configured as shown in Table 29.

[0340] Value Meaning 0 Individual IDC 1 Broadcast IDC 2 Reserved 3 Reserved

[0341] For example, if the value of the Fully Unavailable subfield is 1, this may mean that the unavailable time interval or the entire IDC SP provided through the information about the IDC is fully unavailable. In the case of full unavailable, other types of information about the IDC other than time domain information (e.g., IDC start time, interval, etc.) may be omitted. For example, if the value of the Fully Unavailable subfield is 0, this may mean that the unavailable time interval or the entire IDC SP is partially unavailable. For example, if the value of the Fully Unavailable subfield is 0, this may mean that transmission and reception are possible through other available channels including a specific subchannel.

[0342] For example, if the value of the unavailable subfield as a whole is 0 (or 1), this may mean that some of the unavailable time intervals or the entire IDC SPs are partially unavailable (e.g., transmission and reception are possible through other available channels including a specific subchannel). In addition, whether the interval is available for use can be confirmed and utilized through an initial control frame, etc. for each interval (e.g., some of the unavailable time intervals or the entire IDC SPs).

[0343] Additionally or alternatively, a field that is completely unavailable may be defined to mean the same thing as a field that is partially unavailable. For example, a field that is completely unavailable may have a value of 0, which may mean that the unavailable time interval provided in the information about the IDC and / or the entire IDC SP are completely unavailable. A field that is completely unavailable may have a value of 1, which may mean that some of the unavailable time intervals provided in the information about the IDC and / or the entire IDC SP are partially unavailable.

[0344] As an example of the present disclosure, the IDC setup command subfield may be configured as shown in Table 30.

[0345] Value Meaning 0 Request 1 Update 2 Suspend 3 Teardown

[0346] For example, if the IDC setup command subfield value is 0, this may mean a command requesting an IDC individual TWT. If the IDC setup command subfield value is 1, this may mean a command to update an existing IDC SP. If the IDC setup command subfield value is 2, this may mean a command to reserve an existing IDC SP. If the IDC setup command subfield value is 3, this may mean a command to terminate an existing IDC SP. If the TWT teardown frame is transmitted / used separately, the IDC setup command value may be omitted or reserved. Each IDC setup command may be assigned an ID of a TWT including IDC SPs through a TWT flow identifier. That is, the IDC setup command may be managed with the corresponding ID.

[0347] Example 4

[0348] Example 4 relates to an aperiodic IDC signaling method utilizing A-control.

[0349] FIG. 15 relates to a method for transmitting information about an IDC using A-control according to one embodiment of the present disclosure. That is, FIG. 15 relates to a procedure for transmitting IDC information through the A-control field of a QoS data frame in response to a trigger frame.

[0350] For example, STAs 1, 2, and 3 may transmit a CTS to the AP in response to an MU-RTS trigger frame (TF). The AP may allocate resource units (RUs) to STAs 1, 2, and 3 through the underlying TF.

[0351] STA 1 and STA 3, knowing that an IDC will occur, can transmit the A-Control field of the QoS data frame to the AP after receiving the basic TF. At this time, the A-Control field may include an IDC information field or a control field containing IDC information. For example, since STA 1's IDC overlaps with the BA transmission, the AP may not transmit ACK information that it should respond to STA 1. Additionally or alternatively, STA 1 may set an ACK policy that does not require an immediate ACK, such as a BA, when transmitting a QoS data frame.

[0352] FIG. 16 illustrates a method for transmitting information about an IDC using A-control according to one embodiment of the present disclosure. Specifically, FIG. 16 illustrates a method for transmitting and receiving a QoS null frame as a response to a BSRP TF, wherein the QoS null frame may include IDC information, etc.

[0353] STA 1, 2, and 3 may transmit CTS in response to the MU-RTS TF transmitted by the AP. After that, the AP may allocate RUs to STA 1, 2, and 3 through the basic TF. After receiving the BSRP TF, STA 2 and STA 3, which know that an IDC will occur, may transmit a QoS null frame to the AP. At this time, the A-Control field of the QoS null frame may include an IDC information field or a control field containing IDC information. After that, the AP may not transmit frames to STA 2 / 3, as it knows that an IDC related to STA 2 and STA 3 will occur.

[0354] Meanwhile, when transmitting a response to a BSRP TF, the STA may transmit a BSR containing a QoS null frame in addition to a QoS null frame containing information about the IDC.

[0355] FIG. 17 illustrates a method for transmitting information about an IDC using A-control according to one embodiment of the present disclosure. Specifically, FIG. 17 illustrates that after an STA acquires a TXOP, it can transmit information about an IDC using an A-control field through a QoS data frame (or a QoS null frame).

[0356] An STA can transmit a QoS data frame (or QoS null frame) to the AP to notify that an IDC has occurred. The QoS data frame includes an A-Control field, which can include an IDC information field or a control information field containing IDC information. Through this, the AP can avoid transmitting frames to the STA during the STA's IDC section when it acquires a TXOP in the future.

[0357] Example 4-1

[0358] Example 4-1 relates to a method for transmitting information about an IDC using A-control based on a multi-link.

[0359] For example, when an IDC occurs on a specific link, an STA may not be able to transmit information related to the IDC if it fails to obtain a TXOP. Therefore, when multi-links are applied, when a TXOP is obtained on another link, the STA may transmit information about the link on which the IDC occurred through the other link. For example, the A-control field for IDC information transmitted by the STA may include at least one of a control ID (e.g., a control ID for the IDC information), link information (e.g., a link bitmap or link ID), other control information, and padding.

[0360] Link ID information can indicate a link ID (e.g., the ID of the link where the IDC occurred). The link ID can be acquired through discovery (e.g., beacon reception) or the association process. Additionally, information regarding the number of link IDs can be included in the A-Control field to indicate that one or more link IDs are included in the A-Control field. IDC information for the corresponding link can be included after each link ID.

[0361] The link ID bitmap may refer to a bitmap indicating a link on which an IDC occurs. For example, the link corresponding to the i-th bit position in the bitmap may have link ID i. Additionally, if each bit value of the link ID bitmap is set to 1, this may indicate that an IDC occurs on the link corresponding to each bit. Additionally or alternatively, the size of the link ID bitmap may be 2 octets or more. Additionally or alternatively, the size of the link ID bitmap (e.g., 1 or 2 octets, etc.) may be changed, and the bitmap size may be indicated separately.

[0362] FIG. 18 is a diagram illustrating a method for transmitting IDC information using an A-control field according to one embodiment of the present disclosure. Specifically, FIG. 18 relates to a method for transmitting IDC information via the A-control field of a QoS data frame (or QoS null frame) for multi-link after STA 1 of a non-AP MLD acquires a TXOP.

[0363] STA 1 may be notified that an IDC has occurred with STA 2 operating on link 2 belonging to the same non-AP MLD. STA 1 may transmit the fact that an IDC has occurred with STA 2 to the AP MLD (e.g., AP 1) via a QoS data frame (or QoS null frame). At this time, the QoS data frame may include IDC information or a control information field that may include IDC information. Accordingly, when AP 2 obtains a TXOP later, it may not transmit a frame to the STA during the IDC section of STA 2.

[0364] Example 5

[0365] Example 5 relates to an aperiodic IDC signaling method using a trigger response frame. Information about one or more IDCs may be requested via the trigger frame. Furthermore, it may be indicated that IDC information or a control information field containing IDC information is requested (by the trigger frame). The following describes how information about IDCs requested in one or more trigger frames is transmitted and received via a response frame.

[0366] Example 5-1

[0367] Example 5-1 relates to a new in-device coexistence report (IDCR) A (aggregated) control field that responds to a trigger frame. That is, Example 5-1 relates to the configuration of an A-control field that includes information related to IDC.

[0368] For the definition of new control fields (e.g., IDC and A-control fields), the control ID can be defined as in Table 31.

[0369] Control ID Value Meaning 0 Triggered response scheduling (TRS) 1 Operating mode (OM) 2 HE link adaptation (HLA) / EHT link adaptation (ELA) 3 Buffer status report (BSR) 4 UL power headroom (UPH) 5 Bandwidth query report (BQR) 6 Command and status (CAS) 7 EHT operating mode (EHT OM) 8 Single response scheduling (SRS) 9 AP assisted request (AAR) 10 In-device-coexistence report (IDCR) 11-14 Reserved 15 ONES (Ones need expansion surely)

[0370] FIG. 14(d) illustrates a control information subfield of an IDCR control subfield (e.g., an A-control subfield in which a control ID value corresponds to an IDCR). For example, the control information subfield may include a subfield related to an IDC ST, a subfield related to an IDC interval, a subfield related to an IDC channel, and / or a subfield related to a maximum Rx NSS related to an IDC. However, this is only an embodiment, and the control information subfield may omit some of the above-described subfields or may have new subfields added. The IDCR may be signaled by being included in QoS data, a QoS null frame, etc. FIG. 19 is a diagram for explaining a method of transmitting IDC information via an A-control field according to an embodiment of the present disclosure. That is, FIG. 19 relates to a method of transmitting and receiving a response frame (e.g., a response frame using an A-control field) for a trigger frame including a field requesting IDC information.

[0371] Specifically, the AP can request IDC information from at least one STA via a trigger frame (e.g., a BSRP trigger frame, etc.). At least one STA can transmit a response frame (e.g., a QoS null frame) containing IDC information to the AP. For example, after receiving the trigger frame, STA 2, which knows that an IDC event / action will occur, can transmit a QoS null frame to the AP. At this time, the A-Control field of the QoS null frame can include IDC information or a control information field that can include IDC information.

[0372] Accordingly, the AP can confirm that STA 2 will have an IDC event / action and may not transmit frames to STA 2 during the period in which the IDC event / action occurs. In Fig. 19, it is assumed that the AP transmits a trigger frame, but as described above, the AP may be replaced by a non-AP STA.

[0373] Example 5-2

[0374] Example 5-2 relates to a new multiple IDCR A-control subfields that respond to a trigger frame. If IDC information is included in a single A-control field, the header size may be exceeded. Therefore, a control ID may be defined for each type of IDC information, and IDC-related information may be configured based on the A-control field(s) to which each control ID is set / mapped. For example, a control ID associated with an A-control field may be configured as shown in Table 32.

[0375] Control ID Value Meaning 0 Triggered response scheduling (TRS) 1 Operating mode (OM) 2 HE link adaptation (HLA) / EHT link adaptation (ELA) 3 Buffer status report (BSR) 4 UL power headroom (UPH) 5 Bandwidth query report (BQR) 6 Command and status (CAS) 7 EHT operating mode (EHT OM) 8 Single response scheduling (SRS) 9 AP assistance request (AAR) 10 In-device-coexistence start time (IDCS) 11 In-device-coexistence duration (IDCD) 12 In-device-coexistence channel and NSS (IDCCN) 11-14 Reserved 15 ONES (Ones need expansion surely)

[0376] FIG. 20 is a diagram illustrating control information subfields on IDCS, IDCD, and IDCCN subfields according to one embodiment of the present disclosure. An A-control field corresponding to an IDCS includes information about an IDC start time, an A-control field corresponding to an IDCD includes information about an IDC interval, and an A-control field corresponding to an IDCCN may include a channel and / or a maximum Rx NSS associated with the IDC. The A-control fields corresponding to each of the IDCS, IDCD, and IDCCN may be signaled via QoS data or / and a QoS null frame. In addition, reserved bits on each of the A-control fields illustrated in FIG. 16 may be omitted. In this case, the sizes of the A-control fields corresponding to each of the IDCS, IDCD, and IDCCN may be configured as 16 bits, 16 bits, and 20 bits, respectively.

[0377] Additionally or alternatively, the subfields related to the IDC channel and the subfields related to the maximum Rx NSS included in the A-control field corresponding to the IDCCN may be separated into separate A-control fields. The A-control fields related to the IDC channel and the maximum Rx NSS may be assigned / applied different control IDs. In addition, the A-control field may be configured based on a combination of one or more pieces of IDC control information, within a range not exceeding the maximum size of the A-control field.

[0378] Additionally or alternatively, a control ID for the IDC (e.g., a control ID corresponding to the IDCR in Table 32) may be defined, and one or more subtypes may be defined within the A-Control field. Each of the one or more subtypes may correspond to IDC-related information. The control ID value (or the value corresponding to the subtype) may be configured as shown in Table 33.

[0379] Control ID Value Meaning 0 Start Time 1 Interval 2 Channel 3 Max Rx NSS 4 Channel + Max Rx NSS 5 - 7 Reserved

[0380] For example, as disclosed in Table 6, eight subtypes can be defined with three bits, but is not limited thereto. Depending on the number of subtypes, it can be composed of two or four bits, etc. Each control information subfield can include the IDC information described above, but is not limited thereto, and some IDC information may be omitted or new IDC information may be added.

[0381] Example 5-3

[0382] Example 5-3 relates to the configuration of an A-MPDU response including one or more types of IDC information. That is, a response frame based on an A-MPDU can be transmitted and received in order to simultaneously transmit one or more types of IDC information described above.

[0383] FIG. 21 is a diagram illustrating a control information subfield on an IDCR subfield according to one embodiment of the present disclosure. As illustrated in FIG. 21, an AP may request information related to IDC from at least one STA via a trigger frame (e.g., a BSRP trigger frame). At least one STA may transmit information related to IDC to the AP via a response frame (e.g., a QoS null frame). In this case, the response frame may include an A-control frame corresponding to the IDCR.

[0384] For example, after receiving a trigger frame, STA 2, which knows that an IDC event / action will occur, can transmit IDC-related information or a control frame that may include IDC-related information to the AP through the A-Control frame of the QoS null frame. When transmitting IDC-related information, each subtype of IDCR can be included in an A-MPDU subframe. That is, IDC-related information can be included in the A-Control field of the same frame as the QoS null frame.

[0385] For example, as illustrated in FIG. 21, MPDU#1 including an A-control frame with an IDCR subtype value set to 0 (e.g., an A-control frame of a QoS null frame) may include IDC start time information. MPDU#2 including an A-control frame with an IDCR subtype value set to 1 may include IDC interval information. In addition, MPDU#N (N is a natural number greater than or equal to 1) transmitted by STA 2 may be configured as an A-MPDU.

[0386] Accordingly, the AP can confirm that STA 2 will have an IDC event / action and may not transmit frames to STA 2 during the period in which the IDC event / action occurs. In Fig. 21, it is assumed that the AP transmits a trigger frame, but as described above, the AP may be replaced by a non-AP STA.

[0387] Example 6

[0388] Example 6 relates to an aperiodic IDC signaling method utilizing a new frame. At least one of the following detailed embodiments may be utilized.

[0389] Example 6-1

[0390] Example 6-1 relates to a new response frame (or control frame) for a trigger frame. A control frame may be separately defined for a new response frame for a trigger frame that indicates an IDC information request and / or a general response. Additionally or alternatively, a new response frame may be defined that does not include an IDC information request and / or a general response.

[0391] For example, subtype values ​​0000 to 0001 and 1111 may be reserved within the frame control field of the MAC header. Therefore, if the subtype value is set to one of 0000 to 0001 and 1111, this may indicate that the frame is an IDC frame. An IDC frame may include, but is not limited to, a frame control field, a duration field, an RA field, a TA field, an IDC control field, an IDC information field, and an FCS.

[0392] Here, the IDC control field may be configured as a bitmap indicating the presence or absence of each subfield related to IDC information. The IDC information field may include subfields related to, but not limited to, IDC start time, interval, channel, gap, continuity, and / or maximum Rx NSS.

[0393] Additionally or alternatively, the new control frame may be a frame that responds to the IDC information request and / or response frame included in the trigger frame. Accordingly, the new control frame may include a response according to the trigger type. For example, the new control frame may include a frame control field, an interval field, an RA field, a TA field, an IDC control field, an IDC information field, an A-control field, and an FCS.

[0394] As an example of the present disclosure, the A-Control field may be based on the A-Control field of a basic wireless LAN system. The first two bits of the A-Control field are used for existing variant indication purposes and may be reserved. As an example, the A-Control subfield included in the IDC frame may be configured as shown in Table 34.

[0395] B0 - B1 B2 - B5 Variable Reserved Control ID Control Information

[0396] B0 - B1B2 - B5B6 - B9B10 - B11B12 - B13B14 - B15B16 - B23B24 - B31ReservedControl ID=0b11ACI BitmapDelta TIDACI HighScalingElementQueueSize HighQueueSize All

[0397] As described above, when A-control information is configured, the IDC control field may include information on the existence of the A-control field. The A-control field may be determined according to the type of the trigger frame. For example, when a BSRP trigger frame includes an IDC information request and / or a general response, the A-control field of the IDC frame may be configured as BSR. As another example, when an MU-RTS trigger frame includes an IDC information request and / or a general response, the STA may respond using a new control frame rather than a CTS. In this case, the IDC information is included in the control frame, but the A-control field may be omitted.

[0398] Additionally or alternatively, the new control frame may include response information according to the IDC information request and / or general response included in the trigger frame and / or one or more A-control fields. Accordingly, the control frame may include an A-control presence subfield. For example, the new control frame may include, but is not limited to, a frame control field, an interval field, an RA field, a TA field, an IDC control field, an IDC information field, an A-control presence field, an A-control list, and an FCS.

[0399] Each bit of the A-control presence field can be matched with each control ID based on MSB or LSB. When each bit value of the A-control presence field is set to 1, this may mean that the A-control field corresponding to each bit is present in the control frame. When multiple bit values ​​are set to 1, this may mean that multiple A-control fields are included in the A-control list. For example, when the bit values ​​mapped to each of BSR and OM are set to 1, the A-control list may include BSR and OM simultaneously. Each bit of the A-control presence subfield can be mapped to an A-control ID. The control ID values ​​may be defined in various ways, such as sequential, reversed, or random.

[0400] Example 6-2

[0401] Example 6-2 relates to a new response frame (e.g., an action frame) to a trigger frame.

[0402] A response frame may be defined for a trigger frame that includes an IDC information request and / or a general response instruction as an action frame. Additionally or alternatively, a new response frame may be defined even if it does not include an IDC information request and / or a general response instruction.

[0403] For example, an action frame may include a category field and an action detail field, and the category value may be set to one of the values ​​33 or 38 to 125. In the following, it is assumed that the category value is set to 38, but this is not limiting. Depending on the category value, the IDC action field value may be defined as shown in Table 36.

[0404] Value Meaning 0 IDC Response 1 IDC + A - Control Information Response 2 A - Control Information Response 3 - 255 Reserved

[0405] For example, if the IDC action field value is 0, it may mean that the body of the action frame contains an IDC response, and the IDC action field may be defined as in Table 37.

[0406] Sequence Meaning 1 Category 2 One or more IDC information

[0407] For example, if the IDC action field value is 1, it may mean that the body of the action frame includes an IDC response and A-control field, and the IDC action field may be defined as in Table 38.

[0408] Sequence Meaning 1 Category 2 One or more IDC information 3 One or more A-control information

[0409] For example, if the IDC action field value is 2, it may mean that the body of the action frame includes an A-control field, and the IDC action field may be defined as in Table 39.

[0410] Sequence Meaning 1 Category 2 One or more A-control information

[0411] As an example of the present disclosure, the element ID for defining IDC information and A-control elements can be defined as in Table 40.

[0412] Element Element ID Element ID Extension Extension Splittable...IDC Information 255117YesNoA-Control Information 255118YesNo...

[0413] IDC information elements can be defined as in Table 41, and IDC information of IDC information elements can be defined as in Table 42.

[0414] Octet: 1 octet: 1 octet: 1 octet: Variable element ID length Element ID extension IDC information

[0415] Octet: 1 Octet: 1 Octet: Variable Length Control IDC Info

[0416] The IDC information subfield may contain information about one or more of the types of IDCs described above. Furthermore, the control subfield may indicate the presence or absence of subfields containing information about one or more types of IDCs. The length field value may vary depending on the number and type of IDC information. The A-control information element may be structured as shown in Table 43.

[0417] Octet: 1 octet: 1 octet: 1 octet: Variable element ID length Element ID extension A-control information

[0418] The A-control information subfield may include an A-control field, and the A-control information subfield may be configured as shown in Table 34. In addition, the A-control information field related to BSR may be configured as shown in Table 35. Additionally or alternatively, the IDC information field may include one or more control information fields, and the A-control information element ID may be configured as shown in Table 44.

[0419] Element Element ID Element ID Extension Extension Splittable... A-Control Information 255117 Yes No...

[0420] The configuration of the A-control information field and the IDC information related to the control ID of the A-control information has been described above, so a redundant description will be omitted. FIG. 22 is a diagram illustrating a BSRP trigger frame with a general response according to an embodiment of the present disclosure. When a general response is indicated through a reserved bit in the common information field of the trigger frame, IDC information and / or BSRP can be simultaneously transmitted and received through a new control response based on BSRP.

[0421] An AP may transmit a BSRP trigger frame to at least one STA. At this time, a generic response indication field may be set / defined through at least one of the reserved bits described above in the common information field of the BSRP trigger frame (e.g., the EHT reserved bit of the EHT variant). At this time, the value of the generic response indication field may be set to 1. STA 1 and STA 3 (e.g., STAs that do not support IDC-related procedures) may ignore the value of the generic response indication field. STA 2 (e.g., STAs that support IDC-related procedures) may transmit an IDC frame as a response frame after interpreting the generic response indication field.

[0422] That is, STA 2 may transmit an IDC frame instead of a BSR response frame via the A-Control field of the QoS null frame. Additionally or alternatively, the IDC frame transmitted by STA 2 may include IDC information and / or BSR. An AP receiving the IDC frame may confirm that an IDC event related to STA 2 has occurred. In addition, the IDC frame may not transmit data to STA 2 during the IDC period.

[0423] Additionally or alternatively, an STA where an IDC event occurs may transmit a control frame / action frame to the opposing STA unsolicited.

[0424] FIG. 23 is a diagram illustrating a method for transmitting IDC information via an unsolicited control frame and / or action frame according to one embodiment of the present disclosure.

[0425] The occurrence of an IDC event can be detected when an STA acquires transmission authority. At this time, the STA can transmit IDC information to the AP via a control frame or action frame. Accordingly, the AP can identify the IDC event period associated with the STA and, after that period, perform data transmission through an RTS / CTS exchange with the STA.

[0426] Example 6-3

[0427] Example 6-3 relates to a new response frame to a trigger frame (e.g., an action frame including an A-control field on an HT control field).

[0428] A-control information may be included in the HT control field of an action frame, and IDC information may be included in the body of the action frame. The action frame may include a category field and an action detail field. If the category field value is set to one of the values ​​33, 38, or 125, this may indicate that the action frame is related to an IDC. In the following, it is assumed that the category field value is 38, but is not limited thereto.

[0429] The IDC action field value contained within the action frame may be determined based on the category field value. For example, if the IDC action field value is 0, this may indicate an IDC response, and IDC action field values ​​from 1 to 255 may be reserved.

[0430] For example, if the IDC action field value is 0, this may mean that an IDC response is included in the body of the action frame. Accordingly, the IDC action field may be configured as shown in Table 37.

[0431] As an example of the present disclosure, the element ID for defining IDC information and A-control information elements can be configured as shown in Table 45.

[0432] Element Element ID Element ID Extension Extensible Fragmentable...IDC Info255117 Yes No...

[0433] As an example of the present disclosure, the IDC information element may be configured as shown in Table 46.

[0434] Octet: 1 Octet: 1 Octet: 1 Octet: Variable Element ID Length Element ID Extension IDC Information

[0435] As an example of the present disclosure, the IDC information of the IDC information element may be configured as shown in Table 47.

[0436] Octet: 1 Octet: 1 Octet: Variable Length Control IDC Information

[0437] As an example of the present disclosure, the IDC information subfield may include at least one of the multiple types of IDC information described above. The presence or absence of each of the multiple types of IDC information may be indicated via a control subfield. The length of the IDC information subfield may vary depending on the type of IDC information included.

[0438] FIG. 24 is a diagram for explaining an action frame response of a BSRP trigger frame according to one embodiment of the present disclosure.

[0439] As illustrated in FIG. 24, the AP may transmit a BSRP trigger frame to at least one STA. STA 2, where IDC is to occur, may transmit a response frame (e.g., an IDC action frame) to the AP. Here, the A-control field may be included in the HT control field of the action frame based on the trigger frame. For example, the IDC action frame may include information related to the IDC.

[0440] Specifically, the BSRP trigger frame may include an IDC information request, a general response instruction, and / or requested information. A response frame to the BSRP trigger frame (e.g., a response frame composed of a new action frame) may include a BSR A-control field in the HT control area, and information related to the IDC may be included in the action frame body. For example, as illustrated in FIG. 25, an IDC action frame may include an A-control field related to the BSR and an action frame body containing information related to the IDC.

[0441] Example 7

[0442] Example 7 relates to an aperiodic IDC signaling method utilizing compressed BA.

[0443] Information about one or more types of IDCs may be included in an IDC information field or a control information field / element, and the IDC information field or the control information field / element may be included in a compressed BA frame. The following embodiment relates to a method for configuring IDC information on a compressed BA frame. That is, since the compressed BA frame is a frame that can be transmitted to one STA, the IDC information field or the control information / element may be included on the BA frame according to the method described below.

[0444] Example 7-1

[0445] In one embodiment of the present disclosure, an IDC information field or a control information field / element may be set via reserved bits of a BA control field of a compressed BA frame.

[0446] The presence of the IDC information field can be indicated using one of the reserved bits in the BA control field. Additionally or alternatively, the presence of the control information field can be indicated using an ID. In this case, the presence of control information is indicated, and if the control information exists, the IDC information can be included in the BA frame using a specific ID mapped to the IDC information.

[0447] Additionally or alternatively, one of the fields not used by non-DMG STAs, such as No Memory Kept, Memory Settings on Tag, Management ACK, etc., may be replaced with a field indicating the presence or absence of the IDC information field. For example, if the BA information field is included in the BA frame, the IDC information field or the control information field may be positioned subsequent to the BA information field.

[0448] FIG. 25 is a diagram for explaining the configuration and related procedures of a compressed BA frame according to one embodiment of the present disclosure.

[0449] Specifically, as illustrated in FIG. 25, a BA control field and an IDC information field (or a control information field) may be included on a compressed BA frame, and a field indicating whether an IDC information field (or a control information field) exists on the BA control field may be included. For example, the first bit of the BA control field may indicate whether control information or IDC information exists. If control information or IDC information exists on the BA control field, the IDC information or the IDC information in the control information may be placed after the BA information.

[0450] For example, an AP may transmit data to an STA, and the STA may transmit a compressed BA frame to the AP in response to the data. The compressed BA frame may include information indicating that an IDC has occurred and information about the IDC.

[0451] Example 7-2

[0452] Example 7-2 relates to a method for setting an IDC-related field through a specific value of a fragment number field of a BA start sequence control field of a compressed BA frame.

[0453] For example, a particular value of a fragment number that is not used in the fragment number field (e.g., a value that is not used in the fragment number field) may be used to indicate / set at least one field associated with the IDC.

[0454] When a specific value as described above is set in the fragment number field, the IDC information field or the control information field may be included in the compressed BA frame instead of the BA bitmap subfield. In addition, the size of the field may be the size of the IDC information field or the control information field itself.

[0455] Additionally or alternatively, the size of the BA bitmap subfield may be utilized. For example, if 8 octets are used as the size of the BA bitmap subfield, the remaining bits of the 8 octets, excluding the IDC information field or the control information field, may be reserved.

[0456] Additionally or alternatively, the methods of each of Examples 7-1 and 7-2 may be used simultaneously.

[0457] As an example of the present disclosure, whether IDC information or control information is included in a compressed BA frame may be indicated based on a specific value of a fragment number field of a BA information field of a compressed BA frame. For example, if the fragment number field value is set to 1111, this may mean that a field related to IDC information in the IDC information or control information follows the fragment number field.

[0458] For example, an AP may transmit data to an STA, and the STA may transmit a compressed BA frame to the AP in response to the data. The compressed BA frame may include information indicating that an IDC has occurred and information about the IDC.

[0459] Additionally or alternatively, when the IDC information field and the control information field are included in a compressed BA frame, the BA information field may not be included in the BA frame. In this case, whether or not the BA information field is additionally included may be indicated through a reserved bit in the BA control field.

[0460] Additionally or alternatively, the compressed BA frame may not be a response frame to data transmitted by the AP. For example, the compressed BA frame may be a response frame to a BAR (BA Request) frame (e.g., compressed BAR), a BSRP TF, or a TF of another variant (e.g., a basic / BQRP TF).

[0461] Example 7-3

[0462] In one embodiment of the present disclosure, one or more IDC information fields and / or control information fields / elements may be included in a multi-STA BA frame. For example, fields related to IDC may be set / indicated through specific values ​​in the AID TID information field of the multi-STA BA frame.

[0463] At least one of the AID11, ACK type, and TID fields present in the AID TID information field of the multi-STA BA frame may be set to a specific value, thereby indicating whether an IDC information field exists on the multi-STA BA frame. For example, the Ack type field value may be set to 0, and the TID field may be set to one of the values ​​8 to 15.

[0464] Additionally or alternatively, the AID11 field value may be set to a specific value. For example, when a non-AP STA transmits a multi-STA BA frame to the AP, the AID11 field value may be set to a value other than 0 (e.g., 1, 2008).

[0465] Additionally or alternatively, the ACK Type and TID fields may be set to specific values. Since non-AP STAs transmit multi-STA BA frames to the AP, the AP can indicate the presence or absence of the IDC information field through a specific AID value.

[0466] Additionally or alternatively, if the AP transmits a multi-STA BA frame to one or more non-AP STAs, the AID11 field value may be set to a specific value (e.g., one of 0, 2008, and 2044). Additionally or alternatively, if the AP transmits a multi-STA BA frame to only one STA, the AID11 field may be set to the AID of that STA.

[0467] Additionally or alternatively, when a specific value of the AID TID information field is used, an IDC information field or a control information field containing IDC information may be included in the multi-STA BA frame instead of the BA Start Sequence Control field and the BA Bitmap field. Additionally, the size of the field (e.g., the AID TID information field) may be the size of the IDC information field or the control information field itself.

[0468] FIG. 26 is a diagram illustrating the configuration and related procedures of IDC information in a multi-STA BA frame according to one embodiment of the present disclosure. That is, FIG. 26 illustrates a case in which IDC information or control information utilizing the AID TID information field is included in a multi-STA BA frame.

[0469] An STA that receives data (e.g., a multi-TID A-MPDU) from an AP may transmit a multi-STA BA frame to the AP, and the multi-STA BA frame may include information about an IDC related to an IDC event occurrence.

[0470] As an example of the present disclosure, each of the ACK type and TID fields may be set to specific values ​​(e.g., 0 and 14, respectively), and the IDC information field (or control information field) may be positioned subsequent to the TID field.

[0471] Additionally or alternatively, as described above, the AID11 field may also be set to a specific value. BA information for one or more AIDs / TIDs (e.g., BA information for TID 0 and TID 1 for the AP) may also be transmitted to the AP before the IDC information field.

[0472] Additionally or alternatively, a field whose size is the sum of the BA Start Sequence Control field (e.g., 2 octets) and the BA Bitmap Size (e.g., 4 or 8 octets) may be used.

[0473] For example, a fragment number subfield value may be used with a specific AID value, "ACK type field = 0", and "TID field = a specific value." Accordingly, the BA bitmap size may be determined, and IDC information or control information may be included on a multi-STA BA frame based on the BA start sequence control field and the BA bitmap field.

[0474] Additionally or alternatively, if the available field size is larger than the size of the IDC information field or the control information field, the remaining bits except for the information described above may be reserved. For example, in the fragment number subfield, the B3 value may be set to 0, the "B2-B1" value may be set to 3, and the B0 value may be set to 0. The BA bitmap size may be 4 octets, and IDC information or control information may be included on a multi-STA BA frame.

[0475] As another example of the present disclosure, as illustrated in FIG. 27, IDC information or control information may be included using the AID TID information field on a multi-STA BA frame.

[0476] An STA that receives data (e.g., a multi-TID A-MPDU) from an AP may transmit a multi-STA BA frame to the AP, and the multi-STA BA frame may include information about an IDC related to an IDC event occurrence.

[0477] At this time, the ACK type field and TID field values ​​can both be set to 0, the presence of the BA start sequence control field (e.g., 2 octets) is determined, and B3, B2-B1, and B0 of the fragment number field can be set to 0, 3, and 0, respectively. Accordingly, the BA bitmap size can be determined (e.g., 4 octets).

[0478] The fields described above may be used to include IDC information or a control information field containing IDC information in a multi-STA BA frame (e.g., a BA information field of a multi-STA BA frame).

[0479] Additionally or alternatively, the AID11 field value may be set to a specific value and / or the remaining bits may be reserved to contain IDC information within a multi-STA BA frame.

[0480] When the above-described method is applied, when a Multi-STA BA frame is transmitted to multiple STAs, STAs that do not understand the presence of IDC information can understand the length of each AID TID information field.

[0481] Meanwhile, BA information for one or more AIDs / TIDs (e.g., BA information for TID 0 and TID 1 for the AP) may also be transmitted to the AP prior to the IDC information.

[0482] Example 7-4

[0483] In one embodiment of the present disclosure, one or more IDC information fields and / or control information fields / elements may be included in a multi-STA BA frame.

[0484] As another example of the present disclosure, it may be determined whether IDC information is included in a multi-STA BA frame based on a specific value of a fragment number field of a BA start sequence control field of the multi-STA BA frame.

[0485] For example, whether an IDC information field is included on a multi-STA BA frame may be indicated by setting a specific value of the fragment number field of the BA start sequence control field of the AID TID information field.

[0486] For example, a specific value for the fragment number (e.g., a value not to be used in the fragment number field) that causes the BA bitmap to be reserved (e.g., "B3=1", "B2-B1=3", "B0=1") can be used.

[0487] For example, when a specific value of the fragment number field is used, an IDC information field or a control information field may be included in the multi-STA BA frame instead of a BA bitmap subfield. Additionally, the size of the field (e.g., the BA bitmap subfield) may be the size of the IDC information field or the control information field itself. Additionally or alternatively, the size of an existing BA bitmap subfield may be used. For example, when 4 octets are used in relation to the BA bitmap, etc., the remaining bits except for the IDC information field or the control information field among the 4 octets may be reserved.

[0488] Additionally or alternatively, the methods according to Example 7-3 and Example 7-4 may be used simultaneously.

[0489] As an example of the present disclosure, when the fragment number field value is set to "1111" (e.g., "B3 = 1", "B2-B1 = 3", "B0 = 1"), it may mean that an IDC information field or a control information field including IDC information is included in a multi-STA BA frame (or a BA information field, etc.). The above-described method may indicate the presence or absence of IDC information when a multi-STA BA frame is transmitted to one STA.

[0490] Meanwhile, BA information for one or more AIDs / TIDs (e.g., BA information for TID 0 and TID 1 for the AP) may also be transmitted to the AP prior to the IDC information.

[0491] Additionally or alternatively, the presence of the IDC information field may be indicated by one of the bits of the reserved field of the multi-STA BA frame, and an STA that receives the multi-STA BA frame may confirm that the IDC information is present on the multi-STA BA frame.

[0492] Additionally or alternatively, the presence of a control information field may be indicated via an ID. In this case, the presence of control information is indicated, and if the control information exists, IDC information may be included in the BA frame via a specific ID mapped to the IDC information.

[0493] Additionally or alternatively, one of the fields not used by non-DMG STAs, such as No Memory Kept, Memory Settings on Tag, Management ACK, etc., may be replaced with a field indicating the presence or absence of an IDC information field.

[0494] Additionally or alternatively, a specific value (e.g., 0 or 2) may be used on TID_INFO instead of the bits of the reserved field. If a BA information field is present on a multi-STA BA frame, an IDC information field or a control information field may be placed following the BA information field.

[0495] Additionally or alternatively, when the IDC information field and the control information field are included in a multi-STA BA frame, the multi-STA BA frame may not include a BA information field. In this case, the method related to whether or not the BA information field is included as described above may be applied.

[0496] In describing the present disclosure, a multi-STA BA frame may not be limited to a response frame for data transmission. A multi-STA BA frame may be used as a response to a BAR frame (e.g., multi-TID BAR), a BSRP TF, or a trigger frame of another variant (e.g., basic / BQRP TF, etc.), and the multi-STA BA frame may include an IDC information field or a control information field including IDC information.

[0497] Example 8

[0498] Example 8 relates to an IDC periodic timing change signaling procedure.

[0499] As an example of the present disclosure, as illustrated in FIG. 28, information about IDC may be transmitted periodically. For example, STA 1 may recognize that a periodic IDC event has occurred and transmit an IDC TWT request frame containing information related to the IDC to the AP. The AP may obtain information about the IDC from STA 1 and transmit an IDC TWT response frame to STA 1. Based on the information about the IDC, the AP may determine that there is an unavailable time associated with STA 1 for a certain period and interval. The AP may perform various operations to avoid the unavailable time.

[0500] As an example of the present disclosure, as illustrated in FIGS. 29, 30, and 32, STA 1 (e.g., a non-AP STA or AP) may transmit information about periodic IDC to another STA 2 (e.g., an AP or non-AP STA). A new event (e.g., a change in periodic IDC information) may occur in STA 1 as an event related to the periodic IDC information changes or an unpredictable situation occurs. In this case, STA 1 may update information about the IDC.

[0501] Below, we describe how to signal an IDC periodic timing change using each of a BA frame, a new control frame, and a frame containing an A-control field.

[0502] Example 8-1

[0503] Example 8-1 relates to a method for notifying an IDC periodic timing change based on a BA frame.

[0504] As an example of the present disclosure, as illustrated in FIG. 29, STA 1 may recognize that a periodic IDC event occurs and configure an IDC information field containing information about the IDC event. STA 1 may then transmit an IDC TWT setup frame (or request frame) containing the IDC information field to the AP. The AP may confirm information about the IDC through the IDC TWT setup frame received from STA 1 and transmit an IDC TWT setup frame (or response frame) to STA 1.

[0505] Additionally or alternatively, STA 1 may transmit an IDC TWT request frame to the AP in an unsolicited manner. The AP may set the IDC SP based on information about the IDC (e.g., the IDC cycle, etc.).

[0506] The AP can detect the occurrence of data exchange between non-Wi-Fi devices by STA 1 at each IDC SP period. The AP can perform Wi-Fi data exchange by avoiding the IDC SP period (e.g., by adjusting Tx / Rx parameters).

[0507] At this time, if the IDC TWT SP information related to STA 1 changes (for example, clock drift that may affect the interval of IDC TWT SP, channel conditions that may affect the section of IDC TWT SP, retransmission conditions, etc.), information indicating that the IDC TWT SP information has changed may be transmitted to the AP in an aperiodical manner during the section where Wi-Fi transmission occurs. For example, STA 1 may transmit information about the IDC indicating a change in the IDC TWT SP, etc., to the AP through a response to the data (for example, a BA frame).

[0508] For example, information about an IDC may include periodicity change information indicating that information in an IDC TWT SP has changed. For example, a field value related to a periodic change indicating that information in an IDC TWT SP has changed may be set to 1.

[0509] For example, if more than one IDC TWT SP is configured, an ID can be assigned and distinguished for each of the more than one IDC TWT SP through the ID information in the information about the IDC. Before the IDC TWT SP is updated through the IDC TWT setup frame, information about the IDC can be continuously transmitted through the BA frame (or, in response to the A-Control field and / or a new trigger frame, etc.).

[0510] STA 1 then obtains channel access and can transmit information about changed periodic IDC events to the AP via an IDC TWT setup frame (e.g., update). This may interrupt the aperiodic IDC information signaling method.

[0511] Here, the BA frame may include a compressed BA frame and / or a multi-STA BA frame.

[0512] Example 8-2

[0513] Example 8-2 relates to a method for notifying an IDC periodic timing change based on an A-control field (or a frame including an A-control field).

[0514] As an example of the present disclosure, as illustrated in FIG. 30, STA 1 may recognize that a periodic IDC event occurs and configure an IDC information field containing information about the IDC event. STA 1 may then transmit an IDC TWT setup frame (or request frame) containing the IDC information field to the AP. The AP may confirm information about the IDC through the IDC TWT setup frame received from STA 1 and transmit an IDC TWT setup frame (or response frame) to STA 1.

[0515] Additionally or alternatively, STA 1 may transmit an IDC TWT request frame to the AP in an unsolicited manner. The AP may set the IDC SP based on information about the IDC (e.g., the IDC cycle, etc.).

[0516] The AP can detect the occurrence of data exchange between non-Wi-Fi devices by STA 1 at each IDC SP period. The AP can perform Wi-Fi data exchange by avoiding the IDC SP period (e.g., by adjusting Tx / Rx parameters).

[0517] At this time, if the IDC TWT SP information related to STA 1 changes (for example, clock drift that may affect the interval of IDC TWT SP, channel conditions that may affect the section of IDC TWT SP, retransmission conditions, etc.), information indicating that the IDC TWT SP information has changed may be transmitted to the AP in an aperiodical manner during the section where Wi-Fi transmission occurs. For example, STA 1 may transmit information about the IDC indicating a change in the IDC TWT SP, etc., to the AP through a response to a BSRP trigger frame (for example, a QoS null frame).

[0518] For example, information about an IDC may include periodicity change information indicating that information in an IDC TWT SP has changed. For example, a field value related to a periodic change indicating that information in an IDC TWT SP has changed may be set to 1.

[0519] For example, if one or more IDC TWT SPs are configured, an ID can be assigned and distinguished for each one or more IDC TWT SPs through the ID information in the information about the IDC. Before the IDC TWT SPs are updated through the IDC TWT setup frame, information about the IDC can be continuously transmitted through frames containing the A-Control field (or, for example, in response to a BA frame and / or a new trigger frame).

[0520] STA 1 then obtains channel access and can transmit information about changed periodic IDC events to the AP via an IDC TWT setup frame (e.g., update). This may interrupt the aperiodic IDC information signaling method.

[0521] Example 8-3

[0522] Example 8-3 relates to a method for notifying an IDC periodic timing change based on a new control frame.

[0523] Figure 31 is a diagram illustrating a method for notifying periodic IDC information according to one embodiment of the present disclosure. Specifically, Figure 31 relates to a procedure for transmitting and receiving IDC-related information via a new ICF and a new ICR. For example, IDC-related information can be transmitted and received via an integrated control frame for IDC, and the operations described below can be applied to all types of control frames.

[0524] As an example of the present disclosure, referring to FIG. 31, an AP may transmit an ICF containing data to an STA. At this time, a response subfield of the ICF (e.g., a response subfield included in a control frame of the ICF) may indicate that the frame is an ICF. For example, if the response subfield is set to 0 (or 1), this may mean / indicate that the frame transmitted by the AP to the STA is an ICF. In addition, the ICF may include an IDC information request field for checking a status related to the IDC of the STA.

[0525] For example, to receive information related to all types of IDC, the AP can set the IDC Request Type subfield of the ICF to 0. The STA can identify a request for information related to all types of IDC through the IDC Request Type subfield of the ICF set to 0. In addition, if information about a predicted event that causes an IDC to occur exists at the time of receiving the ICF, the STA can configure information related to the IDC.

[0526] Information related to the corresponding IDC may be included in the IDC information field of the ICR. The STA may set the value of the response subfield of the ICR (e.g., the response subfield of the control field of the ICR) to 1 for ICR transmission. Based on the value of the response subfield being set to 1 (or 0), this may mean / indicate that the frame transmitted by the STA is an ICR.

[0527] An STA can transmit an ICR to an AP, and the AP can identify that an IDC has occurred in the STA based on the ICR. Furthermore, the AP can perform data exchange operations with the STA by avoiding the time, channel, and spatial stream in which the IDC occurs based on information related to the IDC contained in the ICR.

[0528] As an example of the present disclosure, as illustrated in FIG. 32, STA 1 may recognize that a periodic IDC event occurs and configure an IDC information field containing information about the IDC event. STA 1 may then transmit an IDC TWT setup frame (or request frame) containing the IDC information field to the AP. The AP may confirm information about the IDC through the IDC TWT setup frame received from STA 1 and transmit an IDC TWT setup frame (or response frame) to STA 1.

[0529] Additionally or alternatively, STA 1 may transmit an IDC TWT request frame to the AP in an unsolicited manner. The AP may set the IDC SP based on information about the IDC (e.g., the IDC cycle, etc.).

[0530] The AP can detect the occurrence of data exchange between non-Wi-Fi devices by STA 1 at each IDC SP period. The AP can perform Wi-Fi data exchange by avoiding the IDC SP period (e.g., by adjusting Tx / Rx parameters).

[0531] At this time, if the IDC TWT SP information related to STA 1 changes (e.g., clock drift that may affect the interval of IDC TWT SP, channel conditions that may affect the section of IDC TWT SP, retransmission conditions, etc.), information indicating that the IDC TWT SP information has changed may be transmitted to the AP in an aperiodical manner during the section where Wi-Fi transmission occurs. For example, STA 1 may transmit information about the IDC indicating the change of the IDC TWT SP, etc., to the AP through a new control frame ICF and / or a response to a trigger frame (e.g., ICR and / or a new action frame).

[0532] For example, information about an IDC may include periodicity change information indicating that information in an IDC TWT SP has changed. For example, a field value related to a periodic change indicating that information in an IDC TWT SP has changed may be set to 1.

[0533] For example, when one or more IDC TWT SPs are configured, an ID may be assigned and distinguished for each one or more IDC TWT SPs through ID information in the information about the IDC. Before the IDC TWT SPs are updated through the IDC TWT setup frame, information about the IDC may be continuously transmitted through the ICF, trigger frame, ICR, and / or new action frame (or, BA frame and / or response to new trigger frame, etc.). Data exchange between the AP and STA may be possible before the unavailable time after the ICF / ICR transmission and reception. At this time, information about the IDC may be included in the BA frame for the data.

[0534] STA 1 then obtains channel access and can transmit information about changed periodic IDC events to the AP via an IDC TWT setup frame (e.g., update). This may interrupt the aperiodic IDC information signaling method.

[0535] As an example of the present disclosure, an AP (or a separate STA 2) can decode one or more PPDUs and / or frames containing information about an IDC, and determine whether to transmit and the transmission capability in the IDC section of the first STA through decoding the one or more PPDUs and / or frames.

[0536] FIG. 33 is a diagram illustrating a PPDU transmission and reception procedure between a transmitting STA and a receiving STA according to one embodiment of the present disclosure. Some of the steps shown in FIG. 33 may be omitted depending on circumstances and / or settings. The transmitting device and the receiving STA may be APs and / or non-AP STAs.

[0537] The transmitting STA may obtain control information related to the aforementioned tone plan (or RU / DRU) (S105). The control information related to the tone plan may include the size and location of the RU, control information related to the RU, information about the frequency band in which the RU is included, information about the STA receiving the RU, etc.

[0538] The transmitting STA may configure / generate a PPDU based on the acquired control information (S110). Configuring / generating a PPDU may mean configuring / generating each field of the PPDU. That is, the step of configuring / generating a PPDU may include a step of configuring U-SIG and UHR-SIG-A / B / C fields that contain control information regarding a tone plan.

[0539] That is, the step of configuring / generating a PPDU may include a step of configuring a field including control information (e.g., N bitmap) indicating the size / position of the RU and / or a step of configuring a field including an identifier (e.g., AID) of an STA receiving the RU.

[0540] Additionally, the step of configuring / generating a PPDU may include a step of generating an STF / LTF sequence to be transmitted via a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0541] Additionally, the step of constructing / generating a PPDU may include a step of generating a data field (i.e., an MPDU) to be transmitted via a specific RU.

[0542] The transmitting STA can transmit the configured / generated PPDU to the receiving STA (S115).

[0543] Specifically, the transmitting STA can perform at least one of cyclic shift diversity (CSD), spatial mapping, inverse discrete Fourier transform (IDFT) / inverse fast Fourier transform (IFFT) operation, and guard interval (GI) insertion operation.

[0544] The receiving STA can decode the PPDU and obtain control information related to the tone-plan (or RU) (S120).

[0545] Specifically, the receiving STA can decode the L-SIG and U-SIG / UHR-SIG of the PPDU based on the L-STF / LTF, and obtain information included in the L-SIG and U-SIG, UHR-SIG fields. Information about various tone plans (i.e., RUs) of the present disclosure can be included in the U-SIG / UHR-SIG (UHR-SIG-A / B / C, etc.), and the receiving STA can obtain information about the tone plan (i.e., RU) through the EHT-SIG.

[0546] The receiving STA can decode the remaining portion of the PPDU based on the information about the acquired tone plan (i.e., RU) (S125). For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about the tone plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the tone plan (i.e., RU) and obtain the MPDU included in the data field.

[0547] Additionally, the receiving STA may perform a processing operation to forward the decoded data to a higher layer (e.g., the MAC layer). Furthermore, if the higher layer instructs the PHY layer to generate a signal in response to the data forwarded to the higher layer, the receiving STA may perform a subsequent operation.

[0548] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0549] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0550] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

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

Claims

1. A step of transmitting a first frame containing first information related to an unavailability operation by a first station (STA) to a second STA; and A step of transmitting a second frame by the first STA to the second STA based on a change in timing of a period of an i-th unavailable operation among periods of at least one unavailable operation related to the first information, The second frame includes second information related to whether the timing of the period of the i-th unavailable operation has changed and third information related to the identifier of the period of the i-th unavailable operation, A method wherein the duration of the i-th unavailable operation is determined based on the second frame.

2. In paragraph 1, A method in which the above unavailable operation includes an operation in which an operating channel of the first STA or at least one subchannel of the operating channel becomes unavailable.

3. In paragraph 1, A method according to claim 1, wherein the first information comprises at least one of the time at which the unavailable operation starts, the period of the unavailable operation, the length of the period of the unavailable operation, the channel or bandwidth on which the unavailable operation occurs, the number of spatial streams associated with the unavailable operation, or an antenna available during the period of the unavailable operation.

4. In paragraph 1, The method according to claim 1, wherein the second frame is one of a compressed block acknowledgment (BA) frame, a multi-STA BA frame, a quality of service (QoS) null frame, a frame including an aggregated control field related to the unavailable operation, an initial control response (ICR), or an action frame related to the unavailable operation.

5. In paragraph 1, The second frame is a response frame to the third frame transmitted from the second STA to the first STA, The method according to claim 3, wherein the third frame is one of a physical layer protocol data unit (PPDU) including a trigger frame, ICF, and downlink DL data.

6. In paragraph 1, A method wherein the second frame includes at least one of a start time or a length of a period of the i-th unavailable operation.

7. In paragraph 1, The first frame includes a target wake time (TWT) setup frame, A method in which the first information is included in a TWT element of the TWT setup frame.

8. In paragraph 1, A fourth frame including fourth information for updating the first information is transmitted from the first STA to the second STA, A method wherein a period of at least one unavailable operation related to the fourth information is set.

9. In paragraph 3, A method wherein the time at which the above-described unavailable operation starts includes a partial timing synchronization function (TSF) time at which the above-described unavailable operation is expected to start.

10. In paragraph 1, A method wherein each of the first STA and the second STA is either a non-access point (AP) STA or an AP.

11. In the first STA, the first STA: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting a first frame containing first information related to an unavailability operation to a second STA via the one or more transceivers; and Based on a change in timing of the duration of the i-th unavailable operation among the durations of at least one unavailable operation related to the first information, a second frame is set to be transmitted to the second STA through the one or more transceivers, The second frame includes second information related to whether the timing of the period of the i-th unavailable operation has changed and third information related to the identifier of the period of the i-th unavailable operation, The duration of the above i-th unavailable operation is determined based on the second frame, the first STA.

12. A step of receiving a first frame containing first information related to an unavailability operation from a first STA by a second station (STA); and A step of receiving a second frame from the first STA by the second STA based on a change in timing of a period of the i-th unavailable operation among the periods of at least one unavailable operation related to the first information, The second frame includes second information related to whether the timing of the period of the i-th unavailable operation has changed and third information related to the identifier of the period of the i-th unavailable operation, A method wherein the duration of the i-th unavailable operation is determined based on the second frame.

13. In the second station (STA), the second STA: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving a first frame containing first information related to an unavailability operation from a first STA via the one or more transceivers; and Based on a change in timing of a period of an i-th unavailable operation among at least one unavailable operation period related to the first information, a second frame is set to be received from the first STA through the one or more transceivers, The second frame includes second information related to whether the timing of the period of the i-th unavailable operation has changed and third information related to the identifier of the period of the i-th unavailable operation, The duration of the above i-th unavailable operation is determined based on the second frame, the second STA.

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

15. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a device in a wireless LAN system to perform a method according to any one of claims 1 to 10.

Images