Managing EDCA parameters with low latency reliable traffic

[0001] This application is the National Phase entry of PCT Application No. PCT/EP2021/086286, filed on Dec. 16, 2021 and titled “MANAGING EDCA PARAMETERS WITH LOW LATENCY RELIABLE TRAFFIC”, which claims the benefit under 35 U.S.C. § 119(a)-(d) of United Kingdom Patent Application No. 2020431.9, filed on Dec. 22, 2020 and entitled “MANAGING EDCA PARAMETERS WITH LOW LATENCY RELIABLE TRAFFIC”. The above cited patent applications are incorporated herein by reference in their entireties.

[0002] The invention relates to the technical field of wireless communication networks, and more particularly methods and devices for transmitting Low Latency Reliable Service (LLRS) data traffic in Extremely High Throughput (EHT) systems.

[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Examples of such multiple-access networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA) networks.

[0004] The 802.11 family of standards adopted by the Institute of Electrical and Electronics Engineers (IEEE®) provides a great number of mechanisms for wireless communications between stations.

[0005] With the development of latency sensitive applications such as online gaming, real-time video streaming, virtual reality, drone or robot remote controlling, better low latency and robustness requirements and issues need to be taken into consideration. For instance, 99.9% of latency sensitive packets should be delivered to the end equipment within a 2 ms latency.

[0006] Such problematic issues are currently under consideration by the IEEE 802.11 working group as a main objective to issue the next major 802.11 release, known as 802.11 be or EHT for “Extremely High Throughput”.

[0007] Low latency reliable services, LLRS, have been defined as targets of such main objective. LLRSs are services provided to a higher layer traffic stream that prioritize and deliver MSDUs (data units) within a worst-case latency budget with a given reliability/packet delivery ratio (PDR) and low jitter.

[0008] For instance, the 802.11be Project Authorization Request (PAR) targets a worst-case latency of 5 ms for realtime gaming.

[0009] Some low latency, LL, measures are being studied in order to prioritize LLRS traffic within a BSS (Basic Service Set) with a view of meeting QoS constraints.

[0010] Some LL measures, passive measures, may be applied by non-AP stations that do not participate to the 10LLRS traffic (passive stations), with a view of reducing their impact on the network. An example is provided in the IEEE 802.11-20/1046r2 document where a regular non-AP station shall stop its transmission opportunity, TXOP, before a protected/restricted TWT service period (for LLRS traffic) starts. The LLRS traffic transmission may thus take place without waiting the end of the pending TXOP, hence ensuring low latency.

[0011] However, non-AP stations that have no LLRS capability, e.g. legacy non-AP stations complying with one of the previous IEEE 802.11 standard specification including 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac or 802.1ax, may coexist with LLRS capable stations in the same BSS or at least operate over the same wireless medium (e.g. 20 MHz channel). Such LLRS not-capable non-AP stations cannot give the wireless medium back, by stopping an ongoing TXOP. This dramatically impacts the latency performance of the network as a LLRS-capable non-AP station must wait the whole ongoing TXOP, sometimes longer than the required latency, before accessing the medium.

[0012] An efficient network management is thus required to improve latency for LL reliable services.

[0013] A proposed key issue to improve latency is to guarantee the LLRS capable non-AP stations have often enough opportunities to access the wireless medium, given latency requirements.

[0014] This objective may be achieved by adapting the length of the TXOP, should LLRS data traffic occurring on the wireless medium.

[0015] In this respect, the present invention thus proposes a communication method in a wireless network, comprising at an access-point, AP, managing one or more Basic Service Sets, BSSs:

• • [0016] setting Enhanced Distributed Channel Access, EDCA, parameters for a first BSS (i.e. EDCA parameters to be applied by non-AP stations of the first BSS to access a wireless medium and transmit frames), and
  • [0017] upon detecting low latency reliable service, LLRS, activity in the one or more BSSs, modifying the EDCA parameters for the first BSS.

[0018] The AP is thus able to detect LLRS activity in one of the BSSs it manages and responsively to modify the communication parameters of the stations in one (or more) BSS. Consequently, by choosing appropriate modified communication parameters for the first BSS, the AP can force the non-AP stations to limit their TXOP over time, hence increasing the access opportunities on the wireless medium for the LLRS capable stations.

[0019] Optional features of embodiments of the invention are defined in the appended claims. Some of these features are explained here below with reference to a method, while they can be transposed into device features.

[0020] In some embodiments, the modified EDCA parameters includes a modified Transmission Opportunity, TXOP, limit parameter that defines a maximum duration of a TXOP. The AP thus directly controls the maximum duration the LLRS not-capable stations of the first BSS are allowed to reserve the wireless medium. The AP may thus guarantee LLRS capable stations will have new medium access opportunities with a minimum frequency corresponding to the prescribed maximum duration.

[0021] In particular embodiments, the modified TXOP limit parameter is lower than the TXOP limit parameter of the EDCA parameters before modification. This aims at reducing the maximum duration of an access to the wireless medium by the non-AP station of the BSS.

[0022] For instance, the (lower) TXOP limit parameter may be one from:

• • [0023] half a value of a worst-case latency budget for LLRS data traffic as defined in the document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6, for instance the lowest non-zero value,
  • [0024] a TXOP limit value from table 9-137 of IEEE 802.11 Standard®, version 2016, or from table 8-105 of IEEE 802.11 Standard®, version 2012, that is lower than a worst-case latency budget for LLRS data traffic as defined in the document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6,
  • [0025] a ratio between a worst-case latency budget for LLRS data traffic as defined in the document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6 and a number that is based (e.g. identity) on a number of non-AP stations having no LLRS capability (i.e. not implementing LLRS) in the first BSS,
  • [0026] value 0, i.e. restricting the TXOP to the transmission of a single MAC service data unit, MSDU, or management frame,
  • [0027] a value equal to 1.024 ms that meets the requirements of the above-cited document “IEEE 802.11 Real Time Applications TIG Report” while limiting the impact on the station throughput when there is LLRS activity,
  • [0028] a value equal or lower than Delay Bound values indicating, in TSPEC information elements managed by the AP and received from LLRS capable non-AP stations, maximum amounts of time to complete successful transmissions, and
  • [0029] a value equal or lower than ratios, each between a Delay Bound value indicating, in a TSPEC information element managed by the AP and received from a LLRS capable non-AP station, a maximum amount of time to complete a successful transmission and an integer N increased from 1 in case of retransmission policy.

[0030] In some embodiments, the TXOP limit parameter has the same value for different access categories of traffic data. This eases the management of the TXOP duration when LLRS activity is running in the network.

[0031] In variants, the lower TXOP limit parameter has different values for different access categories of traffic data. This allows keeping QoS for legacy (i.e. not LLRS) communications.

[0032] In some embodiments, the method further comprises, upon detecting an end of the LLRS activity in the one or more BSSs, restoring (i.e. modifying back) the set EDCA parameters for the first BSS. That means the AP resets the first BSS with the previously used EDCA parameters. Of course, the AP may use another and new set of EDCA parameters, for instance due to changes in the network. Therefore, more generally, the AP sets new EDCA parameters with a higher TXOP limit parameter (than the modified one used when LLRS data traffic exists).

[0033] In some embodiments, detecting LLRS activity in the one or more BSSs includes detecting LLRS activity in the first BSS. This means LLRS capable and not-capable stations coexist in the same BSS. The adaptation of the EDCA parameters therefore impacts both types of non-AP stations.

[0034] In variants, detecting LLRS activity in the one or more BSSs includes detecting LLRS activity in another BSS managed by the AP than the first BSS. In that case, the AP advantageously only degrades the EDCA parameters (TXOP limit) for the not-LLRS BSS. Long TXOP may survive in the other BSS dedicated to LLRS data traffic, since the LLRS capable stations are able for instance to interrupt or stop an on-going TXOP, should a LLRS transmission be starting. In other words, EDCA parameters for the other BSS remain unchanged upon detecting the LLRS activity.

[0035] In some embodiments, detecting LLRS activity in the one or more BSSs includes detecting one or more criteria from:

• • [0036] receiving LLRS capability for a non-AP station in the one or more BSSs. This means the AP may consider there is LLRS activity as soon as it is aware a LLRS capable station is present (associated with the AP) in the network,
  • [0037] exchanging LLRS data traffic (i.e. UpLink or DownLink traffic) with a non-AP station in the one or more BSSs, preferably data traffic carrying a predefined Traffic Identifier or of a predefined access category (e.g. AC_VI or AC_VO). Here the AP considers there is LLRS activity as long as it is involved in LLRS data traffic exchanges,
  • [0038] receiving, from a non-AP station, a message signaling LLRS data traffic requirements or needs, for instance a TSPEC message with a specified latency lower than a predefined TXOP limit (e.g. the TXOP limit set in the EDCA parameters of the BSS).

[0039] Conversely, detecting an end of the LLRS activity may correspond to the disassociation of all the LLRS capable non-AP stations from the AP, the end of a LLRS data traffic exchange with non-AP stations or the end of stations' needs or requirements in terms of LLRS.

[0040] In some embodiments, setting the EDCA parameters for the first BSS includes broadcasting a beacon frame including the EDCA parameters. In variants, setting the EDCA parameters for the first BSS includes sending a probe response frame including the EDCA parameters to a probe requesting non-AP station.

[0041] In some embodiments, modifying the EDCA parameters for the first BSS includes broadcasting a beacon frame including the modified EDCA parameters. The AP thus broadcasts the new EDCA values to all the non-AP stations of the first BSS, for the latter to apply the modified parameters.

