Map coordination for channel resource announcement for peer-to-peer communications

Abstract

A first access point (AP) device in a wireless network, the first STA device comprising a memory and a processor coupled to the memory, the processor configured to send, to a second AP, a first frame requesting multi-AP coordination (MAP) for peer-to-peer (P2P) communications between a plurality of stations (STAs) and including information for resource allocation for the coordinating STAs for the P2P communications, receive, from the second AP, a second frame in response to the first frame, and advertise, to one or more STAs associated with the first AP, information about the resource allocation for the P2P communications.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to multi-access point (MAP) coordination, such as, but not limited to, channel resource announcements for peer-to-peer (P2P) communication. Background Technology

[0002] Since the late 1990s, Wireless Local Area Network (WLAN) technology has evolved towards higher data rates and has seen continuous growth 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 these 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. Each WLAN device can have one or more stations (STAs), such as access point (AP) STAs and non-access point (non-AP) STAs.

[0004] Multi-Link Optimization (MLO) enables non-AP multi-link devices (MLDs) to establish multiple links with AP MLDs. Each of these links can independently enable channel access and frame switching 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 construed as 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] Technical issues

[0007] One aspect of this disclosure provides a first access point (AP) in a wireless network, the first AP including: a memory; and a processor coupled to the memory. The processor is configured to send a first frame to a second AP, the first frame requesting a multi-AP coordination map (MAP) for peer-to-peer (P2P) communication among multiple station (STA) locations, and including information for coordinating resource allocation for P2P communication among one or more STAs. The processor is configured to receive a second frame from the second AP in response to the first frame. The processor is configured to notify one or more STAs associated with the first AP of the resource allocation information for P2P communication.

[0008] In some examples, the information included in the first frame includes one or more channels or one or more time periods for P2P communication.

[0009] In some examples, the second frame accepts a request for MAP coordination.

[0010] In some examples, the second frame provides a set of alternative channels or time periods for P2P communication between the plurality of STAs, wherein the processor is further configured to: send a third frame to the second AP, the third frame requesting MAP coordination and including a set of alternative channels or time periods for P2P communication between the plurality of STAs; receive a fourth frame from the second AP, the fourth frame accepting the request through the third frame; and announce the set of alternative channels or time periods for P2P communication to one or more STAs associated with the first AP.

[0011] In some examples, the plurality of STAs are associated with the first AP and are located in the first basic service set (BSS).

[0012] In some examples, a first STA among the plurality of STAs is associated with the first AP, and a second STA among the plurality of STAs is associated with the second AP, such that the first STA and the second STA are in different Basic Service Sets (BSS).

[0013] In some examples, the first frame includes information for coordination based on Target Wake-up Time (TWT), Time Division Multiple Access (TDMA), Spatial Reuse-based Mapping (MAP), or channel announcement for P2P communication.

[0014] In some examples, the announced information is announced in a beacon frame or probe response frame.

[0015] One aspect of this disclosure provides a first access point (AP) in a wireless network. The first AP includes a memory and a processor coupled to the memory. The processor is configured to: receive a first frame from a second AP, the first frame requesting a multi-AP coordination map (MAP) for peer-to-peer (P2P) communication among multiple station (STA) locations, and including information for coordinating resource allocation for P2P communication among one or more STAs. The processor is configured to send a second frame to the second AP in response to the first frame. The processor is also configured to notify one or more STAs associated with the first AP of the resource allocation information for P2P communication.

[0016] In some examples, the information included in the first frame includes one or more channels or one or more time periods for P2P communication.

[0017] In some examples, the second frame accepts a request for MAP coordination.

[0018] In some examples, the second frame provides a set of alternative channels and time periods for P2P communication between the plurality of STAs, wherein the processor is further configured to: receive a third frame from the second AP, the third frame requesting MAP coordination and including a set of alternative channels or time periods for P2P communication between the plurality of STAs; send a fourth frame to the second AP, the fourth frame accepting the request through the third frame; and announce the set of alternative channels or time periods for P2P communication to one or more STAs associated with the first AP.

[0019] In some examples, the plurality of STAs are associated with the first AP and are located in the first basic service set (BSS).

