QOS support for P2P communications

By implementing dynamic request and allocation of TXOP between AP and STA devices, the problem of low P2P communication efficiency in MLO wireless communication system is solved, and communication efficiency and reliability are improved.

CN119014109APending Publication Date: 2024-11-22SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028806.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2023-05-23
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing multi-link operation (MLO) wireless communication systems have low transmission efficiency in P2P communication and are difficult to meet the needs of efficient communication.

Method used

A quality of service (QoS) support method and apparatus for P2P communication is provided, allowing the STA device to perform uplinks on a link to the AP by implementing dynamic requests and allocations of TXOP between an AP device and a STA device. Communication and P2P communication improve communication efficiency.

Benefits of technology

Through the dynamic management and distribution of TXOP, the efficiency and reliability of P2P communication are improved, and the needs of efficient wireless communication are met.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119014109A_ABST
    Figure CN119014109A_ABST
Patent Text Reader

Abstract

Methods and apparatus for supporting quality of service (QoS) support for peer-to-peer (P2P) communications. A method for wireless communication performed by a non-access point (AP) device including a first station (STA) includes transmitting a request associated with a transmit opportunity (TXOP) to a first AP; receiving information associated with the TXOP from the first AP; and performing uplink (UL) communication or both UL communication and peer-to-peer (P2P) communication based on the received information. The UL communication is performed on a link formed with the first AP, and the P2P communication is performed on a first P2P link formed with a second STA included in the second non-AP device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to transmission efficiency in wireless communication systems including multi-link devices.Embodiments of the present disclosure relate to methods and apparatus for Quality of Service (QoS) support for peer-to-peer (P2P) communications. Background Art

[0002] Wireless Local Area Network (WLAN) technology allows devices to access the Internet in the 2.4GHz, 5GHz, 6GHz, or 60GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 family of standards is designed to increase speed and reliability and extend the operating range of wireless networks.

[0003] Multi-link Operation (MLO) is a feature currently being developed by the standards body for the next generation Extremely High Throughput (EHT) Wi-Fi system in IEEE 802.11be. A Wi-Fi device that supports MLO is called a Multi-link Device (MLD). With MLO, a non-access point (AP) Multi-link Device (MLD) can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame exchange are possible on each link between an AP MLD and a non-AP MLD. Summary of the invention

[0004] Technical issues

[0005] Recently, there is a need to improve the efficiency of wireless communication (eg, P2P communication) using MLO.

[0006] Solution

[0007] Embodiments of the present disclosure provide methods and apparatus for QoS support for P2P communications.

[0008] In one embodiment, a first non-access point (AP) device is provided, comprising: a first station (STA) including a transceiver; and at least one processor operably coupled to the transceiver. The at least one processor is configured to control the transceiver to: send a request associated with a transmit opportunity (TXOP) to a first AP, receive information associated with the TXOP from the first AP, and perform uplink (UL) communication or both UL communication and peer-to-peer (P2P) communication based on the received information. The UL communication is performed on a link formed with the first AP, and the P2P communication is performed on a first P2P link formed with a second STA included in a second non-AP device.

[0009] In another embodiment, a method of wireless communication performed by a first non-AP device including a first station (STA) includes: sending a request associated with a transmit opportunity (TXOP) to the first AP; receiving information associated with the TXOP from the first AP; and performing uplink (UL) communication or performing both UL communication and peer-to-peer (P2P) communication based on the received information. The UL communication is performed on a link formed with the first AP, and the P2P communication is performed on a first P2P link formed with a second STA included in a second non-AP device.

[0010] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.

[0011] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document.The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other.The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication.The terms "include" and "comprise" and their derivatives mean including but not limited to this.The term "or" is inclusive, meaning and / or.The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to or connected with, coupled to or coupled with, can communicate with, collaborate with, interweave, juxtapose, be close to, be bound to or bound with, have, have the property of, have a relationship with, or have a relationship with.The term "controller" means any device, system or part thereof that controls at least one operation.Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. Functionality associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of..." means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. As used herein, terms such as "first" and "second" or "first" and "second" may be used to simply distinguish a corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as "coupled with another element (e.g., a second element)", "coupled to another element", "connected to another element", or "connected to another element" with or without the term "operably" or "communicatively", it means that the element may be coupled to another element directly (e.g., wired), wirelessly, or via a third element.

[0012] As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "component," or "circuit"). A module may be a single integrated component or its smallest unit or portion suitable for performing one or more functions. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0013] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.

[0014] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0016] Figure 1 illustrates an example wireless network according to an embodiment of the present disclosure;

[0017] Figure 2A An example AP according to an embodiment of the present disclosure is shown;

[0018] Figure 2B An example station (STA) according to an embodiment of the present disclosure is shown;

[0019] Figure 3 An example of Mode 1 Transmit Opportunity (TXOP) sharing according to an embodiment of the present disclosure is shown, where STA1 uses the TXOP only for uplink communications;

[0020] Figure 4 An example of Mode 2 TXOP sharing according to an embodiment of the present disclosure is shown, where STA1 uses the TXOP for both uplink communication with the AP and P2P communication with STA2;

[0021] Figure 5An example multi-user request to send (MU-RTS) TXOP sharing (TXS) trigger frame format is shown according to an embodiment of the present disclosure;

[0022] Figure 6 An example of requesting a TXOP by a peer non-AP STA according to an embodiment of the present disclosure is shown;

[0023] Figure 7 An example format of a TXS request frame according to an embodiment of the present disclosure is shown;

[0024] Figure 8 An example format of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown;

[0025] Fig. 9 Another example format of the TXS request information field in the TXS request frame according to an embodiment of the present disclosure is shown;

[0026] Fig.10 Another example format of the TXS request information field in the TXS request frame according to an embodiment of the present disclosure is shown;

[0027] Fig.11 An example of requesting TXOP for multiple P2P links according to an embodiment of the present disclosure is shown;

[0028] Fig.12 Another example format of the TXS request information field in the TXS request frame according to an embodiment of the present disclosure is shown;

