Apparatus and method for coordinated transmissions in wireless network

Abstract

The present disclosure relates to a shared AP (110) for sharing a transmission opportunity (TXOP) with a plurality of shared APs (120), the plurality of shared APs (120) operating under a coordination protocol within a set of M-APs, for participating in a coordinated transmission to one or more non-AP sites (115a to 115c) associated with the shared AP and a plurality of other non-AP sites (125a to 125c) associated with the shared AP (120). The shared AP (110) is configured to receive completion state information from one or more of the plurality of shared APs (120), the completion status information indicates a completion status of sending information related to operation under the coordination protocol to one or more other non-AP sites (125a-125c) of the plurality of other non-AP sites (125a-125c) associated with the respective shared AP (120). Further, the shared AP (110) is configured to generate and maintain a data structure indicating the completion status of each of the plurality of shared APs (120) based on the completion status information for each of the one or more shared APs of the plurality of shared APs (120).

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to devices and methods for coordinating transmissions in wireless communication networks, particularly in IEEE 802.11-based WLANs. Background Art

[0002] IEEE 802.11-based WLANs (also known as Wi-Fi networks) are proliferating at an unprecedented rate. 802.11be discusses coordinated transmissions among multiple access points (M-APs), such as coordinated beamforming transmissions. In coordinated transmissions, a group of access points (APs) can initiate concurrent frame exchanges within a limited time period, with each participating AP utilizing the entire bandwidth. One or more APs in the group can share one or more transmission opportunities (TXOPs), including the sharing AP and one or more shared APs. The group of APs that have decided to cooperate to perform coordinated transmissions is called an M-AP set. Summary of the Invention

[0003] The object is to provide an improved device and method for M-AP coordinated transmission in a wireless communication network, particularly in a WLAN based on IEEE 802.11.

[0004] The above and other objects are achieved by the subject matter claimed in the independent claims. Other implementations are apparent from the dependent claims, the description and the drawings.

[0005] According to a first aspect, a shared access point (AP) is provided, wherein the shared AP is configured to share at least a portion of a transmission opportunity (TXOP) obtained using a plurality of shared APs, the plurality of shared APs operating under a coordination protocol within a multi-AP (M-AP) set to participate in coordinated transmissions with one or more non-AP stations associated with the shared AP and a plurality of other non-AP stations associated with the plurality of shared APs. The shared AP includes a communication interface configured to receive completion status information, specifically a completion station information frame, from one or more of the shared APs, wherein the completion status information frame received from each of the one or more shared APs indicates a completion status of successfully sending information related to operation under the coordination protocol to one or more of the plurality of other non-AP stations associated with the corresponding shared AP. In addition, the shared AP includes processing circuitry configured to generate and maintain a data structure based on the completion status information frame of each shared AP in one or more of the plurality of shared APs, wherein the data structure indicates the completion status of each shared AP in the plurality of shared APs. In one implementation, the data structure may further indicate a completion status of the shared AP successfully transmitting information related to operation under the coordination protocol to the one or more non-AP stations associated with the shared AP.

[0006] In another possible implementation, the communication interface is configured to send the data structure to each shared AP among the multiple shared APs, and in particular, perform the above operation before a current transmission opportunity ends.

[0007] In another possible implementation, the communication interface is configured to send a status indication frame to the multiple shared APs, wherein the indication frame includes the data structure.

[0008] In another possible implementation, the status indication frame further includes an address (specifically, a MAC address) and / or an identifier of the sharing AP and / or each shared AP in the multiple shared APs.

[0009] In another possible implementation manner, the status indication frame further includes an M-AP set identifier indicating the M-AP set.

[0010] In another possible implementation, the indication status frame also includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0011] In another possible implementation, the data structure includes each shared AP of the plurality of shared APs operating under a same coordination protocol and an indication of the completion status of the shared AP.

[0012] In another possible implementation manner, the data structure includes (ie, is implemented as) a lookup table.

[0013] In another possible implementation, the communication interface is also used to send one or more M-AP trigger frames (specifically one or more M-AP trigger frames for indication within the BSS) to one or more shared APs among the multiple shared APs, so as to trigger (i.e., request) the corresponding shared AP to provide the information related to the operation under the coordination protocol to the one or more other non-AP sites associated with the corresponding shared AP.

[0014] In another possible implementation, the communication interface is used to send the one or more M-AP trigger frames to the one or more shared APs among the multiple shared APs to trigger the corresponding shared AP to provide the information related to the operation under the coordination protocol to the one or more other non-AP sites among the multiple other non-AP sites associated with the corresponding shared AP, wherein, for the one or more shared APs, the data structure indicates that the corresponding shared AP has not yet completed the relevant process within the BSS, for example, the corresponding shared AP has not yet completed sending the information related to the operation under the coordination protocol to the one or more other non-AP sites among the multiple other non-AP sites associated with the corresponding shared AP.

[0015] In another possible implementation manner, the one or more M-AP trigger frames include an address (specifically, a MAC address) and / or an identifier of the sharing AP and / or each shared AP in the multiple shared APs.

[0016] In another possible implementation manner, the one or more M-AP trigger frames include an M-AP set identifier indicating the M-AP set.

[0017] In another possible implementation, the one or more M-AP trigger frames include a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0018] In another possible implementation, the processing circuit is used to limit the coordinated transmission to those shared APs among the multiple shared APs, among which the shared AP has indicated its status information as "completed", and to limit it to those shared APs among the multiple shared APs, for which the data structure indicates the completion status as "completed".

[0019] In another possible implementation manner, the information related to the operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

[0020] In another possible implementation, the information related to the operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the shared AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0021] In another possible implementation manner, the information related to the operation under the coordination protocol includes an address (specifically, a MAC address) and / or an identifier of each shared AP in the multiple shared APs.

[0022] In another possible implementation, the shared AP further includes a memory, where the memory is used to store the data structure.

[0023] According to a second aspect, a method of operating a shared access point (AP) is provided, wherein the shared AP is configured to share at least a portion of a transmission opportunity (TXOP), the TXOP being acquired using a plurality of shared APs, the plurality of shared APs operating under a coordination protocol within a multi-AP (Multi-AP, M-AP) set to participate in coordinated transmissions with one or more non-AP stations associated with the shared AP and a plurality of other non-AP stations associated with the plurality of shared APs. The method comprises the following steps:

