Peer-to-peer resource management

Abstract

A station (STA) in a wireless network includes a memory and a processor coupled to the memory, the processor configured to send a request frame to an access point (AP), the request frame requesting resources for a P2P group to which the STA belongs from the AP; receive a trigger frame from the AP allocating a transmission opportunity (TXOP); and send one or more frames to peer STAs in the P2P group within the TXOP.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication systems, and more particularly to peer-to-peer (P2P) resource management in wireless networks, 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 is designed 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 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 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] Solution to the problem

[0007] One aspect of this disclosure provides a station (STA) in a wireless network, including a memory; and a processor coupled to the memory. The processor is configured to send a request frame to an access point (AP) requesting resources from the AP for a peer-to-peer (P2P) group to which the STA belongs. The processor is configured to receive a trigger frame for allocating a transmission opportunity (TXOP) from the AP. The processor is configured to send one or more frames within the TXOP to peer STAs in the P2P group.

[0008] In some embodiments, the processor is also configured to send a frame to the peer STA that reallocates a portion of the TXOP.

[0009] In some embodiments, the processor is further configured to receive from the AP a response frame in response to a request frame, the response frame including an indication of acceptance, rejection, or substitution of the request in the request frame.

[0010] In some embodiments, the response frame includes a Quality of Service (QoS) characteristic element, which includes a substitution for the request in the request frame.

[0011] In some embodiments, the request frame includes a P2P group identifier or a stream identifier that identifies the P2P group, wherein the stream identifier is a stream classification service identifier or a target wake-up time (TWT) stream identifier.

[0012] In some embodiments, the request frame includes a Quality of Service (QoS) characteristic element, which includes information associated with the service requirements of the P2P group.

[0013] In some embodiments, the request frame includes information about one or more peer STAs in a P2P group that are requesting resources for it.

[0014] One aspect of this disclosure provides an access point (AP) in a wireless network, including a memory; and a processor coupled to the memory. The processor is configured to receive a request frame from a station (STA) requesting resources from the AP for a P2P group to which the STA belongs. The processor is configured to send a trigger frame to the STA to allocate a transmission opportunity (TXOP) to the P2P group.

[0015] In some embodiments, the processor is further configured to send a response frame to the STA in response to the request frame, the response frame including an indication of acceptance, rejection, or substitution of the request in the request frame.

[0016] In some embodiments, the response frame includes a Quality of Service (QoS) characteristic element, which includes a substitution for the request in the request frame.

[0017] In some embodiments, the request frame includes a P2P group identifier or a stream identifier that identifies the P2P group, wherein the stream identifier is a stream classification service identifier or a target wake-up time (TWT) stream identifier.

[0018] In some embodiments, the request frame includes a Quality of Service (QoS) characteristic element, which includes information associated with the service requirements of the P2P group.

[0019] In some embodiments, the request frame includes information about one or more peer STAs in a P2P group that are requesting resources for it. Attached Figure Description

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

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

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

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

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

[0025] Figure 5 P2P communication between STAs in a P2P group according to an embodiment is illustrated.

[0026] Figure 6 P2P communication between STAs in a P2P group established according to an embodiment is illustrated.

[0027] Figure 7 The example illustrates the initiation of a new P2P TWT group by a STA according to an embodiment.

[0028] Figure 8 Group-based triggering for P2P communication is illustrated according to an embodiment.

[0029] Figure 9a An example of a QoS feature element according to an embodiment is shown.

[0030] Figure 9b An example of a control information field within a QoS feature element according to an embodiment is shown.

[0031] Figure 10 A flowchart illustrating an example process of an STA requesting resources for a P2P group according to an embodiment is shown.

[0032] Figure 11 A flowchart illustrating an example process of allocating resources from an AP to a P2P group according to an embodiment is shown.

[0033] 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

[0034] This description is not intended to represent the only possible implementation of the subject matter. Rather, this detailed description includes specific details to provide a thorough understanding of the subject matter of the invention. 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 description are to be considered illustrative rather than restrictive in nature. The same reference numerals denote the same elements.

[0035] The following description pertains to certain implementations 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 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 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 used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof.

[0036] 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 "site" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user equipment." For convenience, the terms "site" 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.).

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

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

[0039] 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 medium. 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 distribution system services to an associated STA via the wireless medium. 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 1In 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-114 are wireless communication devices, each of which may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

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