[0029] Fig.13 An example format of a P2P link information subfield in a P2P link information set subfield according to various embodiments of the present disclosure is shown;

[0030] Fig.14 Another example format of the TXS request information field in the TXS request frame according to an embodiment of the present disclosure is shown;

[0031] Fig.15 An example of a TXS request-response frame exchange according to an embodiment of the present disclosure is shown;

[0032] Fig.16 An example of an implicit request for a P2P TXOP using a P2P Buffer Status Report (BSR) frame according to an embodiment of the present disclosure is shown;

[0033] Fig.17 An example format of a TXS request frame including a QoS characteristic element according to an embodiment of the present disclosure is shown;

[0034] Fig.18 An example of using a QoS characteristic element with a TXS request frame according to an embodiment of the present disclosure is shown;

[0035] Fig.19 A flowchart showing a method of using a TXS request process according to an embodiment of the present disclosure;

[0036] Fig. 20 A flowchart showing a method for soliciting a TXOP using a P2P-specific BSR according to an embodiment of the present disclosure;

[0037] Fig.21 An example of sending a TXS request for a P2P service of another link on one link according to an embodiment of the present disclosure is shown;

[0038] Fig. 22 An example format of a P2P link information subfield in a P2P link information set subfield according to an embodiment of the present disclosure is shown;

[0039] Fig.23 An example of sending a P2P BSR on one link for P2P traffic on another link according to an embodiment of the present disclosure is shown; and

[0040] Fig.24 A flowchart of a method for wireless communication performed by a non-AP device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0041] Discussed below Figures 1 to 24 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0042] Embodiments of the present disclosure provide mechanisms for Quality of Service (QoS) support for peer-to-peer (P2P) communications.

[0043] Figure 1 An example wireless network 100 is shown in accordance with various embodiments of the present disclosure. Figure 1 The embodiment of the wireless network 100 shown is for illustration purposes. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0044] The wireless network 100 includes APs 101 and 103. The 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. The AP 101 provides wireless access to the network 130 for a plurality of STAs 111-114 within a coverage area 120 of the AP 101. The APs 101 and 103 may communicate with each other and with the STAs 111-114 using Wi-Fi or other wireless local area network (WLAN) communication technologies.

[0045] 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 a remote terminal. In a WLAN, assuming that the AP also competes for a wireless channel, the AP may also be referred to as a STA (e.g., APSTA). In addition, depending on the network type, other well-known terms may be used instead of "station" or "STA", such as "mobile station", "subscriber station", "remote terminal", "user device", "wireless terminal" or "user device". For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or competes for a wireless channel in a WLAN, whether the STA is a mobile device (e.g., a mobile phone or smart phone) or is generally considered to be a fixed device (e.g., a desktop computer, an AP, a media player, a fixed sensor, a television, etc.). This type of STA may also be referred to as a non-APSTA.

[0046] In various embodiments of the present disclosure, each of the APs 101 and 103 and each of the STAs 111-114 may be a multi-link device (MLD). In such an embodiment, the APs 101 and 103 may be AP MLDs, and the STAs 111-114 may be non-AP MLDs. Each MLD is affiliated with more than one STA. For ease of explanation, an AP MLD is described herein as being affiliated with more than one AP (e.g., more than one AP STA), and a non-AP MLD is described herein as being affiliated with more than one STA (e.g., more than one non-AP STA).

[0047] Dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with APs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the AP and variations in the radio environment associated with natural and man-made obstacles.

[0048] As described in more detail below, one or more of the APs may include circuitry and / or programming for QoS support for P2P communications. Figure 1 An example of a wireless network 100 is shown, but may be Figure 1 Various changes may be made. For example, wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. In addition, AP 101 may communicate directly with any number of STAs and provide these STAs with wireless broadband access to network 130. Similarly, each of APs 101 and 103 may communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. In addition, APs 101 and / or 103 may provide access to other or additional external networks (such as an external telephone network or other types of data networks).

[0049] Figure 2A An example AP 101 is shown in accordance with various embodiments of the present disclosure. Figure 2A The embodiment of AP 101 shown in FIG. 1 is for illustration purposes only, and Figure 1 APs 103 may have the same or similar configurations. In the embodiments discussed below, AP 101 is an AP MLD. However, APs have a variety of configurations, and Figure 2A The scope of the present disclosure is not limited to any particular implementation of an AP.

[0050] The AP MLD 101 is subordinate to a plurality of APs 202a-202n (which may be referred to as, for example, AP1-APn). Each of the subordinate APs 202a-202n includes a plurality of antennas 204a-204n, a plurality of radio frequency (RF) transceivers 209a-209n, a transmit (TX) processing circuit 214, and a receive (RX) processing circuit 219. The AP MLD 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.

[0051] The illustrated components of each subordinate AP 202a-202n may represent the physical (PHY) layer and the lower media access control (LMAC) layer in the open systems interconnection (OSI) networking model. In such an embodiment, the illustrated components of the AP MLD 101 represent a single upper MAC (UMAC) layer and other higher layers in the OSI model, which are shared by all subordinate APs 202a-202n.

[0052] For each subordinate AP 202a-202n, an RF transceiver 209a-209n receives an incoming RF signal from an antenna 204a-204n, such as a signal transmitted by a STA in the network 100. In some embodiments, each subordinate AP 202a-202n operates in a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and thus the incoming RF signal received by each subordinate AP may be at a different RF frequency. The RF transceiver 209a-209n down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuit 219, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 219 sends the processed baseband signal to the controller / processor 224 for further processing.

[0053] For each subordinate AP 202a-202n, the TX processing circuit 214 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 224. The TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 209a-209n receives the outgoing processed baseband or IF signal from the TX processing circuit 214 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 204a-204n. In an embodiment where each subordinate AP 202a-202n operates in a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each subordinate AP can be at a different RF frequency.

