Transmission control method, apparatus, and storage medium

Abstract

Provided in the embodiments of the present application are a transmission control method, a device, and a storage medium. The method comprises: a first non-access point device receiving first information sent by an access point device, wherein the first information is configured to indicate a first target wake time (TWT) service period (SP); in the first TWT SP, P2P transmission is preferentially performed over at least one P2P link; and the at least one link comprises a first P2P link between the first non-access point device and a second non-access point device.

Description

Transmission control method, device, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a transmission control method and device, and a storage medium. Background Art

[0002] The wireless LAN industry is one of the fastest-growing sectors in the data communications sector. As a supplement and extension of traditional wired LANs, wireless LAN solutions have gained widespread adoption among home network users, small and medium-sized offices, enterprises, and telecom operators due to their flexibility, mobility, scalability, and low investment costs.

[0003] The wireless LAN industry is one of the fastest-growing sectors in the data communications sector. As a supplement and extension of traditional wired LANs, wireless LAN solutions have gained widespread adoption among home network users, small and medium-sized offices, enterprises, and telecom operators due to their flexibility, mobility, scalability, and low investment costs.

[0004] The coordinated coexistence of peer-to-peer (P2P) networks and wireless local area networks (WLANs) is one of the key indicators of next-generation WLANs. How to achieve the integration of P2P transmission and WLANs is an urgent problem that needs to be solved.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a transmission control method and device, and a storage medium.

[0007] The transmission control method provided in the embodiment of the present application includes:

[0008] A first non-access point device receives first information sent by an access point device, where the first information is used to indicate a first target wake time (Target Wake Time, TWT) service period (Service Period, SP). During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and a second non-access point device.

[0009] The transmission control method provided in the embodiment of the present application includes:

[0010] The access point device sends first information to a first non-access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

[0011] The first non-access point device provided in an embodiment of the present application includes:

[0012] A first communication unit is configured to receive first information sent by an access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

[0013] The access point device provided in the embodiment of the present application includes:

[0014] A second communication unit is configured to send first information to a first non-access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

[0015] The communication device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the communication device executes the above-mentioned transmission control method.

[0016] The chip provided in the embodiment of the present application is used to implement the above-mentioned transmission control method.

[0017] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned transmission control method.

[0018] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, and the execution of the computer program enables the computer to execute the above-mentioned transmission control method.

[0019] The computer program product provided in the embodiment of the present application includes computer program instructions, and the execution of the computer program instructions enables the computer to execute the above-mentioned transmission control method.

[0020] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned transmission control method.

[0021] Through the above technical solution, the access point device indicates the first TWT SP to the first non-access point device. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, thereby proposing a TWT SP for coordinating P2P transmission, realizing AP scheduling of P2P transmission on at least one P2P link, and improving resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] FIG1A is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0024] FIG1B is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0025] FIG1C is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0026] FIG2 is an optional schematic diagram of the format of the Per-STA Profile sub-element according to an embodiment of the present application;

[0027] FIG3 is an optional schematic diagram of an R-TWT supporting P2P transmission according to an embodiment of the present application;

[0028] FIG4 is an optional schematic diagram of a P2P transmission window according to an embodiment of the present application;

[0029] FIG5 is an optional schematic diagram of enhanced distributed channel access parameter broadcasting in the r-TWT mode according to an embodiment of the present application;

[0030] FIG6 is an optional schematic diagram of a TDLS establishment process according to an embodiment of the present application;

[0031] FIG7 is an optional schematic diagram of MLD establishing a TDLS direct link according to an embodiment of the present application;

[0032] FIG8 is an optional schematic diagram of a TDLS direct link of an MLD according to an embodiment of the present application;

[0033] FIG9 is an optional schematic diagram of transmission of a TDLS establishment request frame of an MLD according to an embodiment of the present application;

[0034] FIG10 is an optional schematic diagram of transmission of a TDLS setup response frame of an MLD according to an embodiment of the present application;

[0035] FIG11 is an optional schematic diagram of a TDLS direct link of an MLD according to an embodiment of the present application;

[0036] FIG12 is an optional schematic diagram of a single TWT operation according to an embodiment of the present application;

[0037] FIG13 is an optional schematic diagram of a broadcast TWT operation according to an embodiment of the present application;

[0038] FIG14 is an optional schematic diagram of frame transmission based on triggering sharing mode 2 according to an embodiment of the present application;

[0039] FIG15 is an optional schematic diagram of a TDLS establishment process according to an embodiment of the present application;

[0040] FIG16 is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0041] FIG17 is an optional flow chart of a transmission control method according to an embodiment of the present application;

[0042] FIG18 is an optional flow chart of a transmission control method according to an embodiment of the present application;

[0043] FIG19 is a schematic diagram of an optional flow chart of a multi-P2P link according to an embodiment of the present application;

[0044] FIG20A is an optional schematic diagram of triggered P2P transmission according to an embodiment of the present application;

[0045] FIG20B is an optional schematic diagram of non-triggered P2P transmission according to an embodiment of the present application;

[0046] FIG21 is an optional flow chart of a transmission control method according to an embodiment of the present application;

[0047] FIG22 is a schematic diagram of an optional format of the STA Control field according to an embodiment of the present application;

[0048] FIG23 is a schematic diagram of an optional format of the STA Info field according to an embodiment of the present application;

[0049] FIG24 is a schematic diagram of an optional format of a Peer-to-peer link report field according to an embodiment of the present application;

[0050] FIG25 is a schematic diagram of an optional format of a broadcast TWT recommendation subfield according to an embodiment of the present application;

[0051] FIG26 is a schematic diagram of an optional format of a P2P Peer subfield according to an embodiment of the present application;

[0052] FIG27 is an optional flow chart of a transmission control method according to an embodiment of the present application;

[0053] FIG28 is a schematic diagram of an optional flow chart of a multi-link device establishing a TDLS direct link according to an embodiment of the present application;

[0054] FIG29 is an optional schematic diagram of triggered P2P transmission according to an embodiment of the present application;

[0055] FIG30 is an optional schematic diagram of non-triggered P2P transmission according to an embodiment of the present application;

[0056] FIG31 is an optional schematic diagram of non-triggered P2P transmission according to an embodiment of the present application;

[0057] FIG32 is an optional schematic diagram of non-triggered P2P transmission according to an embodiment of the present application;

[0058] FIG33 is a schematic diagram of an optional format of a P2P TWT EDCA Parameter Set element according to an embodiment of the present application;

[0059] FIG34 is an optional schematic diagram of a multi-P2P link according to an embodiment of the present application;

[0060] FIG35 is an optional structural diagram of a first non-access point device according to an embodiment of the present application;

[0061] FIG36 is a schematic diagram of an optional structure of an access point device according to an embodiment of the present application;

[0062] FIG37 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0063] FIG38 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0064] Figure 39 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0065] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0066] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems. WLAN can support frequency bands including, but not limited to, low frequency bands (2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (60 GHz).

[0067] FIG1A is an example of a communication system architecture applied in an embodiment of the present application.

[0068] As shown in FIG1A , the communication system 100 may include an AP 110 and a STA 120 that accesses the network through the AP 110. In some scenarios, the AP 110 may be referred to as an AP STA, meaning that, in a sense, the AP 110 is also a type of STA. In some scenarios, the STA 120 may be referred to as a non-AP STA. In some scenarios, the STA 120 may include both AP STAs and non-AP STAs. Communication in the communication system 100 may include communication between the AP 110 and the STA 120, communication between the STA 120 and another STA 120, or communication between the STA 120 and a peer STA. A peer STA may refer to a device communicating with the STA 120, for example, a peer STA may be an AP or a non-AP STA.

[0069] AP 110 can be used as a bridge between wired and wireless networks, connecting wireless network clients together and then connecting the wireless network to Ethernet. AP 110 can be a terminal device (such as a mobile phone) or a network device (such as a router) equipped with a WiFi chip.

[0070] It should be noted that the role of STA 120 in the communication system is not absolute. In other words, the role of STA 120 in the communication system can switch between AP and STA. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a STA. When the mobile phone is used as a hotspot for other mobile phones, the mobile phone plays the role of AP.

[0071] In some embodiments, AP 110 and STA 120 can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0072] In some embodiments, AP 110 may be a device supporting the 802.11be standard. The AP may also be a device supporting various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. In some embodiments, STA 120 may support the 802.11be standard. The STA may also support various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0073] In some embodiments, AP 110 and / or STA 120 can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship); can also be deployed in the air (for example, on an airplane, balloon, and satellite, etc.).

[0074] In some embodiments, STA 120 may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a set-top box, a wireless device in self-driving, an in-vehicle communication device, a wireless device in remote medical, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city or a wireless device in a smart home, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc. that supports WLAN / WiFi technology.

[0075] For example, STA 120 can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are full-featured, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0076] It should be understood that Figure 1A is merely an example of the present application and should not be construed as limiting the present application. For example, Figure 1A only exemplarily illustrates one AP and two STAs. In some embodiments, the communication system 100 may include multiple APs and other numbers of STAs, which is not limited in this embodiment of the present application.

[0077] FIG1B is a schematic diagram of an application scenario of an embodiment of the present application.

[0078] As shown in Figure 1B , communication system 200 may include: AP MLD 210 and non-AP MLD 220. AP MLD 210 is an electronic device capable of forming a wireless local area network 230 based on transmitted signals, such as a router or a mobile phone with hotspot functionality. Non-AP MLD 220 is an electronic device connected to the wireless local area network 230 formed by AP MLD 210, such as a mobile phone, smart washing machine, air conditioner, or electronic lock. Non-AP MLD 220 communicates with AP MLD 210 via wireless local area network 230. AP MLD 210 may be a soft AP MLD, a mobile AP MLD, or the like.

[0079] As shown in FIG1C , in the communication system described in FIG1B , AP MLD 210 is associated with at least two APs 2101, and non-AP MLD 220 is associated with at least two STAs (STAs) 2201. Each AP is connected to a different STA in non-AP MLD 220 via a different link. An AP associated with an AP MLD is also referred to as an AP MLD-associated AP, and a STA associated with a non-AP MLD is also referred to as a non-AP MLD-associated STA.

[0080] In the embodiments of the present application, the AP MLD 210 and the non-AP MLD 220 may be terminal devices, which may refer to access terminals, user equipment (UE), subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents, or user devices. Access terminals may be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5th generation (5G) networks, or terminal devices in future Public Land Mobile Networks (PLMNs), etc.

[0081] The communication system 200 shown in Figure 1B may also include a network device, which may be an access network device that communicates with a terminal device. The access network device may provide communication coverage for a specific geographical area and may communicate with terminal devices within the coverage area.

[0082] FIG1B exemplarily shows an AP MLD and a non-AP MLD. Optionally, the wireless communication system 200 may include multiple non-AP MLDs connected to the wireless local area network 230 , which is not limited in this embodiment of the present application.

[0083] It should be noted that Figures 1A, 1B, and 1C are merely examples of the systems to which this application applies. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships can exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " herein generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an associated relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; it can also mean that A and B have an associated relationship. It should also be understood that the “correspondence” mentioned in the embodiments of the present application may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of the present application, the “protocol” may refer to a standard protocol in the field of communications, for example, it may include LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0084] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0085] With the rapid development of wireless network technology, a trend is becoming increasingly apparent: in various deployment scenarios, the phenomenon of P2P communication over WLAN is increasing over time. This comes with the problem that P2P communication competes with the infrastructure WLAN for media resources.

[0086] The current technology for P2P communication over WLAN is called Tunneled Direct Link Setup (TDLS). TDLS technology is transparent to the access point (AP). Although the AP can obtain the establishment status of TDLS direct links within the Basic Service Set (BSS) through P2P reports, the AP cannot know the usage of TDLS direct link resources within the current BSS.

[0087] The BSS describes a group of communication devices that communicate with each other in a wireless local area network (WLAN), which may or may not include an AP.

[0088] Therefore, a mechanism is urgently needed to enable the AP to schedule the transmission of TDLS direct links within the BSS and coordinate the allocation and use of P2P network and WLAN resources. In related technologies, the solutions for coordinating the allocation and use of P2P network and WLAN resources include the following solutions 1 to 4:

[0089] Option 1

[0090] This proposal proposes establishing TDLS direct links on multiple links. The process for establishing a multi-link TDLS direct link is consistent with the TDLS establishment process. The multi-link elements in the TDLS Setup Request frame, TDLS Setup Response frame, and TDLS Setup Confirmation frame used in the establishment process carry a separate site description (Per-STA Profile) sub-element for each affiliated STA that needs to establish a TDLS direct link. The format of this sub-element is shown in Figure 2 and includes the following fields: Subelement ID, Length, STA Control, STA Info, and STA Profile. The Subelement ID contains the identifier of the Per-STA Profile sub-element, the Length field contains the length of the Per-STA Profile sub-element, the STA Control field contains the control information of the corresponding site, and the STA Profile field contains the configuration information of the corresponding site.

[0091] Each Per-STA Profile represents an attached STA that needs to establish a TDLS direct link. The STA Info field carries the STA's MAC address. By carrying Per-STA Profile elements, multiple TDLS direct links can be established simultaneously on a single link.

[0092] Option 2

[0093] This solution uses restricted target wake time (r-TWT) to support delay-sensitive P2P traffic. The basic idea is to establish an r-TWT service period (SP), and then the AP uses mode 2 of transmission opportunity (TXOP) sharing, that is, the shared TXOP can be used for P2P transmission. When establishing the r-TWT SP, the resources required for P2P traffic are carried through the target wake time (TWT) element. The resources required for P2P traffic may include: the duration of the SP used for P2P traffic transmission and the traffic identifier (TID) of delay-sensitive P2P traffic.

[0094] In r-TWT SP, the AP uses a multi-user request to send transmission status (MU-RTS TXS) trigger frame to share TXOP for P2P transmission.

[0095] As shown in Figure 3, the link between AP and STA1 is link 1, and the link between STA1 and STA2 is link 2. AP broadcasts a beacon frame. The TWT element in the Beacon frame indicates that the broadcast TWT (bTWT) is used for P2P transmission. After receiving the beacon frame, STA1 returns a TWT request frame to AP to apply to join the current broadcast TWT. At this time, AP sends a TWT response frame in response to the TWT request frame to STA1 to agree to STA1 to join the broadcast TWT. During the r-TWT SP, AP sends a basic trigger (Basic Trig) frame to STA1. Based on the trigger of the basic trigger frame, STA sends data to AP through a trigger-based (TB) presentation protocol data unit (PPDU). AP sends a block response (BA) frame to STA1, and communication is first carried out between AP and STA1. The AP can trigger sharing mode 2 by sending a MU-RTS TXS trigger frame to STA1, and share the AP's transmission opportunity with STA1 for P2P transmission. After receiving the MU-RTS TXS trigger frame, STA1 returns a Clear-to-Send (CTS) frame to the AP. At this time, STA1 and STA2 use the transmission opportunity shared by the AP to transmit data (Data) frames, wherein the end receiving the data returns a Block Ack (BA) frame to the end sending the data after receiving the data frame. The value of the Broadcast TWT Recommendation subfield in the TWT element is 5, indicating that the broadcast TWT (bTWT) is used for P2P transmission. The value of the Broadcast TWT Recommendation subfield in the TWT element of the TWT request frame and the TWT response frame is 5. Based on the value of the Broadcast TWT Recommendation subfield in the TWT element being 5, the STA joins the TWT and becomes a member site of the r-TWT SP.

[0096] In the embodiment of the present application, a member site of a TWT SP can be understood as a TWT scheduled site (TWT scheduled STA).

[0097] Option 3

[0098] This solution better supports P2P channel usage in WLANs by allowing the AP to schedule P2P traffic transmission, thereby coordinating resource usage between BSS and P2P traffic. As shown in Figure 4, the AP announces the P2P transmission window in a beacon frame. Within the P2P transmission window, STAs prioritize P2P traffic transmission. To ensure P2P traffic transmission, the AP provides minimal support for BSS traffic transmission.

[0099] Because the transmission of P2P traffic within the current BSS is basically not managed by the AP, the goal of this proposal is to allow the AP to manage these unmanaged P2P transmissions, thereby improving resource utilization and thus improving the traffic transmission efficiency of the BSS.

[0100] Option 4

[0101] Within the r-TWT SP, all STAs, including the r-TWT scheduled STA (scheduled STA), which is the member station of the r-TWT SP, can compete for TXOP, which will interfere with the transmission of low-latency traffic. Therefore, the beacon frame carries the restricted TWT enhanced distributed channel access (EDCA) parameter set (Restricted TWT EDCA Parameter Set) element to notify all STAs that in the non-trigger-enabled r-TWT SP, STAs of different roles should use the EDCA parameters assigned by the Restricted TWT EDCA Parameter Set element when competing for TXOP. This ensures that the r-TWT scheduled STA has high-priority channel access rights in the non-trigger-enabled r-TWT SP, as shown in Figure 5.

[0102] In Figure 5, STA1 and STA2 interact with the AP through rTWT request frames and rTWT response frames, respectively, and join rTWT to become the rTWT scheduled station (r-TWT scheduled STA). Among them, STA1 is a member station of SP1 and STA2 is a member station of SP2. STA3 supports r-TWT, but has not joined rTWT and is not a station scheduled by the rTWT SP (r-TWT unscheduled STA), that is, it is not a member station of a certain SP. It can be understood as a non-member station of SP1 and a non-member station of SP2. STA4 is a station that does not support rTWT (non-r-TWT STA).

[0103] The AP broadcasts a beacon frame, which includes EDCA parameter 1 (EDCA parameters for member sites during the SP or within the SPA (rTWT-Scheduled-In-SP(s)-EDCA-Parameters)). The beacon frame may also include: EDCAC parameter 2 (EDCA parameters for member sites outside the SP (rTWT-Scheduled-Outside-SP(s)-EDCA-Parameters)), EDCA parameter 3 (EDCA parameters for non-member sites within the SP (rTWT-non-Scheduled-In-SP(s)-EDCA-Parameters)), and EDCA parameter 4 (EDCA parameters for non-member sites outside the SP (rTWT-non-Scheduled-Outside-SP(s)-EDCA-Parameters)). It should be noted that EDCA parameter 2, EDCA parameter 3, and EDCA parameter 4 may or may not be included in the beacon frame.

[0104] In the embodiment of the present application, rTWT SP1 and rTWT SP2 adopt non-trigger scheduling, that is, each site competes for transmission opportunities through EDCA parameters.

[0105] As shown in Figure 5, within SP1, STA1 uses EDCA parameter 1 to compete for transmission opportunities, STA2 and STA3 use EDCA parameter 3 to compete for transmission opportunities, and STA4 uses EDCA parameter 5 (EDCA parameters independent of rTWT SP(s)) to compete for transmission opportunities. STA1 competes for the transmission opportunity, and STA1 transmits uplink data (UL-PPDU) or downlink data (DL PPDU) with the AP based on the transmission opportunity it competes for. Among them, the priority of EDCA parameter 1 is greater than the priority of EDCA parameter 3.

[0106] As shown in Figure 5, outside of SP1 and SP2, STA1 and STA2 use EDCA parameter 2 to compete for transmission opportunities, STA3 uses EDCA parameter 4 to compete for transmission opportunities, and STA4 uses EDCA parameters independent of the rTWT SP to compete for transmission opportunities. At this time, STA3 and STA4 compete for the transmission opportunity and transmit uplink data to the AP respectively. In this case, EDCA parameter 4 has higher priority than EDCA parameter 2.

[0107] As shown in Figure 5, within SP2, STA1 and STA3 use EDCA parameter 3 to compete for transmission opportunities, STA3 uses EDCA parameter 1 to compete for transmission opportunities, STA4 uses EDCA parameters independent of rTWT SP to compete for transmission opportunities, and STA3 competes for the transmission opportunity. Based on the competed transmission opportunity, STA3 communicates with the AP for uplink data (UL-PPDU) or downlink data (DL PPDU).

[0108] TDSL

[0109] TDLS includes three parts: TDLS discovery, TDLS direct link establishment, and TDLS direct link termination.

