Method and apparatus for negotiation for multi-access point coordination in wireless LAN system

Abstract

Disclosed are a method and apparatus for negotiation for multi-access point coordination in a wireless LAN system. The method according to an embodiment of the present disclosure may comprise the steps of: receiving, by a first AP, a negotiation request frame for multi-access point (AP) coordination from a second AP; and transmitting, by the first AP, a negotiation response frame for the multi-AP coordination to the second AP. The negotiation request frame may comprise one or more pieces of request information comprising one or more request parameter sets. The negotiation response frame may comprise one piece of first information indicating accept, reject, or alternate, for each of the one or more pieces of request information included in the negotiation request frame. The one piece of first information may be associated with a specific target wake time (TWT) schedule.

Description

Consultation method and device for multi-access point cooperation in a wireless LAN system

[0001] The present disclosure relates to a method and apparatus for negotiation of multi-access point coordination 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 negotiation regarding multi-access point coordination in a wireless LAN (WLAN) system.

[0005] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving a response to a request for multi-access point cooperation in a wireless LAN system.

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

[0007] A method according to one aspect of the present disclosure may include the steps of: receiving a negotiation request frame for multi-access point (AP) coordination from a second AP by a first AP; and transmitting a negotiation response frame for multi-AP coordination to the second AP by the first AP. The negotiation request frame may include one or more request information comprising one or more sets of request parameters. The negotiation response frame may include one first information indicating acceptance, rejection, or alternative for each of the one or more request information included in the negotiation request frame. The one first information may be associated with a specific target wake time (TWT) schedule.

[0008] A method according to a further aspect of the present disclosure may include the step of transmitting a consultation request frame for multi-access point (AP) cooperation to a first AP by a second AP; and the step of receiving a consultation response frame for multi-AP cooperation from the first AP by the second AP. The consultation request frame may include one or more request information comprising one or more sets of request parameters. The consultation response frame may include one first information indicating acceptance, rejection, or alternative for each of the one or more request information included in the consultation request frame. The one first information may be associated with a specific target wake time (TWT) schedule.

[0009] According to the present disclosure, a method and apparatus for negotiation of multi-access point coordination in a wireless LAN (WLAN) system may be provided.

[0010] According to the present disclosure, a method and apparatus for transmitting or receiving a response to a request for multi-access point cooperation consultation in a wireless LAN system may be provided.

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

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

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

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

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

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

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

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

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

[0020] FIG. 8 is a diagram illustrating various transmission and reception techniques in a MAP environment to which the present disclosure can be applied.

[0021] FIG. 9 is a drawing illustrating an example of an individual TWT operation to which the present disclosure may be applied.

[0022] FIG. 10 is a drawing illustrating an example of a broadcast TWT operation to which the present disclosure may be applied.

[0023] Figure 11 is a diagram illustrating an example of a TWT information element format.

[0024] Figure 12 is a diagram illustrating examples of individual TWT parameter set field formats.

[0025] Figure 13 is a diagram illustrating examples of broadcast TWT parameter set field formats.

[0026] FIG. 14 is a diagram illustrating exemplary APs and STAs in an OBSS to which the present disclosure may be applied.

[0027] FIG. 15 is a drawing showing an example of the operation of a first AP according to the present disclosure.

[0028] FIG. 16 is a drawing illustrating an example of the operation of a second AP according to the present disclosure.

[0029] FIG. 17 shows examples of configurations of status information and TWT identification information included in a cooperation / consultation response according to the present disclosure.

[0030] FIG. 18 is a diagram illustrating the process of sending and receiving a request for consultation on cooperation between APs and a response for consultation on cooperation according to the present disclosure.

[0031] FIG. 19 is a drawing showing examples of TWT information extension elements according to the present disclosure.

[0032] FIG. 20 is a drawing showing additional examples of TWT information extension elements according to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0060] An AP refers to an entity that enables access to the DS via the WM for combined non-AP STAs and also possesses the functionality of an STA. Data movement between the BSS and the 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 the 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.

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

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

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

[0064] In wireless LAN systems, no assumptions are made regarding the relative physical locations of BSSs, and all of the following forms are 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 forms such as when an ad-hoc network operates at a location where an ESS network exists, when wireless networks that physically overlap are configured by different organizations, or when two or more different access and security policies are required at the same location.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0081] With reference 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, ...).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] Multiple Access Point (MAP) Operation

[0135] Examples of the present disclosure regarding multiple access point (MAP) operations are described below.

[0136] MAP operation can be defined as operation between a master AP (or sharing AP) and a slave AP (or shared AP).

[0137] The master AP plays the role of initiating and controlling MAP operations for transmission and reception between multiple APs. The master AP groups slave APs and manages links with slave APs to enable information sharing among them. The master AP manages information about the BSS configured by the slave APs and information about the STAs that have formed an association with the BSS.

[0138] A slave AP forms a pair with a master AP and can share control information, management information, and data traffic. The slave AP performs the same basic functions as an AP, including establishing a BSS in a wireless LAN.

[0139] In MAP operation, the STA can form a BSS by combining with a slave AP or a master AP.

[0140] In a MAP environment, the master AP and slave AP can perform direct transmission and reception with each other. The master AP and STA may not be able to perform direct transmission and reception with each other. A slave AP (for example, a slave AP coupled with a STA) can perform direct transmission and reception with the STA. One of the slave APs can become the master AP.

[0141] MAP operation is a technique in which one or more APs transmit and receive information to one or more STAs. For example, techniques such as C-TDMA (coordinated-time division multiple access), which divides allocation between APs along the time axis; C-OFDMA (coordinated-orthogonal frequency division multiple access), which divides along the frequency axis; and C-SR (coordinated-spatial reuse), which utilizes spatial reuse, can be applied for MAP operation. Alternatively, MAP operation may also apply coordinated beamforming (C-BF) or joint beamforming techniques, which perform simultaneous transmission and reception in cooperation.

[0142] FIG. 8 is a diagram illustrating various transmission and reception techniques in a MAP environment to which the present disclosure can be applied.

[0143] As with the existing method, the transmission performed by a BSS AP to a BSS STA can be referred to as STX (single transmission). In STX, there is a problem where the transmission and reception performance for users / STAs located at the cell edge is degraded due to interference with adjacent APs. For example, as shown in Fig. 8(a), if AP1 and AP2 perform transmissions to STA1 and STA2 respectively at the same time in the same frequency band, a collision may occur on the wireless medium.

[0144] In MAP techniques, performance can be improved by reducing inter-symbol interference (ISI) through cooperation among neighboring APs or by performing joint transmissions. For example, in the C-OFDMA method of Fig. 8(b), interference can be avoided by AP1 transmitting to STA1 in the first bandwidth and AP2 transmitting to STA2 in the second bandwidth at the same time. The example in Fig. 8(c) illustrates a cooperative beamforming or nulling technique in which AP1 nulls the interference affecting AP2 and / or STA2 while transmitting to STA1, and AP2 nulls the interference affecting AP1 and / or STA1 while transmitting to STA2. Fig. 8(d) illustrates an AP selection method in which the AP with the best channel conditions among adjacent APs performs the transmission. As shown in the example of Fig. 8(e), joint transmission (JTX) or joint reception (JRX) in which multiple APs cooperate to transmit or receive simultaneously may be applied, and furthermore, joint MU-MIMO may be supported.

[0145] In the examples of the present disclosure, multiple AP operations are assumed to be performed as follows.

[0146] Step 1: Distribute resource areas to each AP via trigger frames from the master AP (i.e., AP-to-AP trigger frames, or master trigger frames).

[0147] Step 2: Each AP performs DL (i.e., from AP to STA) data transmission within its allocated resource area, or transmits a trigger frame (i.e., AP-to-STA trigger frame) for UL (i.e., from STA to AP) data transmission within its allocated resource area.

[0148] Step 3: The STA transmits a response to the DL data or transmits via UL data (e.g., TB PPDU).

[0149] If the resources distributed among APs are frequency resources, it corresponds to the C-OFDMA method; if they are time resources, it corresponds to the C-TDMA method; and if they are spatial resources (or beams), it corresponds to the CBF method. The examples described below are explained by assuming, typically, that the C-OFDMA method, that is, multi-AP operation is performed through resources distinguished in the frequency domain. However, the scope of the present disclosure is not limited thereto and may additionally or alternatively include multi-AP operation through resources distinguished in other domains (e.g., time domain and / or spatial domain).

[0150] Target Wake Time (TWT)

[0151] The following explains TWT (target wake time).

[0152] TWT is a Power Saving (PS) technology that can improve the energy efficiency of non-AP STAs by defining the Service Period (SP) between APs and non-AP STAs and sharing information about SPs to reduce contention. In the TWT Setup phase, an STA that performs requests, suggestions, or demands can be referred to as a Requesting STA. Additionally, an AP that responds to such requests by accepting or rejecting them can be referred to as a Responding STA. The Setup phase may include the process of determining or defining the STA's TWT request to the AP, the type of TWT operation to be performed, and the frame types to be transmitted and received. TWT operations can be classified into Individual TWT and Broadcast TWT.

