Method and device for transmitting and configuring coordination trigger frame in order to perform MAPC transmission in wireless LAN system

Abstract

Proposed are a method and device for transmitting and configuring a coordination trigger frame in order to perform MAPC transmission in a wireless LAN system. Specifically, a first AP transmits a coordination invitation frame to a second AP. The first AP receives a coordination response frame from the second AP. The first AP transmits the coordination trigger frame to the second AP. The coordination trigger frame includes information about a PHY version of a first PPDU transmitted by the first AP and a PHY version of a second PPDU transmitted by the second AP.

Description

Method and device for transmitting and configuring cooperative trigger frames to perform MAPC transmission in a wireless LAN system

[0001] The present specification relates to a technique for transmitting and configuring cooperative trigger frames to perform MAPC transmission in a wireless LAN system, and more specifically, to a method and apparatus for transmitting and receiving by including information necessary for said Co-SR / Co-BF transmission in cooperative invitation frames, cooperative response frames, and cooperative trigger frames used for frame switching to perform Co-SR / Co-BF transmission.

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

[0003] This specification proposes a method and apparatus for transmitting and configuring cooperative trigger frames to perform MAPC transmission in a wireless LAN system.

[0004] An example of the present specification proposes a method for transmitting and configuring a cooperative trigger frame to perform MAPC transmission.

[0005] This 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[0006] This embodiment may be performed at a first AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be established as a coordinating AP or a coordinated AP through the MAPC negotiation.

[0007] The present embodiment proposes a sequence for performing frame exchange to perform Co-SR / Co-BF transmission. Specifically, the present embodiment proposes a method for transmitting and receiving by including information necessary for said Co-SR / Co-BF transmission in a cooperative invitation frame, a cooperative response frame, and a cooperative trigger frame.

[0008] The first AP (access point) sends a Coordination Invite frame to the second AP.

[0009] The first AP receives a cooperation response frame from the second AP.

[0010] The first AP transmits a cooperation trigger frame to the second AP.

[0011] The first AP is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP. The second AP is a coordinated AP that participates in the MAPC transmission.

[0012] The above-mentioned cooperation trigger frame may include information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. The information regarding the PHY versions may include information regarding whether the first and second PPDUs are Ultra-High Reliability (UHR) or Extremely High Throughput (EHT), etc.

[0013] That is, the present embodiment proposes a method for configuring a frame exchange procedure by including information necessary for Co-SR / Co-BF transmission in the cooperative invitation frame, cooperative response frame, and cooperative trigger frame used for frame exchange for the MAPC transmission.

[0014] According to the embodiments proposed in this specification, i) precise adjustment of transmission timing and beam patterns between multiple APs is possible (since each cooperating AP receiving a cooperating trigger frame can recognize in advance PHY layer parameters such as the transmission timing of DL PPDU of other APs, MCS (Modulation and Coding Scheme), bandwidth, and transmission power, interference minimization and beam alignment can be performed precisely during Co-BF execution), ii) maximization of Co-SR efficiency (since each AP can dynamically adjust its own transmission power based on parameters related to transmission power and spatial reuse of adjacent APs, spatial reuse efficiency within the same channel is improved, and the frequency utilization efficiency of the entire system is increased), iii) reduction of collisions and interference between frames (since each AP can perform transmission timing and power control to minimize mutual interference due to the sharing of PHY information through cooperating trigger frames, collisions or interference between PPDUs that may occur during simultaneous transmission by multiple APs can be effectively mitigated), iv) improvement of reliability and synchronization of the MAPC procedure (the PHY information included in the trigger frame is cooperating AP Since the transmission sequence and transmission conditions between them are clearly defined, explicit and highly reliable synchronization is possible compared to existing implicit synchronization methods.), v) improvement in overall system throughput (due to interference reduction and improved space reuse efficiency, the DL transmission throughput of the entire network is improved, and stable high-speed transmission becomes possible, especially in high-density AP deployment environments).

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

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

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

[0018] FIG. 4 illustrates an example of a multi-link (ML).

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

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

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

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

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

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

[0025] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0026] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0027] FIG. 13 shows a modified example of a transmitting device and / or 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 Coordinated Beamforming (CBF).

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

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

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

[0034] Figure 20 shows an example of coordinated TDMA operation including the discovery, negotiation / agreement process.

[0035] FIG. 21 illustrates an example of a sequence for exchanging Co-SR frames through a sequential CA procedure within a single TXOP.

[0036] FIG. 22 illustrates an example of a sequence for exchanging Co-SR frames through the reception of TB PPDU within a single TXOP.

[0037] FIG. 23 illustrates an example of a sequence for exchanging Co-SR frames through a sequential CA procedure in a separate TXOP.

[0038] FIG. 24 illustrates an example of a sequence for exchanging Co-SR frames through the reception of TB PPDU in a separate TXOP.

[0039] FIG. 25 illustrates an example of a Co-BF sequence through coordination announcement performed within a single TXOP.

[0040] Figure 26 illustrates an example of a Co-BF sequence through a coordination announcement performed in a separate TXOP.

[0041] Figure 27 illustrates an example of a Co-BF sequence by immediate triggering.

[0042] FIG. 28 illustrates an example of a BSRP TF-based Co-SR / Co-BF transmission trigger procedure.

[0043] FIG. 29 illustrates an example of a Co-SR / Co-BF transmission trigger procedure following a BSRP TF-based polling procedure.

[0044] FIG. 30 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[0045] FIG. 31 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

[0046] FIG. 32 is a flowchart illustrating the procedure for receiving a cooperative trigger frame to perform Co-SR / Co-BF transmission according to the present embodiment.

[0047] FIG. 33 is a flowchart illustrating the procedure for transmitting and configuring a cooperative trigger frame to perform Co-SR / Co-BF transmission according to the present embodiment.

[0048] In this specification, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in this specification, “A or B” may be interpreted as “A and / or B.” For example, in this specification, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0049] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B, or C.”

[0050] In this specification, “at least one of A and B” may 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” may be interpreted as synonymous with “at least one of A and B.”

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

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

[0053] Additionally, the expressions “based on,” “on the basis of,” or “according to” as used in this specification mean “based at least in part on,” and do not mean “based only on one.”

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

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

[0056] To explain the technical features of this specification, the technical features to which this specification can be applied are described below.

[0057] FIG. 1 shows an example of a transmitting device and / or receiving device of the present specification.

[0058] 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 this specification may also be referred to by various names such as mobile terminal, wireless device, Wireless Transmit / Receive Unit (WTRU), User Equipment (UE), Mobile Station (MS), Mobile Subscriber Unit, or simply user. The STA (110, 120) of this specification may also be referred to by various names such as network, base station, Node-B, Access Point (AP), repeater, router, relay, etc. The STA (110, 120) of this specification may also be referred to by various names such as receiving apparatus, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

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

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

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

[0062] Based on side drawing (a) of Fig. 1, STA (110, 120) is described as follows.

[0063] The first STA (110) may include a processor (111), 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.

[0064] The transceiver (113) of the first STA performs the operation of transmitting and receiving signals. Specifically, it can transmit and receive IEEE 802.11 packets (e.g., IEEE 802.11a / b / g / n / ac / ax / be, etc.).

[0065] 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 transmitted signal, and perform control for transmitting the signal. The memory (112) of the AP can store the signal received through the transceiver (113) (i.e., the received signal) and the signal to be transmitted through the transceiver (i.e., the transmitted signal).

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

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

[0068] For example, the operation of the device indicated as AP in the following specification may be performed in the first STA (110) or the second STA (120). For example, if the first STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (111) of the first STA (110), and related signals may be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (110). Additionally, control information related to the operation of the AP or the transmission / reception signals of the AP may be stored in the memory (112) of the first STA (110). Additionally, if the second STA (110) is the AP, the operation of the device indicated as AP is controlled by the processor (121) of the second STA (120), and related signals 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 AP or the transmission / reception signals of the AP can be stored in the memory (122) of the second STA (110).

[0069] For example, the operation of a device indicated as non-AP (or User-STA) in the following specification may be performed in the STA (110) or the second STA (120). For example, if the second STA (120) is non-AP, the operation of the device indicated as non-AP is controlled by the processor (121) of the second STA (120), and related signals may be transmitted or received through a transceiver (123) controlled by the processor (121) of the second STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signals 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 the device marked as non-AP is controlled by the processor (111) of the first STA (110), and the related signal can be transmitted or received through a transceiver (113) controlled by the processor (111) of the first STA (120). Additionally, control information related to the operation of the non-AP or the transmission / reception signal of the AP can be stored in the memory (112) of the first STA (110).

[0070] In the following specification, a device referred to as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may refer to the STA (110, 120) of FIG. 1. For example, a device indicated without specific drawing symbols as (transmission / reception) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmission / reception) Terminal, (transmission / reception) device, (transmission / reception) apparatus, network, etc. may also refer to the STA (110, 120) of FIG. 1. For example, in the following example, the operation of various STAs transmitting and receiving signals (e.g., PPDU) may be performed by the transceivers (113, 123) of FIG. 1. Additionally, in the following example, 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 to generate a transmission / reception signal or to perform data processing or operations in advance for a transmission / reception signal may include: 1) an operation to determine / acquire / configure / operate / decode / encode bit information of sub-fields (SIG, STF, LTF, Data) included in the PPDU; 2) an operation to determine / configure / acquire time resources or frequency resources (e.g., subcarrier resources) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 3) an operation to determine / configure / acquire specific sequences (e.g., pilot sequence, STF / LTF sequence, extra sequence applied to SIG) used for sub-fields (SIG, STF, LTF, Data) included in the PPDU; 4) a power control operation and / or power saving operation applied to the STA; and 5) an operation related to determining / acquiring / configuring / operating / decoding / encoding of an ACK signal. In addition, in the following example, various information (e.g., information related to fields, subfields, control fields, parameters, power, etc.) used by various STAs for determining / acquiring / configuring / calculating / decoding / encoding of transmission and reception signals can be stored in the memory (112, 122) of FIG. 1.

[0071] The device / STA of the aforementioned supplementary drawing (a) of FIG. 1 can be modified as shown in supplementary drawing (b) of FIG. 1. Hereinafter, the STA (110, 120) of this specification will be described based on supplementary drawing (b) of FIG. 1.

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

[0073] 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, AP (Access Point), 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) shown in side drawings (a) / (b) of FIG. 1, or the processing chip (114, 124) shown in side drawing (b) of FIG. 1. That is, the technical features of the present specification may be performed in the STA (110, 120) shown in side drawings (a) / (b) of FIG. 1, or only in the processing chip (114, 124) shown in side drawing (b) of FIG. 1. For example, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal generated in the processor (111, 121) shown in side drawings (a) / (b) of FIG. 1 is transmitted through the transceiver (113, 123) shown in side drawings (a) / (b) of FIG. 1. Alternatively, the technical feature of the transmitting STA transmitting a control signal may be understood as a technical feature in which a control signal to be transmitted from the processing chip (114, 124) shown in side drawing (b) of FIG. 1 is generated to the transceiver (113, 123).

[0074] For example, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal being received by the transceivers (113, 123) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceivers (113, 123) shown in side view (a) of FIG. 1 being acquired by the processor (111, 121) shown in side view (a) of FIG. 1. Alternatively, the technical feature of the receiving STA receiving a control signal can be understood as the technical feature of the control signal received by the transceivers (113, 123) shown in side view (b) of FIG. 1 being acquired by the processing chip (114, 124) shown in side view (b) of FIG. 1.

[0075] Referring to side view (b) of FIG. 1, software code (115, 125) may be included in 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.

[0076] The processor (111, 121) or processing chip (114, 124) illustrated in FIG. 1 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. 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 a processor enhanced therefrom.

[0077] In this specification, an uplink may refer to a link for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc. may be transmitted through the uplink. Additionally, in this specification, a downlink may refer to a link for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc. may be transmitted through the downlink.

[0078] Figure 2 is a conceptual diagram showing the structure of a wireless LAN (WLAN).

[0079] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0080] The top of Figure 2 shows the structure of the IEEE (Institute of Electrical and Electronic Engineers) 802.11 infrastructure BSS (basic service set).

[0081] Referring to the top of FIG. 2, the wireless LAN system may include one or more infrastructure BSSs (200, 205) (hereinafter BSS). The BSS (200, 205) is a set of APs and STAs, such as an AP (access point, 225) and STA1 (Station, 200-1), that can communicate with each other by successfully synchronizing, and is not a concept referring to a specific area. The BSS (205) may include one or more STAs (205-1, 205-2) that can be combined with one AP (230).

[0082] The BSS may include at least one STA, an AP (225, 230) that provides a distribution service, and a distribution system (DS, 210) that connects multiple APs.

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

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

[0085] In a BSS like the one at the top 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 between STAs and perform communication without APs (225, 230). A network that establishes a network between STAs and performs communication without APs (225, 230) is defined as an ad-hoc network or an independent basic service set (IBSS).

[0086] The bottom of Fig. 2 is a conceptual diagram showing IBSS.

[0087] 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 performs management functions centrally. 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 since access to the distributed system is not allowed, they form a self-contained network.

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

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

[0090] Figure 3 illustrates a network discovery operation that includes an active scanning process as an example. In active scanning, the STA performing the scanning moves between channels and transmits a probe request frame to search for nearby APs, and waits for a response. The responder transmits a probe response frame as a response to the probe request frame to the STA that transmitted the probe request frame. Here, the responder may be the STA that last transmitted a beacon frame from the BSS of the channel being scanned. In a BSS, the AP becomes the responder because it transmits the beacon frame, whereas in an IBSS, the responder is not constant because STAs within the IBSS take turns transmitting the beacon frame. For example, an STA that transmits a probe request frame on channel 1 and receives a probe response frame on channel 1 can store BSS-related information included in the received probe response frame and move to the next channel (e.g., channel 2) to perform scanning in the same way (i.e., transmit and receive probe request / response on channel 2).

[0091] Although not shown in the example of Fig. 3, scanning operations may also be performed using a passive scanning method. An STA performing scanning based on passive scanning can wait for a beacon frame while switching between channels. A beacon frame is one of the management frames in IEEE 802.11, which announces the presence of a wireless network and is periodically transmitted to allow a scanning STA to find the wireless network and join it. In a BSS, the AP performs the role of periodically transmitting beacon frames, while in an IBSS, STAs within the IBSS take turns transmitting beacon frames. When a scanning STA receives a beacon frame, it stores the information about the BSS included in the beacon frame and records the beacon frame information in each channel while moving to another channel. An STA that has received a beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner.

[0092] The STA that discovered the 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 later. The authentication process of S320 may include the STA sending an authentication request frame to the AP, and the AP sending an authentication response frame to the STA in response. The authentication frame used in the authentication request / response corresponds to a management frame.

[0093] The authentication frame may include information regarding the authentication algorithm number, authentication transaction sequence number, status code, challenge text, RSN (Robust Security Network), Finite Cyclic Group, etc.

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

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

[0096] Subsequently, 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 4-way handshake via an EAPOL (Extensible Authentication Protocol over LAN) frame.

[0097] FIG. 4 illustrates an example of a multi-link (ML).

[0098] As illustrated in FIG. 4, multiple multi-link devices (MLDs) can communicate through a multi-link. The MLDs can be classified into an AP MLD containing multiple AP STAs and a non-AP MLD containing multiple non-AP STAs. That is, the AP MLD may include affiliated APs (i.e., AP STAs), and the non-AP MLD may include affiliated STAs (i.e., non-AP STAs, or user-STAs).

[0099] A multilink may include a first link and a second link, and different channels / subchannels / frequency resources may be assigned to the first and second links. The first and second multilinks may be identified by 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 link may be configured in different bands.

[0100] The AP MLD of FIG. 4 includes three affiliated APs. In one 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 one 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. Additionally, in one 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. Additionally, in one 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.

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

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

[0103] FIG. 5 illustrates a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received in an STA of the present specification.

[0104] The STAs of this specification (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) can transmit and / or receive the PPDU of FIG. 5. The PPDU described in this specification may have the structure of FIG. 5, for example. Additionally, the PPDU described in this specification, the Ultra High Reliability (UHR) PPDU, may be referred to by various names such as transmit PPDU, receive PPDU, first type or N type PPDU. The PPDU described in this specification may be used in WLAN systems defined according to IEEE 802.11bn and / or next-generation WLAN systems that improve upon IEEE 802.11bn.

[0105] 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 SU (single-user) mode / type / transmission, MU (multi-user) mode / type / transmission, and NDP (null data packet) mode / type / transmission related to channel sounding. For example, if the example of FIG. 5 is related to NDP, the illustrated Data field may be omitted. If the PPDU of FIG. 5 is used for TB (Trigger-based) mode, the UHR-SIG of FIG. 5 may be omitted. In other words, an STA that receives a Trigger frame for UL-MU (Uplink-MU) communication may transmit a PPDU in which the UHR-SIG is omitted in the example of FIG. 5.

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

[0107] Each block illustrated in FIG. 5 may be referred to as a field / subfield / signal, etc. As illustrated in FIG. 5, the names of these fields / subfields / signals may be 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.

[0108] The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields in Fig. 5 can be set to 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can 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 can be displayed in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be displayed in units of 78.125 kHz.

[0109] The PPDU of Fig. 5, L-LTF and L-STF, may be the same as conventional fields (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0110] The L-SIG field of FIG. 5 may contain, 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 contain information regarding the length or time duration of the PPDU. For example, the value of the 12-bit Length field may be determined based on the type of the PPDU. For example, 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 a UHR PPDU, the value of the Length field may be determined as a multiple of 3. For example, if the PPDU is an 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, or 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 a UHR PPDU is set to a value satisfying the condition that the remainder is zero when LENGTH is divided by 3.

[0111] For example, a (non-AP and AP) STA can apply BCC encoding based on a code rate of 1 / 2 to 24 bits of information in the L-SIG field. Subsequently, the transmitting STA can obtain 48 bits of BCC encoding. BPSK modulation can be applied to the 48 bits of encoding to generate 48 BPSK symbols. The transmitting STA can map the 48 BPSK symbols to positions excluding the pilot subcarrier {subcarrier indices -21, -7, +7, +21} and the DC subcarrier {subcarrier index 0}. Consequently, 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 of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation for the frequency domain corresponding to {-28, -27, +27, +28}.

[0112] For example, the (non-AP and AP) STA can generate an RL-SIG that is identical to the L-SIG. BPSK modulation may be applied to the RL-SIG. The receiving (non-AP and AP) STA can determine that the received PPDU is a HE PPDU, EHT PPDU, or UHR PPDU based on the presence of the RL-SIG. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the HE PPDU, EHT PPDU, or UHR PPDU if the RL-SIG is present. In other words, the receiving (non-AP and AP) STA can determine that the received PPDU is one of the non-HT PPDU, HT PPDU, or VHT PPDU if the RL-SIG is not present. 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.

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

[0114] U-SIG may contain N bits of information and may contain information to identify the type of EHT PPDU. For example, U-SIG may be constructed based on two symbols (e.g., two consecutive OFDM symbols). Each symbol for U-SIG (e.g., OFDM symbol) may have a duration of 4 us. Each symbol of U-SIG may be used to transmit 26 bits of information. For example, each symbol of U-SIG may be transmitted and received based on 52 data tones and 4 pilot tones.

[0115] For example, A bit information (e.g., 52 un-coded bits) can be transmitted through U-SIG, and the first symbol of U-SIG can transmit the first X bit information (e.g., 26 un-coded bits) of the total A bit information, and the second symbol of U-SIG can transmit the remaining Y bit information (e.g., 26 un-coded bits) of the total A bit information. For example, the transmitting STA can obtain the 26 un-coded bits included in each U-SIG symbol. The transmitting STA can generate 52-coded bits by performing convolutional encoding (i.e., BCC encoding) based on a rate of R=1 / 2 and can perform interleaving on the 52-coded bits. The transmitting STA can generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52-coded bits. 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. 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.

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

[0117] A bit information (e.g., 52 un-coded bits) transmitted by 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 may be assigned only to the first symbol of U-SIG, or the version-independent bits may be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to by various names, such as the first control bit and the second control bit.

[0118] For example, the version-independent bits of 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 of the 3-bit PHY version identifier (e.g., a value of 000) may indicate that the transmitted and received PPDU is an EHT PPDU. Additionally, a second value of the 3-bit PHY version identifier (e.g., a value of 001) may indicate that the transmitted and received PPDU is a UHR PPDU.

[0119] In other words, when an (AP / non-AP) STA transmits an EHT PPDU, it can set a 3-bit PHY version identifier to a first value. In other words, a 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 a UHR PPDU based on the PHY version identifier having the second value.

[0120] 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 is related to UL communication, and the second value of the UL / DL flag field is related to DL communication.

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

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

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

[0124] Preamble puncturing may be applied to the PPDU of Fig. 5. Preamble puncturing means applying puncturing to a portion of the total band of the PPDU (e.g., a 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.

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

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

[0127] 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 configured individually in 80 MHz units. 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 regarding a 160 MHz bandwidth, and the second field of the second U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern). Meanwhile, the UHR-SIG following the first U-SIG may include information regarding preamble puncturing applied to the second 80 MHz band (i.e., information regarding a preamble puncturing pattern), and the UHR-SIG following the second U-SIG may include information regarding preamble puncturing applied to the first 80 MHz band (i.e., information regarding a preamble puncturing pattern).

[0128] Additionally or generally, U-SIG and UHR-SIG may include information regarding preamble puncturing based on the following method. 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).

[0129] 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 may contain different U-SIGs.

[0130] The UHR-SIG of FIG. 5 may include control information for a receiving STA. The UHR-SIG may be transmitted through at least one symbol, and one 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.

[0131] UHR-SIG provides additional signals to the U-SIG field, enabling the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that apply commonly to all users. Additionally, the UHR-SIG field contains resource allocation information, making it possible for the STA to look up resources used in fields containing data fields / UHR-STF / UHR-LTF (i.e., UHR modulated fields of an UHR PPDU).

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

[0133] FIG. 6 is a diagram showing the arrangement of resource units (RUs) used for a 20 MHz PPDU. That is, 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.

[0134] As shown at the top of FIG. 6, 26 units (i.e., units corresponding to 26 tones) may be arranged. Six tones may be used as a guard band in the leftmost band of the 20 MHz band, and five tones may be used as a guard band in the rightmost band of the 20 MHz band. Additionally, seven DC tones are inserted in the center band, i.e., the DC band, and 26 units corresponding to 13 tones may exist on the left and right sides of the DC band. Furthermore, 26 units, 52 units, and 106 units may be allocated to other bands. Each unit may be allocated for a receiving station, i.e., a user.

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

[0136] In the example of FIG. 6, various sizes of RUs, namely 26-RU, 52-RU, 106-RU, 242-RU, etc., are proposed. Since the specific size 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 indicated as N-tone RU, etc. For example, 26-RU may be indicated as 26-tone RU.

[0137] Figure 7 is a diagram showing the arrangement of resource units (RU) used for a 40 MHz PPDU.

[0138] Just as various sizes of RUs were used in the example of FIG. 6, 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc., may also be used in the example of FIG. 7. Additionally, 5 DC tones may be inserted at the center frequency, 12 tones may be used as guard bands in the leftmost band of the 40 MHz band, and 11 tones may be used as guard bands in the rightmost band of the 40 MHz band.

[0139] In addition, as described, 484-RU 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.

[0140] FIG. 8 is a diagram showing the arrangement of resource units (RUs) used for an 80 MHz PPDU. The arrangement of resource units (RUs) used in this specification may be varied. For example, the arrangement of resource units (RUs) used in the 80 MHz band may be varied.

[0141] FIG. 9 illustrates the operation according to UL-MU. As illustrated, a transmitting STA (e.g., AP) can establish a channel connection through contending (i.e., Backoff operation) and transmit a Trigger frame (930). That is, the transmitting STA (e.g., AP) can transmit a PPDU containing the Trigger frame (930). When the PPDU containing the Trigger frame is received, a TB (trigger-based) PPDU is transmitted after a delay of SIFS.

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

[0143] Figure 10 shows an example of a channel used / supported / defined within the 2.4 GHz band.

[0144] The 2.4 GHz band may be referred to by other names, such as the first band (band). Additionally, 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 located between 2.4 and 2.5 GHz) are used / supported / defined.

[0145] The 2.4 GHz band may include multiple 20 MHz channels. The 20 MHz channels 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 to channel index 1 may be 2.412 GHz, the center frequency of a 20 MHz channel assigned to channel index 2 may be 2.417 GHz, and the center frequency of a 20 MHz channel assigned to channel index N may be (2.407 + 0.005*N) GHz. Channel indices may be referred to by various names, such as channel numbers. The specific numerical values ​​of channel indices and center frequencies may change.

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

[0147] FIG. 11 illustrates an example of a channel used / supported / defined within the 5 GHz band.

[0148] The 5 GHz band may be referred to by other names such as the second band / band. The 5 GHz band may refer to a frequency range in which channels with a center frequency of 5 GHz or more 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 may be changed.

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

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

[0151] FIG. 12 illustrates an example of a channel used / supported / defined within the 6 GHz band.

[0152] The 6 GHz band may be referred to by other names such as the third band / band. The 6 GHz band may refer to a frequency range in which channels with a center frequency of 5.9 GHz or higher are used / supported / defined. The specific figures shown in FIG. 12 are subject to change.

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

[0154] Accordingly, the indices (or channel numbers) of the 20 MHz channel in 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, 197, It may be 201, 205, 209, 213, 217, 221, 225, 229, 233. Also, according to the (5.940 + 0.005*N) GHz rule described above, the index of the 40 MHz channel of FIG. 12 may 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.

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

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

[0157] The processor (610) of FIG. 13 may be the same as the processor (111, 121) of FIG. 1. Or, the processor (610) of FIG. 13 may be the same as the processing chip (114, 124) of FIG. 1.

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

