TID-to-link mapping for TDLS direct links

Abstract

Current TID-to-Link (T2L) mapping is limited to mapping in the UL / DL directions only. We teach a mechanism that can extend the R-TWT feature to configure R-TWT membership on TDLS links while providing T2L mapping for TDLS links. Using T2L mapping for TDLS links, we can distinguish different traffic with different priorities and direct them over different TDLS direct links, thereby reducing interference on any single link and allocating RTA traffic to channels with higher bandwidth and less traffic congestion.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Patent Application No. 18 / 428,124, filed January 31, 2024, which is incorporated herein by reference in its entirety. This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 488,431, filed March 3, 2023, which is incorporated herein by reference in its entirety. This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 584,241, filed September 21, 2023, which is incorporated herein by reference in its entirety. This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 608,883, filed December 12, 2023, which is incorporated herein by reference in its entirety.

[0002] STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT Not applicable

[0003] Notification of copyrighted material Portions of the material in this patent document may be subject to copyright protection under the copyright laws of the United States and other countries. The copyright owner has no objection to the reproduction by any third party of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office publicly available files or records, but otherwise reserves all copyright rights. The copyright owner does not hereby waive any of its rights to have this patent document maintained in secrecy, including, but not limited to, the right pursuant to 37 CFR § 1.14.

[0004] The techniques of this disclosure relate generally to wireless communications when supporting peer-to-peer (P2P) transmissions, and more particularly to an enhanced protocol for addressing related communication issues. [Background technology]

[0005] Current wireless communication technologies supporting peer-to-peer (P2P) traffic communication have limited capabilities for splitting different traffic with different TIDs across different types of links and designating traffic with a specific TID(s) over a single P2P direct link during R-TWT SP. Thus, there is a need for a communication apparatus and protocol that addresses these traffic identifier (TID)-to-link mapping limitations and lack of TID specificity. The present disclosure fulfills this need and provides additional benefits over existing systems. Summary of the Invention

[0006] This paper describes an enhanced protocol that uses a traffic identifier (TID)-to-link (T2L) mapping scheme for tunneled direct link setup (TDLS) of direct links. Using T2L mapping for TDLS links, we extend the R-TWT feature to configure R-TWT membership on TDLS links. Additionally, using T2L mapping for TDLS links, different traffic with different priorities can be carried over different TDLS direct links to reduce interference on a single link and allocate RTA traffic to a clearer, wider channel.

[0007] Further aspects of the technology described herein will become apparent in the remainder of this specification, and this detailed description is intended to fully disclose preferred embodiments of the technology without limiting them.

[0008] The techniques described herein will be better understood by reference to the following drawings, which are for illustrative purposes only. [Brief explanation of the drawings]

[0009] [Figure 1]FIG. 2 is a block diagram of communication station hardware in accordance with at least one embodiment of the present disclosure. [Figure 2] FIG. 1 is a block diagram of multi-link device (MLD) hardware in accordance with at least one embodiment of the present disclosure. [Figure 3] FIG. 2 is a topology diagram of a basic service set considered in a described example in accordance with at least one embodiment of the present disclosure. [Figure 4] FIG. 1 is a communication diagram of a single-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 5] FIG. 1 is a communication diagram of a single-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 6] FIG. 1 is a communication diagram of a single-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 7] FIG. 1 is a communication diagram of a multi-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 8] FIG. 1 is a communication diagram of a multi-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 9] FIG. 1 is a communication diagram of a multi-link TDLS direct link setup in accordance with at least one embodiment of the present disclosure. [Figure 10] FIG. 1 is a communication diagram of negotiation during a multi-link TDLS direct link setup, in accordance with at least one embodiment of the present disclosure. [Figure 11] FIG. 1 is a communication diagram of negotiation during a multi-link TDLS direct link setup, in accordance with at least one embodiment of the present disclosure. [Figure 12] FIG. 1 is a communication diagram of negotiation during a multi-link TDLS direct link setup, in accordance with at least one embodiment of the present disclosure. [Figure 13] FIG. 10 is a communication diagram of negotiating over a TDLS direct link after a TDLS direct link is set up, in accordance with at least one embodiment of the present disclosure. [Figure 14]FIG. 10 is a communication diagram of negotiating over a TDLS direct link after a TDLS direct link is set up, in accordance with at least one embodiment of the present disclosure. [Figure 15] FIG. 10 is a communication diagram of negotiating over a TDLS direct link after a TDLS direct link is set up, in accordance with at least one embodiment of the present disclosure. [Figure 16] FIG. 1 is a communication diagram for configuring an R-TWT over a peer-to-peer (P2P) link, in accordance with at least one embodiment of the present disclosure. [Figure 17] FIG. 1 is a communication diagram for configuring an R-TWT over a peer-to-peer (P2P) link, in accordance with at least one embodiment of the present disclosure. [Figure 18] FIG. 10 is a flow diagram for processing a received TDLS discovery / configuration request by an AP, in accordance with at least one embodiment of the present disclosure. [Figure 19] 1 is a flow diagram of an initiating STA performing TID-to-link mapping in accordance with at least one embodiment of the present disclosure. [Figure 20] 1 is a flow diagram of an initiating STA performing TID-to-link mapping in accordance with at least one embodiment of the present disclosure. [Figure 21] 1 is a flow diagram of a P2P STA responding to a request frame in accordance with at least one embodiment of the present disclosure. [Figure 22] FIG. 22 is a data field diagram of a TID-to-link control field format element within the T_D-to-link mapping element of FIG. 21 in accordance with at least one embodiment of the present disclosure. [Figure 23] FIG. 10 is a data field diagram of a TID-to-link mapping control field in accordance with at least one embodiment of the present disclosure. [Figure 24] FIG. 24 is a data field diagram of a restricted TWT (R-TWT) traffic information field added to the R-TWT traffic information format of FIG. 23 in accordance with at least one embodiment of the present disclosure. [Figure 25]FIG. 25 is a data field diagram of the traffic information control field shown in FIG. 24 in accordance with at least one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0010] 1. Conventional wireless communication Current wireless communications, in the current draft P802.11be_D3.0, use Traffic Identifiers (TIDs) and TID-to-link (T2L) mappings limited to the uplink (UL) and / or downlink (DL) directions only. In a TID-to-link mapping element, the direction subfield of the TID-to-link control field is set to "0" if the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on the downlink. This direction subfield is set to "1" if the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on the uplink. This field is set to "2" if the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on both the downlink and uplink. The value of 3 is reserved.

[0011] Tunneled Direct Link Setup (TDLS) is characterized by encapsulating setup frames in data frames, allowing frames to be transmitted transparently through an access point (AP). A station (STA) that establishes a TDLS direct link remains associated with its basic service set (BSS) but has the option of transmitting frames directly to other TDLS peer STAs. Sending a TDLS frame through an AP means that the frame's receiver address (RA) is set to the BSS's identification (BSSID). Sending a frame via the direct path (whether a TDLS frame or another frame) means that the frame's RA is set to the TDLS peer STA's Media Access Control (MAC) address. In the baseline IEEE 802.11 specification, the link identifier element contains information that identifies the TDLS direct link. The information used to identify the TDLS direct link includes the BSSID of the BSS of which the TDLS initiator STA is a member, the MAC address of the TDLS initiator STA, and the MAC address of the TDLS responder STA. Draft P802.11be_D3.0 defines the Link ID as a numerical value corresponding to a tuple (a tuple is an ordered sequence of values) applied to the TDLS Direct Link ID, in this case consisting of the operating class, operating channel and BSSID of the APs belonging to the AP MLD.

[0012] R-TWT was introduced in 802.11be. An R-TWT scheduling AP is an EHT AP with dot11TWTOptionActivated equal to true that sets the Restricted TWT Support subfield to "1" in a transmitted Very High Throughput (EHT) Capabilities element. An R-TWT scheduled STA is a non-AP EHT STA that sets the Restricted TWT Support subfield to "1" in a transmitted EHT Capabilities element and sends and receives broadcast TWT elements carrying one or more restricted TWT parameter sets fields to and from the R-TWT scheduling AP. A non-AP EHT STA establishes membership in one or more R-TWT schedules with the associated EHT AP. An EHT AP with dot11RestrictedTWTOptionImplemented equal to true can advertise one or more R-TWT SPs. An R-TWT SP is established between an R-TWT scheduling AP and an R-TWT member non-AP STA(s) to provide a specific traffic identifier (TID)(s) carrying delay-sensitive traffic on the R-TWT member's uplink (UL) and / or downlink (DL). Thus, if a TID is not found or is no longer mapped to the link on which the R-TWT membership was established, the corresponding R-TWT membership is considered torn down.

[0013] 2. Problem statement While traditional communications utilizes Traffic Identifiers (TIDs) to provide TID-to-Link (T2L) mapping for UL and DL, there is no further mapping capability to map TIDs to Tunneled Direct Link Setup (TDLS). Without T2L mapping to TDLS direct links, it becomes difficult to establish Reserved-Target Wait Time (R-TWT) membership on TDLS direct links. Currently, R-TWT membership can only be configured on DL or UL.

[0014] Without T2L mapping to TDLS direct links, when a multi-link TDLS direct link is established between a pair of TDLS direct links, traffic with different priorities cannot be directed on different TDLS direct links due to the lack of T2L mapping capability.

[0015] The latest draft P802.11be_D5.0 does not specify how to prevent triggered TXOP sharing procedures within an R-TWT SP. However, fairness issues may arise if only R-TWT TID(s) are specified for UL and / or DL ​​traffic, but not for P2P traffic that is assigned to use a shared TXOP period.

[0016] 3. Contribution of this Disclosure This disclosure seeks to extend the R-TWT feature to enable configuration of R-TWT membership on TDLS links by providing a TID-to-link mapping scheme for TDLS direct links. By providing T2L mapping for TDLS links, different traffic can be differentiated with different priorities on different TDLS direct links to reduce interference on specific links and allocate RTA traffic to clearer, wider channels.