[0153] FIG. 9 is a drawing illustrating an example of an individual TWT operation to which the present disclosure may be applied.

[0154] Individual TWT is a mechanism for AP and non-AP STA to perform data exchange after negotiating the awake / doze status of the non-AP STA through the transmission and reception of TWT request / response frames. In the example of Fig. 9, AP and STA1 can form a trigger-enabled TWT agreement through TWT request frames and TWT response frames. Here, the method used by STA1 is a solicited TWT method, in which STA1 transmits a TWT request frame to AP, and STA1 receives information for TWT operation from AP through a TWT response frame. On the other hand, STA2, which performs the unsolicited TWT method, can receive information regarding the setup of the trigger-enabled TWT agreement from the AP via an unsolicited TWT response. Specifically, STA2 can calculate the next TWT by adding a specific number to the current TWT value. During the trigger-enabled TWT SP, the AP can transmit a trigger frame to the STAs. The trigger frame can inform the STAs that there is buffered data in the AP. In this regard, STA1 can notify the AP of its awake state by transmitting a PS-Poll frame. Additionally, STA2 can notify the AP of its awake state by transmitting a QoS Null frame. Here, the data frames transmitted by STA1 and STA2 may be frames in the TB PPDU format. The AP that checks the status of STA1 and STA2 can send DL MU PPDU to the active STAs.When the TWT SP expires, STA1 and STA2 can transition to a doze state.

[0155] FIG. 10 is a drawing illustrating an example of a broadcast TWT operation to which the present disclosure may be applied.

[0156] Broadcast TWT is a type of TWT in which a non-AP STA (or TWT scheduling STA) obtains information regarding the target beacon transmission time (TBTT) and listen interval, etc., by transmitting and receiving TWT request / response frames with an AP (or TWT scheduled STA). Here, a negotiation operation regarding the TBTT may be performed. Based on this, the AP can define a frame containing the TWT scheduling information through a beacon frame. In FIG. 10, STA1 performs a request-type TWT operation, and STA2 performs an un-request-type TWT operation. The AP can transmit a DL MU PPDU after checking the awake status of the STAs through the trigger it transmitted. This may be identical to the process of an individual TWT. In a broadcast TWT, a trigger-enabled TWT SP containing a beacon frame can be repeated multiple times at a regular interval.

[0157] The transmission of TWT information can be achieved through TWT information frames and TWT information elements.

[0158] A TWT information frame is transmitted by an STA to request or transmit information about a TWT consensus, and is transmitted by one of the STAs of the existing TWT consensus. The action frame of the TWT information frame includes a TWT information field. The TWT Information field may include a 3-bit TWT flow identifier subfield, a 1-bit response requested subfield, a 1-bit next TWT request subfield, a 2-bit next TWT subfield size subfield, a 1-bit all TWT subfield, and a 0 / 32 / 48 / 64-bit next TWT subfield.

[0159] Figure 11 is a diagram illustrating an example of a TWT information element format.

[0160] TWT information elements may be transmitted or received by being included in beacons, probe responses, (re)combined response frames, etc. TWT information elements may include an element ID field, a length field, a control field, and a TWT parameter information field.

[0161] The control field of a TWT information element has the same format regardless of whether it is an individual TWT or a broadcast TWT.

[0162] The NDP paging indicator subfield can have a value of 1 if the NDP paging field exists, and a value of 0 if the NDP paging field does not exist.

[0163] The responder PM mode subfield can represent Power Management (PM) mode.

[0164] The negotiation type subfield may indicate whether the information contained in the TWT element is for negotiation of parameters of a broadcast TWT or individual TWT(s), or for a wake TBTT interval.

[0165] For example, if the value of the negotiation type subfield is 0, the TWT subfield is for a future individual TWT SP start time, and the TWT element contains a set of individual TWT parameters. This may correspond to an individual TWT negotiation between a TWT requesting STA and a TWT response STA, or to an individual TWT announcement by a TWT responder.

[0166] For example, if the value of the consultation type subfield is 1, the TWT subfield is for the next TBTT time, and the TWT element contains a single set of TWT parameters. This may correspond to the wake TBTT and wake interval consultation between the TWT-scheduled STA and the TWT-scheduling AP.

[0167] For example, if the value of the consultation type subfield is 2, the TWT subfield is for a future broadcast TWT SP start time, and the TWT element contains one or more sets of broadcast TWT parameters. This may correspond to providing a broadcast TWT schedule to a TWT-scheduled STA by including the TWT element in a broadcast management frame transmitted by the TWT scheduling AP.

[0168] For example, if the value of the consultation type subfield is 3, the TWT subfield is for a future broadcast TWT SP start time, and the TWT element contains one or more sets of broadcast TWT parameters. This may correspond to managing membership in a broadcast TWT schedule by including the TWT element in an individually addressed management frame transmitted by either the TWT-scheduled STA or the TWT-scheduled AP.

[0169] If the TWT information frame disabled subfield is set to 1, it indicates that reception of TWT information frames by the STA is disabled, otherwise it can be set to 0.

[0170] The wake duration unit subfield indicates the unit of the nominal minimum TWT wake duration field. The wake duration unit subfield can be set to 0 when the unit is 256us, and to 1 when the unit is TU. If it is not HE / EHT STA, the wake duration unit subfield can be set to 0.

[0171] The MSB (most significant bit) of the consultation type field may correspond to the broadcast field. If the broadcast field is 1, the TWT element may contain one or more sets of broadcast TWT parameters. If the broadcast field is 0, only one set of individual TWT parameters may be contained in the TWT element. A TWT element in which the broadcast field is set to 1 may be referred to as a broadcast TWT element.

[0172] FIG. 12 is a diagram illustrating examples of individual TWT parameter set field formats. FIG. 13 is a diagram illustrating examples of broadcast TWT parameter set field formats.

[0173] The TWT parameter information field included in the TWT element of Fig. 11 may have different configurations depending on the individual TWT or broadcast TWT.

[0174] In the case of an individual TWT, the TWT parameter information field within the TWT element contains a single individual TWT parameter set field.

[0175] In the case of a broadcast TWT, the TWT parameter information field within the TWT element includes one or more broadcast TWT parameter set fields. Each broadcast TWT parameter set may include specific information for a single broadcast TWT.

[0176] As illustrated in FIGS. 12 and 13, the individual TWT parameter set field and the broadcast TWT parameter set field include common subfields.

[0177] The request type subfield has the same size as the individual TWT parameter set field and the broadcast TWT parameter set field, but its detailed configuration may differ. This will be discussed later.

[0178] The target wake time subfield indicates the start time of an upcoming individual / broadcast TWT SP.

[0179] The nominal maximum TWT wake duration subfield represents the minimum unit that a TWT requesting STA expects to be woken up to complete frame exchanges associated with the TWT flow identifier during the TWT wake interval duration. Here, the TWT wake interval may refer to the average time between consecutive TWT SPs expected by the TWT requesting STA.

[0180] The TWT Wake Interval Mantissa subfield can be expressed in microseconds as the binary value of the TWT Wake Interval.

[0181] Referring to Fig. 12, the TWT group assignment subfield, TWT channel, and NDP paging subfield are included only in the individual TWT parameter set fields.

[0182] The TWT group assignment subfield contains information about the TWT group to which the STA is assigned and provides it to the TWT requesting STA. This information can be used to calculate the TWT value within the TWT group. The STA's TWT value may be equal to the zero offset value and the TWT offset value multiplied by the TWT unit value.

[0183] The TWT channel subfield represents a bitmap indicating an allowed channel. When transmitted by a TWT request STA, the TWT channel subfield may contain a bitmap indicating a channel that the STA requests to use as a temporary default channel during the TWT SP. When transmitted by a TWT response STA, the TWT channel subfield may contain a bitmap indicating a channel that the TWT request allows.

[0184] The NDP paging subfield is optional and may include information such as the identifier of the STA being paged and the maximum number of TWT wake intervals between NDP paging frames.

[0185] Referring to FIG. 13, the broadcast TWT info subfield is included only in the broadcast TWT parameter set field. The broadcast TWT info subfield may include a 3-bit reserve bit, a 5-bit broadcast TWT identifier (ID) subfield, and an 8-bit broadcast TWT persistence subfield. The broadcast TWT identifier subfield indicates the broadcast ID of a specific broadcast TWT that the STA requests to join or provides TWT parameters for, depending on the value of the TWT setup command subfield of the TWT element. The broadcast TWT persistence subfield indicates the number of TBTTs planned on the broadcast TWT schedule.

[0186] Next, the detailed configuration of the request type subfield is explained.

[0187] First, with reference to Fig. 12, the format of the request type subfield of the individual TWT parameter set field will be explained.

[0188] The TWT request subfield can indicate whether it is a request STA or a response STA. If the value is 1, it indicates that it is a TWT request STA or a scheduled STA, and if it is 0, it indicates that it is a TWT response STA or a scheduling AP.

