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. The method according to an embodiment of the present disclosure may comprise the steps of: transmitting, by a first station (STA) to a second STA, a request frame including first information related to enabling or disabling of a first operation mode among at least one operation mode; and on the basis that a first response frame for the request frame is not received from the second STA within a predetermined time, performing, by the first STA, retransmission of the request frame, wherein the first information is included in a reconfiguration multi-link element of the request 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 apparatus 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 LANs (WLANs) to improve transmission rates, increase bandwidth, enhance reliability, reduce errors, and reduce latency. Among wireless LAN technologies, the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series of standards can be referred to as Wi-Fi. For example, technologies recently introduced to wireless LANs 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 an improved wireless communication environment, advanced technologies for Extremely High Throughput (EHT) are being discussed. For example, technologies for Multiple Input Multiple Output (MIMO) supporting increased bandwidth, efficient utilization of multiple bands, and increased spatial streams, as well as technologies for multiple access points (AP) coordination, are being researched. In particular, various technologies are being studied to support traffic with low latency or real-time characteristics. Furthermore, new technologies to support ultra-high reliability (UHR), including improvements or extensions of EHT technology, are being discussed.

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

[0005] The technical problem of the present disclosure is to provide a method and apparatus for performing a negotiation procedure for an IDC mechanism.

[0006] The technical problem of the present disclosure is to provide a method and apparatus for handling errors that may occur when enabling or disabling an IDC mechanism.

[0007] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below.

[0008] A method according to one embodiment of the present disclosure comprises: a step of transmitting a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode to a second STA by a first station (STA); and a step of retransmitting the request frame by the first STA based on the fact that a first response frame for the request frame is not received from the second STA within a certain time, wherein the first information may be included in a reconfiguration multi-link element of the request frame.

[0009] A method according to another embodiment of the present disclosure comprises: receiving a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode by a second station (STA) from a first STA; and generating a first response frame for the request frame by the second STA, wherein, based on the fact that the first response frame is not transmitted to the first STA within a certain time, the request frame is transmitted from the first STA to the second STA, and the first information may be included in a reconfiguration multi-link element of the request frame.

[0010] By various embodiments of the present disclosure, a method and apparatus for transmitting or receiving IDC-related information in a wireless LAN system may be provided.

[0011] By various embodiments of the present disclosure, a method and apparatus for performing a negotiation procedure for an IDC mechanism may be provided.

[0012] By various embodiments of the present disclosure, a method and apparatus for handling errors that may occur when enabling or disabling an IDC mechanism may be provided.

[0013] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description.

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

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

[0017] FIG. 3 is a diagram illustrating a link setup process to which the present disclosure can be applied.

[0018] FIG. 4 is a drawing illustrating a backoff process to which the present disclosure may be applied.

[0019] FIG. 5 is a diagram illustrating a CSMA / CA-based frame transmission operation to which the present disclosure may be applied.

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

[0021] FIG. 7 is a drawing illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure may be applied.

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

[0023] FIG. 9 is a drawing for explaining an example of the operation of a first STA according to the present disclosure.

[0024] FIG. 10 is a drawing for explaining an example of the operation of a second STA according to the present disclosure.

[0025] FIG. 11 shows examples of UHR capability elements according to the present disclosure.

[0026] FIG. 12 is a drawing showing examples of fields including timeout interval information according to the present disclosure.

[0027] FIG. 13 shows examples of elements and fields related to the IDC operation mode according to the present disclosure.

[0028] FIG. 14 shows an example of IDC mode enable using an action frame according to the present disclosure.

[0029] FIG. 15 shows an example of an IDC mode enable using action frame-based requests and responses according to the present disclosure.

[0030] FIG. 16 shows another example of an IDC mode enable using action frame-based requests and responses according to the present disclosure.

[0031] FIGS. 17 and 18 illustrate a procedure according to one embodiment of the present disclosure when the STA does not receive a response to an IDC enable or disable request.

[0032] FIG. 19 shows examples in which enable / disable instruction information of a specific operation mode is included in a reset ML element according to the present disclosure.

[0033] FIG. 20 shows an example of an IDC mode enable using a multi-link operation update according to the present disclosure.

[0034] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

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

[0036] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0037] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0038] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and in the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term "and / or" as used in this disclosure may refer to any one of the related enumerated items, or refers to and includes any and all possible combinations of two or more of them. Additionally, the " / " between words in this disclosure has the same meaning as "and / or" unless otherwise noted.

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

[0040] The following describes the technical features to which the examples of the present disclosure may be applied.

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

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

[0043] The device (100, 200) exemplified in FIG. 1 may be referred to as a station (STA). For example, the device (100, 200) exemplified in FIG. 1 may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, or a receiving STA. For example, the STA (110, 200) may perform the role of an access point (AP) or a non-AP. That is, in the present disclosure, the STA (110, 200) may perform the functions of an AP and / or a non-AP. If the STA (110, 200) performs the AP function, it may simply be referred to as an AP, and if the STA (110, 200) performs the non-AP function, it may simply be referred to as a STA. Additionally, in the present disclosure, the AP may also be indicated as an AP STA.

[0044] 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) may include interfaces for the medium access control (MAC) layer and the physical layer (PHY) that comply with the specifications of the IEEE 802.11 standard.

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

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

[0047] The second device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed in this disclosure. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement 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 through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be used in combination with an RF unit. In the present disclosure, the device may refer to a communication modem / circuit / chip.

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

[0049] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or 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 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure may be included in 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 sequences disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0050] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0051] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of the present disclosure to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in the present disclosure from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected 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, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this disclosure through one or more antennas (108, 208). In this disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0052] 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 transceiver (106, 206) of FIG. 1 may perform the operation of transmitting and receiving signals (e.g., packets or PPDU (Physical Layer Protocol Data Unit) according to IEEE 802.11a / b / g / n / ac / ax / be / bn, etc.). Additionally, the operation of generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals by various STAs in the present disclosure may be performed by the processor (102, 202) of FIG. 1. For example, an example of an operation to generate a transmission and reception signal or to perform data processing or operations in advance for a transmission and reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of fields (SIG (signal), STF (short training field), LTF (long training field), Data, etc.) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for fields (SIG, STF, LTF, Data, etc.) included in the PPDU; 4) power control operations and / or power saving operations applied to the STA; and 5) operations related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (104, 204) of FIG. 1.

[0053] In the following, the 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 the AP STA, and the receiver may be part of the non-AP STA. The 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 the non-AP STA, and the receiver may be part of the AP STA.

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

[0055] The structure of a wireless LAN system can be composed of multiple components. Through the interaction of multiple components, a wireless LAN that supports STA mobility transparent to the upper layer can be provided. A Basic Service Set (BSS) corresponds to the basic building block of a wireless LAN. Figure 2 exemplarily illustrates 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). In Figure 2, the ellipse representing the BSS can also be understood as representing the coverage area where the STAs included in the corresponding BSS maintain communication. This area can be referred to as a Basic Service Area (BSA). If a STA moves outside the BSA, it becomes unable to communicate directly with other STAs within that BSA.

[0056] Excluding the DS illustrated in Fig. 2, the most basic type of BSS in a wireless LAN is the Independent BSS (IBSS). For example, an IBSS can have a minimal form consisting of only two STAs. For instance, assuming other components are omitted, a BSS1 composed of only STA1 and STA2, or a BSS2 composed of only STA3 and STA4, can each be considered a representative example of an IBSS. Such a configuration is possible when the STAs can communicate directly without an AP. Furthermore, this type of wireless LAN is not configured through pre-planning but can be configured when a LAN is needed, and this can be referred to as an ad-hoc network. Since an IBSS does not include an AP, there is no centralized management entity. In other words, in an IBSS, STAs are managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and since connections to distributed systems (DS) are not allowed, they form a self-contained network.

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

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

[0059] DS refers to a structure in which BSSs are interconnected. Specifically, as shown in FIG. 2, a BSS may exist as a component in an extended form of a network composed of multiple BSSs. DS is a logical concept and can be specified by the characteristics of the Distributed System Medium (DSM). In this regard, the Wireless Medium (WM) and the DSM can be logically distinguished. Each logical medium is used for a different purpose and is utilized by different components. These media are not limited to being identical or different. The flexibility of the wireless LAN structure (DS structure or other network structure) can be explained by the fact that multiple media are logically distinct in this way. That is, the wireless LAN structure can be implemented in various ways, and the corresponding wireless LAN structure can be specified independently by the physical characteristics of each implementation.

[0060] DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary for handling addresses to destinations. Additionally, DS may include a component called a portal that acts as a bridge for connecting the wireless LAN with another network (e.g., IEEE 802.X).

[0061] An AP refers to an entity that enables access to a DS via a WM for combined non-AP STAs and also possesses the functionality of an STA. Data movement between a BSS and a DS can be performed through the AP. For example, STA2 and STA3 shown in FIG. 2 possess the functionality of an STA and provide the ability for combined non-AP STAs (STA1 and STA4) to access a DS. Furthermore, since all APs fundamentally correspond to STAs, all APs are addressable entities. The address used by the AP for communication on the WM and the address used by the AP for communication on the DSM do not necessarily have to be the same. A BSS composed of an AP and one or more STAs can be referred to as an infrastructure BSS.

[0062] Data transmitted from one of the STA(s) coupled to the AP to the STA address of the AP can always be received at an uncontrolled port and processed by an IEEE 802.1X port access entity. Additionally, if the controlled port is authenticated, the transmitted data (or frame) can be forwarded to the DS.

[0063] In addition to the structure of the aforementioned DS, an Extended Service Set (ESS) may be configured to provide wider coverage.

[0064] An ESS refers to a network of arbitrary size and complexity composed of DSs and BSSs. An ESS can correspond to a set of BSSs connected to a single DS. However, an ESS does not contain a DS. An ESS network is characterized by appearing as an IBSS at the Logical Link Control (LLC) layer. STAs included in 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 included in a single ESS can have the same Service Set Identification (SSID). The SSID is distinct from the BSSID, which is the identifier for the BSS.

[0065] In wireless LAN systems, no assumptions are made regarding the relative physical locations of BSSs, and the following forms are all possible. BSSs may partially overlap, which is a form commonly used to provide continuous coverage. Additionally, BSSs may not be physically connected, and logically, there is no limit to the distance between BSSs. Furthermore, BSSs may be located in the same physical location, which can be used to provide redundancy. Also, one (or more) IBSS or ESS networks may physically exist in the same space as one (or more) ESS networks. This may apply to ESS network configurations where an ad-hoc network operates at a location where an ESS network exists, where wireless networks are physically overlapping by different organizations, or where two or more different access and security policies are required at the same location.

