Resource reporting in multi-ap coordination in wireless lan systems

Abstract

The present disclosure relates to resource reporting in multi-AP coordination in a wireless LAN system. According to an embodiment of the present disclosure, a method performed by a first AP in a wireless LAN system includes the steps of: performing a negotiation procedure for multi-AP coordination with one or more APs; obtaining a configuration of a multi-AP set including the one or more APs based on the negotiation procedure; updating at least one resource configuration in resource information about the first AP transmitted by the first AP to a second AP in the multi-AP set during the negotiation procedure after obtaining the configuration of the multi-AP set; and transmitting a resource report frame including information about the updated at least one resource configuration to the second AP.

Description

Technical Field

[0001] This disclosure relates to resource reporting in multi-AP coordination in a wireless local area network (WLAN) system. Background Technology

[0002] Next-generation Wi-Fi (e.g., IEEE 802.11be and / or subsequent standards) aims to support ultra-reliable signaling to STAs and is considering various technologies to support high throughput, low latency, and extended range. For example, an AP can perform a negotiation process for multi-AP coordination and execute multi-AP operations based on negotiation / coordination / resource information obtained during the negotiation process. In this case, the negotiation / coordination / resource information provided by the AP during the negotiation process may change after the negotiation process is executed. Summary of the Invention

[0003] Technical issues

[0004] One aspect of this disclosure is intended to provide a method and apparatus for resource reporting in multi-AP coordination within a WLAN system.

[0005] Technical solution

[0006] According to an embodiment of the present disclosure, a method performed by a first AP includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, updating at least one resource configuration in the resource information of the first AP sent by the first AP to a second AP in the multi-AP set during the negotiation process; and sending a resource report frame including information on the updated at least one resource configuration to the second AP.

[0007] According to one embodiment of this disclosure, a method performed by a second AP includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, receiving a resource report frame from a first AP in the multi-AP set, including information on at least one resource configuration; and updating the at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP during the negotiation process.

[0008] In various embodiments, an apparatus for implementing the above method is provided.

[0009] Beneficial effects

[0010] This disclosure can have various beneficial effects.

[0011] For example, according to embodiments of this disclosure, an AP can deliver frames (or resource report frames) for resource reporting unsolicited / separately without requiring a separate request from an AP in a coordination relationship for changes to information related to multi-AP coordination (e.g., negotiation information / coordination information / resource information). In this case, an AP in a coordination relationship that has received the unsolicited frame for resource reporting can update the corresponding AP's multi-AP coordination information (or resource information). Such information transmitted for and / or based on multi-AP coordination (e.g., negotiation information / coordination information / resource information) can later be used for scheduling multi-AP coordination operations of an AP used as an SAP.

[0012] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, various technical effects can exist that can be understood and / or obtained by those skilled in the art from this disclosure. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but can include various effects that can be understood or obtained from the technical features of this disclosure. Attached Figure Description

[0013] Figure 1 Examples of transmitting and / or receiving devices of this disclosure are shown.

[0014] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0015] Figure 3 This illustrates a typical link establishment process.

[0016] Figure 4 An example of multi-link (ML) is shown.

[0017] Figure 5 Examples of modifications to the transmitting and / or receiving apparatus of this disclosure are shown.

[0018] Figure 6 Examples of Physical Protocol Data Units or Physical Layer (PHY) Protocol Data Units (PPDUs) transmitted / received by the STA of this disclosure are shown.

[0019] Figure 7 An example of the layout for a resource unit (RU) for a 20 MHz PPDU is shown.

[0020] Figure 8 An example of the layout of a resource unit (RU) for a 40 MHz PPDU is shown.

[0021] Figure 9 An example of the layout of a resource unit (RU) for an 80 MHz PPDU is shown.

[0022] Figure 10 This demonstrates the operations related to UL-MU.

[0023] Figure 11 Examples of channels used / supported / defined within the 2.4 GHz band are shown.

[0024] Figure 12 Examples of channels used / supported / defined within the 5 GHz band.

[0025] Figure 13 Examples of channels used, supported, and defined within the 6 GHz band are provided.

[0026] Figure 14 This shows the trigger frame format. This trigger frame format can also be referred to as the structure of the trigger frame.

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

[0028] Figure 16 An example of coordinating time division multiple access (Co-TDMA) between APs is shown.

[0029] Figure 17 An example of a peer-to-peer negotiation process according to an embodiment of this disclosure is shown.

[0030] Figure 18 An example of a broadcast-based negotiation process according to an embodiment of this disclosure is shown.

[0031] Figure 19 An example of a method performed by a first AP according to an embodiment of the present disclosure is shown.

[0032] Figure 20 An example of a method performed by a second AP according to an embodiment of this disclosure is shown.

[0033] Figure 21 An example of an unsolicited resource reporting process using QoS data / empty frames is shown according to an embodiment of this disclosure.

[0034] Figure 22 An example of an unsolicited resource reporting process using MU-RTS TF according to an embodiment of this disclosure is shown.

[0035] Figure 23 An example of an unsolicited resource reporting process using management frames according to an embodiment of this disclosure is shown. Detailed Implementation

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

[0037] The forward slash ( / ) or comma used in this disclosure can represent "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0038] In this disclosure, "at least one of A and B" can mean "only A", "only B" or "both A and B". Additionally, in this disclosure, the expression "at least one of A or B" or "at least one of A and / or B" can be interpreted as "at least one of A and B".

[0039] The brackets used in this disclosure may indicate "for example". Specifically, when indicated as "control information (UHR-signal field)", it may indicate that the "UHR-signal field" is cited as an example of "control information". In other words, the "control information" of this disclosure is not limited to the "UHR-signal field", and the "UHR-signal field" may also be cited as an example of "control information". Furthermore, when indicated as "control information (i.e., UHR-signal field)", it may also indicate that the "UHR-signal field" is cited as an example of "control information".

[0040] Furthermore, as used in this disclosure, "a" can mean "at least one" or "one or more". Additionally, terms ending in "(s)" can mean "at least one" or "one or more".

[0041] Furthermore, as used in this disclosure, the expressions “based on”, “on the basis of”, or “according to” mean “at least partially based on”, and not “based on only”.

[0042] The technical features described individually in one of the accompanying drawings of this disclosure may be implemented individually or simultaneously.

[0043] The following examples of this disclosure can be applied to various wireless communication systems. For example, the following examples of this disclosure can be applied to wireless local area network (WLAN) systems. For example, this disclosure can be applied to the IEEE 802.11 a / g / n / ac / ax / be / bn standards. Furthermore, the examples of this disclosure can also be applied to next-generation wireless LAN standards such as enhanced Ultra High Reliability (UHR) standards or IEEE 802.11 bn. Additionally, the examples of this disclosure can be applied to new WLAN standards enhanced from EHT standards or IEEE 802.11be standards. Furthermore, the examples of this disclosure can be applied to mobile communication systems. For example, it can be applied to mobile communication systems based on Long Term Evolution (LTE), which relies on 3GPP standards and is based on LTE evolution. Furthermore, the examples of this disclosure can be applied to communication systems based on the 5G NR standard of 3GPP standards.

[0044] In the following text, for the purpose of describing the technical features of this disclosure, technical features applicable to this disclosure will be described.

[0045] Figure 1 Examples of transmitting and / or receiving devices of this disclosure are shown.

[0046] exist Figure 1 In the example, the various technical features described below can be implemented. Figure 1 At least one station (STA) is involved. For example, STA 110 and 120 of this disclosure may also be referred to by various terms such as mobile terminal, wireless device, wireless transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or simply user. STA 110 and 120 of this disclosure may also be referred to by various terms such as network, base station, Node B, access point (AP), repeater, router, relay, etc. STA 110 and 120 of this disclosure may also be referred to by various names such as receiving device, transmitting device, receiving STA, transmitting STA, receiving device, transmitting device, etc.

[0047] For example, STA 110 and 120 can be used as AP or non-AP. That is, STA 110 and 120 of this disclosure can be used as AP and / or non-AP. In this disclosure, AP can be indicated as AP STA.

[0048] In addition to the IEEE 802.11 standard, the STAs 110 and 120 of this disclosure can together support various communication standards. For example, they can support communication standards based on 3GPP standards (e.g., LTE, LTE-A, 5G NR standards). Furthermore, the STAs of this disclosure can be implemented in various devices such as mobile phones, vehicles, and personal computers. Additionally, the STAs of this disclosure can support communication for various communication services such as voice calls, video calls, data communication, and autonomous driving.

[0049] The STA 110 and 120 disclosed herein may include media access control (MAC) conforming to the IEEE 802.11 standard and a physical layer interface for radio media.

[0050] The following will refer to Figure 1 The subgraph (a) is used to describe STA 110 and 120.

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

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

[0053] For example, the first STA 110 can perform the operations expected by the AP. For example, the AP's processor 111 can receive signals via transceiver 113, process receive (RX) signals, generate transmit (TX) signals, and provide control over signal transmission. The AP's memory 112 can store signals received via transceiver 113 (e.g., RX signals) and can store signals to be transmitted via transceiver 113 (e.g., TX signals).

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

[0055] For example, a non-AP STA processor 121 can receive signals via transceiver 123, process RX signals, generate TX signals, and provide control over signal transmission. A non-AP STA memory 122 can store signals received via transceiver 123 (e.g., RX signals) and can store signals to be transmitted via transceiver 123 (e.g., TX signals).

[0056] For example, the operation of a device designated as an AP in the disclosure described below can be performed in either the first STA 110 or the second STA 120. For instance, if the first STA 110 is an AP, the operation of the device designated as an AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 112 of the first STA 110. Similarly, if the second STA 120 is an AP, the operation of the device designated as an AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Furthermore, control information related to the operation of the AP or the AP's TX / RX signals can be stored in the memory 122 of the second STA 120.

[0057] For example, in the disclosure described below, the operation of a device indicated as a non-AP (or user STA) can be performed in either the first STA 110 or the second STA 120. For instance, if the second STA 120 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 121 of the second STA 120, and related signals can be transmitted or received via a transceiver 123 controlled by the processor 121 of the second STA 120. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 122 of the second STA 120. Similarly, if the first STA 110 is a non-AP, the operation of the device indicated as a non-AP can be controlled by the processor 111 of the first STA 110, and related signals can be transmitted or received via a transceiver 113 controlled by the processor 111 of the first STA 110. Additionally, control information related to the operation of a non-AP or non-AP TX / RX signals can be stored in the memory 112 of the first STA 110.

[0058] In the disclosure described below, devices referred to 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., may implicitly refer to Figure 1 STAs 110 and 120. For example, devices indicated as (but without specific labels) (transmitting / receiving) STA, first STA, second STA, STA1, STA2, AP, first AP, second AP, AP1, AP2, (transmitting / receiving) terminal, (transmitting / receiving) device, (transmitting / receiving) equipment, network, etc., can implicitly refer to... Figure 1 STAs 110 and 120. For example, in the following example, the operation of various STA transmit / receive signals (e.g., PPDU) can be... Figure 1 The operation is performed in transceivers 113 and 123. Additionally, in the following examples, various STAs can generate TX / RX signals or perform data processing and calculations on TX / RX signals in advance. Figure 1 The operations are executed in processors 111 and 121. Examples of operations for generating TX / RX signals or performing prior data processing and calculations may include: 1) operations to determine / obtain / configure / calculate / decode / encode bit information of subfields (SIG, STF, LTF, data) included in the PPDU; 2) operations to determine / configure / obtain time resources or frequency resources (e.g., subcarrier resources) for the subfields (SIG, STF, LTF, data) included in the PPDU; 3) operations to determine / configure / obtain specific sequences (e.g., pilot sequences, STF / LTF sequences, additional sequences applied to SIG) for the subfields (SIG, STF, LTF, data) included in the PPDU; 4) power control operations and / or power-saving operations applied to the STA; and 5) operations related to the determination / obtaining / configuration / decoding / encoding of the ACK signal. Additionally, in the following examples, various information used by various STAs to determine / obtain / configure / calculate / encode / decode the TX / RX signal (e.g., information related to fields / subfields / control fields / parameters / power, etc.) may be stored in the STA. Figure 1 In memory 112 and 122.

