Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first AP sends a first frame to a second AP, wherein the first frame is used for indicating a transmission parameter of a first PPDU sent by a first non-AP STA to the second AP, the first non-AP STA is associated with the second AP, and the first PPDU is sent during coordination between the first AP and the second AP. For non-AP STAs associated with different APs, transmission parameters of PPDUs sent by these non-AP STAs may all be indicated by the first frame. Therefore, the first AP can control, on the basis of the first frame, the transmission parameters of the PPDUs sent by the non-AP STAs during coordination between multiple APs, thereby avoiding conflicts or anomalies between the PPDUs sent by the multiple non-AP STAs associated with the different APs, so that the non-AP STAs associated with the different APs can normally send the PPDUs.

Description

Wireless communication methods and communication devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method and communication device. Background Technology

[0002] With the development of technology, some communication standards (such as IEEE 802.11UHR (Wi-Fi 8)) have proposed multi-access point (M-AP) cooperation solutions. M-AP cooperation allows multiple APs to share transmission resources, thereby improving resource utilization. During the cooperation process, non-AP stations (non-AP STAs) can exchange physical layer protocol data units (PPDUs) with their associated APs. Summary of the Invention

[0003] This application provides a wireless communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a wireless communication method is provided, the method comprising: a first AP sending a first frame to a second AP; wherein the first frame is used to indicate transmission parameters of a first non-AP STA sending a first PPDU to the second AP, the first non-AP STA being associated with the second AP, and the first PPDU being sent during cooperation between the first AP and the second AP.

[0005] In a second aspect, a wireless communication method is provided, the method comprising: a second AP receiving a first frame sent by a first AP; wherein the first frame is used to indicate transmission parameters of a first non-AP STA sent to the second AP by a first PPDU, the first non-AP STA being associated with the second AP, and the first PPDU being sent during cooperation between the first AP and the second AP.

[0006] Thirdly, a communication device is provided, which is an access point (AP). The communication device includes: a transmitting unit for transmitting a first frame to a second AP; wherein the first frame is used to indicate the transmission parameters of a first non-AP STA transmitted to the second AP via a first PPDU, the first non-AP STA being associated with the second AP, and the first PPDU being transmitted during cooperation between the first AP and the second AP.

[0007] Fourthly, a communication device is provided, which is a second AP. The communication device includes: a receiving unit for receiving a first frame sent by a first AP; wherein the first frame is used to indicate the transmission parameters of a first PPDU sent by a first non-AP STA to the second AP, the first non-AP STA being associated with the second AP, and the first PPDU being sent during the cooperation between the first AP and the second AP.

[0008] Fifthly, a communication device is provided, including a processor and a memory, the memory for storing one or more computer programs, the processor for calling the computer programs in the memory to enable some or all of the steps of the methods described in the preceding aspects of the communication device.

[0009] Sixthly, embodiments of this application provide a communication system that includes the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0010] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0011] Eighthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0012] Ninthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0013] For non-AP STAs associated with different APs, the transmission parameters of the PPDUs sent by these non-AP STAs can all be indicated by the first frame. Therefore, the first AP can control or schedule the transmission parameters of the PPDUs sent by non-AP STAs during the multi-AP cooperation process based on the first frame, thereby avoiding conflicts or anomalies between the PPDUs sent by multiple non-AP STAs associated with different APs, and ensuring that non-AP STAs associated with different APs can send PPDUs normally. Attached Figure Description

[0014] Figure 1 is a schematic diagram of the wireless communication system used in the embodiments of this application.

[0015] Figure 2 is an example diagram of a trigger frame format.

[0016] Figure 3A is an example of the format of the public information field for the EHT variant.

[0017] Figure 3B shows an example of the format for special user information fields.

[0018] Figure 3C is an example of the format of a user information field in an EHT variant.

[0019] Figure 4 is an example of the format of the EHT variant user information field in a multi-user request to send TXOP sharing (MU-RTS TXS) trigger frame.

[0020] Figure 5 is an example of the format of the control information subfield in the Triggered Response Scheduling (TRS) control subfield.

[0021] Figure 6 is an example diagram of the confirmation process.

[0022] Figure 7 shows an example of the AP candidate set.

[0023] Figure 8 is an example diagram of a coordinated spatial reuse (C-SR or Co-SR) transport process.

[0024] Figure 9 is an example diagram of a coordinated beamforming (C-BF or Co-BF) transmission process.

[0025] Figure 10 is an example diagram of another Co-BF transfer process.

[0026] Figure 11 is an example diagram of another Co-BF transfer process.

[0027] Figure 12 is a format example of the common field in the UHR-SIG field of the Co-BF PPDU.

[0028] Figure 13 is an example diagram of the non-orthogonal frequency division multiple access (non-OFDMA) MU-MIMO UHR-SIG format.

[0029] Figure 14 is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0030] Figure 15A is an example diagram of a UHR MU PPDU format.

[0031] Figure 15B is an example diagram of a UHR TB PPDU format.

[0032] Figure 16 is an example diagram of a communication process provided in an embodiment of this application.

[0033] Figure 17 is an example diagram of another communication process provided in an embodiment of this application.

[0034] Figure 18 is a format example diagram of a user information field provided in an embodiment of this application.

[0035] Figure 19 is an example diagram of another user information field format provided in an embodiment of this application.

[0036] Figure 20 is an example diagram of another communication process provided in an embodiment of this application.

[0037] Figure 21 is an example diagram of another communication process provided in an embodiment of this application.

[0038] Figure 22 is a format example diagram of a trigger scheduling field provided in an embodiment of this application.

[0039] Figure 23 is an example diagram of another trigger scheduling field format provided in an embodiment of this application.

[0040] Figure 24 is a schematic structural diagram of a communication device 2400 provided in an embodiment of this application.

[0041] Figure 25 is a schematic structural diagram of a communication device 2500 provided in an embodiment of this application.

[0042] Figure 26 is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0044] Communication system

[0045] The technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), high-performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For example, the technical solutions provided in this application can be applied to communication systems using the 802.11 standard. Exemplarily, the 802.11 standard includes, but is not limited to, the 802.11ax standard, the 802.11be standard, the 802.11bn standard, and the next-generation 802.11 standard (post802.11bn).

[0046] Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application. Referring to Figure 1, the communication devices in the communication system 100 may include access points (APs) 111 and 112, as well as stations (STAs) 121 and 122. STA 121 can access the network through AP 111, and STA 122 can access the network through AP 112.

[0047] In some implementations, a STA can establish an association with one or more APs, after which the associated STAs and APs can communicate with each other. As shown in Figure 1, AP 111 and STA 121 can communicate after establishing an association, and AP 112 and STA 122 can communicate after establishing an association.

[0048] In some implementations, the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA. Here, a peer STA can refer to a device that communicates with the STA's counterpart. For example, a peer STA may be an AP or a non-AP STA.

[0049] It should be understood that Figure 1 exemplarily shows two AP STAs and two non-AP STAs. The communication system 100 may also include more AP STAs, or the communication system 100 may include other numbers of non-AP STAs. This application embodiment does not limit this.

[0050] In addition, the above-mentioned communication system can be applied to scenarios involving multi-device collaboration, such as multi-AP (multi-access points) collaboration or multi-site collaboration.

[0051] In the embodiments of this application, the names of AP and / or STA are not limited. In some scenarios, AP can also be called AP STA, that is, in a sense, AP is also a type of STA. In other scenarios, STA can be called non-AP STA.

[0052] In some scenarios, the aforementioned communication equipment can also be a "multi-link device (MLD)," meaning a device that can communicate through multiple communication links. These multiple communication links can include communication links in different frequency bands, such as millimeter-wave bands and / or low-frequency bands. Typically, if the multi-link device is an access point (AP), it can also be called an "AP MLD." If the multi-link device is a non-AP STA, it can also be called a "non-AP MLD."

[0053] In this application embodiment, the AP can be a device in a wireless network. The AP can be a communication server, router, switch, bridge, or other communication entity. Alternatively, the AP can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP can also be a chip, circuit, or processing system within these various forms of devices, thereby implementing the methods and functions of this application embodiment. APs can be applied in various scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.).

[0054] In some implementations, the role of the STA in the communication system is not absolute; in some scenarios, the STA can act as an AP. For example, in a scenario where a mobile phone connects to a router, the mobile phone can be a non-AP STA, while when the mobile phone acts as a hotspot for other mobile phones, it takes on the role of an AP.

[0055] In the embodiments of this application, the STA can be a device with wireless transceiver capabilities, such as one that supports the 802.11 series of protocols and can communicate with the AP or other STAs. For example, an STA is any user communication device that allows users to communicate with the AP and thus with the WLAN. STAs include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0056] In this application embodiment, the STA can also be a device that provides voice / data / image connectivity to the user, such as a handheld device, vehicle device, home device, home appliance, gaming device, etc., with wireless connection function or equipped with a wireless communication module. Examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, drones or aerial photography equipment, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, 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 a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN) can also be televisions, refrigerators, washing machines, kitchen appliances, door locks, fish tanks, robot vacuum cleaners, game consoles, cameras / camcorders, etc. with wireless connectivity, but this application embodiment is not limited to these.

[0057] By way of example and not limitation, in this embodiment, the STA can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Examples include smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require cooperation with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0058] Furthermore, in this embodiment, the STA can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network for human-machine interconnection and object-to-object interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).

[0059] Furthermore, in this embodiment, the STA can be a device in a vehicle-to-everything (V2X) system. The communication methods in a V2X system are collectively referred to as V2X (where X represents anything). For example, V2X communication includes: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0060] In addition, in the embodiments of this application, the STA may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal devices), receiving control information and downlink data from the AP, and sending electromagnetic waves to transmit data to the AP.

[0061] In addition, the AP in this application embodiment can be a device for communicating with the STA. The AP can be a network device in a wireless local area network, and the AP can be used to communicate with the STA through the wireless local area network.

[0062] From the perspective of the communication standards supported by the AP, in some implementations, the AP can be a device that supports the 802.11be standard. The AP can also be a device that supports various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0063] From the perspective of the communication standards supported by the STA, in some implementations, non-AP STAs can support the 802.11be standard. Non-AP STAs can also support various current and future 802.11 family of wireless local area networks (WLAN) standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0064] In this application embodiment, the frequency bands supported by WLAN technology are not limited. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 45GHz, 60GHz).

[0065] It should be understood that the specific forms of STA and AP are not specifically limited in the embodiments of this application, and are merely illustrative examples.

[0066] Trigger Frame

[0067] In some communication standards (such as IEEE 802.11), trigger-based (TB) PPDU transmission can be implemented based on trigger frames. For example, a non-MU-RTS trigger frame allocates resources and requests the transmission of one or more TB PPDUs. The trigger frame may also carry additional information required for the STA to send an HE TB PPDU, EHT TB PPDU, Non-HT PPDU, or Non-HT Duplicate PPDU. For instance, when performing an uplink TB PPDU transmission, the AP can first send a trigger frame, and each non-AP STA can prepare and transmit a TB PPDU based on the parameters indicated by the received trigger frame.

[0068] Figure 2 is an example diagram of the trigger frame format.

[0069] As shown in Figure 2, the trigger frame may include one or more of the following fields: frame control, duration, receiver address (RA), transmission address (TA), common info, user info list, padding, and frame check sequence (FCS).