[0041] 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 "site" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "site" 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.).

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

[0043] As described in more detail below, one or more APs in an AP may include circuitry and / or programming for the management of 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 1Various 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.

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

[0045] 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 (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.

[0046] 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 processed baseband or IF signals. RF transceivers 209a-209n receive the outgoing processed baseband or IF signals from TX processing circuit 214 and up-convert the baseband or IF signals into RF signals transmitted via antennas 204a-204n.

[0047] 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 according to 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-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 assigned to different subcarrier subsets for different receivers (e.g., different STAs 111-114). Various other functions may be supported in the AP 101 via the controller / processor 224, including combinations of 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 may move data into or out of the memory 229 as needed for the execution process.

[0048] 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 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, and another portion of memory 229 can include flash memory or other ROM.

[0049] 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 for each RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, as in a conventional AP. Moreover, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0050] 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 separate antennas, 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.

[0051] 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 appear in a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope of any particular implementation of STA.

[0052] like Figure 2b As shown, STA 111 may include one or more antennas 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.

[0053] 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).

[0054] 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 processed outgoing 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.

[0055] 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 the channel detection process in the WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0056] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sounding 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 sounding, including feedback calculations based on received empty data packet advertisements (NDPA) and empty 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 laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0057] The controller / processor 240 is also coupled to input 250 (e.g., 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).

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

[0059] 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, a TX processing circuit 215, and an RX processing circuit 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.

[0060] 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 of 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-114 in the series.

[0061] 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 to the wireless medium (Link 1, Link 2, or Link 3). 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 different MAC address (lower MAC address) than any other auxiliary AP of AP MLD 310. AP MLD 310 may have an MLD MAC address (upper-layer MAC address), and the auxiliary APs share a 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.

[0062] 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 medium (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 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 MAC address), and the 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.

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

[0064] 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 ii) IEEE P802.11be / D3.0, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”.

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

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

[0067] Next-generation WLAN systems need to provide improved support for low-latency applications. Today, it is common to observe many devices operating on the same network. Many of these devices may be latency-tolerant, but still compete for the same time and frequency resources with 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-AP STAs, while a Standalone BSS is a BSS where non-AP STAs 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 AP-managed Infrastructure BSS. Another source of interference may be transmissions from adjacent Infrastructure OBSSs (Overlapping Basic Service Sets), while other sources 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.

[0068] Currently, when a TXOP is assigned to a STA, only that STA can use the TXOP to send to its peer STA. Therefore, the peer STA may not be able to use the TXOP to send, which could increase latency.

[0069] Figure 5 The illustration shows P2P communication between STAs in a P2P group according to an embodiment. Specifically, Figure 5 The diagram illustrates how a P2P group owner (e.g., a GO or mobile AP in a Wi-Fi Direct connection) uses a TXOP received from an infrastructure AP and uses this TXOP to send Physical Layer Protocol Data Units (PLUs) to other STAs in the P2P group or to trigger other STAs in the same group to send PLUs to the group owner (STA1). Specifically, STA1 is sending PPDU 501 to STA4. STA1 sends a UL trigger frame 503 to STA2 and receives PPDU 505 from STA2. STA1 allocates a TXOP 507 to STA3, and STA3 sends a PPDU to STA5.

[0070] In some embodiments, group-specific P2P resource allocation can be helpful so that any STA falling into the P2P group can utilize the allocated resources. Accordingly, in some embodiments, an AP may allocate its channel resources (e.g., TXOPs) to a group of STAs within the P2P group. In some embodiments, STAs that are members of a P2P group may request resources for that P2P group from the infrastructure AP.

[0071] In some embodiments, different technologies may be used to identify P2P groups. In some embodiments, P2P groups may be explicitly identified using a P2P group ID. In some embodiments, each STA within a P2P group may indicate its P2P group ID to the AP.

[0072] In some embodiments, implicit techniques can be used to identify P2P groups. In some embodiments, a shared flow ID (such as, for example, a Flow Classification Service (SCS) ID or a Target Wake-Up Time (TWT) flow ID) can be used to identify a P2P group. In some embodiments, each P2P STA can use the same flow ID when establishing a P2P TWT with the AP. In some embodiments, the “P2P Flow ID” field can be used to identify a P2P group. Accordingly, using the identifier information, the AP can determine which STAs are in the same P2P group.