[0189] The TWT setup command subfield can represent commands such as Request, Suggest, Demand, Accept, Alternate, Dictate, and Reject.

[0190] The trigger subfield indicates whether to use trigger frames in the TWT SP. If the value is 1, the trigger is used, and if it is 0, the trigger may not be used.

[0191] The implicit subfield can indicate whether it is an implicit TWT or an explicit TWT. If the value is 1, it indicates an implicit TWT, and if it is 0, it indicates an explicit TWT.

[0192] The flow type subfield may indicate the type of interaction between the TWT requesting STA (or the STA being scheduled for TWT) and the TWT responding STA (or the AP scheduling for TWT). If the value is 1, it may indicate an announced TWT, where the STA sends a wake-up signal to the AP by transmitting a PS-Poll or APSD (automatic power save delivery) trigger frame before a non-trigger frame is transmitted from the AP to the STA. If the value is 0, it may indicate an unannounced TWT.

[0193] The TWT flow identifier subfield may include a 3-bit value that uniquely identifies specific information about the TWT request in other requests made between the same TWT request STA and TWT response STA pair.

[0194] The TWT wake interval exponent subfield allows setting the TWT wake interval value in binary microseconds. For individual TWTs, it may refer to the interval between individual TWT SPs. The TWT wake interval of a request STA can be defined as [TWT Wake Interval Mantissa * 2 * TWT Wake Interval Exponent].

[0195] The TWT protection subfield may indicate whether a TWT protection mechanism is used. If the value is 1, the TXOP within the TWT SP may be initiated by a NAV protection mechanism such as (MU)RTS / CTS or CTS-to-self frames, and if it is 0, the NAV protection mechanism may not be applied.

[0196] Referring to Fig. 13, some of the subfields of the request type subfield of the broadcast TWT parameter set field are common to the subfields of the request type subfield of the individual TWT parameter set field, so a description thereof is omitted. The subfields included only in the broadcast TWT parameter set are described below.

[0197] The Last Broadcast Parameter Set subfield indicates whether it is the last broadcast TWT parameter set. If the value is 1, it indicates that it is the last broadcast TWT parameter set, and if it is 0, it indicates that the next broadcast TWT parameter set exists.

[0198] The broadcast TWT recommendation subfield can represent recommendations for frame types transmitted by the AP during the broadcast TWT SP with values ​​from 1 to 7.

[0199] The last bit of the request type subfield of the broadcast TWT parameter set field can be reserved.

[0200] With the recent surge in wired and wireless traffic, latency-sensitive traffic has also increased significantly. Latency-sensitive traffic includes real-time audio and video transmission, and the need to support this in wireless environments has grown with the proliferation of multimedia devices. However, compared to wired environments, there are many factors to consider when supporting latency-sensitive traffic in wireless environments. This is because wireless environments have lower transmission speeds than wired environments, and issues regarding interference from the surroundings must also be taken into account. In particular, in wireless LAN systems, since multiple STAs must compete equally for media occupancy in the ISM (Industry-Science-Medical) band, it is relatively more difficult to support latency-sensitive traffic compared to cellular communication networks based on wireless resource scheduling by a central base station. This disclosure describes a new method for supporting latency-sensitive traffic in wireless LAN systems.

[0201] In the present disclosure, latency may refer to latency as defined in IEEE 802.11 series standards. For example, it may refer to the time from when a frame to be transmitted enters the queue of the MAC layer of a transmitting STA, until the transmission by the transmitting STA is successfully completed at the PHY layer, and until the transmitting STA receives an ACK / block ACK, etc. from a receiving STA and the corresponding frame is deleted from the queue of the transmitting STA's MAC layer. Additionally, in the present disclosure, a non-AP STA that supports the transmission of latency-sensitive data may be referred to as a Low Latency STA. Furthermore, data other than latency-sensitive data may be referred to as regular data.

[0202] Restricted TWT (r-TWT) can support the AP in securing priority data transmission possibilities for low-latency STAs over other STAs by establishing a special broadcast TWT for low-latency STAs transmitting latency-sensitive data. An STA can establish membership for one or more r-TWT schedules with respect to the AP. Here, r-TWT consensus can be established through the same process as broadcast TWT consensus, and for this purpose, broadcast TWT elements can be defined to include an r-TWT parameter set field. For example, the r-TWT parameter set may refer to a specific broadcast TWT parameter set field that is distinct from other broadcast TWT parameter set fields. That is, the r-TWT parameter set field may correspond to a special case of the broadcast TWT parameter set field. Additionally, the AP can announce the r-TWT SP.

[0203] Basically, if another STA that supports r-TWT operation is a TXOP holder, the TXOP must be ended before the start time of the r-TWT SP advertised by the combined AP. Accordingly, the STA associated with the r-TWT (i.e., the low-latency STA) can perform traffic transmission and reception preferentially over the other STA within the r-TWT SP.

[0204] In the present disclosure, as described above, a low-latency STA associated with a specific r-TWT is referred to as a member r-TWT scheduled STA, and other STAs are referred to as non-member STAs. A non-member STA may be a STA that has the capability to support r-TWT operation but is not a member of any r-TWT, a STA that supports r-TWT operation and is a member of another r-TWT, or a STA that does not have the capability to support r-TWT operation.

[0205] A STA that supports the limited SP (or r-TWT SP) operation of a broadcast TWT (e.g., a low-latency STA) may notify the AP that it needs to transmit latency-sensitive data based on the r-TWT operation. If the AP supports the r-TWT operation / mode, the AP may transmit a frame containing scheduling information for the TWTs requested by each STA to the low-latency STA and other STA(s). For example, to perform an operation for an r-TWT, non-AP STAs may obtain r-TWT related information from the AP via a beacon frame, a probe response frame, a (re)join response frame, or other frames in an as-yet-undefined format (e.g., a broadcast, advertisement, or announcement frame).

[0206] According to restricted TWT operations, a separate TXOP (i.e., access by other STAs is restricted) can be secured within an r-TWT SP using a NAV such as (MU) RTS / CTS or CTS-to-self, or a quiet interval. Before a specific r-TWT SP starts, if there is a TXOP of a STA other than the STA that has membership in the specific r-TWT schedule (i.e., a non-member STA), it must be stopped. The TXOP of the other STA (i.e., a non-member STA) may be additionally executed after the specific r-TWT SP ends.

[0207] Response plan during the negotiation process regarding TWT coordination

[0208] In a multi-BSS environment, when APs are located within a range where they can receive beacon frames from each other, an overlapping BSS (OBSS) range can be formed, in which the transmission and reception ranges (i.e., BSS) of the APs overlap.

[0209] FIG. 14 is a diagram illustrating exemplary APs and STAs in an OBSS to which the present disclosure may be applied.

[0210] As illustrated in FIG. 14, the signaling range of AP1 (e.g., the range corresponding to BSS 1) and the signaling range of AP2 (e.g., the range corresponding to BSS 2) may overlap. In this way, when AP1 and AP2 are located within a range where they can receive (i.e., overhear) each other, AP1 and AP2 can negotiate for coordination regarding their respective scheduled R-TWT SP (service period) through (wireless / wired) communication. This case corresponds to the situation where AP1 and AP2 are located within the range of an OBSS where their transmission and reception ranges overlap, unlike the case where AP1 and AP2 are hidden nodes.

[0211] In this regard, STAs located within the overlapping range can receive beacon frames from APs with which they have formed an association, as well as beacon frames from APs with which they have not formed an association. For example, STA 1-2 can receive beacon frames from AP1 with which they have formed an association, and can also receive (i.e., overhear) beacon frames from AP2 with which they have not formed an association. For example, STA 2-3 can receive beacon frames from AP2 with which they have formed an association, and can also receive (i.e., overhear) beacon frames from AP1 with which they have not formed an association.

[0212] The examples of the present disclosure are not limited to the situations of APs and / or STAs exemplified in FIG. 14, but may be applied to various situations where consultation regarding the cooperation service period between APs is required. For example, AP1 may be in a location / situation where it can receive AP2's beacon frame, and AP2 may be in a location / situation where it cannot receive AP1's beacon frame. Alternatively, AP1 and AP2 may be in a location / situation where they can receive each other's beacon frames. Alternatively, AP1 may be in a location / situation where it cannot receive AP2's beacon frame, and AP2 may be in a location / situation where it can receive AP1's beacon frame.