[0059] Figure 1 The aforementioned device / STA in subgraph (a) can be as follows Figure 1 The subgraph (b) is modified as shown below. In the following text, the modifications will be based on... Figure 1 The subgraph (b) is used to describe STA 110 and STA 120 of this disclosure.

[0060] For example, Figure 1The transceivers 113 and 123 shown in subgraph (b) can perform operations with Figure 1 The transceiver shown in sub-diagram (a) has the same function as the aforementioned transceiver. For example, Figure 1 The processing chips 114 and 124 shown in sub-figure (b) may include processors 111 and 121 and memories 112 and 122. Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (b) can perform operations related to Figure 1 The processors 111 and 121 and the memories 112 and 122 shown in sub-figure (a) have the same functions.

[0061] The mobile terminal, wireless device, wireless transceiver 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 unit, transmitting unit, receiving STA, transmitting STA, receiving device, transmitting device, receiving device and / or transmitting device described below may mean Figure 1 The STA 110 and 120 shown in subgraphs (a) / (b) may mean, or Figure 1 The processing chips 114 and 124 are shown in sub-figure (b). That is, the technical features of this disclosure can be... Figure 1 It can be performed in STA 110 and 120 as shown in subgraphs (a) / (b), or it can be performed only in Figure 1 The processing chips 114 and 124 shown in sub-diagram (b) are executed Figure 1 Transceivers 113 and 123 are shown in sub-diagrams (a) and (b). For example, the technical features of transmitting control signals by a STA can be understood as being achieved through... Figure 1 The transceiver 113 illustrated in subgraphs (a) / (b) transmits in Figure 1 The technical features of the control signals generated in processors 111 and 121 are illustrated in sub-figures (a) and (b). Alternatively, the technical features of the STA transmitting control signals can be understood as follows: Figure 1 The technical features of generating control signals to be transmitted to transceivers 113 and 123 in processing chips 114 and 124 are shown in sub-figure (b).

[0062] For example, the technical characteristics of receiving STA control signals can be understood as through... Figure 1 The technical features of transceivers 113 and 123 receiving control signals are shown in sub-figure (a). Alternatively, the technical features of receiving STA control signals can be understood as being achieved through... Figure 1 Processors 111 and 121 shown in subgraph (a) obtain Figure 1The technical features of the control signals received in transceivers 113 and 123 shown in sub-figure (a) are illustrated. Alternatively, the technical features of receiving control signals by the STA can be understood as being achieved through... Figure 1 The processing chips 114 and 124 shown in sub-figure (b) obtain Figure 1 Technical features of the control signals received in transceivers 113 and 123 as shown in sub-figure (b).

[0063] refer to Figure 1 Subgraph (b), software codes 115 and 125 can be included in memories 112 and 122. Software codes 115 and 125 can include instructions for controlling the operation of processors 111 and 121. Software codes 115 and 125 can be included in various programming languages.

[0064] Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. The processor may be an application processor (AP). For example, Figure 1 The processors 111 and 121 or processing chips 114 and 124 may include at least one of the following: a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modulator and demodulator (modem). For example, Figure 1 The processors 111 and 121 or the processor chips 114 and 124 may be SNAPDRAGON® series processors manufactured by Qualcomm®, EXYNOS® series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIO® series processors manufactured by MediaTek®, ATOM® series processors manufactured by Intel®, or processors enhanced from these processors.

[0065] In this disclosure, an uplink can mean a link used for communication from a non-AP STA to an AP STA, and uplink PPDUs / packets / signals, etc., can be transmitted via the uplink. Similarly, in this disclosure, a downlink can mean a link used for communication from an AP STA to a non-AP STA, and downlink PPDUs / packets / signals, etc., can be transmitted via the downlink.

[0066] Figure 2 This is a conceptual diagram illustrating the structure of a wireless local area network (WLAN).

[0067] Figure 2 The upper part illustrates the structure of the Infrastructure Basic Services Set (BSS) of the Institute of Electrical and Electronics Engineers (IEEE) 802.11.

[0068] refer to Figure 2 The upper part of the wireless LAN system may include one or more infrastructure BSS 200 and 205 (hereinafter referred to as BSS). BSS 200 and 205, as a set of APs and STAs (e.g., access point (AP) 225 and station (STA1) 200-1) that have successfully synchronized to communicate with each other, are not concepts indicating a specific area. BSS 205 may include one or more STAs 205-1 and 205-2 that can join an AP 230.

[0069] A BSS may include at least one STA, an AP that provides distributed services, and a distributed system (DS) 210 that connects multiple APs.

[0070] Distributed system 210 can implement an Extended Service Set (ESS) 240 that is expanded by connecting multiple BSSs 200 and 205. ESS 240 can be used as a term to refer to a network configured by connecting one or more APs 225 or 230 via distributed system 210. APs included in an ESS 240 can have the same Service Set Identifier (SSID).

[0071] Portal 220 can be used as a bridge to connect a wireless LAN network (IEEE 802.11) to another network (e.g., 802.X).

[0072] exist Figure 2 The BSS shown at the top allows for networking between APs 225 and 230, as well as between APs 225 and 230 and STAs 200-1, 205-1, and 205-2. However, it also allows for networking between STAs to perform communication even without APs 225 and 230. Networks that enable communication between STAs by configuring networks even without APs 225 and 230 are defined as self-organizing networks or Independent Basic Service Sets (IBSS).

[0073] Figure 2 The lower part illustrates a concept diagram, exemplifying IBSS.

[0074] refer to Figure 2 The lower part of the IBSS is a BSS that operates in a self-organizing mode. Since the IBSS does not include access points (APs), there is no centralized management entity performing management functions at the center. That is, in the IBSS, STAs 250-1, 250-2, 250-3, 255-4, and 255-5 are managed in a distributed manner. In the IBSS, all STAs 250-1, 250-2, 250-3, 255-4, and 255-5 can be composed of mobile STAs, and access to DS to form a self-contained network is not permitted.

[0075] Figure 3 This example illustrates the typical link establishment process.

[0076] In S310, the STA can perform network discovery operations. Network discovery operations can include scanning operations by the STA. That is, in order to access a network, the STA needs to discover participating networks. The process of identifying compatible networks before joining a wireless network and identifying networks existing in a specific area is called scanning. Scanning methods include active scanning and passive scanning.

[0077] Figure 3 An example of network discovery operations including active scanning is provided. In active scanning, the STA performing the scan sends a probe request frame and waits for a response to the probe request frame in order to identify which APs are present in the vicinity while moving to a channel. The responder sends a probe response frame to the STA that sent the probe request frame as a response to the probe request frame. Here, the responder can be the STA that sent the last beacon frame in the BSS of the channel being scanned. In the BSS, the AP is the responder because it sends the beacon frame. In the IBSS, the responder is not fixed because the STAs in the IBSS take turns sending beacon frames. For example, when an STA sends a probe request frame via channel 1 and receives a probe response frame via channel 1, the STA can store the BSS-related information included in the received probe response frame, can move to the next channel (e.g., channel 2), and can perform a scan in the same way (e.g., sending a probe request and receiving a probe response via channel 2).

[0078] Although Figure 3 As not shown, scanning can be performed using a passive scanning method. In passive scanning, the STA performing the scan can wait for beacon frames while moving to a channel. Beacon frames are one of the management frames in IEEE 802.11 and are periodically sent to indicate the presence of a wireless network and enable the STA performing the scan to find and join the wireless network. In a BSS, the AP periodically sends beacon frames. In an IBSS, STAs in the IBSS take turns sending beacon frames. Upon receiving a beacon frame, the STA performing the scan stores information about the BSS included in the beacon frame and records the beacon frame information for each channel, while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, can move to the next channel, and can perform a scan on the next channel using the same method.

[0079] After network discovery, the STA can perform authentication processing in S320. This authentication processing can be referred to as the first authentication processing to clearly distinguish it from the subsequent security establishment operation in S340. The authentication processing in S320 may include the STA sending an authentication request frame to the AP and the AP sending an authentication response frame to the STA in response. The authentication frame used for the authentication request / response is a management frame.

[0080] An authentication frame may include information about the authentication algorithm number, authentication transaction sequence number, status code, challenge text, robust security network (RSN), and finite cyclic group.

[0081] The STA can send an authentication request frame to the AP. The AP can determine whether to allow the STA's authentication based on the information included in the received authentication request frame. The AP can then provide the authentication processing result to the STA via an authentication response frame.

[0082] When a STA is successfully authenticated, it can perform association processing in S330. Association processing includes the STA sending an association request frame to the AP, and the AP responding by sending an association response frame to the STA. For example, the association request frame may include information about various capabilities, beacon listening interval, service set identifier (SSID), supported rates, supported channels, RSN, mobile domain, supported operation classes, service indication map (TIM) broadcast request, and interoperability service capabilities. Similarly, the association response frame may include information about various capabilities, status codes, association ID (AID), supported rates, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), received signal-to-noise ratio indicator (RSNI), mobile domain, timeout interval (association recovery time), overlapping BSS scan parameters, TIM broadcast response, and QoS map.

[0083] In the S340, the STA can perform security establishment processes. The security establishment processes in the S340 may include the process of establishing a private key via a four-way handshake (e.g., via Extensible Authentication Protocol (EAPOL) frames over the LAN).

[0084] Figure 4 An example of multi-link (ML) is shown.

[0085] like Figure 4 As illustrated, multiple multi-link devices (MLDs) can communicate via a remote link. MLDs can be classified as AP MLDs, which include multiple AP STAs, and non-AP MLDs, which include multiple non-AP STAs. That is, an AP MLD may include affiliated APs (i.e., AP STAs), and a non-AP MLD may include affiliated STAs (i.e., non-AP STAs or user STAs).

[0086] Multiple links can include a first link and a second link, and different channel / subchannel / frequency resources can be allocated to the first link and the second link. The first and second multiple links can be identified by a 4-bit (or other n-bit) link ID. The first and second links can be configured in the same 2.4 GHz, 5 GHz, or 6 GHz frequency band. Alternatively, the first and second links can be configured in different frequency bands.

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