[0159] Referring to FIG. 13, a power management module (611) manages power for 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 associated keys used to identify and authenticate a subscriber in a mobile device such as a mobile phone and a computer.

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

[0161] The Multi-AP operation applicable to this specification is described below.

[0162] The above Multi-AP operation refers to a communication technique involving multiple APs in a WLAN. For example, the above 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 above Multi-AP operation, existing techniques may be expressed using various terms such as STX (Single Transmission). For example, the above STX operation may refer to a method in which a single BSS AP communicates with a single BSS STA. When communication is performed based on the above STX operation, interference may occur with adjacent APs (e.g., APs located in overlapping BSSs). Due to this interference, a problem may arise 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.

[0163] FIG. 14 illustrates operation according to a conventional STX operation. As illustrated, interference between STA and AP may occur due to AP1 and AP2 being adjacent to each other.

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

[0165] In Figure 14, STA1 and AP1 are included in the BSS, and STA2 and AP2 can be included in the OBSS (Overlapping Basic Service Set). That is, STA2 is an un-associated STA to AP1, and STA1 is an un-associated STA to AP2.

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

[0167] FIG. 15 illustrates an example of C-OFDMA (Coordinated OFDMA). The illustrated AP1 can transmit a PPDU / signal to STA1, and AP2 can transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 can be performed in the same / overlapping time interval. Transmission from AP1 to STA1 can be performed based on a first frequency band, and transmission from AP2 to STA2 can 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 BSS, and STA2 and AP2 may be included in OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0168] Although not shown in FIG. 15, an example of Co-TDMA (Coordinated 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.

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

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

[0171] FIG. 16 illustrates an example of Coordinated Beamforming (CBF). The illustrated AP1 can transmit a PPDU / signal to STA1, and AP2 can transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 can be performed in the same / overlapping time intervals. Transmission from AP1 and transmission from AP2 can be performed through the same / overlapping frequency bands. To reduce interference caused by AP1 to STA2, AP1 can perform nulling / beamforming toward STA2, and to reduce interference caused by AP2 to STA1, AP2 can perform nulling / beamforming toward STA1. For example, such nulling / beamforming can be implemented by positioning a radiation null to a neighboring unassociated STA. The aforementioned nulling / beamforming can make a specific AP invisible to a neighboring unassociated STA. For example, the aforementioned nulling / beamforming can make AP1 (or AP2) invisible to STA2 (or STA1).

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

[0173] 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 can be transmitted and received through a backhaul link between AP1 and AP2.

[0174] FIG. 17 illustrates an example of AP selection. The illustrated AP2 is determined to have better channel conditions than AP1. AP1 transmits its data / signal to AP2 via a backhaul link, and AP2 can transmit a signal to STA1 instead of AP1. For example, in FIG. 17, STA1 and AP1 may be included in BSS, and STA2 and AP2 may be included in OBSS. That is, STA2 may be an un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0175] FIG. 18 illustrates an example of JTX / JT. The illustrated AP1 can perform transmission to STA1 together with AP2. For example, the PPDU / signal transmitted from AP2 to STA1 may be wholly or partially identical to the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be transmitted simultaneously through a frequency band that is identical to or overlaps with 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 via a backhaul link. For example, in FIG. 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 un-associated STA to AP1, and STA1 may be an un-associated STA to AP2.

[0176] More specifically, in FIG. 18, AP1 transmits a coordination request (or various names such as first request, control request, etc.) to AP2 and receives a coordination response (or various names such as first response, control response, etc.) from AP2. Through the exchange of the request / response, information regarding coordination between AP1 and AP2 (e.g., information regarding whether AP1 and AP2 will perform simultaneous transmission to STA1), information regarding the time when coordination begins, information regarding the time when AP1 and AP2 start simultaneous transmission to STA1, and information regarding data shared between AP1 and AP2 can be exchanged. AP1 can share its data with AP2 via a backhaul link. Subsequently, AP1 transmits a coordination trigger frame (or various names such as trigger frame, etc.) to AP2 and can perform simultaneous transmission to STA1 based on the trigger frame.

[0177] <Examples Applicable to the Present Specification>

[0178] Although a large number of APs are installed in close proximity to each other to enable terminals to maintain continuous WLAN connectivity over a wider area, issues such as radio interference and transmission collisions between APs may occur as the BSSs of multiple APs overlap. To resolve these issues, various technologies for coordinating APs in frequency, time, and spatial domains (e.g., RU selection, joint transmission, nulling, etc.) have been proposed, and attention must also be paid to the various issues that may arise during cooperation between APs.

[0179] In EHT (802.11be), a technique was proposed to allocate a portion of the 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 within the Common Info field of the existing MU-RTS Trigger frame, and a MU-RTS (Multi User-Request To Send) Trigger frame when this value is non-zero is referred to as a MU-RTS TXOP Sharing (TXS) Trigger frame (TF). If the value of 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 TXOP Sharing mode is 2, the non-AP STA supports P2P transmission in addition to (non-TB) PPDU transmission to the AP.

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

[0181] FIG. 19 shows an example of operation when the TXOP Sharing mode value is 2. When the AP transmits a MU-RTS TXS TF containing time allocation information (Time allocated in MU-RTS TXS Trigger Frame in FIG. 19) to non-AP STA 1, Non-AP STA 1 responds to this with a CTS (Clear-To-Send) and can then perform P2P transmission to non-AP STA 2.

[0182] Figure 20 shows an example of coordinated TDMA operation including the discovery, negotiation / agreement process.

[0183] Figure 20 illustrates an example in which APs with Multi-AP cooperation capabilities establish Multi-AP cooperation with neighboring APs and perform Multi-AP cooperation-based transmission. Basically, for Multi-AP cooperation-based transmission to occur between two APs, their respective capabilities and requirements are exchanged in advance (negotiation), and then an agreement is reached based on the acquired information, thereby enabling the execution of Multi-AP cooperation-based technologies (e.g., Co-TDMA, Co-BF, Co-SR, etc.). APs with Multi-AP cooperation capabilities can perform discovery and negotiation / agreement processes to establish Multi-AP cooperation with neighboring APs, and through this, they can establish Multi-AP cooperation relationships or configure Multi-AP cooperation with neighboring APs. Subsequently, APs in a Multi-AP cooperation relationship can perform Multi-AP cooperation when they acquire a TXOP based on the content agreed upon during negotiation. In this specification, an AP that initiates Multi-AP cooperation or triggers Multi-AP cooperation-based transmission is referred to as a Sharing AP (SAP) or Coordinating AP (CAP), and an AP that receives a TXOP from the SAP (or CAP) or triggers Multi-AP cooperation-based transmission is referred to as a shared AP (DAP), Triggered AP (TAP), or Coordinated AP (DAP). Specific designations (names) proposed in this specification may be changed and are not limited.

[0184] To clarify the terminology, the aforementioned cooperative relationship can be referred to as a Multi-AP Coordination (MAPC) relationship or a MAPC agreement. An AP initiating the MAPC (or MAPC negotiation for at least one MAPC technique) can be referred to as a MAPC requesting AP or a coordinating AP. An AP responding to the MAPC requesting AP can be referred to as a MAPC responding AP or a coordinated AP. The coordinating AP is an AP that shares a portion of the TXOP (transmission opportunity) resources by allocating a time portion to the coordinated AP or by allowing simultaneous transmission as part of the MAPC procedure.

[0185] The description of Multi-AP Coordination (MAPC) is as follows.

[0186] MAPC is a framework in which multiple APs cooperate to reduce interference, improve channel utilization efficiency, and enhance reliability and latency; key schemes may include Co-BF (Coordinated Beamforming), Co-SR (Coordinated Spatial Reuse), Co-TDMA (Coordinated TDMA), Co-RTWT (Coordinated Restricted Target Wake Time), and Co-CR (Coordinated Channel Reservation).

[0187] Common procedures for MAPC include the MAPC Discovery procedure and the MAPC Agreement Negotiation procedure. In the MAPC Discovery procedure, an AP can notify other APs of its MAPC capabilities and parameters through the MAPC Discovery Request / Response frame or the management frame. The MAPC Agreement Negotiation procedure may be a process for negotiating, establishing, updating, or terminating an agreement on a specific MAPC scheme among APs. Detailed procedures for the MAPC agreement may include forming the MAPC agreement, assigning an AP ID to identify cooperating APs, updating parameters of the existing MAPC agreement, and terminating the MAPC agreement.

[0188] The discovery and negotiation / agreement process presented in Fig. 20 is a procedure that must be performed commonly for various Multi-AP cooperation-based technologies, but the procedure required for the individual operation of Multi-AP cooperation-based technologies such as Co-SR / Co-BF / Co-TDMA may differ. For example, the detailed sequence of the procedure required for each Multi-AP scheme may differ, and the information included in the frame transmitted in that sequence may also differ.

[0189] Accordingly, this specification proposes a Co-SR / Co-BF sequence required for an AP that has formed a Multi-AP partnership to perform Co-SR / Co-BF-based transmission.

[0190] First, this specification proposes a Co-SR sequence for performing a coordination announcement procedure sequentially with APs participating in Multi-AP cooperation in a single or separate TXOP, or for receiving response frames from said APs and performing Co-SR transmission based on this information. In addition, this specification proposes potential information required for the Co-SR sequence.

[0191] Specifically, in Section 1, the coordination announcement procedure is performed sequentially with participating APs within a single TXOP to confirm whether they intend to participate in Co-SR transmission through the reception of a response frame or the information included therein, and Co-SR transmission is performed based on this.

[0192] Additionally or alternatively, Section 2 checks whether participating APs intend to participate in Co-SR transmission within a single TXOP through the reception of the TB PPDU and the information contained therein, and performs Co-SR transmission based on this.

[0193] Additionally or alternatively, in Section 3, a coordination announcement procedure is performed sequentially with participating APs in a separate TXOP to confirm whether they intend to participate in the subsequent Co-SR transmission, and based on this, the Co-SR transmission is performed.

[0194] Additionally or alternatively, in Section 4, the intention of participating APs to participate in Co-SR transmission is confirmed through the reception of the TB PPDU and the information contained therein in a separate TXOP, and Co-SR transmission is performed based on this.

[0195] 1. Co-SR sequence based on sequential announcement within a single TXOP

[0196] FIG. 21 illustrates an example of a sequence for exchanging Co-SR frames through a sequential CA procedure within a single TXOP.

[0197] The sequence for Co-SR proposed in Section 1 can be depicted as shown in FIG. 21. Specifically, an AP intending to perform Co-SR transmission may acquire a TXOP and sequentially perform a coordination announcement procedure targeting one or more participating APs to select the AP to which the Co-SR transmission is triggered and / or to notify that the Co-SR transmission is scheduled to start. After performing the coordination announcement procedure, at least one AP within the same TXOP may be triggered to perform Co-SR-based transmission.

[0198] FIG. 21 illustrates an example of a Co-SR frame sequence in which a sequential coordination announcement (CA) procedure is performed within a single TXOP to confirm whether cooperative APs will participate in Co-SR transmission. In the negotiation procedure for establishing multi-AP cooperation, APs that have agreed to operate as Co-SR or one or more multi-AP schemes including Co-SR can perform the CA procedure on APs with Co-SR capability. That is, when a specific AP acquires a TXOP, it may perform the CA procedure for the purpose of selecting an AP to perform Co-SR-based transmission together based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that it intends to perform Co-SR-based transmission, and / or for the purpose of exchanging information required to perform Co-SR-based transmission. In the example of FIG. 21, after AP 1 acquires the TXOP, it starts the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an initial control frame (ICF). That is, the CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), be defined as a new type of Trigger frame, or be defined as a new Control frame or Management frame. An AP that receives a CA frame transmitted from AP 1 to a single AP may transmit a coordination announcement response (CAR) frame, which is a response frame solicited from the CA frame.Alternatively, if the CA frame is a MU-RTS(TXS) TF, the CAR frame may not contain separate information. Additionally, if the CA frame is a MU-RTS(TXS) TF, the presence or absence of the CAR frame transmission may indicate whether cooperative-based transmission is currently required or if Co-SR-based transmission is to be performed. The described CA procedure may be performed sequentially for one or more individual cooperative APs.

[0199] Subsequently, AP 1 of FIG. 21 may initiate MAPC-based transmission by transmitting a Co-Triggering frame within the same TXOP based on information that may be included in the response frame with one of the participating APs that transmitted a response frame during the sequential CA procedure described above. At this time, the Co-Triggering frame may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives the Co-Triggering frame addressed by AP 1 may perform Co-SR-based transmission with a target STA within its BSS based on Co-SR-related information included in the frame.

[0200] 2. Co-SR sequence based on TB PPDU received within a single TXOP

[0201] FIG. 22 illustrates an example of a sequence for exchanging Co-SR frames through the reception of TB PPDU within a single TXOP.

[0202] The sequence for Co-SR proposed in Section 2 can be depicted as shown in FIG. 22. Specifically, an AP intending to perform Co-SR transmission may acquire a TXOP and select an AP to trigger the Co-SR transmission and / or perform a coordination announcement procedure to notify that the Co-SR transmission is scheduled to start. After performing the coordination announcement procedure, at least one AP within the same TXOP may be triggered to perform Co-SR-based transmission.

[0203] FIG. 22 illustrates an example of a Co-SR frame sequence based on a TB PPDU received during a Coordination Announcement (CA) procedure performed within a single TXOP. In a negotiation procedure to establish Multi-AP cooperation, APs that have agreed to operate as a Co-SR or one or more Multi-AP schemes including Co-SR can perform a CA procedure targeting APs with Co-SR capability. That is, when a specific AP acquires a TXOP, it may perform a CA procedure for the purpose of selecting an AP to perform Co-SR-based transmission together based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that it intends to perform Co-SR-based transmission, and / or for the purpose of exchanging information required to perform Co-SR-based transmission. In the example of FIG. 22, after AP 1 acquires a TXOP, it starts the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an initial control frame (ICF). That is, a CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. One or more APs (AP 2 and AP 3 in FIG. 22) that receive a CA frame transmitted from AP 1 may transmit a coordination announcement response (CAR) frame containing information soliciting from the CA frame.Alternatively, if the CA frame is a MU-RTS(TXS) TF, the CAR frame may not contain separate information.

[0204] Subsequently, based on the information within the TB PPDU received from the participating APs during the CA procedure described above, AP 1 of FIG. 22 can initiate MAPC-based transmission within the same TXOP by transmitting a Co-Triggering frame. At this time, the Co-Triggering frame may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives the Co-Triggering frame addressed by AP 1 can perform Co-SR-based transmission with a target STA within its BSS based on the Co-SR-related information included in the frame.

[0205] 3. Co-SR sequence based on sequential announcement in a separate TXOP

[0206] FIG. 23 illustrates an example of a sequence for exchanging Co-SR frames through a sequential CA procedure in a separate TXOP.

[0207] The sequence for Co-SR proposed in Section 3 can be depicted as shown in FIG. 23. Specifically, an AP intending to perform Co-SR transmission may sequentially perform a coordination announcement procedure targeting one or more participating APs to select an AP to trigger the Co-SR transmission and / or to notify that the Co-SR transmission is scheduled to begin. Subsequently, in a separate TXOP, Co-SR-based transmission may be performed by triggering the Co-SR transmission to one or more APs based on the response from the coordination announcement procedure.

[0208] FIG. 23 illustrates an example of a Co-SR frame sequence in which a sequential coordination announcement (CA) procedure is performed in a separate TXOP to confirm whether cooperative APs will participate in Co-SR transmission. In the negotiation procedure for establishing multi-AP cooperation, APs that have agreed to operate as Co-SR or one or more multi-AP schemes including Co-SR can perform the CA procedure on APs with Co-SR capability. That is, when a specific AP acquires a TXOP, it can perform the CA procedure for the purpose of selecting an AP to perform Co-SR-based transmission together based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that it intends to perform Co-SR-based transmission, and / or for the purpose of exchanging information required to perform Co-SR-based transmission. In the example of FIG. 23, after AP 1 acquires the TXOP, it starts the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an initial control frame (ICF). That is, the CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), be defined as a new type of Trigger frame, or be defined as a new Control frame or Management frame. An AP that receives a CA frame transmitted from AP 1 to a single AP may transmit a coordination announcement response (CAR) frame, which is a response frame solicited from the CA frame.Alternatively, if the CA frame is a MU-RTS(TXS) TF, the CAR frame may not contain separate information. Additionally, if the CA frame is a MU-RTS(TXS) TF, the presence or absence of the CAR frame transmission may indicate whether cooperative-based transmission is currently required or if Co-SR-based transmission is to be performed. The described CA procedure may be performed sequentially for one or more individual cooperative APs.

[0209] Subsequently, AP 1 of FIG. 23 can initiate MAPC-based transmission by transmitting a Co-Triggering frame from a TXOP obtained through separate channel access. At this time, the Co-Triggering frame may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives the Co-Triggering frame addressed by AP 1 can perform Co-SR-based transmission with a target STA within its BSS based on the Co-SR related information included in the frame.

[0210] 4. Co-SR sequence based on TB PPDU received from a separate TXOP

[0211] FIG. 24 illustrates an example of a sequence for exchanging Co-SR frames through the reception of TB PPDU in a separate TXOP.

[0212] The sequence for Co-SR proposed in Section 4 can be depicted as shown in FIG. 24. Specifically, an AP that intends to perform Co-SR transmission may select an AP to trigger the Co-SR transmission and / or perform a coordination announcement procedure to notify that the Co-SR transmission is scheduled to start. Subsequently, one of the two or more APs that performed the coordination announcement procedure may trigger the Co-SR transmission to perform Co-SR-based transmission.

[0213] FIG. 24 illustrates an example of a Co-SR frame sequence that performs a Coordination Announcement (CA) procedure via a TB PPDU received from a separate TXOP. In the negotiation procedure for establishing Multi-AP cooperation, APs that have agreed to operate as a Co-SR or one or more Multi-AP schemes including Co-SR can perform the CA procedure for APs with Co-SR capability. That is, when a specific AP acquires a TXOP, it may perform the CA procedure for the purpose of selecting an AP to perform Co-SR-based transmission together based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that it intends to perform Co-SR-based transmission, and / or for the purpose of exchanging information required to perform Co-SR-based transmission. In the example of FIG. 24, after AP 1 acquires the TXOP, it starts the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an Initial Control Frame (ICF). That is, the CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. One or more APs (AP 2 and AP 3 in FIG. 24) that receive a CA frame transmitted from AP 1 may transmit a coordination announcement response (CAR) frame containing information soliciting from the CA frame.Alternatively, if the CA frame is a MU-RTS (TXS) TF, the CAR frame may not contain separate information.

[0214] Subsequently, based on the information within the TB PPDU received from the participating APs during the CA procedure described above, AP 1 of FIG. 24 can initiate MAPC-based transmission by transmitting a Co-Triggering frame from a TXOP obtained through separate channel access. At this time, the Co-Triggering frame may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives the Co-Triggering frame addressed by AP 1 can perform Co-SR-based transmission with a target STA within its BSS based on the Co-SR-related information included in the frame.

[0215] Additionally, or alternatively, an AP other than the AP that performed the CA procedure (AP 1 in FIG. 24) may transmit a Co-Triggering frame in a subsequent TXOP. In this case, the AP transmitting the Co-Triggering frame belongs to the AP that received the CA frame from AP 1 in the CA procedure and transmitted the CAR frame, which is the response frame to it. For an AP that did not perform the CA procedure to transmit a Co-Triggering frame, a separate agreement for this may be established during the negotiation / agreement process.

[0216] On the other hand, in situations i) and ii) as described below, the CA procedure for Co-SR-based transmission described in Sections 1 through 4 above may be omitted. Conditions and situations in which the CA procedure is omitted may be added, but are not limited to.

[0217] i) Cases where it is agreed between the two APs during the negotiation / agreement process to omit the CA procedure depending on specific conditions and circumstances

[0218] For example, if a CA procedure was performed in advance between two APs and a specific amount of time has not elapsed, the CA procedure may be omitted in a subsequent TXOP.

[0219] For example, if one AP performs the CA procedure and Co-SR transmission with a peer AP, and then the peer AP acquires a TXOP and performs Co-SR transmission, the CA procedure may be omitted.

[0220] ii) Cases where only one AP negotiated through the Negotiation / agreement process exists (i.e., cases where peer-to-peer Co-SR operation has been agreed upon only between two APs)

[0221] In addition, the present specification proposes a Co-BF sequence in which a response frame is received from APs with Co-BF transmission capabilities at a single or separate TXOP and Co-BF transmission is performed based thereon, and potential information required in the frame exchange at this time. In addition, the present specification proposes a Co-BF sequence in which an AP that has acquired a TXOP immediately transmits a Trigger frame and triggers / starts Co-BF transmission.

[0222] Specifically, we propose a Co-BF sequence in which a Coordination Announcement procedure is performed to confirm whether participating APs with Co-BF capabilities intend to participate in Co-BF transmission within a single TXOP, to announce that Co-BF transmission has started, or to convey information about the target STA of Co-BF transmission, and to trigger Co-BF transmission based on this, and information exchanged between APs in this sequence.

[0223] Additionally or alternatively, we propose a Co-BF sequence in which a Coordination Announcement procedure is performed to confirm whether participating APs with Co-BF capabilities intend to participate in Co-BF transmission or to select a target STA for Co-BF transmission in a separate TXOP, and based on this, Co-BF transmission is triggered, and information exchanged between APs in such a sequence is proposed.

[0224] Additionally or alternatively, we propose a Co-BF sequence that triggers Co-BF transmission immediately upon acquiring a TXOP without having a separate short-term negotiation process / procedure, and we also propose information within the Trigger frame transmitted from the SAP at this time.

[0225] 5. Coordination announcement-based Co-BF sequence performed within a single TXOP

[0226] FIG. 25 illustrates an example of a Co-BF sequence through coordination announcement performed within a single TXOP.

[0227] The overall sequence for Co-BF transmission proposed in Section 5 can be depicted as in Fig. 25.

[0228] FIG. 25 illustrates an example of a Co-BF frame sequence based on a coordination announcement (CA) procedure performed within a single TXOP. In a negotiation procedure to form a Multi-AP cooperation, APs that have agreed to operate as Co-BF or one or more Multi-AP schemes including Co-BF may perform a CA procedure targeting APs with Co-BF capability. That is, when a specific AP acquires a TXOP, it may perform a CA procedure for the purpose of selecting an AP to perform a Co-BF-based transmission together within the currently acquired TXOP based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that a Co-BF-based transmission is scheduled to be performed, and / or for the purpose of exchanging information required to perform a Co-BF-based transmission. In the example of FIG. 25, after AP 1 acquires the TXOP, it initiates the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an initial control frame (ICF). That is, a CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. At least one AP (AP 2 and AP 3 in FIG. 25) that receives a CA frame transmitted from AP 1 may transmit a coordination announcement response (CAR) frame containing information soliciting from the CA frame.Additionally or alternatively, the CAR frame may respond with another type of response frame solicited by the CA frame (e.g., Multi-STA BlockAck frame, Management frame, etc.). Additionally or alternatively, the CAR frame may be transmitted included in another type of PPDU solicited by the CA frame (e.g., TB PPDU, non-TB PPDU, non-HT duplicated PPDU, etc.).

[0229] Subsequently, AP 1 may initiate Co-BF transmission by transmitting a Co-Triggering frame based on the information within the response frame received from at least one participating AP during the CA procedure described above, or based on whether the response frame has been received. At this time, the Co-Triggering frame refers collectively to reusing the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), defining a new type of Trigger frame, or defining a new Control frame or Management frame. Additionally, APs that receive a Co-Triggering frame may omit the transmission of a response frame in response. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives the Co-Triggering frame addressed by AP 1 may perform Co-BF-based transmission with a target STA within its BSS based on the Co-BF-related information included in the frame and the information obtained from the CA frame.

[0230] Basically, it is assumed that before the CA procedure described in Section 5 is performed, a sounding procedure (i.e., OBSS channel sounding or Interference measurement), which is a preliminary procedure for Co-BF transmission, has been completed and performed between the AP that transmitted the CA frame and one or more APs that receive it.

[0231] 6. Co-BF sequence based on coordination announcement performed in a separate TXOP

[0232] Figure 26 illustrates an example of a Co-BF sequence through a coordination announcement performed in a separate TXOP.

[0233] FIG. 26 illustrates an example of a Co-BF frame sequence based on a coordination announcement (CA) procedure performed in a separate TXOP. In the negotiation procedure for establishing Multi-AP cooperation, APs that have agreed to operate as Co-BF or one or more Multi-AP schemes including Co-BF may perform a CA procedure targeting APs with Co-BF capability. That is, when a specific AP acquires a TXOP, it may perform a CA procedure for the purpose of selecting an AP to perform Co-BF-based transmission together based on the agreement during the negotiation process and previously exchanged information, / or for the purpose of announcing that it intends to perform Co-BF-based transmission, and / or for the purpose of exchanging information required to perform Co-BF-based transmission. In the example of FIG. 26, after AP 1 acquires a TXOP, it initiates the CA procedure by transmitting a CA frame. At this time, the CA frame can be considered as an initial control frame (ICF). That is, a CA frame can be transmitted as an ICF along with the acquisition of the TXOP. In addition, the CA frame at this time may reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. At least one AP (AP 2 and AP 3 in FIG. 26) that receives a CA frame transmitted from AP 1 may transmit a coordination announcement response (CAR) frame containing information soliciting from the CA frame.Additionally or alternatively, the CAR frame may respond with another type of response frame solicited by the CA frame (e.g., Multi-STA BlockAck frame, Management frame, etc.). Additionally or alternatively, the CAR frame may be transmitted included in another type of PPDU solicited by the CA frame (e.g., TB PPDU, non-TB PPDU, non-HT duplicated PPDU, etc.).