[0024] receiving completion status information, specifically a completion status information frame, from one or more shared APs of the plurality of shared APs, wherein the completion status information frame received from each of the one or more shared APs of the plurality of shared APs indicates a completion status of successfully sending information related to operation under the coordination protocol to one or more other non-AP stations of the plurality of other non-AP stations associated with the corresponding shared AP; and

[0025] A data structure is generated and maintained based on the completion status information frame of each of the one or more shared APs in the plurality of shared APs operating under the coordination protocol, wherein the data structure indicates the completion status for each of the plurality of shared APs. In one implementation, the data structure may further indicate a completion status of the shared AP successfully sending information related to operation under the coordination protocol to the one or more non-AP stations associated with the shared AP.

[0026] The method provided in the second aspect of the present disclosure can be performed by the shared AP provided in the first aspect of the present disclosure. In addition, other features of the method provided in the second aspect of the present disclosure are directly derived from the functions of the shared AP provided in the first aspect of the present disclosure and its different implementations described above and below.

[0027] According to a third aspect, a shared access point (AP) is provided, wherein the shared AP is configured to participate in coordinated transmissions with one or more non-AP stations associated with the shared AP and one or more other non-AP stations associated with the shared AP using at least a portion of a transmission opportunity (TXOP), wherein the TXOP is acquired and shared by the shared AP operating under a coordination protocol within a multi-AP (M-AP) set. The shared AP includes a communication interface configured to send information related to operation under the coordination protocol to the one or more non-AP stations associated with the shared AP (i.e., stations of the shared AP's BSS). The communication interface is further configured to send completion status information, specifically a completion status information frame, to the shared AP, wherein the completion status information frame indicates a completion status of successfully sending the information related to operation under the coordination protocol to the one or more non-AP stations associated with the corresponding shared AP.

[0028] In another possible implementation, the communication interface is further used to receive a data structure from the shared AP, wherein the data structure indicates the completion status of sending the information related to the operation under the coordination protocol to one or more non-AP sites associated with the shared AP and the corresponding other shared APs for the shared AP and each of the multiple other shared APs operating under the coordination protocol within the M-AP set.

[0029] In another possible implementation manner, the communication interface is configured to receive a status indication frame from the shared AP, wherein the status indication frame includes the data structure.

[0030] In another possible implementation, the status indication frame further includes an address (specifically, a MAC address) and / or an identifier of the sharing AP and / or the shared AP.

[0031] In another possible implementation manner, the status indication frame further includes an M-AP set identifier indicating the M-AP set.

[0032] In another possible implementation, the indication status frame also includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0033] In another possible implementation, the data structure includes an indication of the completion status of the sharing AP and each of the multiple shared APs operating under the same coordination protocol.

[0034] In another possible implementation manner, the data structure includes (ie, is implemented as) a lookup table.

[0035] In another possible implementation, the communication interface is used to provide the information related to the operation under the coordination protocol to the one or more non-AP sites associated with the shared AP (i.e., the BSS sites of the shared AP) after receiving an M-AP trigger frame (specifically, an M-AP trigger frame for indication within the BSS) from the shared AP.

[0036] In another possible implementation manner, the M-AP trigger frame includes an address (specifically, a MAC address) and / or an identifier of the sharing AP and / or each shared AP in the multiple shared APs.

[0037] In another possible implementation manner, the M-AP trigger frame includes an M-AP set identifier indicating the M-AP set.

[0038] In another possible implementation, the M-AP trigger frame includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0039] In another possible implementation manner, the information related to the operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

[0040] In another possible implementation, the information related to the operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the shared AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0041] In another possible implementation, the information related to the operation under the coordination protocol includes the address (specifically MAC address) and / or identifier of each shared AP in the multiple shared APs operating under the same coordination protocol within the M-AP set.

[0042] In another possible implementation, the shared AP further includes a memory, where the memory is used to store the data structure.

[0043] In another possible implementation, the communication interface is further used to receive a confirmation message (specifically, a confirmation frame) from each of the one or more non-AP sites associated with the shared AP in response to sending the information related to the operation under the coordination protocol to the one or more non-AP sites associated with the shared AP (i.e., the BSS sites of the shared AP).

[0044] According to a fourth aspect, a method of operating a shared access point (AP) is provided, wherein the shared AP is configured to participate in coordinated transmissions with one or more non-AP stations associated with the shared AP and one or more other non-AP stations associated with the sharing AP using at least a portion of a transmission opportunity (TXOP), wherein the TXOP is acquired and shared by the sharing AP operating under a coordination protocol within a multi-AP (M-AP) set. The method comprises the following steps:

[0045] Sending information related to operation under the coordination protocol to the one or more non-AP stations associated with the shared AP (i.e., BSS stations of the shared AP); and

[0046] Sending completion status information, specifically a completion status information frame, to the shared AP, wherein the completion status information frame indicates the completion status of successfully sending the information related to the operation under the coordination protocol to the one or more non-AP sites associated with the corresponding shared AP.

[0047] The method provided in the fourth aspect may further include receiving an M-AP trigger frame from the shared AP, and after receiving the M-AP trigger frame from the shared AP (specifically in response to receiving the M-AP trigger frame from the shared AP), sending the information related to the operation under the coordination protocol to the one or more non-AP sites associated with the shared AP.

[0048] The method provided in the fourth aspect of the present disclosure may be performed by the shared AP provided in the third aspect of the present disclosure. In addition, other features of the method provided in the fourth aspect of the present disclosure are directly derived from the functions of the shared AP provided in the third aspect of the present disclosure and its different implementations described above and below.

[0049] According to a fifth aspect, a non-access point (non-AP) station associated with a shared AP is provided, wherein the shared AP is configured to participate in coordinated transmissions with the non-AP station associated with the shared AP and multiple other non-AP stations associated with the shared AP or a sharing AP using at least a portion of a transmission opportunity (TXOP), the TXOP being acquired and shared by the shared AP operating under a coordination protocol within a multi-AP (Multi-AP, M-AP) set. The non-AP station includes a communication interface configured to receive information related to operation under the coordination protocol from the shared AP. The communication interface is further configured to send an acknowledgment, specifically an acknowledgment frame, to the shared AP in response to successfully receiving the information related to operation under the coordination protocol from the shared AP.

[0050] In another possible implementation manner, the information related to the operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

[0051] In another possible implementation, the information related to the operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the shared AP and the multiple shared APs operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

[0052] In another possible implementation manner, the information related to the operation under the coordination protocol includes an address (specifically, a MAC address) and / or an identifier of each shared AP in the multiple shared APs.

