PEER-TO-PEER COMMUNICATION IN WIRELESS NETWORKS

A first station (STA) in a wireless network is provided. The first STA establishes a peer-to-peer (P2P) link with a second STA. The first STA transmits, to an access point (AP), a first frame that requests the AP to assist in protecting a P2P communication between the first STA and the second STA. In response to the first frame, the first STA receives, from the AP, a second frame that indicates assistance that the AP is able to provide in response to the first frame. Then the first STA communicates with the second STA based on the assistance provided from the AP.

TECHNICAL FIELD

This disclosure relates generally to a wireless communication system, and more particularly to, for example, but not limited to, peer-to-peer (P2P) communications in wireless communication systems.

BACKGROUND

Wireless local area network (WLAN) technology has evolved toward increasing data rates and continues its growth in various markets such as home, enterprise and hotspots over the years since the late 1990s. WLAN allows devices to access the internet in the 2.4 GHZ, 5 GHZ, 6 GHz or 60 GHz frequency bands. WLANs are based on the Institute of Electrical and Electronic Engineers (IEEE) 802.11 standards. IEEE 802.11 family of standards aims to increase speed and reliability and to extend the operating range of wireless networks.

WLAN devices are increasingly required to support a variety of delay-sensitive applications or real-time applications such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and unmanned vehicles. To implement extremely low latency and extremely high throughput required by such applications, multi-link operation (MLO) has been suggested for the WLAN. The WLAN is formed within a limited area such as a home, school, apartment, or office building by WLAN devices. Each WLAN device may have one or more stations (STAs) such as the access point (AP) STA and the non-access-point (non-AP) STA.

The MLO may enable a non-AP multi-link device (MLD) to set up multiple links with an AP MLD. Each of multiple links may enable channel access and frame exchanges between the non-AP MLD and the AP MLD independently, which may reduce latency and increase throughput.

The description set forth in the background section should not be assumed to be prior art merely because it is set forth in the background section. The background section may describe aspects or embodiments of the present disclosure.

SUMMARY

An aspect of the disclosure provides a first station (STA) in a wireless network. The first STA comprises a memory and a processor coupled to the memory. The processor is configured to cause establishing a peer-to-peer (P2P) link with a second STA. The processor is configured to cause transmitting, to an access point (AP), a first frame that requests the AP to assist in protecting a P2P communication between the first STA and the second STA. The processor is configured to cause receiving, from the AP, a second frame that indicates assistance that the AP is able to provide in response to the first frame. The processor is configured to cause communicating with the second STA based on the assistance provided from the AP.

In some embodiments, the assistance is associated with reduction of interference to the P2P link from a basic service set (BSS) corresponding to the AP.

In some embodiments, the assistance is associated with channel access opportunity by the first STA or the second STA.

In some embodiments, the first STA is associated with the AP and the second STA is not associated with the AP.

In some embodiments, the first STA is not associated with the AP and the second STA is associated with the AP.

In some embodiments, the first STA is an owner of a P2P group that includes the first STA and the second STA.

In some embodiments, at least one of the first STA or the second STA is within the BSS.

An aspect of the disclosure provides an access point (AP) in a wireless network. The AP comprises a memory and a processor coupled to the memory. The processor is configured to cause receiving, from a first STA, a first frame that requests the AP to assist in protecting a peer-to-peer (P2P) communication with a second STA over a P2P link established between the first STA and the second STA. The processor is configured to cause determining assistance to provide the first STA based on the first frame. The processor is configured to cause transmitting, to the first STA, a second frame that indicates the assistance that the AP is able to provide.

In some embodiments, the assistance is associated with reduction of interference to the P2P link from a basic service set (BSS) corresponding to the AP.

In some embodiments, the assistance is associated with channel access opportunity by the first STA or the second STA.

In some embodiments, the first STA is associated with the AP and the second STA is not associated with the AP.

In some embodiments, the first STA is not associated with the AP and the second STA is associated with the AP.

In some embodiments, the first STA is an owner of a P2P group that includes the first STA and the second STA.

In some embodiments, at least one of the first STA or the second STA is within the BSS.