[0017] 4. Hardware Implementation 4.1. Communication Station (STA and MLD) Hardware FIG. 1 illustrates an example embodiment 10 of STA hardware configured to execute the protocol of the present disclosure. An external I / O connection 14 couples to an internal bus 16 of circuitry 12, on which a CPU 18 and memory (e.g., RAM) 20 are preferably connected for executing program(s) implementing the communications protocol. The host machine contains at least one modem 22 supporting communications, coupled to at least one RF module 24, 28, each connected to one or more antennas 29, 26a, 26b, 26c-26n. RF modules with multiple antennas (e.g., antenna arrays) enable beamforming during transmission and reception. In this manner, the STA can transmit signals using multiple sets of beam patterns.

[0018] The bus 14 can connect various devices, such as sensors and actuators, to the CPU. Executing on the processor 18 are instructions from memory 20 for executing programs that implement communication protocols that are executed to enable the STAs to perform the functions of an access point (AP) station or a regular station (non-AP STA). It should also be understood that this programming is configured to operate in different modes (TXOP owner, TXOP sharing participant, source, intermediate, destination, first AP, other AP, station associated with first AP, station associated with other AP, coordinator, coordinatee, AP in OBSS, STA in OBSS, etc.) depending on what role it plays in the current communication situation.

[0019] Thus, the illustrated STA HW comprises at least one modem and associated RF circuitry for providing communications on at least one band. It should be understood that the present disclosure may be configured using multiple modems 22, each coupled to any number of RF circuits. In general, the more RF circuits used, the greater the coverage of the antenna beam directions. It should be understood that the number of RF circuits and antennas utilized is determined by the hardware constraints of a particular device. Some of the RF circuits and antennas may be disabled when a STA determines that it does not need to communicate with neighboring STAs. In at least one embodiment, the RF circuitry includes a frequency converter, an array antenna controller, etc., and is connected to multiple antennas that are controlled to perform beamforming for transmission and reception. In this manner, a STA may transmit signals using a set of multiple beam patterns, with each beam pattern direction considered an antenna sector.

[0020] It should also be understood that multiple instances of station hardware such as that shown in this figure can be combined into a multi-link device (MLD), which typically has a processor and memory for coordinating activity, but that these resources can be shared, so that separate CPUs and memory are not always required for each STA within an MLD.

[0021] FIG. 2 shows an example embodiment 40 of a multi-link device (MLD) hardware configuration. A "soft AP MLD" is an MLD consisting of one or more STAs that operate as an AP. The soft AP MLD should support multiple radio operations, such as 2.4 GHz, 5 GHz, and 6 GHz. A basic link set among the multiple radios is a link pair that satisfies simultaneous transmit / receive (STR) mode, such as a basic link set (2.4 GHz and 5 GHz) or a basic link set (2.4 GHz and 6 GHz).

[0022] A conditional link is a link that forms a non-simultaneous transmission and reception (NSTR) link pair with some fundamental link. For example, these link pairs can include a 6 GHz link as a conditional link corresponding to the 5 GHz link when 5 GHz is the fundamental link, and can include a 5 GHz link as a conditional link corresponding to the 6 GHz link when 6 GHz is the fundamental link. Soft APs are used in different scenarios, including Wi-Fi hotspots and tethering.

[0023] An MLD has multiple STAs attached to it, each operating on a different frequency link. The MLD has external I / O access to applications, which connects to an MLD management entity 48 having a CPU 62 and memory (e.g., RAM) 64 to enable the execution of program(s) that implement the communication protocol at the MLD level. The MLD can distribute tasks to its attached stations, illustrated here as STA1 42, STA2 44 through STA N 46, collect information from them, and share that information among its attached STAs.

[0024] In at least one embodiment, each STA in the MLD has its own CPU 50 and memory (RAM) 52, which are coupled via a bus 58 to at least one modem 54 connected to at least one RF circuit 56 having one or more antennas. In this example, the RF circuit has multiple antennas 60a, 60b, 60c-60n, such as in the form of an antenna array. The modem in combination with the RF circuit and associated antenna(s) transmits / receives data frames to / from nearby STAs. In at least one implementation, the RF module includes a frequency converter, an array antenna controller, and other circuitry for interfacing with the antennas.

[0025] It should be understood that each STA in an MLD does not necessarily require its own processor and memory, as they may share resources with each other and / or with an MLD management entity depending on the particular MLD implementation. It should be understood that the above MLD diagram is provided by way of example and not limitation, and that the present disclosure can work with a wide variety of MLD implementations.

[0026] 5. Topology Figure 3 illustrates an example STA / MLD topology utilized in the examples of this disclosure. Unless otherwise specified, the examples in this disclosure are based on this topology. It should be understood that this disclosure is not limited to any particular topology, and the topology of this figure is provided merely to simplify the explanation of the disclosed protocol enhancements.

[0027] The BSS under consideration consists of an AP MLD 74, a non-AP STA10 82, and three non-AP MLDs 76, 78, and 80. In this example, the AP MLD 74 has three associated APs: AP1 84, AP2 86, and AP3 88, operating on Link 1 (L1), Link 2 (L2), and Link 3 (L3), respectively. Non-AP MLD1 76 has three associated STAs: STA1 90, STA2 92, and STA3 94, operating on Link 1 (L1), Link 2 (L2), and Link 3 (L3), respectively. Non-AP MLD2 78 has three associated STAs: STA4 96, STA5 98, and STA6 100, operating on Link 1 (L1), Link 2 (L2), and Link 3 (L3), respectively. Non-AP MLD3 80 has three associated STAs, STA7 102, STA8 104, and STA9 106, operating on Link 1 (L1), Link 2 (L2), and Link 3 (L3), respectively. Non-AP STA10 82 operates on Link 1 (L1). STA1, STA4, STA7, and non-AP STA10 are associated with AP1. STA2, STA5, and STA8 are associated with AP2. STA3, STA6, and STA9 are associated with AP3.

[0028] 6. TID-to-Link Mapping for TDLS / P2P Link(s) If a TID is mapped to a set of enabled TDLS direct peer-to-peer (P2P) links between a non-AP MLD and its peer non-AP MLD, the non-AP MLD can use any link in this set of enabled P2P links to transmit individually addressed MAC Service Data Units (MSDUs) or aggregated MSDUs (A-MSDUs) corresponding to this TID that are destined (intended) for its peer non-AP MLD. Under the default mapping mode, all TIDs are mapped to all configured links, DL, UL, and P2P, and all configured links are enabled.

[0029] 6.1. Negotiation of TID-to-Link Mapping for TDLS Direct Link(s) This disclosure describes two methods for negotiating TID-to-link mapping for TDLS direct link(s), including negotiation during TDLS direct link setup and negotiation after TDLS direct link setup.

[0030] 6.2.Negotiation during TDLS Direct Link Setup The following describes the steps involved in setting up a single-link TDLS direct link.

[0031] The non-AP MLD initiator SHOULD include TID-To-Link Mapping Negotiation Support and TID-to-link mapping information in the TDLS discovery request frame and / or TDLS configuration request frame, or any other frame sent to the associated AP MLD or P2P peer non-AP MLD during TDLS configuration as described in Sections 9.2 and 9.4. The P2P peer non-AP MLD SHOULD include TID-To-Link Mapping Negotiation Support, status code, and TID-to-link mapping information in the TDLS discovery response frame and / or TDLS configuration response frame, or any other frame sent to the associated AP MLD or mapping initiator non-AP MLD during TDLS configuration as described in Sections 9.3 and 9.5. It should be understood that the TID-to-link mapping established is for a single TDLS direct link only.

[0032] When a Multilink TDLS direct link is set up over a single link, the following applies: The negotiation initiator EHT non-AP MLD should include TID-to-link mapping negotiation support and TID-to-link mapping information in the TDLS discovery request frame and / or TDLS configuration request frame, or any other frame to be sent to the associated AP MLD or P2P peer non-AP MLD during TDLS configuration. The peer non-AP MLD should include TID-to-link mapping negotiation support, status code, and TID-to-link mapping information in the TDLS discovery response frame and / or TDLS configuration response frame, or any other necessary frame to be sent to the associated AP MLD or mapping initiator non-AP MLD during TDLS configuration. It should be understood that in this case, the TID-to-link mapping is for the Multilink TDLS direct link.

[0033] 6.2.1. Example of Negotiation During Single-Link TDLS Direct Link Setup 4-6 illustrate example embodiments 110, 130, and 150 of a single-link TDLS direct link setup. These figures show communication between non-AP MLD1 76, which includes STA1 90, STA2 92, and STA3 94, and AP MLD 74, which includes AP1 84, AP2 86, and AP3 88, and non-AP MLD2 78, which includes STA4 96, STA5 98, and STA6 100.

[0034] In Figure 4, during the TDLS Setup Request procedure, TDLS setup requests are performed independently on Link 1 (L1) and Link 2 (L2). On L1, STA1 sends a TDLS setup request frame to AP1, carrying information requesting that TID X be mapped to L1 (112). AP1 receives the TDLS setup request frame from STA1 and forwards the received request information to STA4 in a TDLS setup request frame 116. On Link 2 (L2), STA2 sends a TDLS setup request frame to AP2, carrying information requesting that TID Y be mapped to L2 (114). AP1 receives the TDLS setup request frame from STA1 and forwards the received request information to STA5 in a TDLS setup request frame 118.

[0035] In Figure 5, a TDLS configuration response procedure is performed, with TDLS configuration responses being performed independently on L1 and L2. On L1, STA4 responds to AP1 with a TDLS configuration response frame carrying information about accepting the requested mapping 136 of TID X to L1. AP1 receives the TDLS configuration response frame from STA4 and forwards the received response acceptance information 132 to STA1 in a TDLS configuration response frame. On L2, STA5 responds to AP2 with a TDLS configuration response frame indicating that it prefers to map TID Y to L1 (138). AP2 receives the TDLS configuration response frame from STA6 and forwards the received response information 134 to STA2 in a TDLS configuration response frame.