[0053] According to a sixth aspect, a method for operating a non-access point (non-AP) station associated with a shared AP is provided, wherein the shared AP is configured to participate in coordinated transmissions with the non-AP station associated with the shared AP and multiple other non-AP stations associated with the shared AP or a sharing AP using at least a portion of a transmission opportunity (TXOP), the TXOP being acquired and shared by the sharing AP operating under a coordination protocol within a multi-AP (M-AP) set. The method comprises the following steps:

[0054] receiving information related to operation under the coordination protocol from the shared AP;

[0055] In response to receiving the information related to the operation under the coordination protocol from the shared AP, sending an acknowledgement, in particular an acknowledgement frame, to the shared AP.

[0056] The method provided in the sixth aspect of the present disclosure may be performed by the non-AP station provided in the fifth aspect of the present disclosure. Therefore, other features of the method provided in the sixth aspect of the present disclosure are directly derived from the functionality of the non-AP station provided in the fifth aspect of the present disclosure and the different implementations described above and below.

[0057] The following drawings and description set forth in detail one or more embodiments. Other features, objects, and advantages are apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The following describes the embodiments of the present disclosure in detail with reference to the accompanying drawings. In the accompanying drawings:

[0059] Figure 1 An exemplary wireless communication network provided by an embodiment is shown, which includes a sharing AP and multiple shared APs for coordinating transmission;

[0060] Figure 2 The structure of an M-AP frame provided by an embodiment for communicating with a shared AP provided by an embodiment for coordinated transmission is schematically shown, wherein the M-AP frame includes a coordination protocol identifier and an M-AP set identifier;

[0061] Figure 3a The different processing stages of M-AP coordination operation are shown, including coordinated transmission by traditional sharing APs and traditional shared APs;

[0062] Figure 3b The different processing stages of M-AP coordination operation are shown, including coordinated transmission implemented by a sharing AP provided by one embodiment and a shared AP provided by one embodiment;

[0063] Figure 4 A schematic diagram showing a data structure maintained and distributed by a shared AP provided by an embodiment is shown;

[0064] Figure 5 A schematic diagram illustrating signaling between a shared AP provided by an embodiment and two shared APs provided by an embodiment before coordinated transmission is shown;

[0065] Figure 6 A schematic diagram illustrating signaling between a sharing AP provided in one embodiment and three shared APs provided in one embodiment for different coordinated transmissions (specifically, transmission opportunities with different shared APs);

[0066] Figure 7 A schematic diagram illustrating signaling between a shared AP provided by an embodiment and two shared APs provided by an embodiment before coordinated transmission is shown;

[0067] Figure 8 A schematic diagram illustrating signaling between a shared AP provided by an embodiment, a shared AP provided by an embodiment, and multiple non-AP stations associated with the shared AP provided by an embodiment is shown;

[0068] Figure 9 is a flowchart illustrating a method for operating a shared AP provided by one embodiment;

[0069] Figure 10 is a flowchart illustrating a method for operating a shared AP provided by one embodiment;

[0070] Figure 11 FIG. 1 is a flowchart illustrating a method of operating a non-AP station associated with a shared AP provided by one embodiment.

[0071] In the following, identical reference numerals refer to identical or at least functionally equivalent features. DETAILED DESCRIPTION

[0072] In the following description, reference is made to the accompanying drawings that form part of the present disclosure, which illustrate specific aspects of the embodiments of the present disclosure or illustrate specific aspects in which the embodiments of the present disclosure can be used by way of illustration. It should be understood that the embodiments of the present disclosure can be used in other aspects and include structural or logical changes not depicted in the accompanying drawings. Therefore, the following detailed description should not be understood in a restrictive sense, and the scope of the present disclosure is defined by the appended claims.

[0073] For example, it should be understood that the disclosure related to the described method also applies to the corresponding device or system for performing the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units (e.g., functional units) to perform the one or more method steps described (e.g., one unit performs one or more steps, or multiple units perform one or more of the multiple steps respectively), even if such one or more units are not explicitly described or illustrated in the drawings. In addition, if a specific device is described based on one or more units such as functional units, the corresponding method may include steps that perform the functions of one or more units (e.g., one step performs the functions of one or more units, or multiple steps perform the functions of one or more of the multiple units respectively), even if such one or more steps are not explicitly described or illustrated in the drawings. In addition, it will be understood that, unless otherwise expressly stated, the features of the various exemplary embodiments and / or aspects described herein may be combined with each other.

[0074] Figure 1 FIG. 1 shows an exemplary wireless communication network 100 provided by one embodiment, which includes a sharing AP 110 having a plurality of associated non-AP stations 115a to 115c and a plurality of shared APs 120 having a corresponding plurality of associated non-AP stations 125a to 125c for coordinating transmissions. Figure 1 As shown, each of the plurality of APs 110, 120 defines a respective basic service set (BSS). As will be understood and described in more detail below, the sharing AP and the shared AP may be considered to be in Figure 1 The roles or functions provided by sharing AP 110 and shared AP 120 in the exemplary scenario shown may be reversed in further coordinated transmission cycles. In other words, in another coordinated transmission cycle (i.e., in another acquired TXOP), one of APs 120 may serve as a sharing AP, while AP 110 is one of the shared APs.

[0075] The wireless communication network 100 may be a WLAN (also referred to as a Wi-Fi network 100) in accordance with the IEEE 802.11 standard framework. Although by way of example, Figure 1 Three shared APs 120 and their associated non-AP sites 125a and 125b, and 125a through 125c are shown in FIG, but the embodiments disclosed herein may be implemented with more or less than three shared APs 120.

[0076] As an example, Figure 1 The sharing AP 110 and shared AP 120 shown in FIG. 1 may implement a coordinated beamforming transmission scheme (also known as CoBF transmission). However, as will be appreciated, the embodiments disclosed herein may also be implemented with other types of coordinated transmission schemes. CoBF transmission is a coordinated scheme proposed for next-generation Wi-Fi, enabling simultaneous data transmission by multiple APs. This coordinated scheme assumes that each participating AP is capable of precoding its transmitted signal to minimize mutual interference (also known as nulling) between the AP and STAs in overlapping BSSs (OBSSs) during the coordinated transmission. Similar to all other coordinated schemes, CoBF is initiated by the sharing AP, which proposes that other APs (referred to as shared APs) transmit simultaneously. In this case, the proposed resources are spatial streams, with the sharing AP allocating a specific number of spatial streams to each shared AP. CoBF may utilize an additional sounding process to estimate the channel between the AP and non-AP stations. Based on the estimated channel, the AP may construct a precoder matrix for generating beams and nulls for the non-AP stations participating in the current CoBF transmission.