An aspect of the disclosure provides a method performed by a first station (STA) in a wireless network. The method comprises establishing a peer-to-peer (P2P) link with a second STA, transmitting, to an access point (AP), a first frame that requests the AP to assist in protecting a P2P communication between the first STA and the second STA, receiving, from the AP, a second frame that indicates assistance that the AP is able to provide in response to the first frame, and communicating with the second STA based on the assistance provided from the AP.

In some embodiments, the assistance is associated with reduction of interference to the P2P link from a basic service set (BSS) of the AP.

In some embodiments, the assistance is associated with channel access opportunity by the first STA or the second STA.

In some embodiments, the first STA is associated with the AP and the second STA is not associated with the AP.

In some embodiments, the first STA is not associated with the AP and the second STA is associated with the AP.

In some embodiments, the first STA is an owner of a P2P group that includes the first STA and the second STA.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with the appended drawings, is intended as a description of various implementations and is not intended to represent the only implementations in which the subject technology may be practiced. Rather, the detailed description includes specific details for the purpose of providing a thorough understanding of the inventive subject matter. As those skilled in the art would realize, the described implementations may be modified in various ways, all without departing from the scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature and not restrictive. Like reference numerals designate like elements.

The following description is directed to certain implementations for the purpose of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The examples in this disclosure are based on WLAN communication according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, including IEEE 802.11be standard and any future amendments to the IEEE 802.11 standard. However, the described embodiments may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, the Bluetooth standard, Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1×EV-DO, EV-DO Rev A, EV-DO Rev B, High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), 5G NR (New Radio), AMPS, or other known signals that are used to communicate within a wireless, cellular or internet of things (IoT) network, such as a system utilizing 3G, 4G, 5G, 6G, or further implementations thereof, technology.

Multi-link operation (MLO) is a key feature that is currently being developed by the standards body for next generation extremely high throughput (EHT) Wi-Fi systems in IEEE 802.11be. The Wi-Fi devices that support MLO are referred to as multi-link devices (MLD). With MLO, it is possible for a non-AP MLD to discover, authenticate, associate, and set up multiple links with an AP MLD. Channel access and frame exchange is possible on each link between the AP MLD and non-AP MLD.

FIG.1shows an example of a wireless network100in accordance with an embodiment. The embodiment of the wireless network100shown inFIG.1is for illustrative purposes only. Other embodiments of the wireless network100could be used without departing from the scope of this disclosure.

As shown inFIG.1, the wireless network100may include a plurality of wireless communication devices. Each wireless communication device may include one or more stations (STAs). The STA may be a logical entity that is a singly addressable instance of a medium access control (MAC) layer and a physical (PHY) layer interface to the wireless medium. The STA may be classified into an access point (AP) STA and a non-access point (non-AP) STA. The AP STA may be an entity that provides access to the distribution system service via the wireless medium for associated STAs. The non-AP STA may be a STA that is not contained within an AP-STA. For the sake of simplicity of description, an AP STA may be referred to as an AP and a non-AP STA may be referred to as a STA. In the example ofFIG.1, APs101and103are wireless communication devices, each of which may include one or more AP STAs. In such embodiments, APs101and103may be AP multi-link device (MLD). Similarly, STAs111-114are wireless communication devices, each of which may include one or more non-AP STAs. In such embodiments, STAs111-114may be non-AP MLD.

The APs101and103communicate with at least one network130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. The AP101provides wireless access to the network130for a plurality of stations (STAs)111-114with a coverage are120of the AP101. The APs101and103may communicate with each other and with the STAs using Wi-Fi or other WLAN communication techniques.

InFIG.1, dotted lines show the approximate extents of the coverage area120and125of APs101and103, which are shown as approximately circular for the purposes of illustration and explanation. It should be clearly understood that coverage areas associated with APs, such as the coverage areas120and125, may have other shapes, including irregular shapes, depending on the configuration of the APs.

As described in more detail below, one or more of the APs may include circuitry and/or programming for management of MU-MIMO and OFDMA channel sounding in WLANs. AlthoughFIG.1shows one example of a wireless network100, various changes may be made toFIG.1. For example, the wireless network100could include any number of APs and any number of STAs in any suitable arrangement. Also, the AP101could communicate directly with any number of STAs and provide those STAs with wireless broadband access to the network130. Similarly, each AP101and103could communicate directly with the network130and provides STAs with direct wireless broadband access to the network130. Further, the APs101and/or103could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