[0042] In some embodiments, the EDCA parameters for the first BSS includes legacy EDCA parameters and Multi-User EDCA parameters temporary substituting the legacy EDCA parameters for a non-AP station of the first BSS when the non-AP station is scheduled by the AP in a multi-user transmission. The present invention thus impacts the TXOP length whatever the station's state.

[0043] The objective mentioned above may also be achieved by directing the non-AP stations to appropriate BSSs, either dedicated to LLRS traffic data or not.

[0044] In this context, the method may further comprise, at the AP, transmitting, to a non-AP station, an association-related management frame refusing an association of the non-AP station with the first BSS or disassociating the non-AP station from the first BSS, wherein the association-related management frame includes a code indicating another BSS managed by the AP is available. Thanks to the code, the AP may redirect the non-AP station to a BSS corresponding for instance to its capabilities.

[0045] Better management of the transmissions by the stations can be achieved. Indeed, modified EDCA parameters (reduced TXOP limit) may be used for the LLRS not-capable stations (grouped within the same BSS) to reduce their transmission times. Furthermore, conventional EDCA parameters (hence TXOP limit) may be used for the LLRS capable stations (grouped within the same BSS) to offer longer legacy contention free TXOPs, as long as they are able to interrupt them (through LL active measures) and then allow LLRS transmissions to take place.

[0046] The use of such a code may be implemented alone, regardless of modifying the EDCA parameters as mentioned above. To that end, the invention may also concern a communication method in a wireless network, comprising at an access-point, AP:

• • [0047] transmitting, to a non-AP station, an association-related management frame refusing an association of the non-AP station with a first Basic Service Set, BSS, managed by the AP or disassociating the non-AP station from the first BSS, wherein the association-related management frame includes a code indicating another BSS managed by the AP is available.

[0048] Conversely, a communication method in a wireless network may comprise at a non-access-point, non-AP, station:

• • [0049] receiving, from an AP, an association-related management frame refusing an association of the non-AP station with a first Basic Service Set, BSS, managed by the AP or disassociating the non-AP station from the first BSS, wherein the association-related management frame includes a code indicating another BSS managed by the AP is available.

[0050] In some embodiments, the method may further comprise, at the AP:

• • [0051] receiving capabilities from the non-AP station,
  • [0052] determining whether a capability of the non-AP station matches a capability of the first BSS with respect to a low latency reliable service, LLRS,
  • [0053] wherein transmitting the association-related management frame is responsive to determining no match.

[0054] The code thus warns the station it is not compatible with the first BSS, but another more-compatible BSS exists. Of course, the AP may authorise the association with the first BSS, should the capabilities between the station and the BSS match.

[0055] For instance, the non-AP station may be LLRS capable and the first BSS be dedicated (i.e. restricted) to LLRS not-capable non-AP stations, i.e. to non-LLRS data traffic. In that case, the code thus indicates that the first BSS is dedicated to low latency reliable service, LLRS, not-capable non-AP stations and another BSS dedicated to LLRS capable non-AP stations that is managed by the AP is available for the LLRS capable station.

[0056] To the opposite, the non-AP station may be not LLRS capable and the first BSS be dedicated to LLRS capable non-AP stations. In this opposite case, the code indicates that the first BSS is dedicated to low latency reliable service, LLRS, capable non-AP stations and another legacy BSS dedicated to LLRS not-capable non-AP stations that is managed by the AP is available for the LLRS not-capable station.

[0057] In some embodiments, the method further comprises, at the AP, initiating the other BSS responsive to receiving a LLRS capability from the non-AP station. Preferably, the other BSS is, in this case, a LLRS capable BSS (i.e. dedicated for LLRS data traffic). Hence, upon having a first LLRS capable station, the AP decides to implement a dedicated BSS, to ensure an appropriate management of the EDCA parameters (as described above) for the LLRS not-capable stations. The LLRS capable stations may then be directed to this newly initiated BSS, using transmission of the above code.

[0058] In other embodiments, the method further comprises, at the AP upon detecting LLRS activity in the network, restricting the first BSS to LLRS capable non-AP stations or restricting the first BSS to LLRS not-capable non-AP stations. In this configuration, the AP may implement a BSS without any constraint, and decide to restrict it to LLRS capable stations only (or not-capable). In this case, the LLRS not-capable (or capable) stations may then be directed to another BSS, using transmission of the above code.

[0059] In some embodiments, the method further comprises, at the non-AP station after the receiving, transmitting an association request to the AP to associate with another BSS managed by the AP. Conversely, the method further comprises, at the AP after the transmitting, receiving an association request from the non-AP station to associate with another BSS managed by the AP. In this way, the AP succeeded in redirecting the non-AP station to a more appropriate BSS, meaning a capability of the non-AP station preferably matches a capability of the other BSS with respect to LLRS.

[0060] To have knowledge of the various BSSs available, the method may further comprise, at the non-AP station, receiving from the AP one or more beacon frames advertising the first BSS and the other BSS. The beacon frame may be a multi-BSS beacon frame sent by the transmitted AP and advertising of multiple (e.g. all) BSSs instantiated by the AP. This allows the non-AP station to efficiently find another appropriate BSS, with a view of associating with it.

[0061] Of course, the AP may manage various BSSs and perform the above steps with respect to various non-AP stations in the BSSs, for instance to try to have the LLRS capable stations in dedicated BSSs and the LLRS not-capable stations in other BSSs.

[0062] The objective mentioned above may also be achieved by controlling Direct Link (DiL) or Peer-to-peer (P2P) with adapted TXOP lengths.

[0063] In this respect, the present invention also proposes a communication method in a wireless network, comprising at a non-access-point, non-AP, station associated with a first Basic Service Set, BSS, managed by an AP:

• • [0064] receiving Enhanced Distributed Channel Access, EDCA, parameters for the first BSS, the EDCA parameters including a TXOP limit parameter that defines a maximum duration of a transmission opportunity, TXOP, within the first BSS. The station thus belongs to a BSS and is aware of transmission parameters to respect when communicating within the BSS,
  • [0065] negotiating, based on the TXOP limit parameter, a duration of TXOP with another non-AP station for direct link, DiL, transmission, and
  • [0066] performing a DiL transmission with the other non-AP station.

[0067] In that way, although the DiL transmission does not take place within the first BSS but over the same wireless medium as the first BSS, the (P2P) non-AP station forces the other P2P station to limit its TXOP duration to the current requirements provided by the AP. Hence, the latency impacted by the P2P transmissions is still control by the AP. Indeed, the latter may adapt the EDCA parameters (incl. TXOP limit) as mentioned above, depending on whether LLRS activity is sensed or detected.

[0068] In some embodiments, the other (P2P) non-AP station is a non-AP station un-associated with the AP in the first BSS. The invention thus controls any DiL transmission involving a non-AP station associated with the AP.

[0069] In some embodiments, negotiating the TXOP duration includes receiving a TXOP duration from the other non-AP station and replying with a reduced TXOP duration given the TXOP limit parameter. The non-AP station associated with the AP thus takes control over the other P2P (un-associated) station.

[0070] Correlatively, the invention also provides a wireless communication device comprising at least one microprocessor configured for carrying out the steps of any of the above methods.

[0071] 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 wireless device, causes the wireless device to perform any method as defined above.

[0072] At least 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 embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be 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 in the medium.

[0073] Since the present invention can be implemented in software, the present invention can be embodied as computer readable code for provision to a programmable apparatus on any suitable carrier medium. A tangible carrier medium may comprise a storage medium such as a hard disk drive, a magnetic tape device or a solid-state memory device and the like. A transient carrier medium may include a signal such as an electrical signal, an electronic signal, an optical signal, an acoustic signal, a magnetic signal or an electromagnetic signal, e.g. a microwave or RF signal.

[0088] The invention will now be described by means of specific non-limiting exemplary embodiments and by reference to the figures.

[0089] The techniques described herein may be used for various broadband wireless communication systems, including communication systems that are based on an orthogonal multiplexing scheme. Examples of such communication systems include Spatial Division Multiple Access (SDMA) system, Time Division Multiple Access (TDMA) system, Orthogonal Frequency Division Multiple Access (OFDMA) system, and Single-Carrier Frequency Division Multiple Access (SC-FDMA) system. A SDMA system may utilize sufficiently different directions to simultaneously transmit data belonging to multiple user terminals, i.e. wireless devices or stations. A TDMA system may allow multiple user terminals to share the same frequency channel by dividing the transmission signal into different time slots or resource units, each time slot being assigned to different user terminal. An OFDMA system utilizes orthogonal frequency division multiplexing (OFDM), which is a modulation technique that partitions the overall system bandwidth into multiple orthogonal sub-carriers or resource units. These sub-carriers may also be called tones, bins, etc. With OFDM, each sub-carrier may be independently modulated with data. A SC-FDMA system may utilize interleaved FDMA (IFDMA) to transmit on sub-carriers that are distributed across the system bandwidth, localized FDMA (LFDMA) to transmit on a block of adjacent sub-carriers, or enhanced FDMA (EFDMA) to transmit on multiple blocks of adjacent sub-carriers.

[0090] The teachings herein may be incorporated into (e.g., implemented within or performed by) a variety of apparatuses (e.g., stations). In some aspects, a wireless device or station implemented in accordance with the teachings herein may comprise an access point (so-called AP) or not (so-called non-AP station or STA).