[0036] In Figure 6, during TDLS link transmission(s), transmissions are performed independently on L1 and L2. On L1, a mapping of TID X to L1 has been established, so STA1 transmits data for TID X on L1 to STA4 (152). On L2, a mapping of TID Y to L2 has not been established, so no transmission on L2 (154) is indicated until a mapping of TID Y to L2 has been established.

[0037] Returning to L1, STA1 may negotiate (156) the mapping of TID Y to L1 with STA4 after the TID-to-link mapping negotiation results on L2 after transmission 134 is performed, by exchanging corresponding negotiation request and response information in a TID-to-link mapping request frame and a TID-to-link mapping response frame, respectively.

[0038] 6.2.2. Example of negotiation during Multilink TDLS direct link setup (all mappings accepted) 7-9 show examples 170, 190, and 210 of multilink TDLS direct link configurations for L1, L2, and L3 that can be negotiated over a single link, such as L1. These figures show communication between non-AP MLD1 76, which has STA1 90, STA2 92, and STA3 94, and AP MLD 74, which has AP1 84, AP2 86, and AP3 88, and non-AP MLD2 78, which has STA4 96, STA5 98, and STA6 100.

[0039] 7, during the TDLS configuration request procedure, a TDLS configuration request is performed on L1. On L1, STA1 sends a TDLS configuration request frame to AP1, carrying mapping request information to map TID X to L1 172, TID Y to L2 174, and TID Z to L3 176. AP1 receives the TDLS configuration request frame from STA1 and forwards the received request information 178, 180, 182 to STA4 in the TDLS configuration request frame.

[0040] 8, during the TDLS Setup Response procedure, a TDLS Setup Response is performed on L1. On L1, STA4 responds to AP1 with a TDLS Setup Response frame carrying information accepting (194) the requested mapping of TID X to L1, TID Y to L2, and TID Z to L3. AP1 receives the TDLS Setup Response frame from STA4 and forwards the received response information to STA1 in the TDLS Setup Response frame.

[0041] 9, in TDLS link transmission(s), transmissions are performed independently on L1, L2, and L3. On L1, a mapping of TID X to L1 has been established, so STA1 transmits data 212 for TID X on L1 to STA4. On L2, a mapping of TID Y to L2 has been established, so STA2 transmits data 214 for TID Y on L2 to STA5. On L3, a mapping of TID Z to L3 has been established, so STA3 transmits data 216 for TID Z on L3 to STA6.

[0042] 6.2.3. Example of negotiation during Multilink TDLS direct link setup (partial mapping accepted) 10-12 show examples 230, 250, 270 of multilink TDLS direct link configurations for L1, L2, and L3 that can be negotiated over a single link, in this example L1. These figures show communication between non-AP MLD1 76 with STA1 90, STA2 92, and STA3 94 and AP MLD 74 with AP1 84, AP2 86, and AP3 88, and non-AP MLD2 78 with STA4 96, STA5 98, and STA6 100.

[0043] 10, during the TDLS setup request procedure, a TDLS setup request is performed on L1. On L1, STA1 transmits a TDLS setup request frame to AP1, carrying information requesting mapping of TID X to L1 (232), TID Y to L2 (234), and TID Z to L3 (236). AP1 receives the TDLS setup request frame from STA1 and forwards the received request information 238, 240, and 242 to STA4 in the TDLS setup request frame.

[0044] 11, during the TDLS Setup Response procedure, a TDLS Setup Response is generated on L1 such that STA4 responds to AP1 with a TDLS Setup Response frame carrying information regarding acceptance of the requested mapping 252 of TID X to L1, the desired change in the TID-to-link mapping 254 of TID Y to L3, and a different mapping 256 of TID Z to L2. AP1 receives the TDLS Setup Response frame from STA4 and forwards the received response information 258, 260, and 262 to STA1 in the TDLS Setup Response frame.

[0045] In Figure 12, during TDLS link transmission(s), transmissions are performed independently on L1, L2, and L3. On L1, a mapping of TID X to L1 has been established, so STA1 transmits data for TID X on L1 to STA4 (272). On L2, a mapping of TID Y to L2 has not been established, so STA2 must not transmit data for TID Y on L2 to STA5. Similarly, on L3, a mapping of TID Z to L3 has not been established, so STA3 must transmit data for TID Z on L3 to STA6.

[0046] STA2 can negotiate the mapping of TID Z to L2 with STA5 (274) by exchanging corresponding negotiation request and response information in TID-to-link mapping request and TID-to-link mapping response frames, respectively, based on the TID-to-link mapping negotiation result on L1 after transmission 272 is performed. Similarly, STA3 can negotiate the mapping of TID Y to L3 with STA6 (276) by exchanging corresponding negotiation request and response information in TID-to-link mapping request and TID-to-link mapping response frames, respectively, based on the TID-to-link mapping negotiation result on L1 after transmission 272 is performed.

[0047] 6.3.Negotiation using TDLS Direct Link after TDLS Direct Link is set up An initiating non-AP MLD that supports TID-to-link mapping sends individually addressed TID-to-link mapping request frames to P2P peer non-AP MLDs that have indicated support for TID-to-link mapping negotiation.

[0048] By including TID-to-link mapping negotiation support in the TDLS discovery request frame and the TDLS discovery response frame, the exchange of support for TID-to-link mapping negotiation can be achieved during the TDLS direct link setup.

[0049] The P2P peer non-AP MLD MUST send an individually addressed TID-to-link mapping response frame to the negotiation-initiating non-AP STA MLD containing an indication of whether it accepts the requested TID-to-link mapping in the TID-to-link mapping element in the received TID-to-link mapping request frame, or an indication that it rejects the proposed TID-to-link mapping, or an indication that it proposes a preferred mapping that is different from the requested TID-to-link mapping in the TID-to-link mapping element in the received TID-to-link mapping request frame.

[0050] The negotiation-initiating non-AP STA MLD SHOULD consider the peer MLD's preferred TID-to-link mapping. When two non-AP MLDs are negotiating TID-to-link mapping, either of these MLDs can tear down the negotiated P2P TID-to-link mapping by sending an individually addressed TID-to-link Mapping Teardown frame. After the teardown, these MLDs MUST operate in the default mapping mode.

[0051] 6.3.1. Example of Negotiation via TDLS Direct Link after TDLS Direct Link Setup 13-15 show examples 290, 310, and 330 of multilink TDLS direct link configurations for L1, L2, and L3 established between non-AP MLD1 and non-AP MLD2, and between non-AP MLD1 and non-AP MLD3. These figures show communication between non-AP MLD1 76, which has STA1 90, STA2 92, and STA3 94, and non-AP MLD2 78, which has STA4 96, STA5 98, and STA6 100, and non-AP MLD3 80, which has STA7 102, STA8 104, and STA9 106.

[0052] 13, during the TID-to-link mapping request procedure, TID-to-link mapping requests are sent independently on L1 and L2. On L1, STA1 sends a TID-to-link mapping request frame to STA7, carrying information requesting that TID X be mapped (294) to L1. On L2, STA2 sends a TID-to-link mapping request frame to STA5, carrying information requesting that TID Y be mapped (292) to L2 and L3.

[0053] 14, it can be seen that during the TID-to-link mapping response procedure, the TID-to-link mapping responses are performed independently on L1 and L2. On L1, STA7 responds to STA1 with a TID-to-link mapping response frame carrying information regarding the requested mapping of TID X to L1 314. On L2, STA5 responds to STA2 with a TID-to-link mapping response frame carrying information regarding the requested mapping of TID Y to L2 and the acceptance 312 of the mapping of TID Y to L3.

[0054] In Figure 15, during TDLS link transmission(s), transmissions are performed independently on L1, L2, and L3. On L1, a mapping of TID X to L1 has been established, so STA1 transmits data for TID X on L1 to STA7 (336). On L2, a mapping of TID Y to L2 has been established, so STA2 transmits data for TID Y on L2 to STA5 (332). On L3, a mapping of TID Y to L3 has been established, so STA3 transmits data for TID Y on L2 to STA6 (334).

[0055] 7. Setting up P2P links 7.1. R-TWT Configuration over P2P Links Using TID-to-link mapping on a multilink TDLS / P2P link, an R-TWT may also set up a P2P link using an embodiment that incorporates the following: Adding a Restricted TWT P2P TID Bitmap field to the Restricted TWT Traffic Info field as defined in Section 9.6 TWT Element, and Adding a P2P TID Bitmap Valid subfield to the Traffic Info Control field as defined in Section 9.6 TWT Element.

[0056] An R-TWT requesting STA sends an R-TWT request frame to its associated AP indicating that the R-TWT is for a specific TID(s) on an established P2P link with a P2P peer STA. The TID(s) negotiated for the R-TWT MUST be included in the TID(s) mapped to the P2P link.

[0057] The R-TWT scheduling AP may send an unsolicited R-TWT response frame to the P2P peer STA to pass on the R-TWT request / proposed schedule from the R-TWT requesting STA.

[0058] A peer STA that receives an unsolicited R-TWT response frame can either accept the requested / proposed schedule by responding with an R-TWT response frame indicating acceptance of the schedule, or continue R-TWT negotiation with the R-TWT scheduling AP by sending an R-TWT response frame indicating a different R-TWT parameter set, or reject the requested / proposed schedule by responding with an R-TWT response frame indicating rejection of the schedule.

[0059] The R-TWT scheduling AP should forward (send) the response from the peer STA to the R-TWT requesting STA so that the R-TWT requesting STA can update its negotiated R-TWT parameters based on the response received from the R-TWT scheduling AP.

