Access point and wireless communication method

Abstract

Provided are an access point (AP) and a wireless communication method. The AP can be a sharing AP. The wireless communication method comprises: the sharing AP sending a trigger frame to one or more shared APs to request an extremely high throughput (EHT) multi-user (MU) physical layer protocol data unit (PPDU) transmission from the one or more shared APs in a multi-AP cooperative downlink (DL) transmission. The trigger frame comprises an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. A DL bandwidth (BW) subfield of the EHT variant common information field and a DL BW extension subfield of the special user information field indicate a cooperative transmission BW for the multi-AP cooperative DL transmission. In this way, the problems existing in the prior art can be solved, multi-AP DL cooperation is effectively implemented in a multi-AP system, EHT is implemented, and good communication performance and / or high reliability are provided.

Description

[0001] This application is a divisional application of the invention patent application filed on November 5, 2021, with application number "202180103536.4" and invention title "Access Point and Wireless Communication Method". Technical Field

[0002] This disclosure relates to the field of communication systems, and in particular to an access point (AP) and wireless communication method to provide good communication performance and / or high reliability. Background Technology

[0003] Communication systems, such as wireless communication systems, are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These communication systems can be multiple access systems, capable of supporting communication with multiple users by sharing available system resources (such as time, frequency, and power). Wireless networks (e.g., Wi-Fi (IEEE 802.11) networks and other wireless local area networks (WLANs)) may include access points (APs) that can communicate with one or more stations (STAs) or mobile devices. WLANs allow users to wirelessly access the Internet using portable terminals such as personal digital assistants (PDAs), laptops, portable multimedia players (PMPs), and smartphones at home, in the office, or in a specific service area, based on radio frequency technology. APs can be coupled to a network (e.g., the Internet), enabling mobile devices to communicate over the network (or with other devices coupled to the AP). Wireless devices can communicate bidirectionally with network devices. For example, in a WLAN, a STA can communicate with an associated AP via downlink and uplink. Downlink can refer to the communication link from AP to STA, while uplink can refer to the communication link from STA to AP.

[0004] IEEE 802.11 TGbe is developing a new amendment to IEEE 802.11 to define an extremely high throughput (EHT) physical layer (PHY) and medium access control (MAC) layer capable of supporting a maximum throughput of at least 30 Gbps. To this end, it is proposed to increase the maximum channel bandwidth to 320 MHz and the maximum number of spatial streams to 16. Furthermore, it is recommended to enable multi-AP cooperation in multi-AP systems to improve system throughput. For example, multi-AP cooperation schemes include multi-AP cooperative downlink (DL) orthogonal frequency division multiple access (OFDMA) and multi-AP cooperative DL multi-user multiple input multiple output (MU-MIMO). Multi-AP cooperative DL MU-MIMO can also be called multi-AP DL distributed MIMO or multi-AP DL joint transmission. However, effectively implementing multi-AP DL cooperation in multi-AP systems remains an unresolved issue.

[0005] Therefore, there is a need to provide an access point (AP) and wireless communication method to solve the problems existing in the prior art, effectively realize multi-AP downlink (DL) cooperation in multi-AP systems, achieve extremely high throughput, and provide good communication performance and / or high reliability. Summary of the Invention

[0006] The purpose of this disclosure is to provide an access point (AP) and a wireless communication method to address the problems existing in the prior art, effectively realize multi-AP downlink (DL) cooperation in a multi-AP system, achieve extremely high throughput, and provide good communication performance and / or high reliability.

[0007] According to a first aspect of this disclosure, a wireless communication method implemented via an access point (AP) includes: the AP, acting as a shared AP, sending a trigger frame to one or more shared APs to request Very High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission to one or more shared APs in a multi-AP cooperative downlink (DL) transmission, wherein the trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields; the DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for the multi-AP cooperative DL transmission.

[0008] According to a second aspect of this disclosure, a wireless communication method implemented via an access point (AP) includes: the AP receiving, as a shared AP, a trigger frame from another AP, which is also a shared AP, the trigger frame being used to request Very High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission to one or more shared APs, including the AP itself, in a multi-AP cooperative downlink (DL) transmission, wherein the trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields; the DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for the multi-AP cooperative DL transmission.

[0009] According to a third aspect of this disclosure, an access point (AP) includes: a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is used to perform the methods described above.

[0010] According to a fourth aspect of this disclosure, a non-transitory machine-readable storage medium stores instructions, wherein when a computer executes the instructions, the computer performs the method described above.

[0011] According to a fifth aspect of this disclosure, a chip includes a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the methods described above.

[0012] According to a sixth aspect of this disclosure, a computer-readable storage medium stores a computer program that causes a computer to perform the above-described method.

[0013] According to a seventh aspect of this disclosure, a computer program product includes a computer program that causes a computer to perform the methods described above.

[0014] According to the eighth aspect of this disclosure, a computer program causes a computer to perform the above-described method. Attached Figure Description

[0015] To more clearly illustrate the embodiments of this disclosure or related technologies, the embodiments will be briefly described below in conjunction with the accompanying drawings. Obviously, the drawings only show some embodiments of this disclosure. Those skilled in the art can obtain other drawings free of charge based on these drawings.

[0016] Figure 1A A schematic diagram illustrating an exemplary set of AP candidates including multiple APs, provided for embodiments of this disclosure; Figure 1B A schematic diagram illustrating an exemplary multi-AP DL joint transmission provided in an embodiment of this disclosure; Figure 2AA schematic diagram illustrating bandwidth allocation for multiple EHT MU PPDU sets provided in an embodiment of this disclosure; Figure 2B A schematic diagram illustrating bandwidth allocation for multiple EHT MU PPDU sets provided in an embodiment of this disclosure; Figure 2C A schematic diagram illustrating bandwidth allocation for multiple EHT MU PPDU sets provided in an embodiment of this disclosure; Figure 2D A schematic diagram illustrating bandwidth allocation for multiple EHT MU PPDU sets provided in an embodiment of this disclosure; Figure 2E A schematic diagram illustrating bandwidth allocation for multiple EHT MU PPDU sets provided in an embodiment of this disclosure; Figure 3 A schematic diagram of the EHT MU PPDU format provided in the embodiments of this disclosure; Figure 4 A schematic diagram illustrating an exemplary multi-AP cooperative DL transmission provided in an embodiment of this disclosure; Figure 5 A schematic diagram illustrating an exemplary format of the multi-AP cooperative transmission trigger frame format provided in this disclosure embodiment; Figure 6 A schematic diagram illustrating an exemplary format of the EHT variant public information field provided in embodiments of this disclosure; Figure 7A A schematic diagram illustrating an exemplary format of a special user information field in a multi-AP cooperative transmission trigger frame provided in this embodiment of the disclosure; Figure 7B A schematic diagram illustrating an exemplary format of a public information subfield for triggering dependencies provided in embodiments of this disclosure; Figure 7C A schematic diagram illustrating an exemplary format of the punched channel information subfield provided in this embodiment of the disclosure; Figure 7D A schematic diagram illustrating an exemplary format of the punched channel information subfield provided in this embodiment of the disclosure; Figure 8A A schematic diagram illustrating an exemplary format of a special user information field provided in an embodiment of this disclosure; Figure 8B This is a schematic diagram illustrating an exemplary format of a user information sub-field that the triggering of a special user information field provided in this embodiment of the disclosure depends on. Figure 8C A schematic diagram illustrating an exemplary format of the punched channel information subfield provided in this embodiment of the disclosure; Figure 8D A schematic diagram illustrating an exemplary format of the punched channel information subfield provided in this embodiment of the disclosure; Figure 9A A schematic diagram illustrating an exemplary format of an EHT variant user information field provided in an embodiment of this disclosure; Figure 9B A schematic diagram illustrating an exemplary format of a user information field that triggers dependencies, as provided in embodiments of this disclosure; Figure 10A A schematic diagram illustrating an exemplary format of an EHT variant user information field provided in an embodiment of this disclosure; Figure 10B A schematic diagram illustrating an exemplary format of a user information field that triggers dependencies, as provided in embodiments of this disclosure; Figure 11 A schematic diagram illustrating an example of a wireless communication system provided in an embodiment of this disclosure; Figure 12 A schematic diagram illustrating an example of a wireless communication system provided in another embodiment of this disclosure; Figure 13 A schematic diagram illustrating an example of a wireless communication system provided in another embodiment of this disclosure; Figure 14 A block diagram illustrating one or more stations (STAs) and access points (APs) communicating in a wireless communication system, as provided in embodiments of this disclosure; Figure 15 A flowchart of a wireless communication method performed by an AP provided in an embodiment of this disclosure; Figure 16 A flowchart illustrating a wireless communication method performed by an AP, as provided in another embodiment of this disclosure; Figure 17 A block diagram of an access point (AP) provided in an embodiment of this disclosure; Figure 18 A block diagram of an access point (AP) provided in an embodiment of this disclosure; Figure 19 A block diagram of a wireless communication system provided in an embodiment of this disclosure. Detailed Implementation

[0017] The technical problems, structural features, objectives, and effects of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. Specifically, the terminology used in the embodiments of this disclosure is only used to describe the purpose of specific embodiments and is not intended to limit this disclosure.

[0018]

[0019] Table 1 AP refers to a standalone AP or an AP attached to an AP MLD. STA refers to a standalone non-AP STA or a STA attached to a non-AP MLD. dot11EHTBaseLineFeaturesImplementedOnly and dot11Multi-APCoordinationOptionImplemented are two MIB variables maintained by the SME of the STA (or AP). A STA (or AP) with dot11EHTBaseLineFeaturesImplementedOnly equal to true refers to an EHT STA (or EHT AP) that supports one or more EHT baseline features (e.g., MRU and multi-link operation) defined in IEEE 802.11be D1.2, but does not support any EHT advanced features (e.g., multi-AP collaboration) defined in subsequent drafts of IEEE 802.11be (e.g., IEEE 802.11be D3.0), i.e., a WiFi7 R1 STA (or AP). A STA (or AP) with `dot11EHTBaseLineFeaturesImplementedOnly` equal to `false` refers to an EHT STA (or EHT AP) that supports one or more EHT baseline features defined in IEEE 802.11be D1.2 and one or more EHT advanced features to be defined in subsequent drafts of IEEE 802.11be (e.g., IEEE 802.11be D3.0), i.e., a WiFi7 R2 STA (or AP). A STA (or AP) with `dot11Multi-APCoordinationOptionImplemented` equal to `true` refers to an EHT STA (or EHT AP) that supports multi-AP collaboration; a STA (or AP) with `dot11Multi-APCoordinationOptionImplemented` equal to `false` refers to an EHT STA (or EHT AP) that does not support multi-AP collaboration.An STA (or AP) whose dot11EHTBaseLineFeaturesImplementedOnly is false and dot11Multi-APCoordinationOptionImplemented is true is called an STA (or AP) with Multi-AP Coordination (MAPC) capability; an STA (or AP) whose dot11EHTBaseLineFeaturesImplementedOnly is true, or whose dot11EHTBaseLineFeaturesImplementedOnly and dot11Multi-APCoordinationOptionImplemented are both false, is called an STA (or AP) without MAPC capability.

[0020] An AP candidate set refers to a group of APs with MAPC functionality capable of initiating or participating in multi-AP collaboration. The coordinator responsible for establishing and maintaining the AP candidate set can be a member AP of the AP candidate set or a member AP outside the AP candidate set. An AP that obtains a TXOP and initiates multi-AP collaboration is a shared AP. APs in the AP candidate set can participate as shared APs in multi-AP collaboration initiated by shared APs in the same AP candidate set. At least one AP in the AP candidate set can act as a shared AP. Multi-AP collaboration can include a multi-AP collaboration preparation phase and a multi-AP collaboration transmission phase. In the multi-AP collaboration preparation phase, the shared AP that obtains a TXOP and initiates multi-AP collaboration can send a first frame to one or more APs in the same AP candidate set to inquire about its own intention to participate in multi-AP collaboration. Each of the one or more APs responds with a second frame to inform the shared AP whether it intends to participate in multi-AP collaboration. For example, the first frame may include information indicating a predetermined multi-AP collaboration scheme; any AP receiving the first frame can understand, according to the predetermined multi-AP collaboration scheme, that the shared AP is inquiring about its intention to participate in multi-AP collaboration. If an AP intends to participate in multi-AP collaboration, that AP becomes a shared AP in the multi-AP collaboration. During the multi-AP cooperative transmission phase, the sharing AP and one or more shared APs can participate in the multi-AP cooperative transmission. Alternatively, the sharing AP may not participate in the multi-AP cooperative transmission; two or more shared APs may participate in the multi-AP cooperative transmission.

