DEVICE AND METHOD FOR COOPERATIVE TRANSMISSION IN WIRELESS NETWORKS - Patent application

Abstract

The present disclosure relates to a sharing AP (110) configured to share TXOPs with multiple shared APs (120) operating under a cooperative agreement within an M-AP set to participate in cooperative transmissions to one or more non-AP stations (115a-c) associated with the sharing AP and to multiple additional non-AP stations (125a-c) associated with the shared AP (120). The sharing AP (110) is configured to receive completion status information from one or more of the multiple shared APs (120), the completion status information indicating a completion status of transmitting information related to operation under the cooperative agreement to one or more of the multiple additional non-AP stations (125a-c) associated with the respective shared AP (120). The sharing AP (110) is also configured to generate and maintain a data structure indicating a completion status of each of the multiple shared APs (120) based on the completion status information of each of the multiple shared APs (120).

Description

[Technical Field]

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

[0002] IEEE 802.11-based WLANs (also known as Wi-Fi networks) are proliferating at an unprecedented rate. 802.11be addressed multi-AP (M-AP) cooperative transmission, e.g., cooperative beamforming transmission. In cooperative transmission, a group of access points (APs) may initiate simultaneous frame exchanges within a limited period, with each participating AP using the entire BW. One or more APs in the group of APs may share one or more transmission opportunities (TXOPs) with the sharing AP and one or more shared APs. The group of APs that decide to cooperate to perform cooperative transmission is called an M-AP set. Summary of the Invention [Means for solving the problem]

[0003] It is an object to provide an improved device and method for M-AP cooperative transmission in wireless communication networks, particularly in IEEE 802.11 based WLANs.

[0004] These and other objects are achieved by the subject matter of the independent claims. Further embodiments become apparent from the dependent claims, the description and the figures.

[0005] According to a first aspect, a sharing access point (AP) is provided, the sharing AP configured to share at least a portion of transmission opportunities (TXOPs) with multiple shared APs operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations associated with the sharing AP and multiple additional non-AP stations associated with the multiple shared APs. The sharing AP comprises a communication interface configured to receive completion status information, in particular, completion station information frames, from one or more of the multiple shared APs, where the completion status information frames received from each of the one or more of the multiple shared APs indicate a completion status of successfully transmitting information related to operation under the cooperative agreement to one or more of the multiple additional non-AP stations associated with the respective shared AP. Furthermore, the sharing AP comprises a processing circuit configured to generate and maintain a data structure based on the completion status information frames of each of one or more of the multiple shared APs, the data structure indicating a completion status of each of the multiple shared APs. In an embodiment, the data structure may also indicate a completion status of the sharing APs that successfully transmitted information related to operation under the cooperative agreement to one or more non-AP stations associated with the sharing AP.

[0006] In a further possible implementation, the communication interface is configured to transmit the data structure to each of the multiple shared APs, particularly before the end of a current transmission opportunity.

[0007] In a further possible implementation, the communication interface is configured to transmit an indication status frame to the multiple shared APs, the indication frame including a data structure.

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

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

[0010] In a further possible implementation, the indication status frame further comprises a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP and the multiple shared APs operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

[0011] In a further possible implementation, the data structure includes an indication of the completion status of each of multiple shared APs and sharing APs operating under the same collaboration agreement.

[0012] In a further possible implementation, the data structure comprises or is implemented as a lookup table.

[0013] In a further possible implementation, the communication interface is further configured to transmit one or more M-AP trigger frames, in particular one or more M-AP trigger frames for intra-BSS instructions, to one or more of the multiple shared APs for triggering, i.e., to request each shared AP to provide information related to operation under the cooperation agreement to one or more further non-AP stations associated with the respective shared AP.

[0014] In a further possible implementation, the communication interface is configured to transmit one or more M-AP trigger frames to one or more of the plurality of shared APs to trigger the respective shared AP to provide information related to operation under the cooperation agreement to one or more further non-AP stations of the plurality of further non-AP stations associated with the respective shared AP, and the data structure indicates that the respective shared AP has not completed the intra-BSS association procedure, e.g., that the respective shared AP has not yet completed transmission of information related to operation under the cooperation agreement to one or more of the plurality of further non-AP stations associated with the respective shared AP.

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

[0016] In a further possible implementation, the one or more M-AP trigger frames include an M-AP set identifier that indicates an M-AP set.

[0017] In a further possible implementation, the one or more M-AP trigger frames comprise a cooperation agreement identifier within the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements within the M-AP set, and the sharing AP and multiple shared APs operate under the cooperation agreement identified by the cooperation agreement identifier within the M-AP set.

[0018] In a further possible implementation, the processing circuitry is configured to limit cooperative transmission to shared APs among the multiple shared APs whose sharing APs have indicated their status information as “completed” and to shared APs among the multiple shared APs whose data structure indicates their completion status as “completed.”

[0019] In a further possible implementation, the information related to operation under the collaboration agreement includes an M-AP set identifier indicating an M-AP set.

[0020] In a further possible implementation, the information related to operation under the cooperation agreement includes a cooperation agreement identifier in the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements in the M-AP set, and the sharing AP and multiple shared APs operate under the cooperation agreement identified by the cooperation agreement identifier in the M-AP set.

[0021] In a further possible implementation, the information related to operation under the collaboration agreement includes an address, particularly a MAC address, and / or an identifier, of each of the multiple shared APs.

[0022] In a further possible implementation, the sharing AP further comprises a memory, the memory configured to store the data structure.

[0023] According to a second aspect, there is provided a method of operating a sharing access point (AP), the sharing AP configured to share at least a portion of transmission opportunities (TXOPs) that have multiple shared APs operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations associated with the sharing AP and multiple further non-AP stations associated with the multiple shared APs. The method comprises: receiving completion status information, in particular completion status information frames, from one or more of the plurality of shared APs, wherein the completion status information frames received from each of the one or more of the plurality of shared APs indicate a completion status of successful transmission of information related to operation under the cooperation agreement to one or more of a plurality of further non-AP stations associated with the respective shared AP; generating and maintaining a data structure based on completion status information frames of each of one or more of the plurality of shared APs operating under the collaboration agreement, the data structure indicating a completion status for each of the plurality of shared APs; In an embodiment, the data structure may also indicate a completion status of a sharing AP that has successfully transmitted information related to operation under the cooperation agreement to one or more non-AP stations associated with the sharing AP.

