Method and device for configuring management frame for updating information for MAPC on basis of public action frame in wireless LAN system

Abstract

Proposed are a method and a device for configuring a management frame for updating information for MAPC on the basis of a public action frame in a wireless LAN system. Specifically, a first AP configures a first management frame for updating information for MAPC. The first AP transmits the first management frame to a second AP. The first and second APs are a sharing AP controlling the MAPC or a coordinated AP having a resource allocated thereto or shared therewith by / from the sharing AP. The first management frame includes a public action frame. The public action frame includes information related to a TXOP period that the coordinated AP desires to be shared therewith.

Description

Method and device for configuring a management frame for updating information for MAPC based on a common action frame in a wireless LAN system

[0001] The present invention relates to a technique for configuring a management frame for updating information for MAPC based on a common action frame in a wireless LAN system, and more specifically, to a method and device for notifying or transmitting information related to multi-AP cooperation based on the management frame.

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs. To achieve this, various technologies are being considered to support high throughput, low latency, and extended range. For example, multiple APs can cooperate to perform TXOP sharing procedures.

[0003] The present specification proposes a method and device for configuring a management frame for updating information for MAPC based on a common action frame in a wireless LAN system.

[0004] An example of this specification proposes a method for constructing a management frame for updating information for MAPC based on a common action frame.

[0005] The present embodiment can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0006] The present embodiment is performed in a first AP, and the first AP may be set as a shared AP (DAP) or a coordinated AP after negotiation in multi-AP communication, and the second AP may be set as a sharing AP (SAP) after negotiation in multi-AP communication. The first and second non-AP STAs of the present embodiment may correspond to at least one STA (station).

[0007] The present embodiment proposes a method for performing multi-AP cooperation (e.g., Co-TDMA, Co-SR, Co-BF, C-OFDMA, or J-TX) by selecting APs that share TXOPs or perform inter-AP cooperation. In particular, the present embodiment proposes a method for notifying or transmitting information related to the multi-AP cooperation by defining a management frame based on a common action frame to update information for MAPC.

[0008] The first AP (access point) configures the first management frame to update (or renew) information for multi-AP coordination (MAPC).

[0009] The first AP transmits the first management frame to the second AP.

[0010] The first and second APs are either a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP.

[0011] The above first management frame includes a public action frame. The public action frame includes information regarding the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share.

[0012] Information about the TXOP period that the above-mentioned cooperative AP wishes to share may be set as a time in 16us units based on the Allocation Duration subfield of the User Information field of the MU-RTS (Multi User-Request To Send) TXS (TXOP Sharing) trigger frame, or may be set as the length of the PPDU (Physical Protocol Data Unit) required by the above-mentioned cooperative AP for the MAPC.

[0013] That is, the present embodiment proposes a method of defining a MAPC management frame based on the common action frame to update some information for the MAPC between APs participating in the MAPC.

[0014] Previously, there was no appropriate frame that could be used as a control frame when APs participating in the MAPC were not connected to each other. However, by defining the MAPC management frame based on the common action frame as in the present embodiment, request / response frames for multi-AP selection or information for MAPC can be transmitted and received between APs that are not connected under specific conditions or states, thereby enabling efficient MAPC operation.

[0015] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0016] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0017] Figure 3 is a diagram illustrating a general link setup process.

[0018] Figure 4 illustrates one embodiment of a multi-link (ML).

[0019] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0020] Figure 6 is a diagram showing the layout of resource units (RUs) used for 20MHz PPDU.

[0021] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0022] Figure 8 is a diagram showing the layout of resource units (RUs) used for 80MHz PPDU.

[0023] Figure 9 shows the operation according to UL-MU.

[0024] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0025] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0026] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0027] FIG. 13 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0028] Figure 14 illustrates operation according to a conventional STX operation.

[0029] Figure 15 illustrates an example of C-OFDMA (Coordinated OFDMA).

[0030] Figure 16 illustrates an example of CBF (Coordinated beamforming).

[0031] Figure 17 illustrates an example of AP selection.

[0032] Figure 18 shows an example of JTX / JT.

[0033] Figure 19 shows an example of the operation of a 2-day MU-RTS TXS trigger frame with a value of the TXOP Sharing Mode subfield.

[0034] Figure 20 shows an example of coordinated TDMA operation.

[0035] Figure 21 illustrates an example of a multi-AP selection procedure in Co-TDMA.

[0036] Figure 22 illustrates an example of responding to a BSRP TF with a (Public) Action frame.

[0037] Figure 23 illustrates an example of its use as a request / response frame for updating MAPC information.

[0038] Figure 24 illustrates an example of use as a 1-way frame for MAPC information update.

[0039] Figure 25 illustrates an example of its use as a frame for TXOP return in Co-TDMA.

[0040] Fig. 26 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0041] Fig. 27 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0042] FIG. 28 is a flowchart illustrating a procedure for a shared AP according to the present embodiment to receive a management frame for updating information for MAPC.

[0043] FIG. 29 is a flowchart illustrating a procedure for a cooperative AP according to the present embodiment to transmit a management frame for updating information for MAPC.

[0044] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0045] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0046] In this specification, “at least one of A and B” can mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” can be interpreted identically to “at least one of A and B.”

[0047] In addition, parentheses used in this specification may mean “for example.” Specifically, when “control information (UHR-Signal field)” is indicated, the “UHR-Signal field” may be suggested as an example of “control information.” In other words, the “control information” in this specification is not limited to the “UHR-Signal field,” and the “UHR-Signal field” may be suggested as an example of “control information.” In addition, even when indicated as “control information (UHR-Signal field),” the “UHR-Signal field” may be suggested as an example of “control information.”

[0048] Additionally, as used herein, “a / an” can mean “at least one” or “one or more.” Additionally, terms ending in “(s)” can mean “at least one” or “one or more.”

[0049] Additionally, the expressions “based on” or “on the basis of” or “according to” used herein mean “based at least in part on” and not “based solely on.”

[0050] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0051] The following examples of this specification can be applied to various wireless communication systems. For example, the following examples of this specification can be applied to wireless local area network (WLAN) systems. For example, the following examples of this specification can be applied to the IEEE 802.11a / g / n / ac / ax / be / bn standards. In addition, the examples of this specification can be applied to the Ultra High Reliability (UHR) standard or the next-generation wireless LAN standard that enhances IEEE 802.11bn. In addition, the examples of this specification can be applied to mobile communication systems. For example, the following examples of this specification can be applied to mobile communication systems based on the Long Term Evolution (LTE) and its evolution based on the 3rd Generation Partnership Project (3GPP) standard.

[0052] In order to explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0053] Figure 1 illustrates an example of a transmitting device and / or a receiving device of the present specification.

[0054] An example of FIG. 1 can perform various technical features described below. FIG. 1 relates to at least one STA (station). For example, the STA (110, 120) of the present specification may also be referred to by various names such as a mobile terminal, a wireless device, a Wireless Transmit / Receive Unit (WTRU), a User Equipment (UE), a Mobile Station (MS), a Mobile Subscriber Unit, or simply a user. The STA (110, 120) of the present specification may also be referred to by various names such as a network, a base station, a Node-B, an access point (AP), a repeater, a router, a relay, etc. The STA (110, 120) of the present specification may also be referred to by various names such as a receiving apparatus, a transmitting apparatus, a receiving STA, a transmitting STA, a receiving device, a transmitting device, etc.

[0055] For example, STA (110, 120) may perform the role of an AP (access point) or a non-AP role. That is, STA (110, 120) of the present specification may perform the functions of an AP and / or a non-AP. In the present specification, AP may also be indicated as an AP STA.

[0056] The STA (110, 120) of this specification can support various communication standards other than the IEEE 802.11 standard. For example, it can support communication standards according to the 3GPP standard (e.g., LTE, LTE-A, 5G NR standard). In addition, the STA of this specification can be implemented in various devices such as mobile phones, vehicles, and personal computers. In addition, the STA of this specification can support communication for various communication services such as voice calls, video calls, data communications, and autonomous driving (Self-Driving, Autonomous-Driving).

[0057] In this specification, STA (110, 120) may include a medium access control (MAC) and a physical layer interface for a wireless medium that follow the provisions of the IEEE 802.11 standard.

[0058] Based on the sub-drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0059] The first STA (110) may include a processor (111), a memory (112), and a transceiver (113). The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two blocks / functions may be implemented through a single chip.

[0060] The transceiver (113) of the first STA performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0061] For example, the first STA (110) can perform the intended operation of the AP. For example, the processor (111) of the AP can receive a signal through the transceiver (113), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (112) of the AP can store a signal received through the transceiver (113) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

[0062] For example, the second STA (120) can perform the intended operation of a non-AP STA. For example, the transceiver (123) of the non-AP performs signal transmission and reception operations. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0063] For example, the processor (121) of the Non-AP STA can receive a signal through the transceiver (123), process the received signal, generate a transmission signal, and perform control for signal transmission. The memory (122) of the Non-AP STA can store a signal received through the transceiver (123) (i.e., a reception signal) and store a signal to be transmitted through the transceiver (i.e., a transmission signal).

[0064] For example, in the specification below, the operation of a device indicated as AP may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is an AP, the operation of the device indicated as AP may be controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). In addition, control information related to the operation of the AP or a transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110). In addition, when the second STA (110) is an AP, the operation of the device indicated as an AP is controlled by the processor (121) of the second STA (120), and a related signal can be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the AP or the transmission / reception signal of the AP can be stored in the memory (122) of the second STA (110).

[0065] For example, in the specification below, the operation of a device indicated as a non-AP (or User-STA) may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is a non-AP, the operation of the device indicated as a non-AP may be controlled by the processor (121) of the second STA (120), and a related signal may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (122) of the second STA (120). For example, if the first STA (110) is a non-AP, the operation of a device indicated as a non-AP is controlled by the processor (111) of the first STA (110), and a related signal may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). In addition, control information related to the operation of the non-AP or the transmission / reception signal of the AP may be stored in the memory (112) of the first STA (110).

[0066] In the following specification, devices called (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, devices indicated as (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) Terminal, (transmitting / receiving) device, (transmitting / receiving) apparatus, network, etc. without specific drawing symbols may also refer to the STA (110, 120) of FIG. 1. For example, in the example below, the operation of various STAs transmitting and receiving signals (e.g., PPDUs) may be performed by the transceivers (113, 123) of FIG. 1. In addition, in the example below, the operation of various STAs generating transmission and reception signals or performing data processing or calculations in advance for transmission and reception signals may be performed by the processors (111, 121) of FIG. 1.For example, an example of an operation that generates a transmission / reception signal or performs data processing or operation in advance for a transmission / reception signal may include 1) an operation of determining / obtaining / configuring / computing / decoding / encoding bit information of a subfield (SIG, STF, LTF, Data) field included in a PPDU, 2) an operation of determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 3) an operation of determining / configuring / obtaining a specific sequence (e.g., a pilot sequence, an STF / LTF sequence, an extra sequence applied to SIG) used for a subfield (SIG, STF, LTF, Data) field included in a PPDU, 4) a power control operation and / or a power saving operation applied to an STA, 5) an operation related to determining / obtaining / configuring / computing / decoding / encoding an ACK signal, etc. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various STAs for determining / acquiring / configuring / computing / decoding / encoding transmission / reception signals can be stored in the memory (112, 122) of FIG. 1.

[0067] The device / STA of the sub-drawing (a) of the above-described FIG. 1 can be modified as in the sub-drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of the present specification will be described based on the sub-drawing (b) of FIG. 1.

[0068] For example, the transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the transceiver illustrated in sub-drawing (a) of FIG. 1 described above. For example, the processing chip (114, 124) illustrated in sub-drawing (b) of FIG. 1 may include a processor (111, 121) and a memory (112, 122). The processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (b) of FIG. 1 may perform the same function as the processor (111, 121) and the memory (112, 122) illustrated in sub-drawing (a) of FIG. 1 described above.

[0069] The mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, user, user STA, network, Base Station, Node-B, Access Point (AP), repeater, router, relay, receiving device, transmitting device, receiving STA, transmitting STA, receiving Device, transmitting Device, receiving Apparatus, and / or transmitting Apparatus described below may refer to the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may refer to the processing chip (114, 124) illustrated in the sub-drawing (b) of FIG. 1. That is, the technical feature of the present specification may be performed in the STA (110, 120) illustrated in the sub-drawings (a) / (b) of FIG. 1, or may be performed only in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1. For example, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal generated in the processor (111, 121) illustrated in the sub-drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) illustrated in the sub-drawings (a) / (b) of FIG. 1. Alternatively, the technical feature that the transmitting STA transmits a control signal may be understood as a technical feature that the control signal to be transmitted to the transceiver (113, 123) is generated in the processing chip (114, 124) illustrated in the sub-drawings (b) of FIG. 1.

[0070] For example, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal being received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (a) of FIG. 1 being acquired by a processor (111, 121) illustrated in sub-drawing (a) of FIG. 1. Alternatively, the technical feature of a receiving STA receiving a control signal can be understood as a technical feature of a control signal received by a transceiver (113, 123) illustrated in sub-drawing (b) of FIG. 1 being acquired by a processing chip (114, 124) illustrated in sub-drawing (b) of FIG.

[0071] Referring to the sub-drawing (b) of FIG. 1, software code (115, 125) may be included in the memory (112, 122). The software code (115, 125) may include instructions that control the operation of the processor (111, 121). The software code (115, 125) may be included in various programming languages.

[0072] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device. The processor may be an application processor (AP). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). For example, the processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may be a SNAPDRAGON™ series processor manufactured by Qualcomm®, an EXYNOSTM series processor manufactured by Samsung®, an A series processor manufactured by Apple®, a HELIO™ series processor manufactured by MediaTek®, an ATOM™ series processor manufactured by INTEL®, or an enhanced processor thereof.

[0073] In this specification, uplink may mean a link for communication from a non-AP STA to an AP STA, and uplink PPDU / packet / signal, etc. may be transmitted through the uplink. In addition, in this specification, downlink may mean a link for communication from an AP STA to a non-AP STA, and downlink PPDU / packet / signal, etc. may be transmitted through the downlink.

[0074] Figure 2 is a conceptual diagram showing the structure of a wireless local area network (WLAN).

[0075] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0076] The upper part of Figure 2 shows the structure of the infrastructure BSS (basic service set) of IEEE (institute of electrical and electronic engineers) 802.11.