[0066] FIG. 3 is a diagram illustrating a link setup process to which the present disclosure can be applied.

[0067] In order 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 go through authentication procedures for security. The link setup process can also be referred to as the session initiation process or the session setup process. Additionally, the processes of discovery, authentication, association, and security setup in the link setup process can be collectively referred to as the association process.

[0068] In step S310, the STA may perform a network discovery operation. The network discovery operation may include the STA's scanning operation. That is, in order for the STA to access a network, it must find a network it can join. Before joining a wireless network, the STA must identify a compatible network, and the process of identifying networks existing in a specific area is called scanning.

[0069] Scanning methods include active scanning and passive scanning. Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels to search for nearby APs, transmits a probe request frame, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame; however, in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. 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 in the same way (i.e., transmit and receive probe request / response on channel 2).

[0070] Although not illustrated in FIG. 3, the scanning operation may be performed using a passive scanning method. In passive scanning, the STA performing the scanning waits for a beacon frame while switching between channels. A beacon frame is one of the management frames defined in IEEE 802.11, which is periodically transmitted to announce the presence of a wireless network and to allow the scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, and in an IBSS, the STAs within the IBSS take turns transmitting beacon frames. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. The STA that receives the beacon frame stores the BSS-related information included in the received beacon frame, moves to the next channel, and can perform scanning in the next channel in the same way. When comparing active scanning and passive scanning, active scanning has the advantage of lower delay and power consumption than passive scanning.

[0071] 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 in step S340 described later.

[0072] The authentication process involves the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

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

[0074] The STA can send an authentication request frame to the AP. Based on the information contained in the received authentication request frame, the AP can determine whether to allow authentication for the STA. The AP can provide the result of the authentication process to the STA through an authentication response frame.

[0075] After the STA is successfully authenticated, the association process can be performed in step S330. The association process includes the STA transmitting an association request frame to the AP, and in response, the AP transmitting an association response frame to the STA.

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

[0077] After the STA is successfully joined to the network, a security setup process can be performed in step S340. The security setup process in step S340 may be described as an authentication process through RSNA (Robust Security Network Association) requests / responses, and the authentication process in step S320 may be referred to as the first authentication process, and the security setup process in step S340 may simply be referred to as the authentication process.

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

[0079] FIG. 4 is a drawing illustrating a backoff process to which the present disclosure may be applied.

[0080] In wireless LAN systems, the basic access mechanism for MAC (Medium Access Control) is the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism is also known as the Distributed Coordination Function (DCF) of IEEE 802.11 MAC, and it basically employs a "listen before talk" access mechanism. According to this type of access mechanism, the AP and / or STA may perform Clear Channel Assessment (CCA) to sense the wireless channel or medium for a predetermined time interval (e.g., DIFS (DCF Inter-Frame Space)) before starting transmission. If the sensing result determines that the medium is in an idle status, it starts transmitting a frame through that 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 wait by setting a delay period for medium access (e.g., a random backoff period) before attempting to transmit a frame. 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.

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

[0082] Referring to FIG. 4, the operation based on the random backoff period is described. When a medium in an occupied / busy state changes to an idle state, multiple STAs may attempt to transmit data (or frames). As a measure to minimize collisions, each STA may select a random backoff count and attempt transmission after waiting for the corresponding slot time. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​in the range from 0 to CW. Here, CW is the Contention Window parameter value. The CW parameter is given an initial value of CWmin, but in the case of transmission failure (e.g., failure to receive an ACK for a transmitted frame), it may take a value twice that amount. When the CW parameter value becomes CWmax, data transmission may be attempted while maintaining the CWmax value until data transmission is successful; if data transmission is successful, it is reset to the CWmin value. The values ​​of CW, CWmin, and CWmax are 2 n It is desirable to set it to -1 (n=0, 1, 2, ...).

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

[0084] In the example of Fig. 4, when a packet to be transmitted arrives at the MAC of STA3, STA3 confirms that the medium is idle for DIFS and can immediately transmit the frame. The remaining STAs monitor whether the medium is occupied or busy and wait. Meanwhile, data to be transmitted may also arise from each of STA1, STA2, and STA5, and each STA can perform a countdown of the backoff slot according to a random backoff count value selected by each after waiting for DIFS when the medium is monitored to be idle. Assume the case where STA2 selects the smallest backoff count value and STA1 selects the largest backoff count value. That is, this exemplifies a case where, at the point when STA2 finishes the backoff count and starts transmitting the frame, the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1. STA1 and STA5 pause the countdown briefly and wait while STA2 occupies the medium. When STA2's possession ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and then resume the paused backoff count. That is, they can start transmitting a frame after counting down the remaining backoff slots corresponding to the remaining backoff time. Since STA5's remaining backoff time was shorter than STA1's, STA5 starts transmitting the frame. While STA2 is occupying the medium, data to be transmitted may also be generated by STA4. From STA4's perspective, when the medium becomes idle, it waits for DIFS, performs a countdown based on a random backoff count value selected by itself, and can start transmitting a frame. The example in Figure 4 illustrates a case where STA5's remaining backoff time happens to match STA4's random backoff count value; in this case, a collision may occur between STA4 and STA5. If a collision occurs, neither STA4 nor STA5 receives an ACK, resulting in a failure to transmit data.In this case, STA4 and STA5 can double the CW value, select a random backoff count value, and perform a countdown. STA1 waits while the medium is occupied due to transmission by STA4 and STA5, and when the medium becomes idle, it waits for DIFS, and then can start transmitting frames after the remaining backoff time has passed.

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

[0086] A QoS (Quality of Service) STA can transmit a frame after backoff, which is performed after the passage of the arbitration IFS (AIFS) for the access category (AC) to which the frame belongs, i.e., AIFS[i] (where i is a value determined by the AC). Here, the frame for which AIFS[i] can be used can be a data frame or a management frame, and can also be a control frame rather than a response frame.

[0087] FIG. 5 is a diagram illustrating a CSMA / CA-based frame transmission operation to which the present disclosure may be applied.

[0088] As previously mentioned, the CSMA / CA mechanism includes virtual carrier sensing in addition to physical carrier sensing, where the STA directly senses the medium. Virtual carrier sensing is intended to mitigate problems that may occur in medium access, such as the hidden node problem. For virtual carrier sensing, the STA's MAC can utilize the Network Allocation Vector (NAV). The NAV is a value that indicates to other STAs the time remaining until the medium becomes available, provided that the STA currently using or authorized to use the medium is using it. Therefore, the value set as the NAV corresponds to the period during which the medium is scheduled to be used by the STA transmitting the frame, and the 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 frame's MAC header.

[0089] In the example of FIG. 5, it is assumed that STA1 intends to transmit data to STA2, and STA3 is located in a position where it can overhear part or all of the frames transmitted and received between STA1 and STA2.

[0090] In order to reduce the possibility of collisions between multiple STAs in a CSMA / CA-based frame transmission operation, a mechanism utilizing RTS / CTS frames may be applied. In the example of FIG. 5, while STA1 is transmitting, the medium may be determined to be idle based on the carrier sensing result of STA3. That is, STA1 may be a hidden node to STA3. Alternatively, in the example of FIG. 5, while STA2 is transmitting, the medium may be determined to be idle based on the carrier sensing result of STA3. That is, STA2 may be a hidden node to STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, it is possible to prevent a STA outside the transmission range of either STA1 or STA2, or a STA outside the carrier sensing range for transmission from STA1 or STA3, from attempting to occupy the channel during data transmission and reception between STA1 and STA2.

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

[0092] If the channel is idle during DIFS, STA1 can send an RTS frame to STA2 after performing backoff. If STA2 receives the RTS frame, it can send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0093] If STA3 cannot overhear a CTS frame from STA2 but can overhear an RTS frame from STA1, STA3 can set a NAV timer for the duration of subsequently transmitted frames (e.g., SIFS + CTS frame + SIFS + data frame + SIFS + ACK frame) using the duration information included in the RTS frame. Alternatively, if STA3 cannot overhear an RTS frame from STA1 but can overhear a CTS frame from STA2, STA3 can set a NAV timer for the duration of subsequently transmitted frames (e.g., SIFS + data frame + SIFS + ACK frame) using the duration information included in the CTS frame. That is, if STA3 can overhear one or more of the RTS or CTS frames from one or more of STA1 or STA2, it can set a NAV accordingly. 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.

[0094] If STA1 receives a CTS frame from STA2, it may transmit a data frame to STA2 after SIFS from the time the reception of the CTS frame is completed. If STA2 successfully receives the data frame, it may transmit an ACK frame to STA1 as an acknowledgment to the data frame after SIFS. STA3 may determine whether the channel is in use through carrier sensing when the NAV timer expires. If STA3 determines that the channel is not in use by another terminal during DIFS from the time the NAV timer expires, it may attempt channel access after a contention window (CW) based on random backoff has passed.

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

[0096] Based on instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare the MPDU (MAC PDU) to be transmitted. For example, upon receiving an instruction from the MAC layer requesting the start of transmission, the PHY layer switches to transmit mode and can construct the information provided by the MAC layer (e.g., data) into a frame for transmission. Additionally, if the PHY layer detects a valid preamble of a received frame, it monitors the preamble header and sends an instruction to the MAC layer indicating the start of reception.

[0097] As such, information transmission and reception in wireless LAN systems are carried out in the form of frames, and for this purpose, the Physical Layer Protocol Data Unit (PPDU) format is defined.

[0098] A basic PPDU may include a Short Training Field (STF), a Long Training Field (LTF), a Signal (SIGNAL) field, and a Data field. The most basic (e.g., the non-HT (High Throughput)) PPDU format illustrated in FIG. 7 may consist only of Legacy-STF (Legacy-STF), Legacy-LTF (Legacy-LTF), Legacy-SIG (Legacy-SIG) fields and a Data field. In addition, 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 other types of) RL-SIG, U-SIG, non-legacy SIG fields, 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.

[0099] 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 and frequency error estimation. STF and LTF can be considered signals for synchronization and channel estimation in the OFDM physical layer.

[0100] The SIG field may contain various information related to the transmission and reception of the PPDU. For example, the L-SIG field consists 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 contain information regarding the modulation and coding rates of the data. For example, the 12-bit Length field may contain information regarding 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 non-HT, HT, VHT, or EHT PPDUs, the value of the Length field may be determined as a multiple of 3. For example, for HE PPDUs, the value of the Length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0101] The data field may include a SERVICE field, a PSDU (Physical layer Service Data Unit), and PPDU TAIL bits, and may also include padding bits if necessary. Some bits of the SERVICE field may be used for synchronization of the descrambler at the receiver. The PSDU corresponds to a MAC PDU defined at the MAC layer and may contain data generated or used by the upper layer. The PPDU TAIL bits may be used to return the encoder to a 0 state. Padding bits may be used to adjust the length of the data field to a predetermined unit.