FIG.2Ashows an example of AP101in accordance with an embodiment. The embodiment of the AP101shown inFIG.2Ais for illustrative purposes, and the AP103ofFIG.1could have the same or similar configuration. However, APs come in a wide range of configurations, andFIG.2Adoes not limit the scope of this disclosure to any particular implementation of an AP.

As shown inFIG.2A, the AP101may include multiple antennas204a-204n, multiple radio frequency (RF) transceivers209a-209n, transmit (TX) processing circuitry214, and receive (RX) processing circuitry219. The AP101also may include a controller/processor224, a memory229, and a backhaul or network interface234. The RF transceivers209a-209nreceive, from the antennas204a-204n, incoming RF signals, such as signals transmitted by STAs in the network100. The RF transceivers209a-209ndown-convert the incoming RF signals to generate intermediate (IF) or baseband signals. The IF or baseband signals are sent to the RX processing circuitry219, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The RX processing circuitry219transmits the processed baseband signals to the controller/processor224for further processing.

The TX processing circuitry214receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor224. The TX processing circuitry214encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers209a-209nreceive the outgoing processed baseband or IF signals from the TX processing circuitry214and up-converts the baseband or IF signals to RF signals that are transmitted via the antennas204a-204n.

The controller/processor224can include one or more processors or other processing devices that control the overall operation of the AP101. For example, the controller/processor224could control the reception of uplink signals and the transmission of downlink signals by the RF transceivers209a-209n, the RX processing circuitry219, and the TX processing circuitry214in accordance with well-known principles. The controller/processor224could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor224could support beam forming or directional routing operations in which outgoing signals from multiple antennas204a-204nare weighted differently to effectively steer the outgoing signals in a desired direction. The controller/processor224could also support OFDMA operations in which outgoing signals are assigned to different subsets of subcarriers for different recipients (e.g., different STAs111-114). Any of a wide variety of other functions could be supported in the AP101by the controller/processor224including a combination of DL MU-MIMO and OFDMA in the same transmit opportunity. In some embodiments, the controller/processor224may include at least one microprocessor or microcontroller. The controller/processor224is also capable of executing programs and other processes resident in the memory229, such as an OS. The controller/processor224can move data into or out of the memory229as required by an executing process.

The controller/processor224is also coupled to the backhaul or network interface234. The backhaul or network interface234allows the AP101to communicate with other devices or systems over a backhaul connection or over a network. The interface234could support communications over any suitable wired or wireless connection(s). For example, the interface234could allow the AP101to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface234may include any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory229is coupled to the controller/processor224. Part of the memory229could include a RAM, and another part of the memory229could include a Flash memory or other ROM.

As described in more detail below, the AP101may include circuitry and/or programming for management of channel sounding procedures in WLANs. AlthoughFIG.2Aillustrates one example of AP101, various changes may be made toFIG.2A. For example, the AP101could include any number of each component shown inFIG.2A. As a particular example, an AP could include a number of interfaces234, and the controller/processor224could support routing functions to route data between different network addresses. As another example, while shown as including a single instance of TX processing circuitry214and a single instance of RX processing circuitry219, the AP101could include multiple instances of each (such as one per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, such as in legacy APs. Also, various components inFIG.2Acould be combined, further subdivided, or omitted and additional components could be added according to particular needs.

As shown inFIG.2A, in some embodiment, the AP101may be an AP MLD that includes multiple APs202a-202n. Each AP202a-202nis affiliated with the AP MLD101and includes multiple antennas204a-204n, multiple radio frequency (RF) transceivers209a-209n, transmit (TX) processing circuitry214, and receive (RX) processing circuitry219. Each APs202a-202nmay independently communicate with the controller/processor224and other components of the AP MLD101.FIG.2Ashows that each AP202a-202nhas separate multiple antennas, but each AP202a-202ncan share multiple antennas204a-204nwithout needing separate multiple antennas. Each AP202a-202nmay represent a physical (PHY) layer and a lower media access control (MAC) layer.

FIG.2Bshows an example of STA111in accordance with an embodiment. The embodiment of the STA111shown inFIG.2Bis for illustrative purposes, and the STAs111-114ofFIG.1could have the same or similar configuration. However, STAs come in a wide variety of configurations, andFIG.2Bdoes not limit the scope of this disclosure to any particular implementation of a STA.

As shown inFIG.2B, the STA111may include antenna(s)205, a RF transceiver210, TX processing circuitry215, a microphone220, and RX processing circuitry225. The STA111also may include a speaker230, a controller/processor240, an input/output (I/O) interface (IF)245, a touchscreen250, a display255, and a memory260. The memory260may include an operating system (OS)261and one or more applications262.

The RF transceiver210receives, from the antenna(s)205, an incoming RF signal transmitted by an AP of the network100. The RF transceiver210down-converts the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuitry225, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry225transmits the processed baseband signal to the speaker230(such as for voice data) or to the controller/processor240for further processing (such as for web browsing data).

The TX processing circuitry215receives analog or digital voice data from the microphone220or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the controller/processor240. The TX processing circuitry215encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver210receives the outgoing processed baseband or IF signal from the TX processing circuitry215and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s)205.