[0091] An AP may comprise, be implemented as, or known as a Node B, Radio Network Controller (“RNC”), evolved Node B (eNB), 5G Next generation base station (gNB), Base Station Controller (“BSC”), Base Transceiver Station (“BTS”), Base Station (“BS”), Transceiver Function (“TF”), Radio Router, Radio Transceiver, Basic Service Set (“BSS”), Extended Service Set (“ESS”), Radio Base Station (“RBS”), or some other terminology.

[0092] A non-AP station may comprise, be implemented as, or known as a subscriber station, a subscriber unit, a mobile station (MS), a remote station, a remote terminal, a user terminal (UT), a user agent, a user device, user equipment (UE), a user station, or some other terminology. In some implementations, a STA may comprise a cellular telephone, a cordless telephone, a Session Initiation Protocol (“SIP”) phone, a wireless local loop (“WLL”) station, a personal digital assistant (“PDA”), a handheld device having wireless connection capability, or some other suitable processing device connected to a wireless modem. Accordingly, one or more aspects taught herein may be incorporated into a phone (e.g., a cellular phone or smart phone), a computer (e.g., a laptop), a tablet, a portable communication device, a portable computing device (e.g., a personal data assistant), an entertainment device (e.g., a music or video device, or a satellite radio), a global positioning system (GPS) device, or any other suitable device that is configured to communicate via a wireless or wired medium. In some aspects, the non-AP station may be a wireless node. Such wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link.

[0093] An AP manages a set of stations that together organize their accesses to the wireless medium for communication purposes. The stations (including the AP) form a service set, here below referred to as basic service set, BSS (although other terminology can be used). A same physical station acting as an access point may manage two or more BSS (and thus corresponding WLANs): each BSS is thus uniquely identified by a specific basic service set identification, BSSID and managed by a separate virtual AP implemented in the physical AP.

[0094] Low latency reliable services, LLRS, are services provided to a higher layer traffic stream that prioritize and deliver MSDUs (data units of this traffic stream) within a worst-case latency budget with a given reliability/packet delivery ratio (PDR) and low jitter. Traffic that may be concerned by LLRS includes latency sensitive data, i.e. data from applications such as gaming, media streaming, augmented reality, virtual reality, and so on.

[0095] The 802.11be Project Authorization Request (PAR) gives examples of worst-case latencies, for instance 5 ms for realtime gaming.

[0096] A communication network should adopt appropriate measures, referred here below to as LLRS or low latency or LL measures, to ensure the LLRS traffic has indeed priority over not-LLRS traffic in the network. Some LL measures may be active measures in that they are to be applied by stations exchanging LLRS traffic in the network. Some LL measures may be passive measures in that they are to be applied by passive non-AP stations, i.e. those of the BSS that do not participate in the LLRS traffic exchange. The passive measures reduce use of the wireless network for exchange of not-LLRS traffic, hence prioritizing the LLRS traffic. Such prioritization favors achievement of PDR and low jitter targets.

[0097] The AP of a BSS may declare the LLRS requirements for the non-AP stations to join the BSS, such as the LL measures the non-AP stations will have to apply. A dedicated information element can be used in a management frame, with dedicated bits to declare for instance active and/or passive LL measures to be applied.

[0098] A non-AP station wishing to join the BSS can declare its LLRS capabilities, i.e. its capability to implement LL measures (in general or those or some as declared by the AP) when appropriate. The declaration may be made during the association procedure with the BSS in such a way the AP may decide whether to authorize or refuse the requested association based on the declared capabilities. Such non-AP station are referred below to as LLRS capable stations.

[0099] On the opposite, those having no LLRS capabilities are referred to as LLRS not-capable stations. They include legacy non-AP stations complying with one of the previous IEEE 802.11 standard specification including 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac or 802.1ax.

[0100] LLRS capable and not-capable non-AP stations coexist and share the same wireless medium. While LLRS capable stations can stop an ongoing legacy contention free transmission to let the wireless medium for LLRS transmissions, this is not the case for the LLRS not-capable stations. It results that LLRS transmissions may wait for a long time before starting, due to an ongoing legacy contention free transmission by a LLRS not-capable station.

[0101] The present invention seeks to have a better control over such ongoing legacy contention free transmissions by LLRS not-capable stations, in order to improve transmission latency, in particular with respect to LLRSs.

[0102] FIG. 1 illustrates an exemplary network environment 10 for delivering LLRS traffic, in accordance with one or more example embodiments.

[0103] Each communication station 101-107 registers to a central station or access point (AP) 110 during an association procedure where the AP assigns a specific Association IDentifier (AID) to the requesting non-AP station. For example, the AID, e.g. a 16-bit value uniquely identifying the non-AP station, is used to identify the stations in the frame exchanged. The AP 110 and the associated non-AP stations 101-107 may represent a basic service set (BSS) or an extended service set (ESS).

[0104] An exemplary association procedure is illustrated in FIG. 3, discussed below.

[0105] Once associated with the BSS, the communication stations 101-107, 110 exchange data frames over a radio transmission channel 100 of a wireless local area network (WLAN), under the management of the AP 110. The radio transmission channel 100 is defined by an operating frequency band constituted by a single channel or a plurality of channels forming a composite channel.

[0106] Non-AP stations may also communicate directly via a direct wireless link (DiL for direct link), i.e. without the intervention of the AP as relay of their messages. Exemplary situation of direct communications includes the presence of peer-to-peer (P2P) transmissions between non-AP stations having the same primary channel. Non-AP stations 101 and 107 exchange data frames via direct link and one of those two P2P stations operates as an AP station for this P2P exchange.

[0107] A physical access point 110 may be configured to manage two or more WLANs or BSSs, i.e. two or more groups of stations (see for instance the embodiment of FIG. 9). Each BSS is uniquely identified by a specific basic service set identifier, BSSID, and managed by a respective virtual AP implemented in the physical AP. Within the context of a multiple BSSID set, one virtual AP is referred to as the ‘transmitted’ BSSID or BSS (only one per the multiple set) if the AP emits beacon frames. Other BSSIDs of the AP belonging to a multiple BSSID set are ‘nontransmitted’ BSSIDs or BSSs. A beacon frame sent by the transmitted BSSID includes the basic profiles and each profile elements that are mandatory for the nontransmitted BSSID, including the EDCA and/or MU-EDCA parameters as discussed below.

[0108] The stations 101-107, 110 compete one against the other using EDCA (Enhanced Distributed Channel Access) contention, to gain access to the wireless medium 100 in order to be granted a so-called legacy contention free transmission opportunity (TXOP—or “contention free burst period”) and then transmit (single-user, SU) data frames over the wireless medium during the TXOP duration.

[0109] The stations may also use a multi-user (MU) scheme in which a single station, usually the AP 110, is allowed to schedule a MU transmission, i.e. multiple simultaneous transmissions to or from other stations, during a TXOP granted to it using EDCA contention in the wireless network. One implementation of such a MU scheme has been for example adopted in IEEE 802.11ax amendment standard, as the Multi-User Uplink and Downlink OFDMA (MU UL and DL OFDMA) procedures.

[0110] Access to the shared radio medium to send data frames is primarily based on the CSMA/CA technique, for sensing the carrier and avoiding collision by separating concurrent transmissions in space and time. Carrier sensing in CSMA/CA is performed by both physical and virtual mechanisms. Physical carrier sensing resides in the PHY layer of any station and uses energy detect and preamble detect with frame length deferral to determine when the medium is busy. Virtual carrier sensing resides in the MAC layer and uses reservation information carried in the Duration field of the MAC headers announcing impeding use of the medium. The virtual carrier sense mechanism is called the network allocation vector (NAV). The medium is determined to be idle only when both the physical and virtual carrier sense mechanisms indicate it to be so.

[0111] To access the medium (EDCA contention), any station, including the AP, starts counting down a backoff counter (designed to expire after a number of timeslots) when the medium is sensed as idle at least after a predefined period (e.g. SIFS, PIFS, DIFS or AIFS period depending on the frame type). The backoff counter is chosen randomly in a so-called contention window [0, CW], where CW is an integer selected between CW_min and CW_max (power of 2 less 1 values). This backoff mechanism or procedure, also referred to as Distributed Coordination Function (DCF) contention-based channel access scheme, is the basis of the collision avoidance mechanism that defers the transmission time for a random interval, thus reducing the probability of collisions on the shared channel. After the backoff time expires (i.e. the backoff counter reaches zero), the station may send data or control frames if the medium is still idle. These frames reserve the wireless medium 100 for a TXOP duration indicated in the Duration field of the MAC header (more precisely in the HE-SIG-A field for HE frames).

[0112] Once a station has gained access to the medium, it maintains control of the medium by keeping a minimum gap, the short inter-frame space (SIFS), between frames in a sequence. The successive frames may indicate, in the Duration field, the remaining duration of the current TXOP. Another station will not gain access to the medium during that sequence since it must defer for a fixed duration that is longer than SIFS. By this way, the stations, involved in a TXOP, can be sure that no frames will be transmitted by other stations till the end of the TXOP.

[0113] Rules limit the types of frame exchange sequences that are allowed and the duration of those sequences to prevent one station from monopolizing the medium.

[0114] Parameters governing the EDCA contention and these rules are known as EDCA parameters and are defined per BSS by the AP. They are transmitted to the non-AP stations of the BSS via the beacon frames the AP sends or via so-called probe response frames sent by the AP when the non-AP station tries to associate with the BSS (Figure XX discussed below).

