Multi-AP cooperation in wireless LAN system

Abstract

The present disclosure relates to multi-access point (AP) cooperation in a wireless LAN system. According to an embodiment of the present disclosure, provided is a method comprising the steps in which: an AP performs a negotiation procedure for a multi-AP operation with one or more neighboring APs; the AP obtains coordination information on the basis of the negotiation procedure; the AP sets coordination group information for the one or more neighboring APs on the basis of the coordination information, wherein the coordination group information includes information about a corresponding coordination group to which each of the one or more neighboring APs belongs among one or more coordination groups, and each of the one or more coordination groups is associated with a corresponding coordination scheme; and the AP performs the multi-AP operation with a neighboring AP belonging to a coordination group identified in the coordination group information, on the basis of a coordination scheme related to the coordination group.

Description

Multi-AP cooperation in wireless LAN systems

[0001] The present disclosure relates to multi-AP cooperation in a wireless LAN system.

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or later) aims to support ultra-high reliability when transmitting signals to STAs. To achieve this, various technologies are being considered to support high throughput, low latency, and extended range. For example, an AP can exchange frames with STAs (stations) using resources determined through cooperation with neighboring APs.

[0003] The present disclosure provides a method and device for multi-AP cooperation in a wireless LAN system.

[0004] According to an embodiment of the present disclosure, a method is provided, including: a step in which an access point (AP) performs a negotiation procedure for multi-AP operation with one or more neighboring APs; a step in which the AP acquires coordination information based on the negotiation procedure; a step in which the AP sets coordination group information for the one or more neighboring APs based on the coordination information, the coordination group information including information on a corresponding coordination group to which each of the one or more neighboring APs belongs among one or more coordination groups, and each of the one or more coordination groups is associated with a corresponding coordination scheme; and a step in which the AP performs the multi-AP operation based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation scheme associated with the cooperation group.

[0005] According to an embodiment of the present disclosure, a method is provided, including: a step of a station (STA) performing a connection procedure with a first access point (AP); and a step of performing frame exchange with the first AP in a resource cooperated between the first AP and the second AP based on a coordination scheme, wherein the coordination scheme is related to a cooperation group to which the first AP and the second AP belong, the cooperation group being identified in cooperation group information including information on a corresponding cooperation group to which each of one or more neighboring APs including the second AP belongs, and the cooperation group information being set based on cooperation information acquired through a negotiation procedure for multi-AP operation performed by the AP with the one or more neighboring APs.

[0006] In various embodiments, devices for implementing the above-described methods are provided.

[0007] The present disclosure may have various advantageous effects.

[0008] For example, the present disclosure proposes multi-AP table / cooperation group information that can be ultimately generated through a negotiation process between APs in a multi-AP cooperation environment, and / or a grouping method among multiple APs through a negotiation process. Based on the multi-AP table / cooperation group information and / or the multi-AP group, a SAP (sharing AP) can support cooperation-based transmission to a specific DAP (shared AP).

[0009] The beneficial effects that can be achieved through specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, various technical effects may be understood and / or derived from the present disclosure by those skilled in the art. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure.

[0010] FIG. 1 illustrates an example of a transmitting device and / or a receiving device of the present disclosure.

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

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

[0013] Figure 4 illustrates an embodiment of multi-link (ML).

[0014] FIG. 5 illustrates a modified example of a transmitting device and / or a receiving device of the present disclosure.

[0015] FIG. 6 illustrates an example of a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of the present disclosure.

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

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

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

[0019] Figure 10 shows the operation according to UL-MU.

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

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

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

[0023] Figure 14 shows the trigger frame format.

[0024] Figure 15 shows an example of the user information field format of MU-RTS TXS TF.

[0025] Figure 16 shows an example of operation when the value of the TXOP shared mode subfield is 2.

[0026] Figure 17 shows an example of coordinated time division multiple access (C-TDMA) between cooperating APs.

[0027] Figure 18 shows an example of C-OFDMA.

[0028] Figure 19 shows an example of C-BF.

[0029] Figure 20 shows an example of AP selection.

[0030] Figure 21 shows an example of J-TX / JT.

[0031] FIG. 22 illustrates an example of a method performed by an AP according to an embodiment of the present disclosure.

[0032] FIG. 23 illustrates an example of a procedure for multi-AP cooperation according to an embodiment of the present disclosure.

[0033] FIG. 24 illustrates an example of a pair-to-pair negotiation procedure for multi-AP cooperation according to an embodiment of the present disclosure.

[0034] FIG. 25 illustrates an example of C-TDMA operation based on pair-to-pair based negotiation according to an embodiment of the present disclosure.

[0035] FIG. 26 illustrates an example of a C-TDMA procedure based on broadcast-based negotiation according to an embodiment of the present disclosure.

[0036] FIG. 27 illustrates an example of a multi-AP set / group configuration based on negotiation / consultation for multiple cooperation schemes according to an embodiment of the present disclosure.

[0037] FIG. 28 illustrates an example of a negotiation / consultation-based multi-AP set / group configuration for a single cooperative scheme according to an embodiment of the present disclosure.

[0038] FIG. 29 illustrates an example of an operation based on a multi-AP set / group configuration for multiple cooperation schemes according to an embodiment of the present disclosure.

[0039] FIG. 30 illustrates an example of an operation based on a multi-AP set / group configuration for a single cooperative scheme according to an embodiment of the present disclosure.

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

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

[0042] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

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

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

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

[0046] Technical features individually described in one drawing in this disclosure may be implemented individually or simultaneously.

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

[0048] In order to explain the technical features of the present disclosure, technical features to which the present disclosure can be applied are described below.

[0049] FIG. 1 illustrates an example of a transmitting device and / or a receiving device of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] Figure 4 illustrates an example of a multi-link (ML).

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

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

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

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

[0093] The specific features of the present disclosure 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.

[0094] FIG. 5 illustrates a modified example of a transmitting device and / or a receiving device of the present disclosure.

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

[0096] The processor (510) of FIG. 5 may be identical to the processor (111, 121) of FIG. 1. Alternatively, the processor (510) of FIG. 5 may be identical to the processing chip (114, 124) of FIG. 1.

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

[0098] Referring to FIG. 5, a power management module (511) manages power to a processor (510) and / or a transceiver (530). A battery (512) supplies power to the power management module (511). A display (513) outputs results processed by the processor (510). A keypad (514) receives input to be used by the processor (510). The keypad (514) may be displayed on the display (513). A SIM card (515) may be an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and an associated key used to identify and authenticate a subscriber in a mobile phone device, such as a mobile phone or computer.

[0099] Referring to FIG. 5, the speaker (540) can output sound-related results processed by the processor (510). The microphone (541) can receive sound-related input to be used by the processor (510).

[0100] FIG. 6 illustrates an example of a PPDU (physical protocol data unit or physical layer (PHY) protocol data unit) transmitted / received by an STA of the present disclosure.

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

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

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

[0104] Each block illustrated in Fig. 6 may be called a field / subfield / signal, etc. The names of these fields / subfields / signals may be, as illustrated in Fig. 6, 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0117] For example, the version-independent bits of U-SIG may include a 1-bit UL / DL flag field. The first value of the 1-bit UL / DL flag field relates to UL communication, and the second value of the UL / DL flag field relates to DL communication.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0137] Figure 9 is a diagram illustrating the layout of resource units (RUs) used for an 80MHz PPDU. The layout of the resource units (RUs) used in the present disclosure may vary. For example, the layout of the resource units (RUs) used in the 80MHz band may vary.

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

[0139] TB PPDUs (1041, 1042) are transmitted at the same time and can be transmitted from multiple STAs (e.g., User STAs) whose AIDs are indicated in the Trigger frame (1030). The ACK frame (1050) for the TB PPDU can be implemented in various forms. For example, the ACK frame (1050) for the TB PPDU can be implemented in the form of a BA (block ACK).

[0140] In FIG. 10, transmission(s) of a Trigger Frame (1030), a TB PPDU (1041, 1042) and / or an ACK frame (1050) may be performed within a TXOP (1025).

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

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

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

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

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

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

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

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

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

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

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

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

[0153] The MAC frames included in the data field of the PPDU of the present disclosure can be classified into various types. For example, the MAC frames of the present disclosure can be classified into a control frame, a management frame, and a data frame.

[0154] For example, the management frame includes Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, Disassociation, Authentication, and Deauthentication frames / signals defined in conventional WLAN. For the management frame, the values ​​of the type fields (B3 and B2) of the MAC header are set to 00. In addition, the values ​​of the subtype fields (B7, B6, B5, B4) of the MAC header are as follows: Association Request (0000), Association Response (0001), Reassociation Request (0010), Reassociation Response (0011), Probe Request (0100), Probe Response (0101), Beacon (1000), Disassociation (1010), Authentication (1011), Deauthentication (1100).

[0155] For example, the control frame includes Trigger Beamforming Report Poll, NDP Announcement (NDPA), Control Frame Extension, Control Wrapper, Block Ack Request (BlockAckReq), Block Ack (BlockAck), PS-Poll, RTS, CTS, Ack, and CF-End frames / signals defined in conventional WLAN. For the control frame, the value of the type field (B3 and B2) of the MAC header is set to 01. Additionally, the values ​​of the subtype fields (B7, B6, B5, B4) of the MAC header are as follows: Trigger (0010), Beamforming Report Poll (0100), NDP Announcement (0101), Control Frame Extension (0110), Control Wrapper (0111), BlockAckReq (1000), BlockAck (1001), PS-Poll (1010), RTS (1011), CTS (1100), Ack (1101), CF-End (1110).