[0213] Beacon frames may contain restricted-TWT (R-TWT) scheduling information assigned by an AP to STAs associated with it, and STAs receiving R-TWT scheduling information are required to protect an R-TWT SP to which they are not members (e.g., if the STA's TXOP is in progress before the start time of the R-TWT SP as previously described, the TXOP is terminated). In other words, a STA receiving a beacon frame containing R-TWT scheduling information may be in a position where it must protect the R-TWT SP. Meanwhile, if an STA receives R-TWT scheduling information advertised by an unassociated (or neighboring) AP, it is not yet defined whether it must protect the R-TWT SP or transmit / receive low-latency traffic / data during the R-TWT SP.

[0214] The present disclosure describes a method for performing negotiation for coordination of an R-TWT based on scheduling information for an R-TWT scheduled by a combined AP (e.g., AP1) and / or scheduling information for an R-TWT scheduled by an uncombined (or neighboring) AP (e.g., AP2). In the following description, to distinguish it from an R-TWT SP scheduled by a combined AP (e.g., which may be referred to as a BSS R-TWT SP), an R-TWT SP scheduled by another AP (e.g., an uncombined AP or a neighboring AP) is referred to as an OBSS R-TWT SP. The scope of the present disclosure is not limited by the designation OBSS R-TWT.

[0215] In this disclosure, the case where a cooperation request is transmitted by a coupled AP and a cooperation response is transmitted by an uncoupled (or neighboring) AP is described primarily as a representative example; however, for the sake of clarity of explanation, the method proposed in this disclosure may also be applied to the case where a cooperation request is transmitted by an uncoupled (or neighboring) AP and a cooperation response is transmitted by a coupled AP.

[0216] AP1 and AP2 of FIG. 14 may, for example, belong to the same multi-AP (MAP) group. They may correspond to slave APs in a MAP operation having the same master AP. Alternatively, either AP1 or AP2 may correspond to the master AP in a MAP operation.

[0217] In the present disclosure, negotiation for R-TWT coordination can be performed based on R-TWT schedule information set by AP1 for STAs combined with AP1 and R-TWT schedule information set by AP2 for STAs combined with AP2. During the negotiation process between two APs, in response to a request for cooperation / negotiation from another AP, the AP may transmit a cooperation / negotiation response, and the cooperation / negotiation response may include information signaling the status of the cooperation / negotiation request.

[0218] In this disclosure, it is assumed that the APs performing cooperation / consultation are APs whose BSS overlaps. One of the APs corresponds to an associated AP in terms of a specific STA, and the other AP may correspond to a neighboring AP or an OBSS AP. For example, in terms of the STA associated with the first AP, the first AP may be an associated AP and the second AP may be an OBSS AP. In terms of the STA associated with the second AP, the second AP may be an associated AP and the first AP may be an OBSS AP.

[0219] In the examples of this disclosure, cooperation / consultation among APs is described assuming an R-TWT schedule, but the subject of cooperation / consultation is not limited to the R-TWT schedule. For example, the cooperation / consultation operation among APs regarding the R-TWT schedule described in this disclosure may be equally applied to the cooperation / consultation operation among APs regarding individual TWT schedules or broadcast TWT schedules. For example, in the examples of this disclosure, the TWT parameter set for the R-TWT schedule may be replaced with the TWT parameter set for the individual / broadcast TWT schedule that is the subject of cooperation / consultation.

[0220] In the following examples, methods for sending and receiving negotiation responses to negotiation requests in the negotiation process for Multi-AP Cooperation (MAPC) are explained.

[0221] FIG. 15 is a drawing showing an example of the operation of a first AP according to the present disclosure.

[0222] In step S1510, the first AP can receive a consultation request frame for the MAPC from the second AP.

[0223] For example, the first AP may correspond to a multi-AP cooperation response AP, and the second AP may correspond to a multi-AP cooperation request AP.

[0224] In some examples, the consultation request frame may include one or more request information by the second AP (e.g., information including one or more sets of request parameters).

[0225] In step S1520, the first AP can transmit a consultation response frame for the MAPC to the second AP.

[0226] In some examples, the consultation response frame may include a first information for each of one or more request information included in the consultation request frame. If the consultation request frame includes first request information and second request information, the consultation response frame may include first information for the first request information and first information for the second request information. The first information may indicate one of acceptance, rejection, or alternative for specific request information and may correspond to status information in the examples described below.

[0227] In some examples, the first information may be associated with a specific TWT schedule. For example, the consultation response frame may further include second information containing identification information of the specific TWT schedule. Accordingly, based on one combination (or one pair) of the first information and the second information included in the consultation response frame, acceptance, rejection, or alternative to the specific TWT schedule may be signaled.

[0228] In some examples, the first information and the second information may be included in one specific element (or one specific field) within the consultation response frame. For example, the consultation response frame may include one specific element / field, and this one specific element / field may include the first information and the second information for each of one or more request information included in the consultation request frame. For example, if the consultation request frame includes the first request information and the second request information, the consultation response frame may include a first combination / pair of the first information and the second information for the first request information, and a second combination / pair of the first information and the second information for the second request information, in one specific element / field. For example, one specific element / field may correspond to the status list described below.

[0229] In some examples, one or more request parameter sets included in the consultation request frame may include one or more request parameter sets for the coordinated R-TWT (Co-RTWT). For example, the first request parameter set may be a parameter set for the first Co-RTWT, and the second request parameter set may be a parameter set for the second Co-RTWT.

[0230] In some examples, a specific TWT schedule may correspond to a specific set of request parameters (or specific request information) included in a consultation request frame. For example, a specific TWT schedule may be an R-TWT schedule. Such an R-TWT schedule may be identified by broadcast TWT identification information.

[0231] In some examples, when the first information is set to a value representing an alternative, a set of request parameters by the first AP may be included in the consultation response frame. The set of request parameters by the first AP may correspond to a set of parameters that the first AP rejects but the first AP can accept.

[0232] In some examples, when the first information is set to a value indicating acceptance or rejection, the request parameter set may not be included in the consultation response frame. For example, when the first AP's acceptance / rejection of specific request information (or request parameter set) requested by the second AP is indicated in the consultation request frame, the parameter set requested by the first AP may not need to be included in the consultation response frame.

[0233] The method described in the example of FIG. 15 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) (or the first AP) of FIG. 1 may be configured to receive a consultation request frame for MAPC from the second device (200) through one or more transceivers (106) and to transmit a consultation response frame for MAPC to the second device (200) through one or more transceivers (106). Furthermore, one or more memories (104) of the first device (100) may store instructions for performing the method described in the example of FIG. 15 or the examples described below when executed by one or more processors (102).

[0234] For example, when a PPDU is received from a second device (200) through one or more transceivers (106), one or more processors (102) of the first device (100) can parse a MAC frame obtained through PHY decoding of the data field of the PPDU, obtain information regarding a cooperation / consultation request based on the decoded data from the parsed MAC frame, and determine whether to accept the cooperation / consultation for a specific R-TWT schedule by utilizing the cooperation TWT ID. Additionally, the processor (102) can generate a cooperation / consultation response including a status code for accepting or rejecting the specific R-TWT schedule by utilizing the cooperation TWT ID included in the cooperation / consultation request. Alternatively, when recommending / proposing an alternative for the specific R-TWT schedule of the cooperation / consultation request, the processor can generate a cooperation / consultation response including a parameter set in which some or all of the values ​​of the parameter set of the R-TWT schedule corresponding to the cooperation TWT ID have been changed. The processor (102) can generate a MAC frame corresponding to a cooperation / consultation response and generate a PPDU containing it and transmit it to a second device (200) through one or more transceivers (106).

[0235] FIG. 16 is a drawing illustrating an example of the operation of a second AP according to the present disclosure.

[0236] In step S1610, the second AP can send a consultation request frame for the MAPC to the first AP.

[0237] In step S1620, the second AP can receive a consultation response frame for the MAPC from the first AP.

[0238] In the example of FIG. 16, the specific descriptions of the first AP, the second AP, the consultation request frame, the consultation response frame, and the first information and second information included in the consultation response frame are the same as those in the example of FIG. 15, so redundant descriptions are omitted.

[0239] The method described in the example of FIG. 16 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 (e.g., the second AP) may be configured to receive a consultation request frame for MAPC from the first device (100) through one or more transceivers (206) and to transmit a consultation response frame for MAPC to the first device (100) through one or more transceivers (206). Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 16 or the examples described below when executed by one or more processors (202).

[0240] For example, a processor (202) may generate a MAC frame corresponding to a cooperation / consultation request containing one or more request information (or information including one or more request parameter set information) and generate a PPDU containing the same and transmit it to a first device (100) through one or more transceivers (206). When a PPDU is received from the first device (100) through one or more transceivers (206), one or more processors (202) of the second device (200) may parse the MAC frame obtained through PHY decoding of the data field of the PPDU, obtain information regarding a cooperation / consultation response based on the decoded data from the parsed MAC frame, and verify the acceptance, rejection, or alternative proposal of the first device (100) regarding the cooperation / consultation request for a specific R-TWT schedule using a cooperation TWT ID.