[0077] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter, BSS). The BSSs (200, 205) are a collection of APs and STAs, such as an access point (AP) 225 and a station (STA1, 200-1), that have successfully synchronized and can communicate with each other, and are not a concept that designates a specific area. The BSS (205) may also include one or more STAs (205-1, 205-2) that can be associated with one AP (230).

[0078] A BSS may include at least one STA, an AP (225, 230) providing a distribution service, and a distribution system (DS, 210) connecting multiple APs.

[0079] A distributed system (210) can connect multiple BSSs (200, 205) to implement an extended service set (ESS, 240). An ESS (240) can be used as a term to indicate a network formed by connecting one or more APs through the distributed system (210). APs included in a single ESS (240) can have the same SSID (service set identification).

[0080] The portal (portal, 220) can act as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0081] In a BSS such as the upper part of Fig. 2, a network between APs (225, 230) and a network between APs (225, 230) and STAs (200-1, 205-1, 205-2) can be implemented. However, it may also be possible to establish a network and perform communication between STAs without an AP (225, 230). A network that establishes a network and performs communication between STAs without an AP (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0082] The bottom of Figure 2 is a conceptual diagram showing IBSS.

[0083] Referring to the bottom of Fig. 2, the IBSS is a BSS that operates in ad-hoc mode. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, the STAs (250-1, 250-2, 250-3, 255-4, 255-5) are managed in a distributed manner. In the IBSS, all STAs (250-1, 250-2, 250-3, 255-4, 255-5) can be mobile STAs, and access to the distributed system is not permitted, forming a self-contained network.

[0084] Figure 3 is a diagram illustrating a general link setup process.

[0085] In step S310, the STA may perform a network discovery operation. This network discovery operation may include scanning by the STA. That is, for the STA to access the network, it must find a network it can join. Before joining a wireless network, the STA must identify compatible networks. The process of identifying networks in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

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

[0087] Although not shown in the example of FIG. 3, the scanning operation can also be performed in a passive scanning manner. An STA performing scanning based on passive scanning can wait for a beacon frame while moving between channels. A beacon frame is one of the management frames in IEEE 802.11. It announces the presence of a wireless network and is periodically transmitted so that the scanning STA can find the wireless network and participate in the wireless network. In the BSS, the AP periodically transmits the beacon frame, and in the IBSS, the STAs within the IBSS take turns transmitting the beacon frame. When the scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and moves to another channel, recording the beacon frame information on each channel. An STA that receives a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning on the next channel in the same manner.

[0088] An STA that discovers a network can perform an authentication process through step S320. This authentication process may be referred to as the first authentication process to clearly distinguish it from the security setup operation of step S340 described below. The authentication process of S320 may include a process in which the STA transmits an authentication request frame to the AP, and the AP responds by transmitting an authentication response frame to the STA. The authentication frame used for the authentication request / response corresponds to a management frame.

[0089] The authentication frame may include information such as an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a Robust Security Network (RSN), and a Finite Cyclic Group.

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

[0091] A successfully authenticated STA may perform an association process based on step S330. The association process includes a process in which the STA transmits an association request frame to the AP, and the AP transmits an association response frame to the STA in response. For example, the association request frame may include information related to various capabilities, such as a beacon listen interval, a service set identifier (SSID), supported rates, supported channels, RSN, mobility domain, supported operating classes, a Traffic Indication Map Broadcast request, and interworking service capabilities. For example, the association response frame may contain information related to various capabilities, status codes, Association ID (AID), supported rates, Enhanced Distributed Channel Access (EDCA) parameter sets, Received Channel Power Indicator (RCPI), Received Signal to Noise Indicator (RSNI), mobility domains, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, QoS maps, etc.

[0092] In step S340, the STA may perform a security setup process. The security setup process of step S340 may include, for example, a process of setting up a private key through a four-way handshaking using an Extensible Authentication Protocol over LAN (EAPOL) frame.

[0093] Figure 4 illustrates one embodiment of a multi-link (ML).

[0094] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate over a remote link. The MLDs can be categorized into AP MLDs including multiple AP STAs and non-AP MLDs including multiple non-AP STAs. That is, the AP MLD can include affiliated APs (i.e., AP STAs), and the non-AP MLD can include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0095] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be allocated to the first and second links. The first and second multilinks may be identified through a link ID of 4 bits (or other n bits). The first and second links may be configured in the same 2.4 GHz, 5 GHz, or 6 GHz band. Alternatively, the first link and the second link may be configured in different bands.

[0096] The AP MLD of FIG. 4 includes three affiliated APs. In the example of FIG. 4, AP1 may operate in the 2.4 GHz band, AP2 may operate in the 5 GHz band, and AP3 may operate in the 6 GHz band. In the example of FIG. 4, the first link in which AP1 and non-AP1 operate may be defined as a channel / subchannel / frequency resource within the 2.4 GHz band. Furthermore, in the example of FIG. 4, the second link in which AP2 and non-AP2 operate may be defined as a channel / subchannel / frequency resource within the 5 GHz band. Furthermore, in the example of FIG. 4, the third link in which AP3 and non-AP3 operate may be defined as a channel / subchannel / frequency resource within the 6 GHz band.

[0097] In the example of FIG. 4, AP1 may initiate a multi-link setup procedure (ML setup procedure) by transmitting an Association Request frame to non-AP STA1. In the example of FIG. 4, non-AP STA1 may transmit an Association Response frame in response to the Association Request frame. Each AP (e.g., AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the AP illustrated in FIG. 1 and / or FIG. 2, and each non-AP (e.g., non-AP1 / 2 / 3) illustrated in FIG. 4 may be identical to the STA (i.e., user-STA or non-AP STA) illustrated in FIG. 1 and / or FIG. 2.

[0098] The specific features of this specification are not limited to the specific features of FIG. 4. That is, the number of links can be defined in various ways, and multiple links can be defined in various ways within at least one band.

[0099] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of this specification.

[0100] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) of the present specification can transmit and / or receive the PPDU of FIG. 5. The PPDU described in the present specification may have, for example, the structure of FIG. 5. In addition, the PPDU described in the present specification may be called by various names such as a transmission PPDU, a reception PPDU, a first type PPDU, or an Nth type PPDU, etc. The PPDU described in the present specification can be used in a WLAN system defined according to IEEE 802.11bn and / or a next-generation WLAN system that improves IEEE 802.11bn.

[0101] The PPDU of FIG. 5 may be related to various PPDU types used in a UHR system. For example, the example of FIG. 5 may be used for at least one of a single-user (SU) mode / type / transmission, a multi-user (MU) mode / type / transmission, and a null data packet (NDP) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the Data field illustrated may be omitted. If the PPDU of FIG. 5 is used for a trigger-based (TB) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that has received a trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU with the UHR-SIG omitted in the example of FIG. 5.

[0102] In FIG. 5, L-STF or UHR-LTF may be called a preamble or physical preamble, and may be generated / transmitted / received / acquired / decoded in the physical layer (included in the transmitting / receiving STA).

[0103] Each block illustrated in Fig. 5 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 5, L-STF (legacy short training field), L-LTF (legacy long training field), L-SIG (legacy signal), RL-SIG (repeated L-SIG), U-SIG (Universal Signal), UHR-SIG (UHR-signal), etc.

[0104] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in FIG. 5 may be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields may be set to 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields may be expressed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields may be expressed in units of 78.125 kHz.

[0105] In the PPDU of Fig. 5, L-LTF and L-STF may be identical to conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0106] The L-SIG field of FIG. 5 may include, for example, 24 bits of bit information. For example, the 24 bits of information may include a 4 bit Rate field, a 1 bit Reserved bit, a 12 bit Length field, a 1 bit Parity bit, and a 6 bit Tail bit. For example, the 12 bit Length field may include information about the length or time duration of the PPDU. For example, the value of the 12 bit Length field may be determined based on the type of the PPDU. For example, if the PPDU is a non-HT (non-High Throughput), HT (High Throughput), VHT (Very High Throughput) PPDU, or an EHT (extremely high throughput) PPDU or UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is a HE PPDU, the value of the Length field may be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, for non-HT, HT, VHT PPDU, EHT PPDU, UHR PPDU, the value of the Length field can be determined as a multiple of 3, and for HE (High-Efficiency) PPDU, the value of the Length field can be determined as "a multiple of 3 + 1" or "a multiple of 3 + 2". In other words, the Length field in an UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0107] For example, (non-AP and AP) STAs can apply BCC encoding based on a code rate of 1 / 2 to the 24 bits of information in the L-SIG field. Then, the transmitting STA can obtain 48 BCC coded bits. BPSK modulation can be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarriers {subcarrier index -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. As a result, the 48 BPSK symbols can be mapped to subcarrier indices -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA can additionally map the signal {-1, -1, -1, 1} to the subcarrier indices {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0108] For example, (non-AP and AP) STA can generate RL-SIG, which is generated in the same manner as L-SIG. BPSK modulation can be applied to RL-SIG. Receiving (non-AP and AP) STA can determine whether the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of RL-SIG. In other words, if RL-SIG is present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of HE PPDU, EHT PPDU, or UHR PPDU. In other words, if RL-SIG is not present, receiving (non-AP and AP) STA can determine whether the received PPDU is one of non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repeat of the L-SIG field and is used to differentiate an UHR PPDU from a non-HT PPDU, HT PPDU, and VHT PPDU.

[0109] After the RL-SIG in Fig. 5, a U-SIG (Universal SIG) may be inserted. The U-SIG may be called by various names such as the first SIG field, the first SIG, the first type SIG, the control signal, the control signal field, the first (type) control signal, the common control field, and the common control signal.

[0110] A U-SIG can contain N bits of information and can include information for identifying the type of EHT PPDU. For example, a U-SIG can be formed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol (e.g., an OFDM symbol) for a U-SIG can have a duration of 4 microseconds. Each symbol of a U-SIG can be used to transmit 26 bits of information. For example, each symbol of a U-SIG can be transmitted and received based on 52 data tones and 4 pilot tones.

[0111] For example, A bit information (e.g., 52 uncoded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bits of information (e.g., 26 uncoded bits) out of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bits of information (e.g., 26 uncoded bits) out of the total A bit information. For example, the transmitting STA can obtain 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 to generate 52 coded bits, and perform interleaving on the 52 coded bits. The transmitting STA can perform BPSK modulation on the interleaved 52 coded bits to generate 52 BPSK symbols allocated to each U-SIG symbol. A single U-SIG symbol can be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, excluding DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) excluding the pilot tones -21, -7, +7, and +21.

[0112] For example, A bit information (e.g., 52 uncoded bits) transmitted by U-SIG may include a CRC field (e.g., a 4-bit long field) and a tail field (e.g., a 6-bit long field). The CRC field and the tail field may be transmitted through the second symbol of the U-SIG. The CRC field may be generated based on 26 bits allocated to the first symbol of the U-SIG and the remaining 16 bits excluding the CRC / tail field within the second symbol, and may be generated based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder and may be set to, for example, "000000".

[0113] The A bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the size of the version-independent bits can be fixed or variable. For example, the version-independent bits can be assigned only to the first symbol of the U-SIG, or the version-independent bits can be assigned to both the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits can be called by various names, such as the first control bit and the second control bit.

[0114] For example, the version-independent bits of the U-SIG may include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted and received PPDU. For example, a first value (e.g., a value of 000) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an EHT PPDU. In addition, a second value (e.g., a value of 001) of the 3-bit PHY version identifier may indicate that the transmitted and received PPDU is an UHR PPDU.

[0115] In other words, when the (AP / non-AP) STA transmits an EHT PPDU, it can set the 3-bit PHY version identifier to the first value. In other words, the receiving (AP / non-AP) STA can determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value, and can determine that the received PPDU is an UHR PPDU based on the PHY version identifier having the second value.

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

[0117] For example, the version-independent bits of U-SIG may include information about the length of a transmission opportunity (TXOP) and information about the BSS color ID.

[0118] For example, if a UHR PPDU is classified into various types (e.g., a type related to SU transmission (performed based on UL or DL), a type related to DL transmission, a type related to NDP transmission, a type related to DL non-MU-MIMO, a type related to DL MU-MIMO, a type related to Multi-AP operation, a type related to Coordinated beamforming (Co-BF), Spatial Reuse (SR), a type related to Coordinated OFDMA (C-OFDMA), a type related to Coordinated TDMA (Co-TDMA)), information about the type of the EHT PPDU (e.g., 2-bit or 3-bit information) can be included in the version-dependent bits of the U-SIG.

[0119] For example, a U-SIG may include information about 1) a bandwidth field including information about a bandwidth, 2) a field including information about an MCS technique applied to the UHR-SIG, 3) an indication field including information about whether a dual subcarrier modulation (DCM) technique is applied to the UHR-SIG, 4) a field including information about the number of symbols used for the UHR-SIG, 5) a field including information about whether the UHR-SIG is generated over the entire band, 6) a field including information about the type of UHR-LTF / STF, and 7) a field indicating the length of the UHR-LTF and the CP length.

[0120] Preamble puncturing may be applied to the PPDU of FIG. 5. Preamble puncturing refers to applying puncturing to a portion of the entire bandwidth of the PPDU (e.g., the secondary 20 MHz band). For example, when an 80 MHz PPDU is transmitted, the STA applies puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0121] For example, the pattern of preamble puncturing can be preset. For example, when the first puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when the second puncturing pattern is applied, puncturing can be applied only to one of the two secondary 20 MHz bands included in the secondary 40 MHz band within the 80 MHz band. For example, when the third puncturing pattern is applied, puncturing can be applied only to the secondary 20 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band). For example, when the fourth puncturing pattern is applied, a primary 40 MHz band included in the primary 80 MHz band within the 160 MHz band (or 80+80 MHz band) may be present, and puncturing may be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band.

[0122] Information regarding preamble puncturing applied to the PPDU may be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information regarding the contiguous bandwidth of the PPDU, and the second field of the U-SIG may include information regarding preamble puncturing applied to the PPDU.

[0123] For example, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be individually configured in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for the first 80 MHz band and a second U-SIG for the second 80 MHz band. In this case, the first field of the first U-SIG may include information regarding the 160 MHz bandwidth, and the second field of the first U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding the preamble puncturing pattern). Additionally, the first field of the second U-SIG may include information about a 160 MHz bandwidth, and the second field of the second U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern). Meanwhile, the UHR-SIG consecutive to the first U-SIG may include information about preamble puncturing applied to the second 80 MHz band (i.e., information about a preamble puncturing pattern), and the UHR-SIG consecutive to the second U-SIG may include information about preamble puncturing applied to the first 80 MHz band (i.e., information about a preamble puncturing pattern).