[0115] The EDCA parameters are provided through an EDCA Parameter Set information element (IE) 210, as described in FIGS. 9-261 and 9-262 of IEEE 802.11 Standard®, version 2016, and reproduced in FIG. 2, The EDCA parameters includes a minimum contention window CW_min (or ECW_min), a maximum contention window CW_max (or ECW_max), an AIFSN value (defining the AIFS period mentioned above) and a TXOP limit value specifying the maximum allowed duration for a solicited TXOP.

[0116] As shown in the Figure, these parameters may be provided per each access category, AC_BE (through field 211), AC_BK (212), AC_VI (213), AC_VO (214) as defined in standard 802.11e-2005. This means that any obtained TXOP is a bounded period during which a station may transfer data of a particular traffic class (AC). Once the TXOP has been obtained, the station may continue to transmit data, control, and management frames and receive response frames, provided the frame sequence duration does not exceed the TXOP limit set (field 215) for that AC. To be noted that a TXOP limit of zero means that only one MSDU or management frame can be transmitted before competing again for access.

[0117] The AP can update the AC parameters at any time by using the QoS Info field 216. The QoS Info field 216 contains the EDCA Parameter Set Update Count subfield, which is initially set to 0 and is incremented each time any of the AC parameters changes. This subfield is used by the non-AP STAs receiving a new EDCA Parameter Set information element (IE) 210 to determine whether the EDCA parameter set has changed or not, and accordingly updates its local values to use them for the next data transmission.

[0118] The following table provides default values for the EDCA parameters for various 802.11 standards, as defined in table 9-137 of IEEE 802.11 Standard®, version 2016, and table 8-105 of IEEE 802.11 Standard®, version 2012.

[0119]

TABLE 1
default values for EDCA parameters
	TXOP limit
	802.11REVmd ™/D5.0
						OFDM (ERP,
AC	ECWmin	ECWmax	AIFSN	802.11n	DSSS	HT, VHT)	802.11ac
AC_BK	31	1023	7	0	3.264 ms	2.528 ms	0
AC_BE	31	1023	3	0	3.264 ms	2.528 ms	0
AC_VI	15	31	2	3.008 ms	6.016 ms	4.096 ms	22.56 ms
AC_VO	7	15	2	1.504 ms	3.264 ms	2.080 ms	11.28 ms
non-QOS	15	1023	2	0	0	0	0

[0120] 802.11ax standard introduced an additional set of EDCA parameters, namely MU EDCA parameters in order to restore fairness between non-AP stations involved in MU transmission with the AP and those stations not involved. The MU EDCA parameters temporary substitute the legacy EDCA parameters for a non-AP station of the BSS when the non-AP station is scheduled by the AP in a multi-user transmission.

[0121] The MU EDCA parameters are also transmitted by the AP to the non-AP stations of the BSS via beacon frames and/or probe response frames. The format of the MU EDCA Parameter Set information element is described in FIGS. 9-788o and 9-788p of the 802.11ax D6.1 standard. It is quite similar to the format of FIG. 2 except that a MU EDCA Timer field replaces the TXOP limit field 615. It means that the TXOP limit provided in the legacy EDCA parameters should apply when using the MU EDCA parameters.

[0122] FIG. 3 illustrates an exemplary sequence of management frames allowing a not-yet-associated non-AP station to discover and register with an AP managing a BSS. It comprises three phases: WLAN discovery, authentication and association, at the end of which the non-AP station enters into an authenticated and associated state with the AP, should the AP authorizes the association. Note that the station may be currently associated with another AP (of another BSS) and willing to join this BSS.

[0123] Prior to association with the AP, the non-AP stations gather information about the APs by scanning the channels one by one either through passive scanning (passive discovery procedure) or active scanning (active discovery procedure).

[0124] In the passive scanning mode, the station scans through successively each 20 MHz channel and waits to listen for beacon frames (declaring SSID—service set identifier of the BSSs) on the scanned channel, regardless of whether the stations have already connected to a specific BSS before or not.

[0125] The beacon frame is a management frame advertising details of the BSS. It is periodically sent over the wireless medium by the AP, for instance each 100 ms.

[0126] In the active scanning mode, the stations send out probe request frames 310 on each wireless 20 MHz channel. The probe request frames may contain the SSID of a specific BSS or WLAN that the station is looking for or the probe request frames may not contain a specific SSID meaning the station is looking for “any” BSS in the vicinity of the station.

[0127] In response to receiving a probe request frame, the AP checks whether the station has at least one common supported data rate or not. If there is a compatible data rate, the AP responds with a probe response frame 320, the content of which is similar to a beacon frame: advertising of the SSID (wireless network name), of supported data rates, of encryption types if required, and of other 802.11 capabilities of the AP including (MU-)EDCA parameters sets values to be used to perform further data transmission using EDCA.

[0128] An acknowledgment frame 330 may be sent by the station, in response to receiving the probe response frame 320.

[0129] According to embodiments of the invention, the AP may use the beacon frame 380 and the probe response frame 320 to advertise and update dynamically EDCA parameters sets values to be used by non-AP stations joining the BSS.

[0130] At the reception of the beacon frame or of the probe response frame, the non-AP station may decide to initiate or not the association procedure with the given BSS.

[0131] The second phase is the 802.11 authentication once a BSS to join has been chosen by the station. As a well-known conventional authentication phase is run, it is not described in details. The station sends a low-level 802.11 authentication request frame 340 to the selected AP. The AP receives the authentication request frame 340 and responds to the station with an authentication response frame 350.

[0132] Next, the station has to perform actual association with the AP from the low-level authentication step. This is the next phase of actual 802.11 association by which the station actually joins the BSS, if the AP agrees with. This stage finalizes the security and bit rate options and establishes the data link between the station and the AP. The purpose of this final exchange is for the station to obtain an Association Identifier (AID) to be used to access the medium and send data within the joined BSS.

[0133] To that end, the station sends an association request frame 360 to the selected AP. The association request frame contains chosen encryption types if required and other compatible 802.11 capabilities. The association request frame 360 is a management frame.

[0134] If the elements in the association request frame match the capabilities of the AP, the AP creates an Association ID (AID) for the station and responds with an association response frame 370 with a success message granting network access to the station. In case of no match, an association refusal may be issued.

[0135] More generally, the AP may authorise or refuse an association of the non-AP station with the BSS based on the received declaration of capabilities. To that end (authorization or refusal), result codes are provided in the association response frame 370. Exemplary codes are listed in section 6.3.7.5.2 of IEEE 802.11 Standard®, version 2016, for instance SUCCESS, REFUSED_REASON_UNSPECIFIED, REFUSED_CAPABILITIES_MISMATCH, REFUSED_EXTERNAL_REASON, REFUSED_AP_OUT_OF_MEMORY, REFUSED_BASIC_RATES_MISMATCH, REJECTED_EMERGENCY_SERVICES_NOT_SUPPORTED, REFUSED_TEMPORARILY.

[0136] Once the station is successfully associated with the AP, data transfer can start in the chosen BSS using the physical medium 100.

[0137] Once associated, a non-AP station and an AP can also disassociate unliterally by sending a disassociation frame 390. Reason codes are also provided in the dissociation frame 390. Numerous exemplary codes are listed in section 9.4.1.2 of IEEE 802.11 Standard®, version 2016. Disassociation cannot be refused by either party.

[0138] The probe response frame 320, authentication request/response frames 340 and 350, association request/response frames 360 and 370 and disassociation request frame 390 are unicast management frames emitted in an 802.11 legacy format, known as a single user (SU) format. This is a format used for point-to-point communication (here between the AP and the station). Each of these unicast management frames can be acknowledged by an ACK frame 330.

[0139] Back to FIG. 1, the non-AP stations may represent various devices such as gaming client, augmented/virtual reality headset, smartphones, wireless display and some of them have to exchange (i.e. transmit or/and receives) low-latency or LLRS data traffic over time. LLRS data traffic has more constrained QoS requirements regarding for instance PDR, jitter and latency, than not-LLRS traffic coexisting in the WLAN 10.

[0140] As an example, document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/200916, provides the following latency requirements for LLRS (real time):

• • [0141] Real-time gaming: latency lower than 5 ms
  • [0142] Cloud gaming: latency lower than 10 ms
  • [0143] Real-time video: latency lower than 3 to 10 ms

[0144] In robotics and industrial automation, equipment control and human safety: latency lower than 1 to 10 ms; haptic technology: latency lower than 1 to 5 ms.

[0145] Some non-AP stations 102, 103, 105 are LLRS capable and can participate to prioritize LLRS traffic over not-LLRS traffic, LL or LLRS measures can be implemented within the BSS: active LL measures for the stations (referred to as active stations) exchanging the LLRS traffic and passive LL measures for the non-AP stations (referred to as passive stations) not participating in the LLRS traffic exchange at a given time. The non-AP stations 102, 103, 105 may become successively active and passive stations within the same BSS. The non-AP stations 102, 103, 105 are LLRS capable.

[0146] The non-AP stations 103, 106, 107 are not implementing the LLRS features. The non-AP stations 103, 106, 107 are LLRS not-capable. The non-AP stations 103,106,107 can be legacy stations complying to a previous version of IEEE 802.11 standard specification not including the LLRS (802.11a, 802.11b, 802.11g, 802.11n, 802.11ac or 802.11ax) or stations not supporting LLRS (for example, if it is considered optional in the next 802.11 release).

[0147] FIG. 4 illustrates some LL measures taken in the BSS in an exemplary scenario where LLRS traffic is transmitted.