[0020] In some examples, a first STA among the plurality of STAs is associated with the first AP, and a second STA among the plurality of STAs is associated with the second AP, such that the first STA and the second STA are in different Basic Service Sets (BSS).

[0021] In some examples, the first frame includes information for coordination based on target wake-up time (TWT), coordination based on time division multiple access (TDMA), MAP coordination based on spatial reuse, or coordination for channel announcements for P2P communication.

[0022] In some examples, the announced information is announced in a beacon frame or probe response frame.

[0023] One aspect of this disclosure provides a computer-implemented method for multi-AP coordination (MAP) of peer-to-peer (P2P) communication at a first access point (AP) in a wireless network. The method includes sending a first frame to a second AP requesting MAP coordination for P2P communication among multiple stations (STAs) and including information for coordinating resource allocation for P2P communication among one or more STAs. The method includes receiving a second frame from the second AP in response to the first frame. The method also includes notifying one or more STAs associated with the first AP of the information regarding resource allocation for P2P communication.

[0024] In some examples, the information included in the first frame includes one or more channels or one or more time periods used for P2P communication.

[0025] In some examples, the second frame accepts a request for MAP coordination.

[0026] In some examples, the second frame provides a set of alternative channels or time periods for P2P communication between the multiple STAs, and the method further includes sending a third frame to the second AP, the third frame requesting MAP coordination and including a set of alternative channels or time periods for P2P communication between the multiple STAs, receiving a fourth frame from the second AP, the fourth frame accepting the request through the third frame, and announcing the set of alternative channels or time periods for P2P communication to one or more STAs associated with the first AP. Attached Figure Description

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

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

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

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

[0031] Figure 4 A network with different types of traffic is shown according to an embodiment.

[0032] Figure 5 A MAP coordination for channel announcements for P2P communication according to an embodiment is shown.

[0033] Figure 6 A MAP coordination for channel announcements for P2P communication according to an embodiment is shown.

[0034] Figure 7 A MAP coordination for channel resource guidance for P2P communication is illustrated according to an embodiment.

[0035] Figure 8 The P2P channel and time period negotiation and announcement are illustrated according to an embodiment.

[0036] Figure 9 A flowchart illustrating an example process for initiating MAP coordination for P2P communication via an AP, according to an embodiment, is shown.

[0037] Figure 10 A flowchart illustrating an example process for MAP coordination of P2P communication via a receiving AP, according to an embodiment, is shown.

[0038] In one or more implementations, not all components depicted in each figure may be required, and one or more implementations may include additional components not shown in the figures. The arrangement and type of components may vary without departing from the scope of this subject matter disclosure. Within the scope of this subject matter disclosure, additional components, different components, or fewer components may be used. Detailed Implementation

[0039] The specific embodiments given below, in conjunction with the accompanying drawings, are intended to describe various implementations and not to represent the only implementations in which the subject matter can be practiced. Rather, the specific embodiments include detailed descriptions to provide a thorough understanding of the subject matter of the invention. As those skilled in the art will recognize, the described implementations can be modified in various ways without departing from the scope of this disclosure. Therefore, the drawings and descriptions are to be considered illustrative in nature and not restrictive. Similar reference numerals denote similar elements.

[0040] For the purpose of describing the innovative aspects of this disclosure, the following description is directed to certain implementations. 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 in accordance with 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 (such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof) 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 Version A, EV-DO Version 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 communication within wireless, cellular, or Internet of Things (IoT) networks.

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

[0042] Multilink Operation (MLO) is a key feature currently being developed by the standards organization IEEE 802.11be for next-generation Ultra High Throughput (EHT) Wi-Fi systems. 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 are possible on each link between the AP MLD and non-AP MLDs.

[0043] 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.

[0044] 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, which is a separately addressable instance of the Media Access Control (MAC) layer and Physical (PHY) layer interface to 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 associated STAs via the wireless media. A Non-AP STA may be a STA that is not included in 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, and each wireless communication device may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP multilink devices (MLDs). Similarly, STAs 111-114 are wireless communication devices, and each wireless communication device may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

[0045] 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 (STAs) 111-114 in the coverage area 120 of AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

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

[0047] exist Figure 1 In the diagram, the dashed lines show 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.