[0088] exist Figure 4 In the example, AP1 can initiate the multi-link establishment process (ML establishment process) by sending an association request frame to a non-AP STA1. Figure 4 In the example, a non-AP STA1 can send an association response frame in response to an association request frame. Figure 4 The individual APs shown (e.g., AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The APs shown are the same, and Figure 4 The various non-APs shown (e.g., non-AP1 / 2 / 3) can be compared with... Figure 1 and / or Figure 2 The STAs shown are the same (i.e., user STAs or non-AP STAs).

[0089] The specific features of this disclosure are not limited to Figure 4 The specific characteristics are as follows. That is, the number of links can be defined in various ways, and multiple links can be defined in at least one frequency band in various ways.

[0090] Figure 5 Examples of modifications to the transmitting and / or receiving apparatus of this disclosure are shown.

[0091] Figures 1 to 4The devices shown (e.g., AP STA, non-AP STA) can be as follows: Figure 5 The modifications shown are as follows. Figure 5 The 530 transceiver can be used with Figure 1 The transceivers 113 and 123 are the same. Figure 5 The transceiver 530 may include a receiver and a transmitter.

[0092] Figure 5 The processor 510 can be used with Figure 1 The processors 111 and 121 are the same. Alternatively, Figure 5 The processor 510 can be used with Figure 1 The processing chips 114 and 124 are the same.

[0093] Figure 5 The memory 150 can be connected with Figure 1 The memory modules 112 and 122 are identical. Alternatively, Figure 5 The memory 150 can be with Figure 1 The memory 112 and 122 are different separate external memories.

[0094] Reference Figure 5 The power management module 511 manages the power used by the processor 510 and / or transceiver 530. The battery 512 supplies power to the power management module 511. The display 513 outputs the results processed by the processor 510. The keypad 514 receives input to be used by the processor 510. The keypad 514 may be displayed on the display 513. The SIM card 515 may be an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and its associated key, which are used to identify and authenticate the user in mobile devices such as mobile phones and computers.

[0095] Reference Figure 5 The speaker (540) can output sound-related results processed by the processor 510. The microphone (541) can receive sound-related inputs that will be used by the processor 510.

[0096] Figure 6 Examples of Physical Protocol Data Units or Physical Layer (PHY) Protocol Data Units (PPDUs) transmitted / received by the STA of this disclosure are shown.

[0097] The STA (e.g., AP STA, non-AP STA, AP MLD, non-AP MLD) disclosed herein can send and / or receive. Figure 6 The PPDU described in this disclosure may have, for example... Figure 6The structure is as follows. Furthermore, the PPDU described in this disclosure may be referred to by various names, such as transmit PPDU, receive PPDU, type 1 or type N PPDU, etc. The PPDU described in this disclosure can be used in WLAN systems defined according to IEEE 802.11bn and / or in next-generation WLAN systems that improve upon IEEE 802.11bn.

[0098] Figure 6 The PPDU can encompass various PPDU types used in UHR systems. For example, Figure 6 Examples can be used for at least one of the following modes related to channel detection: single-user (SU) mode / type / transmission, multi-user (MU) mode / type / transmission, and null packet (NDP) mode / type / transmission. For example, if Figure 6 If the example involves NDP, the data fields shown can be omitted. Figure 6 The PPDU is used in trigger-based (TB) mode and can be omitted. Figure 6 The UHR-SIG. In other words, a STA that has received a trigger frame for uplink-MU (UL-MU) communication can send a UHR-SIG. Figure 6 The UHR-SIG PPDU is omitted in the example.

[0099] exist Figure 6 In this context, L-STF or UHR-LTF can be referred to as a preamble or physical preamble, and can be generated / transmitted / received / acquired / decoded at the physical layer (including in the transmit / receive STA).

[0100] Figure 6 The blocks illustrated can be referred to as fields / subfields / signals, etc. These fields / subfields / signals can be named as Traditional Short Training Field (L-STF), Traditional Long Training Field (L-LTF), Traditional Signal (L-SIG), Repeated L-SIG (RL-SIG), Universal Signal (U-SIG), UHR Signal (UHR-SIG), etc., such as... Figure 6 exemplified.

[0101] Figure 6The subcarrier spacing of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be determined to be 312.5 kHz, and the subcarrier spacing of the UHR-STF, UHR-LTF, and Data fields can be determined to be 78.125 kHz. That is, the tone index (or subcarrier index) of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG fields can be represented in units of 312.5 kHz, and the tone index (or subcarrier index) of the UHR-STF, UHR-LTF, and Data fields can be represented in units of 78.125 kHz.

[0102] exist Figure 6 In the PPDU, the L-LTF and L-STF can be the same as those in the conventional domain (e.g., non-HT LTF and non-HT STF defined in conventional WLAN standards).

[0103] Figure 6 The L-SIG field can include, for example, 24 bits of bit information. For instance, the 24 bits could 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 could include information related to the length or duration of the PPDU. For example, the 12-bit length field can be determined based on the type of PPDU. For example, when the PPDU is a Non-High Throughput (HT), High Throughput (HT), Very High Throughput (VHT) PPDU, Extremely High Throughput (EHT) PPDU, or UHR PPDU, the value of the length field can be determined to be a multiple of 3. For example, when the PPDU is an HE PPDU, the length field can be determined to be a multiple of 3 + 1 or a multiple of 3 + 2. In other words, for non-HT, HT, VHT, EHT, or UHR PPDUs, the length field value can be set to a multiple of 3, and for high-efficiency (HE) PPDUs, the length field value can be set to either a multiple of 3 + 1 or a multiple of 3 + 2. In other words, the LENGTH field in a UHR PPDU is set to a value that satisfies the condition that LENGTH divided by 3 leaves a remainder of 0.

[0104] For example, a (non-AP and AP) STA can apply BCC encoding based on a 1 / 2 coding rate to the 24-bit information of the L-SIG field. The transmitting STA then obtains 48 bits of BCC encoded data. BPSK modulation can be applied to these 48 bits to generate 48 BPSK symbols. The transmitting STA can map these 48 BPSK symbols to positions other than the pilot subcarriers {subcarrier indices -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 subcarrier indices {-28, -27, +27, +28}. The aforementioned signals can be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

[0105] For example, a (non-AP and AP) STA can generate an RL-SIG in the same way as the L-SIG. BPSK modulation can be applied to the RL-SIG. Based on the presence of the RL-SIG, the (non-AP and AP) STA can know that the RX PPDU is an HE PPDU, EHT PPDU, or UHR PPDU. In other words, if the RL-SIG is present, the receiving (non-AP and AP) STA can know that the received PPDU is one of an HE PPDU, EHT PPDU, or UHR PPDU. In other words, if the RL-SIG is not present, the receiving (non-AP and AP) STA can know that the received PPDU is one of a non-HT PPDU, HT PPDU, or VHT PPDU. In other words, the RL-SIG field is a repetition of the L-SIG field and is used to distinguish UHR PPDUs from non-HT PPDUs, HT PPDUs, and VHT PPDUs.

[0106] Universal SIG (U-SIG) can be inserted in Figure 6 Following RL-SIG, U-SIG can be referred to by various terms such as First SIG Field, First SIG, First Type SIG, Control Signal, Control Signal Field, First (Type) Control Signal, Common Control Field, Common Control Signal, etc.

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

[0108] Through U-SIG, for example, A bits of information (e.g., 52 uncoded bits) can be transmitted. The first symbol of U-SIG can transmit the first X bits of the A bits (e.g., 26 uncoded bits), and the second symbol of U-SIG can transmit the remaining Y bits of the A bits (e.g., 26 uncoded bits). For example, the transmitting STA can obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA can perform convolutional coding (i.e., BCC coding) based on a rate of R=1 / 2 to generate 52 coded bits, and can 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 to be assigned to each U-SIG symbol. A U-SIG symbol can be transmitted based on 65 tones (subcarriers) from subcarrier index -28 to subcarrier index +28, except for DC index 0. The 52 BPSK symbols generated by the transmitting STA can be transmitted based on the remaining tones (subcarriers) other than the pilot tone, namely tones -21, -7, +7, and +21.

[0109] For example, the A-bit information generated by U-SIG (e.g., 52 uncoded bits) may include a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit field). The CRC and tail fields can be sent via the second symbol of U-SIG. The CRC field can be generated based on the 26 bits allocated to the first symbol of U-SIG and the remaining 16 bits from the second symbol excluding the CRC / tail field, and can be generated based on a standard CRC calculation algorithm. Additionally, the tail field can be used to terminate the trellis of the convolutional decoder and can be set to, for example, "000000".

[0110] The A-bit information (e.g., 52 uncoded bits) sent by U-SIG (or the U-SIG field) can be divided into version-independent bits and version-dependent bits. For example, the version-independent bits can have a fixed or variable size. For example, the version-independent bits can be assigned only to the first symbol of U-SIG, or they can be assigned to both the first and second symbols of U-SIG. For example, the version-independent bits and version-dependent bits can be referred to by various terms such as first control bit, second control bit, etc.

[0111] For example, the version-independent bits of the U-SIG can include a 3-bit PHY version identifier. For example, the 3-bit PHY version identifier can include information related to the PHY version of the TX / RX PPDU. For example, the first value of the 3-bit PHY version identifier (e.g., a value of 000) can indicate that the TX / RX PPDU is an EHT PPDU. Furthermore, the second value of the 3-bit PHY version identifier (e.g., a value of 001) can indicate that the TX / RX PPDU is a UHR PPDU.

[0112] In other words, when the (AP / non-AP) STA sends an EHT PPDU, the 3-bit PHY version identifier can be set to a first value, and when the (AP / non-AP) STA sends a UHR PPDU, the 3-bit PHY version identifier can be set to a second 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 with the first value, and can determine that the received PPDU is a UHR PPDU based on the PHY version identifier with the second value.

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

[0114] For example, the version-independent bits of U-SIG can include information related to the transmission opportunity (TXOP) length and information related to the BSS color ID.

[0115] For example, if the UHR PPDU is classified into various types (e.g., types related to SU transmission (based on UL or DL), types related to DL transmission, types related to NDP transmission, types related to DL non-MU-MIMO, types related to DL MU-MIMO, types related to multi-AP operation, types related to coordinated beamforming (CBF), spatial reuse (SR), types related to coordinated OFDMA (C-OFDMA), and types related to coordinated TDMA (CTDM), then information about the type of the UHR PPDU (e.g., 2-bit or 3-bit information) can be included in the version-related bits of the U-SIG.

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

[0117] Can be Figure 6 The PPDU uses preamble puncturing. Preamble puncturing means that a puncture is applied to a portion of the full frequency band (e.g., the secondary 20 MHz band). For example, when transmitting an 80 MHz PPDU, the STA can apply puncturing to the secondary 20 MHz band within the 80 MHz band, and can transmit the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0118] For example, the pattern for the preamble punch can be pre-configured. For example, when applying the first punch pattern, punching can be applied only to the secondary 20 MHz band within the 80 MHz band. For example, when applying the second punch pattern, punching can be applied only to any one of the two secondary 20 MHz bands within the secondary 40 MHz band included in the 80 MHz band. For example, when applying the third punch pattern, punching can be applied only to the secondary 20 MHz band within the primary 80 MHz band included in the 160 MHz band (or 80+80 MHz band). For example, when applying the fourth punch pattern, punching can be applied to at least one 20 MHz channel that does not belong to the primary 40 MHz band, provided that the primary 40 MHz band within the 80 MHz band included in the 160 MHz band (or 80+80 MHz band) is present.

[0119] Information related to the prelead puncturing applied to the PPDU can be included in the U-SIG and / or UHR-SIG. For example, the first field of the U-SIG may include information related to continuous bandwidth, and the second field of the U-SIG may include information related to the prelead puncturing applied to the PPDU.

[0120] For example, based on the following method, U-SIG and UHR-SIG can include information related to pre-lead puncture. When the bandwidth of the PPDU exceeds 80 MHz, U-SIG can be configured individually in 80 MHz units. For example, when the bandwidth of the PPDU is 160 MHz, the PPDU can include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG can include information related to the 160 MHz bandwidth, and the second field of the first U-SIG can include information related to the pre-lead puncture applied to the first 80 MHz band (i.e., information related to the pre-lead puncture pattern). Additionally, the first field of the second U-SIG can include information related to the 160 MHz bandwidth, and the second field of the second U-SIG can include information related to the pre-lead puncture applied to the second 80 MHz band (i.e., information related to the pre-lead puncture pattern). Meanwhile, the UHR-SIG consecutive with the first U-SIG may include information related to the preleading hole applied to the second 80 MHz band (i.e., information related to the preleading hole pattern), and the UHR-SIG consecutive with the second U-SIG may include information related to the preleading hole applied to the first 80 MHz band (i.e., information related to the preleading hole pattern).

[0121] Additionally or alternatively, U-SIG and UHR-SIG may include information related to the pre-drilled hole, based on the following method: U-SIG may include information related to the pre-drilled hole for all frequency bands (i.e., information related to the pre-drilled hole pattern). That is, UHR-SIG may not include information related to the pre-drilled hole, while only U-SIG may include information related to the pre-drilled hole (i.e., information related to the pre-drilled hole pattern).

[0122] U-SIGs can be configured in 20 MHz units. For example, when an 80 MHz PPDU is configured, U-SIGs can be duplicated. That is, four identical U-SIGs can be included in an 80 MHz PPDU. PPDUs with bandwidths exceeding 80 MHz can include different U-SIGs.

[0123] Figure 6The UHR-SIG can include control information for receiving STAs. The UHR-SIG can be transmitted using at least one symbol, and a symbol can have a length of 4 μs. Information related to the number of symbols used for the UHR-SIG can be included in the U-SIG.

[0124] UHR-SIG provides additional signals to the U-SIG field to enable the STA to interpret / decode the UHR PPDU. The UHR-SIG field may include U-SIG overflow bits that are typically applied to all users. In addition, the UHR-SIG field includes resource allocation information, allowing the STA to locate resources used in fields including the data field / UHR-STF / UHR-LTF (i.e., the UHR modulation field of the UHR PPDU).

[0125] It can be determined based on the RU (Resource Unit) defined by multiple subcarriers / tones. Figure 6 The frequency resources of the UHR-LTF, UHR-STF, and data fields illustrated herein. That is, the UHR-LTF, UHR-STF, and data fields of this disclosure can be transmitted / received through RUs (resource units) defined by multiple subcarriers / tones.

[0126] Figure 7 The layout of a resource unit (RU) for a 20 MHz PPDU is illustrated. That is, the UHR-LTF, UHR-STF, and / or data fields included in the 20 MHz PPDU can be accessed via... Figure 7 At least one of the various RUs defined in the code is used to send / receive.

[0127] like Figure 7 As illustrated at the top, 26 units (i.e., units corresponding to 26 tones) can be arranged. Six tones can be used for the guard band in the leftmost band of the 20 MHz band, and five tones can be used for the guard band in the rightmost band of the 20 MHz band. Furthermore, seven DC tones can be inserted in the center band (i.e., the DC band), and 26 units corresponding to 13 tones on each of the left and right sides of the DC band can be arranged. Units of 26, 52, and 106 can be allocated to other bands. Individual units can be assigned to receiving STAs (i.e., users).

[0128] Figure 7 The RU layout in the diagram can be used not only for multi-user (MU) but also for single-user (SU). In the single-user case, a 242 unit can be used and three DC tones can be inserted, such as... Figure 7 is illustrated in the bottom part of .

[0129] Although Figure 7Various sizes of RUs have been proposed, namely 26-RU, 52-RU, 106-RU, and 242-RU, but RUs of a specific size can be expanded or increased. Therefore, this embodiment is not limited to individual RUs of a specific size (i.e., the number of corresponding tones). In this specification, an N-RU can be represented as an N-tone RU, etc. For example, a 26-RU can be represented as a 26-tone RU.

[0130] Figure 8 The layout of a resource unit (RU) for a 40 MHz PPDU is illustrated.

[0131] With the use of RUs of various sizes Figure 7 Similarly, in Figure 8 Examples of frequencies that can be used include 26-RU, 52-RU, 106-RU, 242-RU, and 484-RU. Additionally, five DC tones can be inserted into the center frequency; 12 tones can be used for the leftmost guard band of the 40 MHz band; and 11 tones can be used for the rightmost guard band of the 40 MHz band.

[0132] like Figure 8 As shown, a 484-RU can be used when the RU layout is for a single user. The specific number of RUs can be similar to... Figure 7 Change.

[0133] Figure 9 The layout of a resource element (RU) for an 80 MHz PPDU is illustrated. The layout of the resource element (RU) used in this disclosure can be varied. For example, the layout of the resource element (RU) used in the 80 MHz band can be varied.

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

[0135] TB PPDUs 1041 and 1042 can be transmitted simultaneously and from multiple STAs (e.g., user STAs) indicated by their AIDs in 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 as a block ACK (BA).

[0136] exist Figure 10Within TXOP 1025, the transmission of trigger frame 1030, TB PPDU 1041, 1042 and / or ACK frame 1050 can be performed.

[0137] Figure 11 An example of using / supporting / defining a channel within the 2.4 GHz band is shown.

[0138] The 2.4 GHz band can also be referred to by other names, such as "first band". Furthermore, the 2.4 GHz band can refer to the frequency range used / supported / defined by channels having a center frequency adjacent to 2.4 GHz (e.g., channels having a center frequency between 2.4 GHz and 2.5 GHz).

[0139] The 2.4 GHz band can include multiple 20 MHz channels. Each 20 MHz channel within the 2.4 GHz band can have multiple channel indices (e.g., indices 1 to 14). For example, the center frequency of channel index 1 for a 20 MHz channel allocation could be 2.412 GHz, the center frequency of channel index 2 for a 20 MHz channel allocation could be 2.417 GHz, and the center frequency of channel index N for a 20 MHz channel allocation could be (2.407 + 0.005 GHz). (N) GHz. The channel index can be referenced by various names such as the channel number. The specific values ​​of the channel index and the center frequency can be changed.

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

[0141] Figure 12 An example of using / supporting / defining channels within the 5 GHz band is shown.

[0142] The 5 GHz band can be referred to by other names, such as second band / band, etc. The 5 GHz band can refer to the frequency range that uses / supports / defines channels with a center frequency greater than or equal to 5 GHz and less than 6 GHz (or less than 5.9 GHz). Alternatively, the 5 GHz band can include multiple channels between 4.5 GHz and 5.5 GHz. Figure 12 The specific values ​​shown may change.

[0143] Multiple channels within the 5 GHz band include the unlicensed National Information Infrastructure (UNII)-1, UNII-2, UNII-3, and ISM. UNII-1 may be referred to as the lower UNII. UNII-2 may include frequency ranges referred to as the middle UNII and the extended UNII-2. UNII-3 may be referred to as the upper UNII.

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

[0145] Figure 13 Examples of channels used, supported, and defined within the 6 GHz band are illustrated.

[0146] The 6 GHz band can also be referred to by other names, such as the third band. The 6 GHz band can refer to the frequency range in which channels with center frequencies above 5.9 GHz are used, supported, and defined. Figure 13 The specific values ​​shown may vary.

[0147] For example, it can be defined starting from 5.940 GHz. Figure 13 The 20 MHz channel. Specifically, Figure 13 The leftmost channel in the 20 MHz channel can have an index of 1 (or channel index, channel number, etc.) and can be assigned a center frequency of 5.945 GHz. In other words, the center frequency of the indexed N channel can be determined as (5.940 + 0.005 GHz). (N) GHz.

[0148] therefore, Figure 13The index (or channel number) of the 20 MHz channel is 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, and it can be 197, 201, 205, 209, 213, 217, 221, 225, 229, 233. Furthermore, according to the above (5.940+0.005) N)GHz rules, Figure 13 The index of the 40 MHz channel 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.