[0060] During an R-TWT SP on a P2P link, both the R-TWT requesting STA and its P2P peer STAs may be considered R-TWT member STAs and may send P2P traffic with the R-TWT TID to each other, or only the R-TWT requesting STA may be considered an R-TWT member STA and may send P2P traffic with the R-TWT TID to its P2P peer STAs.

[0061] In draft P802.11REVme_D3.0, the TDLS Configuration Request frame and the TDLS Configuration Response frame can include TWT element information. However, given the restriction in Table 9-499 of the information for the TDLS Configuration Request Action field in draft P802.11REVme_D3.0 that "the Trigger subfield and Negotiation Type subfield of the TWT element are set to 0," the TWT element is not a broadcast TWT element. It should be understood that the TDLS Configuration Request frame and the TDLS Configuration Response frame can be configured to carry TWT element information with the Negotiation Type subfield of the TWT element set to a value of "2" and / or "3," respectively, to indicate that the TWT element provides a broadcast TWT schedule in broadcast management frames or individually addressed management frames. Alternatively, in at least one embodiment, the TDLS Configuration Request frame and the TDLS Response frame can also be configured to include TWT element information for R-TWT, which has the TWT element proposed in 9.6 TWT Element of this disclosure. In this case, during the TDLS link setup phase, the R-TWT on the P2P link can also be set up through the exchange of a TDLS setup request frame and a TDLS setup response frame.

[0062] A P2P communicating peer STA that establishes an R-TWT SP for any P2P transmission mentioned in this section MUST conform to the values ​​indicated in the P2P TID Bitmap Valid subfield and the Restricted TWT Traffic Information field as described in Section 9.6 of this disclosure.

[0063] 7.1.1. Example of R-TWT configuration over P2P link 16 and 17 illustrate an example embodiment 350 of R-TWT configuration over a P2P link. Communication is shown between AP MLD 74, which includes AP1 84, AP2 86, and AP3 88, non-AP MLD1 76, which includes STA1 90, STA2 92, and STA3 94, and non-AP MLD3, which includes STA4 96, STA5 98, and STA6 100.

[0064] STA1 sends an R-TWT request frame 352 to AP1 to propose / request the establishment of an R-TWT SP with ID:X on the P2P link established between STA1 and STA4. The requested R-TWT SP is for P2P traffic with TID:N.

[0065] After receiving the R-TWT request frame from STA1, AP1 sends an unsolicited R-TWT response to STA4 with an R-TWT configuration command field indicating that it accepts the R-TWT (354), and assigns the R-TWT(ID:X) schedule requested by STA1 to STA4.

[0066] STA4 receives an unsolicited R-TWT response from AP1 with an R-TWT configuration command field indicating acceptance of the TWT. STA4 then transmits an R-TWT response 356 with a TWT configuration command field indicating TWT acceptance to accept the R-TWT(ID:X) schedule requested by STA1.

[0067] AP1 receives an R-TWT response frame from STA4, which sent an R-TWT response frame to STA1 with a TWT configuration command field indicating R-TWT acceptance (357).

[0068] AP1 broadcasts a beacon frame 358 carrying an R-TWT element 360 to indicate R-TWT SP(ID:X). STA1 and STA4 awaken and receive the beacon frame to determine their R-TWT(ID:X). During R-TWT(ID:X), the AP transmits a basic trigger frame 363 to STA1 and STA4. STA1 indicates its awakening by transmitting a PS-Poll 364, and STA2 indicates its awakening by transmitting a QoS Null frame 366 in response to the basic trigger frame. AP1 transmits a multi-STA Block Ack 365 in response to the Poll.

[0069] STA1 transmits P2P traffic 368 with TID:N to STA4 within R-TWT(ID:X) 362 and receives a Block Ack 370 frame from STA4. STA4 then transmits P2P traffic 372 with TID:N to STA1 and receives a Block Ack frame 374 from STA1. Also shown are ongoing beacons 376, 378 from AP1.

[0070] 7.2. Triggered TXOP sharing procedure enabled P2P transmission in R-TWT SP The following describes two embodiments of an R-TWT scheduling AP and an R-TWT scheduled STA that support the R-TWT feature and the triggered TXOP sharing feature.

[0071] In a first embodiment, either the R-TWT scheduling AP or the R-TWT scheduled STA should specify that triggered TXOP sharing-enabled P2P transmissions are not allowed in the negotiated R-TWT SP, in which case the restricted TWT traffic information field format and traffic information control field format should reuse the frame format designed in draft 802.11be D5.0.

[0072] In the second embodiment, either the R-TWT scheduling AP or the R-TWT scheduled STA should specify that TXOP sharing enabled P2P transmission is allowed in the negotiated R-TWT SP, in which case the restricted TWT traffic information field format and traffic information control field format should be designed as introduced in Section 9.6.

[0073] The capability of whether triggered TXOP sharing enabled P2P transmissions should be allowed within the R-TWT SP can be specified by an attribute such as dot11TXOPSharingEnabledP2PInRtwt. If this attribute value is set to true, the STA shall support P2P transmissions enabled by the triggered TXOP sharing procedure within the R-TWT SP. If this attribute is set to false, the STA does not support P2P transmissions enabled by the triggered TXOP sharing procedure within the R-TWT SP. If no such attribute is specified, it can be assumed by default that the STA supports P2P transmissions enabled by the triggered TXOP sharing procedure within the R-TWT SP.

[0074] The above-mentioned capability attribute value of "dot11TXOPSharingEnabledP2PInRtwt" can be specified at any stage before the initiation of R-TWT SP and / or before the initiation of the triggered TXOP sharing procedure.

[0075] 8. Flow Diagram 18 illustrates an example embodiment 410 in which an AP receives a TDLS discovery or configuration request. Check 412 determines whether a discovery / configuration request frame carrying TID-to-link mapping request information has been received. If the condition is not met, processing ends. Otherwise, execution reaches block 414, which transmits the TID-to-link mapping request information to a P2P peer STA by using a TDLS discovery / configuration request frame.

[0076] Next, it is determined whether the AP received a TDLS discovery / configuration response frame carrying TID-to-link mapping response information at check 416. If the frame was not received, then block 418 waits for a response and then repeats check 416 (timeout logic not shown for simplicity).

[0077] If the condition is met, then in block 420, the AP forwards the TID-to-link mapping response information to the TID-to-link mapping initiator STA in a TDLS discovery / configuration request frame, and the process ends.

[0078] 19 and 20 illustrate an example embodiment 450 of TID-to-link mapping for an initiating STA. At check 452, it is determined whether a TDLS configuration has been established. If not, at block 454, the requestor conveys TID-to-link mapping request information in a TDLS discovery / configuration request frame in a communication addressed to the associated AP.

[0079] Next, check 456 determines whether a TDLS discovery / configuration frame has been received containing information that the P2P peer STA has accepted the TID-to-link mapping request information. If the condition is not met, block 458 transmits a TID-to-link mapping request frame to the P2P peer STA over the P2P link, and execution proceeds to check 462 of FIG. 20.

[0080] At check 462, it is determined whether the P2P peer STA has received a TID-to-link mapping response frame indicating that it has accepted the TID-to-link mapping request information. If so, at block 460, the TID-to-link mapping is established and the process ends.

[0081] On the other hand, if the condition is not met, check 464 determines whether the initiating STA should continue negotiating the TID-to-link mapping. If the condition is not met, processing ends. Otherwise, execution proceeds to block 458 of FIG. 19, previously described.

[0082] Considering check 456 of FIG. 19, if the condition is met, execution proceeds to block 460 of FIG. 20 where the TID-to-link mapping is established, after which processing terminates.

[0083] 21 illustrates an example embodiment 490 of operations performed by a P2P peer STA. Check 492 determines whether a TDLS configuration has been established. If so, processing ends. Otherwise, check 494 determines whether a TDLS discovery / configuration request frame has been received indicating TID-to-link mapping request information for the P2P link.

[0084] If so, in block 496, the P2P STA responds by sending TID-to-link mapping response information to the AP in a TDLS discovery / configuration response frame, and the process ends. Otherwise, in check 498, it is determined whether a TID-to-link mapping request frame indicating TID-to-link mapping request information on the P2P link was received. If the condition is not met, the process ends. Otherwise, in block 500, the P2P STA responds by sending TID-to-link mapping response information to the TID-to-link mapping initiator STA in a TID-to-link mapping response frame, and the process ends.

[0085] 9. Frame Format 9.1 TID-to-Link Mapping Elements FIG. 22 illustrates, by way of example and not limitation, a TID-to-link mapping element 510 including the following fields: Element ID, Length, Element ID Extension, TID-to-link Mapping Control, Mapping Switch Time, Expected Duration, and Link Mapping of TIDs, representing any TID from TID 0 to TID 7.

[0086] FIG. 23 illustrates the contents of the TID-to-Link Mapping Control field shown in FIG. 22, with the subfields Direction, Default Link Mapping, Mapping Switch Time Present, Expected Duration Present, Link Mapping Size, Reserved, and (optional) Link Mapping Presence Indicator.

[0087] Setting the direction subfield of the TID-to-link control field of a TID-to-link mapping element to a value such as "3" indicates that the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on the TDLS direct link. The other fields are the same as those defined in the draft P802.11REVme_D3.0 specification.

[0088] Note that in the TID-to-Link Mapping element, the Link Mapping field (n=0, 1, ..., 7) for any TID n indicates the link(s) that are allowed to transmit frames belonging to TID n. A value of "1" in bit position i (i=0, 1, ..., 14) of the Link Mapping field for TID n indicates that TID n is mapped to the link associated with Link ID i in the direction specified in the Direction subfield. A value of "0" in bit position i indicates that TID n is not mapped to the link associated with Link ID i. This field is not present if the Default Link Mapping subfield is set to "1".