[0156] For example, the data frame includes (QoS) Data, (QoS) Null, etc. defined in conventional WLAN. For the data frame, the value of the type field (B3 and B2) of the MAC header is set to 10.

[0157] A data frame may include an aggregated-control (A-Control) subfield. For example, a HT Control field included in a data frame may consist of 32 bits B0 to B31, and the A-Control subfield may consist of bits B2 to B31 of the HT Control field with B0 and B1 set to 1. In other words, the A-Control subfield may be 30 bits of information.

[0158] The 30-bit A-Control subfield can have a structure as shown in Table 1 below:

[0159] Control ListPadding

[0160] The bit size (or number of bits) of the Control List subfield can be variable. The bit size of the Padding can be 0 or more. A Control List can contain one or more Control subfields. Each Control subfield can have a structure as shown in Table 2 below:

[0161] Control IDControl Information

[0162] The bit size of the Control ID subfield can be 4 (e.g., B0 to B3). The bit size of the Control Information can be variable. The values ​​of the Control ID subfield can be defined as shown in below:

[0163] Control ID valueMeaningLength of the Control Information subfield (bits)0Triggered response scheduling (TRS)261Operating mode (OM)122HE link adaptation (HLA)263Buffer status report (BSR)264UL power headroom (UPH)85Bandwidth query report (BQR)106Command and status (CAS)87-14Reserved-15Ones need expansion surely (ONES)26

[0164] The type of the MAC frame used in the present disclosure can be identified through the type field / information and the subtype field / information included in the frame control field of the header of the MAC frame (i.e., the MAC header). For example, the “trigger frame” of the present disclosure can mean a MAC frame in which the type bits B3 and B2 bits in the frame control field of the MAC header are set to 01, and the subtype bits B7, B6, B5, and B4 bits in the frame control field are also set to 0010. Various MAC frames described in the present disclosure are inserted / included in the data field of various PPDUs (e.g., HE / VHT / HE / EHT / UHR PPDUs).

[0165] Figure 14 illustrates a trigger frame format. The trigger frame format may also be referred to as the structure of a trigger frame.

[0166] Referring to FIG. 14, a trigger frame may include a frame control field, a duration / ID field, a receiver address (RA) field, a transmitter address (TA) field, a common info field, a user info list field, a padding field, and / or a frame check sequence (FCS) field. Optionally, the trigger frame may further include a special user info field between the common info field and the user info list field. The user info list field may include one or more user info fields. The frame control field, the duration / ID field, the RA field, and the TA field may constitute a MAC header.

[0167] For example, the common information field may include a trigger type subfield. The trigger type subfield value may indicate a trigger frame variant, as shown in Table 4:

[0168] Trigger type subfield valueTrigger frame variant0Basic1Beamforming Report Poll (BFRP)2MU-BAR3MU-RTS4Buffer Status Report Poll (BSRP)5GCR MU-BAR6Bandwidth Query Report Poll (BQRP)7NDP Feedback Report Poll (NFRP)8-15Reserved

[0169] For example, if the value of the trigger type subfield is set to 0, the trigger frame may be a basic trigger frame. For example, if the value of the trigger type subfield is set to 3, the trigger frame may be a MU (multi-user) RTS trigger frame. Meanwhile, according to the EHT (or 802.11be) standard, in order to support peer-to-peer (P2P) transmission to a non-AP STA, an AP may allocate a portion of the time interval within the TXOP acquired by the AP. In order to allocate a portion of the time interval within the TXOP, a TXOP Sharing Mode subfield may be defined within the Common Info Field of the MU-RTS trigger frame. When the value of the TXOP Sharing Mode subfield is non-zero, such an MU-RTS trigger frame may be referred to as an MU-RTS TXOP Sharing (TXS) trigger frame (TF). The values ​​of the TXOP Sharing Mode subfield are described in Table 5 below:

[0170] Triggered TXOP Sharing Mode subfield valueDescription0MU-RTS that does not initiate MU-RTS TXOP sharing procedure.1MU-RTS that initiates MU-RTS TXOP sharing procedure wherein a scheduledSTA can only transmit MPDU(s) addressed to its associated AP.2MU-RTS that initiates MU-RTS TXOP sharing procedure wherein a scheduled STA can transmit MPDU(s) addressed to its associated AP or addressed to another STA.3Reserved.

[0171] For example, if the value of the TXOP shared mode subfield is 1, one or more (non-TB) PPDU transmissions to the AP may be supported. If the value of the TXOP shared mode subfield is 2, not only (non-TB) PPDU transmissions to the AP but also P2P transmissions may be supported. In the present disclosure, the MU-RTS TXS TF may also be briefly referred to as a TXS trigger frame.

[0172] Figure 15 shows an example of the user information field format of MU-RTS TXS TF.

[0173] Referring to FIG. 15, the user information field may include an AID subfield, an RU allocation subfield, an allocation duration subfield, reserved bits, and / or a PS160 subfield.

[0174] The AID subfield may indicate the AID for the corresponding STA. The RU allocation subfield may indicate RU allocation for the corresponding STA.

[0175] The allocation interval subfield can contain 9 bits from B20 to B28 in the MU-RTS TXS TF and can indicate an allocation interval in units of 16us. In this case, the maximum length of the allocation interval that can be indicated by the allocation interval subfield can be 2^9= 8192us.

[0176] The PS160 subfield may indicate the primary 160MHz channel or the second 160MHz channel to which RU or MRU allocation applies.

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

[0178] Figure 16 shows an example of operation when the value of the TXOP shared mode subfield is 2.

[0179] Referring to FIG. 16, an AP may transmit an MU-RTS TXS TF including allocation (time) interval information (e.g., Time allocated in MU-RTS TXS Trigger Frame) to non-AP STA 1. Non-AP STA 1 may transmit a CTS in response to the MU-RTS TXS TF and perform P2P transmission to non-AP STA 2.

[0180] When the triggered TXOP sharing protocol is utilized for multi-AP coordination, transmissions within the BSS of each cooperative AP are divided into time units, so that each cooperative AP can perform frame exchange without affecting other cooperative APs.

[0181] In the present disclosure, "frame exchange (FE)" may include frame transmission and / or reception operations between STAs. The STAs may be APs or non-AP STAs. Here, the frames may include various types of frames (e.g., data frames, control frames, management frames).

[0182] In this disclosure, multi-AP operation is proposed. Multi-AP operation may be based on a technique for reducing various interferences, such as inter-symbol interference (ISI), through coordination with neighboring APs (e.g., APs located in overlapping BSSs).

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

[0184] In this disclosure, the terms “multi-AP (cooperative) operation” and “multi-AP cooperative scheme (or cooperative scheme)” may be used interchangeably.

[0185] Figure 17 shows an example of coordinated time division multiple access (C-TDMA) between cooperating APs.

[0186] For example, C-TDMA could mean that each cooperating AP exchanges frames without affecting other cooperating APs by separating transmissions within the BSS of each cooperating AP into time units.

[0187] Figure 18 shows an example of C-OFDMA.

[0188] Referring to FIG. 18, 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. 18, STA1 and AP1 can be included in a BSS, and STA2 and AP2 can be included in an OBSS. That is, STA2 can be an unassociated STA to AP1, and STA1 can be an unassociated STA to AP2.

[0189] Although not illustrated in Fig. 18, an example of Coordinated TDMA (C-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.

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

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

[0192] Figure 19 shows an example of C-BF.

[0193] Referring to FIG. 19, AP1 may transmit a PPDU / signal to STA1, and AP2 may transmit a PPDU / signal to STA2. Transmission from AP1 and transmission from AP2 may be performed in the same / overlapping time interval. Transmission from AP1 and transmission from AP2 may be performed through the same / overlapping frequency band. In order to reduce interference caused to STA2 by AP1, AP1 may perform nulling / beamforming toward STA2, and in order to reduce interference caused to STA1 by AP2, AP2 may perform nulling / beamforming toward STA1. For example, such nulling / beamforming may be implemented in a manner of positioning a radiation null to a neighboring unassociated STA. The above-described nulling / beamforming may make a specific AP invisible to a neighboring unassociated STA. For example, the above-described nulling / beamforming may make AP1 (or AP2) invisible to STA2 (or STA1).

[0194] For example, in FIG. 19, 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.

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

[0196] Figure 20 shows an example of AP selection.

[0197] Referring to Fig. 20, AP2 is determined to have a better channel condition 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. 20, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. In other words, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

[0198] Figure 21 shows an example of J-TX / JT.

[0199] Referring to FIG. 21, AP1 can transmit to STA1 together with AP2. For example, the PPDU / signal transmitted from AP2 to STA1 may be all or part of the same as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be simultaneously transmitted through the same / overlapping frequency band as the PPDU / signal transmitted from AP1 to STA1. For example, the PPDU / signal transmitted from AP2 to STA1 may be a signal transmitted from AP1 through a backhaul link. For example, in FIG. 21, STA1 and AP1 may be included in a BSS, and STA2 and AP2 may be included in an OBSS. That is, STA2 may be an unassociated STA to AP1, and STA1 may be an unassociated STA to AP2.

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

[0201] When the triggered TXS protocol is applied to a multi-AP cooperative operation, an AP in the triggered TXS protocol may be an AP that shares a TXOP in the multi-AP cooperative operation, and an STA in the triggered TXS protocol may be an AP that shares a TXOP in the multi-AP cooperative operation. In the present disclosure, an AP that shares a TXOP may be referred to as a SAP (sharing AP), and an AP that receives a TXOP from a SAP may be referred to as a DAP (shared AP). Here, the name SAP does not limit that the entity that shares a TXOP is only an AP STA, and a SAP may also include a non-AP STA that shares a TXOP. In addition, the name DAP does not limit that the entity that shares a TXOP is only an AP STA, and a DAP may also include a non-AP STA that shares a TXOP (or performs transmission and reception with an AP STA that shares a TXOP). Additionally, the frame exchange performed by the DAP with a non-AP STA or SAP belonging to the DAP BSS during the allocated time (i.e., the allocated period for DAP / AP2 within the TXOP indicated by the MU-RTS TXS TF transmitted from the SAP, which is the time allocated in the MU-RTS TXS TF in FIG. 17) may be referred to as a BSS frame exchange (FE) of the DAP. For example, the RTS / CTS frame exchange between the DAP and the non-AP STA followed by data frame transmission and block ACK frame response, UL data frame transmission of non-AP STAs by a trigger frame transmitted from the DAP, and / or data frame transmission of the DAP by a trigger frame transmitted from the SAP may be performed.

[0202] In order for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) to be performed between two APs, the two APs must be in a connected / associated state with each other, and / or each AP can exchange (i.e., negotiate) information about its capabilities and / or requirements with the other AP, and perform multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) based on the obtained information. In order for multi-AP operations to be performed smoothly, negotiation for multi-AP operations needs to be performed in advance between the SAP and the DAP. Additionally, multi-AP operations that can be newly defined / applied in UHR (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) may require various rules and signaling to be defined / added depending on whether legacy devices are supported, whereas only UHR devices may require relatively little information or signaling.