[0149] The MAC frames included in the data fields of the PPDU disclosed herein can be classified into various types. For example, the MAC frames disclosed herein can be classified into control frames, management frames, and data frames.

[0150] For example, management frames include association requests, association responses, reassociation requests, reassociation responses, probe requests, probe responses, beacons, disassociation, authentication, and deauthentication frames / signals as defined in a typical WLAN. For management frames, the type fields (B3 and B2) of the MAC header are set to 00. Additionally, the subtype fields (B7, B6, B5, B4) of the MAC header have the following values: association request (0000), association response (0001), reassociation request (0010), reassociation response (0011), probe request (0100), probe response (0101), beacon (1000), disassociation (1010), authentication (1011), and deauthentication (1100).

[0151] For example, control frames include trigger beamforming report polling, NDP announcement (NDPA), control frame extension, control encapsulation, block acknowledgment request (BlockAckReq), block acknowledgment (BlockAck), power saving polling (PS-Poll), request to send (RTS), allow to send (CTS), acknowledgment (Ack), and CF end frame / signal as defined in a conventional WLAN. For control frames, the values ​​of the type fields (B3 and B2) in the MAC header are set to 01. Additionally, the values ​​of the subtype fields (B7, B6, B5, B4) in the MAC header are as follows: trigger (0010), beamforming report polling (0100), NDP announcement (0101), control frame extension (0110), control encapsulation (0111), block acknowledgment request (1000), block acknowledgment (1001), power saving polling (1010), request to send (1011), allow to send (1100), acknowledgment (1101), and CF end (1110).

[0152] For example, the data frame includes (QoS) data, (QoS) null, etc., as defined in a regular WLAN. For this data frame, the values ​​of the type fields (B3 and B2) in the MAC header are set to 10.

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

[0154] Figure 14 This shows the trigger frame format. The trigger frame format can also be referred to as the structure of the trigger frame.

[0155] Reference Figure 14 The trigger frame may include a frame control field, a duration field, a receiver address (RA) field, a sender address (TA) field, a common information field, a user information list field, a padding field, and / or a frame check sequence (FCS) field. Alternatively, the trigger frame may include a special user information field between the common information field and the user information list field. The user information list field may include one or more user information fields. The frame control field, duration field, RA field, and TA field may constitute the MAC header.

[0156] For example, a public information field may include a trigger type subfield. The value of the trigger type subfield can indicate a trigger frame variant as shown in Table 1: [Table 1]

[0157] For example, if the value of the trigger type subfield is set to 0, the trigger frame can be a basic trigger frame. For example, if the value of the trigger type subfield is set to 3, the trigger frame can be a multi-user (MU) RTS trigger frame. Meanwhile, according to the EHT (i.e., 802.11be) standard, the AP can allocate a portion of the duration within the TXOP obtained by the AP to non-AP STAs to support peer-to-peer (P2P) transmission. To allocate a portion of the duration within the TXOP, the TXOP sharing mode subfield can be defined within the common information field of the MU-RTS trigger frame. When the value of the TXOP sharing mode subfield is non-zero, such a MU-RTS trigger frame can be called a MU-RTS TXOP sharing (TXS) trigger frame (TF). The descriptions of the values ​​of the TXOP sharing mode subfield are shown in Table 2 below: [Table 2]

[0158] For example, if the value of the TXOP shared mode subfield is 1, it supports sending to one or more (non-TB) PPDUs to the AP; if the value of the TXOP shared mode subfield is 2, it supports both sending to (non-TB) PPDUs to the AP and P2P transmission. In this disclosure, the MU-RTS TXS TF can also be simply referred to as the TXS trigger frame.

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

[0160] Reference Figure 15 The user information field may include the AID subfield, the RU allocation subfield, the allocation duration subfield, reserved bits, and / or the PS160 subfield.

[0161] The AID subfield indicates the AID of the corresponding STA; the RU allocation subfield indicates the RU allocation of the corresponding STA.