[0021] Figure 1A An exemplary AP candidate set including three APs (AP1, AP2, and AP3) is shown. At any given time, AP1 can acquire a TXOP and initiate multi-AP cooperation as a shared AP; while AP2 and AP3 can participate in multi-AP cooperation as shared APs. AP1, AP2, and AP3 can participate in multi-AP cooperative transmissions within the TXOP (e.g., multi-AP cooperative DL OFDMA transmissions or...). Figure 1B (This illustrates multi-AP DL joint transmission). At another time, AP2 can acquire a TXOP and initiate multi-AP cooperation as a shared AP; while AP1 and AP3 can participate in multi-AP cooperation as shared APs. AP1 and AP3 can participate in multi-AP cooperative transmission within the TXOP; while AP2 does not participate in multi-AP cooperative transmission.

[0022] According to some embodiments of this disclosure, AP candidate sets form virtual BSSs (VBSSs) that can be identified by MAC addresses (i.e., VBSSIDs). AP candidate sets or VBSSs can also be identified by VBSS colors. In one embodiment, the VBSS color and the BSS color are in the same numerical space. In this case, the numerical ranges of the VBSS color and the BSS color do not overlap. For example, the numerical range of the BSS color is 0 to N, and the numerical range of the VBSS color is N+1 to 63, where N is a positive integer between 1 and 62, and the value of N can be predefined or configured. The value of N can be displayed in beacon frames, probe response frames, association response frames, and / or reassociation response frames. In another embodiment, the VBSS color and the BSS color are in different numerical spaces. In this case, the numerical range of the VBSS color can overlap with the numerical range of the BSS color. An AP can belong to more than one AP candidate set. An AP candidate set can include up to eight APs; each AP in the AP candidate set is identified by an AP ID. The AP can indicate the configuration information and operating parameters of each AP candidate set to which it belongs in the transmitted beacon frames and / or probe response frames. The configuration information and operating parameters of an AP candidate set may include SSID, short SSID, VBSSID, VBSS color, BSSID of each member AP (excluding the transport AP), BSS color of each member AP (excluding the transport AP), and / or supported multi-AP cooperative transmission schemes. At any given time, a STA with MAPC functionality is associated with no more than one AP candidate set. A STA with MAPC functionality can establish an association with an AP candidate set through its member APs, where the member AP is called the STA's anchor AP. In one embodiment, before associating with an AP candidate set through its anchor AP, the STA should first associate with its anchor AP. In another embodiment, a STA can simultaneously associate with both its anchor AP and the AP candidate set.

[0023] In some embodiments, during the process of a STA with MAPC functionality establishing an association with an AP candidate set through its anchor AP, the coordinator of the AP candidate set assigns a Virtual AID (VAID) to the STA. The VAID uniquely identifies the STA within the VBSS of the AP candidate set. In one embodiment, the VAID and AID may reside in different value spaces. In this case, the value range of the VAID may overlap with that of the AID. In another embodiment, the VAID and AID may reside in the same value space. In this case, the value range of the VAID does not overlap with that of the AID. For example, the AID's value range is 1 to M, and the VAID's value range is M+1 to 2007, where M is a positive integer between 2 and 2006. The value of M can be predefined or configured. The value of M can be displayed in beacon frames, probe response frames, association response frames, and / or reassociation response frames.

[0024] After a STA with MAPC functionality is associated with an AP candidate set through its anchor AP, in the VBSS of the AP candidate set, the STA can send a single PSDU to or receive one or more PSDUs from one or more APs in the AP candidate set during multi-AP cooperative transmissions involving more than one AP. In multi-AP cooperative transmissions, when a STA sends a single PSDU to or receives multiple PSDUs from more than one AP, the more than one AP includes the STA's anchor AP. In multi-AP cooperative transmissions, when a STA sends a single PSDU to or receives a single PSDU from a single AP, that AP is the STA's anchor AP. Alternatively, the AP can be any AP participating in the multi-AP cooperative transmission. Furthermore, a STA can send a single PSDU to or receive a single PSDU from a single AP in non-cooperative transmissions. The single AP is the STA's anchor AP. Alternatively, the single STA can be any AP in the AP candidate set. Figure 1A Taking the multi-AP system shown as an example, assume that the anchor AP for STA2 is AP2. In cooperative multi-AP transmission, STA2 can send only a single PSDU to AP2 or receive only a single PSDU from AP2; or send a single PSDU to at least one of AP1 and AP3 and AP2, or receive two or more PSDUs from at least one of AP1 and AP3 and AP2. In non-cooperative transmission, STA2 can send only a single PSDU to AP2 or receive only a single PSDU from AP2.

[0025] Multi-AP cooperative DL transmission can include multi-AP cooperative DL OFDMA transmission and multi-AP DL joint transmission. For example... Figure 1BAs shown, in some embodiments, in multi-AP DL joint transmission, two or more sharing APs and shared APs transmit their respective EHT MU PPDUs to a single STA or different STAs on a single RU or MRU, wherein the RU or MRU occupies all non-punctured 20 MHz channels within the cooperative transmission bandwidth. In multi-AP cooperative DL OFDMA transmission, two or more sharing APs and shared APs transmit their respective EHT MU PPDUs to different STAs in different frequency portions of the cooperative transmission bandwidth, wherein each frequency portion includes one or more 80 MHz frequency sub-blocks. In multi-AP cooperative DL OFDMA transmission, one or more sharing APs and shared APs may transmit their respective EHT MU PPDUs to a single STA or different STAs on a single RU or MRU, wherein the RU or MRU occupies all non-punctured 20 MHz channels within the same frequency portion of the cooperative transmission bandwidth in a manner similar to multi-AP DL joint transmission.

[0026] like Figure 1B As shown, in some embodiments, when multiple APs transmit their respective EHT MU PPDUs carrying their respective PSDUs to the same STA on a single RU or MRU on all non-punctured 20 MHz channels occupying the cooperative transmission bandwidth or a frequency portion of the cooperative transmission bandwidth, the STA's PSDUs are transmitted using the same FEC encoding type and the same MCS. If the STA's PSDUs have the same content, the PSDUs are transmitted using one or more of the same spatial streams. If the STA's PSDUs have different content, the PSDUs are transmitted using different spatial streams.

[0027] In multi-AP cooperative DL transmission, when multiple APs transmit their respective EHT MU PPDUs on a single RU or MRU across all non-punctured 20 MHz channels within the cooperative transmission bandwidth or a frequency portion of the cooperative transmission bandwidth, in one embodiment, not every EHT MU PPDU transmitted by the multiple APs includes a pre-EHT modulation field; the EHT modulation fields transmitted by the multiple APs begin at the same time. For example, only one of the EHT MU PPDUs transmitted by the multiple APs includes a pre-EHT modulation field, such as... Figure 1BAs shown. Specifically, if multiple APs include a shared AP that initiates multi-AP cooperative DL transmission, only the EHT MU PPDU transmitted by the shared AP contains a pre-EHT modulation field. In this embodiment, a power scaling factor greater than 1 can be applied to the pre-EHT modulation field. In other words, the transmission power of the pre-EHT modulation field of the EHT MU PPDU can be greater than the transmission power of the EHT modulation field of the EHT MU PPDU, therefore the pre-EHT modulation field has the same or similar total transmission power as the EHT modulation fields of the EHT MU PPDU transmitted by the multiple APs.

[0028] Multi-AP DL joint transmission is suitable for cooperative transmission bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 320 MHz. Multi-AP cooperative DL OFDMA transmission is suitable for cooperative transmission bandwidths of 160 MHz or 320 MHz, but not for cooperative transmission bandwidths of 20 MHz, 40 MHz, or 80 MHz. In multi-AP cooperative DL transmission, the EHT MU PPDUs sent by two or more sharing APs and the shared APs should have the same number of EHT-SIG symbols, the same GI and EHT-LTF types, the same number of EHT-LTF symbols, and the same duration for the data field and PE field. Therefore, all EHT MU PPDUs have the same transmission time. When two or more shared APs and the shared APs transmit their respective EHT MU PPDUs on a single RU or MRU on all non-punctured 20 MHz channels within the same frequency portion of the cooperative transmission bandwidth, the U-SIG field of the transmitted EHT MU PPDUs should have the same content; the EHT-SIG field of the transmitted EHT MU PPDUs should also have the same content.

[0029] In multi-AP cooperative DL OFDMA transmission, EHT MUPPDUs transmitted by two or more sharing APs and shared APs are aggregated in the frequency domain to form a MU A-PPDU. A MU A-PPDU consists of multiple sets of EHT MU PPDUs; each set includes one or more EHT MU PPDUs transmitted in the same frequency portion of the cooperative transmission bandwidth. The number of EHT MU PPDUs in a set belonging to a frequency portion of the cooperative transmission bandwidth is equal to the number of APs allocated to that frequency portion. For example, if a frequency portion of the cooperative transmission bandwidth is allocated to a single AP (e.g., a sharing AP or a shared AP), then the set of EHT MU PPDUs belonging to that frequency portion includes a single EHT MU PPDU. If a frequency portion of the cooperative transmission bandwidth is allocated to three APs (e.g., a sharing AP and two shared APs, or three shared APs), then the set of EHT MU PPDUs belonging to that frequency portion includes three EHT MU PPDUs.

[0030] For multi-AP cooperative DL OFDMA transmission with a cooperative transmission bandwidth of 160 MHz, two 80 MHz frequency sub-blocks are allocated to two EHT MU PPDU sets respectively. For multi-AP cooperative DL OFDMA transmission with a cooperative transmission bandwidth of 320 MHz, the bandwidth allocation of multiple EHT MU PPDU sets can be selected from the following five options: Option 1A: When one of the 80 MHz frequency sub-blocks is punctured, the unpunctured 80 MHz frequency sub-blocks located in the same 160 MHz channel as the punctured 80 MHz frequency sub-block are assigned to the first EHT MU PPDU set, while the other 160 MHz channel is assigned to the second EHT MU PPDU set, as follows. Figure 2A As shown.

[0031] Option 1B: When one of the 80 MHz frequency sub-blocks is punctured, the three unpunctured 80 MHz frequency sub-blocks are respectively assigned to three EHT MU PPDU sets, such as... Figure 2B As shown.

[0032] Option 1C: Two 160 MHz channels are respectively assigned to two EHT MU PPDU sets, such as Figure 2C As shown.

[0033] Option 1D: Two 80 MHz frequency sub-blocks within the same 160 MHz channel are allocated to the first two EHT MUPPDU sets, respectively; the other 160 MHz channel is allocated to the third EHT MUPPDU set, as follows. Figure 2D As shown.

[0034] Option 1E: Four 80 MHz frequency sub-blocks are respectively allocated to four EHT MU PPDU sets, such as Figure 2E As shown.