[0124] Additionally or alternatively, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following methods. U-SIG may include information regarding preamble puncturing for all bands (i.e., information regarding preamble puncturing patterns). That is, UHR-SIG may not include information regarding preamble puncturing, and only U-SIG may include information regarding preamble puncturing (i.e., information regarding preamble puncturing patterns).

[0125] U-SIGs can be configured in 20 MHz units. For example, if an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included within an 80 MHz PPDU. PPDUs exceeding the 80 MHz bandwidth can contain different U-SIGs.

[0126] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted via at least one symbol, and each symbol may have a length of 4 us. Information regarding the number of symbols used for the UHR-SIG may be included in the U-SIG.

[0127] UHR-SIG provides additional signals to the U-SIG field to enable STAs to interpret / decode UHR PPDUs. The UHR-SIG field may contain U-SIG overflow bits that are common to all users. The UHR-SIG field also contains resource allocation information, allowing STAs to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

[0128] The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated in FIG. 5 can be determined based on RUs (resource units) defined by multiple subcarriers / tones. That is, the UHR-LTF, UHR-STF, and data fields of this specification can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.

[0129] FIG. 6 is a diagram illustrating the layout of resource units (RUs) used for a 20 MHz PPDU. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be transmitted / received through at least one of the various RUs defined in FIG. 6.

[0130] As shown at the top of Fig. 6, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used as a guard band in the leftmost band of the 20 MHz band, and five tones can be used as a guard band in the rightmost band of the 20 MHz band. In addition, seven DC tones can be inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones can exist on each side of the DC band. In addition, 26 units, 52 units, and 106 units can be allocated to other bands. Each unit can be allocated for a receiving station, i.e., a user.

[0131] Meanwhile, the RU arrangement of FIG. 6 is utilized not only in a situation for multiple users (MUs) but also in a situation for a single user (SU), in which case it is possible to use one 242-unit as shown at the bottom of FIG. 4, in which case three DC tones can be inserted.

[0132] In the example of Fig. 6, RUs of various sizes, such as 26-RU, 52-RU, 106-RU, and 242-RU, are proposed. Since the specific sizes of these RUs can be expanded or increased, the present embodiment is not limited to the specific size of each RU (i.e., the number of corresponding tones). In this specification, N-RU may be represented as N-tone RU, etc. For example, 26-RU may be represented as 26-tone RU.

[0133] Figure 7 is a diagram showing the layout of resource units (RUs) used for 40MHz PPDU.

[0134] As in the example of Fig. 6 where RUs of various sizes were used, the example of Fig. 7 can also use 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0135] Additionally, as illustrated, 484 RUs may be used when used for a single user. Meanwhile, the specific number of RUs may be changed, as in the example of FIG. 6.

[0136] Figure 8 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of resource units (RUs) used in this specification may vary. For example, the layout of resource units (RUs) used in the 80MHz band may vary.

[0137] Figure 9 illustrates an operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can perform channel access through contending (i.e., backoff operation) and transmit a trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU including a trigger frame (930). When a PPDU including a trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

[0138] TB PPDUs (941, 942) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (930). The ACK frame (950) for the TB PPDU can be implemented in various forms.

[0139] Figure 10 shows an example of channels used / supported / defined within the 2.4 GHz band.

[0140] The 2.4 GHz band may be referred to by other names, such as the first band (band). Furthermore, the 2.4 GHz band may refer to a frequency range in which channels with a center frequency adjacent to 2.4 GHz (e.g., channels with a center frequency between 2.4 and 2.5 GHz) are used / supported / defined.

[0141] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz within the 2.4 GHz band may have multiple channel indices (e.g., indices 1 through 14). For example, the center frequency of a 20 MHz channel assigned channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned channel index N may be (2.407 + 0.005*N) GHz. The channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of the channel indices and center frequencies may change.

[0142] Figure 10 exemplarily illustrates four channels within the 2.4 GHz band. The illustrated first frequency region (1010) to fourth frequency region (1040) may each include one channel. For example, the first frequency region (1010) may include channel 1 (a 20 MHz channel having an index of 1). In this case, the center frequency of channel 1 may be set to 2412 MHz. The second frequency region (1020) may include channel 6. In this case, the center frequency of channel 6 may be set to 2437 MHz. The third frequency region (1030) may include channel 11. In this case, the center frequency of channel 11 may be set to 2462 MHz. The fourth frequency region (1040) may include channel 14. In this case, the center frequency of channel 14 may be set to 2484 MHz.

[0143] Figure 11 illustrates an example of channels used / supported / defined within the 5 GHz band.

[0144] The 5 GHz band may be referred to by other names, such as a second band / band, etc. The 5 GHz band may refer to a frequency range in which channels with center frequencies greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz) are used / supported / defined. Alternatively, the 5 GHz band may include multiple channels between 4.5 GHz and 5.5 GHz. The specific figures shown in FIG. 11 are subject to change.

[0145] Multiple channels within the 5 GHz band include Unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as UNII Low. UNII-2 may include frequency ranges called UNII Mid and UNII-2Extended. UNII-3 may be referred to as UNII-Upper.

[0146] Within the 5 GHz band, multiple channels can be configured, and the bandwidth of each channel can be variously configured, such as 20 MHz, 40 MHz, 80 MHz, or 160 MHz. For example, the 5170 MHz to 5330 MHz frequency domain / range within UNII-1 and UNII-2 can be divided into eight 20 MHz channels. The 5170 MHz to 5330 MHz frequency domain / range can be divided into four channels through a 40 MHz frequency domain. The 5170 MHz to 5330 MHz frequency domain / range can be divided into two channels through an 80 MHz frequency domain. Alternatively, the 5170 MHz to 5330 MHz frequency domain / range can be divided into one channel through a 160 MHz frequency domain.

[0147] Figure 12 illustrates an example of channels used / supported / defined within the 6 GHz band.

[0148] The 6 GHz band may also be referred to by other names, such as the third band / band. The 6 GHz band may refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, or defined. The specific figures shown in Figure 12 are subject to change.

[0149] For example, the 20 MHz channel of FIG. 12 can be defined from 5.940 GHz. Specifically, the leftmost channel among the 20 MHz channels of FIG. 12 can have an index of 1 (or channel index, channel number, etc.), and a center frequency of 5.945 GHz can be assigned. That is, the center frequency of the indexed channel N can be determined as (5.940 + 0.005*N) GHz.

[0150] Accordingly, the indexes (or channel numbers) of the 20 MHz channels of FIG. 12 are 1, 5, 9, 13, 17, 21, 25, 29, 33, 37, 41, 45, 49, 53, 57, 61, 65, 69, 73, 77, 81, 85, 89, 93, 97, 101, 105, 109, 113, 117, 121, 125, 129, 133, 137, 141, 145, 149, 153, 157, 161, 165, 169, 173, 177, 181, 185, 189, 193, It can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule mentioned above, the indices of the 40 MHz channels in Fig. 12 can be 3, 11, 19, 27, 35, 43, 51, 59, 67, 75, 83, 91, 99, 107, 115, 123, 131, 139, 147, 155, 163, 171, 179, 187, 195, 203, 211, 219, 227.

[0151] FIG. 13 illustrates a modified example of a transmitting device and / or a receiving device of the present specification.

[0152] The devices (e.g., AP STA, non-AP STA) illustrated in FIGS. 1 to 4 may be modified as illustrated in FIG. 13. The transceiver (630) of FIG. 13 may be identical to the transceivers (113, 123) of FIG. 1. The transceiver (630) of FIG. 13 may include a receiver and a transmitter.

[0153] The processor (610) of FIG. 13 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (610) of FIG. 13 may be identical to the processing chip (114, 124) of FIG. 1.

[0154] The memory (150) of FIG. 13 may be the same as the memory (112, 122) of FIG. 1. Alternatively, the memory (150) of FIG. 13 may be a separate external memory different from the memory (112, 122) of FIG. 1.

[0155] Referring to FIG. 13, a power management module (611) manages power to a processor (610) and / or a transceiver (630). A battery (612) supplies power to the power management module (611). A display (613) outputs results processed by the processor (610). A keypad (614) receives input to be used by the processor (610). The keypad (614) may be displayed on the display (613). A SIM card (615) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0156] Referring to FIG. 13, the speaker (640) can output sound-related results processed by the processor (610). The microphone (641) can receive sound-related input to be used by the processor (610).

[0157] Below, the Multi-AP operation applied to this specification is described.

[0158] The above Multi-AP operation refers to a communication technique related to multiple APs in a WLAN. For example, the Multi-AP operation may refer to an operation in which one or more APs transmit and receive information to one or more STAs. In contrast to the Multi-AP operation, existing techniques may be expressed by various terms such as STX (Single Transmission). For example, the STX operation may refer to a method in which one BSS AP performs communication with one BSS STA. When communication is performed based on the STX operation, interference with adjacent APs (e.g., APs located in an overlapping BSS) may occur. Due to such interference, a problem in which the transmission and reception performance of cell-edge users (e.g., non-AP STAs located at the edge of the BSS) is reduced may occur.

[0159] Figure 14 illustrates operation according to a conventional STX operation. As illustrated, interference between STA and AP may occur due to adjacent AP1 and AP2.

[0160] To improve the above STX operation, a new Multi-AP operation is proposed. The Multi-AP operation may be based on a technology that reduces various interferences, such as Inter-Symbol Interference (ISI), through coordination with neighboring APs (e.g., APs located in overlapping BSSs).

[0161] In Fig. 14, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS (Overlapping Basic Service Set). That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0162] For example, the Multi-AP operation can be classified into various technologies / types / formats / protocols, etc. For example, the Multi-AP operation can include Coordinated TDMA (Co-TDMA) that distinguishes wireless resources allocated to multiple APs based on a time axis (time domain). Additionally or alternatively, the Multi-AP operation can include Coordinated OFDMA (C-OFDMA) that distinguishes wireless resources allocated to multiple APs based on a frequency axis (time domain). Additionally or alternatively, the Multi-AP operation can include Coordinated Spatial Reuse (Co-SR) that applies Spatial Reuse (SR) to at least one AP. Additionally or alternatively, the Multi-AP operation can include Coordinated beamforming (CBF) / nulling that nulls and transmits interference generated from neighbors (e.g., adjacent APs / STAs, and / or OBSS APs / OBSS STAs). Additionally or alternatively, the Multi-AP operation may include AP selection in which an AP with a good channel condition among neighboring APs (e.g., at least one AP located within a BSS or OBSS and with a good channel condition) transmits. Additionally or alternatively, the Multi-AP operation may include Joint Transmission (JTX) or JT in which multiple APs (e.g., multiple APs included in the same BSS / OBSS, or multiple APs included in different BSS / OBSS) cooperate to perform simultaneous transmission and reception, and JTX / JT may be implemented based on Joint Beamforming or Joint MU-MIMO.

[0163] FIG. 15 illustrates an example of Coordinated OFDMA (C-OFDMA). The illustrated AP1 may transmit a PPDU / signal to STA1, and AP2 may transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 may be performed in the same / overlapping time intervals. Transmission from AP1 to STA1 may be performed based on a first frequency band, and transmission from AP2 to STA2 may be performed based on a second frequency band different from the second frequency band. For example, in FIG. 15, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0164] Although not illustrated in Figure 15, an example of Coordinated TDMA (Co-TDMA) is also possible. For example, the acquired TXOP can be divided into specific time units (e.g., slots), and the divided slots can be sequentially assigned to multiple different APs.

[0165] The above-described example of C-OFDMA can be further modified as follows. For example, an AP (e.g., AP1) that has acquired a TXOP can share frequency resources with at least one AP in the vicinity (e.g., AP2 existing in the BSS / OBSS). For example, the shared frequency resources can be defined in units of RU (resource units) or subchannels, and for example, frequency resources can be shared by AP1 to AP2 in units of 20 / 40 / 80 MHz subchannels or 242 / 484 / 996-tone RUs for flexibility.

[0166] AP1, which performs C-OFDMA, can act as a sharing AP or a master AP. That is, AP1 can request at least one AP in its vicinity (e.g., AP2 in the BSS / OBSS) to report information about the channel and / or buffer status. Based on this, AP1 can obtain a TXOP and share a portion of its frequency resources (e.g., a 20 MHz subchannel or a RU of a specific size) with at least one AP in its vicinity (e.g., AP2 in the BSS / OBSS) within all or part of the time interval associated with the TXOP.

[0167] Figure 16 illustrates an example of Coordinated Beamforming (CBF). In the illustrated example, AP1 may transmit a PPDU / signal to STA1, and AP2 may transmit a PPDU / signal to STA2. Transmissions from AP1 and AP2 may be performed in the same / overlapping time intervals. Transmissions from AP1 and AP2 may be performed through the same / overlapping frequency bands. In order to reduce interference caused to STA2 by AP1, AP1 may perform nulling / beamforming toward STA2, and in order to reduce interference caused to STA1 by AP2, AP2 may perform nulling / beamforming toward STA1. For example, such nulling / beamforming may be implemented in a manner of positioning a radiation null to a neighboring unassociated STA. The above-described nulling / beamforming may make a specific AP invisible to a neighboring unassociated STA. For example, the above-described nulling / beamforming may make AP1 (or AP2) invisible to STA2 (or STA1).

[0168] For example, in FIG. 16, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0169] Although not shown in FIG. 16, control signals (e.g., coordination frames) for nulling / beamforming between AP1 and STA2 and / or nulling / beamforming between AP2 and STA1 may be transmitted and received over the backhaul link between AP1 and AP2.

[0170] Figure 17 illustrates an example of AP selection. The illustrated AP2 is determined to have a better channel condition than AP1. AP1 transmits its data / signal to AP2 via a backhaul link, and AP2, instead of AP1, can transmit a signal to STA1. For example, in Figure 17, STA1 and AP1 may be included in the BSS, and STA2 and AP2 may be included in the OBSS. In other words, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0171] Figure 18 illustrates an example of JTX / JT. The illustrated AP1 can transmit to STA1 together with AP2. For example, the PPDU / signal transmitted from AP2 to STA1 may be all or part of the same as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be simultaneously transmitted through the same / overlapping frequency band as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be a signal transmitted from AP1 through a backhaul link. For example, in Figure 18, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0172] More specifically, in FIG. 18, AP1 can transmit a coordination request (or can be named variously, such as a first request, a control request, etc.) to AP2 and receive a coordination response (or can be named variously, such as a first response, a control response, etc.) from AP2. Through the exchange of the request / response, information about coordination between AP1 and AP2 (e.g., information about whether AP1 and AP2 will perform simultaneous transmission to STA1), information about the point in time when coordination starts, information about the point in time when AP1 and AP2 start simultaneous transmission to STA1, information about data shared between AP1 and AP2, etc. can be exchanged. AP1 can share its data with AP2 via the backhaul link. Thereafter, AP1 can transmit a coordination trigger frame (or can be named variously, such as a trigger frame) to AP2 and perform simultaneous transmission to STA1 based on the trigger frame.