[0102] A MAC PDU is 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 a MAC PDU and can be transmitted or received through the PSDU of the data portion in the PPDU format.

[0103] The MAC header includes a Frame Control field, a Duration / ID field, an Address field, etc. The Frame Control field may contain control information necessary for transmitting or receiving frames. The Duration / ID field may be set as the time for transmitting the corresponding frame. Address subfields may indicate the frame's receiver address, transmitter address, destination address, and source address, and some address subfields may be omitted. Specific details regarding each subfield of the MAC header, including Sequence Control, QoS Control, and HT Control subfields, can be found in the IEEE 802.11 standard document.

[0104] The Null-Data PPDU (NDP) format refers to a PPDU format that does not include a data field. In other words, NDP is a frame format that includes the PPDU preamble (i.e., L-STF, L-LTF, L-SIG fields, and additionally, non-legacy SIG, non-legacy STF, and non-legacy LTF if present) from a standard PPDU format, but excludes the remaining parts (i.e., the data field).

[0105] FIG. 7 is a drawing illustrating examples of PPDUs defined in the IEEE 802.11 standard to which the present disclosure may be applied.

[0106] Various forms of PPDU have been used in standards such as IEEE 802.11a / g / n / ac / ax. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and Data fields. The basic PPDU format may also be referred to as the non-HT PPDU format (Fig. 7(a)).

[0107] 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 the HT-mixed format. Additionally, an HT-greenfield format PPDU may be defined, which corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a Data field, without including L-STF, L-LTF, and L-SIG (not shown).

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

[0109] An example of the HE PPDU format (IEEE 802.11ax) includes the 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 the 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 multiple users (MU), but is not included in the HE PPDU format for single users (SU). Additionally, the HE trigger-based (TB) PPDU format does not include HE-SIG-B, and the length of the HE-STF field may vary to 8 µs. 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 16 µs. For example, RL-SIG can be configured identically to L-SIG. Based on the presence of RL-SIG, the receiving STA can determine that the received PPDU is a HE PPDU or the EHT PPDU described later.

[0110] The EHT PPDU format may include the EHT MU (multi-user) 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 RL-SIG following L-SIG, but it may include U (universal)-SIG, EHT-SIG, EHT-STF, and EHT-LTF following RL-SIG.

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

[0112] The EHT-SIG is omitted in the EHT TB PPDU of FIG. 7(f) compared to the EHT MU PPDU. A STA that receives 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.

[0113] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG (Universal SIGNAL), and EHT-SIG fields can be encoded and modulated so that demodulation and decoding can be attempted even on legacy STAs, and mapped based on a defined 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 so that they can be demodulated and decoded by a STA that has successfully decoded a non-legacy SIG (e.g., U-SIG and / or EHT-SIG) to obtain the information contained in the corresponding fields, and mapped based on a defined subcarrier frequency interval (e.g., 78.125 kHz). These can be referred to as EHT modulated fields.

[0114] Similarly, in the HE PPDU format, the L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A, and HE-SIG-B fields can be referred to as pre-HE modulation fields, and the HE-STF, HE-LTF, Data, and PE fields can be referred to as HE modulation fields. Also, in the VHT PPDU format, the L-STF, L-LTF, L-SIG, and VHT-SIG-A fields can be referred to as pre-VHT modulation fields, and the VHT STF, VHT-LTF, VHT-SIG-B, and Data fields can be referred to as VHT modulation fields.

[0115] The U-SIG included in the EHT PPDU format of FIG. 7 can be constructed based on, for example, two symbols (e.g., two consecutive OFDM symbols). Each symbol for the U-SIG (e.g., OFDM symbol) can have a duration of 4 µs, and the U-SIG can have a total duration of 8 µs. 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.

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

[0117] For example, A number of uncoded bits may be transmitted through U-SIG, and the first symbol of U-SIG (e.g., U-SIG-1 symbol) transmits the first X bits of the total A bit information, and the second symbol of U-SIG (e.g., U-SIG-2 symbol) transmits the remaining Y bits of the total A bit information. The A bit information (e.g., 52 uncoded bits) may include a CRC field (e.g., a field of 4 bits) and a tail field (e.g., a field of 6 bits). The tail field may be used to terminate the trellis of the convolution decoder and may be set to, for example, 0.

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

[0119] For example, the size of the version-independent bits of U-SIG may be fixed or variable. The version-independent bits may be assigned only to U-SIG-1 symbols or to both U-SIG-1 and U-SIG-2 symbols. The version-independent bits and version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

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

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

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

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

[0124] Preamble puncturing may refer to the transmission of a PPDU in which a signal is not present in one or more frequency units within the PPDU bandwidth. For example, the size of the frequency unit (or the resolution of preamble puncturing) may be defined as 20 MHz, 40 MHz, etc. For example, preamble puncturing may be applied to a PPDU bandwidth of a predetermined size or larger.

[0125] 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. A non-legacy SIG may be transmitted through at least one symbol, and one symbol may have a length of 4 µs. Information regarding the number of symbols used for EHT-SIG may be included in the previous SIG (e.g., HE-SIG-A, U-SIG, etc.).

[0126] Non-legacy SIGs, such as HE-SIG-B and EHT-SIG, may include common fields and user-specific fields. Common fields and user-specific fields may be coded individually.

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

[0128] 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 may be related to MU-MIMO allocation or non-MU-MIMO allocation.

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

[0130] An RU may include multiple subcarriers (or tones). An RU may be used when transmitting signals to multiple STAs based on the OFDMA technique. Additionally, an RU may be defined when transmitting signals to a single STA. Resources may be allocated on an RU basis for non-legacy STF, non-legacy LTF, and Data fields.

[0131] Applicable RU sizes can be defined according to the PPDU bandwidth. RUs 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 80 MHz PPDU, the RU placement for HE PPDU and EHT PPDU may differ. The applicable RU sizes, number of RUs, RU locations, DC (direct current) subcarrier locations and numbers, null subcarrier locations and numbers, and guard subcarrier locations and numbers for each PPDU bandwidth can be referred to as a tone-plan. For example, a tone-plan for a wide bandwidth may be defined as a multiple repetition of a tone-plan for a low bandwidth.

[0132] RUs of various sizes can be defined as 26-ton RUs, 52-ton RUs, 106-ton RUs, 242-ton RUs, 484-ton RUs, 996-ton RUs, 2x996-ton RUs, 4x996-ton RUs, etc. An MRU (multiple RU) is distinguished from multiple individual RUs and corresponds to a group of subcarriers composed 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. In addition, multiple RUs constituting a single MRU may be continuous or non-continuous in the frequency domain.

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

[0134] The names of the respective fields in the PPDU formats of FIG. 7 are exemplary and the scope of the present disclosure is not limited by such names. Furthermore, the examples of the present disclosure may be applied not only to the PPDU formats exemplified in FIG. 7, but also to new PPDU formats based on the PPDU formats of FIG. 7 in which some fields are excluded and / or some fields are added.

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

[0136] A trigger frame may allocate resources for one or more TB PPDU transmissions and request TB PPDU transmissions. The trigger frame may also include other information required by an STA that transmits a TB PPDU in response. The trigger frame may include common info and user info list fields in the frame body.

[0137] The common information field may include information commonly applicable to one or more TB PPDU transmissions requested by a trigger frame, such as trigger type, UL length, whether a subsequent trigger frame exists (e.g., More TF), whether a CS (channel sensing) is required, UL BW (bandwidth), etc. FIG. 8 illustrates an exemplary format for the common information field of an EHT variant.

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

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

[0140] 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 contains extended common information not provided in the common information field.

[0141] The user information list contains zero or more user info fields. Figure 8 illustrates an exemplary EHT variant user info field format.

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

[0143] The RU allocation subfield can indicate the size and location of the RU / MRU. To this end, the RU allocation subfield may 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.

[0144] For example, as shown in Table 1 below, the mapping of B7-B1 of the RU allocation subfield can be defined along with the settings of B0 and PS160 of the RU allocation subfield. Table 1 shows an example of the encoding of the PS160 subfield and the RU allocation subfield of the EHT variant user information field.

[0145]

[0146]

[0147]

[0148] If B0 of the RU allocation subfield is set to 0, it indicates that the RU / MRU allocation is applied to the primary 80MHz channel, and if the value is set to 1, it indicates that the RU allocation is applied to the secondary 80MHz channel of the primary 160MHz. If B0 of the RU allocation subfield is set to 0, it indicates that the RU / MRU allocation is applied to the lower 80MHz of the secondary 160MHz, and if the value is set to 1, it indicates that the RU allocation is applied to the upper 80MHz of the secondary 160MHz.

[0149] In the trigger frame RU allocation table of Table 1, the parameter N can be calculated based on the formula N=2*X1+X0. For bandwidths of 80 MHz or less, the values ​​of PS160, B0, X0, and X1 can be set to 0. For 160 MHz and 320 MHz bandwidths, the values ​​of PS160, B0, X0, and X1 can be set as shown in Table 2. These settings represent the absolute frequency order for the primary and secondary 80 MHz and 160 MHz channels. The order from left to right indicates the order from lowest to highest frequency. The primary 80 MHz channel is designated as P80, the secondary 80 MHz channel as S80, and the secondary 160 MHz channel as S160.

[0150]

[0151] Transmission or reception of operation mode enable information

[0152] Support for various operation modes, including IDC (e.g., DUO (dynamic unavailability operation) or PUO (periodic unavailability operation)), is being discussed. For example, various operation modes (or mechanisms) to prevent unnecessary media access and performance degradation in IDC situations are being discussed. These IDC operation modes (or simply IDC modes) can be broadly classified into periodic IDC and non-periodic IDC.

[0153] When IDC events occur periodically in an STA, periodic interval information for the IDC events (e.g., IDC TWT SP (target wake time service period)) can be set so that the STA can inform the AP that the period is an unavailability period according to the IDC. An STA that generates periodic IDC events can share / set parameters such as an unavailability period of a predetermined duration and an interval between unavailability periods through IDC TWT request frames and IDC TWT response frames with the AP.

[0154] If an IDC event occurs non-periodically in the STA, information about it can be transmitted to the AP. The STA that detects a future IDC event can send a multi-STA block ACK (M-BA) frame in response to a BSRP trigger frame from the AP, and can report the unavailability period through the presence field of IDC information, the IDC information field, the BSR information field, etc. within the M-BA frame.

[0155] These examples of periodic / non-periodic IDC modes between non-AP STAs and APs can be applied in a similar manner when IDC events occur between non-AP STAs and APs, between APs and APs, and between non-AP STAs and non-AP STAs.