[0035] Figure 3 The EHT MU PPDU format shown is used for transmissions not in response to a trigger frame from an AP. L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG are called the pre-EHT modulation fields, while EHT-STF, EHT-LTF, the data field, and the PE field are called the EHT modulation fields. The U-SIG field includes two OFDM symbols, each with a duration of 4 µs. Each EHT-LTF symbol has the same GI duration as each data symbol, which is 0.8 µs, 1.6 µs, or 3.2 µs. EHT-LTF includes three types: 1x EHT-LTF, 2x EHT-LTF, and 4x EHT-LTF. The duration of each 1x EHT-LTF, 2x EHT-LTF, or 4x EHT-LTF symbol without GI is 3.2 µs, 6.4 µs, or 12.8 µs, respectively. The duration of each data symbol without GI is 12.8 µs. The PE duration of the EHT MU PPDU is 0 µs, 4 µs, 8 µs, 12 µs, 16 µs, or 20 µs. Specifically, the U-SIG has two OFDM symbols, each with a duration of 4 µs. The number of EHT-SIG symbols can be variable. Therefore, the duration of the EHT-SIG may not be 8 µs.

[0036] The U-SIG field carries the information needed to interpret the EHT MU PPDU. The U-SIG field is designed to achieve forward compatibility of the EHT preamble by introducing version-independent fields. The location and interpretation of these fields remain consistent across multiple IEEE 802.11 PHY versions. Version-independent content aims to achieve better coexistence between IEEE 802.11 PHY versions defined for the 2.4, 5, and 6 GHz spectrum, starting with the EHT PHY. Furthermore, the U-SIG can have some version-dependent fields, which are specific to the IEEE 802.11 PHY version. The U-SIG includes version-independent bits as well as version-dependent bits. Additionally, the U-SIG field includes one or more verification fields. The value of the verification field indicates whether to continue receiving the EHT MU PPDU on the STA. If the STA encounters an EHT MU PPDU and at least one field in the preamble marked as verification is not set to its specified value, the STA should postpone the duration of the EHT MU PPDU, report the version-independent field information within the RXVECTOR, and terminate reception of the EHT MU PPDU.

[0037] First embodiment: According to the first embodiment, the U-SIG field of the EHT MU PPDU may include a BSS / VBSS subfield and a BSS / VBSS color subfield. For a STA with MAPC functionality, the BSS / VBSS subfield is interpreted as indicating whether the EHT MU PPDU is transmitted in the BSS or the VBSS. For example, the BSS / VBSS subfield is set to a first value (e.g., 1) to indicate that the EHT MU PPDU is transmitted in the BSS; or the BSS / VBSS subfield is set to a second value (e.g., 0) to indicate that the EHT MU PPDU is transmitted in the VBSS. In multi-AP cooperative DL transmission, when an EHT MU PPDU is transmitted along with any other EHT MU PPDU on the same RU or MRU on all non-punctured 20MHz channels within the cooperative transmission bandwidth or frequency portion of the cooperative transmission bandwidth, the BSS / VBSS subfield should be set to indicate that the EHT MU PPDU is transmitted in VBSS. When the RU or MRU transmitting the EHT MU PPDU is different from the RU or MRU transmitting any other EHT MU PPDU, if the transmitting AP is the anchor AP for all STAs to which the EHT MU PPDU is expected, the BSS / VBSS subfield is set to indicate that the EHT MU PPDU is transmitted in BSS; otherwise, the BSS / VBSS subfield should be set to indicate that the EHT MU PPDU is transmitted in VBSS. For STAs without MAPC functionality, the BSS / VBSS subfield is always interpreted as an authentication field that should be set to 1. In other words, when a STA without MAPC receives an EHTMU PPDU with the U-SIG field's BSS / VBSS subfield set to 0, it will terminate the reception of the EHTMU PPDU. For STAs with MAPC, the BSS / VBSS color subfield is interpreted based on its value. When the BSS / VBSS subfield is set to indicate that the EHTMU PPDU is transmitted in the BSS, the BSS / VBSS color subfield will be interpreted as the BSS color subfield indicating the BSS color of the transmitting AP. When the BSS / VBSS subfield is set to indicate that the EHTMU PPDU is transmitted in the VBSS, the BSS / VBSS color subfield will be interpreted as the VBSS color subfield indicating the VBSS color of the AP candidate set. For STAs without MAPC, the BSS / VBSS color subfield of the U-SIG field is always interpreted as the BSS color subfield.

[0038] If the transmitting AP is an AP with MAPC functionality and the EHT MU PPDU is transmitted within the BSS, the transmitting AP sets the BSS / VBSS subfield to indicate the transmission within the transmitting AP's BSS and sets the BSS / VBSS color subfield to indicate the transmitting AP's BSS color. If the transmitting AP is an AP with MAPC functionality and the EHT MU PPDU is transmitted within the VBSS, the transmitting AP sets the BSS / VBSS subfield to indicate the transmission within the VBSS of the AP candidate set and sets the BSS / VBSS color subfield to indicate the VBSS color of the AP candidate set. If the transmitting AP is an AP without MAPC functionality, the transmitting AP sets the BSS / VBSS subfield to indicate the transmission within the transmitting AP's BSS and sets the BSS / VBSS color subfield to indicate the transmitting AP's BSS color.

[0039] In one embodiment, the BSS / VBSS subfield is one of the version-independent fields of the U-SIG field. In this case, the BSS / VBSS subfield corresponds to B25 of U-SIG-1 of the U-SIG field. In another embodiment, the BSS / VBSS subfield is one of the version-dependent fields of the U-SIG field. In this case, the BSS / VBSS subfield corresponds to B2 or B8 of U-SIG-2 of the U-SIG field. Table 2 shows an exemplary format of the U-SIG field of the EHT MU PPDU according to the first embodiment.

[0040]

[0041] Table 2 Second embodiment: In the second embodiment, it is assumed that the VBSS color and the BSS color are in the same numerical space. In this case, the numerical ranges of the VBSS color and the BSS color do not overlap. According to the second embodiment, the U-SIG field of the EHT MU PPDU may include a BSS / VBSS color subfield. For STAs with MAPC functionality, the BSS / VBSS color subfield is interpreted based on its value. When the value of the BSS / VBSS color subfield is within the numerical range of the BSS color, it is interpreted as a BSS color subfield indicating the BSS color of the transmitting AP. When the value of the BSS / VBSS color subfield is within the numerical range of the VBSS color, it is interpreted as a VBSS color subfield indicating the VBSS color of the AP candidate set. For STAs without MAPC functionality, the BSS / VBSS color subfield is always interpreted as a BSS color subfield.

[0042] In multi-AP cooperative DL transmission, when an EHT MU PPDU is transmitted along with any other EHT MU PPDU on the same RU or MRU occupying all non-punctured 20 MHz channels within the cooperative transmission bandwidth or a frequency portion of the cooperative transmission bandwidth, the EHT MU PPDU should be transmitted in the VBSS. When the RU or MRU transmitting the EHT MU PPDU is different from the RU or MRU transmitting any other EHT MU PPDU, if the transmitting AP is the anchor AP for all STAs to which the EHT MU PPDU is expected, the EHT MU PPDU can be transmitted in the BSS; otherwise, the EHT MU PPDU should be transmitted in the VBSS. If the transmitting AP is an AP with MAPC functionality and the EHT MU PPDU is transmitted in the BSS, the transmitting AP sets the BSS / VBSS color subfield to indicate the BSS color of the transmitting AP. If the transmitting AP is an AP with MAPC functionality and the EHT MU PPDU is transmitted in the VBSS, the transmitting AP sets the BSS / VBSS color subfield to indicate the VBSS color of the AP candidate set. If the transmitting AP is an AP without MAPC functionality, the transmitting AP always sets the BSS / VBSS color subfield to indicate the BSS color of the transmitting AP. Table 3 shows an exemplary format of the U-SIG field of the EHT MU PPDU according to the second embodiment.

[0043]

[0044] Table 3 The EHT-SIG field provides additional signaling to the U-SIG field to facilitate STA interpretation of the EHT MU PPDU. The EHT-SIG field of a 20 MHz EHT MU PPDU contains one EHT-SIG content channel. For OFDMA transmissions and non-OFDMA transmissions to multiple users, the EHT-SIG field of a 40 MHz or 80 MHz EHT MU PPDU contains two EHT-SIG content channels; for EHT MU PPDUs of 160 MHz or wider, the EHT-SIG field contains two EHT-SIG content channels every 80 MHz. When the bandwidth of the EHT MU PPDU used for OFDMA transmission is greater than 80 MHz, different information is allowed per 80 MHz EHT-SIG content channel. The EHT-SIG field of an EHT MU PPDU sent to a single user contains one EHT-SIG content channel; when the EHT PPDU is equal to or greater than 40 MHz, this EHT-SIG field is repeated every 20 MHz. For EHT MU PPDUs, the EHT-SIG content channel includes common fields and user-specific fields. Tables 36-33 of IEEE 802.11be D1.2 show exemplary formats of the common fields for EHT MU PPDUs used for OFDMA transmissions. Tables 36-34 of IEEE 802.11be D1.2 show exemplary formats of the common fields for EHT MU PPDUs used for non-OFDMA transmissions. In each EHT-SIG content channel, the user-specific fields include one or more user fields.

[0045] Third embodiment: According to the third embodiment, the user field for non-MU-MIMO or MU-MIMO allocation may include a STA-ID / VSTA-ID subfield indicating the STA addressed by the user field. If the transport AP is an AP with MAPC functionality and the EHT MUPPDU is transmitted in the BSS, the transport AP sets the STA-ID / VSTA-ID subfield to the value of the TXVECTOR parameter STA_ID. If the transport AP is an AP with MAPC functionality and the EHT MUPPDU is transmitted in the VBSS, the transport AP sets the STA-ID / VSTA-ID subfield to the value of the TXVECTOR parameter VSTA_ID. If the transport AP is an AP without MAPC functionality, the transport AP always sets the STA-ID / VSTA-ID subfield to the value of the TXVECTOR parameter STA_ID.

[0046] For STAs with MAPC functionality, the interpretation of the STA-ID / VSTA-ID subfields depends on whether the EHT MU PPDU is transmitted in the BSS or VBSS, which is determined by the STA based on the value of the BSS / VBSS subfield of the U-SIG field in the first embodiment or the value of the BSS / VBSS color subfield of the U-SIG field in the second embodiment. For STAs without MAPC functionality, the STA-ID / VSTA-ID subfields are always interpreted as STA-ID subfields. The definition of the TXVECTOR parameter STA_ID is found in IEEE 802.11be D1.2. The TXVECTOR parameter VSTA_ID indicates a list of VSTA-IDs for EHT MU PPDUs transmitted in the VBSS. Each parameter VSTA_ID in the TXVECTOR identifies the STA or STA group that is the receiver of the RU or MRU in the EHT MU PPDU. For a separately addressed RU or MRU, the parameter VSTA_ID is set to 11 LSBs of the VAID of the STA receiving the PSDU contained in that RU or MRU. If the RU or MRU is used for one or more STAs without an associated AP candidate set, the STA_ID parameter of the RU or MRU is set to 2045. If the RU or MRU is not for a specific user, the VSTA_ID parameter of the RU or MRU is set to 2046. If the RU or MRU is used for more than one associated STA in the VBSS that is not a separately addressed RU or MRU receiver, the STA_ID parameter of the RU or MRU is set to 0. The definition of the user field format according to the non-MU-MIMO allocation of the third embodiment is shown in Table 4. The definition of the user field format according to the MU-MIMO allocation of the third embodiment is shown in Table 5.

[0047]

[0048] Table 4

[0049] Table 5 Fourth embodiment: According to the fourth embodiment, the format of the user field for non-MU-MIMO or MU-MIMO allocation depends on whether the EHT MUPPDU is transmitted in the BSS or the VBSS. If the EHT MUPPDU is transmitted in the BSS, the definition of the format of the user field for non-MU-MIMO or MU-MIMO allocation is given in Tables 36-40 or 36-41 of IEEE 802.11be D1.2. If the EHT MUPPDU is transmitted in the VBSS, the user field for non-MU-MIMO or MU-MIMO allocation may include an AP ID subfield, which, together with the STA-ID subfield, indicates the STA addressed by the user field. The AP ID subfield is set to the AP ID in the AP candidate set corresponding to the VBSS color specified in the U-SIG field; the STA-ID subfield is set to the value of the TXVECTOR parameter STA_ID corresponding to the STA addressed by the user field.

