Transmission control method, and device and storage medium

Abstract

Provided in the embodiments of the present application are a transmission control method, and a device and a storage medium. The method comprises: a first access point device receiving a first frame, which is sent by a second access point device, wherein the first frame is used for indicating a target transmission parameter, the target transmission parameter is used for each access point among at least one access point device that participates in cooperative transmission to schedule the transmission of at least one target frame, the at least one access point device comprises a first non-access point device, and the target frame is located behind a first frame that is transmitted between the first access point device and the first 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 access point (AP) candidate set is a collection of APs that can initiate or participate in multi-AP collaboration. An AP that obtains a transmission opportunity (TXOP) and initiates multi-AP collaboration is called a sharing AP. APs in the AP candidate set can act as shared APs to participate in multi-AP collaboration initiated by sharing APs in the same AP candidate set. At least one AP in an AP candidate set can become a sharing AP. How to control transmission between APs participating in multi-AP collaborative transmission and stations (STAs) is an urgent problem that needs to be solved.

[0004] Summary of the Invention

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

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

[0007] A first access point device receives a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

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

[0009] The second access point device sends a first frame to the first access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in the collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

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

[0011] A first communication unit is configured to receive a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in the collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0012] The second access point device provided in this embodiment of the present application includes:

[0013] A second communication unit is configured to send a first frame to a first access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in the collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0014] The communication device provided in an embodiment of the present application may be the first access point device or the second access point device in the above-described solution, and includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, so that the communication device performs the above-described transmission control method.

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

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

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

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

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

[0020] Through the above technical solution, the first access point device receives a first frame sent by the second access point device, where the first frame is used to indicate a target transmission parameter, and the target transmission parameter is used for each access point device in at least one access point device participating in the cooperative transmission to schedule the transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after the first frame transmitted between the first access point device and the first non-access point device, thereby configuring the transmission of the non-first frame transmitted between the first access point device and the first non-access point device through the first frame, thereby controlling the transmission between multiple APs and stations (STAs) participating in the multi-AP cooperative transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] 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:

[0022] FIG1 is an optional schematic diagram of an application scenario of an embodiment of the present application;

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

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

[0025] FIG3 is an optional schematic diagram of a multi-AP cooperative transmission scenario provided in an embodiment of the present application;

[0026] FIG4 is an optional schematic diagram of C-OFDMA provided in an embodiment of the present application;

[0027] FIG5 is an optional schematic diagram of collaborative UL MU-MIMO provided in an embodiment of the present application;

[0028] FIG6 is an optional schematic diagram of collaborative beamforming / nulling provided in an embodiment of the present application;

[0029] FIG7 is an optional schematic diagram of collaborative space reuse provided in an embodiment of the present application;

[0030] FIG8 is an optional schematic diagram of joint transmission provided in an embodiment of the present application;

[0031] FIG9 is an optional schematic diagram of a multi-AP cooperative transmission scenario provided in an embodiment of the present application;

[0032] FIG10 is a schematic diagram of an optional uplink confirmation method provided in an embodiment of the present application;

[0033] FIG11 is a schematic diagram of an optional uplink confirmation method provided in an embodiment of the present application;

[0034] FIG12 is a schematic diagram of an optional downlink confirmation method provided in an embodiment of the present application;

[0035] FIG13 is a schematic diagram of an optional downlink confirmation method provided in an embodiment of the present application;

[0036] FIG14 is a schematic diagram of an optional downlink confirmation method provided in an embodiment of the present application;

[0037] FIG15 is a schematic diagram of an optional frame format of a trigger frame provided in an embodiment of the present application;

[0038] FIG16 is a schematic diagram of an optional frame format of a common information field of a trigger frame provided in an embodiment of the present application;

[0039] 17 is a schematic diagram of an optional frame format of a special user information field of a trigger frame provided in an embodiment of the present application;

[0040] FIG18 is a schematic diagram of an optional frame format of an EHT variable user information field of a trigger frame provided in an embodiment of the present application;

[0041] FIG19 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0042] FIG20 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0043] FIG21 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0044] FIG22 is an optional flow chart of a transmission control method provided in an embodiment of the present application;

[0045] FIG23 is an optional flow chart of a transmission control method provided in an embodiment of the present application;

[0046] FIG24 is a schematic diagram of an optional format of a UHR MU PPDU provided in an embodiment of the present application;

[0047] FIG25 is a schematic diagram of an optional format of a UHR TB PPDU provided in an embodiment of the present application;

[0048] FIG26 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0049] FIG27 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0050] FIG28 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0051] FIG29 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0052] FIG30 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0053] FIG31 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0054] FIG32 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0055] FIG33 is a schematic diagram of an optional format of UL confirmation information provided in an embodiment of the present application;

[0056] FIG34 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0057] FIG35 is a schematic diagram of an optional format of UL confirmation RU allocation information provided in an embodiment of the present application;

[0058] FIG36 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0059] FIG37 is a schematic diagram of an optional format of UL confirmation RU allocation information provided in an embodiment of the present application;

[0060] FIG38 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0061] FIG39 is an optional schematic diagram of multi-cooperative transmission provided in an embodiment of the present application;

[0062] FIG40 is a schematic diagram of an optional format of UL confirmation RU allocation information provided in an embodiment of the present application;

[0063] FIG41A is a schematic diagram of an optional format of ULTB PPDU information provided in an embodiment of the present application;

[0064] FIG41B is a schematic diagram of an optional format for confirming RU allocation information provided in an embodiment of the present application;

[0065] FIG42 is a schematic diagram of an optional structure of a first access point device provided in an embodiment of the present application;

[0066] FIG43 is a schematic diagram of an optional structure of a second access point device provided in an embodiment of the present application;

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

[0068] FIG45 is a schematic structural diagram of a chip provided in an embodiment of the present application;

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

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

[0071] 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. WLANs may support frequency bands including, but not limited to, low frequency bands (2.4 GHz, 5 GHz, and 6 GHz) and high frequency bands (45 GHz and 60 GHz).

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

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

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

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

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

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

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

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

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

[0081] It should be understood that Figure 1 is merely an example of the present application and should not be construed as limiting the present application. For example, Figure 1 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 are not limited in this embodiment of the present application.

[0082] FIG2A is a schematic diagram of an application scenario of an embodiment of the present application.

[0083] As shown in Figure 2A, 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.

[0084] As shown in FIG2B , in the communication system described in FIG2A , AP MLD 210 is affiliated with at least two APs 2101, and non-AP MLD 220 is affiliated 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 affiliated with an AP MLD may also be referred to as an AP affiliated with an AP MLD, and a STA affiliated with a non-AP MLD may also be referred to as a non-AP STA affiliated with a non-AP MLD or a STA affiliated with a non-AP MLD.

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

[0086] The communication system 200 shown in Figure 2A 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.

[0087] FIG2A exemplarily shows an AP MLD and a non-AP MLD. Optionally, the 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.

[0088] It should be noted that Figures 1, 2A, and 2B 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 IEEE 802.11 protocol, LTE protocol, NR protocol and related protocols used in future communication systems, and the present application does not limit this.

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

[0090] Unless otherwise specified, a STA refers to a STA that has no associated MLD.

[0091] Multi-AP collaboration

[0092] Multi-AP collaboration includes multi-AP collaboration preparation phase and multi-AP collaboration transmission phase.

[0093] In the multi-AP collaboration preparation phase, the sharing AP obtains a TXOP and initiates multi-AP collaboration. It can send a frame to one or more APs in the same AP candidate set to inquire about their intention to participate in multi-AP collaboration. One or more APs will respond with a frame to inform the sharing AP whether it intends to participate in multi-AP collaboration. If an AP intends to participate in multi-AP collaboration, it becomes the shared AP in the multi-AP collaboration.

[0094] In the multi-AP cooperative transmission phase, the sharing AP and one or more shared APs can participate in the multi-AP cooperative transmission. Alternatively, the sharing AP may not participate in the multi-AP cooperative transmission; two or more shared APs can participate in the multi-AP cooperative transmission.

[0095] Figure 3 shows an example AP candidate set that includes three APs: AP1, AP2, and AP3. In one example, AP1 can obtain a TXOP as a sharing AP and initiate multi-AP collaboration; AP2 and AP3 can participate in multi-AP collaboration as shared APs. AP1, AP2, and AP3 can participate in multi-AP collaboration (such as coordinated orthogonal frequency division multiple access (OFDMA) or joint transmission) in a TXOP. In another example, AP2 can obtain a TXOP and initiate multi-AP collaboration as a sharing AP; AP1 and AP3 can participate in multi-AP collaboration as shared APs. In a TXOP, AP1 and AP3 may participate in multi-AP collaborative transmission, but AP2 does not.

[0096] When multi-AP coordinated transmission is performed, the sharing AP first sends a trigger frame (for example, a Multi-AP coordinated transmission Trigger frame (M-AP TF)) to each shared AP, allocates resources in the time domain, frequency domain, spatial domain, or power domain to each shared AP, and aligns the physical layer protocol data unit (PPDU) sent or requested by each shared AP at the OFDM symbol level or PPDU level to ensure orthogonality of frequency domain symbols and synchronization between APs.

[0097] In related technologies, multi-AP cooperative transmission includes the following modes: cooperative OFDMA, cooperative UL MU-MIMO, cooperative beamforming, cooperative spatial reuse, and joint transmission.

[0098] Coordinated OFDMA (coordinated OFDMA, C-OFDMA)

[0099] In multi-AP collaborative OFDMA transmission, two or more sharing APs and shared APs send their own downlink multi-user PPDUs (DL MU PPDUs) in different frequency parts of the collaborative transmission bandwidth or send trigger frames to their associated STAs. The trigger frames are used to request uplink trigger-based (TB) PPDUs (TB PPDUs).

[0100] As shown in Figure 4, the basic service set (BSS) 1 uses the first frequency part (the upper 20M of 40M in Figure 4) for transmission, and BSS2 uses the second frequency part (the lower 20M of 40M in Figure 4) for transmission. Among them, STA1, STA2 and STA3 belong to BSS1, and STA4 and STA5 belong to BSS2, thereby achieving orthogonality during synchronous transmission.

[0101] Cooperative UL Multi-User Multiple Input / Output (MU-MIMO)

[0102] In multi-AP collaborative UL MU-MIMO transmission, two or more sharing APs and shared APs request their own uplink TB PPDUs over the entire collaborative transmission bandwidth, and each non-AP STA is assigned a different spatial stream.

[0103] As shown in Figure 5, the sharing AP sends a multi-AP transmission trigger frame (M-AP TF) to shared AP1 and shared AP 2, requesting an uplink TB PPDU. After receiving the M-AP TF, shared AP1 and shared AP2 each send a coordinated uplink trigger frame (coordinated UL Trigger) to the associated STA to trigger the associated STA to send data frames to shared AP1. STA1 and STA2 use different spatial streams to transmit data frames. The PPDU carrying the data frame also carries a multi-user multiple input and output (MU-MIMO) high-efficiency long training field (HE-LTF), and the uplink data frames sent by STA and STA2 are fully aligned. After receiving the data frame, AP1 and AP2 use different spatial streams to send block acknowledgment (BlockAck, B-ACK or BA) frames to STA1 and STA2.

[0104] Coordinated beamforming (C-BF)

[0105] Collaborative beamforming / nulling (Null Steering) When transmitting / receiving data, the AP can enhance the beam toward the target STA and null the spatial radiation toward non-target STAs to achieve interference suppression.

[0106] As shown in FIG6 , AP1 in BSS1 enhances the beam toward the associated STA and adjusts the beam toward the STA in BSS2 to 0; AP2 in BSS2 enhances the beam toward the associated STA and adjusts the beam toward the STA in BSS1 to 0.

[0107] Coordinated spatial reuse (C-SR)

[0108] C-SR reduces interference between APs through joint power control, enabling multiple APs to transmit in parallel and maximizing aggregate throughput. Because it eliminates synchronization and CSI collection, requires no physical layer (PHY) changes, and requires no STA protocol updates, it can be implemented with relatively low complexity. Compared to other multi-AP solutions, C-SR achieves both low complexity and high performance (throughput and latency).

[0109] As shown in FIG7 , control information is exchanged between AP1 and AP2 to perform power control on transmissions from AP1 to STA1 and from AP2 to STA2, and to perform interference control on transmissions from AP1 to STA2 and from AP2 to STA1.

[0110] Joint transmission

[0111] Joint transmission means that at least two APs send shared data to the target STA at the same time, occupying exactly the same frequency domain resources (cooperative bandwidth). Data from different APs is distinguished by different spatial streams and is transparent to the receiving STA.

[0112] As shown in Figure 8, the backhaul link between AP1 and AP2 exchanges shared data. AP1 and AP2 simultaneously send shared data to STAs in BSS1 and BSS2 through exactly the same frequency domain resources. One STA can receive shared data from multiple APs.

[0113] Multi-AP coordinated transmission trigger frame design

[0114] In the related art, some fields in the Multi-AP coordinated transmission Trigger frame are used to indicate the parameters of the first DL MU PPDU sent by each shared AP participating in multi-AP collaborative transmission after the short interframe space (SIFS) of the frame. The indicated parameters include: PPDU length, multi-AP collaboration type, puncturing channel information, extremely high throughput signal (EHT-SIG) symbol number and modulation mode, and spatial stream allocation information.

[0115] Among them, common information is indicated in the Trigger Dependent Common Info subfield (Trigger Dependent Common Info subfield) or the Trigger Dependent User Info subfield (Trigger Dependent User Info subfield) in the Special User Info field (Special User Info field); user information is indicated in the Extremely high throughput (ETH) variant User Info subfield (EHT variant User Info subfield).

[0116] In one example, as shown in FIG9 , AP1 as a sharing AP sends a Multi-AP coordinated transmission Trigger frame to AP2 (shared AP) and AP3 (shared AP), and AP2 (shared AP) and AP3 (shared AP) send an EHT MU PPDU based on the information configured in the Multi-AP coordinated transmission Trigger frame.

[0117] Acknowledgment procedure in DL MU PPDU

[0118] For DL ​​MU PPDU transmission, two methods are defined for an AP to request a BlockAck from a non-AP STA.

[0119] Method 1: Data frame carries trigger frame