[0077] Figure 1 The shared AP 110 shown in FIG is used to share at least a portion of its acquired transmission opportunity (TXOP) with the shared AP 120, wherein the shared AP 120 operates under the same coordination protocol within a multi-AP set (also referred to as an M-AP set) and is used to participate in coordinated transmission, such as coordinated beamforming transmission. Figure 1 As shown, the shared AP 110 includes a processing circuit 111 and a communication interface 113, specifically a wireless communication interface 113 according to the IEEE 802.11 standard framework. The processing circuit 111 can be implemented in hardware and / or software, and can include digital circuits, or both analog circuits and digital circuits. The digital circuit can include components such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), or a general-purpose processor. The shared AP 110 may also include a memory 114 for storing executable program code that, when executed by the processing circuit 111, enables the shared AP 110 to perform the functions and methods described herein.

[0078] Likewise, Figure 1 Each of the shared APs 120 shown includes a processing circuit 121 and a communication interface 123, specifically a wireless communication interface 123 according to the IEEE 802.11 standard framework. The processing circuit 121 can be implemented in hardware and / or software and can include digital circuits, or both analog circuits and digital circuits. The digital circuits can include components such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or general-purpose processors. Each shared AP 120 can also include a memory 124 for storing executable program code that, when executed by the processing circuit 121, causes the shared AP 120 to perform the functions and methods described herein.

[0079] Likewise, each non-AP station (e.g. Figure 1The exemplary non-AP station 125a shown in FIG includes processing circuitry 126a and a communication interface 127a, specifically a wireless communication interface 127a according to the IEEE 802.11 standard framework. The processing circuitry 126a can be implemented in hardware and / or software and can include digital circuitry, or both analog circuitry and digital circuitry. The digital circuitry can include components such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), or a general-purpose processor. The exemplary non-AP station 125a can also include a memory 128a for storing executable program code that, when executed by the processing circuitry 126a, causes the exemplary non-AP station 125a to perform the functions and methods described herein.

[0080] Several coordinated transmission schemes may involve communication between the AP 110, 120 and its OBSS stations 115a to 115c, 125a to 125c, i.e., communication between the AP 110, 120 and non-AP stations 115a to 115c, 125a to 125c associated with other APs. For example, as described above, for CoBF transmission, the AP 110, 120 may perform a sounding process and may request sounding feedback reports from non-AP stations associated with the AP and non-AP stations associated with other APs (also referred to as OBSS, i.e., overlapping non-AP stations). This may be accomplished by Figure 2 The multi-AP (Multi-AP, M-AP) frame 200 shown is implemented. Figure 2 As shown, such an M-AP frame 200 may include an M-AP set ID (identifier) ​​211 and a coordination protocol ID (identifier) ​​213 within a common portion 210 of the M-AP frame 200 for exchange between APs operating under the same coordination protocol within the same M-AP set. These parameters may enable a receiver to identify and respond to the M-AP frame 200. In addition to the common portion 210, the M-AP frame 200 may include STA information blocks 220a to 220n for each non-AP station in the M-AP set and AP information blocks 230a to 230n for each AP in the M-AP set. Figure 2 As shown, the common portion 210 of the M-AP frame 200 may further include an indication block 215 regarding an expected response to the M-AP frame 200 and blocks 217 and 219 indicating the number of STA information blocks 220 a to 220 n and AP information blocks 230 a to 230 n of the M-AP frame 200 .

[0081] Figure 3a A conventional M-AP coordinated transmission scheme 300 is shown. Figure 3a The illustrated M-AP coordinated transmission scheme 300 includes the following main phases. In phase 301, a set of APs participating in coordinated transmission (referred to as a multi-AP or M-AP set) is determined. In the coordinated transmission protocol phase 303, all member APs in the M-AP set, or a subset thereof, agree to share each acquired TXOP, or portion thereof, with at least one other member AP operating under the same protocol. The coordinated protocol may last for several TXOPs, wherein specific participants (shared APs) may be exchanged between TXOPs. As described above, each TXOP may be acquired by a different AP (referred to as a sharing AP), while all other APs (i.e., shared APs) may transmit during that TXOP (or portion thereof) only when triggered by the sharing AP. The sharing APs decide how to share resources in the current TXOP and with which APs to share (this may be announced by the sharing AP and approved by the shared AP).