[0110] TDLS Discovery Process

[0111] Within the same BSS, the initiator sends a TDLS Discovery Request frame through the AP, which contains the MAC address of the responder. The responder receives the TDLS Discovery Request frame from the AP and, if it supports TDLS, sends a TDLS Discovery Response frame to the initiator via a direct path.

[0112] In addition, the initiator can also send an unsolicited TDLS Discovery Response frame to the responder directly through the direct path. If the responder receives such an unsolicited TDLS Discovery Response frame and supports the TDLS function, it will respond with a TDLS Discovery Response frame through the direct path.

[0113] TDLS discovery functions as follows: 1. It allows a TDLS STA (a STA that supports TDLS) to confirm whether another STA is a TDLS STA. Upon receiving a TDLS Discovery Request frame or an unsolicited TDLS Discovery Response frame, a TDLS STA must reply with a TDLS Discovery Response frame to indicate support for TDLS. 2. It also allows a TDLS STA to confirm whether the other STA is in the same BSS as itself.

[0114] TDLS direct link establishment process

[0115] Figure 6 shows the TDLS direct link establishment process. The TDLS STA that sends the TDLS setup request frame is called the initiator, and the TDLS STA that receives the TDLS setup request frame is called the responder, or the TDLS peer. The initiator sends a TDLS setup request frame to the responder through the AP. The frame carries the BSSID of the initiator's BSS. After the responder receives it, there are five different situations:

[0116] Case 1: The TDLS establishment request is accepted.

[0117] The responder sends a TDLS establishment response frame to the initiator through the AP, and the status code carried in the frame is success.

[0118] Case 2: The TDLS establishment request is rejected.

[0119] If the BSSID in the TDLS setup request frame received by the responder is different from the BSSID of the responder's BSS, the responder must reject the TDLS setup request and send a TDLS setup response frame to the initiator through the AP. The status code carried in the frame is request_declined (request rejected).

[0120] Case 3: Before receiving the TDLS Setup Request frame, the responder sends a TDLS Setup Request frame as the initiator and has not received a response from the responder. If the source address in the TDLS Setup Request frame is smaller than its own MAC address, the responder should terminate the TDLS setup initiated by itself and then send the TDLS Setup Response frame in Case 1 or Case 2.

[0121] Case 4: Before receiving a TDLS setup request frame, the responder, as the initiator, sends a TDLS setup request frame and has not yet received a response from the responder. If the source address in the TDLS setup request frame is larger than its own MAC address, the responder discards the TDLS setup request frame and does not send a TDLS setup response frame.

[0122] Case 5: If a TDLS direct link already exists between the responder and the initiator, the responder terminates the existing TDLS direct link and responds with a TDLS setup response frame.

[0123] TDLS direct link termination

[0124] Generally, a TDLS STA can send a TDLS teardown frame over the TDLS direct link at any time, with the reason code set to TDLS_UNSPECIFIED_REASON. If the peer cannot receive information from the TDLS direct link, the TDLS STA can send a TDLS teardown frame through the AP with the reason code set to TDLS_PEER_UNREACHEABLE. Once the TDLS STA sends or receives the TDLS teardown frame, the TDLS direct link is terminated.

[0125] If a TDLS STA wants to leave the current BSS, it needs to send a TDLS teardown frame to all peer STAs on the TDLS direct link, with the reason code set to leaving the network (LEAVING_NETWORK_DEAUTH).

[0126] The preceding TDSL link establishment process is for establishing a TDLS direct link between non-multi-link devices. The following describes the TDSL link establishment process for other scenarios:

[0127] Case 1: A multi-link device (MLD) and a non-multi-link device (STA) establish a TDLS direct link

[0128] As shown in Figure 7, MLD_S wants to establish a TDLS direct link with STA3. In the TDLS discovery phase, STA1 in MLD_S sends a data frame to AP1 of MLD_A through link 1. This data frame is a TDLS discovery request frame and carries the following information: A1 indicating the receiving address (RA) is AP1, A2 indicating the sending address (TA) is STA1, A3 indicating the target address (DA) is STA3, and the link information is (MLD_S, STA3, AP1); STA1 in MLD_S sends a data frame to AP2 of MLD_A through link 2. This data frame is a TDLS discovery request frame and carries the following information: A1 indicating the receiving address (RA) is AP2, A2 indicating the sending address (TA) is STA2, A3 indicating the target address (DA) is STA3, and the link information is (MLD_S, STA3, AP1). The TDLS discovery request frame sent by STA1 and STA2 is used to request the establishment of the link (MLD_S, STA3, AP1). AP1 forwards both discovery request frames to STA3. STA3 checks the Link Information (LI) element in the discovery request frames, which contains three addresses:<MLD_S,STA3,AP1> , indicating that MLD_S wants to establish a TDLS direct link with STA3 in the BSS where AP1 resides. STA3 receives this message and sends it to STA1 via the direct link between MLD_S and STA3 as a management frame. This management frame is a TDLS Discovery Response frame. Note that if AP2 is in the LI, the BSSID of STA3's BSS is different, so STA3 will not send a Discovery Response frame to STA2. The resulting TDLS direct link is shown in Figure 8.

[0129] In the direct link shown in Figure 8, when STA1 sends a data frame to STA3, the sending address in the data frame is MLD_S, the receiving address is STA3, and the BSS ID is AP1. When STA3 sends a data frame to STA1, the sending address in the data frame is STA3, the receiving address is MLD_S, and the BSS ID is AP1.

[0130] Case 2: Establishing a TDLS direct link between multi-link devices

[0131] As shown in Figures 9 and 10, MLD_S can send data frames as TDLS establishment request frames over all links (STA1 over the link between AP1 and STA3, and STA2 over the link between AP2 and STA4). Similarly, MLD_R can also send data frames as TDLS establishment response frames over all links, but ultimately, only one link can be used to establish a TDLS direct link. In the LI element in Figures 9 and 10, BSSID = AP1, indicating that the TDLS direct link between MLD_S and MLD_R is established only within AP1's BSS. The final established TDLS direct link is shown in Figure 11.

[0132] Target wake-up time

[0133] TWT is divided into independent TWT, broadcast TWT and restricted TWT.

[0134] Individual TWT: non-AP STA1 sends a TWT request frame to the AP. The AP can choose to accept, reject, or negotiate further. The AP tells non-AP STA1 the result through a TWT response. If the AP wants to send downlink traffic to other STAs at the same time within the individual TWT SP, the AP can also send an unsolicited TWT response frame to non-AP STA2. Within the individual TWT SP, non-AP STA1 and non-AP STA2 wake up and exchange frames with the AP. As shown in Figure 12, the AP broadcasts a Basic Trigger frame, non-AP STA1 returns a Power Save-Poll (PS-Poll) frame to the AP, and non-AP STA1 returns a QoS Nul frame to the AP, indicating that data transmission is possible. The AP responds with a Multi-STA Block Ack frame. At this point, the AP can send downlink multi-user (MU) PPDU (DL MU PPDU) frames to non-AP STA1 and non-AP STA2. After receiving the PPDU frames, non-AP STA1 and non-AP STA2 return BA frames to the AP. In Figure 12, the AP and STA1 and STA2 are all aware of the TWT SP. During non-TWT SP periods, the AP and STA1 and STA2 are in a sleep state (Doze) to save energy. When the TWT SP arrives, the AP and STA1 and STA2 wake up to provide service.

[0135] Broadcast TWT: As shown in Figure 13, the non-AP STA and the AP can negotiate the broadcast TWT SP through the TWT request frame and the TWT response frame, or the AP can determine the broadcast TWT SP itself. After the broadcast TWT is established, the AP must carry the broadcast TWT element in the beacon, probe response frame or (re)association frame to notify other non-AP STAs in the BSS of the existence of the broadcast TWT. As shown in Figure 13, the non-AP STA receives the beacon frame and parses the broadcast TWT information from it. If necessary, it can wake up at the beginning of the broadcast TWT SP and wait to receive the basic trigger frame from the AP. Within the broadcast TWT SP, the AP can actively send downlink traffic as shown in Figure 13, and the AP can also schedule non-AP STAs to send uplink traffic. Inside and outside the broadcast TWT SP, non-AP STAs are not recommended to compete for transmission opportunities through the EDCA mechanism.

[0136] Restricted TWT: Restricted TWT is a base address established for periodic, low-latency traffic. The establishment process of restricted TWT is the same as broadcast TWT. The restricted TWT Traffic Info subfield is added to the broadcast TWT parameter set field and a new value 4 is added to the Broadcast TWT Recommendation field to indicate that the current broadcast TWT is restricted TWT. The restricted TWT Traffic Info is used to indicate the TID of the low-latency traffic supported by the current restricted TWT. After the restricted TWT is established, the AP will also broadcast the restricted TWT SP to prevent other non-AP STAs from transmitting frames within the restricted TWT SP.

[0137] Triggered TXOP sharing procedure

[0138] The Triggered TXOP Sharing mechanism allows the AP to allocate part of the TXOP it has won to associated non-AP STAs. As shown in Figure 14, STA1 and STA2 negotiate a TWT SP. The AP broadcasts the TWT element. After the AP wins the TXOP, it allocates part of the TXOP to non-AP STA1 via a MU-RTS TXS Trigger frame. The MU-RTS TXS Trigger frame indicates TXOP sharing mode 2. Non-AP STA1 returns a CTS frame to the AP. Within the TXOP, non-AP STA1 can perform PPDU transmission with the AP and P2P data transmission with non-AP STA2.

[0139] The Trigger TXOP sharing mechanism has two modes. In Mode 1, non-AP STAs can only transmit data with the AP within the allocated TXOP. In Mode 2, non-AP STAs can not only transmit data with the AP within the allocated TXOP, but also conduct P2P traffic transmission with other non-AP STAs.

[0140] The multi-link establishment method provided in the embodiment of the present application proposes how to establish multiple TDLS links on a multi-link device. Specifically:

[0141] 1. Establish multiple TDLS direct links simultaneously on one link;

[0142] 2. Eliminate BSS restrictions. STAs with different non-AP MLDs can establish TDLS without being in the same BSS.

[0143] As shown in Figure 15:

[0144] S1501, non-AP MLD1 sends a TDLS setup request frame to AP MLD;

[0145] S1502: AP MLD sends a TDLS setup request frame to non-AP MLD2.

[0146] S1503. Non-AP MLD2 sends a TDLS setup response frame to AP MLD.

[0147] S1504: AP MLD sends a TDLS setup response frame to non-AP MLD1.

[0148] S1505. Non-AP MLD1 sends a TDLS setup confirmation frame to AP MLD.

[0149] S1506: AP MLD sends a TDLS setup confirmation frame to non-AP MLD2.

[0150] The TDLS establishment request frame, response frame, and confirmation frame carry per-STA information and indicate the link that can be used to establish TDLS.

[0151] 1. The TDLS setup request frame sent by Non-AP MLD1 may carry three links.

[0152] 2. After receiving the request frame, Non-AP MLD2 selects one or more links that can establish TDLS and notifies Non-AP MLD1 through a TDLS setup response frame.

[0153] 3. Non-AP MLD1 finally confirms the link identified in the response frame and informs non-AP MLD2 through a TDLS establishment confirmation frame.

[0154] In related technologies, the TDLS discovery, TDLS direct link establishment, and TDLS direct link termination operations of the TDLS mechanism are transparent to the AP, so the AP cannot know the resource usage of the TDLS direct link in the current BSS, nor can the AP schedule the TDLS direct link to improve resource utilization.

[0155] In the scenario shown in Figure 16, under the current TDLS mechanism, the processes of establishing TDLS direct links between STA1 and STA2 and between STA7 and STA8 are independent of each other. It is possible to calculate whether simultaneous data transmission on the two TDLS direct links will cause interference. Assuming that the calculation results for the two TDLS direct links in Figure 16 indicate no interference, the situation is as follows:

[0156] 1. STA7 and STA8 cannot perform WLAN transmission because the AP sending / receiving data may interfere with P2P transmission;

[0157] 2. STA7 and STA8 can perform P2P transmission because the two TDLS direct links do not interfere with each other.

[0158] 3. r-TWT can only share a single P2P transmission, resulting in low resource utilization.

[0159] The highest resource utilization should be achieved when two TDLS direct links perform P2P transmission simultaneously.

[0160] The two pairs of P2P traffic are transmitted within a time period, and P2P transmission is performed during the time period when WLAN transmission is unavailable. This reduces the total P2P traffic transmission time, thereby increasing the Infrastructure BSS transmission time and improving resource utilization.

[0161] Obviously, the current TDLS mechanism cannot implement such scheduling because the non-AP STA cannot know whether there are other TDLS direct links in the BSS. Although the AP can know the existence of these two TDLS direct links, it does not know the resource usage of these two TDLS direct links and therefore cannot implement scheduling.

[0162] Theoretically, this can be achieved through broadcast TWT technology. Suppose STA1 and STA2 agree to transmit on the TDLS direct link during a specific time period and request a broadcast TWT SP from the AP for that time period. After that, the AP broadcasts the broadcast TWT scheduling information, which STA7 and 8 will definitely receive. As long as STA7 and 8 also join the broadcast TWT and transmit on the TDLS direct link within the broadcast TWT SP, the above optimal scheduling cannot be achieved. The reasons are as follows:

[0163] First, STA7 and STA8 know that there is a broadcast TWT, but do not know that the broadcast TWT is the scheduling of the TDLS direct link between STA1 and STA2. They may intentionally stagger the same time period when applying for the broadcast TWT SP for the TDLS direct link.

[0164] Second, the AP knows that simultaneous transmission of two TDLS direct links will not cause interference, but it cannot align its SP with the broadcast TWT SP of STA1 and 2 when STA7 and 8 apply to establish a broadcast TWT, because the AP cannot understand the purpose of STA7 and 8 applying for broadcast TWT.

[0165] Third, the Triggered TXOP sharing mechanism is also unfeasible because the AP does not know when TDLS STAs will need to transmit traffic. Sharing every TXOP won through competition would be counterproductive.

[0166] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0167] The transmission control method provided in the embodiment of the present application is applied to a first non-access point device, as shown in FIG17 , and includes:

[0168] S1701. A first non-access point device receives first information sent by an access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and a second non-access point device.

[0169] The transmission control method provided in the embodiment of the present application is applied to an access point device, as shown in FIG18 , and includes:

[0170] S1801. The access point device sends first information to a first non-access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and a second non-access point device.

[0171] Below, the transmission control method shown in Figure 17 or Figure 18 provided in the embodiment of the present application is further described.

[0172] The access point device, the first non-access point device, and the second access point device belong to the same BSS, namely the first BSS, and a P2P link is established between the first non-access point device and the second non-access point device. The access point device can determine the first TWT SP and send first information indicating the first TWT SP to the first non-access point device.

[0173] It is understandable that, of the first non-access point device and the second non-access point device, one is the link initiator or link initiating end of the first P2P link, and the other is the link responder or link responding end of the first P2P link. If the first non-access point device is the link initiator of the first P2P link, then the second non-access point device is the link responder of the first P2P link; if the second non-access point device is the link initiator of the first P2P link, then the first non-access point device is the link responder of the first P2P link.

[0174] In addition to sending the first TWT SP to the first non-access point device, the access point device may also send the first TWT SP to the second non-access point device.

[0175] During the first TWT SP, the access point device schedules at least one P2P link, i.e., one P2P link or multiple P2P links, to prioritize P2P transmission, thereby prioritizing P2P transmission on at least one P2P link during the first TWT SP, wherein the at least one P2P link includes the first P2P link.

[0176] It is understandable that the first P2P link is any one of the at least one P2P link. In the at least one P2P link, different P2P links are links between two different non-access point devices.

[0177] In the embodiment of the present application, TWT is used for P2P, so the TWT can also be understood as P2P TWT.

[0178] The access point device sends the first information to the first non-access point device during the P2P TWT establishment process.

[0179] It can be understood that the first TWT SP can be an independent TWT (Individual TWT) or a broadcast TWT (Broadcast TWT).

[0180] If the first TWT is an independent TWT, different P2P links correspond to different TWT SPs. At this time, different P2P links in at least one P2P link correspond to independent TWT SPs respectively.

[0181] If the first TWT is a broadcast TWT, different P2P links may correspond to the same TWT SP. In this case, the TWT SP corresponding to at least one P2P link is the first TWT SP.

[0182] In the embodiment of the present application, the first TWT SP indicates: a first channel and a first duration, for indicating that the first P2P link between the first non-access point device and the second non-access point device performs P2P transmission on the first channel within the first duration.

[0183] In the embodiment of the present application, at least one member site of the first TWT SP performs P2P transmission on the first channel within a first duration.

[0184] In the embodiment of the present application, during the first TWT SP period, at least one P2P link performs P2P transmission on a first channel, and at least one P2P link may also perform transmission on a second channel different from the first channel.

[0185] In an embodiment of the present application, the access point device indicates a first TWT SP to the first non-access point device. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, thereby proposing a TWT SP for coordinating P2P transmission and realizing AP scheduling of P2P transmission on the P2P link.

[0186] It is understandable that the access point device indicates the first TWT SP to the first non-access point device, and controls the access point device and the first non-access point device to be in TWT SP mode based on the first TWT SP. In the TWT SP mode, P2P transmission on multiple P2P links is realized.

[0187] It is understandable that the access point device in the embodiment of the present application may be an access point or an attached AP of an AP MLD.

[0188] In some embodiments, the first TWT SP is included in a first frame sent by the access point device to the first non-access point device, and the first frame includes at least one of the following:

[0189] TWT establishment response frame; beacon frame; association frame or reassociation frame; probe response frame.

[0190] If the first non-access point device is the link initiator of the P2P link, the first frame is a TWT establishment response frame.

[0191] If the first non-access point device is a link responder of the P2P link, the first frame is one of the following: a beacon frame, an association frame, or a reassociation frame; or a probe response frame.

[0192] In an embodiment of the present application, during the P2P TWT establishment process, the link initiator of the P2P link (hereinafter referred to as the initiator) sends a TWT establishment request frame to the access point device, namely AP. The AP determines the first TWT SP based on the TWT establishment request frame, and carries the first information in the TWT establishment response frame and sends it to the initiator. At this time, the initiator is a member site of the first TWT SP, and the establishment of the P2P TWT between the initiator and the AP is completed. After the P2P TWT between the initiator and the AP is established, the AP carries the first information in the beacon frame, the probe response frame, the association frame or the reassociation frame, and broadcasts the first information to the link responder of the P2P link (hereinafter referred to as the responder). The responder receives the first information broadcast by the AP and determines whether to join the P2P TWT; if not, the first TWT SP is saved, and the responder is not a member site of the first TWT SP; if joining, the responder needs to send a TWT establishment request frame to the AP and receive the TWT establishment response frame sent by the AP to complete the establishment of the P2P TWT between the responder and the AP, also known as the member site of the first TWT SP.

[0193] In the embodiment of the present application, whether the responder is a member site of the first TWT SP or not, it can perform P2P transmission with the initiator during the first TWT SP period.

[0194] In some embodiments, the first TWT SP is included in a first TWT element of the first frame.

[0195] In the embodiment of the present application, the first TWT element can be understood as a TWT element corresponding to the first P2P link, which is used to carry TWT information related to the first P2P link.

[0196] In some embodiments, the first TWT element further includes at least one of the following:

[0197] First indication information, where the first indication information is used to indicate that the first TWT SP is used for a P2P link;

[0198] Parameters of the peer device of the first P2P link;

[0199] Channel information of the first P2P link.

[0200] The parameters of the peer device of the first P2P link can be understood as the address parameters of the responder, such as the MAC address and AID of the responder.

[0201] The channel information of the first P2P link is used to indicate a channel used for P2P transmission of the first P2P link.

[0202] In an embodiment of the present application, the first TWT element includes not only the first information but also the second information, and the second information includes one of the following: the first indication information, the parameters of the opposite device of the first P2P link, i.e., the responder, and the channel information of the first P2P link.

