[go: up one dir, main page]

WO2025011770A1 - Commande d'utilisation de canal primaire pendant des opérations sur des canaux non primaires - Google Patents

Commande d'utilisation de canal primaire pendant des opérations sur des canaux non primaires Download PDF

Info

Publication number
WO2025011770A1
WO2025011770A1 PCT/EP2023/081327 EP2023081327W WO2025011770A1 WO 2025011770 A1 WO2025011770 A1 WO 2025011770A1 EP 2023081327 W EP2023081327 W EP 2023081327W WO 2025011770 A1 WO2025011770 A1 WO 2025011770A1
Authority
WO
WIPO (PCT)
Prior art keywords
sta
channel
primary
primary channel
nonprimary
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2023/081327
Other languages
English (en)
Inventor
Abhishek AMBEDE
Leif Wilhelmsson
Rocco Di Taranto
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025011770A1 publication Critical patent/WO2025011770A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • the present disclosure relates to wireless communications, and in particular, to controlling primary channel usage.
  • Wi-Fi also known as Wireless Local Area Network (WLAN) is a technology that currently mainly operates in the 2.4 GHz, the 5 GHz band, and the 6 GHz frequency bands.
  • WLAN Wireless Local Area Network
  • PHY physical
  • MAC medium access layer
  • Wi-Fi is generally operated in license-exempt bands, and as such, communication over Wi-Fi may be subject to interference sources from any number of known and unknown devices.
  • Wi-Fi is commonly used as wireless extensions to fixed broadband access, e.g., in domestic environments and hotspots, like airports, train stations and restaurants.
  • LBT listen before talk
  • CSMA/CA carrier sense multiple access with collision avoidance
  • a basic service set (BSS) in IEEE 802.11 (WLANs) typically comprises an AP STA which possibly serves one or more non-AP STAs associated with it. Every BSS has a primary channel, which is the common channel of operation for all STAs that are members of the BSS. For example, in a 20 MHz, 40 MHz, 80 MHz, 160 MHz or 320 MHz BSS the primary channel is a primary 20 MHz channel. Some frames such as beacon frames are always sent only on the primary 20 MHz channel.
  • a BSS whose operating bandwidth is larger than 20 MHz can also have a primary 40 MHz channel, a primary 80 MHz channel, etc. All primary channels of bandwidth wider than 20 MHz necessarily include at least the primary 20 MHz channel. Corresponding to the primary channel nomenclature, all channels other than a primary channel are termed corresponding nonprimary channels.
  • FIG. l is a diagram of an example illustrating channel bonding nomenclature and some related channel hierarchy.
  • the allowed transmission bandwidth is determined by first assessing whether the primary 20 MHz channel of the operating bandwidth is ‘idle’ and then assessing and appropriately cascading the nonprimary channels.
  • an 80 MHz transmission is composed of one primary 40 MHz channel and one secondary (i.e., nonprimary) 40 MHz channel.
  • the primary 40 MHz channel is itself composed of one primary 20 MHz channel and one secondary (i.e., nonprimary) 20 MHz channel. Even if channel bonding is aimed at improving the flexibility of transmissions, it still comes with significant limitations. As an example based on FIG. 1 and how a transmitter and receiver can interact to determine an allowed transmission bandwidth, if P2 happens to be not available at the receiver (while the whole 160 MHz is available at the transmitter), then only Pl can be used and this means that only 20 MHz in a 160 MHz channel may be used regardless of the status of P3 up to P8.
  • FIG. 2 An example of a proposed operation is shown in FIG. 2 which illustrates communication using a nonprimary channel when a primary channel is found busy due to OBSS transmissions.
  • FIG. 3 is a diagram of an example of a multi-BSS deployment wherein the proposed operation in, for example, IEEE 802.1 l-23/0797r0 in UHR SG could be beneficial.
  • the bold and dotted circles centered around API, AP2, and STA21 denote their coverage areas, respectively.
  • STA12 may detect ongoing OBSS communication in BSS2 and could therefore potentially leverage the proposed feature discussed in, for example, IEEE 802.1 l-23/0797r0 to transmit data in uplink to API using a secondary (i.e., nonprimary) channel instead- assuming that the OBSS managed by AP2, termed BSS2, also uses the primary channel of B S S 1.
  • BSS2 also uses the primary channel of B S S 1.
  • the IEEE 802.11 WLAN standard supports two physical layer (PHY) carrier sensing mechanisms that can help IEEE 802.11 WLAN stations (STAs) to assess and identify the “idle” and “busy” portions of their operating channels. These mechanisms are termed carrier sense/clear channel assessment (CS/CCA) mechanisms as described in, for example, IEEE 802.11-2020. CS/CCA using energy detection (ED) threshold —
  • PHY physical layer
  • CS/CCA carrier sense/clear channel assessment
  • ED energy detection
  • a STA is required to defer its transmissions over the channel while the energy it senses on the channel is at or above an ED threshold.
  • An example of a typical value of ED threshold for a 20 MHz channel is -62 dBm.
  • the ED threshold value is based on spectrum regulations and may differ for different frequency bands.
  • the CS/CCA using ED threshold is technology-neutral and enables STAs to co-exist with both Wi-Fi and non-Wi-Fi devices.
  • This mechanism relies on known signals specific to a technology. Thus, this mechanism works exclusively within one technology or family of technologies.
  • Wi-Fi if a STA detects the start of a signal with a valid IEEE 802.11 preamble (specifically the legacy preamble portion comprising legacy short training field, L-STF, legacy long training field L-LTF, and the legacy signal field, L-SIG) at, or above, the PD threshold in a particular channel, the STA is required to decode the preamble and to defer its transmissions over that channel for a duration corresponding to the frame length value that is indicated in the preamble. For example, a typical value of PD threshold for a 20 MHz channel is -82 dBm. Since the IEEE 802.11 preamble is only used for Wi-Fi signals, the CS/CCA using PD threshold limits STAs to co-exist with Wi-Fi devices only and therefore, mainly targets spectrum sharing among neighboring Wi-Fi networks.
  • the IEEE 802.11 WLAN standard (e.g., IEEE 802.11-2020) also supports a virtual carrier sensing mechanism using a network allocation vector (NAV).
  • NAV network allocation vector
  • This is a medium access control (MAC) layer mechanism, and it relies on information carried in the Duration field of the MAC headers of successfully decoded IEEE 802.11 frames that are detected at or above the receiver sensitivity level.
  • the minimum receiver sensitivity level as mandated by the IEEE 802.11 standard is -82 dBm for a 20 MHz channel (e.g., IEEE 802.11-2020).
  • the Duration field carries information about the impending use of the medium, and the STAs must defer from transmitting until the end of the read duration.
  • the NAV is an indicator, maintained by each STA, of time periods when transmission onto the wireless medium should not be initiated by the STA regardless of whether the STA’s CS/ CCA mechanism assesses the medium to be “busy” or “idle”.
  • a STA is mandated to set its NAV only if the detected and decoded frame includes the primary 20 MHz channel of the operating bandwidth of that STA.
  • the IEEE 802.11 standard does not dictate how a STA should behave below the minimum receiver sensitivity level that is mandated by the standard. Thus, if a valid IEEE 802.11 frame is detected by a STA at a level below -82 dBm for a 20 MHz channel, the STA is not required to set its NAV. Similar to the CS/ CCA mechanism using PD threshold, this virtual NAV mechanism is limited to be effective only within a specific technology - in this case, Wi-Fi.
  • the PD based CS/CCA and the NAV based carrier sensing mechanisms both rely on successfully detecting the start of and at least partially decoding IEEE 802.11 packets.
  • a STA that is expected to defer its transmissions may fail to perform carrier sensing using the PD based CS/CCA or NAV based mechanisms, for example - it may fail in detecting the start of a packet, or it may fail in decoding the preamble or the MAC header of a packet, or it may not be awake when a packet is being transmitted, or it may be busy with its own ongoing transmission or reception.
  • the IEEE 802.11 WLAN standard (e.g., IEEE 802.11-2020) supports two key NAV distribution mechanisms that can help an STA to reserve the medium for its use and avoid colliding transmissions that may cause interference during that STA’s use of the medium.
  • This mechanism involving request-to-send (RTS) and clear-to-send (CTS) control frames can be used by a transmitter STA immediately prior to transmitting a data packet or a burst of data packets to one or more receiver STAs, for example, for - o ensuring that the receiver STA(s) is(are) awake and ready for reception, and o reserving and protecting the transmit opportunity (TXOP) and preventing hidden node related interference (both for the data packet as well as a corresponding acknowledgement frame) by setting the NAVs at all neighboring STAs belonging to the same BSS as well as overlapping BSSs (OBSSs).
  • RTS request-to-send
  • CTS clear-to-send
  • FIG. 4 is a diagram of an example that illustrates communication using RTS/ CTS frame exchange and the corresponding NAV distribution.
  • the NAV is indicated for STAs that might receive the RTS frame, while other STAs might receive only the CTS frame, resulting in the lower NAV bar as shown (with the exception of the STA to which the RTS frame was addressed).
  • the STA may first transmit a CTS frame with the receiver address (RA) field equal to its own MAC address - this frame is termed as a CTS-to-self frame.
  • a data packet e.g., a packet encoded with a high data rate modulation and coding scheme, MCS, that may result in requiring a large transmit power backoff to satisfy transmit signal quality and unwanted emission requirements
  • the STA may first transmit a CTS frame with the receiver address (RA) field equal to its own MAC address - this frame is termed as a CTS-to-self frame.
  • RA receiver address
  • Such a CTS-to-self frame transmission may help to protect the medium in a wider coverage area than what may be possible by directly transmitting the data packet, e.g., when the data packet is transmitted with a lower transmit power than the CTS-to-self frame and/or if the data packet is encoded in a relatively less robust manner. Similar to the RTS/ CTS mechanism, the duration value in the CTS-to-self frame protects the pending transmission, plus possibly an acknowledgement frame.
  • Both RTS/CTS and CTS-to-self mechanisms are optional and are not used for all data packet transmissions. Because the additional RTS/ CTS/ CTS-to-self frames add overhead inefficiency, these mechanisms are not always justified, especially for short data packets. For instance, the RTS/CTS mechanism may only be used if the length of the PSDU to be communicated exceeds a threshold value indicated by dotl IRTSThreshold (e.g., IEEE 802.11-2020, Section 10.3.5). Compared to the RTS/CTS mechanism, the CTS-to-self mechanism is lower in network overhead cost but is less robust against hidden nodes and collisions.
  • dotl IRTSThreshold e.g., IEEE 802.11-2020, Section 10.3.5
  • RU resource unit
  • OFDM orthogonal frequency division multiplexing
  • PPDU physical layer protocol data unit
  • a transmission bandwidth can be split up into multiple RUs.
  • a 20 MHz transmission BW can constitute either nine 26-tone RUs, or four 52-tone RUs, or two 106-tone RUs, or one 242-tone RU.
  • This RU feature in HE is multiuser communication based on OFDMA, which is also a newly supported feature in HE.
  • OFDMA based multi-user communications in HE every user is allocated a single RU, possibly also with different RU sizes for different users.
  • HE supports downlink OFDMA as well as uplink OFDMA transmissions.
  • EHT Extremely High Throughput
  • HE supports the allocation of only one RU per STA
  • the IEEE 802.1 Ibe (Extremely High Throughput, EHT) amendment extends this further to support the allocation of more than one RU to a single STA (e.g., as described in IEEE P802.1 Ibe D3.0).
  • EHT also supports new RU sizes that are derived from the combinations of the different RU sizes defined in HE.
  • API tries to schedule downlink or uplink multi-user communications, e.g., using orthogonal frequency division multiplexed access (OFDMA) involving STA12 and does not know that STA12 cannot access the primary channel (e.g., due to ongoing OBSS transmissions over the primary channel)
  • OFDMA orthogonal frequency division multiplexed access
  • Embodiments of the present disclosure provide configurations for controlling primary channel usage.
  • a method implemented in an access point station, AP STA that is configured to wirelessly communicate with a first non- access point station, non-AP STA, in a wireless communication system employing listen- before-talk, LBT, and the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel.
  • the method comprises receiving, from the first non-AP STA on the nonprimary channel, an uplink transmission, based on the first non-AP STA’s LBT assessment that the nonprimary channel is idle and the primary channel is busy due to its usage in an overlapping second BSS, and transmitting, on the primary channel, a control frame to control the usage of the primary channel by one or more non-AP STAs of the first BSS.
  • the control frame transmitted on the primary channel by the AP STA may be arranged to cause one out of the following controlled usage actions: non-AP STAs of the first BSS omit transmitting on the primary channel, at least one second non-AP STA transmits an uplink transmission to the AP STA on the primary channel, and at least one second non-AP STA transmits a peer-to-peer transmission to at least one third non-AP STA on the primary channel.
  • a duration of the caused controlled usage action on the primary channel may be arranged not to exceed a duration indicated in the control frame transmitted by the AP STA, and where the duration indicated in the control frame may correspond to an expected duration of a communication on the nonprimary channel between the AP STA and the first non-AP STA.
  • the uplink transmission or the peer-to-peer transmission on the primary channel may be time-aligned with transmissions on the nonprimary channel, for example, on an OFDM symbol level.
  • the uplink transmission received from the first non-AP STA on the nonprimary channel may be a control frame sent by the first non-AP STA prior to sending an uplink data transmission.
  • the control frame sent by the first non-AP STA on the nonprimary channel may be a request-to-send, RTS, frame, clear-to-send-to-self, CTS-to-self, control frame, or any new type of control frame formed for this purpose.
  • the wireless communication system may be based on a Wireless Local Area Network technology according to the IEEE 802.11 standards family.
  • the primary channel may be a primary 20 MHz channel, or a primary 40 MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • the control frame transmitted on the primary channel by the AP STA may be a clear-to-send, CTS, frame or a CTS-to-self frame, or any suitably modified version of either of the two or new type of control frame.
  • the control frame transmitted on the primary channel by the AP STA may be a trigger frame.
  • a method implemented in a first non-access point station, non-AP STA that is configured to wirelessly communicate with an access point station, AP STA, in a wireless communication system employing listen- before-talk, LBT, where the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel.
  • the method comprises assessing the primary and nonprimary channels, wherein the non-AP STA assesses when the nonprimary channel is idle, and the primary channel is busy due to its usage in an overlapping second BSS.
  • the non-AP STA notifies on the nonprimary channel, the AP STA about inability to communicate using the primary channel, and the non-AP STA receives a scheduling of communication involving the non-AP STA, wherein the scheduling does not allocate frequency resources of the primary channel to first STA.
  • the notifying of the AP STA on the nonprimary channel may comprise transmitting a control frame.
  • the notifying of the AP STA may be performed using one out of a single bit to indicate the idle/busy status of the primary channel, and a bitmap to indicate idle/busy status of multiple subchannels, the multiple subchannels at least including the primary channel.
  • the notifying of the AP STA on the nonprimary channel may further comprise a duration of inability to communicate using the primary channel, where the notified duration corresponds to the identified duration of the overlapping second BSS’s communications on the primary channel.
  • the notifying of the AP STA may further comprise a duration of inability to communicate using the primary channel when the identified duration of the overlapping second BSS’s communications on the primary channel is larger than a threshold.
  • the method may further comprise that the threshold is determined by the AP STA, or by the non-AP STA, or by means of negotiation between the AP STA and the non-AP STA.
  • the wireless communication system may be based on a Wireless Local Area Network technology according to the IEEE 802.11 standards family.
  • the primary channel may be a primary 20 MHz channel, or a primary 40 MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • an access point station AP STA, that is configured to wirelessly communicate with a first non-access point station, non-AP STA, in a wireless communication system employing listen-before-talk, LBT, and the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel.
  • the AP STA is configured to perform the method according to the first aspect.
  • a non-access point station configured to wirelessly communicate with an access point station, AP STA, in a wireless communication system employing listen-before-talk, LBT, where the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel.
  • the non-AP STA is configured to perform the method according to the second aspect.
  • an AP STA While being engaged in communications on nonprimary channels, it is described herein for an AP STA to control the primary channel’s usage in its BSS, whenever possible. Such controlling could help, for example, to avoid ‘likely to fail’, ‘uncontrolled’ or ‘undesired’ transmission attempts by non-AP STAs that are not engaged in communications using nonprimary channels. It could also help, for example, to orchestrate communications on the primary channel to improve their likelihood of succeeding. Different embodiments are provided to elaborate on how the primary channel’s usage may be controlled - communications on the primary channel could either be avoided, or be enabled in a controlled manner.
  • a non-AP STA may inform its associated AP STA about the inability to communicate using the primary channel of its BSS for a certain duration due to ongoing OBSS transmissions.
  • Related embodiments are introduced wherein the AP STA could take this information into account while scheduling multi-user communications involving the non-AP STA.
  • FIG. l is a diagram of an example illustrating channel bonding nomenclature and some related channel hierarchy
  • FIG. 2 is a diagram of an example communication using a nonprimary channel when a primary channel is found busy due to OBSS transmissions;
  • FIG. 3 is a diagram of an example multi-BSS deployment with STA12 in range of AP2 and STA21;
  • FIG. 4 is a diagram of an example that illustrates communication using RTS/ CTS frame exchange and the corresponding NAV distribution
  • FIG. 5 is a block diagram of a STA1 communicating with a STA2 over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 6 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 7 is a block diagram of a host computer communicating via a STA1 with a STA2 over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a STA1 and a STA2 for executing a client application at a STA2 according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a STA1 and a STA2 for receiving user data at a STA2 according to some embodiments of the present disclosure
  • FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a STA1 and a STA2 for receiving user data from the STA2 at a host computer according to some embodiments of the present disclosure
  • FIG. 11 is a flowchart illustrating example methods implemented in a communication system including a host computer, a STA1 and a STA2 for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 12 is a flowchart illustrating a method performed in an AP STA according to embodiments
  • FIG. 13 is a flowchart illustrating a method performed in a non-AP STA according to embodiments
  • FIG. 14 is a flowchart of an example process in an AP STA according to some embodiments of the present disclosure.
  • FIG. 15 is a flowchart of an example process in a first STA according to some embodiments of the present disclosure.
  • FIG. 16 is a diagram of an example usage of one or more embodiments of Example Group 1.
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the term “access point” or “AP” is used interchangeably and may comprise, or be, a network node.
  • the AP may include any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in
  • the non-limiting term “device” is used to describe a wireless device (WD) and/or user equipment (UE) that may be used to implement some embodiments of the present disclosure.
  • the device may be and/or comprise an access point (AP) station (STA).
  • the device may be and/or comprise a non-access point station (non-AP STA).
  • the device may be any type of device capable of communicating with a network node, such as an AP, over radio signals.
  • the device may be any radio communication device, target device, a portable device, device-to-device (D2D) device, machine type device or device capable of machine to machine communication (M2M), low-cost and/or low-complexity device, a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, Reduced Capability (RedCap) device, etc.
  • D2D device-to-device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • low-cost and/or low-complexity device a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or
  • a device may be considered a network node and may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware.
  • the network node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the network node is said to be virtualized.
  • a network node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.
  • a STA1 may be the transmitter and the receiver is the STA2.
  • the transmitter may be the STA2 and the receiver is the STA1.
  • the STA1 may be an AP or non-AP STA
  • the STA2 may be an AP or a non-AP STA.
  • STA1 STA2
  • STA3 STA3
  • stations and/or devices e.g., APs, non-AP STAs, user equipment, wireless devices, mobile terminals, etc.
  • IEEE 802.11 denotes a set of Wireless Local Area Network (WLAN) air interface standards developed by the IEEE 802.11 committee for short-range communications (e.g., tens of meters to a few hundred meters).
  • WLAN Wireless Local Area Network
  • Some embodiments may also be supported by standard documents disclosed in Third Generation Partnership Project (3GPP) technical specifications. That is, some embodiments of the description can be supported by the above documents.
  • 3GPP Third Generation Partnership Project
  • wireless systems such as, for example, IEEE 802.11, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), 5th Generation (5G) and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system.
  • Other wireless systems including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by one or more of a first STA, second STA, transmitting STA, receiving STA, AP, non-AP STA, wireless device, network node, etc. may be distributed over a plurality of STAs, APs, non-AP STAs, wireless devices, network nodes, etc.
  • the functions of the devices described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • Puncturing may refer to a situation where STA may assume that no transmission to the STA is present in a part of the bandwidth.
  • some of the DL resources are nominally allocated to DL data (or UL data), but have been ‘punctured’ by, i.e., replaced with, e.g., control information, other data information, etc., that is not associated with the DL data (or UL data), which may occur in a puncturing region. Puncturing may mean, e.g., that the bits (and/or symbols, etc.) in the affected resource units are replaced with “new” information.
  • FIG. 5 a block diagram of the communication system 10, according to one embodiment, constructed in accordance with the principles of the present disclosure.
  • the communication system 10 in FIG. 5 is a non-limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and/or networks.
  • system 10 may comprise a wireless local area network (WLAN) 12.
  • WLAN wireless local area network
  • the devices in the system 10 may communicate over one or more spectrums, such as, for example, an unlicensed spectrum, which may include frequency bands typically used by Wi-Fi technology.
  • One or more of the devices may be further configured to communicate over other frequency bands, such as shared licensed frequency bands, etc.
  • the WLAN 12 includes a STA1 14 and a STA2 16. Note that although a single STA1 14 and a single STA2 16 are shown for convenience, the communication system 10 may include many more STA1 14 and STA2 16. Each STA1 14 may connect to/serve/configure/schedule/etc. one or more STA2 16 (or vice-versa). In some embodiments, STA1 may include identical hardware and/or software as STA2. For example, STA1 and STA2 may be similar models of non-AP STAs, such as a user equipment or mobile terminals, or both STA1 and STA 2 may be APs, such as base stations, etc.
  • STA1 may include one or more different hardware and/or software components compared to STA2.
  • STA1 may be an AP or a non-AP STA
  • STA2 may be a different type of device, such as a non-AP STA or an AP, respectively.
  • system 10 may include additional nodes/devices not shown in FIG. 5.
  • system 10 may include many more connect! ons/interfaces than those shown in FIG. 5.
  • the elements shown in FIG. 5 are presented for ease of understanding.
  • a STA1 14 and/or a STA2 16 can be in communication and/or configured to separately communicate with more than one STA2 16 and/or more than one type of STA1 14, e.g., for coordination of scheduling, transmission of data or control signaling, RU allocation, controlling primary channel usage, etc., which may be via wired and/or wireless communication channels.
  • a STA1 14 is configured to include an AP unit 18, which is configured to perform one or more STA1 functions described herein.
  • a STA2 16 is configured to include notification unit 19, which is configured to perform one or more STA2 16 functions described herein.
  • the STA1 14 includes hardware 20 including a communication interface 22, processing circuitry 24, a processor 26, and memory 28.
  • the communication interface 22 may be configured to communicate with any of the nodes/devices in the system 10 according to some embodiments of the present disclosure, such as with one or more other STAls 14 and/or one or more STA2s 16.
  • the communication interface 22 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • the communication interface 22 may also include a wired interface.
  • the processing circuitry 24 may include one or more processors 26 and memory, e.g., memory 28.
  • the processing circuitry 24 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 26 may be configured to access (e.g., write to and/or read from) the memory 28, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the memory 28 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the STA1 14 may further include software 30 stored internally in, for example, memory 28, or stored in external memory (e.g., database) accessible by the STA1 14 via an external connection.
  • the software 30 may be executable by the processing circuitry 24.
  • the processing circuitry 24 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., STA1 14.
  • the memory 28 is configured to store data, programmatic software code and/or other information described herein.
  • the software 30 may include instructions stored in memory 28 that, when executed by the processor 26 and/or AP unit 18 causes the processing circuitry 24 and/or configures the STA1 14 to perform the processes described herein with respect to the STA1 14.
  • STA1 14 may also include a notification unit 19.
  • the STA2 16 includes hardware 32, which may include a communication interface 34, processing circuitry 36, a processor 38, and memory 40.
  • the communication interface 34 may be configured to communicate with one or more STA1 14, such as via wireless connection 35, and/or with other elements in the system 10, according to some embodiments of the present disclosure.
  • the communication interface 34 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • RF radio frequency
  • the communication interface 34 may also include a wired interface.
  • the processing circuitry 36 may include one or more processors 38 and memory, such as, the memory 40. Furthermore, in addition to a traditional processor and memory, the processing circuitry 36 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors 38 and memory such as, the memory 40.
  • the processing circuitry 36 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 38 may be configured to access (e.g., write to and/or read from) the memory 40, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the memory 40 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the STA2 16 may further include software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database) accessible by the STA2 16 via an external connection.
  • the software 42 may be executable by the processing circuitry 36.
  • the processing circuitry 36 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the STA2 16.
  • the memory 40 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 40 that, when executed by the processor 38 and/or notification unit 19, causes the processing circuitry 36 and/or configures the STA2 16 to perform the processes described herein with respect to the STA2 16.
  • STA2 16 may also be configured with notification unit 19 for performing STA2 16 function as described herein.
  • FIG. 5 shows AP unit 18 and notification unit 19, as being within a respective processor, it is contemplated that this element may be implemented such that a portion of the element is stored in a corresponding memory within the processing circuitry. In other words, the element may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 6 is a schematic diagram of a communication system 10, according to some embodiments of the present disclosure.
  • STA1 14 and STA2s 16 may be similar to those of the example of FIG. 5, described herein.
  • STA1 14 may be an access point (AP) and STA2 16 may be a non-AP STA, but are not limited to these types of devices.
  • STA1 14 may be a non-AP STA
  • STA2 16 may be an AP, or both may be APs, both may be non-AP STAs, etc.
  • the classification of a device as an AP and/or as a non-AP STA may depend on the context or configuration.
  • one or more STAls 14 and/or STA2s 16 may form and/or be part of a service set network 44 (e.g., a basic service set, or any other network, set, and/or grouping of STAls 14 and STA2s 16).
  • the communication system 10 and/or service set network 44 may itself be connected to a host computer 46, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 46 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 48, 50 between the communication system 10 and/or the service set network 44 and the host computer 46 may extend directly from the service set network 44 to the host computer 46 or may extend via an optional intermediate network 52.
  • the intermediate network 52 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 52 if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 52 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 6 as a whole enables connectivity between one of the connected STA2s 16 and the host computer 46.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 46 and the connected STA2s 16 are configured to communicate data and/or signaling via the OTT connection, using the service set network 44, any intermediate network 52 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • an STA1 14 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 46 to be forwarded (e.g., handed over) to a connected STA2 16. Similarly, the STA1 14 need not be aware of the future routing of an outgoing uplink communication originating from the STA2 16 towards the host computer 46.
  • the STA1 14 and the STA2 16 may have similar features and components as the STA1 14 and STA2 16 depicted in FIG. 5.
  • the host computer 46 comprises hardware (HW) 53 including a communication interface 54 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 46 further comprises processing circuitry 56, which may have storage and/or processing capabilities.
  • the processing circuitry 56 may include a processor 58 and memory 60.
  • the processing circuitry 56 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 58 may be configured to access (e.g., write to and/or read from) memory 60, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 60 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 56 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 46.
  • Processor 58 corresponds to one or more processors 58 for performing host computer 46 functions described herein.
  • the host computer 46 includes memory 60 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 62 and/or the host application 64 may include instructions that, when executed by the processor 58 and/or processing circuitry 56, causes the processor 58 and/or processing circuitry 56 to perform the processes described herein with respect to host computer 46.
  • the instructions may be software associated with the host computer 46.
  • the software 62 of host computer 46 may be executable by the processing circuitry 56.
  • the software 62 includes a host application 64.
  • the host application 64 may be operable to provide a service to a remote user, such as a STA2 16 connecting via an OTT connection 66 terminating at the STA2 16 and the host computer 46.
  • the host application 64 may provide user data which is transmitted using the OTT connection 66.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 46 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 56 of the host computer 46 may enable the host computer 46 to observe, monitor, control, transmit to and/or receive from the STA1 14 and/or the STA2 16.
  • the processing circuitry 56 of the host computer 46 may include a Cloud Configuration unit 68 configured to enable the service provider to observe/monitor/control/transmit to/receive from/configure/etc. the STA1 14 and/or the STA2 16.
  • the communication interface 22 of STA1 14 may be configured to facilitate a connection 66 to the host computer 46.
  • the connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and/or through one or more intermediate networks 52 outside the communication system 10.
  • the communication interface 34 of STA2 16 may be configured to facilitate a connection 66 to the host computer 46.
  • the connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and/or through one or more intermediate networks 52 outside the communication system 10.
  • the software 42 of STA2 16 may include a client application 70.
  • the client application 70 may be operable to provide a service to a human or non-human user via the STA2 16, with the support of the host computer 46.
  • an executing host application 64 may communicate with the executing client application 70 via the OTT connection 66 terminating at the STA2 16 and the host computer 46.
  • the client application 70 may receive request data from the host application 64 and provide user data in response to the request data.
  • the OTT connection 66 may transfer both the request data and the user data.
  • the client application 70 may interact with the user to generate the user data that it provides.
  • the inner workings of the STA1 14, STA2 16, and host computer 46 may be as shown in FIG. 7 and independently, the surrounding network topology may be that of FIG. 6.
  • the OTT connection 66 has been drawn abstractly to illustrate the communication between the host computer 46 and the STA2 16 via the STA1 14, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which may be configured to hide from the STA2 16 or from the service provider operating the host computer 46, or both. While the OTT connection 66 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 35 between the STA2 16 and the STA1 14 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the STA2 16 using the OTT connection 66, in which the wireless connection 35 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 66 may be implemented in the software 62 of the host computer 46 or in the software 42 of the STA2 16, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 66 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 62, 42 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 66 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the STA1 14, and it may be unknown or imperceptible to the STA1 14. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary wireless device signaling facilitating the host computer’s 46 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 62, 42 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 66 while it monitors propagation times, errors, etc.
  • the host computer 46 includes processing circuitry 56 configured to provide user data and a communication interface 54 that is configured to forward the user data to a wireless network and/or cellular network for transmission to the STA2 16.
  • the wireless network and/or cellular network also includes the STA1 14 with a communication interface 22.
  • the STA1 14 is configured to, and/or the STA1 14 processing circuitry 24 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the STA2 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the STA2 16.
  • the host computer 46 includes processing circuitry 56 and a communication interface 54 that is configured to receive user data originating from a transmission from a STA2 16 to an STA1 14.
  • the STA2 16 is configured to, and/or comprises a communication interface 34 and/or processing circuitry 36 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the STA1 14, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the STA1 14.
  • FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 6 and 7, in accordance with one embodiment.
  • the communication system may include a host computer 46, an STA1 14 and a STA2 16, which may be those described with reference to FIG. 7.
  • the host computer 46 provides user data (Block SI 00).
  • the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64 (Block SI 02).
  • the host computer 46 initiates a transmission carrying the user data to the STA2 16 (Block S104).
  • the STA1 14 transmits to the STA2 16 the user data which was carried in the transmission that the host computer 46 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the STA2 16 executes a client application, such as, for example, the client application 70, associated with the host application 64 executed by the host computer 46 (Block SI 08).
  • FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 7, in accordance with one embodiment.
  • the communication system may include a host computer 46, a STA1 14, and a STA2 16.
  • the host computer 46 provides user data (Block SI 10).
  • the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64.
  • the host computer 46 initiates a transmission carrying the user data to the STA2 16 (Block SI 12).
  • the transmission may pass via the STA1 14, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the STA2 16 receives the user data carried in the transmission (Block SI 14).
  • FIG. 10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 7, in accordance with one embodiment.
  • the communication system may include a host computer 46, an STA1 14 and a STA2 16.
  • the STA2 16 receives input data provided by the host computer 46 (Block SI 16).
  • the STA2 16 executes the client application 70, which provides the user data in reaction to the received input data provided by the host computer 46 (Block SI 18).
  • the STA2 16 provides user data (Block S120).
  • the STA2 16 provides the user data by executing a client application, such as, for example, client application 70 (Block S122).
  • client application 70 may further consider user input received from the user.
  • the STA2 16 may initiate, in an optional third substep, transmission of the user data to the host computer 46 (Block S124).
  • the host computer 46 receives the user data transmitted from the STA2 16, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 11 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 7, in accordance with one embodiment.
  • the communication system may include a host computer 46, an STA1 14 and a STA2 16.
  • the STA1 14 receives user data from the STA2 16 (Block S128).
  • the STA1 14 initiates transmission of the received user data to the host computer 46 (Block S130).
  • the host computer 46 receives the user data carried in the transmission initiated by the STA1 14 (Block S132).
  • FIG. 12 is a flowchart illustrating a method performed in an AP STA.
  • the AP STA is configured to wirelessly communicate with at least a first non-access point station, non- AP STA, in a wireless communication system employing listen-before-talk, LBT, as elucidated above.
  • the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel according to the channel bonding approach described above.
  • the first non-AP STA is here assumed to be present in an environment where the first BSS overlaps with a second BSS operated by another AP STA.
  • the method comprises receiving S144 an uplink transmission from the first non-AP STA on the nonprimary channel (but not on the primary channel).
  • the AP STA will thus be able to know that the first non-AP STA’s LBT assessment was that the nonprimary channel is idle and the primary channel is busy due to its usage in an overlapping second BSS. Then, the AP STA carries on with transmitting S146 a control frame, on the primary channel, to control the usage of the primary channel by one or more non-AP STAs, i.e., other non-AP STAs than the first non-AP STA, of the first BSS.
  • the control frame transmitted on the primary channel by the AP STA may be arranged to cause one out of the following controlled usage actions:
  • At least one second non-AP STA transmits an uplink transmission to the AP STA on the primary channel
  • At least one second non-AP STA transmits a peer-to-peer transmission to at least one third non-AP STA on the primary channel.
  • the control frame transmitted on the primary channel by the AP STA may be a clear-to-send, CTS, frame or a CTS-to-self frame or a suitably modified version of either of the two.
  • a new type of control frame, not present in legacy protocol, is also feasible for transmitting on the primary channel for this purpose.
  • the control frame transmitted on the primary channel by the AP STA may be a trigger frame.
  • a purpose of the trigger frames is to allocate time and/or frequency resources and solicit one or more uplink trigger-based physical layer protocol data unit, TB PPDU, transmissions.
  • the trigger frame can be used to solicit the uplink data from one or more non-AP STAs.
  • Trigger frames may also be used to provide time and/or resources for peer-to-peer transmissions.
  • a duration of the caused controlled usage action on the primary channel may be arranged not to exceed a duration indicated in the control frame transmitted by the AP STA, and where the duration indicated in the control frame may correspond to an expected duration of a communication on the nonprimary channel between the AP STA and the first non-AP STA.
  • the uplink transmission or the peer-to-peer transmission on the primary channel may be time-aligned with transmissions on the nonprimary channel, for example, on an OFDM symbol level.
  • the uplink transmission received from the first non-AP STA on the nonprimary channel may be a control frame sent by the first non-AP STA prior to sending an uplink data transmission.
  • the control frame sent by the first non-AP STA on the nonprimary channel may be a request-to-send, RTS, frame, a clear-to-send-to-self, CTS-to-self, control frame, or a new type of control frame defined in a future amendment to the IEEE 802.11 WLAN standard.
  • FIG. 13 is a flowchart illustrating a method performed in a non-AP STA according to embodiments.
  • the context of the non-AP STA is that of the first non-AP STA, i.e., when operating in the overlapping area of BSSs.
  • the non-AP STA is configured to wirelessly communicate with an access point station, AP STA, in a wireless communication system employing listen-before-talk, LBT, where the AP STA operates a first basic service set, BSS, involving a primary channel and a nonprimary channel.
  • the method comprises, when assessing the primary and nonprimary channels, and the nonprimary channel is idle, and the primary channel is busy due to its usage in an overlapping second BSS, notifying S148, on the nonprimary channel, the AP STA about the non-AP STA's inability to communicate using the primary channel.
  • the non-AP STA can then transmit S150 an uplink transmission on the nonprimary channel, and thus omitting transmission on the primary channel.
  • the uplink transmission SI 50 may be preceded by receiving a CTS from the AP STA on the non-primary channel.
  • the notification on the nonprimary channel may be a control frame sent prior to sending an uplink data transmission.
  • the control frame can be a request-to-send, RTS, frame, a clear-to-send-to-self, CTS-to-self, control frame, or a new type of control frame defined in a future amendment to the IEEE 802.11 WLAN standard.
  • the wireless communication system may be based on a Wireless Local Area Network technology according to the IEEE 802.11 standards family, from which the used terminology is picked, but also other communication systems may benefit from the approach.
  • the primary channel can be a primary 20 MHz channel, or a primary 40 MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • FIG. 14 is a flowchart of an example process in a AP STA (e.g., STA1 14) that is configured to communicate with one or more second STA2s 16 (e.g., receiving STAs, such as an AP or a non-AP STA) according to one or more embodiments of the present disclosure.
  • a AP STA e.g., STA1 14
  • second STA2s 16 e.g., receiving STAs, such as an AP or a non-AP STA
  • one or more Blocks and/or functions and/or methods performed by the first STA1 14 may be performed by one or more elements of STA1 14, such as by AP unit 18 in processing circuitry 24, memory 28, processor 26, communication interface 22, etc.
  • AP STA (e.g., STA1 14) is configured to receive (Block S140), from the first STA (e.g., STA2 16), an indication of an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • the AP STA (e.g., STA 14) is further configured to schedule multi-user downlink or uplink communications involving the first STA where the scheduling does not allocate frequency resources of the primary channel to the first STA.
  • the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • FIG. 15 is a flowchart of an example process in a first STA (e.g., STA2 16) that is configured to wirelessly communicate with an AP STA (e.g., STA1 14) in a wireless communication system according to one or more embodiments of the present disclosure.
  • a first STA e.g., STA2 16
  • AP STA e.g., STA1 14
  • FIG. 15 is a flowchart of an example process in a first STA (e.g., STA2 16) that is configured to wirelessly communicate with an AP STA (e.g., STA1 14) in a wireless communication system according to one or more embodiments of the present disclosure.
  • AP STA e.g., STA1 14
  • FIG. 15 is a flowchart of an example process in a first STA (e.g., STA2 16) that is configured to wirelessly communicate with an AP STA (e.g., STA1 14) in a
  • First STA (e.g., STA2 16) is configured to indicate (Block S142), to AP STA (e.g., STA1 14), an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • the first STA (e.g., STA2 16) is further configured to receive a scheduling of multi-user downlink or uplink communications involving the first STA where the scheduling does not allocate frequency resources of the primary channel to the first STA.
  • the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • the primary channel term may refer to a primary 20 MHz channel, or a primary 40MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • FIG. 16 is a diagram of an example usage of one or more embodiments of Example Group 1 (described below).
  • API e.g., STA1 14
  • API can then transmit a control frame not only on the S80 channel (e.g., a CTS frame in response to the RTS frame sent by STA 12), but also on the P80 channel - in order to, for example, implicitly or explicitly notify all STAs (e.g., STA2s 16) in its BSS1 about its ongoing communications on the nonprimary channel for a certain upcoming duration.
  • control frame transmission on the primary channel could be a CTS-to-self frame. What may matter with the control frame is spreading the information corresponding to duration of ongoing communications on the nonprimary channel, so that the STAs in the BSS1 can set their NAVs appropriately in both primary and nonprimary channels.
  • the control frame could also be a suitably modified version of the CTS frame or the CTS-to-self frame, or a new type of control frame defined in a future amendment to the IEEE 802.11 WLAN standard, which may be useful if there are no 'legacy pre-UHR' STAs present (as may be the case in some frequency bands).
  • API could rather enable its usage in a controlled manner. This could be performed, for example, by means of triggered communications.
  • API could send a trigger frame (another example of a control frame) to enable peer-to-peer communications among non-AP STAs at least on the primary channel, for example, letting STA11 and STA I 3 communicate with each other in FIG. 3.
  • the trigger frame could solicit uplink transmissions on the primary channel, e.g., from STA12 or STA13 or both (e.g., if such transmissions are multiplexed in the primary channel).
  • the durations of the potential peer-to- peer communications or uplink transmissions may be aligned with the durations of the communications on the nonprimary channel(s) - for example, it may be mandated that the communications on the primary channel should not exceed the duration of the communications on the nonprimary channel.
  • the potential peer-to-peer communications or uplink transmissions may be time-aligned with the communications on the nonprimary channel(s), for example, on an OFDM symbol level. This could help to avoid potential interference arising from unaligned parallel reception of independent transmissions on adjacent channels.
  • the control frame transmitted by API on the primary channel may be transmitted while transmitting (e.g., a control frame such as a CTS frame) on the nonprimary channel or while receiving (e.g., a data frame) on the nonprimary channel.
  • FIG. 16 illustrates an example of the former case.
  • a capability to transmit on the primary channel while simultaneously receiving on the nonprimary channel would involve higher implementation complexity (e.g., to be able to sufficiently mitigate self-interference) compared with a capability of only either transmitting or receiving simultaneously on the primary and nonprimary channels.
  • STA12 e.g., STA2s 16
  • API e.g., STA1 14
  • STA12 upon detecting that the primary channel of B SSI is occupied by communications in BSS2 for a certain duration, notifies API (e.g., STA1 14) about its inability to communicate using such primary channel.
  • Such notification could be, for example, sent using a control frame on its nonprimary channel (which is not used in BSS2).
  • the notification may, for example, be performed using: a. either a single bit to indicate the idle/busy status of the primary channel; b. or a bitmap to indicate idle/busy status of multiple subchannels, the multiple subchannels at least including the primary channel.
  • Such notification could also include information regarding the duration of inability to communicate using the primary channel, where the notified duration corresponds to the identified duration of OBSS communications on the primary channel.
  • notifications may be restricted to be sent only when the OBSS communications on the primary channel are identified to be of a duration larger than a threshold.
  • a threshold may be decided by the AP, the non-AP STAs themselves, or via means of negotiation among them.
  • API may effectively schedule single-user or multiuser communications in its BSS, by not allocating frequency resources of the primary channel to STA12. For example, if API has buffered downlink traffic for both STA11 and STA12, it could use the primary channel P80 to deliver traffic to STA11 and the nonprimary channel S80 to deliver traffic to STA12. One reason for this choice is that API knows that the S80 is interference-free for STA12 (while the P80 is interfered). In a similar way, API may trigger, for example using a TF (trigger frame), uplink transmissions from STA11 and STA12, i.e., API may request UL transmission from STA11 on the primary channel P80 and from STA12 on the nonprimary channel S80. This is because STA12 can use S80 channel freely (which is not the case for its primary channel P80 that is being used in BSS2). Such multi-user communications could be orchestrated by the AP using existing standardized features such as OFDMA.
  • transmission of a control frame, or orchestration of different types of communications on the primary channel in a BSS as proposed in the present disclosure may result in undesirable interference caused to ongoing communications in the OBSS.
  • the existing carrier sensing mechanism has not triggered a medium busy indication corresponding to the primary channel at a STA due to OBSS transmissions, it is free to attempt transmissions on the primary channel.
  • none of the embodiments or solutions described herein may involve breaking any existing LBT rules. All the proposed transmissions on the primary channel, e.g., transmission of a control frame by an AP STA to spread information about nonprimary channel usage, when the primary channel is being used in another BSS are based on obeying all existing LBT rules. Usage of mechanisms such as RTS-CTS frame exchanges in an OBSS should also automatically enable good protection for the corresponding communications.
  • Example 1 A A method for an AP STA (e.g., STA1 14) to control primary channel usage while being involved in communications on nonprimary channel(s), wherein the controlling involves transmitting a control frame on the primary channel.
  • STA e.g., STA1 14
  • Example 2 A As in Example 1 A, wherein the control frame transmitted on the primary channel is a CTS frame or a CTS-to-self frame, or a suitably modified version of either of the two, or a new type of control frame.
  • Example 3 A As in Example 2A, wherein if the control frame is a CTS frame, it is sent together with a similar CTS frame transmitted on the nonprimary channel(s) that is(are) being used for ongoing communications.
  • Example 4 A As in Example 1 A, wherein the control frame transmitted on the primary channel is trigger frame.
  • Example 5A As in Example 4A, wherein the trigger frame is sent to enable peer- to-peer communications among non-AP STAs (e.g., STA2s 16) on at least the primary channel.
  • non-AP STAs e.g., STA2s 16
  • Example 6A As in Example 4A, wherein the trigger frame is sent to solicit uplink transmissions on the primary channel.
  • Example 7A As in Example 5 A or 6A, wherein the durations of the potential peer-to-peer communications or uplink transmissions are aligned with the durations of the communications on the nonprimary channel(s).
  • Example 8A As in Example 7A, where the alignment is such that the potential peer-to-peer communications or uplink transmissions do not exceed the duration of the communications on the nonprimary channel(s).
  • Example 9 A As in one or more of Examples 5A-8A, wherein the potential peer- to-peer communications or uplink transmissions are time-aligned with the communications on the nonprimary channel(s), for example, on an OFDM symbol level.
  • Example 10 A As in one or more of Examples 1 A-9A, wherein the primary channel is a primary 20 MHz channel, or a primary 40MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • Example IB A method for a non-AP STA (e.g., STA2 16) to notify its associated AP STA (e.g., STA1 14) about inability to communicate using a primary channel of its BSS for a certain duration due to ongoing OBSS transmissions on the primary channel, wherein the notification is sent using a control frame sent on a nonprimary channel.
  • STA2 16 a non-AP STA
  • STA1 14 e.g., STA1 14
  • Example 2B As in Example IB, wherein the AP STA schedules multi-user downlink or uplink communications involving the non-AP STA by taking into account the information shared by the non-AP STA, and wherein the AP STA does not allocate frequency resources corresponding to the primary channel to the non-AP STA.
  • Example 3B As in one or more of Examples 1B-2B, wherein the primary channel is a primary 20 MHz channel, or a primary 40MHz channel, or a primary 80 MHz channel, or a primary 160 MHz channel.
  • one or more embodiments and/or examples provide at least the following advantage: enables a STA (e.g, an AP STA) to control the usage of the primary channel of its BSS in order to avoid undesired transmissions on the primary and nonprimary channels as well as potential interference to the ongoing communications in the same or overlapping BSS, or to orchestrate communications on the primary channel in a controlled manner, or to better enable multi-user communications in the BSS.
  • a STA e.g, an AP STA
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • Embodiment Al A method implemented in an access point station, AP STA, that is configured to wirelessly communicate with first STA in a wireless communication system, the method comprising: transmitting information related to ongoing communications on a nonprimary channel to control primary channel usage, the information being configured to trigger the first STA to set a network allocation vector, NAV, for both primary and nonprimary channels.
  • NAV network allocation vector
  • Embodiment A2 The method of Embodiment Al, wherein the information corresponds to a control frame that is transmitted on the primary channel.
  • Embodiment A3 The method of Embodiment Al, wherein the control frame is a clear-to-send, CTS, frame or a CTS-to-self frame.
  • Embodiment A4 The method of Embodiment A2, wherein the information corresponds to a trigger frame that is configured to enable peer-to-peer communications among a plurality of non-AP STAs on at least the primary channel, the non-AP STAs including the first STA.
  • Embodiment A5 The method of any one of Embodiments A1-A4, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment Bl An access point station, AP STA, configured to wirelessly communicate with first STA in a wireless communication system, the AP STA configured to: transmit information related to ongoing communications on a nonprimary channel to control primary channel usage, the information being configured to trigger the first STA to set a network allocation vector, NAV, for both primary and nonprimary channels.
  • NAV network allocation vector
  • Embodiment B2 The AP STA of Embodiment Bl, wherein the information corresponds to a control frame that is transmitted on the primary channel.
  • Embodiment B3 The AP STA of Embodiment Bl, wherein the control frame is a clear-to-send, CTS, frame or a CTS-to-self frame.
  • Embodiment B4 The AP STA of Embodiment B2, wherein the information corresponds to a trigger frame that is configured to enable peer-to-peer communications among a plurality of non-AP STAs on at least the primary channel, the non-AP STAs including the first STA.
  • Embodiment B5. The AP STA of any one of Embodiments B1-B4, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment Cl A method implemented in a first station, STA, that is configured to wirelessly communicate with an access point STA, AP STA, in a wireless communication system, the method comprising: receiving information related to ongoing communications on a nonprimary channel; and setting a network allocation vector, NAV, for both primary and nonprimary channels based on the information.
  • Embodiment C2 The method of Embodiment Cl, wherein the information corresponds to a control frame that is transmitted on the primary channel.
  • Embodiment C3 The method of Embodiment Cl, wherein the control frame is a clear-to-send, CTS, frame or a CTS-to-self frame.
  • Embodiment C4 The method of Embodiment C2, wherein the information corresponds to a trigger frame that is configured to enable peer-to-peer communications among a plurality of non-AP STAs on at least the primary channel, the non-AP STAs including the first STA.
  • Embodiment C5. The method of any one of Embodiments C1-C4, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment DI A first station, STA, configured to wirelessly communicate with an access point STA, AP STA, in a wireless communication system, the first STA configured to: receive information related to ongoing communications on a nonprimary channel; and set a network allocation vector, NAV, for both primary and nonprimary channels based on the information.
  • NAV network allocation vector
  • Embodiment D2 The first STA of Embodiment DI, wherein the information corresponds to a control frame that is transmitted on the primary channel.
  • Embodiment D3. The first STA of Embodiment DI, wherein the control frame is a clear-to-send, CTS, frame or a CTS-to-self frame.
  • Embodiment D4 The first STA of Embodiment D2, wherein the information corresponds to a trigger frame that is configured to enable peer-to-peer communications among a plurality of non-AP STAs on at least the primary channel, the non-AP STAs including the first STA.
  • Embodiment D5 The first STA of any one of Embodiments D1-D4, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment El A method implemented in a first station, STA, that is configured to wirelessly communicate with an access point STA, AP STA, in a wireless communication system, the method comprising: indicating, to AP STA, an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • Embodiment E2 The method of Embodiment El, further comprising receiving a scheduling of multi-user downlink or uplink communications involving the first STA, the scheduling not allocating frequency resources of the primary channel to the first STA.
  • Embodiment E3 The method of any one of Embodiments E1-E2, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment Fl A first station, STA, configured to wirelessly communicate with an access point STA, AP STA, in a wireless communication system, the first STA is configured to: indicate, to AP STA, an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • Embodiment F2 The first STA of Embodiment Fl, wherein the first STA is further configured to receive a scheduling of multi-user downlink or uplink communications involving the first STA, the scheduling not allocating frequency resources of the primary channel to the first STA.
  • Embodiment F3. The first STA of any one of Embodiments F1-F2, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment Gl A method implemented in an access point station, AP STA that is configured to wirelessly communicate with a first STA, in a wireless communication system, the method comprising: receiving, from the first STA, an indication an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • Embodiment G2 The method of Embodiment Gl, further comprising scheduling multi-user downlink or uplink communications involving the first STA, the scheduling not allocating frequency resources of the primary channel to the first STA.
  • Embodiment G3 The method of any one of Embodiments G1-G2, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.
  • Embodiment Hl An access point station, AP STA, configured to wirelessly communicate with first STA, in a wireless communication system, the AP STA configured to: receive, from the first STA, an indication an inability to communicate using a primary channel of a basic service set, BSS, due to ongoing overlapping BSS, OBSS, transmissions on the primary channel.
  • BSS basic service set
  • Embodiment H2 The AP STA of Embodiment Hl, wherein the AP STA is further configured to schedule multi-user downlink or uplink communications involving the first STA, the scheduling not allocating frequency resources of the primary channel to the first STA.
  • Embodiment H3 The AP STA of any one of Embodiments H1-H2, wherein the primary channel is one of a primary 20 MHz channel, a primary 40MHz channel, a primary 80 MHz channel, or a primary 160 MHz channel.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé mis en œuvre dans une station de point d'accès, STA AP. La STA AP est conçue pour communiquer sans fil avec une première station de point de non-accès, STA non AP, dans un système de communication sans fil employant une procédure « écouter avant de parler », LBT, et la STA AP actionne un premier ensemble de services de base, BSS, impliquant un canal primaire et un canal non primaire. Le procédé consiste à recevoir, en provenance de la première STA non AP sur le canal non primaire, une transmission de liaison montante, sur la base de l'évaluation LBT de la première STA non AP que le canal non primaire est inactif et que le canal primaire est occupé en raison de son utilisation dans un second BSS chevauchant, et à transmettre, sur le canal primaire, une trame de commande destinée à commander l'utilisation du canal primaire par une ou plusieurs STA non AP du premier BSS. L'invention concerne également un procédé pour la STA non AP ainsi que des appareils STA AP et STA non AP.