[0050] A shared AP can send a multi-AP cooperative transmission trigger frame to request EHT MU PPDU transmission from one or more shared APs during multi-AP cooperative DL transmission. Within the SIFS following the receipt of the multi-AP cooperative transmission trigger frame, the shared APs simultaneously send their respective EHT MU PPDUs to one or more STAs. If the shared AP is participating in multi-AP cooperative DL transmission, it will also send its own EHT MU PPDU within the SIFS following the sending of the multi-AP cooperative transmission trigger frame. Figure 4 An exemplary multi-AP cooperative DL transmission is illustrated. AP1, AP2, and AP3 belong to the AP candidate set; AP1 is the shared AP that initiates the multi-AP cooperative DL transmission; AP2 and AP3 are the shared APs that participate in the multi-AP cooperative DL transmission.

[0051] Multi-AP cooperative transmission trigger frame is a variant of trigger frame. Figure 5 An exemplary format of a multi-AP cooperative transmission trigger frame is shown, which includes an EHT variant common information field and a user information list field, the user information list field including a special user information field and one or more EHT variant user information fields.

[0052] For multi-AP cooperative transmission trigger frames, the transmitter address (TA) field is set to the VBSSID of the VBSS or the AP candidate set associated with the multi-AP cooperative DL transmission. If the multi-AP cooperative transmission trigger frame is used to request an EHT MU PPDU transmission to a single shared AP, the receiver address (RA) field is set to the BSSID of the shared AP. If the multi-AP cooperative transmission trigger frame is used to request an EHT MU PPDU transmission to more than one shared AP, the RA field is set to the broadcast address. An exemplary format definition for the EHT variant public information field is as follows: Figure 6 As shown. The Trigger Type subfield is set to a value in [9 15] (e.g., 9) to indicate a multi-AP cooperative transmission variant of the trigger frame. The DL Length subfield indicates the value of the L-SIG LENGTH field of the requested EHT MU PPDU. The More TF subfield indicates whether subsequent multi-AP cooperative transmission trigger frames are planned for transmission. The Carrier Sense (CS) subfield is set to 1 to indicate that the shared AP needs to use ED to sense the medium and consider the medium state and NAV when deciding whether to transmit the requested EHT MU PPDU. The CS subfield is set to 0 to indicate that the shared AP does not need to consider the medium state or NAV when deciding whether to transmit the requested EHT MU PPDU.

[0053] The GI and EHT-LTF type subfields indicate the value of the GI+LTF size subfield of the EHT-SIG field of the requested EHT MU PPDU, that is, indicating the GI duration and EHT-LTF size of the requested EHT MU PPDU. This subfield is set to 0 to indicate 2. EHT-LTF + 0.8 µs GI; set to 1 to indicate 2 EHT-LTF + 1.6 µs GI; set to 2 to indicate 4 EHT-LTF + 0.8 µs GI; or set to 3 to indicate 4. EHT-LTF + 3.2 µs GI. The EHT-LTF symbol count subfield indicates the value of the EHT-LTF symbol count subfield in the EHT-SIG field of the requested EHT MU PPDU, that is, the number of EHT-LTF symbols in the requested EHT MU PPDU. For example, the EHT-LTF symbol count subfield is set to 0 to indicate 1 EHT-LTF symbol; set to 1 to indicate 2 EHT-LTF symbols; set to 2 to indicate 4 EHT-LTF symbols; set to 3 to indicate 6 EHT-LTF symbols; set to 4 to indicate 8 EHT-LTF symbols; set to 5 to indicate 12 EHT-LTF symbols; or set to 6 to indicate 16 EHT-LTF symbols.

[0054] The LDPC Additional Symbol Segment subfield indicates the value of the LDPC Additional Symbol Segment subfield of the EHT-SIG field of the requested EHT MU PPDU, indicating the presence of an LDPC Additional Symbol Segment in the requested EHT MU PPDU. This subfield is set to 1 if an LDPC Additional Symbol Segment exists in the requested EHT MU PPDU; otherwise, it is set to 0. The Pre-FEC Fill Factor subfield indicates the value of the Pre-FEC Fill Factor subfield of the EHT-SIG field of the requested EHT MU PPDU, indicating the pre-FEC fill factor of the requested EHT MU PPDU. This subfield is set to 0 to indicate a pre-FEC fill factor of 4; set to 1 to indicate a pre-FEC fill factor of 1; set to 2 to indicate a pre-FEC fill factor of 2; or set to 3 to indicate a pre-FEC fill factor of 3. The PE disambiguation subfield indicates the value of the PE disambiguation subfield of the EHT-SIG field in the requested EHT MU PPDU, as defined in IEEE 802.11be D1.2, 36.3.14. The HE / EHT P160 subfield is always set to 0, indicating that each requested MU PPDU within the primary 160MHz channel is an EHT MU PPDU. The Special User Information Field Flag subfield is always set to 0, indicating that the Special User Information Field is included in the multi-AP cooperative transmission trigger frame.

[0055] Fifth embodiment: According to the fifth embodiment, the exemplary format of the special user information field in the multi-AP cooperative transmission trigger frame is defined as follows: Figure 7AAs shown. The PHY Version Identifier subfield of the Special User Information field indicates the PHY version of the requested MU PPDU; and, for EHT, it is set to 0. The DL BW subfield of the Public Information field and the DL BW Extension subfield of the Special User Information field together indicate the cooperative transmission bandwidth of multi-AP cooperative DL transmission, which is the same as or within the width of the shared AP's BSS working channel. The definition of the DL BW Extension subfield is shown in Table 6.

[0056]

[0057] Table 6 The EHT Space Reuse subfield of the Special User Information field carries the value contained in the Space Reuse subfield of the EHT-SIG field of the requested EHT MU PPDU, indicating whether space reuse mode is allowed when transmitting the requested EHT MU PPDU. This field is set to a value in Tables 27-22 of IEEE Std. 802.11ax-2021. The U-SIG / EHT-SIG Ignore and Verify subfield carries the values ​​contained in the Ignore and Verify subfields of the U-SIG field and the common field for non-OFDMA transmission of the EHT-SIG field for the requested EHT MU PPDU. The definition of the mapping from the U-SIG / EHT-SIG Ignore and Verify subfield to the bits in the U-SIG field and the common field for non-OFDMA transmission of the EHT-SIG field for the EHT MU PPDU is shown in Table 7. To simplify implementation, if one or more bits of the U-SIG field and the ignore and verify subfield of the common field used for non-OFDMA transmission of the EHT-SIG field in the EHT MU PPDU are used for a specific signaling purpose, then the corresponding bits of the U-SIG / EHT-SIG ignore and verify subfield of the special user information field are reserved or used for the same signaling purpose. For example, as shown in Table 7, if B25 of the U-SIG-1 field of the EHT MU PPDU is used as the BSS / VBSS subfield indicating whether the EHT MU PPDU is transmitted in the BSS or VBSS, then B5 of the U-SIG / EHT-SIG ignore and verify subfield of the special user information field is reserved.

[0058]

[0059] Table 7 According to the fifth embodiment, the trigger-dependent user information field of the special user information field is retained, and the size of the trigger-dependent user information field is the same as that of the trigger-dependent user information field of the EHT variant user information field. According to the fifth embodiment, a common information subfield for trigger dependence exists in the multi-AP cooperative transmission trigger frame. An exemplary format definition of the common information subfield for trigger dependence is as follows... Figure 7B As shown. The Multi-AP Cooperative Transmission Type subfield indicates the type of multi-AP cooperative transmission. For example, the Multi-AP Cooperative Transmission Type subfield is set to a first value (e.g., 0) to indicate multi-AP cooperative DL OFDMA transmission; set to a second value (e.g., 1) to indicate multi-AP combined DL transmission; set to a third value (e.g., 2) to indicate multi-AP cooperative UL OFDMA transmission; or set to a fourth value (e.g., 3) to indicate multi-AP cooperative ULMU-MIMO transmission. The EHT-SIG Symbol Count subfield indicates the value of the EHT-SIG Symbol Count subfield of the U-SIG field of the requested EHT MU PPDU, that is, the number of EHT-SIG symbols in the requested EHT MU PPDU. The EHT-SIG Symbol Count subfield is set to the EHT-SIG symbol count minus 1.

[0060] The EHT-SIG MCS subfield indicates the value of the EHT-SIG MCS subfield of the U-SIG field of the requested EHT MU PPDU, i.e., the MCS of the EHT-SIG field used to modulate the requested EHT MU PPDU. It is set to 0 for EHT-MCS 0; 1 for EHT-MCS 1; 2 for EHT-MCS 3; and 3 for EHT-MCS 15. The Pre-EHT Preamble Presence subfield indicates whether a pre-EHT modulation field exists in the requested EHT MU PPDU. The Pre-EHT Preamble Presence subfield is set to 1 to indicate the presence of a pre-EHT modulation field in the requested EHT MU PPDU; or set to 0 to indicate the absence of a pre-EHT modulation field in the requested EHT MU PPDU. For multi-AP cooperative DL OFDMA transmissions, the Pre-EHT Preamble Presence subfield should be set to indicate the presence of a pre-EHT modulation field in the requested EHT MU PPDU. In multi-AP cooperative joint DL transmission involving shared APs, the Pre-EHT preamble presence subfield can be set to indicate that the requested EHT MU PPDU does not contain a pre-EHT modulation field. In this case, the user information list field does not include any user information fields for any STAs addressing to PSDUs that only the shared APs send. Therefore, the overhead of the multi-AP cooperative transmission trigger frame can be reduced. Furthermore, since each shared AP does not need to prepare the pre-EHT modulation field for the requested EHT MU PPDU, padding of the multi-AP cooperative transmission trigger frame can be reduced or avoided.

[0061] The Puncture Channel Information Size subfield indicates the size of the puncture channel information subfield. The puncture channel information size subfield is set to a first value (e.g., 0) to indicate that no puncture channel information subfield exists, meaning no 20MHz channel is punctured in the cooperative transmission bandwidth; a second value (e.g., 1) to indicate that the puncture channel information subfield has 8 bits; or a third value (e.g., 2) to indicate that the puncture channel information subfield has 16 bits. When the cooperative transmission bandwidth is 20 MHz or 40 MHz, the puncture channel information size subfield should be set to indicate that no puncture channel information subfield exists. The format of the puncture channel information subfield depends on the type of multi-AP cooperative DL transmission. For multi-AP joint DL transmission, an exemplary format definition of the puncture channel information subfield is as follows: Figure 7CAs shown, the puncturing channel information subfield includes the 5-bit non-OFDMA puncturing channel information subfield defined in Table 8. Alternatively, if it is a multi-AP joint DL transmission, there is no puncturing channel information subfield; the puncturing channel information for the cooperative transmission bandwidth can be determined from the allocated RU or MRU specified in the RU allocation subfield and PS160 subfield of each EHT variant user information field.

[0062]

[0063] Table 8 If it is a multi-AP cooperative DL OFDMA transmission, the exemplary format definition of the punched channel information subfield is as follows: Figure 7D As shown, the puncturing channel information subfield includes N puncturing channel information subfields per 80 MHz; N = 2 or 4; each puncturing channel information subfield per 80 MHz indicates the puncturing channel information for an 80 MHz frequency subblock. Subfields 1 to 4 of the puncturing channel information subfields per 80 MHz indicate the puncturing channel information for the lowest, second lowest, third lowest, and highest 80 MHz frequency subblocks, respectively. For each bit in each puncturing channel information subfield per 80 MHz, a value of 0 indicates that the corresponding 20 MHz channel is punctured; otherwise, the value is 1. For each 80 MHz frequency subblock, the following allowed puncturing patterns (B0-B3) are defined: 1111 (no puncturing), 0111, 1011, 1101, 1110, 0011, 1100, and 1001, where the bits from left to right represent 20 MHz channels with sequentially increasing frequencies.