[0054] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP MLD 101. For example, the controller / processor 224 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 209a-209n, the RX processing circuit 219, and the TX processing circuit 214 according to well-known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, in which the output signals from the multiple antennas 204a-204n are weighted differently to effectively steer the output signals in the desired direction. The controller / processor 224 may also support orthogonal frequency division multiplexing (OFDMA) operations, in which outgoing signals are assigned to different subcarrier subsets of different recipients (e.g., different STAs 111-114). The controller / processor 224 may support any of a variety of other functions in the AP MLD 101, including QoS support for P2P communications. In some embodiments, the controller / processor 224 includes at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an OS, residing in the memory 229. The controller / processor 224 can move data into or out of the memory 229 as required by the executing process.

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

[0056] As described in more detail below, AP MLD 101 may include circuitry and / or programming for QoS support for P2P communications. Figure 2A An example of AP MLD 101 is shown, but the same may be applied to Figure 2A For example, AP MLD 101 may include Figure 2A. As a specific example, the AP MLD 101 may include multiple interfaces 234, and the controller / processor 224 may support routing functions to route data between different network addresses. As another specific example, although each subordinate AP 202a-202n is shown as including a single instance of the TX processing circuit 214 and a single instance of the RX processing circuit 219, the AP MLD 101 may include multiple instances of each AP in one or more of the subordinate APs 202a-202n (such as one for each RF transceiver). Alternatively, in one or more of the subordinate APs 202a-202n, only one antenna and RF transceiver path may be included, such as in a traditional AP. In addition, Figure 2A The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0057] Figure 2B An example STA 111 is shown according to various embodiments of the present disclosure. Figure 2B The embodiment of STA 111 shown in FIG. is for illustration only, and Figure 1 STAs 111-115 may have the same or similar configurations. In the embodiments discussed below, STA 111 is a non-AP MLD. However, STAs may have a variety of configurations, and Figure 2B The scope of the present disclosure is not limited to any particular implementation of a STA.

[0058] The non-AP MLD 111 is subordinate to a plurality of STAs 203a-203n (which may be referred to as, for example, STA1-STAn). Each subordinate STA 203a-203n includes an antenna (or multiple) 205, an RF transceiver 210, a TX processing circuit 215, and an RX processing circuit 225. The non-AP MLD 111 also includes a microphone 220, a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touch screen 250, a display 255, and a memory 260. The memory 260 includes an operating system (OS) 261 and one or more applications 262.

[0059] The illustrated components of each subordinate STA 203a-203n may represent the PHY layer and the LMAC layer in the OSI networking model. In such an embodiment, the illustrated components of the non-AP MLD 111 represent a single UMAC layer and other higher layers in the OSI model, which are shared by all subordinate STAs 203a-203n.

[0060] For each subordinate STA 203a-203n, the RF transceiver 210 receives the incoming RF signal sent by the AP of the network 100 from the antenna (or multiple) 205. In some embodiments, each subordinate STA 203a-203n operates in a different bandwidth (e.g., 2.4GHz, 5GHz, or 6GHz), and thus the incoming RF signal received by each subordinate STA can be at a different RF frequency. The RF transceiver 210 down-converts the input RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuit 225, which generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. The RX processing circuit 225 sends the processed baseband signal to the speaker 230 (such as for voice data) or to the controller / processor 240 for further processing (such as for web browsing data).

[0061] For each subordinate STA 203a-203n, the TX processing circuit 215 receives analog or digital voice data from the microphone 220, or receives other outgoing baseband data (such as web data, email, or interactive video game data) from the controller / processor 240. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 210 receives the outgoing processed baseband or IF signal from the TX processing circuit 215 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna (or multiple) 205. In an embodiment where each subordinate STA 203a-203n operates in a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each subordinate STA can be at a different RF frequency.

[0062] The controller / processor 240 may include one or more processors and execute a basic OS program 261 stored in the memory 260 to control the overall operation of the non-AP MLD 111. In one such operation, the main controller / processor 240 controls the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 210, the RX processing circuit 225, and the TX processing circuit 215 according to well-known principles. The main controller / processor 240 may also include processing circuits configured to support QoS support for P2P communications. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.

[0063] The controller / processor 240 is also capable of executing other processes and programs resident in the memory 260, such as operations for QoS support to support P2P communications. The controller / processor 240 can move data into or out of the memory 260 as needed for the executed process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for QoS support to support P2P communications. The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to a signal received from the AP. The main controller / processor 240 is also coupled to the I / O IF 245, which provides the non-AP MLD 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O IF 245 is the communication path between these accessories and the main controller 240.

[0064] Controller / processor 240 is also coupled to touch screen 250 and display 255. An operator of non-AP MLD 111 may input data into non-AP MLD 111 using touch screen 250. Display 255 may be a liquid crystal display, light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website. Memory 260 is coupled to controller / processor 240. A portion of memory 260 may include RAM, and another portion of memory 260 may include flash memory or other ROM.

[0065] although Figure 2B An example of a non-AP MLD 111 is shown, but the Figure 2B Make various changes. For example, Figure 2B The various components in the may be combined, further subdivided, or omitted, and additional components may be added as required. In a specific example, one or more of the subordinate STAs 203a-203n may include any number of antennas (or multiple) 205 for multiple-input and multiple-output (MIMO) communications with the AP 101. In another example, the non-AP MLD 111 may not include voice communications, 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). In addition, although Figure 2B The non-AP MLD 111 is shown configured as a mobile phone or smart phone, but the non-AP MLD may be configured to operate as other types of mobile or stationary devices.

[0066] Various embodiments of the present disclosure recognize that transmit opportunity (TXOP) sharing is a newly defined feature in the IEEE 802.11be specification. Using this process, an AP can allocate TXOPs to non-AP STAs using a multi-user request to send (MU-RTS) trigger frame.

[0067] Using the TXOP sharing process, the AP helps the STA win the channel so that the STA can deliver its packets. The following illustrative steps may be included in the TXOP sharing process:

[0068] Step-1: AP first wins the channel; AP obtains TXOP of wireless medium;

[0069] Step-2: The AP decides to allocate a portion of its won TXOP to a specific STA (e.g., STA1) in its Basic Service Set (BSS);

[0070] Step 3: AP gives some instructions to STA1, notifying it of the allocated TXOP;