[0070] The frame control field can carry control information such as frame type.

[0071] The duration field can indicate the remaining transmission opportunity (TXOP) duration.

[0072] The RA field can indicate the site address or broadcast address that received the trigger frame.

[0073] The TA field can indicate the address of the site that sent the trigger frame or the basic service set identifier (BSSID).

[0074] The following provides examples of the public information field, user information list field, and populate fields. It should be noted that the examples used below, specifically the EHT trigger frame, are for illustrative purposes and are not intended to limit this application. This application can also be applied to other versions of trigger frames. For example, the public information field and user information list field in the UHR trigger frame can have the same or similar fields as those in the EHT trigger frame; simply replace "EHT" with "UHR" in the fields. Alternatively, the UHR trigger frame may include fields not described below.

[0075] 1) Public Information Fields

[0076] The common information field primarily carries common information for each STA. The common information field can have different variations. For example, a common information field can be interpreted as an HE variant common Info field or an EHT variant common Info field.

[0077] Figure 3A is an example diagram of the format of the public information field of the EHT variant.

[0078] As shown in Figure 3A, the EHT variant common information field may include one or more of the following fields: trigger type, uplink length (UL length), more trigger frames (TF), carrier sensing required (CS), uplink bandwidth (UL BW), number of HE / EHT / UHR-LTF symbols and midamble periodicity, number of HE / EHT-LTF symbols, reserved, low-density parity check extra symbol segment (LDPC), AP transmit power (TX power), Pre-FEX padding factor (Pre-FEC padding factor), PE disambiguation, uplink spatial reuse (UL spatial reuse), HE / EHT P160, special user info field flag, EHT reserved, and trigger dependency common information.

[0079] The trigger type subfield can be used to indicate a variant of the trigger frame. Table 1 shows an example of the encoding of the trigger type subfield.

[0080] Table 1

[0081] 2) User information list fields

[0082] The user information list field consists of one or more user information fields. In some types of trigger frames (such as EHT trigger frames), the user information list field includes one or more special user information fields and / or multiple variant user information fields. These variant user information fields can be, for example, HE variant user information fields, EHT variant user information fields, UHR variant user information fields, etc.

[0083] The following sections explain the special user information fields and the variant user information fields respectively.

[0084] A Special User Information field is a user information field that does not carry user-specific information but carries extended public information not provided in the public information field. If a Special User Information field exists, it is located after the public information field of the triggering frame and carries information from the U-SIG field of the requested EHT TB PPDU.

[0085] Figure 3B shows an example of the format of a special user information field. As shown in Figure 3B, the special user information field may include one or more of the following fields: AID12, PHY version identifier, UL BW extension, EHT spatial reuse 1, EHT spatial reuse 2, U-SIG disregard and validate, trigger dependent user Info, and reserved.

[0086] The AID12 subfield of a special user information field can be set to 2007 to identify that this user information field is a special user information field.

[0087] The Physical Layer Version Identifier field indicates the physical layer (PHY) version of the requested TB PPDU (non-HE TB PPDU). For EHT, the Physical Layer Version Identifier field is set to 0. Values ​​between 1 and 7 are reserved.

[0088] The Uplink Bandwidth Extension field, together with the UL BW subfield in the Public Information field, indicates the bandwidth of the requested TB PPDU.

[0089] The EHT Spatial Reuse 1 field carries the value to be included in the corresponding Spatial Reuse 1 subfield of the U-SIG field of the EHT TB PPDU.

[0090] The EHT Spatial Reuse 2 field carries the value to be included in the corresponding Spatial Reuse 2 subfield of the U-SIG field of the EHT TB PPDU.

[0091] The U-SIG ignore and validate fields carry the values ​​from the ignore and validate subfields to be included in the U-SIG field of the requested EHT TB PPDU.

[0092] Figure 3C is an example of the format of a user information field in an EHT variant.

[0093] As shown in Figure 3C, the EHT variant user information field may include one or more of the following: Association Identifier 12 (AID12), RU allocation, UL FEC coding type, UL EHT modulation and coding scheme (UL EHT-MCS), SS allocation / RA-RU information, UL target receive power, PS160, trigger-dependent user information, and reserved. These will be explained in detail below.

[0094] The AID12 field is used to indicate the AID of an associated site or a non-associated site.

[0095] The UL BW subfield in the RU allocation field and the public information field, the UL BW extended subfield in the special user information field, and the PS160 subfield in the EHT variant user information field together identify the size and location of the RU or MRU.

[0096] The UL FEC Encoding Type field indicates the encoding type of the requested EHT TB PPDU. A UL FEC Encoding Type subfield set to 0 indicates BCC, and a set to 1 indicates LDPC.

[0097] The UL EHT-MCS field indicates the EHT-MCS for the requested EHT TB PPDU.

[0098] As mentioned above, there are many variations of trigger frames. Examples of some of these variations are given below.

[0099] (1) MU-RTS trigger frame

[0100] The Trigger Dependent Common Info subfield and Trigger Dependent User Info subfield are not present in the MU-RTS Trigger frame.

[0101] The following subfields in the Common Info field are reserved: Uplink Length, GI and HE-LTF Type, MU-MIMO HE-LTF Mode, Number of HE-LTF Symbols and Midamble Periodicity, UL STBC, LDPC Extra Symbol Segment, AP Transmit Power, Pre-FEC Padding Factor, PE Disambiguity, UL Spatial Reuse, Doppler Effect, and UL HE-SIG-A2 Reserved subfields.

[0102] The UL HE-MCS, UL FEC Coding Type, UL DCM, SS Allocation / RA-RU Information, and UL Target Receive Power fields in the User Info field are reserved.

[0103] MU-RTS TXS

[0104] If the TXS Mode subfield in the Common Info field of a MU-RTS frame transmitted by an EHT AP is set to a nonzero value, the frame indicates that time is allocated within an obtained TXOP to an associated non-AP EHT STA for the sequential transmission of one or more non-TB PPDUs; otherwise, the subfield is set to 0.

[0105] The encoding definition of the TXS mode subfield can be found in Table 2.

[0106] Table 2

[0107] A MU-RTS trigger frame that sets the TXS Mode subfield to a non-zero value is called a MU-RTS TXS trigger frame.

[0108] In a MU-RTS TXS trigger frame with EHT variant common information, the EHT variant user information field can be defined as shown in Figure 4.

[0109] In MU-RTS frames that are not MU-RTS TXS trigger frames, the UL EHT-MCS, UL FEC Coding Type, SS Allocation, and UL Target Receive Power fields in the EHT variant User Info field are reserved.

[0110] BSRP trigger frame

[0111] The Trigger Dependent Common Info subfield and Trigger Dependent User Info subfield are not present in the BSRP Trigger frame.

[0112] TRS Control Subfield

[0113] The TRS control subfield is present in the frame header. The control information subfield within the TRS control subfield contains TRS information, which is used to request a TB PPDU. For example, the TRS information can be used to request the transmission of an HE TB PPDU after an HE MU PPDU, HE SU PPDU, or HE ER SU PPDU carrying this control subfield, or the TRS information can be used to request the transmission of an EHT TB PPDU after an EHT MU PPDU carrying this control subfield.

[0114] Figure 5 is an example of the format of the control information subfield in the TRS control subfield. As shown in Figure 5, the control information subfield in the TRS control subfield may include one or more of the following fields: uplink data symbols (UL data symbols), RU allocation, AP transmit power (AP Tx power), uplink target receive power (UL target receive power), and uplink modulation and coding scheme (UL MCS).

[0115] The following describes the TXVECTOR parameters for the EHT TB PPDU response to the TRS Control subfield.

[0116] For non-AP STAs sending EHT TB PPDUs, the TXVECTOR parameter can be set as described below. This EHT TB PPDU is a request EHT PPDU in response to a frame containing a TRS control subfield.

[0117] The RU allocation (RU_ALLOCATION) parameter is set to the value represented by the RU allocation subfield and PS160 subfield in the TRS control subfield, which is determined based on the RU allocation in the request PPDU (soliciting PPDU) in Table 1.

[0118] The channel bandwidth (CH_BANDWIDTH) parameter is set to the value of the CH_BANDWIDTH parameter of the RXVECTOR request for the PPDU.

[0119] Acknowledgment procedure for DL ​​MU PPDU

[0120] When a non-AP STA receives a DL MU PPDU containing a QoS data frame with a HETP Ack acknowledgment policy, a QoS null frame, a MU-BAR trigger frame, a GCR MU-BAR trigger frame, or a management frame requesting acknowledgment, the non-AP STA should send an immediate response based on the scheduling information in the trigger frame or the TRS control subfield. If no basic trigger frame or frame carrying the TRS control subfield is received, the non-AP STA should not respond.

[0121] An AP can use a MU-BAR trigger frame or a GCR MU-BAR trigger frame to request acknowledgment (Ack) frames (i.e., block Ack, BA frames) from multiple non-AP STAs. Prior to this, the AP may have sent QoS data frames with a block acknowledgment policy to these non-AP STAs, or the AP may have sent QoS data frames with a HETP Ack acknowledgment policy in a MU PPDU but did not receive immediate acknowledgment frames from these non-AP STAs.

[0122] Figure 6 is an example diagram of the confirmation process for DL ​​MU PPDU.

[0123] As shown in Figure 6, the DL MU PPDU includes multiple A-MPDUs with trigger frames. After the MU PPDU, SIFS and BA frames are transmitted in the UL via OFDMA.

[0124] Multi-AP cooperative transmission

[0125] With the development of technology, some communication standards (such as IEEE 802.11UHR (Wi-Fi 8)) have proposed multi-AP cooperation technology solutions. Multi-AP cooperation allows multiple APs to share transmission resources, thereby improving the utilization rate of transmission resources.

[0126] The following explains some of the terminology used in multi-AP collaboration.

[0127] The AP candidate set can refer to the set of APs that can initiate or participate in multi-AP collaboration.

[0128] A sharing AP or initiating AP can refer to an AP that obtains a TXOP and initiates multi-AP collaboration. At least one AP in a candidate set can become a sharing AP.

[0129] A shared AP or a responding AP can participate in multi-AP collaboration initiated by a shared AP in the same set of AP candidates.

[0130] Multi-AP collaboration can be divided into a multi-AP collaboration preparation phase and a multi-AP collaboration communication phase (or multi-AP collaboration transmission phase). These will be explained separately below.

[0131] During the multi-AP collaboration preparation phase, the sharing AP obtains a TXOP and initiates multi-AP collaboration. The sharing AP can send query frames to one or more APs in the same AP candidate set to inquire about each AP's intention to participate in multi-AP collaboration. One or more APs will respond with a notification frame to inform the sharing AP whether they intend to participate in multi-AP collaboration. If an AP intends to participate in multi-AP collaboration, that AP becomes the shared AP in the multi-AP collaboration.

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

[0133] Figure 7 shows an example of an AP candidate set. The AP candidate set shown in Figure 7 contains three APs: AP1, AP2, and AP3. For example, AP1 can acquire a TXOP as a shared AP and initiate multi-AP cooperation; AP2 and AP3 can participate in multi-AP cooperation as shared APs. AP1, AP2, and AP3 can participate in multi-AP cooperation within a TXOP. As another example, AP2 can acquire a TXOP and initiate multi-AP cooperation as a shared AP; AP1 and AP3 can participate in multi-AP cooperation as shared APs. Within a TXOP, AP1 and AP3 may participate in multi-AP cooperative transmission, but AP2 may not.