[0120] When a non-AP STA receives a DL MU PPDU containing a Quality of Service (QoS) data frame or a QoS Null frame with a High-efficiency Trigger PPDU Acknowledgement (HETP Ack) acknowledgment policy, a Multi-User Block Acknowledgment Request (MU-BAR) Trigger frame, a Groupcast with Retries (GCR) MU-BAR Trigger frame, or a management frame requesting acknowledgment, the non-AP STA should send an immediate acknowledgment frame based on the scheduling information in the trigger frame or Triggered Response Scheduling (TRS) control subfield carried in the MU PPDU. As shown in Figure 10, in the obtained transmission opportunity, the Aggregate Medium Access Control (MAC) Protocol Data Unit (A-MPDU) sent downlink carries a trigger frame, and the uplink responds with a BA frame. If a non-AP STA does not receive a trigger frame containing scheduling information or a frame carrying the TRS control subfield, it does not respond.

[0121] Method 2: The AP can use MU-BAR Trigger frames or GCR MU-BAR Trigger frames to request acknowledgment frames from multiple non-AP STAs. Prior to this, the AP sent QoS data frames with a Block Ack ack policy to these non-AP STAs, or the AP did not receive immediate acknowledgment frames from these non-AP STAs after sending QoS data frames with a HETP Ack ack policy in a MU PPDU. As shown in Figure 11, after a downlink MU PPDU is sent, if no BA frame is received within a SIFS, the downlink trigger frame is sent after the SIFS following the MU PPDU, and the uplink BA frame is sent after the SIFI of the trigger frame.

[0122] Here, MU-BAR Trigger frames or GCR MU-BAR Trigger frames, and management frames requesting acknowledgement can be understood as trigger frames. Frames with a Block Ack policy or HETP Ack policy can be understood as data frames. Acknowledgement frames can include BA frames.

[0123] ACKNOWLEDGEMENT PROCEDURE IN UL MU PPDU

[0124] In uplink multi-user (UL MU) transmission, if the AP receives frames from multiple STAs and requires an immediate acknowledgment frame (for example, a QoS data frame carrying a normal acknowledgment (Normal Ack) or an implicit BAR ack policy, or a management frame other than Action No Ack), the AP should send the immediate acknowledgment in the form of a single-user (SU) PPDU or MU PPDU. The immediate acknowledgment can be an Ack frame, a compressed BlockAck frame, or a Multi-STA BlockAck frame.

[0125] When the AP receives an UL frame requiring immediate acknowledgment, the AP should transmit a DL acknowledgment after a SIFS, regardless of whether the medium is busy or idle. When the AP transmits an immediate acknowledgment in an MU PPDU in response to an Aggregate Medium Access Control (MAC) Protocol Data Unit (A-MPDU) in a TB PPDU, the AP should send it in the same 20 MHz subchannel as the separate high efficiency / extremely high efficiency (pre-HE / EHT) modulation field of the TB PPDU sent by the STA.

[0126] The AP responds to DL BlockAck in the following three ways:

[0127] Case 1: Multiple BlockAck frames shown in Figure 12 are sent in DL MU mode;

[0128] Case 2: A multi-STA BlockAck frame shown in FIG13 is sent in a non-high-throughput (non-HT) PPDU, HT PPDU, VHT PPDU, HE SU PPDU, or HE ER SU PPDU.

[0129] Case 3: The multi-STA BlockAck frame shown in FIG14 is sent in a non-HT duplicated PPDU.

[0130] Trigger Frame

[0131] According to the standard, when transmitting an uplink TB PPDU, the AP first sends a trigger frame. Each non-AP STA then prepares and transmits the TB PPDU based on parameters indicated in the received trigger frame, including the uplink length (UL Length), uplink bandwidth (UL BW), low-density parity-check (LDPC) extra symbol segment (LDPC Extra Symbol Segment), separate forward error correction (FEC) padding factor (Pre-FEC Padding Factor), packet extension (PE) disambiguity, resource unit (RU) allocation (RU Allocation), uplink FEC code type (UL FEC Coding Type), and uplink extremely high throughput modulation and coding scheme (MCS) (UL EHT-MCS).

[0132] As shown in Figure 15, a trigger frame includes a Common Info field, a User Info List field, and a Padding field. As shown in Figure 15, the trigger frame also includes the following fields: Frame Control, Duration, Receive Address (RA), and Transmit Address (TA). The User Info List field includes multiple User Info fields. The User Info field can be understood as the EHT variant User Info field.

[0133] The Common Info field carries common information for each STA. As shown in Figure 16, the Common Info field includes the following fields: Trigger Type, UL Length, More TF, CS Required, UL BW, GI And HE / EHT-LTF Type / Trigger TXOP Sharing Mode, Reserved, Number of HE / EHT-LTF Symbols, LDPC Extra Symbol Segment, AP TX Power, Pre-FEC Padding Factor, PE Disambiguity, UL Spatial Reuse, HE / EHT / UHR P160, Special User Info Field Flag, EHT Reserved, and Trigger Dependent Common Info.

[0134] The User Info List field consists of one or more User Info fields. For the EHT Trigger frame, the User Info List field contains one Special User Info field and multiple EHT Variant User Info fields.

[0135] The Special User Info field carries the required U-SIG subfield of the requested EHT TB PPDU. The Special User Info field is located after the Common Info field in the trigger frame. The format is shown in Figure 17, where the AID12 subfield of the Special User Info field should be set to 2007. As shown in Figure 17, the Special User Info field also includes the following fields: PHY Version Identifier, UL BW Extension, Spatial Reuse 1, Spatial Reuse 2, U-SIG Disregard And Validate, Trigger Dependent User Info, and Reserved.

[0136] The EHT variant User Info field carries information about the non-AP STA indicated by AID12. The format of the EHT variant User Info field is shown in Figure 18 and includes the following fields: AID12, RU Allocation, UL FEC Coding Type, UL EHT-MCS, Reserved, Spatial Stream (SS) allocation or RU for random access (RA-RU) notification (SS Allocation / RA-RU Information), UL Target RSSI, PS160, and Trigger Dependent User Info.

[0137] The Padding field may appear in the trigger frame to extend the frame length so that the receiving STA has enough time to prepare the response PPDU for transmission after receiving the trigger frame SIFS.

[0138] In related technologies, in multi-AP collaborative DL transmission:

[0139] The Multi-AP coordinated transmission trigger frame only indicates the transmission parameters of the first DL PPDU after the trigger frame SIFS. It does not indicate the parameters of each PPDU in the subsequent BlockAck feedback process of each STA. This cannot guarantee the orthogonality of frequency domain symbols and synchronization between APs. In addition, if DL joint transmission is performed, the sharing AP does not pre-allocate frequency domain RUs to each shared AP, which will cause RU allocation conflicts between shared APs when requesting BlockAck.

[0140] In one example, when performing multi-AP coordinated DL transmission as shown in Figure 19, if the BA frame is replied in mode 1, the sharing AP only indicates the transmission parameters of the MU PPDU in the first Multi-AP coordinated transmission Trigger frame, and does not indicate the PPDU parameters of the transmission BA frame. As a result, the various fields within the PPDU are not aligned, and the synchronization between APs and the orthogonality of frequency domain symbols cannot be ensured.

[0141] In one example, when performing multi-AP cooperative DL transmission as shown in Figure 20, if the BA frame is replied in mode 2, the sharing AP only indicates the transmission parameters of the MU PPDU in the first Multi-AP coordinated transmission Trigger frame, and does not indicate the PPDU parameters for transmitting the next trigger frame and the BA frame. As a result, the various fields within the PPDU are not aligned, and the synchronization between APs and the orthogonality of frequency domain symbols cannot be ensured.

[0142] In related technologies, in multi-AP collaborative UL transmission:

[0143] When performing multi-AP coordinated UL transmission, as shown in Figure 21, if the AP responds with an Ack in the downlink, the sharing AP only indicates the transmission parameters of the PPDU for transmitting the trigger frame in the first Multi-AP coordinated transmission Trigger frame, and does not indicate the PPDU parameters for transmitting the subsequent TB PPDU and BlockAck. This results in the misalignment of the various fields within the PPDU, making it impossible to ensure synchronization between APs and orthogonality of frequency domain symbols. In addition, if collaborative UL MU-MIMO is performed, the sharing AP does not pre-allocate frequency domain RUs to each shared AP, which will cause RU usage conflicts between shared APs when transmitting BlockAcks.

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

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

[0146] S2201. A first access point device receives a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each of at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0147] The transmission control method provided in the embodiment of the present application is applied to a second access point device, as shown in FIG23 , and includes:

[0148] S2301. A second access point device sends a first frame to a first access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each of at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0149] Next, the transmission control method shown in FIG. 22 or FIG. 23 is further described.

[0150] The second access point device sends a first frame to the first access point device, where the first frame is used to indicate target transmission parameters used by at least one access point device participating in the coordinated transmission when transmitting a target frame.

[0151] The first access point device is any one of the multiple access point devices participating in the collaborative transmission. It is understandable that the multiple access point devices participating in the collaborative transmission can receive the first frame sent by the second access point device and control transmission between themselves and at least one associated non-access point device based on the target transmission parameters indicated in the first frame.

[0152] In the embodiment of the present application, the target transmission parameter is used to control the transmission of non-first frames after the first frame between the multiple access point devices participating in the coordinated transmission and at least one associated non-access point device.

[0153] In some embodiments, the target transmission parameters include at least one of the following:

[0154] The length of the PPDU carrying the target frame;

[0155] Guard interval (GI) and long training field (LTF) types;

[0156] Number of LTF symbols;

[0157] RU or MRU.

[0158] In the embodiment of the present application, the GI and LTF types may include one of the following: 1×LTF+1.6μs GI, 2×LTF+1.6μs GI, 4×LTF+3.2μs GI, etc.

[0159] In an embodiment of the present application, the number of LTF symbols may include one of the following: 1, 2, 4, 6, 8, etc.

[0160] The length, GI, LTF type, and number of LTF symbols of the PPDU carrying the target frame are used to ensure synchronization and frequency-domain symbol orthogonality between at least one access point device participating in the coordinated transmission. In this case, the length, GI, LTF type, and number of LTF symbols of the PPDU carrying the target frame configured in the first frame are used by the multiple access points participating in the coordinated transmission to control the transmission of the target frame, ensuring synchronization and frequency-domain symbol orthogonality between different access points.

[0161] The RU or MRU is used to ensure that there is no RU conflict between at least one access point device participating in the coordinated transmission. In this case, the multiple access points participating in the coordinated transmission use the RU configured in the first frame to control the transmission of the target frame, ensuring that there is no RU conflict between different access points.

[0162] In the embodiment of the present application, for an access point device participating in cooperative transmission, the target frame may include at least one of the following:

[0163] a first confirmation frame, where the first confirmation frame is a confirmation frame sent by the non-access point device to the access point device during downlink transmission. In this case, the confirmation frame is used to confirm the first data frame in the downlink transmission. The first data frame may or may not carry a trigger frame;

[0164] a first trigger frame, which is a trigger frame sent by the access point device to the non-access point device for triggering a first confirmation frame when the first data frame does not carry a trigger frame;

[0165] a second data frame, where the second data frame is a data frame sent by the non-access point device to the access point device during uplink transmission;

[0166] The second confirmation frame is sent by the access point device to the non-access point device to confirm the second data frame.

[0167] It is understandable that the first confirmation frame and the first trigger frame are used in the scenario of downlink MU PPDU transmission, and the second data frame and the second confirmation frame are used in the scenario of uplink MU PPDU transmission.

[0168] In the multi-AP cooperative transmission scenario shown in FIG. 19 or FIG. 20 , the first confirmation frame is an uplink BA frame.

[0169] In the multi-AP cooperative transmission scenario shown in FIG20 , the first trigger frame is a downlink Trigger frame.

[0170] In the multi-AP cooperative transmission scenario shown in FIG21 , the first data frame is a data frame carried by an uplink TB PPDU.

[0171] In the multi-AP cooperative transmission scenario shown in FIG21 , the second confirmation frame is a downlink BA frame.

[0172] In the embodiment of the present application, the target frame may include a first target frame and a second target frame, where the first target frame is an uplink frame and the second target frame is a downlink frame. It is understood that the first target frame includes: a first confirmation frame and / or a second data frame. The second target frame includes: a first trigger frame and / or a second confirmation frame.

[0173] If the target frame is a downlink frame, then after receiving the first frame, the AP participating in the coordinated transmission controls the transmission of the target frame based on the target transmission parameters for controlling the downlink frame indicated in the first frame. If the target frame is an uplink frame, then after receiving the first frame, the AP participating in the coordinated transmission sends the target transmission parameters for controlling the uplink frame indicated in the first frame to the associated non-access point device, so that the non-access point device transmits the uplink frame based on the received target transmission parameters for controlling the uplink frame.

[0174] In one example, the target frame includes a first confirmation frame. In the multi-AP collaborative transmission scenario shown in Figure 19, the first confirmation frame is an uplink BA frame, the second access point device is a sharing AP, and the APs participating in the collaborative transmission include: shared AP1 and shared AP2. STA1 and STA2 respectively use the transmission parameters of the uplink BA frame configured by the sharing AP to control the transmission parameters of the uplink BA frame to send BA frames to shared AP1, and STA3 and STA4 respectively use the transmission parameters of the uplink BA frame configured by the sharing AP to control the transmission parameters of the uplink BA frame to send BA frames to shared AP2, thereby controlling the transmission of BA frames received by shared AP1 and shared AP2.

[0175] In one example, the target frame includes a first confirmation frame and a first trigger frame. In the multi-AP collaborative transmission scenario shown in Figure 20, the first confirmation frame is an uplink BA frame, the first trigger frame is a Trigger frame, the second access point device is a sharing AP, and the APs participating in the collaborative transmission include: shared AP1 and shared AP2. Shared AP1 and shared AP2 use the transmission parameters for the Trigger frame allocated by the sharing AP to transmit the Trigger frame, and STA1 and STA2 respectively use the transmission parameters of the control uplink BA frame configured by the sharing AP to shared AP1 to send BA frames to shared AP1, and STA3 and STA4 respectively use the transmission parameters of the control uplink BA frame configured by the sharing AP to shared AP2 to send BA frames to shared AP2, thereby controlling the transmission of BA frames received by shared AP1 and shared AP2.