[0203] The first indication information is used to indicate that the currently established TWT is a P2P TWT for a P2P link, wherein the TWT being a P2P TWT for a P2P link can be understood as the currently determined first TWT SP being used for a P2P link or P2P transmission.

[0204] It can be understood that the channel indicated by the channel information of the first P2P link is the first channel of the first TWT SP.

[0205] In an embodiment of the present application, the second information in the first TWT element may be carried by the initiator in the TWT establishment request sent, so that the initiator provides the second element to the AP.

[0206] If the responder sends a TWT establishment request frame to the AP, the TWT element carried in the TWT establishment request frame is filled with the content of the TWT element sent by the initiator.

[0207] In one example, the initiator is STA1 and the responder is STA2. The TWT element of the TWT establishment request frame sent by STA1 to the AP includes the second information, and the second information includes the following information: the first indication information and the address information of STA2. After the AP determines the first TWT SP, the TWT element of the TWT establishment response frame sent to STA1 carries the first information and the second information. The TWT element of the beacon frame broadcast by the AP includes the first information and the second information. After receiving the beacon frame, STA2 recognizes that the beacon frame is sent to itself based on the address information of STA2 in the TWT element, and thus determines whether to request to join the first TWT SP. If so, it sends a TWT establishment request frame including the second information in the TWT element to the AP, and receives a TWT establishment response frame including the second information in the TWT element sent by the AP.

[0208] In some embodiments, the first indication information is included in a request type subfield of a TWT parameter information field of the first TWT element.

[0209] In an embodiment of the present application, the first TWT element includes the following fields: element ID, length, control, and TWT parameter information, wherein the TWT parameter information field is variable in size and represents the parameters of the current first P2P link. The TWT parameter information field includes a request type subfield, and the first indication information can be the original information in the request type subfield or newly added information.

[0210] In some embodiments, the first indication information is a broadcast TWT recommendation information whose value in the request field is a first value. The first value is a value agreed upon in a protocol or a set value.

[0211] In an embodiment of the present application, the broadcast TWT recommendation information is used to indicate the type of the current first TWT SP.

[0212] In one example, the first value is 5. If the value of the broadcast TWT recommendation information is 5, it indicates that the current TWT is a P2P TWT, that is, used for P2P transmission, and the determined TWT SP is a P2P TWT SP for P2P transmission.

[0213] In one example, the first value is 6. If the value of the broadcast TWT recommendation information is 6, it indicates that the current TWT is a P2P TWT, that is, used for P2P transmission, and the determined TWT SP is a P2P TWT SP used for P2P transmission.

[0214] In some embodiments, the condition that the first TWT element includes parameters of the peer device of the first P2P link and / or channel information of the first P2P link includes: the first TWT element includes the first indication information.

[0215] When the first TWT element includes the first indication information, it also includes the parameters of the peer device of the first P2P link and / or the channel information of the first P2P link. It is understandable that the parameters of the peer device of the first P2P link and / or the channel information of the first P2P link are stored in the P2P TWT.

[0216] In some embodiments, the parameters of the second non-access point device are included in a peer subfield of a TWT parameter information field of the first TWT element.

[0217] In some embodiments, the channel information of the first P2P link is contained in a channel subfield of a TWT parameter information field of the TWT element.

[0218] In some embodiments, if at least two P2P links are established between the first non-access point device and the second non-access point device, and the first frame is a TWT establishment response frame, then the first frame includes at least two TWT elements, one TWT element of the at least two TWT elements is used for a P2P link, and the first TWT element is used for the first P2P link of the at least two P2P links.

[0219] At this time, the first non-access point device and the second non-access point device are non-access point multi-link devices (Non-AP MLD) or station multi-link devices (STA MLD).

[0220] The first non-access point device is attached to at least two first attached STAs, the second non-access point device is attached to at least two second attached STAs, and there is a P2P link between a first attached STA and a second attached STA, there are at least two P2P links between the first non-access point device and the second non-access point device, and the first frame sent by the access point device to the first non-access point device includes at least two TWT elements, and different TWT elements correspond to different P2P links.

[0221] It can be understood that as the number of TWT elements in the first frame changes, the number of TWT elements in the TWT establishment request frame sent by the first non-access point device to the access point device changes accordingly, and the TWT Parameter Information field in the TWT element represents the parameters of the current P2P link.

[0222] In one example, as shown in Figure 19, STA MLD1 is attached to STA1 and STA2, STA MLD2 is attached to STA3 and STA4, P2P link 1 is established between STA1 and STA2, and P2P link 2 is established between STA3 and STA4. In the scenario shown in Figure 18, the TWT establishment request frame sent by STA MLD1 or STA MLD2 to the AP includes TWT element 1 and TWT element 2, and the first frame sent by the AP to STA MLD1 or STA MLD2 includes TWT element 1 and TWT element 2, where TWT element 1 corresponds to P2P link 1 and TWT element 2 corresponds to P2P link 2.

[0223] In some embodiments, when at least two P2P links are established between the first non-access point device and the second non-access point device, the first TWT element further includes a first traffic identifier TID of the first P2P link.

[0224] It can be understood that a TWT element includes the TID of a corresponding P2P link.

[0225] In some embodiments, the first TID is contained in a restricted TWT downlink or uplink TID bitmap subfield of a TWT parameter information field of the first TWT element.

[0226] In an embodiment of the present application, the restricted TWT downlink or uplink TID bitmap subfield of the TWT parameter information field in the TWT element is used to indicate the TID of the corresponding P2P link.

[0227] In one example, the restricted TWT downlink bitmap sub-resource of the TWT parameter information field of the first TWT element represents the traffic from the initiator to the responder, and the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the first TWT element represents the traffic from the responder to the initiator.

[0228] In one example, the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the first TWT element represents the traffic from the initiator to the responder, and the restricted TWT downlink bitmap sub-resource of the TWT parameter information field of the first TWT element represents the traffic from the responder to the initiator.

[0229] In some embodiments, the TWT parameter information field in the first TWT element is used to indicate whether the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the first TWT element is used to represent the TID of the P2P link.

[0230] In one example, the downlink TID bit value (DL TID Bitmap Valid) and the uplink TID bit value (UL TID Bitmap Valid) in the TWT parameter information field in the TWT element are used to indicate whether the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the TWT element is used to represent the TID of the P2P link.

[0231] For example: if the values ​​of the downlink TID bit value (DL TID Bitmap Valid) and the uplink TID bit value (UL TID Bitmap Valid) in the TWT parameter information field in the TWT element are respectively the second values, it indicates that the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the TWT element is used to represent the TID of the P2P link; if the values ​​of the downlink TID bit value (DL TID Bitmap Valid) and the uplink TID bit value (UL TID Bitmap Valid) in the TWT parameter information field in the TWT element are not the second values, it indicates that the restricted TWT uplink bitmap sub-resource of the TWT parameter information field of the TWT element is not used to represent the TID of the P2P link.

[0232] In some embodiments, the first TWT SP is determined based on a first communication requirement, where the first communication requirement includes a communication requirement of a first P2P link, where the first P2P link is a P2P link between the first non-access point device and the second non-access point device.

[0233] In an embodiment of the present application, the access point device determines the first TWT SP based at least on the communication requirements of the first P2P link, so that the determined first TWT SP is determined based on the communication requirements of the first P2P link, thereby associating the first TWT SP with the communication requirements of the first P2P link and improving resource utilization efficiency.

[0234] In some embodiments, the communication requirement of the first P2P link is a resource of the first P2P link.

[0235] The resources of the first P2P link can be understood as the available resources of the first P2P link, including: the time domain resources and / or frequency domain resources of the first P2P link, or, so that the first TWT SP corresponding to the first P2P link is related to the time domain resources and / or frequency domain resources of the first P2P link in the time domain and / or frequency domain, thereby improving the resource utilization of the BSS system.

[0236] In some embodiments, the first communication requirement further includes a communication requirement of a first BSS, and the first basic service set BSS is the BSS to which the first non-access point device belongs.

[0237] The communication demand of the first BSS represents the communication demand for transmission between the AP and the STA in the first BSS. The access point device determines the first TWT SP corresponding to the first P2P link based on the available resources of the first P2P link and the communication demand of the first BSS.

[0238] In some embodiments, the communication demand of the first BSS is resources used by the first BSS.

[0239] The access point device determines a first TWT SP according to the communication requirements of the first P2P link and the communication requirements of the first BSS.

[0240] The first TWT SP completely or partially overlaps with the time domain resources of the first P2P link in the time domain. The channel of the first TWT SP is the channel of the first P2P link. The frequency domain of the first TWT SP and the first P2P link is the same, that is, the first P2P link uses the first channel of the first TWT SP.

[0241] The first TWT SP overlaps or does not overlap with the frequency domain of the first BSS in the frequency domain, that is, the channel of the first TWT SP is the same as or different from the channel used by the traffic of the first BSS.

[0242] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP and the second TWT SP corresponding to the second P2P link overlap in the time domain and / or frequency domain, and the second P2P link is a P2P link between a third non-access point device and a fourth non-access point device.

[0243] The first TWT SP and the second TWT SP are independent TWT SPs, and one TWT SP corresponds to one P2P link, wherein the first TWT SP corresponds to the first P2P link, and the second TWT SP corresponds to the second P2P link. If the transmission of the first P2P link and the second P2P link does not interfere with each other, the access point device can set the first TWT SP and the second TWT SP to overlap in the time domain and / or frequency domain. It can be understood that the overlap of the first TWT SP and the second TWT SP can be understood as complete overlap or alignment. During the first TWT SP, the first P2P link is preferentially scheduled for priority transmission, and during the second TWT SP, the second P2P link is preferentially scheduled for priority transmission.

[0244] If the first TWT SP and the second TWT SP overlap in the time domain but do not overlap in the frequency domain, it can be understood that the P2P transmissions of the first P2P link and the second P2P link are the same in the time domain but different in the frequency domain. In this case, the access point device prioritizes scheduling the first P2P link for P2P transmission during the first TWT SP, and prioritizes scheduling the second P2P link for P2P transmission during the second TWTSP. The first P2P link and the second P2P link perform P2P transmission in the same time period and on different channels.

[0245] If the first TWT SP and the second TWT SP overlap in the frequency domain but do not overlap in the time domain, they can be understood as two TWT SPs with the same channel. The P2P transmissions of the first P2P link and the second P2P link are different in the time domain but the same in the frequency domain. In this case, the access point device prioritizes scheduling the first P2P link for P2P transmission during the first TWT SP, and prioritizes scheduling the second P2P link for P2P transmission during the second TWTSP. The first P2P link and the second P2P link perform P2P transmission in different time periods and on the same channel.

[0246] If the first TWT SP and the second TWT SP overlap in the time domain and frequency domain, they can be understood as two TWT SPs with the same time domain and channel, and the P2P transmission of the first P2P link and the second P2P link are the same in the time domain and frequency domain. In this case, the access point device prioritizes scheduling the first P2P link for P2P transmission during the first TWT SP, and prioritizes scheduling the second P2P link for P2P transmission during the second TWTSP. The first P2P link and the second P2P link perform P2P transmission in different time periods and on the same channel.

[0247] It can be understood that when the P2P transmissions of the first P2P link and the second P2P link are in the same time domain, even if the first P2P link and the second P2P link correspond to different TWT SPs, the two P2P links perform P2P transmission in the same time period.

[0248] In an embodiment of the present application, the access point device determines whether there is interference between the transmission of the first P2P link and the second P2P link. If there is no interference between the transmission of the first P2P link and the second P2P link, the channel and / or first duration of the first TWTSP and the second TWT SP are set to be the same; if there is interference between the transmission of the first P2P link and the second P2P link, the channel and / or first duration of the first TWTSP and the second TWT SP are set to be different.

[0249] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP is the TWT SP corresponding to the second P2P link, and the second P2P link is the P2P link between the third non-access point device and the fourth non-access point device.

[0250] In this case, the first TWT SP is a broadcast TWT SP, and one TWT SP corresponds to one or more P2P links, wherein the first TWT SP corresponds to the first P2P link and the second P2P link. If the transmission of the first P2P link and the second P2P link does not interfere with each other, the access point device can be set to determine the TWT SP corresponding to the existing second P2P link as the first TWT SP.

[0251] In the case where the first TWT SP corresponds to the first P2P link and the second P2P link, the access point device can preferentially schedule the first P2P link and the second P2P link through the first TWT SP to perform P2P transmission respectively.

[0252] It can be understood that the first P2P link and the second P2P link are two P2P links in at least one P2P link. When the at least one P2P link includes at least two P2P links, the at least two P2P links correspond to the same TWT SP.

[0253] In an embodiment of the present application, the access point device determines whether there is interference between the transmission of the first P2P link and the second P2P link. If there is no interference between the transmission of the first P2P link and the second P2P link, the first TWTSP is set as the TWT SP of the second P2P link; if there is interference between the transmission of the first P2P link and the second P2P link, the first P2P link and the second P2P link are set to correspond to different TWT SPs respectively.

[0254] In some embodiments, whether transmissions of the first P2P link and the second P2P link interfere with each other is determined based on the first communication requirement and a second communication requirement, where the second communication requirement is a communication requirement of the second P2P link.

[0255] The first communication requirement includes the communication requirement of the first P2P link and may also include the communication requirement of the first BSS.

[0256] After receiving the TWT establishment request frame sent by the first non-access point device or the second access point device, the access point device determines whether there is interference between the transmission of the first P2P link and the transmission of the second P2P link based on the first communication requirement and the second communication requirement.

[0257] It is understandable that the factors for the access point device to determine whether there is interference between the transmission of the first P2P link and the transmission of the second P2P link may also include at least one of the following information of the first P2P link and the second P2P link: working frequency band, working channel, MAC address or BSSID of the responder, transmit power of the responder on the P2P link, connection establishment time, and current status of the P2P link (including in use, disconnected, etc.).

[0258] In some embodiments, the communication requirement of the second P2P link is a resource of the second P2P link.

[0259] Regarding the communication requirement of the first P2P link in the first communication requirement, the communication requirement of the first P2P link is reported by the first access point device to the access point device.

[0260] In some embodiments, based on the transmission control method shown in FIG17 , the method further includes:

[0261] The first non-access point device sends a link report frame to the access point device, where the link report frame includes second indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

[0262] In some embodiments, based on the transmission control method shown in FIG18 , the method further includes:

[0263] The access point device receives a link report frame sent by the first non-access point device, where the link report frame includes second indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

[0264] If the first non-access point device is the initiator, the link report frame is transmitted at one of the following times:

[0265] After the P2P link is established or before the first non-access point device sends a TWT link establishment request frame;

[0266] After the first non-access point device sends a TWT link establishment request frame.

[0267] If the first non-access point device sends a link report frame to the access point device before the first non-access point device sends a TWT link establishment request frame, the first non-access point device may actively send a link report frame to the access point device.

[0268] If the first non-access point device sends a link report frame to the access point device after the first non-access point device sends the TWT link establishment request frame, the access point device may send a link report request frame to the first non-access point device after receiving the TWT link establishment request frame, and the first non-access point device may send a link report frame to the access point device in response to the received link report request frame.

[0269] If the first non-access point device is the responder, the link report frame is transmitted after the P2P link is established or before the first non-access point device sends a TWT link establishment request frame.

[0270] The transmission timing of the link report frame includes: before the first non-access point device sends a TWT link establishment request frame.

[0271] Here, after completing the P2P link establishment process, the first non-access point device may actively send a link report frame to the access point device, where the link report frame carries the communication requirements of the first link.

[0272] Regarding the communication requirement of the first BSS in the first communication requirement, the access point device may obtain resource usage in the first BSS through a channel state indication (CSI) report to determine the communication requirement of the first BSS.

[0273] The access point device may obtain the communication requirements of the second P2P link from the third non-access point device or the fourth non-access point device. The specific acquisition method is the same as the method in which the access point device obtains the communication requirements of the first link, which will not be repeated here.

[0274] In some embodiments, the second indication information is included in the event report field of the event report element of the link report frame.

[0275] The link report frame can also be understood as a peer-to-peer link report frame. The event report field in the event report element of the peer-to-peer link report frame carries a P2P available window list field, the content of which is the second indication information of the corresponding first P2P link.

[0276] In some embodiments, the first P2P link is a first tunnel direct link setting a TDLS direct link.

[0277] If the first P2P link is a first TDLS direct link, during the first TWT SP period, P2P transmission is preferentially performed on at least one TDLS direct link.

[0278] In the embodiment of the present application, if the first P2P link is a first TDLS direct link, the first non-access point device and the second non-access point device perform a TDLS direct link establishment process through the access point device to establish the first TDLS direct link.

[0279] The process of the TDLS direct link establishment process for establishing a first TDLS direct link includes: the initiator sends a TDLS establishment request frame to the access point device; the access point device sends a TDLS establishment request frame to the responder; the responder sends a TDLS establishment response frame to the access point device; the access point device sends a TDLS establishment response frame to the initiator; the initiator sends a TDLS establishment confirmation frame to the access point device; and the access point device sends a TDLS establishment confirmation frame to the responder.

[0280] TDLS direct link establishment process for establishing the first TDLS direct link

[0281] In some embodiments, the first non-access point device receives or sends a TDLS setup confirmation frame, where the TDLS setup confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

[0282] For an access point device, the access point device receives or sends a TDLS establishment confirmation frame, where the TDLS establishment confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

[0283] If the first non-access point device is the initiator, the first non-access point device sends a TDLS setup confirmation frame to the access point device.

[0284] If the first non-access point device is the responder, the first non-access point device receives the TDLS setup confirmation frame sent by the access point device.

[0285] The TDLS establishment confirmation frame carries third indication information indicating the communication requirement of the first P2P link.

[0286] In some embodiments, the third indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup confirmation frame.

[0287] In some embodiments, the first non-access point device receives or sends a TDLS establishment request frame, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information indicates a communication requirement of an initiator of the first P2P link for the first P2P link.

[0288] For an access point device, the access point device receives or sends a TDLS establishment request frame, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information is used to indicate a communication requirement of an initiator of the first P2P link for the first P2P link.

[0289] If the first non-access point device is the initiator, the first non-access point device sends a TDLS establishment request frame to the access point device.

[0290] If the first non-access point device is a responder, the first non-access point device receives the TDLS establishment request frame sent by the access point device.

[0291] In some embodiments, the fourth indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS establishment request frame.

[0292] In some embodiments, the first non-access point device sends or receives a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information is used to indicate a communication requirement of a responding end of the first P2P link for the first P2P link.

[0293] For an access point device, the access point device sends or receives a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information indicates a communication requirement of the responding end of the first P2P link for the first P2P link.

[0294] If the first non-access point device is the initiator, the first non-access point device receives the TDLS setup response frame sent by the access point device.

[0295] If the first non-access point device is the responder, the first non-access point device sends a TDLS setup response frame to the access point device.

[0296] In some embodiments, the fifth indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup response frame.

[0297] In some embodiments, the site information field of the first individual site description element includes an available window subfield, and the available window subfield includes indication information indicating corresponding resources.

[0298] For the first individual site description element including the second indication information, the third indication information or the fourth indication information, the site information field of the first individual site description element includes an available window subfield, and the available window subfield carries the corresponding indication information.

[0299] The first individual site description element in the TDLS setup confirmation frame carries third indication information in its available window subfield.

[0300] The first individual site description element in the TDLS setup request frame carries fourth indication information in its available window subfield.

[0301] The first individual site description element in the TDLS setup response frame carries fifth indication information in its available window subfield.

[0302] In the embodiment of the present application, an available window (P2P Available Window) subfield is added to the site information (STA Info) field of the Per-STA Profile element. The P2P Available Window represents a period of time domain and frequency domain resource information that can be used for P2P transmission.

[0303] In some embodiments, if the second frame including the first individual site description element is used to establish at least two P2P links, the second frame includes at least two individual site description elements, one individual site description element is used for one P2P link, and the at least two individual site description elements include the first individual site description element corresponding to the first P2P link.