[0148] In this scenario, the AP schedules a reserved service period 410. It may announce the starting time and the ending time of the period. The reserved service period 410 may be fully dedicated to LLRS traffic exchange, or in variant may allow both LLRS traffic and not-LLRS traffic. In the figure, it is a reserved LLRS period.

[0149] The AP participates to the LLRS traffic exchange (sends 421 to non-AP station 105 and then receives 422 from non-AP station 102) in the reserved service period. However, this is not mandatory. The reserved LLRS period may alternatively be used by non-AP stations to directly exchange P2P LLRS traffic.

[0150] In one embodiment, the reserved service period is a protected TWT service period as presented in the IEEE 802.11-20/1046r2 document.

[0151] Prior to the reserved service period, non-AP station 104 gains access to the wireless medium 100 for a TXOP duration and starts transmitting not-LLRS traffic 420.

[0152] As station 104 is aware of the scheduled reserved service period 410, it is able to stop its not-LLRS traffic transmission when LLRS traffic is to be exchanged between other stations of the BSS, although its own TXOP is not ending. Such stopping action is a passive LL measure because it reduces the use of the wireless medium by station 104 to exchange not-LLRS traffic in the network. Such reduction mechanism (or measure) gives priority to the LLRS traffic.

[0153] AP 110 can next transmit LLRS traffic to non-AP station 105 and then receives other LLRS traffic from non-AP station 102. The stations can apply active LL measures to perform the LLRS traffic exchange, for instance using specific network resources dedicated to LLRS traffic.

[0154] The above stopping of a current TXOP is only one example of possible LL measures.

[0155] More generally, LLRS capable stations are able to stop or to suspend their current data transmission in favor to LLRS data traffic transmission from another LLRS capable station while TXOP is not ended.

[0156] The example of FIG. 4 shows that if station 104 does not apply the passive measure in due time, the LLRS exchange within the reserved service period cannot take place (or at least interference occur), resulting in degraded QoS for the LLRS traffic.

[0157] The non-AP stations may declare their LLRS capability or capabilities (or not) when associating as described above with reference to FIG. 3. It is reminded that the non-AP stations already declare some 802.11 capabilities in the association request frame 360, for instance using the Extended Capabilities information element (IE) defined in P802.11-REVmd/D5.0, section 9.4.2.27.

[0158] According to embodiments of the invention, the non-AP station wishing to join the BSS declares own LLRS capabilities to apply one or more LL measures. It may declare to be passive LLRS capable and/or active LLRS capable, or declare merely it is LLRS capable. Of course, stations that are not LLRS capable will provide a declaration accordingly. Examples of signalling the LLRS capabilities in the management frame sent by the non-AP station are provided below with reference to FIGS. 5 and 6.

In a variant to providing the LLRS capabilities in the association request frame 360, the non-AP station may decide using the probe request frame 310. The latter is also a management frame. Therefore, a similar signalling of the LLRS capabilities can be used. In that scenario, at the reception of the probe request frame, the AP may analyse the LLRS capabilities of the non-AP station and decide to continue or not the association procedure with the non-AP station as described below.

[0159] In FIG. 5, a single bit 500 is added to the existing IE as a supplemental station capability. In the case of the known Extended Capabilities IE, available bits are from the 87^th bit. Bit 87 is thus for instance chosen to signal whether the non-AP station is capable to apply LL measures (LLRS capable—value set to 1) or not (value to 0). At this stage, no distinction is made between active and passive LLRS capability. This may mean the station has both passive and active LLRS capabilities. In a variant, this may mean the station has at least one of the two capabilities.

[0160] In FIG. 6, two bits 600 are added to the existing IE as supplemental station capabilities. In the case of the known Extended Capabilities IE, available bits are from the 87^th bit. Bits 88 and 89 are chosen to respectively:

• • [0161] signal whether the non-AP station is capable to apply passive LL measures when LLRS traffic is to be exchanged between other stations of the BSS, to the effect of reducing the use of a wireless medium by the non-AP station to exchange not-LLRS traffic in the network (bit 88 set to 1), or not (bit 88 set to 0). In that way, the station declares to be passive LLRS capable or not, and
  • [0162] signal whether the non-AP station is capable to apply active LL measures when it has to exchange LLRS traffic with another station of the BSS, to the effect of using resources dedicated to LLRS traffic for exchanging the LLRS traffic in the network (bit 89 set to 1), or not (bit 89 set to 0). In that way, the station declares to be active LLRS capable or not.

[0163] Although FIG. 6 shows the two bits together, embodiments may contemplate using only one of the two bits, for instance for a non-AP station to only declare itself as a passive (or active) LLRS capable station or not.

[0164] Thanks to such signalling by the non-AP station (FIGS. 5 and 6), the AP becomes aware of which non-AP stations are LLRS capable and which are not, and therefore of which non-AP stations are supposed to transmit LLRS data traffic. As described below, the AP may refuse an association if the LLRS capabilities declared by a non-AP station do not match LLRS requirements of the BSS (for instance declared in the beacon 380 or probe response frame 320).

[0165] FIG. 7 illustrates, using a timeline, the impact of non-LLRS data traffic exchanged by legacy stations (i.e. LLRS not-capable non-AP stations) on the latency for LLRS data traffic.

[0166] In FIG. 7, illustrates a long duration TXOP 714 performed by a legacy station 106 gains a TXOP 714 having a long duration, e.g. equal to TXOP limit provided by the AP (FIG. 2), in order to transmit non LLRS data traffic 710 over the wireless medium 100.

[0167] During this contention free period TXOP 714, a LLRS capable station 105 may be ready to transmit LLRS data traffic 711. Unfortunately, as the legacy station 106 does not implement LLRS measure feature (it is LLRS not-capable), it cannot stop its TXOP 714 and then give back the wireless medium 100 to the LLRS capable station 105.

[0168] The LLRS data transmission is postponed until the end of the legacy contention free period transmission opportunity: the LLRS capable station 105 has to wait until the end of TXOP 714 to get a new contention free period 713 using EDCA and then transmit the LLRS data traffic referenced here as 712. A high delay is therefore introduced before the LLRS capable station 105 can transmit its LLRS data traffic 711.

[0169] The delay may exceed a worst-case latency budget required for LLRS data traffic, which is dramatic for quality of real time applications. For example, if the worst-case latency budget of LLRS data traffic is 2 ms and TXOP 714 duration is 3 ms (complying with above table 1) considering 802.11ac video data traffic (non-LLRS data traffic), the LLRS data traffic is transmitted too late.

[0170] More generally, this example shows that when passive stations do not accept to apply the passive LL measures to reduce their impact on the network and free bandwidth, the LLRS data traffic is not given priority, hence the low latency, PDR and jitter requirements cannot be fulfilled.

[0171] A similar consideration can be made for the active stations. An active non-AP station may decide not to activate/use active LL measures, for instance not penalize its own not-LLRS data traffic (as web browsing, mail, etc.). However, this penalizes the overall LLRS efficiency of the network.

[0172] Also, the station designed on a previous 802.11 standard (being a non EHT non-AP stations) obviously cannot apply the LL measures. They can dramatically degrade the LLRS efficiency in the BSS as shown in this example.

[0173] To overcome the foregoing deficiencies, embodiments of the invention provide modifying the EDCA parameters of the BSS, in particular the TXOP limit values, when LLRS activity is detected (including suspected) in the network 10. Such modification makes it possible to reduce the TXOP limit values, hence the duration of the TXOP obtained by legacy non-AP stations. It results that LLRS capable stations can obtain more frequent (given the lower TXOP duration) opportunities to access the medium, despite the presence of LLRS not-capable stations.

[0174] To that end, the AP may initially set (e.g. using beacon frames) Enhanced Distributed Channel Access, EDCA, parameters for a first BSS, i.e. EDCA parameters to be applied by non-RECTIFIED SHEET (RULE 91) ISA/EP AP stations of the first BSS to access a wireless medium and transmit frames. Next, upon detecting low latency reliable service, LLRS, activity in the BSS or BSSs it manages, it may modify the EDCA parameters for the first BSS. The modified EDCA parameters are indeed transmitted to the concerned non-AP stations, e.g. through beacon frames.

[0175] With the modified EDCA parameters, in particular with a reduced TXOP limit value, legacy station 106 is no longer allowed to reserve a TXOP as large as TXOP 714.

[0176] FIG. 8 illustrates, using a timeline, technical effects of embodiments of the present invention, in particular on the latency for LLRS data traffic. This Figure illustrates the behavior of the stations in the BSS once the AP has broadcasted modified EDCA parameters, in particular a reduced TXOP limit, upon being aware of LLRS activity in the network.

[0177] Legacy station 106 can EDCA-reserve a TXOP 814 within the TXOP limit constraint, to transmit not-LLRS data traffic. As the TXOP limit may be severely reduced, TXOP 814 is shorter than TXOP 714; the wireless medium is released earlier. LLRS capable station 105 can therefore EDCA-access the wireless medium 100 substantially earlier (lower delay) than in FIG. 7: it then transmits its LLRS data traffic 812 during an obtained TXOP 813. Legacy station 106 which still has some not-LLRS data 820 may again EDCA-access the medium and transmit the data during an obtained TXOP 824 still complying with the TXOP limit.

[0178] It turns out that the LLRS capable stations are able to transmit LLRS data traffic in a shorter delay, therefore being inclined to meet worst-case latency requirements. The impact for not-LLRS capable stations is reasonable: their data transmission is performed in two (or more) times, starting at a similar time than data transmission 710 over TXOP 714 but split in two (or more) parts 810, 820 during different TXOPs 814, 824.