[0234] Subsequently, based on the information within the response frame received from at least one participating AP during the CA procedure described above, or whether the response frame has been received, AP 1 of FIG. 26 may initiate Co-BF transmission by transmitting a Co-Triggering frame from a TXOP obtained through a separate channel access. At this time, the Co-Triggering frame refers collectively to reusing the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), defining a new type of Trigger frame, or defining a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, at least one AP that receives an addressed Co-Triggering frame from AP 1 can perform Co-BF-based transmission with a target STA in its BSS based on the Co-BF-related information contained in the frame.

[0235] Additionally, or alternatively, an AP other than the AP that performed the CA procedure (AP 1 in FIG. 26) may transmit a Co-Triggering frame in a subsequent TXOP. In this case, the AP transmitting the Co-Triggering frame belongs to the AP that received the CA frame from AP 1 in the CA procedure and transmitted the CAR frame, which is the response frame to it. For an AP that did not perform the CA procedure to transmit a Co-Triggering frame, a separate agreement for this may be established during the negotiation / agreement process.

[0236] Additionally or alternatively, following the CA procedure described above, a sounding procedure (OBSS channel sounding or Interference measurement), which is a preliminary procedure for transmitting BSS and Co-BF corresponding to at least one AP that transmitted a response frame within the same TXOP, may be initiated. The sounding procedure may be performed based on the target STA information of each AP obtained in the CA procedure or based on all STAs.

[0237] Additionally or alternatively, based on information within a response frame received from at least one participating AP during the CA procedure described above or whether a response frame has been received, AP 1 of FIG. 26 (or the AP that transmitted the response frame) may initiate a sounding procedure (OBSS channel sounding or Interference measurement), which is a preliminary procedure for Co-BF transmission, at a TXOP obtained through a separate channel access. The sounding procedure may be performed based on the target STA information of each AP obtained during the CA procedure or based on all STAs.

[0238] On the other hand, in situations i) and ii) as described below, the CA procedure for Co-BF-based transmission described in Sections 5 and 6 above may be omitted. Conditions and situations in which the CA procedure is omitted may be added, but are not limited to.

[0239] i) Cases where it is agreed between the two APs during the negotiation / agreement process to omit the CA procedure depending on specific conditions and circumstances

[0240] For example, if a CA procedure was performed in advance between two APs and a specific amount of time has not elapsed, the CA procedure may be omitted in a subsequent TXOP.

[0241] For example, if one AP performs the CA procedure and Co-BF transmission with a peer AP, and then the peer AP acquires a TXOP and performs Co-BF transmission, the CA procedure may be omitted.

[0242] ii) Cases where only one AP negotiated through the Negotiation / agreement process exists (i.e., cases where peer-to-peer, pairwise Co-BF operations have been agreed upon only between two APs)

[0243] 7. Immediate triggering Co-BF sequence

[0244] Figure 27 illustrates an example of a Co-BF sequence by immediate triggering.

[0245] The overall sequence for Co-BF transmission proposed in Section 7 can be depicted as in Fig. 27.

[0246] Figure 27 illustrates an example of a Co-BF frame sequence based on immediate triggering. In a negotiation procedure to form a multi-AP cooperation, APs with Co-BF capability agree to operate as Co-BF, and between APs that have performed sounding procedures for Co-BF transmission (OBSS channel sounding, Interference measurement), a Co-Triggering frame is transmitted, and Co-BF transmission can begin immediately. That is, it is assumed that the sounding procedure (OBSS channel sounding or Interference measurement), which is a preliminary procedure for Co-BF transmission, has been completed and performed between the two APs prior to the execution of the described Co-BF sequence.

[0247] In the example of FIG. 27, after AP 1 acquires the TXOP, it transmits a Co-Triggering frame and triggers the transmission of a Co-BF. At this time, the Co-Triggering frame can be considered as an initial control frame (ICF). That is, the Co-Triggering frame can be transmitted as an ICF along with the acquisition of the TXOP. Furthermore, the Co-Triggering frame at this time can reuse the structure of an existing Basic Trigger frame or a specific Trigger frame type (e.g., BSRP TF, MU-RTS (TXS) TF, etc.), define a new type of Trigger frame, or define a new Control frame or Management frame. Additionally, APs that receive the Co-Triggering frame may omit the transmission of a response frame. Alternatively, an indication bit requesting the transmission of a response frame may be included within the Co-Triggering frame. Finally, the AP that receives the Co-Triggering frame addressed from AP 1 can perform Co-BF-based transmission with the target STA in its BSS based on the Co-BF-related information contained in the frame.

[0248] 8. Potential contents in Co-SR / Co-BF sequences

[0249] 8.1. Potential contents in Co-SR sequences

[0250] In this section, we define and propose potential information that can be included in the CA (coordination announcement) frame presented in each of the above sections, the CAR frame which is the response to it, and the Co-Triggering frame.

[0251] First, the CA frame (or ICF) transmitted during the CA process for Co-SR proposed in this specification may include content 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 to specific names.

[0252] A. Address: Address information of potential DAPs among the participating APs that wish to perform Co-SR transmission together (e.g., BSS color, BSSID for Multi-AP, or MAC address)

[0253] B. ICF Type: Indicates the operation type of the corresponding Initial Control frame (or B-1. UHR Feature Type (Feedback Type): described below, indicates the feature type of the BSRP (UHR) TF) or a field containing common information transmitted to the receiving STA via a CA frame (i.e., TF).

[0254] - For example, information required to solicit information such as IDC (In-device coexistence) Info, MAPC Info, DPS (Dynamic power wave) Info, and NPCA (Non-primary channel access) Info

[0255] For example, Common information that must be transmitted to the receiving STA to operate as IDC, MAPC, DPS, or NPCA

[0256] - For example, a field for indication of Common Control (and / or feature) information included in a solicit frame (i.e., TF).

[0257] - For example, the bitmap indicates that it contains common information regarding specific features to be transmitted to the receiving STA to operate as IDC, MAPC, DPS, or NPCA (for example, when Bit 1: IDC, Bit 2: MAPC, Bit 3: DPS, 110 (assuming the MSB is on the right and the LSB is on the left) indicates that Common Control Info fields for IDC and MAPC are included).

[0258] B-1. UHR Feature Type (Feedback Type): Indicates the feature type of the BSRP (UHR) TF.

[0259] - That is, it indicates the purpose for which the BSRP (UHR) TF was transmitted (e.g., Co-SR or Co-SR Sync / Invite or MAPC).

[0260] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0261] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[0262] Specifically, it can indicate the type for which a BSRP TF, which can be utilized as an ICF 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.

[0263] bit 0: Indicates that it is a TF for multi-AP coordination operations.

[0264] bit 1: Indicates that it is a TF for DPS operation

[0265] bit 2: Indicates that it is a TF for IDC operations.

[0266] bit 3: Indicates that it is a TF for NPCA operations.

[0267] other bits: reserved

[0268] Specifically, it can indicate the type for which the BSRP TF was transmitted within a specific feature (e.g., MAPC). An example of signaling is as follows.

[0269] 0: Indicates that it has been transmitted to the ICF in the MAPC.

[0270] 1: Indicates that it was transmitted as a Co-Triggering frame in MAPC

[0271] 2: Indicates that it was transmitted to the CRF in the MAPC

[0272] 3: TBD

[0273] ...

[0274] -> Additionally or alternatively, specific types of particular UHR features and / or MAPC schemes can be indicated. An example of signaling is as follows.

[0275] 0: Co-existence

[0276] 1: Co-BF

[0277] 2: Co-SR

[0278] 3: Co-TDMA

[0279] 4: TBD

[0280] ...

[0281] -> Additionally or alternatively, control information regarding the type of a specific UHR feature and / or MAPC scheme and the role for which the corresponding TF was transmitted can be indicated together. An example of signaling is as follows.

[0282] 0: Co-existence

[0283] 1: Reserved

[0284] 2: Reserved

[0285] 3: ICF in Co-TDMA

[0286] 4: Sounding Invite frame in the sounding section at Co-BF

[0287] 5: Co-BF Invite frame in the transmission interval of Co-BF

[0288] 6: Synchronization (i.e., Co-Triggering) frame in Co-BF

[0289] 7: Co-SR Invite frame in the transmission interval of Co-SR

[0290] 8: Synchronization (i.e., Co-Triggering) frame in Co-SR

[0291] ...

[0292] Additionally or alternatively, control and info type information regarding the type of a specific UHR feature and / or MAPC scheme, the role for which the corresponding TF was transmitted, and specifically what type of information it contains can be indicated together. An example of signaling is as follows.

[0293] 0: Co-existence

[0294] 1: Reserved

[0295] 2: Reserved

[0296] 3: ICF in Co-TDMA

[0297] 4: Includes Common information in Co-BF sounding (i.e., Sounding Invite Common Info)

[0298] 5: Includes Per-User information in Co-BF sounding (i.e., Sounding Invite Per-User Info)

[0299] 6: Includes Common information for Invite in Co-BF (i.e., Invite Common Info)

[0300] 7: Includes Per-User information for Invite in Co-BF (i.e., Invite Per-User Info)

[0301] 8: Includes common information for synchronization in Co-BF (i.e., Sync Common Info)

[0302] 9: Includes Per-User information for synchronization in Co-BF (i.e., Sync Per-User Info)

[0303] 10: Includes information for Invite in Co-SR (i.e., Co-SR Invite Info)

[0304] 11: Includes information for synchronization in Co-SR (i.e., Co-SR Sync / Co-TF Info)

[0305] ...

[0306] - Additionally or as an alternative, a UHR Feature field can be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved without specifying a specific UHR Feature Type.

[0307] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[0308] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[0309] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[0310] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0311] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0312] - Additionally or alternatively, the information may be included by redesigning the reserved bits or parts of the Special User Info field (i.e., AID=2007).

[0313] C. Multi-AP scheme type: Information on Multi-AP cooperative transmission techniques such as Co-SR, Co-BF, C-TDMA, etc. (or, C-1. Multi-AP Coordination (MAPC) Type described below: an indication on Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, Co-BF, etc.)

[0314] - For example, utilizing the EHT Reserved (7 bits) or Reserved (4 bits) of the Common Info field

[0315] Specifically, defining a new field to indicate the type of Multi-AP cooperation by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperation transmission techniques that can be reflected in the new definition and standard).

[0316] Specifically, defining a new field to indicate the type of Multi-AP cooperation by utilizing one or more bits corresponding to Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperation transmission techniques that can be reflected in the new definition and standard).

[0317] - For example, it can be configured by combining and expanding the Triggered TXOP Sharing Mode field (2 bits) and Reserved (1 bit).

[0318] Specifically, using combined and extended 3 bits, it is possible to indicate Multi-AP cooperative transmission techniques currently in operation, such as Co-SR, Co-BF, and C-TDMA.

[0319] - Additionally or alternatively, the Multi-AP scheme type field may be included in the User Info field or the Special User Info field.

[0320] C-1. Multi-AP Coordination (MAPC) Type: Instructions for Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, and Co-BF

[0321] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0322] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0323] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard).

[0324] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to Reserved fields / bits (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard)

[0325] For example, signaling can be done as follows

[0326] bit 0: None

[0327] bit 1: Co-TDMA

[0328] bit 2: Co-SR

[0329] bit 3: Co-BF

[0330] ...

[0331] For example, signaling can be done as follows

[0332] 0: Co-TDMA

[0333] 1: Co-SR

[0334] 2: Co-BF

[0335] ...

[0336] Additionally or alternatively, control information regarding the MAPC Type and the role for which the corresponding TF was transmitted can be signaled together.

[0337] For example, signaling can be done as follows based on each bit value.

[0338] 0: The role of ICF in Co-TDMA

[0339] 1: The role of TXOP return in Co-TDMA

[0340] 2: ICF (or Invite) role for the transmission section in Co-SR

[0341] 3: The Role of Synchronization / Co-Triggering Frames in Co-SR

[0342] 4: ICF (or Invite) role for the transmission section in Co-BF

[0343] 5: Role of Synchronization / Co-Triggering Frames in Co-BF

[0344] 6: The role of ICF (or Invite) for the sounding section in Co-BF

[0345] 7: Role of a trigger frame for sounding failure recovery in Co-BF

[0346] ...

[0347] -> Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0348] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0349] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0350] D. Multi-AP ID or AP ID: An ID locally assigned from each AP within a configured multi-AP group / set (e.g., 0, 1, 2, ...)

[0351] - For example, the relevant Multi-AP ID or AP ID can be included in the AID12 field within the User Info field of the Trigger frame.

[0352] E. Common Procedure: Indicates that this is a Task Force (MAP TF) for the unified coordination announcement procedure regarding Multi-AP cooperation.

[0353] - For example, you can utilize the EHT Reserved (7 bits) or Reserved of the Common Info field.

[0354] Specifically, it uses 1 bit to indicate that it is a TF transmitted for a coordination announcement.

[0355] bit 0: If the TF is not intended for coordination announcement

[0356] bit 1: Indicates that the corresponding TF was sent for the purpose of a coordination announcement.

[0357] - Additionally, or alternatively, 1 bit may be additionally utilized to indicate one of the procedures for Multi-AP cooperation.

[0358] Specifically, it indicates that it is a TF transferred for a specific procedure within the Multi-AP cooperation process.

[0359] bit 0: Indicates that the TF is not intended for coordination announcement.

[0360] bit 1: Indicates that the corresponding TF was sent for the purpose of a coordination announcement.

[0361] Bit 2: Indicates that the TF is transmitted for a TXOP sharing procedure (i.e., time allocation for C-TDMA) or a coordination triggering procedure (a procedure for initiating and triggering transmissions such as Co-SR, Co-BF, etc.). (Additionally or alternatively, Bit 2 can replace Bit 0; that is, Bit 0 can be utilized for the purpose indicated by Bit 2.)

[0362] bit 3: Indicates that the TF was transmitted for the TXOP return procedure.

[0363] - For example, you can utilize the Reserved field of the User Info field.

[0364] - Additionally or alternatively, one or more User Info field(s) with the same AID may exist, and additional User Info fields may include bits or fields to indicate a Common Procedure.

[0365] - Additionally, or as an alternative, the Special User Info field can be utilized.

[0366] - Additionally, or alternatively, it may be included in the Feedback User Info field (AID12 = 2008).

[0367] F. Scheduled Coordination Duration: The period during which APs participating in the MAPC operation cooperate to perform TXOP sharing / coordination (or) the nominal TXOP period scheduled by the sharing AP for the MAPC operation.

[0368] - For example, define a new field including Scheduled TXOP Duration to indicate

[0369] Specifically, define a new field tentatively named Scheduled Duration to indicate the information required for MAPC operation and the Scheduled TXOP Duration value.

[0370] - For example, define a new element including Scheduled TXOP Duration to indicate

[0371] Specifically, a new MAPC Operation element (tentative name) is defined to indicate the information and Scheduled TXOP Duration value required for MAPC operation.

[0372] - For example, instructing to include the Scheduled TXOP Duration within a QoS Characteristic element that can be used to include negotiation information during the pre-negotiation process for MAPC operation, or within an element that can be newly defined for negotiation in MAPC.

[0373] - For example, instructing to include the Scheduled TXOP Duration within a UHR Operation element that can be used to include announcement information during the announcement process of each AP for MAPC operation, or within an element that can be newly defined for announcements in MAPC.

[0374] G. DL / UL Indication: Indicates whether a DL transfer or a UL transfer is to be performed through a MAPC scheme in which the SAP and DAP perform transfers simultaneously, such as Co-SR or Co-BF.

[0375] H. Tx Power: SAP's maximum Tx power information

[0376] - For example, DAP can determine an appropriate Tx power that does not cause interference based on the maximum Tx power information transmitted by SAP.

[0377] - For example, utilizing the AP Tx Power field of the Common Info field

[0378] I. In-BSS STA Info: Indicates information about the Target STA for which the SAP will perform DL / UL transmission, or information about all connected STAs, through a MAPC scheme where the SAP and DAP perform transmission simultaneously, such as Co-SR or Co-BF.

[0379] - For example, the identifiers and capabilities of all STAs connected to the SAP (e.g., STAs' AID or MAC addresses / e.g., STAs' MIMO, RF capability)

[0380] - For example, the identifier and capability of the target STA among the STAs connected to the SAP that intends to perform DL / UL transmission via the MAPC scheme (e.g., the target STA's AID or MAC address / e.g., the target STA's MIMO, RF capability)

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

[0382] J. OBSS STA Info: Indicates information about the OBSS Target STA on which the DAP will perform DL / UL transmission via a MAPC scheme in which the SAP and DAP perform transmission simultaneously, such as Co-SR or Co-BF.

[0383] - For example, the identifier and capability of the target OBSS STA among the OBSS STAs connected to the DAP that intends to perform DL / UL transmission via the MAPC scheme (e.g., the AID or MAC address of the target OBSS STA / e.g., the MIMO, RF capability of the target OBSS STA)

[0384] - For example, an identifier for an OBSS STA that you want to include in the Multi-AP channel sounding (or OBSS channel sounding) process for MAPC operation

[0385] K. BSRP Type (or Co-SR Subtype): Separately indicates control information regarding the role for which the corresponding BSRP TF was transmitted.

[0386] - That is, among the embodiments for the MAPC Type field and / or Coordination Triggering described above, control information regarding what role the corresponding TF was transmitted for can be indicated through a separate BSRP Type field.

[0387] For example, signaling can be done as follows based on each bit value

[0388] 0: Role of ICF or Invite Frame in the sounding phase

[0389] 1: Role of ICF or Invite Frame in Transmission Phase

[0390] 2: Role of Synchronization or Co-Triggering Frame in Transmission Phase

[0391] 3: Role of a trigger frame for the purpose of sounding failure recovery

[0392] 4: Role of the Intermediate Control frame during the sounding or transmission phase (e.g., the role of the TXOP return frame in Co-TDMA)

[0393] ...

[0394] -> Additionally or alternatively, signaling can be done with 1 bit as follows

[0395] 0: Role of ICF or Invite Frame in Transmission Phase

[0396] 1: Role of the Sync (Co-Triggering) frame in the transmission phase

[0397] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0398] - Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0399] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0400] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0401] L. Traffic Priority: Priority information of traffic recommended by SAP to DAP, priority information of traffic allowed by SAP to DAP, or priority information of traffic / AC allowed by SAP to DAP

[0402] - For example, TID / AC information regarding traffic allowed to the DAP within the TXOP obtained by SAP

[0403] - For example, Primary AC information for TXOPs obtained by SAP (obtained TXOP)

[0404] Specifically, if traffic for only one of AC_BK, AC_BE, AC_VI, or AC_VO is allowed, the DAP may transmit only traffic corresponding to that AC within the allocated period or cooperation period.

[0405] Specifically, a 2-bit ACI field can be defined to indicate as follows (ACI-to-AC coding)

[0406] AC index (ACI) 0 = AC_BE (best effort)

[0407] AC index (ACI) 1 = AC_BK (background)

[0408] AC index (ACI) 2 = AC_VI (video)

[0409] AC index (ACI) 3 = AC_VO (voice)

[0410] - Additionally or alternatively, SAP may designate a Primary AC for the acquired TXOP, and based on said Primary AC, the CAP (coordinated AP) may transmit traffic corresponding to an AC equal to or greater than said AC within the allocated period or cooperation period.

[0411] Specifically, a new 2-bit field can be defined to indicate as follows (ACI-to-AC coding)

[0412] AC index (ACI) 0 = AC_BE (best effort)

[0413] AC index (ACI) 1 = AC_BK (background)

[0414] AC index (ACI) 2 = AC_VI (video)

[0415] AC index (ACI) 3 = AC_VO (voice)

[0416] - Additionally or alternatively, seven User Priorities (UPs) may be provided as Traffic Categories, and a CAP may transmit only traffic corresponding to an AC that is less than or equal to the UP within the allocated period or cooperation period.

[0417] Specifically, a new 4-bit field can be defined to indicate as follows (UP-to-AC mapping)

[0418] User Priority (UP) 1 = AC_BK

[0419] UP 2 = AC_BK

[0420] UP 0 = AC_BE

[0421] UP 3 = AC_BE

[0422] UP 4 = AC_VI

[0423] UP 5 = AC_VI

[0424] UP 6 = AC_VO

[0425] UP 7 = AC_VO

[0426] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0427] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0428] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0429] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0430] M. Multi-AP Ack Policy Indicator: Indicates the Ack policy during the Co-SR transmission period or the Ack policy that the DAP and the STA connected to the DAP must follow during the coordination duration.

[0431] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0432] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0433] Specifically, it utilizes the 2 bits corresponding to EHT Reserved or Reserved to instruct the Ack policy for frame exchanges between cooperating APs during the Co-SR Duration.

[0434] For example, it can be defined similarly to the Ack Policy Indicator field within the QoS Control field.

[0435] Bit 0 = 0 & Bit 1 = 0: Indicates a normal ACK or an implicit BAR.

[0436] Bit 0 = 1 & Bit 1 = 0: Indicates No Ack

[0437] Bit 0 = 0 & Bit 1 = 1: Reserved

[0438] Bit 0 = 1 & Bit 1 = 1: Indicates Block Ack

[0439] For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0440] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0441] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0442] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0443] N. Common U-SIG Info: One or more of the information presented below may be added to and defined within the Common U-SIG Info field, but is not limited to. The Common U-SIG Info field indicates and includes U-SIG-1 and U-SIG-2 information that must be commonly included in the DL PPDU transmitted by each AP during the relevant cooperation-based transmission period.

[0444] - For example, PHY Version Identifier (B0-B2) information in the U-SIG-1 field within MU PPDU (e.g., EHT, UHR, etc.)

[0445] Specifically, it indicates the PHY version of the DL PPDU transmitted by each AP during the Co-SR transmission period.

[0446] Additionally or alternatively, SAP specifies the PHY version of the target STA to which it intends to send the DL PPDU during the Co-SR transmission time.

[0447] - For example, Bandwidth (B3-B5) information of the U-SIG-1 field within MU PPDU (e.g., EHT, UHR, etc.)

[0448] Specifically, it indicates the bandwidth of the DL PPDU transmitted by each AP during the Co-SR transmission period.

[0449] -> Additionally or alternatively, it may be a bandwidth based on the bandwidth of the PPDU containing the ICF transmitted by the SAP.

[0450] -> Additionally or alternatively, when a response frame (e.g., M-BA frame) for an ICF transmitted by the SAP exists, it may be a bandwidth based on the bandwidth of the PPDU containing said M-BA frame.

[0451] - For example, UL / DL (B6) information in the U-SIG-1 field within the MU PPDU (e.g., EHT, UHR, etc.)

[0452] Specifically, it indicates whether DL transmission or UL transmission is scheduled to be performed during the relevant Co-SR transmission period.

[0453] - For example, Punctured Channel Information (B3-B7) of the U-SIG-2 field within MU PPDU (e.g., EHT, UHR, etc.)

[0454] Additionally or alternatively, the PPDU containing the ICF transmitted by the SAP may be punctured based on long-term punctured channel info (e.g., all punctured 20 MHz subchannels specified in the TXVECTOR parameter INACTIVE_SUBCHANNELS).

[0455] -> Additionally or alternatively, it can be punctured based on the dynamic puncturing information of each AP

[0456] -> Additionally or alternatively, it may be a puncturing pattern composed of the union of the two APs' punctured 20 MHz.

[0457] - For example, a UHR-SIG MCS can be defined that performs the same role as the EHT-SIG MCS (B9-B10) of the U-SIG-2 field within a MU PPDU (e.g., EHT, UHR, etc.).

[0458] Specifically, the value of UHR-SIG MCS can indicate the following MCS:

[0459] UHR-SIG MCS = 0 indicates UHR-MCS 0.

[0460] UHR-SIG MCS = 1 indicates UHR-MCS 1.

[0461] UHR-SIG MCS = 2 indicates UHR-MCS 3.

[0462] UHR-SIG MCS = 3 indicates UHR-MCS 15.

[0463] - Additionally or alternatively, it can be set to an MCS value that all STAs serviced by each AP can receive.

[0464] - For example, Number of UHR-SIG Symbols can be defined to serve the same role as Number of EHT-SIG Symbols (B11-B15) in the U-SIG-2 field within a MU PPDU (e.g., EHT, UHR, etc.).

[0465] -> Additionally or alternatively, it can be set to an OFDM symbol value configured by considering all user fields for all STAs connected to each AP.

[0466] - For example, a UHR-SIG TXOP can be defined that performs the same role as the TXOP (B13-B19) of the U-SIG field within a MU PPDU (e.g., EHT, UHR, etc.).

[0467] - For example, Spatial Configuration (B16-B19) information within the User field

[0468] Specifically, it specifies the number of spatial streams for each user in MU-MIMO allocation.

[0469] -> Additionally or alternatively, spatial stream allocation information for all STAs connected to each AP can be specified.

[0470] Additionally or alternatively, the Spatial Configuration field can be defined and utilized as 2 or 3 bits.

[0471] - One or more of the information described above may be included in the Common U-SIG Info field, but is not limited to.

[0472] For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI and HE / EHT-LTF Type / TXS Mode field

[0473] Additionally, or as an alternative, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0474] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0475] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0476] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0477] O. Co-SR Mode: Indicates the mode for Co-SR transmission.

[0478] - For example, Mode 1 indicates the case where the target STA for Co-SR transmission is EHT + EHT, EHT + UHR, or UHR + EHT.

[0479] -> Under Mode 1 instructions, Co-SR PPDUs transmitted by two APs during the Co-SR transmission period must have a common L-SIG, but the U-SIG contents may differ.

[0480] - For example, Mode 2 indicates the case where the target STA for Co-SR transmission is UHR+UHR.

[0481] -> The instructions of Mode 2 indicate that the Co-SR PPDU transmitted by the two APs during the Co-SR transmission period must have a common L-SIG and a common U-SIG.

