Peer-to-peer communication in wireless network

Abstract

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

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to peer-to-peer (P2P) communication in wireless communication systems, for example, but not limited to. Background Technology

[0002] Since the late 1990s, Wireless Local Area Network (WLAN) technology has evolved towards increasing data rates and continues to grow in various markets such as homes, businesses, and hotspots. WLAN allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard family aims to improve speed and reliability and extend the operational range of wireless networks.

[0003] WLAN devices increasingly need to support a variety of latency-sensitive or real-time applications, such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and autonomous vehicles. To achieve the extremely low latency and extremely high throughput required for such applications, Multi-Link Operation (MLO) has been proposed for WLANs. A WLAN is formed by WLAN devices within a limited area such as a home, school, apartment, or office building. Each WLAN device can have one or more Stations (STAs), such as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs.

[0004] MLO enables a non-AP multi-link device (MLD) to establish multiple links with an AP MLD. Each of these links can independently enable channel access and frame exchange between the non-AP MLD and the AP MLD, which can reduce latency and increase throughput.

[0005] The descriptions set forth in the Background section should not be assumed to be prior art simply because they are set forth in the Background section. The Background section may describe aspects or embodiments of this disclosure. Summary of the Invention

[0006] One aspect of this disclosure provides a first station (STA) in a wireless network. The first STA includes a memory and a processor coupled to the memory. The processor is configured to establish a peer-to-peer (P2P) link with a second STA. The processor is configured to send a first frame to an access point (AP) requesting AP assistance to protect the P2P communication between the first STA and the second STA. The processor is configured to receive a second frame from the AP indicating that the AP can respond to the assistance provided by the first frame. The processor is configured to communicate with the second STA based on the assistance provided by the AP.

[0007] In some embodiments, assistance is associated with reducing interference to the P2P link from the basic service set (BSS) corresponding to the AP.

[0008] In some embodiments, an auxiliary channel access opportunity is associated with the first STA or the second STA.

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

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

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

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

[0013] One aspect of this disclosure provides an access point (AP) in a wireless network. The AP includes a memory and a processor coupled to the memory. The processor is configured to receive from a first STA a first frame requesting AP assistance in protecting a peer-to-peer (P2P) communication with a second STA on a P2P link established between the first STA and the second STA. The processor is configured to determine assistance to be provided to the first STA based on the first frame. The processor is configured to send to the first STA a second frame indicating the assistance that the AP can provide.

[0014] In some embodiments, assistance is associated with reducing interference to the P2P link from the basic service set (BSS) corresponding to the AP.

[0015] In some embodiments, an auxiliary channel access opportunity is associated with the first STA or the second STA.

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

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

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

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

[0020] One aspect of this disclosure provides a method performed by a first station (STA) in a wireless network. The method includes establishing a peer-to-peer (P2P) link with a second STA, sending a first frame to an access point (AP) requesting AP assistance to protect the P2P communication between the first and second STAs, receiving a second frame from the AP indicating that the AP can provide assistance in response to the first frame, and communicating with the second STA based on the assistance provided by the AP.

[0021] In some embodiments, assistance is associated with reducing interference to the P2P link from the AP's Basic Service Set (BSS).

[0022] In some embodiments, an auxiliary channel access opportunity is associated with the first STA or the second STA.

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

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

[0025] In some embodiments, the first STA is the owner of a P2P group that includes the first STA and the second STA. Attached Figure Description

[0026] Figure 1 An example of a wireless network according to an embodiment is shown.

[0027] Figure 2a An example of an AP according to an embodiment is shown.

[0028] Figure 2b An example of a STA according to an embodiment is shown.

[0029] Figure 3 An example of multi-link communication operation according to an embodiment is shown.

[0030] Figure 4 An example network according to an embodiment is shown.

[0031] Figure 5 An example of a P2P link and infrastructure network according to an embodiment is shown.

[0032] Figure 6 Another example of a P2P link and infrastructure network according to an embodiment is shown.

[0033] Figure 7 An example scenario of a P2P network and an infrastructure network according to an embodiment is shown.

[0034] Figure 8An example P2P assistance is shown according to an embodiment.

[0035] Figure 9 An example process 900 for coexistence between a P2P network and an infrastructure network according to an embodiment is shown.

[0036] Figure 10 Another example process 1000 for coexistence between a P2P network and an infrastructure network according to an embodiment is shown.

[0037] Figure 11 Another example of coexistence between a P2P network and an infrastructure network according to an embodiment is shown.

[0038] Figure 12 Another example of coexistence between a P2P network and an infrastructure network according to an embodiment is shown.