[0156] The above IDC mode may not need to be applied to devices equipped solely with Wi-Fi (e.g., Wi-Fi-only access points, Wi-Fi-only devices). For instance, such IDC mode may be applied only to devices where an IDC situation may occur (e.g., smartphones, IoT gateways equipped with Wi-Fi and non-wireless technologies, sensors equipped with Wi-Fi and Bluetooth, etc.). Therefore, processes such as capability negotiation or notification regarding support for IDC mode may be required. Furthermore, even among devices that support it, a procedure may be required to dynamically enable / disable this mode depending on the situation (e.g., enabling / disabling IDC mode based on whether Bluetooth is turned on / off and operating in conjunction with Wi-Fi on a smartphone). Based on whether IDC mode is enabled, the STA may solicit predicted IDC information to peer STAs. Based on the solicited information, peer STAs may report IDC information. Furthermore, it may be required that specific parameters when this mode is in operation (e.g., maximum PPDU duration, maximum MCS, whether LDPC is used, HT-immediate BA (BlockAck), Tx / Rx parameters such as disabled subchannel bitmaps) be dynamically updated.

[0157] This disclosure describes various examples of capability declarations, enable / disable procedures, etc., for specific operation modes in systems that support various operation modes, such as IDC.

[0158] In the various examples of the present disclosure described below, the sender of the request (e.g., the first STA) may be a non-AP STA or an AP. Additionally, the receiver of the request (e.g., the second STA) may be an AP or a non-AP STA. Furthermore, the exchange of frames between the first STA and the second STA may be performed between AP and AP, or between a non-AP STA and AP, or between an AP and a non-AP STA, or between a non-AP STA and a non-AP STA.

[0159] FIG. 9 is a drawing for explaining an example of the operation of a first STA according to the present disclosure.

[0160] For example, in the examples of FIGS. 9 and 10, the first STA may correspond to a non-AP STA affiliated with a non-AP multi-link device (MLD), and the second STA may correspond to an AP affiliated with an AP MLD. However, this is merely one embodiment, and each of the first STA and the second STA may be either a non-AP STA or an AP.

[0161] The first STA may transmit a request frame containing first information related to enabling or disabling the first operation mode among at least one operation mode to the second STA (S910).

[0162] Here, at least one operation mode may include a DUO (dynamic unavailability operation) mode and / or a PUO (periodic unavailability operation) mode, etc. That is, the first operation mode may be a DUO mode or / and a PUO mode, but is not limited thereto.

[0163] For example, the request frame may be an action request frame or a multi-link operation update request frame associated with a first operation mode. However, this is merely one embodiment, and in FIGS. 9 and 10, the request frame may be a separate beacon frame, a probe request / response frame, or a combined request / response frame. Additionally, capability information associated with at least one operation mode (e.g., information regarding whether at least one operation mode is supported) may be included on the request frame.

[0164] And, the first information may be included in the reconfiguration multi-link element of the request frame (e.g., the STA-per-profile sub-element of the reconfiguration multi-link element).

[0165] Additionally, the first information may include at least one of information related to a request for enabling or disabling the first operation mode, information related to whether the enabling or disabling of the first operation mode is supported, identification information of the first operation mode, or transmission / reception parameters for performing the first operation mode. Information related to a request for enabling or disabling the first operation mode may be set / indicated by an enable / disable subfield of the first operation mode. And, identification information of the first operation mode may be set / indicated by a subfield related to the type of the operation mode.

[0166] For example, a (response) timer may be started from a first time point when a request frame is transmitted, or from a second time point after an inter-frame space (IFS) (e.g., SIFS, PIFS, etc.) from the first time point. The timer may be set / driven by a first STA. The first STA may monitor whether a first response frame is received from a second STA within a certain period of time from the start time of the timer.

[0167] Additionally or alternatively, a timer associated with a specific time may not be used. In this case, the first STA can monitor whether the first response frame is received for a specific time based on the time after the request frame is transmitted and the IFS. As another example, the first STA can monitor whether the first response frame is received during the IFS (e.g., when the specific time is the IFS) based on the time when the request frame is transmitted.

[0168] Based on the fact that the first response frame for the request frame is not received from the second STA within a certain period of time, the first STA may retransmit the request frame (S920).

[0169] That is, if a certain amount of time has elapsed or expired since the timer was activated, the first STA may interpret / consider that the enable / disable request for the first operation mode has failed. Accordingly, the first STA may retransmit (or retry) the request frame.

[0170] However, as described above, the retransmission (or retry) operation may be performed even if the corresponding timer is not used. When a set time has elapsed or expired, the first STA may interpret / consider that the enable / disable request of the first operation mode has failed. Then, the first STA may perform retransmission (or retry) of the request frame.

[0171] And, the first STA may (re)start the timer from a third point in time when the request frame is retransmitted or from a fourth point in time after the IFS from the third point in time. The first STA may monitor whether a response frame of the request frame retransmitted from the second STA is received within a certain period of time from the start of the timer.

[0172] Subsequently, based on the fact that a second response frame for the retransmission of the request frame is not received from the second STA within a certain period of time, the first STA may receive a buffer status report poll (BSRP) trigger frame from the second STA. Subsequently, the first STA may transmit a third response frame for the BSRP trigger frame (e.g., a multi-STA block acknowledgment (BA) frame, etc.) to the second STA, and the third response frame may include second information indicating that the enable or disable of the first operation mode has failed.

[0173] At this time, the second STA is the holder of a transmission opportunity (TXOP), and the first STA may be the responder of the TXOP. Based on the fact that the second STA is the TXOP holder, the first STA may perform retransmission of the request frame after the TXOP. The operation after the retransmission of the request frame may be the same as the method described above.

[0174] In one example of the present disclosure, a timer may be interrupted or reset (by the first STA) based on the reception of a first response frame for a request frame from the second STA within a certain period of time. That is, the timer may be interrupted or reset based on the reception of a first response frame from the second STA within a certain period of time (from the start time of the timer). And, the first STA may proceed with / complete the enable or disable procedure of the first operation mode.

[0175] The method described in the example of FIG. 9 can 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 can transmit a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode to a second STA through one or more transceivers (106). Based on the fact that a first response frame for the request frame is not received from the second STA within a certain time, one or more processors (102) can perform retransmission of the request frame.

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

[0177] FIG. 10 is a drawing for explaining an example of the operation of a second STA according to the present disclosure.

[0178] The second STA can receive a request frame from the first STA containing first information related to enabling or disabling the first operation mode among at least one operation mode (S1010).

[0179] The second STA can confirm that the first STA attempts to enable or disable the first operation mode upon receiving the request frame. Accordingly, the second STA can generate a first response frame for the request frame (S1020). The first response frame may include information indicating approval or rejection of the enable or disable of the first operation mode.

[0180] Additionally, the second STA may perform a procedure to transmit a first response frame to the request frame to the first STA. However, the first response frame of the second STA may not be successfully transmitted to the first STA due to specific reasons (e.g., network instability). Based on the fact that the first response frame to the request frame is not successfully transmitted to the first STA within a certain period of time, the second STA may receive the request frame again from the first STA. Since the procedure for retransmitting the request frame has been explained with reference to FIG. 9, a redundant explanation will be omitted.

[0181] The method described in the example of FIG. 10 can be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may receive a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode from the first STA through one or more transceivers (206). One or more processors (202) may transmit a first response frame for the request frame to the first STA through one or more transceivers (206).

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

[0183] The examples of FIGS. 9 and 10 may correspond to some of the various examples of the present disclosure. Hereinafter, various examples of the present disclosure including the examples of FIGS. 9 and 10 will be described in more detail.

[0184] Devices supporting a specific operating mode may undergo the following process in advance to prepare for the application of that operating mode among the devices. This process can be broadly divided into three stages: capability negotiation and / or notification, enabling / disabling a specific operating mode, and negotiation and / or notification of parameters related to the specific operating mode.

[0185] In the following examples, IDC (e.g., DUO or PUO) operation modes are described as representative examples, but the examples of the present disclosure can be applied equally to other operation modes.

[0186] Example 1

[0187] This embodiment relates to capacity consultation / notification.

[0188] APs and non-AP STAs may mutually announce whether they support IDC mode, and during the association process, a process of mutual negotiation and / or notification regarding support may be performed. To this end, information regarding IDC mode support may be included in beacon frames, probe request / response frames, (re)association request / response frames, etc.

[0189] For example, information regarding whether IDC mode is supported can be indicated through 1-bit information. For example, if the value is 0, it may indicate that IDC mode is not supported, and if the value is 1, it may indicate that IDC mode is supported. Alternatively, if the value is 1, it may indicate that IDC mode is not supported, and if the value is 0, it may indicate that IDC mode is supported.

[0190] For example, information regarding whether IDC mode is supported can be indicated through 1-bit information. For example, if the value is 0, it may indicate that IDC mode is not supported, and if the value is 1, it may indicate that IDC mode is supported. Alternatively, if the value is 1, it may indicate that IDC mode is not supported, and if the value is 0, it may indicate that IDC mode is supported.

[0191] Information regarding the support or non-support of such IDC modes (or detailed modes such as DUO or PUO) may be indicated through capability information, through reserved areas of extended capability elements, and / or through UHR capability elements. Additionally or alternatively, information regarding the support or non-support of IDC / DUO / PUO may be indicated by utilizing reserved areas such as HT capability elements, VHT capability elements, HE capability elements, EHT capability elements, etc.

[0192] For example, it may be possible to include information regarding whether IDC mode is supported or not by adding a new field (e.g., UHR capability field) within the extended capability element. This new field may be defined by utilizing the reserved area within the extended capability element (e.g., if the start bit is 0, the bit(s) from 4th to 6th, 35th, 41st to 43rd, and 101st onwards).

[0193] When UHR capability elements are defined, information regarding the support of one or more operation modes may be included according to various methods described below.

[0194] FIG. 11 shows examples of UHR capability elements according to the present disclosure.

[0195] As shown in the example of FIG. 11(a), UHR capability elements may include an element ID, length, element ID extension, MAC capability information, PHY capability information, a set of supported modulation and coding schemes (MCS) and numbers of spatial streams (Nss), and a PHY packet extension (PPE) threshold field. For example, information indicating whether IDC mode is supported may be included in the MAC capability information field.

[0196] As shown in the example of FIG. 11(a), UHR capability elements may include an element ID, length, element ID extension, MAC capability information, PHY capability information, a set of supported modulation and coding schemes (MCS) and numbers of spatial streams (Nss), and a PHY packet extension (PPE) threshold field. For example, information indicating whether IDC mode is supported may be included in the MAC capability information field.

[0197] As shown in the example of FIG. 11(b), the UHR capability element may further include a UHR feature field. The UHR feature field may include information indicating whether the IDC mode (and other operation mode(s)) is supported.