[0173] <Embodiments applicable to this specification>

[0174] To enable terminals to maintain continuous WLAN connectivity over a wider area, numerous APs are being installed adjacent to each other. However, overlapping BSSs of multiple APs can lead to issues such as radio interference and transmission collisions between APs. To address these issues, various technologies have been proposed to coordinate APs across frequency, time, and spatial domains (e.g., RU selection, joint transmission, nulling, etc.). Furthermore, attention should be paid to the various issues that can arise during inter-AP cooperation.

[0175] In EHT (802.11be), a technology was proposed to allocate some time within the TXOP acquired by the AP to support peer-to-peer (P2P) transmission to non-AP STAs. To this end, a new TXOP Sharing Mode subfield was defined in the Common Info field of the existing MU-RTS Trigger frame, and the MU-RTS (Multi User-Request To Send) Trigger frame when this value is nonzero is referred to as an MU-RTS TXOP Sharing (TXS) Trigger frame (TF). If the value of the TXOP Sharing mode is 1, the non-AP STA supports one or more (non-TB) PPDU transmissions to the AP, and if the value of the TXOP Sharing mode is 2, the non-AP STA supports P2P transmission in addition to (non-TB) PPDU transmissions to the AP.

[0176] Figure 19 shows an example of the operation of a 2-day MU-RTS TXS trigger frame with a value of the TXOP Sharing Mode subfield.

[0177] Fig. 19 shows an example of operation when the TXOP Sharing mode value is 2. When the AP transmits an MU-RTS TXS TF including time allocation information (Time allocated in MU-RTS TXS Trigger Frame of Fig. 19) to non-AP STA 1, non-AP STA 1 can perform P2P transmission to non-AP STA 2 after responding with CTS (Clear-To-Send).

[0178] Figure 20 shows an example of coordinated TDMA operation.

[0179] Meanwhile, if the existing Triggered TXOP Sharing protocol is utilized for multi-AP coordination, frame exchange can be performed without affecting each other by dividing the transmission within the BSS of each cooperative AP by time unit. That is, FIG. 20 shows an example of Coordinated-Time Division Multiplexing Access (Co-TDMA) according to the time unit among the cooperation methods between cooperative APs. At this time, the AP in the existing Triggered TXS protocol can play the role of an AP that shares TXOP in the multi-AP coordination operation, and the STA in the existing Triggered TXS protocol can play the role of an AP that shares TXOP in the multi-AP coordination operation. In this specification, an AP that shares TXOP is referred to as a Sharing AP (SAP), and an AP that receives TXOP from an SAP is referred to as a Shared AP (DAP). Here, the SAP that shares TXOP is not limited to only AP STAs, and may also include non-AP STAs that share TXOP. Additionally, the DAPs that share TXOPs are not limited to AP STAs, and may also include non-AP STAs that share TXOPs (or transmit and receive with AP STAs that share TXOPs). Furthermore, frame exchanges with non-AP STAs or SAPs belonging to the DAP BSS during the time allocated to the DAP are referred to as BSS frame exchanges (FEs) of the DAP.For example, frame exchange may be performed by transmitting data frames and responding to block ACK frames following RTS / CTS frame exchange between a DAP and a non-AP STA, transmitting UL data frames by non-AP STAs in response to a trigger frame transmitted from the DAP, or transmitting data frames by the DAP in response to a trigger frame transmitted from the SAP.

[0180] Co-TDMA or Co-TDMA (coordinated TDMA) procedure allows an AP to share the time portion of the acquired TXOP with other APs belonging to an AP set (which may consist of one AP) to transmit at least one PPDU.

[0181] The Co-TDMA procedure includes a polling phase, a TXOP allocation phase, and a TXOP return phase.

[0182] In the polling phase, a Co-TDMA shared AP can request a poll response transmitted as a TB PPDU from other APs only if the other APs support the response as a TB PPDU. The Co-TDMA shared AP notifies its intention to share the time portion of the TXOP acquired from the ICF (Initial Control Frame) transmitted at the start of the TXOP with other APs. When the ICF receives a time allocation from a Co-TDMA shared AP within the TXOP, it polls one or more APs to request a response in order to determine the intention of the polled AP. The Duration field of the ICF is set to a value equal to one SIFS plus the time required to transmit the requested response from the polled AP. When the ICF polls to determine the intention of the AP in case of receiving a time allocation from a Co-TDMA shared AP within the TXOP, the ICF is a trigger frame. The Co-TDMA shared AP identifies each AP to be polled by setting the AID12 subfield of the user information field of the polled AP to the AP ID of the polled AP in the trigger frame.

[0183] The polled AP provides the following in response to the received ICF:

[0184] - Indicates that it will not receive time allocations from the Co-TDMA shared AP during the current TXOP (Note that if the Co-TDMA shared AP does not receive a response from the polled AP, the Co-TDMA shared AP indicates that the polled AP will not receive time allocations from the Co-TDMA shared AP during the current TXOP)

[0185] - Indicates the intent to receive time allocation from the Co-TDMA shared AP during the current TXOP.

[0186] - Signaling details (including traffic instructions)

[0187] During the TXOP allocation phase, a Co-TDMA shared AP can allocate a portion of the time within the acquired TXOP to other APs that are not collocated with the Co-TDMA shared AP. To share the time portion of the acquired TXOP, the AP must transmit an MU-RTS TXS trigger frame to other APs that are not collocated with the Co-TDMA shared AP.

[0188] The Duration field of the MU-RTS TXS trigger frame is set to a value equal to one SIFS plus the time required to transmit the requested CTS response frame. The Co-TDMA shared AP identifies the Co-TDMA coordinated AP with which it will share the time portion of the acquired TXOP by setting the AID12 subfield of the user information field of the MU-RTS TXS trigger frame to the AP ID of the Co-TDMA coordinated AP. When the Co-TDMA coordinated AP receives the MU-RTS TXS trigger frame from the Co-TDMA shared AP, the AP may transmit and / or receive one or more PPDUs within the time allocation indicated in the MU-RTS TXS trigger frame. The first PPDU of the exchange shall carry a CTS frame. The time allocated to the Co-TDMA coordinated AP identified in the MU-RTS TXS trigger frame is specified in the Allocation Duration subfield of the MU-RTS TXS trigger frame.

[0189] In the TXOP return phase, the Co-TDMA cooperating AP may return the remainder of its allocated time (if any) to the Co-TDMA sharing AP.

[0190] Figure 21 illustrates an example of a multi-AP selection procedure in Co-TDMA.

[0191] However, in order for the above-described Co-TDMA to be successfully performed, a procedure needs to be performed to select a DAP with which the SAP wishes to share a TXOP within the AP set that constitutes Multi-AP cooperation, or a procedure needs to be performed to notify that the TXOP will be shared. At this time, in the Multi-AP selection (or Coordination announcement or Schedule announcement) procedure of FIG. 21, it is necessary to more specifically define and design the Selection / Coordination response frame transmitted by the DAP depending on the type of Selection / Coordination request frame transmitted from the SAP.

[0192] Accordingly, this specification defines the structure and format of a response frame for a Multi-AP selection / coordination request frame. At this time, the Multi-AP selection / coordination request frame can be transmitted for the purpose of selecting a DAP for a SAP to perform Multi-AP cooperation-based transmission in a Multi-AP cooperation environment or Co-TDMA operation, or for the purpose of transmitting information and a schedule for Multi-AP cooperation-based transmission to one or more DAPs. Additionally or alternatively, the frame proposed in this specification can be utilized as a request frame or a response frame for updating information for Multi-AP cooperation. Additionally or alternatively, the frame proposed in this specification can be utilized for a specific purpose (e.g., TXOP return) in a specific Multi-AP scheme (e.g., Co-TDMA).

[0193] Specifically, this specification covers the structure and transmission method of the Public Action frame when responding to a Trigger frame (e.g., BSRP TF (Buffer Status Report Poll) Trigger Frame) transmitted as a selection / coordination request frame. Additionally or alternatively, when the Public Action frame is utilized as a request / response frame for updating Multi-AP cooperation information or a frame for the purpose of TXOP return in Co-TDMA, the structure and transmission examples of the frame are presented. By using the selection / coordination response frame transmitted from the DAP(s), the SAP can perform more efficient Multi-AP cooperation.

[0194] The specific designations (names) proposed in this specification may be changed and are not limited.

[0195] <Composition and operation of the embodiment proposed in this specification>

[0196] This specification defines a response frame to a BSRP Trigger frame that can be transmitted in a Multi-AP selection (or Coordination announcement or Schedule announcement or Polling phase) procedure for a SAP to select a DAP to cooperate with or to obtain information from potential DAPs in a Multi-AP cooperation environment or Co-TDMA operation. Specifically, this specification proposes a method for transmitting a Public Action frame containing information related to Multi-AP cooperation or Co-TDMA operation as a response frame to a Trigger frame (e.g., BSRP TF).

[0197] Additionally or alternatively, the present specification may propose a method of responding to a Trigger frame (e.g., BSRP TF) addressed to an AP or STA from an Overlapping Basic Service Set (OBSS) STA with a (Public) Action frame even if the Trigger frame does not contain Multi-AP cooperation related information or Co-TDMA operation related information (i.e., the Action frame may be a Null Action frame that does not contain additional information in the frame body).

[0198] Additionally or alternatively, the Public Action frame proposed in this specification can be utilized in various procedures within Multi-AP cooperation (e.g., solicited / unsolicited update procedure or TXOP return in Co-TDMA) as well as the Trigger frame (e.g., BSRP TF) that can be transmitted in the Multi-AP selection (or Coordination announcement or Schedule announcement or Polling phase) procedure described above.

[0199] In multi-AP negotiation, management frames can be exchanged between unassociated APs. Each AP receives beacons or discovery frames to obtain information about neighboring APs. Based on the information obtained from the beacons or discovery frames, a newly defined Public Action frame can be used to initiate the process of configuring (i.e., negotiating) a multi-AP set.

[0200] MAPC (Multi-AP Coordination)-based transmission requires the exchange of multiple frames between APs. However, since the APs participating in MAPC are not connected to each other, there are no suitable frames available for management purposes. Therefore, this embodiment defines the Public Action frame to facilitate efficient MAPC operation between APs, thereby enabling transmission to unconnected APs under specific conditions or states.

[0201] 1. Defining a new Public Action frame

[0202] 1.1. Coordination Announcement Report (Public) Action frame or MAPC (Multi-AP Coordination) management frame

[0203] Basically, the Action frame (i.e., the Action field) consists of the Category field and the Action Details field, and the Category values ​​33, 35-125, and 128-255 are reserved. On the other hand, the Public Action frame consists of the Category field, Public Action field, and Action Details field, and the Category values ​​54-59, and 61-255 are reserved.

[0204] Therefore, a new Public Action frame can be defined that can include Multi-AP cooperation-related information or Co-TDMA operation-related information by utilizing the Reserved value. An example utilizing the reserved value of 54 can be as shown in Table 1. In this specification, the response frame to the Trigger frame is called a Multi-AP selection report (or) Coordination announcement report (CAR) (or) Schedule announcement report frame or MAPC management frame. The name of the corresponding response frame may be changed and is not limited.

[0205] Public Action field valueDescription......54Multi-AP Selection Report(or) Coordination Announcement Report(or) Schedule Announcement Report......

[0206] OrderInformation1Category2Public Action3M-AP Coordination Report4Optional Subelements (Reserved)

[0207] For example, the Action field format of a CAR frame using the reserved Category value 54 presented in Table 1 can be defined as shown in Table 2. The M-AP Coordination Report field may include one or more pieces of information for Multi-AP cooperation or Co-TDMA operation. The information may be common or specific information for each scheme of Multi-AP cooperation (e.g., Co-TDMA, Co-SR, Co-BF, etc.). In this case, the HT Control field of the CAR frame may include information (e.g., BSR) solicited from the received Trigger frame (e.g., BSRP TF). Additionally or alternatively, the HT Control field may not include any information.

[0208] Additionally or alternatively, information related to Multi-AP cooperation or Co-TDMA operation may be included in the HT Control field and the M-AP Coordination Report field.

[0209] Additionally or alternatively, information related to Multi-AP cooperation or Co-TDMA operation may be included only in the HT Control field and there may be no separate frame body (i.e., M-AP Coordination Report field, etc.).

[0210] The Optional Subelements field is Reserved or may be used to include information related to the CAR frame being used for other purposes (e.g., TXOP return procedure in Co-TDMA or specific procedures in other Multi-AP cooperation technologies).

[0211] 1.2. Contents for Multi-AP Cooperation and Co-TDMA Operation

[0212] In the Multi-AP selection procedure presented in FIG. 21, the Public Action frame that the DAP can transmit as a response frame to the Trigger frame may include contents based on one or a combination of the following contents. Additionally or alternatively, the MAPC management frame, which is a Public Action frame proposed in this specification, may be utilized in a specific MAPC procedure and may include contents based on one or a combination of the following contents. The designations (names) of the contents defined below may be changed and are not limited.

[0213] A. Operating channel: Information on the primary and punctured channels in operation.

[0214] -> For example, common channel information for smooth cooperation between APs participating in Co-TDMA

[0215] -> For example, primary channel information on which APs participating in Co-TDMA can operate in common

[0216] Specifically, a new field that acts as the CCSF0 field in the EHT Operation Information field can be defined to indicate the channel center frequency index for 20 / 40 / 80 MHz channels.

[0217] Specifically, a new field that acts as the CCSF0 field within the EHT Operation Information field can be defined to indicate the channel center frequency for the primary 80 MHz channel of a 160 MHz channel or the channel center frequency for the primary 160 MHz channel of a 320 MHz channel.

[0218] Additionally, a new field that acts as the CCSF1 field in the EHT Operation Information field can be defined to indicate the channel center frequency for a 160 MHz channel or the channel center frequency for a 320 MHz channel.