[0064] The definition of an effective combination of cooperative transmission bandwidth, multi-AP cooperative transmission type, and the size of the punch channel information subfield is shown in Table 9.

[0065]

[0066] Table 9 Sixth embodiment: According to the sixth embodiment, the multi-AP cooperative transmission trigger frame does not contain a common information subfield that depends on the trigger, thus reducing signaling overhead compared to the fifth embodiment. The exemplary format definition of the special user information field according to the sixth embodiment is as follows: Figure 8A As shown. The exemplary format definition of the user information sub-field that the triggering depends on according to the sixth embodiment is as follows: Figure 8BAs shown. Except for the punched channel information subfield in the sixth embodiment, the other subfields of the special user information field have the same definition as the corresponding fields in the fifth embodiment. According to the sixth embodiment, the format of the punched channel information subfield depends on the type of multi-AP cooperative DL transmission. If it is multi-AP joint DL transmission, the exemplary format definition of the punched channel information subfield according to the sixth embodiment is as follows. Figure 8C As shown, the punctured channel information subfield includes the 5-bit non-OFDMA punctured channel information subfield defined in Table 36-30 of IEEE 802.11be D1.2, but the naming of the first column is changed from PPDU bandwidth to cooperative transmission bandwidth. Alternatively, if it is a multi-AP joint DL transmission, the punctured channel information subfield is retained; the punctured channel information of the cooperative transmission bandwidth can be determined from the allocated RU or MRU specified in the RU allocation subfield and PS160 subfield of the user information field for each EHT variant.

[0067] If it is a multi-AP cooperative DL OFDMA transmission, the exemplary format definition of the punched channel information subfield is as follows: Figure 8D As shown, the puncturing channel information subfield includes four subfields for each 80 MHz frequency sub-block; each subfield indicates the puncturing channel information for one 80 MHz frequency sub-block. Subfields 1 to 4 of the 80 MHz puncturing channel information subfield indicate the puncturing channel information for the lowest, second lowest, third lowest, and highest 80 MHz frequency sub-blocks, respectively. For each bit in each 80 MHz puncturing channel information subfield, a value of 0 indicates that the corresponding 20 MHz channel is punctured; otherwise, the value is 1. For each 80 MHz frequency sub-block, the following allowed puncturing patterns (B0-B3) are defined: 1111 (no puncturing), 0111, 1011, 1101, 1110, 0011, 1100, and 1001, where the bits from left to right represent 20 MHz channels with sequentially increasing frequencies. When the cooperative transmission bandwidth is 160 MHz, the 3rd subfield of the 80 MHz puncturing channel information and the 4th subfield of the 80 MHz puncturing channel information are either reserved or set to all "0".

[0068] Seventh embodiment: According to the seventh embodiment, the exemplary format of the EHT variant user information field is defined as follows: Figure 9AAs shown. If the VAID12 subfield is set to the value in [1 2006], the EHT variant user information field is addressed to the STA where VAID is equal to the value of the VAID12 subfield. If the VAID12 subfield is 2046, the remaining subfields of the EHT variant user information field, except for the RU allocation subfield and the PS160 subfield, are reserved. These reserved subfields, together with the DL BW subfield of the EHT variant public information field and the DL BW extended subfield of the special user information field, indicate the location of the RU or MRU for which no RU or MRU is assigned. The RU allocation subfield and PS160 subfield of the EHT variant user information field, together with the DL BW subfield of the EHT variant public information field and the DL BW extended subfield of the special user information field, identify the size and location of the RU or MRU assigned to the STA addressed by this EHT variant user information field. The mapping of B7-B1 in the RU allocation subfield and the definition of the B0 settings for the RU allocation subfield and the PS160 subfield are shown in Table 9-29j1 of IEEE 802.11be D1.2.

[0069] The DL FEC Encoding Type subfield indicates the encoding type of the STA addressed by this EHT variant user information field. The DL FEC Encoding Type subfield is set to 0 to indicate BCC; or set to 1 to indicate LDPC. The DL EHT-MCS subfield indicates the EHT-MCS of the STA addressed by this EHT variant user information field. The encoding definition of the DL EHT-MCS subfield is found in Section 36.5 of IEEE 802.11be D1.2. The Spatial Stream (SS) Allocation subfield defines one or more spatial streams sent by a shared AP to the STA addressed by this EHT variant user information field. The format of the SS Allocation subfield depends on the number of users multiplexed on the RU or MRU specified by the RU Allocation subfield and the RU Allocation subfield itself. When more than one user is multiplexed on the RU or MRU specified by the RU Allocation subfield and the PS160 subfield, the SS Allocation subfield includes a 4-bit Start Spatial Stream subfield and a 2-bit Spatial Stream Number subfield. The `Start Space Stream` subfield indicates the starting space stream (SSN), and is set to the starting space stream minus 1. The `Space Stream Number` subfield indicates the number of space streams ( ),in, The Space Stream Number subfield is set to the number of space streams minus 1. When only one user is multiplexing on the RU or MRU specified in the RU Allocation subfield and PS160 subfield, the SS Allocation subfield includes a 4-bit Space Stream Number subfield. The Space Stream Number subfield indicates the number of space streams (…). ),in, The space stream number subfield is set to the number of space streams minus 1.

[0070] According to the definition of the exemplary format of the trigger-dependent user information field in the seventh embodiment, as follows: Figure 9B As shown. The AP Participation subfield indicates one or more shared APs in the AP candidate set that will send their respective PSDUs to the STA addressed by the EHT variant user information field. The AP candidate set can be determined based on the TA address of the multi-AP cooperative transmission trigger frame. A value of 1 at the i-th bit position of the AP Participation subfield indicates that the shared AP with AP ID i will send a PSDU to the STA. A value of 0 at the i-th bit position of the AP Participation subfield indicates that the shared AP with AP ID i will not send a PSDU to the STA. The shared APs that will send their respective PSDUs to the STA are numbered consecutively starting from 1 in ascending order of AP ID. For example, if two shared APs with AP IDs 2 and 4 will send their respective PSDUs to the STA, the shared AP with AP ID = 2 is numbered AP1, and the shared AP with AP ID = 4 is numbered AP2. The number of shared APs sending their respective PSDUs to the STA is represented by... Instructions, among which, That is, a maximum of 3 bits in the AP participation subfield can be set to 1. It should be noted that a shared AP can also decide independently to send a PSDU to the STA addressed by the EHT variant user information field. However, when... A shared AP will not send a PSDU to the STA addressed by the EHT variant user information field, because up to three APs can send their own PSDUs to the same STA.

[0071] The single AP flow configuration subfield indicates the number of spatial flows for each shared AP that will send its own PSDU to the STA. When more than one user reuses the RU or MRU specified in the RU allocation subfield and the PS160 subfield, an example encoding of the single AP flow configuration subfield is shown in Table 10.

[0072]

[0073] Table 10 The Single AP Flow Configuration subfield is set to a first value (e.g., 15) to indicate that the shared AP sends one or more of the same spatial flows as indicated by the SS Allocation subfield to the STA. The Single AP Flow Configuration subfield is set to a value different from the first value to indicate that the shared AP sends a different spatial flow to the STA. In this case, the starting flow number for the first shared AP that will send the PSDU to the STA ( )for SSN .when The starting flow number for each remaining shared AP that will send its own PSDU to the STA ( )for: (1).

[0074] When only one user is multiplexed on the RU or MRU specified in the RU allocation subfield and the PS160 subfield, the exemplary encoding of the single AP flow configuration subfield is shown in Table 11.

[0075]

[0076] Table 11 The Single RU / MRU Non-OFDMA User Count subfield indicates the number of STAs multiplexed on the same RU or MRU specified in the RU Allocation subfield and PS160 subfield. This subfield is set to the number of STAs minus 1. The User Location subfield indicates the location of the STA addressed by the EHT Variant User Information field among all STAs multiplexed on the same RU or MRU. The User Location subfield is set to 0 to indicate that the STA addressed by the EHT Variant User Information field is the first among all STAs multiplexed on the same RU or MRU; or it is set to 1 to indicate that the STA addressed by the EHT Variant User Information field is the second among all STAs multiplexed on the same RU or MRU; and so on. According to the seventh embodiment, the EHT Variant User Information fields addressing all STAs multiplexed on the same RU or MRU are placed together in the User Information List field of the Multi-AP Cooperative Transmission Trigger Frame. In this way, when a shared AP identifies an EHT variant user information field addressed to a STA that will send a PSDU, the shared AP can easily identify EHT variant user information fields addressed to one or more other STAs multiplexed on the same RU or MRU. It is important to note that when multiple APs transmit their respective EHT MUPPDUs on the same RU or MRU, each AP needs to know the transmission parameters of each STA multiplexed on the RU or MRU to ensure that the EHT-SIG fields of the transmitted EHT MUPPDUs are identical.

[0077] The Single RU / MRU Multi-AP Cooperative Transmission Flag subfield indicates whether multiple APs will transmit their respective EHT MU PPDUs on the same RU or MRU specified in the RU Assignment subfield and PS160 subfield. The Single RU / MRU Multi-AP Cooperative Transmission Flag subfield is set to a first value (e.g., 0) to indicate that only a single AP will transmit the EHT MU PPDU on the RU or MRU; or it is set to a second value (e.g., 1) to indicate that multiple APs will transmit their respective EHT MU PPDUs on the same RU or MRU. This is determined from the Single User AP Participation subfield. When the value is greater than 1, the Single RU / MRU Multi-AP Cooperative Transmission Flag subfield should be set to indicate that multiple APs will transmit their respective EHT MU PPDUs on the same RU or MRU. In multi-AP joint DL transmission, the Single RU / MRU Multi-AP Cooperative Transmission Flag subfield of each EHT variant user information field should be set to indicate that multiple APs will transmit their respective EHT MU PPDUs on the same RU or MRU. When the Single RU / MRU Multi-AP Cooperative Transmission Flag subfield is set to indicate that only a single AP will transmit the EHT MU PPDU on the RU or MRU specified in the RU allocation subfield and PS160 subfield, the AID12 subfield, DL FEC encoding type subfield, DL EHT-MCS subfield, SS allocation subfield, non-OFDMA user count subfield, and user location subfield in the EHT variant user information field can be retained. In this case, the only AP specified in the AP participation subfield can decide for itself how to transmit the EHT MU PPDU on the RU or MRU (e.g., the scheduled users and transmission parameters for each scheduled user).

[0078] First Example In the first example, it is assumed that in a candidate set of APs, two shared APs, AP ID = 1 and AP ID = 3, participate in a multi-AP joint DL transmission for four STAs (STA1, STA2, STA3, and STA4) on a 320 MHz channel (with the lowest 80 MHz channel punctured). Specifically, the shared AP with AP ID = 1 sends an EHT MU PPDU carrying the first-order stream to STA1, an EHT MU PPDU carrying the third-order stream to STA2, and an EHT MU PPDU carrying the fifth and sixth-order streams to STA3; while the shared AP with AP ID = 3 sends an EHT MU PPDU carrying the second-order stream to STA1, an EHT MU PPDU carrying the fourth-order stream to STA2, and an EHT MU PPDU carrying the seventh and eighth-order streams to STA4. According to the seventh embodiment, in this example, the multi-AP cooperative transmission trigger frame includes four EHT variant user information fields, each addressable to one of the four STAs. For each of the four EHT variant user information fields, the PS160 subfield is set to 0; B0 and B1-B7 of the RU allocation subfield are set to 0 and 104, respectively. For the first EHT variant user information field addressing to STA1, the starting spatial stream subfield is set to 0; the spatial stream count subfield is set to 2; the AP participation subfield is set to 01010000; the single AP stream configuration subfield is set to 0; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user count subfield is set to 3; and the user location subfield is set to 0. For the second EHT variant user information field addressing to STA2, the starting spatial stream subfield is set to 2; the spatial stream count subfield is set to 2; the AP participation subfield is set to 01010000; the single AP stream configuration subfield is set to 0; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user count subfield is set to 3; and the user location subfield is set to 1. For the third EHT variant user information field addressed to STA3, the starting spatial stream subfield is set to 4; the spatial stream number subfield is set to 2; the AP participation subfield is set to 01000000; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user number subfield is set to 3; and the user location subfield is set to 2. For the fourth EHT variant user information field addressed to STA4, the starting spatial stream subfield is set to 6; the spatial stream number subfield is set to 2; the AP participation subfield is set to 00010000; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user number subfield is set to 3; and the user location subfield is set to 3.