[0304] The P2P Available Window List subfield is added to the STA Info field of the Per-STA Profile element. The P2P Available Window List subfield can contain one or more P2P Available Windows. Each P2P Available Window represents a section of time-domain and frequency-domain resource information that can be used for P2P transmission.

[0305] In some embodiments, the first non-access device and / or the second non-access device is a member site of the first TWTSP.

[0306] In the embodiment of the present application, the initiator is a member site of the first TWTSP, and the responder may be a member site of the first TWTSP or may not be a member site of the first TWTSP.

[0307] If the first non-access device is the initiator, then the first non-access device is a member site of the first TWT SP, and the second non-access device may be a member site of the first TWT SP or may not be a member site of the first TWTSP.

[0308] If the second non-access device is the initiator, then the second non-access device is a member site of the first TWT SP, and the first non-access device may be a member site of the first TWT SP or not.

[0309] In some embodiments, if the at least one P2P link includes at least two second P2P links, transmissions between the at least two P2P links do not interfere.

[0310] In some embodiments, transmissions on different P2P links among the at least two P2P links overlap in the time domain and / or frequency domain.

[0311] In an embodiment of the present application, during the first TWT SP period, the access point device can schedule at least two P2P links for P2P transmission, and the transmissions on different P2P links in the at least two P2P links overlap in the time domain and / or frequency domain, thereby improving resource utilization on the basis of ensuring P2P link transmission.

[0312] In some embodiments, the transmission opportunity used by the first P2P link for P2P transmission includes one of the following:

[0313] Case 1: The access point device is shared;

[0314] Case 2: The first non-access point device competes.

[0315] Case 1: Trigger-based scheduling, i.e. trigger mode

[0316] Case 1 can be considered as trigger-based scheduling. The first non-access point device does not compete for the transmission opportunity, while the access point device competes for the transmission opportunity and, after winning the transmission opportunity, shares the contended transmission opportunity with the first P2P link.

[0317] In the embodiment of the present application, the access point device may share part or all of the contended transmission opportunities with the first P2P link.

[0318] In case 1, after the access point device competes for the transmission opportunity, it uses the transmission opportunity sharing method within the first TWT SP to simultaneously schedule at least one P2P link for P2P transmission. The P2P transmissions of these P2P links do not interfere with each other when they are carried out simultaneously.

[0319] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, and the first non-access point device is a member site of the first TWT SP, the transmission control method shown in FIG17 further includes:

[0320] The first non-access point device receives a first trigger frame sent by the access point device during the first TWT SP period, where the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

[0321] For non-access point devices, this also includes:

[0322] If the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, the first non-access point device is a member site of the first TWT SP. Based on the transmission control method shown in Figure 18, the method also includes: the access point device sends a first trigger frame to the first non-access point device during the first TWT SP period, and the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

[0323] The access point device sends a first trigger frame to a first non-access point device to schedule the first non-access point device to perform P2P transmission on a first P2P link. After receiving the first trigger frame, the first non-access point device replies with a response frame to the access point device, indicating that the first access point device can perform P2P transmission on the first P2P link. The response frame may be a CTS frame.

[0324] In the embodiment of the present application, the access point device sends a first trigger frame to the initiators of each P2P link in at least one P2P link to schedule these initiators to perform P2P transmission on the corresponding P2P link.

[0325] In one example, as shown in Figure 20A, the link between STA1 and STA2 is link 1, and STA1 is the initiator of link 1. The link between STA3 and STA4 is link 2, and STA3 is the initiator of link 1. After the AP competes for the transmission opportunity in the first TWT SP, it sends the first trigger frame to STA1 and STA3 respectively. After receiving the first trigger frame, STA1 and STA3 respectively reply with CTS frames to the AP. After replying to the CTS frame, STA1 performs P2P transmission with STA2 on link 1 (sending data frames to STA2). After replying to the CTS frame, STA3 performs P2P transmission with STA4 on link 2 (sending data frames to STA4).

[0326] In some embodiments, the first trigger frame includes a multi-user request to send transmission state trigger (MU-RTS TXS Trigger) frame.

[0327] The access point device sends a MU-RTS TXS Trigger frame to at least one non-access point device including the first non-access point device, thereby triggering the at least one non-access point device to perform P2P transmission on a corresponding P2P link.

[0328] In some embodiments, the first trigger frame includes at least one user information field, the user information field includes sixth indication information, and the sixth indication information is used to indicate a member site of the first TWT SP.

[0329] The first trigger frame includes at least one user information field, and the user information field includes an indication of a member site of the first TWT SP that is a transmission opportunity sharing object. That is, a user information field is used to indicate a transmission opportunity sharing object. When the first trigger frame includes at least one user information field, it indicates at least one transmission opportunity sharing object.

[0330] In some embodiments, the sixth indication information includes the following address information of the corresponding member site: AID12, where AID12 represents the AID of the transmission opportunity sharing object.

[0331] In some embodiments, the user information field may further include eighth indication information, where the eighth indication information is used to indicate an allocation duration. The allocation duration may be understood as the duration of a transmission opportunity allocated by the AP and shared with corresponding non-access point devices.

[0332] It can be understood that the duration indicated by the eighth indication information is less than or equal to the first TWT SP.

[0333] For the scenario shown in Figure 20A, assuming that TWT is an individual P2P TWT, when the P2TWT SP of STA1 and STA2 overlaps with the P2P TWT SP of STA7 and STA8, the AP competes for TXOP, which can theoretically be shared with STA1 and STA7. As shown in Figure 20, STA1 and STA7 are simultaneously triggered for P2P transmission through the MU-RTS TXS trigger frame. The Triggered TXOP Sharing Mode field in the MU-RTS TXS trigger frame indicates that the current TXOP sharing mode is for P2P. The MU-RTS TXS trigger frame will carry two User Info fields, indicating STA1 and STA7 respectively. At this time, although STA1 and STA7 are member sites of different P2P TWT SPs, they can still be scheduled in the same time period. For the scenario shown in Figure 20A, assuming that the TWT is a broadcast P2P TWT, the AP competes for the TXOP, and the MU-RTS TXS trigger frame is used to simultaneously trigger STA1 and STA7 to perform P2P transmission. At this time, STA1 and STA7 are member sites of the same P2P TWT SP.

[0334] For case 1, in some embodiments, during the first TWT SP, at least one of the following is satisfied:

[0335] The member stations of the first TWT SP do not compete for transmission opportunities;

[0336] The non-member stations of the first TWT SP freely compete for transmission opportunities or use first channel access parameters to compete for transmission opportunities or are in a silent state in a first interval published by the access point device, and the first interval partially or completely overlaps with the first TWT SP in the time domain;

[0337] The access point device uses a second channel access parameter to compete for a transmission opportunity, and the priority of the second channel access parameter is higher than the priority of the first channel access parameter.

[0338] In an embodiment of the present application, the channel access parameter may be an EDCA parameter, wherein the first channel access parameter may be EDCA parameter 2, i.e., the EDCA parameter for non-member sites within the SP, and the second channel access parameter may be independent of the EDCA access parameter of the TWT SP.

[0339] In trigger-based scheduling:

[0340] The access point device competes for a transmission opportunity, and competes for the transmission opportunity based on the second channel access parameter.

[0341] Optionally, the access point device competes for transmission opportunities on the first channel of the first TWT SP.

[0342] For the member sites of the first TWT SP, there is no competition for the transmission opportunity. After the access point device competes for the transmission opportunity, the transmission opportunity is shared with the member sites of the first TWT SP.

[0343] For non-member sites of the first TWT SP, they compete with the access point device for transmission opportunities or do not compete with the access point device for transmission opportunities. If they compete with the access point device for transmission opportunities, they can compete for transmission opportunities in a free competition manner, or compete for transmission opportunities using the first channel access parameter, wherein the priority of the first channel access parameter is lower than the priority of the second channel access parameter. It can be understood that the channel access parameter is the priority of the EDCA parameter, and the priority of the EDCA parameter of the access point device is higher than the EDCA parameter of the non-member site of the first TWT SP. If they do not compete for transmission opportunities, the access point device can publish a first interval, and the non-member site of the first TWT SP is in a silent state in the first interval, wherein the first interval overlaps with the first TWT SP in whole or in part in the time domain.

[0344] Case 2: Non-trigger-based scheduling, also known as non-trigger mode

[0345] Case 2 can be considered as non-triggered scheduling. Each member site of at least one member site of the first TWT SP competes for a transmission opportunity and performs P2P transmission on the competed transmission opportunity.

[0346] In the second scenario, after each member site of the first TWT SP competes for a transmission opportunity, it performs P2P transmission on the P2P link between the member sites and the peer end. The P2P transmissions of these P2P links do not interfere with each other when performed simultaneously.

[0347] In one example, as shown in Figure 20B, the link between STA1 and STA2 is link 1, and STA1 is the initiator of link 1. The link between STA3 and STA4 is link 2, and STA4 is the initiator of link 1. In the first P2P TWT SP, STA1 and STA4 compete for transmission opportunities, and after competing for transmission opportunities, they send RTS frames to STA2 and STA3 on the other end respectively. After STA2 replies to STA1 with a CTS frame, it performs P2P transmission with STA1 on link 1 (STA1 sends data frames to STA2). After STA3 replies to ST4 with a CTS frame, it performs P2P transmission with STA4 on link 2 (STA4 sends data frames to STA2).

[0348] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, during the first TWT SP, at least one of the following is satisfied:

[0349] The member stations of the first TWT SP compete for transmission opportunities using third channel access parameters;

[0350] The non-member sites of the first TWT SP freely compete for transmission opportunities or use the first channel access parameter to compete for transmission opportunities or are in a silent state during the first interval published by the access point device, the first interval partially or completely overlaps with the first TWT SP in the time domain, and the priority of the third channel access parameter is higher than the priority of the first channel access parameter.

[0351] In non-trigger based scheduling:

[0352] For the member stations of the first TWT SP, the third channel access parameter is used to compete for the transmission opportunity.

[0353] For non-member sites of the first TWT SP, they compete with the member sites of the first TWT SP for transmission opportunities or do not compete with the member sites of the first TWT SP for transmission opportunities. If they compete with the member sites of the first TWT SP for transmission opportunities, they can compete for transmission opportunities in a free competition manner, or use the first channel access parameter to compete for transmission opportunities, wherein the priority of the first channel access parameter is lower than the priority of the third channel access parameter. It can be understood that the channel access parameter is the EDCA parameter, and the priority of the EDCA parameter of the member sites of the first TWT SP is higher than the priority of the EDCA parameter of the non-member sites of the first TWT SP, and the member sites of the first TWT SP compete for transmission opportunities first. If there is no competition for transmission opportunities, the access point device can publish a first interval, and the non-member sites of the first TWT SP are in a silent state in the first interval, wherein the first interval overlaps with the first TWT SP in whole or in part in the time domain.

[0354] In the embodiment of the present application, the third channel access parameter may be EDCA parameter 1, ie, an access parameter for member sites within an SP.

[0355] If it is a non-trigger mode, the member sites of the P2P TWT SP will use high-priority parameters to compete for TXOP within the P2P TWT SP, thereby starting P2P transmission, while the non-P2P TWT member sites do not compete or use low-priority parameters to compete for TXOP.

[0356] In some embodiments, member stations and non-member stations of a first TWT SP compete for transmission opportunities on a first channel of the first TWT SP.

[0357] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, then:

[0358] A channel used by the first P2P link between the first non-access point device and the second non-access point device is a secondary channel of a first BSS, traffic of the first BSS is transmitted on a primary channel of the first BSS, and the first BSS is the BSS to which the first non-access point device belongs.

[0359] In an embodiment of the present application, the member sites of the first TWT SP compete for transmission opportunities on the secondary channel, thereby performing P2P transmission on the secondary channel, and the non-access point devices that transmit BSS traffic compete for transmission opportunities on the main channel, thereby transmitting BSS traffic on the main channel, so that P2P transmission and BSS transmission exist at the same time.

[0360] The following further describes the resource scheduling method provided in the embodiment of the present application.

[0361] Therefore, the present invention proposes a P2P TWT mode, where the AP allocates a P2P TWT SP. Within the P2P TWT SP, the AP schedules multiple pairs of P2P traffic for simultaneous transmission, thereby achieving optimal scheduling. To determine the P2P TWT SP, the AP needs to perform link measurement. After the P2P TWT SP is determined, the AP needs to ensure the smooth execution of the transmission plan.

[0362] The resource scheduling method provided in the embodiment of the present application involves the following aspects:

[0363] First, the P2P TWT establishment process and frame element design for single-link devices;

[0364] The second aspect is the P2P TWT establishment process and frame element design of multi-link devices;

[0365] Thirdly, the scheduling method and frame element design of P2P traffic transmission;

[0366] Fourthly, channel access rules within P2P TWT SP.

[0367] Below, each aspect is described separately.

[0368] First, the P2P TWT establishment process and frame element design of single-link devices

[0369] As shown in Figure 21, the process of establishing a TDLS direct link and a P2P TWT includes:

[0370] S2101, establish a TDLS direct link

[0371] A P2P STA uses the TDLS establishment procedure to establish a TDLS direct link. During the establishment process, when a P2P STA transmits a TDLS establishment request / response / confirmation frame, it should carry information about resources available for P2P use. The request and response frames carry information about resources available for P2P use by each P2P STA, while the confirmation frame carries information about resources available for P2P use by both parties, i.e., the intersection of the resource information in the request and response frames.

[0372] S2102: The P2P STA sends a P2P link report to the AP.

[0373] After the TDLS direct link is established, the P2P STA can proactively send a peer-to-peer link report to the AP. The peer-to-peer link report frame carries information related to the TDLS direct link. S2002 is optional.

[0374] S2103. Establish a P2P TWT.

[0375] As shown in FIG. 21 , S2103 includes the following steps:

[0376] S2131. The P2P initiator applies for a P2P TWT from the AP.

[0377] The P2P STA sends a TWT establishment request frame to the AP to apply for establishing a P2P TWT.

[0378] S2132: The AP performs link measurement.

[0379] The AP obtains the resource usage within the BSS, basic information about the P2P link, and the location information of the STA through CSI reports, peer-to-peer link reports, and Location Civic reports. Based on the information obtained, the AP negotiates with the P2P STA to determine the most appropriate P2P TWT SP.

[0380] It should be noted that the AP does not start link measurement after receiving the TWT establishment request frame. The AP may also perform link measurement at other times, depending on the specific implementation. If the AP has already obtained the link measurement information, it can stop performing link measurement after receiving the TWT establishment request frame. Similarly, after receiving the TWT establishment request frame, the AP can send a Peer-to-peer Link Report Request frame to the P2P STA to request the P2P STA to send a peer-to-peer link report. This also depends on the specific implementation. The AP may not request the P2P STA to send a peer-to-peer link report.

[0381] S2133. The AP allocates a P2P TWT SP to the P2P STA.

[0382] The AP sends the P2P TWT SP and P2P TWT establishment status to the P2P STA that applies to establish the P2P TWT through the TWT establishment response frame.

[0383] S2104. AP broadcasts P2P TWT.

[0384] After the P2P TWT is established, the AP carries a TWT element containing P2P TWT information in the Beacon frame, (re)association frame, and probe response frame.

[0385] S2105. The P2P peer applies to join the P2P TWT.

[0386] After the P2P peer receives a frame carrying a TWT element containing P2P TWT information, it can use the information in the TWT element to confirm whether it needs to join the current P2P TWT. If so, it only needs to send a TWT establishment request frame to the AP, where the TWT element is filled according to the content in the TWT element broadcast by the AP.

[0387] When the P2P peer joins the P2P TWT, the establishment of the P2P TWT is completed.

[0388] S2106. The P2P STA transmits P2P traffic within the P2P TWT SP.

[0389] There are two ways to schedule P2P STAs to transmit traffic within a P2P TWT SP:

[0390] The first is trigger-enabled scheduling, where the AP uses TXOP sharing within the P2P TWT SP to schedule multiple pairs of P2P links for transmission simultaneously. These P2P links transmit simultaneously without interfering with each other.

[0391] The second type is based on non-trigger-enabled scheduling. Within the P2P TWT SP, P2P STAs actively compete for channels and prioritize P2P traffic transmission within TXOPs. If there are multiple pairs of P2P links that do not interfere with each other, the TXOPs of the P2P STAs of these P2P links may overlap, enabling simultaneous transmission of multiple pairs of P2P links within the P2P TWT SP.

[0392] Next, the steps shown in FIG. 21 will be described in detail.

[0393] As for S2101, the implementation of this step is based on the TDLS direct link establishment process shown in FIG6, and the frames used are TDLS establishment request / response / confirmation frames, such as.

[0394] During the TDLS direct link establishment process, TDLS STAs need to carry information about the time and frequency domain resources available for P2P transmission in the TDLS Setup Request / Response / Confirmation frames. The TDLS Setup Request / Response / Confirmation frames transmitted by the TDLS STAs need to carry one or more Per-STA Profile elements.

[0395] As shown in Figure 22, a P2P available window list (Available Window List Present) bit is added to the STA Control field of the Per-STA Profile element to indicate whether a subfield P2P available window list (P2P Available Window List) exists in the STA Info field. As shown in Figure 22, the Per-STA Profile element includes the following fields: 1-byte Subelement ID, 1-byte Length, 2-byte STA Control, byte-variable STA Info, and byte-variable STA Profile. The STA Control field includes the following subfields: 4-bit Link ID, 1-bit Complete Profile, 1-bit STA MAC Address Present, 1-bit Beacon Interval Present, 1-bit TSF Offset Present, 1-bit DTIM Info Present, 1-bit BSS Parameters Change Count Present, 1-bit P2P Available Window List Present, and 4-bit Reverse. The Subelement ID field indicates the element ID, and the Length field indicates the element length. The STA Control field contains some control information, of which the Link ID subfield is used to uniquely identify the link to which the STA is located. The Complete Profile subfield indicates whether the element carries complete configuration information. If the value is 1, it indicates that the element carries complete configuration information; otherwise, it carries partial information. This complete or partial information is carried in the STA Profile field. The STA MAC Address Present subfield indicates whether the STA Info field contains the STA's MAC address. A value of 1 indicates that it contains the STA's MAC address; otherwise, it does not. The Beacon Interval Present subfield indicates whether the STA Info field contains the Beacon Interval subfield. A value of 1 indicates that it contains the Beacon Interval subfield; otherwise, it does not. The TSF Offset Present subfield indicates whether the STA Info field contains the TSF Offset subfield. A value of 1 indicates that it contains the TSF Offset subfield; otherwise, it does not.The value is 1 only when the AP sends this element. The DTIM Info Present subfield indicates whether the STA Info field contains the DTIM Info subfield. A value of 1 indicates that it is included; otherwise, it is not included. The BSS Parameters Change Count Present subfield indicates whether the STA Info field contains the BSS Parameter Change Count subfield. A value of 1 indicates that it is included; otherwise, it is not included. The P2P Available Window List Present subfield indicates whether the STA Info field contains the P2P Available Window List subfield. A value of 1 indicates that it is included; otherwise, it is not included.

[0396] As shown in Figure 23, the P2P Available Window List subfield is added to the STA Info field of the Per-STA Profile element. This subfield can contain one or more P2P Available Windows, each of which represents a section of time-domain and frequency-domain resource information that can be used for P2P transmission. The P2P Available Window in the TDLS Setup Request frame represents the time-domain and frequency-domain resource information that the TDLS initiator can use for P2P transmission. Similarly, the P2P Available Window in the TDLS Setup Response frame represents the time-domain and frequency-domain resource information that the TDLS responder can use for P2P transmission. The P2P Available Window in the TDLS Setup Confirmation frame represents the time-domain and frequency-domain resource information that both the TDLS requester and the TDLS responder can use for P2P transmission, that is, the intersection of the time-domain and frequency-domain resource information that can be used for P2P transmission carried in the TDLS Setup Request / Response frames.