[0162] The allocation duration subfield may include nine bits from B20 to B28 in the MU-RTS TXS TF and indicate the allocation duration in 16 microseconds. In this case, the maximum length of the allocation duration indicated by this allocation duration subfield can be 8192 microseconds.

[0163] The PS160 subfield can indicate the primary 160 MHz channel or secondary 160 MHz channel used for RU or MRU allocation.

[0164] Meanwhile, many APs are installed adjacent to each other to enable STAs to maintain continuous WLAN connectivity over a wider area. However, overlapping BSSs of multiple APs can lead to problems such as radio interference and transmission conflicts between APs. To address these issues, various techniques related to coordination between APs in the frequency, time, and spatial domains have been proposed (e.g., RU selection, joint transmission, zeroing). Various problems that may arise during inter-AP coordination need to be resolved.

[0165] In this disclosure, multi-AP operation is proposed. Multi-AP operation can be based on techniques to reduce various interferences (such as inter-symbol interference (ISI)) through coordination with neighboring APs (e.g., APs located in overlapping BSSs).

[0166] For example, multi-AP operation can be categorized into multi-AP coordination schemes (or coordination schemes) based on various technologies / types / formats / protocols. For instance, a coordination scheme may include coordinated TDMA (Co-TDMA) based on time axis (time domain) separation of radio resources allocated to multiple APs. Alternatively, a coordination scheme may include coordinated OFDMA (C-OFDMA) based on frequency axis (frequency domain) separation of radio resources allocated to multiple APs. Alternatively, a coordination scheme may include coordinated spatial reuse (Co-SR) applying spatial reuse (SR) to at least one AP. Alternatively, a coordination scheme may include coordinated beamforming (Co-BF) / zeroing that performs transmission by zeroing interference occurring in neighbors (e.g., adjacent APs / STAs, and / or OBSS APs / OBSS STAs). Alternatively, a coordination scheme may include AP selection, where the AP with good channel condition among adjacent APs (e.g., at least one AP with good channel condition located in a BSS or OBSS) performs transmission. Additionally or alternatively, the coordination scheme may include Joint Transmission (JTX) or Joint Transmission (JT), in which multiple APs (e.g., multiple APs included in the same BSS / OBSS, or multiple APs included in different BSS / OBSS) coordinate to perform transmission and reception simultaneously, and JTX / JT may be implemented based on joint beamforming or joint MU-MIMO.

[0167] In this disclosure, "multi-AP (coordination) operation" may also be referred to as "multi-AP (coordination) transmission". Furthermore, "multi-AP (coordination) operation / transmission" and "multi-AP coordination scheme (or, coordination scheme)" are used interchangeably.

[0168] When the triggered TXOP sharing protocol is used for multi-AP coordination, the transmission within the BSS of each coordinating AP is divided into time units, allowing each coordinating AP to perform frame switching without affecting other coordinating APs.

[0169] In this disclosure, "frame switching (FE)" can include frame transmission and / or reception operations between STAs. STAs can be APs or non-AP STAs. Here, frames can include various types of frames (e.g., data frames, control frames, and management frames).

[0170] Figure 16 An example of coordinating time division multiple access (Co-TDMA) between APs is shown.

[0171] For example, Co-TDMA can mean that each coordinating AP performs frame switching by dividing the transmissions within each coordinating AP's BSS into time units without affecting other coordinating APs.

[0172] When a triggered TXS protocol is applied to a multi-AP coordination operation, the AP in the triggered TXS protocol can be an AP sharing a TXOP in the multi-AP coordination operation, and the STA in the triggered TXS protocol can be an AP authorized to share a TXOP in the multi-AP coordination operation. In this disclosure, the AP sharing a TXOP can be referred to as the sharing AP (SAP), and the AP authorized to share a TXOP by the SAP can be referred to as the shared AP (DAP). The term "SAP" here does not limit the entity sharing a TXOP to only AP STAs—SAP can also include non-AP STAs sharing a TXOP. Furthermore, the term "DAP" does not limit the entity authorized to share a TXOP to only AP STAs, and DAP can also include non-AP STAs authorized to share a TXOP (or, non-AP STAs that transmit and receive together with the AP STAs authorized to share a TXOP). Additionally, during the allocated time period (i.e., Figure 16 The time allocated by the MU-RTS TXS TF (which is the allocated duration for DAP / AP2 within the TXOP indicated by the MU-RTS TXS TF sent from SAP) is used for frame exchanges performed by the DAP and non-AP STAs belonging to the DAP BSS or SAP. This can be referred to as the DAP's BSS frame exchange (FE). For example, an RTS / CTS frame exchange between the DAP and a non-AP STA can be performed, followed by data frame transmission and block ACK frame response, UL data frame transmission by the non-AP STA based on a trigger frame sent from the DAP, and / or data frame transmission by the DAP based on a trigger frame sent from the SAP.

[0173] For multi-AP coordination to be performed between two APs, the two APs should be connected / associated with each other, and / or after a prior negotiation process to exchange their respective capability / requirement information, multi-AP transmission can be performed based on the obtained information (e.g., coordinated Time Division Multiple Access (Co-TDMA), coordinated Orthogonal Frequency Division Multiple Access (C-OFDMA), coordinated Spatial Reuse (Co-SR), coordinated Beamforming (Co-BF), AP Selection or Joint Transmission (J-TX)). In other words, for proper multi-AP transmission, a negotiation process for configuring / managing multi-AP coordination and / or transmission based on a specific multi-AP coordination scheme needs to be pre-performed between the aforementioned SAP and DAP. Through this negotiation process, a multi-AP set can be established / configured. Therefore, this negotiation process can also be referred to as the multi-AP set establishment / configuration process.

[0174] The following describes the negotiation process for multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, or J-TX). Figure 17 and Figure 18 The text describes Co-TDMA operation, but this is merely an example. Figure 17 and Figure 18 The description can also be applied to other multi-AP operations (e.g., C-OFDMA, Co-SR, Co-BF, AP selection, J-TX).

[0175] Figure 17 An example of a peer-to-peer negotiation process according to an embodiment of this disclosure is shown.

[0176] refer to Figure 17 Before acquiring a TXOP, each AP whose role as SAP or DAP has not yet been determined can send and receive coordination request and response frames from neighboring APs, and perform a prior negotiation process for multi-AP coordination. Through this negotiation process, which involves exchanging request and response frames that include information for Co-TDMA operation (e.g., negotiation information / coordination information), APs intending to operate in multi-AP coordination and Co-TDMA can obtain information about each other (e.g., negotiation information / coordination information). Based on this negotiation information / coordination information, an AP acquiring a TXOP to perform the SAP role can decide whether to first perform a separate FE with its own STA in its BSS, or to share the TXOP with a specific DAP based on the negotiation information / coordination information.

[0177] Additionally, an AP that has received a coordination request frame or coordination response frame that includes and / or indicates whether UHR STA support is only supported can assume that the corresponding AP intends to perform FE only for a limited number of UHR STAs. A specific AP aware of this, when it acquires the TXOP to perform SAP roles, can preferentially (or based on a negotiated protocol) share the TXOP with a UHR STA-supporting DAP that does not require additional signaling and new procedures for legacy devices in the DAP's BSS that the SAP might need to perform FE with.

[0178] Figure 18 An example of a broadcast-based negotiation process according to an embodiment of this disclosure is shown.

[0179] refer to Figure 18 Before acquiring a TXOP, each AP whose role as SAP or DAP has not yet been determined can broadcast a trigger frame (TF) including Co-TDMA related information (e.g., negotiation information / coordination information) to participate in multi-AP coordination and can receive trigger-based (TB) PPDUs from the corresponding AP. Here, the TF can be a coordination request frame or can correspond to a coordination request frame, and the TB PPDU can be a coordination response frame or can correspond to a coordination response frame. Through a broadcast-based negotiation process of exchanging TFs and TB PPDUs including information for Co-TDMA operation (e.g., negotiation information / coordination information), APs intending to operate in multi-AP coordination and Co-TDMA can obtain information about each other (e.g., negotiation information / coordination information). Based on such information (e.g., negotiation information / coordination information), an AP that has acquired a TXOP to perform the role of SAP can decide whether to first perform a separate FE with the STA in its own BSS, or to share the TXOP with a specific DAP based on the negotiation information / coordination information.

[0180] In this disclosure, negotiation information / coordination information based on one or more of the following A to H may be included in coordination request frames and / or coordination response frames transmitted during the negotiation process for multi-AP operation (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, or J-TX). In this disclosure, the negotiation information / coordination information may include resource information of the AP sending the negotiation information / coordination information (or, resource information of the AP receiving the negotiation information / coordination information).

[0181] A. Multi-AP Group ID: The ID of the group / set of APs that have been configured for multi-AP coordination (e.g., 0, 1, 2, ...).

[0182] B. Multiple AP IDs: IDs locally assigned to each AP within a configured multiple AP group / set (e.g., 0, 1, 2, ...).

[0183] C. Multi-AP Coordination Types (or Coordination Schemes): Information on multi-AP coordination schemes including C-OFDMA, Co-TDMA, J-TX, and Co-SR.

[0184] D. Operation Channel: Information regarding the main channel and punch channel during operation.

[0185] For example, operational channel information may include channel information that is jointly operated for proper coordination among APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX).

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

[0187] For example, operational channel information may include puncturing channel information for APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, a new field can be defined as a disabled sub-channel bitmap field in the EHT operational information field to indicate the punctured 20MHz sub-channels using a bitmap. If a bit value in the bitmap is 0, it indicates that the corresponding 20MHz sub-channel is not punctured. If a bit value in the bitmap is 1, it indicates that the corresponding 20MHz sub-channel is punctured.

[0188] For example, operational channel information may include information about the primary channel of the DAP within the channel operated by SAP.

[0189] For example, operational channel information may include information about the DAP's primary channel within the operational channels excluding SAP's punched channels.

[0190] E. Operational bandwidth information: Bandwidth and maximum bandwidth information during operation.

[0191] For example, operational bandwidth information may include information about the bandwidth (BW) that is shared by APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, the aforementioned operational channel and master channel information may be utilized.

[0192] For example, operational bandwidth information may include the maximum bandwidth information of the APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, a new field can be defined in the control field of the EHT operational information field to indicate the channel width (i.e., the BSS BW information for each AP), as follows: - Set to 0: Indicates a bandwidth of 20MHz - Set to 1: Indicates a 40MHz bandwidth - Set to 2: Indicates 80MHz bandwidth - Set to 3: Indicates 160 / 80+80MHz bandwidth - Set to 4: Indicates 320 / 160+160MHz bandwidth - The remaining values ​​from 5 to 7 can be retained.

[0193] For example, operational bandwidth information may include the BW field information in the SIG-A field.

[0194] For example, operational bandwidth information may include UL BW field information included in the public information field of MU-RTS TXS TF.

[0195] For example, operational bandwidth information can include information about the bandwidth of the DAP within the entire bandwidth of SAP operations.

[0196] For example, a new field for bandwidth indication (i.e., operational bandwidth information) can be added by modifying / redefining it to include a new subfield within the media time field of the QoS characteristic element. In some implementations, a new field can be defined within the control field of the EHT operational information field to indicate the channel width (i.e., the BSS BW information for each AP), as follows: - Set to 0: Indicates a bandwidth of 20MHz - Set to 1: Indicates a 40MHz bandwidth - Set to 2: Indicates 80MHz bandwidth - Set to 3: Indicates 160 / 80+80MHz bandwidth - Set to 4: Indicates 320 / 160+160MHz bandwidth - The remaining values ​​from 5 to 7 can be retained.