[0203] Accordingly, the present disclosure defines a negotiation process for multi-AP operation between APs, information required for negotiation, and additional information that can be used for negotiation between APs that only support UHR non-AP STAs. Furthermore, the present disclosure provides a description of the negotiation process for exchanging the defined information.

[0204] In addition, the present disclosure provides necessary information (i.e., negotiation information / cooperation information) during a negotiation process that must be performed between APs prior to multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) in a multi-AP cooperation environment, and a negotiation procedure for exchanging such negotiation information / cooperation information.

[0205] In this disclosure, through negotiation information / cooperation information, each AP can perform multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX), and can smoothly exchange frames with (UHR) non-AP STAs based on the information (i.e., negotiation information / cooperation information) acquired during the negotiation process.

[0206] The specific designations / names proposed in this disclosure may be changed and are not limited thereto.

[0207] FIG. 22 illustrates an example of a method performed by an AP according to an embodiment of the present disclosure.

[0208] Referring to FIG. 22, in step S2201, the AP can perform a negotiation procedure for multi-AP operation with one or more neighboring APs.

[0209] In step S2203, the AP can obtain cooperation information based on the negotiation procedure.

[0210] In step S2205, the AP may set coordination group information (or multi-AP group information / multi-AP table) for one or more neighboring APs based on the coordination information. The coordination group information may include information about a corresponding coordination group to which one or more neighboring APs belong among one or more coordination groups. Each of the one or more coordination groups may be associated with a corresponding coordination method.

[0211] In step S2207, the AP can perform multi-AP operations based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation method associated with the cooperation group.

[0212] According to various embodiments, to perform a negotiation procedure, an AP may transmit a cooperation request frame to one or more neighboring APs and receive a cooperation response frame including information indicating acceptance or rejection of the cooperation request frame from one or more neighboring APs. The cooperation information may be included in at least one of the cooperation request frame or the cooperation response frame.

[0213] According to various embodiments, the cooperation information may further include at least one of information about the operating channel, information about the operating bandwidth, interval information about the transmission opportunity (TXOP), information about low-latency traffic, or information about whether only STAs of the latest wireless local area network (WLAN) version (e.g., UHR) are supported.

[0214] According to various embodiments, the collaboration information may further include at least one of an identifier of a collaboration group, an identifier of an AP within the collaboration group, or information on a collaboration method.

[0215] According to various embodiments, information on whether only STAs of the latest WLAN version are supported may include a 1-bit field. A 1-bit field set to 0 may indicate that only STAs of the latest WLAN version (e.g., UHR) are supported. A 1-bit field set to 1 may indicate that STAs of the latest WLAN version (e.g., UHR) and STAs of previous WLAN versions (e.g., HT / VHT / HE / EHT) are supported.

[0216] According to various embodiments, an AP may detect management frames or beacon frames transmitted from one or more neighboring APs. Based on the management frames or beacon frames, the AP may identify one or more neighboring APs with which it will perform a negotiation procedure for multi-AP operation.

[0217] According to various embodiments, a management frame or a beacon frame may include a 1-bit field. A 1-bit field set to 0 may indicate that the corresponding AP participates in multi-AP operation. A 1-bit field set to 1 may indicate that the corresponding AP does not participate in multi-AP operation.

[0218] According to various embodiments, the information about the corresponding cooperative group to which each of the one or more neighboring APs belongs may include at least one of an identifier of the cooperative group to which each of the one or more neighboring APs belongs, an identifier of each of the one or more neighboring APs within the cooperative group, or a basic service set (BSS) identifier of each of the one or more neighboring APs.

[0219] According to various embodiments, the cooperation scheme may include at least one of coordinated time division multiple access (C-TDMA), coordinated orthogonal frequency division multiple access (C-OFDMA), coordinated spatial reuse (C-SR), coordinated beamforming (C-BF), AP selection, or joint transmission (J-TX).

[0220] According to various embodiments, an AP may exchange frames with an STA associated with the AP in a resource cooperated with a neighboring AP based on a cooperative manner to perform multi-AP operations.

[0221] FIG. 23 illustrates an example of a procedure for multi-AP cooperation according to an embodiment of the present disclosure.

[0222] Referring to FIG. 23, in step S2301, the STA may perform a connection procedure with the first AP. In FIG. 23, the connection procedure between the STA and the first AP in step S2301 is expressed as being performed before step S2302, but this is exemplary, and the connection procedure in step S2301 may be performed at any point before frame exchange is performed in step S2309.

[0223] In step S2303, the first AP may perform a negotiation procedure for multi-AP operation with one or more neighboring APs, including the second AP.

[0224] In step S2305, the first AP can obtain cooperation information based on the negotiation procedure.

[0225] In step S2307, the first AP may set coordination group information (or multi-AP group information / multi-AP table) for one or more neighboring APs based on the coordination information. The coordination group information may include information about a corresponding coordination group to which one or more neighboring APs belong among one or more coordination groups. Each of the one or more coordination groups may be associated with a corresponding coordination method.

[0226] In step S2309, the STA may exchange frames with the first AP based on the cooperation method, using the resources cooperated between the first AP and the second AP. The cooperation method may be related to the cooperation group to which the first AP and the second AP belong. The cooperation group may be identified in the cooperation group information.

[0227] According to various embodiments, the information may include at least one of information about an operating channel, information about an operating bandwidth, interval information about a transmission opportunity (TXOP), information about low-latency traffic, or information about whether only STAs (stations) of the latest WLAN version (e.g., UHR) are supported.

[0228] According to various embodiments, the collaboration information may further include at least one of an identifier of a collaboration group, an identifier of an AP within the collaboration group, or information on a collaboration method.

[0229] According to various embodiments, information on whether only STAs of the latest WLAN version are supported may include a 1-bit field. A 1-bit field set to 0 may indicate that only STAs of the latest WLAN version (e.g., UHR) are supported. A 1-bit field set to 1 may indicate that STAs of the latest WLAN version (e.g., UHR) and STAs of previous WLAN versions (e.g., HT / VHT / HE / EHT) are supported.

[0230] According to various embodiments, the information about the corresponding cooperative group to which each of the one or more neighboring APs belongs may include at least one of an identifier of the cooperative group to which each of the one or more neighboring APs belongs, an identifier of each of the one or more neighboring APs within the cooperative group, or a basic service set (BSS) identifier of each of the one or more neighboring APs.

[0231] According to various embodiments, the cooperation scheme may include at least one of coordinated time division multiple access (C-TDMA), coordinated orthogonal frequency division multiple access (C-OFDMA), coordinated spatial reuse (C-SR), coordinated beamforming (C-BF), AP selection, or joint transmission (J-TX).

[0232] Below, a detailed implementation for multi-AP cooperation is described.

[0233] FIG. 24 illustrates an example of a pair-to-pair negotiation procedure for multi-AP cooperation according to an embodiment of the present disclosure.

[0234] Referring to FIG. 24, multi-AP cooperation operations can be performed between APs according to a pair-to-pair negotiation procedure. In FIG. 24, each AP that wishes to participate in multi-AP cooperation or to negotiate for multi-AP cooperation can perform a pre-negotiation procedure for multi-AP cooperation by transmitting and receiving a coordination request frame and a coordination response frame thereto with a neighboring AP. Through a negotiation procedure that exchanges cooperation request frames and / or cooperation response frames containing information on various multi-AP cooperation methods and / or information for multi-AP operations, APs that wish to perform multi-AP cooperation-based transmission can obtain information about each other (i.e., cooperation information). An AP that acquires a TXOP and acts as a SAP can decide based on the cooperation information whether to first perform individual FEs with STAs within its BSS or to share the TXOP and / or specific resources with a specific DAP.