[0071] Step 4: STA1 uses the allocated TXOP for its uplink (UL) or P2P communication;

[0072] Step 5: After utilizing its allocated TXOP, STA1 returns the TXOP to the AP.

[0073] The way an AP notifies a STA of its allocated TXOP is by using the MU-RTS TXOP Sharing (TXS) frame, which is a newly defined trigger frame introduced in IEEE 802.11be.

[0074] Currently, one MU-RTS TXS trigger frame can allocate a TXOP to a single STA and no more than one STA. For example:

[0075] -Consider a BSS consisting of one AP and three STAs - STA1, STA2, and STA3.

[0076] -AP competes for the channel with all three STAs.

[0077] -AP wins the channel and gets TXOP for 60ms.

[0078] -AP sends a MU-RTS TXS trigger frame to STA1.

[0079] - In the trigger frame, the AP indicates that the amount of TXOP allocated to STA1 is 20 milliseconds (ms).

[0080] - After receiving the MU-RTS TXS trigger frame from the AP, STA1 uses the allocated 20ms TXOP to send uplink data to the AP.

[0081] - At the end of 20ms, the TXOP is returned to the AP.

[0082] - The AP uses the remaining 40 ms of the TXOP to send downlink (DL) data to STA2 and STA3.

[0083] TGbe defines two TXOP sharing modes:

[0084] - Mode 1: for UL / DL communication

[0085] In this mode, the AP allocates a TXOP to the STA and indicates to the STA that the STA can use the TXOP to send UL data packets.

[0086] - Mode 2: for both UL / DL and P2P communications

[0087] In this mode, the AP allocates a TXOP to the STA and indicates to the STA that the STA can use the TXOP for both UL communication and P2P communication.

[0088] Figure 3 An example 300 of Mode 1 TXOP sharing according to an embodiment of the present disclosure is shown, where STA1 uses the TXOP for UL communication. Figure 3 The embodiment of the example 300 of Mode 1 TXOP sharing in which STA1 uses the TXOP for UL communication shown in is for illustration. Other embodiments of the example 300 of Mode 1 TXOP sharing in which STA1 uses the TXOP for UL communication may be used without departing from the scope of the present disclosure.

[0089] Figure 4 An example 400 of Mode 2 TXOP sharing according to an embodiment of the present disclosure is shown, where STA1 uses the TXOP for both UL communication with the AP and P2P communication with STA2. Figure 4 The embodiment of the example 400 of mode 2 TXOP sharing in which STA1 uses TXOP for both UL communication with the AP and P2P communication with STA2 is shown for illustration. Other embodiments of the example 400 of mode 2 TXOP sharing in which STA1 uses TXOP for both UL communication with the AP and P2P communication with STA2 may be used without departing from the scope of the present disclosure.

[0090] Figure 5 An example MU-RTS TXS trigger frame format 500 is shown according to an embodiment of the disclosure. Figure 5 The illustrated embodiment of the example MU-RTS TXS trigger frame format 500 is for illustration only. Other embodiments of the example MU-RTS TXS trigger frame format 500 may be used without departing from the scope of the present disclosure.

[0091] like Figure 5 As shown, the MU-RTS TXS mode is indicated in the Common Information field of the MU-RTS Trigger frame. In the MU-RTS Trigger frame, the Duration / ID field may be set to the estimated time, in microseconds, required to send: the pending frame(s), plus one Clear to Send (CTS) frame, plus the time to send the requested High Efficiency Triggered-Based Physical Protocol Data Unit (HE TB PPDU) if required, plus the time to send an acknowledgment for the requested HE TB PPDU if required, plus the applicable Inter-Frame Space (IFS).

[0092] Various embodiments of the present disclosure recognize that there is currently no mechanism in the specification that enables requesting a TXOP from an AP. However, such a capability would be beneficial for efficient operation, especially for P2P communications.

[0093] Therefore, various embodiments of the present disclosure provide a mechanism and framework for requesting a TXOP from an AP or AP MLD based on dynamic changes in a non-AP STA's P2P buffer. Various embodiments of the present disclosure also provide a mechanism for QoS support for P2P communications.

[0094] Figure 6 An example 600 of requesting a TXOP by a peer non-AP STA according to an embodiment of the present disclosure is shown. Figure 6 The embodiment of the example 600 of requesting a TXOP by a peer non-AP STA shown in FIG. 6 is for illustration. Other embodiments of the example 600 of requesting a TXOP by a peer non-AP STA may be used without departing from the scope of the present disclosure.

[0095] According to one embodiment, a first non-AP STA (STA1) that has established a P2P link with a second non-AP STA (STA2) may request the AP to allocate a TXOP to the first non-AP STA for enabling P2P transmission of the first non-AP STA. According to one embodiment, the first non-AP STA may send a TXS request frame 602 to the AP (AP1) to request a MU-RTS TXS (mode 2) trigger frame 604 for transmitting the traffic of the first non-AP STA to the second non-AP STA. This embodiment is Figure 6According to another embodiment, the first non-AP STA may send a TXOP request to the AP associated with the first non-AP STA for UL / DL communication or for P2P service. According to this embodiment, the first STA may request a MU-RTS TXS trigger frame corresponding to mode 1 or mode 2.

[0096] Figure 7 An example format 700 of a TXS request frame according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of the example format 700 of a TXS request frame is shown for illustration. Other embodiments of the example format 700 of a TXS request frame may be used without departing from the scope of the present disclosure.

[0097] like Figure 7 As shown, according to one embodiment, the TXS request frame may be a control frame type.

[0098] Figure 8 An example format 800 of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of the example format 800 of the TXS request information field in the TXS request frame is shown for illustration. Other embodiments of the example format 800 of the TXS request information field in the TXS request frame may be used without departing from the scope of the present disclosure.

[0099] According to one embodiment, the median time field 802 specifies the median time requested by the TXS request frame. It can be in units of 256us. The median time can be the average time required per second for sending P2P traffic. The STA can request this median time based on how many P2P packets it has in its queue. If there are a small number of P2P packets in the queue, the requested median time can be relatively short; if there are a large number of P2P packets in the queue, the requested median time can be relatively long.