[0219] -> For example, punctured channel information of an AP participating in Co-TDMA

[0220] Specifically, a new field that acts as the Disabled Subchannel Bitmap field within the EHT Operation Information field can be defined to indicate a punctured 20 MHz subchannel using a bitmap.

[0221] A bit value of 0 in the bitmap indicates that the corresponding 20 MHz subchannel is not punctured.

[0222] A bit value of 1 in the bitmap indicates that the corresponding 20 MHz subchannel is punctured.

[0223] -> The primary channel of DAP can be included within the channel where SAP operates.

[0224] -> DAP's primary channel can be included within the operating channel excluding SAP's punctured channel.

[0225] B. Operating bandwidth: Operating bandwidth (BW) and maximum bandwidth information

[0226] -> For example, BW information that operates in common for smooth cooperation between APs participating in Co-TDMA.

[0227] Specifically, the operating channel and primary channel information described above can be utilized.

[0228] -> For example, maximum bandwidth information of APs participating in Co-TDMA

[0229] Specifically, a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field can be defined to indicate the channel width, which is the BSS BW information of each AP.

[0230] Set to 0: 20 MHz bandwidth indication

[0231] Set to 1: Indicates 40 MHz bandwidth

[0232] Set to 2: Indicates 80 MHz bandwidth

[0233] Set to 3: Indicates 160 / 80+80 MHz bandwidth

[0234] Set to 4: Indicates 320 / 160+160 MHz bandwidth

[0235] The remaining values ​​5 through 7 can be reserved.

[0236] -> For example, BW field information within the SIG-A field

[0237] -> For example, UL BW field information included in the Common Info field of MU-RTS TXS TF

[0238] -> The bandwidth of the DAP may be included within the total bandwidth over which the SAP operates.

[0239] -> For example, a new field for bandwidth indication can be added by changing / redefining the Medium Time field of the QoS Characteristics element to include a new subfield.

[0240] Specifically, a new field that plays the same role as the Channel Width field in the Control field of the EHT Operation Information field can be defined to indicate the channel width, which is the BSS BW information of each AP.

[0241] Set to 0: 20 MHz bandwidth indication

[0242] Set to 1: Indicates 40 MHz bandwidth

[0243] Set to 2: Indicates 80 MHz bandwidth

[0244] Set to 3: Indicates 160 / 80+80 MHz bandwidth

[0245] Set to 4: Indicates 320 / 160+160 MHz bandwidth

[0246] The remaining values ​​5 through 7 can be reserved.

[0247] C. Required TXOP duration: Information related to the TXOP duration that each DAP wishes to share.

[0248] -> Basically, when the Required TXOP Duration field is defined as 9 bits, the included value can be set to be the same as / similar to the value set in the Allocation Duration field of the existing MU-RTS TXS Trigger frame. That is, each AP can report the desired TXOP duration in units of 16 μs.

[0249] -> For example, by defining a new field containing Required TXOP Duration

[0250] Specifically, a new Required Duration field (tentative name) is defined to indicate the information required for Co-TDMA operation and the Required TXOP Duration value.

[0251] -> For example, by defining a new element containing Required TXOP Duration

[0252] Specifically, a new Co-TDMA Operation element (tentative name) is defined to indicate the information required for Co-TDMA operation and the Required TXOP Duration value.

[0253] -> For example, the Required TXOP Duration can be included in the QoS Characteristic element that can be used to include negotiation information during the pre-negotiation process for MAPC operation, or in an element that can be newly defined for negotiation in Co-TDMA.

[0254] -> For example, the Required TXOP Duration can be included in the UHR Operation element that can be used to include announcement information during the announcement process of each AP for MAPC operation, or in an element that can be newly defined for announcement in Co-TDMA.

[0255] -> Alternatively, the Required TXOP Duration field can indicate the length of the PPDU required by the DAP for Co-SR and Co-BF based transmissions.

[0256] For this purpose, a new Required (DL) PPDU Length field (tentative name) can be defined.

[0257] Additionally or alternatively, some values ​​in the Required TXOP Duration field may be used to indicate participation in specific schemes requested from SAP. This may replace the Participation Indication (1 bit or n bits) field presented below.

[0258] -> For example, setting the value of the Required TXOP Duration field to 0 can indicate your intention not to participate in the scheme requested by SAP.

[0259] -> On the other hand, by setting the desired TXOP duration for each AP greater than 0, it can indicate its intention to participate in the scheme requested by SAP.

[0260] -> Additionally or alternatively, if the Required TXOP Duration field is set to a maximum value based on the number of bits defined, it may indicate an intent to use the TXOP duration allocated by SAP without a separately desired TXOP duration.

[0261] -> Specifically, if the Required TXOP Duration field is defined as 9 bits and has a value in units of 16 μs, the maximum value of 511×16 μs=8,176 μs may mean that the AP does not have a specific TXOP duration that it requires separately, but will follow the TXOP duration allocated by the AP.

[0262] D. Buffer status: Buffer status information for each DAP

[0263] -> Alternatively, the Buffer Status field can indicate the length of the PPDU required by the DAP for Co-SR and Co-BF based transmissions.

[0264] For this purpose, a new Required (DL) PPDU Length field (tentative name) can be defined.

[0265] E. TXOP sharing requirement (or Coordination requirement): Indicates whether Coordination Triggering / TXOP sharing is required due to expiration of pre-negotiated Low Latency Traffic Information or the need for cooperative transmission / TXOP sharing (e.g., when individual FEs have already been performed).

[0266] -> For example, indicate and respond whether TXOP sharing is required using 1 bit

[0267] bit 0: Indicates that the DAP receiving the ICF (Initial Control Frame) or selection request frame does not require TXOP sharing.

[0268] bit 1: Indicates that the DAP receiving the ICF or selection request frame requires TXOP sharing.

[0269] F. Low Latency Traffic Information: Information related to low latency traffic that each AP wants to transmit and receive.

[0270] -> For example, information about the QoS Characteristic element included in the SCS request / response frame

[0271] - For example, using the Delay Bound field information among the QoS Characteristic element information.

[0272] Specifically, the Delay Bound field value for the QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0273] In case of changes different from the pre-negotiated Low Latency Traffic Information, include updated Low Latency Traffic Information or Delay Bound field value.

[0274] - For example, using the MSDU Lifetime field information among the QoS Characteristic element information.

[0275] Specifically, the MSDU Lifetime field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0276] In case of changes different from the pre-negotiated Low Latency Traffic Information, include updated Low Latency Traffic Information or MSDU Lifetime field value.

[0277] - For example, use the Service Start Time field information among the QoS Characteristic element information.

[0278] Specifically, the Service Start Time field value for QoS traffic that each AP wants to transmit can be used as Low Latency Traffic information.

[0279] In case of changes different from the pre-negotiated Low Latency Traffic Information, include updated Low Latency Traffic Information or Service Start Time field value.

[0280] -> For example, TXOP sharing request information requested / instructed by an AP that requires transmission of low latency traffic.

[0281] -> For example, time-bound information of Low Latency Traffic requested / instructed by an AP that requires transmission of Low Latency Traffic.

[0282] - For example, the minimum time-bound for which transmission of Low Latency Traffic must begin

[0283] - For example, the maximum time-bound required to successfully complete transmission of Low Latency Traffic

[0284] As a concrete example of this, the minimum time-bound within which LL Traffic transmission must begin or the maximum time-bound within which transmission must successfully complete can be defined as follows.

[0285] The Low Latency Traffic Information (LLTI) field, defined as n bits (e.g., n = 4, 6, 7, 8, 9, 10, or etc.), can indicate the required time-bound in m-μs units (e.g., m = 4, 8, 16, 32, 64, or etc.). For example, an LLTI field defined as 4 bits and 16 μs can indicate a time-bound from 16 μs to 240 μs. For example, an LLTI field defined as 9 bits and 4 μs can indicate a time-bound from 4 μs to 2,044 μs.

[0286] -> For example, arrival rate information of Low Latency Traffic requested / instructed by an AP that requires periodic transmission of Low Latency Traffic.

[0287] - For example, the arrival rate of Low Latency Traffic since the last reporting event.

[0288] As a concrete example, the arrival rate of LL Traffic can be defined as follows:

[0289] The Low Latency Traffic Information field, defined as n bits (e.g., n = 4, 6, 7, 8, 9, 10, or etc.), can indicate a desired arrival rate in m-μs units (e.g., m = 4, 8, 16, 32, 64, or etc.). For example, an LLTI field defined as 4 bits and 16 μs can indicate an arrival rate from 16 μs to 240 μs. For example, an LLTI field defined as 9 bits and 4 μs can indicate an arrival rate from 4 μs to 2,044 μs.

[0290] -> For example, TID (Traffic Identifier) / AC (Access Category) information for Low Latency Traffic

[0291] G. Status Code: Accept / Reject / Recommendation information for the Selection request (i.e., SAP can accept or reject the selected DAP based on whether it currently requires TXOP sharing, which can replace the TXOP sharing requirement information presented above).

[0292] -> For example, Accept or Success (eg, SUCCESS)

[0293] -> For example, Reject with Reject or Recommendation

[0294] Specifically, a Reject code with a Reject reason (e.g., REJECTED_BAD_SUPPORTED_CHANNELS)

[0295] Specifically, a Reject code with a Recommendation (e.g., REJECTED_WITH_SUGGESTED_CHANGES)

[0296] -> If the Status Code value includes Reject or Recommendation, it may include information for a new selection request. That is, the DAP that receives the selection request frame may include additional information about the Operating channel and bandwidth, Required TXOP duration, Low Latency Traffic Information, etc. described above.

[0297] H. Participation Indication (1 bit): Indicates whether to participate in MAPC-based transmission solicited from ICF.

[0298] -> That is, the DAP(s) requesting a response from SAP indicate whether or not they currently require a single MAPC-based transport directed by SAP.

[0299] -> For example, a participation report using 1 bit could be as follows:

[0300] 0: Indicates not to participate in solicited MAPC-based transmissions.

[0301] 1: Indicates participation in solicited MAPC-based transmission.

[0302] I. Preferred Tx Power: Information on the maximum Tx power desired / preferred by the DAP.

[0303] -> For example, DAP can determine its own appropriate Preferred Tx power without causing interference based on the maximum Tx power information, In-BSS STA, and OBSS STA information delivered by SAP.

[0304] J. In-BSS STA Info: Indicates information about the target STA to which SAP will perform DL / UL transmission or information about all connected STAs through MAPC schemes in which SAP and DAP perform simultaneous transmission, such as Co-SR, Co-BF, etc.

[0305] -> There may be as many In-BSS STA Info as the number of STAs indicated in the Number Of Co-BF User information described below.

[0306] -> For example, identifiers and capabilities of all STAs connected to DAP

[0307] For example, AID or MAC address of STAs

[0308] For example, STAs' MIMO and RF capability

[0309] -> For example, the identifier and capability of the target STA that wants to perform DL / UL transmission through the MAPC scheme among the STAs connected to the DAP.

[0310] For example, the AID or MAC address of the target STA

[0311] For example, MIMO and RF capability of taget STA

[0312] -> For example, an identifier for an In-BSS STA that you want to participate in the Multi-AP channel sounding (or OBSS channel sounding) process for MAPC operation.

[0313] K. Target STA Version Info: Indicates the version information of the target STA that is the target of Co-SR transmission of each AP.

[0314] -> For example, DAP indicates the version information of the target STA that is the target of Co-SR transmission during the Co-SR transmission period.

[0315] - For example, a 1-bit Target STA Version Info field can be defined.

[0316] 0: Indicates that the target STA is an EHT STA

[0317] 1: Indicates that the target STA is a UHR STA.

[0318] - For example, an n-bit Target STA Versin Info field can be defined considering future generations.

[0319] 0: Indicates that the target STA is an EHT STA

[0320] 1: Indicates that the target STA is a UHR STA.

[0321] 2: TBD

[0322] bit n: reserved

[0323] L. Feedback Type: Indicates the purpose or type of MAPC-related information contained within the current frame.

[0324] -> Indicates that it is transmitted as a response frame in MAPC cooperation or a specific scheme (e.g., Co-TDMA / SR / BF).

[0325] - Specifically, in the MAPC operation, it is possible to indicate the purpose of the transmitted frame as shown below, and based on this, the receiving STA can know what information is included.

[0326] 0: Indicates ICF in MAPC

[0327] 1: Indicates that this is an ICR (Initial Control Response) in MAPC.

[0328] 2: Indicates that it is a Co-Triggering frame in MAPC (e.g., MU-RTS TXS TF in Co-TDMA).

[0329] - Specifically, it can indicate the purpose of the frame transmitted in a specific scheme as shown below, and based on this, the receiving STA can know what information is included.

[0330] 0: Indicates ICF in Co-TDMA or Co-SR or Co-BF

[0331] 1: Indicates ICR in Co-TDMA or Co-SR or Co-BF

[0332] 2: Indicates that it is a Co-Triggering frame in Co-TDMA or Co-SR or Co-BF (e.g., MU-RTS TXS TF in Co-TDMA).

[0333] -> Additionally or alternatively, indicates that the frame is intended for transmission with one of the various UHR features (e.g., CoEx or IDC, NPCA, DPS, MAPC, etc.).

[0334] - Specifically, it can indicate the type of purpose for which the Action frame, which can be used as an ICR in Dynamic Power Saving (DPS), Inter-Device Coexistence (IDC), Non-primary Channel Access (NPCA), Multi-AP Coordination (MAPC), etc., was transmitted. An example of signaling is as follows.

[0335] 0: Indicates that this is an Action frame for multi-AP coordination operations.

[0336] 1: Indicates that this is an Action frame for DPS operation.

[0337] 2: Indicates that this is an action frame for IDC operation.

[0338] 3: Indicates that this is an action frame for operating NPCA.

[0339] Other bits: reserved

[0340] - Additionally or alternatively, it may be signaled as follows:

[0341] 0: Indicates that this is an Action frame for IDC.

[0342] 1: Indicates that this is an Action frame for low-latency traffic transmission.

[0343] 2: Indicates that this is an action frame for delivering feedback in Co-BF operations.

[0344] 3: Indicates that this is an action frame for delivering feedback in Co-TDMA operation.

[0345] 4: Indicates that this is an action frame for delivering feedback in Co-SR operations.

[0346] - Additionally or alternatively, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.) using a bitmap method.

[0347] An example of indicating the UHR feature type by a combination of each bit (bitmap) is as follows.