[0082] like Figure 3b As generally shown in and described in more detail below, one embodiment disclosed herein provides a management process 305 (in Figure 3b The management process 305 supports the shared AP 110 and one or more shared APs 120 to complete the indication of the associated non-AP sites 115a to 115c, 125a to 125c of each AP 110, 120 operating under the same coordination protocol within the allocated time period. In addition, the embodiments disclosed herein support providing information to each AP 110, 120 in the M-AP set regarding whether each AP 110, 120 in the M-AP set has completed the indication or has not yet completed the indication. Figure 3b As shown, process 305 may be performed once before one or more shared TXOP coordinated transmissions, such as before shared TXOP coordinated transmissions 313a and 313b and before shared TXOP coordinated transmission 333a.

[0083] The embodiments disclosed herein are based on the following idea: for example, by means of a data structure 400 (specifically Figure 4 The lookup table 400 shown is used to exchange information between a sharing AP 110 and one or more shared APs 120 in an M-AP set. The data structure 400 is managed by all APs 110, 120 in the M-AP set that operate under the same coordination protocol, so that each AP 110, 120 that is a member of the coordination protocol has a local copy of the data structure.

[0084] Therefore, if Figure 5As shown, the communication interface 113 of the shared AP 110 is used to receive the completion status information frame 509 from, for example, the shared AP1 120. Figure 5 As shown, the completion status information 509 may be part of a completion status information frame 509 sent by the shared AP1 120 to the sharing AP 110. As shown in FIG3 , before the completion status information frame 509, the sharing AP 110 and the shared AP 120 may have established a coordination protocol in stage 303 (as described above). The sharing AP 110 may send a coordination announcement frame 501 and receive a coordination approval 503 from the shared AP 120 in response. The sharing AP 110 may then send an M-AP trigger frame 505 (which may have the same Figure 2 , such as one or more identifiers), is used to trigger the shared AP1 120 to send information related to operation under the coordination protocol to one or more of its non-AP stations that belong to its BSS.

[0085] This runs on Figure 8 The shared AP 110 sends an M-AP trigger frame 505 (which may have the same Figure 2 , e.g., one or more identifiers) to trigger the shared AP1 120 to send information related to operation under the coordination protocol to one or more of its non-AP stations 125a to 125c. In response to receiving the M-AP trigger frame 505, the shared AP1 120 (as part of the intra-BSS indication process 507) sends an intra-BSS indication frame 801a to its associated non-AP stations 125a, 125b and, in response, receives an acknowledgment frame 803a. At a later stage, the shared AP1 120 (still as part of the intra-BSS indication process 507) may send another intra-BSS indication frame 801b to its associated non-AP station 125c and, in response, receive an acknowledgment frame 803b. Once the shared AP1 120 has received the confirmation frames 803a, 803b from all of its associated non-AP stations 125a, 125c, it sends a completion status information frame 509 to the sharing AP 110, notifying the sharing AP 110 that the information related to the operation under the coordination protocol has been successfully sent to the non-AP stations 125a to 125c associated with the shared AP1 120. In other words, the completion status information frame 509 indicates the completion status of sending the information 801a, 801b related to the operation under the coordination protocol to the non-AP stations 125a to 125c associated with the shared AP1 120.

[0086] like Figure 5As shown, the shared AP 110 may perform the same intra-BSS indication process 507 (in the example of FIG. 5 ) as the shared AP1 120 and its associated non-AP stations 115a to 115c. Figure 8 Based on these intra-BSS indication processes 507 performed by the sharing AP 110 and the shared AP 120, the sharing AP 110 may generate and maintain data structures, such as Figure 4 As shown in the lookup table 400, the data structure indicates the completion status of each shared AP in the plurality of shared APs 120. Figure 4 As shown, the lookup table 400 may include a column 401 for identifying an AP; a column 403 for indicating the completion status of sending information related to operation under the coordination protocol to a non-AP station associated with the corresponding AP. Figure 5 The M-AP BSS intra-indication status frame 511 is shown, and the sharing AP 110 may be used to provide the current version of the data structure 400 to the multiple shared APs 120 .

[0087] The following will refer to Figure 6 To further describe, each AP member of the coordination protocol, i.e., the sharing AP 110 and the shared AP 120, may maintain a local copy of the completion status lookup table 400. In one embodiment, only shared APs 120 with a "completed" status may participate in one or more coordinated transmissions. If the sharing AP 110 wishes to include any shared APs 120 with an "uncompleted" status in the coordinated transmission, it may initiate the above-described coordination status lookup table 400 for these shared APs before initiating the coordinated transmission. Figure 5 The related indication process within the BSS is described in the context of Figure 6 As shown, at the end of the first TXOP 610, the sharing AP 110 may send an update of the completion status lookup table 400 to all shared APs 120 via frame 511 to ensure that all local copies of the table 400 are up to date. In one embodiment, the sharing AP 110 may trigger all shared APs 120 with an "incomplete" status to complete the state lookup table 400. Figure 8 The intra-BSS indication process 507 is shown in detail in FIG.

[0088] As mentioned above, Figure 8The intra-BSS indication process 507 shown in detail in FIG. 5 may be triggered and managed by the shared AP 110 such that each shared AP 120 (as a member of the current coordination protocol) sends information 801a, 801b once to its associated non-AP stations 125a to 125c according to the established coordination protocol. In one embodiment, each shared AP 120 may need to complete its indication before it can participate in coordinated transmissions with its BSS stations. In one embodiment, all APs 110, 120 operating under the same coordination protocol may be within multiple single TXOPs, e.g., within Figure 6 The first TXOP 610 and the second TXOP 630 are shown to complete their intra-BSS related indication procedures 507. The embodiments disclosed herein allow ensuring that at the end of a TXOP, all APs 110, 120 under the same coordination protocol are aware of the completion status of the intra-BSS related indication procedures 507 of all other APs 110, 120 operating under the same coordination protocol.

[0089] The following will Figure 6 A more detailed description is given in Figure 6 In the scenario shown, four APs, namely AP1, AP2, AP3 and AP4, are members of the coordination protocol. Figure 6Schematic diagram illustrates exemplary communications between four APs during two TXOPs 610 and 630 immediately after the coordination protocol is established. The first TXOP 610 is acquired by AP1 (i.e., AP1 is the sharing AP 110 of the first TXOP, while AP2, AP3, and AP4 are the shared APs 120), and the second TXOP 630 is acquired by AP2 (i.e., AP2 is the sharing AP 110 of the second TXOP, while AP1, AP3, and AP4 are the shared APs 120). At the beginning of the first TXOP 610, all APs are marked as "incomplete" in the completion status table 400. AP1, the sharing AP of the first TXOP 610, wishes to share TXOP resources with AP2 and AP3 for M-AP coordinated transmission. Therefore, according to one embodiment, AP1, the current sharing AP 110, triggers AP2 and AP3 to complete the intra-BSS related indication 507 as described above based on the status information in table 400. When both AP2 and AP3 have sent completion indication frames 509 and AP1 has performed intra-BSS indication 507 for its own BSS sites 115a, 115b, a status update frame 511 is sent to all shared APs operating under the same coordination protocol (to include those APs that have completed the intra-BSS indication process with their BSSs). In response to receiving the status update frame 511, all APs operating under the same coordination protocol can update their local copies of the completion status table 400, where AP1, AP2, and AP3 are now marked as being in the "Completed" state. Thus, as part of the first TXOP 610, AP1 can perform coordinated transmissions 313a with either AP2 or AP3. For the second TXOP 630, where AP2 is the sharing AP 110, AP2 wishes to share its acquired TXOP resources with AP4 (one of the shared APs 120). However, since AP4 is still indicated as "not completed" in the completion status table 400, sharing AP2 110 should trigger shared AP4 120 to perform intra-BSS indication 507. Once shared AP4 120 has sent a completion indication frame 509 to sharing AP2 110, sharing AP2 110 can send a status update frame 511 to all APs operating under the same coordination protocol (including AP1 and AP3, which have completed their intra-BSS indications). In response to the status update frame 511, all APs operating under the same coordination protocol can update their local copies of the completion status table 400, where all APs are marked as "completed." From this point on (until the coordination protocol expires), any subset of AP1, AP2, AP3, and AP4 can initiate coordinated transmissions when it becomes a shared AP (when it acquires a TXOP).

[0090] As mentioned above, Figure 7As shown, the shared AP 110 may send an M-AP trigger frame 505 to each of the one or more shared APs 120 to trigger the corresponding shared AP 110 to start the BSS indication process of the non-AP station associated therewith, as shown in FIG. Figure 8 In one embodiment, the M-AP trigger frame 505 may include the address of the triggered shared AP 120, an M-AP set identifier, a coordination protocol identifier, and / or a list of APs in the M-AP set.

[0091] like Figure 8 As shown and described above, AP 120 may send intra-BSS indication frames 801a, 801b to its associated non-AP stations 125a to 125c. The frames 801a, 801b may be part of a PPDU (described below) and may include an M-AP set identifier, a coordination protocol identifier, a list of involved APs, and / or coordination scheme related information. Figure 8 The illustrated intra-BSS indication frames 801a, 801b may be dedicated unicast frames. In another embodiment, the intra-BSS indication frames 801a, 801b may be "multicast"-like frames, such as broadcast management frames for a group of non-AP stations 125a to 125c specified in the frame body.

[0092] As has been described and shown above, for example, Figure 6 In the example, the sharing AP 110 may send an M-AP indication status frame 511 to the shared AP 120 to update all shared APs 120 operating under the same coordination protocol on the completion status of the corresponding AP's intra-BSS indication process 507. In one embodiment, the M-AP indication status frame 511 may include a list of APs operating under the same coordination protocol, information about the completion status of each AP used to update the local copy of the table 400, an M-AP set identifier, and / or a coordination protocol identifier. In another embodiment, the M-AP indication status frame 511 may include the entire completion status table 400 generated and maintained by the sharing AP 110.

[0093] Figure 9The flowchart of a method 900 for operating a shared AP 110 according to an embodiment is provided. As described above, the shared AP 110 is configured to share at least a portion of a TXOP with one or more shared APs 120. The one or more shared APs 120 operate under a coordination protocol within an M-AP set and participate in coordinated transmissions with one or more non-AP stations 115a through 115c associated with the shared AP 110 and other non-AP stations 125a through 125c associated with each of the one or more shared APs 120. The method 900 includes step 901 of receiving completion status information 509 from the one or more shared APs 120, wherein the completion status information 509 indicates a completion status of sending information 801a and 801b related to operation under the coordination protocol to one or more of the other non-AP stations 125a through 125c associated with the respective shared APs 120. Furthermore, the method 900 includes step 903 of generating and maintaining a data structure 400 based on the completion status information 509 of each of the one or more shared APs 120 operating under the coordination protocol, wherein the data structure 400 indicates a completion status for each of the plurality of shared APs 120. As described above, in one embodiment, the data structure 400 may be a lookup table 400.

[0094] As can be understood from the detailed description of the shared AP 110 above, method 900 may further include generating one or more M-AP trigger frames, specifically one or more M-AP trigger frames for indication within the BSS, and sending one or more M-AP trigger frames to one or more shared APs among the multiple shared APs 120 to trigger (i.e., request) the corresponding shared AP 120 to provide information related to operation under the coordination protocol to one or more other non-AP sites 125a to 125c associated with the corresponding shared AP 120.

[0095] Because the method 900 may be implemented by the shared AP 110, other features of the method 900 derive directly from the functionality of the shared AP 110 and its various embodiments described above and below.

[0096] Figure 10FIG1 is a flow chart illustrating a method 1000 for operating one of a plurality of shared APs 120 according to one embodiment. As described above, the shared AP 120 is configured to participate in coordinated transmissions with one or more non-AP stations 125a through 125c associated with the shared AP 120 and one or more other non-AP stations 115a through 115c associated with the sharing AP 110 using at least a portion of a TXOP, wherein the TXOP is obtained and shared by the sharing AP 110 operating under a coordination protocol within an M-AP set. The method 1000 includes step 1001 of transmitting information 801a and 801b related to operation under the coordination protocol to one or more non-AP stations 125a through 125c associated with the shared AP 120. Furthermore, the method 1000 includes step 1003 of sending completion status information to the shared AP, wherein the completion status information 509 indicates the completion status of sending information 801a, 801b related to operation under the coordination protocol to one or more non-AP stations 125a to 125c associated with the shared AP 120.

[0097] As can be understood from the detailed description of the shared AP 120 above, the method 1000 may further include: receiving an M-AP trigger frame from the shared AP 110, and after receiving the M-AP trigger frame from the shared AP 110 (specifically, in response to receiving the M-AP trigger frame from the shared AP 110), sending information related to operation under the coordination protocol to one or more non-AP sites 125a to 125c associated with the shared AP 120.

[0098] Since the method 1000 may be implemented by the shared AP 120, other features of the method 1000 derive directly from the functionality of the shared AP 120 and its various embodiments described above and below.

[0099] Figure 1111 is a flow chart illustrating a method 1100 for operating an exemplary non-AP station 125a associated with a shared AP 120, according to one embodiment. As described above, the shared AP 120 is configured to participate in coordinated transmissions to the non-AP station 125a associated with the shared AP 120 and a plurality of other non-AP stations 115a through 115c, 125b, and 125c associated with the shared AP 120 or the sharing AP 110, utilizing at least a portion of a TXOP obtained and shared by the sharing AP 110 operating under a coordination protocol within an M-AP set. The method 1100 includes step 1101 of receiving information 801a related to operation under the coordination protocol from the shared AP 120. Furthermore, the method 1100 includes step 1103 of transmitting an acknowledgment frame 803a to the shared AP 120 in response to successfully receiving the information 801a related to operation under the coordination protocol from the shared AP 120.

[0100] Because the method 1100 may be implemented by the non-AP station 125a associated with the shared AP 120, other features of the method 1100 derive directly from the functionality of the non-AP station 125a and its various embodiments described above and below.

[0101] Those skilled in the art will understand that the “blocks” (“units”) in the various figures (methods and devices) represent or describe the functions of the embodiments of the present disclosure (and not necessarily independent “units” in hardware or software), thereby equally describing the functions or features of the device embodiments and the method embodiments (unit = step).

[0102] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the described embodiments of the device are merely exemplary. For example, unit division is merely a logical functional division, and other division methods can be used in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented through some interfaces. The indirect coupling or communication connection between devices or units can be implemented through electronic, mechanical or other forms.

[0103] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, and may be located in one location or distributed across multiple network units. Some or all of the units may be selected as needed to achieve the purpose of the embodiments.

[0104] In addition, the functional units in the embodiments disclosed herein may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

Claims

1. A shared access point (AP) (110) for sharing at least a portion of a transmission opportunity (TXOP) with a plurality of shared APs (120), wherein the plurality of shared APs (120) operate under a coordination protocol within a multi-access point (M-AP) set and participate in coordinated transmission of one or more non-AP stations (115a to 115c) associated with the shared AP and a plurality of other non-AP stations (125a to 125c) associated with the plurality of shared APs (120), wherein: The shared AP (110) comprises: a communication interface (113) for receiving a completion status information (509) frame from one or more of the plurality of shared APs (120), wherein the completion status information (509) indicates a completion status of sending information (801a, 801b) related to operation under the coordination protocol to one or more of the plurality of other non-AP stations (125a to 125c) associated with the corresponding shared AP (120); Processing circuitry (111) for generating and maintaining a data structure (400) based on the completion status information (509) frame of each shared AP in the one or more shared APs in the plurality of shared APs (120), wherein the data structure (400) includes the completion status of each shared AP in the plurality of shared APs (120).

2. The shared AP (110) according to claim 1, wherein: The communication interface (113) is used to send the data structure (400) to each shared AP in the plurality of shared APs (120).

3. The shared AP (110) according to claim 2, wherein: The communication interface (113) is used to send an indication status frame (511) to the multiple shared APs (120), and the indication frame (511) includes the data structure (400).

4. The shared AP (110) according to claim 3, wherein: The indication status frame (511) further includes a MAC address and / or an identifier of the sharing AP (110) and / or each shared AP in the plurality of shared APs (120).

5. The shared AP (110) according to claim 3 or 4, wherein: The indication status frame (511) further includes an M-AP set identifier indicating the M-AP set.

6. The shared AP (110) according to any one of claims 3 to 5, wherein: The indication frame (511) further includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

7. The shared AP (110) according to any one of the preceding claims, wherein: The data structure (400) includes an indication (403) of the completion status of each of the plurality of shared APs (120) operating under a same coordination protocol and the shared AP (110).

8. The shared AP (110) according to any one of the preceding claims, wherein: The data structure (400) includes a lookup table (400).

9. The shared AP (110) according to any one of the preceding claims, wherein: The communication interface (113) is further configured to send one or more M-AP trigger frames (505) to one or more shared APs among the plurality of shared APs (120) to trigger the corresponding shared AP (120) to provide the information (509) related to operation under the coordination protocol to the one or more other non-AP stations (125a to 125c) associated with the corresponding shared AP (120).

10. The shared AP (110) according to claim 9, wherein: The communication interface (113) is configured to send the one or more M-AP trigger frames (505) to the one or more shared APs among the plurality of shared APs (120) to trigger the corresponding shared AP (120) to provide the information (509) related to operation under the coordination protocol to the one or more other non-AP stations (125a to 125c) associated with the corresponding shared AP (120), wherein, for the one or more shared APs, the data structure (400) indicates that the corresponding shared AP (120) has not yet completed the related process within the BSS.

11. The shared AP (110) according to claim 9 or 10, wherein: The one or more M-AP trigger frames (505) include a MAC address and / or an identifier of the sharing AP (110) and / or each shared AP in the plurality of shared APs (120).

12. The shared AP (110) according to any one of claims 9 to 11, wherein: The one or more M-AP trigger frames (505) include an M-AP set identifier indicating the M-AP set.

13. The shared AP (110) according to any one of claims 9 to 12, wherein: The one or more M-AP trigger frames (505) include a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of a plurality of coordination protocols within the M-AP set, and the sharing AP (110) and the plurality of shared APs (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

14. The shared AP (110) according to any one of the preceding claims, wherein: The processing circuit (111) is configured to limit the coordinated transmission to those shared APs of the plurality of shared APs (120) for which the shared AP (110) has indicated its status information as "completed".

15. The shared AP (110) according to any one of the preceding claims, wherein: The information (801a, 801b) related to operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

16. The shared AP (110) according to any one of the preceding claims, wherein: The information (801a, 801b) related to operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

17. The shared AP (110) according to any one of the preceding claims, wherein: The information (801a, 801b) related to operation under the coordination protocol includes a MAC address and / or identifier of each shared AP in the plurality of shared APs (120).

18. The shared AP (110) according to any one of the preceding claims, wherein: The shared AP (110) further comprises a memory (114), wherein the memory (114) is used to store the data structure (400).

19. A method (900) of operating a shared access point (AP) (110) for sharing at least a portion of a transmission opportunity (TXOP) with a plurality of shared APs (120), the plurality of shared APs (120) operating within a multi-access point (M-AP) set according to a coordination protocol for participating in coordinated transmissions of one or more non-AP stations (115a to 115c) associated with the shared AP (110) and a plurality of other non-AP stations (125a to 125c) associated with the plurality of shared APs (120), wherein: The method (900) comprises: receiving (901) a completion status information (509) frame from one or more of the plurality of shared APs (120), wherein the completion status information (509) frame indicates a completion status of transmitting information (801a, 801b) related to operation according to the coordination protocol to one or more of the plurality of other non-AP stations (125a to 125c) associated with the corresponding shared AP (120); Based on the completion status information (509) frame of each shared AP in the one or more shared APs in the plurality of shared APs (120) operating under the coordination protocol, a data structure (400) is generated and maintained (903), wherein the data structure (400) indicates the completion status for each shared AP in the plurality of shared APs (120).

20. The method (900) of claim 19, wherein: The method (900) further includes sending one or more M-AP trigger frames (505) to one or more shared APs of the plurality of shared APs (120) to trigger the corresponding shared AP (120) to provide the information (509) related to operation under the coordination protocol to the one or more other non-AP stations (125a to 125c) associated with the corresponding shared AP (120).

21. A shared access point (AP) (120) for participating in coordinated transmissions with one or more non-AP stations (125a to 125c) associated with the shared AP (120) and one or more other non-AP stations (115a to 115c) associated with a sharing AP (110) using at least a portion of a transmission opportunity (TXOP), wherein: The TXOP is acquired and shared by the shared AP (110) operating under a coordination protocol within a multi-access point M-AP set, wherein the shared AP (120) includes: a communication interface (123) for sending information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120), The communication interface (123) is further configured to send a completion status information (509) frame to the shared AP (110), wherein the completion status information (509) frame indicates a completion status of sending the information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP sites (125a to 125c) associated with the shared AP (120).

22. The shared AP (120) according to claim 21, wherein: The communication interface (123) is further configured to receive a data structure (400) from the shared AP (110), wherein the data structure (400) indicates, for the shared AP (110) and for each of a plurality of other shared APs (120) operating under the coordination protocol within the M-AP set, the completion status of sending the information (801a, 801b) related to operation under the coordination protocol to one or more non-AP stations (115a to 115c) associated with the shared AP (110) or the respective other shared APs (120).

23. The shared AP (120) according to claim 22, wherein: The communication interface (123) is used to receive an indication frame (511) from the shared AP (110), and the indication status frame (511) includes the data structure (400).

24. The shared AP (120) according to claim 23, wherein: The indication status frame (511) further includes the address and / or identifier of the sharing AP (110) and / or the shared AP (120).

25. The shared AP (120) according to claim 23 or 24, wherein: The indication status frame (511) further includes an M-AP set identifier indicating the M-AP set.

26. The shared AP (120) according to any one of claims 23 to 25, wherein: The indication status frame (511) further includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

27. The shared AP (120) according to any one of claims 22 to 26, wherein: The data structure (400) includes an indication (403) of the completion status of each shared AP in the plurality of shared APs (120) operating under the same coordination protocol.

28. The shared AP (120) according to any one of claims 22 to 27, wherein: The data structure (400) includes a lookup table (400).

29. The shared AP (120) according to any one of claims 21 to 28, wherein: The communication interface (123) is configured to send the information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120) after receiving an M-AP trigger frame (505) from the shared AP (110).

30. The shared AP (120) of claim 29, wherein: The M-AP trigger frame (505) includes a MAC address and / or an identifier of the sharing AP (110) and / or each shared AP in the plurality of shared APs (120).

31. The shared AP (120) according to claim 29 or 30, wherein: The M-AP trigger frame (505) includes an M-AP set identifier indicating the M-AP set.

32. The shared AP (120) according to any one of claims 29 to 31, wherein: The M-AP trigger frame (505) includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of a plurality of coordination protocols within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

33. The shared AP (120) according to any one of claims 21 to 32, wherein: The information (801a, 801b) related to operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

34. The shared AP (120) according to any one of claims 21 to 33, wherein: The information (801a, 801b) related to operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one coordination protocol among multiple coordination protocols within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

35. The shared AP (120) according to any one of claims 21 to 34, wherein: The information (801a, 801b) related to operation under the coordination protocol includes addresses and / or identifiers of the shared AP (120) and one or more other shared APs (120) in the M-AP set operating under the same coordination protocol.

36. The shared AP (120) according to any one of claims 21 to 35, wherein: The shared AP (120) further comprises a memory (124), wherein the memory (124) is used to store the data structure (400).

37. The shared AP (120) according to any one of claims 21 to 36, wherein: The communication interface (123) is further configured to receive an acknowledgment frame (803a, 803b) from each of the one or more non-AP stations (125a to 125c) associated with the shared AP (120) in response to sending the information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120).