[0079] Second example In the second example, it is assumed that in a candidate set of APs, two shared APs, AP ID = 1 and AP ID = 3, participate in multi-AP cooperative DL OFDMA transmission within a 320 MHz channel. Specifically, the shared AP with AP ID = 1 transmits a first EHT MU PPDU in the primary 160 MHz channel, while the shared AP with AP ID = 3 transmits a second EHT MU PPDU in the secondary 160 MHz channel. How the first and second EHT MU PPDUs are transmitted is determined by the shared APs with AP ID = 1 and AP ID = 3. According to the seventh embodiment, in this example, the multi-AP cooperative transmission trigger frame includes two EHT variant user information fields corresponding to the primary 160 MHz channel and the secondary 160 MHz channel, respectively. For the first EHT variant user information field corresponding to the primary 160 MHz channel, the PS160 subfield is set to 1; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; the AP participation subfield is set to 01000000; and the single RU / MRU multi-AP cooperative transmission flag subfield is set to 0. For the second EHT variant user information field corresponding to the secondary 160 MHz channel, the PS160 subfield is set to 0; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; the AP participation subfield is set to 00010000; and the single RU / MRU multi-AP cooperative transmission flag subfield is set to 0.

[0080] Third Example In the third example, it is assumed that in a candidate AP set, three shared APs, AP ID = 1, AP ID = 2, and AP ID = 3, participate in multi-AP cooperative DL OFDMA transmission within a 320 MHz channel. Specifically, the shared AP with AP ID = 1 transmits a first EHT MU PPDU in the primary 160 MHz channel; the shared AP with AP ID = 2 transmits a second EHT MU PPDU carrying a first stream to STA1, and a second EHT MU PPDU carrying a third and fourth stream to STA2; the shared AP with AP ID = 3 transmits a third EHT MU PPDU carrying a second stream to STA1 in the secondary 160 MHz channel. How the first EHT MU PPDU is transmitted is determined by the shared AP with AP ID = 1. According to the seventh embodiment, in this example, the multi-AP cooperative transmission trigger frame includes three EHT variant user information fields. For the first EHT variant user information field corresponding to the primary 160 MHz channel, the PS160 subfield is set to 1; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; the AP participation subfield is set to 01000000; and the single RU / MRU multi-AP cooperative transmission flag subfield is set to 0. For the second EHT variant user information field addressed to STA1, the starting spatial stream subfield is set to 0; the spatial stream number subfield is set to 2; the AP participation subfield is set to 00110000; the single AP stream configuration subfield is set to 0; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user number subfield is set to 1; and the user location subfield is set to 0. For the third EHT variant user information field addressing to STA2, the starting spatial flow subfield is set to 2; the spatial flow number subfield is set to 2; the AP participation subfield is set to 00100000; the single RU / MRU multi-AP cooperative transmission flag subfield is set to 1; the single RU / MRU non-OFDMA user number subfield is set to 1; and the user location subfield is set to 1. For the second or third EHT variant user information field, the PS160 subfield is set to 0; B0 of the RU allocation subfield is set to 1; and B1-B7 of the RU allocation subfield are set to 68.

[0081] Eighth embodiment According to the eighth embodiment, the exemplary format of the EHT variant user information field is defined as follows: Figure 10A As shown. An exemplary format definition for the user information field that triggers the dependency is as follows: Figure 10BAs shown. According to the eighth embodiment, the value of the VAID12 subfield of the EHT variant user information field is used to indicate whether multiple APs will transmit their respective EHT MU PPDUs on the RU or MRU specified in the RU allocation subfield and PS160 subfield. A VAID equal to the first value in [1 2006] (e.g., 2006) must not be assigned to any STA. The VAID12 subfield of the EHT variant user information field is set to the first value in [1 2006] to indicate that only a single shared AP will transmit the EHT MU PPDU on the RU or MRU specified in the RU allocation subfield and PS160 subfield. The VAID12 subfield of the EHT variant user information field is set to a value in [1 2006] that is not equal to the first value to indicate that multiple APs will transmit the EHT MU PPDU on the RU or MRU specified in the RU allocation subfield and PS160 subfield. In this case, the value of the VAID12 subfield of the EHT variant user information field also indicates the STA whose VAID is equal to the value of the VAID12 subfield. When the VAID12 subfield of the EHT variant user information field is set to the first value in [1 2006], the remaining subfields of the EHT variant user information field, except for the RU allocation subfield, PS160 subfield, and AP participation subfield, are retained. The RU allocation subfield and PS160 subfield, as well as the DLBW subfield of the EHT variant public information field and the DLBW extended subfield of the special user information field, indicate the size and location of the RU or MRU assigned to a single shared AP; the AP participation subfield indicates the shared AP.

[0082] Fourth example In the fourth example, it is assumed that in a candidate set of APs, two shared APs, AP ID = 1 and AP ID = 3, participate in multi-AP cooperative DL OFDMA transmission within a 320 MHz channel. Specifically, the shared AP with AP ID = 1 transmits a first EHT MU PPDU in the primary 160 MHz channel, while the shared AP with AP ID = 3 transmits a second EHT MU PPDU in the secondary 160 MHz channel. How the first and second EHT MU PPDUs are transmitted is determined by the shared APs with AP ID = 1 and AP ID = 3. According to the eighth embodiment, in this example, the multi-AP cooperative transmission trigger frame includes two EHT variant user information fields corresponding to the primary 160 MHz channel and the secondary 160 MHz channel, respectively. For the first EHT variant user information field corresponding to the primary 160 MHz channel, the VAID12 subfield is set to the first value (e.g., 2006); the PS160 subfield is set to 1; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; and the AP participation subfield is set to 01000000. For the second EHT variant user information field corresponding to the secondary 160 MHz channel, the VAID12 subfield is set to the first value (e.g., 2006); the PS160 subfield is set to 0; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; and the AP participation subfield is set to 00010000.

[0083] Fifth example In the fifth example, it is assumed that in a candidate AP set, three shared APs, AP ID = 1, AP ID = 2, and AP ID = 3, participate in multi-AP cooperative DL OFDMA transmission within a 320 MHz channel. Specifically, the shared AP with AP ID = 1 transmits a first EHT MU PPDU in the primary 160 MHz channel; the shared AP with AP ID = 2 transmits a second EHT MU PPDU carrying a first stream to STA1 and a second EHT MU PPDU carrying a third and fourth stream to STA2; the shared AP with AP ID = 3 transmits a third EHT MU PPDU carrying a second stream to STA1 in the secondary 160 MHz channel. How the first EHT MU PPDU is transmitted is determined by the shared AP with AP ID = 1. According to the eighth embodiment, in this example, the multi-AP cooperative transmission trigger frame includes three EHT variant user information fields. For the first EHT variant user information field corresponding to the primary 160 MHz channel, the VAID12 subfield is set to the first value (e.g., 2006); the PS160 subfield is set to 1; B0 of the RU allocation subfield is set to 1; B1-B7 of the RU allocation subfield are set to 68; and the single-user AP participation subfield is set to 01000000. For the second EHT variant user information field addressed to STA1, the starting spatial stream subfield is set to 0; the spatial stream count subfield is set to 2; the AP participation subfield is set to 00110000; the single AP stream configuration subfield is set to 0; the single RU / MRU non-OFDMA user count subfield is set to 1; and the user location subfield is set to 0. For the third EHT variant user information field addressed to STA2, the starting spatial stream subfield is set to 2; the spatial stream count subfield is set to 2; the AP participation subfield is set to 00100000; the single RU / MRU non-OFDMA user count subfield is set to 1; and the user location subfield is set to 1. For the second or third EHT variant user information field, the PS160 subfield is set to 0; B0 of the RU allocation subfield is set to 1; and B1-B7 of the RU allocation subfield are set to 68.

[0084] Figure 11An example of a wireless communication system provided in an embodiment of this disclosure is shown. The wireless communication system may be an example of a WLAN 100 (also referred to as a Wi-Fi network) configured according to various aspects of this disclosure (such as a next-generation, next-big-thing (NBT), ultra-high throughput (UHT), or EHT Wi-Fi network). As described herein, the terms “next-generation,” “NBT,” “UHT,” and “EHT” may be considered synonyms and may each correspond to a Wi-Fi network supporting a large-capacity space-time stream. The WLAN 100 may include an AP 10 and multiple associated STAs 20, which may represent mobile stations, personal digital assistants (PDAs), other handheld devices, netbooks, laptops, tablets, laptop computers, display devices (such as televisions, computer monitors, etc.), printers, and other devices. The AP 10 and associated stations 20 may represent a basic service set (BSS) or an extended service set (ESS). The various STAs 20 in the network are able to communicate with each other through the AP 10. The diagram also shows the coverage area 110 of AP 10, which may represent the basic service area (BSA) of WLAN 100. Extended network sites (not shown) associated with WLAN 100 can connect to a wired or wireless distributed system that allows multiple AP 10s to be connected in an ESS or VBSS.

[0085] In some embodiments, STA 20 may be located at the intersection of more than one coverage area 110 and may be associated with more than one AP 10. A single AP 10 and a group of associated STA 20 may be referred to as a BSS. An ESS or VBSS is a group of connected BSSs. A distributed system (not shown) may be used to connect AP 10s in an ESS or VBSS. In some cases, the coverage area 110 of AP 10 may be divided into sectors (also not shown). WLAN 100 may include different types of AP 10 (such as metropolitan area networks, home networks, etc.), and the coverage areas 110 of different types of AP 10 are different and overlap. Two STA 20 may also communicate directly via a direct wireless link 125, regardless of whether the two STA 20 are in the same coverage area 110. Examples of direct wireless links 125 may include Wi-Fi direct connections, Wi-Fi tunneled direct link setup (TDLS) links, and other packet connections. STA 20 and AP 10 can communicate using WLAN radio and baseband protocols at the physical and media access control (MAC) layers according to IEEE 802.11 and versions including but not limited to 802.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11ax, and 802.11ay. In some other implementations, point-to-point connections or ad hoc networks can be implemented within WLAN 100.

[0086] Figure 12 An example of a wireless communication system provided in another embodiment of this disclosure is shown. The wireless communication system 200 may be an example of a next-generation or EHT Wi-Fi system, and may include AP 10-a, STA 20-a, STA 20-b, and coverage area 110-a. AP 10-a, STA 20-a, STA 20-b, and coverage area 110-a may be... Figure 12 Example of a component described. AP 10-a can send a DL PPDU 210 (e.g., EHT MU PPDU) including an RU allocation table indication 215 to STA 20 on downlink 205.

[0087] In some implementations, the wireless communication system 200 can be a next-generation Wi-Fi system (e.g., an EHT system). In some implementations, the wireless communication system 200 can also support multiple communication systems. For example, the wireless communication system 200 can support both EHT and HE communication. In some implementations, STA 20-a and STA 20-b can be different types of STAs. For example, STA 20-a can be an example of an EHT STA, while STA 20-b can be an example of an HE STA. STA 20-b can be referred to as a traditional STA.

