Resource units for non-associated stations and grouped multi-user transmissions in 802.11AX networks

The method allocates RUs using a unique association identifier and enhances acknowledgment mechanisms to address inefficiencies in 802.11ax MU downlink and uplink transmissions, improving efficiency and reducing latency and bandwidth waste.

JP7591025B2Active Publication Date: 2024-11-27CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2022208675
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2018-04-16
Filing Date
2022-12-26
Publication Date
2024-11-27
Estimated Expiration
2038-04-20

AI Technical Summary

Technical Problem

The current 802.11ax multi-user (MU) downlink and uplink OFDMA transmission mechanisms in wireless communication networks are inefficient due to issues such as padding bits, bandwidth waste from SU signaling for registration and frame duplication in multicast traffic, and the inability to effectively manage stations without an Association Identifier (AID).

Method used

A method and device that allocate resource units (RUs) to stations using a unique association identifier, allowing efficient identification and communication with stations not yet associated, and implement an improved acknowledgment mechanism for group RUs, reducing latency and optimizing bandwidth usage.

Benefits of technology

Significantly improves MU downlink transmission efficiency by reducing medium occupancy and latency during association procedures, minimizing bandwidth waste, and enabling efficient communication with unassociated stations and multicast traffic.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007591025000002
    Figure 0007591025000002
  • Figure 0007591025000003
    Figure 0007591025000003
  • Figure 0007591025000004
    Figure 0007591025000004
Patent Text Reader

Abstract

Improve resource unit usage in MU transmissions in 802.11ax networks. [Solution] An unassociated station (US) can receive a data frame (DF) via a downlink (DL) resource unit (RU) assigned to an AID, e.g., 2045, reserved for stations not associated with an AP. The AP can use a DLRU that shares the allocation scheme characteristics of an uplink (UL) RU previously used by the US. The AP can also aggregate DFs addressed to several stations within the same DLRU, for example, to acknowledge frames previously received from the stations. The aggregated DF can signal which response RU the receiving station should use for the next multi-user UL transmission to respond to the AP. These techniques can be particularly applied to the exchange of management frames to expedite the US association procedure.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates generally to wireless communication networks comprising access points (APs) and stations, and more particularly to the transmission of data frames and / or acknowledgments within transmission opportunities comprised of sub-channels or resource units, and corresponding devices.

[0002] The present invention applies in wireless communication networks, in particular to the access of 802.11ax composite channels and to the access of OFDMA resource units forming, for example, an 802.11ax composite channel for downlink communication from an access point to a station. One application of the method considers wireless data communication over a wireless communication network using carrier sense multiple access with collision avoidance (CSMA / CA), the network being accessible by multiple station devices. [Background technology]

[0003] The IEEE 802.11 MAC family of standards (a / b / g / n / ac / etc.) specifies how Wireless Local Area Networks (WLANs) operate at the physical and Medium Access Control (MAC) levels. Typically, the 802.11 MAC (Medium Access Control) mode of operation implements the well-known Distributed Coordination Function (DCF), which relies on a contention-based mechanism based on the so-called "Carrier Sense Multiple Access with Collision Avoidance" (CSMA / CA) technique.

[0004] Recently, the Institute of Electrical and Electronics Engineers (IEEE) officially approved the 802.11ax task group as the successor to 802.11ac. The main goal of the 802.11ax task group is to explore ways to improve data rates for wireless communication devices (or stations) used in high-density deployment scenarios.

[0005] In this regard, multi-user (MU) transmission has been considered to enable multiple simultaneous transmissions to / from different stations (i.e., users) registered with the AP, in both the downlink (DL) direction from the AP and the uplink (UL) direction to the AP, during a transmission opportunity granted to the AP over a 20 MHz (or greater) communication channel.

[0006] In the uplink, multi-user transmission is used to reduce the collision probability. This is because multiple non-AP stations are allowed to transmit simultaneously.

[0007] To practically implement such multi-user transmissions, it has been proposed to divide the granted communication channel (or transmission opportunities granted to the AP) into sub-channels, also called resource units (RUs), which are typically shared among multiple users (non-AP stations / nodes) in the frequency domain, e.g., based on Orthogonal Frequency Division Multiple Access (OFDMA) techniques.

[0008] The multi-user downlink OFDMA and uplink OFDMA scheme offers overhead reduction as a key advantage.

[0009] To perform a multi-user (MU) downlink OFDMA transmission, the AP transmits a MU packet over the entire allowed communication channel, which means that from the RU's perspective, the same preamble is transmitted. Then, the AP transmits a RU-dependent payload, which means that the payload is different for different RUs among the entire allowed communication channel. The assignment of RUs to stations is signaled at the beginning of the MU downlink frame by giving the station's association identifier (AID) for each RU defined in the transmission opportunity.

[0010] Such an AID is obtained individually by each station when it registers with or associates with an AP during an association procedure, i.e., when the station joins a group of stations managed by the AP. During the association procedure, the not yet associated station, i.e., the "unassociated station", and the AP exchange a series of single-user (SU) 802.11 management frames to enter the authenticated and associated state for the station. As a result of the association procedure, the station is assigned an AID and is able to use MU communication (resource units).

[0011] The AID is typically formed by the lowest 11 bits of a 12-bit identifier.

[0012] Thus, a station may be either registered or associated with an AP and have an AID, or may not yet be registered or associated with an AP and not have an AID until registration is complete.

[0013] A group of stations together with an access point is known as a Basic Service Set (BSS). Note that the range of available AIDs must be shared among several groups of stations (i.e., several BSSs) that can be served by the same physical access point, instantiating a virtual access point for each BSS.

[0014] Stations receiving an MU downlink frame in their respective assigned RUs may have to acknowledge receipt during a multi-user (MU) uplink OFDMA transmission that follows the MU downlink OFDMA transmission within the same transmission opportunity.

[0015] To perform a multi-user (MU) uplink OFDMA transmission, the AP transmits a control frame known as a Trigger Frame (TF) to a station, after which the station can access one RU assigned to it. The assignment of an RU to a station is signaled in the same manner as above (for downlink transmission using AID), but in the payload of the TF packet.

[0016] Since a station is generally equipped with a single transceiver, in 802.11ax, allocation of multiple RUs to one and the same station for both multi-user downlink and uplink transmissions should not be allowed. Of course, a station with multiple transceivers can be assigned multiple RUs.

[0017] Thus, in the context of 802.11ax, a station is assigned at most one RU and all stations are provided with the same RU length. This has several implications:

[0018] In the specific case of acknowledging the MU downlink through the MU uplink transmission, the AP does not use a separate trigger frame. Rather, the AP directly indicates in the data frame transmitted through each RU of the MU downlink transmission which RU the receiving station must use in the subsequent MU uplink OFDMA transmission to acknowledge the data frame. This specific indication is carried by the so-called UMRS field (standing for UL MU Response Scheduling) provided in at least one data frame of each MU downlink RU.

[0019] For multi-user uplink OFDMA transmissions, the AP does not know how much data each station has to transmit, therefore 802.11ax requires that the AP give an indication in the trigger frame to the stations regarding the size of the requested (and granted) transmission opportunity, i.e., for how long each station can transmit data in its allocated RUs.

[0020] For multi-user downlink OFDMA transmission, the AP may have different amounts of data to transmit to the stations, and therefore the AP may have to add padding bits to the shortest packet until the transmission opportunity ends.

[0021] Padding is a waste of bandwidth and should be avoided.

[0022] Also, the association procedure introduced above seems to consume bandwidth. This is mainly because SU management frames are transmitted at a low bit rate (typically the lowest bit rate supported) over a 20 MHz channel to allow legacy (i.e., not implementing 802.11ax) stations to understand the common 802.11 preamble. Also, this is because each SU management frame requests a specific access to the medium by a station, and therefore requires the station to wait until new medium access is granted. As the number of BSSs in the same area increases and / or the number of stations in a BSS increases substantially, more channel bandwidth is lost due to such SU signaling, and the cost of accessing the medium by a station increases.

[0023] Recently, the 802.11ax task group proposed a mechanism whereby an AP reserves one or more RUs of a multi-user uplink OFDMA transmission for not yet associated stations, i.e., "unassociated" stations (which are 802.11ax compliant). This mechanism expedites registration of these stations to the AP by sending a request management frame over such reserved RUs (in MU uplink OFDMA mode). The proposed mechanism relies on using a predefined AID value equal to 2045 to indicate a random RU that not yet associated stations can access through contention.

[0024] Even with this new mechanism, the response management frame from the AP is performed using low bit rate SU signaling, since these not yet associated stations cannot be assigned RUs in MU downlink transmissions due to their inability to have their own AIDs, and channel bandwidth is still wasted.

[0025] Furthermore, 802.11 does not provide a mechanism for multicast traffic, while an AP may receive a multicast frame from a higher OSI layer, e.g., a link layer implementing Ethernet multicast. In that case, the AP must generate multiple data frames containing the payload of the received multicast frame, which will be individually addressed to each one of the recipient stations. Each data frame is then transmitted in a dedicated RU of a multi-user downlink OFDMA transmission, which results in the same payload data being duplicated multiple times across several RUs. Again, this wastes channel bandwidth.

[0026] Therefore, the current operation mode of the 802.11ax multi-user mechanism is not fully satisfactory due to at least the above-mentioned disadvantages related to padding bits, SU signaling for registration, and frame duplication for multicast traffic. Summary of the Invention

[0027] The broad object of the present invention is to effectively improve this situation, i.e. to overcome some or all of the limitations mentioned above. In particular, the present invention seeks to provide a more efficient use of MU downlink transmissions from the AP.

[0028] The multi-user downlink communication protocol can be improved to allow stations to efficiently identify their RUs in MU downlink transmissions from APs that do not allow AID, such as in the case of stations that are not yet associated, i.e., unassociated stations.

[0029] The present approach proposes an improved wireless communication method in a wireless network comprising access points and stations.

[0030] In an embodiment, any station that registers or associates with an access point is associated with or assigned a unique association identifier that is used by the access point to allocate resource units to the station in transmission opportunities granted to the access point, and the method includes, at one of the stations: determining downlink resource units to be assigned to association identifiers reserved for stations not associated with the access point (meaning that the AID is not associated with at least one particular station) from a plurality of downlink resource units included in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point; receiving a frame(s) from the access point on the determined downlink resource unit; Includes.

[0031] In another embodiment, the method includes, at one of the stations: transmitting a frame to the access point using one uplink resource unit of a plurality of uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the plurality of uplink resource units being allocated according to an allocation scheme; determining a downlink resource unit from a plurality of downlink resource units included in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point based on at least one allocation scheme feature of the uplink resource unit; receiving a frame(s) from the access point on the determined downlink resource unit; Includes.

[0032] From an AP perspective, an improved wireless communication method in a wireless network comprising access points and stations is also proposed.

[0033] In an embodiment, any station that registers with or associates with an access point is associated with or assigned a unique association identifier that is used by the access point to allocate resource units to the station in transmission opportunities granted to the access point, the method comprising: constructing a plurality of downlink resource units in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point, the plurality of downlink resource units including downlink resource units assigned to association identifiers reserved for stations not associated with the access point (meaning that the AID is not at least associated with a particular station); transmitting a frame to a station on a downlink resource unit assigned to an association identifier reserved for stations not associated with the access point; Includes.

[0034] In another embodiment, the method comprises, at the access point: receiving a frame from a station on one uplink resource unit of a plurality of uplink resource units included in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point; constructing a plurality of downlink resource units in a multi-user downlink transmission from an access point within a transmission opportunity granted to the access point, the plurality of downlink resource units including downlink resource units having at least one matching allocation scheme characteristic with an uplink resource unit; transmitting a frame (typically a response to a frame received on an uplink RU) to a station on a downlink resource unit; Includes.

[0035] 802.11ax already proposes a prefixed number of RU allocation schemes for a 20MHz channel, each of which defines a specific allocation of RUs within a 20MHz channel (e.g., in terms of RU size, frequency band, and RU position along the frequency direction in 802.11ax). The RU allocation schemes are declared, for example, in the HE-SIG-B field of the MU downlink frame or in an equivalent field of the trigger frame.

[0036] A different RU allocation scheme can be used for each 20 MHz channel forming a 40 MHz, or 80 MHz, or 160 MHz wide composite channel.

[0037] By using a downlink RU that matches an already used uplink RU according to some RU allocation scheme criteria / characteristics, an AID is no longer needed for a station to identify which downlink RU to listen to for downlink transmission, which is particularly advantageous for communicating with stations that are not yet associated with the AP (i.e., do not have an AID).

[0038] In another embodiment, by using an AID that is not associated with a station during MU downlink transmission, the proposed method gives the AP the opportunity to address stations that do not provide an AID, such as stations that are not associated with the AP. In this case, for a particular embodiment, the AID that is not associated with a particular station can be reserved for stations that are not associated with the AP. Again, such stations can easily identify which downlink RU to wait for in the downlink transmission.

[0039] As will be described more extensively below, these techniques can be implemented during the association procedure for such unassociated stations, resulting in a significant reduction in medium occupancy and overall latency for the association procedure in 802.11ax networks.

[0040] Therefore, MU downlink transmission is significantly improved compared to the current requirements of known 802.11ax.

[0041] Also provided is a wireless communications device forming a station in a wireless network comprising access points and stations.

[0042] In an embodiment, any station that registers or associates with an access point is associated with or assigned a unique association identifier that is used by the access point to allocate resource units to that station in transmission opportunities granted to the access point, and the devices forming the station include: determining downlink resource units to be assigned to association identifiers reserved for stations not associated with the access point (meaning that the AID is not associated with at least one particular station) from a plurality of downlink resource units included in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point; receiving a frame from the access point on the determined downlink resource unit; The computer-implemented method includes:

[0043] In another embodiment, the devices forming the station include: transmitting a frame to the access point using one uplink resource unit of a plurality of uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the plurality of uplink resource units being allocated according to an allocation scheme; determining a downlink resource unit from a plurality of downlink resource units included in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point based on at least one allocation scheme characteristic of the uplink resource unit; receiving a frame from the access point on the determined downlink resource unit; The computer-implemented method includes:

[0044] Also provided is a wireless communications device forming an access point in a wireless network comprising access points and stations.

[0045] In an embodiment, any station that associates with an access point is assigned a unique association identifier that is used by the access point to allocate resource units to the station in transmission opportunities granted to the access point, and the device forming the access point is constructing a plurality of downlink resource units in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point, the plurality of downlink resource units including downlink resource units assigned to association identifiers reserved for stations not associated with the access point (meaning that the AID is not at least associated with a particular station); transmitting a frame to a station on a downlink resource unit that is assigned to an association identifier that is reserved for stations that are not associated with the access point; The computer-implemented method includes:

[0046] In another embodiment, the device forming the access point comprises: receiving a frame from a station on one uplink resource unit of a plurality of uplink resource units included in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the plurality of uplink resource units being allocated according to an allocation scheme; constructing a plurality of downlink resource units in a multi-user downlink transmission from an access point within a transmission opportunity granted to the access point, the plurality of downlink resource units including downlink resource units having at least one matching allocation scheme characteristic with an uplink resource unit; transmitting a frame (typically a response to a frame received on an uplink RU) to a station on a downlink resource unit; The computer-implemented method includes:

[0047] Optional features of these embodiments are defined in the appended claims referring to the method. Naturally, the same features can be replaced by features of the system dedicated to any device according to an embodiment of the invention.

[0048] In an embodiment relating to a station, a plurality of downlink resource units are determined in the determining step (it can be considered that there is an RU-based aggregation of the data frames across a plurality of downlink RUs), and the method can further include extracting one or more data frames from one of the plurality of determined downlink resource units.

[0049] In an embodiment relating to a station, the method may further include transmitting, at the station, a frame to the access point using one of a plurality of uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the plurality of uplink resource units being allocated according to an allocation scheme. In that case, determining the downlink resource units to be assigned to association identifiers not associated with a particular station, in particular reserved for stations not associated with the access point, may also be based on at least one allocation scheme characteristic of the uplink resource units.

[0050] Conversely, with respect to the AP, the method may further include receiving, at the access point, a frame from the station on one uplink resource unit of a plurality of uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the resource unit of the plurality of uplink resource units being allocated according to an allocation scheme, in which case downlink resource units assigned to association identifiers not associated with a particular station, in particular reserved for stations not associated with the access point, within the constructed plurality of downlink resource units may have at least one matching allocation scheme characteristic with the uplink resource units.

[0051] In some embodiments, determining the downlink resource units is based on a number of downlink resource units assigned to association identifiers reserved for stations not associated with the access point in a multi-user downlink transmission.

[0052] In one embodiment, if the number of downlink resource units is one, a single downlink resource unit assigned to an association identifier reserved for stations not associated with the access point is selected as the determined downlink resource unit for receiving the frame.

[0053] In one embodiment, if the number of downlink resource units is two or more, one downlink resource unit assigned to an association identifier reserved for a station not associated with the access point is selected as the determined downlink resource unit for receiving the frame, the selection being based on at least one allocation scheme characteristic of the uplink resource units used by the station to transmit the frame to the access point. The uplink resource unit can be one of a plurality of uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the plurality of uplink resource units being allocated according to an allocation scheme.

[0054] In some embodiments, preferably (but not limited to), when it is determined that the multi-user downlink transmission includes a single determined downlink resource unit assigned to an association identifier reserved for stations not associated with the access point, the station may further include checking whether the frame received in the determined downlink resource unit is addressed to the station before decoding the frame, which means that the station further includes checking whether the determined downlink resource unit includes a frame addressed to the station, in order to trigger reception and subsequent decoding of the frame if the check is positive. This approach is for discarding the frame if it is not addressed to the station.

[0055] In embodiments related to a station's association procedure with an AP, the station is not associated with the access point, and the frames in the uplink resource units are request management frames in the process of associating the station with the access point, while the frames in the downlink resource units are response management frames that respond to the request management frames. In this regard, the embodiments substantially improve the overall latency for the association procedure.

[0056] In some embodiments, the allocation scheme characteristic includes the location of the resource unit within the corresponding multiple resource units according to the allocation scheme. For example, if an uplink resource unit corresponds to an RU at location #3 in the RU allocation scheme (as indicated in the trigger frame that triggers the MU uplink transmission), the downlink resource unit for the downlink transmission may be the downlink resource unit at location #3 within the multiple downlink RUs. This may be independent of whether the two RUs share the same frequency range (or range of tones).

[0057] This feature or criterion is easily identified by the AP and stations with little or no temporary storage of information from the uplink RU to configure the downlink RU.

[0058] In a variant, the allocation scheme characteristic includes the frequency band of the resource units in the corresponding multiple resource units that are allocated in the frequency domain according to the allocation scheme. This can be independent of whether two RUs share the same position in the respective multiple RUs. For example, a downlink RU has exactly the same tone as an uplink RU in the considered 20 MHz channel. It can also be considered to make a downlink RU start or end at exactly the same tone as an uplink RU (even if their RU sizes are different).

[0059] This feature or criterion is easily identified by the AP and stations with little or no temporary storage of information from the uplink RU to configure the downlink RU.

[0060] In another variation, the allocation scheme characteristic includes a size of a resource unit in the corresponding plurality of resource units according to the allocation scheme. For example, if an uplink RU is 52 tones wide, a downlink RU can be identified as an RU (or RUs) that is also 52 tones wide. It can be noted that one or more other criteria can be used to identify the correct downlink RU from among several candidates (e.g., if several 52-tone wide RUs are defined in the multiple downlink RUs). An exemplary other criterion is a predefined AID assigned to the downlink RU, as will be introduced later.

[0061] Of course, the location criteria, frequency band criteria, and size criteria may all or some of them may be combined to determine or structure the downlink RUs relative to the uplink RUs.

[0062] In some embodiments, any station that registers or associates with an access point is associated with or assigned a unique association identifier that is used by the access point to allocate resource units to the station in transmission opportunities granted to the access point, and uplink and / or downlink resource units are assigned predefined association identifiers that are not associated with a particular station, and are specifically reserved for stations that are not associated with the access point. Although the predefined association identifiers are not dedicated to a particular station, in accordance with these embodiments, they allow a station (e.g., a station that is not yet associated) to quickly identify uplink RUs and verify allocation scheme characteristics for a small number of RUs to find suitable downlink RUs. This reduces processing at the station.

[0063] In a particular embodiment, the uplink resource units and the downlink resource units are assigned to the same predefined association identifier that is not associated with a particular station, specifically reserved for stations that are not associated with an access point, for the purpose of simplifying processing at both the AP and the station.

[0064] According to a particular feature, the association identifier not associated with a particular station is an 11-bit identifier equal to 2045. In a particular case, this association identifier is reserved for stations that are not associated with an access point.

[0065] In some embodiments, multiple uplink and downlink resource units belong to the same transmission opportunity granted to the access point, which reduces the latency of frame exchanges initiated between the AP and the station (e.g., associated with an association procedure).

[0066] In a particular embodiment, the downlink resource units in the multi-user downlink transmission immediately follow the uplink resource units included in the multi-user uplink transmission within the same transmission opportunity granted to the access point, meaning that no intermediate (downlink or uplink) resource units are used in between. However, this does not preclude the presence of acknowledgements. This approach optimizes latency.

[0067] In a variant, the uplink resource units included in the multi-user uplink transmission and the downlink resource units in the multi-user downlink transmission are separated by at least one third resource unit provided for a multi-user uplink or downlink transmission within the same transmission opportunity granted to the access point, thereby allowing an AP to schedule intermediate MU downlink or uplink transmissions within the same TXOP to improve station exchange.

[0068] In another variant, the multiple uplink and downlink resource units belong to different transmission opportunities granted to the access point, which can give the AP enough time to prepare a response to a not yet associated station that sent a request through a so-called "uplink RU" of a MU uplink transmission.

[0069] In some embodiments, each of the plurality of resource units is allocated in the frequency domain according to a respective allocation scheme, which is the case for RUs as defined in 802.11ax.

[0070] In some embodiments, the uplink resource units provided in the multi-user uplink transmission are triggered within the transmission opportunity by a trigger frame transmitted by the access point, which is particularly applicable in 802.11ax networks.

[0071] Additionally, the multi-user downlink communication protocol can be improved to support multiple receiving stations during the same downlink RU, including stations that have not yet received an AID (i.e., not yet registered with the AP or not yet associated with the AP).

[0072] This approach, hereinafter referred to as the aggregation-based approach, proposes an improved wireless communication method in a wireless network comprising access points and stations.

[0073] In an embodiment, the method includes, at one of the stations: determining resource units dedicated to a plurality of stations from among a plurality of resource units forming multi-user downlink transmission opportunities granted to the access point for downlink transmission to the stations; receiving an aggregated data frame via the determined resource unit; extracting from the received aggregated data frames one or more data frames addressed to the station; Includes.

[0074] From an AP perspective, an improved wireless communication method in a wireless network comprising access points and stations is also proposed.