[0048] As described in more detail below, one or more of the APs may include circuitry and / or programs for managing MU-MIMO and OFDMA channel probing in the 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 them 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.

[0049] 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 to any particular implementation of AP.

[0050] like Figure 2a As shown, AP 101 may include multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-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-209n receive incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in network 100. RF transceivers 209a-209n down-convert the incoming RF signals to generate intermediate frequency (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.

[0051] TX processing circuit 214 receives analog or digital data (such as voice data, web 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-209n receive the 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-204n.

[0052] 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 RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 to receive uplink signals and transmit downlink signals, based on known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a-204n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subsets of subcarriers from different receivers (e.g., different STAs 111-114). In the AP 101, the controller / processor 224 may support any of a variety of other functions, including a combination of DLMU-MIMO and OFDMA in the same transmission opportunity. In some embodiments, controller / processor 224 may include at least one microprocessor or microcontroller. Controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in memory 229. Controller / processor 224 may move data into or out of memory 229 as needed for the execution process.

[0053] 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 via a wired or wireless local area network or via a wired or wireless connection to a larger network, such as the Internet. Interface 234 can include any suitable structure that supports 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 can include RAM, while another portion of memory 229 can include flash memory or other ROM.

[0054] As described in more detail below, AP 101 may include circuitry and / or programming 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 is 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 component (such as one instance per RF transceiver). Alternatively, as in a conventional AP, it may include only one antenna and one RF transceiver path. Furthermore, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

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

[0056] 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-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.

[0057] 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.

[0058] 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 an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 225 sends the processed baseband signal to speaker 230 (e.g., for voice data) or controller / processor 240 for further processing (e.g., for web browsing data).

[0059] TX processing circuit 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 circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the processed baseband or IF signal from TX processing circuit 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0060] 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 known principles. The controller / processor 240 may also include processing circuitry configured to provide management of channel detection processes in a WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0061] 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, which include feedback calculations based on received null data packet announcements (NDPA) and null data packets (NDP), and sending beamforming feedback reports in response to trigger frames (TF). The controller / processor 240 can operate the 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 laptop computers and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0062] The controller / processor 240 is also connected to input 250 (such as a touchscreen) and display 255. The 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 (such as from a website) and / or at least limited graphics. Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), while another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0063] 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.

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

[0065] 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, rather than AP MLD 220, can be Figure 1 One of the wireless communication devices 111-114 in the series.

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

[0067] 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 (Link 1, Link 2, or Link 3) to the wireless media. The non-AP MLD 320 may include a single MAC SAP 328, through which the affiliated STAs communicate with higher layers (Layer 3 or the network layer). Each affiliated STA of the non-AP MLD 320 may have a MAC address (lower-layer MAC address) different from any other affiliated STA of the non-AP MLD 320. The non-AP MLD 320 may have an MLD MAC address (upper-layer MAC address), and the affiliated STAs share the single MAC SAP 328 to Layer 3. Therefore, the affiliated STAs share a single IP address, and Layer 3 identifies the non-AP MLD 320 by assigning this single IP address.

[0068] Multiple links can be established between AP MLD 310 and non-AP MLD 320 devices and 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 switching between AP MLD 310 and non-AP MLD 320 devices, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (established links), each non-AP device is assigned a unique Association Identifier (AID).

[0069] The following documents are incorporated herein by reference in their entirety, 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.0, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications”.

[0070] Next-generation WLAN systems can benefit from better support for low-latency applications. Specifically, it is not uncommon for numerous devices to operate on the same network, with different devices having different latency requirements. Many of these devices can tolerate latency but may still compete for the same time and frequency resources with devices having low-latency applications. In some cases, the access point (AP), acting as the network controller, may not be able to adequately control unregulated / unmanaged traffic competing with low-latency traffic within the Infrastructure Basic Services Set (BSS). Some unmanaged traffic interfering with the AP's latency-sensitive traffic on its BSS may originate from uplink (UL) / downlink (DL) or direct link communications within the infrastructure BSS managed by the AP. Other interference may arise from transmissions in adjacent infrastructure BSSs (OBSSs). Further interference may originate from adjacent independent BSSs or P2P networks.