[0134] Multi-AP transmission modes can include: Coordinated Time Division Multiple Access (C-TDMA), Coordinated Beamforming (C-BF or Co-BF), Coordinated Spatial Reuse (C-SR or Co-SR), Joint Transmission, and Coordinated Orthogonal Frequency Division Multiple Access (C-OFDMA). Co-BF and Co-SR will be explained below as examples.

[0135] Co-SR can refer to reducing interference between APs through joint power control, thereby enabling multiple APs to transmit in parallel and maximizing the total throughput.

[0136] In some embodiments, Co-SR is only applicable to UHR DL SU transmission within each BSS.

[0137] Figure 8 is an example diagram of a Co-SR transmission process. The method shown in Figure 8 may include steps S810 to S830.

[0138] In step S810, the sharing AP (AP1 in Figure 8) transmits a Co-SR trigger frame to the shared AP (AP2 in Figure 8). The transmission duration and transmission power of the AP are specified by the Co-SR trigger frame.

[0139] Before step S810, the shared AP obtains TXOP.

[0140] In step S820, all APs (including shared APs and APs that are shared) transmit in parallel with their associated STAs (STA1 and STA2 in Figure 8).

[0141] In step S830, STA1 sends a BA frame to AP1. STA2 sends a BA frame to AP2.

[0142] The Co-SR trigger frame is explained below.

[0143] The AP that sends the Co-SR trigger frame is the sharing AP, and the AP that receives the Co-SR trigger frame is the shared AP.

[0144] The trigger type field in the common information field of the Co-SR trigger frame can take any value from 9-15 (reserved values) in Table 1, such as 9, to indicate that the trigger frame is a new type of trigger frame. The UL length field in the common information field of the Co-SR trigger frame is set to the length of the PPDU transmitted by the shared AP. The AP transmit power field in the common information field of the Co-SR trigger frame is set to the transmission power of the shared AP.

[0145] In the Co-SR trigger frame, the AID12 field in the user information field is set to the AP ID of the shared AP. Other bits in the user information field (e.g., bits [20:38]) can be redefined to carry the maximum transmission power of the shared AP.

[0146] Co-BF works similarly to null steering, enabling interference suppression. For example, during data transmission / reception, the AP can enhance the beam directed towards the target STA. Alternatively, during data transmission / reception, the AP can nullify the spatial radiation directed towards a non-target STA.

[0147] In some embodiments, Co-BF is only applicable to DL non-OFDMA MU MIMO transmissions.

[0148] Co-BF transmission can be triggered by a MAC frame. This MAC frame may, for example, include a MU-RTS TXS trigger frame. The MU-RTS TXS frame may be a modified version of the specifications of the relevant technology.

[0149] The MAC control frame that triggers Co-BF transmission (e.g., the MU-RTS TXS trigger frame applied to Co-BF) may include one or more of the following parameters: M-AP TXS type, OBSS STA ID, shared AP ID, and PPDU length for Co-BF transmission.

[0150] The Multi-AP TXS Type field indicates the type of multi-AP collaboration involving TXOP sharing. For example, a value of 0 indicates Co-BF; a value of 1 indicates C-TDMA; and a value of 2 indicates Co-SR, etc.

[0151] The OBSS STA ID field can indicate information about the non-AP STA associated with the shared AP. For example, this field can indicate the AID or (partial) MAC address of the non-AP STA associated with the shared AP.

[0152] The In-BSS STA ID field can indicate information about the non-AP STA associated with the shared AP. For example, this field can indicate the AID or (partial) MAC address of the non-AP STA associated with the shared AP.

[0153] The Shared AP ID field can be used to indicate information about the shared AP. For example, this field can indicate the BSS color of the shared AP, or the LSB of the shared AP's BSSID.

[0154] The PPDU length field of Co-BF can indicate the length of the PPDU used for Co-BF transmission after the SIFS of the MAC control frame (or the CTS frame after SIFS).

[0155] A MAC control frame that triggers a Co-BF transmission can concurrently trigger a single Co-BF PPDU transmission from a shared AP and one or more shared APs. Multiple MAC control frames can be transmitted in a TXOP to trigger multiple Co-BF PPDU transmissions.

[0156] Optionally, after a Co-BF PPDU is transmitted to its associated STAs, the shared AP can send a BAR frame (or MU-BAR frame) in a separate TXOP to request an acknowledgment frame from its associated STA. As shown in Figure 9, AP1 is the sharing AP, and AP2 and AP3 are both shared APs. In the TXOP obtained by AP1, AP1 sends a MAC control frame to AP2, triggering AP2 and AP1 to concurrently send a Co-BF PPDU; and AP1 sends a MAC control frame to AP3, triggering AP3 and AP1 to concurrently send a Co-BF PPDU. Next, AP2 obtains the TXOP and sends a BAR frame to request a BA frame from the STA associated with AP2. AP3 obtains the TXOP and sends a BAR frame to request a BA frame from the STA associated with AP3.

[0157] Optionally, the sharing AP allocates a certain amount of time within the same TXOP to the shared AP, allowing the shared AP to send a BAR frame. As shown in Figure 10, after the Co-BF PPDU is sent, within the TXOP acquired by the sharing AP1, AP1 sends a second MAC control frame to allocate the TXOP acquired by AP1 to the shared AP2. AP2 sends a BAR frame within the TXOP allocated by AP1 to request a BA frame from the STA associated with AP2.

[0158] Multi-AP cooperation can be achieved through an initial-control frame (ICF). For example, this ICF can be a MU-RTS frame or a BSRP frame. The following example, with reference to Figure 11, illustrates the ICF-based Co-BF process.

[0159] In step S1110, AP1 uses an ICF to start TXOP.

[0160] The ICF's address points to AP1's associated STA and AP2.

[0161] This ICF can perform the general functions of an ICF.

[0162] This ICF can indicate the possibility of a Co-BF transfer during this TXOP.

[0163] The ICF includes an "AP2-notification" to inform AP2 of the information required for Co-BF transmission. The "AP2-notification" can be included in the user information field where the AID12 subfield has a special value.

[0164] Step S1120: AP1 sends an associated STA response ICF frame. For example, a CTS or BSR response may be used.

[0165] When the ICF indicates Co-BF, AP1's STA may not be served immediately after responding.

[0166] In step S1130, AP2 transmits an ICF (Second Control Frame, such as MU-RTS or BSRP). The address of this ICF points to the associated STA of AP2 and AP1, and instructs the associated STA of AP2 to transmit a Co-BF.

[0167] The ICF in step S1130 can additionally attach an "AP1-response" response to AP1. This can be included in the user information field where the AID12 subfield has a special value.

[0168] Step S1140: If any associated STA of AP2 is addressed by AP2's ICF, then respond with an ICR (e.g., CTS / BSR).

[0169] If no associated STA of AP2 is addressed, and feedback to AP1 indicates that AP2 cannot participate in Co-BF, then AP1 initiates non-Co-BF transmission with its associated STA.

[0170] In step S1150, if AP2 indicates participation in Co-BF, then AP1 and AP2 initiate Co-BF PPDU transmission via SIFS after AP2's associated STA response.

[0171] In step S1160, after the SIFS following the Co-BF PPDU, the associated STAs of the two APs transmit their BAs in a common TB PPDU (on a separate RU).

[0172] In some embodiments, U-SIG is used to indicate information related to multi-AP collaboration. For example, B20-B25 of U-SIG-1 is used to indicate the second BSS color for Co-BF / Co-SR. Exemplarily, the fields corresponding to each bit in the U-SIG field can be as shown in Table 3.

[0173] Table 3

[0174] The following explanation uses the UHR-SIG field of the Co-BF PPDU as an example to illustrate the UHR-SIG field of the multi-AP collaborative PPDU.

[0175] Figure 12 is a format example of the common field in the UHR-SIG field of the Co-BF PPDU.

[0176] As shown in Figure 12, the public fields may include one or more of the following fields: spatial reuse, GI-LTF size, number of UHR-LTF symbols, LDPC extra symbol segment, pre-FEC padding factor, PE diversity, disregard, and number of non-OFDMA users.

[0177] The 3-bit non-OFDMA user count subfield is used to indicate the total number of users participating in Co-BF. This field can be similar to the definition of non-OFDMA MU-MIMO. For example, the non-OFDMA user count subfield can be set to n to indicate the number of n+1 Co-BF users.

[0178] Figure 13 is an example diagram of non-OFDMA MU-MIMO UHR-SIG format.

[0179] In some embodiments, based on the non-OFDMA MU-MIMO UHR-SIG format, the user's coding subfield (B21) is reused to distinguish the two BSS colors (i.e., reused as the BSS Color Indication field). For example, 0 indicates that the user associates the AP with the first BSS color indicated by U-SIG; 1 indicates that the user associates the AP with the second BSS color indicated by U-SIG.

[0180] As shown in Figure 13, the non-OFDMA MU-MIMO UHR-SIG field may also include one or more of the following fields: STA-ID, MCS, spatial configuration, and 2xLDPC. The spatial configuration field can reuse the IEEE 802.11ax spatial configuration subfield encoding.

[0181] Figure 14 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 14 can be executed by a first AP and a second AP. The first AP and the second AP can be APs that cooperate with multiple APs. For example, the first AP may include a sharing AP, and the second AP may include a shared AP.

[0182] The method shown in Figure 14 may include step S1410.

[0183] In step S1410, the first AP sends the first frame to the second AP.

[0184] The first frame indicates the transmission parameters of the first PPDU sent by the first non-AP STA to the second AP. The first non-AP STA is associated with the second AP. The first PPDU is sent during the cooperation between the first AP and the second AP.

[0185] The process of cooperation between the first AP and the second AP can be a multi-AP cooperation process. For example, the first AP and the second AP can perform Co-BF transmission or Co-SR transmission.

[0186] The first PPDU is sent by the first non-AP STA. The first non-AP STA is associated with the second AP, meaning that the first non-AP STA is not associated with the first AP. Therefore, the first AP can indicate the transmission parameters associated with the non-AP STA that is participating in multi-AP cooperation through the first frame.

[0187] As mentioned above, in multi-AP cooperation, each non-AP STA can exchange PPDUs with its associated AP. For non-AP STAs associated with different APs, the transmission parameters of the PPDUs sent by these non-AP STAs can all be indicated by the first frame. Therefore, the first AP can control or schedule the transmission parameters of the PPDUs sent by non-AP STAs during the multi-AP cooperation process based on the first frame, thereby avoiding conflicts or anomalies between PPDUs sent by multiple non-AP STAs associated with different APs, and ensuring that non-AP STAs associated with different APs can send PPDUs normally.

[0188] It should be noted that the PPDU in this application can be a UHR PPDU. For example, the first PPDU mentioned above, and the second, third, or fourth PPDU mentioned below can all be UHR PPDUs.

[0189] UHR PPDUs can include the following formats: UHR MU PPDU and UHR TB PPDU. If the UHR PPDU is not a response to a trigger frame, its format can be UHR MU PPDU. In other words, UHR MU PPDU is a non-trigger-based PPDU. If the UHR PPDU is a response to a trigger frame, its format can be UHR TB PPDU. That is, the UHR TB PPDU format can be used to respond to a trigger frame transmission from the AP; i.e., UHR TB PPDU is a trigger-based PPDU.