[0039] In one or more embodiments, not all components depicted in each figure are necessary, and one or more embodiments may include additional components not shown in the figures. Variations in the arrangement and type of components may be made without departing from the scope of this subject matter disclosure. Additional components, different components, or fewer components may be utilized within the scope of this subject matter disclosure. Detailed Implementation

[0040] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various implementations and are not intended to represent the only components that can be used to practice the subject matter. Specifically, the specific embodiments include particular details to provide a thorough understanding of the inventive subject matter. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the scope of this disclosure. Therefore, the drawings and descriptions are to be considered illustrative rather than restrictive in nature. The same reference numerals denote the same elements.

[0041] The following description pertains to certain embodiments for the purpose of describing the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety 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 the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. However, the described embodiments can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, Bluetooth standard, Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-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 for transmitting and receiving radio frequency (RF) signals for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof.

[0042] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "station" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0043] Multilink Operation (MLO) is a key feature currently being developed by the standards body for next-generation Ultra High Throughput (EHT) Wi-Fi systems in IEEE 802.11be. Wi-Fi devices that support MLO are called Multilink Devices (MLDs). Using MLO, a non-AP MLD can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame switching can occur on each link between the AP MLD and non-AP MLDs.

[0044] Figure 1 An example of a wireless network 100 according to an embodiment is shown. Figure 1 The illustrated embodiment of the wireless network 100 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0045] like Figure 1 As shown, wireless network 100 may include multiple wireless communication devices. Each wireless communication device may include one or more stations (STAs). An STA may be a logical entity that is a separate addressable instance of an interface to the Media Access Control (MAC) layer and Physical (PHY) layer of the wireless media. STAs may be classified as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs. An AP STA may be an entity that provides access to distributed system services to an associated STA via the wireless media. A Non-AP STA may be a STA that is not included within an AP-STA. For simplicity, an AP STA may be referred to as an AP, and a Non-AP STA may be referred to as a STA. Figure 1 In the example, APs 101 and 103 are wireless communication devices, each of which may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP multilink devices (MLDs). Similarly, STAs 111 to 114 are wireless communication devices, each of which may include one or more non-AP STAs. In such an embodiment, STAs 111 to 114 may be non-AP MLDs.

[0046] APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. AP 101 provides wireless access to network 130 to multiple stations 111 to 114 with coverage 120 that have AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

[0047] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "station" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0048] exist Figure 1 In the diagram, the dashed lines indicate the approximate extent of the coverage areas 120 and 125 of APs 101 and 103, which are shown as approximately circular for illustrative and explanatory purposes. It should be clearly understood that, depending on the configuration of the APs, the coverage areas associated with the APs (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0049] As described in more detail below, one or more APs in an AP may include circuitry and / or programming for managing MU-MIMO and OFDMA channel detection in a WLAN. Although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Furthermore, AP 101 can communicate directly with any number of STAs and provide these STAs with wireless broadband access to network 130. Similarly, each AP 101 and 103 can communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. Additionally, AP 101 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0050] Figure 2a An example of AP 101 according to an embodiment is shown. Figure 2a The embodiment of AP 101 shown is for illustrative purposes, and Figure 1 AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and Figure 2a This disclosure is not intended to limit the scope of any particular implementation of AP.

[0051] like Figure 2a As shown, AP 101 may include multiple antennas 204a to 204n, multiple radio frequency (RF) transceivers 209a to 209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. AP 101 may also include a controller / processor 224, a memory 229, and a backhaul or network interface 234. RF transceivers 209a to 209n receive incoming RF signals from antennas 204a to 204n, such as signals transmitted by STAs in network 100. RF transceivers 209a to 209n downconvert the incoming RF signals to generate intermediate (IF) or baseband signals. The IF or baseband signals are sent to RX processing circuitry 219, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 219 sends the processed baseband signals to controller / processor 224 for further processing.

[0052] TX processing circuit 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 224. TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 209a to 209n receive the outgoing processed baseband or IF signal from TX processing circuit 214 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 204a to 204n.

[0053] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller / processor 224 may control the reception of uplink signals and the transmission of downlink signals by the RF transceivers 209a to 209n, the RX processing circuitry 219, and the TX processing circuitry 214 according to well-known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a to 204n are weighted differently to effectively direct outgoing signals to a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are allocated to subsets of different subcarriers for different receivers (e.g., different STAs 111 to 114). The controller / processor 224 may support various other functions in the AP 101, including combining DL MU-MIMO and OFDMA in the same transmission opportunity. In some embodiments, the controller / processor 224 may include at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in the memory 229. The controller / processor 224 can move data into or out of the memory 229 as needed for the execution process.