The controller/processor240can include one or more processors and execute the basic OS program261stored in the memory260in order to control the overall operation of the STA111. In one such operation, the controller/processor240controls the reception of downlink signals and the transmission of uplink signals by the RF transceiver210, the RX processing circuitry225, and the TX processing circuitry215in accordance with well-known principles. The controller/processor240can also include processing circuitry configured to provide management of channel sounding procedures in WLANs. In some embodiments, the controller/processor240may include at least one microprocessor or microcontroller.

The controller/processor240is also capable of executing other processes and programs resident in the memory260, such as operations for management of channel sounding procedures in WLANs. The controller/processor240can move data into or out of the memory260as required by an executing process. In some embodiments, the controller/processor240is configured to execute a plurality of applications262, such as applications for channel sounding, including feedback computation based on a received null data packet announcement (NDPA) and null data packet (NDP) and transmitting the beamforming feedback report in response to a trigger frame (TF). The controller/processor240can operate the plurality of applications262based on the OS program261or in response to a signal received from an AP. The controller/processor240is also coupled to the I/O interface245, which provides STA111with the ability to connect to other devices such as laptop computers and handheld computers. The I/O interface245is the communication path between these accessories and the main controller/processor240.

The controller/processor240is also coupled to the input250(such as touchscreen) and the display255. The operator of the STA111can use the input250to enter data into the STA111. The display255may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites. The memory260is coupled to the controller/processor240. Part of the memory260could include a random access memory (RAM), and another part of the memory260could include a Flash memory or other read-only memory (ROM).

AlthoughFIG.2Bshows one example of STA111, various changes may be made toFIG.2B. For example, various components inFIG.2Bcould be combined, further subdivided, or omitted and additional components could be added according to particular needs. In particular examples, the STA111may include any number of antenna(s)205for MIMO communication with an AP101. In another example, the STA111may not include voice communication or the controller/processor240could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, whileFIG.2Billustrates the STA111configured as a mobile telephone or smartphone, STAs could be configured to operate as other types of mobile or stationary devices.

As shown inFIG.2B, in some embodiment, the STA111may be a non-AP MLD that includes multiple STAs203a-203n. Each STA203a-203nis affiliated with the non-AP MLD111and includes an antenna(s)205, a RF transceiver210, TX processing circuitry215, and RX processing circuitry225. Each STAs203a-203nmay independently communicate with the controller/processor240and other components of the non-AP MLD111.FIG.2Bshows that each STA203a-203nhas a separate antenna, but each STA203a-203ncan share the antenna205without needing separate antennas. Each STA203a-203nmay represent a physical (PHY) layer and a lower media access control (MAC) layer.

FIG.3shows an example of multi-link communication operation in accordance with an embodiment. The multi-link communication operation may be usable in IEEE 802.11be standard and any future amendments to IEEE 802.11 standard. InFIG.3, an AP MLD310may be the wireless communication device101and103inFIG.1and a non-AP MLD220may be one of the wireless communication devices111-114inFIG.1.