[0024] The method according to the second aspect of the present disclosure may be performed by a sharing AP according to the first aspect of the present disclosure. Accordingly, further features of the method according to the second aspect of the present disclosure result directly from the functionality of the sharing AP according to the first aspect of the present disclosure and from the different embodiments described above and below.

[0025] According to a third aspect, a shared access point AP is provided, configured to utilize at least a portion of shared transmission opportunities (TXOPs) obtained by the sharing APs operating under a cooperation agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations associated with the shared AP and one or more further non-AP stations associated with the sharing AP. The shared AP comprises a communication interface configured to transmit information related to operation under the cooperation agreement to one or more non-AP stations associated with the shared AP, i.e., BSS stations of the shared AP. The communication interface is further configured to transmit completion status information, in particular a completion status information frame, to the sharing AP, where the completion status information frame indicates a completion status of successful transmission of the information related to operation under the cooperation agreement to one or more non-AP stations associated with the respective shared AP.

[0026] In a further possible implementation, the communication interface is further configured to receive a data structure from the sharing AP, the data structure indicating, for the sharing AP and for each of a plurality of further shared APs operating under the cooperation agreement in the M-AP set, a completion status of transmitting information related to operation under the cooperation agreement to the sharing AP and one or more non-AP stations associated with each further shared AP.

[0027] In a further possible implementation, the communication interface is configured to receive an indication status frame from the sharing AP, the indication status frame including a data structure.

[0028] In a further possible implementation, the indication status frame further includes the address, in particular the MAC address and / or identifier, of the sharing AP and / or the shared AP.

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

[0030] In a further possible implementation, the indication status frame further comprises a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP and the multiple shared APs operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

[0031] In a further possible implementation, the data structure includes an indication of the completion status of the sharing AP and each of multiple shared APs operating under the same collaboration agreement.

[0032] In a further possible implementation, the data structure comprises or is implemented as a lookup table.

[0033] In a further possible implementation, the communication interface is configured to, following receipt of an M-AP trigger frame from a sharing AP, in particular an M-AP trigger frame for intra-BSS instructions, provide information related to operation under the cooperation agreement to one or more non-AP stations associated with that shared AP, i.e., BSS stations of the shared AP.

[0034] In a further possible implementation, the M-AP trigger frame includes an address, in particular a MAC address and / or identifier, of the sharing AP and / or each of the multiple shared APs.

[0035] In a further possible implementation, the M-AP trigger frame includes an M-AP set identifier that indicates the M-AP set.

[0036] In a further possible implementation, the M-AP trigger frame comprises a cooperation agreement identifier within the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements in the M-AP set, and the sharing AP and multiple shared APs operate under the cooperation agreement identified by the cooperation agreement identifier within the M-AP set.

[0037] In a further possible implementation, the information related to operation under the collaboration agreement includes an M-AP set identifier indicating an M-AP set.

[0038] In a further possible implementation, the information related to operation under the cooperation agreement includes a cooperation agreement identifier in the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements in the M-AP set, and the sharing AP and multiple shared APs operate under the cooperation agreement identified by the cooperation agreement identifier in the M-AP set.

[0039] In a further possible implementation, the information related to operation under the cooperation agreement includes an address, particularly a MAC address, and / or an identifier, of each of multiple shared APs operating under the same cooperation agreement within the M-AP set.

[0040] In a further possible implementation, the shared AP further comprises a memory, the memory configured to store the data structure.

[0041] In a further possible implementation, the communication interface is further configured to receive an acknowledgement message, in particular an acknowledgement frame, from each of one or more non-AP stations associated with the shared AP in response to transmitting information related to operation under the cooperation agreement to one or more non-AP stations associated with the shared AP, i.e., BSS stations of the shared AP.

[0042] According to a fourth aspect, there is provided a method of operating a shared access point (AP), where the shared AP is configured to utilize at least a portion of shared transmission opportunities (TXOPs) obtained by the sharing APs operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations associated with the shared AP and one or more further non-AP stations associated with the sharing AP, the method comprising: transmitting information related to operation under the cooperation agreement to one or more non-AP stations associated with the shared AP, i.e., BSS stations of the shared AP; transmitting completion status information, in particular a completion status information frame, to the sharing AP, the completion status information frame indicating a completion status of successfully transmitting information related to operation under the cooperation agreement to one or more non-AP stations associated with the respective shared AP; Includes:

[0043] The method according to the fourth aspect may further include receiving an M-AP trigger frame from the sharing AP and, particularly following response to receiving the M-AP trigger frame from the sharing AP, transmitting information related to operation under the cooperation agreement to one or more non-AP stations associated with the shared AP.

[0044] The method according to the fourth aspect of the present disclosure may be performed by a shared AP according to the third aspect of the present disclosure. Thus, further features of the method according to the fourth aspect of the present disclosure result directly from the functionality of the shared AP according to the third aspect of the present disclosure and from the different embodiments described above and below.

[0045] According to a fifth aspect, there is provided a non-AP station associated with a shared access point AP, configured to utilize at least a portion of shared transmission opportunities TXOPs obtained by the sharing APs operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to the non-AP station associated with the shared AP and to the shared AP or to multiple further non-AP stations associated with the sharing AP. The non-AP station comprises a communication interface configured to receive information related to operation under the cooperative agreement from the shared AP. The communication interface is further configured to transmit an acknowledgement, in particular an acknowledgement frame, to the shared AP in response to successfully receiving the information related to operation under the cooperative agreement from the shared AP.

[0046] In a further possible implementation, the information related to operation under the collaboration agreement includes an M-AP set identifier indicating an M-AP set.

[0047] In a further possible implementation, the information related to operation under the cooperation agreement includes a cooperation agreement identifier in the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements in the M-AP set, and the sharing AP and multiple shared APs operate under the cooperation agreement identified by the cooperation agreement identifier in the M-AP set.