[0176] In one example, the target frame includes a second data frame and a second confirmation frame. In the multi-AP collaborative transmission scenario shown in Figure 21, the second data frame is a data frame carried by the TB PPDU, the second confirmation frame is a downlink BA frame, the second access point device is a sharing AP, and the APs participating in the collaborative transmission include: shared AP1 and shared AP2. STA1 and STA2 respectively use the transmission parameters of the TB PPDU control frame configured by the sharing AP to shared AP1 to send TB PPDU to shared AP1, and STA3 and STA4 respectively use the transmission parameters of the TB PPDU control frame configured by the sharing AP to shared AP2 to send TB PPDU to shared AP2, thereby controlling the transmission of the TB PPDU received by shared AP1 and shared AP2. Shared AP1 and shared AP2 use the transmission parameters for BA frames allocated by the sharing AP to control the transmission of BA frames.

[0177] In the embodiment of the present application, the second access point device is configured to control the transmission of non-first frames between each of the multiple access point devices participating in the collaborative transmission and the associated non-access point devices, so that the second access point device centrally controls the transmission of the multiple access point devices participating in the collaborative transmission, thereby realizing control of the collaborative transmission of multiple access point devices and ensuring normal transmission of different access point devices during the multi-AP collaborative transmission process.

[0178] In some embodiments, the second access point device is an access point device that initiates multi-access point device collaboration.

[0179] It can be understood that the second access point device is a sharing AP, and the first access point device is a shared AP.

[0180] The first frame sent by the sharing AP to the shared AP configures the target transmission information, thereby configuring the target transmission information in the preparation stage of multi-AP assistance. At this time, it can be understood that the PPDU carrying the first frame is an MU PPDU.

[0181] In some embodiments, the target transmission parameters include first transmission parameters for scheduling transmission of a first target frame, the first target frame being sent by a first non-access point device to the first access point device.

[0182] The first target frame is an uplink frame sent by the non-access point device to the access point device. The first transmission parameter used to control the transmission of the first target frame includes at least one of the following:

[0183] a first length, where the first length is the length of a first PPDU carrying the first target frame;

[0184] A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU;

[0185] A first number of symbols, where the first number of symbols is the number of LTF symbols in the first PPDU.

[0186] In some embodiments, the first target frame includes at least one of the following:

[0187] a first confirmation frame, where the first confirmation frame is used to confirm a first data frame sent by the first access point device, where the first data frame carries a trigger frame or does not carry a trigger frame;

[0188] The second data frame is a trigger-based data frame received by the first access point device.

[0189] In some embodiments, at least one of the following of the first transmission parameters is indicated by a first field in the first frame:

[0190] a first length, where the first length is the length of a first PPDU carrying the first target frame;

[0191] A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU;

[0192] A first number of symbols, where the first number of symbols is the number of LTF symbols in the first PPDU.

[0193] In an embodiment of the present application, the first field may indicate one or more of a first length, a first type, and a first number of symbols.

[0194] In an example, the first field indicates a first length.

[0195] In an example, the first field indicates a first length and a first type.

[0196] In an example, the first field indicates a first length, a first type, and a first number of symbols.

[0197] In an embodiment of the present application, the transmission parameters in the first transmission parameters that are not indicated by the first field can be determined by transmission parameters of other frames or pre-set or agreed upon by protocol.

[0198] In some embodiments, the manner in which the first field indicates the first transmission parameter includes the following manner 1A or manner 1B:

[0199] Mode 1A: The first field includes: a first subfield, a second subfield, and a third subfield;

[0200] The first length is indicated by the first subfield;

[0201] The first type is indicated by the second subfield;

[0202] The first number of symbols is indicated by the third subfield.

[0203] Mode 1B: The first field includes: a first subfield;

[0204] The first length is indicated by the first subfield;

[0205] The first type is the same as the type of the GI and LTF of the second PPDU carrying the second frame;

[0206] The first number of symbols is the same as the number of symbols of the LTF of the second PPDU.

[0207] The first subfield is used to indicate a first length. In some embodiments, if the first target frame is a first acknowledgment frame, the first subfield may be defined as the length subfield of the PPDU carrying the acknowledgment; if the first target frame is a second data frame, the first subfield may be defined as the length subfield of the UL TB PPDU.

[0208] The second subfield is used to indicate the first type. In some embodiments, if the first target frame is the first acknowledgment frame, the second subfield may be defined as the GI and LTF Type for PPDU carrying acknowledgement subfield; if the first target frame is the second data frame, the second subfield may be defined as the GI and LTF Type for UL TB PPDU subfield.

[0209] The second field can indicate different types of LTFs based on different values.

[0210] In one example, the value of the second field can be one of 0 to 3. If the value of the second field is 0, it indicates that the first type is 1×LTF+1.6μs GI. If the value of the second field is 1, it indicates that the first type is 2×LTF+1.6μs GI. If the value of the second field is 2, it indicates that the first type is 4×LTF+3.2μs GI. If the value of the second field is 3, it indicates reserved.

[0211] The third subfield is used to indicate the first number of symbols. In some embodiments, if the first target frame is the first acknowledgment frame, the second subfield may be defined as the LTF symbol data subfield of the PPDU carrying the acknowledgment (Number of LTF symbols for PPDU carrying acknowledgement subfield). Wherein, LTF may be HE / EHT / UHR-LTF, then the Number of LTF symbols for acknowledgement subfield may be replaced with the Number of HE / EHT / UHR-LTF symbols for PPDU carrying acknowledgement subfield; if the first target frame is the second data frame, then the third subfield may be defined as the LTF symbol number subfield of the UL TB PPDU (Number of LTF symbols for UL TB PPDU subfield).

[0212] The third field can indicate different LTF symbol numbers based on different values. In one example, the third field can take a value from 0 to 7. If the third field takes a value of 0, it indicates that the first symbol number is 1; if the third field takes a value of 1, it indicates that the first symbol number is 2; if the third field takes a value of 2, it indicates that the first symbol number is 4; if the third field takes a value of 3, it indicates that the first symbol number is 6; if the third field takes a value of 4, it indicates that the first symbol number is 8; if the third field takes a value from 5 to 7, it indicates reserved.

[0213] In some embodiments, if the first target frame is a first confirmation frame, the second frame is the first data frame sent by the first access point device before the first confirmation frame; or

[0214] If the first target frame is a second data frame, the second frame is a second trigger frame of the first access point device, and the second trigger frame is used to trigger the sending of the second data frame.

[0215] Taking the first target frame as the first confirmation frame as an example, the first transmission parameter indicated by the first field only includes the first length, then the type of GI and LTF of the first confirmation frame is the same as the type of GI and LTF of the first data frame confirmed by the first confirmation frame, and the number of LTF symbols of the first confirmation frame is the same as the number of LTF symbols of the first data frame.

[0216] Taking the first target frame as the second data frame as an example, the first transmission parameter indicated by the first field only includes the first length, then the type of GI and LTF of the second data frame is the same as the type of GI and LTF of the second trigger frame that triggers the second data frame, and the number of LTF symbols of the second data frame is the same as the number of LTF symbols of the second trigger frame.

[0217] In some embodiments, the target transmission parameters further include a second transmission parameter for scheduling transmission of a second target frame, the second target frame being sent by the first access point device to the first non-access point device.

[0218] At this time, the first field not only indicates the transmission parameter of the first target frame, ie, the first transmission parameter, but is also used to indicate the transmission parameter of the second target frame, ie, the second transmission parameter.

[0219] The second target frame is a downlink frame sent by the access point device to the non-access point device. The second transmission parameter used to control the transmission of the second target frame includes at least one of the following:

[0220] a second length, where the second length is the length of a third PPDU carrying the second target frame;

[0221] A second type, where the second type is a type of a GI and an LTF of the third PPDU;

[0222] The second number of symbols is the number of LTF symbols in the third PPDU.

[0223] In some embodiments, the second target frame includes at least one of the following: a first trigger frame and a second confirmation frame.

[0224] In some embodiments, at least one of the following of the second transmission parameters is indicated by the first field:

[0225] a second length, where the second length is the length of a third PPDU carrying the second target frame;

[0226] A second type, where the second type is a type of a GI and an LTF of the third PPDU;

[0227] The second number of symbols is the number of LTF symbols in the third PPDU.

[0228] In an example, the first field indicates the second length.

[0229] In an example, the first field indicates a second length and a second type.

[0230] In an example, the first field indicates a second length, a second type, and a second number of symbols.

[0231] In an embodiment of the present application, the transmission parameters in the second transmission parameters that are not indicated by the first field can be determined by transmission parameters of other frames or pre-set or agreed upon by protocol.

[0232] In the scenario where the second target frame is a first trigger frame independent of the first data frame and used to trigger the first confirmation frame

[0233] It can be understood that, at this time, the first target frame is the first confirmation frame.

[0234] The second field indicates the second transmission parameter in the following manner: manner 2A, manner 2B, or manner 2C:

[0235] Mode 2A: The first field includes: a first subfield;

[0236] The first length and the second length are indicated by the first subfield.

[0237] Mode 2B, the first field includes: a fourth subfield;

[0238] The second length is indicated by the fourth subfield.

[0239] Mode 2C: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0240] The second length consists of the fourth subfield;

[0241] The second type is represented by the fifth subfield;

[0242] The second symbol number is determined by the sixth subfield.

[0243] The first field here is used to indicate the first length and the second length. In some embodiments, the first field at this time can be defined as the UL Length for PPDU carrying acknowledgement sequences subfield, where the acknowledgement sequences include: trigger frame and BA frame.

[0244] The fourth subfield is used to indicate the second length. In some embodiments, the fourth subfield may be defined as the UL Length for PPDU carrying trigger frame subfield.

[0245] The fifth subfield is used to indicate the second type. In some embodiments, the fifth subfield may be defined as the GI and LTF type subfield for the PPDU carrying the trigger frame (GI And LTF Type for PPDU carrying trigger frame subfield).

[0246] The sixth subfield is used to indicate the second symbol number. In some embodiments, the sixth subfield may be defined as the LTF symbol data subfield for the PPDU carrying the trigger frame (Number of-LTF symbols for PPDU carrying trigger frame subfield). Wherein, LTF may be HE / EHT / UHRLTF, and the Number of-LTF symbols for PPDU carrying trigger frame subfield may be replaced with the Number of HE / EHT / UHR-LTF symbols for PPDU carrying trigger frame subfield.

[0247] In mode 2A, for the second transmission parameter, the first field includes a first subfield indicating a first length, and the first subfield is also used to indicate a second length. In this case, the first length and the second length are the same size.

[0248] In mode 2B, for the second transmission parameter, the first field includes a fourth subfield indicating the second length. In this case, the first field may include a first field and a fourth field, which are used to indicate the first length and the fourth length, respectively.

[0249] For Mode 2A and Mode 2B, in some embodiments, the third PPDU is a non-HT PPDU or a non-HT duplicated PPDU.

[0250] In Mode 2A and Mode 2B, the third PPDU carrying the first trigger frame is a non-HT PPDU or a non-HT duplicated PPDU, and the first field does not need to indicate the LTF type and the number of LTF symbols.

[0251] In mode 2C, for the second transmission parameter, the first field includes: a fourth subfield indicating the second length, a fifth subfield indicating the second type, and a sixth subfield indicating the second symbol data.

[0252] In an embodiment of the present application, the manner in which the fifth subfield indicates the second type may be the same as the manner in which the second subfield indicates the first type, and / or the manner in which the sixth subfield indicates the second number of symbols may be the same as the manner in which the third subfield indicates the first number of symbols, which will not be repeated here.

[0253] It can be understood that when the first field indicates the first transmission parameter and the second transmission parameter, any of the modes 1A and 1B in which the first field indicates the first transmission parameter can be combined with any of the modes 2A, 2B, and 2C in which the first field indicates the second transmission parameter.

[0254] Taking the combination of mode 1A and mode 2A as an example, the first field includes a first subfield, a second subfield and a third subfield. The first subfield is used to indicate the first length of the first confirmation frame and the second length of the first trigger frame. At this time, the target transmission parameters indicated by the first field include: the first length, the first type and the first number of symbols of the first confirmation frame, and the second length of the first trigger frame, wherein the first length and the second length are the same.

[0255] Taking the combination of mode 1A and mode 2B as an example, the first field includes a first subfield, a second subfield, a third subfield and a fourth subfield. The first field is used to indicate the target transmission parameters including: the first length, the first type and the first number of symbols of the first confirmation frame, and the second length of the first trigger frame, and the first length and the second length are indicated independently.

[0256] Taking the combination of mode 1A and mode 2C as an example, the first field includes: a first subfield, a second subfield, a third subfield, a fourth subfield, a fifth subfield and a sixth subfield. At this time, the target transmission parameters indicated by the first field include: the first length, the first type, and the first number of symbols of the first confirmation frame, and the second length, the second type and the second number of symbols of the first trigger frame.

[0257] Taking the combination of mode 1B and mode 2A as an example, the first field includes the first field, the first subfield is used to indicate the first length, and the fourth subfield is used to indicate the second length. At this time, the target transmission parameters indicated by the first field include: the first length of the first confirmation frame, the second length of the first trigger frame, wherein the first type of the first confirmation frame is the same as the type of GI and TLF of the first data frame, and the first number of symbols of the first confirmation frame is the same as the number of symbols of the TLF of the first data frame.

[0258] Taking the combination of mode 1B and mode 2B as an example, the first field includes a first subfield and a fourth subfield. The target transmission parameters indicated by the first subfield include: a first length and a second length, and the first length and the second length are independent. The first type is the same as the type of the GI and TLF of the first data frame, and the first number of symbols is the same as the number of symbols of the TLF of the first data frame.

[0259] Taking the combination of mode 1B and mode 2C as an example, the first field includes the first subfield and the fourth subfield, the fifth subfield, and the sixth subfield. The target transmission parameters indicated by the first field include: the first length of the first confirmation frame, and the second length, the second type, and the second number of symbols of the first trigger frame, and the first length and the second length are independent. The first type of the first confirmation frame is the same as the type of the GI and TLF of the first data frame, and the first number of symbols of the first confirmation frame is the same as the number of symbols of the TLF of the first data frame.

[0260] In the scenario where the second target frame is used as the second confirmation frame for confirming the second data frame

[0261] It can be understood that, at this time, the first target frame is the second data frame.

[0262] The second transmission parameter indication method includes the following method 2D or method 2E:

[0263] Method 2D,

[0264] The second length is the same as the length in a fourth PPDU carrying a second trigger frame, and the second trigger frame is used to trigger the second data frame;

[0265] The second type is the same as the type of the GI and LTF in the fourth PPDU;