[0197] F. Required TXOP Duration: Information related to the duration of the TXOP that each AP intends to share.

[0198] For example, a new field including the required TXOP duration can be defined. In some implementations, the required duration field is defined to indicate the information required for multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX) and the required TXOP duration value. In some implementations, a Co-TDMA operation element is defined to indicate the information required for multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX) and the required TXOP duration value.

[0199] For example, the required TXOP duration can be included in a QoS feature element that can be used to include negotiation / coordination information during the pre-negotiation process of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX), or it can be included in an element that can be newly defined for negotiation of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX).

[0200] For example, the required TXOP duration can be included in a UHR operation element that can be used to include broadcast information during the broadcast process of each AP in a multi-AP operation (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP Selection, J-TX), or it can be included in an element that can be newly defined for broadcasting of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP Selection, J-TX).

[0201] G. Low-latency service information: Information related to the low-latency services that each AP intends to send or receive.

[0202] For example, low-latency service information can be included in the information of a QoS feature element, which is included in the SCS request / response frame.

[0203] For example, the delay threshold field information within the QoS feature element information can be utilized. In some implementations, the value of the delay threshold field for the QoS service that each AP intends to send can be used as low-latency service information. In this way, the SAP can use it to check the necessity of TXOP sharing, or to update existing values ​​for DAPs that can complete the transmission of MSDU or A-MSDU within the duration of the TXOP to be shared (i.e., the pre-negotiated low-latency service information or delay threshold field value is shorter than the allocated time).

[0204] For example, the MSDU lifetime field information in the QoS feature element information can be utilized. In some implementations, the value of the MSDU lifetime field for the QoS service that each AP intends to send can be used as low-latency service information. In this way, the SAP can use it to check the necessity of TXOP sharing, or to update the existing value for DAPs that do not discard MSDUs within the duration of the TXOP to be shared (i.e., the pre-negotiated low-latency service information or the value of the MSDU lifetime field has not expired within the allocated time).

[0205] For example, the Service Start Time field information in the QoS feature element information can be utilized. In some implementations, the value of the Service Start Time field for the QoS service that each AP intends to send can be used as low-latency service information. In this way, the SAP can use it to check the necessity of TXOP sharing, or to update existing values ​​for DAPs that can begin the expected service period and frame exchange within the time limit of the TXOP to be shared (i.e., the pre-negotiated low-latency service information or the value of the Service Start Time field is shorter than the allocated time).

[0206] For example, low-latency service information may include TXOP sharing request information requested / indicated by the AP that needs to send low-latency services.

[0207] For example, low-latency service information may include time limit information for low-latency services requested / indicated by the AP that needs to transmit the low-latency service (e.g., the minimum time limit at which the transmission of the low-latency service should begin / the maximum time limit at which the transmission of the low-latency service should be successfully completed).

[0208] For example, low-latency service information may include arrival rate information for low-latency services requested / instructed by the AP that needs to send periodic low-latency services (e.g., the arrival rate of low-latency services since the last reported event).

[0209] For example, low-latency service information may include service identifier (TID) / access class (AC) information.

[0210] H. UHR STA Support: Indicates whether only information for UHR non-AP STAs is supported.

[0211] For example, a 1-bit signaling bit can be defined in the coordination request / response frame to indicate UHR STA support information. In this case, bit 0 indicates that only UHR non-AP STAs are supported, and bit 1 indicates that HE / EHT / UHR non-AP STAs are supported.

[0212] For example, information in special user information fields included in the trigger frame (e.g., PHY version identifier) ​​can be used as UHR STA support information.

[0213] For example, QoS feature elements included in the SCS request / response frame can be used as UHR STA support information. In some implementations, reserved bits of control information within the QoS feature element can be used. That is, a 1-bit signaling bit can be defined in the reserved bits to indicate UHR STA support information. In this case, bit 0 can indicate support only for UHR non-AP STAs. Bit 1 can indicate support for HE / EHT / UHR non-AP STAs.

[0214] UHR STA support information / signaling can be defined as indicating that the AP only supports UHR non-AP STAs, or indicating that it supports not only UHR but also HE / EHT non-AP STAs, and is not limited thereto.

[0215] Additionally, the following negotiation / coordination information can be further included in the coordination response frame: I. Status Code: Acceptance / Rejection / Recommendation information for the coordination request.

[0216] For example, a status code can indicate acceptance or success.

[0217] For example, a status code can indicate rejection, or include recommendation information while indicating rejection. In some implementations, the status code may include a rejection code containing the reason for rejection (e.g., REJECTED_BAD_SUPPORTED_CHANNELS). In some implementations, the status code may include a rejection code containing recommendation information (e.g., REJECTED_WITH_SUGGESTED_CHANGES). If the value of the status code includes rejection and / or recommendation information, it may also include information for new negotiation. That is, a neighboring AP that has received the coordination request frame may include additional information regarding the aforementioned operating channel, bandwidth, required TXOP duration, low-latency service information, and / or UHR STA support.

[0218] The identifiers and / or signaling / information names defined above can be changed and can exist and include information based on multi-AP operations (e.g., channel information, DAP buffer information).

[0219] The negotiation process between APs used for multi-AP coordination can be carried out over a long period of time, and as a result, there may be situations where pre-negotiated negotiation / coordination information expires and / or needs to be updated to the latest information.

[0220] Therefore, this disclosure proposes various implementations for APs participating in multi-AP coordination to perform resource reporting independently in an unsolicited manner (rather than in a manner that receives a resource request from another AP and responds to that resource request (i.e., a requesting manner)). According to various implementations of this disclosure, each AP can report frames in an unsolicited manner including information related to its own multi-AP coordination and / or information sent based on multi-AP coordination (i.e., negotiation information / coordination information), such that the coordinating AP can update the corresponding information and update the resource information of the AP that delivered the information.

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

[0222] Figure 19 An example of a method performed by a first AP according to an embodiment of the present disclosure is shown. The first AP may be an AP that performs resource reporting (or sends resource report frames).

[0223] refer to Figure 19 In step S1901, the first AP may perform a negotiation process for multi-AP coordination with one or more APs.

[0224] In step S1903, the first AP can obtain a configuration of a multi-AP set including one or more APs based on the negotiation process.

[0225] In step S1905, after obtaining the configuration of the multi-AP set, the first AP may update at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP in the multi-AP set during the negotiation process.

[0226] In step S1907, the first AP may send a resource report frame to the second AP, which includes information about the configuration of at least one updated resource.

[0227] According to various implementations, while performing the negotiation process, the first AP may send a coordination request frame including resource information of the first AP to the second AP. The first AP can receive a coordination response frame from the second AP in response to the coordination request frame. The coordination response frame may include the resource information of the second AP.

[0228] According to various implementations, while performing the negotiation process, the first AP can receive a coordination request frame including resource information of the second AP from the second AP. The first AP can send a coordination response frame to the second AP in response to the coordination request frame. The coordination response frame may include the resource information of the first AP.

[0229] According to various implementations, the resource information of the first AP may include at least one of the following: an identifier (ID) of the multi-AP set; the ID of the first AP; the address of the first AP; information on the dynamic channel of the first AP; information on the operating bandwidth of the first AP; information on the transmission opportunities (TXOPs) required by the first AP; information on the buffer status of the first AP; information on whether the first AP needs TXOP sharing; or low-latency service information for the first AP.

[0230] According to various implementations, the at least one resource configuration may include all or part of the resource configuration included in the resource information of the first AP.

[0231] According to various implementation methods, the resource report frame can be a Quality of Service (QoS) data frame or a QoS empty frame. After sending the QoS data frame or QoS empty frame, the first AP can receive an acknowledgment (ACK) frame for the QoS data frame or QoS empty frame from the second AP.

[0232] According to various implementations, the resource report frame can be a multi-user (MU) request to send (RTS) trigger frame. After sending the MU-RTS trigger frame, the first AP can receive a clear-to-send (CTS) frame from the second AP in response to the MU-RTS trigger frame.

[0233] According to various implementation methods, the resource report frame can be a management frame. After sending the management frame, the first AP can receive an acknowledgment (ACK) frame for the management frame from the second AP.

[0234] According to various implementation methods, the Receiver Address (RA) field of the resource report frame can be set to the address of the second AP. The Association Identifier (AID) field of the resource report frame can be set to a value unrelated to the second AP.

[0235] According to various implementations, the first AP can send a resource report frame to the second AP even if it has not received a frame for requesting a resource report frame from the second AP.

[0236] According to various implementations, the at least one resource configuration can be updated after the negotiation process and before the next negotiation process. A resource report frame including the at least one resource configuration can be sent when the at least one resource configuration is updated.

[0237] According to various implementation methods, the first AP can perform multi-AP operations with the second AP based on at least one updated resource configuration.

[0238] Figure 20 An example of a method performed by a second AP according to an embodiment of the present disclosure is shown. The second AP may be an AP that receives a resource report frame from a first AP that performs a resource report (or sends a resource report frame).

[0239] refer to Figure 20 In step S2001, the second AP may perform a negotiation process for multi-AP coordination with one or more APs.

[0240] In step S2003, the second AP can obtain a configuration of a multi-AP set including one or more APs based on the negotiation process.

[0241] In step S2005, after obtaining the configuration of the multiple AP set, the second AP can receive a resource report frame including information on the configuration of at least one resource from the first AP in the multiple AP set.

[0242] In step S2007, the second AP may update at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP during the negotiation process.

[0243] According to various implementation methods, the resource report frame can be a management frame. After receiving the management frame, the second AP can send an acknowledgment (ACK) frame to the first AP for that management frame.

[0244] According to various implementations, the second AP can receive a resource report frame from the first AP without sending a frame for requesting a resource report frame to the first AP.

[0245] According to various implementation methods, the resource report frame can be received from the first AP after the negotiation process and before the next negotiation process.

[0246] The following section describes the detailed implementation of unsolicited resource reporting for multi-AP coordination.

[0247] In this disclosure, resource information based on a combination of one or more of the following A to I may be included in a report frame (e.g., a resource report frame) transmitted during an unsolicited resource reporting process for multi-AP coordination as proposed in this disclosure. The names of the resource information defined below may be changed and are not limited thereto.

[0248] A. Multi-AP Group ID: The ID of the group / set of APs that have been configured for multi-AP coordination (e.g., 0, 1, 2, ...).

[0249] B. DAP ID: The ID assigned to each AP within a configured multi-AP group / set (e.g., 0, 1, 2, ...).

[0250] C. Address: Address information of the target AP (i.e., the AP that sent the resource report frame) (e.g., BSS color, BSSID for multiple APs, multiple AP group ID, and / or DAP ID).

[0251] D. Operation Channel: Information on the main channel and punch channel during operation.

[0252] For example, operational channel information may include channel information that is jointly operated for proper coordination among APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX).

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

[0254] For example, operational channel information may include puncturing channel information for APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, a new field can be defined as a disabled sub-channel bitmap field in the EHT operational information field to indicate the punctured 20MHz sub-channels using a bitmap. If a bit value in the bitmap is 0, it indicates that the corresponding 20MHz sub-channel is not punctured. If a bit value in the bitmap is 1, it indicates that the corresponding 20MHz sub-channel is punctured.

[0255] For example, operational channel information may include information about the DAP's primary channel within the channel operated by SAP.

[0256] For example, the operation channel information may include information about the DAP's main channel within the operation channels excluding SAP's punched channels.