[0048] In a further possible implementation, the information related to operation under the collaboration agreement includes an address, particularly a MAC address, and / or an identifier, of each of the multiple shared APs.

[0049] According to a sixth aspect, there is provided a method of operating a non-AP station associated with a shared access point AP, where the shared AP is configured to utilize at least a portion of a shared transmission opportunity TXOP obtained by the shared AP operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to the non-AP station associated with the shared AP and to a plurality of further non-AP stations associated with the shared AP or the sharing AP. The method comprises: receiving information related to operation under the cooperative agreement from a shared AP; transmitting an acknowledgement, in particular an acknowledgement frame, to the shared AP in response to receiving information related to operation under the cooperative agreement from the shared AP; Includes:

[0050] The method according to the sixth aspect of the present disclosure may be performed by a non-AP station according to the fifth aspect of the present disclosure. Therefore, further features of the method according to the sixth aspect of the present disclosure result directly from the functionality of the non-AP station according to the fifth aspect of the present disclosure and the different embodiments described above and below.

[0051] The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will become apparent from the description, drawings, and claims.

[0052] In the following, embodiments of the present disclosure will be described in more detail with reference to the accompanying figures and drawings. [Brief explanation of the drawings]

[0053] [Figure 1] 1 illustrates an exemplary wireless communication network including a sharing AP and multiple shared APs for cooperative transmission, according to one embodiment. [Figure 2]10A and 10B schematically illustrate the structure of an M-AP frame used by a sharing AP according to one embodiment for communicating with a shared AP according to one embodiment for cooperative transmission, where the M-AP frame includes a cooperative agreement identifier and an M-AP set identifier. [Figure 3a] 1 illustrates different processing stages of M-AP cooperation, including cooperative transmissions performed by a conventional sharing AP and a conventional shared AP. [Figure 3b] 1 illustrates different processing stages of M-AP cooperation, including cooperative transmissions performed by a sharing AP and a shared AP according to one embodiment. [Figure 4] 1 is a schematic diagram illustrating data structures maintained and distributed by a sharing AP according to one embodiment. [Figure 5] 1 is a schematic diagram illustrating signaling between a sharing AP according to one embodiment and two shared APs according to one embodiment before cooperative transmission; [Figure 6] 1 is a schematic diagram illustrating signaling between a sharing AP according to one embodiment and three shared APs according to one embodiment for different cooperative transmissions, particularly transmission opportunities with different sharing APs; [Figure 7] 1 is a schematic diagram illustrating signaling between a sharing AP according to one embodiment and two shared APs according to one embodiment before cooperative transmission; [Figure 8] 1 is a schematic diagram illustrating signaling between a sharing AP according to one embodiment, a shared AP according to one embodiment, and multiple non-AP stations associated with the shared AP according to one embodiment. [Figure 9] 1 is a flow diagram illustrating a method of operation of a sharing AP according to one embodiment. [Figure 10] 1 is a flow diagram illustrating a method of operation of a shared AP according to one embodiment. [Figure 11] 1 is a flow diagram illustrating a method of operation of a non-AP station associated with a shared AP according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0054] Hereinafter, the same reference symbols refer to identical or at least functionally equivalent features.

[0055] In the following description, reference is made to the accompanying figures which form a part of this disclosure and which show, by way of illustration, specific aspects of embodiments of the present disclosure or in which embodiments of the present disclosure may be used. It is understood that embodiments of the present disclosure may be used in other ways and may include structural or logical changes not shown in the figures. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

[0056] For example, it should be understood that disclosure related to a described method can also apply to a corresponding device or system configured to perform that method, and vice versa. For example, when one or more particular method steps are described, a corresponding device can include one or more units, e.g., functional units, for performing the described one or more method steps (e.g., one unit that performs one or more steps, or multiple units that each perform one or more of the multiple steps), even if such one or more units are not explicitly described or shown in the drawings. On the other hand, for example, when a particular apparatus is described based on one or more units, e.g., functional units, a corresponding method can include one step to perform the function of one or more units (e.g., one step performs the function of one or more units, or multiple steps each perform the function of one or more of multiple units), even if one or more steps are not explicitly described or shown. Furthermore, it is understood that features of various exemplary embodiments and / or aspects described herein can be combined with each other, unless specifically stated otherwise.

[0057] 1 illustrates an exemplary wireless communication network 100 including a sharing AP 110 with a plurality of associated non-AP stations 115a-c and a plurality of shared APs 120 with a respective plurality of associated non-AP stations 125a-c for cooperative transmission, according to one embodiment. Each of the plurality of APs 110, 120 defines a respective basic service set (BSS) as shown in FIG. 1. As will be appreciated, as will be explained in more detail below, being a sharing AP and a shared AP can be considered roles or functions provided by the sharing AP 110 and the shared AP 120 in the exemplary scenario illustrated in FIG. 1, but may be reversed during further cooperative transmission periods. In other words, during further cooperative transmission periods (i.e., another obtained TXOP), one of the APs 120 may function as a sharing AP, and the AP 110 is one of the shared APs.

[0058] The wireless communication network 100 may be a WLAN (also referred to as a Wi-Fi network 100) that conforms to the IEEE 802.11 standards framework. By way of example, although three shared APs 120 are shown in FIG. 1 with associated non-AP stations 125a, b, and 125a-c, embodiments disclosed herein may be implemented with more or less than three shared APs 120.

[0059] As an example, the sharing AP 110 and the shared AP 120 shown in FIG. 1 may implement a cooperative beamforming transmission scheme (also referred to as CoBF transmission). However, it should be understood that the embodiments disclosed herein may also be implemented with other types of cooperative transmission schemes. CoBF transmission is a cooperative scheme proposed for next-generation Wi-Fi for simultaneous data transmission by several APs. This cooperative scheme assumes that each participating AP has the ability to precode its transmission signal so that mutual interference between this AP and STAs in an overlapping BSS (OBSS) during cooperative transmission is minimized (also referred to as nulling). As with all other cooperative schemes, CoBF is initiated by a sharing AP proposing other APs (called shared APs) to transmit simultaneously. The proposed resources in this case are spatial streams, and the sharing AP assigns a specific respective number of spatial streams to each shared AP. CoBF may utilize an additional sounding procedure to estimate the channel between the AP and non-AP stations. Based on the estimated channel, the AP may construct a precoder matrix to generate beams and nulls toward the non-AP stations participating in the current CoBF transmission.