[0482] - For example, the final Co-SR Mode information may be included in the BSRP (GI3) TF in the Triggering procedure (i.e., the TF that solicits the Co-SR PPDU).

[0483] That is, in the BSRP (GI3) TF (e.g., Invite frame or ICF) in the Polling procedure, the Sharing AP can indicate and specify the PHY version of the target STA to which it intends to send the Co-SR PPDU.

[0484] A coordinated AP (i.e., shared AP) that receives a BSRP (GI3) TF in the polling procedure can also indicate the PHY version of the target STA to which it intends to send the Co-SR PPDU.

[0485] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0486] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0487] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0488] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0489] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0490] a. ICF / ICR Required: Indicates whether an additional sequence is required to transmit the ICF to the associated STA before triggering the Co-SR transmission.

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

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

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

[0494] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[0495] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0496] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0497] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0498] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0499] b. BSS Color 1 and BSS Color 2 (6 bits each): Indicates the BSS color of the SAP and the BSS color of the coordinated AP.

[0500] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[0501] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0502] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0503] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0504] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0505] c. Non-OFDMA Common Info: Non-OFDMA information that must be commonly included in the DL PPDU transmitted by each AP during the corresponding cooperative-based transmission period.

[0506] - For example, Spatial Reuse (4 bits) information within the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[0507] - For example, GI+LTF Size (B4-B5) information in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[0508] Specifically, it can be set to a GI+LTF value that enables all STAs serviced by each AP to reliably estimate the channel.

[0509] - For example, Number of UHR-LTF Symbols can be defined to serve the same role as Number of EHT-LTF Symbols (B6-B8) in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission.

[0510] Specifically, it can be set as the dimension of the Giant P matrix determined based on the sum of the spatial streams required for each AP.

[0511] -> Additionally or alternatively, it can be set to the larger of the LTF symbol values ​​required for each AP.

[0512] - For example, Number of Non-OFDMA Users (B17-B19) information in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[0513] Specifically, the value of the Number Of Non-OFDMA Users field can represent the sum of the number of SAP-side Co-SR target users and the number of DAP-side Co-SR target users.

[0514] Alternatively, the Number Of Non-OFDMA Users field can be defined as 2 bits, with each bit used to indicate the number of Co-SR target users for SAP and DAP.

[0515] For example, B17 indicates the number of SAP users (e.g., 0 is single user, 1 is 2 users)

[0516] For example, B18 indicates the number of DAP users (e.g., 0 is single user, 1 is 2 users)

[0517] - One or more of the information described above may be included in the BSRP Trigger frame, but is not limited to.

[0518] For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI and HE / EHT-LTF Type / TXS Mode field

[0519] Additionally, or as an alternative, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0520] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0521] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0522] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0523] d. ICF / ICR Duration: Indicates the period required to send the ICF to the coordinating AP's associated STA and receive the ICR before triggering the Co-SR transmission.

[0524] - For example, if an ICF / ICR exchange procedure is required to switch an EMLSR STA among the associated STAs from listening mode to frame exchange mode, indicate the estimated period required for this.

[0525] - For example, if an ICF / ICR exchange procedure is required to switch a DPS STA among the associated STAs from low capability mode to high capability mode, indicate the estimated period required for this.

[0526] - For example, if an ICF / ICR exchange procedure is required to switch a DUO STA among the associated STAs, indicate the estimated period required for this.

[0527] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[0528] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0529] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0530] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0531] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0532] e. Co-SR Response Padding: Indicates the padding length required for the response frame transmitted by the coordinated AP receiving the Co-SR Invite frame.

[0533] - For example, an 8-bit padding field can be used for definition and padding.

[0534] - Additionally or alternatively, it can be signaled using 3 bits as follows

[0535] 0: 0 μs / 1: 32 μs / 2: 64 μs / 3: 128 μs / 4: 256 μs / 5-7: Reserved

[0536] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[0537] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0538] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0539] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0540] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0541] In addition to the contents presented above, some fields included in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission to existing multiple users (e.g., LDPC Extra Symbol Segment, Pre-FEC Padding Factor, PE Disambiguity, Spatial Reuse, etc.) may be included in the Common Info or Special User Info within the BSRP (UHR) Trigger frame proposed in this specification as contents for Co-SR transmission, or in the (UHR) Special User Info that can be newly defined for UHR.

[0542] Additionally, the CAR frame (or ICR frame) transmitted in the CA procedure for Co-SR proposed in this specification may include content 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.

[0543] A. Required Coordination Duration: Information regarding the cooperation period desired by each DAP

[0544] - For example, define a new field including Required Coordination Duration to indicate

[0545] Specifically, a new field tentatively named the Required Coordination Duration field is defined to indicate the information required for Co-SR transmission and the Required Coordination Duration value.

[0546] - For example, define a new element including Required Coordination Duration to indicate

[0547] Specifically, a new Multi-AP Operation element (tentative name) is defined to indicate the information and Required Coordination Duration value necessary for Co-SR operation.

[0548] - For example, instructing to include the Required Coordination Duration within a QoS Characteristic element that can be used to include negotiation information during the pre-negotiation process for Co-SR operations, or within an element that can be newly defined for negotiation in Co-SR.

[0549] - For example, instructing the inclusion of Required Coordination Duration within a UHR Operation element that can be used to include announcement information during the announcement process of each AP for Co-SR operation, or within an element that can be newly defined for announcements in Co-SR.

[0550] B. Buffer Status: Current buffer status information of each DAP or the amount of buffer that each DAP intends to send to the Co-SR

[0551] C. Preferred Tx Power: Information on the DAP's desired / preferred maximum Tx power

[0552] - For example, the DAP can independently determine its own appropriate non-interfering Preferred Tx power based on the maximum Tx power information, In-BSS STA, and OBSS STA information transmitted by the SAP.

[0553] D. Status Code: Accept / Reject / Recommendation information for the coordination announcement (i.e., the DAP selected by SAP may accept or reject based on whether it currently requires cooperation-based transmission or intends to perform Co-SR-based transmission)

[0554] - For example, Accept or Success (e.g., SUCCESS)

[0555] - For example, a Reject including a Reject or Recommendation

[0556] Specifically, a rejection code containing the rejection reason (e.g., REJECTED_BAD_SUPPORTED_CHANNELS)

[0557] Specifically, a reject code including a recommendation (e.g., REJECTED_WITH_SUGGESTED_CHANGES)

[0558] If the value of the Status Code includes Reject or Recommendation, it may include information for a new coordination announcement. That is, a DAP that receives a CA frame may include additional information regarding the Required Coordination Duration, Buffer Status, and Status Code described above.

[0559] Additionally, the Co-Triggering frame transmitted in the MAPC-based transmission procedure following the CA procedure for Co-SR proposed herein may include content 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.

[0560] A. Address: Address information of the DAP that ultimately triggers Co-SR execution among the APs that sent the response frame in the CA procedure (e.g., BSS color, BSSID for Multi-AP, or MAC address)

[0561] B. Multi-AP ID or AP ID: An ID locally assigned to each AP within a configured multi-AP group / set (e.g., 0, 1, 2, ...)

[0562] - For example, the relevant Multi-AP ID or AP ID can be included in the AID12 field within the User Info field of the Trigger frame.

[0563] C. Multi-AP scheme type: Information on Multi-AP cooperative transmission techniques such as Co-SR, Co-BF, C-TDMA, etc. (or, C-1. Multi-AP Coordination (MAPC) Type described below: an indication on Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, Co-BF, etc.)

[0564] - For example, utilizing the EHT Reserved (7 bits) or Reserved (4 bits) of the Common Info field

[0565] Specifically, defining a new field to indicate the type of Multi-AP cooperation by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperation transmission techniques that can be reflected in the new definition and standard).

[0566] Specifically, defining a new field to indicate the type of Multi-AP cooperation by utilizing one or more bits corresponding to Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperation transmission techniques that can be reflected in the new definition and standard).

[0567] - For example, it can be configured by combining and expanding the Triggered TXOP Sharing Mode field (2 bits) and Reserved (1 bit).

[0568] Specifically, using combined and extended 3 bits, it is possible to indicate Multi-AP cooperative transmission techniques currently in operation, such as Co-SR, Co-BF, and C-TDMA.

[0569] Additionally or alternatively, the Multi-AP scheme type field may be included in the User Info field or the Special User Info field.

[0570] C-1. Multi-AP Coordination (MAPC) Type: Instructions for Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, and Co-BF

[0571] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0572] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0573] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard).

[0574] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to Reserved fields / bits (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard)

[0575] For example, signaling can be done as follows

[0576] bit 0: None

[0577] bit 1: Co-TDMA

[0578] bit 2: Co-SR

[0579] bit 3: Co-BF

[0580] ...

[0581] For example, signaling can be done as follows

[0582] 0: Co-TDMA

[0583] 1: Co-SR

[0584] 2: Co-BF

[0585] ...

[0586] Additionally or alternatively, control information regarding the MAPC Type and the role for which the corresponding TF was transmitted can be signaled together.

[0587] For example, signaling can be done as follows based on each bit value.

[0588] 0: The role of ICF in Co-TDMA

[0589] 1: The role of TXOP return in Co-TDMA

[0590] 2: ICF (or Invite) role for the transmission section in Co-SR

[0591] 3: The Role of Synchronization / Co-Triggering Frames in Co-SR

[0592] 4: ICF (or Invite) role for the transmission section in Co-BF

[0593] 5: Role of Synchronization / Co-Triggering Frames in Co-BF

[0594] 6: The role of ICF (or Invite) for the sounding section in Co-BF

[0595] 7: Role of a trigger frame for sounding failure recovery in Co-BF

[0596] ...

[0597] -> Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0598] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0599] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0600] D. Coordination Triggering: Indicates that this is a trigger frame transmitted for the coordination triggering procedure in Multi-AP cooperation (can be replaced by D-1. BSRP Type described below).

[0601] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0602] Specifically, define a new field to indicate a trigger frame for Coordination Triggering by utilizing one or more bits corresponding to EHT Reserved.

[0603] Specifically, define a new field to indicate a trigger frame for coordination triggering by utilizing one or more bits corresponding to Reserved fields / bits.

[0604] bit 0: Indicates that the corresponding TF was sent for the purpose of a coordination announcement.

[0605] bit 1: Indicates that the corresponding TF was transmitted for the purpose of Coordination Triggering.

[0606] - Additionally, or alternatively, it may be included in the Feedback User Info field (AID12 = 2008).

[0607] D-1. BSRP Type (or Co-SR Subtype): Separately indicates control information regarding the role for which the corresponding BSRP TF was transmitted.

[0608] - That is, among the embodiments for the MAPC Type field and / or Coordination Triggering described above, control information regarding what role the corresponding TF was transmitted for can be indicated through a separate BSRP Type field.

[0609] For example, signaling can be done as follows based on each bit value

[0610] 0: Role of ICF or Invite Frame in the sounding phase

[0611] 1: Role of ICF or Invite Frame in Transmission Phase

[0612] 2: Role of Synchronization or Co-Triggering Frame in Transmission Phase

[0613] 3: Role of a trigger frame for the purpose of sounding failure recovery

[0614] 4: Role of the Intermediate Control frame during the sounding or transmission phase (e.g., the role of the TXOP return frame in Co-TDMA)

[0615] ...

[0616] -> Additionally or alternatively, signaling can be done with 1 bit as follows

[0617] 0: Role of ICF or Invite Frame in Transmission Phase

[0618] 1: Role of the Sync (Co-Triggering) frame in the transmission phase

[0619] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0620] - Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0621] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0622] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0623] E. Response Required: Indicates whether a response frame must be transmitted in response to the trigger frame (i.e., indicates whether it is solicit or unsolicit).

[0624] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0625] Specifically, defining a new field / signaling bit to indicate the requirement for transmitting a response frame by utilizing the 1 bit corresponding to EHT Reserved.

[0626] Specifically, define a new field / signaling bit to indicate the requirement for transmitting a response frame by utilizing the 1 bit corresponding to Reserved.

[0627] - For example, utilizing the Reserved (10 bits) of the User Info field

[0628] Specifically, define a new field / signaling bit to indicate the requirement for transmitting a response frame by utilizing the 1 bit corresponding to Reserved.

[0629] - For example, utilizing the Reserved (3 bits) of the Special User Info field

[0630] Specifically, define a new field / signaling bit to indicate the requirement for transmitting a response frame by utilizing the 1 bit corresponding to Reserved.

[0631] - The examples described above can all signal as follows.

[0632] bit 0: Solicit the transmission of the response frame for the transmission of the corresponding Trigger frame.

[0633] bit 1: Unsolicit transmission of the response frame for the transmission of the corresponding trigger frame

[0634] F. Coordination Duration: The period during which SAP collaborates with DAPs to perform Co-SR-based transmission.

[0635] - For example, define a new field including Coordination Duration to indicate

[0636] Specifically, a new field tentatively named Coordination Duration is defined to indicate the information and Coordination Duration values ​​required for MAPC operation.

[0637] - For example, utilizing the Allocation Duration field of the User Info field in the MU-RTS TXS Trigger frame

[0638] Specifically, the instruction includes the Coordination Duration value in the Allocation Duration field.

[0639] G. Recommended Tx Power: Maximum Tx power information recommended by SAP to the DAP triggering the Co-SR transfer.

[0640] - For example, in a scenario where SAP determines the Tx power of a DAP performing Co-SR transmission, SAP can determine the recommended maximum Tx power for the DAP that does not cause interference with its transmission.

[0641] - For example, it can refer to the maximum threshold Tx power of the DAP during the Co-SR transmission period.

[0642] In other words, the Recommended Tx Power that SAP conveys to the DAP can refer to an absolute value (e.g., calculated in units of dBm).

[0643] - For example, it can refer to the relative Tx power value allowed to the DAP during the Co-SR transmission period.

[0644] In other words, the Recommended Tx Power that SAP conveys to the DAP can represent a relative value.

[0645] Specifically, the value obtained by subtracting the maximum Tx power recommended to the DAP from SAP's Tx Power (i.e., Tx Power of SAP - Recommended Tx Power of DAP)

[0646] Additionally or alternatively, the value obtained by subtracting SAP's Tx Power from the maximum Tx power recommended to the DAP (i.e., Recommended Tx Power of DAP - Tx Power of SAP)

[0647] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0648] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0649] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0650] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0651] H. Multi-AP Ack Policy Indicator: Indicates the Ack policy during the coordination duration for Multi-AP cooperation.

[0652] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0653] Specifically, it utilizes the 2 bits corresponding to EHT Reserved or Reserved to instruct the Ack policy for frame exchanges between cooperating APs during the coordination duration.

[0654] For example, it can be defined similarly to the Ack Policy Indicator field within the QoS Control field.

[0655] Bit 0 = 0 & Bit 1 = 0: Indicates a normal ACK or an implicit BAR.

[0656] Bit 0 = 1 & Bit 1 = 0: Indicates No Ack

[0657] Bit 0 = 0 & Bit 1 = 1: Indicates No Explicit Acknowledgment or HETP Ack

[0658] Bit 0 = 1 & Bit 1 = 1: Indicates Block Ack

[0659] This specification proposes a Co-SR sequence required for APs in a cooperative relationship to perform Co-SR-based transmission in a multi-AP environment.

[0660] Specifically, Section 1 proposes a coordination announcement procedure to be performed sequentially with participating APs within a single TXOP to confirm whether they intend to participate in Co-SR transmission through the reception of a response frame or the information contained therein, and proposes a Co-SR sequence and necessary information for performing Co-SR transmission based on this.

[0661] Additionally or alternatively, Section 2 proposes confirming whether participating APs intend to participate in Co-SR transmission within a single TXOP through the reception and included information of the TB PPDU, and proposes the Co-SR sequence and necessary information when performing Co-SR transmission based on this.

[0662] Additionally or alternatively, Section 3 proposes a coordination announcement procedure to be performed sequentially with participating APs in a separate TXOP to confirm their intent to participate in the subsequent Co-SR transmission, and based on this, proposes the Co-SR sequence and necessary information for performing the Co-SR transmission.

[0663] Additionally or alternatively, Section 4 proposes the Co-SR sequence and necessary information for performing Co-SR transmission based on the information received from and contained in the TB PPDU, and confirming whether participating APs intend to participate in Co-SR transmission in a separate TXOP.

[0664] 8.2. Contents exchanged for Co-BF transmission in CA procedures performed within a single TXOP

[0665] In this section, we define and propose potential information that can be included in the CA (coordination announcement) frame presented in each section and the CAR frame, which is the response to it.

[0666] First, the CA frame (or ICF) transmitted during the CA process for Co-BF proposed in this specification may include content 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 to specific names.

[0667] A. Address: Address information of potential DAPs among the participating APs that wish to perform Co-BF transmission together (e.g., BSS color, BSSID for Multi-AP, or MAC address)

[0668] B. Multi-AP ID or AP ID: An ID locally assigned to each AP within a configured multi-AP group / set (e.g., 0, 1, 2, ...)

[0669] - For example, the relevant Multi-AP ID or AP ID can be included in the AID12 field within the User Info field of the Trigger frame.

[0670] C. UHR Feature Type: Indicates the feature type of the BSRP (UHR) TF (or C-1. UHR Feature Type (Feedback Type): described below, indicates the feature type of the BSRP (UHR) TF)

[0671] - That is, it indicates the purpose for which the BSRP (UHR) TF was transmitted.

[0672] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0673] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[0674] Specifically, it can indicate the type for which a BSRP TF, which can be utilized as an ICF 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.

[0675] bit 0: Indicates that it is a TF for multi-AP coordination operations.

[0676] bit 1: Indicates that it is a TF for DPS operation

[0677] bit 2: Indicates that it is a TF for IDC operations.

[0678] bit 3: Indicates that it is a TF for NPCA operations.

[0679] other bits: reserved

[0680] - Additionally or as an alternative, a UHR Feature field can be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved without specifying a specific UHR Feature Type.

[0681] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[0682] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[0683] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[0684] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field that can be newly defined for UHR.

[0685] C-1. UHR Feature Type (Feedback Type): Indicates the feature type of the BSRP (UHR) TF.

[0686] - That is, it indicates the purpose for which the BSRP (UHR) TF was transmitted (e.g., Co-SR or Co-SR Sync / Invite or MAPC).

[0687] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0688] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[0689] Specifically, it can indicate the type for which a BSRP TF, which can be utilized as an ICF 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.

[0690] bit 0: Indicates that it is a TF for multi-AP coordination operations.

[0691] bit 1: Indicates that it is a TF for DPS operation

[0692] bit 2: Indicates that it is a TF for IDC operations.

[0693] bit 3: Indicates that it is a TF for NPCA operations.

[0694] other bits: reserved

[0695] Specifically, it can indicate the type for which the BSRP TF was transmitted within a specific feature (e.g., MAPC). An example of signaling is as follows.

[0696] 0: Indicates that it has been transmitted to the ICF in the MAPC.

[0697] 1: Indicates that it was transmitted as a Co-Triggering frame in MAPC

[0698] 2: Indicates that it was transmitted to the CRF in the MAPC

[0699] 3: TBD

[0700] ...

[0701] -> Additionally or alternatively, specific types of particular UHR features and / or MAPC schemes can be indicated. An example of signaling is as follows.

[0702] 0: Co-existence

[0703] 1: Co-BF

[0704] 2: Co-SR

[0705] 3: Co-TDMA

[0706] 4: TBD

[0707] ...

[0708] -> Additionally or alternatively, control information regarding the type of a specific UHR feature and / or MAPC scheme and the role for which the corresponding TF was transmitted can be indicated together. An example of signaling is as follows.

[0709] 0: Co-existence

[0710] 1: Reserved

[0711] 2: Reserved

[0712] 3: ICF in Co-TDMA

[0713] 4: Sounding Invite frame in the sounding section at Co-BF

[0714] 5: Co-BF Invite frame in the transmission interval of Co-BF

[0715] 6: Synchronization (i.e., Co-Triggering) frame in Co-BF

[0716] 7: Co-SR Invite frame in the transmission interval of Co-SR

[0717] 8: Synchronization (i.e., Co-Triggering) frame in Co-SR

[0718] ...

[0719] Additionally or alternatively, control and info type information regarding the type of a specific UHR feature and / or MAPC scheme, the role for which the corresponding TF was transmitted, and specifically what type of information it contains can be indicated together. An example of signaling is as follows.

[0720] 0: Co-existence

[0721] 1: Reserved

[0722] 2: Reserved

[0723] 3: ICF in Co-TDMA

[0724] 4: Includes Common information in Co-BF sounding (i.e., Sounding Invite Common Info)

[0725] 5: Includes Per-User information in Co-BF sounding (i.e., Sounding Invite Per-User Info)

[0726] 6: Includes Common information for Invite in Co-BF (i.e., Invite Common Info)

[0727] 7: Includes Per-User information for Invite in Co-BF (i.e., Invite Per-User Info)

[0728] 8: Includes common information for synchronization in Co-BF (i.e., Sync Common Info)

[0729] 9: Includes Per-User information for synchronization in Co-BF (i.e., Sync Per-User Info)

[0730] 10: Includes information for Invite in Co-SR (i.e., Co-SR Invite Info)

[0731] 11: Includes information for synchronization in Co-SR (i.e., Co-SR Sync / Co-TF Info)

[0732] ...

[0733] - Additionally or as an alternative, a UHR Feature field can be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved without specifying a specific UHR Feature Type.

[0734] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[0735] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[0736] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[0737] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0738] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0739] - Additionally or alternatively, the information may be included by redesigning the reserved bits or parts of the Special User Info field (i.e., AID=2007).

[0740] D. Response Type: Indicates the type of response frame for the transmitted TF or the type of information solicited from the receiving device.

[0741] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0742] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[0743] Specifically, the type of TF that can be used as an ICF in DPS, IDC, NPCA, MAPC, etc., can indicate for what purpose it was transmitted and which response frame it solicits, and an example of signaling is as follows.

[0744] bit 0: No response (unsolicited)

[0745] bit 1: Instructs the receiving device to respond with a QoS Null / Data frame (including the A-Control field).

[0746] bit 2: Instructs the receiving device to respond with a BlockAck frame (e.g., Multi-STA BA).

[0747] bit 3: Instructs the receiving device to respond with an Action frame (including the A-Control field).

[0748] bit 4: Reserved

[0749] Depending on the solicit type and method, more bits can be used, and bitmaps can be utilized.

[0750] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0751] - Additionally or alternatively, one or more User Info field(s) with the same AID may exist, and additional User Info fields may include bits or fields to indicate the Response type.

[0752] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0753] - Additionally or alternatively, a Response Type field may be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved and integrating with the above-mentioned UHR Feature Type field.

[0754] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[0755] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[0756] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[0757] E. General Response: Allows a General response as a response frame for the transmitted TF.

[0758] - For example, allow the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, or QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields) in response to Basic TF.

[0759] - For example, allow the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, or QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields) in response to a BSRP TF.

[0760] - For example, allows the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields), CTS frames, etc., in response to a MU-RTS (TXS) TF.

[0761] F. Multi-AP Coordination Type: Instructions for Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, and Co-BF

[0762] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0763] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0764] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard).

[0765] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to Reserved fields / bits (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard)

[0766] For example, signaling can be done as follows

[0767] bit 0: None

[0768] bit 1: Co-TDMA

[0769] bit 2: Co-SR

[0770] bit 3: Co-BF

[0771] ...

[0772] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field that can be newly defined for UHR.

[0773] G. Common Procedure: Indicates that this is a Task Force (MAP TF) for the unified coordination announcement procedure for Multi-AP cooperation (can be replaced by G-1. BSRP Type described below).

[0774] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0775] - For example, you can utilize the EHT Reserved (7 bits) or Reserved of the Common Info field.

[0776] Specifically, it uses 1 bit to indicate that it is a TF transmitted for a coordination announcement.

[0777] bit 0: If the TF is not intended for coordination announcement

[0778] bit 1: Indicates that the corresponding TF was sent for the purpose of a coordination announcement.

[0779] - Additionally, or alternatively, 1 bit may be additionally utilized to indicate one of the procedures for Multi-AP cooperation.

[0780] Specifically, it indicates that it is a TF transferred for a specific procedure within the Multi-AP cooperation process.

[0781] bit 0: Indicates that the TF is not intended for coordination announcement.

[0782] bit 1: Indicates that the corresponding TF was sent for the purpose of a coordination announcement.

[0783] Bit 2: Indicates that the corresponding TF was transmitted for the purpose of coordination triggering (Additionally or alternatively, bit 2 can replace bit 0; that is, bit 0 can be used for the purpose indicated by bit 2).

[0784] bit 3: Indicates that the TF was transmitted for the TXOP return procedure.

[0785] - For example, you can utilize the Reserved field of the User Info field.

[0786] - Additionally or alternatively, one or more User Info field(s) with the same AID may exist, and additional User Info fields may include bits or fields to indicate a Common Procedure.

[0787] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field that can be newly defined for UHR.

[0788] G-1. BSRP Type (or Co-BF Subtype): Separately indicates control information regarding the role for which the corresponding BSRP TF was transmitted.

[0789] - That is, among the embodiments for the MAPC Type field and / or Coordination Triggering described above, control information regarding what role the corresponding TF was transmitted for can be indicated through a separate BSRP Type field.

[0790] For example, signaling can be done as follows based on each bit value

[0791] 0: Role of ICF or Invite Frame in the sounding phase

[0792] 1: Role of ICF or Invite Frame in Transmission Phase

[0793] 2: Role of Synchronization or Co-Triggering Frame in Transmission Phase

[0794] 3: Role of a trigger frame for the purpose of sounding failure recovery

[0795] 4: Role of the Intermediate Control frame during the sounding or transmission phase (e.g., the role of the TXOP return frame in Co-TDMA)

[0796] ...