[0054] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP 101 to communicate with other devices or systems via a backhaul connection or over a network. Interface 234 can support communication via any suitable wired or wireless connection. For example, interface 234 can allow the AP 101 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 234 may include any suitable structure supporting communication via a wired or wireless connection, such as an Ethernet or RF transceiver. Memory 229 is coupled to the controller / processor 224. A portion of memory 229 may include RAM, and another portion of memory 229 may include flash memory or other ROM.

[0055] As described in more detail below, AP 101 may include circuitry and / or procedures for managing the channel detection process in a WLAN. Although Figure 2a An example of AP 101 is shown, but it is possible to compare it with other versions. Figure 2a Various changes can be made. For example, AP101 can include any number of... Figure 2aEach component shown. As a specific example, the AP may include multiple interfaces 234, and the controller / processor 224 may support routing functionality to route data between different network addresses. As another example, although shown as a single instance including TX processing circuitry 214 and a single instance including RX processing circuitry 219, AP 101 may include multiple instances of each (e.g., one per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, as in a conventional AP. Furthermore, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0056] like Figure 2a As shown, in some embodiments, AP 101 may be an AP MLD comprising multiple APs 202a to 202n. Each AP 202a to 202n is attached to AP MLD 101 and includes multiple antennas 204a to 204n, multiple radio frequency (RF) transceivers 209a to 209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. Each AP 202a to 202n may communicate independently with controller / processor 224 and other components of AP MLD 101. Figure 2a The diagram shows that each AP 202a to 202n has multiple separate antennas, but each AP 202a to 202n can share multiple antennas 204a to 204n without requiring separate multiple antennas. Each AP 202a to 202n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0057] Figure 2b An example of STA 111 according to an embodiment is shown. Figure 2b The embodiment of STA 111 shown is for illustrative purposes, and Figure 1 STAs 111 to 114 can have the same or similar configurations. However, STAs have a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope of any particular implementation of STA.

[0058] like Figure 2b As shown, STA 111 may include an antenna 205, an RF transceiver 210, a TX processing circuit 215, a microphone 220, and an RX processing circuit 225. STA 111 may also include a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touchscreen 250, a display 255, and a memory 260. The memory 260 may include an operating system (OS) 261 and one or more applications 262.

[0059] RF transceiver 210 receives incoming RF signals transmitted by the AP of network 100 from antenna 205. RF transceiver 210 down-converts the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 225 sends the processed baseband signals to speaker 230 (e.g., for voice data) or to controller / processor 240 for further processing (e.g., for web browsing data).

[0060] TX processing circuitry 215 receives analog or digital voice data from microphone 220, or other outgoing baseband data (such as web data, email, or interactive video game data) from controller / processor 240. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the outgoing processed baseband or IF signal from TX processing circuitry 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0061] The controller / processor 240 may include one or more processors and executes a basic OS program 261 stored in memory 260 to control the overall operation of STA 111. In one such operation, the controller / processor 240 controls the RF transceiver 210, RX processing circuitry 225, and TX processing circuitry 215 to receive downlink signals and transmit uplink signals according to well-known principles. The controller / processor 240 may also include processing circuitry configured to provide management of the channel detection process in the WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0062] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sensing processes in the WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution of the process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for channel sensing, including feedback calculations based on received Null Data Packet Advertisements (NDPA) and Null Data Packets (NDP), and sending beamforming feedback reports in response to trigger frames (TF). The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to signals received from the AP. The controller / processor 240 is also coupled to an I / O interface 245, which provides the STA 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0063] The controller / processor 240 is also coupled to input 250 (such as a touchscreen) and display 255. An operator of STA 111 can use input 250 to input data into STA 111. Display 255 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website). Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), and another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0064] although Figure 2b An example of STA 111 is shown, but it is possible to compare it with other models. Figure 2b Make various changes. For example, Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In a specific example, STA 111 may include any number of antennas 205 for MIMO communication with AP 101. In another example, STA 111 may not include voice communication, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 2b The STA 111 is shown configured as a mobile phone or smartphone, but the STA can be configured to operate as other types of mobile or fixed devices.