[0060] The sharing AP 110 shown in FIG. 1 is configured to share at least a portion of its obtained transmission opportunities TXOPs with shared APs 120 operating under the same coordination agreement in a multi-AP set (also referred to as an M-AP set) to participate in cooperative transmissions, e.g., cooperative beamforming transmissions. As shown in FIG. 1, the sharing AP 110 includes a processing circuit 111 and a communication interface 113, particularly a wireless communication interface 113 according to the IEEE 802.11 standard framework. The processing circuit 111 may be implemented in hardware and / or software and may include digital circuits or both analog and digital circuits. The digital circuit may 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 sharing AP 110 may further include a memory 114 configured to store executable program code that, when executed by the processing circuit 111, causes the sharing AP 110 to perform the functions and methods described herein.

[0061] 1 includes a processing circuit 121 and a communication interface 123, particularly a wireless communication interface 123 according to the IEEE 802.11 standard framework. The processing circuit 121 may be implemented in hardware and / or software and may include digital circuitry or both analog and digital circuitry. The digital circuitry may 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. Each shared AP 120 may further include a memory 124 configured to store executable program code that, when executed by the processing circuit 121, causes the shared AP 120 to perform the functions and methods described herein.

[0062] Similarly, each non-AP station, such as the exemplary non-AP station 125a shown in FIG. 1, includes a processing circuit 126a and a communication interface 127a, particularly a wireless communication interface 127a according to the IEEE 802.11 standard framework. The processing circuit 126a may be implemented in hardware and / or software and may include digital circuitry or both analog and digital circuitry. The digital circuitry may 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 may further include a memory 128a configured to store executable program code that, when executed by the processing circuit 126a, causes the exemplary non-AP station 125a to perform the functions and methods described herein.

[0063] Some cooperative transmission schemes may involve communication between the APs 110, 120 and their OBSS stations 115a-c, 125a-c, i.e., between the APs 110, 120 and non-AP stations 115a-c, 125a-c associated with other APs. For example, as already mentioned above, for CoBF transmission, the APs 110, 120 may perform a sounding procedure and request sounding feedback reports from both the non-AP stations associated with it and the non-AP stations associated with other APs (also called OBSS, i.e., overlapping non-AP stations). This may be achieved by a so-called multi-AP (M-AP) frame 200 shown in FIG. 2. As shown in FIG. 2, such an M-AP frame 200 may include an M-AP set ID (identifier) ​​211 and a cooperation agreement ID (identifier) ​​213 in a common portion 210 of the M-AP frame 200 to be exchanged between APs operating under the same cooperation agreement in the same M-AP set. These parameters enable receivers to recognize and respond to the M-AP frame 200. In addition to the common portion 210, the M-AP frame 200 may include an STA information block 220a-n for each of the non-AP stations in the M-AP set and an AP information block 230a-n for each of the APs in the M-AP set. As shown in FIG. 2, the common portion 210 of the M-AP frame 200 may further include an indication block 215 regarding a desired response to the M-AP frame 200, and blocks 217, 219 indicating the number of STA information blocks 220a-n and AP information blocks 230a-n in the M-AP frame 200.

[0064] FIG. 3a illustrates a conventional M-AP cooperative transmission scheme 300. The M-AP cooperative transmission scheme 300 shown in FIG. 3a includes the following main steps: In step 301, a set of APs is determined to participate in cooperative transmission (this set is called a multi-AP set or M-AP set). In cooperative transmission agreement step 303, all or a subset of the member APs of the M-AP set agree to share each acquired TXOP, or part of it, with at least one other member AP operating under the same agreement. The cooperative agreement may last for several TXOPs, and specific participants (shared APs) may be exchanged between TXOPs. As already mentioned above, each TXOP may be acquired by a different AP (called a sharing AP), but all other APs, i.e., shared APs, may transmit during this TXOP (or part of it) only if triggered to do so by the sharing AP. The sharing AP decides how to share resources and with which APs in the current TXOP (this may be announced by the sharing AP and acknowledged by the shared AP).

[0065] As generally shown in FIG. 3b and described in more detail below, embodiments disclosed herein provide a management procedure 305 (referred to as an intra-BSS association indication procedure in FIG. 3b) that enables the sharing AP 110 and the shared AP(s) 120 to complete indication of their associated non-AP stations 115a-c, 125a-c operating under the same cooperative agreement within an allocated time period. Additionally, embodiments disclosed herein enable each AP 110, 120 of the M-AP set to be provided with information regarding whether it has completed indication or has not yet completed indication. As shown in FIG. 3b, procedure 305 may be performed once before one or more shared TXOP cooperative transmissions, such as before shared TXOP cooperative transmissions 313a and 313b and before shared TXOP cooperative transmission 333a.

[0066] The embodiments disclosed herein are based on the idea of ​​exchanging information between the sharing AP 110 and the shared AP 120(s) of the M-AP set, for example, by means of a data structure 400, in particular the lookup table 400 shown in FIG. 4 , which is managed by all APs 110, 120 of the M-AP set operating under the same collaboration agreement, such that each AP 110, 120 that is a member of the collaboration agreement possesses a local copy of the data structure 400.

[0067] 5, the communication interface 113 of the sharing AP 110 is configured to receive a completion status information frame 509, for example, from the shared AP1 120. As shown in FIG. 5, the completion status information 509 may be part of the completion status information frame 509 transmitted by the shared AP1 120 to the sharing AP 110. As shown in FIG. 3, prior to the completion status information frame 509, the sharing AP 110 and the shared AP 120 may have established a collaboration agreement in stage 303 (as already described above). The sharing AP 110 may transmit a collaboration announcement frame 501 and, in response, receive a collaboration acknowledgement 503 from the shared AP 120. The sharing AP 110 may then transmit an M-AP trigger frame 505 (which may have content similar to the M-AP frame 200 shown in FIG. 2, such as one or more identifiers) to the shared AP1 120 to transmit information related to operation under the cooperation agreement to one or more of its non-AP stations associated with that BSS in order to trigger the shared AP1 120.