[0797] -> Additionally or alternatively, signaling can be done with 1 bit as follows

[0798] 0: Role of ICF or Invite Frame in Transmission Phase

[0799] 1: Role of the Sync (Co-Triggering) frame in the transmission phase

[0800] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[0801] - Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0802] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0803] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[0804] H. Scheduled Coordination Duration: The period scheduled / planned for Co-BF transmission (or) the nominal TXOP period acquired by the sharing / coordinator AP for MAPC operation.

[0805] - For example, define a new field including Scheduled Coordination Duration and indicate it.

[0806] Specifically, it indicates the period during which Co-BF transmission is to be performed within the acquired TXOP by newly defining the Scheduled Coordination Duration field (tentative name).

[0807] - Additionally or alternatively, it may refer to and indicate the period for conducting cooperation with the target AP.

[0808] - Additionally, or alternatively, indicate the length of PPDUs that can be transmitted simultaneously while cooperating via Co-BF.

[0809] - Additionally, or alternatively, indicates a period including the length of one or more PPDUs that can be transmitted simultaneously while cooperating via Co-BF, the response frames thereto (e.g., BA), and the intervals between them (e.g., SIFS, PIFS).

[0810] I. Number of Non-OFDMA Users: The sum of the number of Co-BF recipient users on the SAP side and the number of Co-BF recipient users on the DAP side, or the number of Co-BF recipient users per AP

[0811] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / Triggered TXOP Sharing Mode field

[0812] - For example, Number Of Non-OFDMA Users (B17-B19) information in the Common field for EHT SU transmission and non-OFDMA transmission

[0813] Specifically, the value of the Number Of Non-OFDMA Users field can represent the sum of the number of Co-BF target users on the SAP side and the number of Co-BF target users on the DAP side.

[0814] - Additionally, or alternatively, the Number Of Non-OFDMA Users field can be defined as 2 bits, and each 1 bit can be used to indicate the number of Co-BF target users of SAP and DAP.

[0815] For example, B17 indicates the number of SAP users (e.g., 0 is single user, 1 is 2 users)

[0816] For example, B18 indicates the number of DAP users (e.g., 0 is single user, 1 is 2 users)

[0817] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0818] J. In-BSS STA Info: Indicates information about the Target STA or all associated STAs for which SAP will perform DL / UL transmission via Co-BF transmission.

[0819] - For example, the identifier and capability of the target STA among the STAs connected to SAP that intends to perform DL / UL transmission via Co-BF transmission within the current TXOP.

[0820] For example, the Target STA's AID (11 or 12 bits) or MAC address

[0821] For example, the MIMO and RF capabilities of the Target STA

[0822] - For example, the identifier and capability of the target STA among the STAs connected to SAP that intends to perform DL / UL transmission via a subsequent Co-BF transmission.

[0823] For example, the Target STA's AID (11 or 12 bits) or MAC address

[0824] For example, the MIMO and RF capabilities of the Target STA

[0825] - For example, an identifier for an In-BSS STA that you want to include in the sounding (or OBSS channel sounding) process for Co-BF transmission.

[0826] - For example, STA-ID field (B0-B10) information within the User field for non-MU-MIMO allocation

[0827] Specifically, ID information of the STA receiving the DL PPDU transmitted based on Co-BF

[0828] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0829] K. Coordination Triggering: Indicates that the TF was transmitted to trigger Co-BF transmission.

[0830] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0831] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0832] Specifically, define a new field to direct Coordination Triggering using one or more bits corresponding to EHT Reserved.

[0833] Specifically, define a new field to direct Coordination Triggering by utilizing one or more bits corresponding to Reserved fields / bits.

[0834] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0835] L. Coordination Duration: Indicates the period for performing Co-BF transmission.

[0836] - For example, the Allocation Duration field within a MU-RTS TXS Trigger frame

[0837] - For example, define a new field containing a coordination duration that plays a role similar to the Allocation Duration field within a MU-RTS TXS Trigger frame, and indicate it.

[0838] Specifically, a new field tentatively named Coordination Duration is defined to indicate the Co-BF transmission period.

[0839] - Additionally or alternatively, it may refer to and indicate the period for conducting cooperation with the target AP.

[0840] - Additionally, or alternatively, indicate the length of PPDUs that can be transmitted simultaneously while cooperating via Co-BF.

[0841] - Additionally, or alternatively, indicates a period including the length of one or more PPDUs that can be transmitted simultaneously while cooperating via Co-BF, the response frames thereto (e.g., BA), and the intervals between them (e.g., SIFS, PIFS).

[0842] M. Multi-AP Ack Policy Indicator: Indicates the Ack policy during the Co-BF transmission period

[0843] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0844] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0845] Specifically, it utilizes the 2 bits corresponding to EHT Reserved or Reserved to specify the Ack policy for frame exchanges between cooperating APs during the Co-BF Duration.

[0846] For example, it can be defined similarly to the Ack Policy Indicator field within the QoS Control field.

[0847] Bit 0 = 0 & Bit 1 = 0: Indicates a normal ACK or an implicit BAR.

[0848] Bit 0 = 1 & Bit 1 = 0: Indicates No Ack

[0849] Bit 0 = 0 & Bit 1 = 1: Indicates No Explicit Acknowledgment or HETP Ack

[0850] Bit 0 = 1 & Bit 1 = 1: Indicates Block Ack

[0851] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0852] N. Common U-SIG Info: U-SIG-1 and U-SIG-2 information that must be commonly included in DL PPDUs transmitted by each AP during the relevant cooperation-based transmission period.

[0853] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0854] - For example, Bandwidth (B3-B5) information of the U-SIG-1 field within the EHT MU PPDU

[0855] Specifically, it indicates the bandwidth of the DL PPDU transmitted by each AP during the Co-BF transmission period.

[0856] - For example, UL / DL (B6) information in the U-SIG-1 field within the EHT MU PPDU

[0857] Specifically, it indicates whether DL transmission or UL transmission is scheduled to be performed during the relevant Co-BF transmission period.

[0858] - For example, Punctured Channel Information (B3-B7) of the U-SIG-2 field within the EHT MU PPDU

[0859] - For example, a UHR-SIG MCS can be defined that performs the same role as the EHT-SIG MCS (B9-B10) of the U-SIG-2 field within the EHT MU PPDU.

[0860] Specifically, the value of UHR-SIG MCS can indicate the following MCS:

[0861] UHR-SIG MCS = 0 indicates UHR-MCS 0.

[0862] UHR-SIG MCS = 1 indicates UHR-MCS 1.

[0863] UHR-SIG MCS = 2 indicates UHR-MCS 3.

[0864] UHR-SIG MCS = 3 indicates UHR-MCS 15.

[0865] - For example, Number of UHR-SIG Symbols can be defined to serve the same role as Number of EHT-SIG Symbols (B11-B15) in the U-SIG-2 field within the EHT MU PPDU.

[0866] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0867] - One or more of the information described above may be included in the Common U-SIG Info field, but is not limited to.

[0868] O. Non-OFDMA Common Info: Non-OFDMA information that must be commonly included in the DL PPDU transmitted by each AP during the corresponding cooperative-based transmission period.

[0869] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0870] - For example, GI+LTF Size (B4-B5) information in the Common field for EHT SU transmission and non-OFDMA transmission

[0871] - For example, Number of UHR-LTF Symbols can be defined to serve the same role as Number of EHT-LTF Symbols (B6-B8) in the Common field for EHT SU transmission and non-OFDMA transmission.

[0872] - For example, Number Of Non-OFDMA Users (B17-B19) information in the Common field for EHT SU transmission and non-OFDMA transmission

[0873] Specifically, the value of the Number Of Non-OFDMA Users field can represent the sum of the number of Co-BF target users on the SAP side and the number of Co-BF target users on the DAP side.

[0874] - Additionally, or alternatively, the Number Of Non-OFDMA Users field can be defined as 2 bits, and each 1 bit can be used to indicate the number of Co-BF target users of SAP and DAP.

[0875] For example, B17 indicates the number of SAP users (e.g., 0 is single user, 1 is 2 users)

[0876] For example, B18 indicates the number of DAP users (e.g., 0 is single user, 1 is 2 users)

[0877] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0878] - One or more of the information described above may be included in the Non-OFDMA Common Info field, but is not limited to.

[0879] P. MU-MIMO User Info: MU-MIMO user field information or user field format information for MU-MIMO allocation that must be included in the DL PPDU transmitted by each AP during the relevant cooperative-based transmission period.

[0880] - For example, STA-ID field (B0-B10) information within the User field

[0881] Specifically, ID information of the STA receiving the DL PPDU transmitted based on Co-BF

[0882] - For example, MCS (B11-B15) information within the User field

[0883] - For example, Spatial Configuration (B16-B19) information within the User field

[0884] Specifically, it specifies the number of spatial streams for each user in MU-MIMO allocation.

[0885] Additionally, or as an alternative, the Spatial Configuration field can be defined and utilized as 3 bits.

[0886] - For example, BSS Color Indication (B21) information can be newly defined.

[0887] Specifically, it is used to indicate which of the two BSSs participating in Co-BF the MU-MIMO User Info field refers to a user existing in.

[0888] - For example, 2xLDPC (B22) information

[0889] - Additionally, or alternatively, include the relevant information in the UHR Special User Info field that may be newly defined for UHR.

[0890] - Additionally, or alternatively, some information may be included in Common Info fields or User Info fields.

[0891] - One or more of the information described above may be included in the MU-MIMO User Info field, but is not limited to.

[0892] In addition to the contents presented above, some fields included in the Common field for EHT SU transmission and non-OFDMA transmission for existing users (e.g., LDPC Extra Symbol Segment, Pre-FEC Padding Factor, PE Disambiguity, Spatial Reuse, etc.) may be included in the contents for Co-BF transmission.

[0893] Additionally, the CAR frame (or ICR frame) transmitted in the CA procedure for Co-BF proposed in this specification may include content 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.

[0894] A. Coordination Required: Indicates the need for coordination regarding confirmation of intent to participate in a Co-BF transmission solicited from a CA frame or confirmation of intent to participate in a cooperation-based transmission based on one or more MAPC schemes.

[0895] - For example, uses 1 bit to indicate whether to participate in MAPC-based transmission.

[0896] bit 0: Indicates not to participate in the requested MAPC-based transmission

[0897] bit 1: Indicates participation in the requested MAPC-based transmission.

[0898] B. Required Coordination Duration: Information regarding the cooperation period desired / required by the AP receiving the CA frame.

[0899] - For example, define a new field including Required Coordination Duration to indicate

[0900] Specifically, a new field tentatively named "Required Coordination Duration" is defined to indicate the TXOP duration and period required for Co-BF transmission.

[0901] - Additionally or alternatively, indicate the length of the PPDU you wish to transmit during Co-BF transmission.

[0902] - Additionally or alternatively, indicate a period including the length of one or more PPDUs to be transmitted during Co-BF transmission, the response frames (e.g., BA), and the intervals between them (e.g., SIFS, PIFS).

[0903] C. Buffer Status: Current buffer status information of the AP that received the CA frame, or the amount of buffer that the AP intends to transmit during the Co-BF transmission period.

[0904] D. In-BSS STA Info: Indicates information about the Target STA or all associated STAs for which SAP will perform DL / UL transmission via Co-BF transmission.

[0905] - For example, the identifier and capability of the target STA among the STAs connected to SAP that intends to perform DL / UL transmission via Co-BF transmission within the current TXOP.

[0906] For example, the Target STA's AID (11 or 12 bits) or MAC address

[0907] For example, the MIMO and RF capabilities of the Target STA

[0908] - For example, the identifier and capability of the target STA among the STAs connected to SAP that intends to perform DL / UL transmission via a subsequent Co-BF transmission.

[0909] For example, the Target STA's AID (11 or 12 bits) or MAC address

[0910] For example, the MIMO and RF capabilities of the Target STA

[0911] - For example, an identifier for an In-BSS STA that you want to include in the sounding (or OBSS channel sounding) process for Co-BF transmission.

[0912] - For example, STA-ID field (B0-B10) information within the User field for non-MU-MIMO allocation

[0913] Specifically, ID information of the STA receiving the DL PPDU transmitted based on Co-BF

[0914] -> Additionally, or alternatively, include the relevant information in the UHR Special User Info field that can be newly defined for UHR.

[0915] E. Status Code: Accept / Reject / Recommendation information for the CA frame (i.e., can serve the same role as the Coordination Required information defined and described above, or the Status Code can replace it)

[0916] - For example, an AP that receives a CA frame can accept or reject it based on its intention to participate, whether it currently requires cooperation-based transmission or wishes to perform Co-BF-based transmission.

[0917] - For example, Accept or Success (e.g., SUCCESS)

[0918] - For example, a Reject including a Reject or Recommendation

[0919] Specifically, a rejection code containing the rejection reason (e.g., REJECTED_BAD_SUPPORTED_CHANNELS)

[0920] Specifically, a reject code including a recommendation (e.g., REJECTED_WITH_SUGGESTED_CHANGES)

[0921] If the value of the Status Code includes Reject or Recommendation, it may include information for a new coordination announcement procedure. That is, the AP that receives the CA frame may include additional information regarding the Coordination Required, Required Coordination Duration, Buffer Status, In-BSS STA Info, and Status Code described above.

[0922] This specification proposes an overall Co-BF sequence required for APs in a cooperative relationship to perform Co-BF-based transmission in a multi-AP environment. Specifically, an AP intending to perform Co-BF transmission may initiate a TXOP with a coordination announcement procedure. This is intended to notify the APs that will perform Co-BF transmission together that Co-BF transmission is scheduled to begin, and / or to exchange information necessary for Co-BF transmission. The relevant SAP can confirm the intention to participate in Co-BF transmission from the target AP and obtain relevant information, and based on this, can trigger Co-BF transmission within the same TXOP to perform Co-BF-based transmission.

[0923] Additionally or alternatively, an AP that intends to perform Co-BF transmission may perform a coordination announcement procedure during a separate TXOP for the purpose of selecting an AP to perform Co-BF transmission with and / or announcing that Co-BF transmission is scheduled to begin and / or exchanging information necessary for a sounding procedure for Co-BF transmission. Through the coordination announcement procedure and / or sounding procedure performed in a separate TXOP, the AP may confirm the intention of the target AP to participate in Co-BF transmission and obtain relevant information, and based on this, may trigger Co-BF transmission in a subsequent TXOP to perform Co-BF-based transmission.

[0924] Additionally or alternatively, an AP wishing to perform Co-BF transmission can initiate a TXOP with the transmission of a Co-Triggering frame to immediately trigger Co-BF transmission. This has the advantage of reducing frame exchange overhead because it does not require short-term negotiation. Upon receiving this, the AP can perform Co-BF-based transmission with the SAP.

[0925] To clarify the terms, in each of the above sections, the CA frame may be a Co-BF / Co-SR Invite frame, the CAR frame may be a Co-BF / Co-SR Response frame, and the Co-Triggering frame may be a Co-BF / Co-SR Trigger frame.

[0926] 9. Definition of a Trigger Frame for the Purpose of Initiating and Triggering Co-SR / Co-BF Transmission

[0927] Basically, in a Co-TDMA environment, since the SAP allocates time to the DAP, cooperative-based transmission can be triggered by utilizing the existing Triggered TXS protocol. That is, TXOP sharing between APs can be performed by including information for Co-TDMA operation and signaling bits in the MU-RTS TXS TF. Meanwhile, Co-SR / Co-BF, one of the Multi-AP cooperative-based technologies, is characterized by the DAP transmitting together in response to triggering from the SAP. Consequently, to initiate Co-SR / Co-BF transmission, it is necessary to implement a new Trigger Frame (TF) that can be delivered from the SAP or to modify an existing Trigger Frame. New information for Co-SR / Co-BF transmission may also be included within the Trigger Frame.

[0928] Accordingly, this specification defines the structure and format of a Trigger frame transmitted by SAP to initiate Co-SR / Co-BF transmission with a DAP and / or to perform a polling procedure targeting one or more cooperating APs. Specifically, this specification utilizes a BSRP Trigger frame to trigger Co-SR / Co-BF transmission and / or perform a polling procedure. Using the BSRP TF presented in this specification, SAP can trigger Co-SR / Co-BF transmission to a DAP or determine whether cooperating APs will participate in Co-SR / Co-BF transmission during the polling procedure.

[0929] Specific designations (names) proposed in this specification may be changed and are not limited.

[0930] 9.1. BSRP TF-based Co-SR / Co-BF Transmission Trigger Procedure

[0931] This specification defines a Trigger frame for the purpose of initiating and triggering Co-SR / Co-BF transmission. The structure and format of the BSRP Trigger frame for Co-SR / Co-BF proposed in this specification can be defined and designed as presented in the detailed sections below.

[0932] Additionally, this specification assumes that SAP transmits a BSRP TF to at least one DAP to trigger a Co-SR / Co-BF transmission or for a polling procedure targeting one or more cooperating APs. In this case, the BSRP TF transmitted for the polling procedure may also be transmitted to a non-AP STA connected to SAP (i.e., the AID12 value for the target non-AP STA may be included in the AID12 field within the User Info field).

[0933] FIG. 28 illustrates an example of a BSRP TF-based Co-SR / Co-BF transmission trigger procedure.

[0934] FIG. 28 illustrates an example of a procedure for triggering Co-SR / Co-BF transmission based on a BSRP TF assumed in this specification. AP 1, acting as the SAP, acquires a TXOP and transmits a BSRP TF acting as an initial control frame (ICF), thereby initiating and triggering Co-SR / Co-BF transmission. Upon receiving the BSRP TF transmitted from the SAP, the target DAP (AP 2 in FIG. 28) may transmit a response frame (e.g., Management frame, BlockAck frame, etc.) as a confirmation of the start of Co-SR / Co-BF transmission. Additionally or alternatively, the response frame may be defined and implemented to be unsolicit. For example, in the case of Co-SR / Co-BF, the response frame may be defined to be unsolicit (i.e., not responding with a response frame). Additionally or alternatively, a separate signaling bit / field may indicate no response.

[0935] Additionally or alternatively, the BSRP TF can be used as a trigger frame in a polling (or Multi-AP selection, coordination announcement) procedure that can be performed for the purpose of determining whether one or more cooperating APs will participate in Co-SR / Co-BF transmission. In this case, the BSRP TF can also serve as an ICF. Additionally or alternatively, the BSRP TF in the polling phase and the response frame thereto (e.g., Multi-STA BA) can be performed for the purpose of exchanging preliminary information for Co-SR / Co-BF transmission. FIG. 29 illustrates an example of performing a polling procedure in advance for Co-SR transmission based on the BSRP TF assumed herein.

[0936] FIG. 29 illustrates an example of a Co-SR / Co-BF transmission trigger procedure following a BSRP TF-based polling procedure.

[0937] Basically, the AID12 field or RA field within the User Info field of a BSRP TF transmitted between APs may contain the receiving AP's AP ID (ID for Multi-AP cooperation) or the AP's MAC address. Therefore, the Spec may define that an AP receiving a BSRP TF addressed to it transmits a corresponding response frame (e.g., Multi-STA BA frame). In other words, based on definitions regarding the type and format of the ICF and ICR for Multi-AP cooperation operation between APs, each AP can transmit and receive appropriate ICFs and ICRs. For example, a BSRP TF transmitted by an SAP as an ICF is basically sent to a MU, and the receiving STAs (cooperating APs and non-AP STAs) respond by including an appropriate frame in the TB PPDU. At this time, the cooperating AP can respond with a specific frame (e.g., Multi-STA BlockAck) depending on the type and format of the ICR, and the non-AP STA can respond with the existing method (i.e., QoS Data / Null frame including A-Control) or with a specific frame (e.g., Multi-STA BlockAck) defined according to the mode of the non-AP STA (e.g., DPS, NPCA, IDC, Coexistence, etc.).

[0938] Additionally or alternatively, the BSRP TF can be defined and utilized as a new mode or subtype of the BSRP TF based on the existing GI And HE / EHT-LTF Type / TXS Mode field (i.e., B20-B21 within the EHT variant Common Info field). That is, as shown in Table 1, it can be defined for use with the main features of the UHR. When indicating the role of the ICF for the main features of the UHR, a field indicating which feature the corresponding BSRP UHR TF (tentative name) is intended to operate on can be included by utilizing the subsequent Reserved bit. By defining a new subtype of the BSRP TF in this way, the remaining fields, excluding those essential for the operation of each feature, can be defined to contain the information required for each feature (i.e., the remaining fields following the GI And HE / EHT-LTF Type / TXS Mode field can be reserved; this may differ from the format of the existing BSRP TF). Exceptions and rules can be additionally defined in this new subtype of the BSRP TF. For example, a BSRP TF with GI And HE / EHT-LTF Type / TXS Mode field = 3 can be classified as a Class 1 frame. Additionally, the remaining fields, excluding those essential for the operation of each feature, can be defined to contain the information required for each feature (i.e., the remaining fields following the GI And HE / EHT-LTF Type / TXS Mode field can be reserved, which may differ from the format of the existing BSRP TF).Additionally or alternatively, the reserved range may be utilized to include Common Info for Multi-AP cooperation or Info specific to each Multi-AP cooperation scheme (e.g., Co-SR, Co-BF, Co-TDMA, etc.). Additionally or alternatively, a STA receiving the BSRP (UHR) TF may not transmit a response frame under specific conditions / instructions. A separate signaling bit / field may be added for a no response. Additionally or alternatively, a STA receiving the BSRP (UHR) TF may respond with a frame of a different type than a QoS Data / Null frame containing BSR information. Additionally or alternatively, a STA receiving the BSRP (UHR) TF may transmit a non-TB PPDU or non-HT (dup) PPDU instead of a TB PPDU. For example, when the value of the GI And HE / EHT-LTF Type / TXS Mode field of the BSRP TF transmitted by the SAP as an ICF is set to 3, it is transmitted to the SU by default, and the receiving STA (i.e., cooperating AP or non-AP STA) responds by including an appropriate frame in a non-TB PPDU or non-HT (dup) PPDU. Specifically, the cooperating AP may respond by including a specific frame (e.g., Multi-STA BlockAck) in the non-TB PPDU or non-HT (dup) PPDU depending on the type and format of the ICR.

[0939] To trigger Co-SR / BF transmission, a BSRP (UHR) TF based on a new subtype may include common information for Multi-AP cooperation and specific parameters related to each Multi-AP cooperation base technology, and for this purpose, existing fields may be reused or new fields may be defined. The specific designations (names) of the proposed information, fields, and signaling bit(s) may be changed.

[0940] GI And HE / EHT-LF Type / TXS Mode Subfield valueDescription01x HE / EHT-LTF + 1.6us GI12x HE / EHT-LTF + 1.6us GI24x HE / EHT-LTF + 3.2us GI3BSRP serves as the initial control frame for UHR features

[0941] 9.2. Information and contents for Co-SR / Co-BF transmission

[0942] For example, common information for Multi-AP cooperation and specific information related to Co-SR / Co-BF transmission may be defined as follows. One or more of the information, fields, and signaling bit(s) presented below may be added and defined within the BSRP TF, but are not limited thereto. Additionally, the specific designations (names) of the proposed information, fields, and signaling bit(s) may be changed.

[0943] A. Address: Address information of the DAP that triggers the Co-SR / BF transmission (e.g., BSS color, BSSID for Multi-AP, or MAC address)

[0944] B. Multi-AP ID or AP ID: An ID locally assigned to each AP within a configured multi-AP group / set (e.g., 0, 1, 2, ...)

[0945] - For example, the relevant Multi-AP ID or AP ID can be included in the AID12 field within the User Info field of the Trigger frame.

[0946] -> Additionally or alternatively, a Multi-AP ID or AP ID may be included within the AID12 field of the UHR Special User Info field, which may be newly defined for UHR.

[0947] - For example, the relevant Multi-AP ID or AP ID may be included in the AID11 field within the STA Info field of the UHR NDP Announcement frame.

[0948] C. Operating channel: Information on the operating primary channel and punctured channel

[0949] - For example, channel information that operates commonly to ensure smooth cooperation between APs participating in MAPC

[0950] - For example, primary channel information that APs participating in MAPC can operate in common

[0951] Specifically, a new field that serves as the CCFS0 field within the UHR Operation Information field can be defined to indicate the channel center frequency index for 20 / 40 / 80 MHz channels.

[0952] Specifically, a new field that serves as the CCFS0 field within the UHR Operation Information field can be defined to indicate the channel center frequency for the primary 80 MHz channel of the 160 MHz channel or the channel center frequency for the primary 160 MHz channel of the 320 MHz channel.

[0953] In addition, a new field that serves as the CCFS1 field within the UHR 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.

[0954] - For example, punctured channel information of APs participating in MAPC

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

[0956] Bit value of 0 in the bitmap: Indicates that the corresponding 20 MHz subchannel is not punctured.

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

[0958] - The primary channel of the coordinated AP may be included within the channel where the SAP operates.

[0959] - The primary channel of the coordinated AP may be included within the operation channel, excluding the punctured channel of the SAP.

[0960] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0961] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0962] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0963] - Additionally or alternatively, the information may be included by redesigning the reserved bits or parts of the Special User Info field (i.e., AID=2007).

[0964] D. Operating bandwidth: Information on operating bandwidth and maximum bandwidth

[0965] - For example, BW information that operates commonly for smooth cooperation among APs participating in MAPC

[0966] Specifically, the Operating channel and primary channel information described above can be utilized.

[0967] - For example, maximum bandwidth information of APs participating in MAPC

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

[0969] Set to 0: 20 MHz bandwidth indication

[0970] Set to 1: 40 MHz bandwidth indication

[0971] Set to 2: 80 MHz bandwidth indication

[0972] Set to 3: 160 / 80+80 MHz bandwidth indication

[0973] Set to 4: 320 / 160+160 MHz bandwidth indication