[0089] The link ID of a TDLS link is used to provide link ID information in the link mapping field of TID n in the TID-to-link mapping element. Based on the draft P802.11be_D3.0, the link ID is defined as a numerical value corresponding to a tuple consisting of the operating class, operating channel, and BSSID of an AP belonging to the AP MLD.

[0090] 9.2 TDLS Discovery Request Frame Table 1 shows the information in the TDLS discovery request action field. Insert a new row in the TDLS discovery request action field table. The TID-to-link mapping negotiation support field indicates what the STA that sent this frame supports for TID-to-link mapping negotiation. The TID-to-link mapping field contains TID-to-link mapping elements that indicate the TDLS direct links that can exchange frames belonging to each TID.

[0091] 9.3 TDLS Discovery Response Frame Table 2 shows the information in the TDLS discovery response action field. Insert a new row in the TDLS discovery response action field table. TID-to-link mapping negotiation supported indicates that the STA sent information in this frame to support TID-to-link mapping negotiation. The status code is used to indicate whether the requested TID-to-link mapping information carried in the received TDLS discovery request frame addressed to the receiver is accepted or rejected, or whether the receiver has proposed a preferred mapping. The TID-to-link mapping information field contains a TID-to-link mapping element that indicates the preferred mapping on the TDLS direct link.

[0092] 9.4 TDLS Configuration Request Frame Table 3 shows the information in the TDLS Configuration Request Action field. Insert a new row in the TDLS Configuration Request Action field. The TID-to-Link Mapping Negotiation Support indicates what the STA that sent this frame supports for TID-to-Link Mapping negotiation. The TID-to-Link Mapping field contains TID-to-Link Mapping elements that indicate the TDLS direct links that can exchange frames belonging to each TID.

[0093] 9.5 TDLS Configuration Response Frame Table 4 shows the information in the TDLS Configuration Response Action field with the addition of a new row of information. TID-to-Link Mapping Negotiation Support indicates what the STA that sent this frame supports for TID-to-Link mapping negotiation. The Status Code is used to indicate whether the requested TID-to-Link mapping information carried in the received TDLS Discovery Request frame addressed to the receiver is accepted or rejected, or whether the receiver has proposed a preferred mapping. The TID-to-Link Mapping Information field contains a TID-to-Link Mapping element that indicates the preferred mapping on the TDLS direct link.

[0094] 9.6 TWT Element 24 shows the Restricted TWT P2P traffic information field 550 with the following subfields: This element incorporates the restricted TWT P2P TID bitmap subfield, which already contains a traffic information control field, a restricted TWT DL TID bitmap subfield, and a restricted TWT UL TID bitmap subfield.

[0095] Figure 25 shows the contents of the Traffic Information Control field shown in Figure 24, with the following subfields: This field format already includes a DL TID bitmap valid subfield, a UL TID bitmap valid subfield, and a reserved subfield, to which a P2P TID Bitmap Valid subfield is added.

[0096] The P2P TID Bitmap Valid subfield, when set to a first state (e.g., "1"), indicates that the Restricted TWT P2P TID Bitmap field is valid; otherwise, it is set to a second state (e.g., "0"), indicating that P2P traffic for all TIDs mapped in the P2P link to the link on which R-TWT membership is established is identified as delay-sensitive traffic and the Restricted TWT P2P TID Bitmap field is spare.

[0097] It should be understood that the proposed frame formats as defined in Figures 24 and 25 are still required when R-TWT is not configured on the P2P direct link and / or when TID-to-link mapping is not applied to the P2P direct link. For example, when the Triggered TXOP Sharing procedure is utilized and the Triggered TXOP Sharing Mode subfield value is equal to "2," the AP, for example, shares a portion of the TXOP with P2P transmissions occurring within the R-TWT SP. To mitigate potential fairness issues, in addition to specifying the Restricted TWT TID in the UL and / or DL, the Restricted TWT TID should also be specified on the P2P direct link. In this context, the P2P TID Bitmap Valid subfield is set to a first state (e.g., "1") to indicate that the Restricted TWT P2P TID Bitmap field is valid. A P2P TID Bitmap Valid subfield set to a second state (e.g., "0") can have different interpretations, such as indicating that P2P traffic for all TIDs is identified as delay-sensitive traffic, or that all TIDs mapped on the UL or DL ​​to the link for which R-TWT membership is indicated by the set TWT element and P2P traffic for the same TID is identified as delay-sensitive traffic. The interpretation of these data field values ​​can depend on the application. When the P2P TID Bitmap Valid subfield is set to a second state (e.g., "0"), the Limited TWT P2P TID Bitmap field is reserved.

[0098] The Restricted TWT P2P TID Bitmap subfield specifies the TID(s) that the R-TWT scheduling AP or the R-TWT scheduled STA identifies as a delay-sensitive traffic stream in the P2P direction. When this subfield is set to a first state (e.g., “1”) at bit position k in the bitmap, it indicates that TID k is classified as a delay-sensitive traffic stream, and when this value is set to a second state (e.g., “0”), it indicates that TID k is not classified as a delay-sensitive traffic stream.

[0099] The P2P TID Bitmap Valid subfield and the Limited TWT Traffic Information field may be set during the R-TWT configuration procedure over a P2P link as proposed in Section 7.1, or may be set for triggered TXOP-enabled P2P transmissions within an R-TWT SP as proposed in Section 7.2. In either case, P2P communicating peer STAs MUST abide by the values ​​indicated in the P2P TID Bitmap Valid subfield and the Limited TWT Traffic Information field as proposed in this section.

[0100] 10. General Scope of Embodiments Embodiments of the technology of the present disclosure may be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the technology. Embodiments of the technology of the present disclosure may also be described with reference to procedures, algorithms, steps, operations, formulas, or other computational representations, which may be included within flowchart illustrations or otherwise described herein. It will be understood that any of the foregoing may also be implemented as computer program instructions. In this regard, each block or step of a flowchart, and combinations of blocks (and / or steps) of a flowchart, and any procedure, algorithm, step, operation, formula, or computational representation, may be implemented by various means, such as hardware, firmware, and / or software that includes one or more computer program instructions embodied in the form of computer-readable program code. It will be understood that any such computer program instructions may be executed by one or more computer processors, including, but not limited to, a general-purpose computer or a special-purpose computer, or any other programmable processing device for producing a machine, such that the computer program instructions executing on the computer processor or other programmable processing device produce means for performing the specified function(s).

[0101] Thus, the flowchart blocks and procedures, algorithms, steps, operations, formulas, or computational expressions described herein support combinations of means for performing a particular function(s), combinations of steps for performing a particular function(s), and computer program instructions for performing a particular function(s) as embodied in computer-readable program code logic means. It will also be understood that each flowchart block and any procedures, algorithms, steps, operations, formulas, or computational expressions described herein, and combinations thereof, can also be implemented by a dedicated hardware-based computer system that performs the particular function(s) or step(s), or a combination of dedicated hardware and computer-readable program code.

[0102] Furthermore, these computer program instructions, embodied in computer-readable program code or the like, may be stored in one or more computer-readable memories or memory devices that can direct a computer processor or other programmable processing device to function in a particular manner, such that the instructions stored in these computer-readable memories or memory devices produce an article of manufacture that includes instruction means for performing the functions specified in the flowchart(s). The computer program instructions may be executed by the computer processor or other programmable processing device to cause a series of operational steps to be performed on the computer processor or other programmable processing device to generate a computer-implemented process, such that the instructions executing on the computer processor or other programmable processing device provide steps for performing the function specified in the flowchart(s) block(s), procedure(s), algorithm(s), step(s), operation(s), mathematical formula(s), or computational expression(s).

[0103] Furthermore, as used herein, the terms "program" or "program executable" will be understood to mean one or more instructions executable by one or more computer processors to perform one or more functions described herein. The instructions may be embodied in software, firmware, or a combination of software and firmware. The instructions may be stored locally on a non-transitory medium of the device or remotely, such as on a server, or all or a portion of the instructions may be stored locally or remotely. Remotely stored instructions may be downloaded (pushed) to the device upon user initiation or automatically based on one or more factors.

[0104] Furthermore, as used herein, the terms controller, microcontroller, processor, microprocessor, hardware processor, computer processor, central processing unit (CPU), and computer are used interchangeably to refer to devices capable of executing instructions and communicating with input / output interfaces and / or peripheral devices, and it will be understood that the terms controller, microcontroller, processor, microprocessor, hardware processor, computer processor, CPU, and computer are intended to include single or multiple devices, single-core devices and multi-core devices, and variations thereof.

[0105] From the description herein, it will be understood that the present disclosure encompasses multiple technology implementations, including but not limited to the following.

[0106] 1. An apparatus for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each connected to one or more antennas; (b) the stations (STAs) being independent STAs or STAs in a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN), (e) the instructions, when executed by the processor, cause (e) (i) the STA to communicate with other STAs as an access point (AP) STA or a non-AP STA using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless communication protocol. and (e)(ii) an Extremely High Throughput (EHT) STA is capable of implementing mapping a traffic identifier (TID) to a Tunneled Direct Link Setup (TDLS) direct link; and (e)(iii) setting a direction subfield of a TID-to-link control field of a TID-to-link mapping element to a value indicating that the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on the TDLS direct link.

[0107] 1. An apparatus for communicating in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each connected to one or more antennas; (b) the stations (STAs) being independent STAs or STAs within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN), wherein (e) the instructions, when executed by the processor, perform steps of a wireless communication protocol, including: (e)(i) the STA operating as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless communication protocol; and (e)(ii) performing negotiation of a traffic identifier (TID)-to-link mapping for a tunneled direct link setup (TDLS) direct link during TDLS direct link setup.

[0108] 1. An apparatus for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each connected to one or more antennas; (b) the stations (STAs) being independent STAs or STAs in a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN), wherein (e) the instructions, when executed by the processor, cause (e)(i) the STA to operate as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless communication protocol; and (e)(ii) a negotiation initiator non-AP STA that supports TID-to-link mapping after establishment of a TDLS direct link. and performing, as an MLD, negotiation of TID-to-link mapping for the TDLS direct link, and transmitting an individually addressed TID-to-link mapping request frame to a P2P peer non-AP MLD indicating support for the TID-to-link mapping negotiation.