[0235] As above, APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) need to exchange negotiation information / cooperation information with each other in advance through a negotiation procedure.

[0236] I. Negotiation Information / Cooperation Information for Multi-AP Operation

[0237] The negotiation information / cooperation information according to the present disclosure can be used by each AP for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) and also for frame exchange with each non-AP STA. For example, the negotiation information / cooperation information according to the present disclosure allows the AP that first acquired the TXOP to act as a SAP to determine the length of the TXOP section (or allocation section) to be shared with the DAP, and to match the operating bandwidth and channel between each AP for smooth cooperation. In addition, by specifying / indicating that the AP participating in the multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) is an AP or BSS that only supports UHR non-AP STAs, the sharing AP that shares the TXOP with the corresponding AP may not require additional rules or signaling.

[0238] Negotiation / cooperation information can be included in cooperation request / response frames (e.g., new cooperation request / response frames, SCS request / response, A-Control fields) exchanged during the negotiation process between APs participating in multi-AP cooperation, and transmitted individually from each AP. It is assumed that the cooperation request and response frames can be defined as new frames or as new elements to be transmitted alongside existing request and response frames.

[0239] In the negotiation procedure for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) proposed in the present disclosure, the cooperation request frame transmitted may include negotiation information / cooperation information based on one or a combination of multiple of the following A to H:

[0240] A. Multi-AP Group ID: ID for the group / set of APs that constitute multi-AP cooperation (e.g. 0, 1, 2, ...)

[0241] B. Multi-AP ID: An ID locally assigned by each AP within the configured multi-AP group / set (e.g. 0, 1, 2, ...)

[0242] C. Multi-AP cooperation type (or cooperation method): Information about multi-AP cooperation methods including C-OFDMA, C-TDMA, J-TX, and C-SR.

[0243] D. Operating Channel: Information about the primary channel and punctured channels that are in operation.

[0244] For example, the operating channel information may include commonly operating channel information for smooth cooperation between APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0245] For example, the operating channel information may include primary channel information on which APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) can commonly operate. In some implementations, a new field that serves as the CCSF0 field in the EHT operating information field may be defined to indicate a channel center frequency index for a 20 / 40 / 80 MHz channel. In some implementations, a new field that serves as the CCSF0 field in the EHT operating information field may be defined to indicate a channel center frequency for a primary 80 MHz channel of a 160 MHz channel or a channel center frequency for a primary 160 MHz channel of a 320 MHz channel. In addition, a new field that serves as the CCSF1 field in the EHT operating information field may be defined to indicate a channel center frequency for a 160 MHz channel or a channel center frequency for a 320 MHz channel.

[0246] For example, the operating channel information may include punctured channel information of an AP participating in multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a new field that acts as a Disabled subchannel bitmap field in the EHT operating information field may be defined to indicate a punctured 20 MHz subchannel using a bitmap. A bit value of 0 in the bitmap may indicate that the corresponding 20 MHz subchannel is not punctured. A bit value of 1 in the bitmap may indicate that the corresponding 20 MHz subchannel is punctured.

[0247] For example, the operating channel information may include information about the primary channel of the DAP within the channel on which the SAP operates.

[0248] For example, the operating channel information may include information about the primary channel of the DAP within the operating channel excluding the punctured channel of the SAP.

[0249] E. Operating Bandwidth Information: Operating bandwidth and maximum bandwidth information.

[0250] For example, the operating bandwidth information may include common operating bandwidth (BW) information for smooth cooperation between APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, the operating channel and primary channel information described above may be utilized.

[0251] For example, the operating bandwidth information may include the maximum bandwidth information of an AP participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a new field, similar to the channel width field in the control field of the EHT operation information field, may be defined to indicate the channel width, which is BSS BW information for each AP, as follows:

[0252] - Set to 0: Indicates 20 MHz bandwidth

[0253] - Set to 1: Indicates 40 MHz bandwidth

[0254] - Set to 2: Indicates 80 MHz bandwidth

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

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

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

[0258] For example, the operating bandwidth information may include BW field information within the SIG-A field.

[0259] For example, the operating bandwidth information may include UL BW field information included within the common information field of the MU-RTS TXS TF.

[0260] For example, the operating bandwidth information may include information about the bandwidth of the DAP within the overall bandwidth over which the SAP operates.

[0261] For example, a new field for bandwidth indication (i.e., operating bandwidth information) can be added by modifying / redefining the Medium Time field of the QoS characteristic element to include a new subfield. In some implementations, a new field that functions similarly to the Channel Width field in the Control field of the EHT Operating Information field can be defined to indicate the channel width, which is BSS BW information for each AP, as follows:

[0262] - Set to 0: Indicates 20 MHz bandwidth

[0263] - Set to 1: Indicates 40 MHz bandwidth

[0264] - Set to 2: Indicates 80 MHz bandwidth

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

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

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

[0268] F. Requested TXOP interval: Information related to the TXOP interval that each AP wishes to share.

[0269] For example, a new field including a requested TXOP interval may be defined. In some implementations, a requested interval field may be defined to indicate information and a requested TXOP interval value required for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a C-TDMA operation element may be defined to indicate information and a requested TXOP interval value required for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0270] For example, the required TXOP interval may be included within a QoS characteristic element that may be used to include negotiation information / cooperation information during pre-negotiation for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) or an element that may be newly defined for negotiation for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0271] For example, a UHR operation element that can be used to include broadcast information in the broadcast process of each AP for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) or a required TXOP interval can be included within an element that can be newly defined for broadcast for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

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

[0273] For example, low-latency traffic information may be included in the information of QoS attribute elements included in the SCS request / response frame.

[0274] For example, the Delay Bound field information among the QoS characteristic elements can be utilized. In some implementations, the Delay Bound field value for the QoS traffic that each AP wishes to transmit can be utilized as low-delay traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that can complete transmission of an MSDU or A-MSDU within the end time of the TXOP section to be shared (i.e., the time allocated for the pre-negotiated low-delay traffic information or Delay Bound field value is shorter than the time allocated) or to update the existing value.

[0275] For example, the MSDU Lifetime field information among the QoS characteristic elements can be utilized. In some implementations, the MSDU Lifetime field value for the QoS traffic that each AP wants to transmit can be utilized as low-latency traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that does not discard MSDUs within the end point of the TXOP section to be shared (i.e., the pre-negotiated low-latency traffic information or the MSDU Lifetime field value has not expired within the allocated time) or to update the existing value.

[0276] For example, the service start time field information among the QoS characteristic elements can be utilized. In some implementations, the service start time field value for the QoS traffic that each AP wishes to transmit can be utilized as low-latency traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that can start the expected service section and frame exchange within the end time of the TXOP section to be shared (i.e., the pre-negotiated low-latency traffic information or the service start time field value is shorter than the allocated time) or to update the existing value.

[0277] For example, low-latency traffic information may include TXOP sharing request information requested / instructed by an AP requiring transmission of low-latency traffic.

[0278] For example, the low-latency traffic information may include time bound information of the low-latency traffic requested / instructed by the AP requiring transmission of the low-latency traffic (e.g., minimum time-bound within which transmission of the low-latency traffic must begin / maximum time-bound within which transmission of the low-latency traffic must successfully end).

[0279] For example, the low-latency traffic information may include arrival rate information of low-latency traffic requested / instructed by an AP requiring periodic transmission of low-latency traffic (e.g., the arrival rate of low-latency traffic since the last reporting event).

[0280] For example, low-latency traffic information may include TID (Traffic Identifier) / AC (Access Category) information.

[0281] H. UHR STA Support: Information indicating whether only UHR non-AP STAs are supported.

[0282] For example, a 1-bit signaling may be defined to indicate UHR STA support information within a cooperation request / response frame. In this case, bit 0 may indicate that only UHR non-AP STAs are supported, and bit 1 may indicate that HE / EHT / UHR non-AP STAs are supported.

[0283] For example, information (e.g., PHY version identifier) ​​in the Special User Information field included in the trigger frame may be utilized for UHR STA support information.

[0284] For example, a QoS characteristic element included in an SCS request / response frame may be utilized for UHR STA support information. In some implementations, a reserved bit of control information among the information of the QoS characteristic element may be utilized. That is, a 1-bit signaling may be defined among the reserved bits to indicate UHR STA support information. In this case, bit 0 may indicate that only UHR non-AP STAs are supported. Bit 1 may indicate that HE / EHT / UHR non-AP STAs are supported.

[0285] UHR STA support information / signaling may be defined to indicate, but is not limited to, that the AP supports only UHR non-AP STAs, or that it supports UHR as well as HE / EHT non-AP STAs.

[0286] The names of the IDs and / or signaling / information defined above may change, and information that is the basis for multi-AP operation (e.g., channel information, DAP buffer information) may exist and be included.

[0287] Additionally, the cooperation response frame transmitted during the negotiation process for the multi-AP operation proposed in the present disclosure (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) may include negotiation information / cooperation information based on one or more combinations of A to I below:

[0288] A. Multi-AP Group ID: ID for the group / set of APs that constitute multi-AP cooperation (e.g. 0, 1, 2, ...)