As shown inFIG.3, the AP MLD310may include a plurality of affiliated APs, for example, including AP 1, AP 2, and AP 3. Each affiliated AP may include a PHY interface to wireless medium (Link 1, Link 2, or Link 3). The AP MLD310may include a single MAC service access point (SAP)318through which the affiliated APs of the AP MLD310communicate with a higher layer (Layer 3 or network layer). Each affiliated AP of the AP MLD310may have a MAC address (lower MAC address) different from any other affiliated APs of the AP MLD310. The AP MLD310may have a MLD MAC address (upper MAC address) and the affiliated APs share the single MAC SAP318to Layer 3. Thus, the affiliated APs share a single IP address, and Layer 3 recognizes the AP MLD310by assigning the single IP address.

The non-AP MLD320may include a plurality of affiliated STAs, for example, including STA 1, STA 2, and STA 3. Each affiliated STA may include a PHY interface to the wireless medium (Link 1, Link 2, or Link 3). The non-AP MLD320may include a single MAC SAP328through which the affiliated STAs of the non-AP MLD320communicate with a higher layer (Layer 3 or network layer). Each affiliated STA of the non-AP MLD320may have a MAC address (lower MAC address) different from any other affiliated STAs of the non-AP MLD320. The non-AP MLD320may have a MLD MAC address (upper MAC address) and the affiliated STAs share the single MAC SAP328to Layer 3. Thus, the affiliated STAs share a single IP address, and Layer 3 recognizes the non-AP MLD320by assigning the single IP address.

The AP MLD310and the non-AP MLD320may set up multiple links between their affiliate APs and STAs. In this example, the AP 1 and the STA 1 may set up Link 1 which operates in 2.4 GHz band. Similarly, the AP 2 and the STA 2 may set up Link 2 which operates in 5 GHZ band, and the AP 3 and the STA 3 may set up Link 3 which operates in 6 GHz band. Each link may enable channel access and frame exchange between the AP MLD310and the non-AP MLD320independently, which may increase date throughput and reduce latency. Upon associating with an AP MLD on a set of links (setup links), each non-AP device is assigned a unique association identifier (AID).

The following documents are hereby incorporated by reference in their entirety into the present disclosure as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” ii) IEEE 802.11ax-2021, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” and iii) IEEE P802.11be/D3.1, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.”

FIG.4shows an example network in accordance with an embodiment. The network depicted inFIG.4is for explanatory and illustration purposes.FIG.4does not limit the scope of this disclosure to any particular implementation.

InFIG.4, a plurality of STAs410are non-AP stations associated with AP430, and a plurality of STAs420are non-AP stations which are not associated with AP430. Additionally, solid lines between stations represent uplink or downlink with AP430, while the dashed lines between stations represent a direct link between STAs.

Next generation WLAN system needs to provide improved support for low-latency applications. Today, it is not uncommon to observe numerous devices operating on the same network. Many of these devices may have a tolerance for latency, but still compete with the devices running low-latency applications for the same time and frequency resources. In some cases, the AP as a network controller may not have enough control over the unregulated or unmanaged traffic that contends with the low-latency traffic within the infrastructure basic service set (BSS). In some embodiments, the infrastructure BSS is a basic service set that includes an AP and one or more non-APs, while independent BSS is a basic service set where stations communicate with each other without the need for a centralized AP. Some of the unregulated or unmanaged traffic that interferes with the latency-sensitive traffic in the AP's BSS may originate from uplink, downlink, or direct link communications within the infrastructure BSS that the AP manages. Another source of the interference may be transmission from the neighboring infrastructure OBSS (Overlapping Basic Service Set), while others may come from neighboring independent BSS or P2P networks. Therefore, the next generation WLAN system needs mechanisms to more effectively handle unmanaged traffic while prioritizing low-latency traffic in the network. On the other hand, a P2P communication device (or P2P device) may also suffer from interference caused by the infrastructure BSS. The P2P device may or may not be associated with the infrastructure AP as shown inFIG.4.

FIG.5shows an example of a P2P link and infrastructure network in accordance with an embodiment.

Referring toFIG.5, AP 1 forms an infrastructure BSS. STA 1 and STA 2 are associated with AP 1, and STA 3 is a peer STA that communicates with STA 1 in a P2P link. STA 3 is not associated with AP 1. AP 1 is an infrastructure AP. In this example, STA 3 may suffer from interference from the infrastructure BSS.