38. A method (1000) of operating a shared access point (AP) (120) for participating in coordinated transmissions with one or more non-AP stations (125a to 125c) associated with the shared AP (120) and one or more other non-AP stations (115a to 115c) associated with a sharing AP (110) using at least a portion of a transmission opportunity (TXOP), wherein: The TXOP is acquired and shared by the shared AP (110) operating under a coordination protocol within a multi-access point (M-AP) set, wherein the method (1000) comprises: Sending (1001) information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120); A completion status information (509) frame is sent (1003) to the shared AP (110), wherein the completion status information (509) indicates a completion status of sending the information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120).

39. The method (1000) of claim 38, wherein: The method (1000) further includes receiving an M-AP trigger frame (505) from the shared AP (110), and after receiving the M-AP trigger frame (505) from the shared AP (110), sending the information (801a, 801b) related to operation under the coordination protocol to the one or more non-AP stations (125a to 125c) associated with the shared AP (120).

40. A non-access point AP station (125a) associated with a shared AP (120), wherein: The shared AP (120) is configured to utilize at least a portion of a transmission opportunity TXOP to participate in coordinated transmission of the non-AP station (125a to 125c) associated with the shared AP (120) and a plurality of other non-AP stations (115a to 115c, 125b, 125c) associated with the shared AP (120) or a sharing AP (110), wherein the TXOP is obtained and shared by the shared AP (110) operating under a coordination protocol within a multi-access point M-AP set, wherein the non-AP station (125a) includes: a communication interface (127a) for receiving information (801a) related to operation under the coordination protocol from the shared AP (120), The communication interface (127a) is further configured to send a confirmation frame (803a) to the shared AP (120) in response to receiving the information (801a) related to the operation under the coordination protocol from the shared AP (120).