[0068] This operation is shown in more detail in Figure 8. The sharing AP 110 may transmit an M-AP trigger frame 505 (which may have content similar to the M-AP frame 200 shown in Figure 2, such as one or more identifiers) to the shared AP1 120 to transmit information related to operation under the cooperation agreement to one or more of its non-AP stations 125a-c to trigger the shared AP1 120. In response to receiving the M-AP trigger frame 505, the shared AP1 120 (as part of the intra-BSS indication process 507) transmits an intra-BSS indication frame 801a to its associated non-AP stations 125a,b and receives an acknowledgment frame 803a in response. At a later stage, the shared AP1 120 (still as part of the intra-BSS indication process 507) may transmit a further intra-BSS indication frame 801b to its associated non-AP stations 125c and receive an acknowledgment frame 803b in response. Once the shared AP1 120 receives the acknowledgement frames 803a,b from all of the associated non-AP stations 125a,c, it transmits a completion status information frame 509 to the sharing AP 110 to notify the sharing AP 110 that the information related to operation under the collaboration agreement has been successfully transmitted to the non-AP stations 125a-c associated with the shared AP1 120. That is, the completion status information frame 509 indicates the completion status of the transmission of the information related to operation under the collaboration agreement 801a,b to the non-AP stations 125a-c associated with the shared AP1 120.

[0069] 5, the sharing AP 110, together with its associated non-AP stations 115a-c, may perform the same intra-BSS instruction process 507 as the shared AP1 120 (illustrated in FIG. 8 and described above), i.e., may transmit information related to operation under the cooperative agreement to one or more of its non-AP stations 115a-c. Based on these intra-BSS instruction processes 507 performed by the sharing AP 110 and the shared AP 120, the sharing AP 110 may generate and maintain a data structure, such as the lookup table 400 shown in FIG. 4, that indicates the completion status of each of the multiple shared APs 120. As illustrated in FIG. 4, the lookup table 400 may include a column 401 for identifying the AP and a column 403 that indicates the completion status of the transmission of information related to operation under the cooperative agreement to the non-AP stations associated with the respective AP. A sharing AP 110 may be configured to provide a current version of data structure 400 to multiple shared APs 120 via an M-AP intra-BSS indication status frame 511 shown in FIG.

[0070] As described below with further reference to FIG. 6 , each AP member of the collaboration agreement, 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 status of “complete” may participate in the collaborative transmission(s). If the sharing AP 110 wants to include any shared APs 120 with a status of “not complete” in the collaborative transmission, it may initiate the intra-BSS association indication procedure described above in the context of FIG. 5 with those shared APs before the start of the collaborative transmission. As shown in FIG. 6 , 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 a status of “not complete” to complete the intra-BSS indication process 507, which is shown in detail in FIG. 8 .

[0071] As already mentioned above, the intra-BSS indication process 507, detailed in FIG. 8, may be triggered and managed by the sharing AP 110 such that each shared AP 120 (that is a member of the current cooperation agreement) sends information 801a, b to its associated non-AP stations 125a-c once per established cooperation agreement. In one embodiment, each shared AP 120 may be required to complete its indication before being able to participate in cooperative transmissions with its BSS stations. In one embodiment, all APs 110, 120 operating under the same cooperation agreement may complete their intra-BSS association indication procedure 507 within multiple TXOPs, such as within the first TXOP 610 and second TXOP 630 shown in FIG. 6. The embodiments disclosed herein enable all APs 110, 120 operating under the same cooperation agreement to reliably know the completion status of the intra-BSS association indication procedure 507 of all other APs 110, 120 operating under the same cooperation agreement at the end of a TXOP.