[0065] like Figure 2bAs shown, in some embodiments, STA 111 may be a non-AP MLD comprising multiple STAs 203a to 203n. Each STA 203a to 203n is attached to the non-AP MLD 111 and includes an antenna 205, an RF transceiver 210, a TX processing circuit 215, and an RX processing circuit 225. Each STA 203a to 203n may independently communicate with the controller / processor 240 and other components of the non-AP MLD 111. Figure 2b Each STA 203a to 203n is shown to have a separate antenna, but each STA 203a to 203n can share antenna 205 without requiring a separate antenna. Each STA 203a to 203n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0066] Figure 3 An example of multi-link communication operation according to an embodiment is shown. Multi-link communication operation can be used in the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. Figure 3 In the middle, AP MLD 310 can be Figure 1 Wireless communication devices 101 and 103 are included, and the non-AP MLD 220 can be... Figure 1 One of the wireless communication devices 111 to 114.

[0067] like Figure 3 As shown, AP MLD 310 may include multiple affiliated APs, such as AP 1, AP 2, and AP 3. Each affiliated AP may include a PHY interface to the wireless media (Link 1, Link 2, or Link 3). AP MLD 310 may include a single MAC Service Access Point (SAP) 318 through which the affiliated APs of AP MLD 310 communicate with higher layers (Layer 3 or network layer). Each affiliated AP of AP MLD 310 may have a different MAC address (lower-layer MAC address) than any other affiliated AP of AP MLD 310. AP MLD 310 may have an MLD MAC address (upper-layer MAC address), and the affiliated APs share a single MAC SAP 318 to Layer 3. Therefore, the affiliated APs share a single IP address, and Layer 3 identifies AP MLD 310 by assigning a single IP address.

[0068] A non-AP MLD 320 may include multiple affiliated STAs, such as STA 1, STA 2, and STA 3. Each affiliated STA may include a PHY interface to the wireless media (Link 1, Link 2, or Link 3). A non-AP MLD 320 may include a single MAC SAP 328, through which affiliated STAs communicate with higher layers (Layer 3 or network layer). Each affiliated STA of a non-AP MLD 320 may have a different MAC address (lower-layer MAC address) than any other affiliated STA of the non-AP MLD 320. A non-AP MLD 320 may have an MLD MAC address (upper-layer MAC address), and affiliated STAs share the single MAC SAP 328 to Layer 3. Therefore, affiliated STAs share a single IP address, and Layer 3 identifies the non-AP MLD 320 by assigning this single IP address.

[0069] AP MLD 310 and non-AP MLD 320 can establish multiple links between their associated APs and STAs. In this example, AP 1 and STA 1 can establish Link 1, operating in the 2.4 GHz band. Similarly, AP 2 and STA 2 can establish Link 2, operating in the 5 GHz band, and AP 3 and STA 3 can establish Link 3, operating in the 6 GHz band. Each link can independently enable channel access and frame exchange between AP MLD 310 and non-AP MLD 320, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (link establishment), each non-AP device is assigned a unique Association Identifier (AID).

[0070] The following documents are incorporated herein by reference in their entirety, as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”, ii) IEEE 802.11ax-2021, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”, and iii) IEEE P802.11be / D3.1, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”.

[0071] Figure 4 An example network according to an embodiment is shown. Figure 4 The network depicted is for illustrative and explanatory purposes. Figure 4 This disclosure is not intended to limit the scope to any particular implementation.

[0072] exist Figure 4In this diagram, multiple STAs 410 are non-AP stations associated with AP 430, and multiple STAs 420 are non-AP stations not associated with AP 430. Furthermore, solid lines between stations represent uplinks or downlinks to AP 430, while dashed lines between stations represent direct links between STAs.

[0073] Next-generation WLAN systems need to provide improved support for low-latency applications. It is not uncommon to observe many devices operating on the same network today. Many of these devices may be latency-tolerant, but still compete for the same time and frequency resources as devices running low-latency applications. In some cases, the AP acting as the network controller may not have sufficient control over unregulated or unmanaged traffic that competes with low-latency traffic within the Infrastructure Basic Service Set (BSS). In some embodiments, the Infrastructure BSS is a BSS that includes the AP and one or more non-APs, while a Standalone BSS is a BSS in which stations communicate with each other without requiring a centralized AP. Some unregulated or unmanaged traffic that interferes with latency-sensitive traffic in the AP's BSS may originate from uplink, downlink, or direct link communications within the Infrastructure BSS managed by the AP. Another source of interference may be transmissions from adjacent Infrastructure OBSSs (Overlapping Basic Service Sets), while other sources of interference may come from adjacent Standalone BSSs or P2P networks. Therefore, next-generation WLAN systems need mechanisms to prioritize low-latency traffic in the network while handling unmanaged traffic more effectively. On the other hand, P2P communication devices (or P2P devices) may also suffer from interference caused by the infrastructure BSS. P2P devices may or may not interact with... Figure 4 The infrastructure AP shown is associated with it.