[0289] B. Multi-AP ID: An ID locally assigned by each AP within the configured multi-AP group / set (e.g. 0, 1, 2, ...)

[0290] C. Multi-AP cooperation type (or cooperation method): Information about multi-AP cooperation methods including C-OFDMA, C-TDMA, J-TX, and C-SR.

[0291] D. Operating Channel: Information about the primary channel and punctured channels that are in operation.

[0292] For example, the operating channel information may include commonly operating channel information for smooth cooperation between APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0293] For example, the operating channel information may include primary channel information on which APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) can commonly operate. In some implementations, a new field that serves as the CCSF0 field in the EHT operating information field may be defined to indicate a channel center frequency index for a 20 / 40 / 80 MHz channel. In some implementations, a new field that serves as the CCSF0 field in the EHT operating information field may be defined to indicate a channel center frequency for a primary 80 MHz channel of a 160 MHz channel or a channel center frequency for a primary 160 MHz channel of a 320 MHz channel. In addition, a new field that serves as the CCSF1 field in the EHT operating information field may be defined to indicate a channel center frequency for a 160 MHz channel or a channel center frequency for a 320 MHz channel.

[0294] For example, the operating channel information may include punctured channel information of an AP participating in multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a new field that acts as a Disabled subchannel bitmap field in the EHT operating information field may be defined to indicate a punctured 20 MHz subchannel using a bitmap. A bit value of 0 in the bitmap may indicate that the corresponding 20 MHz subchannel is not punctured. A bit value of 1 in the bitmap may indicate that the corresponding 20 MHz subchannel is punctured.

[0295] For example, the operating channel information may include information about the primary channel of the DAP within the channel on which the SAP operates.

[0296] For example, the operating channel information may include information about the primary channel of the DAP within the operating channel excluding the punctured channel of the SAP.

[0297] E. Operating Bandwidth Information: Operating bandwidth and maximum bandwidth information.

[0298] For example, the operating bandwidth information may include common operating bandwidth (BW) information for smooth cooperation between APs participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, the operating channel and primary channel information described above may be utilized.

[0299] For example, the operating bandwidth information may include the maximum bandwidth information of an AP participating in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a new field, similar to the channel width field in the control field of the EHT operation information field, may be defined to indicate the channel width, which is BSS BW information for each AP, as follows:

[0300] - Set to 0: Indicates 20 MHz bandwidth

[0301] - Set to 1: Indicates 40 MHz bandwidth

[0302] - Set to 2: Indicates 80 MHz bandwidth

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

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

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

[0306] For example, the operating bandwidth information may include BW field information within the SIG-A field.

[0307] For example, the operating bandwidth information may include UL BW field information included within the common information field of the MU-RTS TXS TF.

[0308] For example, the operating bandwidth information may include information about the bandwidth of the DAP within the overall bandwidth over which the SAP operates.

[0309] For example, a new field for bandwidth indication (i.e., operating bandwidth information) can be added by modifying / redefining the Medium Time field of the QoS characteristic element to include a new subfield. In some implementations, a new field that functions similarly to the Channel Width field in the Control field of the EHT Operating Information field can be defined to indicate the channel width, which is BSS BW information for each AP, as follows:

[0310] - Set to 0: Indicates 20 MHz bandwidth

[0311] - Set to 1: Indicates 40 MHz bandwidth

[0312] - Set to 2: Indicates 80 MHz bandwidth

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

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

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

[0316] F. Requested TXOP interval: Information related to the TXOP interval that each AP wishes to share.

[0317] For example, a new field including a requested TXOP interval may be defined. In some implementations, a requested interval field may be defined to indicate information and a requested TXOP interval value required for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). In some implementations, a C-TDMA operation element may be defined to indicate information and a requested TXOP interval value required for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0318] For example, the required TXOP interval may be included within a QoS characteristic element that may be used to include negotiation information / cooperation information during pre-negotiation for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) or an element that may be newly defined for negotiation for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0319] For example, a UHR operation element that can be used to include broadcast information in the broadcast process of each AP for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) or a required TXOP interval can be included within an element that can be newly defined for broadcast for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

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

[0321] For example, low-latency traffic information may be included in the information of QoS attribute elements included in the SCS request / response frame.

[0322] For example, the Delay Bound field information among the QoS characteristic elements can be utilized. In some implementations, the Delay Bound field value for the QoS traffic that each AP wishes to transmit can be utilized as low-delay traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that can complete transmission of an MSDU or A-MSDU within the end time of the TXOP section to be shared (i.e., the time allocated for the pre-negotiated low-delay traffic information or Delay Bound field value is shorter than the time allocated) or to update the existing value.

[0323] For example, the MSDU Lifetime field information among the QoS characteristic elements can be utilized. In some implementations, the MSDU Lifetime field value for the QoS traffic that each AP wants to transmit can be utilized as low-latency traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that does not discard MSDUs within the end point of the TXOP section to be shared (i.e., the pre-negotiated low-latency traffic information or the MSDU Lifetime field value has not expired within the allocated time) or to update the existing value.

[0324] For example, the service start time field information among the QoS characteristic elements can be utilized. In some implementations, the service start time field value for the QoS traffic that each AP wishes to transmit can be utilized as low-latency traffic information. Through this, the SAP can use it to check whether TXOP sharing is necessary for a DAP that can start the expected service section and frame exchange within the end time of the TXOP section to be shared (i.e., the pre-negotiated low-latency traffic information or the service start time field value is shorter than the allocated time) or to update the existing value.

[0325] For example, low-latency traffic information may include TXOP sharing request information requested / instructed by an AP requiring transmission of low-latency traffic.

[0326] For example, the low-latency traffic information may include time bound information of the low-latency traffic requested / instructed by the AP requiring transmission of the low-latency traffic (e.g., minimum time-bound within which transmission of the low-latency traffic must begin / maximum time-bound within which transmission of the low-latency traffic must successfully end).

[0327] For example, the low-latency traffic information may include arrival rate information of low-latency traffic requested / instructed by an AP requiring periodic transmission of low-latency traffic (e.g., the arrival rate of low-latency traffic since the last reporting event).

[0328] For example, low-latency traffic information may include TID (Traffic Identifier) / AC (Access Category) information.

[0329] H. UHR STA Support: Information indicating whether only UHR non-AP STAs are supported.

[0330] For example, a 1-bit signaling may be defined to indicate UHR STA support information within a cooperation request / response frame. In this case, bit 0 may indicate that only UHR non-AP STAs are supported, and bit 1 may indicate that HE / EHT / UHR non-AP STAs are supported.

[0331] For example, information (e.g., PHY version identifier) ​​in the Special User Information field included in the trigger frame may be utilized for UHR STA support information.

[0332] For example, a QoS characteristic element included in an SCS request / response frame may be utilized for UHR STA support information. In some implementations, a reserved bit of control information among the information of the QoS characteristic element may be utilized. That is, a 1-bit signaling may be defined among the reserved bits to indicate UHR STA support information. In this case, bit 0 may indicate that only UHR non-AP STAs are supported. Bit 1 may indicate that HE / EHT / UHR non-AP STAs are supported.

[0333] UHR STA support information / signaling may be defined to indicate, but is not limited to, that the AP supports only UHR non-AP STAs, or that it supports UHR as well as HE / EHT non-AP STAs.

[0334] I. Status Code: Acceptance / Rejection / Proposal information for the cooperation request.

[0335] For example, the status code could indicate acceptance or success.

[0336] For example, the status code may indicate a rejection, or may indicate a rejection while including proposal information. In some implementations, the status code may include a rejection code that includes a reason for the rejection (e.g., REJECTED_BAD_SUPPORTED_CHANNELS). In some implementations, the status code may include a rejection code that includes proposal information (e.g., REJECTED_WITH_SUGGESTED_CHANGES). If the value of the status code includes rejection and / or proposal information, it may also include information for a new negotiation. That is, a neighboring AP that receives a cooperation request frame may include additional information about the operating channel, bandwidth, required TXOP period, low-latency traffic information, and / or UHR STA support described above.

[0337] The names of the IDs and / or signaling / information defined above may change, and information that is the basis for multi-AP operation (e.g., channel information, DAP buffer information) may exist and be included.

[0338] II. Negotiation Procedure for Multi-AP Operation

[0339] Through the inter-AP negotiation process for multi-AP cooperation, APs can participate in multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). For the inter-AP negotiation process for multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX), negotiation through request / response between APs and non-AP STAs can be utilized. In addition, the subject of cooperation request / response and the criteria / conditions of cooperation requests for multi-AP cooperation and multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) need to be specified.

[0340] First, the criteria for an AP willing to participate in multi-AP cooperation to transmit a cooperation request frame can be determined by the following example:

[0341] Example 1) Individual cooperation request based on AP’s need for cooperation.

[0342] When multi-AP cooperation is required, each AP can individually transmit a cooperation request frame to a specific AP based on overheard frames (e.g., management, control, and data frames) from neighboring APs. The need for multi-AP cooperation may arise from the burst data and / or low-latency traffic that individual APs transmit. Upon receiving a cooperation request frame transmitted based on the cooperation need of each individual AP, the specific AP can transmit a corresponding cooperation request response frame based on the status code.

[0343] Example 2) Request for cooperation to modify and utilize the beacon frame.

[0344] Each AP can overhear periodically transmitted beacon frames to determine the presence of APs interested in participating in multi-AP cooperation and multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). For this purpose, new signaling bits can be defined and added to the beacon frames.