[0109] 1. An apparatus for communicating in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each connected to one or more antennas; (b) the stations (STAs) being independent STAs or STAs within a multi-link device (MLD); (c) a processor at the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN), wherein (e) the instructions, when executed by the processor, cause (e)(i) the STA to operate as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless communication protocol; and (e)(ii)(A) ​​a limited TWT P2P traffic information field specifying TID(s) identified by an R-TWT scheduling AP or an R-TWT scheduled STA as a delay-sensitive traffic stream in the P2P direction. and (e)(ii)(B) adding a P2P TID Bitmap Enabled subfield to a Traffic Information Control field, the P2P TID Bitmap Enabled subfield indicating whether a Restricted TWT P2P TID Bitmap field is enabled.

[0110] 1. An apparatus for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each connected to one or more antennas; (b) the stations (STAs) being independent STAs or STAs in a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN), the instructions, when executed by the processor, causing: (e)(i) the STA to operate as either an access point (AP) STA or a non-AP STA communicating with other STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless communication protocol; and (e)(ii) a R-TWT. and performing, within the SP, a peer-to-peer (P2P) direct link transmission including either (e)(ii)(A) ​​adding a restricted target wake time (R-TWT) P2P traffic identifier (TID) bitmap field in the R-TWT traffic information field, the R-TWT traffic identifier (TID) bitmap specifying TID(s) in the P2P direct link direction identified by the R-TWT scheduling AP or the R-TWT scheduled STA, and (e)(ii)(B) adding a P2P TID bitmap valid subfield in the traffic information control field, the P2P TID bitmap valid subfield indicating whether the restricted TWT P2P TID bitmap field is valid.

[0111] An apparatus for communicating in a wireless network in which an EHT STA can map TID(s) to a TDLS direct link by implementing: (a) setting a direction subfield of a TID-to-link control field of a TID-to-link mapping element to a value such as 3 to indicate that the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on the TDLS direct link; (b) in some cases, indicating an ability to support TID-to-link mapping negotiation for the TDLS direct link(s) with a signal design; and (c) using a default mapping mode in which all TIDs are mapped to all configured links of DL, UL, and P2P and all configured links are enabled.

[0112] 1. An apparatus for communication in a wireless network, capable of processing negotiation of TID-to-link mapping for a TDLS direct link during TDLS direct link setup, the apparatus comprising: (a) when negotiating TID-to-link mapping during single-link TDLS direct link setup, (i) a negotiation initiator EHT STA MLD can include TID-to-link mapping negotiation support and TID-to-link mapping information in a TDLS discovery request frame and / or a TDLS setup request frame, or other frame transmitted to an associated AP MLD or a P2P peer non-AP MLD during TDLS setup, (A) the TID-to-link mapping field includes a TID-to-link mapping element indicating a TDLS direct link over which frames belonging to each TID can be exchanged; and (ii) the peer non-AP MLD can include TID-to-link mapping negotiation support and TID-to-link mapping information in a TDLS discovery response frame and / or a TDLS setup response frame, or other frame transmitted to an associated AP MLD or a P2P peer non-AP MLD during TDLS setup, (B) including TID-to-link mapping negotiation support, a status code, and TID-to-link mapping information in any other frame sent back to the MLD; (B) the status code indicates whether the requested TID-to-link mapping information carried in the received TDLS discovery / configuration request frame or other frame addressed to the receiver was accepted, rejected, or a preferred mapping was proposed by the peer non-AP MLD; (C) the TID-to-link mapping information indicates the preferred mapping of TID(s) on the TDLS direct link; and (iii) in some cases, the TID-to-link mapping negotiation support is provided to the peer non-AP MLD.A device indicating that MLD supports TID-to-link mapping negotiation, and (iv) in some cases, the TID-to-link mapping negotiation is for a single-link TDLS direct link, and (b) when negotiating TID-to-link mapping on a multi-link TDLS direct link set over a single link, some procedures are reused with the further rule that the TID-to-link mapping negotiation is for a multi-link TDLS direct link.

[0113] An apparatus for communication in a wireless network capable of processing negotiation of TID-to-link mapping for a TDLS direct link after a TDLS direct link setup, the apparatus comprising: (a) a negotiation initiator non-AP STA MLD supporting TID-to-link mapping transmits an individually addressed TID-to-link mapping request frame to a P2P peer non-AP MLD that has indicated support for the TID-to-link mapping negotiation; (b) during the TDLS direct link setup, the exchange in support of the TID-to-link mapping negotiation is achieved by including TID-to-link mapping negotiation support in exchanged frames; (c) the P2P peer non-AP MLD transmits an individually addressed TID-to-link mapping response frame to the negotiation initiator non-AP STA MLD indicating whether to accept the requested TID-to-link mapping, reject the proposed TID-to-link mapping, or propose a preferred mapping different from the requested TID-to-link mapping; and (d) a negotiation initiator non-AP STA MLD transmits an individually addressed TID-to-link mapping response frame to the negotiation initiator non-AP STA MLD indicating whether to accept the requested TID-to-link mapping, reject the proposed TID-to-link mapping, or propose a preferred mapping different from the requested TID-to-link mapping. An apparatus, wherein an MLD should consider the preferred TID-to-link mapping of a peer MLD, and (e) when two non-AP MLDs have negotiated a TID-to-link mapping, either MLD can dismantle the negotiated P2P TID-to-link mapping by sending an individually addressed TID-to-link mapping dismantle frame.

[0114] 1. An apparatus for communicating in a wireless network in which R-TWT membership configuration is enabled on TDLS link(s), the R-TWT membership configuration including: (a) adding, to a restricted TWT traffic information field, a restricted TWT P2P TID bitmap field that specifies TID(s) that are identified as delay-sensitive traffic streams in the P2P direction by an R-TWT scheduling AP or an R-TWT scheduled STA, wherein a first value (e.g., “1”) in bit position k of the bitmap indicates that TID k is classified as a delay-sensitive traffic stream, and a second value (e.g., “0”) in bit position k of the bitmap indicates that TID k is not classified as a delay-sensitive traffic stream; and b) adding, to a traffic information control field, a P2P TID bitmap enable subfield that indicates whether the restricted TWT P2P TID bitmap field is enabled, wherein the P2P TID bitmap enable subfield, when set to a first state (e.g., “1”), indicates that the restricted TWT P2P TID bitmap field is enabled, and The TID Bitmap Valid subfield, when set to a second state (e.g., “0”), indicates that P2P traffic of all TIDs in the P2P link to the link on which the R-TWT membership is established is identified as delay-sensitive traffic, and the Limited TWT P2P TID Bitmap field is reserved; and (c) the R-TWT requesting STA sends an R-TWT request frame to the associated AP to request the R-TWT membership.(d) the SP indicates that the R-TWT is for a specific TID(s) on an established P2P link with a P2P peer STA; (d) the TID(s) negotiated for the R-TWT are within the range of TID(s) mapped to that P2P link; (e) the R-TWT scheduling AP may send an unsolicited R-TWT response frame to the P2P peer STA to forward the R-TWT request / proposed schedule from the R-TWT requesting STA; and (f) a peer STA that receives an unsolicited R-TWT response frame may forward the requested / proposed schedule by responding with an R-TWT response frame indicating acceptance. (g) the R-TWT scheduling AP should forward the response from the peer STA to the R-TWT requesting STA, and the R-TWT requesting STA can update the negotiated R-TWT parameters based on the response from the R-TWT scheduling AP; and (h) during an R-TWT SP on a P2P link, both the R-TWT requesting STA and its P2P peer STA can be considered R-TWT member STAs and be able to send P2P traffic with the R-TWT TID to each other, or it is also possible that only the R-TWT requesting STA can be considered an R-TWT member STA and be able to send P2P traffic with the R-TWT TID to the P2P peer STA.

[0115] The apparatus of any preceding implementation, further including: performing a default mapping mode in which all TIDs are mapped to all configured links for downlink (DL), uplink (UL), and peer-to-peer (P2P) and all configured links are enabled.

[0116] The apparatus of any preceding implementation, further including signaling a capability of TID-to-link mapping negotiation support for the TDLS direct link(s) with the signal design.

[0117] The apparatus of any preceding implementation, further including negotiating TID-to-link mapping during TDLS direct link setup by including TID-to-link mapping negotiation support and TID-to-link mapping information in a frame sent by the negotiation initiator EHT STA MLD to an associated AP MLD or sent to a peer non-AP MLD during TDLS setup in peer-to-peer (P2P) mode.

[0118] The device of any preceding implementation, wherein the TID-to-link mapping negotiation support for TDLS direct link(s), and the TID-to-link mapping information is transmitted in a TDLS discovery request frame.

[0119] 10. The apparatus of any preceding implementation, wherein the TID-to-link mapping negotiation support for TDLS direct link(s), and the TID-to-link mapping information is transmitted in a TDLS configuration request frame.

[0120] The TID-to-link mapping field includes a TID-to-link mapping element indicating the TDLS direct links over which frames belonging to each TID can be exchanged.

[0121] The device of any preceding implementation, wherein the peer non-AP MLD includes TID-to-link mapping negotiation support, status code, and TID-to-link mapping information.

[0122] The device of any preceding implementation, wherein the TID-to-link mapping negotiation support, status code, and TID-to-link mapping information are included in a TDLS discovery response frame, and / or a TDLS configuration response frame, or other frame sent back to an associated AP MLD or a mapping-initiating non-AP MLD during TDLS configuration.

[0123] The status code indicates the requested TID-to-link mapping information carried in frames addressed to the receiver, which can be accepted or rejected, or can be a suggested preferred mapping provided by a peer non-AP MLD device in any prior implementation.