[0074] Figure 5 An example of a P2P link and infrastructure network according to an embodiment is shown.

[0075] refer to Figure 5 AP 1 forms the infrastructure BSS. STA 1 and STA 2 are associated with AP 1, and STA 3 is a peer STA communicating with STA 1 in a P2P link. STA 3 is not associated with AP 1. AP 1 is the infrastructure AP. In this example, STA 3 may suffer interference from the infrastructure BSS.

[0076] When STA 3 suffers interference originating from the infrastructure BSS, it can lead to a degradation in the performance of P2P communication between STA 1 and STA 3. Therefore, AP 1 may need to take measures to reduce interference to STA 3, which can be referred to as a victimized P2P STA or simply a victimized STA. Thus, a mechanism is needed to reduce interference from the infrastructure network to victimized P2P STAs. However, current WLAN systems do not provide such a mechanism.

[0077] Figure 6 Another example of a P2P link and infrastructure network according to an embodiment is shown.

[0078] refer to Figure 6 AP 1 forms the infrastructure BSS. STA 1, STA 2, and STA 3 are associated with AP 1. STA 4 and STA 5 are peer STAs communicating with STA 3. STA 3 is the group owner (GO) of the P2P group. STA 4 and STA 5 are members of the P2P group but are not associated with AP 1. Figure 6 As shown, STA 3 and STA 4 are located inside the BSS, while STA 5 is located just outside or at the edge of the BSS.

[0079] 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, current WLAN systems do not provide such a mechanism. Therefore, a mechanism is needed that enables STA 3 to take action to reduce interference from the infrastructure network.

[0080] This disclosure provides various solutions and embodiments for better coexistence between P2P networks and infrastructure networks, such as, but not limited to, minimizing interference from infrastructure networks to P2P networks.

[0081] Figure 7 An example scenario of a P2P network and an infrastructure network according to an embodiment is shown. Figure 7 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0082] refer to Figure 7AP 1 forms BSS 1 and is associated with STA 1, STA 3, and STA 4. STA 1 has established 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 communication within the infrastructure BSS 1. STA 1 can send a P2P assistance request to AP 1 to minimize the impact of communication within BSS 1 on the P2P link. Figure 7 In the diagram, solid lines between stations represent uplinks or downlinks with AP 1, while dashed lines between stations represent P2P links between STAs.

[0083] In some embodiments, the first STA is associated with the AP and has already established a P2P link with the second STA. When the first STA intends to seek assistance from the AP to protect the P2P communication between the first STA and the second STA, the first STA can send a P2P assistance request frame to the AP indicating that the P2P link needs protection.

[0084] Figure 8 An example P2P assistance is shown according to an embodiment. Figure 8 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0085] Figure 8 The example is based on Figure 7 The scene depicted in the film. (Reference) Figure 8 STA 1 sends 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, such as, but not limited to, including:

[0086] i) AID of STA 1;

[0087] ii) AID of STA 2;

[0088] iii) The MAC address of STA 1;

[0089] iv) MAC address of STA 2;

[0090] v) Interference levels perceived by STA 1 and / or STA 2 due to transmissions from BSS 1;

[0091] vi) The maximum level of interference that the P2P link can tolerate (e.g., the maximum received power from the infrastructure network).

[0092] vii) Whether STA 1 or / and STA 2 are instructions from the victim STA;

[0093] viii) Identification of P2P links;

[0094] ix) The identifier (e.g., AID) of the STA that interferes with the P2P link in BSS 1;

[0095] x) The type of assistance required from BSS 1 for the P2P link. For example, AP 1 i) reduces transmission power (e.g., using spatial reuse processes), or ii) performs beamforming in another direction to mitigate interference to the victim STA; and

[0096] xi) The timeline of P2P link operation. For example, STA 1 shares TWT information, TDLS (Tunneling Direct Link Establishment) peer-to-peer PSM (Power Saving Mode) information, TDLS U-APSD (Unscheduled Automatic Power Saving Delivery) information, or any other power saving mechanism adopted by the victim STA. Based on this shared information, the AP will know when to assist the P2P link, for example, by i) muting transmission, ii) not triggering uplinks for nearby infrastructure STAs, iii) performing spatial reuse to reduce power, or iv) creating an empty beam toward the victim STA.

[0097] Upon receiving a P2P assistance request frame from STA 1, AP 1 sends a P2P assistance response frame to STA 1, indicating how AP 1 intends to assist the P2P communication between STA 1 and STA 2. The P2P assistance response frame may carry information, including, but not limited to, the following:

[0098] i) AP 1 indicates whether to accept or reject the P2P assistance request;

[0099] ii) Instructions for the type of assistance provided by AP 1. For example, i) reducing power level, ii) performing beamforming, or iii) not scheduling transmissions during P2P link operation;

[0100] iii) AID of STA 1;

[0101] iv) AID of STA 2;

[0102] v) MAC address of STA 1;

[0103] vi) MAC address of STA 2;

[0104] vii) Identification of P2P links;

[0105] viii) Recommendations for replacing the timeline of P2P link operations; and

[0106] ix) Alternative suggestions for other P2P parameters used by STA 1 and STA 2. For example, AP 1 may suggest increasing or decreasing the P2P transmission power, which indicates the maximum transmission power that the P2P STA should use.

[0107] Figure 9 An example process 900 for coexistence between a P2P network and an infrastructure network according to an embodiment is illustrated. For purposes of explanation and illustration, process 900 can be described by... Figure 8 The execution of STA 1 is depicted in the figure. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods.

[0108] refer to Figure 9 Process 900 can begin in operation 901. In operation 901, the first STA has established a P2P link with the second STA. The first STA is associated with the infrastructure AP in its BSS, while the second STA is not associated with the infrastructure AP.

[0109] In operation 903, the first STA may experience interference from the infrastructure BSS formed by the AP. The first STA determines that the P2P link requires assistance from the infrastructure AP to protect the P2P link. In some embodiments, assistance may be associated with providing better channel access opportunities or reducing the perceived interference level of the P2P link.

[0110] In operation 905, the first STA sends a P2P assistance request frame to the infrastructure AP. The P2P assistance request frame may include various parameters indicating that assistance is requested from the infrastructure AP.

[0111] In operation 907, the first STA receives a P2P assistance response frame from the infrastructure AP indicating acceptance of the assistance request. The P2P assistance response frame may include various parameters indicating acceptance of the assistance request from the infrastructure AP. In some embodiments, the response may be associated with providing better channel access opportunities or reducing interference levels from the infrastructure BSS.

[0112] In Operation 909, the first STA initiates communication with the second STA via a P2P link using the parameters indicated in the P2P Assist Request Frame or P2P Assist Response Frame.

[0113] Figure 10 Another example process 1000 for coexistence between a P2P network and an infrastructure network according to an embodiment is illustrated. For purposes of explanation and illustration, process 1000 may be described by... Figure 8The execution of AP 1 is depicted in the figure. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods.

[0114] refer to Figure 10 Procedure 1000 can begin in operation 1001. In operation 1001, the 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 the other STA is not associated with the AP. The P2P assistance request frame may be associated with providing better channel access opportunities or reducing the perceived interference level of the P2P link to reduce interference from the infrastructure BSS to the P2P link.

[0115] In Operation 1003, upon receiving a P2P assistance request frame, the AP determines the conditions and criteria used for the assistance request.

[0116] In Operation 1005, the AP assesses the criteria and conditions for the requested assistance. The AP then determines whether to accept the assistance requested from the STA.

[0117] In operation 1007, 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.

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

[0119] Figure 11 Another example of coexistence between a P2P network and an infrastructure network according to an embodiment is shown. Figure 11 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0120] Figure 11 The example is also based on Figure 7 The scene depicted in the film. (Reference) Figure 11 STA 2 is not associated with AP 1, which is related to Figure 8 The example is different. 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.

[0121] In some embodiments, when the STA is the P2P GO of a P2P group, the STA can send a P2P Assistance Request frame to the AP to request assistance in protecting P2P communication within the P2P group. The STA may be associated with the AP. In one embodiment, the STA may not be associated with the AP.

[0122] In some embodiments, the P2P GO may send a P2P group assistance request frame to the infrastructure AP, for example, but not limited to, indicating i) a request for resources (e.g., time, frequency, and channel access opportunities), ii) a request to reduce interference to the P2P group to ensure better P2P communication within the P2P group (e.g., reducing transmission power from the infrastructure BSS to the P2P group), and / or iii) a request to create an empty beam toward the P2P group.

[0123] In some embodiments, the P2P group assistance request frame may include request information, such as, but not limited to, including:

[0124] i) The AID or a subset of the AIDs of the STAs in the P2P group that requires assistance;

[0125] ii) The MAC address or subset of MAC addresses of the STA in the P2P group that requires assistance;

[0126] iii) The level of interference perceived by STAs in the P2P group;

[0127] iv) The maximum level of interference that the P2P link can tolerate (e.g., the maximum received power from the infrastructure network).

[0128] v) A list of subsets of STAs in the P2P group that require assistance;