PCT/EP2023/081327 2023-07-07 2023-11-09 Commande d'utilisation de canal primaire pendant des opérations sur des canaux non primaires Pending WO2025011770A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363512515P 2023-07-07 2023-07-07
US63/512,515 2023-07-07

Publications (1)

Publication Number Publication Date
WO2025011770A1 true WO2025011770A1 (fr) 2025-01-16

Family

ID=88863425

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/081327 Pending WO2025011770A1 (fr) 2023-07-07 2023-11-09 Commande d'utilisation de canal primaire pendant des opérations sur des canaux non primaires

Country Status (1)

Country Link
WO (1) WO2025011770A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3823407A1 (fr) * 2019-11-12 2021-05-19 Intel Corporation Accès à des supports multicanaux pour wlan très haut débit
US20230079334A1 (en) * 2016-11-04 2023-03-16 Panasonic Intellectual Property Corporation Of America Communication apparatus and communication method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230079334A1 (en) * 2016-11-04 2023-03-16 Panasonic Intellectual Property Corporation Of America Communication apparatus and communication method
EP3823407A1 (fr) * 2019-11-12 2021-05-19 Intel Corporation Accès à des supports multicanaux pour wlan très haut débit

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LIWEN CHU (NXP): "Single Radio MLD", vol. 802.11 UHR, 27 February 2023 (2023-02-27), pages 1 - 14, XP068201326, Retrieved from the Internet <URL:https://mentor.ieee.org/802.11/dcn/23/11-23-0016-00-0uhr-single-radio-mld.pptx> [retrieved on 20230227] *