[0348] If B0: MAPC, B1: DPS, B2: IDC, B3: NPCA, 1100 may contain instructions and related information for MAPC and DPS operations.

[0349] M. MAPC Type: Instructions for multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, and Co-BF.

[0350] -> For example, you can signal as follows:

[0351] bit 0: None

[0352] bit 1: Co-TDMA

[0353] bit 2: Co-SR

[0354] bit 3: Co-BF

[0355] -> For example, you can signal as follows:

[0356] bit 0: Co-TDMA

[0357] bit 1: Co-SR

[0358] bit 2: Co-BF

[0359] N. Extra LTF Allowed (1 bit): Information indicating when channel estimation performance gains can be obtained by utilizing more LTFs than the total number of streams.

[0360] Specifically, in a situation where the corresponding LTF number for each total stream number is defined as in Table 3, channel estimation performance can be improved by utilizing LTFs exceeding that number. Compared to applying the minimum required number of LTFs, twice the number of LTF symbols can be transmitted, and a combining gain can be obtained at the RX end, resulting in a channel estimation performance gain of 3 dB.

[0361] # of streams# of UHR LTFs# of UHR LTFs when extra LTF is allowed1122243-448

[0362] O. Number of Co-BF Users (1 or 2 bits): Indicates the number of Co-BF STAs that the DAP side wants to support.

[0363] -> For example, the Number of Co-BF Users using 1 bit can be defined as follows:

[0364] 0: Supports one STA

[0365] 1: Supports two STAs

[0366] -> For example, the Number of Co-BF Users using 2 bits can be defined as follows:

[0367] 0: Supports one STA

[0368] 1: Supports two STAs

[0369] 2: Supports three STAs

[0370] 3: reserved

[0371] P. MCS (5 bit): MCS information of Co-BF STAs to be supported by the DAP side

[0372] -> There may be as many MCS fields as the number of STAs indicated in the Number Of Co-BF User information described above.

[0373] Q. NSS For Co-BF Users (1 bit): NSS information for Co-BF STAs to be supported by the DAP side.

[0374] -> The NSS For Co-BF Users field may exist as many times as the number of STAs indicated in the Number Of Co-BF User information described above.

[0375] -> Additionally or alternatively, only one NSS For Co-BF Users field can be passed, since only one NSS value / count is allowed within a single BSS.

[0376] R. 2xLDPC (1 bit): 2xLDPC (Low-Density Parity Check) information of each Co-BF STA to be supported on the DAP side

[0377] -> There may be as many 2xLDPC fields as the number of STAs indicated in the Number Of Co-BF User information described above.

[0378] S. Number of Data OFDM Symbols (9 bits): Indicates the number of data OFDMA symbols that the DAP desires / requires. This can be a value selected by the DAP within the range of the minimum number of OFDM (Orthogonal frequency division multiplexing) symbols and the maximum number of OFDM symbols received from the SAP.

[0379] -> Based on this information, SAP can set the appropriate PPDU length and MCS / NSS for Co-BF transmission.

[0380] T. Bandwidth (3 bits): Indicates the available bandwidth to the DAP within the bandwidth delivered / proposed by the SAP.

[0381] U. Punctured Channel Information (5 bits): Indicates the non-OFDMA (Orthogonal frequency division multiple access) puncturing pattern of the DAP within the non-OFDMA puncturing pattern transmitted / suggested from the SAP.

[0382] V. GI+LTF Size (2 bits): Indicates the GI+LTF recommended by DAP among the GI+LTF sizes that are equal to or more robust than the GI+LTF size transmitted / suggested by SAP.

[0383] W. ICF / ICR Exchange Required: Indicates whether additional sequence is required to transmit ICF to the associated STA before triggering Co-TDMA / SR / BF transmission.

[0384] -> For example, it indicates that an ICF / ICR exchange procedure is required to switch an EMLSR STA among the associated STAs from listening mode to frame exchange mode.

[0385] -> For example, it indicates that an ICF / ICR exchange procedure is required to switch a DPS STA among the associated STAs from low capability mode to high capability mode.

[0386] -> For example, it indicates that an ICF / ICR exchange procedure is required to switch a DUO STA among the associated STAs.

[0387] X. TXOP Return Indication: Indicates that the frame is intended for TXOP return.

[0388] -> For example, using 1 bit to indicate that the frame was transmitted for the purpose of TXOP return

[0389] - 0: Indicates that the frame is not intended for TXOP return.

[0390] - 1: Indicates that the frame is intended for TXOP return.

[0391] -> Additionally or alternatively, when TXOP Return Indication is enabled (i.e., set to 1), the remaining feedback information and fields related to Co-TDMA operation may be reserved or set to specific values ​​(e.g., all 0s or all 1s).

[0392] - Additionally or alternatively, instead of defining or including the TXOP Return Indication bit, some or all of the remaining feedback information related to Co-TDMA operation may be set to a specific value (e.g., all 0s or all 1s).

[0393] - For example, the value of the MAPC Type field can be set to default or 0 to indicate that it was transmitted for the purpose of TXOP return.

[0394] Additionally or alternatively, one of the MAPC Type values ​​may be defined and set as the value for the TXOP return.

[0395] - For example, the value of the 1-bit Participation Indication bit can be set to 0 to indicate that participation is terminated or that the transmission was intended for TXOP return. Additionally or alternatively, the value of the n-bit Participation Indication field can be set to 0 to indicate that participation is terminated, or one of the values ​​of the Participation Indication field can be defined and set as a value for TXOP return.

[0396] For example, you can set the value of the Required TXOP Duration field to 0 to indicate that you have used all of the TXOP / hours allocated by SAP or to return the allocated TXOP / hours.

[0397] <Content들의 포함 위치>

[0398] One or more pieces of information for Multi-AP cooperation or Co-TDMA operation, as presented in Section 1.2, may be included in the M-AP Coordination Report field. In this case, the HT Control field of the corresponding CAR frame may include information (e.g., BSR) solicited from the received Trigger frame (e.g., BSRP TF). Additionally or alternatively, the HT Control field may not contain any information.

[0399] Additionally or alternatively, information related to Multi-AP cooperation or Co-TDMA operation may be divided and included in the HT Control field and the M-AP Coordination Report field. In such a case, the HT Control field may include one or more of the information described above. Other information, as well as information about STAs associated with each AP that can be utilized for Co-SR / Co-BF-based transmission (e.g., AID, channel status information), may be included in the M-AP Coordination Report field.

[0400] Additionally or alternatively, information related to Multi-AP cooperation or Co-TDMA operation may be included only in the HT Control field and there may be no separate frame body (i.e., M-AP Coordination Report field, etc.).

[0401] 2. Example

[0402] 2.1. Role of ICR in the multi-AP selection (or polling phase) procedure

[0403] Figure 22 illustrates an example of responding to a BSRP TF with a (Public) Action frame.

[0404] Figure 22 illustrates an embodiment of a response utilizing the (Public) Action frame proposed in this specification. AP 1 can transmit a BSRP TF to APs in a cooperative relationship (i.e., AP 2 and AP 3) in order to perform a Multi-AP selection (or Coordination announcement or polling phase) procedure during Co-TDMA operation. At this time, the BSRP TF may include a new field that indicates that the BSRP TF is transmitted for Multi-AP cooperation or Co-TDMA operation by utilizing a Reserved bit. APs that can recognize this and have their own ID (e.g., Multi-AP ID or AP ID, etc. for Multi-AP cooperation) included in the User Info field(s) or whose RA field is designated as their own address can transmit the CAR (Public Action) frame proposed in this specification as a response frame to the BSRP TF. The response frame at this time may include specific information instructed or requested from the BSRP TF, or information for Multi-AP cooperation. AP 1, which receives CAR frames from APs in a cooperative relationship, can select AP(s) to perform Co-TDMA-based transmission based on the information, or determine whether to perform Co-TDMA-based transmission and when.

[0405] <Multi-AP 협력 기반 전송 참여 여부 전달 방법>

[0406] If information (i.e., BSR) solicited from a Trigger frame (e.g., BSRP) is included as is in the A-Control field, a field indicating whether to participate in the Multi-AP cooperation-based transmission (e.g., TXOP sharing requirement or Participation Indication in Section 1.2) may be included in the M-AP Coordination Report field in the frame body.

[0407] Additionally or alternatively, if the A-Control field does not contain the information solicited from the Trigger frame, the A-Control field may contain a specific value instead of the solicited information. For example, a response frame may be sent with all 26 bits of the A-Control field set to 0, indicating that the AP will not participate in the Multi-AP cooperation requested by the SAP. If the A-Control field is set to 0, a separate Multi-AP Coordination Report field may not be included in the frame body. On the other hand, an AP wishing to participate in Multi-AP cooperation may express its intent to participate by including a non-zero value in the A-Control field. For example, some or all bits of the A-Control field may be set to 1. Additionally or alternatively, a response frame may be transmitted by configuring an A-Control field that includes one or more of the Multi-AP cooperation-related information presented in Section 1.2 above instead of the solicited information and also includes whether to participate in Multi-AP cooperation-based transmission (e.g., TXOP sharing requirement or Participation Indication in Section 1.2).

[0408] 2.2. Request / Response Frame Role for Updating MAPC Information

[0409] Figure 23 illustrates an example of its use as a request / response frame for updating MAPC information.

[0410] Figure 23 illustrates an embodiment of a request / response frame for MAPC information update based on the Public Action frame proposed in this specification. That is, the Public Action frame proposed in this specification can be utilized in a method in which a specific AP solicits a MAPC management response frame in a 2-way manner. APs that have established MAPC cooperation can transmit a MAPC management request Action frame and a MAPC management response Action frame as a response frame to the MAPC management request Action frame to update some information for MAPC operation. A separate Type field can be defined and included so that a single MAPC management Action frame can be used as a request and response frame. For example, a 1-bit Type field can be set to 0 to indicate that it is a MAPC management request frame. On the other hand, if the Type field is set to 1, it can indicate that it is a MAPC management response frame. Additionally or alternatively, the Public Action frame can be utilized solely for the purpose of MAPC management response.

[0411] The MAPC management request frame and / or MAPC management response frame described above may include, but are not limited to, the following contents among the contents defined in Section 1.2 above.

[0412] - Operating channel: Information on the primary and punctured channels in operation.

[0413] - Operating bandwidth: Operating bandwidth and maximum bandwidth information

[0414] - Buffer status: Buffer status information for each AP

[0415] - Low Latency Traffic Information: Information related to low latency traffic that each AP wants to transmit and receive.

[0416] - Punctured Channel Information (5 bits): Indicates the non-OFDMA puncturing pattern of the responding AP within the non-OFDMA puncturing pattern transmitted / suggested from the requesting AP.

[0417] - In-BSS STA Info: Indicates information about the target STA to which each AP will perform DL / UL transmission or information about all connected STAs through a MAPC scheme where two APs perform transmission simultaneously, such as Co-SR, Co-BF, etc.

[0418] Figure 24 illustrates an example of use as a 1-way frame for MAPC information update.

[0419] Additionally or alternatively, an AP that has changes in information related to MAPC operation can unsolicitedly transmit a MAPC management Action frame to a specific AP to update the information. That is, FIG. 24 illustrates an example of utilizing the Public Action frame proposed in the present invention in a one-way manner.

[0420] 2.3. Frame role for specific roles in MAPC operation (e.g., TXOP return)

[0421] The Public Action frame proposed in this specification can be utilized for a specific purpose (e.g., TXOP return) in a specific Multi-AP scheme (e.g., Co-TDMA).

[0422] Figure 25 illustrates an example of its use as a frame for TXOP return in Co-TDMA.

[0423] Figure 25 illustrates an embodiment of a TXOP return frame based on the Public Action frame proposed in this specification. That is, a MAPC management Action frame can be utilized as a TXOP return frame that a shared AP can transmit to return the allocated time / TXOP in Co-TDMA.

[0424] The MAPC management TXOP return frame described above may include, but is not limited to, the following contents among the contents defined in Section 1.2 above.

[0425] - TXOP Return Indication: Indicates that the frame is intended for TXOP return.

[0426] This specification discusses the structure and transmission method of response frames for trigger frames (e.g., BSRP TF) that can be transmitted from each AP in a multi-AP cooperative environment or Co-TDMA operation. By utilizing the Coordination Announcement Report frame transmitted from the cooperating AP(s), SAP can perform more efficient multi-AP cooperation.

[0427] Fig. 26 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0428] An example of FIG. 26 may be performed at a transmitting STA or transmitting device (AP and / or non-AP STA).

[0429] Some of the steps (or detailed sub-steps described below) in the example of Fig. 26 may be omitted or changed.

[0430] Through step S2610, the transmitting device (transmitting STA) can obtain information regarding the aforementioned Tone Plan. As described above, the information regarding the Tone Plan includes the size and location of the RU, control information related to the RU, information regarding the frequency band in which the RU is included, information regarding the STA receiving the RU, etc.

[0431] Through step S2620, the transmitting device can configure / generate a PPDU based on the acquired control information. The step of configuring / generating the PPDU may include a step of configuring / generating each field of the PPDU. That is, step S2620 may include a step of configuring an EHT-SIG field including control information regarding a Tone Plan. That is, step S2620 may include a step of configuring a field including control information indicating the size / position of an RU (e.g., an N bitmap) and / or a step of configuring a field including an identifier (e.g., an AID) of an STA receiving the RU.

[0432] Additionally, step S2620 may include a step of generating an STF / LTF sequence to be transmitted through a specific RU. The STF / LTF sequence may be generated based on a preset STF generation sequence / LTF generation sequence.

[0433] Additionally, step S2620 may include a step of generating a data field (i.e., MPDU) to be transmitted via a specific RU.

[0434] The transmitting device can transmit the PPDU configured through step S2620 to the receiving device based on step S2630.

[0435] While performing step S2630, the transmitting device may perform at least one of operations such as CSD, Spatial Mapping, IDFT / IFFT operation, and GI insertion.

[0436] A signal / field / sequence configured according to this specification can be transmitted in the form of FIG. 5.

[0437] Fig. 27 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0438] The above-described PPDU can be received according to an example of FIG. 27.

[0439] An example of FIG. 27 may be performed at a receiving STA or receiving device (AP and / or non-AP STA).

[0440] Some of the steps (or detailed sub-steps described below) in the example of Fig. 27 may be omitted.

[0441] A receiving device (receiving STA) may receive all or part of a PPDU through step S2710. The received signal may have the form of FIG. 5.