[0129] vi) Identification of P2P links in a P2P group;

[0130] vii) The identifier (e.g., AID) of the STA in the infrastructure BSS that interferes with the P2P links in the P2P group;

[0131] viii) The type of assistance required by the P2P group from the infrastructure BSS. For example, whether the requesting P2P STA group requires the AP (or any STA associated with the AP) to reduce its transmission power or perform beamforming in another direction to avoid or mitigate interference to the victim STA; and

[0132] ix) A timeline for the operation of the P2P link in P2P. For example, requesting that P2P STAs share TWT information, TDLS peer-to-peer PSM information, TDLS U-APSD information, or any other power-saving mechanism adopted by P2P STAs in 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 uplinks for nearby infrastructure STAs, iii) performing spatial reuse, or iv) creating an empty beam toward the victim STA.

[0133] In some embodiments, upon receiving a P2P group assistance request frame for P2P group assistance from a P2P STA (e.g., P2P GO), the AP may send a P2P group assistance response frame to the P2P STA, indicating how the AP intends to assist P2P communication between P2P STAs in the P2P group. The P2P group assistance response frame may include response information, such as, but not limited to, including:

[0134] i) An instruction from the AP to accept or reject the P2P group assistance request;

[0135] ii) Instructions of an auxiliary type provided by the AP. For example, reducing power level, beamforming, and stopping scheduled transmissions during P2P link operation;

[0136] iii) AID of a subset of STAs within a P2P group that can benefit from the assistance of AP;

[0137] iv) MAC addresses of a subset of STAs within a P2P group that can benefit from the assistance of the AP;

[0138] v) Identifiers of P2P links that provide P2P assistance within a P2P group;

[0139] vi) Replacement recommendations for timelines used in P2P link operations within a P2P group. For example, replacing TWT information or TDLS peering PSM; and

[0140] vii) Alternative suggestions for other P2P parameters used in P2P STAs. For example, i) recommendations for increasing or decreasing the P2P transmission power within a P2P group, iii) indications of the maximum transmission power that a P2P STA should use, or iv) the number of MCSs to be used in a P2P group.

[0141] Figure 12 Another example of coexistence between a P2P network and an infrastructure network according to an embodiment is shown. Figure 12 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0142] refer to Figure 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 via a P2P link established between them. STA 5 and STA 6 are outside of BSS 1. In this scenario, STA 2 can be the P2P GO of the P2P group. When the P2P group experiences interference from BSS 1, STA 2 (the P2P GO) can send a P2P group assistance request frame to AP 1, indicating a request for assistance to protect communication within the P2P group. In response, AP 1 sends a P2P group assistance response to STA 2, indicating acceptance of the request or assistance offered by BSS 1.

[0143] The various embodiments described in this disclosure provide mechanisms for coexistence between P2P networks and infrastructure networks. By coordinating with the infrastructure BSS, P2P networks can reduce interference from the infrastructure BSS. This coordination helps to protect and enhance P2P communication.

[0144] Unless otherwise specified, references to elements in the singular form are not intended to indicate one and only one, but rather one or more. For example, a “one” module can refer to one or more modules. Without further constraints, elements preceded by “a,” “an,” “the,” or “the” do not preclude the presence of additional identical elements.

[0145] Titles and subtitles (if any) are used for convenience only and do not limit the invention. The terms "exemplary" are used to indicate that they are intended as examples or illustrations. Within the scope of the use of terms such as "comprising," "having," etc., such terms are intended to be inclusive in a manner similar to the term "comprising," as "comprising" is interpreted when used as a transitional word in the claims. Relational terms such as "first" and "second" may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0146] Phrases such as aspect, that aspect, on the other hand, some aspects, one or more aspects, implementation, that implementation, another implementation, some implementations, one or more implementations, embodiment, that embodiment, another embodiment, some embodiments, one or more embodiments, configuration, that configuration, another configuration, some configurations, one or more configurations, subject matter, disclosure, this disclosure, other variations thereof, etc., are used for convenience and do not imply that disclosures associated with such phrases are essential to the subject matter, or that such disclosures apply to all configurations of the subject matter. Disclosures associated with such phrases may apply to all configurations or one or more configurations. Disclosures associated with such phrases may provide one or more examples. Phrases such as aspect or some aspects may refer to one or more aspects, and vice versa, and this similarly applies to other foregoing phrases.