[0241] The first AP in FIG. 15 corresponds to a transmitting STA (or requesting AP), and the second AP in FIG. 16 corresponds to a receiving STA (or response AP). For example, the transmitting STA may generate and transmit a cooperation / consultation request based on information regarding an R-TWT schedule (or R-TWT SP) to proceed with cooperation with the receiving STA before configuring the PPDU, information for consultation regarding the cooperation target, and information regarding the protection level for the R-TWT SP within the receiving STA's BSS. Based on the data included in the received cooperation / consultation request, the receiving STA may generate and transmit a cooperation / consultation response including a status code indicating acceptance / rejection for a specific R-TWT schedule by utilizing the cooperation TWT ID included in the cooperation / consultation request. When an alternative to a specific R-TWT schedule of a cooperation / consultation request from a sending STA is recommended / proposed, the receiving STA may generate and transmit a cooperation / consultation response containing a parameter set in which some / all values ​​of the parameter set of the R-TWT schedule corresponding to the cooperation TWT ID have been changed.

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

[0243] In the embodiments described below, examples of the present disclosure are explained by assuming two APs where neighbors or BSSs (partially) overlap, but the scope of the present disclosure is not limited thereto, and the examples of the present disclosure can be equally applied to the consultation process regarding the cooperation service period between three or more APs / BSSs.

[0244] In the following examples, the term "field" may be replaced with "subfield," and the term "subfield" may be replaced with "field." Additionally, in the following examples, the term "element" may be replaced with "subelement," and the term "subelement" may be replaced with "element."

[0245] Example 1

[0246] This embodiment relates to a general consultation process for R-TWT cooperation among APs.

[0247] As shown in Fig. 14, APs can perform consultation via wireless communication in a topology where the other party's BSS and their own BSS overlap. If wireless communication between APs is not possible, consultation may be performed via wired communication. Additionally, if there is a master AP of a MAP group to which the APs belong in common, wireless / wired consultation between APs may be performed through the master AP. For example, cooperation / consultation requests and cooperation / consultation responses in the examples described below may be transmitted / received through direct wireless / wired communication between APs, or indirectly transmitted / received through another AP (e.g., master AP).

[0248] In the present disclosure, it may be assumed that a consultation for cooperation is initiated whether the AP has prior knowledge of information regarding an R-TWT SP (or R-TWT schedule) scheduled by a neighboring AP or not. As a case where the AP obtains / shares information regarding the neighboring AP's R-TWT schedule in advance, for example, the case where the AP overhears the neighboring AP's beacon frame may be assumed, but the scope of the present disclosure is not limited to such a case.

[0249] In the examples described below, a request for cooperation may correspond to a request for consultation regarding cooperation and may simply be referred to as a request for consultation. Similarly, in the examples described below, a cooperation response may correspond to a consultation response regarding cooperation and may simply be referred to as a consultation response. Therefore, in the examples described below, a request for cooperation and a cooperation response may be replaced by a request for consultation and a consultation response, respectively.

[0250] In the examples of the present disclosure, the cooperation request and the cooperation response may be defined as a new frame or as a new element transmitted together with other information / elements.

[0251] In the examples of the present disclosure, it is assumed that the AP transmitting the cooperation request and the AP receiving the cooperation response correspond to one identical AP, and that the AP receiving the cooperation request and the AP transmitting the cooperation response correspond to another identical AP. However, the scope of the present disclosure may include cases where the AP transmitting the cooperation request and the AP receiving the cooperation response correspond to different APs, and / or cases where the AP receiving the cooperation request and the AP transmitting the cooperation response correspond to different APs.

[0252] In the present disclosure, an AP can determine / obtain a cooperative R-TWT (e.g., an R-TWT schedule subject to cooperation between APs) based on the result of wireless / wired consultation for cooperation regarding an R-TWT SP with neighboring APs.

[0253] For example, the consultation process for cooperation between an AP (e.g., AP1) and a neighboring AP (e.g., AP2) can be carried out in a 2-way manner as follows.

[0254] Step 1) AP1 sends a cooperation request to neighbor AP2.

[0255] Step 2) Neighbor AP2, having received the cooperation request, sends a cooperation response to AP1, which sent the cooperation request.

[0256] Based on the results of the consultation, R-TWT SP(s) may be classified into cooperative R-TWT SPs or non-cooperative (or non-cooperative) R-TWT SPs.

[0257] For example, if the status code included in the cooperation response in Step 2 indicates acceptance of the request in Step 1, it is interpreted that the consultation for cooperation has been successfully completed, and the R-TWT SP can be considered as a cooperative R-TWT SP between the AP participating in the consultation and a neighboring AP.

[0258] Alternatively, if the status code included in the cooperation response in Step 2 indicates a rejection of the request in Step 1, the AP may resend the cooperation request to a neighboring AP. In this case, the information of the R-TWT SP included in the cooperation request sent in Step 1 during the previous consultation process, or information that is identical or changed, may be included in the resent cooperation request. If the last cooperation response received from the neighboring AP during the consultation process following the resent consultation request indicates a rejection, the consultation is interpreted as rejected (or failed), and the R-TWT SP may be considered a non-cooperative R-TWT SP between the AP participating in the consultation and the neighboring AP.

[0259] Alternatively, the status code included in the cooperation response in Step 2 may not be an acceptance of the request in Step 1 but may include a proposal (e.g., REJECTED_WITH_SUGGESTED_CHANGES). In this case, the AP sending the cooperation response may send a value containing its own proposal through the cooperation response based on the values ​​included in the received cooperation request.

[0260] As another example, the consultation process for cooperation between an AP (e.g., AP1) and a neighboring AP (e.g., AP2) may be carried out in a 3-way manner as follows.

[0261] Step 1) AP1 sends the first cooperation request to neighbor AP2.

[0262] Step 2) Neighbor AP2, having received the cooperation request, may send a first cooperation response to AP1, which sent the cooperation request, and may include a second cooperation request containing R-TWT information scheduled by neighbor AP2, which sent the cooperation request, within the frame containing the first cooperation response.

[0263] Step 3) AP1, having received a frame containing a first cooperation response and a second cooperation request, can transmit a second cooperation response to the second cooperation request to neighbor AP2.

[0264] Example 2

[0265] This embodiment relates to a method for signaling cooperative responses during the consultation process for R-TWT cooperation among APs.

[0266] FIG. 17 shows examples of configurations of status information and TWT identification information included in a cooperation / consultation response according to the present disclosure.

[0267] For a specific R-TWT included in a cooperation request, an AP receiving the cooperation request may include a new (sub)field in the cooperation response indicating a status code meaning acceptance / rejection / alternative, etc. Such new (sub)field may be referred to as a status list (sub)field, but the scope of the present disclosure is not limited by such name.

[0268] A single status list field may include a TWT ID field and a status field. The TWT ID field may include the ID of the TWT schedule being collaborated on (or the R-TWT schedule subject to consultation for collaboration). The status field may include information indicating acceptance / rejection / alternative for a specific TWT schedule (e.g., an R-TWT schedule) identified by the TWT ID field.

[0269] As exemplified in FIG. 17(a), one TWT ID field and one state field can be associated with each other as a combination or pair. For example, one TWT ID field and one state field can form a tuple. A state list field may contain only one combination / pair / tuple of the TWT ID field and one state field, or it may contain multiple such combinations / pairs / tuples.

[0270] Within a single state list field, one TWT ID field and one state field associated with each other may be configured as fields at consecutive positions or as fields at discontinuous positions. For example, a single state list field may include additional other field(s) in addition to the TWT ID field and the state field. Within a single state list field, one combination / pair / tuple of one TWT ID field and one state field associated with each other and another combination / pair / tuple may be located consecutively or discontinuously.

[0271] The status list field may be defined as a field within the frame corresponding to the cooperation response, or as an element within the frame corresponding to the cooperation response.

[0272] In the TWT ID field, the TWT ID refers to an ID having a unique value that distinguishes the schedules of R-TWTs being negotiated between APs (e.g., negotiations regarding cooperation). For example, a TWT ID within a broadcast TWT parameter set field (or individual TWT parameter set field) containing information on the schedule of the R-TWTs being negotiated may be used as the TWT ID being cooperated with. For example, the value of a single TWT ID field included in a cooperation response may correspond to one of the ID(s) of the R-TWT schedule(s) scheduled by the AP sending the cooperation request. For example, the TWT ID field may be defined as having a length of 5 bits.

[0273] The status field may include a specific value (e.g., an index or bitmap) or a status code value indicating acceptance / rejection / alternative for a cooperation request for a specific R-TWT schedule identified by the TWT ID field. For example, if a status code defined in the existing method is utilized, the status field may be defined with a length of 2 octets (or 16 bits). Alternatively, the status field indicating a specific value indicating acceptance / rejection / alternative may be defined with a length of 1 octet, 1 bit, 2 bits, or 3 bits, which is a value smaller than 2 octets.

[0274] If the status code is set to a value corresponding to success, acceptance, or confirmation, it may indicate that cooperation / consultation regarding a specific R-TWT schedule (or a parameter set corresponding to a specific R-TWT) included in the cooperation request has been successfully achieved. In this case, elements / fields (e.g., TWT elements and / or broadcast TWT parameter set fields) containing information about the specific R-TWT schedule identified by the TWT ID within the cooperation response (e.g., a parameter set corresponding to a specific R-TWT) may not be included within the cooperation response.