[0974] The remaining values ​​from 5 to 7 can be set to reserved.

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

[0976] - For example, UL BW field information included within the Common Info field of the Trigger frame

[0977] - The bandwidth of DAP or CAP may be included within the total bandwidth in which SAP operates.

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

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

[0980] Set to 0: 20 MHz bandwidth indication

[0981] Set to 1: 40 MHz bandwidth indication

[0982] Set to 2: 80 MHz bandwidth indication

[0983] Set to 3: 160 / 80+80 MHz bandwidth indication

[0984] Set to 4: 320 / 160+160 MHz bandwidth indication

[0985] The remaining values ​​from 5 to 7 can be set to reserved.

[0986] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[0987] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[0988] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[0989] - Additionally or alternatively, the information may be included by redesigning the reserved bits or parts of the Special User Info field (i.e., AID=2007).

[0990] E. UHR Feature Type (Feedback Type): Indicates the feature type of the BSRP (UHR) TF.

[0991] - That is, it indicates the purpose for which the BSRP (UHR) TF was transmitted (e.g., Co-SR or Co-SR Sync / Invite or MAPC).

[0992] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[0993] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[0994] Specifically, it can indicate the type for which a BSRP TF, which can be utilized as an ICF 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.

[0995] bit 0: Indicates that it is a TF for multi-AP coordination operations.

[0996] bit 1: Indicates that it is a TF for DPS operation

[0997] bit 2: Indicates that it is a TF for IDC operations.

[0998] bit 3: Indicates that it is a TF for NPCA operations.

[0999] other bits: reserved

[1000] Specifically, it can indicate the type for which the BSRP TF was transmitted within a specific feature (e.g., MAPC). An example of signaling is as follows.

[1001] 0: Indicates that it has been transmitted to the ICF in the MAPC.

[1002] 1: Indicates that it was transmitted as a Co-Triggering frame in MAPC

[1003] 2: Indicates that it was transmitted to the CRF in the MAPC

[1004] 3: TBD

[1005] ...

[1006] -> Additionally or alternatively, specific types of particular UHR features and / or MAPC schemes can be indicated. An example of signaling is as follows.

[1007] 0: Co-existence

[1008] 1: Co-BF

[1009] 2: Co-SR

[1010] 3: Co-TDMA

[1011] 4: TBD

[1012] ...

[1013] -> Additionally or alternatively, control information regarding the type of a specific UHR feature and / or MAPC scheme and the role for which the corresponding TF was transmitted can be indicated together. An example of signaling is as follows.

[1014] 0: Co-existence

[1015] 1: Reserved

[1016] 2: Reserved

[1017] 3: ICF in Co-TDMA

[1018] 4: Sounding Invite frame in the sounding section at Co-BF

[1019] 5: Co-BF Invite frame in the transmission interval of Co-BF

[1020] 6: Synchronization (i.e., Co-Triggering) frame in Co-BF

[1021] 7: Co-SR Invite frame in the transmission interval of Co-SR

[1022] 8: Synchronization (i.e., Co-Triggering) frame in Co-SR

[1023] ...

[1024] Additionally or alternatively, control and info type information regarding the type of a specific UHR feature and / or MAPC scheme, the role for which the corresponding TF was transmitted, and specifically what type of information it contains can be indicated together. An example of signaling is as follows.

[1025] 0: Co-existence

[1026] 1: Reserved

[1027] 2: Reserved

[1028] 3: ICF in Co-TDMA

[1029] 4: Includes Common information in Co-BF sounding (i.e., Sounding Invite Common Info)

[1030] 5: Includes Per-User information in Co-BF sounding (i.e., Sounding Invite Per-User Info)

[1031] 6: Includes Common information for Invite in Co-BF (i.e., Invite Common Info)

[1032] 7: Includes Per-User information for Invite in Co-BF (i.e., Invite Per-User Info)

[1033] 8: Includes common information for synchronization in Co-BF (i.e., Sync Common Info)

[1034] 9: Includes Per-User information for synchronization in Co-BF (i.e., Sync Per-User Info)

[1035] 10: Includes information for Invite in Co-SR (i.e., Co-SR Invite Info)

[1036] 11: Includes information for synchronization in Co-SR (i.e., Co-SR Sync / Co-TF Info)

[1037] ...

[1038] - Additionally or as an alternative, a UHR Feature field can be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved without specifying a specific UHR Feature Type.

[1039] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[1040] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[1041] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[1042] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1043] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1044] - Additionally or alternatively, the information may be included by redesigning the reserved bits or parts of the Special User Info field (i.e., AID=2007).

[1045] F. Feedback Information: A field containing UHR feature or MAPC scheme-specific Control Information transmitted to the receiving STA via an ICF or CRF (i.e., BSRP TF), such as a Co-SR / BF Invite or Sync frame, or a field containing information related to or helpful in providing feedback information regarding the UHR feature or MAPC scheme-specific feedback information that the transmitting device wishes to receive from the receiving device.

[1046] - For example, Control / Feedback Info corresponding to the feature specified in the Control Info / Feedback Type (e.g., MAPC Info or Co-BF / SR / TDMA Info, etc.)

[1047] For example, feature-specific information that must be transmitted to the receiving STA to operate as IDC, MAPC (or Co-BF / SR / TDMA), DPS, or NPCA

[1048] Specifically, common information regarding the feature

[1049] Specifically, user-specific information regarding the feature

[1050] For example, feature-specific information that must be transmitted to the receiving AP to operate as IDC, MAPC (or Co-BF / SR / TDMA), DPS, or NPCA

[1051] Specifically, common information regarding the feature

[1052] Specifically, user-specific information regarding the feature

[1053] G. Common Control / Feedback Info: Common Control / Feedback Info may contain common information for each feature (i.e., IDC, MAPC, DPS, NPCA, or Co-BF / SR / TDMA).

[1054] H. Per-User Control / Feedback Info: Per-User Control / Feedback Info may include user-specific information (i.e., non-AP STA or AP) for each feature (i.e., IDC, MAPC, DPS, NPCA, or Co-BF / SR / TDMA).

[1055] - Additionally or alternatively, the ICF or CRF may include information that can be included in the existing A-Control field (e.g., BSR) in addition to information related to IDC Info, MAPC (Co-BF / SR / TDMA) Info, DPS Info, NPCA Info, etc. as presented in this specification.

[1056] I. Response Type: Indicates the type of response frame for the transmitted TF or the type of information solicited from the receiving device.

[1057] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[1058] - For example, utilizing EHT Reserved or Reserved in the Common Info field

[1059] Specifically, the type of TF that can be used as an ICF in DPS, IDC, NPCA, MAPC, etc., can indicate for what purpose it was transmitted and which response frame it solicits, and an example of signaling is as follows.

[1060] bit 0: No response (unsolicited)

[1061] bit 1: Instructs the receiving device to respond with a QoS Null / Data frame (including the A-Control field).

[1062] bit 2: Instructs the receiving device to respond with a BlockAck frame (e.g., Multi-STA BA).

[1063] bit 3: Instructs the receiving device to respond with an Action frame (including the A-Control field).

[1064] bit 4: Reserved

[1065] Depending on the solicit type and method, more bits can be used, and bitmaps can be utilized.

[1066] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1067] - Additionally or alternatively, one or more User Info field(s) with the same AID may exist, and additional User Info fields may include bits or fields to indicate the Response type.

[1068] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field that can be newly defined for UHR.

[1069] - Additionally or alternatively, a Response Type field may be assumed for the purpose of soliciting response Info for one or more operational purposes, such as DPS, IDC, NPCA, MAPC, etc., by utilizing Reserved and integrating with the above-mentioned UHR Feature Type field.

[1070] For example, each bit of the 4 bits can indicate a specific feature (e.g., DPS, IDC, NPCA, MAPC, etc.).

[1071] An example of soliciting feature type indications and response information using a combination of each bit (bitmap) is as follows.

[1072] If B56: MAPC, B57: DPS, B58: IDC, B59: NPCA, other bits: reserved, 1100 can solicit instructions and response information for MAPC and DPS operations.

[1073] J. General Response: Allows a General response as a response frame for the transmitted TF.

[1074] - For example, allow the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, or QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields) in response to Basic TF.

[1075] - For example, allow the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, or QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields) in response to a BSRP TF.

[1076] - For example, allows the transmission of Multi-STA BA (or Compressed BA) frames, Action frames, QoS Null / Data frames (with a new A-Control field or with one or more A-Control fields), CTS frames, etc., in response to a MU-RTS (TXS) TF.

[1077] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1078] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field that can be newly defined for UHR.

[1079] K. Multi-AP Coordination (MAPC) Type: Instructions for Multi-AP cooperative transmission techniques such as Co-TDMA, Co-SR, and Co-BF

[1080] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[1081] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1082] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to EHT Reserved (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard).

[1083] Specifically, defining a new field to indicate the Multi-AP Coordination Type by utilizing one or more bits corresponding to Reserved fields / bits (i.e., utilizing 1 to n bits depending on the number of Multi-AP cooperative transmission techniques that can be reflected in the new definition and standard)

[1084] For example, signaling can be done as follows

[1085] bit 0: None

[1086] bit 1: Co-TDMA

[1087] bit 2: Co-SR

[1088] bit 3: Co-BF

[1089] ...

[1090] For example, signaling can be done as follows

[1091] 0: Co-TDMA

[1092] 1: Co-SR

[1093] 2: Co-BF

[1094] ...

[1095] Additionally or alternatively, control information regarding the MAPC Type and the role for which the corresponding TF was transmitted can be signaled together.

[1096] For example, signaling can be done as follows based on each bit value.

[1097] 0: The role of ICF in Co-TDMA

[1098] 1: The role of TXOP return in Co-TDMA

[1099] 2: ICF (or Invite) role for the transmission section in Co-SR

[1100] 3: The Role of Synchronization / Co-Triggering Frames in Co-SR

[1101] 4: ICF (or Invite) role for the transmission section in Co-BF

[1102] 5: Role of Synchronization / Co-Triggering Frames in Co-BF

[1103] 6: The role of ICF (or Invite) for the sounding section in Co-BF

[1104] 7: Role of a trigger frame for sounding failure recovery in Co-BF

[1105] ...

[1106] -> Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1107] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1108] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1109] L. Coordination Triggering: Indicates that it is a BSRP (UHR) TF transmitted to trigger a Multi-AP cooperative-based transmission (e.g., Co-SR).

[1110] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[1111] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1112] Specifically, defining a new field to indicate a BSRP (UHR) TF for Coordination Triggering by utilizing one or more bits corresponding to EHT Reserved.

[1113] Specifically, defining a new field to indicate a BSRP (UHR) TF for Coordination Triggering by utilizing one or more bits corresponding to Reserved fields / bits.

[1114] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1115] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1116] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1117] M. BSRP Type (or Co-SR / BF Subtype): Separately indicates control information regarding the role for which the corresponding BSRP TF was transmitted.

[1118] - That is, among the embodiments for the MAPC Type field and / or Coordination Triggering described above, control information regarding what role the corresponding TF was transmitted for can be indicated through a separate BSRP Type field.

[1119] For example, signaling can be done as follows based on each bit value

[1120] 0: Role of ICF or Invite Frame in the sounding phase

[1121] 1: Role of ICF or Invite Frame in Transmission Phase

[1122] 2: Role of Synchronization or Co-Triggering Frame in Transmission Phase

[1123] 3: Role of a trigger frame for the purpose of sounding failure recovery

[1124] 4: Role of the Intermediate Control frame during the sounding or transmission phase (e.g., the role of the TXOP return frame in Co-TDMA)

[1125] ...

[1126] -> Additionally or alternatively, signaling can be done with 1 bit as follows

[1127] 0: Role of ICF or Invite Frame in Transmission Phase

[1128] 1: Role of the Sync (Co-Triggering) frame in the transmission phase

[1129] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1130] - Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1131] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1132] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1133] N. Co-SR / BF Info Type: Indicates specifically what information the frame includes in the Feedback Information field regarding Co-SR / BF transmission.

[1134] - In other words, a separate Co-SR / BF Info Type field can be used to indicate whether Common or Per-User information for Co-SR / BF operation is included.

[1135] Alternatively, whether to include MAC or PHY information for Co-SR / BF operation can be indicated through a separate Co-SR / BF Info Type field.

[1136] For example, signaling can be done with 1 bit as follows

[1137] 0: Includes Co-SR / BF Common Info

[1138] 1: Includes Co-SR / BF Per-User Info (i.e., Per-STA Info)

[1139] -> Additionally or alternatively, signaling can be done with 1 bit as follows

[1140] 0: Contains Common Info for Co-SR / BF operation and indicates the first Common Info.

[1141] 1: Includes Common Info for Co-SR / BF operation and indicates the second Common Info

[1142] -> Additionally or alternatively, signaling can be done with 2 or more bits as follows

[1143] 0: Contains Common Info for Co-SR / BF operation and indicates the first Common Info.

[1144] 1: Includes Common Info for Co-SR / BF operation and indicates the second Common Info

[1145] 2: Includes Common Info for Co-SR / BF operation and indicates the third Common Info.

[1146] 3: reserved

[1147] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1148] - Additionally or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1149] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1150] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1151] O. (Scheduled) Coordination Duration or Whole TXOP Duration: The period during which SAP collaborates with DAPs to perform Co-SR / BF-based transfers, or the total coordination TXOP (Whole TXOP) period scheduled for MAPC operations.

[1152] - For example, specify the expected / scheduled coordination duration anticipated by SAP

[1153] - For example, the total cooperation TXOP period during which SAP intends to perform MAPC operations

[1154] - For example, define a new field including Coordination Duration or Whole TXOP Duration to indicate

[1155] Specifically, define a new field tentatively named Coordination or Whole TXOP Duration to indicate the information necessary for MAPC operation and the Coordination or Whole TXOP Duration values.

[1156] - For example, utilizing the Allocation Duration field of the User Info field in the MU-RTS TXS Trigger frame

[1157] Specifically, instruct by including the corresponding period value in the Allocation Duration field.

[1158] - The relevant information can be included by utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1159] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1160] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1161] - Additionally or alternatively, the information may be included in the Special User Info field (2007).

[1162] P. Traffic Priority: Priority information of traffic recommended by SAP to DAP, priority information of traffic allowed by SAP to DAP, or priority information of traffic / AC allowed by SAP to DAP

[1163] - For example, TID / AC information regarding traffic allowed to the DAP within the TXOP obtained by SAP

[1164] - For example, Primary AC information for TXOPs obtained by SAP (obtained TXOP)

[1165] Specifically, if traffic for only one of AC_BK, AC_BE, AC_VI, or AC_VO is allowed, the DAP may transmit only traffic corresponding to that AC within the allocated period or cooperation period.

[1166] Specifically, a 2-bit ACI field can be defined to indicate as follows (ACI-to-AC coding)

[1167] AC index (ACI) 0 = AC_BE (best effort)

[1168] AC index (ACI) 1 = AC_BK (background)

[1169] AC index (ACI) 2 = AC_VI (video)

[1170] AC index (ACI) 3 = AC_VO (voice)

[1171] - Additionally or alternatively, SAP may designate a Primary AC for the acquired TXOP, and based on said Primary AC, the CAP (coordinated AP) may transmit traffic corresponding to an AC equal to or greater than said AC within the allocated period or cooperation period.

[1172] Specifically, a new 2-bit field can be defined to indicate as follows (ACI-to-AC coding)

[1173] AC index (ACI) 0 = AC_BE (best effort)

[1174] AC index (ACI) 1 = AC_BK (background)

[1175] AC index (ACI) 2 = AC_VI (video)

[1176] AC index (ACI) 3 = AC_VO (voice)

[1177] - Additionally or alternatively, seven User Priorities (UPs) may be provided as Traffic Categories, and a CAP may transmit only traffic corresponding to an AC that is less than or equal to the UP within the allocated period or cooperation period.

[1178] Specifically, a new 4-bit field can be defined to indicate as follows (UP-to-AC mapping)

[1179] User Priority (UP) 1 = AC_BK

[1180] UP 2 = AC_BK

[1181] UP 0 = AC_BE

[1182] UP 3 = AC_BE

[1183] UP 4 = AC_VI

[1184] UP 5 = AC_VI

[1185] UP 6 = AC_VO

[1186] UP 7 = AC_VO

[1187] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1188] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1189] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1190] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1191] Q. Protection Level: Indicates the protection level for the efficient operation of the currently operating cooperative transmission.

[1192] - For example, in Co-SR / BF operation, this may mean that protection is required until Co-Triggering is performed.

[1193] - For example, utilizing the EHT Reserved (7 bits) or Reserved of the Common Info field

[1194] Specifically, it uses the 2 bits corresponding to EHT / UHR Reserved or Reserved to indicate the protection level of the currently operating cooperative transmission.

[1195] 0: Indicates that it is a cooperative transmission with a protection level of 0 (for example, in Co-TDMA / SR / BF operation, this may mean that separate protection (i.e., long NAV setting) is not required for the transmission / reception of ICF, ICR, and Co-Triggering frames).

[1196] 1: Indicates that it is a cooperative transmission with a protection level of 1 (for example, in Co-TDMA / SR / BF operation, this may mean that separate protection (i.e., NAV setting) is required from the ICF / ICR exchange until the transmission of the Co-Triggering frame).

[1197] 2: Indicates that it is a cooperative transmission with a protection level of 2 (for example, this may mean that separate protection (i.e., long NAV setting) is required when transmitting a Co-Triggering frame to ensure a successful TXOP return in Co-TDMA operation).

[1198] 3: Indicates that it is a cooperative transmission with a protection level of 3 (for example, this may mean that all procedures leading from the transmission and reception of ICF, ICR, and Co-Triggering frames in Co-TDMA / SR / BF operation are protected (i.e., long NAV setting)).

[1199] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1200] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1201] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1202] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1203] R. Recommended Tx Power: Maximum Tx power information recommended by SAP to the DAP triggering the Co-SR transfer.

[1204] - For example, in a scenario where SAP determines the Tx power of a DAP performing Co-SR transmission, SAP can determine the recommended maximum Tx power for the DAP that does not cause interference with its transmission.

[1205] - For example, it can mean the maximum threshold Tx power of the DAP during the Co-SR transmission period.

[1206] In other words, the Recommended Tx Power that SAP conveys to the DAP can refer to an absolute value (e.g., calculated in units of dBm).

[1207] - For example, it can refer to the relative Tx power value allowed to the DAP during the Co-SR transmission period.

[1208] In other words, the Recommended Tx Power that SAP conveys to the DAP can represent a relative value.

[1209] Specifically, the value obtained by subtracting the maximum Tx power recommended to the DAP from SAP's Tx Power (i.e., Tx Power of SAP - Recommended Tx Power of DAP)

[1210] Additionally or alternatively, the value obtained by subtracting SAP's Tx Power from the maximum Tx power recommended to the DAP (i.e., Recommended Tx Power of DAP - Tx Power of SAP)

[1211] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1212] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1213] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1214] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1215] S. Multi-AP Ack Policy Indicator: Indicates the Ack policy during the Co-SR / BF transmission period or the Ack policy that the DAP and the STA connected to the DAP must follow during the coordination duration.

[1216] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[1217] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1218] Specifically, it utilizes the 2 bits corresponding to EHT Reserved or Reserved to instruct the Ack policy for frame exchanges between cooperating APs during the Co-SR Duration.

[1219] For example, it can be defined similarly to the Ack Policy Indicator field within the QoS Control field.

[1220] Bit 0 = 0 & Bit 1 = 0: Indicates a normal ACK or an implicit BAR.

[1221] Bit 0 = 1 & Bit 1 = 0: Indicates No Ack

[1222] Bit 0 = 0 & Bit 1 = 1: Reserved

[1223] Bit 0 = 1 & Bit 1 = 1: Indicates Block Ack

[1224] For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1225] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1226] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1227] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1228] T. DL / UL Indication: Indicates whether a DL transmission or a UL transmission is scheduled to be performed during the Co-SR / BF transmission period.

[1229] U. Tx Power: SAP's maximum Tx power information

[1230] - For example, DAP can determine an appropriate Tx power that does not cause interference based on the maximum Tx power information transmitted by SAP.

[1231] - For example, utilizing the AP Tx Power field of the Common Info field

[1232] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1233] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1234] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1235] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1236] V. In-BSS STA Info: Indicates information about the Target STA for which SAP will perform DL / UL transfer, or information about all connected STAs.

[1237] - For example, the identifiers and capabilities of all STAs connected to SAP

[1238] For example, the AID or MAC addresses of the STAs

[1239] For example, STAs' MIMO and RF capabilities

[1240] - For example, the identifier and capability of the target STA among the STAs connected to SAP that intends to perform DL / UL transmission based on Co-SR

[1241] For example, the AID or MAC address of the Target STA

[1242] For example, the MIMO and RF capabilities of the Target STA

[1243] For example, the PHY version of the Target STA

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

[1245] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1246] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1247] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1248] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1249] W. OBSS STA Info: Indicates information about the OBSS Target STA on which the DAP must perform DL / UL transmission.

[1250] - For example, the identifier and capability of the target OBSS STA among the OBSS STAs connected to the DAP that intends to perform DL / UL transmission based on Co-SR

[1251] For example, the AID or MAC address of the Target OBSS STA

[1252] For example, the MIMO and RF capabilities of the Target OBSS STA

[1253] For example, the PHY version of the Target STA

[1254] - For example, an identifier for an OBSS STA that you want to include in the Multi-AP channel sounding (or OBSS channel sounding) process for MAPC operation

[1255] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1256] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1257] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1258] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1259] X. Common L-SIG Info: The Common L-SIG Info field contains L-SIG information that must be commonly included in the DL PPDU transmitted by each AP during the corresponding cooperation (i.e., Co-SR) transmission period.

[1260] - For example, the Length (B5-B16) information of the L-SIG field within a MU PPDU (e.g., EHT, UHR, etc.) may correspond to the Common L-SIG Info field. This can be considered as a value indicating the duration of the DL PPDU transmitted by each AP.

[1261] - For example, utilizing the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field

[1262] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1263] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1264] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1265] Y. Common U-SIG Info: One or more of the information presented below may be added to and defined within the Common U-SIG Info field, but is not limited to. The Common U-SIG Info field indicates and includes U-SIG-1 and U-SIG-2 information that must be commonly included in the DL PPDU transmitted by each AP during the relevant cooperation-based transmission period.

[1266] - For example, PHY Version Identifier (B0-B2) information in the U-SIG-1 field within MU PPDU (e.g., EHT, UHR, etc.)

[1267] Specifically, it indicates the PHY version of the DL PPDU transmitted by each AP during the Co-SR transmission period.

[1268] Additionally or alternatively, SAP specifies the PHY version of the target STA to which it intends to send the DL PPDU during the Co-SR transmission time.

[1269] - For example, Bandwidth (B3-B5) information of the U-SIG-1 field within MU PPDU (e.g., EHT, UHR, etc.)

[1270] Specifically, it indicates the bandwidth of the DL PPDU transmitted by each AP during the Co-SR transmission period.

[1271] -> Additionally or alternatively, it may be a bandwidth based on the bandwidth of the PPDU containing the ICF transmitted by the SAP.

[1272] -> Additionally or alternatively, when a response frame (e.g., M-BA frame) for an ICF transmitted by the SAP exists, it may be a bandwidth based on the bandwidth of the PPDU containing said M-BA frame.

[1273] - For example, UL / DL (B6) information in the U-SIG-1 field within the MU PPDU (e.g., EHT, UHR, etc.)

[1274] Specifically, it indicates whether DL transmission or UL transmission is scheduled to be performed during the relevant Co-SR transmission period.

[1275] - For example, Punctured Channel Information (B3-B7) of the U-SIG-2 field within MU PPDU (e.g., EHT, UHR, etc.)

[1276] Additionally or alternatively, the PPDU containing the ICF transmitted by the SAP may be punctured based on long-term punctured channel info (e.g., all punctured 20 MHz subchannels specified in the TXVECTOR parameter INACTIVE_SUBCHANNELS).

[1277] -> Additionally or alternatively, it can be punctured based on the dynamic puncturing information of each AP

[1278] -> Additionally or alternatively, it may be a puncturing pattern composed of the union of the two APs' punctured 20 MHz.

[1279] - For example, a UHR-SIG MCS can be defined that performs the same role as the EHT-SIG MCS (B9-B10) of the U-SIG-2 field within a MU PPDU (e.g., EHT, UHR, etc.).

[1280] Specifically, the value of UHR-SIG MCS can indicate the following MCS:

[1281] UHR-SIG MCS = 0 indicates UHR-MCS 0.

[1282] UHR-SIG MCS = 1 indicates UHR-MCS 1.

[1283] UHR-SIG MCS = 2 indicates UHR-MCS 3.

[1284] UHR-SIG MCS = 3 indicates UHR-MCS 15.

[1285] - Additionally or alternatively, it can be set to an MCS value that all STAs serviced by each AP can receive.

[1286] - For example, Number of UHR-SIG Symbols can be defined to serve the same role as Number of EHT-SIG Symbols (B11-B15) in the U-SIG-2 field within a MU PPDU (e.g., EHT, UHR, etc.).

[1287] -> Additionally or alternatively, it can be set to an OFDM symbol value configured by considering all user fields for all STAs connected to each AP.

[1288] - For example, a UHR-SIG TXOP can be defined that performs the same role as the TXOP (B13-B19) of the U-SIG field within a MU PPDU (e.g., EHT, UHR, etc.).

[1289] - For example, Spatial Configuration (B16-B19) information within the User field

[1290] Specifically, it specifies the number of spatial streams for each user in MU-MIMO allocation.

[1291] -> Additionally or alternatively, spatial stream allocation information for all STAs connected to each AP can be specified.

[1292] Additionally or alternatively, the Spatial Configuration field can be defined and utilized as 2 or 3 bits.