[0257] E. Operational bandwidth information: Bandwidth and maximum bandwidth information during operation.

[0258] For example, operational bandwidth information may include information about the bandwidth (BW) that is shared by APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, the aforementioned operational channel and master channel information may be utilized.

[0259] For example, operational bandwidth information may include the maximum bandwidth information of the APs participating in multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX). In some implementations, a new field can be defined in the control field of the EHT operational information field to indicate the channel width (i.e., the BSS BW information for each AP), as follows: - Set to 0: Indicates a bandwidth of 20MHz - Set to 1: Indicates a 40MHz bandwidth - Set to 2: Indicates 80MHz bandwidth - Set to 3: Indicates 160 / 80+80MHz bandwidth - Set to 4: Indicates 320 / 160+160MHz bandwidth - The remaining values ​​from 5 to 7 can be retained.

[0260] For example, operational bandwidth information may include the BW field information in the SIG-A field.

[0261] For example, operational bandwidth information may include UL BW field information included in the public information field of MU-RTS TXS TF.

[0262] For example, operational bandwidth information may include information about the bandwidth of the DAP within the entire bandwidth of SAP operations.

[0263] For example, a new field for bandwidth indication (i.e., operational bandwidth information) can be added by modifying / redefining it to include a new subfield within the media time field of the QoS characteristic element. In some implementations, a new field can be defined within the control field of the EHT operational information field to indicate the channel width (i.e., the BSS BW information for each AP), as follows: - Set to 0: Indicates a bandwidth of 20MHz - Set to 1: Indicates a 40MHz bandwidth - Set to 2: Indicates 80MHz bandwidth - Set to 3: Indicates 160 / 80+80MHz bandwidth - Set to 4: Indicates 320 / 160+160MHz bandwidth - The remaining values ​​from 5 to 7 can be retained.

[0264] F. Required TXOP Duration: Information related to the duration of the TXOP that each AP intends to share.

[0265] For example, a new field including the required TXOP duration can be defined. In some implementations, the required duration field is defined to indicate the information required for multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX) and the required TXOP duration value. In some implementations, a Co-TDMA operation element is defined to indicate the information required for multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX) and the required TXOP duration value.

[0266] For example, the required TXOP duration can be included in a QoS feature element that can be used to include negotiation / coordination information during the pre-negotiation process of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX), or it can be included in an element that can be newly defined for negotiation of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP selection, J-TX).

[0267] For example, the required TXOP duration can be included in a UHR operation element that can be used to include broadcast information during the broadcast process of each AP in a multi-AP operation (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP Selection, J-TX), or it can be included in an element that can be newly defined for broadcasting of multi-AP operations (e.g., Co-TDMA, C-OFDMA, Co-SR, Co-BF, AP Selection, J-TX).

[0268] G. Buffer Status: Buffer status information for each AP

[0269] H. TXOP Sharing Requirement: Indicates whether TXOP sharing is required based on the expiration of pre-negotiated low-latency service information and / or when TXOP sharing becomes unnecessary (e.g., in the case of a separate FE already executed). For example, 1 bit can be used to indicate and / or respond to whether TXOP sharing is required. Bit 0 can indicate that the AP (e.g., a DAP that has received a select request frame) does not need TXOP sharing. Bit 1 can indicate that the AP (e.g., a DAP that has received a select request frame) needs TXOP sharing.

[0270] I. Low-latency service information: Information related to the low-latency services that each AP intends to send or receive.

[0271] For example, low-latency service information can be included in the information of a QoS feature element, which is included in the SCS request / response frame.

[0272] For example, the delay threshold field information in the QoS feature element information can be utilized. In some implementations, the value of the delay threshold field for the QoS service that each AP intends to send can be used as low-latency service information. If the pre-negotiated low-latency service information is changed, updated low-latency service information or delay threshold field values ​​can be included.

[0273] For example, the MSDU lifetime field information in the QoS feature element information can be utilized. In some implementations, the value of the MSDU lifetime field of the QoS service that each AP intends to send can be used as low-latency service information. If the pre-negotiated low-latency service information is changed, updated low-latency service information or MSDU lifetime field values ​​can be included.

[0274] For example, the service start time field information within the QoS feature element information can be utilized. In some implementations, the value of the service start time field for the QoS service that each AP intends to send can be used as low-latency service information. If the pre-negotiated low-latency service information is changed, updated low-latency service information or service start time field values ​​can be included.

[0275] For example, low-latency service information may include TXOP sharing request information requested / indicated by the AP that needs to send low-latency services.

[0276] For example, low-latency service information may include time limit information for low-latency services requested / indicated by the AP that needs to transmit the low-latency service (e.g., the minimum time limit at which the transmission of the low-latency service should begin / the maximum time limit at which the transmission of the low-latency service should be successfully completed).

[0277] For example, low-latency service information may include arrival rate information for low-latency services requested / instructed by the AP that needs to send periodic low-latency services (e.g., the arrival rate of low-latency services since the last reported event).

[0278] For example, low-latency service information may include service identifier (TID) / access class (AC) information.

[0279] Figure 21 An example of an unsolicited resource reporting process utilizing QoS data / empty frames according to an embodiment of this disclosure is shown.

[0280] refer to Figure 21 A sending AP (e.g., AP 2 / DAP) can use QoS data / QoS empty frames to send / execute unsolicited resource reports to multiple APs (e.g., AP1 / SAP, AP 3 / DAP). When an AP included in a multi-AP set configured through a multi-AP set establishment process (or negotiation process) needs to update its own resource information, the sending AP can deliver a QoS data / QoS empty frame to the APs included in the multi-AP set, including information sent for multi-AP coordination and / or based on multi-AP coordination (or updated negotiation information / coordination information / resource information), to notify them of the updated resource information. In this case, if the RA field of the QoS data / QoS empty frame is set to the address of a single / specific coordinating AP (e.g., an AP that has already performed the negotiation process / APs included in the multi-AP set), the AID field can be set to any value. An AP that has received the QoS data / QoS empty frame can update the corresponding resource information if it has any, and can send an acknowledgment (ACK) frame in response to receiving the QoS data / QoS empty frame. Through this unsolicited resource reporting process, sending APs can voluntarily notify them of changes in their resource information, and receiving APs can update multi-AP coordination-related information (or, negotiation information / coordination information / resource information) within a short period. Receiving APs that have received updated resource information can support more efficient multi-AP coordination-based sending when they acquire TXOP and assume the SAP role. For example, unnecessary coordination can be prevented.

[0281] Figure 22 An example of an unsolicited resource reporting process using MU-RTS TF according to an embodiment of this disclosure is shown.

[0282] refer to Figure 22The sending AP (e.g., AP 2 / DAP) can use a MU-RTS TF (e.g., MU-RTS TXS TF) to send / execute unsolicited resource reports to multiple APs (e.g., AP 1 / SAP, AP 3 / DAP). When an AP in a multi-AP set configured through a multi-AP set establishment process (or negotiation process) needs to update its own resource information, the sending AP can deliver a MU-RTS TF containing information for multi-AP coordination and / or based on multi-AP coordination (or updated negotiation / coordination information / resource information) to the APs in the multi-AP set to notify them of the updated resource information. Information for APs in a coordination relationship can be included separately in the user information field of the MU-RTS TF. On the other hand, if the RA field of the MU-RTS TF is set to the address of a single DAP, the AID field can be set to any value. An AP that has received a MU-RTS trigger frame can update the corresponding resource information if it has resource information to update, and can send a transmit permission (CTS) frame in response to receiving a MU-RTS TF. Through this unsolicited resource reporting process, sending APs can voluntarily notify them of changes in their resource information, and receiving APs can update multi-AP coordination-related information (or, negotiation information / coordination information / resource information) within a short period. Receiving APs that have received updated resource information can support more efficient multi-AP coordination-based sending when they acquire TXOP and assume the SAP role. For example, unnecessary coordination can be prevented.

[0283] Figure 23 An example of an unsolicited resource reporting process utilizing management frames according to an embodiment of this disclosure is shown.

[0284] refer to Figure 23A sending AP (e.g., AP 2 / DAP) can use a management frame (Mgmt. frame) to send / execute unsolicited resource reports to multiple APs (e.g., AP 1 / SAP, AP 3 / DAP). When an AP included in a multi-AP set configured through a multi-AP set establishment process (or negotiation process) needs to update its own resource information, the sending AP can deliver a management frame to the APs included in the multi-AP set, containing information for multi-AP coordination and / or based on multi-AP coordination (or updated negotiation information / coordination information / resource information), to notify them of the updated resource information. In this case, the RA field of the management frame can be set to the address of a single / specific coordinating AP (e.g., an AP that has already performed a negotiation process / APs included in the multi-AP set). An AP that has received the management frame can update the corresponding resource information if it has any to update, and can send an acknowledgment (ACK) frame in response to receiving the management frame. Through such an unsolicited resource reporting process, the sending AP can voluntarily notify of changes in its resource information, and the receiving AP can update multi-AP coordination-related information (or negotiation information / coordination information / resource information) within a short period. Receiving APs that have received updated resource information can support more efficient multi-AP coordinated transmission when they acquire TXOP and assume the SAP role. For example, unnecessary coordination can be prevented.

[0285] This disclosure presents various implementations for APs participating in multi-AP coordination to send / execute resource reports unsolicited. Specifically, according to embodiments of this disclosure, APs can deliver frames (or resource report frames) for resource reporting unsolicited / separately without any separate request from APs in the coordination relationship regarding changes to information related to multi-AP coordination (e.g., negotiation information / coordination information / resource information). In this case, APs in the coordination relationship that have received the unsolicited frame for resource reporting can update the corresponding AP's multi-AP coordination information (or resource information). Such information sent for and / or based on multi-AP coordination (e.g., negotiation information / coordination information / resource information) can later be used for scheduling multi-AP coordination operations of APs used as SAPs.

[0286] The technical features described above in this disclosure can be applied to various apparatuses and methods. For example, the technical features described above in this disclosure can be used by... Figure 1 and / or Figure 5 The device is used to perform / support this. For example, the above-described technical features of this disclosure can be applied only to... Figure 1 and / or Figure 5 Part of it. For example, the above-described technical features of this disclosure can be based on Figure 1Implemented using processing chips 114 and 124, or based on Figure 1 Implemented by processors 111, 121 and memories 112, 122, or based on Figure 5 This is achieved through the processor 510 and memory 520.

[0287] For example, Figure 1 The processor 121 and / or processing chip 124 may be configured to execute instructions stored in memory 122 to implement the method performed by the first AP in this disclosure. The method includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, updating at least one resource configuration in the resource information of the first AP sent by the first AP to a second AP in the multi-AP set during the negotiation process; and sending a resource report frame to the second AP including information regarding the updated at least one resource configuration.

[0288] For example, Figure 1 The processor 111, the processing chip 114 and / or Figure 5 The processor 510 can be configured to execute instructions stored in memories 112, 520 to implement the method performed by the second AP in this disclosure. The method includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, receiving a resource report frame from a first AP in the multi-AP set, including information regarding at least one resource configuration; and updating the at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP during the negotiation process.

[0289] The technical features of this disclosure can be implemented based on a computer-readable medium (CRM) (e.g., a non-transitory CRM). For example, the CRM in this disclosure may include at least one CRM having program code stored thereon that implements instructions executable by at least one processor.