[0075] In an embodiment, the method comprises, at the access point: aggregating data frames addressed to two or more stations; transmitting the aggregated data frames via a resource unit dedicated to a plurality of stations from among a plurality of resource units forming a multi-user downlink transmission opportunity granted to an access point for downlink communication to the stations; Includes.

[0076] Using these new RU-based transmission schemes, the present invention provides a communication mechanism that supports multiple receiving stations among the same downlink RU, including stations that have not yet received an AID (i.e., not yet registered with the AP or not yet associated with the AP).

[0077] Thus, MU downlink transmissions are significantly improved compared to the current requirements of known 802.11ax. Indeed, by combining data frames that are to be addressed to several stations in the same dedicated RU, embodiments of the present invention allow an AP to efficiently target a large number of stations, thereby using each RU more efficiently (thus reducing padding bits), avoiding duplicating the same payload across several RUs (in the case of multicast), and / or providing efficient (i.e., at a higher bit rate) response management frames to stations that are not yet associated.

[0078] Such a RU dedicated to multiple receiving stations is sometimes called a "group" RU (or "multicast" RU), as opposed to conventional "individual" RUs, each of which is assigned to a single station.

[0079] In practice, such group RUs can be used to carry various types of data frames, including broadcast frames (the same frame targeted to all stations), multicast frames (the same frame targeted to multiple stations), or multiple unicast frames (multiple frames, each targeted to a single station).

[0080] Also provided is a wireless communications device forming a station in a wireless network comprising access points and stations.

[0081] In an embodiment, the devices forming the station include determining resource units dedicated to a plurality of stations from among a plurality of resource units forming a multi-user downlink transmission opportunity granted to the access point for downlink transmission to the stations; receiving an aggregated data frame via the determined resource unit; extracting from the received aggregated data frames one or more data frames addressed to the station; The computer-implemented method includes:

[0082] Also provided is a wireless communications device forming an access point in a wireless network comprising access points and stations.

[0083] In an embodiment, the device forming the access point comprises: aggregating data frames addressed to two or more stations; and transmitting the aggregated data frame via one resource unit dedicated to the multiple stations from among a plurality of resource units forming a multi-user downlink transmission opportunity granted to the access point for downlink communication to the stations.

[0084] In this aggregation-based approach, the problem of frame acknowledgment for a group RU remains.

[0085] In practice, in the conventional 802.11ax acknowledgement mechanism, the acknowledgement of data frames received via the RU is done by the station to which the RU is assigned via the RU in the subsequent MU uplink OFDMA transmission as indicated in the UMRS field (received in the downlink RU). However, this mechanism cannot operate in the case of group RU, since no specific station is designated as the RU recipient. Moreover, even if one station is so designated, it should not be allowed to acknowledge data frames addressed to other stations in the group RU.

[0086] Intuitively, other solutions are possible, but they are not as efficient.

[0087] For example, a response frame (here, an acknowledgment) from a receiving station of a group RU can be triggered later by the AP. This can be performed by individual SU exchange between the AP and each receiving station. However, the SU exchange is not efficient in terms of bandwidth usage, and channel bandwidth is still wasted.

[0088] Alternatively, the AP can send a subsequent trigger frame to provide a RU for the receiving station to acknowledge the preceding MU downlink OFDMA transmission from the AP. However, by not having its own AID, the not yet associated station cannot be provided with a scheduled RU and may therefore rely only on random RUs, resulting in reduced efficiency due to contention. Thus, the not yet associated receiving station may not be in a position to efficiently acknowledge data frames received within the group RU (hereinafter downlink group RU or DL ​​group RU) of the MU downlink OFDMA transmission. As a result, the AP will retransmit unacknowledged data frames, and channel bandwidth will still be wasted.

[0089] To overcome such shortcomings, an improved method and device are proposed in the present invention, aiming to provide an efficient acknowledgement mechanism that can obtain better utilization of OFDMA MU transmissions by the AP.

[0090] In this regard, an improved wireless communication method of the above aggregation-based approach is proposed, which further comprises a step of signaling, at the access point, in two aggregated data frames addressed to two respective stations, respective response resource unit information identifying response resource units to be used by a recipient station in a multi-user uplink transmission opportunity subsequent to the multi-user downlink transmission opportunity to provide a response to the data frames to the access point.

[0091] Conversely, the improved aggregation-based method at the station is obtaining response resource unit information from the retrieved data frame, the response resource unit information identifying one response resource unit in a multi-user uplink transmission opportunity; transmitting a response to the retrieved data frame to the access point via the identified response resource unit; Further includes:

[0092] For example, the response resource unit information is signaled in an uplink multi-user response scheduling (UMRS) control subfield of a data frame as specified in the 802.11ax, version 2.0 standard (formally known as draft P802.11ax_D2.0, specifically clause 9.2.4.6.4.2 “UMRS Control”).

[0093] In contrast to the 802.11ax requirement that limits UMRS per RU to a single value, this improved method allows various receiving stations (via group RUs) to efficiently acknowledge receipt of a data frame.

[0094] Since the AP can schedule more RUs in a MU uplink OFDMA transmission than in a MU downlink OFDMA transmission, all receiving stations can have a chance to acknowledge their received data frames (even when DL group RUs are used). Retransmission of data frames by the AP is thus avoided, thus saving channel bandwidth.

[0095] Also, it is the receiving station as defined in the RA field (MAC address) of the frame MAC header that can use the response RU indicated in the UMRS information of the same MAC header. As a result, even a receiving station that is not yet associated with the AP can acknowledge the data frame. Thus, the association procedure for the station can be simplified (using a random RU with AID=2045, receiving a response from the AP during a MU downlink transmission, and acknowledging the response during a subsequent MU uplink transmission). In other words, a UMRS control field in each MPDU (MAC Protocol Data Unit) of the A-MPDU (Aggregate MPDU) can be used to indicate which UL RU must be used by the unassociated station to acknowledge the MPDU(s).

[0096] Also provided is a wireless communications device forming a station in a wireless network comprising access points and stations, the device forming the station comprising at least one microprocessor configured to execute, from the station's point of view, the steps defined above with respect to the improved aggregation-based method.

[0097] Also provided is a wireless communications device forming an access point in a wireless network comprising access points and stations, the device forming the access point comprising at least one microprocessor configured to execute, from the AP's point of view, the steps defined above with respect to the improved aggregation-based method.

[0098] Optional features of these improved aggregation-based embodiments are defined in the appended claims referring to the method. Naturally, the same features can be replaced by features of the system dedicated to any device according to the embodiments of the invention.

[0099] In some embodiments, the improved aggregation-based method further comprises receiving, at the access point, a response from the recipient station via a resource unit of the subsequent multi-user uplink transmission opportunity, the response from a recipient station, preferably any recipient station, being received via the response resource unit identified in the response resource unit information (UMRS) signaled in a data frame addressed to the recipient station within the transmitted aggregated data frame. Of course, similar response RU information can be used for stations addressed via individual RUs.

[0100] Preferably, the response from the receiving station includes an acknowledgement for the data frame of the transmitted aggregated data frame.

[0101] In some embodiments, the multi-user uplink transmission opportunity and the multi-user downlink transmission opportunity belong to the same transmission opportunity granted to the access point, thus saving time and channel bandwidth since only one contention is required for the AP to access the medium.

[0102] In another embodiment, the improved aggregation-based method further includes configuring a multi-user uplink transmission opportunity at the access point to include a number of response resource units based on the number of stations addressed in the multi-user downlink transmission opportunity, which enables the AP to provide an opportunity for frame acknowledgment to the desired addressed stations.

[0103] For example, the improved aggregation-based method further includes configuring the multi-user uplink transmission opportunity at the access point to include a number of response resource units that is at least (and preferably is equal to) the number of stations that must provide a response to a data frame addressed to a station via any resource unit of the multi-user downlink transmission opportunity, which allows all stations to provide an acknowledgement to the AP.

[0104] For example, stations that must provide a response include receiving stations for which respective response resource unit information is signaled in the aggregated data frame, In practice, stations that must provide a response may be stations that comply with UMRS signaling and / or stations for which UMRS information is provided in a group or individual RU of a MU downlink transmission.

[0105] Aggregating data frames includes aggregating data frames to be addressed to multiple stations such that the total number of stations addressed via the multiple resource units forming the multi-user downlink transmission opportunity does not exceed the determined maximum number of stations. This configuration limits the possibility of an AP involving too many stations per group RU, and therefore in the overall MU downlink transmission, such that not all stations may be able to acknowledge for a data frame. As a result, data frame acknowledgment is performed efficiently, reducing the risk that the AP must retransmit correctly received (but not yet acknowledged) data frames.

[0106] In particular, the determined maximum number of stations depends on (e.g., is equal to) the maximum number of elementary resource units that can be defined within a multi-user uplink transmission opportunity. The elementary resource unit can be considered, for example, as the minimum RU allowable by the 802.11ax standard, in which each 20 MHz channel can be divided into a maximum of 9 elementary RUs.

[0107] Optional features of the aggregation-based embodiment are also defined in the appended claims referring to the method. Naturally, the same features can be replaced by features of the system dedicated to any device according to an embodiment of the invention.

[0108] This aggregation-based approach can be combined with the first approach presented above, especially when using AIDs not associated with a station during MU downlink transmissions to provide an opportunity to an AP to address stations that are not given an AID, such as stations that are not associated with the AP. In such a combination, where a station determines resource units to be assigned to association identifiers that are not associated with a particular station, the method includes, at the station: receiving an aggregated data frame via the determined resource unit; extracting from the received aggregated data frames one or more data frames addressed to the station; It may further include.

[0109] Accordingly, at the access point, the method according to the first approach comprises: aggregating data frames that are to be addressed to two or more stations; transmitting the aggregated data frames over resource units assigned to association identifiers not associated with a particular station; The method may further include:

[0110] In an embodiment, any station that registers or associates with an access point is associated with or assigned a unique association identifier that is used by the access point to allocate resource units to the station in transmission opportunities granted to the access point, and resource units dedicated to multiple stations are assigned to a predefined association identifier that is not associated with a particular station in downlink transmission opportunities. This can be considered a "group AID" for a group of stations. Thus, all 802.11ax compliant stations may know such predefined AID or AIDs in order to probe associated RUs.

[0111] In some embodiments, the access point may set the MAC address field in each data frame to be aggregated to the MAC address of the receiving station, so that the receiving station can efficiently retrieve its own data frames. In effect, from the station's perspective, retrieving one or more data frames addressed to the station may therefore involve comparing the MAC address of each aggregated data frame to the station's MAC address.

[0112] To avoid too much processing at the access point, the station may not acknowledge receipt of the retrieved data frame to the access point, so that not all data frames in the downlink RU are acknowledged.

[0113] In one variant, a station may transmit an acknowledgement for a retrieved data frame only if it contains the last received aggregated data frame, which means that only the last data frame is explicitly acknowledged by its corresponding receiving station, and other data frames of the downlink RU for the group of stations are therefore implicitly acknowledged immediately after the acknowledgement for the last data frame has been correctly received.

[0114] As introduced above, one application example of this technique takes into account management frames for stations that are not yet associated (registered) in order to efficiently register with the access point. In this regard, the station may transmit a management frame to the access point within a procedure for associating the station with the access point (i.e., registering the station with the access point) before determining the resource unit. In such a case, determining the resource unit includes determining a resource unit to be assigned to the station that is not yet associated with the access point in order to retrieve a response from the access point to the transmitted management frame. In other words, a resource unit in a downlink OFDMA transmission is reserved for a station that is not yet associated, and from the RU, the station can obtain a response to its request management frame.

[0115] This approach avoids using SU signaling even for response management frames, thus saving network bandwidth.

[0116] From the AP's perspective, it can mean that the access point receives at least one management frame from a station that is willing to associate with the access point (i.e., register with the access point) prior to the step of transmitting the data frame, and the transmitted data frame includes a response to the received management frame and is transmitted via a resource unit allocated to a station that is not yet associated with the access point.

[0117] To provide an improved association procedure, the management frame is transmitted in a preceding resource unit that forms part of an uplink transmission opportunity granted to the access point for uplink communication from the station, the preceding resource unit being assigned to a station that is not yet associated with the access point. Thus, both the request and response management frames can be transmitted in a (high bit rate) MU OFDMA RU, thereby reducing medium occupancy.

[0118] In some embodiments, the determined resource unit and the preceding resource unit are assigned to the same predefined association identifier not associated with a particular station, e.g., AID=2045, or to an association identifier associated with a basic service set (provided by the AP), e.g., equal to the basic service set identifier of the basic service set, in the downlink and uplink transmission opportunities, respectively, which makes management easier at the stations and the access point.

[0119] To further improve the association procedure, the station may transmit an acknowledgement for the retrieved data frame in the next resource unit forming part of the next uplink transmission opportunity granted to the access point for uplink communication from the station, the next resource unit being allocated to the station not yet associated with the access point. This is an efficient way of providing a low-cost (i.e., without using SU signaling) opportunity for each not yet associated station willing to register to acknowledge receipt of the response management frame.

[0120] Another application of the present invention allows for the management of multicast traffic, or any residual traffic (ie, small amounts of data that, given the RU size, would require padding bits).

[0121] In the case of multicast traffic, the access point receives a multicast frame (e.g., from a higher OSI layer) that is to be addressed to multiple recipient stations. Then, in response to receiving the multicast frame, the access point generates multiple data frames that include the payload of the multicast frame, each of which is to be individually addressed to each of the recipient stations. Thus, an aggregated data frame that is to be transmitted over a resource unit dedicated to the multiple stations includes the generated data frames that include the payload of the multicast frame.

[0122] For example, a resource unit dedicated to multiple stations transmitting aggregated data frames, including the payload of a multicast frame, may be assigned to a predetermined association identifier, not associated with a particular station, equal to 2042 in a downlink transmission opportunity.

[0123] For remaining traffic, the access point can determine small data frames to be transmitted to a station given the size of the downlink transmission opportunity (possibly the size of an RU) and a size threshold. The determined small data frames are then aggregated and transmitted via resource units dedicated to multiple stations, called collecting resource units. For example, the collecting resource units are signaled in the downlink transmission opportunity with a predefined association identifier that is not associated with a particular station, which is equal to 0.

[0124] From the station's point of view, both multicast traffic and residual traffic can be treated in the same way. For example, the station can first scan the resource units assigned to the individual station to verify whether one of the resource units is assigned to the station individually, and if the verification is only negative, determine the resource unit dedicated to the multiple stations from the resource units that have not yet been scanned. In detail, determining the resource unit dedicated to the multiple stations from the resource units that have not yet been scanned can include first scanning the resource units assigned to the list of the station and verifying whether the station belongs to the list associated with one of the scanned resource units. The list can correspond to a particular AID, for example, used as a group AID, and each station can determine whether it belongs to such a group (e.g., through bit masking or by referring to the group AID given by the AP at registration).

[0125] Thus, if the verification is positive, the determined resource unit (to retrieve the data frame) is the resource unit assigned to the list containing the station.

[0126] Also, if the verification is only negative, the determined resource unit is the aggregated resource unit used to carry data frames for any station that is not assigned individually or through a list to another resource unit forming the downlink transmission opportunity.

[0127] These various techniques avoid duplicating the same data across several RUs and / or reduce the amount of padding data that would be added to the RUs, resulting in a more efficient use of the medium.

[0128] To ensure efficient processing by the station, an embodiment provides that a downlink transmission opportunity includes an ordered signaling of allocations of multiple resource units to one or more stations, where the ordered signaling first provides each allocation of resource units to an individual station, then provides each allocation of resource units to a group of stations, and then provides for the allocation of aggregate resource units to any station not yet associated with a resource unit. In practice, a station will therefore first determine the individual RU before considering whether a group RU was used (in case of a negative verification). Thus, only if no RU for the station has been identified, the station can probe a collector RU (dedicated to any station) and possibly retrieve any data addressed to it.

[0129] With this approach, once a station finds one RU (individually or a group) that is addressed to it, the station can advantageously ignore any further RU analysis in the same downlink transmission opportunity.

[0130] The embodiments of the present invention can be implemented in all 802.11ax compliant APs and non-AP stations. Alternatively, 802.11ax compliant APs and non-AP stations can optionally implement some features of the embodiments of the present invention.

[0131] In this regard, according to one embodiment, there is provided a method of wireless communication in a wireless network comprising an access point and a station, the method comprising: receiving capability information from one or more stations, the capability information including a capability of the station to allow a data frame addressed to the station to be aggregated with one or more data frames addressed to one or more other stations; aggregating data frames based on the received capability information; transmitting the aggregated data frames to one or more stations; Includes.

[0132] In a particular embodiment, the transmitting is performed via resource units dedicated to the multiple stations from among a plurality of resource units forming multi-user downlink transmission opportunities granted to the access point for downlink communication to the stations.

[0133] Preferably, the capability information is signaled in a management frame during an association procedure of one or more stations to the access point.

[0134] For example, the capability information is signaled in a subfield of the HE MAC capability information field as specified in the 802.11ax, version 2.1 standard.

[0135] In particular, if the station does not allow a data frame addressed to the station to be aggregated with one or more data frames addressed to one or more other stations, aggregating includes forming a data unit that includes one or more data frames addressed only to the station.

[0136] Conversely, there is provided a method of wireless communication in a wireless network including an access point and stations, the method comprising: transmitting capability information to the access point, the capability information including a capability of the station to allow a data frame addressed to the station to be aggregated by the access point with one or more data frames addressed to one or more other stations; receiving aggregated data frames from an access point; extracting data frames from the received aggregated data frames, the extracting being based on the transmitted capability information; Includes.

[0137] In one variant, the method further comprises the step of receiving capability information from the access point, the capability information comprising a capability of the access point to aggregate data frames addressed to two or more stations.

[0138] In particular, the extracting is further based on capability information received from the access point.

[0139] In a particular embodiment, the receiving is performed via resource units dedicated to the multiple stations from among a plurality of resource units forming multi-user downlink transmission opportunities granted to the access point for downlink communication to the stations.

[0140] In particular, the capability information is signaled in management frames during the association procedure of the station to the access point, for example, the capability information is signaled in a subfield of the HE MAC capability information field as defined in the 802.11ax, version 2.1 standard.

[0141] An embodiment also relates to a wireless communication device forming an access point in a wireless network comprising access points and stations, as well as a wireless communication device forming a station in the wireless network.

[0142] Another aspect of the invention relates to a non-transitory computer readable medium storing a program which, when executed by a microprocessor or computer system in a device, causes said device to perform any of the methods as defined above.

[0143] The non-transitory computer readable medium may have features and advantages similar to those set forth above and below with respect to the methods and devices described above.

[0144] At least some parts of the methods according to the invention may be computer-implemented. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software (including firmware, resident software, microcode, etc.) embodiment, or an embodiment combining software and hardware aspects, all of which may be collectively referred to herein as a "circuit," "module," or "system." Furthermore, the present invention may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied therein.

[0145] Since the present invention can be implemented in software, the present invention can be embodied as computer readable code provided to a programmable device on any suitable carrier medium. Tangible carrier medium can include storage media such as hard disk drives, magnetic tape devices or solid-state memory devices. Transient carrier medium can include signals such as electrical, electronic, optical, acoustic, magnetic or electromagnetic signals, e.g. microwave or RF signals.

[0146] Further advantages of the present invention will become apparent to those skilled in the art from a study of the drawings and detailed description, in which: Embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which: [Brief description of the drawings]

[0147] [Figure 1] FIG. 1 illustrates a typical wireless communication system in which embodiments of the present invention may be implemented. [Figure 2a] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2b] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2c]A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2d] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2e] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2f] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2g] A diagram presenting various formats of 802.11 frames according to the 802.11ax standard. [Figure 2h] FIG. 1 illustrates a UMRS control field as defined in 802.11ax. [Figure 2i] FIG. 1 illustrates a UMRS control field as defined in 802.11ax. [Figure 2j] FIG. 1 illustrates a UMRS control field as defined in 802.11ax. [Diagram 3] 4A-4C illustrate an example sequence of management frames that enable a not-yet-associated station to discover and register with a given access point. [Figure 4] FIG. 1 illustrates an 802.11ac channel allocation supporting channel bandwidths of 20 MHz, 40 MHz, 80 MHz, or 160 MHz, as known in the art. [Diagram 5] FIG. 1 illustrates an example of an 802.11ax uplink OFDMA transmission scheme in which an AP issues a trigger frame to reserve a transmission opportunity on an OFDMA sub-channel (resource unit) on an 80 MHz channel, as known in the art. [Figure 6] FIG. 1 illustrates the shortcomings of the current version of 802.11ax through an exemplary scenario of data transmission in a WLAN. [Figure 7] 1 is a schematic diagram of a communication device according to an embodiment of the present invention. [Figure 8] 1 is a schematic diagram of a wireless communication device according to an embodiment of the present invention. [Figure 9a] 7 illustrates the effect of an embodiment of the present invention on the exemplary situation of FIG. 6 above, in the process of a not-yet-associated station associating with an AP. [Figure 9b] FIG. 9b shows an alternative to FIG. 9a. [Figure 9c] FIG. 9B shows another alternative to FIGS. 9a and 9b. [Figure 9d] FIG. 2 illustrates a general embodiment in which multiple downlink resource units are allocated to multiple unassociated stations. [Figure 10a] FIG. 2 illustrates, by way of a flow chart, the main steps at an access point associated with access point triggered MU uplink transmissions embodying the teachings of the present invention. [Figure 10b] FIG. 1 illustrates, by means of a flow chart, the main steps at an access point associated with an access point triggered MU downlink transmission when implementing an embodiment of the present invention. [Figure 10c] FIG. 1 illustrates, by means of a flow chart, the main steps at an access point associated with an access point triggered MU downlink transmission when implementing an embodiment of the present invention. [Figure 11a] FIG. 2 illustrates, by means of a flow chart, the main steps in an unassociated station involved in an MU uplink transmission triggered by an access point. [Figure 11b] FIG. 2 illustrates, by means of a flow chart, the main steps in an unassociated station involved in an MU downlink transmission triggered by an access point according to an embodiment of the invention. [Figure 11c] FIG. 2 illustrates, by means of a flow chart, the main steps in an unassociated station involved in an MU downlink transmission triggered by an access point according to an embodiment of the invention. [Figure 12a]1 illustrates an embodiment of the present invention in which one MU downlink resource unit is used by an AP to transmit data to an unassociated station through two exemplary scenarios of data transmission in a WLAN; [Figure 12b] 1 illustrates an embodiment of the present invention in which one MU downlink resource unit is used by an AP to transmit data to an unassociated station through two exemplary scenarios of data transmission in a WLAN; [Figure 13a] FIG. 1 illustrates, by means of a flow chart, an embodiment of the invention implemented in a physical access point when preparing and executing a MU downlink transmission. [Figure 13b] FIG. 1 illustrates, by way of a flow chart, an embodiment of the present invention implemented in a non-AP station to handle RUs dedicated to a group of stations in a MU downlink transmission from an AP. [Figure 14] FIG. 7 illustrates the advantages of using group RUs with reference to the example situation of FIG. 6 above. [Figure 15] FIG. 1 illustrates the advantages of using a newly proposed scheme for acknowledgement of grouped multi-user downlink transmissions. [Figure 16a] FIG. 13B illustrates, by way of a flow chart, an improvement to the process of FIG. 13A (at the access point) for efficiently providing frame acknowledgment in the case of group RUs. [Figure 16b] FIG. 13B illustrates, by means of a flow chart, an improvement of the process of FIG. 13b (at a station) to perform efficient and immediate frame acknowledgment in the case of group RUs. [Figure 17] A diagram showing an example format of an HE capabilities element exchanged between a station and an AP. [Figure 18a] FIG. 2 illustrates, by means of a flow chart, the steps performed by an AP when exchanging data. [Figure 18b] FIG. 2 illustrates, by means of a flow chart, the steps performed by a station when exchanging data; [Figure 19] FIG. 13 illustrates an example RU configuration between MU downlink transmission and MU uplink transmission. [Figure 20] FIG. 2 illustrates, by means of a flow chart, an embodiment according to the invention that takes into account the MSAS capability subfield value signaled by the station. [Figure 21] FIG. 2 illustrates, by means of a flow chart, an embodiment according to the invention that takes into account the UMPS capability subfield value advertised by an unassociated station. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0148] The invention will now be described by way of specific, non-limiting, exemplary embodiments with reference to the figures.