[0266] The second number of symbols is the same as the number of symbols of the LTF in the fourth PPDU.

[0267] Mode 2E: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0268] The second length is indicated by the fourth subfield;

[0269] The second type is indicated by the fifth subfield;

[0270] The second number of symbols is indicated by the sixth subfield.

[0271] In mode 2D, the first field does not indicate the transmission parameters of the second confirmation frame. In this case, the length, GI, LTF type, and number of LTF symbols corresponding to the second confirmation frame may be the same as the length, GI, LTF type, and number of LTF symbols corresponding to the second trigger frame. The second trigger frame is a trigger frame sent by the first access point device to trigger the transmission of the second data frame.

[0272] For mode 2E, the fourth subfield is used to indicate the second length. In some embodiments, the fourth subfield may be defined as the UL Length for PPDU carrying acknowledgement subfield.

[0273] The fifth subfield is used to indicate the second type. In some embodiments, the fifth subfield may be defined as the GI and LTF type subfield for the PPDU carrying the acknowledgement frame (GI And LTF Type for PPDU carrying acknowledgement subfield).

[0274] The sixth subfield is used to indicate the second symbol number. In some embodiments, the sixth subfield may be defined as the LTF symbol data subfield for the PPDU carrying the acknowledgment frame (Number of-LTF symbols for PPDU carrying acknowledgement subfield). Where LTF can be HE / EHT / UHRLTF, the Number of-LTF symbols for PPDU carrying acknowledgement subfield may be replaced with the Number of HE / EHT / UHR-LTF symbols for PPDU carrying acknowledgement subfield.

[0275] It is understandable that, when the first field indicates the first transmission parameter and the second transmission parameter, any of the methods 1A and 1B for indicating the first transmission parameter can be combined with any of the methods 2D and 2E.

[0276] Taking the combination of mode 1A and mode 2D as an example, the first field includes a first subfield, a second subfield and a third subfield. The first subfield is used to indicate the first length of the second data frame. At this time, the target transmission parameters indicated by the first field include: the first length, first type and first symbol data of the second data frame, wherein the second length, second type and second symbol data of the second confirmation frame are respectively the same as the corresponding parameters of the second trigger frame.

[0277] Taking the combination of mode 1A and mode 2E as an example, the first field includes: a first subfield, a second subfield, a third subfield, a fourth subfield, a fifth subfield and a sixth subfield. At this time, the target transmission parameters indicated by the first field include: the first length, the first type and the first number of symbols of the second data frame, and the second length, the second type, and the second number of symbols of the second confirmation frame.

[0278] Taking the combination of mode 1B and mode 2D as an example, the first field includes a first subfield, and the first subfield is used to indicate the first length of the second data frame. At this time, the target transmission parameters indicated by the first field include: the first length of the second data frame, wherein the first type of the second data frame is the same as the type of GI and TLF of the second trigger frame, the first number of symbols of the second data frame is the same as the number of symbols of TLF of the second trigger frame, and the second length, second type and second symbol data of the second confirmation frame are respectively the same as the corresponding parameters of the second trigger frame.

[0279] Taking the combination of mode 1B and mode 2E as an example, the first field includes a first subfield, a fourth subfield, a fifth subfield and a sixth subfield. The first subfield is used to indicate the first length of the second data frame. At this time, the target transmission parameters indicated by the first field include: the first length of the second data frame, and the second length, second type and second symbol data of the second confirmation frame, wherein the first type of the second data frame is the same as the type of GI and TLF of the second trigger frame, and the first symbol number of the second data frame is the same as the symbol number of TLF of the second trigger frame.

[0280] In some embodiments, for Mode 2C or Mode 2E, the first field further includes at least one of the following:

[0281] a seventh subfield indicating a third number of symbols, where the seventh number of symbols is the number of symbols in the SIGNAL field in the third PPDU;

[0282] An eighth subfield indicating the modulation and coding scheme of the signal segment.

[0283] In some embodiments, the first frame includes at least one of the following:

[0284] Multi-AP coordinated transmission trigger frame;

[0285] Multi-User Request to Send - Transmission Opportunity Sharing Trigger Frame (MU-RTS TXS frame).

[0286] In some embodiments, if the first frame is a multi-access point coordinated transmission trigger frame, the first field is located in one of the following:

[0287] The trigger-dependent public information subfield in the public information field;

[0288] The trigger-dependent user information subfield in the special user information field.

[0289] In an embodiment of the present application, the first transmission information and / or the second transmission information indicated by the first field is public information, and the first field is located in a common information field (Common Info field) or a special user information field (Special User Info field) indicating public information.

[0290] If the first field is located in the common information field, the first field is located in the Trigger Dependent Common Info subfield in the common information field.

[0291] If the first field is located in the special user information field, the first field is located in the trigger dependent user information subfield (Trigger Dependent User Info subfield) in the special user information field.

[0292] In some embodiments, if the first frame is a multi-user request to send a transmission status trigger frame, the first field is a special user information field, and the value of the AID in the special user information field is a set value.

[0293] The multi-user request to send the transmission state trigger frame is used to share the transmission opportunity competed for by the second access point device with one or more access point devices participating in the multi-AP cooperative transmission, including the first access point device.

[0294] If the first field is located in a multi-user request to send transmission status trigger frame, the first field is a special user information field and the value of the AID in the AID field in the special user information field is a set value, indicating that the information indicated by the first field is applicable to the access point device participating in the collaboration.

[0295] In some embodiments, the value of AID is one of [1, 2006] [2008, 2044].

[0296] In some embodiments, the first transmission parameter includes a first resource unit RU or MRU, the first RU or MRU is determined by the second field of the first frame, and the first RU or MRU is the RU or MRU used when the first target frame is transmitted.

[0297] It is understandable that, when the first target frame is the first confirmation frame, the first confirmation frame may correspond to the first RU or MRU.

[0298] When the collaborative mode is joint transmission or collaborative beamforming, the first confirmation frame may have a corresponding first RU, so that when multiple non-access point devices send the first confirmation frame to the associated access point device, different non-access point devices use different first RUs to send the first confirmation frame.

[0299] In some embodiments, the first RU or MRU is:

[0300] The RU or MRU indicated by the second field; or,

[0301] The first access point device allocates an RU or MRU to the first non-access point device according to the RU or MRU indicated by the second field.

[0302] It is understandable that if the second field indicates an RU or MRU, the second access point device directly allocates the RU or MRU to each STA through the second field. In this case, the second field is for the STA.

[0303] If the first access point device allocates an RU or MRU to the first non-access point device according to the RU or MRU indicated by the second field, the second access point device pre-allocates an RU or MRU to the first access point device through the second field, and the first access point device independently determines the RU or MRU allocated to each STA according to the RU or MRU indicated by the second access point device, then the second field is for the STA first access point device.

[0304] In an embodiment of the present application, the first frame may include one or more second fields, and different second fields are for different STAs or shared APs.

[0305] In some embodiments, the second transmission parameter includes: a second RU or MRU, the second RU or MRU is determined by the second field of the first frame, and the second RU or MRU is the RU or MRU used when the second target frame is transmitted.

[0306] The second target transmission frame may be the first trigger frame or the second confirmation frame.

[0307] In an embodiment of the present application, the first confirmation frame may correspond to the existence of the first RU or MRU. In this case, the first data frame may carry a trigger frame or may not carry a trigger frame.

[0308] In the case that the first data frame does not carry a trigger frame, that is, the first trigger frame exists, the first trigger frame has a corresponding second RU or MRU.

[0309] In the embodiment of the present application, the second confirmation frame may exist in the second RU or MRU.

[0310] In some embodiments, the second RU or MRU is the RU or MRU indicated by the second field.

[0311] The second field can be understood as the RU Allocation field.

[0312] In some embodiments, the second field is used to indicate a RU or MRU in conjunction with at least one of the following:

[0313] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0314] Extension of the bandwidth subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0315] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

[0316] The bandwidth subfield (DL BW subfield) and the bandwidth subfield extension (DL BW Extension subfield) in the common information field of the multi-access point coordinated transmission trigger frame jointly indicate the bandwidth of the requested PPDU.

[0317] In this embodiment of the present application, the second field is used for RU or MRU allocation. Therefore, the second field can also be defined as the RU allocation subfield. The RU allocation subfield, DL BW subfield, DL BW Extension subfield, and PS160 subfield jointly indicate the size and location of the RU requested by each AP. The first RU or MRU is jointly indicated by the RU allocation subfield, DL BW subfield, DL BW Extension subfield, and PS160 subfield.

[0318] In one example, the shared AP pre-allocates its own RU or MRU to each shared AP participating in the collaboration through multiple second fields in the first frame. The shared AP uses these RUs or MRUs to transmit the trigger frame. The shared AP uses the RUs allocated by the sharing AP to allocate them to its associated STAs.

[0319] In one example, the BA frame is sent by the shared AP, and the sharing AP instructs the shared AP in advance to send the RU or MRU of the PPDU carrying the BA frame.

[0320] In some embodiments, the second field is located in a variable user information field of the first frame.

[0321] If the first frame is a multi-AP coordinated transmission trigger frame, the second field is located in the UHR variant User Info subfield in the multi-AP coordinated transmission trigger frame.

[0322] If the first frame is a MU-RTS TXS frame, the second field is located in the UHR variant User Info subfield of the MU-RTS TXS frame.

[0323] In an embodiment of the present application, the first frame may include a first field, and the first transmission data indicated by the first field is used to participate in the scheduling of the first target frame transmitted between multiple access point devices or non-access point devices, so that the first target frames between different access point devices or non-access point devices are synchronized or orthogonal in the frequency domain.

[0324] If the first field indicates second transmission data, the second transmission data is used for scheduling second target frames transmitted between multiple access point devices or non-access point devices, so that the second target frames between different access point devices or non-access point devices are synchronized or frequency domain orthogonal.

[0325] For different access point devices or non-access point devices, the same first transmission parameter or second transmission parameter is used to transmit the first target frame or the second target frame.

[0326] In an embodiment of the present application, the first frame may include multiple second fields, with different second fields being used to indicate RUs or MRUs of different access point devices or non-access point devices. If the second field indicates the RU or MRU of a first access point device, the RU or MRU of the non-access point device associated with the first access point device may be allocated by the access point device.

[0327] In the embodiment of the present application, the existence of the first field and the second field in the first frame may be independent.

[0328] In an embodiment of the present application, the first field may indicate the first transmission parameter and the second transmission parameter independently. In one example, the first field indicates the first transmission parameter. In another example, the first field indicates the second transmission parameter. In another example, the first field indicates the first transmission parameter and the second transmission parameter.

[0329] Similar to the first field, the first RU and the second RU are determined to be independent based on the second field.

[0330] In some embodiments, the first frame includes a third field, the third field being used to indicate a transmission parameter of one of the following:

[0331] If the first data frame sent by the first access point device carries a first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0332] If the first data frame does not carry the first confirmation frame and the first trigger frame, the first trigger frame is used to trigger the first confirmation frame;

[0333] A second data frame received by the first access point device.

[0334] The third field can be understood as a general field indicating at least one of the following transmission parameters, that is, indicating at least one of the following transmission parameters of different frames in different cooperation modes:

[0335] PPDU length;

[0336] Types of GI and LTF in PPDU;

[0337] Number of LTF symbols in the PPDU.

[0338] In DL Coordinated OFDMA, Joint Transmission, or coordinated beamforming mode, the third field may indicate transmission parameters of the first confirmation frame.

[0339] In DL Coordinated OFDMA or Joint Transmission or coordinated beamforming mode, the third field may indicate transmission parameters of the first confirmation frame and the first trigger frame.

[0340] In UL Coordinated OFDMA or UL MU-MIMO cooperative mode, the third field may indicate the transmission parameters of the second data frame. In this case, the transmission parameters of the second confirmation frame are consistent with the corresponding transmission parameters of the second trigger frame.

[0341] In some embodiments, if the third field is used to indicate transmission parameters of the first confirmation frame and the first trigger frame, the third field is used to indicate the length of the PPDU carrying the first trigger frame, and the first trigger frame is carried on a non-HT PPDU or a non-HT duplicated PPDU.

[0342] At this time, the PPDU carrying the first trigger frame may not include the VHT / HE / EHT / UHR-LTF field, and the third field only needs to indicate the length of the PPDU carrying the first trigger frame.

[0343] In some embodiments, if the third field is used to indicate the transmission parameters of the second data frame, the transmission parameters of the second confirmation frame are the same as the transmission parameters of the second trigger frame, the second trigger frame is used to trigger the sending of the second data frame, and the second confirmation frame is used to confirm the second data frame.

[0344] In some embodiments, the third field includes:

[0345] A ninth subfield, where the ninth subfield is used to indicate the length of the fifth PPDU;

[0346] a tenth subfield, where the tenth subfield is used to indicate the type of the LTF in the fifth PPDU;

[0347] The eleventh subfield is used to indicate the number of LTF symbols in the fifth PPDU.

[0348] Here, the fifth PPDU includes one of the following:

[0349] PPDU carrying the first confirmation frame;

[0350] A PPDU carrying a first confirmation frame and a PPDU carrying a first trigger frame;

[0351] A PPDU carrying a second data frame.

[0352] In some embodiments, the third field may be located in one of the following:

[0353] Trigger Dependent Common Info subfield of multi-AP coordinated transmission trigger frame;

[0354] Trigger Dependent User Info subfield in Special User Info field.

[0355] In some embodiments, the first frame further includes a fourth field, where the fourth field is used to determine a third RU or an MRU, where the third RU or the MRU is used when transmitting one of the following:

[0356] When the first data frame carries a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0357] A first confirmation frame and a first trigger frame when the first data frame does not carry a trigger frame, the first trigger frame being used to trigger the first confirmation frame;

[0358] The second data frame is a data frame sent by the first non-access point device to the first access point device.

[0359] In Joint Transmission or collaborative beamforming mode, the fourth field may indicate the RU or MRU of the first confirmation frame when the first data frame carries the trigger frame.

[0360] In the Joint Transmission or collaborative beamforming mode, the fourth field may indicate the RU of the first confirmation frame and the RU or MRU of the first trigger frame when the first data frame does not carry a trigger frame.

[0361] In the collaborative UL MU-MIMO collaborative mode, the fourth field may indicate the RU or MRU of the second data frame.

[0362] In some embodiments, the fourth field is used to indicate RU or MRU in conjunction with at least one of the following:

[0363] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0364] The bandwidth extension subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0365] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