[0275] If the status code is set to a value corresponding to a meaning such as reject or deny, it may indicate that cooperation / consultation regarding a specific R-TWT schedule (or a parameter set corresponding to a specific R-TWT) included in the cooperation request has failed. In this case, elements / fields (e.g., TWT elements and / or broadcast TWT parameter set fields) containing information about the specific R-TWT schedule identified by the TWT ID within the cooperation response (e.g., a parameter set corresponding to a specific R-TWT) may not be included within the cooperation response.

[0276] If the status code is set to a value corresponding to meanings such as alternate, suggest, or recommend, it may indicate that cooperation / consultation regarding a specific R-TWT schedule (or a parameter set corresponding to a specific R-TWT) included in the cooperation request is rejected (or not ultimately rejected), but there is an intention to consult based on the proposed values. In this case, an element / field (e.g., a TWT element and / or a broadcast TWT parameter set field) containing information about a specific R-TWT schedule identified by a TWT ID within the cooperation response (e.g., a parameter set corresponding to a specific R-TWT) may be included within the cooperation response.

[0277] For example, the parameter set for a specific TWT schedule identified by a specific TWT ID included in the cooperation response is the parameter set for a specific TWT schedule identified by the same TWT ID included in the cooperation request, but some or all of the values ​​of the parameter set included in the cooperation response may be changed compared to some or all of the parameter set included in the cooperation request.

[0278] For example, within the cooperation response, the parameter set field for a specific TWT schedule may be located after the state list field in the example of FIG. 17(a). Accordingly, based on the value of the state field within the state list field, it may be implied that a parameter set field corresponding to a cooperating TWT ID exists.

[0279] Additionally or alternatively, if the status field indicates a value corresponding to rejection / denial or alternative / proposal / recommendation, a reason code field indicating the reason for the failure of R-TWT cooperation / consultation between APs may be additionally defined. The reason code field may utilize reason codes defined in the existing method, but is not limited thereto. For example, reason codes that may occur regarding cooperation / consultation between APs may be defined separately or additionally and may be indicated through the corresponding reason code field. If reason codes that may occur regarding cooperation / consultation between APs are defined separately, the corresponding reason code field may have a length less than or equal to 2 octets. Alternatively, if reason codes from the existing method are used as is or are additionally defined, the length of the reason code field may be 2 octets. Additionally, the reason code field may be located immediately after the status field, as a separate field rather than a sub-field of the status list field, or the reason code field may be located instead of the status field, when the value of the status field in the examples of FIGS. 17(a) and (b) indicates a value corresponding to rejection / rejection or alternative / suggestion / recommendation. In this case, the field / element containing the reason code field may be configured together with the examples of FIGS. 17(a) and (b) or as a separate, standalone field / element.

[0280] As another example, a specific field within the cooperation response frame may indicate the reason why the result of the R-TWT consultation between APs corresponds to a rejection / denial / proposal. For example, this specific field may correspond to a status code field within the cooperation response frame, or it may correspond to an unused or reserved field within the cooperation response frame. The reason indicated by the specific field may be defined as a new status code indicating a rejection / denial by one or more of the reasons listed below. Among the values ​​defined in the existing status code, reserved values ​​(e.g., 8, 9, 20, 21, 36, 48, 66, 71, 90, 91, 114, 115, 127, 130 to 135, 139 to 142, 144 to 65535) may be used as new status codes.

[0281] - Among the STAs combined with the response AP, there are no STAs that support R-TWT.

[0282] - The channel and / or bandwidth where the R-TWT SP requested by the requesting AP operates does not overlap with the channel and / or bandwidth used by the responding AP.

[0283] - The R-TWT SP requested by the requesting AP overlaps / overlaps with the R-TWT SP scheduled by the responding AP or the SP scheduled to send an urgent frame for some or all duration.

[0284] - The signal strength, etc. of frames transmitted and received by the requesting AP or / and combined STAs located within the requesting AP's BSS does not affect the response AP or / and combined STAs located within the response AP's BSS. For example, the signal strength of the received or decoded signal (e.g., SINR, etc.) does not exceed a detection threshold defined by the system (e.g., packet detection level or energy detection level).

[0285] - The value of the R-TWT schedule information field does not indicate that it is an active R-TWT schedule.

[0286] Example 2-1

[0287] Referring to FIG. 17(a), an example of the configuration of a cooperation response including a status field indicating acceptance / rejection / alternative to a cooperation request is described.

[0288] Although not shown in FIG. 17(a), a count (sub)field may be positioned before the state list field. Alternatively, the count field may correspond to the first field within the state list field. The count field may indicate the number of combinations / pairs / tuples contained within the state list field (e.g., combinations / pairs / tuples of the TWT ID field and the associated state field) or the total length of the state list field. Accordingly, an AP receiving the cooperative response (e.g., a requesting AP) can recognize the number of combinations / pairs / tuples or the length of the state list field.

[0289] For example, an AP that receives a cooperation request may construct a cooperation response containing one (e.g., a total of N) TWT ID-state combination / pair / tuple for each of the N R-TWT schedules included in the cooperation request. In this case, the value of the count field may be set to N.

[0290] If the length of the count field is 3 bits, it may mean that a TWT parameter set field containing information on up to 8 R-TWT schedules may be included in the Co-RTWT request frame. For example, an AP sending a cooperation response may set the value of the count field to a maximum of 8 based on the number of R-TWT schedules included in the cooperation request. For example, if the value of the count field indicates 3, it may indicate that 3 pairs of TWT ID fields and status fields follow.

[0291] If the length of the count field is 4 bits, it may mean that a TWT parameter set field containing information on up to 16 R-TWT schedules may be included in the Co-RTWT request frame. For example, an AP sending a cooperation response may set the value of the count field to a maximum of 16 based on the number of R-TWT schedules included in the cooperation request. For example, if the value of the count field indicates 10, it may indicate that 10 pairs of TWT ID fields and status fields follow.

[0292] As another example, a count field can be defined with a size of X (=N+M) bits. The N bits may correspond to N consecutive bits from the beginning (or from the least significant bit (LSB)). The M bits may correspond to the remaining bits excluding N from the X bits. The N bits correspond to the maximum number of bits that can actually be set to a value, and the remaining M bits (e.g., M is a value greater than or equal to 1) may be set to a reserved value (e.g., 0) to serve as a boundary between the count field and a subsequent field (e.g., a state list field).

[0293] Additionally or alternatively, since the AP receiving the cooperation request configures the state fields in the state list based on the number of TWT parameter set fields indicating the R-TWT schedule included in the cooperation request, it can be assumed that the AP sending the cooperation request is aware of the number of R-TWT parameter set fields. For this reason, the cooperation response may not include information on a count indicating the number of state fields.

[0294] Additionally or alternatively, if the count field does not exist in the example of FIG. 17(a), the length of the status list field may be predefined or set to a fixed value (e.g., 6*A, where A is an integer between 1 and 32). For example, assuming that a cooperation request may contain up to 32 R-TWT schedules, the status list field in the cooperation response may be configured with bits of a length that can contain 32 pairs of TWT ID fields and status fields. If a cooperation request contains 3 R-TWT schedules, the status list field in the cooperation response may contain 3 pairs of TWT ID fields and status fields, and the remaining bits may all be set to reserved bits (e.g., 0).

[0295] Example 2-2

[0296] Referring to FIG. 17(b), another example of the configuration of a cooperation response including a status field indicating acceptance / rejection / alternative to a cooperation request is described.

[0297] In the example of FIG. 17(b), unlike the example of FIG. 17(a), the TWT ID field may not exist within the state list field. For example, a single state list field may contain one state field or multiple state fields. For example, multiple state fields may be located consecutively.

[0298] For example, the number of state fields within the state list field may be equal to the number of parameter set fields for the requested R-TWT schedule within the cooperation request frame. In this case, the parameter set fields for each R-TWT schedule corresponding to each state field may follow the decoding order. For example, in the example of FIG. 17(b), the state 1 field may be set to a value indicating the state (e.g., accept / reject / alternative) for the parameter set field (or corresponding R-TWT schedule) that is decoded first (or located first) within the field / element for R-TWT cooperation in the cooperation request frame. Similarly, the state 2 field may be set to a value indicating the state (e.g., accept / reject / alternative) for the parameter set field (or corresponding R-TWT schedule) that is decoded second (or located second) within the field / element for R-TWT cooperation in the cooperation request frame.

[0299] Although not illustrated in FIG. 17(b), a count (sub)field may be positioned before the status list field. Alternatively, the count field may correspond to the first field within the status list field. The count field may indicate the number of status fields included within the status list field or the total length of the status list field. If the cooperation request contains request information for N R-TWT schedules, the AP receiving the cooperation request may include N status fields corresponding to the N request information in the status list field within the cooperation response. In this case, the value of the count field may be set to N.