[0100] According to one embodiment, the bandwidth subfield 804 indicates the maximum bandwidth that the TXOP requesting STA can operate on the P2P link. This field can be encoded for different bandwidth representations, for example, 0 can represent a 20 MHz bandwidth, 1 can represent a 40 MHz bandwidth, 2 can represent an 80 MHz bandwidth, 3 can represent a 160 MHz bandwidth, 4 can represent a 320 MHz bandwidth, and so on.

[0101] Fig. 9 An example format 900 of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown. Fig. 9The embodiment of the example format 900 of the TXS request information field in the TXS request frame is shown for illustration. Other embodiments of the example format 900 of the TXS request information field in the TXS request frame may be used without departing from the scope of the present disclosure.

[0102] like Fig. 9 As shown, the TID subfield 902 may specify a TID for requesting a TXOP using a TXS request frame. According to another embodiment, a TID bitmap may also be used to indicate multiple TIDs.

[0103] Fig.10 An example format 1000 of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown. Fig.10 The illustrated embodiment of the example format 1000 of the TXS request information field in a TXS request frame is for illustration. Other embodiments of the example format 1000 of the TXS request information field in a TXS request frame may be used without departing from the scope of the present disclosure.

[0104] like Fig.10 As shown, in another possible variation, the mode subfield may also be included in the TXS request information field in the TXS request frame.

[0105] exist Fig.10 , setting the Mode subfield to 0 may indicate that the TXOP has been requested for UL / DL (i.e., MU-RTS TXS trigger frame-mode-1); otherwise, the TXOP is requested for UL / DL or P2P (i.e., MU-RTS TXS trigger frame-mode-2).

[0106] Fig.11 An example 1100 of requesting TXOPs for multiple P2P links according to an embodiment of the disclosure is shown. Fig.10 The embodiment of the example 1100 of requesting TXOPs for multiple P2P links shown in is for illustration. Other embodiments of the example 1100 of requesting TXOPs for multiple P2P links may be used without departing from the scope of the present disclosure.

[0107] In different scenarios, a non-AP STA may have multiple P2P links with multiple peer non-AP STAs. For each P2P link, the non-AP STA may have different transmission requirements. According to one embodiment, if a first non-AP STA (STA1) has multiple P2P links (P2P link 1 and P2P link 2) established with multiple peer non-AP STAs (STA2 and STA3), the first non-AP STA may send a TXS request frame 1102 to the AP (AP1), which requests a TXOP to enable transmission on each of the multiple P2P links.

[0108] According to one embodiment, the same TXS request frame may be used to request TXOPs for multiple P2P links. To facilitate this, Fig.12 A possible format of the TXS request information field is shown in FIG.

[0109] Fig.12 An example format 1200 of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown. Fig.12 The embodiment of the example format 1200 of the TXS request information field in the TXS request frame is shown for illustration. Other embodiments of the example format 1200 of the TXS request information field in the TXS request frame may be used without departing from the scope of the present disclosure.