[0190] The UHR MU PPDU format can be used to transmit signals to one or more users. Figure 15A is an example diagram of a UHR MU PPDU format. As shown in Figure 15A, a UHR MU PPDU may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG, UHR-STF, UHR-LTF, data, and PE fields. Specifically, the L-STF field is mainly used for signal detection, automatic gain control, time synchronization, and coarse frequency offset estimation; the L-LTF field is mainly used for channel estimation and further frequency offset estimation; the L-SIG field is used for transmission rate and length information; RL-SIG is a repetition of L-SIG; the U-SIG and UHR-SIG fields are used to carry information for decoding the PPDU; the UHR-STF field is used to improve automatic gain control estimation in MIMO transmission; the UHR-LTF field is used for MIMO channel estimation from constellation mapping output to the receive link; the data field transmits information; and the PE field is a packet extension.

[0191] As shown in Figure 15A, in the UHR MU PPDU, L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG can be referred to as UHR pre-modulated fields. UHR-STF, UHR-LTF, data, and PE fields can be referred to as UHR modulated fields.

[0192] Figure 15B is an example diagram of a UHR TB PPDU format. As shown in Figure 15B, a UHR TB PPDU may include: L-STF field, L-LTF field, L-SIG field, RL-SIG field, U-SIG field, UHR-STF field, UHR-LTF field, data, and PE field.

[0193] As shown in Figure 15B, in the UHR TB PPDU, the L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG fields can be referred to as UHR pre-modulation fields. The UHR-STF, UHR-LTF, data, and PE fields are referred to as UHR modulation fields.

[0194] For UHR PPDUs, each UHR-LTF symbol can have the same GI duration as each data symbol, which can be 0.8 μs, 1.6 μs, or 3.2 μs, respectively. The UHR-LTF field can include three types: 1x UHR-LTF, 2x UHR-LTF, and 4x UHR-LTF. The duration without GI for each 1x UHR-LTF, 2x UHR-LTF, or 4x UHR-LTF symbol can be 3.2 μs, 6.4 μs, or 12.8 μs, respectively. The duration without GI for data symbols is 12.8 μs.

[0195] It should be noted that the format of the UHR PPDU described above is merely an example. The format of the UHR PPDU may differ from that of Figures 15A and 15B. Furthermore, the first PPDU may also be other types of PPDUs, and this application does not impose any restrictions.

[0196] In some embodiments, the first frame includes a request frame. The request frame is used to request the second AP and the first AP to cooperate. This request frame can be a multi-AP cooperation trigger frame. Exemplarily, the request frame can be a Co-SR trigger frame or a Co-BF trigger frame.

[0197] For example, a request frame may include one or more of the following: Type I trigger frame, MU-RTS TXS frame, MU-RTS frame, and BSRP frame. Type I trigger frames are used to trigger the Co-SR (Cooperative Space Reuse) process, such as the newly defined multi-AP trigger frame described above. Explanations of some fields in Type I trigger frames, MU-RTS TXS frames, MU-RTS frames, or BSRP frames can be found above and will not be repeated here.

[0198] In some embodiments, the first frame is further used to indicate the transmission parameters of the second PPDU sent by the second AP to the first non-AP STA. The first PPDU may satisfy one or more of the following: the second PPDU is used to trigger the first non-AP STA to send the first PPDU; the second PPDU is used to carry downlink data to the first non-AP STA; and the first PPDU carries feedback (e.g., a BA frame / Ack frame) in response to the second PPDU.

[0199] Therefore, the first frame can indicate not only the transmission parameters of the PPDU sent by the APs participating in multi-AP cooperation, but also the transmission parameters of each non-AP STA (including non-AP STAs not associated with the first AP) during multi-AP cooperation. Thus, based on the first frame, the first AP can coordinate the transmission of each communication device during multi-AP cooperation, thereby enabling normal communication between the devices in multi-AP cooperation.

[0200] In one implementation, the second PPDU may include a second frame. The second frame can be used to trigger the first non-AP STA to send the first PPDU. For example, the second frame can be a trigger frame. This trigger frame can be used to trigger the first non-AP STA to send the first PPDU. Alternatively, the second frame may include a TRS control field. This TRS control field can be used to trigger the first non-AP STA to send the first PPDU.

[0201] The content indicated by the second frame can be determined based on the first frame. For example, the second frame can be used to indicate the transmission parameters of the first PPDU. The transmission parameters of the first PPDU indicated by the second frame can be the same as the transmission parameters of the first PPDU indicated by the first frame.

[0202] In some embodiments, the first PPDU carries a first acknowledgment frame; the first acknowledgment frame confirms whether the first non-AP STA has correctly received the second PPDU sent by the second AP. For example, the first acknowledgment frame is an Ack frame or a BA frame. Exemplarily, the second PPDU sent by the second AP may include data sent to the first non-AP STA and the second frame. Based on the received second frame, the first non-AP STA may send a first PPDU including an Ack frame or a BA frame in response to whether the first non-AP STA has correctly received the data in the second PPDU.

[0203] Taking the scenario shown in Figure 8 as an example, the first AP can be AP1, and the second AP can be AP2. The first acknowledgment frame can be the BA frame sent by STA2 associated with AP2 in step S830. This application proposes that the first frame sent by AP1 can indicate the transmission parameters of the PPDU (i.e., the first PPDU) where the BA frame is located.

[0204] Taking the scenario shown in Figure 11 as an example, the first AP can be AP1, and the second AP can be AP2. The first acknowledgment frame can be the TB-ACK frame sent by AP2-STA associated with AP2 in step S1160. This application proposes that the first frame sent by AP1 can indicate the transmission parameters of the PPDU (i.e., the first PPDU) where the TB-ACK frame is located.

[0205] It should be noted that in some embodiments, multiple APs participating in multi-AP cooperation need to send trigger frames or TRS control fields to their respective associated non-AP STAs to request the non-AP STAs to send BA / Ack frames, rather than having a single AP (e.g., the initiating AP) send the trigger frame or TRS control field. This is due to the following two considerations. First, the initiating AP may not be able to set the AID12 of the STA associated with the responding AP (i.e., the OBSS STA). Alternatively, the AID12 of the STA associated with the responding AP may conflict with the STA of the BSS of the initiating AP, resulting in a transmission parameter indication conflict (e.g., corresponding RU / MRU allocation failure). Second, the initiating AP may not be able to set the uplink target receive power (UL) of the STA associated with the responding AP (i.e., the OBSS STA).

[0206] In some embodiments, the transmission parameters of the first PPDU set in the first frame can satisfy the following: the first PPDU and the third PPDU are frequency-division multiplexed. That is, the settings of the first frame can make the first PPDU and the second PPDU meet the requirements of frequency-division multiplexing transmission. For example, the first PPDU and the third PPDU are transmitted via OFDMA. The third PPDU is used to confirm whether the second non-AP STA has correctly received the fourth PPDU sent by the first AP. The second non-AP STA can be associated with the first AP. The first frame can be used to set the transmission parameters of the PPDU sent by the non-AP STA associated with the AP participating in multi-AP cooperation, so that the PPDU sent by each non-AP STA can be frequency-division multiplexed. For example, in FIG8, the PPDU containing the BA frame sent by STA2 can be the first PPDU; the PPDU containing the BA frame sent by STA1 can be the third PPDU. The first frame can set the transmission parameters of the first PPDU sent by STA2, so that the first PPDU sent by STA2 and the third PPDU sent by STA1 meet the requirements of OFDMA transmission.

[0207] In some embodiments, the transmission parameters of the first PPDU set in the first frame can satisfy the following: the first PPDU and the third PPDU are time-domain aligned. Time-domain alignment can mean that they have the same start time and the same end time. For example, both the first and third PPDUs contain N fields, the start time of the nth field in the first PPDU is the same as the start time of the nth field in the second PPDU, and the end time of the nth field in the first PPDU is also the same as the end time of the nth field in the second PPDU. Here, N is a positive integer, and n is a positive integer less than or equal to N. Exemplarily, the first and third PPDUs have the same UL length or UL data symbols, GI and LTF type, number of LTF symbols, and PE disambiguation.

[0208] Setting the first and third PPDUs to be aligned in the time domain allows the receiver to correctly receive and parse the corresponding PPDUs.

[0209] In some embodiments, the first frame is a trigger frame. The transmission parameters of the first PPDU set in the first frame can be indicated by one or more of the following fields: a public information field; a special user information field; and a user information field. The AID12 subfield in the user information field can point to a second AP. Exemplarily, the transmission parameters of the first PPDU set in the first frame can be indicated by the TRS scheduling field or the trigger scheduling field proposed in this application. The TRS scheduling field or the trigger scheduling field can be located in the public information field, the special user information field, or the user information field.

[0210] In some embodiments, the transmission parameters of the first PPDU set in the first frame include one or more of the following: the resource unit (RU) occupied by the first PPDU; the value of the first field in the first PPDU; the GI and LTF types of the first PPDU; the number of symbols in the second field of the first PPDU; the PE ambiguity cancellation of the first PPDU; the transmission power of the first PPDU; and the value of the BSS color field of the U-SIG field of the first PPDU. These will be described below.

[0211] The RU / MRU occupied by the first PPDU set in the first frame can be different from the RU / MRU occupied by the third PPDU. The second AP can determine the second frame to send to the first non-AP STA based on the RU / MRU occupied by the first PPDU indicated in the first frame. Based on the received second frame, the first non-AP STA can modulate data onto the corresponding RU / MRU.

[0212] The following explanation uses Figures 16 and 17 as examples.

[0213] In Figure 16, the first AP is the initiating AP1 (hereinafter referred to as AP1), and the second AP is the responding AP2 (hereinafter referred to as AP2). The first non-AP STA is STA3 or STA4 associated with AP2.

[0214] The method shown in Figure 16 may include steps S1610 to S1670.

[0215] Step S1610, AP1 sends the first frame.

[0216] The first frame may include one or more of the following: Type 1 trigger frame, MU-RTS TXS frame, MU-RTS frame, BSRP frame. The first frame indicates the RU / MRU occupied by the PPDU carrying the BA frame during the Co-BF process of STA3 and STA4.

[0217] In step S1620, AP1 sends a DL Co-BF PPDU to STA1 and STA2. This Co-PPDU contains a trigger frame or a TRS control field, which is used to trigger STA1 and STA2 to send a BA frame for this DL Co-BF PPDU.

[0218] In step S1630, AP2 sends a DL Co-BF PPDU to STA3 and STA4. This Co-BF PPDU is the second PPDU. This Co-PPDU contains a trigger frame or TRS field, used to trigger STA3 and STA4 to send a BA frame for this DL Co-BF PPDU. The RU / MRU used by STA3 and STA4, indicated in the trigger frame or TRS field, is determined based on the indication in the first frame.

[0219] In steps S1640 to S1670, STA1 to STA4 respectively send BA frames to their respective associated APs.

[0220] After SIFS of the DL Co-BF PPDU, one or more non-AP STAs associated with each AP prepare a TB PPDU based on the parameters indicated by the trigger frame or TRS control field carried within the PPDU, and modulate the data onto the allocated RU / MRU. This TB PPDU carries a BA / Ack frame. The TB PPDU transmitted by STA1 or STA2 is the third PPDU, and the PPDU transmitted by STA3 or STA4 is the first PPDU.