[0088] In some instances, EHT communication can support significantly larger bandwidths than traditional communication. For example, EHT communication can occur on an available bandwidth of 320 MHz, while traditional communication may occur on an available bandwidth of 160 MHz. Furthermore, EHT communication can support higher modulation levels compared to traditional communication. For instance, EHT communication can support 4K quadrature amplitude modulation (QAM), while traditional communication can support 1024 QAM. EHT communication can support more spatial streams compared to traditional systems. In a non-limiting example, EHT communication can support 16 spatial streams, while traditional communication can support 8. In some cases, EHT communication can utilize unlicensed spectrum channels of 2.4 GHz, 5 GHz, or 6 GHz.

[0089] Figure 13 An example of a wireless communication system provided in another embodiment of this disclosure is shown. Wireless communication system 300 may be an example of a post-EHT Wi-Fi system and may include AP 10-b. AP 10-b may be an example of a post-EHT AP 10. Wireless communication system 300 may include HE STA 20-c, EHT STA 20-d, post-EHT STA 20-e, and coverage area 110-b, which may be... Figure 4 and Figure 5 Example of a component described. AP 10-b can send a DL PPDU 310, including an RU allocation table indication 315, to STA 20 on downlink 305. In some implementations, STA 20 may be referred to as a client.

[0090] Figure 14 The illustration shows the communication configuration of one or more STA 20s, one AP 10, and one AP 30 in a wireless communication system 700, as provided in an embodiment of this disclosure. Figure 14As shown, the wireless communication system 700 includes an AP 10, an AP 30, and one or more STAs 20. AP 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. AP 30 may include a memory 32, a transceiver 33, and a processor 31 coupled to the memory 32 and the transceiver 33. One or more STAs 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. Processors 11, 21, or 31 may be configured to implement the proposed functions, procedures, and / or methods described in this specification. Multilayer radio interface protocols may be executed in processors 11, 21, or 31. Memory 12, 22, or 32 is operatively coupled to processors 11, 21, or 31 and stores various information for operating processors 11, 21, or 31. Transceiver 13, 23, or 33 is operatively coupled to processor 11, 21, or 31, and transceiver 13, 23, or 33 transmits and / or receives radio signals.

[0091] Processors 11, 21, or 31 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. Memory 12, 22, or 32 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceivers 13, 23, or 33 may include baseband circuitry for processing radio frequency signals. When the above embodiments are implemented in software, the techniques described herein can be implemented by modules (e.g., processes, functions, etc.) that perform the functions described herein. These modules can be stored in memory 12, 22, or 32 and executed by processor 11, 21, or 31. Memory 12, 22, or 32 can be implemented internally or externally to processor 11, 21, or 31. When implemented externally to processor 11, 21, or 31, memory 12, 22, or 32 can be communicatively connected to processor 11, 21, or 31 in various ways known in the art.

[0092] In some embodiments, transceiver 13 is configured to send a trigger frame to one or more shared APs 30 via AP 10, which acts as a shared AP, to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission to one or more shared APs in a multi-AP cooperative downlink (DL) transmission. The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for the multi-AP cooperative DL transmission. This solves the problems existing in the prior art, effectively realizes multi-AP downlink (DL) cooperation in a multi-AP system, achieves extremely high throughput, and provides good communication performance and / or high reliability.

[0093] In some embodiments, transceiver 33 is configured to receive a trigger frame from AP 10, which is also a shared AP, as AP 30 being the shared AP. The trigger frame is used to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission from one or more shared APs, including the shared AP, in a multi-AP cooperative downlink (DL) transmission. The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for multi-AP cooperative DL transmission. This solves the problems existing in the prior art, effectively realizes multi-AP downlink (DL) cooperation in a multi-AP system, achieves extremely high throughput, and provides good communication performance and / or high reliability.

[0094] In some embodiments, the access point (AP) 10 includes a transmitting unit (e.g., Figure 14 The figure (reference numeral 13) is configured to send Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Units (PPDUs) to one or more stations (STAs), wherein the EHT MU PPDU includes a Basic Service Set (BSS) / Virtual BSS (VBSS) color subfield in the Universal Signaling (U-SIG) field. The BSS / VBSS color subfield in the U-SIG field indicates the BSS color of the AP or the VBSS color of the AP candidate set to which the AP belongs.

[0095] In some embodiments, the station (STA) 20 includes a receiving unit (e.g., Figure 14The figure (reference numeral 23) is configured to receive Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Units (PPDUs) from an Access Point (AP), wherein the EHT MU PPDU includes a Basic Service Set (BSS) / Virtual BSS (VBSS) color subfield in the Universal Signaling (U-SIG) field. The BSS / VBSS color subfield in the U-SIG field indicates the BSS color of the AP or the VBSS color of the AP candidate set to which the AP belongs.

[0096] Figure 15 A wireless communication method 800 performed by an AP according to an embodiment of this disclosure is illustrated. In some embodiments, the method 800 includes: block 802, wherein the AP, as a sharing AP, sends a trigger frame to one or more shared APs to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission in a multi-AP cooperative downlink (DL) transmission, wherein the trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields; the DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for the multi-AP cooperative DL transmission. This solves the problems existing in the prior art, effectively realizes multi-AP downlink (DL) cooperation in a multi-AP system, achieves extremely high throughput, and provides good communication performance and / or high reliability.

[0097] Figure 16 A wireless communication method 900 performed by an AP according to an embodiment of this disclosure is illustrated. In some embodiments, the method 900 includes: block 902, wherein the AP, as a shared AP, receives a trigger frame from another AP, which is also a shared AP. The trigger frame is used to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission to one or more shared APs, including the AP itself, in a multi-AP cooperative downlink (DL) transmission. The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for the multi-AP cooperative DL transmission. This solves the problems existing in the prior art, effectively realizes multi-AP downlink (DL) cooperation in a multi-AP system, achieves extremely high throughput, and provides good communication performance and / or high reliability.

[0098] In some embodiments, the TA field of the triggering frame is set to the Virtual Basic Service Set Identifier (VBSSID) of the VBSS associated with multi-AP cooperative DL transmission. In some embodiments, if one or more shared APs comprise a single AP, the RA field of the triggering frame is set to the AP's BSS Identifier (BSSID); otherwise, the RA field of the triggering frame is set to the broadcast address. In some embodiments, the EHT variant public information field includes a DL length subfield indicating the value of the non-HT signal field (L-SIG) length field of the requested EHT MU PPDU. In some embodiments, the EHT variant public information field includes a Required CS subfield indicating whether one or more shared APs are required to use Energy Detection (ED) to sense the medium, and taking into account the medium state and network allocation vector (NAV) when determining whether to transmit the requested EHT MU PPDU.

[0099] In some embodiments, the EHT variant public information field includes a guard interval (GI) and an EHT long training field (EHT-LTF) type subfield, as well as an EHT-LTF symbol number subfield. The GI, EHT-LTF type subfield, and EHT-LTF symbol number subfield respectively indicate the values ​​of the GI, EHT-LTF type subfield, and EHT-LTF symbol number field of the EHT-SIG field of the requested EHT MU PPDU. In some embodiments, the EHT variant public information field includes a low-density parity-check code (LDPC) extra symbol segment subfield, a forward pre-error correction (pre-FEC) padding factor subfield, and a packet extension field (PE) disambiguation subfield. The LDPC extra symbol segment field, pre-FEC padding factor subfield, and PE disambiguation subfield respectively indicate the values ​​of the LDPC extra symbol segment field, pre-FEC padding factor field, and PE disambiguation field of the EHT-SIG field of the requested EHT MU PPDU. In some embodiments, the special user information field includes an EHT space reuse subfield, which carries a value contained in the space reuse subfield of the EHT-SIG field of the requested EHT MU PPDU.

[0100] In some embodiments, the special user information field or EHT variant public information field includes a multi-AP cooperative transmission type subfield, which indicates the type of multi-AP cooperative DL transmission. In some embodiments, the special user information field or EHT variant public information field includes an EHT-SIG symbol number subfield and an EHT-SIG MCS subfield, which respectively indicate the values ​​of the EHT-SIG symbol number subfield and the EHT-SIG modulation and coding scheme (MCS) subfield of the U-SIG field of the requested EHT MU PPDU. In some embodiments, the special user information field or EHT variant public information field includes a U-SIG / EHT-SIG ignore and verify subfield, which indicates the values ​​of the ignore and verify subfields of the U-SIG field and the public field for non-orthogonal frequency division multiple access (OFDMA) transmission of the EHT-SIG field of the requested EHT MU PPDU.

[0101] In some embodiments, the special user information field or EHT variant public information field includes a pre-EHT preamble presence subfield, which indicates whether a pre-EHT modulation field exists in the requested EHT MU PPDU. In some embodiments, the public information field includes: a puncturing channel information subfield, which indicates the puncturing channel information of the requested EHT MU PPDU; and a puncturing channel information size subfield, which indicates that the size of the puncturing channel information subfield is 0 bits, 8 bits, or 16 bits. In some embodiments, the absence of the puncturing channel information subfield indicates that no 20 MHz channel has been punctured from the cooperative transmission bandwidth. In some embodiments, the 8-bit puncturing channel information subfield includes a 5-bit subfield, which indicates the puncturing channel information of the cooperative transmission bandwidth. In some embodiments, the 8-bit or 16-bit puncturing channel information subfield includes two or four 4-bit subfields, each 4-bit subfield indicating the puncturing channel information of an 80 MHz frequency subblock. In some embodiments, the special user information field includes a 16-bit punctured channel information subfield, which indicates the punctured channel information of the requested EHT MU PPDU. In some embodiments, the punctured channel information subfield includes a 5-bit subfield, which indicates the punctured channel information of the cooperative transmission bandwidth. In some embodiments, the punctured channel information subfield includes four 4-bit subfields, each indicating the punctured channel information of an 80 MHz frequency subblock. In some embodiments, when the cooperative transmission bandwidth is 160 MHz, each of two of the four 4-bit subfields corresponding to the third lowest and highest 80 MHz frequency subblocks is either reserved or set to 0.

[0102] In some embodiments, each EHT variant user information field includes: a Single Resource Unit (RU) / Multiple Resource Unit (MRU) Multi-AP Cooperative Transmission Flag subfield, which indicates whether multiple APs are transmitting their respective EHT MU PPDUs on the same RU or MRU; and a VAID12 subfield, which indicates STAs whose VAID is equal to the value of the VAID12 subfield. In some embodiments, each EHT variant user information field includes a VAID12 subfield, which indicates whether multiple APs are transmitting their respective EHT MU PPDUs on the same RU or MRU. In some embodiments, the VAID12 subfield is set to a first value in [1 2006] to indicate that only a single AP is transmitting an EHT MU PPDU on the RU or MRU; or is set to a value in [1 2006] that is not equal to the first value to indicate that multiple APs are transmitting their respective EHT MU PPDUs on the RU or MRU and to indicate STAs whose VAID is equal to the value of the VAID12 subfield. In some embodiments, each EHT variant user information field includes an SS allocation subfield, the format of which depends on the number of STAs multiplexed to the same RU or MRU. In some embodiments, when only a single STA is multiplexed to an RU or MRU, the SS allocation subfield includes a spatial flow count subfield, indicating the number of spatial flows used by the STA. In some embodiments, when more than one STA is multiplexed to an RU or MRU, the SS allocation subfield includes: a starting spatial flow subfield, indicating the starting spatial flow used by the STA; and a spatial flow count subfield, indicating the number of spatial flows used by the STA. In some embodiments, each EHT variant user information field includes an AP participation subfield, indicating one or more shared APs that send their respective PSDUs to the same STA. In some embodiments, a value of 1 for the i-th bit of the AP participation subfield indicates that the shared AP with AP ID i sends a Physical Layer Service Data Unit (PSDU) to the STA; a value of 0 for the i-th bit of the AP participation subfield indicates that the shared AP with AP ID i does not send a PSDU to the STA. In some embodiments, one or more shared APs are numbered consecutively in ascending order of AP ID.

[0103] In some embodiments, the number of one or more APs is at most three. In some embodiments, each EHT variant user information field includes a single AP flow configuration subfield, which indicates the number of spatial flows sent by each of the one or more shared APs to the STA. In some embodiments, the format of the single AP flow configuration subfield depends on the number of STAs multiplexed to the same RU or MRU. In some embodiments, the single AP flow configuration subfield is set to a first value to indicate that the shared APs send one or more identical spatial flows to the STA; or it is set to a value different from the first value to indicate that the shared APs send different spatial flows to the STA. In some embodiments, each EHT variant user information field includes a single RU / MRU non-OFDMA user count subfield, which indicates the number of STAs multiplexed to the same RU or MRU. In some embodiments, each EHT variant user information field includes a user location subfield, which indicates the location of the STA addressed by the EHT variant user information field among all STAs multiplexed to the same RU or MRU. In some embodiments, the EHT variant user information fields addressing all STAs multiplexed to the same RU or MRU are placed together in the user information list field of the trigger frame.

[0104] Figure 17 This is a block diagram of an access point (AP) 1400 provided in an embodiment of this disclosure. The AP 1400 includes a transmitting unit 1402 configured to send a trigger frame to one or more shared APs to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission to one or more shared APs in a multi-AP cooperative downlink (DL) transmission. The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW for multi-AP cooperative DL transmission. This addresses the problems of the prior art, effectively implementing multi-AP DL cooperation in a multi-AP system, achieving EHT, and providing good communication performance and / or high reliability.

[0105] Figure 18This is a block diagram of an AP 1500 provided in an embodiment of this disclosure. AP 1500 includes a receiving unit 1502 configured to receive a trigger frame from another AP, also a shared AP, in a multi-AP cooperative downlink (DL) transmission. The trigger frame is used to request Extremely High Throughput (EHT) Multi-User (MU) Physical Layer Protocol Data Unit (PPDU) transmission from one or more shared APs, including this AP, in a multi-AP cooperative downlink (DL) transmission. The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The DL bandwidth (BW) subfield of the EHT variant common information field and the DL BW extension subfield of the special user information field indicate the cooperative transmission BW used for multi-AP cooperative DL transmission. This addresses the problems of the prior art, effectively implementing multi-AP DL cooperation in a multi-AP system, achieving EHT, and providing good communication performance and / or high reliability.

[0106] Some embodiments offer the following commercial benefits: 1. Solving problems in the prior art. 2. Efficiently implementing multi-AP downlink (DL) collaboration in multi-AP systems. 3. Achieving extremely high throughput. 4. Providing excellent communication performance. 5. Providing high reliability. 6. Chipset suppliers, communication system development suppliers, vehicle manufacturers (including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc.), drones (unmanned aerial vehicles), smartphone manufacturers, communication equipment manufacturers for public safety, and AR / VR device manufacturers for gaming, conferences / seminars, education, and other purposes are all using some embodiments of this disclosure. Some embodiments of this disclosure are combinations of "technologies / processes" that can be adopted in communication specifications and / or communication standards (e.g., IEEE specifications and / or standards) to create a final product. Some embodiments of this disclosure propose technical mechanisms.

[0107] Figure 19 This is a block diagram of an exemplary wireless communication system 700 provided for embodiments of this disclosure. The embodiments described herein can be implemented in the system using any suitably configured hardware and / or software. Figure 19System 700 is shown, including at least the following interconnected components: radio frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory / storage 740, display 750, camera 760, sensor 770, and input / output (I / O) interface 780. Application circuitry 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors). The processor may be coupled to memory / storage and used to execute instructions stored in memory / storage to enable various applications and / or operating systems to run on the system.

[0108] The baseband circuit 720 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various radio control functions for communicating with one or more radio networks via RF circuitry. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry can support communication with the evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN). Embodiments in which the baseband circuitry is configured to support radio communication using more than one wireless protocol may be referred to as a multi-mode baseband circuitry.