[0110] like Fig.12 As shown in FIG. 1 , the P2P link information set number subfield 1202 indicates the number of P2P link information sets in the P2P link information set subfield (ie, Fig.12 The number of P2P link information sets present in the last subfield shown in .

[0111] Fig.13 An example format 1300 of a P2P link information subfield in a P2P link information set subfield according to an embodiment of the present disclosure is shown. Fig.13 The embodiment of the example format 1300 of the P2P link information subfield in the P2P link information set subfield shown in is for illustration. Other embodiments of the example format 1300 of the P2P link information subfield in the P2P link information set subfield may be used without departing from the scope of the present disclosure.

[0112] like Fig.13 As shown in , the P2P link information set subfield contains one or more P2P link information subfields (one P2P link information subfield for each P2P link for which a TXOP is requested). The format of each P2P link information subfield in the P2P link information set field is as follows: Fig.13 Shown in.

[0113] Fig.13 The Median Time, Bandwidth, TID subfields in the P2P Link Information subfield have the same description as described in the previous embodiment. The Link ID subfield in the P2P Link Information subfield specifies the link ID of the P2P link for which the TXOP is requested. According to another embodiment, the MAC address of the peer STA operating at the other end of the P2P link may also be included in the P2P Link Information subfield.

[0114] Fig.14 An example format 1400 of a TXS request information field in a TXS request frame according to an embodiment of the present disclosure is shown. Fig.14 The embodiment of the example format 1400 of the TXS request information field in the TXS request frame is shown for illustration. Other embodiments of the example format 1400 of the TXS request information field in the TXS request frame may be used without departing from the scope of the present disclosure.

[0115] like Fig.14 As shown in , according to another embodiment, the P2P link information bitmap 1402 can be used to indicate which P2P link corresponding P2P link information is included in the TXS request frame. According to this embodiment, a possible format of the TXS request information field in the TXS request frame is as follows: Fig.14 is shown in .

[0116] exist Fig.14 In the P2P link information bitmap subfield, the P2P link information bitmap subfield specifies a bitmap indicating for which P2P link the corresponding P2P link information subfield exists in the P2P link information set subfield. For example, if the P2P link information bitmap is set to 0 01 0 1 0 0 0 0 0 0 0 0 0 0 0, this may mean that the first P2P link information subfield in the P2P link information set field 1404 corresponds to the P2P link 3 between the AP MLD and the non-AP MLD or the P2P link established on the link 3; the second P2P link information subfield in the P2P link information set field corresponds to the P2P link 5 between the AP MLD and the non-AP MLD or the P2P link established on the link 5. The link number may be relative to the link of the AP MLD.

[0117] Fig.15 An example 1500 of a TXS request-response frame exchange according to an embodiment of the present disclosure is shown. Fig.15 The embodiment of the example 1500 of the TXS request-response frame exchange shown in FIG. 1 is for illustration. Other embodiments of the example 1500 of the TXS request-response frame exchange may be used without departing from the scope of the present disclosure.

[0118] like Fig.15As shown, according to another embodiment, upon receiving a TXS request frame 1502 from a non-AP STA, the AP may send a TXS response frame 1504 to the non-AP STA. The TXS response frame may indicate whether the AP has accepted the request for TXOP made by the non-AP STA through the TXS request frame.

[0119] According to another embodiment, the TXS request frame may also be a variation of the A control subfield. Such a control subfield may be referred to as a TXOP sharing request (TXSR) control subfield. The format of the control information subfield of the TXSR control subfield may be similar to the TXS request information subfield as described in the previous embodiment. The control ID subfield corresponding to the TXSR control subfield may be any value between 10 and 14.

[0120] According to another embodiment, the TXS request frame may also be a management frame. The format may be similar to the format described in the previous embodiment.

[0121] Fig.16 An example 1600 of an implicit request for a P2P TXOP using a P2P buffer status report (BSR) frame is shown according to an embodiment of the present disclosure. Fig.16 The illustrated embodiment of the example 1600 of implicit request for a P2P TXOP using a P2P BSR frame is for illustration. Other embodiments of the example 1600 of implicit request for a P2P TXOP using a P2P BSR frame may be used without departing from the scope of the present disclosure.

[0122] According to another embodiment, a first non-AP STA that has established a P2P link with a second peer non-AP STA may send a P2P BSR frame 1602 to the AP (e.g., in response to a buffer status report poll (BSRP) trigger frame sent by the AP to the non-AP STA). The P2P BSR frame may be an implicit request from the non-AP STA to the AP for a TXOP to enable transmission of P2P traffic as indicated by the buffer status in the P2P BSR frame. Upon receiving the P2P BSR from the non-AP STA, the AP may calculate the median time required in the TXOP so that the non-AP STA can complete transmission of the P2P packets in its buffer. The AP is able to calculate the median time based on queue sizes corresponding to different associated STAs and based on the scheduling algorithm of the AP. Therefore, the AP may allocate the calculated TXOP to the requesting non-AP STA. The P2P BSR frame may also be sent as a response to a BSRP sent by the AP. This embodiment is Fig.16 Shown in.

[0123] Fig.17An example format 1700 of a TXS request frame including a QoS characteristics element according to an embodiment of the present disclosure is shown. Fig.17 The embodiment of the example format 1700 of a TXS request frame including a QoS characteristics element shown in FIG. 1 is for illustration. Other embodiments of the example format 1700 of a TXS request frame including a QoS characteristics element may be used without departing from the scope of the present disclosure.

[0124] According to one embodiment, the QoS characteristics element 1702 may be included in the TXS request frame. Fig.17 The TXS request frame format including the QoS characteristic element is shown in . According to another embodiment, the QoS characteristic element may be sent before or after sending the TXS request frame or the TXSR control subfield or the P2P BSR to the AP.

[0125] exist Fig.17 The QoS characteristics subfield contains one or more QoS characteristics elements.

[0126] Fig.18 An example 1800 of using a QoS characteristic element with a TXS request frame according to an embodiment of the present disclosure is shown. Fig.18 The illustrated embodiment of the example 1800 of using a QoS characteristics element with a TXS request frame is for illustration. Other embodiments of the example 1800 of using a QoS characteristics element with a TXS request frame may be used without departing from the scope of the present disclosure.

[0127] The QoS characteristics element will provide the AP with the QoS requirements for each TID for which the non-AP STA has requested a TXOP. The QoS characteristics element will provide relatively long-term QoS requirements information for the AP or AP MLD, and the context can be set for each TID. These values ​​in the QoS characteristics element can be based on the P2P business mode of the non-AP STA. For example, the delay bound subfield in the QoS characteristics element can be set based on the delay bound requirements of the STA's business mode. The TXS request frame or TXSR control subfield or P2P BSR sent subsequently can indicate the TXOP requirements of the non-AP STA so that the non-AP STA can successfully complete its P2P transmission. The non-AP STA can send the QoS characteristics element once and then send multiple TXS request frames or TXSR control subfields or P2P BSR frames to the AP to request a TXOP for its P2P transmission. The non-AP STA can also use the QoS characteristics element as an implicit request for the TXOP for its P2P transmission, and can indicate the necessary median time and bandwidth corresponding to the requested TXOP. However, the QoS characteristics element contains the average value required for the P2P service. These values ​​may be set based on the long-term P2P traffic pattern. However, in real-time operation, the non-AP STA may also use the EDCA contention method to send some of the traffic for which TXOP has been requested in the QoS characteristics element, and therefore, if the AP allocates TXOP to the non-AP STA based on the original requested TXOP in the QoS characteristics element, the AP will over-allocate TXOP to the P2P traffic of the non-AP STA. On the other hand, if the AP allocates based on the TXOP requested in the QoS characteristics element, the AP may also allocate insufficient TXOP to the non-AP STA. Therefore, in order to dynamically request TXOP, the non-AP STA may use a TXS request frame or a TXSR control frame or a P2P BSR. In Fig.18 A diagram of using the QoS characteristic element with a TXS request frame is shown in FIG.

[0128] Fig.19 A flow chart illustrating a method 1900 of using a TXS request process according to an embodiment of the present disclosure. Fig.19 The illustrated embodiment of the flowchart of the method 1900 using the TXS request process is for illustration. Other embodiments of the flowchart of the method 1900 using the TXS request process may be used without departing from the scope of the present disclosure.

[0129] like Fig.19As shown, method 1900 starts at step 1910, where a non-AP STA sends a TXS request for UL communication to an AP. At step 1920, the non-AP STA sends a QoS requirement to the AP corresponding to the TXS request, for example, through a QoS characteristic element. At step 1930, the non-AP STA receives a response to the TXS request from the AP. At step 1940, it is determined whether the non-AP STA receives an acceptance response to its TXS request from the AP. If not, at step 1950, the non-AP STA does not receive a TXS trigger frame from the AP. If yes, at step 1960, the non-AP STA receives a TXS trigger frame from the AP.

[0130] Fig. 20 A flow chart illustrating a method 2000 of requesting a TXOP using a P2P-specific BSR according to an embodiment of the present disclosure. Fig. 20 The embodiment of the flowchart of the method 2000 for requesting a TXOP using a P2P specific BSR shown in FIG. 2 is for illustration. Other embodiments of the flowchart of the method 2000 for requesting a TXOP using a P2P specific BSR may be used without departing from the scope of the present disclosure.

[0131] like Fig. 20 As shown, method 2000 starts at step 2010, where a non-AP STA has packets for its peer STA in a queue. At step 2020, the non-AP STA sends a peer BSR to the AP indicating its buffer status corresponding to its P2P traffic. At step 2030, the non-AP STA receives a MU-RTS TXS trigger frame (mode-2) from the AP for enabling its P2P traffic.

[0132] Fig.21 An example 2100 of sending a TXS request on one link for a P2P service of another link according to an embodiment of the present disclosure is shown. Fig.21 The illustrated embodiment of the example 2100 of sending a TXS request for P2P traffic on one link for another link is for illustration. Other embodiments of the example 2100 of sending a TXS request for P2P traffic on one link for another link may be used without departing from the scope of the present disclosure.

[0133] According to one embodiment, a non-AP MLD that has established one or more P2P links on one or more links may send a TXS request frame to the AP MLD to request a TXOP for the P2P link. A TXS request frame may be sent on one link to request a TXOP on other links (or links). Fig.21 Shown in.

[0134] According to one embodiment, a non-AP MLD that has established one or more P2P links on one or more links may send a TXS request frame to an AP MLD, the TXS request frame indicating in the request frame information such as on which link between the AP MLD and the non-AP MLD a TXOP is needed and for which P2P link the non-AP MLD needs a TXOP. To achieve this, an MLD-level link ID may be included in the P2P link information subfield together with the P2P link ID. Fig. 22 This variation of the P2P Link Information subfield is shown.

[0135] Fig. 22 An example format 2200 of a P2P link information subfield in a P2P link information set subfield according to an embodiment of the present disclosure is shown. Fig. 22 The embodiment of the example format 2200 of the P2P link information subfield in the P2P link information set subfield shown in is for illustration. Other embodiments of the example format 2200 of the P2P link information subfield in the P2P link information set subfield may be used without departing from the scope of the present disclosure.

[0136] exist Fig. 22 2202 will identify the link ID of the link on which the P2P peer STA affiliated with the non-AP MLD is operating and needs a TXOP for P2P communication. The P2P link ID subfield 2204 will identify the P2P link on which the STA affiliated with the non-AP MLD and operating on the link specified in the MLD level link ID subfield will need to request a TXOP from the AP MLD.

[0137] According to another embodiment, Fig. 22 The P2P MAC address may also be included in the P2P Link Information subfield. The P2P MAC address subfield shall specify the MAC address of the peer STA operating on the other end of the P2P link for which the non-AP MLD requests a TXOP from the AP MLD for communications over the P2P link.

[0138] As an example, for this embodiment, refer to Fig.21 , the MLD-Level Link ID subfield will identify the "Link 2" on which STA-2 is operating. The P2P Link ID subfield or the P2P MAC Address subfield will then identify Fig.21 Note that although Fig.21STA2 is shown to have one P2P link, but in practice, STA2 may have more than one P2P link, and in those scenarios, a P2P Link ID subfield or a P2P MAC Address subfield would be needed to identify the P2P link for which STA2 is requesting a TXOP.

[0139] According to one embodiment, a non-AP MLD that has established one or more P2P links on one or more links may send a P2P specific BSR frame to the AP MLD to implicitly request a TXOP for the P2P link. A P2P BSR frame may be sent on one link to request a TXOP on the other link(s). Fig.23 Shown in.

[0140] Fig.23 An example 2300 of sending a P2P BSR on one link for P2P traffic on another link according to an embodiment of the present disclosure is shown. Fig.23 The embodiment of the example 2300 of sending a P2P BSR on one link for P2P traffic on another link shown in is for illustration. Other embodiments of the example 2300 of sending a P2P BSR on one link for P2P traffic on another link may be used without departing from the scope of the present disclosure.

[0141] According to one embodiment, the MLD Level Link ID subfield may be included in the QoS Characteristics element to indicate to which link the QoS Characteristics element information corresponds to the AP MLD. Using the MLD Level Link ID subfield in conjunction with the P2P Link ID subfield in the QoS Characteristics element may be similar to Fig.21 and Fig. 22 The corresponding embodiments.

[0142] According to one embodiment, a non-AP MLD or a non-AP STA may use the More Data subfield in an Ack or BlockAck frame to an associated AP to have a similar purpose as the TXS request frame as described in the previous embodiments of the present disclosure. For example, if a non-AP STA or a STA belonging to a non-AP MLD requests a TXOP from its associated AP, the non-AP MLD may include a More Data subfield in an Ack or BlockAck frame that it sends to the associated AP. Upon receiving the More Data subfield included in the Ack or BlockAck frame from the STA, the associated AP may trigger the non-AP STA to perform UL transmission and may send a MU-RTS TXS trigger frame with the TXOP sharing mode set to 2 or 1 to the STA. In other words, the More Data subfield in the Ack or BlockAck may be used to indicate to the AP that the non-AP STA already has packets that need to be sent in its buffer.

[0143] According to one embodiment, referring to other embodiments described herein, a STA belonging to a non-AP MLD may send a More Data subfield to an associated AP MLD via a first link between the APMLD and the non-AP MLD, wherein the More Data subfield may indicate that a TXOP is requested by the non-AP MLD for data transmission on a second link between the same AP MLD and the non-AP MLD.

[0144] According to one embodiment, if the AP MLD has a delay-sensitive packet in its buffer, the non-AP STA or STA affiliated with the non-AP MLD may send a More Data subfield in an Ack or BlockAck frame to the associated AP or AP MLD. Including the More Data subfield in the Ack or BlockAck frame may be an indication that the transmitting STA or non-AP MLD has delay-sensitive traffic in its buffer, and may be an indication that the non-AP STA or non-AP MLD requests a TXOP (e.g., a MU-RTS TXS trigger frame with the TXOP sharing mode set to 2 or 1). According to one embodiment, if the STA does not have any packets in its buffer or if the STA has packets in the buffer that are not delay-sensitive, the non-AP STA may not include the More Data subfield in the Ack or BlockAck frame to request a TXOP or request a trigger frame from the AP for UL transmission of the non-AP STA.

[0145] Fig.24 A flowchart of a method 2400 for wireless communication performed by a non-AP device including a first non-AP STA according to an embodiment of the present disclosure is shown. Fig.24 The embodiment of the method 2400 for wireless communication performed by a non-AP MLD shown in FIG. 2 is for illustration. Other embodiments of the method 2400 for wireless communication performed by a non-AP MLD may be used without departing from the scope of the present disclosure.

[0146] like Fig.24 As shown, method 2400 begins at step 2402, where a link is formed with a first AP. At step 2404, a first P2P link is formed with a second non-AP STA. At step 2406, a request associated with a TXOP is sent to the AP. At step 2408, information associated with the TXOP is received from the AP. At step 2410, it is determined whether the received information associated with the TXOP can be used for UL communication or for both UL communication and P2P communication.

[0147] In one embodiment, the request includes a TXS request for requesting a MU-RTS trigger frame associated with sending the first STA traffic to the second non-AP STA.

[0148] In one embodiment, the TXS request includes a control frame type.

[0149] In one embodiment, the first non-AP STA forms a second P2P link with a third non-AP STA, and the request associated with the TXOP requests the TXOP to enable communication over the first P2P link and the second P2P link.

[0150] In one embodiment, the request associated with the TXOP includes a P2P BSR frame including a buffer status indicating the P2P traffic.

[0151] In one embodiment, the request associated with the TXOP includes a QoS characteristics element.

[0152] In one embodiment, the non-AP device is a first non-AP MLD, the first STA is one of a first plurality of STAs in the first non-AP MLD, the second STA is one of a second plurality of STAs in a second non-AP MLD, and the AP is one of a plurality of APs in an AP MLD, wherein the first STA: forms a link with a corresponding AP of the AP MLD, forms a P2P link with a corresponding second STA of the second non-AP MLD, sends a request associated with a TXOP to a corresponding AP of the AP MLD, receives information associated with the TXOP from one of the APs of the AP MLD, and determines whether the received information associated with the TXOP can be used for UL communication or for both UL communication and P2P communication.

[0153] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods or processes shown in the flow charts. For example, although shown as a series of steps, various steps can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0154] Although the present disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A first non-access point (AP) device, include: A first station (STA), including a transceiver; and at least one processor operatively coupled to the transceiver, Wherein, at least one processor is configured to control the transceiver to: sending a request associated with a transmit opportunity (TXOP) to the first AP, receiving information associated with the TXOP from the first AP, and performing uplink (UL) communication or both UL communication and peer-to-peer (P2P) communication based on the received information, Herein, UL communication is performed on a link formed with a first AP, and P2P communication is performed on a first P2P link formed with a second STA included in a second non-AP device.