[0221] AP1 indicates in the trigger frame or TRS control field that the requested TB PPDU bandwidth is 80MHz, and allocates a 242-tone RU1 (the first 20MHz sub-channel from low to high frequency) to STA1, and a 242-tone RU2 (the second 20MHz sub-channel from low to high frequency) to STA2. STA1 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 242-tone RU1. Only the 20MHz sub-channel containing 242-tone RU1 has power in the 80MHz preamble. STA2 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 242-tone RU2. Only the 20MHz sub-channel containing 242-tone RU2 has power in the 80MHz preamble.

[0222] AP2 indicates in the trigger frame or TRS control field that the requested TB PPDU bandwidth is 80MHz, and allocates 242-tone RU3 (the third 20MHz subchannel from low to high frequency) to STA2 and 242-tone RU4 (the fourth 20MHz subchannel from low to high frequency) to STA4. STA3 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 242-tone RU3. Only the 20MHz subchannel containing 242-tone RU3 has power in the 80MHz preamble. STA4 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 242-tone RU4. Only the 20MHz subchannel containing 242-tone RU4 has power in the 80MHz preamble.

[0223] In Figure 17, the first AP is AP1, the second AP is AP3, and the first non-AP STA is STA2.

[0224] The method shown in Figure 17 may include steps S1710 to S1650.

[0225] Step S1710, AP1 sends the first frame.

[0226] The first frame can be a newly defined multi-AP trigger frame (such as the Co-SR trigger frame mentioned above), a modified MU-RTS TXS frame, a MU-RTS frame, or a BSRP frame. The first frame indicates the RU / MRU occupied by the PPDU carrying the BA frame during the Co-SR process on STA2.

[0227] In step S1720, AP1 sends a DL Co-SR PPDU to STA1. This Co-PPDU contains a trigger frame or a TRS control field, which is used to trigger STA1 to send a BA frame for this DL Co-SR PPDU.

[0228] In step S1730, AP2 sends a DL Co-SR PPDU to STA2. This Co-SR PPDU is the second PPDU. This Co-PPDU contains a trigger frame or TRS field, used to trigger STA2 to send a BA frame for this DL Co-SR PPDU. The RU / MRU used by STA2 indicated in the trigger frame or TRS field is determined based on the indication in the first frame.

[0229] In steps S1740-S1750, STA1 and STA2 respectively send BA frames to their respective associated APs. Step S1740 transmits the third PPDU, and step S1750 transmits the first PPDU.

[0230] After SIFS of the DL Co-SR PPDU, one or more non-AP STAs associated with each AP transmit a TB PPDU using different RUs / MRUs, based on the parameters indicated by the trigger frame or TRS control field carried within the PPDU. This TB PPDU carries a BA / Ack frame. In other words, each STA prepares the TB PPDU according to the bandwidth information indicated by the trigger frame or TRS control field and modulates the data onto the assigned RU / MRU.

[0231] AP1 indicates in the trigger frame or TRS control field that the requested TB PPDU bandwidth is 80MHz, and allocates 484-tone RU1 (the first 40MHz subchannel from low to high frequency) to STA1. STA1 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 484-tone RU1. Only the 40MHz subchannel containing 484-tone RU1 has power in the 80MHz preamble.

[0232] AP2 indicates in the trigger frame or TRS control field that the requested TB PPDU bandwidth is 80MHz, and allocates 484-tone RU2 (the second 20MHz subchannel from low to high frequency) to STA2. STA2 prepares the TB PPDU with an 80MHz bandwidth and modulates the data onto 484-tone RU2. Only the 40MHz subchannel containing 484-tone RU2 has power in the 80MHz preamble.

[0233] When the first frame is the trigger frame, the RU occupied by the first PPDU can be jointly indicated by the following fields in the first frame: RU allocation field, PS160 field, and bandwidth field.

[0234] As one implementation, when transmitting DL Co-BF PPDU and / or DL ​​Co-SR PPDU, the initiating AP indicates RU / MRU allocation in the first frame to indicate the RU / MRU occupied by the TB PPDU used for feeding back BA / Ack frames from one or more non-AP STAs associated with each AP. This parameter is also indicated by the trigger frame or TRS control field carried by each AP in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU. RU / MRU allocation information can be located in the common information field, special user information field, or user information field of the first frame.

[0235] For example, in the embodiment shown in Figure 16 or Figure 17, the initiating AP uses the RU allocation field and PS160 field together with PPDU bandwidth information in the first frame to indicate the RU / MRU occupied by the TB PPDU used when one or more non-AP STAs associated with each AP feed back BA / Ack frames.

[0236] As mentioned above, the first frame may indicate one or more of the following fields: the value of the first field in the first PPDU; the GI and LTF types of the first PPDU; the number of signs in the second field of the first PPDU; and the PE ambiguity disambiguation of the first PPDU. These items may all affect the duration of each field in the first PPDU. Therefore, indicating some or all of these contents in the first frame can ensure that the first PPDU and the third PPDU are aligned in the time domain as much as possible.

[0237] In some embodiments, the first field includes the length field in the L-SIG field. That is, the first frame can indicate the value of the length field in the L-SIG field of the first PPDU.

[0238] In some embodiments, the second field may include one or more of the following: a data field and an LTF field. That is, the first frame may indicate the sign count of one or more of the following fields: a data field and an LTF field. By indicating the sign count of the data field and / or the LTF field, the data field of the first PPDU and the data field of the third PPDU may be aligned, and / or the LTF field of the first PPDU and the LTF field of the third PPDU may be aligned.

[0239] In some embodiments, the first frame may include one or more of the following fields: third field, fourth field, fifth field, sixth field, and seventh field.

[0240] The third field is used to indicate the value of the length field indicated by L-SIG in the first PPDU. The number of bits in the third field can be one to 12, for example, 12 bits. The third field can also be called the uplink length (UL length) field.

[0241] The fourth field indicates the GI and LTF types of the first PPDU. The number of bits can be one to two. For example, when the number of bits is 1, it indicates two of the following: 1×LTF+1.6us GI, 2×LTF+1.6us GI, or 4×LTF+3.2us GI. As another example, when the number of bits is 2, it indicates 1×LTF+1.6us GI, 2×LTF+1.6us GI, or 4×LTF+3.2us GI, with the remaining values ​​reserved. The fourth field can also be called the GI and LTF type field.

[0242] The fifth field can be used to indicate the number of LTF symbols in the first PPDU. The number of bits can be one to three. For example, when the number of bits is 1, it indicates two of the following: 1 LTF symbol, 2 LTF symbol, 4 LTF symbol, 6 LTF symbol, and 8 LTF symbol. As another example, when the number of bits is 2, it indicates four of the following: 1 LTF symbol, 2 LTF symbol, 4 LTF symbol, 6 LTF symbol, and 8 LTF symbol. As yet another example, when the number of bits is 3, it indicates 1 LTF symbol, 2 LTF symbol, 4 LTF symbol, 6 LTF symbol, and 8 LTF symbol, with the remaining values ​​reserved. The fifth field can also be called the LTF symbol number field.

[0243] The sixth field indicates PE ambiguity cancellation. The sixth field can occupy 1 bit. Its value can be determined according to the definitions in relevant technologies. For example, if equation (36-94) defined in Draft P802.11be_D7.0 is satisfied, the sixth field is set to 1; otherwise, it is set to 0. The sixth field can also be called the PE ambiguity cancellation field.

[0244] The seventh field indicates the number of symbols in the data field of the first PPDU. The value of the seventh field is the number of symbols in the data field of the first PPDU minus 1. The seventh field occupies one to five bits, for example, 5 bits. The seventh field can also be called the uplink data symbols (UL data symbols) field.

[0245] In some embodiments, when the second frame is a trigger frame (i.e., the frame that triggers the transmission of the first PPDU is the trigger frame), the first frame may include one or more of the first to sixth fields. When the second frame includes a TRS control field (i.e., the transmission of the first PPDU is triggered by the TRS control field), the first frame may include a seventh field. This will be illustrated below with examples 1 and 2.

[0246] Example 1

[0247] Example 1 addresses the case where the second frame is the trigger frame. During multi-AP cooperative transmission (e.g., Co-BF PPDU and / or Co-SR PPDU transmission), the initiating AP carries a trigger scheduling field in the first frame. The trigger scheduling field can be located in the AID12 subfield, pointing to the user information field of the responding AP. The first frame is, for example, a MU-RTS frame. Figure 18 shows an example of the format of the user information field provided in Example 1.

[0248] As shown in Figure 18, the trigger scheduling field includes one or more of the following fields: UL length field, GI and LTF type fields, LTF symbolic number field, and PE ambiguity resolution field.

[0249] The UL length field is used to indicate the value of the length field indicated by L-SIG in the request TB PPDU.

[0250] The GI and LTF type fields are used to indicate the GI and LTF types of the requested TB PPDU. A value of 0 indicates a 1×LTF+1.6us GI, a value of 1 indicates a 2×LTF+1.6us GI, a value of 2 indicates a 4×LTF+3.2us GI, and a value of 3 is reserved.

[0251] The LTF symbol field indicates the number of LTF symbols requested for the TB PPDU. A value of 0 indicates 1 LTF symbol, a value of 1 indicates 2 LTF symbols, a value of 2 indicates 4 LTF symbols, a value of 3 indicates 6 LTF symbols, a value of 4 indicates 8 LTF symbols, and values ​​5-7 are reserved.

[0252] The PE Ambiguity Removal field indicates PE ambiguity removal. It is set to 1 if equation (36-94) defined in Draft P802.11be_D7.0 is satisfied, and otherwise to 0.

[0253] Example 2

[0254] Example 2 addresses the case where the second frame includes a TRS control frame. When multiple APs cooperate in transmission (e.g., Co-BF PPDU and / or Co-SR PPDU transmission), the initiating AP carries a TRS scheduling field in the first frame. The TRS scheduling field is located in the AID12 subfield, which points to the user information field of the responding AP. The first frame is, for example, a MU-RTS frame. Figure 19 shows an example of the format of the user information field provided in Example 2.

[0255] As shown in Figure 19, the TRS scheduling field can include the UL data symbol field. The UL data symbol field can be used to indicate the number of OFDM symbols in the data field of the TB PPDU response, and is set to the number of symbols minus 1.

[0256] In some embodiments, the first frame may be used to indicate the value of the BSS color subfield of the U-SIG field in the first PPDU. For example, the first frame may include an eighth field. The eighth field may be used to indicate the value of the BSS color subfield of the U-SIG field in the first PPDU. The eighth field may also be referred to as the common BSS color field.

[0257] When the first frame indicates the value of the BSS color subfield of the U-SIG field in the first PPDU, the BSS color subfield of the U-SIG field of the PPDUs transmitted by one or more non-AP STAs associated with each AP participating in multi-AP cooperation can all be the value indicated in the first frame. Based on this, the content of the U-SIG field of the PPDUs transmitted by one or more non-AP STAs associated with each AP participating in multi-AP cooperation can be the same, thus meeting the requirements of related technologies. Furthermore, when the content of the U-SIG field of the PPDUs transmitted by multiple non-AP STAs is the same, the receiving AP only needs to parse the preamble of a certain sub-channel (e.g., the main 20MHz channel), which can reduce implementation complexity.