Similar Documents

Publication Publication Date Title
CN111699748B (zh) 用于非授权频带中的新型无线电(nr)操作的技术
US11432300B2 (en) Wi-Fi channel selection and subchannel selective transmissions
EP3941141B1 (fr) Terminal utilisateur et procédé de communication sans fil
KR102784457B1 (ko) 중첩된 베이직 서비스 세트의 공간적 재사용 동작을 위한 무선 통신 방법 및 무선 통신 단말
US9900865B2 (en) Method and apparatus for sub-channel selective access in wireless LAN system
US11153021B2 (en) Soliciting in-basic service set (BSS) interference reports
US10165596B2 (en) Method and apparatus for transmitting frame in wireless local area network
US20150264578A1 (en) Method And Apparatus To Coordinate Simultaneous Transmission In Overlapping Wireless Networks
US12150075B2 (en) Wireless communication method using multilink, and wireless communication terminal using same
US10327262B2 (en) Wireless communication method and wireless communication terminal
WO2020144763A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020166041A1 (fr) Terminal utilisateur et procédé de communication sans fil
CN108028735A (zh) 无线网络中的复用消息传送
WO2011099791A2 (fr) Procédé et appareil d&#39;accès par canal dans un système de réseau local sans fil
WO2020166034A1 (fr) Terminal utilisateur et procédé de communication sans fil
EP3863361B1 (fr) Ap eht configuré pour les opérations multi-ap utilisant une trame d&#39;annonce coordonnée (coa)
WO2022215350A1 (fr) Dispositif de communication, dispositif de station de base, procédé de communication et programme de communication
WO2025011770A1 (fr) Commande d&#39;utilisation de canal primaire pendant des opérations sur des canaux non primaires
US11122621B2 (en) Method for transmitting and receiving data over secondary channel in wireless LAN system and apparatus therefor
EP4521823A1 (fr) Système et procédés d&#39;utilisation de protocoles de commutation de liaison et/ou de détection de trafic de chevauchement
US20250071638A1 (en) System for and methods of using link-switch protocols and/or overlapping traffic detection
WO2020222277A1 (fr) Terminal utilisateur, et procédé de communication sans fil
WO2024052572A1 (fr) Mode de communication par paquets parallèles sur canal unique
WO2025016537A1 (fr) Zones de détection d&#39;écoute avant de parler pour différents schémas de modulation et de codage
WO2024208413A1 (fr) Accès flexible à un canal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23809118

Country of ref document: EP

Kind code of ref document: A1