[0345] For example, one-bit signaling may be utilized (e.g., using the reserved bit in the capability information field in the frame body). Bit 0 may indicate participation in multi-AP cooperation. Bit 1 may indicate not to participate in multi-AP cooperation.

[0346] When an AP that receives a beacon frame containing the new signaling bit (=1) described above wishes to participate in multi-AP cooperation, it can decode the information and elements following the signaling bit and obtain additional information related to multi-AP cooperation. After securing a channel through medium contention, it can transmit a cooperation request frame to the corresponding neighboring AP. The neighboring AP that receives the cooperation request frame can transmit a cooperation response frame based on the status code. On the other hand, non-AP STAs can ignore the signaling bit information regarding multi-AP cooperation described above.

[0347] Based on the criteria for requesting negotiation described above, the negotiation process for cooperation between an AP (e.g., AP 1) and a neighboring AP (e.g., AP 2) can be performed in the following steps:

[0348] Step 1) The AP transmits a cooperation request frame to a neighboring AP.

[0349] Step 2) The neighboring AP that receives the cooperation request frame transmits a cooperation response frame to the AP that transmitted the cooperation request frame.

[0350] At this time, the neighboring AP that receives the cooperation request frame in step 2) can transmit a cooperation response frame including response information for the cooperation request based on the status code. For example, if the cooperation response frame includes a code for acceptance or success, cooperation for multi-AP operation (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) can be considered successful. On the other hand, if the AP receives a cooperation response frame with a rejection code or a rejection code including proposal information, the AP can retransmit the cooperation request frame to the neighboring AP. That is, the AP can retransmit the cooperation request frame including the same information as the information included in the cooperation request frame transmitted during the initial negotiation process, or including changed information based on the rejection reason or proposal information in the received cooperation response frame. In addition, if the AP that received the cooperation response frame with a rejection code or a rejection code including proposal information does not retransmit the cooperation request frame, the cooperation can be considered failed (due to rejection).

[0351] III. Multi-AP Operation Based on Negotiation

[0352] Below, multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) based on negotiation information / cooperation information and negotiation procedures are described. Although C-TDMA operation is described in FIGS. 25 and 26 , this is exemplary, and the descriptions of FIGS. 25 and 26 can also be applied to other multi-AP operations (e.g., C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0353] FIG. 25 illustrates an example of C-TDMA operation based on pair-to-pair based negotiation according to an embodiment of the present disclosure.

[0354] Referring to Figure 25, before acquiring a TXOP, each AP whose role as a SAP or DAP has not been determined can perform a pre-negotiation procedure for multi-AP cooperation by transmitting and receiving a cooperation request frame and a cooperation response frame in response to the cooperation request frame with a neighboring AP. Through the negotiation procedure of exchanging request and response frames containing information for C-TDMA operation (e.g., negotiation information / cooperation information), APs wishing to operate in multi-AP cooperation and C-TDMA can obtain information about each other (e.g., negotiation information / cooperation information). Based on this negotiation information / cooperation information, an AP that acquires a TXOP and performs the SAP role can decide whether to first perform individual FEs with STAs within its BSS or share the TXOP with a specific DAP based on the negotiation information / cooperation information.

[0355] Additionally, an AP that receives a cooperation request frame or cooperation response frame that includes and / or indicates UHR STA support information indicating whether it supports only UHR STAs may assume that the AP intends to perform FE only for UHR STAs. A particular AP that is aware of this may acquire a TXOP and assume the SAP role, and may preferentially (or based on a negotiated agreement) share the TXOP with UHR STA-supporting DAPs that do not require additional signaling and new procedures that may be required from the SAP for FE with existing devices in the DAP's BSS.

[0356] FIG. 26 illustrates an example of a C-TDMA procedure based on broadcast-based negotiation according to an embodiment of the present disclosure.

[0357] Referring to FIG. 26, before acquiring a TXOP, each AP whose role as a SAP or DAP has not been determined can broadcast a TF containing C-TDMA-related information (e.g., negotiation information / cooperation information) to participate in multi-AP cooperation, and receive TB PPDUs from corresponding APs. Through a broadcast-based negotiation procedure that exchanges TF and TB PPDU containing information for C-TDMA operation (e.g., negotiation information / cooperation information), APs that wish to operate in multi-AP cooperation and C-TDMA can obtain information about each other (e.g., negotiation information / cooperation information). Based on this information (e.g., negotiation information / cooperation information), an AP that acquires a TXOP and acts as a SAP can decide whether to first perform individual FEs with STAs within its BSS or share the TXOP with a specific DAP based on the negotiation information / cooperation information.

[0358] Additionally, an AP that has acquired UHR STA support information indicating whether it only supports UHR STAs can assume that the AP intends to perform FE only for UHR STAs. If a specific AP that is aware of this acquires a TXOP and acts as a SAP, it can preferentially (or based on a negotiated agreement) share the TXOP with UHR STA-supporting DAPs that do not require additional signaling or new procedures that may be required from the SAP for FE with existing devices in the DAP's BSS.

[0359] IV. Multi-AP grouping method based on negotiation procedure

[0360] FIG. 27 illustrates an example of a multi-AP set / group configuration based on negotiation / consultation for multiple cooperation schemes according to an embodiment of the present disclosure.

[0361] Among examples of multi-AP sets / groups that can be configured according to the above-described “I. Negotiation Procedure for Multi-AP Cooperation,” FIG. 27 illustrates an example of configuring multi-AP group information (or tables) for multiple coordination groups in order to use an appropriate multi-AP cooperation method when there is one or more multi-AP cooperation methods (or cooperation methods) supported by each AP. In the present disclosure, a cooperation group may correspond to a cooperation method and include one or more APs that support the corresponding cooperation method.

[0362] For example, in FIG. 27, a multi-AP set / group can be configured assuming the following situation:

[0363] - AP 1 and AP 4 can support all types of cooperation schemes (e.g. C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0364] - AP 2 and AP 3 can only support C-TDMA.

[0365] - AP 5 can only support C-SR.

[0366] - AP 6 only supports C-OFDMA.

[0367] Each AP can receive a beacon frame to determine the presence of neighboring APs, and can obtain specific information for multi-AP cooperation (e.g., cooperation information) by performing a negotiation procedure with an AP that wishes to perform multi-AP cooperation and / or has multi-AP cooperation capabilities. Each AP can ultimately generate multi-AP group information (or multi-AP table) for operating multi-AP cooperation based on the cooperation information. That is, each AP participating in multi-AP cooperation can individually and / or locally generate and manage multi-AP group information / table. For example, within the range of AP 1, AP 2, AP 3, AP 4, and AP 6 may exist as APs that wish to participate in multi-AP cooperation, and AP 1 can generate the “Multi-AP table of AP 1” as exemplified in FIG. 27 through a negotiation procedure with AP 2, AP 3, AP 4, and AP 6. Here, a multi-AP group ID can be assigned based on the cooperation method supported by the cooperating APs. The method of utilizing and assigning the multi-AP group ID may differ from that illustrated in FIG. 27, and is not limited thereto.

[0368] Also, when each AP supports more than one cooperation scheme, to reduce grouping overhead, separate group IDs may be assigned to indicate support for more than one cooperation scheme, or negotiation may be performed assuming support for all cooperation schemes or only support for a single cooperation scheme. For example, group ID #2 may be considered to indicate C-TDMA, group ID #3 may be considered to indicate C-OFDMA, group ID #0 may be considered to indicate all cooperation schemes, and group ID #1 may be considered to indicate C-SR. AP 1 may individually assign multiple AP IDs to the cooperating APs and may include the assigned multiple AP IDs in the (cooperation) response frame during the negotiation procedure and forward them to AP 2, AP 3, AP 4, and / or AP 6. Therefore, the negotiation procedure may generate multi-AP group information / table, and when AP 1 acquires a TXOP to act as a SAP, it may initiate a multi-AP selection procedure (or a multi-AP reselection procedure) with one or more APs belonging to the group of the multi-AP group information / table, depending on the intended cooperation procedure.

[0369] FIG. 28 illustrates an example of a negotiation / consultation-based multi-AP set / group configuration for a single cooperative scheme according to an embodiment of the present disclosure.

[0370] Among the examples of multi-AP sets / groups that can be configured according to the above-described “I. Negotiation Procedure for Multi-AP Cooperation,” FIG. 28 illustrates an example of configuring multi-AP group information (or table) for a single cooperation group by negotiating for the purpose of performing cooperation based on only one multi-AP cooperation method preferred by each AP, even if there is more than one multi-AP cooperation method supported by each AP.

[0371] For example, in FIG. 28, a multi-AP set / group can be configured assuming the following situation:

[0372] - AP 1 and AP 4 can support all types of cooperation schemes (e.g. C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX).

[0373] - AP 2 and AP 3 can only support C-TDMA.

[0374] - AP 5 can only support C-SR.

[0375] - AP 6 can only support C-OFDMA.

[0376] Each AP can receive a beacon frame to determine the presence of neighboring APs, and can obtain cooperation information for multi-AP cooperation by performing a cooperation procedure with an AP that wishes to perform multi-AP cooperation and / or has multi-AP cooperation capabilities. Each AP can ultimately generate multi-AP group information (or multi-AP table) for operating multi-AP cooperation based on the cooperation information. That is, each AP participating in multi-AP cooperation can individually generate and / or manage multi-AP group information / table. For example, within the range of AP 1, APs that wish to participate in multi-AP cooperation may include AP 2, AP 3, AP 4, and AP 6, and AP 1 can generate a “multi-AP table of AP 1” as illustrated in FIG. 28 through a negotiation procedure with AP 2, AP 3, AP 4, and AP 6.