[0366] In the embodiment of the present application, the fourth field may be defined as a UL acknowledgement RU allocation information field.

[0367] In some embodiments, the fourth field is located in the UHR variant User Info subfield in the multi-AP coordinated transmission trigger frame.

[0368] In an embodiment of the present application, the first frame may include a third field, and for different collaboration modes, the transmission information indicated by the third field is applied to different frames. However, when multiple access point devices or non-access point devices participating in the collaboration transmit corresponding frames, the transmission information indicated by the third field can be used to schedule the frame, so that the first target frames between different access point devices or non-access point devices are synchronized or frequency domain orthogonal.

[0369] In this embodiment of the present application, the first frame may include multiple fourth fields, and different fourth fields are used to indicate RUs or MRUs of different access point devices or non-access point devices. In different cooperation modes, the RUs or MRUs indicated by the fourth fields are used to schedule different frames.

[0370] Below, the transmission control method provided in the embodiment of the present application is further described in combination with different collaboration modes.

[0371] This embodiment of the present application designs signaling indications for each PPDU transmission parameter for the following four cooperative modes of multi-AP cooperative transmission: DL C-OFDMA, DL joint transmission, UL C-OFDMA, and UL cooperative MU-MIMO. Specifically, the signaling indications for each PPDU transmission parameter, including PPDU length, GI, HE / EHT / UHR-LTF type, and number of HE / EHT / UHR-LTF symbols, are designed to ensure frequency-domain symbol orthogonality of each PPDU and inter-AP synchronization throughout the transmission process. Furthermore, for the DL joint transmission mode and UL cooperative MU-MIMO mode in multi-AP cooperative transmission, signaling is designed to indicate the frequency-domain RUs (RUs) used by APs and non-AP STAs to transmit the acknowledgment sequence to avoid inter-AP conflicts. The acknowledgment sequence includes one of the following: acknowledgment, trigger frame, and acknowledgment.

[0372] Here, the structure of the PPDU is described by taking the Ultra-High Reliability (UHR) PPDU as an example.

[0373] The UHR PPDU has two formats: the UHR MU PPDU and the UHR TB PPDU. If the PPDU is not a response to a Trigger frame, the UHR MU PPDU format shown in Figure 24 is used for transmission to one or more users. In the UHR MU PPDU, the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG are called the Pre-UHR modulation field, while the UHR-STF, UHR-LTF, Data field, and PE field are called the UHR modulation field. The UHR TB PPDU format shown in Figure 25 is used for transmission in response to a Trigger frame from the AP. In the UHR TB PPDU, the L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG are called the Pre-UHR modulation field, while the UHR-STF, UHR-LTF, Data field, and PE field are called the UHR modulation field. The duration of the UHR-STF field in a UHR TB PPDU is twice that of the UHR-STF field in a UHR MU PPDU. For a UHR PPDU, each UHR-LTF symbol has the same GI duration as each data symbol: 0.8μs, 1.6μs, or 3.2μs. The UHR-LTF field consists of three types: 1x UHR-LTF, 2x UHR-LTF, and 4x UHR-LTF. The duration of each 1x UHR-LTF, 2x UHR-LTF, or 4x UHR-LTF symbol without a GI is 3.2μs, 6.4μs, or 12.8μs, respectively. Data symbols without a GI have a duration of 12.8μs.

[0374] The following describes the transmission control methods in downlink transmission, uplink transmission, and general signaling scenarios respectively.

[0375] DL transmission

[0376] For multi-AP DL transmission, for DL ​​coordinated OFDMA and Joint Transmission, relevant parameters of the PPDU that indicate each AP to request the transmission of acknowledgment sequences are designed to ensure orthogonality of frequency domain symbols and synchronization between APs.

[0377] For collaborative mode DL Coordinated OFDMA

[0378] In one embodiment, during DL Coordinated OFDMA transmission, when a non-AP STA receives a DL MU PPDU containing a QoS data frame or QoS Null frame with a HETP Ack policy, a MU-BAR Trigger frame or a GCR MU-BAR Trigger frame, or a management frame requesting acknowledgment, the non-AP STA should send an UL immediate response based on the scheduling information in the trigger frame or TRS control subfield, as shown in Figure 26.

[0379] The scheduling information in the trigger frame or TRS control subfield is indicated by the sharing AP using the first field in the first frame. For example, the first field is UL acknowledgement information, and its subfields can be the following two options, as shown in embodiments 1 and 2 respectively.

[0380] For the first field position:

[0381] If the first frame is a multi-AP coordinated transmission trigger frame, the first field is located in the Trigger Dependent Common Info subfield or the Trigger Dependent User Info subfield in the Special User Info field of the frame;

[0382] If the first frame is a MU-RTS TXS frame, the first field is located in the special user info field of the frame and its AID12 subfield is equal to one of [1, 2006] [2008, 2044], with a total of N bits, for example, N=40. Except for the first field, the remaining bits are reserved fields.

[0383] Example 1

[0384] As shown in Figure 27, the subfields of UL acknowledgement information include: UL Length for acknowledgement subfield, GI And LTF Type for acknowledgement subfield, and Number of HE / EHT / UHR-LTF symbols for acknowledgement subfield, which respectively indicate the length of the PPDU carrying the BlockAck frame, the GI and LTF type, and the number of HE / EHT / UHR-LTF symbols.

[0385] GI And LTF Type for acknowledgement subfield: A value of 0 indicates 1×HE / EHT / UHR-LTF+1.6μs GI; a value of 1 indicates 2×HE / EHT / UHR-LTF+1.6μs GI; a value of 2 indicates 4×HE / EHT / UHR-LTF+3.2μs GI; a value of 3 indicates reserved.

[0386] Number of HE / EHT / UHR-LTF symbols for acknowledgement subfield: A value of 0 indicates one HE-LTF, EHT-LTF, or UHR-LTF symbol; a value of 1 indicates two HE-LTF, EHT-LTF, or UHR-LTF symbols; a value of 2 indicates four HE-LTF, EHT-LTF, or UHR-LTF symbols; a value of 3 indicates six HE-LTF, EHT-LTF, or UHR-LTF symbols; a value of 4 indicates eight HE-LTF, EHT-LTF, or UHR-LTF symbols; and values ​​5-7 indicate reserved.

[0387] It should be noted that the meanings of the GI And LTF Type and Number of HE / EHT / UHR-LTF symbols that appear later are the same and are not repeated here.

[0388] Example 2

[0389] As shown in Figure 28, the UL Acknowledgement Information subfields include: UL Length for Acknowledgement subfield, which indicates the length of the PPDU carrying the BlockAck frame. The GI and LTF types, and the number of HE / EHT / UHR-LTF symbols are consistent with those of the DL MU PPDU received by the non-AP STA.

[0390] In another embodiment, each AP participating in multi-AP transmission uses a MU-BAR Trigger frame or a GCR MU-BAR Trigger frame to request an acknowledgment frame from multiple non-AP STAs. Prior to this, each AP participating in multi-AP transmission sent a QoS data frame with a Block Ack ack policy to these non-AP STAs, or each AP participating in multi-AP transmission did not receive immediate acknowledgment frames from these non-AP STAs after sending a QoS data frame with a HETP Ack ack policy in a MU PPDU. As shown in Figure 29.

[0391] The PPDU transmission parameters of the trigger frame carrying the acknowledgment request and the PPDU transmission parameters of the acknowledgment frame are indicated by the sharing AP using the first field in the first frame. For example, the first field is UL acknowledgement information, and its subfields can be the following four options, as shown in Examples 3 to 6, respectively.

[0392] Example 3

[0393] The contents of the subfields of UL acknowledgement information are shown in Figure 30:

[0394] Length for acknowledgement sequences subfield: indicates the length of the PPDU carrying the trigger frame of the acknowledgment and the PPDU carrying the BlockAck frame;

[0395] GI And LTF Type for PPDU carrying acknowledgement subfield: indicates the GI and LTF type of the PPDU carrying the BlockAck frame;

[0396] Number of HE / EHT / UHR-LTF symbols for PPDU carrying acknowledgement subfield: Indicates the number of HE / EHT / UHR-LTF symbols for the PPDU carrying the BlockAck frame.

[0397] That is, the two PPDUs in the acknowledgment sequence use the same length, specifying the GI and LTF type, and the number of HE / EHT / UHR-LTF symbols, of the PPDU carrying the BlockAck frame. The PPDU carrying the trigger frame requesting the acknowledgment is a non-HT PPDU or a non-HT duplicated PPDU; the PPDU carrying the BlockAck frame is an HE TB PPDU, an EHT TB PPDU, or a UHR TB PPDU.

[0398] Example 4

[0399] The subfield contents of UL acknowledgement information are shown in Figure 31 and include:

[0400] Length for PPDU carrying trigger subfield: indicates the length of the PPDU carrying the trigger frame requesting acknowledgment;

[0401] Length for PPDU carrying acknowledgement subfield: indicates the length of the PPDU carrying the BlockAck frame.

[0402] That is, the two PPDUs in the acknowledgment sequences use different lengths. The PPDU carrying the trigger frame requesting the acknowledgment is a non-HT PPDU or a non-HT duplicated PPDU. The PPDU carrying the BlockAck frame is an HE TB PPDU, EHT TB PPDU, or UHR TB PPDU. The GI and LTF types, as well as the number of HE / EHT / UHR-LTF symbols, are the same as those in the DL MU PPDU (second frame).

[0403] Example 5

[0404] The contents of the subfields of UL acknowledgement information are shown in Figure 32:

[0405] Length for PPDU carrying trigger subfield: indicates the length of the PPDU carrying the trigger frame requesting acknowledgment;

[0406] Length for PPDU carrying acknowledgement subfield: indicates the length of the PPDU carrying the BlockAck frame;

[0407] GI And LTF Type for acknowledgement sequences subfield: indicates the GI and LTF type of the PPDU carrying the BlockAck frame;

[0408] Number of HE / EHT / UHR-LTF symbols for acknowledgement sequences subfield: indicates the number of HE / EHT / UHR-LTF symbols in the PPDU that carries the BlockAck frame.

[0409] That is, the two PPDUs in the acknowledgment sequence use different lengths, specifying the GI and LTF type, and the number of HE / EHT / UHR-LTF symbols, of the PPDU carrying the BlockAck frame. The PPDU carrying the trigger frame requesting the acknowledgment is a non-HT PPDU or a non-HT duplicated PPDU; the PPDU carrying the BlockAck frame is an HE TB PPDU, an EHT TB PPDU, or a UHR TB PPDU.

[0410] Example 6

[0411] The subfield contents of UL acknowledgement information are shown in Figure 33 and include:

[0412] Length for PPDU carrying trigger subfield: indicates the length of the PPDU carrying the trigger frame requesting acknowledgment;

[0413] GI And LTF Type for PPDU carrying trigger subfield: indicates the GI and LTF type of the PPDU carrying the trigger frame requesting acknowledgment;

[0414] Number of HE / EHT / UHR-LTF symbols for PPDU carrying trigger subfield: indicates the number of HE / EHT / UHR-LTF symbols in the PPDU carrying the trigger frame requesting acknowledgment;

[0415] Number of HE-SIG-B / EHT-SIG / UHR-SIG symbols for PPDU carrying trigger: indicates the number of HE-SIG-B / EHT-SIG / UHR-SIG symbols in the PPDU carrying the trigger frame requesting acknowledgment. It is set to the value of the number of HE-SIG-B / EHT-SIG / UHR-SIG symbols minus 1.

[0416] HE-SIG-B / EHT-SIG / UHR-SIG MCS for PPDU carrying trigger subfield: indicates the HE-SIG-B / EHT-SIG / UHR-SIG MCS of the PPDU carrying the trigger frame requesting acknowledgment. The value 0 indicates BPSK, code rate 1 / 2; the value 1 indicates QPSK, code rate 1 / 2; the value 2 indicates 16-QAM, code rate 1 / 2; the value 3 indicates BPSK-DCM, code rate 1 / 2;

[0417] Length for PPDU carrying acknowledgement subfield: indicates the length of the PPDU carrying the acknowledgment frame;

[0418] GI And LTF Type for PPDU carrying acknowledgement subfield: indicates the GI and LTF type of the PPDU carrying the acknowledgment frame;

[0419] Number of HE / EHT / UHR-LTF symbols for PPDU carrying acknowledgement subfield: Indicates the number of HE / EHT / UHR-LTF symbols of the PPDU carrying the acknowledgment frame.

[0420] That is, the two PPDUs in the acknowledgment sequence use different lengths, GI and LTF types, and HE / EHT / UHR-LTF symbol counts. The PPDU carrying the trigger frame requesting the acknowledgment is a non-HT PPDU, non-HT duplicated PPDU, HE MU PPDU, EHT MU PPDU, or UHR MU PPDU; the PPDU carrying the BlockAck frame is an HE TB PPDU, EHT TB PPDU, or UHR TB PPDU.

[0421] Joint Transmission

[0422] In one embodiment, during DL joint transmission, when a non-AP STA receives a DL MU PPDU containing a QoS data frame or QoS Null frame with a HETP Ack policy, a MU-BAR Trigger frame or a GCR MU-BAR Trigger frame, or a management frame requesting acknowledgment, the non-AP STA should send a UL immediate response based on the scheduling information in the trigger frame or the TRS control subfield. PPDUs transmitted between different Shared APs and different STAs use different SSs. As shown in Figure 34 , the PPDU from Shared AP1 to STA1 uses an SS with an identifier of i_ss of 1, the PPDU from Shared AP2 to STA1 uses an SS with an identifier of i_ss of 2, the PPDU from Shared AP2 to STA1 uses an SS with an identifier of i_ss of 3, and the PPDU from Shared AP2 to STA2 uses an SS with an identifier of i_ss of 4.

[0423] The scheduling information in the trigger frame or TRS control subfield is indicated by the sharing AP in the first frame using the first field and the second field. For example, the first field is UL acknowledgement information, and its subfields can be two options, as shown in Examples 1 and 2, respectively; the second field is UL acknowledgement RU allocation information, as shown in Example 7.

[0424] For the first field position:

[0425] If the first frame is a multi-AP coordinated transmission trigger frame, the first field is located in the Trigger Dependent Common Info subfield in the multi-AP coordinated transmission trigger frame or the Trigger Dependent User Info subfield in the Special User Info field;