[0073] In some embodiments, the AP may send trigger frames based on identifier information (e.g., stream ID, P2P group ID, and other identifiers). In some embodiments, the AP may allocate resources based on cumulative resource requests arriving from multiple members within the same group. Figure 6 and Figure 7 Two scenarios are illustrated, highlighting resource allocation and utilization based on P2P groups according to several embodiments.

[0074] Figure 6 P2P communication between STAs in a P2P group established according to an embodiment is illustrated. Although one or more operations are described or illustrated 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.

[0075] Specifically, Figure 6 This illustrates a scenario where STA1 has established a P2P TWT with another peer STA and is using a specific P2PTWT ID. As shown in the figure, STA1 is communicating with STA2.

[0076] In operation 601, STA1 has already established P2P TWT ID1. In some embodiments, each STA within a P2P group can indicate its P2P group ID to the AP. In some embodiments, STAs can use a flow ID, such as a flow classification service ID or a TWT flow ID.

[0077] In operation 603, STA1 sends a P2P link establishment request frame to STA2, including P2P TWT information and an ID. In some embodiments, STA1 may send an SCS request frame. In the SCS request frame, STA1 may indicate that the request is for a TXOP allocation for the P2P group.

[0078] In operation 605, STA2 sends a P2P link establishment response frame to STA1.

[0079] Figure 7 A scenario is illustrated where STA1 intends to initiate a new P2P TWT group. 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. Specifically, Figure 7 The communication between STA1, STA2 and AP is shown.

[0080] In operation 701, STA1 sends a P2P TWT resource request frame to AP, including the P2P TWT ID. In some embodiments, if STA1 intends to request channel resources from AP for a P2P group, STA1 may send an SCS request frame to AP. In the SCS request frame, STA1 may indicate that the request is for a TXOP allocation for the P2P group. In some embodiments, to request channel resources or TXOPs, STA1 may send any other management frame, indicating that the management frame is a request for channel resources or TXOPs for the P2P group indicated in the request management frame.

[0081] In operation 703, the AP sends a P2P TWT resource response frame to STA1. If a P2P TWT ID already exists, this frame may include the MAC addresses of other P2P STAs using that P2P TWT ID. In some embodiments, the AP may send an SCS response frame to STA1, indicating whether the AP accepts the received SCS request, rejects the received SCS request, or suggests an alternative set of SCS parameters corresponding to the received SCS request. If the AP suggests an alternative set of parameters, it may include a QoS feature element in the SCS response frame sent to STA1, where the QoS feature element carries the SCS parameters corresponding to the parameters suggested by the AP. Subsequently, if STA1 sends a second SCS request frame with the parameters suggested by the AP, the AP is likely to accept the second request.

[0082] In operation 705, STA1 sends a P2P TWT resource acknowledgment frame to the AP.

[0083] In operation 707, STA1 sends a P2P link establishment request frame to STA2. In some embodiments, the P2P link establishment request frame may request the establishment of a link between STA1 and STA2.

[0084] In operation 709, STA2 sends a P2P link establishment response frame to STA1. In some embodiments, the P2P link establishment response frame may include information acknowledging the link established between STA1 and STA2.

[0085] In some embodiments, in a group-based triggering mechanism, any STA can use a PPDU to transmit. In some embodiments, STAs in a P2P group can further relay TXOPs. In some embodiments, contention can occur within a P2P group. In some embodiments, the triggering mechanism can be used for Tunnel Direct Link Establishment (TDLS) in the absence of a group owner.

[0086] Figure 8 A group-based triggering method for P2P communication according to an embodiment is illustrated. Specifically, Figure 8 The diagram illustrates an AP and a P2P group comprising STA1 (as the group owner (GO)), STA2, STA3, STA4, and STA5. At step 801, the AP assigns a TXOP to the P2P group. TXOPs can be assigned to P2P groups based on identifiers such as flow IDs, group IDs, and other identifying information. Therefore, during the TXOP assignment, STA1 sends PPDU 803 to STA4, STA2 sends PPDU 805 to STA3, and STA3 sends PPDU 807 to STA5.