[0397] As shown in Figure 23, the STA Info field includes the following subfields: 1-bit STA information length (STA Info Length), 0 or 6-bit STA MAC Address, 0 or 2-bit beacon interval (Beacon Interval), 0 or 8-bit TSF offset (TSF Offset), 0 or 2-bit DTIM information (DTIM Info), 0 or 1 or 2-bit BSS parameter change count (BSS Parameters Change Count), and variable-bit P2P Available Window List. The STA Info field contains some parameter information, among which the STA Info Length subfield indicates the length of the STA Info field; the STA MAC Address subfield indicates the MAC address of the STA; the Beacon Interval subfield indicates the Beacon interval of the BSS where the STA is located; the TSF Offset subfield indicates the offset of the TSF timer between the AP and the STA; the DTIM Info subfield indicates the DTIM information, including the DTIM Count and DTIM Period; the BSS Parameters Change Count subfield indicates the number of BSS parameter changes; and the P2P Available Window List subfield contains zero or more P2P available window (P2P Available Window) fields.

[0398] As shown in Figure 23, each P2P Available Window contains four parts: a 1-bit operating class, a 1-bit channel, a 1-bit offset, and a 2-bit duration. The Operating Class indicates the operating class of the current P2P Available Window. The Channel indicates the channel number of the P2P Available Window. Different Operating Classes can have different channel ranges and allocation methods. The Channel and Operating Class are used together to determine the wireless channel resources where the P2P Available Window is located. The Offset indicates the start time of the P2P Available Window and is an offset whose value is the remainder of the TSF divided by the beacon interval. The Duration indicates the duration of the P2P Available Window, and the default unit is ITU.

[0399] For S2102

[0400] The peer-to-peer link report is sent by both stations that establish or tear down the P2P link to the AP. The P2P STA can report proactively or wait for the AP to send a report request frame before reporting.

[0401] Peer-to-peer link reporting provides a mechanism for non-AP STAs to report peer-to-peer connection events to the AP. When a peer-to-peer link is established or terminated, the P2P STA records the peer-to-peer link event. Peer-to-peer link events can be simply divided into establishment and termination. When a P2P link is established, the P2P STA records the establishment event. When a P2P link is terminated, the P2P STA records the termination event and deletes the corresponding P2P link establishment time.

[0402] After the TDLS direct link is established, the TDLS initiator and / or TDLS responder optionally sends a peer-to-peer link report frame to the AP. The Event Report field in the Event Report element carries the P2P Available Window List field. The function of the P2P Available Window List field is consistent with that described above and will not be repeated here. The information carried in the P2P Available Window List field here is consistent with that in the TDLS Establishment Confirmation frame, namely, the intersection of the time and frequency domain resource information available for P2P transmission between the two TDLS sites. The format of the peer-to-peer link report field is shown in Figure 24 and includes the following fields: a 1-byte Category, a 1-byte WNM Action, a 1-byte Dialog Token, and a variable-byte Event Report Elements. The Category field indicates the current frame type; the WNM Action field indicates the WNM type of the current frame; the Dialog Token field identifies the current session; and the Event Report Elements field carries event report information.

[0403] As shown in Figure 24, the Event Report Elements field includes the following subfields: a 1-byte element identifier (Element ID), a 1-byte length, a 1-byte event token (Event Token), a 1-byte event type (Event Type), a 1-byte event report status (Event Report Status), a 0- or 8-byte event TSF (Event TSF), a 0- or 10-byte UTC offset (UTC Offset), a 0- or 5-byte event time error (Event Time Error), and a variable-byte event report (Event Report); wherein, the Element ID indicates the ID of the current element, which is used to identify the element; the Length subfield indicates the length of the current element; the Event Token subfield identifies the current event; the Event Type subfield indicates the type of the current event; the Event Report Status subfield indicates the status of the event report; if the Event TSF subfield exists, it indicates that the STA records the TSF value of the event; if the UTC Offset subfield exists, it indicates the UTC time when the TSF is 0; if the Event Time Error subfield exists, it indicates the standard deviation of UTC; and the Event Report subfield contains a report on the specified event.

[0404] As shown in Figure 24, the Event Report includes the following information: 6-bit peer STA or BSS ID address (Peer STA / BSSID Address), 1-bit operating class (Operating Class), 1-bit channel number (Channel Number), 1-bit STA transmit power (STA Tx Power), 3-bit connection time (Connection Time), 1-bit peer status (Peer Status) and variable bit (P2P Available Window List). The Peer STA / BSSID Address field indicates the MAC address of the STA if it is a P2P link within a BSS, or the BSSID of the IBSS if it is a P2P link within an IBSS. The Operating Class field indicates the operating class of the P2P link. The Channel Number field indicates the channel on which the P2P link resides. The STA Tx Power field indicates the transmit power of the STA on the P2P link. The Connection Time field indicates the connection time in seconds and is meaningful only when combined with the Peer Status field. The Peer Status field indicates the status of the P2P link. A value of 0 indicates that the P2P link has terminated, and the Connection Time field indicates the duration of the P2P link. A value of 1 indicates that the P2P link is still operating, and the Connection Time field indicates the time difference between the establishment of the P2P link and the reporting of the event. A value of 2 indicates that the P2P link has terminated and is within an IBSS, and the Connection Time field indicates the time duration since the STA became a member of the IBSS. A value of 3 indicates that the P2P link is still operating and is within an IBSS, and the Connection Time field indicates the time difference between the STA becoming a member of the IBSS and the reporting of the event. The frame format of List is shown in Figure 23.

[0405] Optionally, after the TDLS direct link is established, the TDLS initiator and / or TDLS responder may choose not to actively send. During the process of establishing the P2P TWT, when the AP receives a P2P TWT request frame from the P2P STA, it may actively send a peer-to-peer link event request frame to the P2P STA to request the other party to send a peer-to-peer link report frame.

[0406] For S2031 in S2103

[0407] After the TDLS direct link is established, the P2P STA should apply to the AP to establish a P2P TWT. The P2P STA sends a TWT Establishment Request frame to the AP. The TWT element carried in the TWT Establishment Request frame contains the TWT parameters expected by the P2P STA. The AP responds with a TWT Establishment Response frame. If the AP agrees, the TWT element carried in the TWT Establishment Response frame contains the TWT parameters in the TWT Establishment Request frame. If the AP rejects, the TWT element is not carried. Establishing a P2P TWT is a negotiation process.

[0408] During the P2P TWT establishment process, the P2P STA needs to provide some necessary information to the AP. Therefore, the TWT elements must include at least:

[0409] First, it indicates that the TWT currently being negotiated is a P2P TWT;

[0410] Second, it carries the identification information of the P2P peer, namely the MAC address and AID.

[0411] Regarding the first point, a value of 5 is added to the Broadcast TWT Recommendation in the Request Type subfield of the TWT Parameter Information field of the TWT element, indicating that the current broadcast TWT is a P2P TWT. The format of the modified TWT element is shown in Figure 25, and the definition of Broadcast TWT Recommendation is shown in Table 1.

[0412] Table 1. Example of Broadcast TWT Recommendation definition

[0413] As shown in Figure 25, the TWT element includes the following fields: 1-byte Element ID, 1-byte Length, 1-byte Control, and variable-byte TWT Parameter Information. Among them, the Element ID field represents the ID of the element, which is used to uniquely identify the element; the Length field represents the length of the element; the Control field contains some control information; and the TWT Parameter Information field contains TWT parameter information. As shown in Figure 25, the TWT Parameter Information field includes the following subfields: 1-byte Request Type, 2-byte TWT (Target Wake Time), 1-byte Nominal Minimum TWT Wake Duration, 2-byte TWT Wake Inteval Mantissa, 1-byte Broadcast TWT Info, and 0 or 3 bytes of Restricted TWT Traffic. Among them, the Target Wake Time field indicates the wake-up time of the current TWT; the Nominal Minimum TWT Wake Duration field indicates the minimum duration of the TWT SP; the TWT Wake Interval Mantissa field and the TWT Wake Interval Exponen are used together to calculate the TWT interval; the Broadcat TWT Info field contains the information of the broadcast TWT; the Restricted TWT Traffic field indicates the TID traffic indication information of the r-TWT;.

[0414] The Request Type subfield includes the following information: 1-bit TWT request (TWT Request), 2-bit TWT setup command (TWT Setup Command), 1-bit trigger (Trigger), 3-bit last broadcast parameter set (Last Broadcast Parameter Set), 1-bit flow type (Flow Type), 3-bit broadcast TWT recommendation (Broadcast TWT Recommendation), 5-bit TWT wake interval index (TWT Wake Interval Exponent) and 1-bit reserved. Among them, the Request Type subfield indicates the request type of the element; the TWT Request field indicates the role of the current STA. If the STA is a TWT requesting STA, it is set to 1, otherwise it is 0; the TWT Setup Command subfield indicates the TWT command; the Trigger subfield indicates whether the established TWT is trigger-based. If it is 1, it means that the TWT is trigger-based, otherwise the TWT is non-trigger-based; the Last Broadcast Parameter Set subfield indicates whether the Broadcast Parameter Set is the last one of the broadcast TWT element; the Flow Type subfield indicates whether the TWT is an announced TWT. A value of 1 indicates that it is an announced TWT, otherwise it is an unannounced TWT; the Broadcast TWT Recommendation subfield indicates the type of the current broadcast TWT; the TWT Wake Interval Exponent subfield indicates the exponent of the current TWT wake-up interval, which is calculated together with the TWT Wake Interval Mantissa field to calculate the TWT interval.

[0415] Regarding the second point, a P2P Peer subfield is added to the TWT Parameter Information of the TWT element. This subfield only exists in the P2P TWT and contains the MAC address and AID of the P2P Peer. The format of this subfield is shown in Figures 25 and 26. The TWT Parameter Information includes an 8-bit P2P peer (P2P Peer). The P2P Peer field uniquely identifies the P2P Peer. The P2P Peer field contains a 6-byte P2P peer MAC address (P2P Peer MAC Address) and a 2-bit P2P peer AID (P2P Peer AID). The former is the MAC address of the P2P Peer, and the latter is the AID value of the P2P Peer.

[0416] In addition to these two points, a 1-byte Channel subfield is added to the TWT Parameter Information field, as shown in Figures 25 and 26. This subfield also exists only in P2P TWTs and is used to indicate the channel used for P2P transmission of the link corresponding to the current TWT element.

[0417] The AP can obtain the channel model and location information of each STA in the BSS through the CSI report. When the AP receives the P2P TWT establishment request from the P2P STA, the AP will select the optimal P2P TWT SP based on the current channel model, the location information of the P2P STAs and the resource information in the peer-to-peer link report, and send the final P2P TWT SP to the P2P STA that initiated the TWT establishment through the TWT element carried in the TWT response frame.

[0418] It should be noted that Figures 22 to 26 are examples of frame structures of different frames. The fields in each frame can be split or other fields can be added based on the above structure. The size of each field is only an example, and the size of each field can vary according to actual needs.

[0419] For S2034 in S2103

[0420] After the P2P STA negotiates with the AP to establish a P2P TWT, the AP carries the TWT element in the beacon frame, probe response frame and / or (re)association frame. When the P2P peer receives the frame containing the TWT element, it parses the frame and obtains its own identification information from the P2P peer.

[0421] For S2105

[0422] In the final step, the P2P peer applies to the AP to join the P2P TWT. This step is consistent with the existing broadcast TWT mechanism. The P2P STA transmits P2P services in the P2P TWT SP. Finally, the complete P2P TWT establishment process is shown in Figure 27:

[0423] The TDLS initiator sends a TDLS setup request frame carrying a P2P available window list to the AP, and the AP forwards the received TDLS setup request frame to the TDLS peer. The P2P available window list indicates the resources used by the TDLS initiator for the TDLS link.

[0424] The TDLS peer sends a TDLS setup response frame carrying a P2P available window list to the AP, and the AP sends the received TDLS setup response frame to the TDLS initiator, wherein the P2P available window list indicates the resources used by the TDSL peer for the TDLS link.

[0425] The TDLS initiator sends a TDLS setup confirmation frame carrying a P2P available window list to the AP, and the AP forwards the received TDLS setup confirmation frame to the TDLS peer. The P2P available window list indicates the negotiated resources for the TDLS link.

[0426] Optionally, after the TDLS link is established, the TDLS initiator or the TDLS peer sends a P2P link report frame to the AP. The P2P link report frame carries a P2P available window list, and the P2P available window list indicates the negotiated resources for the TDLS link.

[0427] The TDLS initiator sends a TWT establishment request frame to the AP. The TWT element carried in the TWT establishment request frame includes the following information: the broadcast TWT recommendation information with a value of 5, namely the first indication information, the parameters of the P2P peer, and the channel number. The first indication information is used to indicate that the established TW is a TWT for P2P, the parameters of the P2P peer indicate the P2P peer, and the channel number indicates the channel of the TDLS link.

[0428] After the AP receives the TWT establishment request frame from the TDLS initiator, if it does not receive the P2P link report, it can send a P2P link event request frame to the TDLS initiator, and the TDLS initiator responds to the P2P link event request frame by sending a P2P link report frame to the AP. The 2P link report frame carries a P2P available window list, and the P2P available window list indicates the negotiated resources for the TDLS link.

[0429] The AP determines the TWT SP based on the resources of the received TDLS link and returns a TWT establishment response frame to the TDLS initiator. The TWT establishment response frame carries the TWT SP and TWT elements. The TDLS initiator joins the TWT and becomes a member site of the TWT SP.

[0430] The AP broadcasts a Beacon frame that carries the AP and TWT elements. Upon receiving the Beacon frame, the TDLS peer determines that it is destined for it and decides whether to join the TWT. If so, it sends a TWT Setup Request frame carrying the TWT element to the AP. The AP returns a TWT Setup Response frame carrying the TWT element to the TDLS peer, and the TDLS peer joins the TWT and becomes a member site of the TWT.

[0431] It is understandable that when establishing TWT, after the TDLS initiator (belonging to the P2P link initiator) joins the TWT, the TDLS peer (belonging to the P2P link responder) may or may not join the TWT.

[0432] Second aspect: P2P TWT establishment process and frame element design for multi-link devices

[0433] Regarding the establishment of TDLS direct links for multi-link devices, the relevant standards only define the rules for multi-link devices to establish TDLS direct links on one link. The embodiment of this application is the establishment of P2P TWT. In order to describe the establishment of P2P TWT for multi-link devices, it is necessary to involve the establishment process of TDLS direct links for multi-link devices.

[0434] 1) Establishing a TDLS direct link

[0435] The embodiment of the present application provides a feasible multi-link TDLS direct link establishment. Similar to the establishment of a TDLS direct link by a single-link device, it is proposed that when a multi-link device establishes a direct link, it is consistent with the establishment of a TDLS direct link by a single-link device, and one or more Per-STA Profile sub-elements are carried in the TDLS establishment request / response / confirmation frame. Each Per-STA Profile sub-element indicates that the TDLS STA MLD needs to establish an affiliated STA of the TDLS direct link.

[0436] As shown in Figure 28, multi-link devices can establish multiple TDLS direct links simultaneously on a single link. In the figure, after the TDLS Setup Response frame, STA1 also needs to reply with a TDLS Setup Confirmation frame, which contains two Per-STA sub-elements.

[0437] 2) Peer-to-peer link report

[0438] After a TDLS direct link is established, the TDLS Initiator MLD and TDLS Peer MLD also need to proactively send peer-to-peer link reports to the AP MLD. Unlike single-link devices, multi-link devices may establish multiple TDLS direct links simultaneously. Therefore, as shown in Figure 28, the TDLS Setup Request frame sent by MLD_S to MLD_R must carry multiple peer-to-peer link report fields, each indicating the establishment and availability of a non-AP STA's TDLS direct link. Furthermore, the TDLS Setup Response frame sent by MLD_R to MLD_S must carry multiple peer-to-peer link report fields, each indicating the establishment and availability of a non-AP STA's TDLS direct link. This establishes the following two TDLS links: a TDLS direct link between MLD_S's subordinate STA1 and MLD_R's subordinate STA3, and a TDLS direct link between MLD_S's subordinate STA2 and MLD_R's subordinate STA4.

[0439] Optionally, the TDLS Initiator MLD and TDLS Peer MLD do not need to be sent proactively. The AP MLD obtains reports through peer-to-peer link requests.

[0440] 3) Establish P2P TWT

[0441] When a multi-link device establishes multiple TDLS direct links at the same time, there is a problem, that is, traffic identifier (TID) mapping. The embodiment of the present application proposes a solution.

[0442] When the TDLS STA MLD requests the AP MLD to establish a P2P TWT, the process is the same as for single-link devices, but the information contained in the frame is slightly different. This embodiment of the application uses the restricted TWT Traffic Info subfield. If the current broadcast TWT is a P2P TWT, then:

[0443] First, each TWT element represents a link, and the TWT Parameter Information field represents the parameters of the current link;

[0444] Second, the value of Broadcast TWT Recommendation is 5. The TWT Parameter Information field also needs to include P2P Peer and Channel, and the values ​​of DL TID Bitmap Valid and UL TID Bitmap Valid in Traffic Info Control are both 1. The Restricted TWT DL / UL TID Bitmap in each TWT element will indicate the TID on the corresponding TDLS direct link. At this time, DL no longer indicates downlink traffic, but indicates traffic from the TDLS Initiator STA to the TDLS Response STA. Conversely, UL indicates traffic from the TDLS Response STA to the TDLS Initiator STA.

[0445] 4) Broadcast TWT scheduling information

[0446] After the P2P MLD negotiates with the AP MLD to establish the P2P TWT, the AP MLD carries the TWT element in the beacon frame, probe response frame, and / or (re)association frame. When the P2P peer MLD receives the frame containing the TWT element, it parses the frame and obtains its own identification information from the P2P peer.

[0447] 5) P2P Peer MLD joins P2P TWT

[0448] In the final step, the P2P Peer MLD applies to the AP MLD for joining the P2P TWT. This step is consistent with the existing broadcast TWT mechanism. The P2P MLD transmits P2P services within the P2P TWT SP.

[0449] Third aspect: P2P traffic transmission scheduling method and frame element design

[0450] After the P2P TWT is established, the P2P STA needs to execute a specific transmission plan. The embodiment of the present application proposes two feasible scheduling methods: the first method is trigger-enabled scheduling, and the other is non-trigger-enabled scheduling.

[0451] 1) trigger-enabled

[0452] After the P2P TWT is established, P2P STAs need to execute a specific transmission plan, using AP-triggered scheduling to schedule P2P STAs for P2P traffic transmission. Multiple P2P links may share the same P2P TWT SP segment, and these P2P links do not interfere with each other. In this case, the AP needs to simultaneously schedule multiple P2P STAs to transmit within the same P2P TWT SP segment. Therefore, a new TXOP sharing mode must be defined specifically for P2P traffic transmission, and the P2P STAs with whom the TXOP is shared must be specified.

[0453] As shown in Figure 29, the Triggered TXOP Sharing Mode subfield in the Common Info field carried by the MU RTS TXS Trigger frame adds a value of 3 to indicate that the current TXOP is shared with P2P STAs for P2P traffic transmission. For the value of the Trigger TXOP Sharing Mode subfield, refer to Table 2.

[0454] Table 2. Triggered TXOP Sharing Mode subfield value examples

[0455] The MU-RTS TXS Trigger frame needs to carry one or more User Info fields, which are used to indicate the STA. If the Triggered TXOP Sharing Mode value is 3, the User Info field is used to indicate the target STA of TXOP Sharing, where AID12 represents the AID of the target STA of TXOP Sharing, and the time period allocated by Allocation Duration cannot exceed the P2P TWT SP.

[0456] As shown in Figure 29, the TWT SP is a triggered TWT SP. The AP competes for TXOP in the P2P TWT SP by sending a self-permitted transmission (CTS-to-self). After competing for the transmission opportunity, the AP uses the MU-RTS TXS Trigger frame to inform its member stations and allocate resources to the member stations. STA1 and STA7 are member stations of the TWT SP, thereby scheduling STA1 and STA7 for P2P transmission. STA1 and STA7 first transmit CTS to the AP in response to receiving the MU-RTS TXS Trigger frame, and then transmit P2P traffic within the time period allocated by the MU-RTS TXS Trigger frame. P2P transmission is performed between STA1 and ST2, and P2P transmission is performed between STA7 and STA8. After STA2 receives traffic or data on the P2P link, it returns a BA frame to STA1. After STA8 receives traffic or data on the P2P link, it returns a BA frame to STA7.