[0377] Unlike the example in FIG. 27, AP 1 may perform the negotiation / negotiation process based on the multi-AP cooperation scheme (C-TDMA in this example) that AP 1 prefers to cooperate with and / or that the surrounding cooperating APs recommend / prefer more. That is, in addition to indicating the multi-AP cooperation scheme (or cooperation scheme) that it supports in the cooperation request frame and / or cooperation response frame, each AP may also propose the cooperation-based transmission scheme / multi-AP cooperation scheme (or cooperation scheme) that it wants to perform. Accordingly, the cooperation request frame and / or cooperation response frame may include information indicating the multi-AP cooperation scheme (or cooperation scheme) that the AP supports and / or indicating a proposal for the cooperation-based transmission scheme / multi-AP cooperation scheme (or cooperation scheme) that the AP wants to perform.

[0378] For example, AP 1 in FIG. 28 may perform negotiation procedures with APs 2, 3, 4, and 6 individually (or simultaneously), but may establish / complete multi-AP cooperation only with APs 2 and 3, with which it wishes to cooperate in C-TDMA. Similarly, AP 4 may perform negotiation procedures with APs 1, 3, and 5, but may prefer to operate in C-SR or may determine that C-SR operation with AP 5 is more advantageous, and may thus establish / complete multi-AP cooperation only with AP 5.

[0379] The above-described negotiation procedure can create a multi-AP group information / table, and when AP 1 or AP 2 or AP 3 acquires a TXOP and acts as a SAP, each AP can initiate a C-TDMA procedure with one or more other APs in its multi-AP group information / table. On the other hand, when AP 4 or AP 5 acquires a TXOP and acts as a SAP, each AP can initiate a C-SR procedure with one or more other APs in its multi-AP group information / table.

[0380] V. Multi-AP cooperative operation based on configured multi-AP groups / sets

[0381] FIG. 29 illustrates an example of an operation based on a multi-AP set / group configuration for multiple cooperation methods according to an embodiment of the present disclosure. FIG. 29 illustrates an example of a multi-AP cooperation operation using a multi-AP group / set that can be created through the multi-AP grouping method presented in FIG. 27.

[0382] Referring to FIG. 29, based on the multi-AP group information / table configured as in the example of FIG. 27, AP 1 can cooperate with AP 2 or AP 3 in C-TDMA, or cooperate with AP 4 in C-SR. For example, AP 1, which acquires TXOP and acts as a SAP, can transmit an invitation message to AP 4 to ask whether to participate in a C-SR operation or to start a C-SR operation in order to perform C-SR cooperation or C-SR cooperation-based transmission, and can receive a response message including information indicating acceptance or rejection thereof. If AP 4 transmits an acceptance message (or a response message including information indicating acceptance) for the C-SR operation, AP 1 can perform C-SR-based transmission with AP 4 (for example, AP 1 can perform individual frame exchange with STAs within the BSS through spatial reuse). After this, AP 1, which supports various multi-AP cooperation methods, may or may not additionally perform a separate multi-AP cooperation method if there is a remaining TXOP. For example, if the time required by AP 2 matches the remaining TXOP time of AP 1 (or, if the time required by AP 2 is equal to or less than the remaining TXOP time of AP 1), the C-TDMA operation to AP 2 may be performed. Therefore, in a multi-AP cooperation operation using a multi-AP group / set based on negotiation / consultation for a multi-AP cooperation method, multi-AP cooperation can be performed using various multi-AP cooperation methods depending on the scenario.

[0383] FIG. 30 illustrates an example of an operation based on a multi-AP set / group configuration for a single cooperation method according to an embodiment of the present disclosure. FIG. 30 illustrates an example of a multi-AP cooperation operation using a multi-AP group / set that can be created through the multi-AP grouping method presented in FIG. 28.

[0384] Referring to FIG. 30, based on the multi-AP group information / table configured as in the example of FIG. 28, AP 1 can cooperate with AP 2 or AP 3 in C-TDMA. AP 1, which acquires TXOP and acts as a SAP, can transmit a multi-AP selection frame (or a schedule announcement frame announcing a scheduled TXS) to AP 2 to ask whether it participates in the C-TDMA operation in order to cooperate in C-TDMA, and can receive a response frame thereto. If AP 2 transmits a response frame for the C-TDMA operation, AP 1 can allocate time (or an allocation period) to AP 2 using the scheduled time or a future TXS procedure (e.g., TXS for C-TDMA in FIG. 30). For example, AP 2 can perform individual frame exchanges with STAs within its BSS during the time / allocation period allocated by AP 1. Afterwards, AP 1 may or may not perform a separate individual frame exchange if there is a remaining TXOP. Additionally or alternatively, if the time required by AP 3 matches the remaining TXOP time of AP 1 (or, if the time required by AP 3 is equal to or less than the remaining TXOP time of AP 1), an additional C-TDMA operation (i.e., time allocation) to AP 3 may be performed. Therefore, in a multi-AP cooperation operation using a multi-AP set / group based on negotiation / negotiation for a single cooperation method, more than one C-TDMA operation may be performed depending on the scenario.

[0385] The present disclosure defines the negotiation procedure that must be performed between APs before multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX) in a multi-AP cooperation environment, and the information that each AP must exchange during the negotiation procedure. For example, APs that have successfully cooperated based on negotiation information / cooperation information can perform multi-AP operations (e.g., C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, J-TX). That is, after the APs exchange negotiation information / cooperation information during the negotiation process, they can ultimately generate multi-AP group information / table for operating multi-AP cooperation. Based on the multi-AP group information / table, the SAP can support cooperation-based transmission to a specific DAP (e.g., a DAP that only supports UHR non-AP STAs). Through this, the DAP can exchange frames with (UHR) non-AP STAs within its BSS within the allocated time or resources.

[0386] In addition, the present disclosure proposes a method for configuring and grouping multi-AP sets / groups among APs before operating in a multi-AP cooperation-based manner (or, cooperative manner) in a multi-AP cooperation environment. In addition, the present disclosure proposes an example of a multi-AP cooperation operation based on the configured multi-AP sets / groups. The multi-AP sets can be configured based on negotiation / negotiation for multiple cooperation schemes, or based on negotiation / negotiation for a single cooperation scheme. The multi-AP grouping method proposed in the present disclosure allows each AP to perform transmissions based on various multi-AP cooperation schemes, including C-TDMA, C-OFDMA, C-SR, C-BF, AP selection, and J-TX.

[0387] The technical features of the present disclosure described above can be applied to various devices and methods. For example, the technical features of the present disclosure described above can be performed / supported by the devices of FIG. 1 and / or FIG. 5. For example, the technical features of the present disclosure described above can be applied only to a portion of FIG. 1 and / or FIG. 5. For example, the technical features of the present disclosure described above can be implemented based on the processing chip (114, 124) of FIG. 1, or based on the processor (111, 121) and memory (112, 122) of FIG. 1, or based on the processor (510) and memory (520) of FIG. 5.

[0388] For example, the processor (121) and / or the processing chip (124) of FIG. 1 may be configured to execute instructions stored in the memory (122) to implement a method performed by an AP in the present disclosure. The method includes: performing a negotiation procedure for multi-AP operation with one or more neighboring APs; acquiring coordination information based on the negotiation procedure; setting coordination group information for the one or more neighboring APs based on the coordination information, wherein the coordination group information includes information on a corresponding coordination group to which each of the one or more neighboring APs belongs among one or more coordination groups, and each of the one or more coordination groups is associated with a corresponding coordination scheme; and performing the multi-AP operation based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation scheme associated with the cooperation group.

[0389] For example, the processor (111) of FIG. 1, the processing chip (114) and / or the processor (510) of FIG. 5 may be configured to execute instructions stored in the memory (112, 520) to implement a method performed by an STA in the present disclosure. The method includes: performing an association procedure with a first access point (AP); and performing frame exchange with the first AP in a resource cooperated between the first AP and the second AP based on a coordination scheme, wherein the coordination scheme is related to a coordination group to which the first AP and the second AP belong, and the coordination group is identified in coordination group information including information about a corresponding coordination group to which each of one or more neighboring APs including the second AP belongs, and the coordination group information is set based on coordination information acquired through a negotiation procedure for multi-AP operation performed by the AP with the one or more neighboring APs.

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

[0391] For example, the CRM may be the memory (122) of FIG. 1 and / or a separate external memory / storage medium / disk. The CRM may store commands for implementing a method performed by an AP in the present disclosure based on being executed by a processor (e.g., the processor (121) and / or the processing chip (124) of FIG. 1). The method includes: performing a negotiation procedure for multi-AP operation with one or more neighboring APs; acquiring coordination information based on the negotiation procedure; setting coordination group information for the one or more neighboring APs based on the coordination information, wherein the coordination group information includes information on a corresponding coordination group to which each of the one or more neighboring APs belongs among one or more coordination groups, and each of the one or more coordination groups is associated with a corresponding coordination scheme; And a step of performing the multi-AP operation based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation method associated with the cooperation group.