[1293] - One or more of the information described above may be included in the Common U-SIG Info field, but is not limited to.

[1294] For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI and HE / EHT-LTF Type / TXS Mode field

[1295] Additionally, or as an alternative, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1296] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1297] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1298] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1299] Z. Co-SR Mode: Indicates the mode for Co-SR transmission.

[1300] - For example, Mode 1 indicates the case where the target STA for Co-SR transmission is EHT + EHT, EHT + UHR, or UHR + EHT.

[1301] -> Under Mode 1 instructions, Co-SR PPDUs transmitted by two APs during the Co-SR transmission period must have a common L-SIG, but the U-SIG contents may differ.

[1302] - For example, Mode 2 indicates the case where the target STA for Co-SR transmission is UHR+UHR.

[1303] -> The instructions of Mode 2 indicate that the Co-SR PPDU transmitted by the two APs during the Co-SR transmission period must have a common L-SIG and a common U-SIG.

[1304] - For example, the final Co-SR Mode information may be included in the BSRP (GI3) TF in the Triggering procedure (i.e., the TF that solicits the Co-SR PPDU).

[1305] That is, in the BSRP (GI3) TF (e.g., Invite frame or ICF) in the Polling procedure, the Sharing AP can indicate and specify the PHY version of the target STA to which it intends to send the Co-SR PPDU.

[1306] A coordinated AP (i.e., shared AP) that receives a BSRP (GI3) TF in the polling procedure can also indicate the PHY version of the target STA to which it intends to send the Co-SR PPDU.

[1307] - For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI And HE / EHT-LTF Type / TXS Mode field

[1308] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1309] - Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1310] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1311] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1312] a. ICF / ICR Required: Indicates whether an additional sequence is required to transmit the ICF to the associated STA before triggering the Co-SR / BF transmission.

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

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

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

[1316] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[1317] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1318] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1319] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1320] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1321] b. BSS Color 1 and BSS Color 2 (6 bits each): Indicates the BSS color of the SAP and the BSS color of the coordinated AP.

[1322] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[1323] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1324] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1325] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1326] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1327] c. Non-OFDMA Common Info: Non-OFDMA information that must be commonly included in the DL PPDU transmitted by each AP during the corresponding cooperative-based transmission period.

[1328] - For example, Spatial Reuse (4 bits) information within the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[1329] - For example, GI+LTF Size (B4-B5) information in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[1330] Specifically, it can be set to a GI+LTF value that enables all STAs serviced by each AP to reliably estimate the channel.

[1331] - For example, Number of UHR-LTF Symbols can be defined to serve the same role as Number of EHT-LTF Symbols (B6-B8) in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission.

[1332] Specifically, it can be set as the dimension of the Giant P matrix determined based on the sum of the spatial streams required for each AP.

[1333] -> Additionally or alternatively, it can be set to the larger of the LTF symbol values ​​required for each AP.

[1334] - For example, Number of Non-OFDMA Users (B17-B19) information in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission

[1335] Specifically, the value of the Number Of Non-OFDMA Users field can represent the sum of the number of SAP-side Co-SR target users and the number of DAP-side Co-SR target users.

[1336] Alternatively, the Number Of Non-OFDMA Users field can be defined as 2 bits, with each bit used to indicate the number of Co-SR target users for SAP and DAP.

[1337] For example, B17 indicates the number of SAP users (e.g., 0 is single user, 1 is 2 users)

[1338] For example, B18 indicates the number of DAP users (e.g., 0 is single user, 1 is 2 users)

[1339] - One or more of the information described above may be included in the BSRP Trigger frame, but is not limited to.

[1340] For example, utilizing fields / bits reserved in the Common Info field according to a new subtype definition using the GI and HE / EHT-LTF Type / TXS Mode field

[1341] Additionally, or as an alternative, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1342] -> Additionally or alternatively, the information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1343] -> Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1344] -> Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1345] d. ICF / ICR Duration: Indicates the period required to send the ICF to the coordinating AP's associated STA and receive the ICR before triggering the Co-SR / BF transmission.

[1346] - For example, if an ICF / ICR exchange procedure is required to switch an EMLSR STA among the associated STAs from listening mode to frame exchange mode, indicate the estimated period required for this.

[1347] - For example, if an ICF / ICR exchange procedure is required to switch a DPS STA among the associated STAs from low capability mode to high capability mode, indicate the estimated period required for this.

[1348] - For example, if an ICF / ICR exchange procedure is required to switch a DUO STA among the associated STAs, indicate the estimated period required for this.

[1349] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[1350] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1351] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1352] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1353] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1354] e. Co-SR / BF Response Padding: Indicates the padding length required for the response frame transmitted by the coordinated AP receiving the Co-SR / BF Invite frame.

[1355] - For example, an 8-bit padding field can be used for definition and padding.

[1356] - Additionally or alternatively, it can be signaled using 3 bits as follows

[1357] 0: 0 μs / 1: 32 μs / 2: 64 μs / 3: 128 μs / 4: 256 μs / 5-7: Reserved

[1358] - According to the new subtype definition utilizing the GI and HE / EHT-LTF Type / TXS Mode fields, the corresponding information can be included by utilizing fields / bits reserved in the Common Info field.

[1359] - Additionally, or alternatively, utilize the EHT Reserved (7 bits) or Reserved fields / bits of the Common Info field.

[1360] - Additionally, or alternatively, the relevant information may be included in a UHR Special User Info field (i.e., Feedback User Info field, AID >= 2008) that can be newly defined for UHR.

[1361] - Additionally, or as an alternative, you can use the Reserved field of the User Info field.

[1362] - Additionally or alternatively, the relevant information may be included in the Special User Info field (2007).

[1363] In addition to the contents presented above, some fields included in the Common field for SU (e.g., EHT, UHR, etc.) transmission and non-OFDMA transmission for existing multiple users (e.g., LDPC Extra Symbol Segment, Pre-FEC Padding Factor, PE Disambiguity, Spatial Reuse, etc.) may be included in the Common Info or Special User Info within the BSRP (UHR) Trigger frame proposed in this specification as contents for Co-SR / BF transmission, or in the (UHR) Special User Info that can be newly defined for UHR.

[1364] The AID12 field within the User Info field of the BSRP (UHR) TF proposed in this specification may be replaced with an ID related to Multi-AP cooperation. Specifically, the ID related to Multi-AP cooperation may include, for example, the BSSID, BSS color, or a newly defined Multi-AP group ID (i.e., an ID for a set of APs constituting Multi-AP cooperation) or an AP ID (i.e., an ID assigned by an AP in a cooperative relationship within the constituent Multi-AP group). Additionally or alternatively, the AID12 field may be composed of a combination of the BSSID and BSS color of the target DAP. Additionally or alternatively, the AID12 field may be composed of part or all of the BSS color of the target DAP. Additionally or alternatively, the AID12 field may be composed of part of the BSSID of the target DAP. Additionally or alternatively, the AID12 field may be composed of a combination of the AP ID and BSS color of the target DAP. Alternatively, when targeting a single DAP, the MAC address of the target DAP may be included in the RA field.

[1365] FIG. 30 is a flowchart illustrating the operation of a transmitting device according to the present embodiment.

[1366] An example of FIG. 30 can be performed on a transmitting STA or a transmitting device (AP and / or non-AP STA).

[1367] Some of the steps (or detailed sub-steps described later) of each example in FIG. 30 may be omitted or changed.

[1368] Through step S3010, the transmitting device (transmitting STA) can obtain information regarding the above-described 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.

[1369] Through step S3020, the transmitting device can construct / generate a PPDU based on acquired control information. The step of constructing / generating the PPDU may include the step of constructing / generating each field of the PPDU. That is, step S3020 includes the step of constructing an EHT-SIG field containing control information regarding a Tone Plan. That is, step S3020 may include the step of constructing a field containing control information (e.g., N bitmap) indicating the size / location of the RU and / or the step of constructing a field containing an identifier (e.g., AID) of the STA receiving the RU.

[1370] Additionally, step S3020 may include the step of generating an STF / LTF sequence transmitted through a specific RU. The STF / LTF sequence may be generated based on a pre-configured STF generation sequence / LTF generation sequence.

[1371] Additionally, step S3020 may include a step of generating a data field (i.e., MPDU) transmitted through a specific RU.

[1372] The transmitting device can transmit the PPDU configured through step S3020 to the receiving device based on step S3030.

[1373] While performing step S3030, the transmitting device may perform at least one of the following operations: CSD, Spatial Mapping, IDFT / IFFT operation, GI insertion, etc.

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

[1375] FIG. 31 is a flowchart illustrating the operation of a receiving device according to the present embodiment.

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

[1377] An example of FIG. 31 can be performed at a receiving STA or a receiving device (AP and / or non-AP STA).

[1378] Some of the steps (or detailed sub-steps described later) of each example in Fig. 31 may be omitted.

[1379] A receiving device (receiving STA) can receive all or part of the PPDU through step S3110. The received signal may be in the form of FIG. 5.

[1380] The sub-step of step S3110 can be determined based on step S3030 of FIG. 30. That is, step S3110 can perform an operation to restore the results of the CSD, Spatial Mapping, IDFT / IFFT operation, and GI insert operation applied in step S3030.

[1381] In step S3120, the receiving device can perform decoding of 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.

[1382] 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 contained in the L-SIG and EHT-SIG fields. Information regarding various Tone Plans (i.e., RU) described in this specification may be included in the EHT-SIG, and the receiving STA can obtain information regarding the Tone Plan (i.e., RU) through the EHT-SIG.

[1383] In step S3130, the receiving device can decode the remainder of the PPDU based on information regarding the Tone Plan (i.e., RU) obtained through step S3120. For example, the receiving STA can decode the STF / LTF fields of the PPDU based on information regarding the one Plan (i.e., RU). Additionally, the receiving STA can decode the data fields of the PPDU based on information regarding the Tone Plan (i.e., RU) and obtain the MPDU contained in the data fields.

[1384] Additionally, the receiving device can perform a processing operation to transmit the decoded data through step S3130 to an upper layer (e.g., MAC layer). Furthermore, if the generation of a signal is instructed from the upper layer to the PHY layer in response to the data transmitted to the upper layer, a subsequent operation can be performed.

[1385] Hereinafter, the above-described embodiment will be explained with reference to FIGS. 1 to 31.

[1386] FIG. 32 is a flowchart illustrating the procedure for receiving a cooperative trigger frame to perform Co-SR / Co-BF transmission according to the present embodiment.

[1387] An example of FIG. 32 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[1388] An example of FIG. 32 can be performed at a second AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be set as a coordinating AP or a coordinated AP through the MAPC negotiation.

[1389] The present embodiment proposes a sequence for performing frame exchange to perform Co-SR / Co-BF transmission. Specifically, the present embodiment proposes a method for transmitting and receiving by including information necessary for said Co-SR / Co-BF transmission in a cooperative invitation frame, a cooperative response frame, and a cooperative trigger frame.

[1390] In step S3210, the second AP (access point) receives a Coordination Invite frame from the first AP.

[1391] In step S3220, the second AP transmits a cooperation response frame to the first AP.

[1392] In step S3230, the second AP receives a cooperation trigger frame from the first AP.

[1393] The first AP is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP. The second AP is a coordinated AP that participates in the MAPC transmission.

[1394] Specifically, the first AP may initiate the MAPC transmission (or Co-SR / Co-BF transmission) with the second AP by transmitting the cooperation invitation frame to the second AP. The cooperation invitation frame may be a BSRP (Buffer Status Report Poll) NTB (Non-Trigger Based) trigger frame. The TA (Transmitter Address) field of the cooperation invitation frame may be set to the MAC address of the first AP. The RA (Receiver Address) field of the cooperation invitation frame may be set to the MAC address of the second AP. The cooperation invitation frame may solicit the cooperation response frame.

[1395] The second AP may transmit the cooperation response frame to the first AP after aSIFSTime at the end of the PPDU containing the cooperation invitation frame. The cooperation response frame may be a Multi-STA BlockAck frame. The TA field of the cooperation response frame may be set to the MAC address of the second AP. The RA field of the cooperation response frame may be set to the MAC address of the first AP.

[1396] The first or second AP may include an ICF-ICR (Initial Control Response) exchange within the frame exchange sequence for the MAPC transmission when one of the connected STAs of the AP scheduled for the MAPC transmission in the current TXOP is operating in a mode where a frame exchange must precede with the transmission of an ICF (Initial Control Frame). This may apply to a non-AP STA with Dynamic Power Save (DPS) enabled and a non-AP STA belonging to an EMLSR non-AP MLD that is immediately connected on the EMLSR (Enhanced Multi-Link Single Radio) link.

[1397] The above-mentioned cooperation trigger frame may include information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. The information regarding the PHY versions may include information regarding whether the first and second PPDUs are Ultra-High Reliability (UHR) or Extremely High Throughput (EHT), etc.

[1398] The first AP may transmit the cooperation trigger frame to the second AP after aSIFSTime at the end of a PPDU containing the cooperation response frame that accepts the cooperation invitation frame. Before the first and second APs transmit two PPDUs (data PPDUs) simultaneously, the first AP may transmit the cooperation trigger frame to the second AP.

[1399] Prior to the frame exchange sequence for the above MAPC transmission, a negotiation procedure for MAPC consensus may be performed.

[1400] Specifically, the first AP may transmit a negotiation request frame to the second AP. The first AP may receive a negotiation response frame from the second AP. The first AP may form an MAPC agreement with the second AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming). (Alternatively, the second AP may receive a negotiation request frame from the first AP. The second AP may receive a negotiation response frame from the first AP. The second AP may form an MAPC agreement with the first AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming).)

[1401] At this time, the first AP may be a MAPC requesting AP that initiates negotiations for the MAPC agreement. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP.

[1402] Based on the formation of a MAPC agreement for the above Co-SR, the first and second APs can perform Co-SR transmission.

[1403] Specifically, the first AP may transmit the first PPDU to the first non-AP STA (station) after the cooperative trigger frame is transmitted. The second AP may transmit the second PPDU to the second non-AP STA after the cooperative trigger frame is received. The first and second PPDUs may be transmitted concurrently to the first and second non-AP STAs, respectively, using transmit power control. The number of APs participating in the Co-SR transmission must be two. In this case, the first non-AP STA may be a non-AP STA associated with the first AP. The second non-AP STA may be a non-AP STA associated with the second AP.

[1404] Based on the fact that the first and second APs perform Co-SR transmission, the cooperative invitation frame, the cooperative response frame, and the cooperative trigger frame may include the following information.

[1405] Specifically, the cooperative invitation frame contains information regarding the minimum number of data OFDM (Orthogonal Frequency Division Multiplexing) symbols of the Co-SR transmission, information regarding the maximum number of data OFDM symbols of the Co-SR transmission, information regarding the intended PHY version of the first PPDU in the Co-SR transmission, information regarding the size of the GI (Guard Interval) and LTF (Long Training Field) of the Co-SR transmission, information regarding the number of LTF symbols of the Co-SR transmission, information regarding the maximum transmission power of the first AP, control information regarding the cooperative trigger frame (or control information regarding what role the BSRP trigger frame was transmitted for), information regarding the Ack policy during the Co-SR transmission period, and information regarding whether an ICF (Initial Control Frame) and ICR (Initial Control Response) frame exchange is included between the first AP and the first non-AP STA prior to the Co-SR transmission, or the ICF and ICR between the first AP and the first non-AP STA. It may include at least one of the information regarding the interval of frame exchange.

[1406] Based on the second AP accepting the cooperative invitation frame, the cooperative response frame may include at least one of the following: information on the suggested number of data OFDM symbols of the Co-SR transmission; information on the intended PHY version of the second PPDU in the Co-SR transmission; information on the maximum or minimum transmission power preferred by the second AP; information on whether an ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-SR transmission; or information on the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA.

[1407] Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame may include information regarding the reason for the rejection.

[1408] The above cooperation trigger frame may further include at least one of information regarding the segments of the first PPDU and the second PPDU that are identical to each other, information regarding the transmission power limit of the second AP, or information regarding the transmission power of the first AP. In this case, the value of the transmission power limit of the second AP must not be lower than the value indicated by the second AP in the negotiation request frame or the negotiation response frame.

[1409] The above cooperation trigger frame may further include one user information field for the second AP. The AID12 field of the one user information field may be set to the AP ID (Identifier) ​​of the second AP assigned by the first AP while the MAPC consensus is being formed.

[1410] Based on the formation of a MAPC consensus for the above Co-BF, the first and second APs can perform Co-BF transmission. Likewise, the first AP can transmit the first PPDU to the first non-AP STA after the cooperative trigger frame has been transmitted. The second AP can transmit the second PPDU to the second non-AP STA after the cooperative trigger frame has been received. The first and second PPDUs can be transmitted simultaneously to the first and second non-AP STAs, respectively, through multiple transmit chains.

[1411] Based on the fact that the first and second APs perform Co-BF transmission, the cooperative invitation frame, the cooperative response frame, and the cooperative trigger frame may include the following information.

[1412] The above cooperative invitation frame contains information regarding the minimum number of data OFDM symbols of the Co-BF transmission, information regarding the maximum number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding the bandwidth of the Co-BF transmission, information regarding the puncturing pattern of the Co-BF transmission, information regarding the GI and LTF sizes of the Co-BF transmission, control information regarding the cooperative trigger frame (or control information regarding what role the BSRP trigger frame was transmitted for), information regarding the Ack policy during the Co-BF transmission period, information regarding the maximum total number of spatial streams allowed for the second AP of the Co-BF transmission, information regarding the number of the first non-AP STA, information regarding the STA ID of each of the first non-AP STAs, information regarding the number of spatial streams for each of the first non-AP STAs, and information regarding the exchange of ICF and ICR frames between the first AP and the first non-AP STA prior to the Co-BF transmission It may include at least one of information regarding whether it is included or information regarding the interval of the ICF and ICR frame exchange between the first AP and the first non-AP STA.

[1413] Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame contains information regarding the proposed number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding whether additional LTF to be used for the Co-BF transmission at the second AP is allowed, information regarding the number of the second non-AP STA, information regarding the STA ID of each of the second non-AP STAs, information regarding the Modulation and Coding Scheme (MCS) for each of the second non-AP STAs, information regarding the number of spatial streams for each of the second non-AP STAs, information regarding the 2xLow Density Parity Check (2xLDPC) to be used for each of the second non-AP STAs, information regarding whether ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-BF transmission, or in the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA It may include at least one of the information about

[1414] The proposed number of data OFDM symbols in the above Co-BF transmission must not be less than the minimum number of data OFDM symbols indicated by the first AP in the above cooperative invitation frame.

[1415] Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame may include information regarding the reason for the rejection.

[1416] The above cooperative trigger frame is used to ensure time and frequency synchronization between the first and second PPDUs and may further include information necessary to configure a common preamble for the first and second PPDUs.

[1417] The information required to construct a common preamble for the first and second PPDUs includes: information regarding the value set in the Length field within the L-SIG (Legacy-Signal) field of the first and second PPDUs; information regarding the PHY version of the Co-BF transmission; information regarding the bandwidth of the Co-BF transmission; information regarding the puncturing pattern of the Co-BF transmission; information regarding the BSS (Basic Service Set) color of the first AP; information regarding the BSS color of the second AP; information regarding the TXOP interval set in the TXOP field within the U-SIG (Universal-Signal) of the first and second PPDUs; information regarding the number of UHR-SIG (Ultra High Reliability-Signal) symbols of the first and second PPDUs; information regarding the GI and LTF sizes of the Co-BF transmission; information regarding the number of UHR-LTF symbols of the first and second PPDUs; and the first and second non-AP STAs It may include at least one of information regarding the number, information regarding the STA ID of each of the first and second non-AP STAs, information regarding the BSS to which the first and second non-AP STAs belong, information regarding the MCS of each of the first and second non-AP STAs, information regarding the spatial configuration of each of the first and second non-AP STAs, or information regarding whether 2xLDPC will be used for each of the first and second non-AP STAs.

[1418] That is, the present embodiment proposes a method for configuring a frame exchange procedure by including information necessary for Co-SR / Co-BF transmission in the cooperative invitation frame, cooperative response frame, and cooperative trigger frame used for frame exchange for the MAPC transmission. Thus, i) precise adjustment of transmission timing and beam patterns between multiple APs is possible (since each cooperating AP receiving a cooperative trigger frame can recognize in advance PHY layer parameters such as the transmission timing of other APs' DL PPDU, MCS (Modulation and Coding Scheme), bandwidth, and transmit power, interference minimization and precise beam alignment can be performed during Co-BF), ii) maximization of Co-SR efficiency (since each AP can dynamically adjust its own transmit power based on the transmit power and spatial reuse parameters of adjacent APs, spatial reuse efficiency within the same channel is improved, and the frequency utilization efficiency of the entire system increases), iii) reduction of collisions and interference between frames (due to the sharing of PHY information through cooperative trigger frames, each AP can perform transmission timing and power control to minimize mutual interference, thereby effectively mitigating collisions or interference between PPDUs that may occur during simultaneous transmission by multiple APs), and iv) improvement of reliability and synchronization of the MAPC procedure (the PHY information included in the trigger frame [regarding] the transmission sequence and transmission conditions between cooperating APs Since it is clearly defined, explicit and highly reliable synchronization is possible compared to existing implicit synchronization methods.), v) improvement in overall system throughput (due to interference reduction and improved space reuse efficiency, the DL transmission throughput of the entire network is improved, and stable high-speed transmission becomes possible, especially in high-density AP deployment environments).

[1419] The above negotiation request frame may include MAPC elements. The above MAPC elements may include a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[1420] The above MAPC scheme information field may include a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field.

[1421] Based on the value of the above Subelement ID field, the above MAPC technique information field can be defined as a Per-Scheme Profile subelement.

[1422] The above MAPC scheme control field may include a MAPC scheme type (Scheme Type) field. The above MAPC scheme type field may indicate a value that identifies the MAPC scheme.

[1423] The above MAPC technique request set field may include a MAPC Operation Type field. Based on the value of the MAPC Operation Type field, an operation to form the MAPC consensus, update the MAPC consensus, or release the MAPC consensus may be indicated. For example, the MAPC consensus may be formed based on the value of the MAPC Operation Type field being 0. The MAPC consensus may be updated based on the value of the MAPC Operation Type field being 1. The MAPC consensus may be released based on the value of the MAPC Operation Type field being 2.

[1424] The profile sub-elements for each of the above MAPC techniques may include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile.

[1425] The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile can be identified based on the value of the MAPC technique type field. For example, based on the value of the MAPC technique type field being 0, the Co-BF profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 1, the Co-SR profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 2, the Co-TDMA profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 3, the Co-RTWT profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 4, the Co-SR profile may be included in the profile sub-element by MAPC technique.

[1426] The above MAPC technique request set field can be defined for each of the Co-BF profile, the Co-SR profile, the Co-TDMA profile, the Co-RTWT profile, and the Co-CR profile.

[1427] Likewise, the above negotiation response frame may also include MAPC elements. The above MAPC elements may include a MAPC action type field. In the above negotiation response frame, the request for the negotiation request frame can be accepted, rejected, or alternated based on the value of the MAPC action type field.

[1428] FIG. 33 is a flowchart illustrating the procedure for transmitting and configuring a cooperative trigger frame to perform Co-SR / Co-BF transmission according to the present embodiment.

[1429] An example of FIG. 33 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 upon the 802.11be system and can satisfy backward compatibility with the 802.11be system.

[1430] An example of FIG. 33 can be performed at a first AP. The first AP may be a MAPC requesting AP that initiates MAPC negotiation with the second AP regarding at least one MAPC technique. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP. Additionally, the first and second APs may be established as a coordinating AP or a coordinated AP through the MAPC negotiation.

[1431] The present embodiment proposes a sequence for performing frame exchange to perform Co-SR / Co-BF transmission. Specifically, the present embodiment proposes a method for transmitting and receiving by including information necessary for said Co-SR / Co-BF transmission in a cooperative invitation frame, a cooperative response frame, and a cooperative trigger frame.

[1432] In step S3310, the first AP (access point) sends a Coordination Invite frame to the second AP.

[1433] In step S3320, the first AP receives a cooperation response frame from the second AP.

[1434] In step S3330, the first AP transmits a cooperation trigger frame to the second AP.

[1435] The first AP is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP. The second AP is a coordinated AP that participates in the MAPC transmission.

[1436] Specifically, the first AP may initiate the MAPC transmission (or Co-SR / Co-BF transmission) with the second AP by transmitting the cooperation invitation frame to the second AP. The cooperation invitation frame may be a BSRP (Buffer Status Report Poll) NTB (Non-Trigger Based) trigger frame. The TA (Transmitter Address) field of the cooperation invitation frame may be set to the MAC address of the first AP. The RA (Receiver Address) field of the cooperation invitation frame may be set to the MAC address of the second AP. The cooperation invitation frame may solicit the cooperation response frame.

[1437] The second AP may transmit the cooperation response frame to the first AP after aSIFSTime at the end of the PPDU containing the cooperation invitation frame. The cooperation response frame may be a Multi-STA BlockAck frame. The TA field of the cooperation response frame may be set to the MAC address of the second AP. The RA field of the cooperation response frame may be set to the MAC address of the first AP.

[1438] The first or second AP may include an ICF-ICR (Initial Control Response) exchange within the frame exchange sequence for the MAPC transmission when one of the connected STAs of the AP scheduled for the MAPC transmission in the current TXOP is operating in a mode where a frame exchange must precede with the transmission of an ICF (Initial Control Frame). This may apply to a non-AP STA with Dynamic Power Save (DPS) enabled and a non-AP STA belonging to an EMLSR non-AP MLD that is immediately connected on the EMLSR (Enhanced Multi-Link Single Radio) link.

[1439] The above-mentioned cooperation trigger frame may include information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. The information regarding the PHY versions may include information regarding whether the first and second PPDUs are Ultra-High Reliability (UHR) or Extremely High Throughput (EHT), etc.

[1440] The first AP may transmit the cooperation trigger frame to the second AP after aSIFSTime at the end of a PPDU containing the cooperation response frame that accepts the cooperation invitation frame. Before the first and second APs transmit two PPDUs (data PPDUs) simultaneously, the first AP may transmit the cooperation trigger frame to the second AP.

[1441] Prior to the frame exchange sequence for the above MAPC transmission, a negotiation procedure for MAPC consensus may be performed.

[1442] Specifically, the first AP may transmit a negotiation request frame to the second AP. The first AP may receive a negotiation response frame from the second AP. The first AP may form an MAPC agreement with the second AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming). (Alternatively, the second AP may receive a negotiation request frame from the first AP. The second AP may receive a negotiation response frame from the first AP. The second AP may form an MAPC agreement with the first AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming).)