[0198] Information / fields / (sub)elements regarding whether a device supports IDC mode may be transmitted / received through various frames. Information / fields / (sub)elements regarding whether an AP supports IDC mode may be included in beacon frames, probe response frames, (re)join response frames, etc. Information / fields / (sub)elements regarding whether a Non-AP STA supports IDC mode may be included in probe request frames, (re)join request frames, etc.

[0199] Example 2

[0200] This embodiment relates to IDC mode enable / disable.

[0201] IDC mode enable / disable may mean enabling / disable IDC mode after an AP (supporting IDC mode) and a non-AP STA are combined.

[0202] The mutual IDC mode enable / disable between an AP and a non-AP STA can be performed through the following coupling level signaling. For example, information indicating the enable / disable of IDC mode may be included within beacon frames, probe request / response frames, and (re)coupling request / response frames. Information indicating the enable / disable of IDC mode may be included in various frames, similar to the example in the aforementioned capability consultation / notification where capability information is included in various frames.

[0203] Alternatively, enabling / disabling IDC mode between AP and non-AP STA may be performed through management level signaling.

[0204] Additionally or alternatively, the IDC mode enable / disable between the AP and the non-AP STA may be performed together with or independently of the general operation mode enable / disable. For example, information for enabling / disable various modes such as IDC, DPS (dynamic power saving), DSO (dynamic sub-band operation), and NPCA (non-primary channel access) simultaneously and / or individually may be defined and signaled.

[0205] Example 2-1

[0206] This embodiment relates to a method for signaling information related to IDC mode enable / disable through a public action frame.

[0207] AP (or AP affiliated with AP MLD) and / or non-AP STA (or STA affiliated with non-AP MLD) may each indicate their IDC mode enable or disable through a public action frame.

[0208] For example, a new UHR frame (e.g., (UHR) IDC Management Frame) may be defined for enabling / disabling IDC mode. The scope of this disclosure is not limited to the designation (UHR) IDC Management Frame and may be defined by a general designation not limited to a specific mode of operation, such as (UHR) Feature Management Frame.

[0209] (UHR) The IDC management frame may include a category field, a public action field, and an IDC operation mode element field in that order. For example, the public action field may be set to one of the reserved values ​​(e.g., 54-59, 61-255) (e.g., 54). The IDC operation mode element may also be defined by a general name that is not restricted to a specific operation mode, such as the UHR operation mode element / field.

[0210] An STA transmitting an IDC management frame can indicate the IDC mode enable by setting the value of the IDC enable subfield within the IDC operation mode element to 1 (or 0), and indicate the IDC mode disable by setting the value to 0 (or 1).

[0211] Example 2-1-1

[0212] A STA that receives an IDC management frame in which the IDC enable subfield of the IDC operation mode element is set to enable can recognize this as a notification from a peer STA and consider the IDC mode to be enabled.

[0213] Additionally or alternatively, an STA that receives an IDC mode management frame in which the IDC enable subfield of an IDC operation mode element is set to enable can perform an acceptance response procedure for the IDC mechanism enable by transmitting an IDC mode management frame in which the IDC enable subfield of an IDC operation mode element is also set to enable.

[0214] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that an acceptance response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or a timeout interval) has passed or expired without a response to the management frame.

[0215] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that a reject response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or timeout interval) has passed or expired without a response to the management frame.

[0216] Example 2-1-2

[0217] A STA that receives an IDC management frame in which the IDC enable subfield of the IDC operation mode element is set to disable may recognize this as a notification from the other STA and consider the IDC mode to be disabled. In this case, the STA that receives the IDC management frame may respond to the IDC mode disable by transmitting an IDC management frame in which the IDC enable subfield of the IDC operation mode element is set to disable.

[0218] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that a reject response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or a timeout interval) has passed or expired without a response to the management frame.

[0219] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that an accept response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or timeout interval) has passed or expired without a response to the management frame.

[0220] Example 2-1-3

[0221] A STA transmitting an IDC mode management frame in which the IDC enable subfield of the IDC operation mode element is set to enable may transmit it with a recommendation field (e.g., a 1-bit instruction) added to prevent rejection by the other STA. For example, a STA receiving an IDC mode management frame in which the recommendation field is set to 1 may be in a state where acceptance is requested. Unless there is a specific situation (e.g., a state in which the IDC mode cannot be enabled due to internal resource constraints or scheduling limitations), the STA receiving the frame may accept it according to the recommendation.

[0222] These IDC operation mode elements are not limited to specific operation modes and may be referred to as operation modes with general names (e.g., UHR operation mode elements).

[0223] When the aforementioned IDC mode management frame is used for notification, the STA that sent the frame may not have a way to verify whether the other STA has successfully received the frame and enabled IDC mode. Alternatively, even if verification of IDC mode enable is not required, the frame may be used for general notification purposes along with other features without being limited to IDC mode. Accordingly, a request type may be added to the IDC mode management frame, and an exchange method between the request frame and the response frame may be applied.

[0224] For example, the IDC operation mode element can be set to have an element ID value of 255, an element ID extension value of 117, extensible as Yes, and fragmentable as No.

[0225] FIG. 13 shows examples of elements and fields related to the IDC operation mode according to the present disclosure.

[0226] FIG. 13(a) shows an example of an IDC operation mode element. The element may be defined as an independent control field and replaced, or may be included in a public action frame and / or an action frame.

[0227] For the IDC operation mode element, instead of using a combination of the element ID value of 255 and a specific value of the element ID extension, a reserved value of the element ID (e.g., one of 245-254) may be used without using the element ID extension.

[0228] FIG. 13(b) shows an exemplary format of an IDC operation mode field (or IDC operation mode control field) within an IDC operation mode element.

[0229] The IDC mode request type field may indicate a request if its value is 0 (or 1), and a response if its value is 1 (or 0).

[0230] The IDC enable field may indicate IDC mode enable when its value is set to 1 (or 0), and IDC mode disable when its value is set to 0 (or 1).

[0231] The status field may be defined, for example, with a size of 2 octets. Additionally, or alternatively, some or all of the reserved bits may be used as the status field. The size of the status field may be determined by the range of values ​​the status field can have. For example, various states may be defined, such as the result of enabling / disabling IDC mode (e.g., success or failure), failure of the response for error handling when the counterparty STA that received the request does not receive an ACK for the response (e.g., FAIL_TO_RESPONSE, or request received but response failed).

[0232] For example, the status field may be defined with a size of 1 bit. If the IDC mode request type indicates a response, the value of the status field may indicate rejection if it is 0 (or 1) and acceptance if it is 1 (or 0).

[0233] Alternatively, the status field may be indicated by a bitmap. Each bit position of the bitmap may correspond to a different feature / function, such as IDC, DPS, DSO, and NDPCA. A value of 0 at a corresponding bit position may indicate rejection, and a value of 1 may indicate acceptance. For example, if the value of the status bitmap is 10100000b, it may indicate acceptance of the enable of IDC and DSO. Alternatively, a value of 1 at a corresponding bit position may indicate rejection, and a value of 0 may indicate acceptance.

[0234] In the aforementioned examples, the names of information / (sub)fields / (sub)elements / frames related to the IDC may be defined as information / (sub)fields / (sub)elements / frames with general names that are not restricted to a specific operation mode.

[0235] FIG. 13(c) shows an example in which an IDC operation mode control field includes an operation mode request field and an operation mode response field to support requests and responses for one or more operation modes (or features / functions).

[0236] Each bit position of the operation mode request (or feature request) field may correspond to each of one or more operation modes (or features), such as IDC, DPS, DSO, and NPCA. If the value of the corresponding bit position is 1 (or 0), it may indicate that the corresponding operation mode (or feature) is requested, and if the value is 0 (or 1), it may indicate that the corresponding operation mode (or feature) is not requested.

[0237] When only one operation mode is specified without specifying multiple operation modes, the operation mode request field may be defined as a 1-bit indicator. When one or more of multiple operation modes are specified, the operation mode request field may be defined as a bitmap. For example, if the value of the operation mode request field is 10100000b, it may be indicated to request the enable of IDC and DSO.

[0238] Each bit position of the operation mode response (or feature response) field may correspond to each of one or more operation modes (or features), such as IDC, DPS, DSO, and NPCA. If the value of the corresponding bit position is 1 (or 0), it may indicate acceptance of the corresponding operation mode (or feature), and if the value is 0 (or 1), it may indicate rejection of the corresponding operation mode (or feature).

[0239] When only one operation mode is indicated without indicating multiple operation modes, the operation mode response field may be defined as a 1-bit indicator. When one or more of multiple operation modes are indicated, the operation mode response field may be defined as a bitmap. For example, if the value of the operation mode response field is 10100000b, it may be indicated that the IDC and DSO enable are accepted.

[0240] The UHR IDC management frame can be defined as being distinguished into an IDC operation mode request frame and an IDC operation mode response frame. For example, the order value 54 of the public action frame can be defined as corresponding to the IDC operation mode request frame, and the order value 55 as corresponding to the IDC operation mode response frame. In this case, negotiation of IDC operation parameters between STAs (e.g., AP and AP, AP and non-AP STA, non-AP STA and non-AP STA) can be performed through the IDC operation mode request frame and the IDC operation mode response frame.

[0241] Both the IDC mode request frame and the IDC mode response frame may equally include a category field, a public action field, and an IDC operation mode element field in that order. For example, the IDC operation mode element may have a format such as the example in FIG. 13(a).

[0242] UHR IDC mode enable / disable information may be included in the IDC operation mode element. When negotiation is performed in the form of IDC mode request frames and IDC mode response frames, a status code field may be included in the IDC operation mode.

[0243] FIG. 13(d) shows another example of an IDC operation mode field (or IDC operation mode control field).

[0244] For IDC mode response frames, a status field may be included to indicate acceptance or rejection of the IDC mode request frame. The status field can be set to indicate one of several states, such as success or denied operation parameter update.

[0245] Alternatively, the status field may indicate one of various states, such as the result of enabling / disabling the IDC mode (e.g., success or failure), failure of the response for error handling when the counterparty STA that received the request does not receive an ACK for the response (e.g., FAIL_TO_RESPONSE, or request received but response not successful).

[0246] As an example of the present disclosure, the above-described UHR IDC management frame may be configured in various ways for capability negotiation and configuration between devices. In one embodiment, it may be configured to transmit signaling information proposed in the present disclosure by utilizing at least one of the IDC mode field, capability information field, or reserve area of ​​extended capability elements within the UHR IDC management frame. Additionally or alternatively, a UHR Capabilities element to support the operation of the present disclosure may be newly defined and included in the frame.