[0392] For example, the CRM may be the memory (112) of FIG. 1, the memory (520) of FIG. 5, and / or a separate external memory / storage medium / disk. The CRM may store commands for implementing a method performed by the STA in the present disclosure based on being executed by a processor (e.g., the processor (111) of FIG. 1, the processing chip (114), and / or the processor (510) of FIG. 5). The method may include: performing a connection procedure with a first AP (access point); And a step of performing frame exchange with the first AP in the cooperated resources between the first AP and the second AP based on a coordination scheme, wherein the coordination scheme is related to a cooperation group to which the first AP and the second AP belong, the cooperation group is identified in cooperation group information including information on a corresponding cooperation group to which each of one or more neighboring APs including the second AP belongs, and the cooperation group information is set based on cooperation information acquired through a negotiation procedure for multi-AP operation performed by the AP with the one or more neighboring APs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0409] The present disclosure may have various advantageous effects.

[0410] For example, the present disclosure proposes multi-AP table / cooperation group information that can be ultimately generated through a negotiation process between APs in a multi-AP cooperation environment, and / or a grouping method among multiple APs through a negotiation process. Based on the multi-AP table / cooperation group information and / or the multi-AP group, a SAP (sharing AP) can support cooperation-based transmission to a specific DAP (shared AP).

[0411] The beneficial effects that can be achieved through specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, various technical effects may be understood and / or derived from the present disclosure by those skilled in the art. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure.

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

Claims

1. A step in which an AP (access point) performs a negotiation procedure for multi-AP operation with one or more neighboring APs; A step in which the above AP obtains coordination information based on the above negotiation procedure; A step in which the above AP sets coordination group information for one or more neighboring APs based on the cooperation information; The above cooperation group information includes information about a corresponding cooperation group to which each of the one or more neighboring APs belongs among one or more cooperation groups, Each of said one or more cooperation groups is associated with a corresponding coordination scheme; and A method comprising the step of performing the multi-AP operation based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation method associated with the cooperation group.

2. In claim 1, the steps of performing the negotiation procedure are: a step of the AP transmitting a cooperation request frame to one or more neighboring APs; and The step of the AP receiving a cooperation response frame including information indicating acceptance or rejection of the cooperation request frame from one or more neighboring APs, A method wherein the above cooperation information is included in at least one of the cooperation request frame or the cooperation response frame.

3. A method according to claim 1, wherein the cooperation information includes at least one of information on an operating channel, information on an operating bandwidth, section information on a transmission opportunity (TXOP), information on low-latency traffic, or information on whether only STAs of the latest wireless local area network (WLAN) version are supported.

4. A method according to claim 3, wherein the cooperation information further includes at least one of an identifier of a cooperation group, an identifier of an AP within the cooperation group, or information on a cooperation method.

5. In claim 3, information on whether only the STA of the latest wireless LAN version is supported includes a 1-bit field, The above 1-bit field set to 0 indicates that only the latest wireless LAN version STA is supported, A method in which the above 1-bit field set to 1 indicates that STA of the latest wireless LAN version and STA of a previous wireless LAN version are supported.

6. In claim 1, the step of the AP detecting a management frame or a beacon frame transmitted from one or more neighboring APs; and A method comprising a step of identifying one or more neighboring APs with which the AP performs a negotiation procedure for the multi-AP operation, based on the management frame or the beacon frame.

7. In claim 6, the management frame or the beacon frame includes a 1-bit field, The above 1-bit field set to 0 indicates that the AP participates in the above multi-AP operation, A method in which the above 1-bit field set to 1 indicates that the corresponding AP does not participate in the above multi-AP operation.

8. A method according to claim 1, wherein the information about the corresponding cooperative group to which each of the one or more neighboring APs belongs includes at least one of an identifier of the cooperative group to which each of the one or more neighboring APs belongs, an identifier of each of the one or more neighboring APs within the cooperative group, or a BSS (basic service set) identifier of each of the one or more neighboring APs.

9. A method according to claim 1, wherein the cooperative method comprises at least one of coordinated time division multiple access (C-TDMA), coordinated orthogonal frequency division multiple access (C-OFDMA), coordinated spatial reuse (C-SR), coordinated beamforming (C-BF), AP selection, or joint transmission (J-TX).

10. A method according to claim 1, wherein the step of performing the multi-AP operation based on the cooperation method with the neighboring AP includes the step of the AP performing frame exchange with an STA connected to the AP in resources cooperated with the neighboring AP based on the cooperation method.

11. In a wireless local area network (LAN) system, at the AP (access point), Transmitter and receiver; memory; and At least one processor functionally coupled with the transceiver and the memory, The above memory stores instructions for performing operations based on being executed by the at least one processor, the operations being: An operation that performs a negotiation procedure for multi-AP operation with one or more neighboring APs; An action to obtain coordination information based on the above negotiation procedure; An operation in which the above AP sets coordination group information for one or more neighboring APs based on the cooperation information; The above cooperation group information includes information about a corresponding cooperation group to which each of the one or more neighboring APs belongs among one or more cooperation groups, Each of said one or more cooperation groups is associated with a corresponding coordination scheme; and An AP including an operation for performing the multi-AP operation based on a cooperation method associated with a neighboring AP belonging to a cooperation group identified in the cooperation group information and the cooperation group.

12. In a device configured to operate in a wireless local area network (LAN) system, at least one processor; and comprising at least one memory functionally coupled with at least one processor; The at least one memory stores instructions that perform operations based on being executed by the at least one processor, the operations comprising: An operation that performs a negotiation procedure for multi-AP operation with one or more neighboring APs; An action to obtain coordination information based on the above negotiation procedure; An operation in which the above AP sets coordination group information for one or more neighboring APs based on the cooperation information; The above cooperation group information includes information about a corresponding cooperation group to which each of the one or more neighboring APs belongs among one or more cooperation groups, Each of said one or more cooperation groups is associated with a corresponding coordination scheme; and A device including an operation for performing the multi-AP operation based on a neighboring AP belonging to a cooperation group identified in the cooperation group information and a cooperation method associated with the cooperation group.

13. A non-transitory computer readable medium (CRM) storing program code implementing instructions that perform operations based on being executed by at least one processor, said operations comprising: An operation that performs a negotiation procedure for multi-AP operation with one or more neighboring APs; An action to obtain coordination information based on the above negotiation procedure; An operation in which the above AP sets coordination group information for one or more neighboring APs based on the cooperation information; The above cooperation group information includes information about a corresponding cooperation group to which each of the one or more neighboring APs belongs among one or more cooperation groups, Each of said one or more cooperation groups is associated with a corresponding coordination scheme; and A CRM including an operation in which the above AP performs the multi-AP operation based on a neighboring AP belonging to a collaboration group identified in the above collaboration group information and a collaboration method associated with the collaboration group.

14. A step in which STA (station) performs a connection procedure with the first AP (access point); and The STA comprises a step of performing frame exchange with the first AP in the coordinated resources between the first AP and the second AP based on a coordination scheme, The above cooperation method is related to the cooperation group to which the first AP and the second AP belong, The above cooperative group is identified in the cooperative group information including information about the corresponding cooperative group to which each of one or more neighboring APs including the second AP belongs, A method in which the above cooperation group information is set based on cooperation information obtained through a negotiation procedure for multi-AP operation performed by the AP with one or more neighboring APs.

15. In a wireless local area network (LAN) system, at a STA (station), Transmitter and receiver; memory; and At least one processor functionally coupled with the transceiver and the memory, The above memory stores instructions for performing operations based on being executed by the at least one processor, the operations being: An operation in which a STA (station) performs a connection procedure with a first AP (access point); and An operation for performing frame exchange with the first AP on the coordinated resources between the first AP and the second AP based on a coordination scheme, The above cooperation method is related to the cooperation group to which the first AP and the second AP belong, The above cooperative group is identified in the cooperative group information including information about the corresponding cooperative group to which each of one or more neighboring APs including the second AP belongs, The above cooperation group information is set by the STA based on cooperation information obtained through a negotiation procedure for multi-AP operation performed by the AP with one or more neighboring APs.

16. In claim 15, the cooperation information is an STA including at least one of information on an operating channel, information on an operating bandwidth, section information on a transmission opportunity (TXOP), information on low-latency traffic, or information on whether only STAs of the latest wireless local area network (WLAN) version are supported.

17. In claim 16, the cooperation information is a STA that further includes at least one of an identifier of a cooperation group, an identifier of an AP within the cooperation group, or information on a cooperation method.

18. In claim 16, information on whether only the STA of the latest wireless LAN version is supported includes a 1-bit field, The above 1-bit field set to 0 indicates that only the latest wireless LAN version STA is supported, The above 1-bit field set to 1 indicates that the STA supports STAs of the latest wireless LAN version and STAs of previous wireless LAN versions.

19. In claim 15, the STA includes information about a corresponding cooperative group to which each of the one or more neighboring APs belongs, including at least one of an identifier of a cooperative group to which each of the one or more neighboring APs belongs, an identifier of each of the one or more neighboring APs within the cooperative group, or a BSS (basic service set) identifier of each of the one or more neighboring APs.

20. In claim 15, the cooperative method is an STA including at least one of coordinated time division multiple access (C-TDMA), coordinated orthogonal frequency division multiple access (C-OFDMA), coordinated spatial reuse (C-SR), coordinated beamforming (C-BF), AP selection, or joint transmission (J-TX).

Images