[0442] The sub-step of step S2710 can be determined based on step S2630 of Fig. 26. That is, step S2710 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operations, and GI insert operations applied in step S2630.

[0443] At step S2720, the receiving device can decode all or part of the PPDU. Additionally, the receiving device can obtain control information related to the Tone Plan (i.e., RU) from the decoded PPDU.

[0444] More specifically, the receiving device can decode the L-SIG and EHT-SIG of the PPDU based on the Legacy STF / LTF and obtain information included in the L-SIG and EHT SIG fields. Information regarding various Tone Plans (i.e., RUs) described herein can be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.

[0445] In step S2730, the receiving device can decode the remaining portion of the PPDU based on the information about the Tone Plan (i.e., RU) acquired through step S2720. For example, the receiving STA can decode the STF / LTF field of the PPDU based on the information about one Plan (i.e., RU). In addition, the receiving STA can decode the data field of the PPDU based on the information about the Tone Plan (i.e., RU) and acquire the MPDU included in the data field.

[0446] Additionally, the receiving device may perform a processing operation to transmit the decoded data to a higher layer (e.g., MAC layer) through step S2730. Additionally, if the generation of a signal is instructed from the higher layer to the PHY layer in response to the data transmitted to the higher layer, a subsequent operation may be performed.

[0447] Hereinafter, the above-described embodiment will be described with reference to FIGS. 1 to 27.

[0448] FIG. 28 is a flowchart illustrating a procedure for a shared AP according to the present embodiment to receive a management frame for updating information for MAPC.

[0449] An example of FIG. 28 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0450] An example of FIG. 28 is performed in a second AP, wherein the second AP is set as a sharing AP (SAP) after negotiation in multi-AP communication, and the first AP may be set as a shared AP (DAP) or a coordinated AP after negotiation in multi-AP communication. The non-AP STA of the present embodiment may correspond to at least one STA (station).

[0451] The present embodiment proposes a method for performing multi-AP cooperation (e.g., Co-TDMA, Co-SR, Co-BF, C-OFDMA, or J-TX) by selecting APs that share TXOPs or perform inter-AP cooperation. In particular, the present embodiment proposes a method for notifying or transmitting information related to the multi-AP cooperation by defining a management frame based on a common action frame to update information for MAPC.

[0452] At step S2810, the second AP (access point) receives a first management frame from the first AP to update (or renew) information for multi-AP coordination (MAPC).

[0453] At step S2820, the second AP decrypts the first management frame.

[0454] The first and second APs are either a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP.

[0455] The above first management frame includes a public action frame. The public action frame includes information regarding the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share.

[0456] Information about the TXOP period that the above-mentioned cooperative AP wishes to share may be set as a time in 16us units based on the Allocation Duration subfield of the User Information field of the MU-RTS (Multi User-Request To Send) TXS (TXOP Sharing) trigger frame, or may be set as the length of the PPDU (Physical Protocol Data Unit) required by the above-mentioned cooperative AP for the MAPC.

[0457] That is, the present embodiment proposes a method for defining a MAPC management frame based on the common action frame in order to update some information for the MAPC between APs participating in the MAPC. Previously, there was no appropriate frame that could be used as a frame for management purposes when APs participating in the MAPC were not connected to each other. However, as in the present embodiment, by defining the MAPC management frame based on the common action frame, request / response frames for multi-AP selection or information for MAPC can be transmitted and received between APs that are not connected depending on specific conditions or states, thereby enabling efficient MAPC operation.

[0458] As in the above-described embodiment, a MAPC management frame (unsolicited frame) defined based on the common action frame can be transmitted in a 1-way manner to update information for the multi-AP cooperation. Alternatively, a MAPC management request frame and a MAPC management response frame can be transmitted and received in a 2-way manner to update information for the multi-AP cooperation.

[0459] Specifically, the second AP may transmit a second management frame to the first AP. (Alternatively, the first AP may receive a second management frame from the second AP.) At this time, the first management frame may be a MAPC management request frame. The second management frame may be a MAPC management response frame.

[0460] As another example, the MAPC management frame defined based on the above public action frame can be utilized as an ICR role in the procedure of selecting multiple APs, which is a polling step.

[0461] Specifically, the second AP may transmit an ICF (Initial Control Frame) to the first AP. The second AP may receive an ICR (Initial Control Response) from the first AP. (Alternatively, the first AP may receive an ICF (Initial Control Frame) from the second AP. The first AP may transmit an ICR (Initial Control Response) to the second AP.) At this time, the ICF may be set to a BSRP (Buffer Status Report Poll) trigger frame if it is trigger-based. The ICR may be set to the common action frame.

[0462] The operation in the TXOP allocation step after the polling step for the above multi-AP cooperation is as follows.

[0463] Specifically, the second AP can transmit an MU-RTS TXS trigger frame to the first AP. The second AP can receive a CTS (Clear-To-Send) frame from the first AP. The first AP can exchange frames with a first non-AP STA during a first TXOP. (Alternatively, the first AP can receive an MU-RTS TXS trigger frame from the second AP. The first AP can transmit a CTS (Clear-To-Send) frame to the second AP. The first AP can exchange frames with a first non-AP STA during a first TXOP.) The first TXOP can be set based on an allocation interval subfield of the MU-RTS TXS trigger frame. The first non-AP STA is a non-AP STA within a BSS (Basic Service Set) of the first AP.

[0464] As another example, a MAPC management frame defined based on the above public action frame can be utilized for the purpose of returning a TXOP in the TXOP return phase.

[0465] Specifically, the second AP may receive a third management frame from the first AP during the first TXOP. (Alternatively, the first AP may transmit a third management frame to the second AP during the first TXOP.) In this case, the third management frame may be a MAPC management frame that returns the first TXOP. The third management frame may include information about the return of the TXOP shared via the MAPC.

[0466] The following is a description of the common action frame utilized in all of the steps for updating the above multi-AP cooperation, the above polling step, and the above TXOP return step.

[0467] The above common action frame may include a category field, a common action field, and an action detail field. Based on the category field being set to a reserved value (e.g., 54), the common action field may be set to a collaboration notification report field.

[0468] The above-mentioned cooperation notification report field includes information about the channel on which the APs participating in the MAPC operate, information about the bandwidth on which the APs participating in the MAPC operate, information about the TXOP section that the cooperative AP wishes to share, buffer status information of the cooperative AP, information about whether the cooperative AP requires TXOP sharing, information about low-latency traffic that the APs participating in the MAPC wish to transmit and receive, code information about whether to accept a selection request for the MAPC, information about whether to participate in the MAPC, information about the maximum transmission power preferred by the cooperative AP, information about a non-AP STA associated with the cooperative AP through the MAPC, version information of a non-AP STA that performs Co-SR (Coordinated-Spatial Reuse) transmission with the cooperative AP through the MAPC, information about the feedback type of information related to the MAPC, information about the type of the MAPC, information about the number of additional LTFs that is greater than the total number of spatial streams in the MAPC, and information about the number of additional LTFs that are greater than the total number of spatial streams in the MAPC and the cooperative AP through the MAPC. Information on the number of non-AP STAs supporting Co-BF (Coordinated-Beamforming), MCS (Modulation and Coding Scheme) information of the non-AP STAs supporting the Co-BF, information on the number of spatial streams of the non-AP STAs supporting the Co-BF, information on 2xLDPC (2xLow-Density Parity Check) of the non-AP STAs supporting the Co-BF, information on the number of data OFDM (Orthogonal frequency division multiplexing) symbols required by the cooperative AP, information on the bandwidth available to the cooperative AP within the bandwidth transmitted from the shared AP,The information may include at least one of information about a puncturing pattern of the cooperated AP within the puncturing pattern transmitted from the shared AP, information about a GI (Guard Interval) and LTF (Long Training Field) size recommended by the cooperated AP among the GI and LTF sizes transmitted by the shared AP, information about whether a procedure for transmitting an ICF (Initial Control Frame) to a connected non-AP STA is required before triggering the MAPC, and information about the return of a TXOP shared through the MAPC. (A specific description of the information is described in Section 1.2 Contents for Multi-AP Cooperation and Co-TDMA Operation of this specification.)

[0469] That is, one or more pieces of information included in the above cooperation notification report field can be used in the step for updating the multi-AP cooperation, the polling step, and the TXOP return step.

[0470] The above-described technique for multi-AP cooperation may include a coordinated multi-AP technique such as Co-TDMA (Coordinated-Time Division Multiplexing Access), Co-SR (Coordinated-Spatial Reuse), Co-BF (Coordinated-beamforming), or C-OFMA (Coordinated-Orthogonal Frequency Division Multiple Access).

[0471] FIG. 29 is a flowchart illustrating a procedure for a cooperative AP according to the present embodiment to transmit a management frame for updating information for MAPC.

[0472] An example of FIG. 29 can be performed in a network environment that supports a next-generation wireless LAN system (UHR (Ultra High Reliability) wireless LAN system or next wi-fi). The next-generation wireless LAN system is a wireless LAN system that improves on the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0473] An example of FIG. 29 is performed in a first AP, wherein the first AP may be set as a shared AP (DAP) or coordinated AP after negotiation in multi-AP communication, and the second AP may be set as a sharing AP (SAP) after negotiation in multi-AP communication. A non-AP STA of the present embodiment may correspond to at least one STA (station).

[0474] The present embodiment proposes a method for performing multi-AP cooperation (e.g., Co-TDMA, Co-SR, Co-BF, C-OFDMA, or J-TX) by selecting APs that share TXOPs or perform inter-AP cooperation. In particular, the present embodiment proposes a method for notifying or transmitting information related to the multi-AP cooperation by defining a management frame based on a common action frame to update information for MAPC.

[0475] In step S2910, the first AP (access point) configures a first management frame to update (or renew) information for multi-AP coordination (MAPC).

[0476] In step S2920, the first AP transmits the first management frame to the second AP.

[0477] The first and second APs are either a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP.

[0478] The above first management frame includes a public action frame. The public action frame includes information regarding the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share.

[0479] Information about the TXOP period that the above-mentioned cooperative AP wishes to share may be set as a time in 16us units based on the Allocation Duration subfield of the User Information field of the MU-RTS (Multi User-Request To Send) TXS (TXOP Sharing) trigger frame, or may be set as the length of the PPDU (Physical Protocol Data Unit) required by the above-mentioned cooperative AP for the MAPC.

[0480] That is, the present embodiment proposes a method for defining a MAPC management frame based on the common action frame in order to update some information for the MAPC between APs participating in the MAPC. Previously, there was no appropriate frame that could be used as a frame for management purposes when APs participating in the MAPC were not connected to each other. However, as in the present embodiment, by defining the MAPC management frame based on the common action frame, request / response frames for multi-AP selection or information for MAPC can be transmitted and received between APs that are not connected depending on specific conditions or states, thereby enabling efficient MAPC operation.

[0481] As in the above-described embodiment, a MAPC management frame (unsolicited frame) defined based on the common action frame can be transmitted in a one-way manner to update information for the multi-AP cooperation. Alternatively, a MAPC management request frame and a MAPC management response frame can be transmitted and received in a two-way manner to update information for the multi-AP cooperation.

[0482] Specifically, the second AP may transmit a second management frame to the first AP. (Alternatively, the first AP may receive a second management frame from the second AP.) At this time, the first management frame may be a MAPC management request frame. The second management frame may be a MAPC management response frame.

[0483] As another example, the MAPC management frame defined based on the above public action frame can be utilized as an ICR role in the procedure of selecting multiple APs, which is a polling step.

[0484] Specifically, the second AP may transmit an ICF (Initial Control Frame) to the first AP. The second AP may receive an ICR (Initial Control Response) from the first AP. (Alternatively, the first AP may receive an ICF (Initial Control Frame) from the second AP. The first AP may transmit an ICR (Initial Control Response) to the second AP.) At this time, the ICF may be set to a BSRP (Buffer Status Report Poll) trigger frame if it is trigger-based. The ICR may be set to the common action frame.

[0485] The operation in the TXOP allocation step after the polling step for the above multi-AP cooperation is as follows.

[0486] Specifically, the second AP can transmit an MU-RTS TXS trigger frame to the first AP. The second AP can receive a CTS (Clear-To-Send) frame from the first AP. The first AP can exchange frames with a first non-AP STA during a first TXOP. (Alternatively, the first AP can receive an MU-RTS TXS trigger frame from the second AP. The first AP can transmit a CTS (Clear-To-Send) frame to the second AP. The first AP can exchange frames with a first non-AP STA during a first TXOP.) The first TXOP can be set based on an allocation interval subfield of the MU-RTS TXS trigger frame. The first non-AP STA is a non-AP STA within a BSS (Basic Service Set) of the first AP.

[0487] As another example, a MAPC management frame defined based on the above public action frame can be utilized for the purpose of returning a TXOP in the TXOP return phase.

[0488] Specifically, the second AP may receive a third management frame from the first AP during the first TXOP. (Alternatively, the first AP may transmit a third management frame to the second AP during the first TXOP.) In this case, the third management frame may be a MAPC management frame that returns the first TXOP. The third management frame may include information about the return of the TXOP shared via the MAPC.

[0489] The following is a description of the common action frame utilized in all of the steps for updating the above multi-AP cooperation, the above polling step, and the above TXOP return step.

[0490] The above common action frame may include a category field, a common action field, and an action detail field. Based on the category field being set to a reserved value (e.g., 54), the common action field may be set to a collaboration notification report field.

