WO2016011337A1 - Procédés et procédures d'atténuation d'interférences de client wifi collant et de client poste-à-poste (wispim) - Google Patents

Procédés et procédures d'atténuation d'interférences de client wifi collant et de client poste-à-poste (wispim) Download PDF

Info

Publication number
WO2016011337A1
WO2016011337A1 PCT/US2015/040882 US2015040882W WO2016011337A1 WO 2016011337 A1 WO2016011337 A1 WO 2016011337A1 US 2015040882 W US2015040882 W US 2015040882W WO 2016011337 A1 WO2016011337 A1 WO 2016011337A1
Authority
WO
WIPO (PCT)
Prior art keywords
sta
sticky
client
sticky client
undesirable
Prior art date
Application number
PCT/US2015/040882
Other languages
English (en)
Inventor
Oghenekome Oteri
Guodong Zhang
Hanqging LOU
Xiaofei Wang
Pengfei Xia
Robert L. Olesen
Joseph S. Levy
Original Assignee
Interdigital Patent Holdings, Inc.
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 Interdigital Patent Holdings, Inc. filed Critical Interdigital Patent Holdings, Inc.
Publication of WO2016011337A1 publication Critical patent/WO2016011337A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/541—Allocation or scheduling criteria for wireless resources based on quality criteria using the level of interference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • WISPIM PEER-TO-PEER CLIENT INTERFERENCE MITIGATION
  • WiFi networks are increasing. For example, due to the proliferation of WiFi devices a given WiFi network may be more dense, more WiFi networks may be created, and/or there may be more overlapping WiFi networks. Such density may create device relationships that introduce unwanted interference scenarios.
  • a STA and an AP may monitor a metric of a transmission between a station (STA) and an access point (AP).
  • the metric of the transmission may include at least one of a frame check sequence (FCS) error count, a retry count, a retry aggregation Media Access Control (MAC) service data unit (AMSDU) count, a data rate, or a received signal power.
  • FCS frame check sequence
  • MAC Media Access Control
  • AMSDU Media Access Control service data unit
  • the STA or the AP may determine, based on the metric of the transmission, that the STA is a sticky client.
  • the STA or the AP may send a frame that identifies the STA as the sticky client.
  • the frame may include a sticky client notification element.
  • the AP may determine that a station (STA) associated with the AP is a sticky client. The determination may be associated with the STA having an undesirable transmission characteristic or an undesirable reception characteristic.
  • the AP may associate a reassociation delay time with the sticky client. The reassociation delay time may be a time during which the AP will not reassociate with the sticky client.
  • the AP may reassociate with the sticky client and determine that the sticky client has an undesirable transmission characteristic or an undesirable reception characteristic.
  • the AP may assign the sticky client a resource.
  • the resource may be associated with reduced access to a medium.
  • FIG. 1A depicts an exemplary communications system.
  • FIG. IB depicts an exemplary wireless transmit/receive unit (WTRU).
  • WTRU wireless transmit/receive unit
  • FIG. 1C depicts exemplary wireless local area network (WLAN) devices.
  • WLAN wireless local area network
  • FIG. 2 depicts an example of enhanced distributed channel access (EDCA) operation in 802.1 1 ⁇ .
  • EDCA enhanced distributed channel access
  • FIG. 3 depicts an example sticky client scenario.
  • FIG. 4 depicts an example of a frame format of a Sticky Client Notification Element.
  • FIG. 5 depicts an example of secondary request to send (RTS) pre-empting a station (STA) transmission.
  • RTS secondary request to send
  • FIG. 6 depicts an example of secondary clear to send (CTS) pre-empting an STA transmission.
  • CTS secondary clear to send
  • FIG. 7 depicts an example coordinated sticky client restricted access window (RAW) assignment.
  • RAW coordinated sticky client restricted access window
  • FIG. 8 depicts an example sticky client scenario.
  • FIG. 9 depicts an example sticky client scenario that includes a relay.
  • FIG. 10 depicts an example of a downlink relay with explicit acknowledgment
  • FIG. 1 1 depicts an example of an uplink relay with explicit ACK.
  • FIG. 12 depicts an example of basic service set (BSS) spoofing.
  • BSS basic service set
  • FIG. 1 A is a diagram of an example communications system 100 in which one or more disclosed features may be implemented.
  • a wireless network e.g., a wireless network comprising one or more components of the communications system 100
  • bearers that extend beyond the wireless network e.g., beyond a walled garden associated with the wireless network
  • QoS characteristics may be assigned to bearers that extend beyond the wireless network.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • the communications system 100 may include at least one wireless transmit/receive unit (WTRU), such as a plurality of WTRUs, for instance WTRUs 102a, 102b, 102c, and 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • smartphone a laptop
  • netbook a personal computer
  • a wireless sensor consumer electronics, and the like.
  • the communications systems 100 may also include a base station 114a and a base station 1 14b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the Internet 1 10, and/or the networks 112.
  • the base stations 1 14a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 1 14a, 1 14b are each depicted as a single element, it should be appreciated that the base stations 114a, 1 14b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • the base station 114a and/or the base station 1 14b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown).
  • the cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 1 14a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • the base stations 114a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 1 16 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 1 16 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 1 16 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE- Advanced
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • the base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • the base station 1 14b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • WPAN wireless personal area network
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.
  • a cellular- based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.
  • the base station 1 14b may have a direct connection to the Internet 1 10.
  • the base station 114b may not be required to access the Internet 1 10 via the core network 106.
  • the RAN 104 may be in communication with the core network 106, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the core network 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104 and/or the core network 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the core network 106 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 1 10, and/or other networks 1 12.
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links.
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 1 14b, which may employ an IEEE 802 radio technology.
  • FIG. IB depicts an exemplary wireless transmit/receive unit, WTRU 102.
  • WTRU 102 may be used in one or more of the communications systems described herein.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,
  • DSP digital signal processor
  • the processor 1 18 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 1 18 may be coupled to the transceiver 120, which may be coupled to the
  • FIG. IB depicts the processor 1 18 and the transceiver 120 as separate components, it should be appreciated that the processor 1 18 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 1 14a) over the air interface 1 16.
  • a base station e.g., the base station 1 14a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It should be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
  • the processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 1 18 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 1 18 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 1 18 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium ( iCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 1 18 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It should be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 1 18 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player
  • FIG. 1C illustrates exemplary wireless local area network (WLAN) devices.
  • the WLAN may include, but is not limited to, access point (AP) 202, station (STA) 204, and STA 206.
  • STA 204 and 206 may be associated with AP 202.
  • the WLAN may be configured to implement one or more protocols of the IEEE 802.11 communication standard, which may include a channel access scheme, such as DSSS, OFDM, OFDMA, etc.
  • a WLAN may operate in a mode, e.g., an infrastructure mode, an ad-hoc mode, etc.
  • a WLAN operating in an infrastructure mode may comprise one or more APs communicating with one or more associated STAs.
  • An AP and STA(s) associated with the AP may comprise a basic service set (BSS).
  • BSS basic service set
  • AP 202, STA 204, and STA 206 may comprise BSS 210.
  • An extended service set (ESS) may comprise one or more APs (with one or more BSSs) and STA(s) associated with the APs.
  • An AP may have access to, and/or interface to, distribution system (DS), which may be wired and/or wireless and may carry traffic to and/or from the AP.
  • DS distribution system
  • Traffic to a STA in the WLAN originating from outside the WLAN may be received at an AP in the WLAN, which may send the traffic to the STA in the WLAN.
  • Traffic originating from a STA in the WLAN to a destination outside the WLAN, e.g., to server 230 may be sent to an AP in the WLAN, which may send the traffic to the destination, e.g., via DS to network 220 to be sent to server 230.
  • Traffic between STAs within the WLAN may be sent through one or more APs.
  • a source STA e.g., STA 204
  • STA 204 may send the traffic to AP 202
  • AP 202 may send the traffic to STA 206.
  • a WLAN may operate in an ad-hoc mode.
  • the ad-hoc mode WLAN may be referred to as independent basic service set (IBBS).
  • IBBS independent basic service set
  • the STAs may communicate directly with each other (e.g., STA 204 may communicate with STA 206 without such communication being routed through an AP).
  • IEEE 802.1 1 devices may use beacon frames to announce the existence of a WLAN network.
  • An AP such as AP 202, may transmit a beacon on a channel, e.g., a fixed channel, such as a primary channel.
  • a STA may use a channel, such as the primary channel, to establish a connection with an AP.
  • STA(s) and/or AP(s) may use a Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) channel access mechanism.
  • CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
  • a STA and/or an AP may sense the primary channel. For example, if a STA has data to send, the STA may sense the primary channel. If the primary channel is detected to be busy, the STA may back off.
  • a WLAN or portion thereof may be configured so that one STA may transmit at a given time, e.g., in a given BSS.
  • Channel access may include RTS and/or CTS signaling.
  • an exchange of a request to send (RTS) frame may be transmitted by a sending device and a clear to send (CTS) frame that may be sent by a receiving device.
  • RTS request to send
  • CTS clear to send
  • the AP may send an RTS frame to the STA. If the STA is ready to receive data, the STA may respond with a CTS frame.
  • the CTS frame may include a time value that may alert other STAs to hold off from accessing the medium while the AP initiating the RTS may transmit its data.
  • the AP may send the data to the STA.
  • a device may reserve a channel/medium via a network allocation vector (NAV) field.
  • NAV network allocation vector
  • the NAV field may be used to reserve a channel for a time period.
  • a STA that wants to transmit data may set the NAV to the time for which it may expect to use the channel.
  • the NAV may be set for an associated WLAN or subset thereof (e.g., a BSS).
  • Other STAs may count down the NAV to zero.
  • the NAV functionality may indicate to the other STA that the channel is now available.
  • the devices in a WLAN may include one or more of the following: a processor, a memory, a radio receiver and/or transmitter (e.g., which may be combined in a transceiver), one or more antennas (e.g., antennas 106 in FIG. 1), etc.
  • a processor function may comprise one or more processors.
  • the processor may comprise one or more of: a general purpose processor, a special purpose processor (e.g., a baseband processor, a MAC processor, etc.), a digital signal processor (DSP), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the one or more processors may be integrated or not integrated with each other.
  • the processor e.g., the one or more processors or a subset thereof
  • the processor may be integrated with one or more other functions (e.g., other functions such as memory).
  • the processor may perform signal coding, data processing, power control, input/output processing, modulation, demodulation, and/or any other functionality that may enable the device to operate in a wireless environment, such as the WLAN of FIG. 1.
  • the processor may be configured to execute processor executable code (e.g., instructions) including, for example, software and/or firmware instructions.
  • the processer may be configured to execute computer readable instructions included on one or more of the processor (e.g., a chipset that includes memory and a processor) or memory. Execution of the instructions may cause the device to perform one or more of the functions described herein.
  • a device may include one or more antennas.
  • the device may employ multiple input multiple output (MIMO) techniques.
  • MIMO multiple input multiple output
  • the one or more antennas may receive a radio signal.
  • the processor may receive the radio signal, e.g., via the one or more antennas.
  • the one or more antennas may transmit a radio signal (e.g., based on a signal sent from the processor).
  • the device may have a memory that may include one or more devices for storing programming and/or data, such as processor executable code or instructions (e.g., software, firmware, etc.), electronic data, databases, or other digital information.
  • the memory may include one or more memory units. One or more memory units may be integrated with one or more other functions (e.g., other functions included in the device, such as the processor).
  • the memory may include a read-only memory (ROM) (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), etc.), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and/or other non-transitory computer-readable media for storing information.
  • the memory may be coupled to the processer. The processer may communicate with one or more entities of memory, e.g., via a system bus, directly, etc.
  • a WLAN in infrastructure basic service set (IBSS) mode may have an access point (AP) for the basic service set (BSS) and one or more stations (STAs) associated with the AP.
  • the AP may have access or interface to a distribution system (DS) or another type of wired/wireless network that may carry traffic in and out of the BSS.
  • Traffic to STAs may originate from outside the BSS, may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to the respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • Traffic between STAs within a BSS may be peer-to-peer traffic.
  • Such peer-to-peer traffic may be sent directly between the source and destination STAs, e.g., with a direct link setup (DLS) using an IEEE 802.1 le DLS or an IEEE 802.1 lz tunneled DLS (TDLS).
  • DLS direct link setup
  • TDLS IEEE 802.1 lz tunneled DLS
  • a WLAN using an independent BSS (IBSS) mode may have no APs, and the STAs may communicate directly with each other. This mode of communication may be an ad-hoc mode.
  • IBSS independent BSS
  • the AP may transmit a beacon on a fixed channel, e.g., the primary channel.
  • This channel may be 20 MHz wide, and may be the operating channel of the BSS.
  • This channel may also be used by the STAs to establish a connection with the AP.
  • the channel access in an IEEE 802.1 1 system may be Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA).
  • CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
  • each STA may sense the primary channel. If a STA detects that the channel is busy, the STA may back off.
  • One STA may transmit at any given time in a given BSS.
  • dedicated spectrum may be allocated for wireless communication systems such as WLANs.
  • the allocated spectrum (e.g., below lGHz) may be limited in the size and channel bandwidth.
  • the spectrum may be fragmented.
  • the available channels may not be adjacent and may not be combined for larger bandwidth transmissions.
  • WLAN systems for example built on the IEEE 802.1 1 standard, may be designed to operate in such spectrum. Given the limitations of such spectrum, the WLANs systems may be able to support smaller bandwidths and lower data rates compared to HT and/or VHT WLAN systems (e.g., based on the IEEE 802.1 In and/or 802.1 lac standards).
  • Spectrum allocation in one or more countries may be limited. For example, in China the 470-566 and 614-787 MHz bands may allow lMHz bandwidth. In addition to lMHz bandwidth, a 2MHz with lMHz mode may be supported.
  • the 802.1 lah physical layer (PHY) may support 1, 2, 4, 8, and 16 MHz bandwidths.
  • Sub 1 GHz modes of operation may be supported by 802.1 laf, and 802.1 lah.
  • the channel operating bandwidths, and carriers may be reduced relative to those used in 802.11 ⁇ , and 802.1 lac.
  • 802.1 laf may support 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.1 lah may support 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.1 lah may support Meter Type Control (MTC) devices in a macro coverage area.
  • MTC devices may have limited capabilities including support for limited bandwidths, but also include a requirement for long battery life.
  • WLAN systems which support multiple channels, and channel widths may include a channel which is designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be limited by the STA, of all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide if there are STAs (e.g., MTC type devices) that only support a 1 MHz mode even if the AP, and other STAs in the BSS, may support a 2 MHz, 4 MHz, 8 MHz, 16 MHz, or other channel bandwidth operating modes.
  • Carrier sensing, and NAV settings may depend on the status of the primary channel; i.e., if the primary channel is busy, for example, due to a STA supporting only a 1 MHz operating mode is transmitting to the AP, then the entire available frequency bands may be considered busy even though a majority of it stays idle and available.
  • the available frequency bands which may be used by 802.1 lah are from 902 MHz to 928 MHz. In Korea it is from 917.5 MHz to 923.5 MHz; and in Japan, it is from 916.5 MHz to 927.5 MHz.
  • the total bandwidth available for 802.1 lah may be 6 MHz to 26 MHz depending on the country code.
  • Enhanced distributed channel access may be an extension of the basic DCF (Distributed Coordination Function) introduced in the 802.1 1 (e.g., to support prioritized QoS).
  • EDCA may support contention based access of the medium.
  • FIG. 2 depicts an example of EDCA operation in 802.1 In.
  • the Point Coordination Function may use contention free channel access to support time-bounded services with polling by the AP to each STA in the BSS.
  • the AP may send a polling message after waiting for Point Coordination Function Interframe Space (PIFS) and if a client has nothing to transmit, it may return a null data frame.
  • PIFS Point Coordination Function Interframe Space
  • the PCF may be provided for low duty-cycle or heavy/bursty traffic.
  • Hybrid coordination function (HCF) controlled channel access HCCA may enhance PCF in which the AP may poll a STA during both a contention period (CP) and a contention-free period (CFP).
  • the AP may transmit one or more frames under one poll.
  • HCFP contention-free period
  • Association, reassociation, and disassociation may be provided in 802.11.
  • Association may include the process by which a STA joins a BSS.
  • the STA may send an Association Request frame to the target AP.
  • the AP may send the STA an Association
  • the AP and STA may exchange capabilities and attributes.
  • a STA migrating from one AP to another in the same ESS a STA migrating from one AP to another in the same ESS.
  • Reassociation frame may be sent from the STA to the AP.
  • a disassociation frame may be sent to disassociate the STA from the BSS.
  • Disassociation may be initiated by either party to an association (e.g., the AP or the non-AP STA).
  • Disassociation may include a notification, and may not include a request. Disassociation may not be refused by the receiving STA except when management frame protection is negotiated and the message integrity check fails.
  • the IEEE 802.11 High Efficiency WLAN (HEW) Study Group (SG) was created to explore the scope and purpose of a possible, future amendment to enhance the quality of service all users experience for a broad spectrum of wireless users in many usage scenarios including high-density scenarios in the 2.4 GHz and 5 GHz band.
  • New use cases which support dense deployments of APs, and STAs, and associated Radio Resource Management (RRM) technologies are being considered by the HEW SG.
  • Potential applications for 802.1 1 HEW may include emerging usage scenarios such as data delivery for stadium events, high user density scenarios such as train stations, or enterprise/retail environments, and also evidence for an increased dependence on video delivery, and wireless services for medical applications.
  • the IEEE Standard board approved the IEEE 802.1 lax Task Group (TG) based on a Project Authorization Request (PAR) and Criteria for Standards Development (CSD) developed in the HEW SG.
  • Potential problems to be solved may include interference mitigation for sticky client as well as peer-to-peer transmission within infrastructure networks.
  • One or more STAs may remain associated with an AP even when they are fairly far away from the AP (e.g., low SNR or low STNR cell edge area). These STAs may be called sticky clients as they "stick" to an AP (e.g., API) when a different AP, (AP2) may provide better performance either due to the fact that the signal received from AP2 may be stronger than the signal received from API or that AP2 may be more lightly loaded than API .
  • a sticky client may transmit and receive using lower MCS' and may be prone to many retries. This may lead to a reduced aggregated throughput in the network and/or low MAC efficiency as their transmission times may be long due to the use of low MCSs. Sticky clients may be in the
  • FIG. 3 depicts an example sticky client scenario. Solutions to the sticky client problem may also be applied to degraded clients or other reduced performance clients in the network.
  • 802.1 lr defines the Fast BSS Transition mechanism which may provide a means for a STA to set up security and QoS parameters prior to reassociation to a new AP.
  • the fast BSS transition mechanism may allow time-consuming operations to be removed from the time-critical reassociation process (e.g., to facilitate low-latency handover between APs).
  • Fast BSS Transition may take place over the air or over a distribution system (DS) and may be initiated by a non-AP STA, which may be referred to as the Fast BSS Transition Originator (FTO).
  • DS distribution system
  • FTO Fast BSS Transition Originator
  • 802.11 may support BSS transition management via an AP-Directed Handover.
  • the BSS Transition capability may enable improved throughput, effective data rate and/or QoS for the aggregate of STAs in a network.
  • the BSS transition capability may shift (e.g., shift via transition) individual STA traffic loads to more appropriate points of association within the ESS.
  • the BSS transition capability may enable an AP to request non-AP STAs to transition to a specific AP, or to indicate to a non-AP STA a set of preferred APs, due to network load balancing or BSS Termination.
  • the BSS transition capability may be based on the IEEE Wireless network management standard or IEEE802.1 lv and may use information from the IEEE radio resource measurement standard (IEEE802.1 lk).
  • a non-AP STA may send a BSS Transition Management Query to an AP to request a list of BSS Transition Candidates.
  • An AP may transmit a BSS Transition Management Request to one or more associated STAs.
  • the BSS Transition Management Request frame may be unsolicited or may be a response to a BSS Transition Management Query.
  • Additional methods may involve a STA being allowed to associate or disassociate with the "best” APs only.
  • the criteria and thresholds for what is "best” may be predetermined.
  • an enterprise network there may be peer-to-peer transmission such as with wireless docking using WiFi Direct/Display.
  • peer-to-peer transmission such as with wireless docking using WiFi Direct/Display.
  • home networks direct connections between media players and televisions (such as the Roku device) may exist. These mini-ad hoc networks may exist within the overall infrastructure network.
  • the mini-ad hoc networks may include technologies such as WiFi Direct or 802.1 lz also known as Tunneled Direct Link Setup (TDLS).
  • WiFi direct one of the nodes may set up a "soft Access Point" to which a legacy STA may connect with seamlessly. This may result in additional interference to the infrastructure network as the network created by the original or root AP and the soft-AP interact with each other.
  • TDLS two STAs that have information to send to each other may create a link between each other while staying associated with the AP. TDLS may help optimize traffic flow within the network.
  • a solution to the sticky client problem may include handover between the two APs. Handover may not be possible and sticky clients may occur. For example one or more of the following may occur. Sticky clients may be created when roaming/handover decisions are left to the STA as opposed to the AP and/or association/disassociation and/or other handover algorithms are poorly implemented in the STA. Sticky clients may be created when
  • roaming/handover decisions are left to the STA as opposed to the AP and the STA has no information on a better (e.g., the "best") AP to move to.
  • Sticky clients may be created when AP2 may not allow association of STA (e.g., AP2 is fully loaded and unable to accept more STAs).
  • Sticky clients may negatively impact the overall performance of the network without the network being aware that the network performance degradation is caused by such a client.
  • Methods are needed to improve the identification of sticky clients, their "best” APs, and to facilitate the signaling of this information and associated parameters to enable handover to a new "best” AP.
  • the mitigation of the interference experienced by the AP may need to be identified, and the presence of sticky clients may need to be signaled.
  • Handover methods may be implemented as discussed herein or based on improvements to existing handover schemes that are proposed in WiFi Enabled Network Transfer (WENT).
  • WiFi Direct P2P STAs may lack coordination between the soft-AP and the root AP (e.g., the AP that owns the BSS), which may result in poor performance for the entire network.
  • Systems, methods, and instrumentalities may be provided that may improve the performance of the entire system. There may be multiple subnetworks in the infrastructure network.
  • the P2P transmission may impact more than one infrastructure BSS.
  • Systems, methods, and instrumentalities may be provided that may improve the performance of the entire system with additional coordination between multiple (e.g., possible overlapping) BSSs and the P2P transmission.
  • Identification and labeling of a sticky client may be based on a metric. If a STA meets one or more of the following criteria, it may be identified as a sticky client. A STA may be identified as a sticky client if the STA has undesirable transmission and/or reception performance (e.g., one or more of FCS Error Count, Retry Count, or Retry AMSDU Count exceeds a predefined threshold). A STA may be identified as a sticky client if the STA's data rate is close to or below the minimum supported data rate of the currently associated AP.
  • a STA may be identified as a sticky client if the STA's received signal power from its associated AP is X dB lower than its received signal power from another available AP (e.g., its best available AP), where X is a predefined threshold.
  • the received signal power may use RCPI or RSNI measurements.
  • the best available AP may be defined as an AP whose admission policy and load/delay conditions, are considered to be acceptable.
  • the admission policy e.g., including BSS capabilities, supported operating classes, roaming consortium, NAI Realm, etc.
  • AP load/delay conditions may be obtained from the BSS load, BSS AC Access Delay, and/or BSS Ave Access delay measurements and/or statistics.
  • the STA, and/or its associated AP may identify a STA as a sticky client and may send a sticky client notification to STAs or APs of interest.
  • Sticky client notification may include sending a management frame, control frame, or action frame with a Sticky Client Notification Element.
  • FIG. 4 depicts an example of a Sticky Client Notification Element.
  • a Sticky Client Notification Element may signal the sticky client notification to another STA/AP.
  • the Element ID field may indicate whether the current IE is a Sticky Client Notification element.
  • the Length field may comprise the length of the Sticky Client Notification element.
  • the field of sticky client ID may include the MAC address of the STA that is identified as a sticky client.
  • the sticky client ID may include AID or other identification of the sticky client.
  • the reason code field may indicate the reason(s) that the STA is identified as a sticky client.
  • the reason code may indicate undesirable transmission and reception performance, a data rate close to or below the minimum supported data rate of the currently associated AP, received signal power from its associated AP is X dB lower than its received signal power from its best available AP, etc.
  • Each code point of the Reason Code field may indicate one or a combination of several reasons that the STA is identified as a sticky client.
  • the Reason Code field may include a bitmap to indicate one or several reasons that the STA is identified as a sticky client.
  • the associated AP BSSID may be present when the Sticky Client Notification element is sent by a non-AP STA.
  • the associated AP BSSID may be omitted when the Sticky Client Notification element is sent by the AP associated with the sticky client.
  • the STA and/or its associated AP may follow one or more actions for sticky client identification and/or indication. For example, one or more of the following may apply.
  • the STA and its associated AP may monitor the one or more metrics for sticky client identification (such as, whether its FCS Error Count, Retry Count, and/or Retry AMSDU Count exceeds a predefined threshold; data rate is close to or below the minimum supported data rate of the currently associated AP; received signal power from its associated AP is X dB lower than its received signal power from its best available AP).
  • the observing entity e.g., the STA itself or the associated AP
  • the entity that identifies the sticky client may notify STAs or APs of interest by sending a management frame, control frame, or action frame with a Sticky Client Notification Element (e.g. , the Sticky Client Notification Element depicted in FIG. 4).
  • probe response and association may be implemented, e.g., for disadvantaged STAs.
  • An AP may identify a STA as a disadvantaged, or a sticky STA using one or more of the following.
  • the AP may identify a STA as a disadvantaged, or a sticky STA when for a STA that it is associated with (e.g., currently associated or previously associated), the packet(s) that are received from the STA, are received below a pre-defined power level, such as a pre-defined threshold RSSI, RCPI level(s).
  • a pre-defined power level such as a pre-defined threshold RSSI, RCPI level(s).
  • the AP may identify a STA as a disadvantaged, or a sticky STA when for a STA that it is associated with (e.g., currently associated or previously associated), the transmission(s) between the AP and the STA, have been using a low MCS such as a MCS that is below some pre-defined threshold MCS level (e.g., MCSthres).
  • MCSthres some pre-defined threshold MCS level
  • the AP may identify a STA as a disadvantaged, or a sticky STA when for a STA that it is associated with (e.g., currently associated or previously associated), the transmission(s) between the AP and the STA, have been suffering a high retry rate, such as a retry rate that is higher than some pre-defined threshold Rretry thres.
  • a retry rate may be defined as,
  • Number_of_Retries(Pi) is the number of retransmissions for the packet Pi, which may include the initial transmission of the packet Pi and N is the number of total relevant packets, for example, all packets that has been transmitted between the STA and the AP for some period of time, or the packets that the AP has transmitted to the STA for some period of time.
  • the AP may identify a STA as a disadvantaged, or a sticky STA when a STA that was previously identified as a sticky client, and has been disassociated by the AP within some pre-defined interval, e.g., [P sticky client, Now], or (Psticky client, Now), with P sticky client being the Sticky Client Period, and Now being the indication for time for the present time.
  • P sticky client being the Sticky Client Period
  • the AP may identify a STA as a disadvantaged, or a sticky STA when a STA that was previously identified as a sticky client, and has been disassociated by the AP, and the Probe Request or Association Request that are transmitted by the STA is below pre-defined power level, such as a pre-defined threshold RSSI, RCPI level(s).
  • An AP and/or STA may take one or more of the following actions (e.g., as a result of the STA being identified as a sticky client.
  • the AP may record the ID of the STA, such as the AID or MAC address of the STA, and may mark the STA
  • the SME in the AP may issue an MLME-DISASSOCIATE.request primitive that may include an appropriate Reason Code (such as Sticky Client).
  • the AP may generate a Disassociation frame to the STA, which may include an appropriate Reason Code (such as Sticky Client).
  • the AP may include an reassociation delay time to the STA that indicates that the STA not try to reassociate with the AP until after the reassociation delay time.
  • the STA may acknowledge the Disassociation frame.
  • the MLME in the AP may issue a message, such as an MLME- DISASSOCIATE.confirm primitive that may inform the SME of the disassociation.
  • the SME in the AP may maintain any PTKSA and temporal keys held for communication with the STA for some period of time, i.e., Psticky client Temp Keys.
  • Psticky client Temp eys may be pre-defined, or may be conveyed, by the AP to the STA in the Disassociation frame.
  • the SME in the STA may maintain any PTKSA and temporal keys held for communication with the STA for some period of time, i.e., Psticky client Temp Keys.
  • Psticky client Temp Keys At the expiration of the Psticky Client T emp ey s , and if the STA has not reassociated with the AP, the SME in the AP and/or in the STA may delete PTKSA and temporal keys held for communications with the STA, e.g., by using the MLME-DELETEKEYS. request primitive and by invoking MLMESETPROTECTION.request(None) and potentially with identification of the ID of the STA that has been identified as a sticky client.
  • the SME in the STA may delete PTKSA and temporal keys held for communications with the STA, e.g., by using the MLME-DELETEKEYS. request primitive and by invoking MLMESETPROTECTION.request( one), and potentially with identification of the ID of the STA that has been identified as a sticky client.
  • the AP (e.g., at the time of disassociation) may record the ID of the STA, such as the AID or MAC address of the STA, and may mark the STA as a Previous Sticky Client and may record the time of disassociation.
  • the AP may not respond with a Probe Response.
  • the AP may respond with a Probe Response after a pre-defined period, such as a reassociation delay time, e.g., PDesparate sticky client, to allow the STA opportunity to discover another AP (e.g., a better and more appropriate AP).
  • the AP may respond with a Probe Response after a period of time that may be determined based on the parameters of the received Probe Request. For example, the lower the power level of the Probe Request, the longer the wait before the AP may respond with a Probe Response.
  • a Probe Request has been received from a STA, and the power level or other parameters of the Probe Request indicates that the STA may be a sticky client, the AP may not respond with a Probe Response.
  • the AP may respond with a Probe Response after some predefined period, such as a reassociation delay time, e.g., PDesparate sticky client, to allow the STA opportunity to discover another AP (e.g., a better and/or more appropriate AP).
  • the AP may respond with a Probe Response after a period of time that may be determined based on the parameters of the received Probe Request. For example, the lower the power level of the Probe Request, the longer the wait may (e.g., will) be before the AP may respond with a Probe Response.
  • a reassociation delay time e.g., Psticky client
  • an Association Request has been received from a STA that is a Previous Sticky Client, and the power level or other parameters of the Association Request indicates that the STA is still a sticky client
  • the AP may not respond with an Association Response.
  • the AP may respond with an Association Response after some pre-defined period, such as
  • the AP may respond with an Association Response after a period of time that may be determined based on the parameters of the received Association Request. For example, the lower the power level of the Association Request, the longer the wait before the AP may respond with an Association Response.
  • an Association Request has been received from a STA, and the power level or other parameters of the Association Request indicates that the STA may be a sticky client, the AP may not respond with an Association Response.
  • the AP may respond with an Association Response after some pre-defined period, such as PDesparate sticky client, to allow the STA
  • the AP may respond with an Association Response after a period of time that may be determined based on the parameters of the received Association Request. For example, the lower the power level of the Association Request, the longer the wait may (e.g., will) be before the AP may respond with an Association Response.
  • the ST A and the AP may use the security set up that has been saved (e.g., PTKSA and/or temporal keys held for
  • Secondary status identification/channel access may be provided.
  • the sticky client e.g., rather than (a) being forced into handover especially in scenarios where the nearest AP is managed by another entity or (b) being forced to disassociate from the network, may have its performance/medium access reduced subject to the traffic requirements in the AP it may be interfering with.
  • the client may be assigned lower priority relative to other transmissions from BSS 2. Transmission from BSS 2 (which may be impacted the most by the sticky client) may pre-empt the transmission of the sticky client. This technique may be used for a STA that may impact the overall performance of the BSS (e.g., a degraded STA).
  • Sticky-Client specific EDCA parameters may be provided.
  • a priority reduction of the sticky and degraded client may be implemented by the use of a set of Enhanced Distribution Channel Access (EDCA) parameters that may be set for the sticky and degraded client(s) (e.g., modified EDCA parameters) in the access categories (AC) that may include background traffic, best effort traffic, voice traffic or video traffic.
  • EDCA Enhanced Distribution Channel Access
  • FIG. 2 depicts an example of EDCA operation in 802.1 In.
  • the EDCA parameters may include one or more of the following: Arbitration Interframe Spacing: AIFS_sticky[AC]; Backoff: BACKOFF_sticky [AC] ; Contention Window Size: CW_size_sticky[AC]; or +Transmit Opportunity Duration: TxOP_sticky[AC].
  • One or more of the following may be used for sticky/degraded clients.
  • a STA may be identified as sticky and/or degraded clients as described herein.
  • a priority reduction signal may be sent to the STA(s).
  • the priority reduction signal may be indicated by the AP using the Sticky Client Notification element, or may be sent by a new priority notification frame.
  • a change in the contention window size may ensure that the sticky and/or degraded node statistically has lower priority in accessing the channel medium.
  • the CW size may be changed to a contention window size based on the CW sizes of the nodes in the network.
  • Transmit Opportunity Duration - TxOP_sticky[AC] may limit the transmission time allowed for a sticky and/or degraded client in the medium (e.g., modified the allowed transmission time as compared to a client that is not identified as sticky).
  • the transmit opportunity duration may prevent the STA from taking up the transmission time and impacting both BSSs, i.e. the OBSS, negatively (e.g., since it most likely will have a low MCS).
  • the sticky and/or degraded client may be allowed a maximum TxOP within which to transmit.
  • the sticky and/or degraded client may set up a normal TxOP but with a time duration (e.g., a maximum time duration) after which it may use a larger than normal xIFS. Waiting STAs belonging to BSS2 may have an opportunity to reserve the channel medium. In the event that another STA transmits, the TxOP duration may be truncated.
  • the changed EDCA parameters may be broadcast by the AP as a separate frame (e.g., a new frame) or as a part of the beacon frame.
  • the STA may receive the changed EDCA parameters, e.g., automatically. BSS-wide sticky and/or degraded STA EDCA parameters may be enabled.
  • the changed EDCA parameters may be sent as a separate frame (e.g., in the case the Sticky Client Notification element is sent by a non-AP STA) and/or may be added to the client notification element (e.g., when the Sticky Client Notification element is sent by the AP associated with the sticky and/or degraded client).
  • STA-specific sticky client EDCA parameters may be enabled.
  • P2P specific EDCA transmission parameters may be used.
  • the priority reduction of the sticky and/or degraded client may be implemented by the use of a secondary RTS/CTS frame exchange.
  • the secondary RTS may be overridden by a normal RTS from a node in BSS 2.
  • FIG. 5 depicts an example of secondary RTS pre-empting a STA transmission.
  • a secondary RTS frame exchange may include one or more of the following.
  • the sticky and/or degraded client may be able to reserve the medium.
  • the sticky and/or degraded client may be assumed to have a total AIFS + back-off time of BK1 for traffic to be sent to API .
  • the STA may detect no activity on the channel and may send out a secondary RTS on the channel to the AP.
  • API may send a CTS to the STA that may indicate that the channel is clear and data may be transmitted from STA1 to AP I for the duration of the transmit opportunity.
  • Other APs and STAs in the network may set their NAV for the duration of the transmission.
  • the priority reduction of the sticky and/or degraded client may be implemented by the use of a secondary RTS/CTS frame exchange.
  • the secondary RTS may be overridden by a normal RTS from a node in BSS 2.
  • a secondary RTS frame exchange may include one or more of the following.
  • the sticky and/or degraded client may be unable to reserve the medium.
  • For uplink transmission the sticky and/or degraded client may be assumed to have a total AIFS + back-off time of BKl for traffic to be sent to API.
  • the STA may detect no activity on the channel and may send out a secondary RTS on the channel to the AP.
  • a node from BSS2 may preempt the sticky and/or degraded client transmission and may reserve the channel for its own transmission.
  • FIG. 6 depicts an example of a secondary CTS pre-empting a STA transmission.
  • a secondary CTS frame exchange may include one or more of the following when the AP I may be able to reserve the medium for transmission to the sticky and/or degraded client.
  • API may be assumed to have a total AIFS + back-off time of BKl for traffic to be sent to the sticky and/or degraded client.
  • API may detect no activity on the channel and may send an RTS on the channel to the sticky and/or degraded client.
  • the sticky and/or degraded client may send a secondary CTS to AP I that may indicate the channel is conditionally clear and data may be transmitted from AP 1 to STA 1 (e.g., once an all clear is given for the duration of the transmit opportunity).
  • the STA may send a confirmation CTS to the AP and the AP may start transmission.
  • Other (e.g., all other) APs and STAs in the network may set their NAV for the duration of the transmission.
  • a secondary CTS frame exchange procedure may include one or more of the following when the API may be unable to reserve the medium for transmission to the sticky and/or degraded client.
  • the API For downlink transmission, the API may be assumed to have a total AIFS + back-off time of BKl for traffic to be sent to the sticky and/or degraded client.
  • AP I At time BKl, AP I may detect no activity on the channel and may send out an RTS on the channel to the AP.
  • RTS time
  • the sticky and/or degraded client may send a secondary CTS to AP 1 that may indicate the channel is conditionally clear and data may be transmitted from API to STA1 (e.g., once an all clear is given for the duration of the transmit opportunity).
  • a node from BSS2 may preempt the sticky and/or degraded client transmission and ma reserve the channel for its own transmission.
  • Other (e.g., all other) APs and STAs in the network may set their NAV for the duration of the transmission.
  • the P2P transmission may be set up to use the secondary RTS-CTS mechanism.
  • the secondary RTS and secondary CTS frames may be combined (e.g., to improve the reservation of the medium for the sticky and/or degraded client.
  • a sticky client may be isolated based on frequency, time, and/or code. Sticky client(s) may have impact on more than one BSS.
  • a "soft AP" and its clients or two STAs using Direct Link Setup may impact the root AP(s) of the infrastructure BSS.
  • a mechanism to isolate these clients in a particular frequency/time resource so that the impacted BSSs may limit the impact of sticky clients or the P2P transmission may be provided.
  • the APs/BSSs may coordinate (e.g., coordinate semi-statically or dynamically) to ensure orthogonality in isolation dimension. One or more of the following may apply.
  • the AP may announce a sticky client, a group of sticky clients, or a soft AP and its associated clients.
  • the AP may transmit a sticky client management frame to the sticky client(s), and limit the uplink transmission from that client.
  • the allowable uplink transmission from that client may be on an isolated time slot, frequency sub-channel(s), or the combination of both.
  • the uplink transmission from that client may be scheduled by the AP(s), or may occur on the assigned time-frequency resource blocks.
  • the AP may transmit sticky client information to a group of sticky clients.
  • the AP may reuse the group ID mechanism to assign a special group ID for the sticky clients.
  • the special group ID may in addition be used by the AP for addressing special behavior for its use with MU-MIMO reservations of STAs.
  • the AP may transmit a P2P management frame to the soft-AP/client or P2P clients, and may limit the transmission within that P2P transmission.
  • the allowable transmission between the P2P clients may be on an isolated time slot, frequency sub-channel(s), or the combination of both.
  • the transmission between the clients may be scheduled by the AP(s), or may occur on the assigned time-frequency resource blocks.
  • the AP may transmit P2P transmission information to a group of P2P clients.
  • the AP(s) may reuse the group ID mechanism to assign a special group ID for the P2P clients.
  • the special group ID may be used by the AP for addressing special behavior for its use with MU-MIMO reservations of STAs.
  • Clients may be isolated in the frequency domain. One or more of the following may apply.
  • the AP which may be impacted by the sticky client(s) may transmit an information element within its Beacon frame or a control frame which may indicate that one or more subchannels may be utilized for sticky clients.
  • the resource used may be negotiated with the impacted AP to ensure that the interference in both BSSs are limited.
  • the utilization of subchannels) for sticky clients may be within a certain time period or scheduled periodically.
  • the packet duration may be limited, and may be announced by the AP.
  • the STA(s) which may be assigned within the sticky client sub-channel or identified as sticky client may follow the instruction, and may truncate the packet to fit a limited duration if necessary.
  • the AP may update the information element, or may transmit the control frame again to terminate the sticky client sub-channel allocation early.
  • the AP which may be impacted by P2P transmission may transmit an information element within its Beacon frame or a control frame which indicates that one or more subchannels may be utilized for P2P clients.
  • multiple APs may negotiate the allocation of these resources.
  • the signaling may occur in the BSS of the soft AP or an elected STA.
  • the STA/soft AP may communicate the resource allocated to its peer (e.g., the STAs) associated with the soft AP in the case of WiFi direct or the peer STA in the case of Direct Link Setup transmission.
  • the utilization of subchannels) for P2P clients may be within a certain time period, or scheduled periodically.
  • the packet duration may be limited, and may be announced by the AP.
  • the STAs which may be assigned within the P2P sub-channel or identified as P2P clients may follow the instruction, and may truncate the packet to fit the limited duration if necessary.
  • the AP may update the information element, or may transmit the control frame again to terminate the P2P client(s) subchannel allocation early.
  • Clients may be isolated in the time domain. One or more of the following may apply.
  • the AP which may be impacted by sticky client(s) or P2P transmission may transmit an information element within its Beacon frame or a control frame which may indicate that one or more dedicated time slots may be utilized for sticky clients or P2P transmission clients.
  • the dedicated time slot may be a restricted access window (RAW) for sticky clients or P2P transmission clients or a transmit opportunity (TxOP).
  • RAW restricted access window
  • TxOP transmit opportunity
  • the selection of the dedicated time slot may be across multiple BSSs (e.g., to improve both the intra-BSS and inter-BSS interference).
  • the utilization of this period for the sticky clients may be within a certain Beacon interval(s), or may be scheduled periodically.
  • the packet duration may be limited and may be announced by the AP.
  • the STAs which may be assigned within the sticky client/P2P transmission client transmission period or may be identified as sticky clients or P2P transmission clients may follow the instruction, and may truncate the packet to fit the limited duration.
  • the AP may update the information element, or may transmit the control frame again to terminate the sticky client/P2P transmission client transmission period early.
  • FIG. 7 depicts an example coordinated sticky client restricted access window (RAW) assignment.
  • RAW coordinated sticky client restricted access window
  • FIG. 8 depicts an elected relay STA that may be used to send data to a desired AP. Rather than transmitting directly to the associated AP, as depicted in FIG. 8, the sticky client may be redirected to transmit data to/from a relay STA located near the BSS edge which in turn may relay the received information to the AP and vice-versa.
  • FIG. 9 depicts an example sticky client scenario that includes a relay.
  • the relay concept may be used to mitigate the interference of the sticky client to the interfered with AP while improving its performance.
  • a simple bidirectional two-hop relay function may use one relay node.
  • a relay node may be a device that may consist of two logical entities: a relay STA and a relay AP.
  • the relay STA may associate with a parent node or an AP.
  • the relay AP may allow STAs to associate and obtain connectivity to the parent node/AP via the relay STA.
  • a relay node may allow range extension and may support packet/frame forwarding between source and destination nodes.
  • FIG. 10 depicts an example of a downlink relay with explicit ACK.
  • FIG. 1 1 depicts an example of an uplink relay with explicit ACK.
  • Relays may be implemented in sticky clients scenarios.
  • API may elect multiple sticky relay STAs at different points in the network to relay data from clients in different BSSs.
  • Implementing relays may reduce the effect of the sticky client on the network performance (e.g., by improving the interference the sticky client offers to the interferee BSS and/or reducing the transmission time-in-medium due to the improvement in the average channel between the relay and the sticky STA).
  • the relay-STA/AP may transmit/receive to/from sticky clients in a multi-user fashion (e.g., in frequency such as OFDMA/COBRA) or space (e.g., uplink/downlink multi-user MIMO).
  • a multi-user fashion e.g., in frequency such as OFDMA/COBRA
  • space e.g., uplink/downlink multi-user MIMO
  • AP directed relay selection for sticky clients e.g., sticky -client directed relay selection for clients
  • multiple-AP directed relay selection for sticky clients with coordination between both APs e.g., multiple-AP directed relay selection for sticky clients with coordination between both APs.
  • AP directed relay selection for sticky clients may include the AP deliberately selecting a set of STAs to serve as relay nodes to sticky clients.
  • the AP may select a set of STAs to function as possible relay nodes.
  • the STAs selected as relay nodes may be STAs located at or near the BSS edge.
  • the AP may randomly select relays from the STAs in its BSS.
  • the AP may decide to revoke the relay activation if no sticky clients connect to this relay STA after a fixed period.
  • the root AP may send a relay activation frame to the STA(s) in question to set them up as possible relays.
  • Sticky clients may connect to the relay node based on a metric (e.g., a desired metric).
  • Sticky-client directed relay selection for sticky clients may include the sticky client selecting from other STAs in its BSS that it may overhear.
  • the sticky client may ensure that the selected STA is itself not a sticky client (e.g., there has not been any sticky client notification frame sent to or from that STA).
  • the sticky client may send a relay-activation request frame to both the AP and the STA to set up the relay link.
  • the sticky client may send the request to the STA.
  • the STA may forward the request to the AP and the AP may acknowledge the request to set up the link.
  • the sticky client may send the request to the STA.
  • the sticky client may send a request (e.g., an additional request) to the AP and the AP may send a relay activation request to the STA with instructions to forward any information to the sticky client.
  • Multiple-AP directed relay selection for sticky clients with coordination between both APs may include the relay node being selected based on coordination between the AP the sticky client is associated (API) with and the AP the sticky client is closest to (AP2).
  • a STA or group of STAs may be identified as sticky clients, e.g., as discussed herein.
  • a relay redirect signal may then be sent to the STAs.
  • a relay redirect signal may be sent out to the STA to inform the STAs that they may (e.g., should) initiate relay discovery (e.g., they need to look for the "best" relay STA to associate with and transmit/receive from that relay STA).
  • the relay-redirect signal may be sent out once a group of sticky clients may be identified with the redirect signal sent out at regular intervals (e.g., once every beacon or at a time judged suitable by the AP).
  • the relay- redirect signal may inform a STA/group of STAs that they may connect (e.g., connect directly) to the AP if they move (e.g., into a more favorable position).
  • the relay STA e.g., the "best" relay STA
  • the data rate may be weighted more than the delay.
  • FIG. 12 depicts an example of BSS spoofing.
  • AP2 the impacted AP, may spoof AP I or may behave as if it is a member of API 's ESS (e.g., the STA may communicate directly to AP2 instead of AP I) which may eliminate the sticky client condition.
  • API 's ESS e.g., the STA may communicate directly to AP2 instead of AP I
  • One or more of the following may apply.
  • API and AP2 may work together to identify the presence of the sticky client, STAl .
  • AP I and AP2 may or may not be in the same ESS.
  • API may send AP2 the client information of STAl and may check if AP2 has a good reception quality of the client. If confirmed by AP2, AP I may determine STAl is a sticky STA and determine that it may be better served by AP2.
  • AP I and AP2 may agree that traffic (e.g., all traffic) to and from STAl may (e.g., should) be handled by AP2 and AP2 may spoof API 's MAC address and may receive API 's MAC address for traffic (e.g., all traffic) being sent by STAl.
  • STAl may be unaware that it is now being served by AP2 physically.
  • the STA may not be aware that it has switched APs.
  • the "network" e.g., the two APs
  • the "network” may be aware that the STA has switched APs and may coordinate to eliminate the sticky client situation.
  • AP2 may detect existence of the client STAl, which may have a good reception quality but may not be associated with AP2.
  • AP2 may be aware that STAl is associated with AP I and may be aware that STAl is behaving as a sticky client.
  • AP2 may be aware that STAl is impacting AP2 and the STAs associated with AP2 due to it being a sticky client.
  • AP2 may send a signaling to API, that may inform API that it has a good reception quality for STAl and that it suspects that STAl is a sticky STA. If API agrees that STAl is a sticky STA, API may allow, suggest that, or request that AP2 take over
  • AP2 may receive transmissions from STAl addressed to API and may send transmissions to STAl with API 's MAC address.
  • STAl may be unaware that it is now being served by AP2.
  • the STA may not be aware that it has switched APs.
  • the "network" e.g., the two APs
  • the "network" may be aware that the STA has switched APs and may coordinate to eliminate the sticky client situation.
  • AP2 may set up a virtual AP which may look to be in AP I 's ESS and may allow STAl to switch to AP2 while maintaining a connection to the original ESS.
  • the ESS may be extended so that the effect of sticky STAs on adjacent or overlapping ESSs may be mitigated.
  • One or more of the following may apply.
  • API may identify that STAl is behaving as a sticky client and AP I may request AP2 set up a virtual AP so that STAl may use AP2 and may remain in the ESS of API .
  • API may identify that STAl may support (e.g., only support) low MCS data rates, and AP I may request measurements from STAl which indicate that AP2 may be "closer" (e.g., has better radio propagation characteristics) than API .
  • AP I may contact AP2 and may request that AP2 set up a virtual AP which has the characteristics of API 's ESS.
  • AP2 may assess if it considers STAl a sticky STA.
  • AP2 may assess if it is willing to provide a virtual AP to support STAl as requested by API .
  • AP2 may contact API to either decline or accept API 's invitation. If AP2 accepts AP I 's invitation, AP I may send AP2 information (e.g., all the information) it needs to configure a virtual AP and may send security or other identification information necessary to allow AP2 to act as part of AP I 's ESS. AP2 and API may set up a tunneled connection or other mutually agreed interconnection to allow STAl to receive and transmit packets through AP2 into the AP I ESS. AP2 may begin sending beacons which may be consistent with the information provided by API and may be consistent with AP I 's ESS.
  • AP2 information e.g., all the information
  • AP2 and API may set up a tunneled connection or other mutually agreed interconnection to allow STAl to receive and transmit packets through AP2 into the AP I ESS.
  • AP2 may begin sending beacons which may be consistent with the information provided by API and may be consistent with AP I '
  • Sending the beacons may establish a virtual AP in AP2 which is part of API 's ESS.
  • STAl may associate with AP2 via its virtual AP.
  • STAl may send and receive packets as if it is still connected to API 's ESS.
  • AP2 may stop broadcasting beacons associated with the virtual AP and it may tear down the tunnel or other connection established with AP 1.
  • AP2 may notify AP 1 that it no longer supports a virtual AP in AP I 's ESS. If AP2 no longer supports the virtual AP, AP2 may stop broadcasting beacons associated with the virtual AP and it may tear down the tunnel or other connection established with AP 1.
  • AP2 may notify AP 1 that it no longer supports a virtual AP in AP I 's ESS.
  • API may send a request to AP2 to stop supporting its virtual AP.
  • AP2 may send a confirmation to API that it has stopped (e.g., or will stop) its virtual AP.
  • AP2 may stop broadcasting beacons associated with the virtual AP and AP2 may tear down the tunnel or other connection established with AP 1.
  • AP I may tear down the tunnel or other connection established with AP2. If AP2 does not accept AP I 's invitation, no virtual AP will be established and STAl may not be able to connect to AP2 to stay in API 's ESS.
  • AP2 may identify that STAl is behaving as a sticky client and AP2 may request API allow AP2 set up a virtual AP so that STAl can use AP2 and remain in the ESS of API (e.g., ending the sticky client behavior).
  • AP2 may identify that STAl may support (e.g., only support) low MCS data rates and may determine that STAl may support higher MCS's if it was associated with AP2.
  • AP2 may have better radio propagation characteristics than AP I (e.g., if STA is "closer to AP2 than API).
  • AP2 may contact API and may request that AP2 be allowed to set up a virtual AP with the characteristics of AP I 's ESS.
  • API may assess if it considers STAl a sticky STA. AP I may assess whether to provide AP2 with the information it would need to establish a virtual AP to support STAl. [0143] API may contact AP2 to either decline or accept AP2's request. If API accepts AP2's request, AP I may send AP2 information (e.g., all the information) it needs to configure a virtual AP and AP I may send security or other identification information required to allow AP2 to act as part of API 's ESS. AP2 and AP I may set up a tunneled connection or other mutually agreed interconnection that may allow STA 1 to receive and transmit packets through AP2 into the API ESS.
  • AP2 information e.g., all the information
  • AP2 may send beacons which are consistent with the information provided by API and consistent with API 's ESS. Sending the beacons may establish a virtual AP in AP2 which is part of API 's ESS.
  • STA1 may associate with AP2 via its virtual AP.
  • STA1 may send and receive packets as if it is still connected to API 's ESS.
  • AP2 may stop broadcasting beacons associated with the virtual AP and it may tear down the tunnel or other connection established with AP 1.
  • AP2 may notify AP 1 that it no longer supports a virtual AP in API 's ESS.
  • AP2 may stop broadcasting beacons associated with the virtual AP and it may tear down the tunnel or other connection established with AP 1.
  • AP2 may notify AP 1 that it no longer supports a virtual AP in API 's ESS.
  • API no longer requires that AP2 support the virtual AP AP I may send a request to AP2 to stop supporting its virtual AP.
  • AP2 may send a confirmation to API that it has stopped (e.g., or will stop) its virtual AP.
  • AP2 may stop broadcasting beacons associated with the virtual AP and it may tear down the tunnel or other connection established with AP 1.
  • AP 1 may tear down the tunnel or other connection established with AP2. If API does not accept AP2's request, a virtual AP may not be established and STA1 may not be able to connect to AP2 to stay in API 's ESS.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, WTRU, terminal, base station, RNC, or any host computer.

Landscapes

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

Abstract

La présente invention concerne des systèmes, des procédés et des instruments permettant de mettre en œuvre un procédé d'atténuation d'interférences destiné à un point d'accès (AP). L'AP peut déterminer qu'une station (STA) associée à l'AP est un client collant. La détermination peut être associée au fait que la STA présente une caractéristique de transmission non souhaitable ou une caractéristique de réception non souhaitable. L'AP peut associer un retard de réassociation avec le client collant. Le retard de réassociation peut être un temps pendant lequel l'AP ne va pas se réassocier avec le client collant. L'AP peut se réassocier avec le client collant et déterminer que le client collant présente une caractéristique de transmission non souhaitable ou une caractéristique de réception non souhaitable. L'AP peut attribuer une ressource au client collant. La ressource peut être associée à un accès réduit à un support.
PCT/US2015/040882 2014-07-17 2015-07-17 Procédés et procédures d'atténuation d'interférences de client wifi collant et de client poste-à-poste (wispim) WO2016011337A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201462025965P 2014-07-17 2014-07-17
US62/025,965 2014-07-17

Publications (1)

Publication Number Publication Date
WO2016011337A1 true WO2016011337A1 (fr) 2016-01-21

Family

ID=53794485

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/040882 WO2016011337A1 (fr) 2014-07-17 2015-07-17 Procédés et procédures d'atténuation d'interférences de client wifi collant et de client poste-à-poste (wispim)

Country Status (1)

Country Link
WO (1) WO2016011337A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3286951A4 (fr) * 2016-03-31 2018-02-28 Hewlett-Packard Enterprise Development LP Calcul d'une puissance isotrope rayonnée équivalente (eipr) d'un point d'accès (ap) de référence dans un réseau lorsque des conditions prédéterminées sont satisfaites
EP3723418A4 (fr) * 2017-12-28 2021-04-21 Sony Corporation Dispositif de communication sans fil
WO2022166576A1 (fr) * 2021-02-04 2022-08-11 华为技术有限公司 Procédé, appareil et système d'accès, et support de stockage lisible

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013063579A1 (fr) * 2011-10-28 2013-05-02 Qualcomm Incorporated Systèmes et procédés d'établissement de liaison réseau initial rapide
US20150063319A1 (en) * 2013-08-28 2015-03-05 Qualcomm Incorporated Systems, methods, and apparatus for preventing multiple re-association attempts

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013063579A1 (fr) * 2011-10-28 2013-05-02 Qualcomm Incorporated Systèmes et procédés d'établissement de liaison réseau initial rapide
US20150063319A1 (en) * 2013-08-28 2015-03-05 Qualcomm Incorporated Systems, methods, and apparatus for preventing multiple re-association attempts

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"WebSphere Application Server V6 Scalability and Performance Handbook", 1 May 2005 (2005-05-01), pages 1 - 370, XP055004700, Retrieved from the Internet <URL:http://www.redbooks.ibm.com/redbooks/pdfs/sg246392.pdf> [retrieved on 20110811] *
OFCOM: "wifi_in_metro_areas_report.pdf ; 18-13-0096-00-0000-wifi-in-metro-areas-report-pdf", IEEE DRAFT; 18-13-0096-00-0000-WIFI-IN-METRO-AREAS-REPORT-PDF, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.18, 9 August 2013 (2013-08-09), pages 1 - 77, XP068064282 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3286951A4 (fr) * 2016-03-31 2018-02-28 Hewlett-Packard Enterprise Development LP Calcul d'une puissance isotrope rayonnée équivalente (eipr) d'un point d'accès (ap) de référence dans un réseau lorsque des conditions prédéterminées sont satisfaites
EP3723418A4 (fr) * 2017-12-28 2021-04-21 Sony Corporation Dispositif de communication sans fil
US11477672B2 (en) 2017-12-28 2022-10-18 Sony Corporation Wireless communication device
WO2022166576A1 (fr) * 2021-02-04 2022-08-11 华为技术有限公司 Procédé, appareil et système d'accès, et support de stockage lisible

Similar Documents

Publication Publication Date Title
JP6972095B2 (ja) 高密度ワイヤレス環境における周波数多重化通信におけるチャネルセット割振り
US20210243628A1 (en) Methods and devices for sub-channelized transmission schemes in wlans
KR102462737B1 (ko) 웨이크업 라디오들에 대한 협대역 다중 채널 전송을 위한 절차들 및 메커니즘들
JP6166406B2 (ja) 無線ローカルエリアネットワークにおける高度アクティブスキャンニング
JP5986244B2 (ja) チャネルアグリゲーションおよび媒体アクセス制御再送信を実行するための方法および装置
JP5683715B2 (ja) 無線ダイレクトリンクオペレーションに関する方法および装置
JP2022543188A (ja) マルチリンクｗｌａｎを有効にする方法
EP3017643B1 (fr) Procédés multi-bandes pour systèmes de réseau local sans fil à brouillage limité
JP2021520098A (ja) 協力し合う車両間における効率的なリソース使用のための方法
KR20230048366A (ko) Wlan에서의 다중 링크 조향 및 제어
EP3243292A1 (fr) Transmission améliorée en couleur bss dans wlan (bss-cet)
KR20160132456A (ko) 와이파이 효율적 네트워크 전이
WO2013049136A1 (fr) Agrégation de porteuses intrabande
EP2992712A1 (fr) Opération de recherche, d&#39;opportunité de transmission (txop) et commande de flux pour extension de plage dans le wifi
US20150124776A1 (en) Data transmission method and apparatus in network linked with heterogeneous system
TW202209913A (zh) 支援端對端ＱｏＳ方法
WO2015171759A1 (fr) Gestion de spectre pour une priorité d&#39;accès dans un réseau à plusieurs niveaux
WO2016011337A1 (fr) Procédés et procédures d&#39;atténuation d&#39;interférences de client wifi collant et de client poste-à-poste (wispim)
CN113424645A (zh) Ue、无线电网络节点以及其中执行的用于处理通信的方法
US20240154636A1 (en) Methods for improving wireless performance using auxiliary radios
TW202420766A (zh) 啟用多鏈路毫米波請求及報告的方法及機制
CN118266246A (en) NR relay-method for multi-hop discovery and relay selection

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: 15748096

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15748096

Country of ref document: EP

Kind code of ref document: A1