[0457] 2) Non-trigger-enabled

[0458] Non-trigger-enabled scheduling is a rule whereby STAs that are members of the current P2P TWT SP actively compete for channels within a P2P TWT SP. If they are awarded a TXOP, P2P traffic is prioritized for transmission. STAs that are not members of the P2P TWT SP should avoid competing for TXOPs within the P2P TWT SP whenever possible. Alternatively, to ensure that P2P TWT member STAs have priority transmission within the P2P TWT SP, higher priority EDCA parameters can be set. This is device-specific.

[0459] As shown in Figure 30, for non-triggered TWT SP, at the start time of P2P TWT SP, STA1 starts to compete for TXOP, and sends an RTS frame to STA2 after competing for the transmission opportunity. STA2 replies with a CTS frame to STA1, and then STA1 can prioritize scheduling P2P traffic for transmission within TXOP.

[0460] Since the transmission between STA7, STA8 and the two P2P links of STA1 and STA2 does not interfere with each other, STA8 will also compete for TXOP at the start time of P2P TWT SP, so there is a probability that it can compete for TXOP and give priority to scheduling P2P traffic transmission within TXOP.

[0461] Because non-trigger-enabled scheduling inherently prevents efficient utilization of all resources, there are situations where the P2P TWT SP cannot be fully utilized. For example, in Figure 30, at the beginning of the P2P TWT SP, the P2P TWT member STAs compete for the channel, making it impossible to use it for effective P2P transmission. Furthermore, because the TXOP length may not occupy the entire remaining P2P TWT SP, the resources at the end of the P2P TWT SP cannot be used for effective P2P transmission. It is also possible that within a P2P TWT SP, only one pair of P2P links competes for the TXOP, as shown in Figure 31.

[0462] Because the working channel of the P2P link is specified in the TWT element, there may be P2P traffic transmission using other channels. In this case, BSS traffic transmission can exist on the main working channel of the BSS.

[0463] As shown in Figure 32, STA1 competes for the channel on channel y where the P2P TWT SP is located, while STA3 competes for the channel on the main channel (channel x) of the BSS, and then schedules traffic transmission within the corresponding TXOP, where STA1 schedules P2P traffic to be transmitted on channel y where the P2P TWT SP is located, and STA3 schedules BSS traffic to be transmitted on the main channel.

[0464] Fourthly, channel access rules within P2P TWT SP

[0465] According to the scheduling method of P2P traffic transmission within the P2P TWT SP, the channel access rules within the P2P TWT SP can be roughly divided into two types: the first is the channel access rules within the trigger-enabled P2P TWT SP, and the second is the channel access rules within the non-trigger-enabled P2P TWT SP.

[0466] The channel access between the access point and the non-access point station during the P2P TWT SP follows the channel access rules of the restricted TWT in IEEE 802.11be, and enables the access point to obtain the TXOP first during the trigger-enabled P2P TWT SP and schedule the P2P STA as a member station to perform P2P transmission with the pre-scheduled Peer STA, or the P2P STA as a member station to obtain the TXOP first during the non-trigger-enabled P2P TWT SP to perform P2P transmission with the pre-scheduled Peer STA. Specifically, the channel access rules within the P2P TWT SP may optionally follow: for the non-trigger-enabled P2P TWT SP, if it is a member STA of the current P2P TWT, it uses high-priority EDCA parameters to compete for TXOP, and the STA that is not a member of the current P2P TWT uses low-priority EDCA parameters to compete for TXOP.

[0467] Therefore, the AP carries the P2P TWT EDCA Parameter Set element in the beacon frame to inform all STAs of the EDCA parameters used to compete for TXOP within the P2P TWT SP. The format of this element is shown in Figure 33, including a 1-byte element identifier, a 1-byte length, a 1-byte element identifier extension (Element ID extension), a 0 or 20-byte EDCA parameter set for P2P TWT STAs within the P2P TWT SP (EDCA Parameter Set For P2P TWT STA in P2P TWT SP), and a 0 or 20-byte EDCA parameter set for non-P2P TWT STAs within the P2P TWT SP (EDCA Parameter Set For non P2P TWT STA in P2P TWT SP). EDCA Parameter Set For P2P TWT STA in P2P TWT SP indicates the EDCA parameters used by the member STAs of the P2P TWT when competing for TXOP within the P2P TWT SP. EDCA Parameter Set For non-P2P TWT STA in P2P TWT SP indicates the EDCA parameters used by non-P2P TWT member STAs when competing for TXOP within a P2P TWT SP. A P2P TWT STA is a member station of a P2P TWT SP, and a P2P TWT non-STA is a non-member station of a P2P TWT SP.

[0468] Among them, EDCA Parameter Set For P2P TWT STA in P2P TWT SP and EDCA Parameter Set For non P2P TWT STA in P2P TWT SP are optional. If the P2P TWT EDCA Parameter Set element includes EDCA Parameter Set For P2P TWT STA in P2P TWT SP, the size of this field is 20 bytes, otherwise it is 0 bytes. If the P2P TWT EDCA Parameter Set element includes EDCA Parameter Set For non P2P TWT STA in P2P TWT SP, the size of this field is 20 bytes, otherwise it is 0 bytes.

[0469] 1) Channel access rules within trigger-enabled P2P TWT SP

[0470] Within the trigger-enabled P2P TWT SP, the member STAs of the current trigger-enabled P2P TWT SP should not compete for channels within the P2P TWT SP. The non-member STAs of the current trigger-enabled P2P TWT SP can freely compete for channels within the P2P TWT SP or use low-priority EDCA parameters to compete for channels, or publish quiet interval information that overlaps with part or all of the time period of the P2P TWT SP through the AP, so that the non-member STAs are in a silent state during the corresponding quiet interval.

[0471] For trigger-enabled P2P TWT, when the AP competes for the channel based on the implementation of a method of prioritizing obtaining TXOP during the trigger-enabled P2P TWT SP, for example, a high-priority EDCA parameter may be used.

[0472] After the AP competes for the TXOP, it shares the TXOP with the member STAs of the current trigger-enabled P2P TWT SP through TXOP Sharing. After receiving the MU-RTS TXS trigger frame, the member STAs can schedule P2P traffic for transmission on the P2P link.

[0473] 2) Channel access rules within non-trigger-enabled P2P TWT SP

[0474] For non-trigger-enabled P2P TWT, non-member STAs of the P2P TWT SP freely compete for channels within the P2P TWT SP or use low-priority EDCA parameters to compete for channels, or publish quiet interval information that overlaps with part or all of the time period of the P2P TWT SP through the AP, so that non-member STAs are in a silent state during the corresponding quiet interval.

[0475] Optionally, within a non-trigger-enabled P2P TWT SP, all STAs, including the member STAs of the current non-trigger-enabled P2P TWT SP and the member STAs of non-current non-trigger-enabled P2P TWT SP, can freely compete for channels. In order to ensure that the member STAs of the current non-trigger-enabled P2P TWT SP have a greater probability of transmitting P2P traffic, the following two incentive measures can be implemented:

[0476] 1. The AP carries the P2P TWT EDCA Parameter Set element in the beacon frame to inform the member STAs of the non-trigger-enabled P2P TWT SP and the member STAs of the non-trigger-enabled P2P TWT SP of the EDCA parameters to be used when competing for TXOP;

[0477] 2. After a STA that is not a member of the current non-trigger-enabled P2P TWT SP competes for TXOP, it sends an RTS frame to the AP and prepares to send BSS traffic. The AP can decide whether to reply with a CTS based on the situation. For example, if the current non-trigger-enabled P2P TWT SP is about to end, it can reply with a CTS. If the current non-trigger-enabled P2P TWT SP has just begun, it will not reply with a CTS.

[0478] The transmission control method provided in the embodiments of the present application can be implemented as including but not limited to the following embodiment 1 and embodiment 2.

[0479] Example 1

[0480] In the scenario of Example 1, as shown in Figure 16, STA1, STA2, STA7, and STA8 are all in the same BSS, meeting the conditions for establishing a TDLS direct link. Assume the operating frequency band is 2.4 GHz. The following describes the process of establishing a TDLS direct link and P2P TWT between STA1 and STA2, and between STA7 and STA8.

[0481] 1) STA1 and STA2 establish a TDLS direct link and P2P TWT, where STA1 is the TDLS Initiator and STA2 is the TDLS Peer.

[0482] First, STA1 sends a TDLS Setup Request frame to the AP. This frame is a data frame and carries a Per-STA Profile element. The P2P Available Window List Present value in the STA Control field is set to 1, indicating that STA1 has a P2P Available Window List. The P2P Available Window List contains multiple P2P Available Windows, which indicate the time and frequency domain resources available for P2P transmission by STA1.

[0483] The AP forwards the TDLS Setup Request frame to STA2. STA2 accepts the TDLS direct link establishment request and responds to the AP with a TDLS Setup Response frame. This TDLS Setup Response frame is also a data frame. The TDLS Setup Response frame page carries a Per-STA Profile element. The P2P Available Window List Present bit in its STA Control field is 1. The P2P Available Window List contains multiple P2P Available Windows, which represent the time and frequency domain resource information available to STA2 for P2P transmission.

[0484] The AP forwards the TDLS Setup Response frame to STA1. STA1 then replies with a TDLS Setup Confirmation frame to STA2 through the AP. The P2P Available Window List in the TDLS Setup Confirmation frame indicates that the time and frequency domain resource information available for P2P transmission should be the intersection of the resource information in the TDLS Setup Request / Response frames of STA1 and STA2.

[0485] The TDLS direct link between STA1 and STA2 is established. STA1 and STA2 will report the information of the TDLS direct link to the AP using the peer-to-peer link event report. The information includes: operating frequency band, operating channel, MAC address or BSSID of the TDLS peer STA, transmit power on the TDLS direct link, connection establishment time, current status of the TDLS direct link (including in use, disconnected, etc.), and the P2P Available Window List available for the TDLS direct link.

[0486] Next, STA1 sends a TWT establishment request frame to the AP to request the establishment of a P2P TWT. In the P2P TWT establishment request frame: 1.

[0487] The value of Broadcast TWT Recommendation is 5, indicating that this is a P2P TWT; 2. The value of P2P Peer is: <MAC address of STA2, AID of STA2>.

[0488] When the AP receives this TWT establishment request frame, it needs to determine a P2P TWT SP. Therefore, the AP needs to know the channel information within the BSS and the resource usage information of STA1 and STA2, that is, the AP needs to perform link measurement. The means for the AP to perform link measurement include but are not limited to: Channel State Information (CSI) report, Location Civic report, Peer-to-Peer Link event report, and Sounding technology. The specific process of the AP performing link measurement is placed in the establishment of the TDLS direct link and P2P TWT between STA7 and STA8.

[0489] The AP determines the optimal P2P TWT SP according to the CSI report, Location Civic report, Peer-to-peer link report, and the resource situation provided by STA1, and carries the final P2P TWT SP in the TWT Parameter Information field of the TWT element in the TWT establishment response frame.

[0490] It should be noted that the P2P TWT SP is a negotiation process.至此,P2P TWT建立完毕。

[0491] Finally, the AP will carry the TWT element in the beacon frame and broadcast the P2P TWT within the BSS. STA

[0492] The AP receives a TDLS establishment request frame and replies to STA2 with a TDLS establishment response frame. The TWT setup command in this frame is set to accept TWT, and STA2 successfully joins the P2P TWT.

[0493] 2), STA7 and STA8 establish a TDLS direct link and P2P TWT. Among them, STA7 is the TDLS Initiator and STA8 is the TDLS Peer.

[0494] First, STA7 sends a TDLS establishment request frame to the AP, requesting to establish a TDLS direct link with STA8. The P2P Available Window List in it is set according to STA7 itself. The AP forwards the TDLS establishment request frame to STA8. STA8 agrees to the establishment request of this TDLS direct link. Then, the AP forwards the TDLS establishment response frame to STA7. Finally, STA7 replies to STA8 with a TDLS establishment confirmation frame through the AP. The time-domain and frequency-domain resource information represented by the P2P Available Window List in the frame should be the intersection of the resource information in the TDLS establishment request / response frames of STA7 and STA8.

[0495] The TDLS direct link between STA7 and STA8 is established. STA7 and STA8 use the peer-to-peer link event report to report the information of the TDLS direct link to the AP.

[0496] Next, STA7 sends a P2P TWT establishment request frame to the AP, requesting to establish a P2P TWT. In the P2P TWT establishment request frame

[0497] 1. The value of Broadcast TWT Recommendation is 5, indicating that this is a P2P TWT;

[0498] 2. The value of P2P Peer is: <MAC address of STA8, AID of STA8>;

[0499] The AP receives this frame and needs to determine a P2P TWT SP, so it performs a link measurement. The specific process of the AP performing a link measurement is as follows:

[0500] The channel model within the BSS is obtained through CSI reporting. The CSI report field is included in the CSI frame. The AP can use the NDPA&NDP mechanism to request the Non-AP STA to perform relevant channel measurements, and store the measurement results in the CSI frame and send them to the AP as a response to the NDPA&NDP. You can also use a normal sounding PPDU to request the non-AP STA to send a CSI report. You only need to set the CSI / Steering subfield in the HT Control field of the sounding PPDU or NDP to 1, indicating that the non-AP STA is requested to send a CSI report. The function of the CSI / Steering subfield is to specify the feedback type of the non-AP STA.

[0501] It is important to note that the AP does not necessarily request CSI reports from non-AP STAs until it receives a P2P TWT setup request frame. The AP can also request CSI reports from non-AP STAs at other times through probing PPDUs or NDPs. By collecting CSI reports from multiple STAs, the AP can obtain a comprehensive view of multipath propagation and channel characteristics on the same channel. The AP can analyze and process these CSI reports to infer channel models and characteristics such as path loss, multipath delay, phase variation, and channel fading. Based on the inferred channel model, the AP can perform operations such as beamforming, wireless resource allocation, and interference management.

[0502] Non-AP STAs only generate corresponding CSI reports after performing measurements. Non-AP STAs can use sounding PPDUs for measurement. Specifically, the AP uses NDPA&NDP frames to request STA7, STA8 to perform sounding with STA1, STA2, and sends the results to the AP via a CSI report. After receiving the AP's request, STA7, STA8 request STA1, STA2 to send a sounding PPDU. After receiving the sounding PPDU, STA7, STA8 calculates the corresponding channel information and sends this information to the AP via a CSI report.

[0503] The location information of non-AP STAs within the BSS is obtained through Location Civic reports. Location Civic reports are a type of radio measurement reports. STAs can request the location information of other STAs by sending radio measurement request frames to them. The value of Measurement type in the measurement request element in the radio measurement request frame needs to be set to 11, indicating the requested location civic information. When the receiver receives the location civic request, it needs to include its own coordinate information and the reference point in the location civic report and send it to the initiator through the radio measurement report frame. Similarly, the AP does not necessarily request a Location Civic report after receiving the P2P TWT request frame.

[0504] Therefore, the AP can also obtain the relative location information of non-AP STAs and itself through location civic (which can be coordinates or other geographical information). Therefore, the AP can also know the location information of non-AP STAs within the BSS and can calculate the distance between two non-AP STAs.

[0505] Specifically, the AP uses CSI reports to determine the channel model within the BSS, Location Civic reports to calculate the distances between STA1, STA2, STA7, and STA8, and Peer-to-peer Link Event Reports to determine the transmission power of STA1 and STA2's TDLS direct links, as well as the transmission power of STA7 and STA8's TDLS direct links, and the available P2P resources for each of these two TDLS direct links. The AP now needs to use an algorithm to determine whether the transmissions of STA1 and STA2's TDLS direct links affect those of STA7 and STA8, and allocate SPs to the P2P TWTs of STA7 and STA8 based on the calculation results. The simplest algorithm calculates received power, which is dependent on the channel model and the distance between STAs. For example, the AP calculates the received power of STA1's data signal when it reaches STA7 or STA8 based on STA1's transmit power, the distance between STA1 and STA7 and STA8, and the channel model. If the received power is below a threshold, STA1's data transmission will not affect STA7 or STA8. Similarly, the AP can calculate the impact of STA2 on STA7 and STA8, the impact of STA7 on STA1 and STA2, and the impact of STA8 on STA1 and STA2.

[0506] Assuming that it is calculated that the TDLS direct link transmission of STA1 and STA2 does not affect the TDLS direct link transmission of STA7 and STA8, the AP can align these two pairs of P2P TWT SPs to reduce resource usage. The final allocation result is shown in Figure 34.

[0507] Similarly, the AP will carry the TWT element in the beacon frame and broadcast the P2P TWT within the BSS. STA8 needs to receive the beacon frame to obtain the P2P TWT information and request to join the P2P TWT by sending a TWT establishment request frame to the AP.

[0508] After receiving the TDLS setup request frame, the AP sends a TDLS setup response frame to STA8. The TWT setup command in the frame is set to accept TWT, and STA8 successfully joins the P2P TWT.

[0509] After a P2P TWT is established, a specific transmission plan must be executed. There are two types of transmission plans: trigger-enabled and non-trigger-enabled. Devices can choose the one based on their service needs. After a P2P TWT is established, the beacon frame sent by the AP also carries the P2P TWT EDCA Parameter Set element. Within the P2P TWT SP, STAs that compete for TXOPs must use the EDCA parameters for the corresponding role assigned in the beacon frame.

[0510] Example 2

[0511] In the multi-link scenario shown in Figure 28, STA1 and STA3 are associated with AP1, and STA2 and STA4 are associated with AP2. Assume that AP1 operates at 2.4 GHz and AP2 operates at 5 GHz. MLD_S is the TDLS Initiator STA MLD, and MLD_R is the TDLS Response STA MLD.

[0512] First, MLD_S sends a TDLS setup request frame to AP MLD. This frame is a data frame and carries two Per-STA Profile elements.

[0513] 1. The first Per-STA Profile element contains basic information about STA1, where the P2P Available Window List Present and P2P Available Window List are set appropriately based on STA1's own resource information.

[0514] 2. The second Per-STA Profile element contains STA2's basic information, where the P2P Available Window List Present and P2P Available Window List are set appropriately based on STA2's own resource information.

[0515] AP MLD forwards the request to MLD_R's attached STA3. MLD_R agrees to the TDLS direct link establishment request and responds with a TDLS Setup Response frame to AP MLD. This frame is also a data frame. The TDLS Setup Response frame carries two Per-STA Profile elements, in which the P2P Available Window List Present and P2P Available Window List are set appropriately based on its own resource information.

[0516] The AP MLD forwards the response frame to MLD_S. STA1 then sends a TDLS setup confirmation frame to STA3 through the AP. The P2P Available Window List in the frame contains the intersection of the resource information specified by both TDLS parties in the TDLS setup request and response frames. The two TDLS direct links between MLD_S and MLD_R are now established.

[0517] Next, MLD_S-affiliated STA1 sends a P2P TWT establishment request frame to the AP, requesting to establish a P2P TWT. In the P2P TWT establishment request frame:

[0518] Contains two TWT elements, each TWT element represents a link, and each TWT element contains the Broadcast TWT Parameters Set field;

[0519] The Broadcast TWT Parameters Set field contained in each TWT element also contains the P2P Peer field;

[0520] The value of Broadcast TWT Recommendation in each TWT element is 5;

[0521] The Broadcast TWT Parameters Set field contained in each TWT element may optionally also contain a restricted TWT Traffic Info subfield. Assuming that the values ​​of DL TID Bitmap Valid and UL TID Bitmap Valid are 1, the Restricted TWT DL / UL TID Bitmap will represent the TID on the corresponding TDLS direct link.