[0491] The above-mentioned cooperation notification report field includes information about the channel on which the APs participating in the MAPC operate, information about the bandwidth on which the APs participating in the MAPC operate, information about the TXOP section that the cooperative AP wishes to share, buffer status information of the cooperative AP, information about whether the cooperative AP requires TXOP sharing, information about low-latency traffic that the APs participating in the MAPC wish to transmit and receive, code information about whether to accept a selection request for the MAPC, information about whether to participate in the MAPC, information about the maximum transmission power preferred by the cooperative AP, information about a non-AP STA associated with the cooperative AP through the MAPC, version information of a non-AP STA that performs Co-SR (Coordinated-Spatial Reuse) transmission with the cooperative AP through the MAPC, information about the feedback type of information related to the MAPC, information about the type of the MAPC, information about the number of additional LTFs that is greater than the total number of spatial streams in the MAPC, and information about the number of additional LTFs that are greater than the total number of spatial streams in the MAPC and the cooperative AP through the MAPC. Information on the number of non-AP STAs supporting Co-BF (Coordinated-Beamforming), MCS (Modulation and Coding Scheme) information of the non-AP STAs supporting the Co-BF, information on the number of spatial streams of the non-AP STAs supporting the Co-BF, information on 2xLDPC (2xLow-Density Parity Check) of the non-AP STAs supporting the Co-BF, information on the number of data OFDM (Orthogonal frequency division multiplexing) symbols required by the cooperative AP, information on the bandwidth available to the cooperative AP within the bandwidth transmitted from the shared AP,The information may include at least one of information about a puncturing pattern of the cooperated AP within the puncturing pattern transmitted from the shared AP, information about a GI (Guard Interval) and LTF (Long Training Field) size recommended by the cooperated AP among the GI and LTF sizes transmitted by the shared AP, information about whether a procedure for transmitting an ICF (Initial Control Frame) to a connected non-AP STA is required before triggering the MAPC, and information about the return of a TXOP shared through the MAPC. (A specific description of the information is described in Section 1.2 Contents for Multi-AP Cooperation and Co-TDMA Operation of this specification.)

[0492] That is, one or more pieces of information included in the above cooperation notification report field can be used in the step for updating the multi-AP cooperation, the polling step, and the TXOP return step.

[0493] The above-described technique for multi-AP cooperation may include a coordinated multi-AP technique such as Co-TDMA (Coordinated-Time Division Multiplexing Access), Co-SR (Coordinated-Spatial Reuse), Co-BF (Coordinated-beamforming), or C-OFMA (Coordinated-Orthogonal Frequency Division Multiple Access).

[0494] <Device Configuration>

[0495] The technical features of the present specification described above can be applied to various devices and methods. For example, the technical features of the present specification described above can be performed / supported by the devices of FIG. 1 and / or FIG. 13. For example, the technical features of the present specification described above can be applied only to a part of FIG. 1 and / or FIG. 13. For example, the technical features of the present specification described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and the memory (112, 122) of FIG. 1, or based on the processor (610) and the memory (620) of FIG. 13. For example, the device of the present specification configures a first management frame for updating information for multi-AP coordination (MAPC); and transmits the first management frame to a second access point (AP).

[0496] The technical features of this specification can be implemented based on a computer-readable medium (CRM). For example, the CRM proposed by this specification is at least one computer-readable recording medium containing instructions that are executed by at least one processor.

[0497] The CRM may store instructions for performing operations including: configuring a first management frame for updating information for multi-AP coordination (MAPC); and transmitting the first management frame to a second access point (AP). The instructions stored in the CRM of the present specification may be executed by at least one processor. At least one processor related to the CRM of the present specification may be the processor (111, 121) or processing chip (114, 124) of FIG. 1, or the processor (610) of FIG. 13. Meanwhile, the CRM of the present specification may be the memory (112, 122) of FIG. 1, the memory (620) of FIG. 13, or a separate external memory / storage medium / disk, etc.

[0498] The technical features of this specification described above are applicable to various applications and business models. For example, the technical features described above can be applied to wireless communication in devices that support artificial intelligence (AI).

[0499] Artificial intelligence (AI) is the study of artificial intelligence or the methodologies for creating it, while machine learning (ML) defines various problems in the field of AI and studies the methodologies for solving them. Machine learning is also defined as an algorithm that improves performance on a task through consistent experience.

[0500] An artificial neural network (ANN) is a model used in machine learning. It can refer to a model with problem-solving capabilities, consisting of artificial neurons (nodes) formed by the connection of synapses to form a network. An ANN can be defined by the connection patterns between neurons in different layers, the learning process that updates model parameters, and the activation function that generates output values.

[0501] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses connecting neurons. In an artificial neural network, each neuron can output a function value of an activation function based on input signals, weights, and biases received through the synapses.

[0502] Model parameters are parameters determined through learning, including synaptic connection weights and neuron biases. Hyperparameters are parameters that must be set before learning in machine learning algorithms, including the learning rate, number of iterations, mini-batch size, and initialization function.

[0503] The goal of artificial neural network training can be seen as determining model parameters that minimize a loss function. The loss function can be used as an indicator for determining optimal model parameters during the artificial neural network training process.

[0504] Machine learning can be classified into supervised learning, unsupervised learning, and reinforcement learning depending on the learning method.

[0505] Supervised learning refers to a method for training an artificial neural network when given labels for the training data. The labels can refer to the correct answer (or output value) that the artificial neural network must infer when the training data is input to the artificial neural network. Unsupervised learning can refer to a method for training an artificial neural network when the training data is not given labels. Reinforcement learning can refer to a learning method in which an agent defined within a given environment is trained to select actions or action sequences that maximize the cumulative reward in each state.

[0506] Machine learning implemented with a deep neural network (DNN) containing multiple hidden layers among artificial neural networks is also called deep learning, and deep learning is a subset of machine learning. Hereinafter, the term "machine learning" is used to encompass deep learning.

[0507] Additionally, the above-described technical features can be applied to wireless communication of robots.

[0508] A robot can be defined as a machine that automatically performs or operates a given task based on its own capabilities. Specifically, a robot capable of perceiving its environment, making independent judgments, and performing actions can be called an intelligent robot.

[0509] Robots can be categorized into industrial, medical, household, and military applications based on their intended use or field. Robots are equipped with actuators or motors, enabling them to perform various physical actions, such as moving robot joints. Furthermore, mobile robots incorporate wheels, brakes, and propellers into their actuators, enabling them to move on the ground or fly in the air.

[0510] Additionally, the above-described technical features can be applied to devices that support extended reality.

[0511] Extended reality is a general term for virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology presents real-world objects and backgrounds as CG images only, AR technology presents virtual CG images over images of real objects, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0512] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0513] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

[0514] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a wireless LAN system, A step in which a first AP (access point) configures a first management frame for updating information for multi-AP coordination (MAPC); and The first AP comprises a step of transmitting the first management frame to the second AP, The first and second APs are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. method.

2. In paragraph 1, Information about the TXOP section that the above-mentioned cooperative AP wishes to share is set to a time in units of 16us based on the Allocation Duration subfield of the User Information field of the MU-RTS (Multi User-Request To Send) TXS (TXOP Sharing) trigger frame, or is set to the length of the PPDU (Physical Protocol Data Unit) required by the above-mentioned cooperative AP for the MAPC. method.

3. In paragraph 1, The first AP further comprises a step of receiving a second management frame from the second AP, The above first management frame is a MAPC management request frame, The above second management frame is a MAPC management response frame. method.

4. In paragraph 1, The above public action frame includes a category field, a public action field, and an action detail field, Based on the above category field being set to a reserved value, the above public action field is set to a collaboration notification reporting field, The above-mentioned cooperation notification report field includes information about the channel on which the APs participating in the MAPC operate, information about the bandwidth on which the APs participating in the MAPC operate, information about the TXOP section that the cooperative AP wishes to share, buffer status information of the cooperative AP, information about whether the cooperative AP requires TXOP sharing, information about low-latency traffic that the APs participating in the MAPC wish to transmit and receive, code information about whether to accept a selection request for the MAPC, information about whether to participate in the MAPC, information about the maximum transmission power preferred by the cooperative AP, information about a non-AP STA associated with the cooperative AP through the MAPC, version information of a non-AP STA that performs Co-SR (Coordinated-Spatial Reuse) transmission with the cooperative AP through the MAPC, information about the feedback type of information related to the MAPC, information about the type of the MAPC, information about the number of additional LTFs that is greater than the total number of spatial streams in the MAPC, and information about the number of additional LTFs that are greater than the total number of spatial streams in the MAPC and the cooperative AP through the MAPC. Information on the number of non-AP STAs supporting Co-BF (Coordinated-Beamforming), MCS (Modulation and Coding Scheme) information of the non-AP STAs supporting the Co-BF, information on the number of spatial streams of the non-AP STAs supporting the Co-BF, information on 2xLDPC (2xLow-Density Parity Check) of the non-AP STAs supporting the Co-BF, information on the number of data OFDM (Orthogonal frequency division multiplexing) symbols required by the cooperative AP, information on the bandwidth available to the cooperative AP within the bandwidth transmitted from the shared AP,Information about the puncturing pattern of the cooperated AP within the puncturing pattern transmitted from the shared AP, information about the GI (Guard Interval) and LTF (Long Training Field) sizes recommended by the cooperated AP among the GI and LTF sizes transmitted by the shared AP, information about whether a procedure for transmitting an ICF (Initial Control Frame) to a connected non-AP STA is required before triggering the MAPC, and information about the return of a TXOP shared through the MAPC, including at least one of: method.

5. In paragraph 4, A step in which the first AP receives an ICF (Initial Control Frame) from the second AP; and The first AP further includes a step of transmitting an ICR (Initial Control Response) to the second AP, If the above ICF is trigger-based, it is set to a BSRP (Buffer Status Report Poll) trigger frame, The above ICR is set to the above public action frame method.

6. In paragraph 4, A step in which the first AP receives an MU-RTS TXS trigger frame from the second AP; A step in which the first AP transmits a CTS (Clear-To-Send) frame to the second AP; The first AP further includes a step of exchanging frames with a first non-AP STA during a first TXOP, The above first TXOP is set based on the allocation interval subfield of the MU-RTS TXS trigger frame. method.

7. In paragraph 6, The first AP further comprises a step of transmitting a third management frame to the second AP during the first TXOP, The above third management frame is a MAPC management frame that returns the above first TXOP, The third management frame includes information about the return of the TXOP shared through the MAPC. method.

8. In a wireless LAN system, the first AP (access point) is memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Configure a first management frame to update information for multi-AP coordination (MAPC); and Transmit the first management frame to the second AP, The first and second APs are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. 1st AP.

9. In a wireless LAN system, A step in which a second AP (access point) receives a first management frame for updating information for multi-AP coordination (MAPC) from a first AP; and The second AP includes a step of decoding the first management frame, The first and second APs are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. method.

10. In paragraph 9, Information about the TXOP section that the above-mentioned cooperative AP wishes to share is set to a time in units of 16us based on the Allocation Duration subfield of the User Information field of the MU-RTS (Multi User-Request To Send) TXS (TXOP Sharing) trigger frame, or is set to the length of the PPDU (Physical Protocol Data Unit) required by the above-mentioned cooperative AP for the MAPC. method.

11. In paragraph 9, The second AP further includes a step of transmitting a second management frame to the first AP, The above first management frame is a MAPC management request frame, The above second management frame is a MAPC management response frame. method.

12. In paragraph 9, The above public action frame includes a category field, a public action field, and an action detail field, Based on the above category field being set to a reserved value, the above public action field is set to a collaboration notification reporting field, The above-mentioned cooperation notification report field includes information about the channel on which the APs participating in the MAPC operate, information about the bandwidth on which the APs participating in the MAPC operate, information about the TXOP section that the cooperative AP wishes to share, buffer status information of the cooperative AP, information about whether the cooperative AP requires TXOP sharing, information about low-latency traffic that the APs participating in the MAPC wish to transmit and receive, code information about whether to accept a selection request for the MAPC, information about whether to participate in the MAPC, information about the maximum transmission power preferred by the cooperative AP, information about a non-AP STA associated with the cooperative AP through the MAPC, version information of a non-AP STA that performs Co-SR (Coordinated-Spatial Reuse) transmission with the cooperative AP through the MAPC, information about the feedback type of information related to the MAPC, information about the type of the MAPC, information about the number of additional LTFs that is greater than the total number of spatial streams in the MAPC, and information about the number of additional LTFs that are greater than the total number of spatial streams in the MAPC and the cooperative AP through the MAPC. Information on the number of non-AP STAs supporting Co-BF (Coordinated-Beamforming), MCS (Modulation and Coding Scheme) information of the non-AP STAs supporting the Co-BF, information on the number of spatial streams of the non-AP STAs supporting the Co-BF, information on 2xLDPC (2xLow-Density Parity Check) of the non-AP STAs supporting the Co-BF, information on the number of data OFDM (Orthogonal frequency division multiplexing) symbols required by the cooperative AP, information on the bandwidth available to the cooperative AP within the bandwidth transmitted from the shared AP,Information about the puncturing pattern of the cooperated AP within the puncturing pattern transmitted from the shared AP, information about the GI (Guard Interval) and LTF (Long Training Field) sizes recommended by the cooperated AP among the GI and LTF sizes transmitted by the shared AP, information about whether a procedure for transmitting an ICF (Initial Control Frame) to a connected non-AP STA is required before triggering the MAPC, and information about the return of a TXOP shared through the MAPC, including at least one of: method.

13. In paragraph 12, A step in which the second AP transmits an ICF (Initial Control Frame) to the first AP; and The second AP further includes a step of receiving an ICR (Initial Control Response) from the first AP, If the above ICF is trigger-based, it is set to a BSRP (Buffer Status Report Poll) trigger frame, The above ICR is set to the above public action frame method.

14. In paragraph 12, The second AP transmits an MU-RTS TXS trigger frame to the first AP; and The second AP further includes a step of receiving a CTS (Clear-To-Send) frame from the first AP, The first AP exchanges frames with the first non-AP STA during the first TXOP, The above first TXOP is set based on the allocation interval subfield of the MU-RTS TXS trigger frame. method.

15. In paragraph 14, The second AP further comprises a step of receiving a third management frame from the first AP during the first TXOP, The above third management frame is a MAPC management frame that returns the above first TXOP, The third management frame includes information about the return of the TXOP shared through the MAPC. method.

16. In a wireless LAN system, the second AP (access point) is memory; transceiver; and A processor operatively coupled to the memory and the transceiver, the processor comprising: Receive a first management frame for updating information for multi-AP coordination (MAPC) from a first AP; and Decrypt the above first management frame, The first and second APs are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. 2nd AP.

17. At least one computer-readable recording medium containing instructions based on being executed by at least one processor, A step of configuring a first management frame for updating information for multi-AP coordination (MAPC); and Including a step of transmitting the first management frame to a second AP (access point), The first AP and the second AP are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. Recording medium.

18. In a wireless LAN system, in a device, memory; and A processor operatively coupled to the memory, the processor comprising: Configure a first management frame to update information for multi-AP coordination (MAPC); and Transmit the first management frame to the second AP (access point), The first AP and the second AP are a sharing AP that controls the MAPC or a coordinated AP that is allocated or shares resources from the sharing AP. The above first management frame includes a public action frame, and The above public action frame contains information about the TXOP (Transmit Opportunity) section that the cooperated AP wishes to share. device.

Images