[0300] If the length of the count field is 3 bits, it may mean that a TWT parameter set field containing information on up to 8 R-TWT schedules may be included in the Co-RTWT request frame. For example, an AP sending a cooperation response may set the value of the count field to a maximum of 8 based on the number of R-TWT schedules included in the cooperation request. For example, if the value of the count field indicates 3, it may indicate that 3 status fields follow.

[0301] If the length of the count field is 4 bits, it may mean that a TWT parameter set field containing information on up to 16 R-TWT schedules may be included in the Co-RTWT request frame. For example, an AP sending a cooperation response may set the value of the count field to a maximum of 16 based on the number of R-TWT schedules included in the cooperation request. For example, if the value of the count field indicates 10, it may indicate that 10 status fields follow.

[0302] As another example, a count field can be defined with a size of X (=N+M) bits. The N bits may correspond to N consecutive bits from the beginning (or from the LSB). The M bits may correspond to the remaining bits excluding N from the X bits. The N bits correspond to the maximum number of bits that can actually be set to a value, and the remaining M bits (e.g., M is a value greater than or equal to 1) may be set to a reserved value (e.g., 0) to serve as a boundary between the count field and a subsequent field (e.g., a state list field).

[0303] Additionally or alternatively, since the AP receiving the cooperation request configures the state fields in the state list based on the number of TWT parameter set fields indicating the R-TWT schedule included in the cooperation request, it can be assumed that the AP sending the cooperation request is aware of the number of R-TWT parameter set fields. For this reason, the cooperation response may not include information on a count indicating the number of state fields.

[0304] Additionally or alternatively, if the count field does not exist in the example of FIG. 17(b), the length of the status list field may be predefined or set to a fixed value (e.g., an integer between 1 and 32). For example, assuming that a cooperation request may contain up to 32 R-TWT schedules, the status list field in the cooperation response may be configured with bits of a length that can contain 32 status fields. If a cooperation request contains 3 R-TWT schedules, the status list field in the cooperation response may contain 3 status fields, and the remaining bits may all be set to reserved bits (e.g., 0).

[0305] Example 3

[0306] This embodiment relates to examples of the operation of a transmitting STA (e.g., a request STA) and a receiving STA (e.g., a response STA).

[0307] FIG. 18 is a diagram illustrating the process of sending and receiving a request for consultation on cooperation between APs and a response for consultation on cooperation according to the present disclosure.

[0308] In the examples of the present disclosure, a process is described regarding an AP conducting consultation on R-TWT cooperation for obtaining an R-TWT that is cooperated with a neighboring AP. For example, it is assumed that one AP can receive a beacon frame from a neighboring AP, and that the neighboring AP is located in a position where it can receive a beacon frame from one AP.

[0309] As shown in the example of FIG. 18, one AP (e.g., requesting AP) sends a cooperation / consultation request containing information about an R-TWT SP to be consulted to a neighboring AP (e.g., responding AP), and the neighboring AP (e.g., responding AP) can send a cooperation response containing information such as a status code for the R-TWT schedule based on the R-TWT schedule included in the received cooperation request. Based on the value of the status code in the cooperation response, it can be indicated whether cooperation / consultation for each R-TWT schedule was successfully carried out.

[0310] If the value of the status code (sub)field within the status list (sub)field of a cooperative response transmitted by a neighbor AP has a value indicating success / acceptance / acceptance, the R-TWT schedule corresponding to the cooperative TWT ID associated with that status code (sub)field (e.g., forming a single combination / pair / tuple or corresponding to a decoding / batch order) can be determined / obtained as the cooperative R-TWT SP between the AP and the neighbor AP.

[0311] If the value of the status code (sub)field within the status list (sub)field of a cooperative response transmitted by a neighbor AP has a value indicating rejection / denial, the R-TWT schedule corresponding to the cooperative TWT ID associated with that status code (sub)field (e.g., forming a combination / pair / tuple or corresponding to a decoding / batch order) cannot be determined / acquired as the cooperative R-TWT SP between the AP and the neighbor AP.

[0312] If the value of the status code (sub)field within the status list (sub)field of a cooperation response transmitted by a neighbor AP has a value signifying an alternative / proposal / recommendation, information regarding the R-TWT schedule corresponding to the cooperating TWT ID associated with that status code (sub)field (e.g., forming a single combination / pair / tuple or corresponding to a decoding / batch order) (e.g., the parameter set field requested by the responding AP) may be added to the cooperation response and transmitted. Based on this, the AP and the neighbor AP can perform frame exchange for additional R-TWT cooperation.

[0313] Example 4

[0314] This embodiment relates to examples utilizing TWT information extension elements.

[0315] FIG. 19 is a drawing showing examples of TWT information extension elements according to the present disclosure.

[0316] For consultation regarding an R-TWT schedule, a parameter set for a specific R-TWT schedule (e.g., a cooperating R-TWT schedule) may be transmitted / received between the requesting AP and the responding AP. To this end, the cooperation / consultation response frame includes a TWT information extension element, and the TWT information extension element may include information (e.g., a parameter set) regarding the cooperating R-TWT schedule.

[0317] In the examples of FIG. 19, the TWT information extension element may include information of the R-TWT schedule in the parameter set field. The scope of the present disclosure is not limited thereto, and examples in which information for one or more R-TWT schedules (e.g., parameter sets) described in the present disclosure is included in an element of a different name / format, rather than a TWT information extension element of the format of the examples of FIG. 19, are also included within the scope of the present disclosure.

[0318] In the examples of FIG. 19, the TWT information field may correspond to a broadcast TWT information (B-TWT information) field. For example, the TWT information field may include a broadcast TWT ID field (e.g., a field carrying the identifier of an R-TWT schedule), and / or a response status field.

[0319] In the examples of FIG. 19, the parameter set field may correspond to an individual TWT parameter set field, a broadcast TWT parameter set field, or a new parameter set field of a different name / format.

[0320] In the example of FIG. 19(a), the control field may include a TWT information presence field indicating whether the TWT information field exists within the element. For example, if the value of the TWT information presence field is set to exist (e.g., 1), the TWT information field may be included after the control field, and if the value is set to not exist (e.g., 0), the TWT information field may not be included.

[0321] In the example of FIG. 19(a), the control field may include a parameter set existence field indicating whether a parameter set field exists within the element. For example, if the value of the parameter set existence field is set to exist (e.g., 1), the parameter set field may be included after the control field or after the TWT information field, and if the value is set to not exist (e.g., 0), the parameter set field may not be included.

[0322] Examples regarding the presence or absence of the TWT information field and the parameter set field, respectively, are described below. In the examples of the present disclosure regarding signaling methods through cooperation / consultation responses, the following examples may be applied without limiting the cases where the TWT information field exists in the response or where it does not.

[0323] Referring to FIG. 19(b), when the value of the TWT information existence field indicates that it exists and the value of the parameter set existence field indicates that it exists, the parameter set field may contain parameter set information for a specific TWT schedule identified by the value indicated in the broadcast TWT ID subfield within the TWT information field.

[0324] As shown in the example of FIG. 19(c), a response AP that receives a cooperation request may transmit a cooperation response containing a field (e.g., a status field) that indicates whether to cooperate with a specific R-TWT schedule included in the cooperation request. The status field may indicate acceptance / rejection / alternative and may be included, for example, in the remaining bits other than the broadcast ID field of the TWT information. If the size of the status field is N bits, the remaining bits excluding N bits out of 3 bits may be reserved. If the size of the status field is 2 bits, 1 bit may be reserved.

[0325] In the example of FIG. 19(c), the status field is shown to be included within the TWT information field, but the scope of the present disclosure is not limited thereto, and the status field may be included in other locations within the element containing the broadcast TWT ID field (e.g., a reserved bit within the control field, or other fields other than the control field and the TWT information field), so that a specific R-TWT schedule identified by the broadcast TWT ID field and an acceptance / rejection / alternative indicated by the status field may be associated.

[0326] For example, if the value of the status field is set to 0, it means none, and if the value of the status field is set to a value of 1 or more, it may indicate acceptance, rejection, or alternative depending on the value.

[0327] Although not illustrated in FIG. 19, when the value of the status field is set to a value corresponding to an alternative (or suggestion / recommendation), a parameter set field may be included within the element containing the broadcast TWT ID field (e.g., following the TWT information field). In this case, the value of the parameter set presence field within the control field may be set to 1.

[0328] FIG. 20 is a drawing showing additional examples of TWT information extension elements according to the present disclosure.

[0329] Referring to FIG. 20(a), when the value of the TWT information existence field indicates that there is no value and the value of the parameter set existence field indicates that there is a value, the parameter set field may include parameter set(s) based on information about (R-)TWT schedule(s) that are subject to consultation for cooperation.

[0330] For example, elements such as the example in FIG. 20(a) may be included in the cooperation request frame. Accordingly, the requesting AP may provide the responding AP with a set of parameters for the R-TWT(s) that are the target of the R-TWT cooperation request.