[0290] For example, CRM can be Figure 1 The memory 122 and / or separate external memory / storage medium / disk. The CRM can store instructions based on those generated by the processor (e.g., Figure 1The processor 121 and / or processing chip 124 executes the method performed by the first AP in this disclosure. The method includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, updating at least one resource configuration in the resource information of the first AP sent by the first AP to a second AP in the multi-AP set during the negotiation process; and sending a resource report frame including information for the updated at least one resource configuration to the second AP.

[0291] For example, CRM can be Figure 1 memory 112, Figure 5 The CRM may store 520 memory and / or separate external memory / storage medium / disk. The CRM may store instructions based on those generated by the processor (e.g., ...). Figure 1 The processor 111, the processing chip 114 and / or Figure 5 The processor 510 executes the method performed by the second AP in this disclosure. The method includes: performing a negotiation process with one or more APs for multi-AP coordination; obtaining a configuration of a multi-AP set including one or more APs based on the negotiation process; after obtaining the configuration of the multi-AP set, receiving a resource report frame from a first AP in the multi-AP set including information for at least one resource configuration; and updating the at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP during the negotiation process.

[0292] The aforementioned technical features of this disclosure are applicable to various applications or business models. For example, the aforementioned technical features can be applied to wireless communication in devices that support artificial intelligence (AI).

[0293] Artificial intelligence (AI) refers to the field of research concerning artificial intelligence or the methods used to create it, while machine learning refers to the field of research concerning methods for defining and solving various problems within the field of AI. Machine learning is also defined as an algorithm that improves operational performance through stable operational experience.

[0294] Artificial neural networks (ANNs) are models used in machine learning, and can refer to models that solve problems in general, including artificial neurons (nodes) that form a network by combining synapses. An artificial neural network 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 the output value.

[0295] An artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer includes one or more neurons, and the artificial neural network may include synapses connecting the neurons. In an artificial neural network, each neuron can output the value of an activation function of the input signal input through synapses, weights, and biases.

[0296] Model parameters refer to the parameters determined through learning, and include the weights of synaptic connections and the biases of neurons. Hyperparameters refer to the parameters that are set before learning in a machine learning algorithm, and include the learning rate, number of iterations, minimum batch size, and initialization function.

[0297] Learning artificial neural networks may aim to determine model parameters used to minimize a loss function. The loss function can be used as a metric for determining the optimal model parameters during the learning process of an artificial neural network.

[0298] Machine learning can be divided into supervised learning, unsupervised learning, and reinforcement learning.

[0299] Supervised learning refers to the method of training an artificial neural network using labels provided for the training data. When the training data is input into the artificial neural network, the labels indicate the correct answer (or result value) that the network should infer. Unsupervised learning refers to the method of training an artificial neural network without providing labels for the training data. Reinforcement learning can be a training method used to train an agent defined in an environment to select actions or sequences of actions to maximize the cumulative reward in each state.

[0300] Machine learning implemented using deep neural networks (DNNs) with multiple hidden layers is called deep learning, and deep learning is a part of machine learning. In the following text, machine learning is interpreted as including deep learning.

[0301] The aforementioned technical features can be applied to wireless communication for robots.

[0302] A robot can be defined as a machine that automatically processes or operates a given task using its own capabilities. In particular, a robot that has the ability to recognize its environment and make autonomous judgments to perform operations can be called an intelligent robot.

[0303] Depending on their application or field, robots can be categorized into industrial, medical, household, and military robots, among others. Robots can include actuators or drives that include motors to perform various physical operations, such as moving robot joints. Additionally, mobile robots can include wheels, brakes, propellers, etc., in their drives to move on the ground or fly in the air.

[0304] The aforementioned technical features can be applied to devices that support extended reality.

[0305] Extended reality is collectively referred to as virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology is a computer graphics technology that provides real-world objects and backgrounds only in CG images; AR technology is a computer graphics technology that provides virtual CG images on top of real object images; and MR technology is a computer graphics technology that provides virtual objects that are mixed and combined with the real world.

[0306] MR technology is similar to AR technology in that it can display real and virtual objects together. However, in AR technology, virtual objects are used as a supplement to real objects, while in MR technology, virtual and real objects are used as equals.

[0307] XR technology can be applied to head-mounted displays (HMDs), head-up displays (HUDs), mobile phones, tablets, laptops, desktop computers, televisions, digital signage, and more. Devices that utilize XR technology can be referred to as XR devices.

[0308] This disclosure can have various beneficial effects.

[0309] For example, according to embodiments of this disclosure, an AP can deliver frames (or resource report frames) for resource reporting unsolicited / separately without any separate request from an AP in a coordination relationship regarding changes to information related to multi-AP coordination (e.g., negotiation information / coordination information / resource information). In this case, an AP in a coordination relationship that has received the unsolicited frame for resource reporting can update the corresponding AP's multi-AP coordination information (or resource information). Such information transmitted for and / or based on multi-AP coordination (e.g., negotiation information / coordination information / resource information) can later be used for scheduling multi-AP coordination operations of an AP used as an SAP.

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

[0311] The claims in this disclosure can be combined in various ways. For example, the technical features in the method claims of this disclosure can be combined to be implemented or performed in an apparatus, and the technical features in the apparatus claims can be combined to be implemented or performed in a method. Furthermore, the technical features in the method claims and apparatus claims can be combined to be implemented or performed in an apparatus, and the technical features in the method claims and apparatus claims can be combined to be implemented or performed in a method.

Claims

1. A method comprising the following steps: The negotiation process for multi-AP coordination is performed by the first access point (AP) and one or more other APs. The configuration of a multi-AP set, including one or more APs, is obtained by the first AP based on the negotiation process; After obtaining the configuration of the multi-AP set, the first AP updates at least one resource configuration in the resource information of the first AP sent by the first AP to the second AP in the multi-AP set during the negotiation process; as well as The first AP sends a resource report frame, which includes information about the updated configuration of the at least one resource, to the second AP.

2. The method according to claim 1, wherein, The steps for performing the negotiation process include the following: The first AP sends a coordination request frame, including the resource information of the first AP, to the second AP; and The first AP receives a coordination response frame from the second AP in response to the coordination request frame. The coordination response frame includes resource information of the second AP.

3. The method according to claim 1, wherein, The steps for performing the negotiation process include the following: The first AP receives a coordination request frame from the second AP, which includes resource information of the second AP; and The first AP sends a coordination response frame to the second AP in response to the coordination request frame. The coordination response frame includes the resource information of the first AP.

4. The method according to claim 1, wherein, The resource information of the first AP includes at least one of the following: The identifier ID of the multi-AP set; The ID of the first AP; The address of the first AP; Information regarding the dynamic channel of the first AP; Information regarding the operating bandwidth of the first AP; Information regarding the transmission opportunities (TXOPs) required for the first AP; Information regarding the buffer state of the first AP; Regarding whether the first AP needs TXOP sharing information; or Low-latency service information for the first AP.

5. The method according to claim 4, wherein, The at least one resource configuration includes all or part of the resource configurations included in the resource information of the first AP.

6. The method according to claim 1, wherein, The resource report frame is a Quality of Service (QoS) data frame or a QoS empty frame, and The method further includes the following steps: after sending the QoS data frame or the QoS empty frame, the first AP receives an ACK frame from the second AP for the QoS data frame or the QoS empty frame.

7. The method according to claim 1, wherein, The resource report frame is a multi-user MU request sent RTS trigger frame, and The method further includes the following steps: after sending the MU-RTS trigger frame, the first AP receives a CTS frame from the second AP that allows transmission of the MU-RTS trigger frame.

8. The method according to claim 1, wherein, The resource report frame is a management frame. The method further includes the following steps: after sending the management frame, the first AP receives an ACK frame for the management frame from the second AP.

9. The method according to claim 1, wherein, The receiver address (RA) field of the resource report frame is set to the address of the second AP, and The AID field of the resource report frame is set to a value that is not related to the second AP.

10. The method according to claim 1, wherein, The step of sending the resource report frame includes the following steps: the first AP sends the resource report frame to the second AP if it has not received a frame from the second AP requesting the resource report frame.

11. The method according to claim 1, wherein, The at least one resource configuration is updated after the negotiation process and before the next negotiation process, and The resource report frame, which includes the at least one resource configuration, is sent when the at least one resource configuration is updated.

12. The method according to claim 1, further comprising the following steps: The first AP performs multi-AP operations with the second AP based on the updated resource configuration of the at least one resource.

13. A first access point (AP), the first AP comprising: transceiver; Memory; as well as At least one processor, said at least one processor being operatively coupled to the transceiver and the memory, The memory stores instructions, which perform operations based on execution by the at least one processor, the operations including: Perform a negotiation process with one or more APs for multi-AP coordination; Based on the negotiation process, a configuration of a multi-AP set including one or more APs is obtained; After obtaining the configuration of the multi-AP set, at least one resource configuration is updated in the resource information of the first AP sent by the first AP to the second AP in the multi-AP set during the negotiation process; and Send a resource report frame to the second AP, including information about the updated configuration of the at least one resource.

14. An apparatus, the apparatus comprising: At least one processor; as well as At least one memory, said at least one memory being operatively coupled to said at least one processor. Wherein, the at least one memory stores instructions, the instructions performing operations based on execution by the at least one processor, the operations including: Perform a negotiation process with one or more APs for multi-AP coordination; Based on the negotiation process, a configuration of a multi-AP set including one or more APs is obtained; After obtaining the configuration of the multi-AP set, at least one resource configuration is updated in the resource information of the first AP sent by the first AP to the second AP in the multi-AP set during the negotiation process; and Send a resource report frame to the second AP, including information about the updated configuration of the at least one resource.

15. A non-transitory computer-readable medium (CRM) storing program code, the program code implementing instructions that perform operations based on execution by at least one processor, the operations including: Perform a negotiation process with one or more APs for multi-AP coordination; Based on the negotiation process, a configuration of a multi-AP set including one or more APs is obtained; After obtaining the configuration of the multi-AP set, at least one resource configuration is updated in the resource information of the first AP sent by the first AP to the second AP in the multi-AP set during the negotiation process; as well as Send a resource report frame to the second AP, including information about the updated configuration of the at least one resource.

16. A method comprising the steps of: The negotiation process for multi-AP coordination is performed by the second access point (AP) and one or more APs. The second AP obtains a configuration of a multi-AP set including one or more APs based on the negotiation process; After obtaining the configuration of the multi-AP set, the second AP receives a resource report frame from the first AP in the multi-AP set, which includes information on the configuration of at least one resource. as well as The at least one resource configuration is updated by the second AP in the resource information of the first AP sent from the first AP to the second AP during the negotiation process.

17. A second access point (AP), the second AP comprising: transceiver; Memory; as well as At least one processor, said at least one processor being operatively coupled to the transceiver and the memory, The memory stores instructions, which perform operations based on execution by the at least one processor, the operations including: Perform a negotiation process with one or more APs for multi-AP coordination; Based on the negotiation process, a configuration of a multi-AP set including one or more APs is obtained; After obtaining the configuration of the multi-AP set, a resource report frame including information on at least one resource configuration is received from the first AP in the multi-AP set; and During the negotiation process, the resource information of the first AP sent by the first AP to the second AP is updated with the at least one resource configuration.

18. The second AP according to claim 17, wherein, The resource report frame is a management frame, and The operation further includes: after receiving the management frame, sending an ACK frame to the first AP in response to the management frame.

19. The second AP according to claim 17, wherein, The operation further includes receiving the resource report frame from the first AP without sending a frame to the first AP requesting the resource report frame.

20. The second AP according to claim 17, wherein, The resource report frame is received from the first AP after the negotiation process and before the next negotiation process.

Images