[0179] As the adaptation of the EDCA parameters impacts the throughput of the legacy stations by reducing their burst duration (TXOP duration), it is preferable that the adaptation be temporary, for instance as long as LLRS activity is ongoing. Therefore, upon detecting an end of the LLRS activity in the BSS or BSSs, the AP may restore (i.e. modify back) the set EDCA parameters for the first BSS.

[0180] In the case of FIG. 1, LLRS not-capable non-AP stations 103, 106, 107 may coexist with LLRS capable non-AP stations 102, 104, 105 within the same BSS. In that case, LLRS activity is detected is said first BSS.

[0181] However, in this configuration, the LLRS capable stations are also impacted by the modified EDCA parameters, in particular a reduced TXOP limit, although they are able to apply passive LL measures to stop an ongoing TXOP and favor LLRS data traffic.

[0182] Therefore, other embodiments are contemplated wherein the AP manages two or more BSSs sharing the same wireless medium 100, one (first BSS) being reserved to LLRS not-capable stations and another one (second BSS) reserved to LLRS capable stations. In that way, it is possible to only modify the EDCA parameters for the LLRS not-capable stations (i.e. the first BSS). In the second BSS, the LLRS capable stations are still allowed to reserve TXOPs with longer duration even to transmit not-LLRS data traffic, without impacting the LLRS data latency. This is because, as mentioned earlier, they are able to stop their ongoing TXOP at any time, to release the wireless medium for transmission of LLRS data traffic.

[0183] In this configuration, the LLRS activity is detected in another (second) BSS managed by the AP than the first BSS, and the EDCA parameters for the other (second) BSS may remain unchanged upon detecting the LLRS activity.

[0184] An illustration of this configuration is provided in FIG. 9, where a first BSS 901, named LEGACY_BSS, is created by AP 110 to manage legacy stations 103,106,107 (LLRS not-capable stations) and a second BSS 902, named LL_BSS, is created by AP 110 to manage the LLRS capable stations 102,104,105.

[0185] Multiple BSSs are possible either by creating independent BSSs or by using the multi-BSS standard feature (802.11be). LEGACY_BSS 901 and LL_BSS 902 receives two different EDCA Parameter Set elements from AP 110, which can be updated independently. As mentioned above the EDCA Parameter Set element (FIG. 2) may be accompanied with a MU EDCA Parameter Set element.

[0186] To achieve backward compatibility with legacy non-AP stations, LEGACY_BSS 901 is the transmitted BSS, while LL_BSS is a nontransmitted BSS.

[0187] When using the multi-BSS standard feature, a single beacon frame may be used by AP 110 to transmit the information relating to the two BSSs (including the EDCA parameters). As LEGACY_BSS is the transmitted BSS, its information (EDCA parameters) is provided first. This allows legacy stations to retrieve the communication parameters they need. LL_BSS information is transmitted over the same beacon frame, after the LEGACY_BSS information.

[0188] When the EDCA parameters (e.g. TXOP limit) for the first BSS, LEGACY_BSS 901, are modified upon detecting LLRS activity, a new beacon frame 380 may be sent where the LEGACY_BSS information is updated while the LL_BSS information may be kept unchanged.

[0189] FIG. 10 illustrates, using a flowchart, general steps at the AP for embodiments of the present invention where the EDCA parameters are adapted/modified depending on LLRS activity in the network. The algorithm applies to both single-BSS embodiments and multi-BSS (LEGACY_BSS and LL_BSS) embodiments.

[0190] Here below, the first BSS refers to the single BSS or the LEGACY_BSS in case of multi-BSS.

[0191] At step 1000, AP 110 sets the EDCA parameters (including the MU EDCA parameters) for the first BSS, for example upon creating the first BSS or when updating its EDCA parameters.

[0192] The setting is made in a conventional manner: it may include broadcasting a beacon frame including the EDCA parameters or sending a probe response frame including the EDCA parameters to each probe requesting non-AP station. The EDCA parameters are conveyed in (MU-)EDCA Parameter Set IEs (e.g. 210 in FIG. 2). The EDCA parameter values may be those indicated in Table 1 above.

[0193] This state of the first BSS (LEGACY STATE) corresponds to the absence of LLRS activity detected by AP 110 over the wireless network or in the BSSs it manages.

[0194] The non-AP stations of the first BSS thus access the wireless medium as described above with reference to FIG. 7 for instance. This configuration allows high throughput data transmission to be achieved.

[0195] At step 1010, AP 110 becomes aware of LLRS activity in the network, in particular concerning the wireless medium 100. For instance, AP 110 may detect LLRS activity in the BSS or BSSs it manages: this may be LLRS activity in the first BSS or LLRS activity in another BSS (e.g. LL_BSS above).

[0196] Such detection may include for AP 110 to be involved in the LLRS measures as described in FIG. 4 or to detect any LLRS measures in the network.

[0197] It may also include, for the AP, to receive LLRS capability for a non-AP station in its BSSs sharing the wireless medium 100 (incl. the first BSS). In that case, as soon as a LLRS capable non-AP station is present, the state of the first BSS can be changed as described below (into LL STATE). Reversely, as soon as there is no more LLRS capable non-AP station in the first BSS or in its BSSs, the state of the first BSS can be configured back to its prior state (LEGACY STATE).

[0198] Alternatively, it may include, for the AP, to exchange LLRS data traffic (i.e. UpLink or DownLink traffic) with a non-AP station in its BSSs (incl. the first BSS). Data traffic may carry a predefined Traffic Identifier to identify it as LLRS traffic, or be of a predefined access category (e.g. AC_VI or AC_VO). Therefore, as soon as AP 110 is involved in LLRS data exchange, the state of the first BSS is changed. Reversely, once the LLRS data exchanges with the AP end, the state of the first BSS may be configured back to its prior state.

[0199] Another alternative includes for the AP to receive, from a non-AP station, a message signaling LLRS data traffic requirements or needs. This may for instance be a TSPEC message indicating a low latency, i.e. a specified latency lower than a predefined TXOP limit (e.g. the TXOP limit set in the EDCA parameters of the BSS). In this situation, as soon as the AP becomes aware of station needs in terms of LLRS data traffic, the state of the first BSS may be changed. Reversely, as soon as the station needs are satisfied and no more LLRS need is identified, the AP may switch back the first BSS to its prior state.

[0200] For instance, the Delay Bound field in the TSPEC specifies a maximum amount of time, in micro-seconds, to complete a successful transmission, including retransmission if any. LLRS activity may be declared when Delay Bound<TXOP limit without retransmission or Delay Bound<(N+1)*TXOP limit with retransmission (N being an integer, for instance N=1 for an immediate single retransmission).

[0201] Once LLRS activity has been detected in the network (first BSS or LL_BSS for example), AP 110 modifies the EDCA parameters for the first BSS, in particular the Transmission Opportunity, TXOP, limit parameter that defines a maximum duration for the TXOPs and which is lowered (compared to the TXOP limit parameter of the EDCA parameters before modification). This is step 1020.

[0202] This includes forming a new EDCA Parameter Set IE with the modified TXOP limit (in field 215 for each AC) for instance to a predefined TXOP_LL limit value as shown in the table below. The same TXOP_LL limit value may be used throughout the ACs or they may be different one AC from the other.

[0203] As mentioned above, the TXOP_LL values help to reduce the impact of not-LLRS data traffic transmitted by legacy non-AP stations or LLRS not-capable non-AP stations.

[0204]

TABLE 2
default values for EDCA parameters adapted to LLRS
	TXOP limit
	ECWmin	802.11REVmd ™/D5.0
	ECWmax			OFDM (ERP,		802.11be
AC	AIFSN	802.11n	DSSS	HT, VHT)	802.11ac	LLRS
AC_BK	Un-changed	0	3.264 ms	2.528 ms	0	TXOP_LL(BK)
AC_BE		0	3.264 ms	2.528 ms	0	TXOP_LL(BE)
AC_VI		3.008 ms	6.016 ms	4.096 ms	22.56 ms	TXOP_LL(VI)
AC_VO		1.504 ms	3.264 ms	2.080 ms	11.28 ms	TXOP_LL(VO)
non-QOS		0	0	0	0	TXOP_LL(noQoS)

[0205] Preferably, the TXOP_LL values are set lower (ideally strictly lower) than a worst-case latency budget (depending on the data type) required for LLRS data traffic, for instance as mentioned in document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6.

[0206] As examples, a TXOP_LL value may be set to:

• • [0207] half a value of such a worst-case latency budget, for instance the lowest non-zero value,
  • [0208] a TXOP limit value from table 9-137 of IEEE 802.11 Standard®, version 2016, or from table 8-105 of IEEE 802.11 Standard®, version 2012, that is lower than a worst-case latency budget for LLRS data traffic as defined in the document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6. For instance 1.504 ms may be used if the worst-case latency budget is 2 ms,
  • [0209] a ratio between a worst-case latency budget for LLRS data traffic as defined in the document “IEEE 802.11 Real Time Applications TIG Report”, referenced IEEE 802.11-18/2009r6 and a number that is based on a number of non-AP stations having no LLRS capability (i.e. not implementing LLRS) in the first BSS. For instance it may be the ratio between the worst-case latency budget and the number of LLRS not-capable stations,
  • [0210] value 0, i.e. restricting the TXOP to the transmission of a single MAC service data unit, MSDU, or management frame,
  • [0211] a value equal to 1.024 ms. This reduces to the minimum the duration of any TXOP performed by any LLRS not-capable non-AP stations,
  • [0212] a value equal or lower than Delay Bound values indicating, in TSPEC information elements managed by the AP and received from LLRS capable non-AP stations, maximum amounts of time to complete successful transmissions,
  • [0213] a value equal or lower than ratios, each between a Delay Bound value indicating, in a TSPEC information element managed by the AP and received from a LLRS capable non-AP station, a maximum amount of time to complete a successful transmission and an integer N increased from 1 in case of retransmission policy.