2. The first non-AP device according to claim 1, in, The request associated with the TXOP includes a TXOP share (TXS) request for requesting a multi-user request to send (MU-RTS) trigger frame associated with transmission of the P2P traffic to the second STA.

3. The first non-AP device according to claim 2, in, The TXS request includes a control frame type.

4. The first non-AP device according to claim 1, in, A request associated with the TXOP requests the TXOP to enable communication on the first P2P link and the second P2P link, and The second P2P link is formed with a third STA included in a third non-AP device.

5. The first non-AP device according to claim 1, in, The request associated with the TXOP includes a P2P buffer status report (BSR) frame including a buffer status indicating the P2P traffic.

6. The first non-AP device according to claim 1, in, The request associated with the TXOP includes a Quality of Service (QoS) characteristics element.

7. The first non-AP device according to claim 1, in: The first non-AP device is a first non-AP multi-link device (MLD), The second non-AP device is a second non-AP MLD. The first STA is one of the first plurality of STAs included in the first non-AP MLD, The second STA is one of the second plurality of STAs included in the second non-AP MLD, The first AP is one of the plurality of APs in the AP MLD.

8. The first non-AP device according to claim 1, in, The at least one processor is configured to: if the received information indicates that the first STA uses the TXOP for UL communication, perform UL communication, or In a case where the received information indicates that the first STA uses the TXOP for both UL communication and P2P communication, both UL communication and P2P communication are performed.