[0124] In any prior implementation, the TID-to-link mapping information is carried in a received TDLS discovery or configuration request frame, or other frame addressed to the receiver.

[0125] 10. The apparatus of any preceding implementation, wherein the TID-to-link mapping information indicates preferred TID mapping(s) on the TDLS direct link.

[0126] A device of any preceding implementation in which the exchange of support for TID-to-link mapping negotiation is performed during TDLS direct link setup and includes TID-to-link mapping negotiation support in the exchanged frames.

[0127] The device of any preceding implementation, wherein the P2P peer non-AP MLD sends an individually addressed TID-to-link mapping response frame to the negotiation-initiating non-AP STA MLD indicating whether it accepts the requested TID-to-link mapping, rejects the proposed TID-to-link mapping, or proposes a preferred mapping that differs from the requested TID-to-link mapping.

[0128] In any prior implementation, the negotiation-initiating non-AP STA MLD considers whether to accept the peer MLD's preferred TID-to-link mapping.

[0129] When two non-AP MLDs negotiate a TID-to-link mapping, either MLD can dismantle the negotiated P2P TID-to-link mapping by sending an individually addressed TID-to-link mapping dismantling frame, and after the dismantling, this MLD operates in the default mapping mode, in any prior implementation of the device.

[0130] The apparatus of any preceding implementation, wherein an R-TWT requesting STA sends an R-TWT request frame to an associated AP indicating that the R-TWT SP is for a particular TID(s) on an established P2P link with a P2P peer STA.

[0131] The TID(s) negotiated for R-TWT are within the range of TID(s) mapped to the P2P link in any prior implementation of the device.

[0132] The apparatus of any preceding implementation, wherein the R-TWT scheduling AP sends an unsolicited R-TWT response frame to a P2P peer STA to forward a request or proposed R-TWT schedule from an R-TWT requesting STA.

[0133] The apparatus of any preceding implementation, wherein the peer STA receives an unsolicited R-TWT response frame and determines whether to accept the requested or proposed schedule by responding with an R-TWT response frame indicating acceptance, or the peer STA continues R-TWT negotiation with the R-TWT scheduling AP by sending an R-TWT response frame indicating a different R-TWT parameter set, or the peer STA rejects the requested or proposed schedule by responding with an R-TWT response frame indicating rejection.

[0134] The R-TWT scheduling AP forwards the response from the peer STA to the R-TWT requesting STA, as in any preceding implementation.

[0135] The device of any preceding implementation, wherein the R-TWT requesting STA updates the negotiated R-TWT parameters based on what response it receives from the R-TWT scheduling AP.

[0136] A device of any preceding implementation, in which an R-TWT requesting STA exchanges TDLS configuration request frames and TDLS configuration response frames with a P2P peer STA through its AP to which it belongs in order to configure an R-TWT SP for P2P transmission.

[0137] In any preceding implementation, the TDLS Configure Request frame and the TDLS Configure Response frame carry information about the TWT element in which the Negotiation Type subfield of the TWT element is set to a value of "2" and / or "3".

[0138] An apparatus of any preceding implementation, wherein during an R-TWT SP on a P2P link, if it is determined that both the R-TWT requesting STA and its P2P peer STA are considered to be R-TWT member STAs, the R-TWT requesting STA and its P2P peer STA can send P2P traffic having an R-TWT TID to each other.

[0139] The apparatus of any preceding implementation, wherein during an R-TWT SP on a P2P link, if it is determined that only an R-TWT requesting STA is considered an R-TWT member STA, the R-TWT requesting STA can send P2P traffic having an R-TWT TID to a P2P peer STA.

[0140] An apparatus of any preceding implementation, wherein the P2P TID Bitmap Valid subfield indicates an invalid value if (A) P2P traffic for all TIDs is identified as delay-sensitive traffic, or (B) P2P traffic for the same TID as all TIDs mapped in the UL or DL ​​to the link on which the R-TWT membership indicated by the TWT element is established is identified as delay-sensitive traffic.

[0141] The P2P TID Bitmap Valid subfield indicates an invalid value if the R-TWT P2P TID Bitmap field is reserved, as in any prior implementation of the device.

[0142] The term "implementation," as used herein, is intended to include, without limitation, any embodiment, example, or other form for practicing the techniques described herein.

[0143] As used herein, the singular forms "a," "an," and "the" include plural references unless the context clearly indicates otherwise. Reference to an object in the singular does not mean "one and only one" unless expressly stated otherwise, but rather "one or more."

[0144] In this disclosure, phrases such as "A, B, and / or C" indicate that either A, B, or C, or any combination of items A, B, and C, can be present. Phrases such as "at least one of" followed by a group of listed elements indicate that at least one of the group of elements is present, including, where applicable, any possible combination of the listed elements.

[0145] References in this disclosure to "one embodiment," "at least one embodiment," or similar embodiment phrases indicate that a particular feature, structure, or characteristic described in connection with the described embodiment is included in at least one embodiment of the disclosure. Thus, these references to various embodiments do not necessarily refer to all the same embodiment, or to a specific embodiment that is different from all other embodiments described. Reference to an embodiment should be interpreted to mean that the particular feature, structure, or characteristic of a given embodiment can be combined in any suitable manner in one or more embodiments of the disclosed device, system, or method.

[0146] As used herein, the term "set" means a collection of one or more objects. Thus, for example, a set of objects can include a single object or multiple objects.

[0147] Use of relative terms such as first and second, top and bottom, etc. in this document is used merely to distinguish one entity or action from another and does not necessarily require or imply any such actual relationship or ordering between such entities or actions.

[0148] The terms "comprises, compris- ing, has, having, includes, including, contains, containing," or any other variations of these terms, are intended to cover non-exclusive inclusions, and thus a process, method, article, apparatus, or system that comprises, has, or includes a list of elements does not include only those elements, but may also include other elements not expressly listed or that are inherent to such process, method, article, apparatus, or system. An element following "comprises ... a, has ... a, includes ... a, or contains ... a" does not exclude, without further constraint, the presence of additional identical elements in the process, method, article, apparatus, or system that comprises, has, or includes that element.

[0149] As used herein, the terms “approximately,” “approximate,” “substantially,” “substantial,” “essentially,” and “about,” or any variation thereof, are used to describe and explain slight variations. When used in connection with events or circumstances, these terms can mean that the events or circumstances will definitely occur and that the events or circumstances are highly likely to occur. When used in connection with a numerical value, these terms can mean a variation range of ±10% or less, such as ±5% or less, ±4% or less, ±3% or less, ±2% or less, ±1% or less, ±0.5% or less, ±0.1% or less, or ±0.05% or less of the numerical value. For example, “substantially” aligned can mean an angular variation range of ±10° or less, such as ±5° or less, ±4° or less, ±3° or less, ±2° or less, ±1° or less, ±0.5° or less, ±0.1° or less, or ±0.05° or less.

[0150] Additionally, amounts, ratios, and other numerical values ​​may be presented in range format herein. Such range formats are used for convenience and simplicity, and should be understood to include numerical values ​​explicitly specified as the limits of the range, but also to include all individual numerical values ​​or subranges within the range, as if each such numerical value and subrange were expressly set forth. For example, a ratio within the range of about 1 to about 200 should be understood to include the explicitly recited limits of about 1 and about 200, but also to include individual ratios such as about 2, about 3, and about 4, as well as subranges such as about 10 to about 50 and about 20 to about 100.

[0151] The term "coupled," as used herein, is defined as connected, but not necessarily by a direct mechanical connection. A device or structure that is "configured" in a particular way is configured in at least that way, but may also be configured in unlisted ways.

[0152] Benefits, advantages, solutions to problems, and any element(s) that cause or make more pronounced any benefit, advantage, or solution should not be construed as a critical, necessary, or essential feature or element of the technology described herein or any or all of the claims.

[0153] Also, in the foregoing disclosure, various features may be grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Inventive subject matter may comprise less than all features of a single disclosed embodiment.

[0154] The Abstract of the Disclosure is intended to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

[0155] It is understood that some jurisdictions have a practice of requiring the deletion of one or more portions of the disclosure after filing. Accordingly, the reader should refer to the application as of its filing date for the original content of the disclosure. The deletion of any of the disclosed content should not be construed as an abandonment, forfeiture, or dedication to the public of any subject matter of the application as originally filed.

[0156] The following claims are hereby incorporated into this disclosure, with each claim standing on its own as a separate inventive subject matter.

[0157] Although the description herein contains many details, these should not be construed as limiting the scope of the disclosure, but merely as exemplifying some of the presently preferred embodiments, and therefore, the scope of the disclosure will be understood to fully encompass other embodiments that may become apparent to those skilled in the art.

[0158] Structural and functional equivalents of elements of embodiments of the present disclosure known to those skilled in the art are also expressly incorporated herein by reference and are intended to be within the scope of the claims. Furthermore, no elements, components, or method steps of the present disclosure are intended to be publicly disclosed, regardless of whether they are explicitly recited in the claims. No claim element herein should be construed as a "means-plus-function" element unless the element is expressly recited using the phrase "means for." Also, no claim element herein should be construed as a "step-plus-function" element unless the element is expressly recited using the phrase "step for." [Explanation of symbols]

[0159] 412 Was a TDLS discovery / configuration request frame received that carries TID-to-link mapping request information? 414: Transmits TID-to-link mapping request information to P2P peer STA via TDLS discovery / configuration request frame 416 Was a TDLS discovery / configuration response frame received that carries TID-to-link mapping response information? Waiting for 418 response 420: Transmit TID-to-link mapping response information to the TID-to-link mapping initiator STA via a TDLS discovery / configuration request frame. Table 1 TDLS Discovery Request Action Field TIFF2026507193000002.tif28155 Table 2 TDLS discovery response frame TIFF2026507193000003.tif34155 Table 3 TDLS Configuration Request Action Field TIFF2026507193000004.tif28155 Table 4 TDLS setting response frame TIFF2026507193000005.tif34155