[0258] In some embodiments, the U-SIG field of the first PPDU and the U-SIG field of the third PPDU are different. That is, the BSS color subfield of the U-SIG field of the PPDU sent by one or more non-AP STAs associated with each AP participating in multi-AP cooperation can be different. As mentioned above, related technologies specify that the U-SIG content of TB PPDUs must be the same. Therefore, this application proposes that, in the multi-AP cooperation process, the U-SIG content of the TB PPDUs sent by each STA can be different in every 20MHz subchannel. Considering that the first PPDU and the third PPDU belong to different BSSs, this application modifies the related technologies to allow the BSS color field in the U-SIG field of the first PPDU and the BSS color field in the U-SIG field of the third PPDU to be different. For example, the BSS color field in the U-SIG field of the first PPDU can indicate the color of the BSS where the second AP is located; the BSS color field in the U-SIG field of the third PPDU can indicate the color of the BSS where the first AP is located.

[0259] For example, when performing Co-BF and / or Co-SR PPDU transmissions, the U-SIG content of the TB PPDUs returned by each STA can be different. As another example, when performing 40MHz / 80MHz / 160MHz / 320MHz Co-BF and / or Co-SR PPDU transmissions, the U-SIG content of the TB PPDUs returned by each STA can be different for every 20MHz.

[0260] In some embodiments, the first frame may indicate the transmission power of the first PPDU. For example, the first frame may indicate the transmission power of the TB PPDU carrying BA / Ack frames for one or more non-AP STAs associated with the second AP.

[0261] In one implementation, the first frame can directly indicate the transmission power value of the first PPDU. For example, the first frame can indicate the transmission power value corresponding to the TB PPDU carrying the BA / Ack frame for one or more non-AP STAs associated with the second AP, that is, it includes one or more transmission power values ​​corresponding to one or more non-AP STAs.

[0262] The transmission power values ​​of the TB PPDUs carrying BA / Ack frames for one or more non-AP STAs associated with the second AP indicated in the first frame can be arranged from largest to smallest or smallest to largest based on the indicator identifiers of the corresponding non-AP STAs. The indicator identifiers may include, for example, AID11, AID12, or a MAC address.

[0263] As one implementation, the first frame may indicate one or more of the maximum, minimum, or range of transmission power for the first PPDU. For example, the first frame may indicate one or more of the maximum, minimum, or range of transmission power for the TB PPDU carrying BA / Ack frames for one or more non-AP STAs associated with the second AP. In this case, even for multiple non-AP STAs, the first frame may include only one field indicating the power of the PPDUs transmitted by the multiple non-AP STAs. For example, the first frame may include a maximum transmit power field allowed for STAs, which may indicate the maximum power of the PPDUs transmitted by one or more non-AP STAs. Each AP can set the power of the PPDUs transmitted by the non-AP STAs in the trigger frame based on this maximum power.

[0264] In some embodiments, during Co-BF sounding, the beamforming transmitter (initiating AP and / or responding AP) causes the beamforming receiver (the STA associated with the initiating AP and / or the STA associated with the responding AP) to report the received signal strength indication (RSSI).

[0265] Based on this, one or more non-AP STAs associated with the second AP can transmit TB PPDUs carrying BA / Ack frames according to certain power control after SIFS of DL Co-BF PPDU and / or DL ​​Co-SR PPDU, thereby enabling each TB PPDU carrying BA / Ack frames to be correctly received.

[0266] The power control scheme proposed in this application is illustrated below with reference to Figures 20 and 21.

[0267] In Figure 20, the first AP is the initiating AP1 (hereinafter referred to as AP1), and the second AP is the responding AP2 (hereinafter referred to as AP2). The first non-AP STA is STA3 or STA4.

[0268] The method shown in Figure 20 may include steps S2010 to S2070.

[0269] Step S2010, AP1 sends the first frame.

[0270] The first frame can be the newly defined multi-AP trigger frame (i.e., Co-SR trigger frame) mentioned above, the modified MU-RTS TXS frame, the MU-RTS frame, or the BSRP frame. The first frame indicates the transmission power of the PPDU carrying the BA frame in STA3 and STA4 during the Co-BF process.

[0271] In step S2020, AP1 sends a DL Co-BF PPDU to STA1 and STA2. This Co-PPDU contains a trigger frame or a TRS control field, which is used to trigger STA1 and STA2 to send a BA frame for this DL Co-BF PPDU.

[0272] In step S2030, AP2 sends a DL Co-BF PPDU to STA3 and STA4. This Co-BF PPDU is the second PPDU. This Co-PPDU contains a trigger frame or TRS field, used to trigger STA3 and STA4 to send a BA frame for this DL Co-BF PPDU. The transmission power of the PPDUs of STA3 and STA4 indicated in the trigger frame or TRS field is determined based on the indication of the first frame.

[0273] In steps S2040 to S2070, STA1 to STA4 respectively send BA frames to their respective associated APs.

[0274] One or more non-AP STAs associated with each AP transmit a TB PPDU using the corresponding transmission power after SIFS of the DL Co-BF PPDU, based on the parameters indicated by the trigger frame or TRS control field carried within the PPDU. This TB PPDU carries a BA / Ack frame.

[0275] In Figure 21, the first AP is AP1, the second AP is AP3, and the first non-AP STA is STA2.

[0276] The method shown in Figure 21 may include steps S2110 to S1650.

[0277] Step S2110, AP1 sends the first frame.

[0278] The first frame can be a newly defined multi-AP trigger frame (such as the Co-SR trigger frame mentioned above), a modified MU-RTS TXS frame, a MU-RTS frame, or a BSRP frame. The first frame indicates the transmission power of STA2 carrying the BA frame during the Co-SR process.

[0279] In step S2120, AP1 sends a DL Co-SR PPDU to STA1. This Co-PPDU contains a trigger frame or a TRS control field, which is used to trigger STA1 to send a BA frame for this DL Co-SR PPDU.

[0280] In step S2130, AP2 sends a DL Co-SR PPDU to STA2. This Co-SR PPDU is the second PPDU. This Co-PPDU contains a trigger frame or TRS field, used to trigger STA2 to send a BA frame for this DL Co-SR PPDU. The transmit power used by STA2, indicated in the trigger frame or TRS field, is determined based on the indication in the first frame.

[0281] In steps S2140-S2150, STA1 and STA2 respectively send BA frames to their respective associated APs. Step S2140 transmits the third PPDU, and step S2150 transmits the first PPDU.

[0282] After SIFS of the DL Co-SR PPDU, one or more non-AP STAs associated with each AP transmit a TB PPDU using the corresponding transmit power, based on the parameters indicated by the trigger frame or TRS control field carried within the PPDU. The TB PPDU carries a BA / Ack frame.

[0283] The first frame indicates that the transmission power of the TB PPDU carrying the BA / Ack frame for one or more non-AP STAs associated with the second AP can be carried in one or more ninth fields. A ninth field can indicate the transmission power of the TB PPDU carrying the BA / Ack frame for the corresponding non-AP STA. The ninth field can also be called the allowed STA's Tx power field.

[0284] The unit of the ninth field can be dBm. The value Fval of the ninth field can satisfy: Txpwr = -110 + Fval. Where Txpwr is the value of the indicated transmission power.

[0285] Figure 22 is a format example diagram of a trigger scheduling field provided in an embodiment of this application.

[0286] The trigger scheduling field shown in Figure 22 is located in the first frame, which is a MU-RTS frame. This trigger scheduling field is located in the AID12 subfield, which points to the user information field of the second AP.

[0287] As shown in Figure 22, the trigger scheduling field includes two allowed site transmission power fields: Allowed Site Transmission Power 1 and Allowed Site Transmission Power 2. The Allowed Site Transmission Power field indicates the allowed transmission power for the corresponding non-AP STA, in dBm, where Txpwr = -110 + Fval, and Fval is the value of this field, and Txpwr is the allowed transmission power value. Allowed Site Transmission Power 1 corresponds to the STA with the smaller AID11 (or AID12 or MAC address) among the STAs associated with the second AP; Allowed Site Transmission Power 2 corresponds to the STA with the larger AID11 (or AID12 or MAC address) among the STAs associated with the second AP.

[0288] The maximum transmission power of the TB PPDU carrying BA / Ack frames for one or more non-AP STAs associated with the second AP, as indicated in the first frame, can be carried in the tenth field. The tenth field can indicate the maximum transmission power of the TB PPDU carrying BA / Ack frames for all non-AP STAs. The tenth field can also be called the allowed STA's Max Tx power field.

[0289] The unit of the tenth field can be dBm. The value of the tenth field, Fval, can satisfy: TxpwrMax = -110 + Fval. Where TxpwrMax is the indicated maximum transmission power.

[0290] Figure 23 is an example diagram of the format of a trigger scheduling field provided in an embodiment of this application.

[0291] The trigger scheduling field shown in Figure 23 is located in the first frame, which is a MU-RTS frame. This trigger scheduling field is located in the AID12 subfield, which points to the user information field of the second AP.

[0292] As shown in Figure 23, the trigger scheduling field includes the allowed maximum station transmission power field. The allowed maximum station transmission power field indicates the maximum allowed transmission power for a non-AP STA, in dBm, TxpwrMax = -110 + Fval, where Fval is the value of this field and TxpwrMax is the indicated maximum transmission power.

[0293] In some embodiments, the transmission mode of the first PPDU is determined by a default method. The transmission parameters of the first PPDU determined by the default method may not be indicated by the first frame, that is, the corresponding fields may not exist in the first frame.

[0294] In some embodiments, the transmission parameters determined by the default method can be predefined. That is, the default method can be a standard-predefined method. For example, the standard can define the following: The UL length subfield value indicated by the trigger frame carried in the second PPDU can be one of 0 to 4095. The GI and LT type subfield values ​​indicated by the trigger frame carried in the second PPDU can be one of 1×LTF+1.6us GI, 2×LTF+1.6us GI, or 4×LTF+3.2us GI. The LTF symbol number subfield value indicated by the trigger frame carried in the second PPDU can be one of 1, 2, 4, 6, or 8. The PE ambiguity cancellation subfield value indicated by the trigger frame carried in the second PPDU can be one of 0 or 1. The UL data symbol subfield value indicated by the TRS carried in the second PPDU can be one of 0 to 31. The BSS color subfield of the U-SIG field of the first PPDU can be set to the value indicated by the first BSS Color subfield or the second BSS Color subfield of the U-SIG field in the second PPDU.

[0295] In some embodiments, the transmission parameters determined by default can be determined by the transmission parameters of the second PPDU. The second PPDU is used to trigger the first non-AP STA to send the first PPDU. Exemplarily, the transmission parameters of the first PPDU can be consistent with the transmission parameters of the second PPDU.

[0296] For example, when transmitting DL Co-BF PPDU and / or DL ​​Co-SR PPDU, the TB PPDU transmission parameters used by one or more non-AP STA feedback BA / Ack frames associated with each AP are the same as those used in the previous DL Co-BF PPDU and / or DL ​​Co-SR PPDU. These parameters are also indicated by the trigger frame or TRS control field carried by each AP in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU. Parameters that are the same as those used in the previous DL Co-BF PPDU and / or DL ​​Co-SR PPDU may include some or all of parameters 1 through 4.

[0297] Parameter 1, the UL length subfield value indicated by the trigger frame carried in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU is the same as the value indicated by the L-SIG field in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU.