[0087] In some embodiments, the first STA may be a member of a P2P group comprising one or more peer STAs, including the first STA. If the first STA intends to request channel resources for the P2P group from the AP, the first STA may send a Flow Classification Service (SCS) request frame to the AP. In the SCS request frame, the first STA may indicate that the request is for a TXOP allocation for the P2P group. In some embodiments, to request channel resources or TXOPs, the first STA may send any other management frame indicating that the management frame is a request for channel resources or TXOPs for the P2P group indicated in the request management frame.

[0088] In some embodiments, to indicate a request for channel resources or TXOPs for a P2P group, the first STA may include a Quality of Service (QoS) feature element in the SCS request frame sent by the first STA to the AP. In the QoS feature element included in the SCS request frame, the first STA may include different parameters such that the requested parameters reflect the total demand for channel resources necessary to satisfy the service requirements of one or more member STAs in the P2P group. In some embodiments, the QoS feature element or the SCS request frame may also include an identifier of the P2P group, allowing the AP to identify the P2P group in subsequent resource allocation. In some embodiments, the first STA may also identify a list of other STAs in the P2P group that have already requested channel resources for it in the SCS request frame. In some embodiments, the AID (Association ID) or Media Access Control (MAC) address of the P2P STA may be included in the SCS request frame.

[0089] In some embodiments, upon receiving an SCS request frame from a first STA, where the SCS request requests channel resources for a group of P2P STAs, the AP can decide whether to accept the request. In some embodiments, if the AP rejects the request, the AP can suggest an alternative set of SCS parameters for SCS establishment, including parameters different from the set requested by the first STA.

[0090] In some embodiments, the AP may receive an SCS request frame from a first STA, wherein the SCS request frame indicates a request for channel resources for a P2P group. Upon receiving the request, the AP may send an SCS response frame to the STA, indicating whether the AP accepts the received SCS request, rejects the received SCS request, or suggests an alternative SCS parameter set corresponding to the received SCS request. In some embodiments, if the AP suggests an alternative parameter set, the AP may include a QoS feature element in the SCS response frame sent to the first STA, wherein the QoS feature element carries SCS parameters corresponding to the parameters suggested by the AP. Subsequently, if the first STA sends a second SCS request frame with the parameters suggested by the AP, the AP is likely to accept the second request.

[0091] In some embodiments, the AP may receive an SCS request frame or any other management frame from a first STA indicating a request for channel resources or TXOPs for the P2P STA group. If the AP accepts the request and sends an SCS response frame to the first STA indicating acceptance of the request, the AP may subsequently send a trigger frame to allocate TXOPs or channel resources for the P2P group. In some embodiments, the AP may allocate TXOPs at internal intervals and periodically to satisfy the resource requirements indicated in the SCS request for the P2P group. In some embodiments, the AP may send a TXOP (TXS) trigger frame triggered by a multi-user (MU) request transmission (RTS) for the P2P group, indicating that the trigger frame is for the P2P STA group. In some embodiments, the trigger frame may be a Mode 2 variant of the MU-RTS TXS trigger frame. In some embodiments, the trigger frame may be a variant of the MU-RTS TXS trigger frame. In some embodiments, the trigger frame may be a trigger frame that can be defined for TXOP allocation for the P2P group.

[0092] Figure 9a An example of a QoS feature element according to an implementation method is shown, and Figure 9b An example of a control information field within a QoS feature element according to an implementation is shown.

[0093] Reference Figure 9a The QoS feature element 900 includes the element ID field, length field, element ID extension field, control field, maximum service interval field, minimum service interval field, minimum data rate field, delay limit field, maximum MSDU size field, service start time field, service start time link ID field, average data rate field, delay limit burst size field, MSDU lifetime field, MSDU transmission information field, and media time field.

[0094] refer to Figure 9bThe control information field 910 includes a direction subfield, a TID subfield, a user priority subfield, a bitmap subfield for the presence of additional parameters, a link ID subfield, and reserved bits. The direction subfield indicates the direction of data transmission, such as uplink, downlink, or direct link. A direct link indicates that the frame (more specifically, MSDUs or A-MSDUs) is transmitted to the peer STA via a P2P link. The TID subfield indicates the TID value of the data frame described by QoS feature element 900. The user priority subfield indicates the user priority value (0-7) of the data frame described by QoS feature element 900. The bitmap subfield for the presence of additional parameters indicates a bitmap where the i-th entry in the bitmap is set to 1 if the i-th field, starting from the maximum MSDU size field, exists in QoS feature element 900. The link ID subfield contains the link identifier corresponding to the link where the direct link transmission will occur.