[0426] If the first frame is a MU-RTS TXS frame, the first field is located in the special user info field of the frame and its AID12 subfield is equal to one of [1, 2006] [2008, 2044], with a total of N bits, for example, N=40. Except for the first field, the remaining bits are reserved fields.

[0427] For the second field position:

[0428] If the first frame is a multi-AP coordinated transmission trigger frame, the second field is located in the UHR variant User Info subfield in the multi-AP coordinated transmission trigger frame;

[0429] If the first frame is a MU-RTS TXS frame, the second field is located in the UHR variant User Info subfield of the frame.

[0430] Example 7

[0431] As shown in Figure 35, the UL acknowledgement RU allocation information, the DL BW subfield in the Common Info field in the multi-AP coordinated transmission trigger frame, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field,

[0432] Jointly indicate the size and position of the frequency domain RU / MRU of the acknowledgment sequence requested by each AP participating in multi-AP transmission identified by the AID12 subfield. Each AP participating in multi-AP transmission independently decides to allocate the PPDU carrying the acknowledgment frame to the non-AP STA based on the resource; or jointly indicate the size and position of the frequency domain RU / MRU of the PPDU carrying the acknowledgment frame transmitted by each non-AP STA participating in multi-AP transmission identified by the VAID 12 subfield.

[0433] In another embodiment, each AP participating in multi-AP transmission uses a MU-BAR Trigger frame or a GCR MU-BAR Trigger frame to request an acknowledgment frame from multiple non-AP STAs. Prior to this, each AP participating in multi-AP transmission sent a QoS data frame with a Block Ack ack policy to these non-AP STAs, or each AP participating in multi-AP transmission did not receive immediate acknowledgment frames from these non-AP STAs after sending a QoS data frame with a HETP Ack ack policy in a MU PPDU. As shown in Figure 36.

[0434] The trigger frame for transmitting the acknowledgment request and the PPDU transmission parameters for the acknowledgment request frame are indicated by the sharing AP using the first field and the second field in the first frame. For example, the first field is UL acknowledgment information, and its subfields may be four options, as shown in Examples 3 to 6, respectively. The second field is UL acknowledgment RU allocation information, as shown in Example 8.

[0435] Example 8

[0436] The UL acknowledgement RU allocation information shown in Figure 37, together with the DL BW subfield in the Common Info field, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field in the multi-AP coordinated transmission trigger frame,

[0437] The joint indication is the size and position of the frequency domain RU / MRU of the PPDU transmitted by the AP participating in multi-AP transmission, identified by the AID 12 subfield. The PPDU carries the trigger frame requesting acknowledgment. Furthermore, the AP participating in multi-AP transmission independently determines the frequency domain RU / MRU allocated to the PPDU for transmitting the acknowledgment frame to the non-AP STA based on the frequency domain resources.

[0438] UL transmission

[0439] For multi-AP UL transmission, for UL coordinated OFDMA and collaborative UL MU-MIMO, relevant parameters are designed to instruct each non-AP STA to transmit a TB PPDU and each AP to transmit an acknowledgment PPDU to ensure orthogonality of frequency domain symbols and synchronization between APs.

[0440] For collaborative mode UL Coordinated OFDMA

[0441] When performing UL multi-AP coordinated OFDMA transmission, if an AP receives TB PPDUs from multiple STAs and requires an immediate acknowledgment (e.g., a QoS data frame carrying a Normal Ack or Implicit BAR ack policy, or a management frame other than Action No Ack), it should send the immediate acknowledgment in the form of a SU PPDU or MU PPDU. The immediate acknowledgment can be an Ack frame, a Compressed BlockAck frame, or a Multi-STA BlockAck frame, as shown in Figure 38.

[0442] Among them, the transmission parameters of the TB PPDU (PPDU length, GI and LTF type, number of HE / EHT / UHR-LTF symbols) and the transmission parameters of the PPDU carrying the acknowledgment frame have the following two schemes:

[0443] Scenario 1: (Indicates that the 3rd frame, frame 4 and frame 2 have the same length)

[0444] The sharing AP uses the first field only in the first frame to indicate the transmission parameters of the TB PPDU. The transmission parameters of the PPDU carrying the acknowledgement frame are the same as those of the PPDU carrying the trigger frame. For example, the first field is UL TB PPDU information, and its subfield can have two options. As shown in Examples 1 and 2, respectively, replace the "PPDU carrying acknowledgement" subfield with "UL TB PPDU."

[0445] Option 2: Indicates the 3rd and 4th frames

[0446] The sharing AP uses the first field in the first frame to indicate the transmission parameters of the TB PPDU and the transmission parameters of the PPDU carrying the acknowledgment. For example, the first field is UL TB PPDU and Acknowledgement PPDU Information, as shown in Example 6, and the subfields are replaced as follows:

[0447] "PPDU carrying trigger" is replaced with "PPDU carrying acknowledgement";

[0448] "PPDU carrying acknowledgement" is replaced with "UL TB PPDU".

[0449] For collaborative UL MU-MIMO

[0450] When performing collaborative UL MU-MIMO transmission, if the AP receives TB PPDUs from multiple STAs and requires an immediate acknowledgment (e.g., a QoS data frame carrying a Normal Ack or Implicit BAR ack policy, or a management frame other than an Action No Ack), the AP should send the immediate acknowledgment in the form of a SU PPDU or MU PPDU. The immediate acknowledgment can be an Ack frame, a Compressed BlockAck frame, or a Multi-STA BlockAck frame, as shown in Figure 39.

[0451] There are two schemes for indicating the transmission parameters of the TB PPDU and the PPDU carrying the acknowledgment (PPDU length, GI and LTF type, and the number of HE / EHT / UHR-LTF symbols), which are the same as Scheme 1 and Scheme 2 in Section 3.3.1. The frequency domain resource RU for the PPDU carrying the acknowledgment is indicated by the sharing AP using the second field in the first frame. For example, the second field is the DL acknowledgement RU allocation information, as shown in Example 9.

[0452] Example 9

[0453] The DL acknowledgement RU allocation information shown in Figure 40 is combined with the DL BW subfield in the Common Info field, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field in the multi-AP coordinated transmission trigger frame.

[0454] The AID 12 subfield jointly indicates the size and position of the frequency domain RU / MRU used by the AP participating in multi-AP transmission, identified by the AID 12 subfield, to transmit the PPDU carrying the acknowledgment.

[0455] General Signaling Indicator

[0456] This general signaling indication is applicable to the following four cooperative modes and designs the signaling indication of each PPDU transmission parameter: DL C-OFDMA, DL joint transmission, UL C-OFDMA, and UL cooperative MU-MIMO.

[0457] UL TB PPDU information field

[0458] As shown in FIG. 41A , this field is located in the Trigger Dependent Common Info subfield of the multi-AP coordinated transmission trigger frame or the Trigger Dependent User Info subfield in the Special User Info field.

[0459] (1) DL coordinated OFDMA transmission: If the transmission is in the manner of Figure 26, this field indicates the TB PPDU parameters for the third frame. If the transmission is in the manner of Figure 2B, this field indicates the TB PPDU parameters for the fourth frame and the PPDU length of the third frame. The third frame is a non-HT duplicate PPDU.

[0460] (2) DL joint transmission: If the transmission is performed in the manner shown in Figure 34, this field indicates the TB PPDU parameters for the third frame. If the transmission is performed in the manner shown in Figure 36, this field indicates the TB PPDU parameters for the fourth frame and also indicates the PPDU length of the third frame. The third frame is a non-HT duplicate PPDU.

[0461] (3) UL coordinated OFDMA transmission: If transmitted in the manner of Figure 38, this field indicates the TB PPDU parameters of the third frame transmitted, and the PPDU parameters of the fourth frame are the same as those of the second frame (the PPDU parameters of the second frame can refer to the relevant parameters of the first PPDU in the Multi-AP coordinated transmission Trigger frame).

[0462] (4) UL collaborative MU-MIMO transmission: If transmitted in the manner of Figure 39, this field indicates the TB PPDU parameters of the third frame of transmission, and the PPDU parameters of the fourth frame are the same as those of the second frame (the PPDU parameters of the second frame can refer to the relevant parameters of the first PPDU in the Multi-AP coordinated transmission Trigger frame).

[0463] UL acknowledgement RU allocation information field

[0464] This field is located in the UHR variant User Info subfield in the multi-AP coordinated transmission trigger frame.

[0465] (5) DL joint transmission: If transmitted in the manner of Figure 34, this field, together with the DL BW subfield in the Common Info field of the multi-AP coordinated transmission trigger frame, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field, indicates the frequency domain RU / MRU of the TB PPDU transmitted in the third frame. If transmitted in the manner of Figure 36, this field, together with the DL BW subfield in the Common Info field of the multi-AP coordinated transmission trigger frame, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field, indicates the frequency domain RU / MRU of the TB PPDU transmitted in the third and fourth frames.

[0466] (6) UL collaborative MU-MIMO transmission: If transmitted in the manner of Figure 39, this field, together with the DL BW subfield in the Common Info field in the multi-AP coordinated transmission trigger frame, the DL BW Extension subfield in the Special User Info field, and the PS160 subfield in the UHR variant User Info field, indicates the frequency domain RU / MRU of the TB PPDU of the third frame.

[0467] The format of the acknowledgement RU allocation information field may be as shown in FIG. 41B .

[0468] It should be noted that the information or fields included in the frame format in the embodiment of the present application can be deleted, modified or added according to actual needs, and different information and fields are independent of each other.

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

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

[0471] FIG42 is a schematic diagram of the structure of a first access point device provided in an embodiment of the present application. As shown in FIG42 , the first access point device 4200 includes:

[0472] The first communication unit 4201 is configured to receive a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0473] It is understandable that the first access point device further includes a processing unit configured to parse the received first frame to obtain the target transmission parameter indicated by the first frame.

[0474] In some embodiments, the second access point device is an access point device that initiates multi-access point device collaboration.

[0475] In some embodiments, the first frame includes at least one of the following:

[0476] Multiple access points coordinate transmission of trigger frames;

[0477] Multiple users request to send-transmission opportunity sharing trigger frame.

[0478] In some embodiments, the target transmission parameters include first transmission parameters for scheduling transmission of a first target frame, the first target frame being sent by a first non-access point device to the first access point device.

[0479] In some embodiments, the first target frame includes at least one of the following:

[0480] a first confirmation frame, where the first confirmation frame is used to confirm a first data frame sent by the first access point device, where the first data frame carries a trigger frame or does not carry a trigger frame;

[0481] The second data frame is a trigger-based data frame received by the first access point device.

[0482] In some embodiments, at least one of the following of the first transmission parameters is indicated by a first field in the first frame:

[0483] a first length, where the first length is the length of a first PPDU carrying the first target frame;

[0484] A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU;

[0485] A first number of symbols, where the first number of symbols is the number of LTF symbols in the first PPDU.

[0486] In some embodiments, the first field includes: a first subfield, a second subfield, and a third subfield;

[0487] The first length is indicated by the first subfield;

[0488] The first type is indicated by the second subfield;

[0489] The first number of symbols is indicated by the third subfield.

[0490] In some embodiments, the first field includes: a first subfield;

[0491] The first length is indicated by the first subfield;

[0492] The first type is the same as the type of the GI and LTF of the second PPDU carrying the second frame;

[0493] The first number of symbols is the same as the number of symbols of the LTF of the second PPDU.

[0494] In some embodiments, if the first target frame is a first confirmation frame, the second frame is the first data frame sent by the first access point device before the first confirmation frame; or

[0495] If the first target frame is a second data frame, the second frame is a second trigger frame of the first access point device, and the second trigger frame is used to trigger the sending of the second data frame.

[0496] In some embodiments, the target transmission parameters further include a second transmission parameter for scheduling transmission of a second target frame, the second target frame being sent by the first access point device to the first non-access point device.

[0497] In some embodiments, at least one of the following of the second transmission parameters is indicated by the first field:

[0498] a second length, where the second length is the length of a third PPDU carrying the second target frame;

[0499] A second type, where the second type is a type of a GI and an LTF of the third PPDU;

[0500] The second number of symbols is the number of LTF symbols in the third PPDU.

[0501] In some embodiments, the second target frame is a first trigger frame independent of the first data frame and used to trigger the first confirmation frame.

[0502] In some embodiments, the first field includes: a first subfield;

[0503] The first length and the second length are indicated by the first subfield.

[0504] In some embodiments, the first field includes: a fourth subfield;

[0505] The second length is indicated by the fourth subfield.

[0506] In some embodiments, the third PPDU is a non-HT PPDU or a non-HT duplicated PPDU.

[0507] In some embodiments, the first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0508] The second length is indicated by the fourth subfield;

[0509] The second type is indicated by the fifth subfield;

[0510] The second number of symbols is indicated by the sixth subfield.

[0511] In some embodiments, the second target frame is a second confirmation frame used to confirm the second data frame.

[0512] In some embodiments, the second length is the same as a length in a fourth PPDU carrying a second trigger frame, and the second trigger frame is used to trigger the second data frame;

[0513] The second type is the same as the type of the GI and LTF in the fourth PPDU;

[0514] The second number of symbols is the same as the number of symbols of the LTF in the fourth PPDU.

[0515] In some embodiments, the first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0516] The second length is indicated by the fourth subfield;

[0517] The second type is indicated by the fifth subfield;

[0518] The second number of symbols is indicated by the sixth subfield.

[0519] In some embodiments, the first field further includes at least one of the following:

[0520] a seventh subfield indicating a third number of symbols, where the seventh number of symbols is the number of symbols in the SIGNAL field in the third PPDU;

[0521] An eighth subfield indicating the modulation and coding scheme of the signal segment.

[0522] In some embodiments, if the first frame is a multi-access point coordinated transmission trigger frame, the first field is located in one of the following:

[0523] The trigger-dependent public information subfield in the public information field;

[0524] The trigger-dependent user information subfield in the special user information field.

[0525] In some embodiments, if the first frame is a multi-user request to send a transmission status trigger frame, the first field is located in the special user information field, and the value of the AID in the special user information field is a set value.

[0526] In some embodiments, the first transmission parameter includes a first resource unit RU or multiple resource units MRU, the first RU or MRU is determined by the second field of the first frame, and the first RU is the RU or MRU used when the first target frame is transmitted.

[0527] In some embodiments, the first RU or MRU is:

[0528] The RU or MRU indicated by the second field; or,

[0529] The first access point device allocates an RU or MRU to the first non-access point device according to the RU or MRU indicated by the second field.