41. The non-AP station (125a) of claim 40, wherein: The information (801a) related to operation under the coordination protocol includes an M-AP set identifier indicating the M-AP set.

42. The non-AP station (125a) of claim 40 or 41, wherein: The information (801a) related to operation under the coordination protocol includes a coordination protocol identifier within the M-AP set, wherein the coordination protocol identifier identifies one of multiple coordination protocols within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the coordination protocol identified by the coordination protocol identifier within the M-AP set.

43. The non-AP station (125a) according to any one of claims 40 to 42, wherein: The information (801a) related to operation under the coordination protocol includes the MAC address and / or identifier of the shared AP (120).

44. A method (1100) of operating a non-access point AP station (125a) associated with a shared AP (120), wherein: The shared AP (120) is configured to participate in coordinated transmission of the non-AP station (125a) associated with the shared AP (120) and a plurality of other non-AP stations (115a to 115c, 125b, 125c) associated with the shared AP (120) or a sharing AP (110) by utilizing at least a portion of a transmission opportunity TXOP, wherein the TXOP is obtained and shared by the shared AP (110) operating under a coordination protocol within a multi-access point (M-AP) set, wherein the method (1100) comprises: receiving (1101) information (801a) related to operation under the coordination protocol from the shared AP (120); In response to receiving the information (801a) related to operation under the coordination protocol from the shared AP (120), an acknowledgement frame (803a) is sent (1103) to the shared AP (120).

45. A computer program product comprising a computer-readable storage medium for storing program code, which, when executed by a computer or a processor, causes the computer or the processor to perform the method (900) according to claim 19, the method (1000) according to claim 38, or the method (1100) according to claim 44.

Images