9. A method of wireless communication performed by a first non-access point (AP) multi-link device (MLD) comprising a first station (STA), the method include: sending a request associated with a transmit opportunity (TXOP) to the first AP; receiving information associated with the TXOP from the first AP; as well as performing uplink (UL) communication or both UL communication and peer-to-peer (P2P) communication based on the received information, Herein, UL communication is performed on a link formed with a first AP, and P2P communication is performed on a first P2P link formed with a second STA included in a second non-AP device.

10. The method according to claim 9, in, The request associated with the TXOP includes a TXOP share (TXS) request for requesting a multi-user request to send (MU-RTS) trigger frame associated with transmission of the P2P traffic to the second STA.

11. The method according to claim 10, in, The TXS request includes a control frame type.

12. The method according to claim 9, in, A request associated with the TXOP requests the TXOP to enable communication on the first P2P link and the second P2P link, and The second P2P link is formed with a third STA included in a third non-AP device.

13. The method according to claim 9, in, The request associated with the TXOP includes a P2P buffer status report (BSR) frame including a buffer status indicating the P2P traffic.

14. The method according to claim 9, in, The request associated with the TXOP includes a Quality of Service (QoS) characteristics element.

15. The method according to claim 9, in: The first non-AP device is a first non-AP multi-link device (MLD), The second non-AP device is a second non-AP MLD. The first STA is one of the first plurality of STAs included in the first non-AP MLD, The second STA is one of the second plurality of STAs included in the second non-AP MLD, and The first AP is one of the plurality of APs in the AP MLD.