[0095] when Figure 9a When the direction subfield in the configuration is set to direct link, Figure 9a The minimum service interval field in the table indicates the minimum interval between the start of two consecutive service periods assigned to a STA for direct link frame switching.

[0096] when Figure 9b When the direction subfield in the configuration is set to direct link, Figure 9a The maximum service interval field in the table can indicate the maximum interval between the start of two consecutive service periods assigned to a STA for direct link frame switching.

[0097] Figure 10 A flowchart illustrating an example process 1000 for requesting resources for a P2P group 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.

[0098] Process 1000 can begin in operation 1001. In operation 1001, the first STA forms a P2P group with one or more other peer STAs.

[0099] In operation 1003, the first STA intends to request channel resources (e.g., TXOP) from the infrastructure AP associated with the first STA, where the channel resources are requested for P2P groups.

[0100] In operation 1005, the first STA notifies the AP of a P2P group request for resources. In some embodiments, the first STA may send an SCS request frame to the AP including QoS feature elements. In the QoS feature elements included in the SCS request frame, the first STA may appropriately include different parameters such that the requested parameters reflect the total channel resource requirement necessary to satisfy the service requirements of one or more members of the P2P group. In some embodiments, the QoS feature elements or the SCS request frame may also include an identifier of the P2P group, allowing the AP to identify the P2P group in subsequent resource allocation. In some embodiments, the first STA may also identify a list of other STAs in the P2P group that have already requested channel resources for them in the SCS request frame. For example, the AID (Association ID) or MAC address of the P2P STAs may be included in the SCS request frame.

[0101] In operation 1007, the first STA receives an SCS response frame from the AP. In some embodiments, the SCS response frame may indicate a request to accept the SCS request frame. In some embodiments, the SCS response frame may not accept the request, but instead send an alternative set of SCS parameters for SCS establishment, including parameters different from those requested by the first STA. If the AP suggests an alternative set of parameters, the AP may include a QoS feature element in the SCS response frame sent to the first STA, wherein the QoS feature element carries SCS parameters corresponding to the parameters suggested by the AP. Subsequently, the first STA may send a second SCS request frame with the parameters suggested by the AP, and the AP may then accept the second request.

[0102] In operation 1009, the first STA receives a trigger frame from the AP that allocates a TXOP to the P2P group. In some embodiments, a MU-RTS TXS (Mode 2) trigger frame can be used as the trigger frame and can indicate that the trigger frame is for the P2P STA group. The allocated TXOP can be determined by the AP based on parameters within the QoS feature element of the SCS request frame. The allocated TXOP can be a part of the AP's TXOP.

[0103] In operation 1011, the first STA sends P2P services to one or more peer STAs in the P2P group during the allocated TXOP period.

[0104] Figure 11 A flowchart of an example process 1100 for an AP to allocate resources to a P2P group 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.

[0105] Process 1100 can begin in operation 1101. In operation 1001, the AP receives a request for resources (e.g., TXOP) for the P2P group from a first STA. In some embodiments, the AP may receive an SCS request frame including QoS feature elements from the first STA. In the QoS feature elements included in the SCS request frame, the first STA may appropriately include different parameters such that the requested parameters reflect the total demand for channel resources necessary to satisfy the service requirements of one or more members of the P2P group. In some embodiments, the QoS feature elements or the SCS request frame may also include an identifier of the P2P group, allowing the AP to identify the P2P group in subsequent resource allocation. In one embodiment, the first STA may also identify a list of other STAs in the P2P group that have already requested channel resources for them in the SCS request frame. For example, the AID (Association ID) or MAC address of the P2P STAs may be included in the SCS request frame.

[0106] In operation 1103, the AP determines whether to accept the resource request. If the AP does not accept the resource request in operation 1103, then in operation 1105, the AP may send an alternative set of SCS parameters for SCS establishment, which includes parameters different from those requested by the first STA. In some embodiments, the alternative parameter set may be included in a QoS feature element in an SCS response frame sent to the first STA, wherein the QoS feature element carries SCS parameters corresponding to the parameters suggested by the AP. Subsequently, the AP can receive a second SCS request frame with the parameters suggested by the AP from the first STA, and then the AP may accept the second request.