[0072] The following provides a more detailed description of Figure 6. In the scenario shown in Figure 6, four APs, namely AP1, AP2, AP3, and AP4, are members of a collaboration agreement. Figure 6 shows exemplary communications between the four APs during two TXOPs 610, 630 immediately after the collaboration agreement is established. The first TXOP 610 is acquired by AP1 (i.e., AP1 is the shared AP 110 of the first TXOP, and AP2, AP3, and AP4 are the shared APs 120), and the second TXOP 630 is acquired by AP2 (i.e., AP2 is the shared AP 110 of the second TXOP, and 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 sharer of the first TXOP 610, wants to share TXOP resources with AP2 and AP3 for M-AP cooperative transmission. Therefore, according to one embodiment, AP1, the current sharer AP 110, based on the status information in table 400, triggers AP2 and AP3 to complete the intra-BSS association instruction 507 in the manner already described above. Once both AP2 and AP3 transmit completion instruction frames 509 and AP1 executes the intra-BSS instruction 507 for its own BSS stations 115a, b, a status update frame 511 is transmitted to all shared APs operating under the same cooperative agreement (to include APs that have completed the intra-BSS instruction procedure with their BSS). In response to receiving the status update frame 511, all APs operating under the same cooperative agreement may update their local copies of the completion status table 400, where AP1, AP2, and AP3 are marked with the status "completed." Thus, AP1 may perform cooperative transmission 313a with either AP2 or AP3 as part of the first TXOP 610. For the second TXOP 630, which AP2 shares with AP 110, AP2 wants to share its acquired TXOP resources with AP4 (which is one of the shared APs 120).However, because AP4 is still indicated with a status of "not completed" in the completion status table 400, sharing AP2 110 shall trigger shared AP4 120 to execute intra-BSS instruction 507. When shared AP4 120 transmits completion instruction frame 509 to sharing AP2 110, sharing AP2 110 may send status update frame 511 to all APs operating under the same collaboration agreement (including AP1 and AP3, which have already completed their intra-BSS instructions). In response to status update frame 511, all APs operating under the same collaboration agreement may update their local copies of completion status table 400, and all APs are marked as "completed." From this point onwards (until the collaboration agreement expires), any subset of AP1, AP2, AP3, and AP4 may begin collaborative transmissions if any of them become sharing APs (get a TXOP).

[0073] As already mentioned above and shown in Figure 7, the sharing AP 110 may transmit an M-AP trigger frame 505 to each of the shared AP(s) 120 to trigger each sharing AP 110 to initiate an intra-BSS indication procedure with its associated non-AP stations, as shown in 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 collaboration agreement identifier, and / or a list of APs in the M-AP set.

[0074] As illustrated in FIG. 8 and previously described, the AP 120 may transmit intra-BSS indication frames 801 a, b to associated non-AP stations 125 a-c. The frames 801 a, b may be part of a PPDU (see details below) and may include an M-AP set identifier, a cooperation agreement identifier, a list of participating APs, and / or cooperation scheme-related information. The intra-BSS indication frames 801 a, b shown in FIG. 8 may be dedicated unicast frames. In further embodiments, the intra-BSS indication frames 801 a, b may be “multicast”-like frames, such as broadcast management frames, intended for a group of non-AP stations 125 a-c specified within the frame body.

[0075] 6, the sharing AP 110 may send an M-AP indication status frame 511 to all shared APs 120 operating under the same coordination agreement to update all shared APs 120 regarding the respective completion status of each AP's intra-BSS indication procedure 507. In one embodiment, the M-AP indication status frame 511 may include a list of APs operating under the same coordination agreement, information regarding the completion status for each AP for updating their local copies of table 400, an M-AP set identifier, and / or a coordination agreement identifier. In a further embodiment, the M-AP indication status frame 511 may include the entire completion status table 400 generated and maintained by the sharing AP 110.

[0076] 9 is a flow chart illustrating a method 900 of operating a sharing AP 110 according to one embodiment. As already described above, the sharing AP 110 is configured to share at least a portion of TXOPs with one or more shared APs 120(s) operating under a cooperative agreement in an M-AP set to participate in cooperative transmissions to one or more non-AP stations 115a-c associated with the sharing AP 110 and to additional non-AP stations 125a-c associated with each of the shared APs 120. The method 900 includes a step 901 of receiving completion status information 509 from one or more of the shared APs 120(s), the completion status information 509 indicating a completion status of a transmission of information 801a, b related to operation under the cooperative agreement to one or more of the additional non-AP stations 125a-c associated with the respective shared AP 120. Further, the method 900 includes generating and maintaining 903 a data structure 400 based on the completion status information 509 of each of the one or more shared AP(s) 120 operating under the collaboration agreement, the data structure 400 indicating the completion status for each of the plurality of shared APs 120. As already mentioned above, in one embodiment, the data structure 400 may be a lookup table 400.

[0077] As will be understood from the detailed description of the shared AP 110 above, the method 900 may further include generating and transmitting one or more M-AP trigger frames, in particular one or more M-AP trigger frames for intra-BSS instructions, to one or more of the multiple shared APs 120 to trigger, i.e., to request each shared AP 120 to provide information related to operation under the cooperation agreement to one or more additional non-AP stations 125a-c associated with the respective shared AP 120.

[0078] Because the method 900 may be performed by the sharing AP 110, further features of the method 900 result directly from the functionality of the sharing AP 110 and the different embodiments described above and below.

[0079] 10 is a flow chart illustrating a method 1000 of operating one of a plurality of shared APs 120 according to one embodiment. As already described above, the shared AP 120 is configured to participate in cooperative transmissions to one or more non-AP stations 125 a-c associated with the shared AP 120 and one or more additional non-AP stations 115 a-c associated with the sharing AP 110, utilizing at least a portion of the shared TXOPs obtained by the sharing AP 110 operating under a cooperative agreement in the M-AP set. The method 1000 includes a step 1001 of transmitting information 801 a, b related to operation under the cooperative agreement to one or more non-AP stations 125 a-c associated with the shared AP 120. Furthermore, the method 1000 includes a step 1003 of transmitting completion status information 509 to the sharing AP, where the completion status information 509 indicates a completion status of transmitting the information 801 a, b related to operation under the cooperative agreement to one or more non-AP stations 125 a-c associated with the shared AP 120.

[0080] As will 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 sharing AP 110, and, in particular, transmitting information related to operation under the cooperation agreement to one or more non-AP stations 125a-c associated with the shared AP 120 in response to receiving the M-AP trigger frame from the sharing AP 110.

[0081] Because the method 1000 may be performed by a shared AP 120, further features of the method 1000 result directly from the shared AP 120 and the functionality of the different embodiments described above and below.

[0082] 11 is a flow chart illustrating a method 1100 of operating an exemplary non-AP station 125a associated with a shared AP 120, according to one embodiment. As already described above, the shared AP 120 is configured to utilize at least a portion of the TXOPs obtained and shared by the sharing AP 110 operating under a cooperation agreement in the M-AP set to participate in cooperative transmissions to the non-AP station 125a associated with the shared AP 120 and to multiple additional non-AP stations 115a-c, 125b, c associated with the shared AP 120 or the sharing AP 110. The method 1100 includes a step 1101 of receiving information 801a related to operation under the cooperation agreement from the shared AP 120. Furthermore, the method 1100 includes a 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 cooperation agreement from the shared AP 120.

[0083] Because the method 1100 can be implemented by a non-AP station 125a associated with the shared AP 120, further features of the method 1100 result directly from the functionality of the non-AP station 125a and the different embodiments described above and below.

[0084] Those skilled in the art will appreciate that the "blocks" ("units") of the various figures (method and apparatus) represent or describe functions of embodiments of the present disclosure (not necessarily individual "units" of hardware or software), and thus equally describe functions or features of apparatus embodiments as well as method embodiments (units = steps).

[0085] In some embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be realized in other ways. For example, the described device embodiments are merely examples. For example, the unit division is merely a logical functional division, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the shown or described mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. Indirect couplings or communication connections between devices or units may be realized electronically, mechanically, or in other forms.

[0086] The units described as separate parts may or may not be physically separated, and the 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 according to actual needs to achieve the objectives of the solutions of the present embodiment.

[0087] Furthermore, the functional units in the embodiments disclosed herein may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit. [Explanation of symbols]

[0088] 100 Wireless communication networks, Wi-Fi networks 110 Shared AP 111 Processing circuit 113 Communication interface, wireless communication interface 114 memory 115a Non-AP station, BSS station, OBSS station 115b Non-AP station, BSS station, OBSS station 115c Non-AP stations, BSS stations, OBSS stations 120 shared AP 121 Processing circuit 123 Communication interface, wireless communication interface 124 memory 125a Non-AP station 125b Non-AP station 125c non-AP station 126a Processing circuit 127a Communication interface, wireless communication interface 128a memory 200 Multi-AP frames, M-AP frames 210 Common parts 215 Instruction Block 217 blocks 220a STA Information Block 230a AP Information Block 300 AP cooperative transmission method 301 steps 303 Cooperative Transmission Agreement Phase 305 Administrative Procedures 313a Cooperative Transmission, Shared TXOP Cooperative Transmission 313b Cooperative Transmission, Shared TXOP Cooperative Transmission 333a Cooperative Transmission, Shared TXOP Cooperative Transmission 400 Data Structures, Lookup Tables, Completion Status Tables Column 401 Column 403, instructions 501 Collaborative Announcement Frame 503 Cooperative Approval 505 AP trigger frame 507 Intra-BSS instruction process, Intra-BSS instruction procedure, Intra-BSS instruction, Intra-BSS related instruction procedure 509 Completion Status Information, Completion Status Information Frame 511 Indication status frame, status update frame 610 First TXOP 630 Second TXOP 801a Intra-BSS instruction frame and related information 801b BSS instruction frame 803a Acknowledgment Frame, Information 803b Acknowledgment Frame, Information

Claims

1. a sharing access point (AP) (110) configured to share at least a portion of transmission opportunities (TXOPs) with a plurality of shared APs (120) operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations (115a-c) associated with the sharing AP and a plurality of further non-AP stations (125a-c) associated with the plurality of shared APs (120), the sharing AP (110) comprising: a communication interface (113) configured to receive completion status information (509) frames from one or more of the plurality of shared APs (120), the completion status information (509) indicating a completion status of transmission of information (801 a, b) related to operation under the cooperation agreement to one or more of the plurality of additional non-AP stations (125 a-c) associated with the respective shared AP (120); a processing circuit (111) configured to generate and maintain a data structure (400) based on the completion status information (509) frame of each of the one or more of the plurality of shared APs (120), the data structure (400) including the completion status of each of the plurality of shared APs (120); Including shared AP (110).

2. The sharing AP (110) of claim 1, wherein the communication interface (113) is configured to transmit the data structure (400) to each of the plurality of shared APs (120).

3. The sharing AP (110) of claim 2, wherein the communication interface (113) is configured to transmit an instruction status frame (511) to the plurality of shared APs (120), the instruction frame (511) including the data structure (400).

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

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

6. A sharing AP (110) as described in any one of claims 3 to 5, wherein the instruction frame (511) further includes a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

7. 7. The sharing AP (110) of claim 1, wherein the data structure (400) includes an indication (403) of the completion status of each of the multiple shared APs (120) and the sharing APs (110) operating under the same collaboration agreement.

8. The sharing AP (110) of any one of claims 1 to 7, wherein the data structure (400) comprises a lookup table (400).

9. 9. The sharing AP (110) of claim 1, wherein the communication interface (113) is further configured to transmit one or more M-AP trigger frames (505) to one or more of the plurality of shared APs (120) to provide the information (509) related to operation under the coordination agreement to one or more further non-AP stations (125a-c) associated with the respective shared AP (120) to trigger the respective shared AP (120).

10. 10. The sharing AP (110) of claim 9, wherein the communication interface (113) is configured to transmit the one or more M-AP trigger frames (505) to one or more of the plurality of shared APs (120) for which the data structure (400) indicates that the respective shared AP (120) has not completed an intra-BSS association procedure, so as to provide the one or more further non-AP stations (125a-c) associated with the respective shared AP (120) with the information (509) related to operation under the coordination agreement to trigger the respective shared AP (120).

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

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

13. 13. The sharing AP (110) of claim 9, wherein the one or more M-AP trigger frames (505) include a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

14. The sharing AP (110) of any one of claims 1 to 13, wherein the processing circuit (111) is configured to limit the cooperative transmission to a shared AP (120) among the plurality of shared APs (120) for which the sharing AP (110) has indicated status information as "completed."

15. The sharing AP (110) of any one of claims 1 to 14, wherein the information (801a, b) related to operation under the collaboration agreement includes an M-AP set identifier indicating the M-AP set.

16. A sharing AP (110) as described in any one of claims 1 to 15, wherein the information (801a, b) related to operation under the collaboration agreement includes a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements in the M-AP set, and the sharing AP (110) and the multiple shared APs (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

17. The sharing AP (110) of any one of claims 1 to 16, wherein the information (801a, b) related to operation under the collaboration agreement includes a MAC address and / or identifier of each of the plurality of shared APs (120).

18. The sharing AP (110) of any one of claims 1 to 17, further comprising a memory (114), the memory (114) configured to store the data structure (400).

19. 9. A method (900) of operating a sharing access point (AP) (110) configured to share at least a portion of transmission opportunities (TXOPs) with a plurality of shared APs (120) operating under a cooperative agreement in a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations (115a-c) associated with the sharing AP (110) and a plurality of further non-AP stations (125a-c) associated with the plurality of shared APs (120), the method (900) comprising: receiving (901) a completion status information (509) frame from one or more of the plurality of shared APs (120), the completion status information (509) frame indicating a completion status of transmission of information (801 a, b) related to operation under the cooperation agreement to one or more of the plurality of additional non-AP stations (125 a-c) associated with the respective shared AP (120); generating and maintaining a data structure (400) based on the completion status information (509) frames of each of the one or more of the shared APs (120) operating under the collaboration agreement, the data structure (400) indicating the completion status of each of the shared APs (120); A method (900).

20. 20. The method (900) of claim 19, further comprising transmitting one or more M-AP trigger frames (505) to one or more of the plurality of shared APs (120) to provide the information (509) related to operation under the cooperation agreement to one or more additional non-AP stations (125a-c) associated with the respective shared AP (120) to trigger the respective shared AP (120).

21. a shared access point (AP) (120) configured to utilize at least a portion of shared transmission opportunities (TXOPs) obtained by a sharing AP (110) operating under a cooperative agreement within a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations (125a-c) associated with the shared AP (120) and one or more further non-AP stations (115a-c) associated with the sharing AP (110), wherein the shared AP (120): a communication interface (123) configured to transmit information (801 a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125 a-c) associated with the shared AP (120); The shared AP (120), wherein the communication interface (123) is further configured to transmit a completion status information (509) frame to the sharing AP (110), the completion status information (509) frame indicating a completion status of transmission of the information (801a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125a-c) associated with the shared AP (120).

22. The shared AP (120) of claim 21, wherein the communication interface (123) is further configured to receive a data structure (400) from the sharing AP (110), the data structure (400) indicating, for the sharing AP (110) and for each of a plurality of further shared APs (120) operating under the cooperation agreement in the M-AP set, the completion status of the transmission of the information (801a, b) related to operation under the cooperation agreement to one or more non-AP stations (115a-c) associated with the sharing AP (110) or each further shared AP (120).

23. The shared AP (120) of claim 22, wherein the communication interface (123) is configured to receive an instruction frame (511) from the sharing AP (110), the instruction status frame (511) including the data structure (400).

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

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

26. 26. A shared AP (120) according to any one of claims 23 to 25, wherein the instruction status frame (511) further includes a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP (110) and multiple shared APs (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

27. 27. A 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 of a plurality of the shared APs (120) operating under the same collaboration agreement.

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

29. 29. The shared AP (120) of claim 21, wherein the communication interface (123) is configured to transmit the information (801a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125a-c) associated with the shared AP (120) following receipt of an M-AP trigger frame (505) from the sharing AP (110).

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

31. The shared AP (120) of claim 29 or 30, wherein the M-AP trigger frame (505) includes an M-AP set identifier that indicates the M-AP set.

32. 32. The shared AP (120) of claim 29, wherein the M-AP trigger frame (505) includes a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

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

34. A shared AP (120) according to any one of claims 21 to 33, wherein the information (801a, b) relating to operation under the collaboration agreement includes a collaboration agreement identifier within the M-AP set, the collaboration agreement identifier identifying one collaboration agreement among multiple collaboration agreements within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the collaboration agreement identified by the collaboration agreement identifier within the M-AP set.

35. A shared AP (120) according to any one of claims 21 to 34, wherein the information (801a, b) relating to operation under the cooperation agreement includes addresses and / or identifiers of the shared AP (120) and one or more further shared APs (120) operating under the same cooperation agreement within the M-AP set.

36. 36. The shared AP (120) of claim 21, further comprising a memory (124), the memory (124) configured to store the data structure (400).

37. 37. The shared AP (120) of claim 21, wherein the communication interface (123) is further configured to receive an acknowledgement frame (803a, b) from each of the one or more non-AP stations (125a-c) associated with the shared AP (120) in response to transmitting the information (801a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125a-c) associated with the shared AP (120).

38. A method (1000) of operating a shared access point (AP) (120) configured to utilize at least a portion of shared transmission opportunities (TXOPs) obtained by a sharing AP (110) operating under a cooperative agreement within a multi-AP (M-AP) set to participate in cooperative transmissions to one or more non-AP stations (125a-c) associated with the shared AP (120) and one or more further non-AP stations (115a-c) associated with the sharing AP (110), the method (1000) comprising: transmitting (1001) information (801a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125a-c) associated with the shared AP (120); transmitting (1003) a completion status information (509) frame to the sharing AP (110), the completion status information (509) indicating a completion status of transmission of the information (801 a, b) related to operation under the collaboration agreement to the one or more non-AP stations (125 a-c) associated with the shared AP (120); A method (1000) comprising:

39. The method (1000) of claim 38, further comprising: receiving an M-AP trigger frame (505) from the sharing AP (110); and, following the reception of the M-AP trigger frame (505) from the sharing AP (110), transmitting the information (801a, b) related to operation under the cooperation agreement to the one or more non-AP stations (125a-c) associated with the shared AP (120).

40. a non-AP station (125a) associated with a shared access point (AP) (120), the shared AP (120) configured to utilize at least a portion of a shared transmission opportunity (TXOP) obtained by the sharing AP (110) operating under a cooperative agreement within a multi-AP (M-AP) set to participate in cooperative transmissions to the non-AP stations (125a-c) associated with the shared AP (120) and to a plurality of additional non-AP stations (115a-c, 125b, c) associated with the shared AP (120) or the sharing AP (110), the non-AP station (125a) a communication interface (127a) configured to receive information (801a) related to operation under the collaboration agreement from the shared AP (120); A non-AP station (125a), wherein the communication interface (127a) is further configured to transmit an acknowledgment frame (803a) to the shared AP (120) in response to receiving the information (801a) related to operation under the collaboration agreement from the shared AP (120).

41. 41. The non-AP station of claim 40, wherein the information related to operation under the cooperation agreement 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 cooperation agreement includes a cooperation agreement identifier within the M-AP set, the cooperation agreement identifier identifying one cooperation agreement among multiple cooperation agreements within the M-AP set, and the sharing AP (110) and the shared AP (120) operate under the cooperation agreement identified by the cooperation agreement identifier within the M-AP set.

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

44. 1. A method (1100) of operating a non-AP station (125a) associated with a shared access point (AP) (120), wherein the shared AP (120) is configured to utilize at least a portion of a shared transmission opportunity (TXOP) obtained by the sharing AP (110) operating under a cooperative agreement within a multi-AP (M-AP) set to participate in cooperative transmissions to the non-AP station (125a) associated with the shared AP (120) and to a plurality of additional non-AP stations (115a-c, 125b, c) associated with the shared AP (120) or the sharing AP (110), the method (1100) comprising: receiving (1101) information (801a) related to operation under the collaboration agreement from the shared AP (120); transmitting (1103) an acknowledgement frame (803a) to the shared AP (120) in response to receiving the information (801a) related to operation under the collaboration agreement from the shared AP (120); A method (1100) comprising:

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

Images