[0214] This reduces to the minimum the duration of any TXOP performed by any LLRS not-capable non-AP stations in favor to the low latency data traffic transmitted by any LLRS capable non-AP stations.

[0215] The modified EDCA parameters for the first BSS are broadcast in the first BSS using a beacon frame. Each non-AP station of the first BSS accordingly sets its local TXOP limit values to the modified TXOP_LL(i) values. The first BSS thus enters the state (LL STATE) during which LLRS activity takes place over the shared wireless medium. The non-AP stations of the first BSS thus access the wireless medium with shorter TXOPs, as described above with reference to FIG. 8 for instance.

[0216] This configuration allows low latency transmission to be achieved for LLRS data traffic, even when LLRS capable stations and LLRS not-capable stations are associated within the same AP.

[0217] Next, at step 1030, AP 110 determines whether the LLRS activity stopped. Exemplary situations of such determination are provided above. Upon detecting an end of the LLRS activity in the BSS or BSSs, AP 110 loops back to step 1000 to restore (i.e. modifying back) the previous EDCA parameters for the first BSS. The first BSS therefore enters back the LEGACY STATE when longer TXOPs can be obtained by the non-AP stations.

[0218] As shown in FIGS. 1 and 9, Direct Link communications may also take place over the wireless medium 110 (here between associated non-AP station 107 and not-associated station 101). The P2P stations (here 101 and 107) directly negotiate their communication parameters, including the TXOP duration, without consideration of the (MU-)EDCA parameters they may know.

[0219] This negotiation can be performed using QoS control fields in the MAC header of exchanged frames, as described in the IEEE 802.11-2007 standard. Particularly, the “QoS Data(+)CF-Poll” frame can be used to request a TXOP duration (‘TXOP duration requested’ in the QoS control field) and the “QoS Data(+)CF-Ack” frame can be used to response with a TXOP limit (‘TXOP limit’ in the QoS control field).

[0220] To further minimize the chance of collisions, and as a more robust collision detect mechanism, the initiating P2P station may begin a sequence with a short control frame exchange using robustly modulated RTS and CTS frames permitting a contention free burst period during a transmit opportunity TXOP. This sets the NAV in the stations surrounding both the P2P initiator and P2P responder, some of which may be hidden nodes unable to detect the more remote station's transmissions and thus only able to defer for frame transmissions from nearby nodes.

[0221] RTS and CTS frames include also a duration field which can be used to know the remaining duration of the current TXOP.

[0222] The P2P process does not follow the rules of the BSSs, hence the EDCA parameters of the first BSS. DiL or P2P communications therefore have the same impact as the one shown in FIG. 7: long TXOPs that dramatically degrade the latency of LLRS data traffic

[0223] To improve this situation, the P2P station also belonging to the first BSS (here station 107 which has knowledge of the EDCA parameters) may negotiate, based on the TXOP limit parameter, a duration of a P2P TXOP with the other P2P station (here station 101) based on the TXOP limit currently applicable in the EDCA parameters. For instance, the duration of the P2P TXOP is made shorter than the TXOP limit parameter. Therefore, should the first BSS be in the LEGACY STATE, the P2P TXOP may have a large duration. On the other hand, when the first BSS is in the LL STATE (because LLRS activity has been detected), the P2P TXOP is made with a short duration, compliant with the LLRS latency requirements.

[0224] If both P2P stations belong to respective BSS, they may negotiate the P2P TXOP duration using the lowest TXOP limit value.

[0225] In practice, P2P station 107 may receive a TXOP duration from P2P station 101 and reply with a reduced TXOP duration given the TXOP limit parameter (e.g. if the received TXOP duration is higher than the TXOP limit parameter applicable for the first BSS and the AC considered).

[0226] Turning now to the case of multi-BSS, AP 110 may simultaneously manage LEGACY_BSS 901 and LL_BSS 902. As mentioned above, grouping the LLRS not-capable stations in one BSS (LEGACY_BSS) and the LLRS capable stations in another BSS (LL_BSS) advantageously allows to impact the TXOP duration to the LLRS not-capable stations only (by setting appropriate EDCA parameters only for LEGACY_BSS). An efficient management of the association of stations with the AP is therefore required.

[0227] It is proposed that the AP transmits, to a given non-AP station, an association-related management frame refusing an association of the non-AP station with a target BSS managed by the AP or disassociating the non-AP station from the target BSS, wherein the association-related management frame includes a code indicating another BSS managed by the AP is available.

[0228] Such code thus makes it possible to warn a LLRS not-capable station that the target BSS is not appropriate to it (LL_BSS) but another appropriate BSS (LEGACY_BSS) is available at the same AP. Alternatively, such a code may warn a LLRS capable station that the target BSS is not appropriate to it (LEGACY_BSS) but another more appropriate BSS (LL_BSS) is available at the same AP.

[0229] Such signalling may take place during the association phase (i.e. in association response frame 870) or take place through the disassociation procedure (i.e. in a disassociation request or response frame 390 from the AP).

[0230] FIG. 11a illustrates, using a flowchart, general operations for such management at the AP during an association phase for a non-AP station wishing to join LEGACY_BSS.

[0231] Step 1100 determines when an association request frame 360 is received from a non-AP station for LEGACY_BSS 901. It is reminded that this BSS is reserved to LLRS not-capable stations.

[0232] Therefore, at step 1110, the AP determines whether the requesting non-AP station is LLRS capable or not, using for instance the capability declaration shown in FIG. 5. In that way, the AP determines whether a capability of the non-AP station matches a capability of the BSS considered with respect to a low latency reliable service, LLRS.

[0233] If the requesting station is LLRS not-capable, the association can be authorized, and a response (association response frame 370 e.g. with a conventional result code SUCCESS) is sent to the station at step 1120.

[0234] If the requesting station is LLRS capable, the BSS is not appropriate compared to LL_BSS the AP instantiates or can instantiate.

[0235] Therefore, at step 1130, the AP determines whether the low latency BSS (LL_BSS) is already initiated or not. In the negative, at step 1140, the AP creates LL_BSS 902 either by using a second beacon frame or by using the multi-BSS feature.

[0236] In the affirmative or after step 1140, the AP refuses the association and signals to the requesting LLRS capable station that LL_BSS is available.

[0237] This is made by sending (step 1150) an association response frame 370 with a newly proposed result code, for instance REFUSED_LL_BSS_AVAILABLE. This code thus supplements the result codes listed in section 6.3.7.5.2 of IEEE 802.11 Standard®, version 2016.

[0238] The requesting LLRS capable station receiving such result code may search for another BSS of the same AP. Such information may be retrieved from the beacon frames sent by the AP. Responsive to identifying another BSS, ideally LL_BSS, the requesting station may transmit an association request frame to the AP to associate with this other BSS. The process of FIG. 11b may then be performed by the AP receiving the association request frame with a view of accepting (or not) the association. Thanks to the result code redirecting the requesting station, it is expected that ultimately a capability of the redirected non-AP station matches a LLRS capability of the other BSS to which it is redirected.

[0239] FIG. 11b illustrates, using a flowchart, general operations for BSS management by the AP during an association phase for a non-AP station wishing to join LL_BSS.

[0240] Step 1160 determines when an association request frame 360 is received from a non-AP station for LL_BSS 902. It is reminded that this BSS is reserved to LLRS capable stations.

[0241] Therefore, at step 1170, the AP determines whether the requesting non-AP station is LLRS capable or not, using for instance the capability declaration shown in FIG. 5.

[0242] If the requesting station is LLRS capable, the association can be authorized, and a response (association response frame 370 e.g. with a conventional result code SUCCESS) is sent to the station at step 1180. This is for instance the case of the above LLRS capable non-AP station that has received the result code REFUSED_LL_BSS_AVAILABLE when trying to join LEGACY_BSS, and that was directed to LL_BSS for association.

[0243] If the requesting station is LLRS not-capable, the BSS is not appropriate compared to LEGACY_BSS the AP already instantiates.

[0244] Therefore, at step 1190, the AP refuses the association and signals to the requesting LLRS not-capable station that LEGACY_BSS is available.

[0245] This is made by sending an association response frame 370 with a newly proposed result code, for instance REFUSED_LL_BSS_RESERVED. This code thus supplements the result codes listed in section 6.3.7.5.2 of IEEE 802.11 Standard®, version 2016.

[0246] The requesting LLRS not-capable station receiving such result code may search for another BSS of the same AP. Such information may be retrieved from the beacon frames sent by the AP. Responsive to identifying another BSS, ideally LEGACY_BSS, the requesting station may transmit an association request frame to the AP to associate with this other BSS. The process of FIG. 11a is then performed by the AP receiving the association request frame with a view of accepting (or not) the association. Thanks to the result code redirecting the requesting station, it is expected that ultimately a capability of the redirected non-AP station matches a LLRS capability of the other BSS to which it is redirected.

[0247] Thanks to new result codes REFUSED_LL_BSS_AVAILABLE and REFUSED_LL_BSS_RESERVED indicating the reason of association rejection, an AP determining a LLRS capability mismatch between an association requesting non-AP station and a target BSS may redirect the requesting non-AP station to another BSS it instantiates. A requesting non-AP station receiving such codes may search another BSS managed by the same AP, e.g. through the multi-BSS feature, and solicit association with this other BSS.