[0071] Figure 4 A network with different types of traffic according to an embodiment is shown. Specifically, Figure 4 The diagram illustrates a network with AP405 and multiple STAs, some of which (e.g., STA 401) are associated with the AP, as shown in the legend. Some STAs, such as STA 403, are not associated with the AP. Furthermore, as shown in the legend, STAs associated with the AP can have UL / DL links to the AP, as indicated by solid lines connecting the STA and the AP. Some STAs can be directly linked to other STAs, as shown by dashed lines.

[0072] The WLAN system according to this disclosure may include various mechanisms designed to better handle unmanaged traffic in order to prioritize low-latency traffic in the network.

[0073] In some embodiments, a STA may receive instructions from its associated AP regarding which channels it should operate its P2P communication on. However, interference from the OBSS may exist, potentially disrupting P2P communication between two peer STAs. Such interference may need to be addressed so that the peer STAs can meet their QoS requirements for P2P communication.

[0074] In some embodiments, the first AP may coordinate with the second AP to determine a common set of time periods that can be used by peer STAs for their P2P communication. For example, this could be a set of time periods that P2P STAs in two BSSs operated by these two APs can use. This set of time periods can be considered more favorable for P2P communication. For example, both APs may reduce infrastructure BSS activity during these time periods. In some embodiments, multi-AP (MAP) coordination for channel advertising may be used for P2P communication to reduce interference from the OBSS.

[0075] Figure 5 A MAP coordination for channel announcement in P2P communication according to an embodiment is illustrated. Specifically, Figure 5 The diagram illustrates a first BSS (Best Support Shield) BSS 1 managed by a first AP (AP1) and a second BSS (Best Support Shield) BSS 2 managed by a second AP (AP2). AP1 is associated with STA3 and has an infrastructure connection to STA3, and AP2 is associated with STA4 and has an infrastructure connection to STA4. Furthermore, STA1 and STA2 are P2P STAs and are associated with the same AP (AP1). STA1 and STA2 can follow the channel / transmission window recommended by AP1 for their P2P communication in BSS1. However, this P2P link may be subject to interference from BSS (Best Support Shield) BSS 2. As shown in the diagram, interference may exist between BSS1 and BSS2, as indicated by the overlapping circles of the overlapping range of the illustrated wireless network. Therefore, AP1 may request BSS (Best Support Shield) AP2 to restrict its transmission to the specific channel designated by AP1 for P2P communication. In some embodiments, MAP coordination for channel announcement can be used for P2P communication between two peer STAs associated with two different APs.

[0076] Figure 6 A MAP coordination method for channel announcements for P2P communication between two peer STAs, according to an embodiment, is illustrated, where the peer STAs are associated with two different APs. As shown, a first AP, AP1, is associated with STA1, and a second AP, AP2, is associated with STA2. Furthermore, STA1 and STA2 can be P2P STAs. Therefore, when associated with two different APs, it can be helpful to manage infrastructure and P2P communication by providing announcements from the APs to the STAs, where such announcements can provide some guidance on channel and time usage in the P2P network. Thus, both AP1 and AP2 may need to allocate a public channel dedicated to P2P communication.

[0077] Figure 7 A MAP coordination for channel resource guidance in P2P is illustrated according to an embodiment. For example... Figure 7 As shown, the first AP (AP1) can manage the first BSS (Broadcast Security System), BSS 1, and the second AP (AP2) can manage the second BSS (Broadcast Security System), BSS 2. BSS1 includes STA1, which is associated with AP1 and has an infrastructure connection to AP1. BSS2 includes STA4, which is associated with AP2 and has an infrastructure connection to AP2. Furthermore, STA1 and STA2 can be P2P STAs. Figure 7 In this process, AP1 and AP2 can coordinate (e.g., exchange frames) to determine a common set of channels and / or time periods that can be used for P2P communication in these two BSSs.