[0331] For example, a response AP that receives a cooperation request frame can transmit information indicating whether to cooperate (e.g., accept / reject / alternative) with respect to the R-TWT schedule included in the cooperation request through a cooperation response frame. For example, the response AP can include a parameter set field of a specific (R-)TWT schedule included in the cooperation request in the cooperation response frame and use a TWT setup command subfield within the parameter set field to indicate whether to cooperate (e.g., accept / reject / alternative).

[0332] Within the response frame, status information indicating acceptance, rejection, or alternatives to request information for a specific R-TWT schedule is contained within a single element and associated with a field identifying the specific R-TWT schedule (e.g., a broadcast TWT ID field), but is not necessarily limited to being in consecutive fields or within the same field. For example, if they have a structure where they are clearly associated within a single element (e.g., contained in the same parent field or in the same element / sub-element), the broadcast TWT ID information and the status information may be contained in separate locations or in different fields.

[0333] Referring to FIG. 20(b), a state list existence field may be added to the control field within the element. When the state list existence field is set to a value indicating that it exists (e.g., 1), the state list field is included within the element, and when it is set to a value indicating that it does not exist (e.g., 0), the state list field is not included within the element.

[0334] The status list field of FIG. 20(b) may include one or more status fields without a broadcast TWT ID field, as in the example of FIG. 17(b). For example, the response AP may apply the order of status field(s) included in the cooperation response according to the order in which the parameter set field(s) of the (R-)TWT schedule(s) included in the received cooperation request are decoded. If request information (e.g., request parameter sets) for N R-TWT schedules within the cooperation request is included, the status list within the cooperation response may include N status fields. If a status field indicates only acceptance or rejection, each status field may be defined with a size of 1 bit. If a status field indicates acceptance, rejection, or alternative, each status field may be defined with a size of 2 bits. If a specific status field indicates an alternative / proposal / recommendation, a parameter set field for the R-TWT schedule indicating the alternative / proposal / recommendation may be included after the status list field.

[0335] The length of the status list field can be indicated in the following way.

[0336] - By utilizing reserved bits within the control field, the length of the state list field or the number of state fields included in the state list (or the number of combinations / pairs / tuples of the broadcast TWT ID field and the state field) can be indicated.

[0337] - The first subfield within the state list field may indicate the length of the state list field or the number of state fields included in the state list (or the number of combinations / pairs / tuples of the broadcast TWT ID field and the state field).

[0338] If the status information included in the cooperation response corresponds to an alternative (or proposal / recommendation), the value(s) of the parameter set for a specific R-TWT schedule included in the cooperation request may be modified and included in the cooperation response. In this case, the parameter set existence field within the control field may be set to a value indicating existence.

[0339] Alternatively, if the response AP intends to include a parameter set corresponding to an alternative / proposal / recommendation for a specific R-TWT schedule included in the received cooperation request, the status field for that R-TWT schedule may not be indicated. For example, a cooperation response including an alternative can provide parameter information for the R-TWT schedule corresponding to the alternative / proposal / recommendation through subsequent field(s) by setting the TWT setup command subfield within the parameter set field to a value corresponding to the alternative. When this method is applied, the status field included in the response frame may be defined to indicate only acceptance or rejection, and accordingly, may be defined as having a size of 1 bit.

[0340] In the example of FIG. 20(b), when the response AP indicates whether to cooperate (e.g., accept / reject / alternative) for a specific (R-)TWT schedule included in the received cooperation request, it can be configured to associate the Broadcast TWT ID (or Cooperation R-TWT ID), which is identification information indicating the specific (R-)TWT schedule included in the cooperation request, with the cooperation status (e.g., accept / reject / alternative) for that specific (R-)TWT schedule. For example, within the response frame, one Broadcast TWT ID field for one R-TWT schedule and one associated state field may be included in the form of a combination / pair / tuple within a single element. If N sets of parameters corresponding to N Broadcast TWT IDs are included in the cooperation request, N combinations / pairs / tuples of the Broadcast TWT ID field and the state field may be included in the response frame.

[0341] When the state field within the cooperative response frame is set to a value corresponding to an alternative / proposal / recommendation, the parameter set (as many times as the number of R-TWT schedules corresponding to the alternative) in the example of FIG. 20(b) may be included after the state list field. In this case, the value of the parameter set existence field may be set to 1.

[0342] Referring to FIG. 20(c), a new field (e.g., All field) indicating whether the response AP directs acceptance / rejection / alternative for each of the R-TWT schedules included in the received cooperation request may be included in the control field.

[0343] If the value of the All field is 0, it means none, and among the values ​​of 1 or more, one may indicate acceptance of all, another may indicate rejection of all, and yet another may indicate alternatives.

[0344] The size of the remaining reserved bits in the control field can be determined by the length of the All field. If the size of the All field is 2 bits, the reserved bits can be 3 bits.

[0345] When the All field is set to a value corresponding to all alternatives (e.g., rejecting all and presenting all alternative / proposal / recommendation parameter sets), the parameter set field may be located after the control field in the example of FIG. 20(c). In this case, the parameter set existence field within the control field may be set to a value indicating existence (e.g., 1).

[0346] Alternatively, the responding AP may send a response that does not present alternatives for all R-TWT schedules included in the received cooperation request, but presents alternative parameters for a specific R-TWT schedule. In this case, the value of the All field in FIG. 20(c) may be set to 0, or the All field may not exist. In this case, a parameter set field exists within the element, and by setting the TWT setup command field within the parameter set field corresponding to the specific R-TWT schedule to a value indicating an alternative, parameter set information for that specific R-TWT schedule may be provided through the subsequent field(s).

[0347] In existing wireless LAN systems, regarding cooperation between APs on R-TWT schedules, there is no specific method provided for a responding AP receiving information requested by a requesting AP to signal a response regarding cooperation. According to the present disclosure, a consultation response can be efficiently configured to signal acceptance, rejection, alternative, etc., of a responding AP regarding a specific TWT schedule(s) for which cooperation is requested.

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

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

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

[0351] 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 receiving a negotiation request frame for multi-access point (AP) coordination from the second AP by the first AP; and It includes the step of transmitting a consultation response frame for multi-AP cooperation to the second AP by the first AP, The above consultation request frame includes one or more request information including one or more sets of request parameters, and The above consultation response frame includes one first piece of information indicating acceptance, rejection, or alternative for each of the one or more request information included in the above consultation request frame, and The above-mentioned first information is associated with a specific target wake time (TWT) schedule, a method.

2. In Paragraph 1, A method in which the above consultation response frame further includes second information including identification information of the specific TWT schedule.

3. In Paragraph 2, A method in which the first information and the second information are included in one specific element within the consultation response frame.

4. In Paragraph 3, A method in which the above consultation response frame includes, for each of the one or more request information included in the above consultation request frame, the one specific element including the first information and the second information.

5. In Paragraph 1, A method wherein the above one or more request parameter sets include one or more request parameter sets for a coordinated R-TWT.

6. In Paragraph 1, The above specific TWT schedule is an R-TWT schedule, a method.

7. In Paragraph 6, The above R-TWT schedule is determined by broadcast TWT identification information, a method.

8. In Paragraph 1, A method in which a set of request parameters by the first AP is included in the consultation response frame, based on the first information being set to a value representing an alternative.

9. In Paragraph 8, A method in which, based on the first information being set to a value indicating acceptance or rejection, the request parameter set is not included in the consultation response frame.

10. In Paragraph 1, The above-mentioned first AP is a multi-AP cooperative response AP, and The above second AP is a multi-AP cooperation request AP, method.

11. 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 consultation request frame for multi-access point (AP) cooperation from a second AP through one or more of the transceivers; and It is configured to transmit a consultation response frame for multi-AP cooperation to the second AP through the one or more transceivers, and The above consultation request frame includes one or more request information including one or more sets of request parameters, and The above consultation response frame includes one first piece of information indicating acceptance, rejection, or alternative for each of the one or more request information included in the above consultation request frame, and The above-mentioned first information is a first AP associated with a specific target wake time (TWT) schedule.

12. A step of transmitting a consultation request frame for multi-access point (AP) cooperation to the first AP by the second AP; and It includes the step of receiving a consultation response frame for multi-AP cooperation from the first AP by the second AP, and The above consultation request frame includes one or more request information including one or more sets of request parameters, and The above consultation response frame includes one first piece of information indicating acceptance, rejection, or alternative for each of the one or more request information included in the above consultation request frame, and The above-mentioned first information is associated with a specific target wake time (TWT) schedule, a method.

13. 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 consultation request frame for multi-access point (AP) cooperation to the first AP through the one or more transceivers; and It is configured to receive a consultation response frame for multi-AP cooperation from the first AP through the one or more transceivers, and The above consultation request frame includes one or more request information including one or more sets of request parameters, and The above consultation response frame includes one first piece of information indicating acceptance, rejection, or alternative for each of the one or more request information included in the above consultation request frame, and The above-mentioned first information is a second AP associated with a specific target wake time (TWT) schedule.

14. 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 10 based on execution by one or more processors.

15. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the execution of a method according to any one of claims 1 through 10.

Images