[0107] If the AP accepts the request in operation 1103, then in operation 1107, the AP can send an SCS response frame indicating acceptance of the request via an SCS request frame.

[0108] In operation 1109, the AP may send a trigger frame to the first STA to allocate a TXOP to the P2P group. In some embodiments, a MU-RTS TXS (Mode 2) trigger frame may be used as the trigger frame, and may indicate that the trigger frame is for the P2P STA group. The allocated TXOP may be determined by the AP based on parameters within the QoS feature element of the SCS request frame. The allocated TXOP may be a part of the AP's TXOP.

[0109] According to various embodiments of this disclosure, an AP can allocate channel resources (e.g., TXOP) to a group of STAs within a P2P group, which can improve wireless network service performance and thereby enhance multi-device connectivity. The TXOP request process according to the embodiments described herein can be used to maintain seamless latency-sensitive service flows and improve overall system efficiency.

[0110] Unless otherwise specified, references to singular elements 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. In the absence of further constraints, elements preceded by “a,” “an,” “the,” or “the” do not preclude the presence of additional identical elements.

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

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

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

[0114] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration 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.

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

[0116] All structural and functional equivalents of the various aspects described throughout this disclosure, which are now or hereafter known to a person 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 explicitly stated in the claims. No claim element is to be interpreted pursuant to paragraph 6 of §112 unless it is expressly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “steps for…”.

[0117] 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 become 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.

[0118] 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 station (STA) in a wireless network, comprising: Memory; and A processor, coupled to a memory, is configured to: Send a request frame to the access point (AP), requesting resources from the AP for the P2P group to which the STA belongs; Receive the trigger frame for allocating a transmission opportunity (TXOP) from the AP; and Send one or more frames to peer STAs in the P2P group within the TXOP.

2. The STA according to claim 1, wherein, The processor is also configured to: Send a frame to the peer STA to reallocate a portion of the TXOP.

3. The STA according to claim 1, wherein, The processor is also configured to: Receive a response frame from the AP in response to the request frame. The response frame includes an indication of acceptance, rejection, or substitution of the request in the request frame.

4. The STA according to claim 3, wherein, The response frame includes Quality of Service (QoS) attribute elements, which include substitutions for the request in the request frame.

5. The STA according to claim 1, wherein, The request frame includes a P2P group identifier or a stream identifier that identifies the P2P group, wherein the stream identifier is a stream classification service identifier or a target wake-up time (TWT) stream identifier.

6. The STA according to claim 1, wherein, The request frame includes Quality of Service (QoS) characteristic elements, which include information associated with the service requirements of the P2P group.

7. The STA according to claim 1, wherein, The request frame includes information about one or more peer STAs in the P2P group that are requesting resources for it.

8. An access point (AP) in a wireless network, comprising: Memory; and A processor, coupled to a memory, is configured to: Receive a request frame from the site (STA), which requests resources from the AP for the P2P group to which the STA belongs; and Send a trigger frame to the STA to allocate a transmission opportunity (TXOP) to the P2P group.

9. The AP according to claim 8, wherein, The processor is also configured to: Send a response frame to the STA in response to the request frame. The response frame includes an indication of acceptance, rejection, or substitution of the request in the request frame.

10. The AP according to claim 9, wherein, The response frame includes Quality of Service (QoS) attribute elements, which include substitutions for the request in the request frame.

11. The AP according to claim 8, wherein, The request frame includes a P2P group identifier or a stream identifier that identifies the P2P group, wherein the stream identifier is a stream classification service identifier or a target wake-up time (TWT) stream identifier.

12. The AP according to claim 8, wherein, The request frame includes Quality of Service (QoS) characteristic elements, which include information associated with the service requirements of the P2P group.

13. The AP according to claim 8, wherein, The request frame includes information about one or more peer STAs in the P2P group that are requesting resources for it.

14. A computer-implemented method for communication conducted by a station (STA) in a wireless network, comprising: Send a request frame to the access point (AP), requesting resources from the AP for the P2P group to which the STA belongs; Receive the trigger frame for allocating a transmission opportunity (TXOP) from the AP; and Send one or more frames to peer STAs in the P2P group within the TXOP.

15. The computer-implemented method according to claim 14, further comprising: Send a frame to the peer STA to reallocate a portion of the TXOP.

Images