[0078] In some embodiments, a first AP may send a P2P channel negotiation request frame to a second AP. This request frame may include one or more channels and / or time periods preferred by the first AP for P2P communication between P2P STAs. Upon receiving the request frame, the second AP may send a P2P channel negotiation response frame to the first AP. This response frame may accept the request or suggest a set of alternative channels and / or time periods for P2P communication between P2P STAs. Specifically, the second AP may send a response frame without accepting the request, and the first AP may send another request frame, which may include the parameters suggested in the response frame. The second AP may then send a second response frame accepting the request for the set of alternatives with parameters. When the first AP receives the second response frame, both the first and second APs may announce the agreed-upon channels and time periods. In some embodiments, the announcement of channels and time periods may be made in the corresponding beacon frames or probe response frames of the APs. Furthermore, channel information can provide indications that these channel resources may be more favorable for P2P communication between P2P STAs.

[0079] In some embodiments, the channel negotiation request frame and the channel negotiation request response frame may include a channel usage element and a TWT element to indicate favorable channel and time period scheduling for P2P communication.

[0080] Figure 8 The diagram illustrates P2P channel and time period negotiation and announcement according to an embodiment. As shown, AP1 can send a P2P channel negotiation request frame 801 to AP2. AP2 can send a channel negotiation response frame 803 to AP1. AP2 can send a beacon frame 805, which can announce the channel and / or time period agreed upon between AP1 and AP2. Similarly, AP1 can send a beacon frame 807, which can announce the channel and / or time period agreed upon with AP2. Therefore, during the TWT 809 of P2P, a set of channels can be utilized, including P2P Ch3, P2P CH2, and P2P Ch1, as shown.

[0081] Table 1 below provides possible formats for P2P channel negotiation request frames according to an embodiment.

[0082] [Table 1]

[0083]

[0084] As shown in Table 1, the category field provides information about the frame's category. The unprotected S1G protected action field can distinguish the format of unprotected S1G action frames. The session token field identifies the request.

[0085] The Multiple Access Point (MAP) Coordination Mode field indicates the type of MAP coordination expected for the request frame. For example, this field can indicate whether the MAP coordination is for TWT-based coordination, TDMA-based coordination, space reuse-based MAP coordination, or channel announcement coordination for P2P communication.

[0086] The MAP capability information field may include information related to its various capability characteristics in relation to MAP coordination, and this information may be shared with the receiver of the frame.

[0087] The Wireless Network Management (WNM) Action field can include information for managing the network and can be used to indicate different action values. The Channel Usage element field can provide usage information for one or more channels. The Supported Operation Category element field can provide operation category information. The Target Wake-Up Time (TWT) element field can include information for establishing and managing TWT agreements. The Timeout Interval element field can include information about the timeout interval. The High Throughput (HT) Capability element field can provide information about the STA's HT capabilities. The Very High Throughput (VHT) Capability element field can provide information about the STA's VHT capabilities. The High Efficiency (HE) Capability element field can provide information about the STA's HE capabilities. The High Efficiency (HE) 6 GHz Capability element field can provide information about the STA's HE 6 GHz capabilities.

[0088] Table 2 below provides possible formats for P2P channel negotiation response frames according to an embodiment.

[0089] [Table 2]

[0090]

[0091] In Table 2, the Category field provides frame category information. The Unprotected S1G Protected Action field distinguishes the format of unprotected S1G action frames. The Session Token field identifies the request. The Multi-AP (MAP) C-OCP Coordination Mode field indicates the type of MAP coordination expected for the response frame. For example, this field can indicate whether the MAP coordination is for TWT-based coordination, TDMA-based coordination, space reuse-based MAP coordination, or channel announcement coordination for P2P communication.

[0092] The MAP capability information field may include information related to different capability characteristics involved in MAP coordination and may be shared with the receiver of the frame.

[0093] The Wireless Network Management (WNM) Action field can include information for managing the network and can be used to indicate different action values. The Channel Usage element field can provide usage information for one or more channels. The Supported Operation Category element field can provide operation category information. The Target Wake-Up Time (TWT) element field can include information for establishing and managing TWT agreements. The Timeout Interval element field can include information about the timeout interval. The High Throughput (HT) Capability element field can provide information about the STA's HT capabilities. The Very High Throughput (VHT) Capability element field can provide information about the STA's VHT capabilities. The High Efficiency (HE) Capability element field can provide information about the STA's HE capabilities. The High Efficiency (HE) 6 GHz Capability element field can provide information about the STA's HE 6 GHz capabilities.