When STA 3 suffers from interference originating from the infrastructure BSS, it may cause degradation in performance for the P2P communication between STA 1 and STA 3. Therefore, AP 1 may have to take measures to reduce the interference towards STA 3, which may be referred to as the victim P2P STA or victim STA. Therefore, a mechanism is needed to reduce the interference from the infrastructure network toward the victim P2P STA. However, the current WLAN system does not provide such mechanisms.

FIG.6shows another example of a P2P link and infrastructure network in accordance with an embodiment.

Referring toFIG.6, AP 1 forms an infrastructure BSS. STA 1, STA 2, and STA 3 are associated with AP 1. STA 4 and STA 5 are peer STAs that communicate with STA 3. STA 3 is a group owner (GO) for a P2P group. STA 4 and STA 5 are members of the P2P group but are not associated with AP 1. As shown inFIG.6, STA 3 and STA 4 are located within the BSS, while STA 5 is either just outside or at the edge of the BSS.

In this example, STA 3 and STA 4 may experience interference from the infrastructure BSS. Therefore, when STA 4 (the victim P2P STA) is a member of the P2P Group, STA 3 (the P2P GO) needs to mitigate this interference, for example, by coordinating with the infrastructure AP (AP 1). However, the current WLAN system does not provide such a mechanism. Thus, there needs to be a mechanism that enables STA 3 to take actions to reduce interference from the infrastructure network.

The disclosure provides various solutions and embodiments for better coexistence between the P2P network and the infrastructure network, for example and without limitation, to minimize interference to the P2P network from the infrastructure network.

FIG.7shows an example scenario of a P2P network and infrastructure network in accordance with an embodiment. The operation depicted inFIG.7is for illustration purposes and does not limit the scope of this disclosure to any particular implementations.

Referring toFIG.7, AP 1 forms a BSS 1 and is associated with STA 1, STA 3, and STA 4. STA 1 has set up a P2P link with STA 2 which is not associated with AP 1. In this scenario, the P2P link between STA 1 and STA 2 may experience interference caused by communications within infrastructure BSS 1. STA 1 may send a P2P assistance request to AP 1 to minimize the impact of communication in BSS 1 on the P2P link. InFIG.7, solid lines between stations represent uplink or downlink with AP 1, while the dashed lines between stations represent a P2P link between STAs.

In some embodiments, a first STA is associated with an AP and has formed a P2P link with a second STA. When the first STA intends to seek assistance from the AP for protection of the P2P communication between the first STA and the second STA, the first STA may send a P2P assistance request frame to the AP indicating a need to protect the P2P link.

FIG.8shows an example P2P assistance in accordance with an embodiment. The operation depicted inFIG.8is for illustration purposes and does not limit the scope of this disclosure to any particular implementations.

The example ofFIG.8is based on the scenario depicted inFIG.7. Referring toFIG.8, STA 1 send a P2P assistance request frame to AP 1. In response, AP 1 sends a P2P assistance response frame to STA 1. The P2P assistance request frame may carry information, for example and without limitation, including:i) AID of STA 1;ii) AID of STA 2;iii) MAC Address of STA 1;iv) MAC Address of STA 2;v) Interference level perceived by STA 1 and/or STA 2 due to a transmission from BSS 1;vi) Maximum interference level tolerable by the P2P link (e.g., maximum received power from the infrastructure network);vii) An indication of whether STA 1 or/and STA 2 are the victim STAs;viii) An identification for the P2P link;ix) An identification (e.g. AID) of STA in BSS 1 that causes interference to the P2P link;x) Type of assistance needed for the P2P link from BSS 1. For example, AP 1 i) lowers the transmission power (e.g., using spatial reuse procedures), or ii) perform beamforming in another direction to mitigate interference to the victim STAs; andxi) Timeline of operation for the P2P link. For example, STA 1 shares TWT information, TDLS (tunneled direct-link setup) peer PSM (power save mode) information, TDLS U-APSD (unscheduled automatic power save delivery) information, or any other power saving mechanism adopted by victim STAs. Based on this shared information, the AP will know when to assist the P2P link, for example, by i) muting the transmission, ii) not triggering nearby infrastructure STAs for uplink, iii) performing spatial reuse for power reduction, or iv) creating a null beam towards the victim STAs.