[0298] Parameter 2, the GI and LTF type subfield values ​​indicated by the trigger frame carried in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU are the same as the GI+LTF size subfield value indicated by the UHR-SIG field in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU, and conform to the GI+LTF type allowed by the TB PPDU, such as: 2×LTF+1.6us GI or 4×LTF+3.2us GI.

[0299] Parameter 3, the LTF symbol number subfield value indicated by the trigger frame carried in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU is the same as the LTF symbol number subfield value indicated by the UHR-SIG field in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU.

[0300] Parameter 4, the PE ambiguity cancellation subfield value indicated by the trigger frame carried in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU is the same as the PE ambiguity cancellation subfield value indicated by the UHR-SIG field in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU.

[0301] For example, the uplink data symbols (UL Data symbols) subfield value indicated by the TRS carried in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU is the same as the number of data symbols in the DL Co-BF PPDU and / or DL ​​Co-SR PPDU.

[0302] In some embodiments, the transmission parameters of the first PPDU sent by the first non-AP STA are partly indicated by the first frame; partly they are the same as the transmission parameters of the second PPDU, or are a certain value specified by the standard.

[0303] In some embodiments, the transmission parameters of the first PPDU indicated by the first frame and / or default mode are also the content indicated by the second frame (i.e., the trigger frame or TRS control field) carried by the second AP in the second PPDU. Other parameters in the second frame can be set to default values ​​or set by the second AP itself.

[0304] For example, if the second frame is the trigger frame, the fields in the second frame can satisfy one or more of the following: the More TF field is set to a value of 0 or 1; the CS Required field is set to a value of 0 or 1; the UL BW field and the UL BW extension field are jointly set to the bandwidth of the Co-BF PPDU and / or Co-SR PPDU; the LDPC extra symbol segment is set to a value of 0 or 1; the AP Tx power field is set by the AP itself; the Pre-FEC fill factor is set to one of the values ​​0 to 3; and the UL FEC encoding type field, the UL EHT-MCS field, and the UL target received power field are set by the second AP itself.

[0305] For example, if the second frame includes a TRS control field, the AP Tx power field, UL target received power field, and UL-MCS field in the TRS control field can be set by the second AP itself.

[0306] In some embodiments, the first frame may indicate the triggering method of the first PPDU, i.e., whether the second PPDU is sent by triggering the first PPDU via a trigger frame or by triggering the first PPDU via a TRS field. For example, the first frame may include a trigger type field. The trigger type field may occupy 1 bit. Exemplarily, a value of 0 in the trigger type field indicates that the request for the first PPDU is triggered using a basic trigger frame; a value of 1 in the trigger type field indicates that the request for the first PPDU is triggered using a TRS field.

[0307] The following explains the various fields in the second frame when the second frame is the trigger frame.

[0308] The UL length field of the second frame indicates the LENGTH value of the L-SIG field in the second PPDU;

[0309] The reserved value or reuse of other fields in the second frame, such as B25-B36 of the special user information field, indicates the first BSS color and the second BSS color of the U-SIG field in the second PPDU;

[0310] The UL BW field and UL BW extension field of the second frame jointly indicate the bandwidth value of the U-SIG field in the Co-BF PPDU and / or Co-SR PPDU.

[0311] The reserved value or reuse of other fields in the second frame, such as B56-B57 of the UHR variant public information field, indicates the UHR-SIG MCS value of the U-SIG field in the second PPDU.

[0312] The reserved value or reuse of other fields in the second frame, such as B58-B62 of the UHR variant public information field, indicates the UHR-SIG symbol value of the U-SIG field in the second PPDU.

[0313] The GI and HE / EHT / UHR LTF type fields in the second frame indicate the GI+LTF size value of the UHR-SIG field in the second PPDU. The HE / EHT / UHR-LTF symbol number field in the second frame indicates the of UHR-LTF symbol value of the UHR-SIG field in the second PPDU.

[0314] The LDPC extra symbol segment field of the second frame indicates the LDPC extra symbol segment value of the UHR-SIG field in the second PPDU.

[0315] The pre-FEC fill factor field in the second frame indicates the pre-FEC fill factor value of the UHR-SIG field in the second PPDU.

[0316] The PE ambiguity cancellation field in the second frame indicates the PE ambiguity cancellation value of the UHR-SIG field in the second PPDU.

[0317] The method embodiments of this application have been described in detail above. The apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0318] Figure 24 is a schematic structural diagram of a communication device 2400 provided in an embodiment of this application. The communication device 2400 is a first access point (AP). The communication device 2400 includes a transmitting unit 2410.

[0319] The transmitting unit 2410 is used to transmit a first frame to the second AP; wherein the first frame is used to indicate the transmission parameters of a first PPDU transmitted by a first non-AP STA to the second AP, the first non-AP STA being associated with the second AP, and the first PPDU being transmitted during the cooperation between the first AP and the second AP.

[0320] In this embodiment, the communication device 2400 can be used to execute some or all of the method steps performed by the first AP in the above method embodiment. The communication device 2400 includes units or modules for executing the aforementioned method steps. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment and correspond to the modules in the communication device 2400.

[0321] In an optional embodiment, the transmitting unit 2410 may be a transceiver 2630. The communication device 2400 may also include a processor 2610 and a memory 2620, as shown in FIG26.

[0322] Figure 25 is a schematic structural diagram of a communication device 2500 provided in an embodiment of this application. The communication device 2500 is a second access point (AP). The communication device 2500 includes a receiving unit 2510.

[0323] The receiving unit 2510 is used to receive a first frame sent by the first AP; wherein the first frame is used to indicate the transmission parameters of a first PPDU sent by the first non-AP STA to the second AP, the first non-AP STA being associated with the second AP, and the first PPDU being sent during the cooperation between the first AP and the second AP.

[0324] In this embodiment, the communication device 2500 can be used to execute some or all of the method steps performed by the second AP in the above method embodiments. The communication device 2500 includes units or modules for executing the aforementioned method steps. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment and correspond to the modules in the communication device 2500.

[0325] In an optional embodiment, the receiving unit 2510 may be a transceiver 2630. The communication device 2500 may also include a processor 2610 and a memory 2620, as shown in FIG26.

[0326] Figure 26 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 26 indicate that the unit or module is optional. The apparatus 2600 can be used to implement the methods described in the above method embodiments. The apparatus 2600 can be a chip or a communication device.

[0327] Apparatus 2600 may include one or more processors 2610. The processor 2610 may support apparatus 2600 in implementing the methods described in the preceding method embodiments. The processor 2610 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0328] The apparatus 2600 may further include one or more memories 2620. The memories 2620 store a program that can be executed by the processor 2610, causing the processor 2610 to perform the methods described in the preceding method embodiments. The memories 2620 may be independent of the processor 2610 or integrated within the processor 2610.

[0329] The device 2600 may also include a transceiver 2630. The processor 2610 can communicate with other devices or chips via the transceiver 2630. For example, the processor 2610 can send and receive data with other devices or chips via the transceiver 2630.

[0330] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0331] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0332] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0333] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0334] In the embodiments of this application, a "field" may also be referred to as a "domain", "subfield", or "subfield". A field may occupy one or more bytes (byte / octet), or a field may occupy one or more bits (bit).

[0335] Unless otherwise stated, this application does not restrict the position of each field, that is, the position of each field can be adjusted.

[0336] The field names defined in the embodiments of this application are merely examples, and the field may have other names.

[0337] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0338] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0339] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0340] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including AP and STA). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0341] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0342] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".

[0343] In the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0344] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the WiFi protocol and related protocols applied to future WiFi communication systems, and this application does not limit it.

[0345] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0346] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0347] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0348] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0349] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of wireless communication, the method comprising: include: The first access point (AP) sends the first frame to the second AP; The first frame is used to indicate the transmission parameters of the first physical layer protocol data unit (PPDU) sent by the first non-AP STA to the second AP. The first non-AP STA is associated with the second AP, and the first PPDU is sent during the cooperation between the first AP and the second AP.

2. The method of claim 1, wherein, The first frame is also used to indicate the transmission parameters of the second PPDU sent by the second AP to the first non-AP STA, and the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

3. The method of claim 2, wherein, The second PPDU includes a second frame, which is used to trigger the first non-AP STA to send the first PPDU.

4. The method of claim 3, wherein, The content indicated by the second frame is determined based on the first frame.

5. The method according to claim 3 or 4, characterized in that, The second frame is a trigger frame, or the second frame includes a Trigger Feedback Scheduler (TRS) control field.

6. The method according to any one of claims 1-5, characterized in that, The first PPDU is used to carry a first acknowledgment frame; the first acknowledgment frame is used to confirm whether the first non-AP STA has correctly received the second PPDU sent by the second AP.

7. The method of claim 6, wherein, The first confirmation frame is a Block Confirmation (BA) frame.

8. The method according to claim 6 or 7, characterized in that, The first PPDU and the third PPDU are frequency division multiplexed, wherein the third PPDU is used to confirm whether the second non-AP STA has correctly received the fourth PPDU sent by the first AP.

9. The method of claim 8, wherein, The first PPDU and the third PPDU are transmitted via Orthogonal Frequency Division Multiple Access (OFDMA).

10. The method according to claim 8 or 9, characterized in that, The first PPDU and the third PPDU are aligned in the time domain.

11. The method according to any one of claims 8-10, characterized in that, The U-SIG field of the first PPDU is different from the U-SIG field of the third PPDU.

12. The method according to any one of claims 1-11, characterized in that, The transmission parameters include: The resource units occupied by the first PPDU; The value of the first field in the first PPDU; The guard interval (GI) and long training field (LTF) type of the first PPDU; The number of signs in the second field of the first PPDU; Ambiguity in the packet extension field PE of the first PPDU is eliminated; The transmission power of the first PPDU; The value of the Basic Service Set (BSS) color field of the U-SIG field of the first PPDU.

13. The method of claim 12, wherein, The first field includes the length field in the conventional signal field L-SIG.

14. The method according to claim 12 or 13, characterized in that, The second field includes one or more of the following: a data field, an LTF field.

15. The method according to any one of claims 12-14, characterized in that, The resource unit occupied by the first PPDU is jointly indicated by the following fields in the first frame: resource unit allocation field, PS160 field, and bandwidth field.

16. The method of any one of claims 1-15, wherein, The first frame is a trigger frame, and the transmission parameters are indicated by one or more of the following fields: Public information fields; Special user information fields; User information field.

17. The method according to any one of claims 1-16, characterized in that, Some or all of the transmission parameters of the first PPDU are determined by default.

18. The method according to claim 17, characterized in that, The transmission parameters determined by the default method satisfy one or more of the following: The transmission parameters determined by the default method are predefined; The transmission parameters of the second PPDU determine that the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

19. The method of any one of claims 1-18, wherein, The first frame includes a request frame, which is used to request the second AP and the first AP to cooperate.

20. The method of claim 19, wherein, The request frame includes any one of the following: a first type trigger frame, a multi-user request to send a Transport Opportunity Sharing (MU-RTS) TXS frame, a multi-user request to send a MU-RTS frame, and a Buffer Status Report Polling (BSRP) frame, wherein the first type trigger frame is used to trigger the Cooperative Space Reuse (Co-SR) process.