[0530] In some embodiments, the second transmission parameter includes: a second RU or MRU, the second RU or MRU is determined by the second field of the first frame, and the second RU or MRU is the RU or MRU used when the second target frame is transmitted.

[0531] In some embodiments, the second RU or MRU is the RU or MRU indicated by the second field.

[0532] In some embodiments, the second field is used to indicate a RU or MRU in conjunction with at least one of the following:

[0533] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0534] Extension of the bandwidth subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0535] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame;

[0536] The first RU is one of the at least one RU.

[0537] In some embodiments, the second field is located in a variable user information field of the first frame.

[0538] In some embodiments, the first frame includes a third field, the third field being used to indicate a transmission parameter of one of the following:

[0539] If the first data frame sent by the first access point device carries a first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0540] If the first data frame does not carry the first confirmation frame and the first trigger frame, the first trigger frame is used to trigger the first confirmation frame;

[0541] A second data frame received by the first access point device.

[0542] In some embodiments, if the third field is used to indicate transmission parameters of the first confirmation frame and the first trigger frame, the third field is used to indicate the length of the PPDU carrying the first trigger frame, and the first trigger frame is carried on a non-HT PPDU or a non-HT duplicated PPDU.

[0543] In some embodiments, if the third field is used to indicate the transmission parameters of the second data frame, the transmission parameters of the second confirmation frame are the same as the transmission parameters of the second trigger frame, the second trigger frame is used to trigger the sending of the second data frame, and the second confirmation frame is used to confirm the second data frame.

[0544] In some embodiments, the third field includes:

[0545] A ninth subfield, where the ninth subfield is used to indicate the length of the fifth PPDU;

[0546] a tenth subfield, where the tenth subfield is used to indicate the type of the LTF in the fifth PPDU;

[0547] The eleventh subfield is used to indicate the number of LTF symbols in the fifth PPDU.

[0548] In some embodiments, the first frame further includes a fourth field, where the fourth field is used to indicate a third RU or an MRU, where the third RU or the MRU is used when transmitting one of the following:

[0549] If the first data frame carries the first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0550] If the first data frame does not carry the first confirmation frame and the first trigger frame, the first trigger frame is used to trigger the first confirmation frame;

[0551] The second data frame is a data frame sent by the first non-access point device to the first access point device.

[0552] In some embodiments, the fourth field is used to indicate the third RU or MRU in conjunction with at least one of the following:

[0553] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0554] Extension of the bandwidth subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0555] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

[0556] FIG43 is a schematic diagram of the structure of a second access point device provided in an embodiment of the present application. As shown in FIG43 , the second access point device 4300 includes:

[0557] The second communication unit 4301 is configured to send a first frame to a first access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used by each access point device among at least one access point device participating in the collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

[0558] It is understandable that the second access point device further includes a processing unit configured to generate the first frame based on the target transmission parameter.

[0559] In some embodiments, the second access point device is an access point device that initiates multi-access point device collaboration.

[0560] In some embodiments, the first frame includes at least one of the following:

[0561] Multiple access points coordinate transmission of trigger frames;

[0562] Multiple users request to send-transmission opportunity sharing trigger frame.

[0563] In some embodiments, the target transmission parameters include first transmission parameters for scheduling transmission of a first target frame, the first target frame being sent by a first non-access point device to the first access point device.

[0564] In some embodiments, the first target frame includes at least one of the following:

[0565] a first confirmation frame, where the first confirmation frame is used to confirm a first data frame sent by the first access point device, where the first data frame carries a trigger frame or does not carry a trigger frame;

[0566] The second data frame is a trigger-based data frame received by the first access point device.

[0567] In some embodiments, at least one of the following of the first transmission parameters is indicated by a first field in the first frame:

[0568] a first length, where the first length is the length of a first PPDU carrying the first target frame;

[0569] A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU;

[0570] A first number of symbols, where the first number of symbols is the number of LTF symbols in the first PPDU.

[0571] In some embodiments, the first field includes: a first subfield, a second subfield, and a third subfield;

[0572] The first length is indicated by the first subfield;

[0573] The first type is indicated by the second subfield;

[0574] The first number of symbols is indicated by the third subfield.

[0575] In some embodiments, the first field includes: a first subfield;

[0576] The first length is indicated by the first subfield;

[0577] The first type is the same as the type of the GI and LTF of the second PPDU carrying the second frame;

[0578] The first number of symbols is the same as the number of symbols of the LTF of the second PPDU.

[0579] In some embodiments, if the first target frame is a first confirmation frame, the second frame is the first data frame sent by the first access point device before the first confirmation frame; or

[0580] If the first target frame is a second data frame, the second frame is a second trigger frame of the first access point device, and the second trigger frame is used to trigger the sending of the second data frame.

[0581] In some embodiments, the target transmission parameters further include a second transmission parameter for scheduling transmission of a second target frame, the second target frame being sent by the first access point device to the first non-access point device.

[0582] In some embodiments, at least one of the following of the second transmission parameters is indicated by the first field:

[0583] a second length, where the second length is the length of a third PPDU carrying the second target frame;

[0584] A second type, where the second type is a type of a GI and an LTF of the third PPDU;

[0585] The second number of symbols is the number of LTF symbols in the third PPDU.

[0586] In some embodiments, the second target frame is a first trigger frame independent of the first data frame and used to trigger the first confirmation frame.

[0587] In some embodiments, the first field includes: a first subfield;

[0588] The first length and the second length are indicated by the first subfield.

[0589] In some embodiments, the first field includes: a fourth subfield;

[0590] The second length is indicated by the fourth subfield.

[0591] In some embodiments, the third PPDU is a non-HT PPDU or a non-HT duplicated PPDU.

[0592] In some embodiments, the first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0593] The second length is indicated by the fourth subfield;

[0594] The second type is indicated by the fifth subfield;

[0595] The second number of symbols is indicated by the sixth subfield.

[0596] In some embodiments, the second target frame is a second confirmation frame used to confirm the second data frame.

[0597] In some embodiments, the second length is the same as a length in a fourth PPDU carrying a second trigger frame, and the second trigger frame is used to trigger the second data frame;

[0598] The second type is the same as the type of the GI and LTF in the fourth PPDU;

[0599] The second number of symbols is the same as the number of symbols of the LTF in the fourth PPDU.

[0600] In some embodiments, the first field includes a fourth subfield, a fifth subfield, and a sixth subfield:

[0601] The second length is indicated by the fourth subfield;

[0602] The second type is indicated by the fifth subfield;

[0603] The second number of symbols is indicated by the sixth subfield.

[0604] In some embodiments, the first field further includes at least one of the following:

[0605] a seventh subfield indicating a third number of symbols, where the seventh number of symbols is the number of symbols in the SIGNAL field in the third PPDU;

[0606] An eighth subfield indicating the modulation and coding scheme of the signal segment.

[0607] In some embodiments, if the first frame is a multi-access point coordinated transmission trigger frame, the first field is located in one of the following:

[0608] The trigger-dependent public information subfield in the public information field;

[0609] The trigger-dependent user information subfield in the special user information field.

[0610] In some embodiments, if the first frame is a multi-user request to send a transmission status trigger frame, the first field is located in the special user information field, and the value of the AID in the special user information field is a set value.

[0611] In some embodiments, the first transmission parameter includes a first resource unit RU or multiple resource units MRU, the first RU or MRU is determined by the second field of the first frame, and the first RU is the RU or MRU used when the first target frame is transmitted.

[0612] In some embodiments, the first RU or MRU is: the RU or MRU indicated by the second field; or the RU or MRU allocated by the first access point device to the first non-access point device according to the RU or MRU indicated by the second field.

[0613] In some embodiments, the second transmission parameter includes: a second RU or MRU, the second RU or MRU is determined by the second field of the first frame, and the second RU or MRU is the RU or MRU used when the second target frame is transmitted.

[0614] In some embodiments, the second RU or MRU is the RU or MRU indicated by the second field.

[0615] In some embodiments, the second field is used to indicate a RU or MRU in conjunction with at least one of the following:

[0616] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0617] Extension of the bandwidth subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0618] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

[0619] In some embodiments, the second field is located in a variable user information field of the first frame.

[0620] In some embodiments, the first frame includes a third field, the third field being used to indicate a transmission parameter of one of the following:

[0621] If the first data frame sent by the first access point device carries a first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0622] If the first data frame does not carry the first confirmation frame and the first trigger frame, the first trigger frame is used to trigger the first confirmation frame;

[0623] A second data frame received by the first access point device.

[0624] In some embodiments, if the third field is used to indicate transmission parameters of the first confirmation frame and the first trigger frame, the third field is used to indicate the length of the PPDU carrying the first trigger frame, and the first trigger frame is carried on a non-HT PPDU or a non-HT duplicated PPDU.

[0625] In some embodiments, if the third field is used to indicate the transmission parameters of the second data frame, the transmission parameters of the second confirmation frame are the same as the transmission parameters of the second trigger frame, the second trigger frame is used to trigger the sending of the second data frame, and the second confirmation frame is used to confirm the second data frame.

[0626] In some embodiments, the third field includes:

[0627] A ninth subfield, where the ninth subfield is used to indicate the length of the fifth PPDU;

[0628] a tenth subfield, where the tenth subfield is used to indicate the type of the LTF in the fifth PPDU;

[0629] The eleventh subfield is used to indicate the number of LTF symbols in the fifth PPDU.

[0630] In some embodiments, the first frame further includes a fourth field, where the fourth field is used to indicate a third RU or an MRU, where the third RU or the MRU is used when transmitting one of the following:

[0631] If the first data frame carries the first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame;

[0632] If the first data frame does not carry the first confirmation frame and the first trigger frame, the first trigger frame is used to trigger the first confirmation frame;

[0633] The second data frame is a data frame sent by the first non-access point device to the first access point device.

[0634] In some embodiments, the fourth field is used to indicate the third RU or MRU in conjunction with at least one of the following:

[0635] The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame;

[0636] Extension of the bandwidth subfield in the special user information field of the multi-access point coordinated transmission trigger frame;

[0637] The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

[0638] Those skilled in the art should understand that the description related to the first access point device or the second access point device in the embodiments of the present application can be understood with reference to the description related to the transmission control method in the embodiments of the present application.

[0639] Figure 44 is a schematic structural diagram of a communication device 4400 provided in an embodiment of the present application. The communication device can be a first access point device or a second access point device. The communication device 4400 shown in Figure 44 includes a processor 4410, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0640] Optionally, as shown in FIG44 , the communication device 4400 may further include a memory 4420. The processor 4410 may call and execute a computer program from the memory 4420 to implement the method in the embodiment of the present application.

[0641] The memory 4420 may be a separate device independent of the processor 4410 or may be integrated into the processor 4410 .

[0642] Optionally, as shown in FIG44 , the communication device 4400 may further include a transceiver 4430 , and the processor 4410 may control the transceiver 4430 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

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

[0645] Optionally, the communication device 4400 may be specifically a second access point device in the embodiment of the present application, and the communication device 4400 may implement the corresponding processes implemented by the second access point device in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

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

[0647] Optionally, as shown in FIG45 , the chip 4500 may further include a memory 4520. The processor 4510 may call and execute a computer program from the memory 4520 to implement the method in the embodiment of the present application.

[0648] The memory 4520 may be a separate device independent of the processor 4510 or may be integrated into the processor 4510 .

[0649] Optionally, the chip 4500 may further include an input interface 4530. The processor 4510 may control the input interface 4530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0650] Optionally, the chip 4500 may further include an output interface 4540. The processor 4510 may control the output interface 4540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0651] Optionally, the chip may be applied to the first access point device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the first 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.

[0652] Optionally, the chip may be applied to the second access point device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the second 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.

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

[0654] FIG46 is a schematic block diagram of a communication system 4600 provided in an embodiment of the present application. As shown in FIG46 , the communication system 4600 includes a first access point device 4610 and a second access point device 4620 .

[0655] The first access point device 4610 may be used to implement the corresponding functions implemented by the first access point device in the above method, and the second access point device 4620 may be used to implement the corresponding functions implemented by the second access point device in the above method. For the sake of brevity, they are not described here in detail.

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

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

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

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

[0660] Optionally, the computer-readable storage medium may be applied to the first 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 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.

[0661] Optionally, the computer-readable storage medium may be applied to the second 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 second 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.

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

[0663] Optionally, the computer program product may be applied to the first 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 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.

[0664] Optionally, the computer program product may be applied to the second 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 second 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.

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

[0666] Optionally, the computer program may be applied to the first 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 first 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.

[0667] Optionally, the computer program may be applied to the second 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 second 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.

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

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

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

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

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

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

[0674] 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 access point device receives a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used for each access point device in at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

2. The method according to claim 1, wherein: The second access point device is an access point device that initiates multi-access point device collaboration.

3. The method according to claim 1 or 2, wherein: The first frame includes at least one of the following: Multiple access points coordinate transmission of trigger frames; Multiple users request to send-transmission opportunity sharing trigger frame.

4. The method according to any one of claims 1 to 3, wherein: The target transmission parameters include first transmission parameters for scheduling transmission of a first target frame, the first target frame being sent by a first non-access point device to the first access point device.

5. The method according to claim 4, wherein: The first target frame includes at least one of the following: A first confirmation frame, where the first confirmation frame is used to confirm a first data frame sent by the first access point device, where the first data frame carries a trigger frame or does not carry a trigger frame; The second data frame is a trigger-based data frame received by the first access point device.

6. The method according to claim 4 or 5, wherein: At least one of the following of the first transmission parameters is indicated by a first field in the first frame: A first length, where the first length is the length of a first PPDU carrying the first target frame; A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU; A first number of symbols, where the first number of symbols is the number of symbols of the LTF in the first PPDU.

7. The method according to claim 6, wherein: The first field includes: a first subfield, a second subfield, and a third subfield; The first length is indicated by the first subfield; The first type is indicated by the second subfield; The first number of symbols is indicated by the third subfield.

8. The method according to claim 6, wherein: The first field includes: a first subfield; The first length is indicated by the first subfield; The first type is the same as the type of the GI and LTF of the second PPDU carrying the second frame; The first number of symbols is the same as the number of symbols of the LTF of the second PPDU.

9. The method according to claim 8, wherein: If the first target frame is a first confirmation frame, the second frame is the first data frame sent by the first access point device before the first confirmation frame; or, If the first target frame is a second data frame, the second frame is a second trigger frame of the first access point device, and the second trigger frame is used to trigger the sending of the second data frame.