Upon receiving the P2P assistance request frame from STA 1, AP 1 sends a P2P assistance response frame to STA 1 indicating how the AP 1 intends to assist the P2P communication between STA 1 and STA 2. The P2P assistance response frame may carry information, for example and without limitation, including:i) An indication of whether AP 1 accepts or rejects the P2P assistance request;ii) An indication of types of assistance that will be provided by AP 1. For example, i) reducing power level, ii) performing beamforming, or iii) not scheduling transmission during the P2P link operation;iii) AID of STA 1;iv) AID of STA 2;v) MAC Address of STA 1;vi) MAC Address of STA 2;vii) An identification for the P2P link;viii) Alternative suggestion for the timeline for the P2P link operation; andix) Alternative suggestion for other P2P parameters to use by STA 1 and STA 2. For example, AP 1 may recommend increasing or decreasing the P2P transmission power with indication of the maximum transmission power that the P2P STAs should use.

FIG.9shows an example process900of coexistence between the P2P network and the infrastructure network in accordance with an embodiment. For explanatory and illustration purposes, the process900may be performed by STA 1 depicted inFIG.8. Although one or more operations are described or shown in particular sequential order, in other embodiments the operations may be rearranged in a different order, which may include performance of multiple operations in at least partially overlapping time periods.

Referring toFIG.9, the process900may begin in operation901. In operation901, a first STA has formed a P2P link with a second STA. The first STA is associated with an infrastructure AP in its BSS, while the second STA is not associated with the infrastructure AP.

In operation903, the first STA may experience interference from the infrastructure BSS formed by the AP. The first STA determines that the P2P link needs assistance from the infrastructure AP to protect the P2P link. In some embodiments, the assistance may be associated with providing better channel access opportunity or reducing the perceived interference level for the P2P link.

In operation905, the first STA sends a P2P assistance request frame to the infrastructure AP. The P2P assistance request frame may include various parameters indicating requests for assistance from the infrastructure AP.

In operation907, the first STA receives a P2P assistance response frame from the infrastructure AP that indicates the acceptance to the request for assistance. The P2P assistance response frame may include various parameters indicating acceptance of the request for assistance from the infrastructure AP. In some embodiments, the response may be associated with providing better channel access opportunity or reducing the interference level from the infrastructure BSS.

In operation909, the first STA initiates communication with the second STA over the P2P link using parameters indicated in the P2P assistance request frame or the P2P assistance response frame.

FIG.10shows another example process1000of coexistence between the P2P network and the infrastructure network in accordance with an embodiment. For explanatory and illustration purposes, the process1000may be performed by AP 1 depicted inFIG.8. Although one or more operations are described or shown in particular sequential order, in other embodiments the operations may be rearranged in a different order, which may include performance of multiple operations in at least partially overlapping time periods.

Referring toFIG.10, the process1000may begin in operation1001. In operation1001, an AP receives a P2P assistance request frame from a STA. The AP is an infrastructure AP that forms its infrastructure BSS, and the STA forms a P2P link with another STA. The STA is associated with the AP, while another STA is not associated with the AP. The P2P assistance request frame may be associated with providing better channel access opportunity or reducing the perceived interference level for the P2P link to reduce interference from the infrastructure BSS to the P2P link.

In operation1003, upon receiving the P2P assistance request frame, the AP determines conditions and criteria for the assistance request.

In operation1005, the AP evaluates the criteria and conditions for the requested assistance. Then, the AP determines to accept the requested assistance from the STA.

In operation1007, the AP sends a P2P assistance response frame to the STA. The P2P assistance response frame may include various parameters indicating acceptance of the requested assistance.

In some embodiments, the STA that sends the P2P assistance request frame to the AP may or may not be associated with the AP.

FIG.11shows another example of coexistence between the P2P network and the infrastructure network in accordance with an embodiment. The operation depicted inFIG.11is for illustration purposes and does not limit the scope of this disclosure to any particular implementations.

The example ofFIG.11is also based on the scenario depicted inFIG.7. Referring toFIG.11, STA 2 is not associated with AP 1, which is unlike the example ofFIG.8. STA 2 sends a P2P assistance request frame to AP 1. In response, AP 1 sends a P2P assistance response frame to STA 2. Then, STA 2 communicates with STA 1 with the assistance from AP 1.

In some embodiments, when a STA is a P2P GO of a P2P group, the STA may send a P2P assistance request frame to an AP to request assistance to protect the P2P communication in the P2P group. The STA may be associated with the AP. In an embodiment, the STA may not be associated with the AP.