[0109] In various embodiments, baseband circuitry 720 may include circuitry to operate signals that are not strictly speaking baseband frequencies. For example, in some embodiments, baseband circuitry may include circuitry to operate signals having an intermediate frequency between the baseband frequency and a radio frequency. RF circuitry 710 can communicate with a wireless network using modulated electromagnetic radiation via a non-solid-state medium. In various embodiments, RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with a wireless network. In various embodiments, RF circuitry 710 may include circuitry to operate signals that are not strictly speaking radio frequencies. For example, in some embodiments, RF circuitry may include circuitry for operating signals having an intermediate frequency between the baseband frequency and a radio frequency.

[0110] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above in conjunction with AP or STA may be wholly or partially embodied in one or more circuits within the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, “circuit” may refer to or include, or be a part of, application-specific integrated circuits (ASICs), electronic circuitry, processors (shared, dedicated, or grouped) and / or memories (shared, dedicated, or grouped), combinational logic circuitry, and / or other suitable hardware components that provide the described functionality. In some embodiments, electronic device circuitry may be implemented by one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all components of the baseband circuitry, application circuitry, and / or memory / storage may be implemented together in a system on a chip (SOC). Memory / storage 740 may be used to load and store data and / or instructions, for example, for a system. The memory / storage of one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory, DRAM) and / or non-volatile memory (e.g., flash memory).

[0111] In various embodiments, I / O interface 780 may include: one or more user interfaces designed to enable user interaction with the system; and / or peripheral component interfaces designed to enable peripheral components to interact with the system. User interfaces may include, but are not limited to, physical keyboards or keypads, touchpads, speakers, microphones, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal serial bus (USB) ports, audio jacks, and power interfaces. In various embodiments, sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information relevant to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. Positioning units may also be part of or interact with baseband and / or RF circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0112] In various embodiments, display 750 may include a display, such as a liquid crystal display (LCD) and a touchscreen display. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, smartphone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium (e.g., a non-transitory storage medium).

[0113] Those skilled in the art will understand that each unit, algorithm, and step described and disclosed in the embodiments of this disclosure is implemented through electronic hardware or a combination of computer software and electronic hardware. Whether the function runs in hardware or software depends on the application conditions and the design requirements of the technical plan. Those skilled in the art can implement the function in different ways for each specific application, and these implementations should not exceed the scope of this disclosure. Those skilled in the art will understand that since the workflows of the above-described systems, devices, and units are substantially the same, the workflows of the systems, apparatuses, and units in the above embodiments can be referred to. For ease of description and simplification, these workflows will not be described in detail.

[0114] It is understood that the systems, devices, and methods disclosed in the embodiments of this disclosure can be implemented in other ways. The above embodiments are merely examples. The above division of units is based solely on logical function; other divisions may exist during implementation. Multiple units or components may be combined or integrated into another system. Certain features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed are all operated indirectly or communicatively through some ports, devices, or units in an electrical, mechanical, or other form. The units explained as separating components may or may not be physically separated. The shown units may or may not be physical units, i.e., located in one place or distributed across multiple network units. Some or all of the units are used according to the purposes of this embodiment. Furthermore, each functional unit in each embodiment can be integrated into a processing unit, or physically independent, or integrated into a processing unit having two or more units.

[0115] If the software functional units are implemented, used, and sold as a product, then the software functional units can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this disclosure can be implemented substantially or partially in the form of a software product. Alternatively, a portion of a technical solution that benefits from conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium and includes multiple commands for a computing device (e.g., a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this disclosure. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other media capable of storing program code.

[0116] While this disclosure has been described in conjunction with what are considered to be the most practical and preferred embodiments, it is to be understood that this disclosure is not limited to the disclosed embodiments, but is intended to cover various configurations made without departing from the broadest interpretation of the appended claims.

Claims

1. A wireless communication method implemented through an access point (AP), comprising: The AP, acting as the sharing AP, sends a trigger frame to the shared AP to request ultra-high throughput EHT multi-user MU physical layer protocol data unit (PPDU) transmission in the multi-AP cooperative downlink (DL) transmission. The shared AP sends one EHT MU PPDU to one or more STAs within SIFS after receiving the trigger frame, and the sharing AP sends another EHT MU PPDU within SIFS after sending the trigger frame.

2. The wireless communication method according to claim 1, characterized in that, The transmitter address (TA) field of the trigger frame is set to the Virtual Basic Service Set Identifier (VBSSID) of the Virtual Basic Service Set (VBSS) associated with the multi-AP cooperative DL transmission.

3. The wireless communication method according to claim 1 or 2, characterized in that, If the one or more shared APs include a single AP, the receiver address (RA) field of the trigger frame is set to the basic service set identifier (BSSID) of that AP; otherwise, the RA field of the trigger frame is set to the broadcast address.

4. The wireless communication method according to any one of claims 1 to 3, characterized in that, The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The EHT variant common information field includes a DL length subfield, which indicates the value of the non-HT signal field L-SIG length field of the requested EHT MU PPDU.

5. The wireless communication method according to any one of claims 1 to 4, characterized in that, The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The EHT variant common information field includes a guard interval (GI) and an EHT long training field (EHT-LTF type subfield). The GI and EHT-LTF type subfield indicate the value of the GI+LTF size subfield of the EHT-SIG field of the requested EHT MU PPDU. Wherein, when the GI and EHT-LTF type subfields are set to the first value, indicator 2 EHT-LTF +0.8 µs GI; or, When the GI and EHT-LTF type subfields are set to the second value, indicator 2 EHT-LTF + 1.6 µsGI; or, When the GI and EHT-LTF type subfields are set to a third value, indicator 4 EHT-LTF + 3.2 µsGI.

6. The wireless communication method according to any one of claims 1 to 5, characterized in that, The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields. The special user information field or the EHT variant common information field includes an EHT-SIG symbol number subfield. The EHT-SIG symbol number subfield indicates the value of the EHT-SIG symbol number subfield of the U-SIG field of the requested EHT MU PPDU, and the EHT-SIG symbol number subfield is set to the value of the EHT-SIG symbol number minus 1.

7. The wireless communication method according to any one of claims 1 to 6, characterized in that, Each EHT variant user information field includes: a single resource unit (RU) / multiple resource unit (MRU) multi-AP cooperative transmission flag subfield, which indicates whether multiple APs are transmitting their respective EHT MU PPDUs on the same RU or MRU; and a VAID12 subfield, which indicates the STA whose VAID is equal to the value of the VAID12 subfield.

8. The wireless communication method according to any one of claims 1 to 6, characterized in that, Each EHT variant user information field includes a VAID12 subfield, which indicates whether multiple APs are transmitting their respective EHT MU PPDUs on the same RU or MRU.

9. The wireless communication method according to claim 8, characterized in that, The VAID12 subfield is set to the first value in [12006] to indicate that only a single AP transmits an EHT MU PPDU on the RU or MRU; or is set to a value in [12006] that is not equal to the first value to indicate that multiple APs transmit their respective EHT MU PPDUs on the RU or MRU and to indicate the STA whose VAID is equal to the value of the VAID12 subfield.

10. The wireless communication method according to claim 1, characterized in that, The method further includes: The shared AP sends a first frame to one or more shared APs. The first frame is used to initiate multi-AP cooperation and query the respective intentions of each AP to participate in the multi-AP cooperation. The sharing AP receives a second frame sent by one or more shared APs, the second frame being used to indicate whether the shared AP that sent the second frame intends to participate in the multi-AP cooperation.

11. The wireless communication method according to claim 1, characterized in that, The trigger frame includes an EHT variant common information field, a special user information field, and one or more EHT variant user information fields; The DL BW subfield of the EHT variant public information field and the DL BW extended subfield of the special user information field together indicate the cooperative transmission bandwidth of multi-AP cooperative DL transmission.

12. The wireless communication method according to claim 11, characterized in that, The cooperative transmission bandwidth is the same as or within the width of the shared AP's BSS working channel.

13. The wireless communication method according to claim 1, characterized in that, The U-SIG field of the transmitted EHT MU PPDU has the same content, and the EHT-SIG field of the transmitted EHT MU PPDU has the same content.

14. An access point (AP), comprising: Memory; transceiver; as well as The processor, coupled to the memory and the transceiver, The processor is configured to perform the method according to any one of claims 1 to 13.

Images