[0522] When the AP MLD receives the P2P TWT request frame, it needs to determine the P2P TWT SP. Like a single-link device, it can use the CSI report, Location Civic report, Peer-to-Peer link report, and the information given by MLD_S to determine the optimal P2P TWT SP allocation according to a specific algorithm, and carry the final P2P TWT SP through the TWT Parameter Information field in the TWT element of the TWT response.

[0523] The P2P TWT response frame sent by the AP MLD carries the restricted TWT Traffic Info subfield, which indicates the TID allocation status. The AP is associated with the MLD_S and MLD_R and therefore knows the TID allocation status of MLD_S and MLD_R in the WLAN. Based on this information, the AP writes the uplink TID information of MLD_S into the Restricted TWT UL TID Bitmap and the uplink TID information of MLD_R into the Restricted TWT DL TID Bitmap.

[0524] 1. From the MLD_S perspective: The Restricted TWT UL TID Bitmap indicates the traffic with the corresponding TID that the MLD_S can send on the corresponding TDLS direct link. The Restricted TWT DL TID Bitmap indicates the traffic with the corresponding TID that the MLD_S can receive on the corresponding TDLS direct link.

[0525] 2. From the MLD_R's perspective: The Restricted TWT UL TID Bitmap indicates the traffic of the corresponding TID that the MLD_R can receive on the corresponding TDLS direct link. The Restricted TWT DL TID Bitmap indicates the traffic of the corresponding TID that the MLD_R can send on the corresponding TDLS direct link.

[0526] P2P TWT has been established.

[0527] Finally, the AP will carry the TWT element in the beacon and broadcast the P2P TWT within the BSS. The MLD_R receives the beacon frame and sends a TWT establishment request frame to the AP MLD to request to join the P2P TWT. The AP MLD receives the TDLS establishment request frame and replies to the MLD_R with a TDLS establishment response frame. The TWT setup command in the frame is set to accept TWT, and the P2P TWT is established.

[0528] After the P2P TWT is established, a specific transmission plan needs to be executed. The transmission plan is implemented by the device. Within the P2P TWT SP, if the STA wants to compete for TXOP, it needs to use the EDCA parameters of the corresponding role allocated in the beacon frame.

[0529] The transmission control method provided in the embodiments of the present application proposes a new mode of TWT for coordinating P2P transmission, referred to as P2P TWT. In the presence of one or more P2P links, the AP reasonably allocates P2P TWT SPs based on resource information within the current BSS and resource information used by the P2P links. Within the P2P TWT SP, multiple pairs of P2P links can be scheduled by the AP to transmit P2P traffic within the P2P TWT SP, or a non-triggered method can be used to enable P2P STAs to preferentially transmit P2P traffic within the P2P TWT.

[0530] In this way, we achieve:

[0531] AP scheduling of P2P traffic transmission, both trigger-enabled and non-trigger-enabled, enables simultaneous transmission of multiple P2P links, making efficient use of WLAN media resources and freeing up more media resources for BSS transmission.

[0532] The transmission of P2P traffic is restricted to the P2P TWT SP, so that the transmission of BSS traffic outside the P2P TWT SP will not be interfered with by P2P traffic;

[0533] When there are enough P2P direct connections, a "P2P network" objectively exists. Through the P2P TWT mode, the AP can coordinate the resources of the "P2P network" and WLAN, allowing the two networks to coexist in a coordinated manner and utilize resources efficiently.

[0534] In addition, the embodiment of the present application also provides a feasible method for establishing multiple TDLS direct links at the same time.

[0535] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0536] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0537] FIG35 is a schematic diagram of the structure of a first non-access point device provided in an embodiment of the present application. As shown in FIG35 , the first non-access point device 3500 includes:

[0538] The first communication unit 3501 is configured to receive first information sent by an access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

[0539] In some embodiments, the first TWT SP is included in a first frame sent by the access point device to the first non-access point device, and the first frame includes at least one of the following:

[0540] TWT establishes a response frame;

[0541] Beacon frame;

[0542] Associate frames or reassociate frames;

[0543] Probe response frame.

[0544] In some embodiments, the first TWT SP is included in a first TWT element of the first frame.

[0545] In some embodiments, the first TWT element further includes at least one of the following:

[0546] First indication information, where the first indication information is used to indicate that the first TWT SP is used for a P2P link;

[0547] Parameters of the peer device of the first P2P link;

[0548] Channel information of the first P2P link.

[0549] In some embodiments, the first indication information is included in a request type subfield of a TWT parameter information field of the first TWT element.

[0550] In some embodiments, the first indication information is broadcast TWT recommendation information whose value in the request field is the first value.

[0551] In some embodiments, the condition that the first TWT element includes parameters of the peer device of the first P2P link and / or channel information of the first P2P link includes: the first TWT element includes the first indication information.

[0552] In some embodiments, the parameters of the second non-access point device are included in a peer subfield of a TWT parameter information field of the first TWT element.

[0553] In some embodiments, the channel information of the first P2P link is contained in a channel subfield of a TWT parameter information field of the TWT element.

[0554] In some embodiments, if at least two P2P links are established between the first non-access point device and the second non-access point device, and the first frame is a TWT establishment response frame, then the first frame includes at least two TWT elements, one TWT element of the at least two TWT elements is used for a P2P link, and the first TWT element is used for the first P2P link of the at least two P2P links.

[0555] In some embodiments, the first TWT element further includes a first traffic identifier TID of the first P2P link.

[0556] In some embodiments, the first TID is contained in a restricted TWT downlink or uplink TID bitmap subfield of a TWT parameter information field of the first TWT element.

[0557] In some embodiments, the first TWT SP is determined based on a first communication requirement, where the first communication requirement includes a communication requirement of a first P2P link, where the first P2P link is a P2P link between the first non-access point device and the second non-access point device.

[0558] In some embodiments, the communication requirement of the first P2P link is a resource of the first P2P link.

[0559] In some embodiments, the first communication requirement further includes a communication requirement of a first BSS, and the first basic service set BSS is the BSS to which the first non-access point device belongs.

[0560] In some embodiments, the communication demand of the first BSS is resources used by the first BSS.

[0561] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP and the second TWT SP corresponding to the second P2P link overlap in the time domain and / or frequency domain, and the second P2P link is a P2P link between a third non-access point device and a fourth non-access point device.

[0562] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP is the TWT SP corresponding to the second P2P link, and the second P2P link is the P2P link between the third non-access point device and the fourth non-access point device.

[0563] In some embodiments, whether transmissions of the first P2P link and the second P2P link interfere with each other is determined based on the first communication requirement and a second communication requirement, where the second communication requirement is a communication requirement of the second P2P link.

[0564] In some embodiments, the communication requirement of the second P2P link is a resource of the second P2P link.

[0565] In some embodiments, the first communication unit 3501 is further configured to:

[0566] A link report frame is sent to the access point device, where the link report frame includes first indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

[0567] In some embodiments, the second indication information is included in an event report field in an event report element of the link report frame.

[0568] In some embodiments, the first P2P link is a first tunnel direct link setting a TDLS direct link.

[0569] In some embodiments, the first communication unit 3501 is further configured to:

[0570] A TDLS establishment confirmation frame is received or sent, where the TDLS establishment confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

[0571] In some embodiments, the third indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup confirmation frame.

[0572] In some embodiments, the first communication unit 3501 is further configured to:

[0573] A TDLS establishment request frame is received or sent, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information indicates a communication requirement of an initiator of the first P2P link for the first P2P link.

[0574] In some embodiments, the third fourth indication information is carried in the first individual station description (Per-STA Profile) element of the TDLS establishment request frame.

[0575] In some embodiments, the first communication unit 3501 is further configured to:

[0576] Send or receive a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information is used to indicate a communication requirement of a responding end of the first P2P link for the first P2P link.

[0577] In some embodiments, the fifth indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup response frame.

[0578] In some embodiments, the site information field of the first individual site description element includes an available window subfield, and the available window subfield includes indication information indicating corresponding resources.

[0579] In some embodiments, if the second frame including the first individual site description element is used to establish at least two P2P links, the second frame includes at least two individual site description elements, one individual site description element is used for one P2P link, and the at least two individual site description elements include the first individual site description element corresponding to the first P2P link.

[0580] In some embodiments, the site control field of the first individual site description element includes an available window existence subfield, and the available window existence subfield is used to indicate whether the available window subfield includes the indication information.

[0581] In some embodiments, the first non-access device and / or the second non-access device is a member site of the first TWTSP.

[0582] In some embodiments, if the at least one P2P link includes at least two second P2P links, transmissions between the at least two P2P links do not interfere.

[0583] In some embodiments, transmissions on different P2P links among the at least two P2P links overlap in the time domain and / or frequency domain.

[0584] In some embodiments, the transmission opportunity used by the first P2P link for P2P transmission includes one of the following:

[0585] The access point device is shared with the first non-access point device;

[0586] The first non-access point device competes.

[0587] In some embodiments, the first communication unit 3501 is further configured to: if the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, the first non-access point device is a member site of the first TWT SP, and receives the first trigger frame sent by the access point device during the first TWT SP period, and the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

[0588] In some embodiments, the first trigger frame is used to trigger at least one member site of the first TWT SP to use the transmission opportunity shared by the access point device to perform P2P transmission.

[0589] In some embodiments, the first trigger frame includes a multi-user request to send transmission state trigger (MU-RTS TXS Trigger) frame.

[0590] In some embodiments, the first trigger frame includes at least one user information field, the user information field includes sixth indication information, and the sixth indication information is used to indicate a member site of the first TWT SP.

[0591] In some embodiments, the first trigger frame includes a general information field, the general information field includes seventh indication information, and the seventh indication information is used to indicate that the transmission opportunity competed for by the access point device is shared with P2P transmission.

[0592] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, during the first TWT SP, at least one of the following conditions is satisfied:

[0593] The member stations of the first TWT SP do not compete for transmission opportunities;

[0594] The non-member stations of the first TWT SP freely compete for transmission opportunities or use first channel access parameters to compete for transmission opportunities or are in a silent state in a first interval published by the access point device, and the first interval partially or completely overlaps with the first TWT SP in the time domain;

[0595] The access point device uses a second channel access parameter to compete for a transmission opportunity, and the priority of the second channel access parameter is higher than the priority of the first channel access parameter.

[0596] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, during the first TWT SP, at least one of the following is satisfied:

[0597] The member stations of the first TWT SP compete for transmission opportunities using third channel access parameters;

[0598] The non-member sites of the first TWT SP freely compete for transmission opportunities or use the first channel access parameter to compete for transmission opportunities or are in a silent state during the first interval published by the access point device, the first interval partially or completely overlaps with the first TWT SP in the time domain, and the priority of the third channel access parameter is higher than the priority of the first channel access parameter.

[0599] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, then:

[0600] A channel used by the first P2P link between the first non-access point device and the second non-access point device is a secondary channel of a first BSS, traffic of the first BSS is transmitted on a primary channel of the first BSS, and the first BSS is the BSS to which the first non-access point device belongs.

[0601] FIG36 is a schematic diagram of the structure of a non-access point device provided in an embodiment of the present application. As shown in FIG36 , the non-access point device 3600 includes:

[0602] The second communication unit 3601 is configured to send first information to the first non-access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

[0603] In some embodiments, the first TWT SP is included in a first frame sent by the access point device to the first non-access point device, and the first frame includes at least one of the following:

[0604] TWT establishes a response frame;

[0605] Beacon frame;

[0606] Associate frames or reassociate frames;

[0607] Probe response frame.

[0608] In some embodiments, the first TWT SP is included in a first TWT element of the first frame.

[0609] In some embodiments, the first TWT element further includes at least one of the following:

[0610] First indication information, where the first indication information is used to indicate that the first TWT SP is used for a P2P link;

[0611] Parameters of the peer device of the first P2P link;

[0612] Channel information of the first P2P link.

[0613] In some embodiments, the first indication information is included in a request type subfield of a TWT parameter information field of the first TWT element.

[0614] In some embodiments, the first indication information is broadcast TWT recommendation information whose value in the request field is the first value.

[0615] In some embodiments, the condition that the first TWT element includes parameters of the peer device of the first P2P link and / or channel information of the first P2P link includes: the first TWT element includes the first indication information.

[0616] In some embodiments, the parameters of the second non-access point device are included in a peer subfield of a TWT parameter information field of the first TWT element.

[0617] In some embodiments, the channel information of the first P2P link is contained in a channel subfield of a TWT parameter information field of the TWT element.

[0618] In some embodiments, if at least two P2P links are established between the first non-access point device and the second non-access point device, and the first frame is a TWT establishment response frame, then the first frame includes at least two TWT elements, one TWT element of the at least two TWT elements is used for a P2P link, and the first TWT element is used for the first P2P link of the at least two P2P links.

[0619] In some embodiments, the first TWT element further includes a first traffic identifier TID of the first P2P link.

[0620] In some embodiments, the first TID is contained in a restricted TWT downlink or uplink TID bitmap subfield of a TWT parameter information field of the first TWT element.

[0621] In some embodiments, the first TWT SP is determined based on a first communication requirement, where the first communication requirement includes a communication requirement of a first P2P link, where the first P2P link is a P2P link between the first non-access point device and the second non-access point device.

[0622] In some embodiments, the communication requirement of the first P2P link is a resource of the first P2P link.

[0623] In some embodiments, the first communication requirement further includes a communication requirement of a first BSS, and the first basic service set BSS is the BSS to which the first non-access point device belongs.

[0624] In some embodiments, the communication demand of the first BSS is resources used by the first BSS.

[0625] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP and the second TWT SP corresponding to the second P2P link overlap in the time domain and / or frequency domain, and the second P2P link is a P2P link between a third non-access point device and a fourth non-access point device.

[0626] In some embodiments, if the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP is the TWT SP corresponding to the second P2P link, and the second P2P link is the P2P link between the third non-access point device and the fourth non-access point device.

[0627] In some embodiments, whether transmissions of the first P2P link and the second P2P link interfere with each other is determined based on the first communication requirement and a second communication requirement, where the second communication requirement is a communication requirement of the second P2P link.

[0628] In some embodiments, the communication requirement of the second P2P link is a resource of the second P2P link.

[0629] In some embodiments, the second communication unit 3601 is further configured to:

[0630] A link report frame is sent to the access point device, where the link report frame includes first indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

[0631] In some embodiments, the second indication information is included in an event report field in an event report element of the link report frame.

[0632] In some embodiments, the first P2P link is a first tunnel direct link setting a TDLS direct link.

[0633] In some embodiments, the second communication unit 3601 is further configured to:

[0634] A TDLS establishment confirmation frame is received or sent, where the TDLS establishment confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

[0635] In some embodiments, the third indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup confirmation frame.

[0636] In some embodiments, the second communication unit 3601 is further configured to:

[0637] A TDLS establishment request frame is received or sent, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information indicates a communication requirement of an initiator of the first P2P link for the first P2P link.

[0638] In some embodiments, the third fourth indication information is carried in the first individual station description (Per-STA Profile) element of the TDLS establishment request frame.

[0639] In some embodiments, the second communication unit 3601 is further configured to:

[0640] Send or receive a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information is used to indicate a communication requirement of a responding end of the first P2P link for the first P2P link.

[0641] In some embodiments, the fifth indication information is carried in a first individual station description (Per-STA Profile) element of the TDLS setup response frame.

[0642] In some embodiments, the site information field of the first individual site description element includes an available window subfield, and the available window subfield includes indication information indicating corresponding resources.

[0643] In some embodiments, if the second frame including the first individual site description element is used to establish at least two P2P links, the second frame includes at least two individual site description elements, one individual site description element is used for one P2P link, and the at least two individual site description elements include the first individual site description element corresponding to the first P2P link.

[0644] In some embodiments, the site control field of the first individual site description element includes an available window existence subfield, and the available window existence subfield is used to indicate whether the available window subfield includes the indication information.

[0645] In some embodiments, the first non-access device and / or the second non-access device is a member site of the first TWTSP.

[0646] In some embodiments, if the at least one P2P link includes at least two second P2P links, transmissions between the at least two P2P links do not interfere.

[0647] In some embodiments, transmissions on different P2P links among the at least two P2P links overlap in the time domain and / or frequency domain.

[0648] In some embodiments, the transmission opportunity used by the first P2P link for P2P transmission includes one of the following:

[0649] The access point device is shared with the first non-access point device;

[0650] The first non-access point device competes.

[0651] In some embodiments, the second communication unit 3601 is further configured to: if the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, the first non-access point device is a member site of the first TWT SP, and a first trigger frame is sent to the first non-access point device during the first TWT SP period, and the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

[0652] In some embodiments, the first trigger frame is used to trigger at least one member site of the first TWT SP to use the transmission opportunity shared by the access point device to perform P2P transmission.

[0653] In some embodiments, the first trigger frame includes a multi-user request to send transmission state trigger (MU-RTS TXS Trigger) frame.

[0654] In some embodiments, the first trigger frame includes at least one user information field, the user information field includes sixth indication information, and the sixth indication information is used to indicate a member site of the first TWT SP.

[0655] In some embodiments, the first trigger frame includes a general information field, the general information field includes seventh indication information, and the seventh indication information is used to indicate that the transmission opportunity competed for by the access point device is shared with P2P transmission.

[0656] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, during the first TWT SP, at least one of the following conditions is satisfied:

[0657] The member stations of the first TWT SP do not compete for transmission opportunities;

[0658] The non-member stations of the first TWT SP freely compete for transmission opportunities or use first channel access parameters to compete for transmission opportunities or are in a silent state in a first interval published by the access point device, and the first interval partially or completely overlaps with the first TWT SP in the time domain;

[0659] The access point device uses a second channel access parameter to compete for a transmission opportunity, and the priority of the second channel access parameter is higher than the priority of the first channel access parameter.

[0660] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, during the first TWT SP, at least one of the following is satisfied:

[0661] The member stations of the first TWT SP compete for transmission opportunities using third channel access parameters;

[0662] The non-member sites of the first TWT SP freely compete for transmission opportunities or use the first channel access parameter to compete for transmission opportunities or are in a silent state during the first interval published by the access point device, the first interval partially or completely overlaps with the first TWT SP in the time domain, and the priority of the third channel access parameter is higher than the priority of the first channel access parameter.

[0663] In some embodiments, if the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, then:

[0664] A channel used by the first P2P link between the first non-access point device and the second non-access point device is a secondary channel of a first BSS, traffic of the first BSS is transmitted on a primary channel of the first BSS, and the first BSS is the BSS to which the first non-access point device belongs.

[0665] Those skilled in the art should understand that the relevant description of the above-mentioned wireless communication device in the embodiment of the present application can be understood with reference to the relevant description of the transmission control method in the embodiment of the present application.

[0666] Figure 37 is a schematic diagram of a communication device 3700 provided in an embodiment of the present application. The communication device can be a non-access point device or an access point device. The communication device 3700 shown in Figure 37 includes a processor 3710, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0667] Optionally, as shown in FIG37 , the communication device 3700 may further include a memory 3720. The processor 3710 may call and execute a computer program from the memory 3720 to implement the method in the embodiment of the present application.

[0668] The memory 3720 may be a separate device independent of the processor 3710 or may be integrated into the processor 3710 .

[0669] Optionally, as shown in FIG37 , the communication device 3700 may further include a transceiver 3730 , and the processor 3710 may control the transceiver 3730 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0670] The transceiver 3730 may include a transmitter and a receiver. The transceiver 3730 may further include an antenna, and the number of antennas may be one or more.

[0671] Optionally, the communication device 3700 may be specifically the first non-access point device in the embodiment of the present application, and the communication device 3700 may implement the corresponding processes implemented by the first non-access point device in each method of the embodiment of the present application, which will not be described in detail for the sake of brevity.

[0672] Optionally, the communication device 3700 may specifically be an access point device in an embodiment of the present application, and the communication device 3700 may implement corresponding processes implemented by the access point device in various methods in the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0673] Figure 38 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 3800 shown in Figure 38 includes a processor 3810, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0674] Optionally, as shown in FIG38 , the chip 3800 may further include a memory 3820 , wherein the processor 3810 may call and execute a computer program from the memory 3820 to implement the method in the embodiment of the present application.