[0247] In addition, considering compatibility or scalability with the specifications of a basic wireless LAN system, it is also possible to indicate the above-described information by utilizing at least one reserved area among the HT capability element, VHT capability element, HE capability element, or EHT capability element.

[0248] Example 2-1-4

[0249] Example 2-1-4 relates to a method for handling errors that may occur when an IDC-related procedure / mode is enabled or disabled through a public action frame. However, this is merely one example, and the description of Example 2-1-4 may be extended to apply not only to public action frames but also to protection action frames. That is, "public action frame" may be replaced or applied as "protection action frame," etc., below.

[0250] Specifically, if an STA that has transmitted an IDC mode management frame does not receive an ACK or response regarding the IDC mode management frame from a peer STA, the STA may not be able to determine whether the peer STA has enabled the IDC-related procedures / modes / mechanisms. Consequently, operations based on the IDC enable status may not be performed. To handle this situation, at least one of the methods described below may be performed. Additionally, at least one of the methods may be equally applied to the error handling procedure when disabling IDC-related procedures / modes / mechanisms.

[0251] Method 1

[0252] As an example of the present disclosure, if a specific STA that has transmitted an IDC mode management frame (as a request frame) fails to receive a response to the said IDC mode management frame and a set time (e.g., a response timer) passes or expires, the specific STA may consider that the enable of the IDC-related procedure / mode / mechanism has failed.

[0253] For example, the STA may transmit an IDC mode management frame and set / start the timer, or transmit an IDC mode management frame and set / start the timer after a certain period of time (e.g., an IFS such as SIFS, PIFS, etc.). Additionally, a specific STA may perform at least one of the operations described below:

[0254] - i) Additionally or alternatively, when the above timer expires, a specific STA may retransmit an IDC mode management frame to retry enabling the IDC-related procedures / modes / mechanisms.

[0255] - ii) Additionally or alternatively, when a neighboring STA transmits a BSRP (trigger) frame as an ICF for acquiring a TXOP, a specific STA may transmit information to the neighboring STA indicating that the enable of an IDC-related procedure / mode / mechanism has failed. In this case, the information transmitted by the specific STA may be included in a multi-STA BA frame that can be an ICR.

[0256] - iii) Additionally or alternatively, in conjunction with (and / or independently of) the procedure ii) above, if a specific STA that has received a BSRP trigger frame indicates to a neighboring STA that the enable of an IDC procedure / mode / mechanism has failed (and / or that the IDC procedure / mode / mechanism has not been enabled) through a multi-STA BA frame, a retry of the enable of the IDC procedure / mode / mechanism may be possible as needed.

[0257] - iv) Additionally or alternatively, the IDC mode management frame may include information related to the response timer. Information related to the response timer may be defined using microseconds and / or a full timestamp (TSF) (e.g., 8 octets) or a partial TSF. Additionally, a partial TSF may be indicated using some bits of the 64 bits of the TSF (e.g., [10:25], [20:35], the first 4 octets). Information related to the response timer may be passed to a neighboring STA. Accordingly, the neighboring STA can identify that the IDC enable / disable procedure has failed as the response timer has expired based on the information related to the response timer.

[0258] Method 2

[0259] As an example of the present disclosure, if a specific STA that has transmitted an IDC mode management frame (as a response frame) fails to receive a response (e.g., ACK) to the said IDC mode management frame and a set time (e.g., ACK timer) passes or expires, the specific STA may consider that the enable of an IDC-related procedure / mode / mechanism has failed.

[0260] For example, the STA may transmit an IDC mode management frame and set / start the timer, or transmit an IDC mode management frame and set / start the timer after a certain period of time (e.g., an IFS such as SIFS, PIFS, etc.). Additionally, a specific STA may perform at least one of the operations described below:

[0261] - i) Additionally or alternatively, the STA may attempt to complete the IDC enable procedure by retransmitting the IDC mode management frame response.

[0262] - ii) Additionally or alternatively, when the STA transmits a BSRP (trigger) frame as an ICF to acquire a TXOP, it may include information in the BSRP (trigger) frame indicating that an IDC-related procedure / mode / mechanism has failed. Information indicating that an IDC-related procedure / mode / mechanism has failed may be indicated by an AID12 subfield within the user information field of the BSRP (trigger) frame (e.g., an AID12 subfield set to a specific value such as 2008). However, this is merely one example, and the failure of an IDC-related procedure / mode / mechanism may be indicated through various information / fields.

[0263] - iii) An STA that receives information indicating that an IDC-related procedure / mode / mechanism has failed via a BSRP (trigger) frame can retry enabling the IDC-related procedure / mode / mechanism by retransmitting an IDC mode management frame request at a specific time.

[0264] Method 3

[0265] In one example of the present disclosure, an STA transmitting an IDC mode management frame (as a request frame) may receive a response frame from a neighboring STA with the status code set to failure. At this time, the STA may perform at least one of the operations described below:

[0266] - i) If the enable of an IDC-related procedure / mode / mechanism fails, the STA may not perform the IDC-related procedure / mode / mechanism. Additionally or alternatively, if the disable of an IDC-related procedure / mode / mechanism fails, the STA may recognize that the IDC-related procedure / mode / mechanism is enabled and perform the relevant operation.

[0267] - ii) Additionally or alternatively, the STA may recognize that the enable (and / or disable) of an IDC-related procedure / mode / mechanism has failed and may re-perform the enable procedure for the IDC-related procedure / mode / mechanism.

[0268] Example 2-2

[0269] This embodiment relates to a method for signaling information related to IDC mode enable / disable through a new action frame (e.g., an IDC operation mode action frame).

[0270] These new UHR action frames may include a category field and an action details field. One of the reserved values ​​of the category field (e.g., 33, 38-125) may be used for the new UHR action frame. As a non-limiting example, it is assumed that when the value of the category field is 38, it is an IDC operation mode action frame.

[0271] The value of the action field of the IDC operation mode action frame can be set to, for example, 0. In this case, the value of the action field 1-255 is assumed to be reserved. Accordingly, IDC operation parameter information can be transmitted to the other device unsolicitedly.

[0272] A new IDC operation mode frame may be defined for IDC mode enable / disable. This new IDC operation mode frame may include a category field, an IDC operation mode field, and an IDC operation mode element in that order. The IDC operation mode field may also include an IDC operation mode element as described below.

[0273] An STA transmitting an IDC operation mode frame can indicate the IDC mode enable by setting the value of the IDC enable subfield within the IDC operation mode element to 1 (or 0), and indicate the IDC mode disable by setting the value to 0 (or 1).

[0274] Example 2-2-1

[0275] As an example of the present disclosure, an STA that receives an IDC operation mode frame in which the IDC enable subfield value of an element of an IDC operation mode is set to enable can transmit an IDC operation mode frame in which the IDC enable subfield value of an element of an IDC operation mode is set to enable, thereby performing a response to the enable of an IDC mode / procedure / mechanism.

[0276] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that an acceptance response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or a timeout interval) has passed or expired without a response to the management frame.

[0277] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that a reject response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or timeout interval) has passed or expired without a response to the management frame.

[0278] Example 2-2-2

[0279] Additionally or alternatively, an STA that receives an IDC operation mode frame in which the IDC enable subfield value of the IDC operation mode is set to enable may also transmit an IDC operation mode frame in which the IDC enable subfield of the IDC operation mode element is set to disable to indicate the disable of the IDC mode / procedure / mechanism.

[0280] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that an acceptance response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or a timeout interval) has passed or expired without a response to the management frame.

[0281] Additionally or alternatively, the STA that transmitted the IDC management frame may operate by assuming that a reject response for the operation mode has been implicitly signaled when a set time (e.g., a response timer or timeout interval) has passed or expired without a response to the management frame.

[0282] Example 2-2-3

[0283] A STA transmitting an IDC operation mode action frame in which the IDC enable subfield of the IDC operation mode element is set to enable may transmit it by adding a recommendation field (e.g., a 1-bit instruction) to prevent rejection by the other STA. For example, a STA receiving an IDC operation mode action frame in which the recommendation field is set to 1 may be in a state where acceptance is requested. Unless there is a specific situation (e.g., a state in which the IDC mode cannot be enabled due to internal resource constraints or scheduling limitations of the STA), the STA receiving the frame may accept it according to the recommendation.

[0284] When the aforementioned IDC operation mode action frame is used for notification, the STA that transmitted the frame may not have a way to verify whether the other STA has successfully received the frame and enabled the IDC mode. Accordingly, a request type may be added to the IDC operation mode action frame, and a method of exchanging request frames and response frames may be applied.

[0285] In the aforementioned Example 2-1-3, the example of the IDC operation mode element in FIG. 13(a) and the example of the IDC operation mode field (or IDC operation mode control field) in FIG. 13(b) are applied equally to this embodiment, so a redundant description is omitted.

[0286] The IDC operation mode action frame can be defined by distinguishing between the IDC operation mode request action frame and the IDC operation mode response action frame. In this case, negotiation of IDC operation parameters between STAs (e.g., AP and AP, AP and non-AP STA, non-AP STA and non-AP STA) can be performed through the IDC operation mode request action frame and the IDC operation mode response action frame.

[0287] For example, if the value of the action field of the IDC operation mode action frame is 0, it corresponds to an IDC operation mode request action frame, and if the value of the action field of the IDC operation mode action frame is 1, it corresponds to an IDC operation mode response action frame. In this case, the value of the action field 2-255 may be reserved.

[0288] For example, an IDC operation mode request action frame may include a category field, an IDC operation mode request field, and an IDC operation mode element field in that order.

[0289] For example, an IDC operation mode response frame may include a category field, an IDC operation mode response field, and a status code field in that order. The status code field can be set to indicate one of several states, such as success or denied operation parameter update.

[0290] The IDC operation mode field may include UHR IDC mode enable / disable information.

[0291] In this embodiment, the IDC operation mode field may be defined in the same way as the example in Example 2-1.

[0292] FIG. 14 shows an example of IDC mode enable using an action frame according to the present disclosure.

[0293] In the example of FIG. 14, the STA may transmit an action frame containing information indicating IDC mode enable to the AP. This may correspond to the STA's notification regarding IDC mode enable. Accordingly, the AP may petition the STA for information related to the IDC through a BSRP trigger frame initiating a TXOP, and in response, the STA may notify the AP of the IDC information through a multi-STA block ACK (M-BA) frame. Accordingly, frame exchange may be performed within the AP's TXOP, taking into account the STA's unavailability.

[0294] FIG. 15 shows an example of an IDC mode enable using action frame-based requests and responses according to the present disclosure.

[0295] The example in FIG. 15 illustrates the case of a request by the STA and a response by the AP. For example, the STA sends an action frame request to the AP containing information indicating IDC mode enable, and if the AP can accept IDC mode enable, it sends an action frame response to the STA containing status code information indicating success. Since the operation after IDC mode enable is the same as the example in FIG. 14, a redundant description is omitted.