[0149] 1 shows a communication system in which several communication nodes (or stations) 101-107 exchange data frames over a radio transmission channel 100 of a wireless local area network (WLAN) under the control of a central station or access point (AP) 110. The radio transmission channel 100 is defined by an operating frequency band composed of a single channel or several channels forming a composite channel.

[0150] 1 shows a single physical access point 110, the AP 110 may support multiple BSSs (also called a set of "virtual APs") and may be configured to manage one or more WLANs (or BSSs), i.e., one or more groups of stations. Each BSS must be uniquely identified by a particular Basic Service Set Identification, or BSSID.

[0151] To achieve this configuration, the physical AP 110 may implement two (or more) virtual APs to manage two (or more) WLANs, e.g., a virtual AP1 VAP-1 (not shown) having a MAC address MAC1 as a specific BSSID to manage a first WLAN (BSS) having “guest” as an SSID, and a virtual AP2 VAP-2 (not shown) having a MAC address MAC2 as a specific BSSID to manage a second WLAN (BSS) having “Employee” as an SSID.

[0152] Some stations may register or "associate" with VAP-1 and therefore participate in a first WLAN "guest", while other stations may simultaneously register with VAP-2 and therefore participate in a second WLAN "Employee".

[0153] The security for each WLAN can be different, ie WEP and WPA can be used.

[0154] AP devices that support multiple BSSIDs include two types of virtual APs. The first virtual AP is called the "transmitted AP" or "representative AP". The BSSID is called the transmitted BSSID. The BSSID plays the main role of transmitting multiple BSSID elements in beacon and probe response frames. For a given physical AP, only one virtual AP is designated as a transmitted AP.

[0155] The second type of virtual AP is called a "non-representative AP" or "non-transmitting AP". The BSSID is called a non-transmitting BSSID. Non-representative APs correspond to other virtual APs and do not broadcast beacon frames with multiple BSSID elements. However, they can broadcast beacon frames specific to their BSS, i.e., without multiple BSSID elements, to associate with legacy STAs (stations that do not implement IEEE 802.11v).

[0156] The same physical device can participate in two WLANs simultaneously only if it has two separate WLAN interfaces (e.g., Wi-Fi network cards), in which case the device is considered as two stations in the network, with each station registered on only one WLAN at a time.

[0157] In order for stations to become aware of available WLANs (or BSSs) and information defining those WLANs (e.g., corresponding SSID(s), corresponding specific BSSID(s), communication mode including Infrastructure or Ad-Hoc, protection security scheme used including Open, WEP, WPA-PSK or 802.1X, supported transmission rates used, operating channels, and optional any information elements), the AP transmits several control or management frames, including beacon frames and probe response frames, having substantially the same content.

[0158] A probe response frame is sent by an AP to a particular station in response to a probe request frame broadcast by the station. This is done in an active discovery procedure, in which the station continuously scans a 20 MHz channel in which it broadcasts probe request frames. In the active discovery procedure, the station must periodically reaffirm its effective presence by sending a new probe request frame.

[0159] Meanwhile, a passive discovery procedure has been implemented in which an AP spontaneously and periodically (eg, every 100 ms) broadcasts a beacon frame to announce the WLAN to stations.

[0160] Both beacon and probe response frames are used in any version of 802.11, which means that they are transmitted at the lowest bit rate using the non-HT (high throughput) PPDU (physical layer (PHY) protocol data unit) format as shown in Figure 2a.

[0161] This format is simple since it contains a preamble formed from three fields that can be understood by any station according to any version of 802.11, namely the L-STF (Legacy Short Training Field), the L-LTF (Legacy Long Training Field) and the L-SIG (Legacy Signal Field) fields, followed by the payload data, here a data field containing information defining the WLAN to be declared.

[0162] The repeated probe request / response or beacon frames preempt a non-negligible portion of the network bandwidth, which increases substantially with multiple WLANs that must share the same communication channel, and with multiple physical APs (possibly some implementing multiple BSSs) because multiple beacons (one for each active BSS) are broadcast as above.

[0163] As a result, stations have to process beacon frames more frequently, and channel occupancy due to management frames increases. It does not seem to be entirely reasonable to widen the beacon interval (to be longer than 100 ms) so that beacon frames for each BSS are transmitted less frequently, reducing station processing and channel occupancy. This is because the WLAN becomes less visible / detectable to stations, and some stations may not detect beacon frames for a given BSS when scanning, and therefore may conclude (through the SSID) that a particular BSS is not available. Also, stations may decide to actively send out probe request frames to find their own network, which will result in probe response frames being broadcast by each neighboring AP.

[0164] The discovery procedure (using beacon and probe response frames) may be an initial part of a more general association procedure in which a station registers or associates with an AP in order to join the corresponding WLAN.

[0165] 3 shows an example sequence of management frames that allows a not-yet-associated station to discover and register / associate with a given access point. The sequence includes three stages: WLAN discovery, authentication, and association, and upon completion, the station enters an authenticated and associated state with the AP. Note that the station may currently be associated with a first AP (i.e., belongs to a first WLAN) but may be willing to join a second WLAN.

[0166] 802.11 networks utilize several options for the first stage of the 802.11 probing or discovery process. For example, in an enterprise deployment, searching for a particular network may involve sending out probe request frames on multiple channels that specify the network name (SSID) and bit rate.

[0167] More generally, before associating with an AP, a station gathers information about the AP by scanning channels one by one, either through passive scanning (the passive discovery procedure introduced above) or active scanning (the active discovery procedure introduced above).

[0168] In passive scanning mode, a station scans each 20 MHz channel consecutively and waits to hear a beacon frame (announcing the SSID) on the scanned channel, regardless of whether the station has already previously connected to a particular SSID.

[0169] In active scanning mode, the station sends out a probe request frame 310 on each wireless 20 MHz channel. The probe request frame may contain the SSID of the particular WLAN that the station is searching for, or the probe request frame may not contain a particular SSID, meaning that the station is searching for "any" SSID in the station's vicinity.

[0170] In response to receiving a probe request frame, the AP checks whether the stations have at least one common supported data rate. If a matching data rate exists, the AP responds with a probe response frame 320, similar in content to a beacon frame, advertising the SSID (wireless network name), supported data rates, encryption type if required, and other 802.11 capabilities of the AP.

[0171] In response to receiving the probe response frame 320, an acknowledgement frame 330 may be transmitted by the station.

[0172] It is also common for a station already associated with an AP to periodically transmit probe request frames on other wireless channels to maintain an updated list of available WLANs with the best signal strength, which allows the station to roam to another AP with better signal strength using the second and third phases of the association procedure when it can no longer maintain a strong connection with the AP.

[0173] Once a WLAN to join has been selected by a station, the second stage is 802.11 authentication. In particular, the station selects compatible WLANs from the probe response frames it receives.

[0174] 802.11 was originally developed with two authentication mechanisms. The first authentication mechanism is called "Open Authentication" and is basically a NULL authentication, where the station asks "to authenticate itself" and the AP responds with "yes". This is the mechanism used in nearly all 802.11 deployments. The second authentication mechanism, i.e. WEP / WPA / WPA2, is a shared key mechanism and is widely used in home networks or small Wi-Fi deployments to provide security.

[0175] During the 802.11 authentication phase, the station sends a lower-level 802.11 authentication request frame 340 to the selected AP, for example setting authentication to open and setting sequence to 0x0001. The AP receives the authentication request frame 340 and responds to the station with an authentication response frame 350 that is set to open and indicates a sequence of 0x0002.

[0176] Note that some 802.11 capabilities allow a station to perform low-level authentication to multiple APs without being associated with the AP (i.e., without belonging to the corresponding WLAN). This speeds up the overall association procedure as the station moves between APs. In practice, a station can be 802.11 authenticated to multiple APs, but can be actively associated with, and transfer data through, only one AP at a time.

[0177] Next, the station must perform an actual association with the AP from the low-level authentication step. This is the next stage of the actual 802.11 association, whereby the station actually joins the WLAN cell. This stage finalizes security and bit rate options and establishes a data link between the station and the AP. The purpose of this final exchange is for the station to obtain an Association Identifier (AID) that will be used to access the medium and transmit data within the joined WLAN.

[0178] Note that a station may be joining a first network and may roam from one AP to another within the physical network, in which case the association is called a re-association.

[0179] Once the station has determined which AP (i.e., WLAN) it wishes to associate with, it transmits an association request frame 360 ​​to the selected AP. The association request frame includes the selected encryption type, if requested, and other compatible 802.11 capabilities.

[0180] If the elements in the association request frame match the capabilities of the AP, the AP generates an association ID (AID) for the station and responds with an association response frame 370 with a success message granting the station network access.

[0181] The station has now successfully associated with the AP and can start data transfer in the selected WLAN using the physical medium.

[0182] Note that when an AP receives a data frame from an authenticated but not yet associated station, the AP responds with a disassociation frame that places the station in an authenticated but not yet associated state. As a result, the station must reassociate with the AP in order to join the corresponding WLAN.

[0183] Probe response frame 320, authentication request / response frames 340 and 350, and association request / response frames 360 and 370 are unicast management frames sent in the 802.11 legacy format known as the Single User (SU) format, which is the format used for point-to-point (here, between an AP and a station) communications. Each of these unicast management frames is acknowledged by an ACK frame 330.

[0184] As indicated above, all management frames (310, 320, 340, 350, 360, 370) and ACK frames (330) use the lowest common rate (eg, 24 mbps or less) supported by both stations and APs.

[0185] To meet the ever-increasing demand for faster wireless networks and to support bandwidth-intensive applications, 802.11ac and later versions (e.g., 802.11ax) implement wider bandwidth transmissions through multi-channel operation. Figure 4 shows an 802.11ac channel allocation that supports composite channel bandwidths of 20 MHz, 40 MHz, 80 MHz, or 160 MHz.

[0186] IEEE 802.11ac introduced support for a limited number of predefined subsets of 20 MHz channels that form a unique predefined composite channel configuration that is available for reservation by any 802.11ac (or later) station on the wireless network transmitting data.

[0187] These predefined subsets are shown in the figure and correspond to channel bandwidths of 20 MHz, 40 MHz, 80 MHz, and 160 MHz, as compared to only 20 MHz and 40 MHz supported by 802.11n. In effect, the 20 MHz component channels 400-1 through 400-8 are concatenated to form a wider composite communication channel.

[0188] In the 802.11ac standard, the channels of each predefined 40 MHz, 80 MHz or 160 MHz subset are contiguous within the operating frequency band, i.e., no holes (missing channels) are allowed in the ordered composite channels within the operating frequency band.

[0189] A 160 MHz channel bandwidth consists of two 80 MHz channels that may or may not be contiguous in frequency. An 80 MHz channel and a 40 MHz channel consist of two adjacent or contiguous 40 MHz and 20 MHz channels, respectively. However, the present invention may have embodiments with any composition of channel bandwidth, i.e., a composition that includes only contiguous channels within the operating band or a composition formed of non-contiguous channels.

[0190] Stations (including APs) are granted transmission opportunities (TxOPs) through an Enhanced Distributed Channel Access (EDCA) mechanism on the "primary channel" (400-3). Indeed, for each composite channel with a certain bandwidth, 802.11ac designates one channel as "primary", meaning that it is used to compete for access to the composite channel. The primary 20 MHz channel is common to all stations (STAs) that belong to the same BSS, i.e., all stations that are managed by or registered to the same local access point (AP).

[0191] Meanwhile, in order to ensure that other legacy stations (i.e., stations not belonging to the same set) do not use the secondary channel, it is provided that the control frames reserving the composite channel (e.g., RTS / CTS frames or trigger frames described later) are duplicated over each 20 MHz channel of such composite channel.

[0192] Transmissions in such a composite channel are made from one station to another (including the AP) using HE Single-User (SU) PPDUs, the format of which is shown in Figure 2b, which includes the following fields: RL-SIG, HE-SIG-A, HE-STF, HE-LTF, data and PE, in addition to the traditional preamble (L-STF, L-LTF, L-SIG) that is readable by any legacy station.

[0193] The IEEE 802.11ac standard allows bonding up to four or even eight 20 MHz channels. Due to the limited number of channels (19 in the 5 GHz band in Europe), channel saturation becomes an issue. In fact, in densely populated areas, the 5 GHz band tends to become saturated even with 20 MHz or 40 MHz bandwidth per wireless LAN cell.

[0194] Developments in the 802.11ax standard aim to improve the efficiency and utilization of wireless channels in dense environments.

[0195] In this respect, one can consider a multi-user (MU) transmission mechanism that allows multiple simultaneous transmissions to different users in both the downlink (DL) and uplink (UL) directions when transmission opportunities are reserved and granted by the AP. In the uplink, multi-user transmission can be used to reduce the collision probability by allowing multiple non-AP stations to transmit simultaneously to the AP.

[0196] To practically implement such multi-user transmissions, it has been proposed to divide the licensed 20 MHz channel (400-1 to 400-4) into at least one sub-channel, and preferably multiple sub-channels 310 (basic sub-channels), also called subcarriers or resource units (RUs) or "traffic channels", shared by multiple users in the frequency domain, e.g. based on Orthogonal Frequency Division Multiple Access (OFDMA) techniques.

[0197] This is illustrated with reference to FIG.

[0198] To increase contention within the reserved transmission opportunity TXOP, the multi-user mechanism of OFDMA allows the AP to assign different RUs to different stations, which can help reduce contention and collisions within 802.11 networks.

[0199] In this example, each 20 MHz channel (400-1, 400-2, 400-3, or 400-4) is subdivided in the frequency domain into four OFDMA subchannels or RUs 510 of size 5 MHz. Of course, the number of RUs into which a 20 MHz channel is divided may be different from four, and the RUs may have different sizes. For example, there may be between 2 and 9 RUs (thus having a size of 10 MHz to about 2 MHz each). It is also possible to have an RU width wider than 20 MHz when included within a wider composite channel (e.g., 80 MHz).

[0200] Considering MU downlink (AP to station) transmission, the AP can transmit multiple data in multiple RUs directly to multiple stations by simply providing a specific instruction in the preamble header of the PPDU transmitted during the TXOP and then transmitting the data in the data field. The RUs used in the downlink direction are known as downlink RUs, while the RUs used in the uplink direction are known as uplink RUs.

[0201] FIG. 2c shows a HE MU (Multi-User) PPDU format (HE-MU) used in 802.11ax for transmission to one or more stations, in particular for MU downlink transmission from an AP to multiple stations.

[0202] The HE-MU PPDU contains the same preamble as the non-HT PPDU (Figure 2a), and the preamble is always transmitted at a low bit rate so that all devices, especially legacy devices that do not implement 802.11ac / ax, can understand the preamble for any of the transmission modes.

[0203] Since multiple stations are intended recipients or receivers of an OFDMA downlink transmission, the AP needs to inform the stations in which resource units they will find their data. To accomplish such signaling, 802.11ax provides an HE-SIG-B field 200, as shown, in which stations are assigned RUs.

[0204] The SIG-B field 200 is only found in the downlink HE-MU-PPDU and includes two types of fields: a single common block field 220 and one or more user-specific fields 230, as shown in FIG. 2e.

[0205] A single common block field 220 specifies the RU allocation for the current transmission opportunity through the RU allocation field (the other fields are of minor importance). The format follows substantially the same format as the downlink RU allocation given in the trigger frame as introduced later.

[0206] 802.11ax specifies a set of predefined RU allocation schemes for 20 MHz channels, as shown in Figure 2f. Thus, the RU allocation fields of the common block field 220 reference N 8-bit indices that point to entries in the table of Figure 2f.

[0207] Each such entry defines an RU allocation scheme, i.e., how the 20 MHz channel is divided into consecutive downlink RUs. Specifically, the entry gives the position (in ascending frequency order), size in terms of tones, and frequency range of each RU within the MU transmission.

[0208] For example, the first entry (index=00000000) specifies nine 26-tone wide downlink RUs at positions #1 through #9. Thus, the frequency band of the downlink RU at position #i is the [26th] 26th 26-tone wide downlink RU of the 20 MHz channel under consideration. * (i-1)+1] tone to (26* i) Tones spanned: If the AP wishes to define multiple downlink RUs with this particular allocation, then the RU Allocation field in the common block field 220 is set to the value 00000000.