[0094] The status code field can include the result of responding to a request frame received from another AP. If the status code is set to the value ACCEPT, it indicates that the AP sending the response frame has accepted the channel announcement parameters from the other AP. If the status code is set to the value REJECT, it indicates that the AP sending the response frame has rejected the channel announcement parameters from the other AP. If the status code is set to the value ALTERNATE, it indicates that the AP sending the response frame suggests an alternative set of parameters for MAP coordination with the AP sending the request frame.

[0095] Figure 9 A flowchart illustrating an example process for initiating AP-based MAP coordination of P2P communication according to an embodiment is shown. 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. Figure 9 The flowchart shown illustrates the process in AP (e.g.) Figure 7 The operations performed in the AP shown.

[0096] In process 900, during operation 901, the first AP sends a channel negotiation request frame to the second AP. In some embodiments, the channel negotiation request frame may provide one or more parameters for P2P communication between peer STAs. In some embodiments, peer STAs may be associated with the same AP. In some embodiments, peer STAs may be associated with different APs. These parameters may include one or more channels that the peer STA can use for communication. In some embodiments, the parameters may include one or more time periods during which the peer STA can communicate.

[0097] In operation 903, the first AP receives a channel negotiation response frame from the second AP. In some embodiments, the channel negotiation response frame may accept a request, reject a request, or suggest an alternative set of parameters for P2P communication. In some embodiments, the channel negotiation request frame and the channel negotiation response frame may include channel usage elements and TWT elements to indicate beneficial channel and / or time period scheduling for P2P communication.

[0098] In operation 905, the first AP determines whether the second AP accepts the parameters specified in the request. If the second AP accepts in operation 905, the process proceeds to operation 907, in which the first AP announces the parameters agreed upon with the second AP for P2P communication. In some embodiments, the first AP may announce the parameters, including the agreed channel and / or time period, in a beacon frame or probe response frame.

[0099] In operation 905, if the second AP does not accept the request, the process proceeds to operation 909, in which the first AP determines whether the second AP provides an alternative set of parameters.

[0100] If, in operation 909, the first AP determines that the second AP has provided a candidate set of parameters, the procedure returns to operation 901 to continue negotiation. Specifically, if the response frame includes a candidate set of parameters, and the first AP agrees to these candidate parameters, the first AP may send another channel negotiation request frame to the second AP, including the candidate set of parameters.

[0101] If, in operation 909, the second AP does not provide an alternative set of parameters and instead rejects the request, then in operation 911, the first AP does not take any action.

[0102] Figure 10 A flowchart illustrating an example process for MAP coordination of P2P communication by a receiving AP according to an embodiment is shown. 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. Figure 9 The flowchart shown illustrates the process in AP (e.g.) Figure 7 The operations performed in the AP shown.

[0103] In process 1000, during operation 1001, the first AP receives a channel negotiation request frame from the second AP. In some embodiments, the channel negotiation request frame may provide one or more parameters for P2P communication between peer STAs. The parameters may include one or more channels that the peer STAs can use for communication. In some embodiments, the parameters may include one or more time periods during which the peer STAs can communicate.

[0104] In operation 1003, the first AP determines whether it accepts the parameters in the request frame. If the first AP accepts the parameters in operation 1003, the process proceeds to operation 1005, in which the first AP sends a channel negotiation response frame accepting the request to the second AP. In some embodiments, the channel negotiation request frame and the channel negotiation response frame may include a channel usage element and a TWT element to indicate favorable channel and / or time period scheduling for P2P communication.

[0105] In operation 1007, the first AP announces the parameters agreed upon with the second AP for P2P communication. In some embodiments, the first AP may announce the parameters, including the agreed channel and / or time period, in a beacon frame or probe response frame.

[0106] If the first AP does not accept the parameters in operation 1003, the process proceeds to operation 1009, in which the first AP determines whether it wants to provide an alternative set of parameters for P2P communication. If the first AP determines in operation 1009 that it wants to provide an alternative set of parameters, the process proceeds to operation 1013, in which the first AP sends a channel negotiation response frame including the alternative set of parameters to the second AP, and the process returns to operation 1001.

[0107] If, in operation 1009, the first AP determines that it does not want to provide the alternative set of parameters (i.e., the first AP rejects the request), the process proceeds to operation 1011, in which the first AP sends a channel negotiation response frame rejecting the request.