[0248] FIG. 12a illustrates, using a flowchart, general operations for BSS management by AP during a disassociation phase of a LLRS capable non-AP station belonging to LEGACY_BSS 901.

[0249] Disassociation is performed when a LLRS capability mismatch appears between one (or more) non-AP station associated with a first BSS and the first BSS. The AP thus has to determine whether a capability of the already associated non-AP station does not match a capability of the first BSS with respect to a low latency reliable service, LLRS.

[0250] Such situation may happen for several reasons. For instance, a non-AP station already associated with a first BSS (i.e. during the life of the first BSS) may change its LLRS capability declaration.

[0251] It may also happen when the AP detects LLRS activity (either a start thereof, or a substantial amount thereof) in the network and thus decides (based on some criteria) to instantiate both LEGACY_BSS and LL_BSS. In other words, the AP may, upon detecting LLRS activity in the network, restrict the first BSS to LLRS not-capable non-AP stations. The first BSS thus becomes LEGACY_BSS and LLRS capable stations should move to LL_BSS.

[0252] Step 1200 thus consists in checking whether such situation occurs and then triggers the disassociation process for non-AP stations not adapted (i.e. LLRS capable) to LEGACY_BSS considered.

[0253] At step 1210, the AP determines whether the low latency BSS (LL_BSS 902) is already initiated or not. In the negative, at step 1220, the AP creates LL_BSS 902 either by using a second beacon frame or by using the multi-BSS feature.

[0254] In the affirmative or after step 1220, the AP disassociates the (or several) non-AP station having non-matching LLRS capability with LEGACY_BSS and signals to the station under disassociation process that LL_BSS is however available.

[0255] This is made by sending (step 1230) a disassociation request frame 390 with a newly proposed reason code, for instance LL_BSS_AVAILABLE. This code thus supplements the reason codes listed in section 9.4.1.2 of IEEE 802.11 Standard®, version 2016.

[0256] The LLRS capable station under disassociation process and receiving such reason code may search for another BSS of the same AP. Such information may be retrieved from the beacon frames sent by the AP. Responsive to identifying another BSS, ideally LL_BSS, the requesting station may transmit an association request frame to the AP to associate with this other BSS. The above process of FIG. 11b may then be performed by the AP with a view of authorizing the association of the disassociated LLRS capable station with LL_BSS (step 1240).

[0257] FIG. 12b illustrates, using a flowchart, general operations for BSS management by the AP during a disassociation phase of a LLRS not-capable non-AP station belonging to LL_BSS 902. It is quite similar to FIG. 12b where the BSSs has exchanged roles.

[0258] Disassociation is performed when a LLRS capability mismatch appears between one (or more) non-AP station associated with a first BSS and the first BSS. The AP thus has to determine whether a capability of the already associated non-AP station does not match a capability of the first BSS with respect to a low latency reliable service, LLRS.

[0259] Such situation may happen for several reasons. For instance, a non-AP station already associated with a first BSS (i.e. during the life of the first BSS) may change its LLRS capability declaration.

[0260] It may also happen when the AP detects LLRS activity (either a start thereof, or a substantial amount thereof) in the network and thus decides (based on some criteria) to instantiate both LEGACY_BSS and LL_BSS. In other words, the AP may, upon detecting LLRS activity in the network, restrict the first BSS to LLRS capable non-AP stations. The first BSS thus becomes LL_BSS and LLRS not-capable stations should move to LEGACY_BSS.

[0261] Step 1250 thus consists in checking whether such situation occurs and then triggers the disassociation process for non-AP stations not adapted (i.e. LLRS not-capable) to LL_BSS considered.

[0262] At step 1260, the AP determines whether the legacy BSS (LEGACY_BSS 901) is already initiated or not. In the negative, at step 1270, the AP creates LEGACY_BSS 902 either by using a second beacon frame or by using the multi-BSS feature. Preferably, LEGACY_BSS 902 is always instantiated as the transmitted BSS, as soon as the AP is switched on. Indeed, LEGACY_BSS can be initiated permanently or ‘on-demand’ when LLRS is active in the network.

[0263] In the affirmative or after step 1270, the AP disassociates the (or several) non-AP station having non-matching LLRS capability with LL_BSS and signals to the station under disassociation process that LEGACY_BSS is however available.

[0264] This is made by sending (step 1280) a disassociation request frame 390 with a newly proposed reason code, for instance LL_BSS_RESERVED. This code thus supplements the reason codes listed in section 9.4.1.2 of IEEE 802.11 Standard®, version 2016.

[0265] The LLRS not-capable station under disassociation process and receiving such reason code may search for another BSS of the same AP. Such information may be retrieved from the beacon frames sent by the AP. Responsive to identifying another BSS, ideally LEGACY_BSS, the requesting station may transmit an association request frame to the AP to associate with this other BSS. The above process of FIG. 11a may then be performed by the AP with a view of authorizing the association of the disassociated LLRS not-capable station with LEGACY_BSS (step 1290).

[0266] Thanks to new reason codes LL_BSS_AVAILABLE and LL_BSS_RESERVED, an AP determining a LLRS capability mismatch between an associated non-AP station and the BSS may redirect the mismatching non-AP station to another more adapted BSS it instantiates. A mismatching non-AP station receiving such codes may search the other BSS managed by the same AP, e.g. through the multi-BSS feature, and solicit association with this more adapted BSS.

[0267] The above embodiments show that an AP may dynamically manage its BSS or BSSs to improve the latency for LLRS data traffic

[0268] FIG. 13 schematically illustrates a communication device 1300, either a non-AP station 101-107 or the access point 110, of the radio network 100, configured to implement at least one embodiment of the present invention. The communication device 1300 may preferably be a device such as a micro-computer, a workstation or a light portable device. The communication device 1300 comprises a communication bus 1313 to which there are preferably connected:

• • [0269] a central processing unit 1301, such as a processor, denoted CPU;
  • [0270] a memory 1303 for storing an executable code of methods or steps of the methods according to embodiments of the invention as well as the registers adapted to record variables and parameters necessary for implementing the methods; and
  • [0271] at least one communication interface 1302 connected to a wireless communication network, for example a communication network according to one of the IEEE 802.11 family of standards, via transmitting and receiving antennas 1304.

[0272] Preferably the communication bus provides communication and interoperability between the various elements included in the communication device 1300 or connected to it. The representation of the bus is not limiting and in particular the central processing unit is operable to communicate instructions to any element of the communication device 1300 directly or by means of another element of the communication device 1300.

[0273] The executable code may be stored in a memory that may either be read only, a hard disk or on a removable digital medium such as for example a disk. According to an optional variant, the executable code of the programs can be received by means of the communication network, via the interface 1302, in order to be stored in the memory of the communication device 1300 before being executed.

[0274] In an embodiment, the device is a programmable apparatus which uses software to implement embodiments of the invention. However, alternatively, embodiments of the present invention may be implemented, totally or in partially, in hardware (for example, in the form of an Application Specific Integrated Circuit or ASIC).

[0275] FIG. 13b is a block diagram schematically illustrating the architecture of the communication device 1300, either AP 110 or one of stations 101-107, adapted to carry out, at least partially, the invention. As illustrated, device 1300 comprises a physical (PHY) layer block 1323, a MAC layer block 1322, and an application layer block 1321.

[0276] The PHY layer block 1323 (here an 802.11 standardized PHY layer) has the task of formatting, modulating on or demodulating from any 20 MHz channel or the composite channel, and thus sending or receiving frames over the radio medium used 100, such as 802.11 frames, to reserve a TXOP and exchange (LLRS or not) data.

[0277] The MAC layer block or controller 1322 preferably comprises an 802.11 MAC layer 1324 implementing conventional 802.11ax MAC operations, and additional block 1325 for carrying out, at least partially, the invention. The MAC layer block 1322 may optionally be implemented in software, which software is executed by CPU 1301.

[0278] Preferably, the additional block 1325, referred to as LLRS management module, implements the part of embodiments of the invention.

[0279] At the AP, it manages the EDCA parameters of its BBSs, depending on whether LLRS activity is detected. It also manage the association and disassociation procedures in order to provide the above result or reason codes to redirect some non-AP stations to another more adapted BSS.

[0280] At a non-AP station, it declares the station LLRS capabilities and processes such result or reason code in order to find another BSS and associate with it. It may also adapt the TXOP negotiation for a DiL or P2P TXOP, with respect to a TXOP limit known for a BSS it is associated with.

[0281] 802.11 MAC layer 1324 and LLRS management module 1325 interact one with the other in order to perform LLRS management of the BSSs and/or of the DiL TXOPs, according to embodiments of the invention.

[0282] On top of the Figure, application layer block 1321 runs an application that generates and receives data packets, for example data packets such as a video stream. Application layer block 1321 represents all the stack layers above MAC layer according to ISO standardization.

[0283] Although the present invention has been described hereinabove with reference to specific embodiments, the present invention is not limited to the specific embodiments, and modifications will be apparent to a skilled person in the art which lie within the scope of the present invention.

[0284] Many further modifications and variations will suggest themselves to those versed in the art upon referring to the foregoing illustrative embodiments, which are given by way of example only and which are not intended to limit the scope of the invention, that being determined solely by the appended claims. In particular the different features from different embodiments may be interchanged, where appropriate.

[0285] In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be advantageously used.