10. The method according to any one of claims 6 to 9, wherein: The target transmission parameters also include a second transmission parameter for scheduling transmission of a second target frame, the second target frame being sent by the first access point device to the first non-access point device.

11. The method according to claim 10, wherein: At least one of the following of the second transmission parameters is indicated by the first field: A second length, where the second length is the length of a third PPDU carrying the second target frame; A second type, where the second type is a type of a GI and an LTF of the third PPDU; The second number of symbols is the number of symbols of the LTF in the third PPDU.

12. The method according to claim 11, wherein: The second target frame is a first trigger frame independent of the first data frame and used to trigger the first confirmation frame.

13. The method according to claim 12, wherein: The first field includes: a first subfield; The first length and the second length are indicated by the first subfield.

14. The method according to claim 13, wherein: The first field includes: a fourth subfield; The second length is indicated by the fourth subfield.

15. The method according to claim 13 or 14, wherein: The third PPDU is a non-HT PPDU or a non-HT duplicated PPDU.

16. The method according to claim 12, wherein: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield: The second length is indicated by the fourth subfield; The second type is indicated by the fifth subfield; The second number of symbols is indicated by the sixth subfield.

17. The method according to claim 11, wherein: The second target frame is a second confirmation frame used for confirming the second data frame.

18. The method according to claim 17, wherein: The second length is the same as a length in a fourth PPDU carrying a second trigger frame, and the second trigger frame is used to trigger the second data frame; The second type is the same as the type of the GI and LTF in the fourth PPDU; The second number of symbols is the same as the number of symbols of the LTF in the fourth PPDU.

19. The method according to claim 17, wherein: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield: The second length is indicated by the fourth subfield; The second type is indicated by the fifth subfield; The second number of symbols is indicated by the sixth subfield.

20. The method according to claim 16 or 19, wherein: The first field also includes at least one of the following: a seventh subfield indicating a third number of symbols, the seventh number of symbols being the number of symbols of a SIGNAL field in the third PPDU; An eighth subfield indicating a modulation and coding scheme of the signal segment.

21. The method according to any one of claims 6 to 20, wherein: If the first frame is a multi-access point coordinated transmission trigger frame, the first field is located in one of the following: The trigger-dependent common information subfield in the common information field; The trigger-dependent user information subfield in the special user information field.

22. The method according to any one of claims 6 to 20, wherein: If the first frame is a transmission status trigger frame requested by multiple users to send, the first field is located in the special user information field, and the value of the AID in the special user information field is a set value.

23. The method according to any one of claims 4 to 22, wherein: The first transmission parameter includes a first resource unit RU or multiple resource units MRU, the first RU or MRU is determined by the second field of the first frame, and the first RU is the RU or MRU used when the first target frame is transmitted.

24. The method according to claim 23, wherein: The first RU or MRU is: The second field indicates the RU or MRU; or, The first access point device allocates an RU or MRU to the first non-access point device according to the RU or MRU indicated by the second field.

25. The method according to any one of claims 10 to 20, wherein: The second transmission parameter includes: a second RU or MRU, the second RU or MRU is determined by the second field of the first frame, and the second RU or MRU is the RU or MRU used when the second target frame is transmitted.

26. The method according to claim 25, wherein: The second RU or MRU is the RU or MRU indicated by the second field.

27. The method according to any one of claims 23 to 26, wherein: The second field is used to indicate RU or MRU in conjunction with at least one of the following: The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame; Extension of bandwidth subfield in special user information field of multi-access point coordinated transmission trigger frame; The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

28. The method according to any one of claims 23 to 27, wherein: The second field is located in the variable user information field of the first frame.

29. The method according to any one of claims 1 to 3, wherein: The first frame includes a third field, and the third field is used to indicate one of the following transmission parameters: If the first data frame sent by the first access point device carries a first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame; If the first data frame does not carry the first confirmation frame and the first trigger frame in the case of a trigger frame, the first trigger frame is used to trigger the first confirmation frame; The second data frame received by the first access point device.

30. The method of claim 29, wherein: If the third field is used to indicate transmission parameters of the first confirmation frame and the first trigger frame, the third field is used to indicate the length of the PPDU carrying the first trigger frame, and the first trigger frame is carried on a non-HT PPDU or a non-HT duplicated PPDU.

31. The method of claim 29, wherein: If the third field is used to indicate the transmission parameters of the second data frame, the transmission parameters of the second confirmation frame are the same as the transmission parameters of the second trigger frame, the second trigger frame is used to trigger the sending of the second data frame, and the second confirmation frame is used to confirm the second data frame.

32. The method according to any one of claims 29 to 31, wherein: The third field includes: A ninth subfield, where the ninth subfield is used to indicate the length of the fifth PPDU; a tenth subfield, the tenth subfield being used to indicate a type of LTF in the fifth PPDU; The eleventh subfield is used to indicate the number of LTF symbols in the fifth PPDU.

33. The method according to any one of claims 29 to 31, wherein: The first frame further includes a fourth field, where the fourth field is used to indicate a third RU or MRU, where the third RU or MRU is used when one of the following is transmitted: If the first data frame carries the first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame; If the first data frame does not carry the first confirmation frame and the first trigger frame in the case of a trigger frame, the first trigger frame is used to trigger the first confirmation frame; The second data frame is a data frame sent by the first non-access point device to the first access point device.

34. The method of claim 33, wherein: The fourth field is used to indicate the third RU or MRU in conjunction with at least one of the following: The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame; Extension of bandwidth subfield in special user information field of multi-access point coordinated transmission trigger frame; The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

35. A transmission control method, the method comprising: The second access point device sends a first frame to the first access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used for each access point device in at least one access point device participating in the collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

36. The method of claim 35, wherein: The second access point device is an access point device that initiates multi-access point device collaboration.

37. The method of claim 365 or 36, wherein: The first frame includes at least one of the following: Multiple access points coordinate transmission of trigger frames; Multiple users request to send-transmission opportunity sharing trigger frame.

38. A method according to any one of claims 35 to 37, wherein: The target transmission parameters include first transmission parameters for scheduling transmission of a first target frame, the first target frame being sent by a first non-access point device to the first access point device.

39. The method of claim 38, wherein: The first target frame includes at least one of the following: A first confirmation frame, where the first confirmation frame is used to confirm a first data frame sent by the first access point device, where the first data frame carries a trigger frame or does not carry a trigger frame; The second data frame is a trigger-based data frame received by the first access point device.

40. The method according to claim 38 or 39, wherein: At least one of the following of the first transmission parameters is indicated by a first field in the first frame: A first length, where the first length is the length of a first PPDU carrying the first target frame; A first type, where the first type is a type of a guard interval GI and a long training field LTF of the first PPDU; A first number of symbols, where the first number of symbols is the number of symbols of the LTF in the first PPDU.

41. The method of claim 40, wherein: The first field includes: a first subfield, a second subfield, and a third subfield; The first length is indicated by the first subfield; The first type is indicated by the second subfield; The first number of symbols is indicated by the third subfield.

42. The method of claim 40, wherein: The first field includes: a first subfield; The first length is indicated by the first subfield; The first type is the same as the type of the GI and LTF of the second PPDU carrying the second frame; The first number of symbols is the same as the number of symbols of the LTF of the second PPDU.

43. The method of claim 42, wherein: If the first target frame is a first confirmation frame, the second frame is the first data frame sent by the first access point device before the first confirmation frame; or, If the first target frame is a second data frame, the second frame is a second trigger frame of the first access point device, and the second trigger frame is used to trigger the sending of the second data frame.

44. The method according to any one of claims 40 to 43, wherein: The target transmission parameters also include a second transmission parameter for scheduling transmission of a second target frame, the second target frame being sent by the first access point device to the first non-access point device.

45. The method of claim 44, wherein: At least one of the following of the second transmission parameters is indicated by the first field: A second length, where the second length is the length of a third PPDU carrying the second target frame; A second type, where the second type is a type of a GI and an LTF of the third PPDU; The second number of symbols is the number of symbols of the LTF in the third PPDU.

46. ​​The method of claim 45, wherein: The second target frame is a first trigger frame independent of the first data frame and used to trigger the first confirmation frame.

47. The method of claim 46, wherein: The first field includes: a first subfield; The first length and the second length are indicated by the first subfield.

48. The method of claim 47, wherein: The first field includes: a fourth subfield; The second length is indicated by the fourth subfield.

49. The method according to claim 47 or 48, wherein: The third PPDU is a non-HT PPDU or a non-HT repeatedly transmitted PPDU.

50. The method of claim 46, wherein: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield: The second length is indicated by the fourth subfield; The second type is indicated by the fifth subfield; The second number of symbols is indicated by the sixth subfield.

51. The method of claim 45, wherein: The second target frame is a second confirmation frame used for confirming the second data frame.

52. The method of claim 51, wherein: The second length is the same as a length in a fourth PPDU carrying a second trigger frame, and the second trigger frame is used to trigger the second data frame; The second type is the same as the type of the GI and LTF in the fourth PPDU; The second number of symbols is the same as the number of symbols of the LTF in the fourth PPDU.

53. The method of claim 51, wherein: The first field includes a fourth subfield, a fifth subfield, and a sixth subfield: The second length is indicated by the fourth subfield; The second type is indicated by the fifth subfield; The second number of symbols is indicated by the sixth subfield.

54. The method of claim 50 or 53, wherein: The first field also includes at least one of the following: a seventh subfield indicating a third number of symbols, the seventh number of symbols being the number of symbols of a SIGNAL field in the third PPDU; An eighth subfield indicating a modulation and coding scheme of the signal segment.

55. The method according to any one of claims 40 to 54, wherein: If the first frame is a multi-access point coordinated transmission trigger frame, the first field is located in one of the following: The trigger-dependent common information subfield in the common information field; The trigger-dependent user information subfield in the special user information field.

56. The method according to any one of claims 40 to 54, wherein: If the first frame is a transmission status trigger frame requested by multiple users to send, the first field is located in the special user information field, and the value of the AID in the special user information field is a set value.

57. A method according to any one of claims 38 to 56, wherein: The first transmission parameter includes a first resource unit RU or multiple resource units MRU, the first RU or MRU is determined by the second field of the first frame, and the first RU is the RU or MRU used when the first target frame is transmitted.

58. The method of claim 57, wherein: The first RU or MRU is: The second field indicates the RU or MRU; or, The first access point device allocates an RU or MRU to the first non-access point device according to the RU or MRU indicated by the second field.

59. The method according to any one of claims 44 to 54, wherein: The second transmission parameter includes: a second RU or MRU, the second RU or MRU is determined by the second field of the first frame, and the second RU or MRU is the RU or MRU used when the second target frame is transmitted.

60. The method of claim 59, wherein: The second RU or MRU is the RU or MRU indicated by the second field.

61. The method according to any one of claims 57 to 60, wherein: The second field is used to indicate RU or MRU in conjunction with at least one of the following: The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame; Extension of bandwidth subfield in special user information field of multi-access point coordinated transmission trigger frame; The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

62. The method according to any one of claims 57 to 61, wherein: The second field is located in the variable user information field of the first frame.

63. The method according to any one of claims 35 to 37, wherein: The first frame includes a third field, and the third field is used to indicate one of the following transmission parameters: If the first data frame sent by the first access point device carries a first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame; If the first data frame does not carry the first confirmation frame and the first trigger frame in the case of a trigger frame, the first trigger frame is used to trigger the first confirmation frame; The second data frame received by the first access point device.

64. The method of claim 63, wherein: If the third field is used to indicate transmission parameters of the first confirmation frame and the first trigger frame, the third field is used to indicate the length of the PPDU carrying the first trigger frame, and the first trigger frame is carried on a non-HT PPDU or a non-HT duplicated PPDU.

65. The method of claim 63, wherein: If the third field is used to indicate the transmission parameters of the second data frame, the transmission parameters of the second confirmation frame are the same as the transmission parameters of the second trigger frame, the second trigger frame is used to trigger the sending of the second data frame, and the second confirmation frame is used to confirm the second data frame.

66. A method according to any one of claims 63 to 65, wherein: The third field includes: A ninth subfield, where the ninth subfield is used to indicate the length of the fifth PPDU; a tenth subfield, the tenth subfield being used to indicate a type of LTF in the fifth PPDU; The eleventh subfield is used to indicate the number of LTF symbols in the fifth PPDU.

67. The method according to any one of claims 63 to 65, wherein: The first frame further includes a fourth field, the fourth field being used to determine a third RU or MRU, the third RU or MRU being used for the RU or MRU used when one of the following is transmitted: If the first data frame carries the first confirmation frame in the case of a trigger frame, the first confirmation frame is used to confirm the first data frame; If the first data frame does not carry the first confirmation frame and the first trigger frame in the case of a trigger frame, the first trigger frame is used to trigger the first confirmation frame; The second data frame is a data frame sent by the first non-access point device to the first access point device.

68. The method of claim 67, wherein: The fourth field is used to indicate the third RU or MRU in conjunction with at least one of the following: The bandwidth subfield in the common information field of the multi-access point coordinated transmission trigger frame; Extension of bandwidth subfield in special user information field of multi-access point coordinated transmission trigger frame; The PS160 subfield in the variable user information field of the multi-access point coordinated transmission trigger frame.

69. A first access point device, comprising: The first communication unit is configured to receive a first frame sent by a second access point device, where the first frame is used to indicate a target transmission parameter, where the target transmission parameter is used for each access point device in at least one access point device participating in collaborative transmission to schedule transmission of at least one target frame, where the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

70. A second access point device, comprising: The second communication unit is configured to send a first frame to the first access point device, where the first frame is used to indicate a target transmission parameter, and the target transmission parameter is used for each access point device in at least one access point device participating in the collaborative transmission to schedule the transmission of at least one target frame, the at least one access point device includes the first non-access point device, and the target frame is located after a first frame transmitted between the first access point device and the first non-access point device.

71. 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 1 to 34, or executes the method according to any one of claims 35 to 68.

72. 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 34, or executes a method as claimed in any one of claims 35 to 68.

73. 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 34, or the method according to any one of claims 35 to 68.

74. A computer program product, comprising computer program instructions, wherein the execution of the computer program instructions causes a computer to perform the method according to any one of claims 1 to 34, or the method according to any one of claims 35 to 68.

75. 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 34, or the method according to any one of claims 35 to 68.

Images