[1443] At this time, the first AP may be a MAPC requesting AP that initiates negotiations for the MAPC agreement. The second AP may be a MAPC responding AP that responds to the MAPC requesting AP.

[1444] Based on the formation of a MAPC agreement for the above Co-SR, the first and second APs can perform Co-SR transmission.

[1445] Specifically, the first AP may transmit the first PPDU to the first non-AP STA (station) after the cooperative trigger frame is transmitted. The second AP may transmit the second PPDU to the second non-AP STA after the cooperative trigger frame is received. The first and second PPDUs may be transmitted concurrently to the first and second non-AP STAs, respectively, using transmit power control. The number of APs participating in the Co-SR transmission must be two. In this case, the first non-AP STA may be a non-AP STA associated with the first AP. The second non-AP STA may be a non-AP STA associated with the second AP.

[1446] Based on the fact that the first and second APs perform Co-SR transmission, the cooperative invitation frame, the cooperative response frame, and the cooperative trigger frame may include the following information.

[1447] Specifically, the cooperative invitation frame contains information regarding the minimum number of data OFDM (Orthogonal Frequency Division Multiplexing) symbols of the Co-SR transmission, information regarding the maximum number of data OFDM symbols of the Co-SR transmission, information regarding the intended PHY version of the first PPDU in the Co-SR transmission, information regarding the size of the GI (Guard Interval) and LTF (Long Training Field) of the Co-SR transmission, information regarding the number of LTF symbols of the Co-SR transmission, information regarding the maximum transmission power of the first AP, control information regarding the cooperative trigger frame (or control information regarding what role the BSRP trigger frame was transmitted for), information regarding the Ack policy during the Co-SR transmission period, and information regarding whether an ICF (Initial Control Frame) and ICR (Initial Control Response) frame exchange is included between the first AP and the first non-AP STA prior to the Co-SR transmission, or the ICF and ICR between the first AP and the first non-AP STA. It may include at least one of the information regarding the interval of frame exchange.

[1448] Based on the second AP accepting the cooperative invitation frame, the cooperative response frame may include at least one of the following: information on the suggested number of data OFDM symbols of the Co-SR transmission; information on the intended PHY version of the second PPDU in the Co-SR transmission; information on the maximum or minimum transmission power preferred by the second AP; information on whether an ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-SR transmission; or information on the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA.

[1449] Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame may include information regarding the reason for the rejection.

[1450] The above cooperation trigger frame may further include at least one of information regarding the segments of the first PPDU and the second PPDU that are identical to each other, information regarding the transmission power limit of the second AP, or information regarding the transmission power of the first AP. In this case, the value of the transmission power limit of the second AP must not be lower than the value indicated by the second AP in the negotiation request frame or the negotiation response frame.

[1451] The above cooperation trigger frame may further include one user information field for the second AP. The AID12 field of the one user information field may be set to the AP ID (Identifier) ​​of the second AP assigned by the first AP while the MAPC consensus is being formed.

[1452] Based on the formation of a MAPC consensus for the above Co-BF, the first and second APs can perform Co-BF transmission. Likewise, the first AP can transmit the first PPDU to the first non-AP STA after the cooperative trigger frame has been transmitted. The second AP can transmit the second PPDU to the second non-AP STA after the cooperative trigger frame has been received. The first and second PPDUs can be transmitted simultaneously to the first and second non-AP STAs, respectively, through multiple transmit chains.

[1453] Based on the fact that the first and second APs perform Co-BF transmission, the cooperative invitation frame, the cooperative response frame, and the cooperative trigger frame may include the following information.

[1454] The above cooperative invitation frame contains information regarding the minimum number of data OFDM symbols of the Co-BF transmission, information regarding the maximum number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding the bandwidth of the Co-BF transmission, information regarding the puncturing pattern of the Co-BF transmission, information regarding the GI and LTF sizes of the Co-BF transmission, control information regarding the cooperative trigger frame (or control information regarding what role the BSRP trigger frame was transmitted for), information regarding the Ack policy during the Co-BF transmission period, information regarding the maximum total number of spatial streams allowed for the second AP of the Co-BF transmission, information regarding the number of the first non-AP STA, information regarding the STA ID of each of the first non-AP STAs, information regarding the number of spatial streams for each of the first non-AP STAs, and information regarding the exchange of ICF and ICR frames between the first AP and the first non-AP STA prior to the Co-BF transmission It may include at least one of information regarding whether it is included or information regarding the interval of the ICF and ICR frame exchange between the first AP and the first non-AP STA.

[1455] Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame contains information regarding the proposed number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding whether additional LTF to be used for the Co-BF transmission at the second AP is allowed, information regarding the number of the second non-AP STA, information regarding the STA ID of each of the second non-AP STAs, information regarding the Modulation and Coding Scheme (MCS) for each of the second non-AP STAs, information regarding the number of spatial streams for each of the second non-AP STAs, information regarding the 2xLow Density Parity Check (2xLDPC) to be used for each of the second non-AP STAs, information regarding whether ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-BF transmission, or in the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA It may include at least one of the information about

[1456] The proposed number of data OFDM symbols in the above Co-BF transmission must not be less than the minimum number of data OFDM symbols indicated by the first AP in the above cooperative invitation frame.

[1457] Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame may include information regarding the reason for the rejection.

[1458] The above cooperative trigger frame is used to ensure time and frequency synchronization between the first and second PPDUs and may further include information necessary to configure a common preamble for the first and second PPDUs.

[1459] The information required to construct a common preamble for the first and second PPDUs includes: information regarding the value set in the Length field within the L-SIG (Legacy-Signal) field of the first and second PPDUs; information regarding the PHY version of the Co-BF transmission; information regarding the bandwidth of the Co-BF transmission; information regarding the puncturing pattern of the Co-BF transmission; information regarding the BSS (Basic Service Set) color of the first AP; information regarding the BSS color of the second AP; information regarding the TXOP interval set in the TXOP field within the U-SIG (Universal-Signal) of the first and second PPDUs; information regarding the number of UHR-SIG (Ultra High Reliability-Signal) symbols of the first and second PPDUs; information regarding the GI and LTF sizes of the Co-BF transmission; information regarding the number of UHR-LTF symbols of the first and second PPDUs; and the first and second non-AP STAs It may include at least one of information regarding the number, information regarding the STA ID of each of the first and second non-AP STAs, information regarding the BSS to which the first and second non-AP STAs belong, information regarding the MCS of each of the first and second non-AP STAs, information regarding the spatial configuration of each of the first and second non-AP STAs, or information regarding whether 2xLDPC will be used for each of the first and second non-AP STAs.

[1460] That is, the present embodiment proposes a method for configuring a frame exchange procedure by including information necessary for Co-SR / Co-BF transmission in the cooperative invitation frame, cooperative response frame, and cooperative trigger frame used for frame exchange for the MAPC transmission. Thus, i) precise adjustment of transmission timing and beam patterns between multiple APs is possible (since each cooperating AP receiving a cooperative trigger frame can recognize in advance PHY layer parameters such as the transmission timing of other APs' DL PPDU, MCS (Modulation and Coding Scheme), bandwidth, and transmit power, interference minimization and precise beam alignment can be performed during Co-BF), ii) maximization of Co-SR efficiency (since each AP can dynamically adjust its own transmit power based on the transmit power and spatial reuse parameters of adjacent APs, spatial reuse efficiency within the same channel is improved, and the frequency utilization efficiency of the entire system increases), iii) reduction of collisions and interference between frames (due to the sharing of PHY information through cooperative trigger frames, each AP can perform transmission timing and power control to minimize mutual interference, thereby effectively mitigating collisions or interference between PPDUs that may occur during simultaneous transmission by multiple APs), and iv) improvement of reliability and synchronization of the MAPC procedure (the PHY information included in the trigger frame [regarding] the transmission sequence and transmission conditions between cooperating APs Since it is clearly defined, explicit and highly reliable synchronization is possible compared to existing implicit synchronization methods.), v) improvement in overall system throughput (due to interference reduction and improved space reuse efficiency, the DL transmission throughput of the entire network is improved, and stable high-speed transmission becomes possible, especially in high-density AP deployment environments).

[1461] The above negotiation request frame may include MAPC elements. The above MAPC elements may include a MAPC Control field, a MAPC Common Info field, and a MAPC Schemes Info field.

[1462] The above MAPC scheme information field may include a Subelement ID field, a MAPC scheme control field, and a MAPC scheme request set field.

[1463] Based on the value of the above Subelement ID field, the above MAPC technique information field can be defined as a Per-Scheme Profile subelement.

[1464] The above MAPC scheme control field may include a MAPC scheme type (Scheme Type) field. The above MAPC scheme type field may indicate a value that identifies the MAPC scheme.

[1465] The above MAPC technique request set field may include a MAPC Operation Type field. Based on the value of the MAPC Operation Type field, an operation to form the MAPC consensus, update the MAPC consensus, or release the MAPC consensus may be indicated. For example, the MAPC consensus may be formed based on the value of the MAPC Operation Type field being 0. The MAPC consensus may be updated based on the value of the MAPC Operation Type field being 1. The MAPC consensus may be released based on the value of the MAPC Operation Type field being 2.

[1466] The profile sub-elements for each of the above MAPC techniques may include at least one Co-BF (Coordinated beamforming) profile, Co-SR (Coordinated spatial reuse) profile, Co-TDMA (Coordinated time division multiple access) profile, Co-RTWT (Coordinated restricted target wake time) profile, and Co-CR (Coordinated channel recommendation) profile.

[1467] The above Co-BF profile, the above Co-SR profile, the above Co-TDMA profile, the above Co-RTWT profile, and the above Co-CR profile can be identified based on the value of the MAPC technique type field. For example, based on the value of the MAPC technique type field being 0, the Co-BF profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 1, the Co-SR profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 2, the Co-TDMA profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 3, the Co-RTWT profile may be included in the profile sub-element by MAPC technique. Based on the value of the MAPC technique type field being 4, the Co-SR profile may be included in the profile sub-element by MAPC technique.

[1468] The above MAPC technique request set field can be defined for each of the Co-BF profile, the Co-SR profile, the Co-TDMA profile, the Co-RTWT profile, and the Co-CR profile.

[1469] Likewise, the above negotiation response frame may also include MAPC elements. The above MAPC elements may include a MAPC action type field. In the above negotiation response frame, the request for the negotiation request frame can be accepted, rejected, or alternated based on the value of the MAPC action type field.

[1470] <Device Configuration>

[1471] The technical features o...

Claims

1. In a wireless LAN system, A step in which the first AP (access point) transmits a cooperation invitation frame to the second AP; The first AP receives a cooperation response frame from the second AP; and The above first AP includes the step of transmitting a cooperation trigger frame to the above second AP, wherein The first AP above is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. method.

2. In Paragraph 1, The step of the first AP transmitting a negotiation request frame to the second AP; The first AP receives a negotiation response frame from the second AP; and The above first AP further includes the step of forming a MAPC agreement with the above second AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming), wherein The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP. method.

3. In Paragraph 2, Based on the MAPC consensus formed regarding the above Co-SR, The step of the first AP transmitting the first PPDU to the first non-AP STA (station) after the cooperation trigger frame is transmitted; and The above second AP further includes the step of transmitting the second PPDU to the second non-AP STA after the cooperation trigger frame is received, The first and second PPDUs are transmitted concurrently to the first and second non-AP STAs, respectively, using transmit power control, and The above first non-AP STA is a non-AP STA associated with the above first AP, and The above second non-AP STA is a non-AP STA connected to the above second AP. method.

4. In Paragraph 3, Based on the above first and second APs performing Co-SR transmission, The above cooperative invitation frame includes at least one of the following: information regarding the minimum number of data OFDM (Orthogonal frequency division multiplexing) symbols of the Co-SR transmission; information regarding the maximum number of data OFDM symbols of the Co-SR transmission; information regarding the intended PHY version of the first PPDU in the Co-SR transmission; information regarding the size of the GI (Guard Interval) and LTF (Long Training Field) of the Co-SR transmission; information regarding the number of LTF symbols of the Co-SR transmission; information regarding the maximum transmission power of the first AP; control information for the cooperative trigger frame; information regarding the Ack policy during the Co-SR transmission period; information regarding whether an ICF (Initial Control Frame) and ICR (Initial Control Response) frame exchange is included between the first AP and the first non-AP STA before the Co-SR transmission; or information regarding the interval of the ICF and ICR frame exchange between the first AP and the first non-AP STA. Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame includes at least one of the following: information regarding the suggested number of data OFDM symbols in the Co-SR transmission; information regarding the intended PHY version of the second PPDU in the Co-SR transmission; information regarding the maximum or minimum transmission power preferred by the second AP; information regarding whether an ICF and ICR frame exchange is included between the second AP and the second non-AP STA prior to the Co-SR transmission; or information regarding the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA. Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame includes information regarding the reason for rejection. method.

5. In Paragraph 4, The above cooperative trigger frame further includes at least one of information regarding the same segment of the first PPDU and the segment of the second PPDU, information regarding the transmission power limit of the second AP, or information regarding the transmission power of the first AP. The value of the transmission power limit of the second AP must not be lower than the value indicated by the second AP in the negotiation request frame or the negotiation response frame. method.

6. In Paragraph 4, The above cooperation trigger frame further includes one user information field for the second AP, and The AID12 field of the above-mentioned single user information field is set to the AP ID (Identifier) ​​of the second AP assigned by the first AP while the MAPC consensus is being formed. method.

7. In Paragraph 3, Based on the MAPC agreement formed for the above Co-BF, the first and second PPDUs are simultaneously transmitted to the first and second non-AP STAs, respectively, through multiple transmit chains, and Based on the above first and second APs performing Co-BF transmission, The above cooperative invitation frame contains information regarding the minimum number of data OFDM symbols of the Co-BF transmission, information regarding the maximum number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding the bandwidth of the Co-BF transmission, information regarding the puncturing pattern of the Co-BF transmission, information regarding the GI and LTF sizes of the Co-BF transmission, control information for the cooperative trigger frame, information regarding the Ack policy during the Co-BF transmission period, information regarding the maximum total number of spatial streams allowed for the second AP of the Co-BF transmission, information regarding the number of the first non-AP STA, information regarding the STA ID of each of the first non-AP STAs, information regarding the number of spatial streams for each of the first non-AP STAs, information regarding whether ICF and ICR frame exchanges are included between the first AP and the first non-AP STA prior to the Co-BF transmission, or information regarding the first AP and the first non-AP It includes at least one of the information regarding the interval of the ICF and ICR frame exchange between the STAs, and Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame contains information regarding the proposed number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding whether additional LTF to be used for the Co-BF transmission at the second AP is allowed, information regarding the number of the second non-AP STA, information regarding the STA ID of each of the second non-AP STAs, information regarding the Modulation and Coding Scheme (MCS) for each of the second non-AP STAs, information regarding the number of spatial streams for each of the second non-AP STAs, information regarding the 2xLow Density Parity Check (2xLDPC) to be used for each of the second non-AP STAs, information regarding whether ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-BF transmission, or in the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA Includes at least one of the information regarding, The proposed number of data OFDM symbols in the above Co-BF transmission must not be less than the minimum number of data OFDM symbols indicated by the first AP in the above cooperative invitation frame, and Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame includes information regarding the reason for rejection. method.

8. In Paragraph 7, The above cooperative trigger frame is used to ensure time and frequency synchronization between the first and second PPDUs and further includes information necessary to construct a common preamble for the first and second PPDUs, and The information required to construct a common preamble for the first and second PPDUs includes: information regarding the value set in the Length field within the L-SIG (Legacy-Signal) field of the first and second PPDUs; information regarding the PHY version of the Co-BF transmission; information regarding the bandwidth of the Co-BF transmission; information regarding the puncturing pattern of the Co-BF transmission; information regarding the BSS (Basic Service Set) color of the first AP; information regarding the BSS color of the second AP; information regarding the TXOP interval set in the TXOP field within the U-SIG (Universal-Signal) of the first and second PPDUs; information regarding the number of UHR-SIG (Ultra High Reliability-Signal) symbols of the first and second PPDUs; information regarding the GI and LTF sizes of the Co-BF transmission; information regarding the number of UHR-LTF symbols of the first and second PPDUs; and the first and second non-AP STAs at least one of information regarding the number, information regarding the STA ID of each of the first and second non-AP STAs, information regarding the BSS to which the first and second non-AP STAs belong, information regarding the MCS of each of the first and second non-AP STAs, information regarding the spatial configuration of each of the first and second non-AP STAs, or information regarding whether 2xLDPC will be used for each of the first and second non-AP STAs. method.

9. In a wireless LAN system, the first AP (access point) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Send a cooperation invitation frame to the 2nd AP; Receive a cooperation response frame from the above-mentioned second AP; and Transmit a cooperation trigger frame to the above-mentioned second AP, The first AP above is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. 1st AP.

10. In wireless LAN systems, A step in which the second AP (access point) receives a cooperation invitation frame from the first AP; The step of the second AP transmitting a cooperation response frame to the first AP; and The above second AP includes the step of receiving a cooperation trigger frame from the first AP, wherein The first AP above is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. method.

11. In Paragraph 10, The step of the second AP receiving a negotiation request frame from the first AP; The second AP receives a negotiation response frame from the first AP; and The above second AP further includes the step of forming a MAPC agreement with the above first AP regarding Co-SR (Coordinated spatial reuse) or Co-BF (Coordinated beamforming), wherein The above-mentioned first AP is a MAPC requesting AP that initiates negotiations for the above-mentioned MAPC agreement, and The above second AP is a MAPC responding AP that responds to the above MAPC request AP. method.

12. In Paragraph 11, Based on the MAPC consensus formed regarding the above Co-SR, The step of the first AP transmitting the first PPDU to the first non-AP STA (station) after the cooperation trigger frame is transmitted; and The above second AP further includes the step of transmitting the second PPDU to the second non-AP STA after the cooperation trigger frame is received, The first and second PPDUs are transmitted concurrently to the first and second non-AP STAs, respectively, using transmit power control, and The above first non-AP STA is a non-AP STA associated with the above first AP, and The above second non-AP STA is a non-AP STA connected to the above second AP. method.

13. In Paragraph 12, Based on the above first and second APs performing Co-SR transmission, The above cooperative invitation frame includes at least one of the following: information regarding the minimum number of data OFDM (Orthogonal frequency division multiplexing) symbols of the Co-SR transmission; information regarding the maximum number of data OFDM symbols of the Co-SR transmission; information regarding the intended PHY version of the first PPDU in the Co-SR transmission; information regarding the size of the GI (Guard Interval) and LTF (Long Training Field) of the Co-SR transmission; information regarding the number of LTF symbols of the Co-SR transmission; information regarding the maximum transmission power of the first AP; control information for the cooperative trigger frame; information regarding the Ack policy during the Co-SR transmission period; information regarding whether an ICF (Initial Control Frame) and ICR (Initial Control Response) frame exchange is included between the first AP and the first non-AP STA before the Co-SR transmission; or information regarding the interval of the ICF and ICR frame exchange between the first AP and the first non-AP STA. Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame includes at least one of the following: information regarding the suggested number of data OFDM symbols in the Co-SR transmission; information regarding the intended PHY version of the second PPDU in the Co-SR transmission; information regarding the maximum or minimum transmission power preferred by the second AP; information regarding whether an ICF and ICR frame exchange is included between the second AP and the second non-AP STA prior to the Co-SR transmission; or information regarding the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA. Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame includes information regarding the reason for rejection. method.

14. In Paragraph 13, The above cooperative trigger frame further includes at least one of information regarding the same segment of the first PPDU and the segment of the second PPDU, information regarding the transmission power limit of the second AP, or information regarding the transmission power of the first AP. The value of the transmission power limit of the second AP must not be lower than the value indicated by the second AP in the negotiation request frame or the negotiation response frame. method.

15. In Paragraph 13, The above cooperation trigger frame further includes one user information field for the second AP, and The AID12 field of the above-mentioned single user information field is set to the AP ID (Identifier) ​​of the second AP assigned by the first AP while the MAPC consensus is being formed. method.

16. In Paragraph 12, Based on the MAPC agreement formed for the above Co-BF, the first and second PPDUs are simultaneously transmitted to the first and second non-AP STAs, respectively, through multiple transmit chains, and Based on the above first and second APs performing Co-BF transmission, The above cooperative invitation frame contains information regarding the minimum number of data OFDM symbols of the Co-BF transmission, information regarding the maximum number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding the bandwidth of the Co-BF transmission, information regarding the puncturing pattern of the Co-BF transmission, information regarding the GI and LTF sizes of the Co-BF transmission, information regarding the maximum total number of spatial streams allowed for the second AP of the Co-BF transmission, information regarding the number of the first non-AP STA, information regarding the STA ID of each of the first non-AP STAs, information regarding the number of spatial streams for each of the first non-AP STAs, control information for the cooperative trigger frame, information regarding the Ack policy during the Co-BF transmission period, information regarding whether ICF and ICR frame exchanges are included between the first AP and the first non-AP STA before the Co-BF transmission, or between the first AP and the first non-AP It includes at least one of the information regarding the interval of the ICF and ICR frame exchange between the STAs, and Based on the acceptance of the cooperative invitation frame by the second AP, the cooperative response frame contains information regarding the proposed number of data OFDM symbols of the Co-BF transmission, information regarding the PHY version of the Co-BF transmission, information regarding whether additional LTF to be used for the Co-BF transmission at the second AP is allowed, information regarding the number of the second non-AP STA, information regarding the STA ID of each of the second non-AP STAs, information regarding the Modulation and Coding Scheme (MCS) for each of the second non-AP STAs, information regarding the number of spatial streams for each of the second non-AP STAs, information regarding the 2xLow Density Parity Check (2xLDPC) to be used for each of the second non-AP STAs, information regarding whether ICF and ICR frame exchange is included between the second AP and the second non-AP STA before the Co-BF transmission, or in the interval of the ICF and ICR frame exchange between the second AP and the second non-AP STA Includes at least one of the information regarding, The proposed number of data OFDM symbols in the above Co-BF transmission must not be less than the minimum number of data OFDM symbols indicated by the first AP in the above cooperative invitation frame, and Based on the fact that the above second AP rejects the above cooperation invitation frame, the above cooperation response frame includes information regarding the reason for rejection. method.

17. In Paragraph 16, The above cooperative trigger frame is used to ensure time and frequency synchronization between the first and second PPDUs and further includes information necessary to construct a common preamble for the first and second PPDUs, and The information required to construct a common preamble for the first and second PPDUs includes: information regarding the value set in the Length field within the L-SIG (Legacy-Signal) field of the first and second PPDUs; information regarding the PHY version of the Co-BF transmission; information regarding the bandwidth of the Co-BF transmission; information regarding the puncturing pattern of the Co-BF transmission; information regarding the BSS (Basic Service Set) color of the first AP; information regarding the BSS color of the second AP; information regarding the TXOP interval set in the TXOP field within the U-SIG (Universal-Signal) of the first and second PPDUs; information regarding the number of UHR-SIG (Ultra High Reliability-Signal) symbols of the first and second PPDUs; information regarding the GI and LTF sizes of the Co-BF transmission; information regarding the number of UHR-LTF symbols of the first and second PPDUs; and the first and second non-AP STAs at least one of information regarding the number, information regarding the STA ID of each of the first and second non-AP STAs, information regarding the BSS to which the first and second non-AP STAs belong, information regarding the MCS of each of the first and second non-AP STAs, information regarding the spatial configuration of each of the first and second non-AP STAs, or information regarding whether 2xLDPC will be used for each of the first and second non-AP STAs. method.

18. In a wireless LAN system, the second AP (access point) is, Memory; transceiver; and The processor comprises the memory and the transceiver, operably coupled thereto, wherein the processor comprises: Receive a cooperation invitation frame from the 1st AP; Transmitting a cooperation response frame to the above-mentioned first AP; and Receive a cooperation trigger frame from the above-mentioned first AP, The first AP above is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. 2nd AP.

19. At least one computer-readable medium comprising an instruction based on execution by at least one processor, A step of transmitting a cooperation invitation frame to the second AP (access point); The step of receiving a cooperation response frame from the second AP; and The method includes the step of transmitting a cooperation trigger frame to the second AP, The first AP is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. Recording media.

20. In a device in a wireless LAN system, Memory; and The processor comprises the above memory and operablely coupled thereto, wherein the processor is: Send a cooperation invitation frame to the second AP (access point); Receive a cooperation response frame from the above-mentioned second AP; and Transmit a cooperation trigger frame to the above-mentioned second AP, The first AP is a coordinating AP that acquires a TXOP (transmission opportunity) and initiates MAPC (Multi-AP Coordination) transmission with the second AP, and The above second AP is a coordinated AP participating in the above MAPC transmission, and The above cooperation trigger frame includes information regarding the PHY (Physical) version of the first PPDU (Physical Protocol Data Unit) transmitted by the first AP and the PHY version of the second PPDU transmitted by the second AP. device.

Images