[0296] FIG. 16 shows another example of an IDC mode enable using action frame-based requests and responses according to the present disclosure.

[0297] The example in FIG. 16 illustrates a case involving a request by the AP and a response by the STA. For instance, the AP sends an action frame request to the STA containing information indicating IDC mode enable, and the STA sends an action frame response to the STA containing status code information indicating success if IDC mode enable can be accepted. Accordingly, the AP can predict that there will be an IDC event from the STA. Since the operation after IDC mode enable is the same as the example in FIG. 14, a redundant description is omitted.

[0298] In the examples above, if the IDC mode is not enabled (or disabled) through the action frame request / response, a petition for IDC information may not be included in the trigger frame, such as BSRP.

[0299] Example 2-2-4

[0300] In one embodiment of the present disclosure, if a STA that has transmitted an IDC operation mode action frame (or an IDC operation mode request frame) does not receive an ACK or response for the frame from a neighboring STA, the STA may not be able to determine whether the neighboring STA has enabled the IDC mechanism. Accordingly, operations based on the IDC enable status may not be performed.

[0301] To handle such situations, at least one of the methods described below may be performed. In addition, at least one of the methods may be equally applied to error handling procedures when disabling IDC-related procedures / modes / mechanisms.

[0302] The following describes a method based on IDC operation mode action frames; however, in the method described below, the IDC operation mode action frames for requests and / or responses can be replaced by IDC operation mode request frames and / or IDC operation mode response frames, respectively. In other words, the method described below can be extended and applied to IDC operation mode request / response frames as well.

[0303] Method 1

[0304] As an example of the present disclosure, if a specific STA that has transmitted an IDC operation mode action frame (as a request frame) fails to receive a response to the said IDC mode action frame and a set time (e.g., a response timer) passes or expires, the specific STA may consider that the enable of the IDC-related procedure / mode / mechanism has failed.

[0305] For example, the STA may transmit an IDC operation mode action frame and set / start the timer, or transmit an IDC operation mode action frame and set / start the timer after a certain period of time (e.g., an IFS such as SIFS, PIFS, etc.). Additionally, a specific STA may perform at least one of the operations described below:

[0306] - i) Additionally or alternatively, when the above timer expires, a specific STA may retransmit an IDC operation mode action frame to retry enabling the IDC-related procedure / mode / mechanism.

[0307] - ii) Additionally or alternatively, when a neighboring STA transmits a BSRP (trigger) frame as an ICF for acquiring a TXOP, a specific STA may transmit information to the neighboring STA indicating that the enable of an IDC-related procedure / mode / mechanism has failed. In this case, the information transmitted by the specific STA may be included in a multi-STA BA frame that can be an ICR.

[0308] - iii) Additionally or alternatively, in conjunction with (and / or independently of) the procedure ii) above, if a specific STA that has received a BSRP trigger frame indicates to a neighboring STA that the enable of an IDC procedure / mode / mechanism has failed (and / or that the IDC procedure / mode / mechanism has not been enabled) through a multi-STA BA frame, a retry of the enable of the IDC procedure / mode / mechanism may be possible as needed.

[0309] - iv) Additionally or alternatively, the IDC operation mode action frame may include information related to the response timer. Information related to the response timer may be defined using microseconds and / or a full timestamp (TSF) (e.g., 8 octets) or a partial TSF. Additionally, a partial TSF may be indicated using some bits of the 64 bits of the TSF (e.g., [10:25], [20:35], the first 4 octets). Information related to the response timer may be passed to a neighboring STA. Accordingly, the neighboring STA can identify that the IDC enable / disable procedure has failed as the response timer has expired based on the information related to the response timer.

[0310] Method 2

[0311] As an example of the present disclosure, if a specific STA that has transmitted an IDC operation mode action frame (as a response frame) fails to receive a response (e.g., ACK) for the said IDC operation mode action frame and a set time (e.g., ACK timer) passes or expires, the specific STA may consider that the enable of the IDC-related procedure / mode / mechanism has failed.

[0312] For example, the STA may transmit an IDC operation mode action frame and set / start the timer, or transmit an IDC operation mode action frame and set / start the timer after a certain period of time (e.g., an IFS such as SIFS, PIFS, etc.). Additionally, a specific STA may perform at least one of the operations described below:

[0313] - i) Additionally or alternatively, the STA may attempt to complete the IDC enable procedure by retransmitting the IDC operation mode action frame response.

[0314] - ii) Additionally or alternatively, when the STA transmits a BSRP (trigger) frame as an ICF to acquire a TXOP, it may include information in the BSRP (trigger) frame indicating that an IDC-related procedure / mode / mechanism has failed. Information indicating that an IDC-related procedure / mode / mechanism has failed may be indicated by an AID12 subfield within the user information field of the BSRP (trigger) frame (e.g., an AID12 subfield set to a specific value such as 2008). However, this is merely one example, and the failure of an IDC-related procedure / mode / mechanism may be indicated through various information / fields.

[0315] - iii) An STA that receives information indicating that an IDC-related procedure / mode / mechanism has failed via a BSRP (trigger) frame can retry enabling the IDC-related procedure / mode / mechanism by retransmitting an IDC operation mode action frame request at a specific time.

[0316] Method 3

[0317] In one example of the present disclosure, an STA transmitting an IDC operation mode action frame (as a request frame) may receive a response frame from a neighboring STA with the status code set to failure. At this time, the STA may perform at least one of the operations described below:

[0318] - i) If the enable of an IDC-related procedure / mode / mechanism fails, the STA may not perform the IDC-related procedure / mode / mechanism. Additionally or alternatively, if the disable of an IDC-related procedure / mode / mechanism fails, the STA may recognize that the IDC-related procedure / mode / mechanism is enabled and perform the relevant operation.

[0319] - ii) Additionally or alternatively, the STA may recognize that the enable (and / or disable) of an IDC-related procedure / mode / mechanism has failed and may re-perform the enable procedure for the IDC-related procedure / mode / mechanism.

[0320] FIGS. 17 and 18 illustrate a procedure according to one embodiment of the present disclosure when a STA does not receive a response to an IDC enable or / and disable request. That is, FIGS. 17 and 18 illustrate a method of handling when the enable / disable of an IDC-related mechanism / mode / procedure fails. A procedure when a STA requesting the enable / disable of an IDC mechanism / mode / procedure via an action frame does not receive an ACK and / or response to the corresponding frame from a neighboring STA may be performed as in FIGS. 17 and / or FIGS. 18.

[0321] As an example of the present disclosure, as illustrated in FIG. 17, STA 1 may transmit an action frame request (e.g., an action request frame) to the AP regarding a request to enable / disable an IDC mode / procedure / mechanism. At this time, even though the AP has transmitted an ACK and / or response (e.g., an action response frame) for the action frame request, STA 1 may not receive the said ACK and / or response for a specific reason (e.g., deterioration of channel conditions).

[0322] Accordingly, STA 1 may wait for the reception of an ACK and / or response while the response timer is operating. The response timer may operate after an action frame request is transmitted and an IFS (e.g., SIFS, PIFS, etc.) is executed, but is not limited thereto. If the response timer expires, STA 1 determines that the reception of the ACK and / or response has failed and may retransmit or retry the action frame request. If the AP transmits an action frame response for the retransmission / retry and STA 1 successfully receives the response, the enable / disable procedure of the IDC mode / procedure / mechanism may proceed normally.

[0323] Additionally or alternatively, if the retransmission / retry fails, the AP, as the TXOP holder, may send an ICF (e.g., a BSRP trigger frame) to STA 1. At this time, STA 1 may send a multi-STA BA frame that is an ICR to the AP, and the multi-STA BA frame may contain information indicating the failure of STA 1's IDC enable / disable. Accordingly, STA 1 may retry the IDC enable / disable by sending an action frame request to the AP again during the TXOP or after the TXOP has ended.

[0324] As another example of the present disclosure, as illustrated in FIG. 18, STA 1 can transmit an action frame request (e.g., an action request frame) related to a request to enable / disable an IDC mode / procedure / mechanism to the AP.

[0325] AP sends a response (e.g., an action response frame) to STA 1 in response to an action frame request, and STA 1 sends an ACK for that response to AP, but AP may not receive the ACK for a specific reason (e.g., deterioration of channel conditions). Accordingly, AP may wait for the reception of the ACK from STA 1 while the response timer is running. The response timer may run after the response to the action frame request is transmitted and after an IFS (e.g., SIFS, PIFS, etc.), but is not limited thereto. If the response timer expires, AP determines that the reception of the ACK has failed and may retransmit or retry the action frame response.

[0326] Afterwards, STA 1 transmits an ACK for the above response, and if the AP successfully receives the ACK, the IDC enable / disable procedure can be successfully completed.