[0147] The phrase "at least one" preceding a series of items, separated by the terms "and" or "or," modifies the list as a whole, rather than each member of the list. The phrase "at least one of..." does not require the selection of at least one item; rather, it allows for the inclusion of at least one of any one item, and / or at least one of any combination of items, and / or at least one of each item. For example, each of the phrases "at least one of A, B, and C" or "at least one of A, B, or C" refers to only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.

[0148] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an explanation of exemplary methods. Unless otherwise expressly stated, it should be understood that the specific order or hierarchy of steps, operations, or processes may be performed in a different order. Some steps, operations, or processes may be performed simultaneously, or may be performed as part of one or more other steps, operations, or processes. The appended method claims (if any) present elements of various steps, operations, or processes in a sample order, but this does not imply limitation to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in different orders. It should be understood that the described instructions, operations, and systems can generally be integrated together in a single software / hardware product or packaged into multiple software / hardware products.

[0149] This disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring the concept of the subject matter. This disclosure provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0150] All structural and functional equivalences of the elements of each aspect described throughout this disclosure, whether now known to a person skilled in the art or hereafter known, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be made public, whether or not such disclosure is explicitly stated in the claims. No claim element is to be construed under paragraph 6 of 35 USC §112 unless it is explicitly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “steps for…”.

[0151] The title, background information, description of the drawings, abstract, and figures are incorporated herein by reference and are provided as illustrative examples rather than as limiting descriptions. It should be understood at the time of filing that they are not intended to limit the scope or meaning of the claims. Furthermore, in the detailed description, it will be apparent that the description provides illustrative examples and that various features are combined in various embodiments for the purpose of simplifying the disclosure. The approach of this disclosure should not be construed as reflecting an intention to require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in all features of fewer than those in a single disclosure configuration or operation. The appended claims are incorporated herein by reference, wherein each claim is independently claimed as a separate subject matter.

[0152] The claims are not intended to be limited to the aspects described herein, but rather to conform to the full scope consistent with the language claims and to include all legal equivalents. Nevertheless, no claim is intended to include subject matter that does not meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. A first STA in a wireless network, comprising: Memory; and The processor coupled to the memory is configured to: Establish a peer-to-peer (P2P) link with the second STA; Send the first frame of the request to the access point (AP) to assist in protecting the P2P communication between the first STA and the second STA. Receive a second frame from the AP indicating that the AP can respond to the first frame by providing assistance; as well as Based on the auxiliary communication provided by the AP with the second STA.

2. The first STA according to claim 1, wherein, It is associated with assisting and reducing interference to P2P links from the Basic Service Set (BSS) corresponding to the AP.

3. The first STA according to claim 1 or claim 2, wherein, The auxiliary channel access opportunity is associated with the first STA or the second STA.

4. The first STA according to any one of the preceding claims, wherein, The first STA is associated with the AP, and the second STA is not associated with the AP.

5. The first STA according to any one of the preceding claims, wherein, The first STA is not associated with the AP, while the second STA is associated with the AP.

6. The first STA according to any one of the preceding claims, wherein, The first STA is the owner of the P2P group that includes the first STA and the second STA.

7. The first STA according to any one of the preceding claims, wherein, At least one of the first STA or the second STA is within the BSS.

8. An access point (AP) in a wireless network, comprising: Memory; and The processor coupled to the memory is configured to: The first frame of the request AP to assist in protection is received from the first STA for the first frame of the peer-to-peer P2P communication with the second STA on the P2P link established between the first STA and the second STA. The assistance to be provided to the first STA is determined based on the first frame; as well as Send a second frame to the first STA indicating the assistance that the AP can provide.

9. The AP according to claim 8, wherein, It is associated with assisting and reducing interference to P2P links from the Basic Service Set (BSS) corresponding to the AP.

10. The AP according to claim 8 or claim 9, wherein, The auxiliary channel access opportunity is associated with the first STA or the second STA.

11. The AP according to any one of claims 8 to 10, wherein, The first STA is associated with the AP, and the second STA is not associated with the AP.

12. The AP according to any one of claims 8 to 11, wherein, The first STA is not associated with the AP, while the second STA is associated with the AP.

13. The AP according to any one of claims 8 to 12, wherein, The first STA is the owner of the P2P group that includes the first STA and the second STA.

14. The AP according to any one of claims 8 to 13, wherein, At least one of the first STA or the second STA is within the BSS.

15. A method performed by a first STA in a wireless network, comprising: Establish a peer-to-peer (P2P) link with the second STA; Send the first frame of the request to the access point (AP) to assist in protecting the P2P communication between the first STA and the second STA. Receive a second frame from the AP indicating that the AP can respond to the first frame by providing assistance; as well as Based on the auxiliary communication provided by the AP with the second STA.

Images