[0108] Unless otherwise specified, an element mentioned in the singular does not mean one and only one, but one or more. For example, a “one” module can refer to one or more modules. Without further restriction, an element beginning with “a,” “an,” “the,” or “the” does not exclude the existence of other identical elements.

[0109] Titles and subtitles (if any) are for convenience only and do not limit the invention. The word “exemplary” is used to indicate that it is an example or illustration. With regard to the use of terms such as “comprising,” “having,” etc., such terms are intended to encompass in a manner similar to how the term “comprising” is interpreted when used as a transitional word in a claim. Relational terms such as “first” and “second” can be used to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0110] Phrases such as "one aspect," "this aspect," "on the other hand," "some aspects," "one or more aspects," "an implementation," "this implementation," "another implementation," "some implementations," "one or more implementations," "an embodiment," "this embodiment," "another embodiment," "some embodiments," "one or more embodiments," "a configuration," "this configuration," "another configuration," "some configurations," "one or more configurations," "the subject matter," "disclosure," "this disclosure," and other variations thereof are used for convenience and do not imply that the disclosures associated with these phrases are necessary to the subject matter, nor do they imply that these disclosures are applicable to all configurations of the subject matter. The disclosures associated with these phrases can be applied to all configurations, or one or more configurations. The disclosures associated with these phrases can provide one or more examples. Phrases such as "one aspect" or "some aspects" can refer to one or more aspects, and vice versa, and this also applies to other foregoing phrases.

[0111] The phrase “at least one of” following a series of items, along with the terms “and” or “or” separating any items, modifies the entire list, not 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 any one of at least one items, and / or any combination of at least one items, and / or the meaning of each of at least one items. 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 A, B, and C.

[0112] As described herein, any electronic device and / or portion thereof according to any example embodiment may include, be included in, or be implemented by one or more processors and / or processor combinations. A processor is a circuit that performs processing.

[0113] The processor may include processing circuitry, which may more specifically include, but is not limited to, a central processing unit (CPU), an MPU, a system-on-a-chip (SoC), an integrated circuit (IC), an arithmetic logic unit (ALU), a graphics processing unit (GPU), an application processor (AP), a digital signal processor (DSP), a microcomputer, a field-programmable gate array (FPGA) and programmable logic unit, a microprocessor, an application-specific integrated circuit (ASIC), a neural network processing unit (NPU), an electronic control unit (ECU), an image signal processor (ISP), etc. In some example embodiments, the processing circuitry may include: a non-transitory computer-readable storage device (e.g., memory), such as a DRAM device, storing a program of instructions; and a processor (e.g., a CPU) configured to execute the program of instructions to implement the functions and / or methods performed by all or some of any device, system, module, unit, controller, circuit, architecture, and / or portions thereof according to any example embodiment and / or any part of any example embodiment. Instructions may be stored in memory and / or partitioned among multiple memories.

[0114] Different processors can perform different functions and / or parts of functions. For example, processor 1 can perform functions A and B, while processor 2 can perform function C; or processor 1 can perform a portion of function A, while processor 2 can perform the remainder of function A and perform functions B and C. Different processors can be dynamically configured to perform different processes. For example, at one time, processor 1 can perform function A, while at another time, processor 2 can perform function A. Processors can reside on different processing circuits (e.g., client-side processors and server-side processors, device-side processors and cloud computing processors, etc.).

[0115] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration of exemplary methods. Unless explicitly stated otherwise, 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 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 an exemplary order and are not intended to limit one to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in a different order. It should be understood that the described instructions, operations, and systems may generally be integrated together in a single software / hardware product or packaged into multiple software / hardware products.

[0116] This disclosure is intended to enable any person skilled in the art to practice the aspects described herein. In some instances, to avoid obscuring the concepts of the subject matter, well-known structures and components are shown in block diagram form. 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 readily apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0117] All structural and functional equivalents of the elements of the aspects described in this disclosure that are known or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. No element expressly recited in the claims is subject to the provisions of paragraph 6 of 35 USC § 112 unless the element is expressly expressed as “means for…” or, in the case of a method claim, as “steps for…”.