[0327] Additionally or alternatively, if a retry (e.g., retransmission of the response of the AP's action frame) fails, when the AP transmits an ICF (e.g., BSRP trigger frame) as a TXOP holder, STA 1 may notify the AP of the failure of IDC enable / disable via an ICR (e.g., multi-STA BA frame).

[0328] Accordingly, STA 1 can retry IDC enable / disable by sending an action frame request to the AP again during the TXOP or after the TXOP has ended.

[0329] Examples 2-3

[0330] This embodiment relates to a method for signaling information related to IDC mode enable / disable through multi-link operation update requests and responses.

[0331] In the case of a multi-link device (MLD), an ML operation update request / response frame may be used. Information regarding IDC mode enable / disable may be indicated by using common information of the reset ML element included in the ML operation update request / response frame and / or per-STA profile sub-elements.

[0332] FIG. 19 shows examples in which enable / disable instruction information of a specific operation mode is included in a reset ML element according to the present disclosure.

[0333] The example in FIG. 19(a) illustrates an example of a common information field within a reset ML element. For example, the common information field may include a common information length field, an MLD MAC address field, an enhanced multi-link (EML) capability field, an MLD capability and operation field, and an enhanced MLD capability and operation field. Additionally, the common field may further include an IDC operation mode field. Accordingly, an IDC mode enable / disable common to itself and / or all other STAs / APs among the STAs (or APs) affiliated with the MLD may be indicated.

[0334] For example, the IDC operation mode field may be included in the common information field, and the IDC operation mode field may include IDC mode enable / disable information. Additionally, an IDC operation mode presence bit may be added to the presence bitmap field of the reset ML element, and depending on the value of the bit, the IDC operation mode field may or may not be included in the common field.

[0335] This IDC mode enable / disable information may instruct IDC mode enable / disable for all STAs (or APs) belonging to the MLD. Alternatively, the IDC mode enable / disable information may instruct IDC mode enable / disable only for itself among the STAs (or APs) belonging to the MLD.

[0336] The example in FIG. 19(b) illustrates a case where IDC mode enable / disable information is included in the STA-per-profile sub-element of a reset ML element. The example in FIG. 19(b) illustrates a specific example in which the link ID of the STA control field is specified so that IDC mode enable / disable information is included within the STA information field of the link ID, but the scope of the present disclosure is not limited thereto and includes examples in which IDC mode enable / disable information is included at other locations of the STA-per-profile sub-element of a reset ML element.

[0337] For example, IDC mode enable / disable for itself or for other STAs belonging to the MLD may be indicated based on the link ID. The STA control field of the profile subelement per STA includes a link ID subfield, and depending on the value of the link ID, the information of the profile per STA may indicate other STAs belonging to the MLD. Since the link ID value 15 is reserved, this value may be used to indicate itself belonging to the MLD. In this way, IDC mode enable / disable for itself or other STAs belonging to the MLD may be indicated using the link ID.

[0338] An IDC operation mode field is defined, and IDC mode enable / disable information may be included within the IDC operation mode field. An IDC operation mode presence bit is added to the STA control field within the profile subelement per STA, and depending on the value of that bit, the IDC operation mode field may or may not be included. This field may also indicate, via a link ID, that it pertains to itself or another STA belonging to the MLD.

[0339] For example, regarding the IDC operation mode field, the same content described in the aforementioned Example 2-1 may also be applied to this embodiment.

[0340] As another example, IDC mode enable / disable information may be included in the operation parameter field. An IDC mode enable presence bit may be added to the presence bit of the operation parameter, and an IDC mode enable subfield may be added to the operation parameter information having 1 bit or a bit of a different size (e.g., a bit size that can distinguish the entire index in the case of index-based).

[0341] Additionally, or alternatively, by utilizing the presence bit of the operation parameter field and the reserved area / bit of the operation parameter information field, various operation modes / features such as IDC, DPS, DSO, and NPCA may be added and indicated.

[0342] FIG. 20 shows an example of an IDC mode enable using a multi-link operation update according to the present disclosure.

[0343] The example in FIG. 20 illustrates an example where STA1, belonging to a non-AP MLD, sends an ML operation update request to AP1, belonging to an AP MLD, and receives an ML operation update response. Through this frame exchange between STA1 and AP2, IDC mode enable between STA2 and AP2 can be performed.

[0344] During this frame exchange process, information regarding IDC mode enable / disable may be included within the STA-per-profile sub-element of the aforementioned reset ML element. For example, if the link ID specifies Link 2 for STA2 and AP2, IDC mode enable for STA2 may be indicated. If link 15 is indicated, IDC mode enable for STA1 of Link 1 may also be indicated. Alternatively, if IDC mode enable information is included in the common information field, IDC mode enable may be indicated for the entire MLD and / or for STA1 itself.

[0345] As AP2 belonging to the AP MLD requests IDC information through a BSRP trigger frame, STA2 belonging to the non-AP MLD can transmit a multi-STA block ACK (M-BA) containing IDC information as a response to the BSRP trigger frame.

[0346] In the process of exchanging ML operation update request / response frames, if IDC mode disable is indicated, IDC information may not be petitioned in the BSRP trigger frame.

[0347] In the example of FIG. 20, a STA belonging to a non-AP MLD transmits an ML operation update request frame to indicate IDC mode enable, but an AP belonging to an AP MLD transmits an ML operation update request frame to indicate IDC mode enable, and a STA belonging to a non-AP MLD transmits an ML operation update response frame.

[0348] Additionally or alternatively, the IDC operation mode element may not be included in the reset ML element within the ML operation update request frame, but may be included directly within the ML operation update request frame outside the reset ML element. For example, the ML operation update request frame may include the category field, the protected EHT action field, the dialogue token field, the reset ML element field, and the IDC operation mode element field in that order.

[0349] In the examples described above, the example in which an IDC operation mode element is included within a reset ML element or within a frame containing a reset ML element may also be applied to any other management frame containing a reset ML element, such as a link reset notification frame or a link reset request / response frame.

[0350] In the examples described above, the names of information / (sub)fields / (sub)elements / frames associated with a specific operation mode may be defined as general names for use with other operation modes or multiple operation modes.

[0351] The aforementioned IDC operation mode can be configured in the same way as described in the aforementioned Example 2-1.

[0352] Example 2-3-1

[0353] For the present embodiment, the IDC (mode) management frame of the aforementioned Embodiment 2-1-1 may include any management frame including basic ML elements and / or reset ML elements. Since the remaining features, excluding these additional features, are identical to those of the aforementioned Embodiment 2-1-1 and apply to the present embodiment, a redundant description is omitted.

[0354] When timeout interval information is included in an ML element, common information fields within various types (e.g., basic ML element, probe ML element, reset ML element) may be included. For example, timeout interval information may be included within an IDC operation mode element / field or within a UHR operation mode element / field.

[0355] Example 2-3-2

[0356] For the present embodiment, the IDC (mode) management frame of the aforementioned Embodiment 2-1-2 may include any management frame including basic ML elements and / or reset ML elements. Since the remaining features, excluding these additional features, are identical to those of the aforementioned Embodiment 2-1-2 and apply to the present embodiment, a redundant description is omitted.

[0357] When timeout interval information is included in an ML element, common information fields within various types (e.g., basic ML element, probe ML element, reset ML element) may be included. For example, timeout interval information may be included within an IDC operation mode element / field or within a UHR operation mode element / field.

[0358] Meanwhile, the error handling method of the procedure for enabling / disabling the IDC mode / procedure / mechanism through the multi-link operation update may be identical to / correspond to the error handling method described above. For example, the action request / response frames described in FIGS. 18 and 19 may be replaced / applied to the multi-link operation update request / response frames. In addition, each IDC-related frame described in Example 2-1, Example 2-2, and Example 2-3 may be replaced with the multi-link operation update frames, etc.

[0359] Examples 2-4

[0360] This embodiment relates to a method for indicating IDC mode enable / disable using IDC TWT SP (service period) pause / resume frames.

[0361] You can enable / disable IDC mode by requesting / pausing / resuming the IDC SP using the channel usage request frame, channel usage response frame, and TWT setup frame. If you use the IDC setup command of the IDC SP request type in the TWT element, you can enable / disable IDC mode.

[0362] Additionally, or alternatively, IDC mode enable / disable can be enabled / disabled in various ways as follows through TXOP level signaling.

[0363] For example, IDC mode enable / disable instruction information may be included in the trigger frame and the trigger response frame. In this case, the information instructing IDC mode enable / disable may be included in the delivered info of the trigger frame and / or the control information of the trigger response frame. Accordingly, IDC mode enable / disable can be dynamically instructed in a short-term manner at the TXOP level.

[0364] As another example, a new aggregated-control (A-control) field may be defined, and IDC mode enable / disable may be indicated through this A-control field. For the control ID of the new A-control field, one of the previously reserved values ​​10–14 (e.g., 10) may be used. For example, a control ID value of 10 may be defined as corresponding to an IDC report (IDCR). IDC mode enable / disable indication information may be included in an A-control field having such a new control ID. An A-control field containing this IDCR may be signaled by being included in a QoS data frame, a QoS null frame, etc.

[0365] Support and / or enablement of various operation modes not supported by existing wireless LAN systems can be indicated, and the action for cases where there is no response to an enable request can be clearly and efficiently defined using a timeout interval.

[0366] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct 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 obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0367] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0368] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may 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 may 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 may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0369] Although the method proposed in this disclosure has been described with an example applied to an IEEE 802.11-based system, it 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 request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode to a second STA by a first station (STA); and Based on the fact that a first response frame for the request frame is not received from the second STA within a certain period of time, the method includes the step of retransmitting the request frame by the first STA. The above first information is a method included in the reconfiguration multi-link element of the above request frame.

2. In Paragraph 1, A method comprising at least one of the first information, which includes information related to a request for enabling or disabling the first operation mode or identification information of the first operation mode.

3. In Paragraph 1, A timer starts at a first point in time when the above request frame is transmitted, or at a second point in time after the inter-frame space (IFS) from the first point in time, and A method in which whether the first response frame is received from the second STA within the specified time from the start time of the timer is monitored by the first STA.

4. In Paragraph 3, A method in which the timer is stopped based on the first response frame being received from the second STA within the specified time from the start time of the timer.

5. In Paragraph 1, The above first information is a method included in the Per-STA profile sub-element of the reset multi-link element.

6. In Paragraph 3, Based on the fact that a second response frame for the retransmission of the above request frame is not received from the second STA within the above specified time: The above buffer status report poll (BSRP) trigger frame is transmitted from the second STA to the first STA, and A method in which a third response frame for the above BSRP trigger frame is transmitted from the first STA to the second STA.

7. In Paragraph 6, A method in which the third response frame includes second information indicating that the enable or disable of the first operation mode has failed.

8. In Paragraph 6, The above third response frame is a method comprising a multi-STA BA (block acknowledgment) frame.

9. In Paragraph 6, A method in which, based on the fact that the second STA is the holder of a transmission opportunity (TXOP), the retransmission of the request frame after the TXOP is performed by the first STA.

10. In Paragraph 1, The above request frame is an action request frame or a multi-link operation update request frame associated with the first operation mode, a method.

11. In Paragraph 1, The above-mentioned first STA is a non-access point (AP) STA, and The above second STA is a method that is an access point (AP).

12. In the first STA, the first STA is: One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Transmitting a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode to a second STA through the one or more transceivers; and Based on the fact that a first response frame for the above request frame is not received from the second STA within a certain period of time, the request frame is configured to be retransmitted, and The first information above is a first STA included in the reconfiguration multi-link element of the request frame.

13. A step of receiving a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode from a first STA by a second station (STA); and It includes the step of generating a first response frame for the above request frame by the second STA, Based on the fact that the first response frame is not transmitted to the first STA within a set period of time, the request frame is transmitted from the first STA to the second STA, and The above first information is a method included in the reconfiguration multi-link element of the above request frame.

14. In the second station (STA), the second STA is: One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Receiving a request frame containing first information related to enabling or disabling a first operation mode among at least one operation mode from a first STA through the one or more transceivers; and It is configured to generate a first response frame for the above request frame, and Based on the fact that the first response frame is not transmitted to the first STA within a set period of time, the request frame is transmitted from the first STA to the second STA, and The first information above is a second STA included in the reconfiguration multi-link element of the request frame.

15. A processing device configured to control a first station (STA) in a wireless local area network (WLAN) system, wherein the processing device: One or more processors; and A processing device comprising one or more computer memories that are operably connected to one or more processors and store instructions for performing a method according to any one of claims 1 to 11 based on execution by one or more processors.

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

Images