21. A wireless communication method, characterized in that, include: The second access point (AP) receives the first frame sent by the first AP. The first frame is used to indicate the transmission parameters of the first physical layer protocol data unit (PPDU) sent by the first non-AP STA to the second AP. The first non-AP STA is associated with the second AP, and the first PPDU is sent during the cooperation between the first AP and the second AP.

22. The method according to claim 21, characterized in that, The first frame is also used to indicate the transmission parameters of the second PPDU sent by the second AP to the first non-AP STA, and the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

23. The method of claim 22, wherein, The second PPDU includes a second frame, which is used to trigger the first non-AP STA to send the first PPDU.

24. The method according to claim 23, characterized in that, The content indicated by the second frame is determined based on the first frame.

25. The method according to claim 23 or 24, characterized in that, The second frame is a trigger frame, or the second frame includes a Trigger Feedback Scheduler (TRS) control field.

26. The method according to any one of claims 21-25, characterized in that, The first PPDU is used to carry a first acknowledgment frame; the first acknowledgment frame is used to confirm whether the first non-AP STA has correctly received the second PPDU sent by the second AP.

27. The method according to claim 26, characterized in that, The first confirmation frame is a Block Confirmation (BA) frame.

28. The method according to claim 26 or 27, characterized in that, The first PPDU and the third PPDU are frequency division multiplexed, wherein the third PPDU is used to confirm whether the second non-AP STA has correctly received the fourth PPDU sent by the first AP.

29. The method according to claim 28, characterized in that, The first PPDU and the third PPDU are transmitted via Orthogonal Frequency Division Multiple Access (OFDMA).

30. The method according to claim 28 or 29, characterized in that, The first PPDU and the third PPDU are aligned in the time domain.

31. The method according to any one of claims 28-30, characterized in that, The U-SIG field of the first PPDU is different from the U-SIG field of the third PPDU.

32. The method according to any one of claims 21-31, characterized in that, The transmission parameters include: The resource units occupied by the first PPDU; The value of the first field in the first PPDU; The guard interval (GI) and long training field (LTF) type of the first PPDU; The number of signs in the second field of the first PPDU; Ambiguity in the packet extension field PE of the first PPDU is eliminated; The transmission power of the first PPDU; The value of the Basic Service Set (BSS) color field of the U-SIG field of the first PPDU.

33. The method according to claim 32, characterized in that, The first field includes the length field in the conventional signal field L-SIG.

34. The method according to claim 32 or 33, characterized in that, The second field includes one or more of the following: a data field, an LTF field.

35. The method according to any one of claims 32-34, characterized in that, The resource unit occupied by the first PPDU is jointly indicated by the following fields in the first frame: resource unit allocation field, PS160 field, and bandwidth field.

36. The method according to any one of claims 21-35, characterized in that, The first frame is a trigger frame, and the transmission parameters are indicated by one or more of the following fields: Public information fields; Special user information fields; User information field.

37. The method according to any one of claims 21-36, characterized in that, Some or all of the transmission parameters of the first PPDU are determined by default.

38. The method according to claim 37, characterized in that, The transmission parameters determined by the default method satisfy one or more of the following: The transmission parameters determined by the default method are predefined; The transmission parameters of the second PPDU determine that the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

39. The method according to any one of claims 21-38, characterized in that, The first frame includes a request frame, which is used to request the second AP and the first AP to cooperate.

40. The method according to claim 39, characterized in that, The request frame includes any one of the following: a first type trigger frame, a multi-user request to send a Transport Opportunity Sharing (MU-RTS) TXS frame, a multi-user request to send a MU-RTS frame, and a Buffer Status Report Polling (BSRP) frame, wherein the first type trigger frame is used to trigger the Cooperative Space Reuse (Co-SR) process.

41. A communication device, characterized in that, The communication device is a first access point (AP), and the communication device includes: The transmitting unit is used to send the first frame to the second AP; The first frame is used to indicate the transmission parameters of the first physical layer protocol data unit (PPDU) sent by the first non-AP STA to the second AP. The first non-AP STA is associated with the second AP, and the first PPDU is sent during the cooperation between the first AP and the second AP.

42. The communication device according to claim 41, characterized in that, The first frame is also used to indicate the transmission parameters of the second PPDU sent by the second AP to the first non-AP STA, and the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

43. The communication device according to claim 42, characterized in that, The second PPDU includes a second frame, which is used to trigger the first non-AP STA to send the first PPDU.

44. The communication device according to claim 43, characterized in that, The content indicated by the second frame is determined based on the first frame.

45. The communication device according to claim 43 or 44, characterized in that, The second frame is a trigger frame, or the second frame includes a Trigger Feedback Scheduler (TRS) control field.

46. ​​The communication device according to any one of claims 41-45, characterized in that, The first PPDU is used to carry a first acknowledgment frame; the first acknowledgment frame is used to confirm whether the first non-AP STA has correctly received the second PPDU sent by the second AP.

47. The communication device according to claim 46, characterized in that, The first confirmation frame is a Block Confirmation (BA) frame.

48. The communication device according to claim 46 or 47, characterized in that, The first PPDU and the third PPDU are frequency division multiplexed, wherein the third PPDU is used to confirm whether the second non-AP STA has correctly received the fourth PPDU sent by the first AP.

49. The communication device according to claim 48, characterized in that, The first PPDU and the third PPDU are transmitted via Orthogonal Frequency Division Multiple Access (OFDMA).

50. The communication device according to claim 48 or 49, characterized in that, The first PPDU and the third PPDU are aligned in the time domain.

51. The communication device according to any one of claims 48-50, characterized in that, The U-SIG field of the first PPDU is different from the U-SIG field of the third PPDU.

52. The communication device according to any one of claims 41-51, characterized in that, The transmission parameters include: The resource units occupied by the first PPDU; The value of the first field in the first PPDU; The guard interval (GI) and long training field (LTF) type of the first PPDU; The number of signs in the second field of the first PPDU; Ambiguity in the packet extension field PE of the first PPDU is eliminated; The transmission power of the first PPDU; The value of the Basic Service Set (BSS) color field of the U-SIG field of the first PPDU.

53. The communication device according to claim 52, characterized in that, The first field includes the length field in the conventional signal field L-SIG.

54. The communication device according to claim 52 or 53, characterized in that, The second field includes one or more of the following: a data field, an LTF field.

55. The communication device according to any one of claims 52-54, characterized in that, The resource unit occupied by the first PPDU is jointly indicated by the following fields in the first frame: resource unit allocation field, PS160 field, and bandwidth field.

56. The communication device according to any one of claims 41-55, characterized in that, The first frame is a trigger frame, and the transmission parameters are indicated by one or more of the following fields: Public information fields; Special user information fields; User information field.

57. The communication device according to any one of claims 41-56, characterized in that, Some or all of the transmission parameters of the first PPDU are determined by default.

58. The communication device according to claim 57, characterized in that, The transmission parameters determined by the default method satisfy one or more of the following: The transmission parameters determined by the default method are predefined; The transmission parameters of the second PPDU determine that the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

59. The communication device according to any one of claims 41-58, characterized in that, The first frame includes a request frame, which is used to request the second AP and the first AP to cooperate.

60. The communication device according to claim 59, characterized in that, The request frame includes any one of the following: a first type trigger frame, a multi-user request to send a Transport Opportunity Sharing (MU-RTS) TXS frame, a multi-user request to send a MU-RTS frame, and a Buffer Status Report Polling (BSRP) frame, wherein the first type trigger frame is used to trigger the Cooperative Space Reuse (Co-SR) process.

61. A communication device, characterized in that, The communication device is a second access point (AP), and the communication device includes: The receiving unit is used to receive the first frame sent by the first AP; The first frame is used to indicate the transmission parameters of the first physical layer protocol data unit (PPDU) sent by the first non-AP STA to the second AP. The first non-AP STA is associated with the second AP, and the first PPDU is sent during the cooperation between the first AP and the second AP.

62. The communication device according to claim 61, characterized in that, The first frame is also used to indicate the transmission parameters of the second PPDU sent by the second AP to the first non-AP STA, and the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

63. The communication device according to claim 62, characterized in that, The second PPDU includes a second frame, which is used to trigger the first non-AP STA to send the first PPDU.

64. The communication device according to claim 63, characterized in that, The content indicated by the second frame is determined based on the first frame.

65. The communication device according to claim 63 or 64, characterized in that, The second frame is a trigger frame, or the second frame includes a Trigger Feedback Scheduler (TRS) control field.

66. The communication device according to any one of claims 61-65, characterized in that, The first PPDU is used to carry a first acknowledgment frame; the first acknowledgment frame is used to confirm whether the first non-AP STA has correctly received the second PPDU sent by the second AP.

67. The communication device according to claim 66, characterized in that, The first confirmation frame is a Block Confirmation (BA) frame.

68. The communication device according to claim 66 or 67, characterized in that, The first PPDU and the third PPDU are frequency division multiplexed, wherein the third PPDU is used to confirm whether the second non-AP STA has correctly received the fourth PPDU sent by the first AP.

69. The communication device according to claim 68, characterized in that, The first PPDU and the third PPDU are transmitted via Orthogonal Frequency Division Multiple Access (OFDMA).

70. The communication device according to claim 68 or 69, characterized in that, The first PPDU and the third PPDU are aligned in the time domain.

71. The communication device according to any one of claims 68-70, characterized in that, The U-SIG field of the first PPDU is different from the U-SIG field of the third PPDU.

72. The communication device according to any one of claims 61-71, characterized in that, The transmission parameters include: The resource units occupied by the first PPDU; The value of the first field in the first PPDU; The guard interval (GI) and long training field (LTF) type of the first PPDU; The number of signs in the second field of the first PPDU; Ambiguity in the packet extension field PE of the first PPDU is eliminated; The transmission power of the first PPDU; The value of the Basic Service Set (BSS) color field of the U-SIG field of the first PPDU.

73. The communication device according to claim 72, characterized in that, The first field includes the length field in the conventional signal field L-SIG.

74. The communication device according to claim 72 or 73, characterized in that, The second field includes one or more of the following: a data field, an LTF field.

75. The communication device according to any one of claims 72-74, characterized in that, The resource unit occupied by the first PPDU is jointly indicated by the following fields in the first frame: resource unit allocation field, PS160 field, and bandwidth field.

76. The communication device according to any one of claims 61-75, characterized in that, The first frame is a trigger frame, and the transmission parameters are indicated by one or more of the following fields: Public information fields; Special user information fields; User information field.

77. The communication device according to any one of claims 61-76, characterized in that, Some or all of the transmission parameters of the first PPDU are determined by default.

78. The communication device according to claim 77, characterized in that, The transmission parameters determined by the default method satisfy one or more of the following: The transmission parameters determined by the default method are predefined; The transmission parameters of the second PPDU determine that the second PPDU is used to trigger the first non-AP STA to send the first PPDU.

79. The communication device according to any one of claims 61-78, characterized in that, The first frame includes a request frame, which is used to request the second AP and the first AP to cooperate.

80. The communication device according to claim 79, characterized in that, The request frame includes any one of the following: a first type trigger frame, a multi-user request to send a Transport Opportunity Sharing (MU-RTS) TXS frame, a multi-user request to send a MU-RTS frame, and a Buffer Status Report Polling (BSRP) frame, wherein the first type trigger frame is used to trigger the Cooperative Space Reuse (Co-SR) process.

81. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1-40.

82. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-40.

83. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-40.

84. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-40.

85. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-40.

86. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-40.

Images