Claims

1. 1. An apparatus for communicating in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) An Very High Throughput (EHT) STA is capable of mapping a Traffic Identifier (TID) to a Tunneled Direct Link Setup (TDLS) direct link by implementing: (iii) setting a direction subfield of a TID-to-link control field of a TID-to-link mapping element to a value indicating that the TID-to-link mapping element provides TID-to-link mapping information for frames transmitted on a TDLS direct link; performing steps of a wireless communication protocol including: An apparatus characterized in that

2. and performing a default mapping mode in which all TIDs are mapped to all configured links for downlink (DL), uplink (UL), and peer-to-peer (P2P) and all configured links are enabled.

10. The apparatus of claim 1.

3. and signaling a capability of TID-to-link mapping negotiation support for the TDLS direct link(s) having the signal design.

10. The apparatus of claim 1.

4. 1. An apparatus for communicating in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) performing a traffic identifier (TID)-to-link mapping negotiation for a tunneled direct link setup (TDLS) direct link during a TDLS direct link setup; performing steps of a wireless communication protocol including: An apparatus characterized in that

5. The method further includes negotiating TID-to-link mapping during the TDLS direct link setup by the negotiation initiator EHT STA MLD including TID-to-link mapping negotiation support and TID-to-link mapping information in a frame sent to an associated AP MLD or sent to a peer non-AP MLD during the TDLS setup in a peer-to-peer (P2P) mode.

5. The apparatus of claim 4.

6. The TID-to-link mapping negotiation support for TDLS direct link(s), and the TID-to-link mapping information is transmitted in a TDLS discovery request frame; 6. The apparatus of claim 5.

7. The TID-to-link mapping negotiation support for TDLS direct link(s), and the TID-to-link mapping information is transmitted in a TDLS setup request frame; 6. The apparatus of claim 5.

8. The TID-to-link mapping field includes a TID-to-link mapping element indicating a TDLS direct link through which frames belonging to each TID can be exchanged; 5. The apparatus of claim 4.

9. The peer non-AP MLD includes TID-to-link mapping negotiation support, status code, and TID-to-link mapping information; 5. The apparatus of claim 4.

10. The TID-to-link mapping negotiation support, status code, and TID-to-link mapping information are included in a TDLS discovery response frame, and / or a TDLS setup response frame, or other frame sent back to the associated AP MLD or mapping initiator non-AP MLD during TDLS setup; 10. The apparatus of claim 9.

11. The status code indicates the requested TID-to-link mapping information to be carried in the frame addressed to the receiver, which can be accepted or rejected, or can be a suggested preferred mapping provided by a peer non-AP MLD.

11. The apparatus of claim 10.

12. the TID-to-link mapping information is carried in a received TDLS discovery or setup request frame or other frame addressed to the receiver; 12. The apparatus of claim 11.

13. the TID-to-link mapping information indicates a preferred TID mapping(s) on the TDLS direct link; 5. The apparatus of claim 4.

14. A station device for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) after the establishment of the TDLS direct link, as a negotiation initiator non-AP STA MLD that supports TID-to-link mapping, perform negotiation of TID-to-link mapping for the TDLS direct link, and send an individually addressed TID-to-link mapping request frame to a P2P peer non-AP MLD that indicates support for TID-to-link mapping negotiation; performing steps of a wireless communication protocol including: An apparatus characterized in that

15. An exchange in support of TID-to-link mapping negotiation is performed during TDLS direct link establishment, and the exchange frame includes the TID-to-link mapping negotiation support; 15. The apparatus of claim 14.

16. the P2P peer non-AP MLD transmits an individually addressed TID-to-link mapping response frame to the negotiation initiator non-AP STA MLD indicating whether to accept the requested TID-to-link mapping, reject the proposed TID-to-link mapping, or propose a preferred mapping that differs from the requested TID-to-link mapping; 15. The apparatus of claim 14.

17. The negotiation initiator non-AP STA MLD considers whether to accept the peer MLD's preferred TID-to-link mapping; 15. The apparatus of claim 14.

18. When two non-AP MLDs negotiate a TID-to-link mapping, either MLD can dismantle the negotiated P2P TID-to-link mapping by sending an individually addressed TID-to-link mapping dismantle frame, and after the dismantlement, the MLD operates in a default mapping mode.

15. The apparatus of claim 14.

19. A station device for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) (A) adding a Restricted TWT P2P TID Bitmap field to the Restricted TWT Traffic Information field, the Restricted TWT P2P TID Bitmap field specifying TID(s) identified as delay-sensitive traffic streams in the P2P direction by the R-TWT scheduling AP or the R-TWT scheduled STA; (B) adding a P2P TID Bitmap Valid subfield to the Traffic Information Control field, which indicates whether the Restricted TWT P2P TID Bitmap field is valid; Enabling R-TWT membership configuration over TDLS link(s) using an implementation including: performing steps of a wireless communication protocol including: An apparatus characterized in that

20. An R-TWT requesting STA sends an R-TWT request frame to an associated AP, indicating that the R-TWT SP is for a specific TID(s) on an established P2P link with a P2P peer STA; 20. The apparatus of claim 19.

21. The TID(s) negotiated for the R-TWT are within the range of TID(s) mapped to the P2P link; 20. The apparatus of claim 19.

22. The R-TWT scheduling AP sends an unsolicited R-TWT response frame to the P2P peer STA to forward the requested or proposed R-TWT schedule from the R-TWT requesting STA; 20. The apparatus of claim 19.

23. The peer STA receives the unsolicited R-TWT response frame and decides whether to accept the requested or proposed schedule by responding with an R-TWT response frame indicating acceptance, or the peer STA continues R-TWT negotiation with the R-TWT scheduling AP by transmitting an R-TWT response frame indicating a different R-TWT parameter set, or the peer STA rejects the requested or proposed schedule by responding with an R-TWT response frame indicating rejection.

23. The apparatus of claim 22.

24. The R-TWT scheduling AP forwards the response from the peer STA to the R-TWT requesting STA; 24. The apparatus of claim 23.

25. The R-TWT requesting STA updates the negotiated R-TWT parameters based on the response received from the R-TWT scheduling AP.

25. The apparatus of claim 24.

26. The R-TWT requesting STA exchanges a TDLS setup request frame and a TDLS setup response frame with a P2P peer STA through the AP to which the R-TWT requesting STA belongs in order to set up an R-TWT SP for P2P transmission; 20. The apparatus of claim 19.

27. The TDLS setup request frame and the TDLS setup response frame carry information about TWT elements whose negotiation type subfields are set to the value of "2" and / or "3".

27. The apparatus of claim 26.

28. During the R-TWT SP on the P2P link, if it is determined that both the R-TWT requesting STA and its P2P peer STA are considered as R-TWT member STAs, the R-TWT requesting STA and its P2P peer STA may transmit P2P traffic with the R-TWT TID to each other; 20. The apparatus of claim 19.

29. During the R-TWT SP on the P2P link, if it is determined that only the R-TWT requesting STA is considered as an R-TWT member STA, the R-TWT requesting STA can send P2P traffic with the R-TWT TID to the P2P peer STA; 20. The apparatus of claim 19.

30. A station device for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) supporting triggered TXOP sharing procedure enabled P2P transmission within the R-TWT SP; and (iii) Within the R-TWT SP, (A) adding a Restricted Target Wake Time (R-TWT) P2P Traffic Identifier (TID) Bitmap field in the R-TWT Traffic Information field, which specifies TID(s) in the P2P direct link direction identified by the R-TWT scheduling AP or the R-TWT scheduled STA; and (B) adding a P2P TID Bitmap Valid subfield to the Traffic Information Control field, which indicates whether the Restricted TWT P2P TID Bitmap field is valid; performing a peer-to-peer (P2P) direct link transmission, including any of performing steps of a wireless communication protocol including: An apparatus characterized in that

31. The P2P TID Bitmap Valid subfield indicates an invalid value if (A) all P2P traffic of all TIDs are identified as delay-sensitive traffic, or (B) all P2P traffic of the same TID as the TID mapped in the UL or DL ​​to the link on which the R-TWT membership indicated by the TWT element is established is identified as delay-sensitive traffic.

31. The apparatus of claim 30.

32. The P2P TID Bitmap Valid subfield indicates an invalid value if the R-TWT P2P TID Bitmap field is reserved; 31. The apparatus of claim 30.

33. The STA can be characterized as supporting triggered TXOP sharing procedure enabled P2P transmission in the R-TWT SP by setting a newly designed attribute value to true.

31. The apparatus of claim 30.

34. The STA sets the newly designed attribute value to true, and its P2P peer STAs must comply with the values ​​indicated in the P2P TID Bitmap Valid subfield and the Restricted TWT Traffic Information field.

32. The apparatus of claim 31.

35. A station device for communication in a wireless network, comprising: (a) at least one modem coupled to at least one radio frequency (RF) circuit, each modem coupled to one or more antennas; (b) the station (STA) is an independent STA or a STA within a multi-link device (MLD); (c) a processor of the STA; and (d) a non-transitory memory storing instructions executable by the processor to wirelessly communicate with other STAs on an IEEE 802.11 wireless local area network (WLAN); and Furthermore, (e) the instructions, when executed by the processor: (i) the STA operates in a wireless communication protocol as either an access point (AP) STA or a non-AP STA that communicates with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism; (ii) the wireless communication protocol does not allow a triggered TXOP sharing procedure to enable P2P transmission within the R-TWT SP; and performing steps of a wireless communication protocol including: An apparatus characterized in that

36. The STA indicates that it does not support triggered TXOP sharing procedure enabled P2P transmission in the R-TWT SP by setting the newly specified attribute value to false; 36. The apparatus of claim 35.

Images