In some embodiments, a P2P GO may send a P2P group assistance request frame to an infrastructure AP, for example and without limitation, indicating i) a request for resource (e.g., time, frequency, and channel access opportunity), ii) a request to reduce interference toward P2P group to ensure better P2P communication within the P2P group (e.g., reduction of transmission power from infrastructure BSS to P2P group), and/or iii) a request to create a null beam toward the P2P group.

In some embodiments, the P2P group assistance request frame may include request information, for example and without limitation, including:i) AIDs or a subset of the AIDs of STAs in the P2P group that need the assistance;ii) MAC address or a subset of the MAC addresses of STAs in the P2P group that need the assistance;iii) Interference level perceived by STAs in the P2P group;iv) Maximum interference level tolerable by the P2P link (e.g., maximum received power from the infrastructure network);v) A list of subsets of the STAs in the P2P group that need assistance;vi) Identification of P2P links in the P2P group;vii) Identifications (e.g., AID) of the STAs in infrastructure BSS causing interference toward the P2P links in the P2P group;viii) Types of assistance needed for the P2P group from the infrastructure BSS. For example, whether the requesting P2P STA group needs the AP (or any STAs associated with the AP) to lower its transmission power or perform beamforming in another direction to avoid or mitigate interference for the victim STAs; andix) Timeline of operation for the P2P links in the P2P. For example, the requesting P2P STA may share TWT information, TDLS peer PSM information, TDLS U-APSD information, or any other power saving mechanism adopted by the P2P STAs in the P2P. By knowing this information, the AP will know when to assist the P2P link by i) muting the AP's transmission, ii) not triggering nearby infrastructure STAs for uplink, iii) perform spatial reuse, or iv) creating a null beam towards the victim STAs.

In some embodiments, upon receiving the P2P group assistance request frame from a P2P STA (e.g., P2P GO) for P2P assistance for the P2P group, the AP may send a P2P group assistance response frame to the P2P STA indicating how the AP intends to assist the P2P communication between P2P STAs in the P2P group. The P2P group assistance response frame may include response information, for example and without limitation, including:i) An indication of whether the AP accepts or rejects the P2P group assistance request;ii) An indication of types of assistance provided by the AP. For example, reduction of power level, beamforming, and stopping scheduling transmission during the P2P link operation;iii) AIDs of a subset of STA within the P2P group that can be benefited by the AP's assistance;iv) MAC addresses of a subset of STA within the P2P group that can be benefited by the AP's assistance;v) An identification for the P2P links within the P2P group for which the P2P assistance is provided;vi) Alternative suggestion for the timeline for the P2P link operation within the P2P group. For example, an alternative TWT information or TDLS peer PSM; andvii) Alternative suggestion for other P2P parameters for P2P STAs. For example, i) a recommendation of increasing or decreasing the P2P transmission power within the P2P group, iii) indication of the maximum transmission power that the P2P STAs should use, or iv) number of MCS to use for the P2P group.

FIG.12shows another example of coexistence between the P2P network and the infrastructure network in accordance with an embodiment. The operation depicted inFIG.12is for illustration purposes and does not limit the scope of this disclosure to any particular implementations.

Referring toFIG.12, AP 1 forms BSS 1 and is associated with STA 2, STA 3, and STA 4. STA 2 is a member of a P2P group that includes STA 1, STA 2, STA 5, and STA 6. STA 1 and STA 2 communicate over a P2P link established between them. Also, STA 5 and STA 6 are out of BSS 1. In this scenario, STA 2 may be a P2P GO of the P2P group. When the P2P group experience interference from the BSS 1, the STA 2 (P2P GO) may send a P2P group assistance request frame to the AP 1 indicating a request for assistance to protect communication in the P2P group. In response, AP 1 sends a P2P group assistance response from the STA 2 indicating the acceptance of the request or assistance which is provided by BSS 1.

Various embodiments described in this disclosure provide a mechanism for coexistence between P2P networks and infrastructure networks. By coordinating with the infrastructure BSS, the P2P network can reduce interference from the infrastructure BSS. This coordination helps to protect and enhance P2P communication.

All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using a phrase means for or, in the case of a method claim, the element is recited using the phrase step for.