[0118] The title, background art, description of the drawings, abstract, and figures are incorporated herein by reference as illustrative examples, not 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 illustrative examples are provided, and various features are combined in various implementations to simplify the disclosure. This approach to disclosure should not be construed as reflecting an intention that the claimed subject matter requires more features than expressly stated in each claim. Rather, as reflected in the appended claims, the inventive subject matter lies in all features of fewer than those in a single disclosed configuration or operation. The appended claims are thus incorporated into the detailed description, each claim itself as a separately claimed subject matter.

[0119] 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 fails to meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. A first access point (AP) in a wireless network, the first AP comprising: Memory; A processor coupled to the memory, the processor being configured to: Send a first frame to the second AP, the first frame requesting a multi-AP coordination MAP for peer-to-peer P2P communication between multiple STAs, and including information for coordinating resource allocation for one or more STAs for P2P communication; Receive a second frame in response to the first frame from the second AP; and Announce information about resource allocation for P2P communication to one or more STAs associated with the first AP.

2. The first AP according to claim 1, wherein, The information included in the first frame includes one or more channels or one or more time periods for P2P communication.

3. The first AP according to claim 1 or 2, wherein, The second frame accepts the MAP coordination request.

4. The first AP according to any one of the preceding claims, wherein, The second frame provides a set of alternative channels or time periods for P2P communication between the plurality of STAs, wherein the processor is further configured to: A third frame is sent to the second AP, the third frame requesting MAP coordination and including a candidate set of channels or time periods for P2P communication between the plurality of STAs; Receive a fourth frame from the second AP, the fourth frame accepting the request through the third frame; and The alternative set of channels or time periods for P2P communication is announced to the one or more STAs associated with the first AP.

5. The first AP according to any one of the preceding claims, wherein, The plurality of STAs are associated with the first AP and are located in the first basic service set (BSS).

6. The first AP according to any one of the preceding claims, wherein, The first STA of the plurality of STAs is associated with the first AP, and the second STA of the plurality of STAs is associated with the second AP, such that the first STA and the second STA are in different Basic Service Sets (BSS).

7. The first AP according to any one of the preceding claims, wherein, The first frame includes information for coordination based on target wake-up time (TWT), coordination based on time division multiple access (TDMA), coordination based on spatial reuse (MAP), or coordination for channel announcements for P2P communication.

8. The first AP according to any one of the preceding claims, wherein, The announced information is announced in beacon frames or probe response frames.

9. A first access point (AP) in a wireless network, the first AP comprising: Memory; A processor coupled to the memory, the processor being configured to: Receive a first frame from the second AP. The first frame requests a multi-AP coordination MAP for peer-to-peer P2P communication between multiple STAs and includes information for coordinating resource allocation for one or more STAs for P2P communication. Send a second frame in response to the first frame to the second AP; and Announce information about resource allocation for P2P communication to one or more STAs associated with the first AP.

10. The first AP according to claim 9, wherein, The information included in the first frame includes one or more channels or one or more time periods for P2P communication.

11. The first AP according to claim 9 or claim 10, wherein, The second frame provides a set of alternative channels and time periods for P2P communication between the plurality of STAs, wherein the processor is further configured to: A third frame is received from the second AP, the third frame requesting MAP coordination and including a candidate set of channels or time periods for P2P communication between the plurality of STAs; Send a fourth frame to the second AP, the fourth frame accepting the request through the third frame; and The alternative set of channels or time periods for P2P communication is announced to the one or more STAs associated with the first AP.

12. The first AP according to any one of claims 9 to 11, wherein, The plurality of STAs are associated with the first AP and are located in the first basic service set (BSS).

13. The first AP according to any one of claims 9 to 12, wherein, The first STA of the plurality of STAs is associated with the first AP, and the second STA of the plurality of STAs is associated with the second AP, such that the first STA and the second STA are in different Basic Service Sets (BSS).

14. The first AP according to any one of claims 9 to 13, wherein, The first frame includes information for coordination based on Target Wake-up Time (TWT), coordination based on Time Division Multiple Access (TDMA), MAP coordination based on spatial reuse, or coordination for channel announcements for P2P communication.

15. The first AP according to any one of claims 9 to 14, wherein, The announced information is announced in beacon frames or probe response frames.

Images