[0209] The 12th entry (index=00001011) of the table of a predetermined RU allocation scheme, for example, specifies a first 52-tone wide downlink RU (position #1), followed by second, third and fourth downlink RUs (positions #2, #3 and #4) having a width of 26 tones, followed by fifth and sixth downlink RUs (positions #5 and #6) having a width of 52 tones.

[0210] The user-specific fields 230 define information related to each downlink RU defined in the common block field and are provided in the same order as the downlink RUs are consecutively defined in the common block field. For example, the nth declared user-specific field 230 provides information about the nth downlink RU as defined in the common block field, i.e., the downlink RU at position #n.

[0211] Each user-specific field 230 contains the AID of the receiving station (the "STA-ID" field, given by the AP during the association procedure in FIG. 3) and also contains other information that is less important here, such as modulation and coding scheme, spatial streams, etc.

[0212] When a given station can be allocated only a single downlink RU, the signaling that enables the station to decode its data is carried in only one user-specific field (corresponding to the single RU).

[0213] Based on the resource allocation given in the common block field and the corresponding user-specific fields, a station can easily know which resource units have been allocated to it, and therefore in which downlink RU it will receive its data from the AP.

[0214] The HE-SIG-B is encoded every 20 MHz using BCC and transmitted on the station's preferred band so that the station's signaling information is transmitted on the same band as the payload.

[0215] For MU uplink transmissions, the situation is different, since the AP must control when and how (in which RU) the station must send data.

[0216] In contrast to MU downlink transmissions, a triggering mechanism is employed for the AP to trigger MU uplink communications from various non-AP stations since the AP exercises such control over the stations.

[0217] To support MU uplink transmissions (during TXOPs pre-acquired by the AP), the 802.11ax AP must provide signaling information for legacy stations (i.e., non-802.11ax stations) to set their NAVs and for 802.11ax stations to determine resource unit allocations.

[0218] In the following description, the term legacy refers to a non-802.11ax station, which means a prior art 802.11 station that does not support OFDMA communication.

[0219] As shown in the example of Figure 5, the AP transmits a trigger frame (TF) 530 to the target 802.11ax station to reserve a transmission opportunity. The bandwidth or width of the target composite channel for the transmission opportunity is signaled in the TF frame, which means a value of 20 MHz, 40 MHz, 80 MHz or 160 MHz is signaled.

[0220] The TF frame is a control frame conforming to the 802.11 legacy non-HT format shown in Figure 2a, transmitted over the primary 20 MHz channel and duplicated (repeated) on each of the other 20 MHz channels forming the intended composite channel. Due to the duplication of the control frame, all nearby legacy stations (non-HT or 802.11ac stations) receiving the TF on their primary channel are expected to then set their NAV to the value specified in the header of the TF frame. This prevents these legacy stations from accessing the channel of the intended composite channel during a TXOP.

[0221] Based on the AP's decision, the trigger frame TF can define multiple uplink resource units (RUs) 510. The multi-user mechanism of OFDMA allows the AP to assign different RUs to different stations to increase contention, which can help reduce contention and collisions in 802.11 networks.

[0222] Information about RU allocation in requested transmission opportunities and about the assignment of stations to uplink RUs is indicated in the payload of the MAC frame carried in the data field (shown in FIG. 2a). In practice, the MAC payload is basically empty for conventional control frames (such as RTS or CTS frames), but is improved to have information structure for trigger frames. The RU allocation field specifies the allocated uplink RUs (i.e., the RU allocation in the TXOP), while one or more user information fields indicate information related to the respective uplink RUs (in the same order as given by the RU allocation information field). In particular, the address field in each user information field gives the AID of the station to which the corresponding uplink RU is assigned.

[0223] These various fields are similar to the fields (common block and user specific) defined above with reference to Figures 2e and 2f.

[0224] The trigger frame 530 may define "scheduled" uplink RUs, which may be reserved by the AP for certain stations, in which case these stations do not need to contend to access such RUs. Such scheduled RUs and corresponding scheduled stations are indicated in the trigger frame (the address field of the user information field for the scheduled RU is set to the AID of the station). This indicates which stations are allowed to use each scheduled RU. Such a transmission mode competes with conventional EDCA mechanisms within the stations to access the medium.

[0225] If a station finds that there is no user information field for a scheduled RU in the trigger frame 530 that carries its AID in the address field, then the station should not be allowed to transmit in the scheduled RU of a TF-triggered TXOP.

[0226] The trigger frame TF 530 may also specify "random" uplink RUs (also called "random access" (RA) RUs) in addition to or instead of "scheduled" RUs. Random RUs may be accessed randomly by stations. In other words, random RUs specified or allocated by the AP in the TF may serve as a basis for contention between stations willing to access the communication medium to transmit data. A collision occurs when two or more stations attempt to transmit simultaneously via the same random RU.

[0227] Such random RUs are signaled in the TF by using a unique reserved AID in the address field of the user information field corresponding to the RU. For example, an AID equal to 0 is used to identify a random RU available for contention by stations associated (i.e., belonging to the same BSS) with the AP sending the trigger frame. On the other hand, an AID equal to 2045 can be used to identify a random uplink RU available for contention by stations that are not yet associated, or "associated" stations (i.e., stations that do not belong to the same BSS as the AP sending the TF 530).

[0228] Note that the same TF may provide several random RUs with AID=0 and / or AID=2045.

[0229] For random RU contention by 802.11ax non-AP stations, i.e., to allow multiple 802.11ax non-AP stations performing contention among themselves to access random RUs and transmit data via random RUs, a random allocation procedure for the 802.11ax standard can be considered based on an additional backoff counter (OFDMA backoff counter, or OBO counter or RU counter). The RU backoff counter is different from the traditional EDCA backoff counter (specified in the 802.11e version). However, data transmitted in the accessed OFDMA RU 510 is assumed to be sourced from the same EDCA traffic queue.

[0230] The RU random allocation procedure includes a first step of determining, for one of the multiple 802.11ax stations with a positive RU backoff value (first drawn within the RU contention window range), from the received trigger frame, a subchannel or RU of the communication medium available for contention (so-called "random RU", identified by value 0 for an already associated station or value 2045 for an unassociated station), a second step of verifying whether the value of the local RU backoff value for the station under consideration is less than or equal to the number of random RUs detected as available, and then, in case of successful verification, a third step of randomly selecting one RU among the RUs detected as available and then transmitting data. If the second step is not verified, a fourth step (instead of the third step) is performed to decrement the RU backoff counter by the number of random RUs detected as available.

[0231] As can be noted, a station without scheduled RUs is not guaranteed to perform OFDMA transmission via random RUs for every received TF, since at least the RU backoff counter is decremented by the number of proposed random RUs every time a trigger frame is received, thereby postponing data transmission to a subsequent trigger frame (which depends on the current value of the number of RU backoffs and also on the number of random RUs provided by each received TF).

[0232] Returning to Figure 5, from various possible accesses to the uplink RUs, some of those uplink RUs went unused (510u) because none of the stations with RU backoff values ​​less than the number of available random RUs randomly selected one of those random RUs, whereas some other uplink RUs collided (510c, for example) because at least two of those stations randomly selected the same random RU. This shows that due to randomly determining which random RU to access, collisions may occur over some uplink RUs, while other RUs may remain free.

[0233] Uplink transmission of data by a station in RU 510 is performed in each uplink RU accessed by the station using an HE trigger-based PPDU (HE_Trig) as shown in Fig. 2d. Each HE_Trig PPDU carries a transmission only once (i.e., from one station to the AP) in response to a trigger frame 530. This HE_Trig PPDU frame format has a format very similar to that of the HE SU PPDU, except that the duration of the HE-STF field is 8 μS.

[0234] When a station uses scheduled and / or random RUs to transmit data to the AP, the AP responds with a multi-user acknowledgment (not shown in FIG. 5) to acknowledge the data received in each uplink RU.

[0235] FIG. 2g shows a typical format of a MAC frame 230 that may be carried in the data fields of the different PPDUs as shown in FIGS. 2a to 2d, i.e. in the downlink direction by an AP or in the uplink direction by a station.

[0236] The illustrated MAC frame includes a 24 octet MAC header, a frame body 207 of 0-2312 octets, and a 4 octet Frame Check Sequence (FCS) 208. The MAC header includes, among other fields, a frame control field 201, a duration field 202, a RA (receiver or destination address) field 203, and a TA (transmitter or source address) field 204.

[0237] For example, in the downlink direction, the RA field 203 is set to the MAC address of the station to which it is destined (a unicast MAC address) or to the broadcast value FF:FF:FF:FF:FF:FF (broadcast MAC address) if the MAC frame is to be destined for all stations. The frame body is a variable length field, for example, the information can be a frame exchanged during the association process (e.g., as described below with reference to FIG. 6). For example, the MAC frame body 207 can encapsulate a management frame sent by the AP during the association procedure (described above with reference to FIG. 3). In this case, the control field 201 indicates that the MAC frame is a management frame.

[0238] In this disclosure, MAC Frame and MAC Protocol Data Unit (MPDU) are synonymous terms and define a unit of data exchanged between MAC entities. An Aggregate MAC PDU (A-MPDU) is a structure that contains one or more MPDUs and is transported in a PHY Protocol Data Unit (PPDU). An A-MPDU may be carried, for example, in an HE SU PPDU, an HE MU PPDU, or an HE Trigger-based PPDU.

[0239] FIG. 6 illustrates the shortcomings of the current version of 802.11ax through an exemplary scenario of data transmission in a WLAN.

[0240] In this exemplary situation, the wireless network comprises a physical access point 110, a number of associated stations STA2, STA3, STA4, STA5, STA7 and STA8, and a number of unassociated 802.11ax stations STA1 and STA6.

[0241] The AP 110 periodically sends out a beacon frame 610 that contains parameters for the WLAN / BSS group(s).

[0242] All stations (including the AP) contend for access to the wireless network using the conventional EDCA scheme. The contention process (backoff counter) in each station is started or restarted whenever the wireless network is detected as idle for a predefined period of time (usually a DIFS period after the end of a preceding TXOP, e.g., after an acknowledgment from the AP, or after the end of a PPDU transmission).

[0243] When accessing the medium, the AP 110 transmits a trigger frame 530 reserving a MU UL transmission opportunity (TXOP#1) on at least one communication channel of the wireless network. The trigger frame 530 specifies resource units for MU uplink OFDMA transmission in TXOP#1, including one or more random RUs associated with AID=2045 (i.e., dedicated or reserved or assigned to unassociated stations such as STA1 and STA6). This is to expedite the association procedure of not yet associated stations while reducing medium access and occupancy. In this example, two random RUs with AID=2045 are provided, and the other RUs are scheduled RUs and / or random RUs with AID=0 (i.e., dedicated or reserved or assigned to already associated stations such as STA2, STA3, STA4, STA5, STA7, and STA8).

[0244] In response to the TF 530, the AP receives data on the uplink RU 510 from one or more stations during the MU uplink OFDMA transmission time, including data transmitted via scheduled RUs as well as data transmitted via random RUs.

[0245] In particular, the AP may receive request management frames (e.g., 310, 340, 360) from not-yet-associated 802.11ax stations, such as STA1 and STA6, via a random RU with AID=2045.

[0246] Upon receiving the data and management frames via the uplink RU 510 forming the MU uplink OFDMA transmission, the AP 110 responds with a Multi-STA BlockAck frame 640 using an HE SU PPDU (with the "Receiver Address" RA field of the encapsulated MAC frame set to the broadcast address). Note that in the Multi-STA BlockAck frame, the AP acknowledges receipt to each transmitting station by giving the AIDs of the transmitting stations whose data was correctly received. Since there is no AID associated with each not yet associated station, the Multi-STA BlockAck frame is modified to receive the MAC addresses of each not yet associated station whose requested management frame was correctly received.

[0247] Following TXOP#1, the AP 110 may again access the medium over a new TXOP, referred to as TXOP#2, to perform a MU downlink OFDMA transmission 620.

[0248] This exemplary scenario gives rise to several problems that are solved by several embodiments described below.

[0249] 7 shows a schematic diagram of a communication device 700, either a non-AP station 101-107 or an access point 110 of a wireless network 100 configured to implement at least one embodiment of the present invention. The communication device 700 may preferably be a device such as a microcomputer, a workstation or a lightweight portable device. The communication device 700 comprises a communication bus 713, to which are preferably connected the following: · a central processing unit 711, denoted by a CPU such as a microprocessor; · a read-only memory 707, denoted ROM, which stores a computer program implementing the invention; a random access memory 712, denoted RAM, storing the executable code of the method according to an embodiment of the invention and registers adapted to record variables and parameters necessary for implementing the method according to an embodiment of the invention; and At least one communication interface 702 connected to a wireless communication network 100, for example a wireless communication network according to the 802.11ax protocol, through which digital data packets or digital data frames or control frames are transmitted. Frames are written from a FIFO transmit memory in RAM 712 to the transmit network interface, or read from the receive network interface and written into a FIFO receive memory in RAM 712, under the control of a software application running in CPU 711.

[0250] Optionally, the communications device 700 may also include the following components: · data storage means 704, such as a hard disk, storing a computer program for implementing the method according to one or more embodiments of the present invention; a disk drive 705 for a disk 706 adapted to read data from or write data onto the disk 706; A screen 709 that displays the decoded data and / or acts as a graphical interface for the user via a keyboard 710 or any other pointing means.

[0251] Communications device 700 may optionally be connected to various peripheral devices, such as, for example, a digital camera 708. Each peripheral device is connected to an input / output card (not shown) to provide data to communications device 700.

[0252] Preferably, a communications bus provides communication and interoperability between the various elements included in or connected to communications device 700. The term bus is not limiting, and in particular a central processing unit is operable to communicate instructions to any element of communications device 700 directly or by way of another element of communications device 700.

[0253] The disk 706 may optionally be replaced by any information medium, such as, for example, a rewritable or non-rewritable compact disk (CD-ROM), a ZIP disk, a USB key or a memory card, and generally by an information storage means that can be read by a microcomputer or microprocessor, that may or may not be integrated in the device, possibly removable, and that is adapted to store one or more programs that, when executed, make it possible to carry out the method according to the invention.

[0254] The executable code may optionally be stored either in a read-only memory 707, in the hard disk 704 or in a removable digital medium, such as for example the disk 706 as previously described. According to an optional variant, the executable code of the program may be received via the interface 702 by means of the communications network 703, for storage in one of the storage means of the communications device 700, such as the hard disk 704, before being executed.

[0255] The central processing unit 711 is preferably adapted to control and direct the execution of instructions or parts of the software code of the program or programs according to the invention, which instructions are stored in one of the aforementioned storage means. Upon power-up, the program or programs stored in a non-volatile memory, for example the hard disk 704 or the read-only memory 707, are transferred into the random access memory 712, which then contains the executable code of the program or programs and registers for storing variables and parameters necessary to implement the invention.

[0256] In a preferred embodiment, the apparatus is a programmable apparatus that implements the invention using software, although the invention may alternatively be implemented in hardware (e.g. in the form of an application specific integrated circuit or ASIC).

[0257] 8 is a block diagram that illustrates a schematic architecture of a communication device 700, either an AP 110 or one of the stations 101-107, adapted to at least partially carry out the present invention. As shown, the device 700 comprises a physical (PHY) layer block 803, a MAC layer block 802, and an application layer block 801.

[0258] The PHY layer block 803 (here the 802.11 standardized PHY layer) has the task of formatting the frames, modulating them onto or demodulating them from any 20 MHz or composite channel, and transmitting and receiving the frames over the used wireless medium 100. By way of example, the frames are 802.11 frames, such as medium access trigger frames TF 530 (FIG. 5) reserving transmission slots, MAC data management frames based on 20 MHz width interacting with legacy 802.11 stations, and MAC data management frames of OFDMA type having a width smaller than 20 MHz legacy (usually 2 MHz or 5 MHz) between the wireless medium, etc.

[0259] The MAC layer block or controller 802 preferably comprises a MAC 802.11 layer 804 which performs conventional 802.11ax MAC operations. The MAC layer block 802 may optionally be implemented in software which is loaded into RAM 712 and executed by CPU 711.

[0260] The device 700 further comprises an additional block 805 that implements some of the embodiments of the present invention (either from the station's perspective or from the AP's perspective). The additional block 805 may be implemented in the MAC layer block 802 and / or the physical layer block 803 and may therefore interact with both blocks. In one embodiment, the additional block 805 receives a formed MAC frame for encapsulation within a MU DL frame.

[0261] To properly handle communications over OFDMA, in accordance with an embodiment of the present invention, the MAC 802.11 layer 804, the additional block 805 and the PHY layer block 803 interact with each other.

[0262] At the top of the diagram, an application layer block 801 executes applications that generate and receive data packets, e.g. data packets of a video stream. The application layer block 801 represents all stack layers above the MAC layer according to ISO standardization.

[0263] Returning to some of the issues arising from the scenario of Figure 6, the RUs provided for MU downlink OFDMA transmission are assigned to specific stations using AIDs. In the illustrated example, the RUs are assigned consecutively to STA3, STA5, STA4, STA2, STA8, and STA7.

[0264] For some stations, here STA3 and ST8, the amount of data to transmit is small relative to the size of the reserved RU. As a result, padding data (black portion) is added by the AP 110 to maintain sufficient activity on the 20MHz channel (so that legacy nodes can detect to avoid unexpected access). The black portion of the illustrated RU shows how padding wastes network bandwidth.

[0265] AP 110 may also be receiving multicast MAC frames from another network or higher OSI layers that are addressed to multiple recipient stations, here STA4 and STA5.

[0266] Multicast addressing can be used within the link layer, such as Ethernet multicast, and can be used at the Internet layer (as an example, the IP protocol includes addresses from 224.0.0.0 to 239.255.255.255 as a multicast range).

[0267] Since 802.11ax does not provide any mechanism to enable multicast traffic in MU downlink OFDMA transmissions, the AP must duplicate the MAC frame into two HE-MU PPDUs, which will be transmitted over two separate RUs, as shown, for the RUs assigned to STA5 and STA4. This also wastes bandwidth, especially since it is costly to signal two separate RUs.

[0268] Acknowledgement of data frames transmitted during an MU downlink OFDMA transmission may be performed by receiving stations STA2-5 and STA7 and 8 during an MU ACK period 625 belonging to the same TXOP#2. An MU ACK period 625 is, for example, a subsequent MU uplink OFDMA transmission immediately following an MU downlink OFDMA transmission.

[0269] In that case, the MU ACK Period 625 is formed from multiple scheduled RUs (hereinafter referred to as "response" or "acknowledgement" or "ack" RUs), which are defined in a dedicated MAC header portion of the frame carried in the preceding MU downlink OFDMA transmission.

[0270] The response RU to be used by each of the receiving stations STA2-5 and STA7 and 8 in the MU ACK period 625 for frame acknowledgment is identified in the response resource unit information provided by the AP in the transmitted data frame of the MU downlink OFDMA transmission. With this identification, the response RU is (indirectly) assigned to the station. The response RU is therefore the scheduled RU. In general, the response RU is the same as the RU used during the MU downlink OFDMA transmission (i.e., in the same RU location).

[0271] The response resource unit information is signaled in a so-called uplink multi-user response scheduling (or UMRS) control subfield in one (or more) of the data frames addressed to the receiving station.

[0272] The UMRS subfield is defined in the 802.11ax, version 2.0 standard, as described herein with reference to Figures 2h-2j.

[0273] Figure 2h shows the MAC header of a MAC frame in an HE multi-user PPDU carried over a MU DL transmission 620. The MAC frame (and therefore the MAC header) is carried in the data field of the HE MU PPDU (see Figure 2c).

[0274] As is known, the MAC header includes a field "Address_1" 210 that contains the receiving address (RA) of the MAC frame, i.e. the MAC address of the receiving station to which the MPDU is addressed. In a particular case, the MAC address can be a broadcast address (e.g. FF:FF:FF:FF:FF:FF). This MAC header also includes a HT control field 250. The HT control field can have several configurations depending on the 802.11 standard considered: A variant HE configuration corresponds to the 802.11ax standard, in which case the variant HE HT control field includes the A-Control subfield 260 (representing the Aggregate Control field) shown in FIG. 2i.

[0275] The A-Control subfield 260 aggregates several control fields, which are a series of one or more control subfields 261. The length of the A-Control subfield 260 is equal to 30 bits. Each control subfield 261 consists of a Control ID 262 subfield, which indicates the type of information carried in the following Control Information subfield 263. If necessary, padding bits are added to make the total A-Control subfield 30 bits.

[0276] Thus, various types of information can be provided through the A-Control subfield 260. For example, when the Control ID 262 is 1, an operating mode can be indicated in the Control Information subfield 263. Also, when the Control ID 262 is 4, power data can be indicated in the Control Information subfield 263.

[0277] When control ID 262 is 0, control information subfield 263 is UL MU Response Scheduling (UMRS) information or control subfield 264. One representation of UMRS information 264 is shown in Figure 2j, which contains various subfields across 26 bits.

[0278] One of those subfields is the 8-bit RU Allocation subfield 265. The subfield indicates which response RU of the MU Ack 625 should be used by the receiving station receiving the corresponding HE multi-user MPDU to provide a response to the data frame (an HE trigger-based PPDU, as shown in FIG. 2d) to the access point.

[0279] The format of the RU allocation subfield 265 follows substantially the same format as the RU allocation subfield provided in the common block 220 of the HE-SIG-B field 200 or the RU allocation subfield provided in the trigger frame, as introduced above.

[0280] It may be noted that since the station intended to send the response is the receiving station (i.e., the station to which the RU is assigned) that receives the HE DL MU frame containing the UMRS information 264, the UMRS information 264 does not require a subfield indicating the AID of this station.

[0281] If valid UMRS information 264 is not found, the receiving station should not respond to the access point.

[0282] Generally, only one MPDU transmitted by an AP via the same RU contains UMRS information 264. Of course, several MPDUs may contain such information, in which case the UMRS control fields 264 in the MPDUs carried in the A-MPDU have the same value, i.e., all have the same value when UMRS information occurs. The UMRS control fields in the MPDUs carried in the A-MPDU have the same value. This is to avoid collisions when determining the response RU to be used.

[0283] Returning to Figure 6, since the AP must assign an AID to the downlink RU for the MU downlink OFDMA transmission, the AP cannot give a response management frame (e.g., 320, 350, 370) to unassociated stations, here STA1 and STA6, using the MU downlink OFDMA transmission. In the current version of 802.11ax, the MU downlink OFDMA transmission is limited to already associated stations, which means that the response management frame (from the AP to the station) should still be carried using the legacy single-user (SU) mode. For example, AP 110 may wait until it again accesses the medium for a new TXOP (here, TXOP#3), during which AP 110 transmits, for example, a probe response frame 320 to STA1 using HE SU PPDU 630-1, and wait again until it again accesses the medium for another TXOP (here, TXOP#4), during which AP 110 transmits, for example, an authentication response frame 350 to STA6 using HE SU PPDU 630-2. In all cases, an acknowledgement ACK 330 may be received from the receiving station.

[0284] The need to use the HE SU PPDU to handle the response management frame is unsatisfactory: on the one hand, it introduces delays in network management since the AP 110 has to contend for access to the network anew, and on the other hand, since the HE SU PPDU is transmitted at a low bit rate, given the small amount of data to be transmitted, it uses the medium inefficiently for a long period of time.

[0285] These various shortcomings of the current version of 802.11ax (illustrated through the exemplary context of an exchange of management frames, but which may relate to any other type of frame) indicate that a more efficient use of MU downlink transmissions is required.

[0286] A first approach to resolving some of these drawbacks is introduced below and explained by means of exemplary detailed embodiments with reference to Figures 9a-9d to 12a-b.

[0287] Another aggregation-based approach, which also addresses some of these drawbacks, will be further introduced later and explained by means of an exemplary detailed embodiment with reference to Figs. 13a and 13b to 16.

[0288] According to a first approach, the inventors have considered allowing stations that do not use AIDs, for example stations that are not given an AID, such as unassociated stations, to address (be assigned) downlink RUs in MU downlink transmissions.

[0289] The first novel concept relies on using a specific AID that is not associated with a specific station when registering / associating, e.g., an association identifier reserved for stations that are not associated with an access point, such as AID=2045.

[0290] Thus, an AP willing to address a station without an AID can grant multiple downlink resource units in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point, including downlink resource units assigned to association identifiers not associated with a particular station (e.g., reserved for stations not associated with the access point). The AP can then transmit frames to the station on such downlink resource units reserved for stations not associated with the access point.

[0291] One or more receiving stations may easily determine downlink resource units that are assigned to an association identifier that is not associated with a particular station (e.g., reserved for stations that are not associated with the access point, such as AID=2045) from a plurality of downlink resource units included in a multi-user downlink transmission from the access point within a transmission opportunity granted to the access point. The station may then receive frames from the access point on the determined downlink resource units.

[0292] The second novel concept relies on matching on RU profiles between the uplink RUs already used by a station in an MU uplink transmission and the downlink RUs that the AP will use in an MU downlink transmission to provide a frame to the same station.

[0293] Thus, when a station transmits a frame (e.g., a request management frame of a station that is not yet associated) to an access point (or conversely, the AP receives a frame) using one of the uplink resource units provided in a multi-user uplink transmission towards the access point within a transmission opportunity granted to the access point, the uplink resource units are allocated (e.g., allocated in the frequency domain) according to a certain allocation scheme, and the AP can construct downlink resource units to be included in a multi-user downlink transmission from the access point within the same transmission opportunity granted to the access point or within a next transmission opportunity, the downlink resource units including a downlink resource unit having at least one matching allocation scheme characteristic with the uplink resource unit, and then the AP can transmit a frame (e.g., a response management frame) to the station on the downlink resource unit.

[0294] In this regard, the station only needs to determine the downlink resource units based on the allocation scheme characteristics of the used uplink resource units, and then receives the frame from the access point on the determined downlink resource units.

[0295] In an embodiment, such a decision by a station may depend on the number of downlink resource units assigned to association identifiers not associated with a particular station (e.g., reserved for stations not associated with the access point) in a multi-user downlink transmission, to give the station the ability to switch between the two behaviors.

[0296] For example, if an MU downlink transmission includes only one downlink RU with a predefined identifier (e.g., AID=2045) reserved for unassociated stations, each unassociated station may be considered as a recipient of the downlink RU, i.e., the downlink RU may potentially include frames addressed to the station. For example, the downlink RU may include a frame for one of the unassociated stations, or may include a broadcast frame for all unassociated stations. In this behavior, the allocation scheme of the MU uplink transmission is not taken into account.

[0297] Each receiving station can check the RA field (receiver or destination address) of the (MAC) frame(s) contained in the downlink RU to retain ("receive") only those frame(s) for which the station is the receiving station.

[0298] On the other hand, if the MU downlink transmission contains two or more downlink RUs with a predefined identifier (e.g., AID=2045) reserved for unassociated stations, the unassociated station must determine which downlink resource units, if any, are assigned to it based on the allocation scheme characteristic of the used uplink resource units. If such a downlink RU that matches the allocation scheme characteristic is found, the unassociated station will receive frames from the access point on the determined downlink resource units.

[0299] In that case, each downlink RU has only one recipient station, so an unassociated station may optionally check the RA field of the (MAC) frame(s) contained in the downlink RU to ensure that the frame is actually addressed to it.

[0300] Even when performing the checking step, the unassociated station benefits from uplink signaling to determine which downlink RU to decode. Advantageously, in either case (one downlink RU not assigned to a particular station or multiple downlink RUs), each unassociated station does not need to decode more than one downlink RU.

[0301] Therefore, an unassociated non-AP STA receiving an MU DL frame (e.g., an HE MU PPDU) containing an RU with a STA-ID equal to 2045 should be considered as a recipient of the RU with STA-ID equal to 2045 if one of the following conditions occurs: · There is only one RU with STA-ID equal to 2045 in the MU DL frame. The STA has previously sent a management request frame in response to a trigger frame containing a random access RU(s) with AID set to 2045, and the RU with STA-ID equal to 2045 has the same RU allocation as the RA RU carrying the request in the previously sent MU UL frame (e.g. HE TB PPDU according to 802.11ax).

[0302] Note that the MU DL RU with AID=2045 is sometimes referred to as a "broadcast RU". As this designation implies, a broadcast RU may contain a unicast MAC frame (RA field corresponding to a unicast MAC address) or a broadcast MAC frame (RA field corresponding to a broadcast MAC address).

[0303] It should also be noted that providing multiple RUs with STA-ID equal to 2045 in an HE MU PPDU can be considered an exception to the general requirement of not having more than one downlink RU addressed to an associated STA. In other words, if the list of STAs that are recipients of a transmitted HE MU PPDU is represented by the array STA_ID_LIST, then a STA_ID_LIST element with a particular (AID) value will not appear more than once in the array, except in the following cases: The value identifies an unallocated RU (e.g., 2046), or · Its value is 2045 and identifies a broadcast RU destined for an unassociated STA.

[0304] According to an embodiment, from the AP's perspective, the AP sends an association response frame in a broadcast RU (eg, with AID=2045) to the unassociated STAs, taking into account the following constraints: ·Multiple broadcast RUs (AID=2045) may be inserted in an HE MU PPDU. · If only one Broadcast RU (AID=2045) is inserted in the HE MU PPDU, the Broadcast RU can address one or all unassociated STAs. · If multiple broadcast RUs (AID=2045) are inserted in an HE MU PPDU, each broadcast RU is addressed to only one unassociated STA. To send an association response frame to a non-associated STA, The AP may use the same RU allocation for the broadcast RU (AID=2045) as the RU allocation for the RA RU (AID=2045) used by the unassociated STA to send the corresponding association request frame (see FIG. 9d), or - The AP can use a single Broadcast RU (AID=2045) embedding a Broadcast MAC frame to broadcast an Association Response frame to all unassociated STAs (see Fig. 12a), or - The AP may use a single Broadcast RU (AID=2045) that embeds unicast MAC frames addressed to unassociated STAs (see Figure 12b).

[0305] A broadcast RU containing a unicast MAC frame addressed to an unassociated station may contain an information item identifying the uplink resource unit to be used by the unassociated station in a multi-user uplink transmission opportunity subsequent to the multi-user downlink transmission opportunity to provide an acknowledgement to the access point. The UMRS control field as defined in the standard IEEE 802.11ax draft 2.1 may be used to indicate which UL RU should be used by the unassociated STA to acknowledge the MPDU.

[0306] As a result of these concepts, MU downlink transmissions can be efficiently extended to unassociated stations, or more generally, to any station that does not use an AID assigned to a specific station, preferably an AID reserved for stations that are not associated with an access point.

[0307] Therefore, MU downlink transmission is significantly improved compared to the known current 802.11ax requirements.

[0308] Regarding these novel concepts, an additional block 805 can act as a RU profile management module to control the usage of downlink OFDMA resource units (sub-channels).

[0309] For example, but not exhaustively, operations with respect to the AP may include determining an uplink RU used by a station whose AID (e.g., an AID reserved for unassociated stations) is unavailable in the MU uplink transmission, storing RU allocation scheme properties associated with the used uplink RU, constructing the MU downlink transmission with a downlink RU that includes a downlink RU that matches the stored RU allocation scheme properties, and transmitting a response to the station in such matching downlink RU. Operations with respect to a station different from the AP may include keeping track of the RU allocation scheme properties of an uplink RU used to transmit data (e.g., a request) to the AP in the MU uplink transmission, and determining a downlink RU in the MU downlink transmission that matches the RU allocation scheme properties of the used RU to read the response provided by the AP on the matching downlink RU.

[0310] In that case, the MAC 802.11 layer 804, RU profile management module 805 and PHY layer block 803 interact with each other to correctly handle communications over downlink OFDMA RUs addressed to the station that do not use the AID associated with the station.

[0311] Embodiments of these concepts are now illustrated with various example embodiments in the context of IEEE 802.11ax by considering an OFDMA RU.

[0312] The proposed example is similarly primarily described with reference to the management frames of the 802.11 association process, however the first approach is not limited to such management frame transmissions but can be applied to any 802.11 data or control frame.

[0313] FIG. 9a illustrates the effect of some embodiments of the first approach on the exemplary situation of FIG. 6 described above, with respect to stations STA1 and STA6 that are not yet associated and are in the process of associating with the AP.

[0314] The AP 110 is granted TXOP#1 and sends the same trigger frame 530 as in Figure 6 to reserve a MU UL transmission opportunity. This trigger frame 530 specifies at least one random RU (here, two such random RUs) with AID=2045. The not-yet-associated stations STA1 and STA6 send request management frames to the AP in random RUs 510 with AID=2045 (the other RUs are used by other stations).

[0315] The AP acknowledges the received frame with a Multi-STA BlockAck frame 640 .

[0316] During this sequence, both the AP and the stations perform certain operations to preserve one or more allocation scheme characteristics that govern the uplink RUs used by STA1 and STA6.

[0317] This includes one or more of the following information: the position of the uplink resource unit in the allocation scheme used (i.e. the corresponding entry in Fig. 2f), the frequency band of the uplink resource unit in the allocation scheme used (i.e. the tones in a 20 MHz channel, as per the corresponding entry in Fig. 2f), the size of the uplink resource unit in the allocation scheme used (i.e. the number of tones as shown in the corresponding entry in Fig. 2f).

[0318] For example, FIG. 10a illustrates, by way of a flow chart, the main steps at an AP involved in AP-triggered MU uplink transmissions.

[0319] In step 1010, a trigger frame 530 initiates an MU uplink transmission.

[0320] If the AP receives a frame from a not yet associated station with AID=2045 on a random RU (test 1020), the AP stores the RU profile of the uplink RU used, i.e. the associated allocation scheme characteristics, and associates them, respectively, with the not yet associated station to which it is sent, in step 1030. The frame is, for example, a request management frame.

[0321] For example, the AP may store the MAC address of the not yet associated station (obtained in the received request management frame) together with an 8-bit index (Fig. 2f) corresponding to the allocation scheme used and the position of the uplink RU to be used among the list defined by the allocation scheme used. These three information items allow the AP to retrieve any of the allocation scheme characteristics mentioned above.

[0322] If test 1020 is not successful, the algorithm loops back to step 1010 to wait for the transmission of a new trigger frame.

[0323] Following step 1030, in step 1040, the AP transmits an acknowledgment to the transmitting station, including, for example, a not yet associated station that transmitted the request management frame.

[0324] Accordingly, FIG. 11a illustrates, by means of a flow chart, the main steps in a not yet associated station involved in an AP-triggered MU uplink transmission.

[0325] The process begins at step 1110, where a not-yet-associated station detects a trigger frame 530 transmitted by the AP, which contains one or more random RUs with AID=2045.

[0326] In that case, a not yet associated station willing to register / associate with the AP will contend for access to such random RU with AID=2045. If such a random RU is granted to a not yet associated station, the not yet associated station will send a request frame (310, 340, 360 depending on which stage of the association procedure the station is in) such as a request management frame in the accessed random RU 510 with AID=2045. This is step 1120.

[0327] If an acknowledgement is received from the AP, meaning that the AP will respond to the request in the future (test 1130), the not yet associated station stores the RU profile of the random RU used, i.e. the associated allocation scheme characteristics, this is step 1140.

[0328] For example, a station that is not yet associated can store the 8-bit index (FIG. 2f) corresponding to the allocation scheme to be used and the position of the uplink RU to be used from a list defined by the allocation scheme to be used.

[0329] Returning to Fig. 9a, the AP starts MU downlink transmission in the same TXOP#1. This is possible due to the cascading option provided by 802.11ax (the AP can enable the cascading field in the header of the trigger frame 530 to notify the stations that it will cascade some MU transmissions, either downlink or uplink, during the granted TXOP). Alternatively, after the Multi-STA BlockAck frame 640, the AP can pre-acquire the medium by waiting less than the DIFS period (so other stations have no time to start decrementing their back-off counters to compete for access to the medium).

[0330] In this example, the AP uses the teachings of the embodiments to respond to a received frame, such as a request management frame, during a MU downlink transmission.

[0331] Therefore, the AP constructs the MU downlink transmission with a specific RU allocation profile that takes into account the stored RU profiles of the uplink RUs (with AID=2045) used by STA1 and STA6. In particular, the AP provides the MU downlink transmission with a first downlink RU with AID=2045 that has the same allocation scheme characteristics (e.g., the same location) as the uplink RU used by STA1, and a second downlink RU with AID=2045 that has the same allocation scheme characteristics as the uplink RU used by STA6.

[0332] That means that the various resource units for not yet associated stations in both MU downlink and MU uplink transmissions are not associated with any particular station, in particular, are signaled using the same predefined association identifier, here AID=2045, reserved for not yet associated stations.

[0333] In the illustrated example, STA1 transmitted its probe request frame 310 on an uplink RU at location #1 during MU uplink transmission 510. The AP then constructs the MU downlink transmission using a downlink RU also having AID=2045 at location #1.

[0334] Similarly, STA6 transmitted its authentication request frame 340 in an uplink RU at location #6 during MU uplink transmission 510. In that case, the AP constructs the MU downlink transmission using a downlink RU also having AID=2045 at location #6.

[0335] Of course, other allocation scheme characteristics than uplink RU location, as introduced above, may be used.

[0336] By this approach, the not yet associated stations STA1 and STA6 know that the first and sixth resource units in the MU downlink transmission are directed to them, provided that they are assigned AID=2045. That means that in this embodiment, two criteria are combined for the not yet associated stations to identify the downlink RU addressed to them: as the first criterion, the downlink RU may be assigned AID=2045, and as the second criterion, the associated allocation scheme characteristics must match the uplink RU used in the MU uplink transmission when transmitting the preceding frame, e.g., a request management frame.

[0337] Thus, the AP 110 uses the so configured downlink RU 920 with AID=2045 to send responses to not yet associated stations (other downlink RUs are used conventionally). In this example, the AP uses the first downlink RU (location #1) to send a probe response frame 320 to STA1, and the sixth downlink RU (location #6) to send an authentication response frame 350 to STA6.

[0338] Finally, the not yet associated stations STA1 and STA6 receive and decode the response frames sent by the AP on their two downlink RUs in response to their previous request frames, and acknowledge successful receipt with uplink transmissions 940.

[0339] As is readily apparent from this figure, in comparison with Fig. 6, consecutive SU transmissions (630-1 and 630-2) for management frames are now avoided, resulting in a simplified association procedure for not yet associated STAs and a more efficient use of the network, which is particularly advantageous for managing associations of new stations in high density networks such as 802.11ax.

[0340] 10b illustrates, by way of a flow chart, the main steps at an AP associated with AP-triggered MU downlink transmissions when implementing some embodiments. These operations describe how the AP, following receipt of one or more request management frames from not yet associated stations, transmits response frames to those stations using a MU DL transmission.

[0341] In step 1050, the AP determines whether it is ready to transmit one or more response management frames in response to a request management frame received from a station that is not yet associated during a previous MU uplink transmission.

[0342] If yes, in step 1060, the AP constructs a MU downlink frame (i.e., a number of downlink resource units to be allocated for downlink transmission from the access point within the transmission opportunity granted to the access point) that includes, for each response frame to be transmitted, downlink resource units that match the allocation scheme characteristics stored for the corresponding not-yet-associated station (i.e., match the allocation scheme characteristics of the uplink resource units used by the station to transmit the request frame in the MU uplink transmission). For example, the downlink RU and the uplink RU may have the same position in the allocation scheme used. Each such downlink resource unit is declared in HE-SIG-B in association with AID=2045.

[0343] Next, in step 1070, the AP 110 transmits each response management frame on the corresponding downlink RU with AID=2045 to the appropriate not-yet-associated stations.

[0344] Accordingly, Figure 11b illustrates, by means of a flow chart, the main steps in a not-yet-associated station involved in an AP-triggered MU downlink transmission, according to some embodiments. These operations describe how such a station decodes a response management frame received from the AP in the MU downlink transmission.

[0345] A station that is not yet associated has already sent a request management frame to the AP using an uplink RU with AID=2045 in a previous MU uplink transmission and is waiting for a response.

[0346] The process begins when a MU downlink frame is received, in step 1150, to determine if the frame contains a downlink resource unit with AID=2045.

[0347] If not, the not yet associated station waits for the next MU downlink frame.

[0348] If so, in step 1160, the station determines whether one of the downlink RUs with AID=2045 has allocation scheme characteristics that match the allocation scheme characteristics stored in step 1140. This may consist of simply verifying whether the downlink RU with AID=2045 has the same location (uplink RU) as was used in the preceding MU uplink transmission.

[0349] If a matching downlink RU with AID=2045 is found, the not-yet-associated station selects this downlink RU to read the frame transmitted by the AP, step 1170. Optionally, before processing the frame, the station may further read and check the MAC address specified in the frame.

[0350] Accordingly, the response management frame is decoded from this downlink RU and forwarded, for example, to the MAC 802.11 layer block 804 (step 1180).

[0351] Although FIG. 9a illustrates a situation in which the downlink resource units of the MU downlink transmission providing the response immediately follow the uplink resource units of the MU uplink transmission for which the request was transmitted within the same transmission opportunity granted to the access point, other embodiments may provide that the uplink resource units allocated to the uplink transmission for which the request was transmitted and the downlink resource units allocated to the downlink transmission providing the response are separated by one or more other MU transmissions, either downlink or uplink, within the same transmission opportunity granted to the access point.

[0352] This is illustrated in FIG. 9b, which shows that one or more MU transmissions can be inserted between transmission 510 and transmission 920.

[0353] This embodiment gives the AP time to prepare a response management frame.

[0354] Another situation is shown in Figure 9c, where the downlink resource units of the MU downlink transmission providing the response and the uplink resource units of the MU uplink transmission for which the request was sent belong to two separate transmission opportunities granted to the access point.

[0355] Between the two separate TXOPs, any station can contend to transmit data and access the medium.

[0356] This embodiment also allows the AP time to prepare a response management frame.

[0357] In the embodiment of Figures 9b and 9c, the AP can avoid inserting between the two transmissions an "intermediate" MU downlink frame containing a downlink resource unit with AID=2045 that matches the associated allocation scheme characteristic or characteristics of an uplink RU previously used by an unassociated station that transmits a request frame to the AP, i.e., is currently waiting for a response (management) frame from the AP, which advantageously avoids an unassociated station reading a downlink RU that does not contain a frame ultimately addressed to it.

[0358] Note, however, that it is not mandatory to avoid such "intermediate" MU downlink frame(s): if an "intermediate" MU downlink frame(s) is inserted between two transmissions, an unassociated station reading a downlink RU with AID=2045 (matching the associated allocation scheme characteristic(s)) containing a frame not addressed to it will simply ignore the frame (e.g., by determining whether the RA field 203 is its own MAC address) and continue to monitor for another MU downlink frame containing a downlink resource unit with AID=2045 matching the associated allocation scheme characteristic(s).

[0359] 9d shows a general embodiment in which multiple downlink resource units (950) are allocated to multiple unassociated stations in a MU DL frame. In the illustrated embodiment, several RUs with AID equal to 2045 are signaled in the HE-SIG-B in locations corresponding to UL requests. The AP can use these downlink RUs with AID=2045 to send response frames, such as probe responses and authentication responses, to the unassociated stations.

[0360] Another embodiment is shown in Figure 12a, where a specific downlink resource unit (1210) is allocated to an unassociated station (i.e., with AID=2045) in a MU DL frame. The AP can use this single downlink RU with AID=2045 to send a response frame to the unassociated station as a broadcast frame (i.e., with RA field 203 set to the broadcast address).

[0361] As will be explained later, given a single downlink RU with AID=2045, unassociated stations do not check for a match with their associated allocation scheme property or properties. They all read the frame(s) of this single downlink RU with AID=2045. Due to the lack of an allocation scheme property check, this downlink resource unit with AID=2045 can be placed anywhere in the MU DL frame. Figure 12a shows steps 1058 and 1054 on the AP side of the flowchart of Figure 10c, which will be explained later.

[0362] A variant is shown in Fig. 12b, where a specific downlink resource unit (1220) is allocated to the unassociated station in the MU DL frame. This may be done because the AP decides to send a specific response to a particular unassociated station. In that case, the RA field 203 of the frame sent through the specific downlink resource unit (1220) with AID=2045 is set to the MAC address of the destination unassociated station. Fig. 12b shows steps 1053 and 1054 on the AP side of the flowchart of Fig. 10c, which will be described later.

[0363] These figures show that depending on the number of downlink RUs specified in the MU DL transmission, an unassociated station can switch between a first behavior in which the unassociated station checks for a match between a downlink RU having AID=2045 and its associated allocation scheme characteristic(s) before accessing / reading a matching downlink RU (e.g., when there are two or more downlink RUs having AID=2045), and a second behavior in which the unassociated station does not perform a check and directly accesses / reads the downlink RU (e.g., when there is a single downlink RU having AID=2045).

[0364] In the second behavior, it is the responsibility of the unassociated station to check whether the frame(s) transmitted via its own downlink RU are addressed to it, for example by checking the RA field 203 (broadcast address or station-specific MAC address). Such checking of the RA field 203 may optionally be done by the unassociated station with the first behavior.

[0365] According to some embodiments, several RUs with AID=2045 can be used in the same MU downlink transmission to transmit response management frames to each not yet associated station. This is advantageous in densely active networks (e.g., train stations where many stations connect and disconnect from the network in a short period of time).

[0366] Advantageously, the AP can periodically provide a trigger frame with multiple (possibly only one) random RU with AID=2045. Preferably, the allocation scheme of the first entry of Fig. 2f is used to provide the maximum number of opportunities for not yet associated stations to perform their association procedure. The AP can therefore provide an MU downlink transmission matching the same allocation scheme immediately afterwards in order to provide a response management frame.

[0367] 10c illustrates, by way of a flow chart, the main steps at the AP associated with one or more MU downlink transmissions embedding frames destined for unassociated stations, according to some other embodiments. Note that MU downlink transmissions can also embed frames intended for already associated stations, but these transmissions can use conventional methods and will not be further described here.

[0368] In the following description, a predefined identifier value of 2045 is chosen to designate the MU DL RU reserved for unassociated stations. Of course, this value is given for illustrative purposes only, and any other predefined value or signaling means may be adopted.

[0369] In step 1051, the AP determines whether there is a list of pending frames (e.g., response management frames or any other type of frame) waiting to be transmitted to the unassociated station. Again, other frames intended for associated stations may be handled by the AP in parallel or sequentially.

[0370] If the list of untransmitted frames is not empty, it is determined in step 1052 whether the list contains a broadcast frame (i.e., an MPDU packet with RA field 203 set to broadcast value FF:FF:FF:FF:FF:FF). If a broadcast frame is found, it is selected for transmission in step 1053. The MU DL frame containing the selected frame contains a single downlink RU with AID=2045 (step 1054). The downlink RU can be located anywhere in the MU DL frame (an example is shown in FIG. 12a). The MU DL frame may be constructed at the time of incorporating the downlink RU with AID=2045, or may be formed earlier by the AP's module 805, for example, at the time of defining other downlink RUs destined for already associated stations.

[0371] If the list does not contain a broadcast frame (test 1052 is negative), then the number of frames that are yet to be transmitted is determined in step 1057. If there is only one frame in the list, then the frame is selected (step 1058) and incorporated into the MU DL frame (step 1054). As in step 1053, only one downlink RU with AID=2045 is incorporated into the MU DL frame (e.g., as shown in FIG. 12b).

[0372] If there are multiple frames in the list (two or more frames to be transmitted in test 1057), multiple frames are selected from the list in step 1059. Preferably, all response frames following the reception of a request frame received on an uplink RU from an unassociated station (for example, according to the flowchart of FIG. 10a) are selected for transmission to the corresponding unassociated station. The design of the downlink RU with AID=2045 for the response frame can be based on at least one allocation scheme characteristic of the uplink RU used by the unassociated station. Naturally, the response frame for a particular unassociated station will be transmitted via a downlink RU that matches the allocation scheme characteristic of the uplink RU used by the same station when requesting the AP.

[0373] The number of frames selected in step 1059 may be limited to the available downlink RUs, e.g., the number of available downlink RUs that will be assigned to AID=2045. This may be the case if some downlink RUs are already assigned to certain already-associated stations.

[0374] In step 1061, multiple downlink RUs with AID value 2045 are embedded into the MU DL frame. The MU DL frame is constructed either in advance or at the time of embedding. Each embedded downlink resource unit with AID=2045 matches the allocation scheme characteristic stored for the corresponding unassociated station (i.e., each downlink RU matches the allocation scheme characteristic of the uplink resource unit used by the station to transmit the frame in the MU uplink transmission).

[0375] For example, an AP that receives an RA RU carrying a management request frame from an unassociated STA may transmit a management response frame in an HE MU PPDU (i.e., an MU DL frame) using a broadcast RU identified by a STA_ID (AID) equal to 2045 and having the same RU allocation as the RU allocation of the received RA RU.

[0376] The MU DL frame is transmitted by the AP in step 1055. Finally, in step 1056, the list of untransmitted frames is updated by removing the selected frames that have been transmitted (and acknowledged), and the steps of the flowchart are repeated from step 1051.

[0377] The flow chart shown in Figure 10c illustrates one possible implementation for handling the transmission of frames for unassociated stations according to some embodiments, however other implementation variations are also contemplated.

[0378] For example, a broadcast frame may be given a lower priority compared to other frames in the list, meaning that even if there is a broadcast frame in the list, one or more frames may be selected first for transmission, and then the broadcast frame is transmitted only after all or some specified number of frames from the list (based on elapsed time or other criteria) have been transmitted.

[0379] In another variation, instead of selecting multiple frames in step 1059, the AP can decide to select only one frame in the list of multiple frames to transmit. In this case, the MU DL frame will contain only one downlink RU with AID=2045, which contains the selected frame. In this variation, step 1061 is omitted. The selected frame is embedded in the MU DL frame, as shown in step 1054.

[0380] Accordingly, Figure 11c illustrates, by means of a flow chart, the main steps in an unassociated station related to an AP-triggered MU downlink transmission. These operations show how such an unassociated station decodes frames received from the AP in an MU downlink transmission.

[0381] The process begins by checking when an MU downlink frame (HE MU PPDU) is received by the station (step 1151), which is similar to step 1150 in Figure 11b.

[0382] If an MU downlink frame is received (the test in step 1151 is positive), the station determines in step 1152 whether the received MU DL frame contains multiple downlink RUs with AID equal to 2045.

[0383] If multiple downlink RUs with AID value 2045 are found (the test in step 1152 is positive), the unassociated station enters a first behavior and checks whether the previously stored RU profile matches the RU allocation of one of the downlink resource units with AID=2045 contained in the just received MU DL frame (step 1153). The RU profile may be pre-stored by the station, for example, after execution of the flowchart of Fig. 11a (e.g., sending a request frame in a MU UL RU with AID=2045 and storing the profile of the uplink RU as shown in step 1140). Thus, if the unassociated station has already sent a request frame to the AP with an uplink RU with AID=2045 in a previous MU uplink transmission, the RU profile is stored.

[0384] The match test in step 1153 may consist of simply verifying whether the downlink RU with AID=2045 has the same position as that used in the preceding MU uplink transmission.

[0385] The matching test in step 1153 may also be that the STA has previously transmitted a management request frame in response to a trigger frame containing a RA-RU(s) with AID set to 2045, and the broadcast RU with STA-ID (AID) equal to 2045 has the same RU allocation as the RA-RU carrying the request in the previously transmitted HE TB PPDU.

[0386] If the test in step 1153 is positive, the unassociated station is considered as the recipient of the matching downlink RU, which means that the matching downlink RU potentially contains MAC frames destined for the unassociated station. Then, in step 1154, the matching downlink RU is selected for decoding. Optionally, before decoding, the unassociated station checks whether the RA field 203 of the MAC frame carried in the selected matching downlink RU corresponds to the MAC address of the unassociated station.

[0387] If the test in step 1153 is negative, the unassociated station is not the recipient of the downlink RU. The unassociated station waits in step 1151 for the reception of a new MU DL frame with AID=2045.

[0388] In step 1155, the frame encapsulated in the selected downlink RU with AID=2045 is decoded and forwarded, for example, to the MAC 802.11 layer block 804. The encapsulated frame may be a response frame.

[0389] If in step 1152 a single downlink RU with AID value 2045 is found (the test is negative), the unassociated station enters a second behavior and does not check any match between the stored RU profile and the single downlink RU. The unassociated station is (automatically) considered as the recipient of the downlink RU. The unassociated station then checks in step 1156 whether the RA field 203 of the MAC frame corresponds to the MAC address of the unassociated station or to a broadcast address. If so, in step 1157 a downlink RU is selected and the frame contained therein is decoded in step 1155. If not, the unassociated station waits in step 1151 for the reception of a new MU DL frame with AID=2045.

[0390] In any case, it should be noted that, particularly in step 1152, when multiple downlink RUs with AID=2045 are determined, the unassociated station will eventually decode at most one downlink RU with AID=2045. This makes it easy for the unassociated station to determine whether it is the recipient of the downlink RU, and if so, to determine which downlink RU it is the recipient of.

[0391] It should also be noted that an unassociated station that receives an MU DL frame containing an RU with a STA-ID (AID) equal to 2045 is considered to be the recipient of the RU with STA-ID equal to 2045 when one of the following conditions occurs: · There is only one RU with STA-ID equal to 2045 in the MU DL frame (test 1152 is not true). · The STA has previously transmitted a (e.g. management) request frame in response to a trigger frame containing RA-RU(s) with AID set to 2045, and a broadcast RU with STA-ID equal to 2045 has the same RU allocation as the RA-RU carrying the request in the previously transmitted MU UL frame (test 1153 is positive).

[0392] According to a second approach based on aggregation, the inventors have considered using one RU, i.e. one resource unit targeted (or equivalently, dedicated) to multiple stations, in the MU downlink transmission for multiple receiving stations. Thus, the access point can aggregate data frames addressed to more than one station and transmit the aggregated data frames via such one resource unit dedicated to multiple stations among the resource units forming a multi-user downlink transmission opportunity (MU downlink OFDMA TXOP) granted to the access point for downlink communication to the stations. The aggregated data frames may only include individually addressed data frames, i.e. data frames each having an RA addressing a single station. The aggregated data frames may include a combination of individually addressed (i.e. having an RA of a single station) and group addressed (i.e. having an RA corresponding to a multicast or broadcast address) data frames.

[0393] Such RUs targeted to a group of stations may be signaled with a "group AID," in contrast to the current requirement of only allowing individual (i.e., associated with a single station) AIDs to be used for MU downlink transmissions. In particular, resource units targeted to multiple stations may therefore be assigned to a predefined (group) association identifier that is not associated with a particular station in a downlink transmission opportunity.

[0394] As a result, any station (associated with such a group) can determine (e.g., using a group AID) a "group" resource unit intended for multiple stations from among the multiple resource units forming the multi-user downlink transmission opportunity granted by the access point for downlink communication to those stations, receive aggregated data frames via the determined resource unit, and extract one or more data frames addressed to the station from the received aggregated data frames.

[0395] In fact, if any station registered with an access point is associated with a unique association identifier used by the access point to assign resource units to the station in transmission opportunities granted to the access point, the concept proposed by the inventors consists of the AP constructing a number of resource units forming a multi-user downlink transmission opportunity granted to the access point for downlink communication to the station, the number of resource units including a "group" resource unit assigned to an association identifier not associated with a specific station, and then transmitting one or more data frames to the station on the resource unit assigned to the association identifier not associated with a specific station.

[0396] Thus, the station determines only those "group" resource units that are assigned to association identifiers that are not associated with a particular station from the multiple resource units that form the multi-user downlink transmission opportunities granted to the access point for downlink communication to the station, and therefore receives one or more data frames from the access point on the determined downlink "group" resource units.

[0397] By aggregating data frames that are to be addressed to several stations within the same dedicated group RU, the proposed concept allows the AP to efficiently target a large number of stations, thereby making more efficient use of each RU (thus reducing padding bits), avoiding duplicating the same payload across several RUs (by grouping stations targeted by the same multicast frame), and providing efficient (i.e., at a higher bit rate) response management frames to stations that are not yet associated (thus forming groups of unassociated stations).

[0398] Also, by using an AID that is not associated with a station during MU downlink transmission, the proposed concept provides an opportunity for the AP to address one or more stations that are not given an AID. Thus, a group RU that is assigned to an association identifier that is not associated with a specific station can be dedicated to multiple stations. Thus, a station can easily identify which RU to wait for in a downlink transmission.

[0399] Therefore, MU downlink transmission is significantly improved compared to the known current 802.11ax requirements.

[0400] To that end, an additional block 805 may act as a multi-station RU management module to control the usage of OFDMA resource units (sub-channels).

[0401] For example, but not exhaustively, operations for the AP may include generating and transmitting an MU downlink frame as specified below, which identifies at least one RU intended for multiple stations with a specific AID instead of one station per RU as is done today, and then managing the aggregation of MAC frames that will be addressed to multiple stations within such resource unit.

[0402] Operations with respect to a station other than the AP may include analyzing a received MU downlink frame to determine whether the station is allowed access to an RU for itself or to an RU dedicated to multiple stations (group RU), and, in association with such an RU dedicated to multiple stations, processing the MAC frames aggregated therein to extract the MAC frames addressed to itself.

[0403] However, some problems may arise regarding the acknowledgment by stations of data frames transmitted via DL group RUs.

[0404] In current 802.11ax systems, data frames received via an RU are acknowledged by the receiving station to which the RU is specifically assigned, and this acknowledgement is transmitted via an acknowledging RU in a subsequent MU uplink OFDMA transmission 625 as indicated in the received UMRS information 264.

[0405] However, this scheme cannot operate in the case of DL group RUs, since no particular station is designated as the RU recipient, and even if one station were to be so designated, it should not be allowed to acknowledge data frames addressed to other stations in the DL group RU.

[0406] Our improved concept to overcome these acknowledgement problems relies on signaling different UMRS information in different data frames carried via the DL Group RU. For example, if a Group RU carries two aggregated data frames addressed to two respective stations, then the respective response resource unit information is signaled to identify the response resource unit to be used by the receiving station in the MU uplink OFDMA transmission 625 that follows the MU downlink OFDMA transmission 620 to provide a response (or acknowledgement) to the data frame to the access point.

[0407] As a result, the receiving station (addressed through the DL group RU): Obtaining response resource unit information from the data frame retrieved via the group RU that identifies one response resource unit in the MU uplink OFDMA transmission 265; A response (eg, an acknowledgment) to the retrieved data frame is then transmitted to the access point via the identified response resource unit.

[0408] In contrast to the 802.11ax requirement that limits UMRS per RU to one value, this improved concept allows different receiving stations (using the same group RU) to efficiently acknowledge receipt of a data frame.

[0409] The AP can schedule more RUs for MU uplink OFDMA transmission 625 than for MU downlink OFDMA transmission 620, allowing all receiving stations a chance to acknowledge the data frames they received, thus avoiding retransmission of data frames by the AP, thereby saving channel bandwidth.

[0410] Also, the receiving station as defined in the RA field 210 (MAC address) of the frame MAC header can use the response RU indicated in the UMRS information defined in the HT control field 250 of the same MAC header. As a result, even a receiving station that is not yet associated with the AP can acknowledge the data frame. Thus, the association procedure for the station can be simplified (using a random RU with AID=2045, receiving the response from the AP during the MU downlink transmission 620, and acknowledging the response during the subsequent MU uplink transmission 625).

[0411] To achieve this, the operation of the multi-station RU management module 805 at the AP may also include signaling in the aggregated MAC frame respective response resource unit information (e.g., UMRS values) that identify response resource units to be used by the receiving stations in a multi-user uplink transmission opportunity that follows the multi-user downlink transmission opportunity to provide a response to the access point to the received data frame.

[0412] Operations relating to a station other than the AP may also include obtaining response resource unit information (e.g., a UMRS value) from the retrieved data frame that identifies one response resource unit in the multi-user uplink transmission opportunity, and transmitting a response to the retrieved data frame to the access point via the identified response resource unit.

[0413] In the description, the terms "multi-destination" RU, "multi-station" RU, "multi-STA" RU, "multicast" RU and "broadcast" RU are intended to be synonymous with the "group" RU discussed above and refer to a resource unit targeted to multiple stations. Note that "broadcast RU" does not imply that the RU must carry broadcast data frames, but rather refers to the RU targeting multiple stations.

[0414] An embodiment of the aggregation-based approach is illustrated herein with various exemplary embodiments in the context of IEEE 802.11ax by considering an OFDMA RU dedicated to multiple stations.

[0415] Although the proposed examples below are described with reference to management frames of the 802.11 association process, the teachings are not limited to such management frame transmissions but may be applied to any 802.11 data frames, such as data frames addressed to various stations.

[0416] FIG. 13a illustrates, by means of a flow chart, an embodiment implemented in a physical access point when preparing and executing a MU downlink transmission.

[0417] In step 1310, the AP first determines whether it is willing to group several receiving stations for downlink transmission.

[0418] Here, three illustrative situations are proposed.

[0419] In the case of a station association procedure, a station may send a request management frame to the access point during the procedure of associating (i.e., registering) with the access point. In other words, the access point may receive request management frames (310, 340, 360) from stations willing to associate (i.e., register) with the access point and will attempt to respond to those stations by grouping together response management frames (320, 350, 370) in the same group RU intended for multiple receiving stations.

[0420] The request management frame may have been received via a previous single-user communication sent by the AP, or via a previous trigger frame (typically TF 530 with respect to FIG. 6), or both, which allocates a number of random RUs with AIDs equal to 2045 values ​​so that during the uplink transmission phase 510, a number of request management frames may be transmitted by stations that are not yet associated in the corresponding RU or RUs.

[0421] An AP can also group stations with respect to a common interest in receiving data frames. For example, an access point may receive (e.g., from a higher OSI layer) a multicast frame that is to be addressed to multiple recipient stations, and therefore may consider forwarding the multicast frame to the recipient stations using a group RU dedicated to the multiple stations.

[0422] Another example is the case where, given the size of a downlink transmission opportunity and a size threshold (possibly the size of an RU), the access point determines whether there are small data frames to be transmitted to the station that can be grouped into a single RU to reduce padding bits. More generally, the AP can consider using a special group to carry any MAC frames (to be transmitted) that do not belong to an existing individual transmission of the MU download transmission. In order to fill the "MPDU collector" RU or "aggregate RU" (hence group RU) with the largest MAC frame of the remaining MAC frames (smaller than the largest MAC frame), the AP can try to carry the largest MAC frame, for example, using an individual RU.

[0423] As an example, the aggregate RU may be stored in the AP's EDCA buffer and collect any untransmitted MAC frames for which individual RU allocation is inefficient (too much padding would be required, e.g., STA3 and STA8 in FIG. 6).

[0424] Once the AP has determined one or more groups of recipient stations that have corresponding MAC frames to be transmitted, in step 1320, an RU (hence referred to as a group RU, broadcast RU, multicast RU or multi-station RU) is assigned to each group so determined.

[0425] For example, a group RU may be assigned to carry a response management frame (320, 350 or 370) in response to a previously received request from a station that is not yet associated.

[0426] In a preferred embodiment, the AID value assigned to this group RU for multiple stations takes a predefined value (known by all 802.11ax nodes conforming to the present concept) of 2045. It can be noted that, to speed up the association procedure, this value is the same value used to indicate RUs dedicated or assigned to stations not yet associated in MU uplink transmissions (510 in FIG. 6).

[0427] As a result, when a request management frame is transmitted (by a station) in a previous resource unit that forms part of an uplink transmission opportunity granted to the access point for multi-user uplink communication from the station, the previous resource unit allocated to a station not yet associated with the access point, the group resource unit allocated in step 1320, and the previous resource unit used are signaled in the downlink transmission opportunity and uplink transmission opportunity, respectively, using the same predetermined association identifier (not given by the AP to a specific station), here AID=2045.

[0428] It may be noted that even if not aggregating MAC frames in a RU dedicated to a not yet associated station, the unique concept of providing an RU with an AID reserved for not yet associated stations for downlink transmission improves (speeds up) the association procedure for such stations. Such a RU may also be used for a single not yet associated station.

[0429] Group RUs may also be assigned to carry multicast frames targeted to several recipients, in which case a predefined AID may be used, e.g. AID=2042, known by all 802.11ax nodes conforming to the concept.

[0430] Also, AID=0 may be used to signal an aggregation RU that collects small pending MAC frames.

[0431] Other variations can also be proposed. For example, in the context of multiple BSSs ("virtual APs") managed by a single physical AP, the AP can assign a unique AID value to each BSS it manages, meaning that each BSS has a unique AID value that is not associated with a specific station (but is associated with all BSSs). For example, the AID value can be an index of each BSS. If "n" is the maximum number of virtual APs managed by the physical AP (for example, this value is defined in the MaXBSSID indicator in the composite BSSID element of the beacon and probe response frames), BSSs 1 to n are assigned AIDs 1 to n, respectively.

[0432] Each non-designated AP can only use its own AID, however, the designated AP can use any AID of the VAP.

[0433] In this regard, the representative AP can provide one or more aggregated RUs specific to one or more respective BSSs in the MU downlink transmission by using the respective AIDs. Thus, the AP can select the AID of the BSS to which it intends to transmit a frame.

[0434] The representative AP can also signal random RUs in the TF (MU uplink transmission) that are each individually assigned to a particular BSS. The first random RU is assigned to AID=i to restrict access to not yet associated stations willing to register with VAPi, while the second random RU is assigned to AID=j to restrict access to not yet associated stations willing to register with VAPj. RUs with the same AID can be used in the MU downlink transmission to transmit response management frames related to each BSS.

[0435] Once one or more RUs dedicated to the group of stations have been determined, step 1330 consists of the AP concatenating or aggregating, for each group RU, all untransmitted MPDU frames relating to the corresponding group of stations. In the following, it should be appreciated that the term "data frame" in the further illustrations of steps 1330 and 1340 corresponds to any untransmitted frame in the outbound MAC transmit queue (i.e., including, but not limited to, any data frame from the application layer 801 and any 802.11 management frame useful for the MAC layer 804, such as frames of the 802.11 association procedure).

[0436] Regarding management frames, all response MAC management frames prepared by the AP for stations that are not yet associated can be aggregated together into one HE-MU PPDU (up to the size of the PPDU given the reserved TXOP).

[0437] For a multicast frame, in response to receiving the multicast frame, the access point can generate multiple data frames including the payload of the multicast frame, which will be individually addressed to each of the receiving stations. Thus, the AP aggregates the generated data frames including the payload of the multicast frame (up to the size of the PPDU, given the reserved TXOP). Of course, if the TXOP does not provide enough space to transmit all the generated data frames, the remainder may be transmitted in one or more subsequent MU downlink transmissions.

[0438] The AP can also aggregate together (up to the size of the PPDU, given the reserved TXOP) MAC frames stored in its EDCA buffer for stations not yet addressed by other RUs of the same MU downlink transmission. Given this constraint, aggregations for aggregated RUs are processed last (as the last RUs).

[0439] The AP can follow the principle of 802.11ax A-MPDU aggregation for conventional RUs, but the principle can be slightly modified so that MPDUs of the same A-MPDU can be addressed to different stations. In other words, the aggregation rules are slightly modified for group RUs ("broadcast RUs" in 802.11ax standard terminology) to support addressing several stations within a single A-MPDU. This mechanism does not require any modification of the 802.11 basic part, since it is limited only to the 802.11ax stations of the present invention that are involved in the limited situation of group RUs.

[0440] For example, when transmitted by an 802.11ax AP in a RU targeted to multiple STAs (e.g., a broadcast RU), the MPDUs in the A-MPDU may have different RAs. The RA may be the MAC address of one of the STAs or the broadcast MAC address. The address type (individual addressing or group addressing) and address value of the MPDU may be different in the A-MPDU in the RU targeted to multiple STAs.

[0441] Any other aggregation mechanism (MAC Service Data Unit (MSDU) aggregation, MAC Protocol Data Unit (MPDU) aggregation, A-MPDU frame concatenation, or any combination of these schemes) can be used to concatenate MAC frames for various stations.

[0442] To allow stations to efficiently retrieve their own MAC frames, the access point sets the MAC address field 210 in each data frame to be aggregated to the MAC address of the recipient station.

[0443] If the MAC address field contains a broadcast address, the MAC frame can be retrieved by all stations belonging to the Group RU. Note that if a Group RU is dedicated to a group to which all stations in a BSS belong, or to a group that is defined as being accessible to all stations in a BSS, then a MAC frame with a broadcast address can be retrieved by all stations in the BSS.

[0444] If the MAC address field contains a multicast address (ie, defines a multicast group of stations), the MAC frame can be retrieved by all stations that belong to both the group RU and the multicast group.

[0445] Next, in step 1340, the MU downlink PPDU formed from each RU is transmitted by the AP on the corresponding RU of the communication channel.

[0446] For a group of stations, that means that the aggregated response management frame is transmitted on the group RU with AID=2045, or (in case of multiple BSSs) on each group RU with AID=i in case of a response management frame related to BSSi, the aggregated generated frame containing the payload data of the multicast frame is transmitted, for example, via the group RU with AID=2042, and the aggregated aggregate frame is transmitted via the last RU of the channel, i.e., the group RU with AID=0 (possibly with AID=j in case of an aggregate frame related to a particular BSSi in case of multiple BSSi).

[0447] Other RUs (assigned to individual stations) are treated as usual.

[0448] To ensure efficient processing by stations, a downlink transmission opportunity may include ordered signaling (in the HE-SIG-B preamble of the 802.11axMU DL frame) of allocations of multiple resource units to one or more stations, with the ordered signaling first specifying each allocation of resource units to individual stations (RUs with AIDs associated with a single station), then specifying each allocation of resource units to groups of stations (in the above example, AID=2042 or 2045, or i in the case of multiple BSS), and then specifying the allocation of aggregated resource units (AID=0) to any stations not already associated with a resource unit. This advantageously allows a station to ignore any further RU analysis in the same HE MU PPDU once it finds one RU (individual or group) addressed to it.

[0449] It may be noted that regardless of the use of groups of stations or transmissions to stations that do not have an AID (not yet associated), the aggregation-based approach advantageously maintains the strict usage of the presence of a unique AID in the RU allocation of the HE-SIG-B preamble.

[0450] Thus, the downlink transmission opportunity includes resource units that a station can read using traditional 802.11ax schemes (e.g., by identifying the RUs associated with its AID) or by using the newly proposed scheme as described herein with reference to FIG. 13b (e.g., by identifying the RUs associated with a group AID).

[0451] FIG. 13b illustrates, by way of a flow chart, an embodiment implemented in a non-AP STA for handling group RUs dedicated to a group of stations in a MU downlink transmission from an AP.

[0452] A non-AP station may be any station that is already associated with the AP that sends the MU downlink PPDU, or any not-yet-associated station that is in the process of associating with the AP that sends the MU downlink PPDU.

[0453] In step 1350, the MU downlink frame formed by the per RU PPDU is received from the physical access point, and the station determines which RUs are addressed to it. RUs assigned to individual stations are processed conventionally.

[0454] Special processing is required for the situation where a station participates in a group RU carrying data for a group of stations, in which the station determines such group resource units dedicated to multiple stations from among multiple resource units forming downlink transmission opportunities granted to the access point for downlink communication to the stations.

[0455] For stations that are not yet associated, that means determining the group resource units that are assigned to stations that are not yet associated with the access point in order to retrieve the response management frame from the access point to the transmitted request management frame. This can be done by simply searching for an RU with AID equal to 2045 or an RU with AID equal to the BSSID (in multi-BSS case) in the HE-SIG-B preamble of the received MU downlink frame.

[0456] If no group RU is found, the process ends and the not yet associated stations set their NAV (duration is taken from the L-SIG field of the received frame).

[0457] If such a group RU with AID=2045 is found, the next step is step 1360 .

[0458] Optionally, a not yet associated station may analyze the received MU downlink frame and therefore determine the resource units to be allocated to the not yet associated station only if the processing of the request management frame sent by the station is incomplete (i.e., no response has been received from the AP). This request may have been sent earlier during a previous MU uplink transmission (e.g., during 510). In particular, an not yet associated STA may ignore any RU with STA-ID set to 2045 in an HE MU PPDU received from an HE AP where this STA is not in a pre-associated situation (which means that the not yet associated STA has not sent any association request to the AP).

[0459] For already associated stations, their behavior may be different: a station may first scan the resource units assigned to individual stations and verify whether a resource unit in the received MU downlink frame is assigned to the station individually, and if the verification is only negative, the station determines a group resource unit dedicated to multiple stations from the multiple not yet scanned resource units.

[0460] The processing order is derived from the order of declaring RUs in the MU downlink frame as shown above with reference to Fig. 13a, where individual RUs are declared first, then group RUs (e.g., AID=2042 for multicast), and then aggregate group RUs (AID=0). In this situation, if the station detects a single RU addressed to it, the process of Fig. 13b ends and the station analyzes the corresponding RU as in conventional 802.11ax. Otherwise, the station searches among the group RUs whether one of them is addressed to it. This can be done using bit masking on the AID (e.g., if the group AIDs have the same most significant bits) and / or by detecting a predefined AID. Thus, the station scans the group resource units assigned to the list (group) of stations and verifies whether the station belongs to the list associated with one of the scanned group resource units.

[0461] This allows a station to stop parsing MU downlink frames as soon as it detects a group RU dedicated to the group it is in. For example, if the station knows that it will be involved in multicast communication (e.g., due to an exchange at the application layer, see module 801), it can probe any group RUs dedicated to multicast (in this example, AID=2042).

[0462] If the verification is positive (the station belongs to the list), the group resource unit determined to retrieve the data frame is the group resource unit assigned to the list containing the station (eg, having AID=2042).

[0463] On the other hand, if the verification is only negative, the determined group resource unit is an aggregated resource unit (AID=0) that is used to convey data frames for any station that is not assigned individually or through a list to another resource unit that forms a downlink transmission opportunity, and thus the station will monitor the aggregated RU.

[0464] Of course, any other order for considering the RUs can be implemented such that the station can decide to stop the analysis when it detects a single RU addressed to it or a group RU dedicated to the group to which the station belongs.

[0465] Finally, if a group RU is found (in the above example, AID=2042, 2045 or 0), step 1360 is executed, where the station reads the determined group RU and therefore receives the aggregated data frame from the AP. All MPDUs forming the A-MPDU received on the determined group RU are provided to the MAC layer (process 805) for further analysis.

[0466] In step 1370, the station compares the MAC address of each aggregated data frame (RA field 210 of each MPDU forming the A-MPDU) with its own MAC address in order to extract one or more data frames addressed to the station, if any, from the received aggregated data frames. Thus, the STA can extract one or more frames carried in RUs intended for multiple STAs that are addressed to this STA based on the RA field of each MPDU frame.

[0467] In contrast to what is done in the AP, the principle of 802.11ax A-MPDU disaggregation for traditional RUs is slightly modified in the station to analyze the MAC address of each MPDU. This is to avoid immediately aborting the deaggregation process when one MPDU is found that does not match the receiver's station address, as is done in the legacy A-MPDU processing. In other words, the aggregation / deaggregation rules for group RUs ("broadcast RUs" in the 802.11ax standard terminology) are slightly modified to support addressing several stations within a single A-MPDU. This mechanism does not require any modification of the 802.11 basic part, since it is limited only to the 802.11ax stations of the present invention that are involved in the limited situation of group RUs.

[0468] The station then keeps only the MPDU or MPDUs with MAC address 210 equal to the station's MAC address, the multicast MAC address of the group the station belongs to, or the broadcast MAC address. In other words, an unassociated station (e.g., the station sent a request to the AP) decodes the group RU (or broadcast RU in 802.11ax standard terminology) and then deaggregates and filters the association management response frames according to the RA MAC address.

[0469] Next, in step 1380, all extracted MPDUs addressed to the station are forwarded to the upper layer stack (eg, application layer 801).

[0470] The stations do not have to acknowledge receipt of the retrieved data frame to the access point (no further steps shown in the figure), so all MU downlink MPDUs transmitted in RUs dedicated to a group of stations include a No-Ack indication.

[0471] In some cases, it is worth acknowledging data frames transmitted via group RUs. However, according to conventional 802.11ax mechanisms, only one station per RU (and therefore also per group RU) can acknowledge receipt of data. This cannot meet the requirement of multiple acknowledgments for group RUs. Therefore, an acknowledgment policy can be realized in which a station sends an acknowledgment for a retrieved data frame only if the retrieved data frame contains the last received aggregated data frame. It means that only the last MPDU in an A-MPDU is explicitly acknowledged by the receiving station (in the MU ACK RU following the MU downlink frame in the same TXOP, according to the 802.11ax standard). As a result, other MPDUs may be implicitly acknowledged by the acknowledgment of the last MPDU. This may result in inaccurate acknowledgments, since some stations may not actually receive their data frames from the AP.

[0472] In the particular case where a not yet associated station receives a response from the AP, an acknowledgement for the elicited response may be transmitted by the receiving station in the next resource unit forming part of the next uplink transmission opportunity granted to the access point for uplink communication from the station, which is assigned to the station not yet associated with the access point (i.e., the next random RU with AID=2045 in the MU uplink TXOP). This acknowledgement scheme is also not efficient in practice, since the not yet associated station may not actually access the random RU even after a short delay. As a result, the AP may schedule a retransmission of the data frame since it does not know that the data frame was received correctly, thereby wasting channel bandwidth.

[0473] To improve network efficiency, this acknowledgement can be further aggregated with any further request management frames in the next RU (e.g., with AID=2045). For example, following that approach, if a probe response frame 320 is received in an MU downlink frame, the station can provide an acknowledgement 330 corresponding to 320 in the next MU uplink transmission 510 along with the next request management frame (here, authentication request frame 340) in an RU with AID=2045. This is to make the association procedure process proceed more quickly for the station. Again, it may take a lot of time (due to contention) before a station that is not yet associated can access the medium in the new random RU.

[0474] FIG. 14 illustrates the advantage of using group RUs with reference to the example situation of FIG. 6 above.

[0475] TXOP#1 is the same as in FIG. 6, in which not yet associated stations STA1 and STA6 send a request management frame to the AP in the RU with AID=2045.

[0476] As is readily apparent from the HE-SIG-B preamble of the MU downlink frame 1420, group AIDs are used, specifically AID=0 (for small frame collections), 2042 (for multicast), and 2045 (for stations not yet associated). As shown above, the HE-SIG-B preamble may first declare RUs for individual stations (here, 2 and 7), then declare group RUs (here, 2042 and 2045), and then declare a group set RU (here, 0), which is dedicated to "all other" associated stations.

[0477] A group RU with AID=2045 is used to carry concatenated MPDU frames addressed to one or more not-yet-associated stations, here a probe response frame targeted to STA1 and a response authentication frame targeted to STA6. In other words, a single RU with AID=2045 in an 802.11ax multi-user frame (HE MU PPDU) concatenates association responses to several not-yet-associated STAs. As a result, consecutive SU transmissions for management frames (630-1 and 630-2 in FIG. 6) are avoided, which simplifies the association procedure for not-yet-associated STAs and makes the network more efficiently used. This is particularly advantageous for managing the association of new stations in a high-density network such as 802.11ax.

[0478] A group RU with AID=2042 is used to carry concatenated MPDU frames addressed to stations belonging to the multicast group, here stations STA5 and STA4. A single 802.11A-MPDU frame is used and carried within a single RU. This avoids RU duplication compared to traditional 802.11ax schemes.

[0479] Group RUs with AID=0 are used to carry concatenated MPDU frames dedicated to multiple associated stations, e.g., to carry small MPDU frames that individually would not efficiently fill an entire RU (even for the smallest band, e.g., 26 tones), or to concatenate small MPDU frames when the limit on the number of RUs (maximum of 9 per 20 MHz band) is already reached. Such concatenation allows to limit padding within the RU, and therefore reduces the latency of small frames compared to traditional 802.11ax schemes.

[0480] As shown, the MU downlink transmission 1420 is followed by an MU ACK period 1440 belonging to the same TXOP#2. For example, an acknowledgment frame 1440 according to the 802.11ax standard may be used, where the acknowledgment for the group AID is not provided or is provided by the station to which the last transmitted MPDU is addressed.

[0481] In some embodiments, the MU downlink frame 1420 is followed by a separate immediate acknowledgment frame in accordance with FIG. 15, described below.

[0482] In these embodiments, each station addressed through the group RU (during MU downlink transmission 1420) obtains an individual UMRS control field 264 from the derived data frame that identifies which response resource unit (1440-A / B / C / D) will be used during MU uplink transmission 1440, and then transmits an acknowledgment frame to the access point via the identified response resource unit.

[0483] This requires the AP to signal in two (or more) aggregated data frames addressed to two respective stations a respective UMRS control field that identifies the response resource to be used by the receiving station in the MU uplink transmission 1440 that follows the MU downlink transmission 1420 to provide a response to the data frame to the access point.

[0484] According to this approach, different UMRS control fields are carried within an (aggregated) MPDU via the same DL group RU.

[0485] Figure 16a illustrates, by means of a flow chart, an improvement of the process of Figure 13a (at the access point) to efficiently provide frame acknowledgment in the group RU case. When unchanged, the same step reference numbers as in Figure 13a are used.

[0486] Thus, as described above, first the AP determines one or more groups of receiving stations along with the corresponding MAC frame to be transmitted (step 1310), and a group RU for the MU downlink transmission 1420 is assigned to each determined group of stations (step 1320).

[0487] As already disclosed, a Group RU can be used to carry association request / response frames intended for at least one unassociated station (Group RU with AID=2045), or to carry multicast frames intended for several receiving stations (Group RU with AID=2042), or to carry an arbitrary collection of packets for several stations (Group Collector RU with AID=0).

[0488] In an embodiment, when selecting a group, the AP may consider the total number of stations that will be addressed in the MU downlink transmission 1420 (through individual and group RUs). In particular, this total number may be less than or equal to the maximum number of acknowledgement RUs that the AP may specify in the MU uplink transmission 1440 for acknowledgment. Preferably, the AP only considers stations that must acknowledge (i.e., are requested to acknowledge) receipt of the data frame, in order to provide a response or ackRU for each station.

[0489] Once a group is selected, the MAC frames to be transmitted for that group are collected (step 1330a).

[0490] The AP must then signal, using the UMRS control field 264, which response RU each station in the group must use to acknowledge its data frame. This is done via steps 1610 and 1611 to signal in two (or more) aggregated data frames addressed to two respective stations, respective UMRS control fields that identify the response resource to be used by the receiving station in the MU uplink transmission 1440 that follows the MU downlink transmission 1420 to provide a response to the data frame to the access point.

[0491] First, in step 1610, the AP determines the number of scheduled RUs required for the next MU uplink communication 1440 based on the number of stations addressed by the frames carried in the group RU of the MU downlink transmission 1420 and other RUs.

[0492] The number of responding RUs for the current group in MU uplink communication 1440 is at most equal to the number of stations in the group.

[0493] This complies with the requirement that a given receiving station should use only one responding RU for the next MU uplink transmission.

[0494] This also prevents a given receiving station from being assigned a response RU if no response (acknowledgement) is expected by the AP. As a result, the AP can only take into account receiving stations that must give a response or acknowledgement, i.e., stations that support UMRS signaling (i.e., if the station has set the UMRS Supported subfield to 1 in the HE MAC Capability Information field of the HE Capability element exchanged with the AP during the association procedure, typically in the probe request frame), and for which the AP expects a response or acknowledgement. This approach reduces the amount of response RUs required. Furthermore, the number of response RUs is limited, which can help increase the number of receiving stations for MU downlink transmission 1420.

[0495] Since the number of associated receiving stations (that must respond) may be different, the AP's configuration of the next MU uplink transmission 1440 for the responding RUs is directly affected: the AP may have to provide a larger or smaller number of responding RUs (one responding RU per DL individual RU, several responding RUs for DL ​​group RUs).

[0496] Thus, the access point can configure the MU uplink transmission 1440 to include a number of response resources based on the number of stations addressed in the MU downlink transmission 1420. In particular, this number of responding RUs can be at least the number of stations that must provide a response to a data frame addressed to them via any resource unit of the MU downlink transmission 1420, but may be the same as the number of stations.

[0497] The AP may also design the MU uplink transmission 1440 such that the requested responding RUs include the entire 20 MHz channel.

[0498] 15 shows an example of RU configuration differences between MU downlink transmission 1420 and MU uplink transmission 1440. Some DL RUs are wider than the next UL response RU.

[0499] For example, 802.11ax supports a maximum number of 9 RUs per 20 MHz channel. Therefore, the basic RU is 26 tones wide. As a result, there can be no more than 10 26-tone response RUs per 20 MHz channel for MU uplink transmission 1440. If a group RU is addressing two stations (assuming it supports acknowledgement for all stations), the maximum number of DL RUs is reduced by one (i.e., there are only 8 RUs in the MU downlink direction, and then 9 response RUs are triggered in the MU uplink direction). As a result, one of the 8 DL RUs can be widened to achieve a 20 MHz band.

[0500] This consideration has little or no impact on the present embodiment, since the Group RU is intended to address several receiving stations and embeds more data frames than the traditional Individual RU. In other words, it is somewhat useful to make the Group RU wider than the Individual RU.

[0501] In some embodiments, the AP may decide not to use one or more DL RUs in the MU downlink direction (e.g., to avoid spreading out some RUs to cover the entire band). The unused RUs in the MU downlink transmission 1420 may be indicated with a specific AID, e.g., 2046, in the HE-SIG-B PHY header. Based on this AID, the station may avoid considering such RUs. This usage may be useful for the AP to avoid sending padding, thus saving power consumption of the AP. As a result, the AP may schedule one used group RU and unused RU(s) in the DL transmission to include the entire frequency band (e.g., 40 MHz) of the response RUs defined for the group RU.

[0502] Next, once the AP has determined a set of available response RUs for the current group, it signals such response RUs to the relevant stations using the UMRS control field 264. This is step 1611. The allocation of the available response RUs to the stations in the group can be done using any allocation scheme (randomly, according to AID order and RU order, etc.).

[0503] In this step, for each receiving station of the group for which a response is desired, a UMRS control field set with the corresponding assigned response RU is inserted in the HE MAC header of at least one data frame addressed to this station (i.e., one MPDU with RA field 210 set to the receiving station's MAC address). When two or more individually addressed MPDU frames are received via the group RU, the UMRS control field in the MPDUs carried in the A-MPDU has the same value for a given receiving station. That is, when several frames addressed to the same STA (identified by RA field set to the STA MAC address) have a UMRS control field, they all have the same UMRS control field value.

[0504] Thus, in the two data frames addressed to the two respective stations of the group, two respective response resource unit information items are inserted that identify the respective response RUs to be used by each receiving station in the MU uplink transmission 1440 that follows the MU downlink transmission 1420, for the stations to provide a response / acknowledgement to the data frames to the access point.

[0505] Once the UMRS information items have been inserted in the various data frames intended for the stations of the group, step 1330b consists of the AP concatenating or aggregating all untransmitted MPDU frames selected in step 1330a into a single A-MPDU to be transmitted via the group RU during MU downlink transmission 1420. This applies, for example, to the group RU with AID=0 in FIG.

[0506] Due to the above-mentioned constraints on the number of receiving stations and the number of responding RUs in the MU downlink transmission 1420, step 1330b can therefore aggregate data frames to be addressed to multiple stations such that the total number of stations addressed via the multiple resource units forming the MU downlink transmission 1420 does not exceed a determined maximum number of stations, where such maximum number is determined by or is the maximum number of basic (26-tone) resource units that can be defined within the MU uplink transmission 1440.

[0507] Next, step 1340 reserves the A-MPDU to be transmitted via the assigned group RU.

[0508] Figure 16b shows, by way of a flow chart, an improvement of the process of Figure 13b (at a station) to perform efficient and immediate frame acknowledgment in the group RU case. When unchanged, the same step reference numbers as in Figure 13b are used.

[0509] After the station determines a group resource unit dedicated to the multiple stations from among the multiple resource units forming the MU downlink transmission 1420 granted by the access point for downlink communication to the station (step 1350), receives aggregated data frames via the determined group resource unit (1360), and extracts one or more data frames addressed to itself from the received aggregated data frames (1370), the station processes the payloads of the extracted data frames, for example by forwarding them to an upper layer stack (step 1380).

[0510] The station must then respond to the received data frame. This can be a simple acknowledgement or response data, as provided by the upper layer stack as a result of payload processing. The response process proceeds through steps 1620-1622.

[0511] In step 1620, stations extracting their data frames via the group RU during MU downlink transmission 1420 obtain the UMRS control field 264 from the MAC header of at least one of the extracted data frames.

[0512] With this information, the station now knows which responding RU should be used in the next MU uplink transmission opportunity 1440 .

[0513] Note that a station may read only the first UMRS control field it finds in a received retrieved data frame intended for it. However, in some embodiments, a station may consider all retrieved data frames to determine what type of traffic data the station must provide a response or acknowledgement for, especially when various data frames may contain data from different traffic classes or queues. In this configuration, a station may therefore construct a multi-TID acknowledgement.

[0514] Once the responding RU is known from the UMRS information, the station can wait for a SIFS (step 1621), which is done when an immediate acknowledgment is required.

[0515] The station then transmits its response or acknowledgement via the responding RU identified in step 1620. This is step 1622.

[0516] As a result, the AP receives various acknowledgements from stations addressed during the MU downlink transmission 1420, including stations addressed via individual RUs and stations addressed via group RUs, via various response RUs of the MU uplink transmission 1440.

[0517] It can be noted that this acknowledgment scheme is highly suitable for stations that are not yet associated. In particular, the UMRS control field 264 does not require any AID, since each receiving station knows that this information derived from its data frame is intended only for itself. This is perfectly suitable for stations that are not yet associated, and have not yet been assigned an AID. Therefore, the proposed approach advantageously utilizes the UMRS format, which does not require any AID, in terms of supporting acknowledgment of association frames exchanged via MU communication.

[0518] Returning to FIG. 15, some advantages of the proposed acknowledgement in the group RU case are explained.

[0519] Conventional acknowledgment through UMRS signaling allows stations STA2, STA7 and STAn receiving a data frame via a DL dedicated RU to send their own acknowledgment via their respective responding RUs. The connection between the UMRS signaling and the responding RUs is shown using a simple arrow.

[0520] According to the aggregation-based approach, two or more stations that are addressed through the same group RU are provided with respective UMRS control fields to find their responding RU.

[0521] In the proposed example, STA3 and STA8 are addressed through a group RU with AID = 0. One MPDU addressed to STA3 has a UMRS control field 264 identifying UL RU 1440-A, and one subsequent MPDU addressed to STA8 has a UMRS control field 264 indicating UL RU 1440-B. The connection between the UMRS signaling and the responding RU is shown here using a dotted arrow.

[0522] As shown, the group RU with AID=0 may be larger (eg, 56-tone RU) compared to the two UL response RUs 1440-A and 1440-B (eg, 26 tones each).

[0523] The same situation occurs for a group RU with AID=2045 carrying an AP response data frame to a station that is not yet associated. As indicated by the dotted arrow, the AP response data frame triggers two UL response RUs 1440-C and 1440-D. In the figure, the AP decides to allocate these two UL response RUs so that they are not consecutive. Moreover, those RUs do not necessarily overlap the same frequency band as the DL group RUs.

[0524] In practice, the allocation of responding RUs can be completely decoupled from the allocation of DL individual or group RUs, with one constraint being that the responding RUs be in the same composite channel for MU downlink OFDMA transmission (indicated in HE-SIG-A field: 20 MHz, 40 MHz, 80 MHz) as the DL individual or group RUs, but not necessarily in the same 20 MHz channel.

[0525] As yet another example, consider a group RU with AID=2042 for transmitting a multicast data frame to STA4 and STA5. Since the data frame is multicast and therefore does not require to be acknowledged, the AP may decide not to include a UMRS control field in the data frame.

[0526] The embodiments of the present invention can be implemented in all 802.11ax compliant APs and non-AP stations. Alternatively, an 802.11ax compliant AP or non-AP station can optionally implement multiple mechanisms of the embodiments of the present invention. For this purpose, supported mechanisms may be declared by the station and / or AP, and the execution of the flowchart according to the embodiments of the present invention can be adapted to or conditional on the supported mechanisms.

[0527] For example, the supported mechanisms may be declared by management frames exchanged during the discovery phase (see FIG. 3). For example, one or more capability bits are added in the 802.11 capabilities exchanged between the AP and the station through the probe request frame 310 (or beacon) and the probe response frame 320 to signal whether a mechanism, a set of mechanisms, or an embodiment is supported by the 802.11ax device. The request management frame may have been received by any preceding MU or SU communication.

[0528] In one embodiment, allowing aggregated MPDUs in the same A-MPDU to be addressable to different stations is considered an optional mechanism. Therefore, it is up to the implementation of the 802.11ax compliant device to support or not support this mechanism. Nevertheless, the device must declare its capability status, for example during the discovery phase. For the mechanism discussed in this embodiment, one capability bit is added, which informs the HE AP which STAs should be considered in the multi-STA A-MPDU aggregation scheme. The capability bit is called "multi-STA aggregation support in broadcast RU". Other names such as "multi-STA aggregation support in group RU", "multi-STA aggregation support", or MSAS capability bit for short, may be used for this capability bit.

[0529] FIG. 17 illustrates an exemplary format of an HE capabilities element 1700 exchanged between a station and an AP and including capability bits according to one alternative embodiment of the present invention.

[0530] According to 802.11ax, an 802.11ax compliant station (also called a high efficiency station, or simply a HE STA) declares itself as a HE STA by transmitting a HE Capability element. The HE Capability element includes several fields that are used to advertise the HE capabilities of the HE STA, not all of which are detailed here. Among those fields is the HE MAC Capability Information field 1710, which includes the number of subfields and reserved bits.

[0531] According to a variant embodiment, a capability bit is added in the HE MAC Capability Information field. Thus, the proposal is to add a "Multi-STA Aggregation Support in Broadcast RU" capability bit in subfield 1721 of the HE MAC Capability Information field 1710. The subfield 1721 can use, for example, bit position B42, which is declared reserved in the 802.11ax standard draft v.2.2. Of course, it should be understood that any other position for the subfield 1721 can be considered in the HE MAC Capability Information field 1710 or in other fields of the HE Capability element 1700.

[0532] The "Multi-STA Aggregation Support in Broadcast RU" (MSAS) subfield may have different interpretations depending on whether the subfield is set by an AP or a non-AP station.

[0533] If the ability is an AP declared ability: - If the MSAS Capability subfield is set to 1, the AP (identified by the BSSID value used in the management response frame or beacon frame that conveys the capability) supports the ability to generate A-MPDUs containing frames addressed to several (different) stations when the A-MPDU is instructed to be transmitted in a downlink RU (group RU) intended for several stations. - If the MSAS Capability subfield is set to 0, then the AP does not support the ability to aggregate in an A-MPDU frame addressed to multiple stations (unless a Broadcast MAC MPDU is aggregated).

[0534] If the capability is a capability declared by the Department: - If the MSAS Capability subfield is set to 1, the station supports reception of A-MPDUs containing frames addressed to downlink RUs intended for several stations (Group RU). - If the MSAS Capability subfield is set to 0, the station does not support the ability to receive MPDUs addressed to it within an A-MPDU containing frames addressed to multiple stations (unless Broadcast MAC MPDUs are aggregated).

[0535] The following table summarizes the definition and encoding of subfield MSAS1721.

[0536] [Table 1]

[0537] FIG. 18a illustrates, by means of a flow chart, the steps performed by an AP when transmitting data to a station.

[0538] Steps 1801 and 1802 relate to informing a station of the capabilities of the AP and receiving the advertised capabilities from the station, respectively. These steps may be performed in any order, and may be performed in an earlier phase, such as the discovery phase, as discussed above.

[0539] In step 1803, the AP constructs one or more A-MPDUs of MAC frames for transmission within the group RU, where the construction of the A-MPDU depends on the capabilities of the AP and / or the capabilities of the receiving stations of the MAC frames to be transmitted, which means that the AP needs to follow certain rules for the construction of the A-MPDU.

[0540] If the AP supports generating A-MPDUs containing frames addressed to several stations, the MPDU address type (individual addressing or group addressing) and address value may be different in A-MPDUs in RUs targeted to several STAs. In such a case, to construct an A-MPDU with MPDU frames addressed to several receivers and carried in a broadcast RU of an HE MU PPDU, the HE AP shall consider only receiver STAs that set the "Multi-STA aggregation support in broadcast RU" subfield to 1 in the HE MAC Capability Information field.

[0541] The HE AP may still consider transmitting an A-MPDU with only MPDU frames addressed to the STA in a DL MU PPDU or in a DL SU PPDU separately for STAs that set the "Multi-STA aggregation support in broadcast RU" subfield to 1. The HE AP still considers transmitting an A-MPDU with only MPDU frames addressed to the STA in a DL MU PPDU or in a DL SU PPDU separately for STAs that set the "Multi-STA aggregation support in broadcast RU" subfield to 0.

[0542] If an AP does not support generating A-MPDUs containing frames addressed to several stations, the HE AP must consider sending A-MPDUs with only MPDU frames addressed to a single STA in a DL MU PPDU or A-MPDUs with only Broadcast MAC frames separately in a Group RU. This also applies if a STA sets its "Multi-STA aggregation support in Broadcast RU" subfield to 1.

[0543] In step 1804, the AP transmits the constructed A-MPDU in the DL group (broadcast) RU.

[0544] FIG. 18b illustrates, by means of a flow chart, the steps performed by a non-AP station when receiving data from an AP.

[0545] Steps 1811 and 1812 relate to informing an AP of the station's capabilities and receiving the AP's advertised capabilities, respectively. These steps may be performed in any order, and may be performed in an earlier phase, such as the discovery phase, as discussed above.

[0546] In step 1813, the station receives the A-MPDU in the DL group (broadcast) RU, and in step 1814, the station extracts the MPDU(s) addressed to it from the A-MPDU depending on the AP capabilities and / or the station capabilities.

[0547] In one embodiment of step 1814, if both the AP and the station have set their "Multi-STA Aggregation Support in Broadcast RU" subfields to 1, the station compares the MAC address of each aggregated data frame (RA field 210 of each MPDU forming the A-MPDU) with its own MAC address in order to extract one or more data frames addressed to the station, if any, from the received aggregated data frames. Thus, the STA can extract one or more data frames addressed to this STA and carried in RUs intended for multiple STAs based on the RA field of each MPDU frame.

[0548] If the AP and / or the station have set their "Multi-STA Aggregation Support in Broadcast RU" subfield to 0, the A-MPDU should not contain MPDUs for different stations (except for broadcast MAC frames). In this case, the station can compare the MAC address of one of the A-MPDUs, preferably the first MPDU, with its own MAC address. If the MAC address matches its own MAC address (or if the MAC address is a broadcast address), then one or more MPDUs contained in the A-MPDU can all be considered as addressed to the station. Therefore, all those MPDUs are extracted for processing by the station. If the MAC address does not match its own MAC address (and if the MAC address is not a broadcast address), it is assumed that the following MPDUs are not destined for the station, and so the extraction (deaggregation) of MPDUs is aborted.

[0549] It should be noted that in one embodiment of a variant, the mechanism allowing aggregated MPDUs in the same A-MPDU to be addressed to different stations is considered optional only for non-AP stations and mandatory for APs. In other words, non-AP stations must still indicate support for receiving A-MPDUs containing frames addressed to several stations in DL broadcast RUs, whereas APs do not need to advertise their capabilities regarding this mechanism, since they will support the mechanism by default. In this variant, the MSAS subfield is added only for capabilities advertised by stations. This variant is advantageous as it gives a good trade-off between system efficiency and cost. In practice, the AP preferably implements the mechanism so that it is valid for all stations of the managed cell, whereas the station may not implement the mechanism so as not to affect the usage of the mechanism for other stations of the same cell.

[0550] FIG. 19 shows an example of a RU configuration between MU downlink transmission 1420 and MU uplink transmission 1440 (see FIG. 14).

[0551] The configuration example identified by 1904 illustrates a case in which the AP considers transmitting an A-MPDU with only MPDU frames addressed to STA7 separately in the DL MU PPDU since STA7 has set the "Multi-STA Aggregation Support in Broadcast RU" subfield to 0.

[0552] The configuration example identified by 1901 illustrates the case where STA2 has set the "Multi-STA Aggregation Support in Broadcast RU" subfield to 1, but the AP considers transmitting the A-MPDU with only the MPDU frames addressed to STA2 separately in the DL MU PPDU.

[0553] The example configurations identified by 1902 and 1903 show the case where the AP always forms one group RU with a given AID that appears only once, in which the group RU with AID=2045 is first transmitted in DL MU PPDU 1020a, and then the group RU with AID=2045 is further transmitted in a subsequent DL MU PPDU 1420b.

[0554] The configuration example identified by 1905 shows an alternative embodiment to the above description regarding Figures 18a and 18b. In this alternative embodiment, the AP aggregates MPDUs in the same A-MPDU addressed to different stations, while one of the receiving stations does not support the aggregation mechanism (the station's MSAS capability subfield is set to 0). In this variant embodiment, the AP constructs the A-MPDU by placing the MPDU(s) for the station that does not support the option first in the aggregation of the A-MPDU. As a result, the station that is the receiving station of the first MPDU(s) (and does not support the aggregation capability) will retrieve the first MPDU(s) since the MAC address comparison results in a match, and the station can then stop retrieving subsequent MPDUs as soon as an MPDU intended for a different station is found, or retrieve all subsequent MPDUs and discard the MPDUs with non-matching addresses afterwards.

[0555] In the example configuration identified by 1905, the first MPDU frame(s) appearing in a multi-station A-MPDU according to one embodiment of the present invention may be directed to a station that has indicated non-support of multi-station aggregation capability by setting bit 1721 to 0. This station handles the decoding of those first MPDU(s) and subsequently ceases upon receiving an MPDU intended for station STA8. In that example, station STA8 is the station that has indicated support of multi-station aggregation capability by setting bit 1721 to 1 and may receive the subsequent aggregated MPDU frame(s).

[0556] When one or more MPDUs with different RA values ​​are aggregated with other MPDUs in an A-MPDU, the following ordering rules apply: The MPDU(s) for one non-AP station that does not support the "Multi-STA Aggregation in Broadcast RU" feature (if present) shall be the first MPDU(s) in the A-MPDU.

[0557] Figure 20 illustrates by means of a flow chart an embodiment according to the invention of the process of constructing an A-MPDU (e.g. step 1803 of Figure 18a) performed by an AP taking into account the MSAS capabilities subfield value signalled by the station. In this example, it is assumed that the AP supports a mechanism allowing aggregated MPDUs within the same A-MPDU to be addressed to different stations, either by default or after the AP signals the station with the MSAS capabilities subfield set to 1.

[0558] In step 2001, a list of receiving stations having MAC frames to be transmitted by the AP in a downlink transmission is obtained, after which the receiving stations are processed sequentially (looping in step 2002). The loop can continue until all receiving stations have been processed (i.e., the end of the list is reached), after which one or more constructed A-MPDUs (embedding the MAC frames) are transmitted in the respective one or more allocated DL RUs (step 2016). In one variant, the loop can be stopped once one A-MPDU has been constructed, and the A-MPDU can be transmitted in one allocated DL RU. The process is then repeated in step 2001 with the updated list of receiving stations, and another DL RU is used for transmission.

[0559] In step 2003 it is checked whether the station (currently selected in the list) advertised the MSAS capabilities subfield set to one.

[0560] If the check is positive (yes to the test in step 2003), the AP (scheduler) decides in step 2004 whether to use a broadcast RU for the station. This means that the AP decides whether it is willing to group different receiving stations that have MAC frames to transmit in the same broadcast RU (hence an A-MPDU aggregating MPDUs for different receiving stations). The situation in which it may be advantageous to group different receiving stations may be similar to the exemplary situation described for step 1310 in Fig. 13a. For example, if a large amount of data is pending for transmission to a given station, it is preferable to allocate a dedicated RU for the station. Another example is the case where a station is allocated a dedicated RU because there is no more space left in the group RU. By allocating a dedicated RU in the same HE MU PPDU, it is possible to avoid waiting for another HE MU PPDU and therefore gain time (especially when it is not allowed to allocate multiple group RUs in the same HE MU PPDU).

[0561] If it is determined in step 2004 that a broadcast RU will be used for the station, then, if necessary, a broadcast RU is allocated in step 2005. Step 2005 is optional since a broadcast RU may already be allocated. If a broadcast RU has not yet been allocated, or if there is no more space left in the previously allocated broadcast RU, then it may be necessary to allocate a new broadcast RU.

[0562] In step 2006, one or more MAC frames intended for the station are selected for insertion into the current A-MPDU.

[0563] Optionally, the AP must signal, using a UMRS control field, which response RU the station must use to acknowledge the MAC frame(s). This is done through steps 2007 and 2008 to signal, in a selected MAC frame addressed to the station, a UMRS control field that identifies the response resource unit to be used by the station in a MU uplink transmission following the MU downlink transmission to provide a response to the data frame to the access point. Steps 2007 and 2008 are similar to steps 1610 and 1611 of FIG. 16a and are not performed if no acknowledgement is required, e.g., because there are no aggregated MAC frames.

[0564] The selected MAC frame(s) are then aggregated in an A-MPDU with other MAC frame(s), possibly for different receiving stations, in step 2009. In some cases, aggregation may be limited to one MPDU, i.e. the A-MPDU contains a single MPDU.

[0565] If the check is negative (test no in step 2003), or if in step 2004 it is determined that no broadcast RU is used for the station, step 2010 is executed.

[0566] In step 2010, it is determined whether the station is already associated with the AP. If the station is already associated, a single-destination RU (having the station's AID) is allocated (step 2011). If the station is not associated, a broadcast RU (e.g., having AID=2045) is allocated (step 2012).

[0567] Then, one or more MAC frames intended for the station are selected (step 2013) and added to the A-MPDU (step 2016).

[0568] Similar to steps 2007 and 2008, steps 2014 and 2015 can be optionally implemented to signal, using the UMRS control field, which responding RU the station must use to acknowledge its MAC frame(s). This is particularly relevant in the case of an unassociated station (not yet assigned an AID).

[0569] It should be noted that the branches of steps 2005-2009 and the branches of steps 2010-2016 may be performed in parallel. It should also be noted that it is not necessary to have both branches in the process, only one of them needs to be performed. For example, only the branches of steps 2005-2009 can be performed if the AP uses a broadcast RU to all stations, or only the branches of steps 2010-2016 can be performed if the AP does not support a mechanism that allows aggregated MPDUs in the same A-MPDU to be addressed to different stations.

[0570] When one or more MPDU frames with different RA values ​​are aggregated with other frames in an A-MPDU (steps 2009 and / or 2016), the following ordering rules may apply: The MPDU frame(s) for one non-AP station that does not support the "Multi-STA Aggregation in Broadcast RU" feature (if present) is the first MPDU frame(s) in the A-MPDU.

[0571] In one embodiment, matching on RU profiles between uplink RUs already used by a station in MU uplink transmission and downlink RUs that the AP will use in MU downlink transmission to provide a frame to the same station (see Figures 10a to 10c) is considered as an optional mechanism.

[0572] For the mechanism discussed in this embodiment, one capability bit is added to reflect the support of this mechanism. The capability bit is called "UL / DL Matching Profile Support", or UMPS capability bit for short.

[0573] For example, a UMPS capability bit can be added to the HE MAC capability information field, similar to the MSAS capability bit in the reserved subfield of field 1710 (see FIG. 17).

[0574] Note that it can be assumed that only one of the features "Multi-STA Aggregation Support in Broadcast RU" and "UL / DL Matching Profile Support" can be implemented in an 802.11ax station. In this case, only one capability bit (e.g., bit B42) is added to signal the one feature that is implemented. Alternatively, it may be allowed to implement both features in an 802.11ax station. In this case, two capability bits (e.g., bits B42 and B43) are added.

[0575] Thus, for example, storing one or more allocation scheme characteristics defining an uplink RU for use when identifying a downlink RU for an unassociated station may only be performed by 802.11ax stations that have advertised the UMPS capability bit set to 1.

[0576] 21 illustrates by means of a flow chart an embodiment according to the invention of the process executed by an AP taking into account the UMPS capabilities subfield value advertised by a non-associated station during the discovery phase. In this example, it is assumed that the AP supports the UL / DL matching profile mechanism, after which the AP advertises the station with the UMPS capabilities subfield set to 1, or by default.

[0577] In the following description, a predefined identifier value of 2045 is chosen to designate the MU DL RU reserved for unassociated stations. Of course, this value is given for illustrative purposes only, and any other predefined value or signaling means may be adopted.

[0578] In step 2101, the AP determines whether there is a list of pending frames (eg, authentication or association response management frames) waiting to be transmitted to an unassociated station.

[0579] If the list of untransmitted frames is not empty, it is determined in step 2102 whether the list contains one or more broadcast frames. If at least one broadcast frame is found, the broadcast frame is selected for transmission in step 2103 (more broadcast frames may be selected for transmission in the same RU). A single downlink RU with AID=2045 is incorporated into the MU DL frame containing the selected frame (step 2104). The downlink RU can be located anywhere within the MU DL frame (HE MU PPDU). The MU DL frame may be constructed at the time of incorporating the downlink RU with AID=2045, or may be formed earlier by the AP's module 805, for example, at the time other downlink RUs destined for already associated stations are defined.

[0580] If the list does not contain a broadcast frame (test 2102 is negative), the number of unassociated stations that are recipients of the untransmitted frame is determined in step 2107. If only one unassociated recipient is found, one or more frames intended for the station are selected (step 2109) and incorporated into the MU DL frame (step 2104). If the number of unassociated is greater than or equal to one (test 2107), further processing is performed based on the UMPS capabilities subfield signaled by the station.

[0581] For example, if it is determined in step 2108 that all stations have the UMPS capabilities subfield set to 0 (do not support the feature), then step 2109 is performed by considering frames from only one of those stations (in the current iteration of the flowchart).

[0582] If test 2108 is negative (at least one station supports the mechanism), in step 2110, one or more frames intended for stations with the capability subfield set to 1 are selected from the list. Preferably, all response frames following the reception of a request frame received on an uplink RU from an unassociated station are selected for transmission to the corresponding unassociated station. The design of the downlink RU with AID=2045 for the response frame can be based on at least one allocation scheme characteristic of the uplink RU used by the unassociated station. Naturally, the response frame for a particular unassociated station will be transmitted via a downlink RU that matches the allocation scheme characteristic of the uplink RU used by the same station when requesting the AP.

[0583] The number of frames selected in step 2110 may be limited to the number of available downlink RUs, e.g., the number of available downlink RUs to be assigned to AID=2045. In particular, one (e.g., the first) RU among the available RUs to be assigned to AID=2045 may be reserved for not yet associated stations that do not support the mechanism, i.e., have their UMPS capability subfield set to 0 (see step 2112).

[0584] In step 2111, one or more downlink RUs with AID value 2045 are incorporated into the MU DL frame to form the corresponding selected frame. The MU DL frame may be pre-constructed or constructed at the time of construction. The incorporated downlink resource unit(s) with AID=2045 match the allocation scheme characteristics stored for the corresponding unassociated station (i.e., each downlink RU matches the allocation scheme characteristics of the uplink resource units used by the station to transmit the frame in the MU uplink transmission).

[0585] Optionally, in step 2112, one RU with AID=2045 is allocated to a predetermined position, e.g., the first position, within the same MU DL frame to contain one or more frames intended for unassociated stations with the capabilities subfield set to 0, if any.

[0586] The MU DL frame is transmitted by the AP in step 2105. Finally, in step 2106, the list of untransmitted frames is updated by removing the selected frames that have been transmitted (and acknowledged), and the steps of the flowchart are repeated from step 2101.

[0587] In another embodiment according to the invention (not shown) of the process performed by the AP, it is assumed that the UL / DL matching profile mechanism is supported by both the AP and all non-AP stations associated with this AP (either by default or determined according to the advertised capabilities of the involved 802.11ax devices).

[0588] In this embodiment, the flow chart of FIG. 21 can be modified by removing test step 2108 and optional step 2112 and modifying steps 2110 and 2111. If the number of unassociated stations is greater than or equal to two (test 2107), frames intended for unassociated receiving stations are selected from the list (modified step 2110). In modified step 2111, downlink RUs with AID value 2045 are incorporated into the MU DL frame to form the corresponding selected frame. The MU DL frame is constructed in advance or at the time of incorporation. The incorporated downlink resource units with AID=2045 match the allocation scheme characteristics respectively stored for the corresponding unassociated stations (i.e., each downlink RU matches the allocation scheme characteristics of the uplink resource units used by the station to transmit the frame in the MU uplink transmission).

[0589] Although the present invention has been described above with reference to specific embodiments, the present invention is not limited to these specific embodiments, and modifications that are within the scope of the present invention will be apparent to those skilled in the art.

[0590] The above description focuses on RUs that are allocated in the frequency domain. Variations can also be considered to have RUs that are allocated in the time domain instead of or in combination with frequency-based allocation. In either case, allocation scheme characteristics that describe a particular RU can be obtained from the allocation scheme used.

[0591] With reference to the above exemplary embodiments, many further modifications and variations will occur to those skilled in the art. It should be noted that the above exemplary embodiments are given by way of example only and are not intended to limit the scope of the present invention, which is defined only by the appended claims. In particular, different features from different embodiments can be interchanged as necessary.

[0592] In the claims, the term "comprises" does not exclude other elements or steps and an unspecified number includes the singular and the plural. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be used to advantage.

Claims

1. A wireless communication method in a wireless network including an access point and at least one station, comprising: receiving a multi-user PPDU (Physical layer Protocol Data Unit) of the IEEE 802.11 standard series from the access point, the PPDU including a preamble including a plurality of STA-ID subfields indicating an allocation of a plurality of downlink resource units for a multi-user downlink transmission transmitted by the access point using an AID (Association ID); determining, from the plurality of downlink resource units, downlink resource units corresponding to a STA-ID subfield in which a value corresponding to a specific AID reserved for stations not associated with the access point is stored as downlink resource units allocated to the non-associated stations; Including, The value corresponding to the specific AID does not identify a specific station among stations not associated with the access point, and the value corresponding to the specific AID is 2045; receiving aggregated data frames from the access point on downlink resource units determined to be downlink resource units allocated to the unassociated stations, the aggregated data frames being directed to the unassociated stations and not directed to the associated stations.

2. The wireless communication method of claim 1, characterized in that at least one STA-ID subfield among the plurality of STA-ID subfields stores a value corresponding to an AID that identifies a specific station associated with the access point, and the plurality of downlink resource units includes at least one downlink resource unit that is assigned in correspondence with the value corresponding to an AID that identifies a specific station associated with the access point.

3. 3. The wireless communication method according to claim 1, wherein the aggregated data frames from the access point include at least a probe response or an authentication response.

4. 4. The wireless communication method according to claim 1, further comprising: before decoding the aggregated data frames received in downlink resource units determined to be downlink resource units allocated to the non-associated stations, checking whether the data frames are addressed to the station.

5. 1. A method for wireless communication in a wireless network including an access point and at least one station, comprising: The IEEE 802.11 series of standards includes a multi-user PPDU (Physical layer Protocol Data Unit) (MU) that includes multiple STA-ID subfields that indicate the allocation of multiple downlink resource units (AIDs) for multi-user downlink transmission. generating an MU PPDU (Multiple MU PPDUs), wherein at least some of the downlink resource units are destined for unassociated stations by storing a value corresponding to a particular AID in at least one STA-ID subfield of the plurality of STA-ID subfields, the value corresponding to the particular AID not identifying a particular one of the stations not associated with the access point, the value corresponding to the particular AID being 2045; and generating the MU PPDU carrying aggregated data frames destined for the unassociated stations and not destined for associated stations on downlink resource units allocated to the unassociated stations that are associated with the value corresponding to the particular AID; transmitting the generated MU PPDU; 13. A wireless communication method comprising:

6. 6. The wireless communication method according to claim 5, wherein, in the generating step, when the access point has both data to be transmitted to a non-associated station and data to be transmitted to an associated station, a value corresponding to an AID identifying a specific station associated with the access point is stored in at least one STA-ID subfield among the plurality of STA-ID subfields, and an aggregated second data frame directed to the specific station is further stored in a downlink resource unit among the plurality of downlink resource units that is assigned in association with the AID identifying the specific station.

7. The wireless communication method according to claim 5 or 6, wherein the aggregated data frames include at least a probe response or an authentication response.

8. A communication device operating as a station not associated with an access point in a wireless network including an access point and at least one station, comprising: A receiving means for receiving from the access point an IEEE 802.11 standard series MU (multi-user) PPDU (Physical layer Protocol Data Unit) including a plurality of STA-ID subfields as a preamble, the STA-ID subfields indicating an allocation of a plurality of downlink resource units used for a multi-user downlink transmission transmitted by the access point using an AID (association ID); A determination means for determining, from the plurality of downlink resource units, a downlink resource unit corresponding to a STA-ID subfield in which a value corresponding to a specific AID reserved for a station not associated with the access point is stored, as a downlink resource unit allocated to the non-associated stations; Equipped with The value corresponding to the specific AID does not identify a specific station among stations not associated with the access point, and the value corresponding to the specific AID is 2045; The receiving means receives aggregated data frames from the access point on downlink resource units that the determining means determines to be downlink resource units allocated to the unassociated stations, the aggregated data frames being directed to the unassociated stations and not directed to the associated stations.

9. A communication device operating as an access point in a wireless network including an access point and at least one station, comprising: A generating means for generating a multi-user PPDU (Physical layer Protocol Data Unit) of the IEEE 802.11 standard series including a plurality of STA-ID subfields indicating an allocation of a plurality of downlink resource units used for multi-user downlink transmission using an AID (Association ID); a transmitting means for transmitting the generated MU PPDU; Equipped with the generating means stores a value corresponding to a specific AID reserved for stations not associated with an access point in at least one STA-ID subfield of the plurality of STA-ID subfields, thereby indicating that at least some of the plurality of downlink resource units are directed to unassociated stations, and generates the MU PPDU such that aggregated data frames directed to the unassociated stations and not directed to associated stations are transmitted on downlink resource units allocated to the unassociated stations, the downlink resource units being associated with the value corresponding to the specific AID; A communication device characterized in that the value corresponding to the specific AID does not identify a specific station among stations that are not associated with an access point, and the value corresponding to the specific AID is 2045.

10. A program for causing a computer to execute the wireless communication method according to any one of claims 1 to 4.

11. A program for causing a computer to execute the wireless communication method according to any one of claims 5 to 7.

Citation Information

Patent Citations

  • Radio communication device and radio communication method

    JP2017055399A