[0675] The memory 3820 may be a separate device independent of the processor 3810 or may be integrated into the processor 3810 .

[0676] Optionally, the chip 3800 may further include an input interface 3830. The processor 3810 may control the input interface 3830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0677] Optionally, the chip 3800 may further include an output interface 3840. The processor 3810 may control the output interface 3840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0678] Optionally, the chip may be applied to the first non-access point device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the first non-access point device in the various methods of the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0679] Optionally, the chip may be applied to the access point device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the access point device in the various methods in the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0680] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0681] FIG39 is a schematic block diagram of a communication system 3900 provided in an embodiment of the present application. As shown in FIG39 , the communication system 3900 includes a non-access point device 3910 and an access point device 3920.

[0682] The non-access point device 3910 can be used to implement the corresponding functions implemented by the first non-access point device in the above method, and the access point device 3920 can be used to implement the corresponding functions implemented by the access point device in the above method. For the sake of brevity, they are not described here in detail. The communication system 3900 may include one or more access point devices 3920, and one access point device 3920 may be associated with multiple non-access point devices, and a P2P link may be established between two non-access point devices.

[0683] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0684] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0685] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0686] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0687] Optionally, the computer-readable storage medium may be applied to the first non-access point device in the embodiments of the present application, and the execution of the computer program enables the computer to execute the corresponding processes implemented by the first non-access point device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0688] Optionally, the computer-readable storage medium may be applied to a non-access point device in an embodiment of the present application, and the execution of the computer program enables the computer to execute the corresponding processes implemented by the non-access point device in each method of the embodiment of the present application. For the sake of brevity, they are not described here.

[0689] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0690] Optionally, the computer program product can be applied to the first non-access point device in the embodiments of the present application, and the execution of the computer program instructions enables the computer to execute the corresponding processes implemented by the first non-access point device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0691] Optionally, the computer program product may be applied to the access point device in the embodiments of the present application, and the execution of the computer program instructions enables the computer to execute the corresponding processes implemented by the access point device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

[0692] The embodiment of the present application also provides a computer program.

[0693] Optionally, the computer program may be applied to the first non-access point device in the embodiments of the present application. When the computer program is executed on a computer, the computer executes the corresponding processes implemented by the first non-access point device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0694] Optionally, the computer program may be applied to the access point device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the access point device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

[0695] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0696] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0697] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0698] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0699] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0700] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0701] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A transmission control method, the method comprising: A first non-access point device receives first information sent by an access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and a second non-access point device.

2. The method according to claim 1, wherein: The first TWT SP is included in a first frame sent by the access point device to the first non-access point device, and the first frame includes at least one of the following: TWT establishes a response frame; Beacon frame; association frame or reassociation frame; Probe response frame.

3. The method according to claim 2, wherein: The first TWT SP is included in a first TWT element of the first frame.

4. The method according to claim 3, wherein: The first TWT element further includes at least one of the following: first indication information, where the first indication information is used to indicate that the first TWT SP is used for a P2P link; Parameters of the peer device of the first P2P link; Channel information of the first P2P link.

5. The method according to claim 4, wherein: The first indication information is contained in the request type subfield of the TWT parameter information field of the first TWT element.

6. The method according to claim 5, wherein: The first indication information is broadcast TWT recommendation information whose value in the request field is the first value.

7. The method according to any one of claims 4 to 6, wherein: The condition that the first TWT element includes parameters of the counterpart device of the first P2P link and / or channel information of the first P2P link includes: the first TWT element includes the first indication information.

8. The method according to claim 4 or 7, wherein: The parameters of the second non-access point device are included in the counterpart subfield of the TWT parameter information field of the first TWT element.

9. The method according to claim 4 or 7, wherein: The channel information of the first P2P link is contained in the channel subfield of the TWT parameter information field of the TWT element.

10. The method according to any one of claims 3 to 9, wherein: If at least two P2P links are established between the first non-access point device and the second non-access point device, and the first frame is a TWT establishment response frame, then the first frame includes at least two TWT elements, one TWT element of the at least two TWT elements is used for a P2P link, and the first TWT element is used for the first P2P link of the at least two P2P links.

11. The method according to claim 10, wherein: The first TWT element also includes a first traffic identifier TID of the first P2P link.

12. The method according to claim 11, wherein: The first TID is contained in the restricted TWT downlink or uplink TID bitmap subfield of the TWT parameter information field of the first TWT element.

13. The method according to any one of claims 1 to 12, wherein: The first TWT SP is determined based on a first communication requirement, where the first communication requirement includes a communication requirement of a first P2P link, and the first P2P link is a P2P link between the first non-access point device and the second non-access point device.

14. The method according to claim 13, wherein: The communication requirement of the first P2P link is the resources of the first P2P link.

15. The method according to claim 13 or 14, wherein: The first communication requirement also includes a communication requirement of a first BSS, and the first basic service set BSS is the BSS to which the first non-access point device belongs.

16. The method according to claim 15, wherein: The communication demand of the first BSS is the resources used by the first BSS.

17. The method according to any one of claims 13 to 16, wherein: If the transmission of the first P2P link and the transmission of the second P2P link do not interfere, the first TWT SP overlaps with the second TWT SP corresponding to the second P2P link in the time domain and / or frequency domain, and the second P2P link is a P2P link between a third non-access point device and a fourth non-access point device.

18. The method according to any one of claims 13 to 16, wherein: If the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP is the TWT SP corresponding to the second P2P link, and the second P2P link is a P2P link between a third non-access point device and a fourth non-access point device.

19. The method according to claim 17 or 18, wherein: Whether transmissions of the first P2P link and the second P2P link interfere with each other is determined based on the first communication requirement and the second communication requirement, where the second communication requirement is the communication requirement of the second P2P link.

20. The method according to claim 19, wherein: The communication requirement of the second P2P link is the resources of the second P2P link.

21. The method according to any one of claims 13 to 20, wherein: The method further comprises: The first non-access point device sends a link report frame to the access point device, where the link report frame includes first indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

22. The method according to claim 21, wherein: The second indication information is included in the event report field in the event report element of the link report frame.

23. The method according to any one of claims 13 to 22, wherein: The first P2P link is a first tunnel direct link setting a TDLS direct link.

24. The method according to claim 23, wherein: The method further comprises: The first non-access point device receives or sends a TDLS establishment confirmation frame, where the TDLS establishment confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

25. The method according to claim 24, wherein: The third indication information is carried in the first separate site description element of the TDLS establishment confirmation frame.

26. The method according to any one of claims 23 to 25, wherein: The method further comprises: The first non-access point device receives or sends a TDLS establishment request frame, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information indicates a communication requirement of an initiator of the first P2P link for the first P2P link.

27. The method according to claim 26, wherein: The third fourth indication information is carried in the first separate site description element of the TDLS establishment request frame.

28. The method according to any one of claims 23 to 27, wherein: The method further comprises: The first non-access point device sends or receives a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information is used to indicate a communication requirement of a responding end of the first P2P link for the first P2P link.

29. The method according to claim 28, wherein: The fifth indication information is carried in the first separate site description element of the TDLS setup response frame.

30. The method of claim 25, 27 or 29, wherein: The site information field of the first individual site description element includes an available window subfield, and the available window subfield includes indication information indicating corresponding resources.

31. The method according to claim 30, wherein: If the second frame including the first separate site description element is used to establish at least two P2P links, the second frame includes at least two separate site description elements, one separate site description element is used for one P2P link, and the at least two separate site description elements include the first separate site description element corresponding to the first P2P link.

32. The method according to claim 30 or 31, wherein: The site control field of the first individual site description element includes an available window existence subfield, and the available window existence subfield is used to indicate whether the available window subfield includes the indication information.

33. The method according to any one of claims 1 to 32, wherein: The first non-access device and / or the second non-access device is a member site of the first TWT SP.

34. The method according to any one of claims 1 to 33, wherein: If the at least one P2P link includes at least two second P2P links, transmissions between the at least two P2P links do not interfere.

35. The method of claim 34, wherein: Transmissions on different P2P links among the at least two P2P links overlap in the time domain and / or frequency domain.

36. The method according to any one of claims 1 to 35, wherein: The transmission opportunity used by the first P2P link for P2P transmission includes one of the following: The access point device is shared with the first non-access point device; The first non-access point device competes.

37. The method of claim 36, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, and the first non-access point device is a member site of the first TWT SP, the method further includes: The first non-access point device receives a first trigger frame sent by the access point device during the first TWT SP period, where the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

38. The method of claim 37, wherein: The first trigger frame is used to trigger at least one member station of the first TWT SP to use the transmission opportunity shared by the access point device to perform P2P transmission.

39. The method according to claim 37 or 38, wherein: The first trigger frame includes: a multi-user request to send a transmission status trigger frame.

40. The method according to any one of claims 37 to 39, wherein: The first trigger frame includes at least one user information field, the user information field includes sixth indication information, and the sixth indication information is used to indicate a member site of the first TWT SP.

41. The method according to any one of claims 37 to 40, wherein: The first trigger frame includes a general information field, the general information field includes seventh indication information, and the seventh indication information is used to indicate that the transmission opportunity contended by the access point device is shared with P2P transmission.

42. The method according to any one of claims 36 to 41, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, during the first TWT SP, at least one of the following conditions is satisfied: The member stations of the first TWT SP do not compete for transmission opportunities; The non-member stations of the first TWT SP freely compete for transmission opportunities or use first channel access parameters to compete for transmission opportunities or are in a silent state at a first interval published by the access point device, and the first interval partially or completely overlaps with the first TWT SP in the time domain; The access point device uses a second channel access parameter to compete for a transmission opportunity, and a priority of the second channel access parameter is higher than a priority of the first channel access parameter.

43. The method of claim 36, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, during the first TWT SP, at least one of the following is satisfied: The member stations of the first TWT SP compete for transmission opportunities using third channel access parameters; The non-member sites of the first TWT SP freely compete for transmission opportunities or adopt the first channel access parameters to compete for transmission opportunities or are in a silent state during the first interval published by the access point device, the first interval partially or completely overlaps with the first TWT SP in the time domain, and the priority of the third channel access parameter is higher than the priority of the first channel access parameter.

44. The method of claim 43, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, then: A channel used by the first P2P link between the first non-access point device and the second non-access point device is a secondary channel of a first BSS, traffic of the first BSS is transmitted on a primary channel of the first BSS, and the first BSS is the BSS to which the first non-access point device belongs.

45. A transmission control method, the method comprising: An access point device sends first information to a first non-access point device, where the first information is used to indicate a first target wake-up time TWT service period SP. During the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one P2P link includes a first P2P link between the first non-access point device and a second non-access point device.

46. ​​The method of claim 45, wherein: The first TWT SP is included in a first frame sent by the access point device to the first non-access point device, and the first frame includes at least one of the following: TWT establishes a response frame; Beacon frame; association frame or reassociation frame; Probe response frame.

47. The method of claim 46, wherein: The first TWT SP is included in a first TWT element of the first frame.

48. The method of claim 47, wherein: The first TWT element further includes at least one of the following: first indication information, where the first indication information is used to indicate that the first TWT SP is used for a P2P link; Parameters of the peer end of the first P2P link; Channel information of a first P2P link between the first non-access point device and the second non-access point device.

49. The method of claim 48, wherein: The first indication information is contained in the request type subfield of the TWT parameter information field of the first TWT element.

50. The method of claim 49, wherein: The first indication information is broadcast TWT recommendation information whose value in the request field is the first value.

51. A method according to any one of claims 48 to 50, wherein: The condition that the first TWT element includes the peer parameters of the first P2P link and / or the channel information of the first P2P link includes: the first TWT element includes the first indication information.

52. The method of claim 48 or 51, wherein: The parameters of the second non-access point device are included in the counterpart subfield of the TWT parameter information field of the first TWT element.

53. The method of claim 48 or 51, wherein: The channel information of the first P2P link is contained in the channel subfield of the TWT parameter information field of the TWT element.

54. A method according to any one of claims 47 to 53, wherein: If at least two P2P links are established between the first non-access point device and the second non-access point device, and the first frame is a TWT establishment response frame, then the first frame includes at least two TWT elements, one TWT element of the at least two TWT elements is used for a P2P link, and the first TWT element is used for the first P2P link of the at least two P2P links.

55. The method of claim 54, wherein: The first TWT element also includes a first traffic identifier TID of the first P2P link.

56. The method of claim 55, wherein: The first TID is contained in the restricted TWT downlink or uplink TID bitmap subfield of the TWT parameter information field of the first TWT element.

57. The method according to any one of claims 45 to 56, wherein: The first TWT SP is determined based on a first communication requirement, where the first communication requirement includes a communication requirement of a first P2P link, and the first P2P link is a P2P link between the first non-access point device and the second non-access point device.

58. The method of claim 57, wherein: The communication requirement of the first P2P link is the resources of the first P2P link.

59. The method according to claim 57 or 58, wherein: The first communication requirement also includes a communication requirement of a first BSS, and the first basic service set BSS is the BSS to which the first non-access point device belongs.

60. The method of claim 59, wherein: The communication demand of the first BSS is the resources used by the first BSS.

61. The method according to any one of claims 57 to 60, wherein: If the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP and the second TWT SP corresponding to the second P2P link overlap in the time domain and / or frequency domain.

62. The method according to any one of claims 57 to 60, wherein: If the transmission of the first P2P link does not interfere with the transmission of the second P2P link, the first TWT SP is the TWT SP corresponding to the second P2P link.

63. The method of claim 61 or 62, wherein: Whether transmissions of the first P2P link and the second P2P link interfere with each other is determined based on the first communication requirement and the second communication requirement, where the second communication requirement is the communication requirement of the second P2P link.

64. The method of claim 63, wherein: The communication requirement of the second P2P link is the resources of the second P2P link.

65. A method according to any one of claims 57 to 64, wherein: The method further comprises: The access point device receives a link report frame sent by the first non-access point device, where the link report frame includes second indication information, and the second indication information is used to indicate a communication requirement of the first P2P link.

66. The method of claim 65, wherein: The second indication information is included in the event report field of the event report element of the link report frame.

67. The method according to any one of claims 57 to 66, wherein: The first P2P link is a first tunnel direct link setting a TDLS direct link.

68. The method of claim 67, wherein: The method further comprises: The access point device receives or sends a TDLS establishment confirmation frame, where the TDLS establishment confirmation frame includes third indication information, where the third indication information is used to indicate a communication requirement of the first P2P link.

69. The method of claim 68, wherein: The third indication information is carried in the first separate site description element of the TDLS establishment confirmation frame.

70. The method according to any one of claims 67 to 69, wherein: The method further comprises: The access point device receives or sends a TDLS establishment request frame, where the TDLS establishment request frame includes fourth indication information, where the fourth indication information is used to indicate a communication requirement of an initiator of the first P2P link for the first P2P link.

71. The method of claim 70, wherein: The third indication information is carried in the first separate site description element of the TDLS establishment request frame.

72. The method according to any one of claims 67 to 71, wherein: The method further comprises: The access point device sends or receives a TDLS setup response frame, where the TDLS setup response frame includes fifth indication information, where the fifth indication information indicates a communication requirement of a responding end of the first P2P link for the first P2P link.

73. The method of claim 72, wherein: The fifth indication information is carried in the first separate site description element of the TDLS setup response frame.

74. The method according to claim 69, 71, 73, wherein: The site information field of the first individual site description element includes an available window subfield, and the available window subfield includes indication information indicating corresponding resources.

75. The method of claim 74, wherein: If the second frame including the first separate site description element is used to establish at least two P2P links, the second frame includes at least two separate site description elements, one separate site description element is used for one P2P link, and the at least two separate site description elements include the first separate site description element corresponding to the first P2P link.

76. The method of claim 74 or 75, wherein: The site control field of the first individual site description element includes an available window existence subfield, and the available window existence subfield is used to indicate whether the available window subfield includes the indication information.

77. The method according to any one of claims 45 to 76, wherein: The first non-access device and / or the second non-access device is a member site of the first TWT SP.

78. The method according to any one of claims 45 to 77, wherein: If the at least one P2P link includes at least two P2P links, transmissions between the at least two P2P links do not interfere.

79. The method of claim 78, wherein: Transmissions of different P2P links among the at least two P2P links overlap in the time domain and / or frequency domain.

80. The method according to any one of claims 45 to 79, wherein: The transmission opportunity used by the first P2P link for P2P transmission includes one of the following: The access point device is shared with the first non-access point device; The first non-access point device competes.

81. The method of claim 80, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, and the first non-access point device is a member site of the first TWT SP, the method further includes: The access point device sends a first trigger frame to the first non-access point device during the first TWT SP period, where the first trigger frame is used to instruct the first non-access point device to perform P2P transmission.

82. The method of claim 81, wherein: The first trigger frame is used to trigger at least one member station of the first TWT SP to use the transmission opportunity shared by the access point device to perform P2P transmission.

83. The method of claim 81 or 82, wherein: The first trigger frame includes: a multi-user request to send transmission state trigger (MU-RTS TXS Trigger) frame.

84. The method according to any one of claims 81 to 83, wherein: The first trigger frame includes at least one user information field, the user information field includes sixth indication information, and the sixth indication information is used to indicate a member site of the first TWT SP.

85. The method according to any one of claims 81 to 84, wherein: The first trigger frame includes a general information field, the general information field includes seventh indication information, and the seventh indication information is used to indicate that the transmission opportunity contended by the access point device is shared with P2P transmission.

86. The method according to any one of claims 80 to 85, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is shared by the access point device to the first non-access point device, during the first TWT SP, at least one of the following conditions is satisfied: The member stations of the first TWT SP do not compete for transmission opportunities; The non-member stations of the first TWT SP freely compete for transmission opportunities or use first channel access parameters to compete for transmission opportunities or are in a silent state at a first interval published by the access point device, and the first interval partially or completely overlaps with the first TWT SP in the time domain; The access point device uses a second channel access parameter to compete for a transmission opportunity, and a priority of the second channel access parameter is higher than a priority of the first channel access parameter.

87. The method of claim 80, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, during the first TWT SP, at least one of the following is satisfied: The member stations of the first TWT SP compete for transmission opportunities using third channel access parameters; The non-member sites of the first TWT SP freely compete for transmission opportunities or adopt the first channel access parameters to compete for transmission opportunities or are in a silent state during the first interval published by the access point device, the first interval partially or completely overlaps with the first TWT SP in the time domain, and the priority of the third channel access parameter is higher than the priority of the first channel access parameter.

88. The method of claim 87, wherein: If the transmission opportunity used by the first P2P link for P2P transmission is competed for by the first non-access point device, then: A channel used by the first P2P link between the first non-access point device and the second non-access point device is a secondary channel of a first BSS, traffic of the first BSS is transmitted on a primary channel of the first BSS, and the first BSS is the BSS to which the first non-access point device belongs.

89. A first non-access point device, comprising: A first communication unit is configured to receive first information sent by an access point device, wherein the first information is used to indicate a first target wake-up time TWT service period SP, and during the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

90. An access point device, comprising: A second communication unit is configured to send first information to a first non-access point device, wherein the first information is used to indicate a first target wake-up time TWT service period SP, and during the first TWT SP, P2P transmission is preferentially performed on at least one P2P link, and the at least one link includes a first P2P link between the first non-access point device and the second non-access point device.

91. A first non-access point device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the first non-access point device executes the method according to any one of claims 1 to 44.

92. An access point device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the access point device executes the method according to any one of claims 45 to 88.

93. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 44, or executes a method as claimed in any one of claims 45 to 88.

94. A computer-readable storage medium for storing a computer program, wherein the execution of the computer program enables a computer to execute the method according to any one of claims 1 to 44, or the method according to any one of claims 45 to 88.

95. A computer program product, comprising computer program instructions, the execution of which causes a computer to perform the method according to any one of claims 1 to 44, or the method according to any one of claims 45 to 88.

96. A computer program, wherein the execution of the computer program causes a computer to execute the method according to any one of claims 1 to 44, or the method according to any one of claims 45 to 88.

Images