WO2025236304A1 - 无线通信方法以及通信设备 - Google Patents

无线通信方法以及通信设备

Info

Publication number
WO2025236304A1
WO2025236304A1 PCT/CN2024/094079 CN2024094079W WO2025236304A1 WO 2025236304 A1 WO2025236304 A1 WO 2025236304A1 CN 2024094079 W CN2024094079 W CN 2024094079W WO 2025236304 A1 WO2025236304 A1 WO 2025236304A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
information
mode
duration
frame
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/094079
Other languages
English (en)
French (fr)
Inventor
康乐
罗朝明
柏年鹤
侯蓉晖
卢刘明
李雅璞
高宁
张军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2024/094079 priority Critical patent/WO2025236304A1/zh
Publication of WO2025236304A1 publication Critical patent/WO2025236304A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools

Definitions

  • This application relates to the field of communication technology, and more specifically, to a wireless communication method and a communication device.
  • M-AP collaboration allows multiple access points (APs) to cooperate in performing communication processes. For example, multiple APs participating in M-AP collaboration can share transmission resources to improve transmission resource utilization.
  • This application provides a wireless communication method and a communication device. The various aspects covered by this application are described below.
  • a wireless communication method comprising: a first access point (AP) receiving first information; wherein the first information is related to a first mode of a first device, the first device including a second AP and/or a station (STA) associated with the second AP.
  • AP access point
  • STA station
  • a wireless communication method comprising: a first device sending first information to a first access point (AP); wherein the first information is related to a first mode of the first device, and the first device includes a second AP and/or a STA associated with the second AP.
  • AP access point
  • a communication device which is a first AP.
  • the communication device includes: a receiving unit for receiving first information; wherein the first information is related to a first mode of the first device, and the first device includes a second AP and/or a STA associated with the second AP.
  • a communication device which is a first device.
  • the communication device includes: a transmitting unit for transmitting first information to a first AP; wherein the first information is related to a first mode of the first device, and the first device includes a second AP and/or a STA associated with the second AP.
  • a communication device including a processor and a memory, the memory for storing one or more computer programs, the processor for calling the computer programs in the memory to enable some or all of the steps of the methods described in the preceding aspects of the communication device.
  • embodiments of this application provide a communication system that includes the aforementioned communication device.
  • the system may further include other devices that interact with the communication device as described in the embodiments of this application.
  • embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.
  • embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects.
  • the computer program product may be a software installation package.
  • embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.
  • an AP can obtain information related to the first mode of another AP (i.e., the second AP) and/or the STA associated with another AP, thereby conducting the M-AP collaboration process in a targeted manner. This allows for more reasonable arrangement or scheduling of M-AP collaboration, enabling it to achieve the expected results.
  • Figure 1 is a schematic diagram of the wireless communication system used in the embodiments of this application.
  • Figure 2A is an example of a network topology for multi-AP collaboration.
  • Figure 2B is an example of a multi-AP collaboration scenario.
  • Figure 2C is an example of another multi-AP collaboration scenario.
  • Figure 2D is a schematic diagram of an M-AP collaboration framework.
  • Figure 3A is an example of the cooperative bandwidth in a coordinated orthogonal frequency division multiple access (C-OFDMA) transmission.
  • C-OFDMA coordinated orthogonal frequency division multiple access
  • Figure 3B is a schematic flowchart of C-OFDMA transmission.
  • Figure 4 is an example of cooperative uplink multi-user multiple input multiple output (UL MU-MIMO) transmission.
  • Figure 5A is an example diagram of cooperative beamforming/zeroing.
  • Figure 5B is an example diagram of an explicit channel state information (CSI) collection process.
  • CSI channel state information
  • Figure 6 is an example diagram of collaborative space reuse.
  • Figure 7 is an example diagram of multi-AP joint transmission.
  • FIG. 8A is an example diagram of coordinated time division multiple access (C-TDMA).
  • Figure 8B is an example diagram of a C-TDMA process in the case of a shared AP.
  • Figure 8C is an example diagram of the C-TDMA process in the case of multiple shared APs.
  • Figure 9A is a schematic diagram of a dynamic energy-saving operation process.
  • Figure 9B is a schematic diagram of a dynamic energy-saving operation process.
  • Figure 10 is a schematic flowchart of a wireless communication method provided in an embodiment of this application.
  • Figure 11A is an example diagram of a first information transmission process.
  • Figure 11B is an example diagram of another first information transmission process.
  • Figure 12A is an example diagram of the transmission process of the first frame.
  • Figure 12B is an example diagram of another first frame transmission process.
  • Figure 13 is an example diagram of a C-OFDMA process provided in an embodiment of this application.
  • Figure 14A is an example diagram of a C-BF process provided in an embodiment of this application.
  • Figure 14B is an example diagram of another C-BF process provided in the embodiments of this application.
  • Figure 15A is an example diagram of a J-TX process provided in an embodiment of this application.
  • Figure 15B is another example diagram of the J-TX process provided in the embodiments of this application.
  • Figure 16A is an example diagram of a C-TDMA process provided in an embodiment of this application.
  • Figure 16B is an example diagram of another C-TDMA process provided in an embodiment of this application.
  • Figure 17 is an example diagram of a C-OFDMA process provided in an embodiment of this application.
  • Figure 18 is a format example diagram of an EHT MAC capability information field provided in an embodiment of this application.
  • Figure 19 is a format example diagram of an M-AP collaborative information element.
  • Figure 20 is an example of the format of a collaborative M-AP parameter information field.
  • Figure 21 is a format example of the EHT operation parameter field in the EHT operation element.
  • Figure 22 is a sample diagram of the DPS frame format.
  • Figure 23 is a sample format diagram of the DPS control field.
  • Figure 24 shows an example of the format of the DPS switching information field.
  • Figure 25 is a schematic diagram of the format of the user information field in the trigger frame provided in the embodiment of this application.
  • Figure 26 is a schematic diagram of the format of the common information field in the MU-RTS frame provided in the embodiment of this application.
  • Figure 27A is a schematic diagram of the user information field format in the MU-RTS frame provided in the embodiment of this application.
  • FIG. 27B is a schematic diagram of the format of a MU-RTS (TXS) frame provided in an embodiment of this application.
  • TXS MU-RTS
  • FIG. 27C is a schematic diagram of the format of the common information field of a MU-RTS (TXS) frame.
  • Figure 27D is a schematic diagram of the format of the user information field in a MU-RTS (TXS) frame.
  • Figure 28 is a schematic structural diagram of a communication device provided in an embodiment of this application.
  • Figure 29 is a schematic structural diagram of another communication device provided in an embodiment of this application.
  • Figure 30 is a schematic structural diagram of a communication device provided in an embodiment of this application.
  • the technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLANs), wireless fidelity (WiFi), high-performance radio local area networks (HIPELANs), wide area networks (WANs), cellular networks, or other communication systems.
  • WLANs wireless local area networks
  • WiFi wireless fidelity
  • HIPELANs high-performance radio local area networks
  • WANs wide area networks
  • the technical solutions provided in this application can be applied to communication systems using the 802.11 standard.
  • the 802.11 standard includes, but is not limited to, the 802.11ax standard, the 802.11be standard, and next-generation 802.11 standards.
  • Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application.
  • the communication devices in the communication system 100 may include AP111, AP112, and station (STA) 121 and STA122, wherein STA121 can access the network through AP111, and STA122 can access the network through AP112.
  • STA121 can access the network through AP111
  • STA122 can access the network through AP112.
  • a STA can establish an association with one or more APs, after which the associated STAs and APs can communicate with each other. As shown in Figure 1, AP 111 and STA 121 can communicate after establishing an association, and AP 112 and STA 122 can communicate after establishing an association.
  • the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA.
  • a peer STA can refer to a device that communicates with the STA's counterpart.
  • a peer STA may be an AP or a non-AP STA.
  • Figure 1 exemplarily shows two AP STAs and two non-AP STAs.
  • the communication system 100 may also include more AP STAs, or the communication system 100 may include other numbers of non-AP STAs. This application embodiment does not limit this.
  • the above-mentioned communication system can be applied to scenarios involving multi-device collaboration, such as multi-AP (multi-access point) collaboration or multi-site collaboration.
  • multi-device collaboration such as multi-AP (multi-access point) collaboration or multi-site collaboration.
  • AP and/or STA are not limited.
  • AP can also be called AP STA, that is, in a sense, AP is also a type of STA.
  • STA can also be called non-AP STA.
  • the aforementioned communication devices can also be "multi-link devices (MLDs)," meaning devices that can communicate through multiple communication links. These multiple communication links can include communication links in different frequency bands, such as millimeter-wave bands and/or low-frequency bands.
  • MLDs multi-link devices
  • AP access point
  • STA stand-alone device
  • multi-link STA multi-link STA
  • the AP can be a device in a wireless network.
  • the AP can be a communication server, router, switch, bridge, or other communication entity.
  • the AP can include various forms of macro base stations, micro base stations, relay stations, etc.
  • the AP can also be a chip, circuit, or processing system within these various forms of devices, thereby implementing the methods and functions of this application embodiment.
  • APs can be applied in various scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.).
  • IoT Internet of Things
  • entertainment terminals e.g., AR, VR, and other wearable devices
  • smart devices in smart offices e.g., printers, projectors, etc.
  • V2X vehicle-to-everything
  • the role of the STA in the communication system is not absolute; in some scenarios, the STA can act as an AP.
  • the STA can act as an AP.
  • the mobile phone can be a non-AP STA, while when the mobile phone acts as a hotspot for other mobile phones, it acts as an AP.
  • the STA can be a device with wireless transceiver capabilities, such as one that supports the 802.11 series of protocols and can communicate with an AP or other STAs.
  • an STA is any user communication device that allows users to communicate with an AP and thus with a WLAN.
  • STAs can be, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.
  • the STA can also be a device that provides voice/data connectivity to the user, such as a handheld device or in-vehicle device with wireless connectivity.
  • a handheld device or in-vehicle device with wireless connectivity examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, and wireless terminals in smart cities.
  • wireless terminals in various applications, including wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMNs).
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs personal digital assistants
  • handheld devices with wireless communication capabilities computing devices or other processing devices connected to a wireless modem
  • in-vehicle devices wearable devices
  • terminal devices in 5G networks or terminal devices in future evolved public land mobile networks (PLMNs).
  • PLMNs public land mobile networks
  • the STA can also be a wearable device.
  • Wearable devices also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Examples include smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require cooperation with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
  • the STA can also be a terminal device in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.
  • IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).
  • NB narrowband
  • the STA can be a device in a vehicle-to-everything (V2X) system.
  • V2X vehicle-to-everything
  • the communication methods in a V2X system are collectively referred to as V2X (where X represents anything).
  • V2X communication includes: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.
  • the STA may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal devices), receiving control information and downlink data from the AP, and sending electromagnetic waves to transmit data to the AP.
  • sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal devices), receiving control information and downlink data from the AP, and sending electromagnetic waves to transmit data to the AP.
  • the AP in this application embodiment can be a device for communicating with the STA.
  • the AP can be a network device in a wireless local area network, and the AP can be used to communicate with the STA through the wireless local area network.
  • the AP can be a device that supports the 802.11be standard.
  • the AP can also be a device that supports various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • non-AP STAs can support the 802.11be standard.
  • Non-AP STAs can also support various current and future 802.11 family of wireless local area networks (WLANs), such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • WLANs wireless local area networks
  • the frequency bands supported by WLAN technology are not limited.
  • the frequency bands supported by WLAN technology may include, but are not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 45GHz, 60GHz).
  • STA and AP are not specifically limited in the embodiments of this application, and are merely illustrative examples.
  • M-AP cooperation technology can significantly improve network throughput, increase spectrum resource utilization, and reduce mutual interference between devices.
  • M-AP cooperation can include techniques such as M-AP cooperative transmission or M-AP cooperative measurement. The following explains some of the terminology related to M-AP cooperation.
  • a candidate set of multiple APs can refer to a set of APs that can initiate or participate in M-AP collaboration.
  • a multi-AP collaboration set can refer to the set of APs participating in multi-AP collaboration.
  • a multi-AP collaboration set can be a subset of a multi-AP candidate set.
  • a sharing AP can refer to an AP that obtains a TXOP and initiates M-AP collaboration. At least one AP in a multi-AP candidate set can become a sharing AP.
  • a shared AP can participate in M-AP collaboration initiated by a shared AP in the same multi-AP candidate set.
  • the role of an AP participating in the collaboration can be either a sharing AP or a shared AP, and role assignment can be dynamic.
  • the AP that acquires the TXOP can be a sharing AP, while other APs participating in the collaboration can be shared APs.
  • FIG. 2A shows an example of an M-AP cooperative network topology.
  • the network topology shown in Figure 2A includes three APs. Each of the three APs establishes its own BSS. AP1 is associated with STA1, AP2 with STA2, and AP3 with STA3. The APs can hear each other. These APs compete for the channel equally, and any AP that wins the TXOP can become a shared AP.
  • Figures 2B and 2C are example diagrams of M-AP collaboration scenarios. As shown in Figures 2B and 2C, any AP in an OBSS can probe any other node in that OBSS.
  • M-AP collaboration modes or schemes can include: cooperative UL MU-MIMO, coordinated beamforming (C-BF), coordinated spatial reuse (C-SR), joint transmission (J-TX), C-TDMA, and C-OFDMA, etc.
  • Figure 2B shows a scenario diagram for C-BF and J-TX.
  • Figure 2C shows a scenario diagram for C-TDMA or C-OFDMA.
  • Figure 2D illustrates the framework of M-AP collaboration.
  • the framework of M-AP collaboration can include one or more of the following phases: M-AP discovery phase, coordinated TX agreement phase, pre-transmission phase, and M-AP coordinated transmission phase.
  • M-AP discovery phase and the coordinated transmission agreement phase are independent of each other and are essential phases for most M-AP coordinated transmission schemes.
  • an AP can declare its support for M-AP cooperation.
  • TXOP Multi-AP Request Point
  • each AP can detect a multi-AP candidate set.
  • the cooperative transmission negotiation phase can take place within the TXOP.
  • the sharing AP that acquires the TXOP establishes a true multi-AP cooperative set with the shared APs in its candidate set. Multiple APs within this multi-AP cooperative set will participate in cooperation.
  • Pre-transmission is an optional phase; for some M-AP schemes, preparatory work is required before data transmission. For example, for C-OFDMA, switching the primary channel may be necessary; for C-BF or C-SR, channel detection may be required.
  • C-OFDMA, C-BF, or C-SR require a pre-transmission phase.
  • the M-AP cooperative transmission phase can be triggered by the sharing AP.
  • the trigger frame carries resource information allocated to one or more shared APs in the TXOP.
  • the receiver of the trigger frame is determined during the cooperative transmission negotiation phase, i.e., an AP belonging to the multi-AP cooperative set.
  • a sharing AP and/or one or more shared APs can send their respective downlink multi-user (DL MU) PPDUs or TB PPDUs requesting uplink data to their respective associated STAs at different frequency portions of the cooperative bandwidth.
  • DL MU downlink multi-user
  • Figure 3A is an example diagram of the cooperative bandwidth in a C-OFDMA transmission.
  • the cooperative bandwidth is 40MHz.
  • one AP participating in multi-AP transmission can exchange data with its associated STA1, STA2, or STA3.
  • another AP participating in multi-AP transmission can exchange data with its associated STA4 or STA5.
  • Figure 3B is a schematic flowchart of a C-OFDMA transmission. As shown in Figure 3B, the process may include a C-OFDMA preparation phase and a C-OFDMA TXOP sharing SP phase.
  • the sharing AP sends a trigger frame (e.g., a basic trigger frame) to trigger simultaneous transmission by the shared APs (including shared AP1 and shared AP2 shown in Figure 3B).
  • the trigger frame may carry allocation information required for TXOP sharing.
  • the shared APs can use pre-allocated frequency resources to transmit their own data.
  • APs can conduct the M-AP discovery phase and/or cooperative transmission negotiation phase shown in Figure 2D.
  • the sharing AP and/or one or more shared APs can transmit TB PPDUs requesting uplink data across the entire cooperative bandwidth, with each non-AP STA allocated a different spatial stream.
  • one or more APs participating in M-AP cooperation can send a cooperative UL trigger frame to their respective associated STAs, and in response to the cooperative UL trigger frame, the STA can send uplink data frames.
  • the uplink data frames sent by each STA can be perfectly aligned.
  • FIG 4 is an example diagram of cooperative UL MU-MIMO transmission.
  • the shared AP1 (AP1 for short) is associated with STA1
  • the shared AP2 (AP2 for short) is associated with STA2.
  • the shared APs send a multi-AP trigger frame (M-AP TF).
  • AP1 sends a cooperative UL trigger frame to STA1.
  • AP2 sends a cooperative UL trigger frame to STA2.
  • Both STA1 and STA2 send UL PPDUs including data frames.
  • the UL PPDUs sent by STA1 and STA2 are perfectly aligned.
  • AP1 After receiving the UL PPDU sent by STA1, AP1 sends a block acknowledge (BA) frame to STA1.
  • BA block acknowledge
  • Cooperative beamforming can achieve interference suppression. For example, during data transmission/reception, the AP can enhance the beam directed towards the target STA. Conversely, during data transmission/reception, the AP can nullify the spatial radiation directed towards a non-target STA.
  • FIG. 5A shows an example of cooperative beamforming/nulling.
  • AP1, STA1, and STA2 belong to basic service set (BSS) 1;
  • AP2, STA3, and STA4 belong to BSS 2.
  • BSS basic service set
  • AP1 and AP2 null each other's STAs within their respective BSSs. That is, AP1 nulls the spatial radiation of STA3 and STA4; AP2 nulls the spatial radiation of STA1 and STA2.
  • the cooperative beamforming process can include the following four stages:
  • Phase 0 Establishment of semi-static collaboration between APs
  • Phase 1 Enhanced spatial reuse opportunity (eSRO) collaboration
  • Phase 3 Data transmission and acknowledgment between cooperating APs with null values (zero bits).
  • Phase 0 establishes a multi-AP cooperative set.
  • the provider AP can actively broadcast its eSRO with "zeroing" capability. Through this eSRO, the APs the donor AP expects to mitigate interference will respond and report their IDs.
  • Phase 2 is the CSI collection process. Once the donor AP determines the nodes that need to be serviced/zeroed in the AP cooperation, the participating APs need the relevant CSI to set the corresponding beam/zeroing.
  • cooperating APs with zeroing capabilities transmit data and acknowledge each other.
  • Figure 5B is an example diagram of an explicit CSI collection process.
  • Cooperative space reuse can refer to reducing interference between APs through joint power control, thereby enabling multiple APs to transmit in parallel and maximizing the total throughput.
  • cooperative space multiplexing can be implemented with relatively low complexity. In other words, compared with other M-AP cooperative schemes, cooperative space multiplexing can achieve low complexity and high performance (throughput and latency) gains.
  • Figure 6 shows an example of collaborative space reuse.
  • AP1 and STA1 belong to BSS1; AP2 and STA2 belong to BSS2.
  • AP1 and AP2 can transmit control information. Based on the control information, AP1 and AP2 can perform interference control on the STAs within each other's BSS. That is, AP1 can perform interference control on STA2; AP2 can perform interference control on STA1.
  • Multi-AP joint transmission refers to at least two APs simultaneously sending data to a target user (i.e., the target STA).
  • the data transmitted by multiple APs occupies the exact same frequency domain resources (cooperative bandwidth) and is distinguished by different spatial streams.
  • joint transmission is transparent. That is, the target STA cannot distinguish whether the received data was transmitted via multi-AP joint transmission.
  • APs can transmit data to the same target STA via a backhaul link. Backhaul messages can be transmitted between APs via wired or wireless connections.
  • Figure 7 shows an example of multi-AP joint transmission.
  • AP1 and AP2 can implement multi-AP joint transmission.
  • AP1 and AP2 can simultaneously send data to one or more of STA1, STA2, STA3, and STA4.
  • STA1 and STA2 can belong to BSS1, and STA3 and STA4 can belong to BSS2.
  • AP1 and AP2 can transmit data destined for the same STA through the backhaul link.
  • multi-AP joint transmission can increase the number of antennas, thereby increasing the total number of spatial streams. Furthermore, multi-AP joint transmission can serve multiple STAs simultaneously, thus improving system throughput. Additionally, multi-AP joint transmission allows the target STA to receive channels from multiple locations, thereby enhancing transmission reliability.
  • C-TDMA can refer to a shared AP allocating a specific time period from its acquired TXOP to a shared AP. During the time period allocated to the shared AP, the shared AP can perform any PPDU transmission, including sending DL PPDUs or requesting UL PPDUs.
  • FIG 8A is an example diagram of C-TDMA.
  • the TXOP TXOP gained by sharing AP
  • the shared AP1 can send a DL PPDU and receive the corresponding BA frame.
  • the shared AP1 can send a trigger frame to request an uplink trigger-based (TB) PPDU.
  • TB uplink trigger-based
  • Figures 8B and 8C are both example diagrams of a C-TDMA process.
  • FIG 8B illustrates an example of a C-TDMA process in the case of a shared AP.
  • the sharing AP i.e., the TXOP owner, AP1 in Figure 8B
  • sends a schedule announcement frame broadcasting to the shared AP (i.e., the AP with the shared TXOP) and the corresponding STAs within the BSS that the sharing AP will share the TXOP.
  • the main function of this frame is to manage the medium, and the shared AP and the corresponding STAs within the BSS can prepare in advance.
  • the schedule announcement frame can be a multi-user request to send (MU-RTS) frame. Additionally, the schedule announcement frame can also specify the TXOP length.
  • frame exchange can occur between AP1 and its STAs.
  • AP1 can send a TXOP allocation frame to a designated shared AP (e.g., AP2 in Figure 8B) to notify of the shared TXOP time and other allocation information.
  • the shared AP can return any remaining TXOP to the sharing AP via a CF-End frame.
  • Figure 8C shows an example of the C-TDMA process in the case of multiple shared APs.
  • the communication process in Figure 8C and Figure 8B is similar and will not be described again.
  • Dynamic energy-saving technology can be applied to both APs and non-AP STAs.
  • STAs including APs or non-AP STAs
  • STAs can default to a lower capability mode.
  • the STA's transmission parameters or capabilities
  • BW bandwidth
  • NSS spatial streams
  • the STA can only receive specific PPDUs (i.e., it cannot receive certain PPDUs).
  • a STA in lower capability mode receives a handover request, it can switch from lower capability mode to higher capability mode.
  • the STA's transmission parameters are not limited, or the STA's transmission parameters can be higher than those in lower capability mode.
  • the bandwidth and/or number of spatial streams can be greater than those in lower capability mode (e.g., 160MHz, 2SS).
  • a handover request sent by the sending STA can be used to request the responding STA (or receiving STA) to switch to a higher capability mode.
  • the handover request can be, for example, an initial control frame (ICF) with padding.
  • ICF initial control frame
  • the sender of the switching request can be either an AP or a STA.
  • the responding STA can switch to the specified wake-up state and reply with a response frame to the sending STA.
  • This response frame can be, for example, an initial control response (ICR) frame.
  • ICR initial control response
  • This set of interactions completes the wake-up of the energy-saving device (i.e., switching to a higher capability mode).
  • both the sending and receiving STAs can send data frames while in the wake-up state.
  • the ICF frame mentioned above can be a MU-RTS trigger frame or a block acknowledgment response (BAR) frame.
  • BAR block acknowledgment response
  • padding is required before the FCS field to allow the responding STA sufficient time to switch to the specified wake-up state.
  • BW/NSS corresponding to higher capability modes can be obtained from the latest Caps/OMN/OM controls (applicable to AM and PS modes).
  • Figure 9A is a schematic diagram of a dynamic energy-saving operation process.
  • the STA uses 20MHz/1SS for transmission.
  • the first ICF frame instructs the STA to switch to the first higher capability mode.
  • the STA uses 80MHz/1SS for transmission.
  • the second ICF frame instructs the STA to switch to the second higher capability mode, in which the STA uses 160MHz/2SS for transmission.
  • Figure 9B is a specific embodiment of Figure 9A.
  • the MU-RTS frame is the first ICF frame.
  • the BAR frame is the second ICF frame.
  • M-AP collaboration certain states of the communication devices may cause the M-AP collaboration mechanism to fail to achieve its intended working objectives. For example, if one or more APs have enabled dynamic power-saving mode, that AP may enter a lower... Capability Mode. Some associated STAs may also have dynamic power-saving mode enabled, which could lead to a lower capability mode.
  • the sharing AP might request the AP in the lower capability mode to join the multi-AP cooperation set and allocate cooperative transmission resources to it. However, because the AP is in a lower capability mode, it may not be able to fully utilize the resources allocated by the sharing AP (including frequency and/or time domain resources), resulting in wasted resources.
  • the states of the multiple APs participating in M-AP cooperation may differ, with some in a higher capability mode and others in a lower capability mode. This asynchrony between AP states may cause M-AP cooperative transmission to fail, preventing true M-AP cooperation.
  • Figure 10 is a schematic flowchart of a wireless communication method provided in an embodiment of this application to solve the above problems.
  • Figure 10 can be performed by a first device and a first AP.
  • the first device may include a second AP and/or a STA associated with the second AP.
  • the first AP and the second AP may be different APs.
  • the first AP may include a sharing AP.
  • the second AP may include a shared AP.
  • a shared AP and one or more shared APs can participate in M-AP collaboration.
  • the shared AP may not participate in M-AP collaboration; two or more shared APs may participate in M-AP collaboration.
  • the method shown in Figure 10 may include step S1010.
  • step S1010 the first AP receives the first information.
  • the first information can be sent by the first device.
  • the first information may be related to a first mode of the first device.
  • the first mode may, for example, include an energy-saving mode.
  • the energy-saving mode may, for example, be a dynamic energy-saving mode.
  • the first device When the first mode is enabled, the first device can be in either the first state or the second state. If the first mode includes an energy-saving mode, the first state can be an energy-saving state, and the second state can be a non-energy-saving state; or, the first state can be a non-energy-saving state, and the second state can be an energy-saving state. It should be noted that energy-saving and non-energy-saving states can be relative.
  • the first state can be called a non-energy-saving state, and the second state can be called an energy-saving state; or, if the first state is more energy-efficient than the second state, the first state can be called an energy-saving state, and the second state can be called a non-energy-saving state.
  • the transmission parameters of the first device may be limited; or, the first device may be unable to actively transmit some or all signals; or, the first device may be unable to receive some or all signals.
  • the transmission parameters of the first device are higher than those in energy-saving mode; or, the transmission parameters of the first device are unrestricted; or, the first device is able to receive all supported signals; or, the first device is able to transmit all supported signals.
  • the first mode can be a dynamic energy-saving mode.
  • the first state can include a lower capacity mode; the second state can include a higher capacity mode.
  • the second state can include a lower capacity mode; the first state can include a higher capacity mode.
  • the first state can include a first higher capacity mode, and the second state can include a second higher capacity mode.
  • the capacity corresponding to the second higher capacity mode can be higher than the capacity corresponding to the first higher capacity mode.
  • a state transition can occur between the first state and the second state.
  • a state transition can include switching from the first state to the second state or vice versa.
  • the capabilities that the first device can possess can be a first capability.
  • the capabilities that the first device can possess can be a second capability.
  • “capable capabilities” can be the upper limit of the first device's capabilities.
  • the first capability can be weaker than all the capabilities that the first device possesses (e.g., the capabilities indicated by a capability element).
  • the second capability can be stronger than the first capability.
  • the second capability can be all capabilities or a capability weaker than all capabilities.
  • the switching between the first state and the second state can be a switching between the first capability and the second capability.
  • the switching between the first capability and the second capability can also be called capability switching.
  • one AP can obtain information related to the first mode of another AP (i.e., the second AP) and/or the STA associated with another AP, thereby enabling targeted communication and improving communication efficiency and resource utilization.
  • the first information allows for more rational arrangement or scheduling of M-AP collaboration, ensuring that M-AP collaboration achieves the expected results.
  • the shared AP can rationally schedule resources based on the first information, effectively avoiding resource waste caused by ineffective resource allocation.
  • the first information may include one or more of the following: enable information, the state of the first device at a first moment or a first period of time, a first duration, and a second duration. These will be described separately below.
  • Enable information can be used to indicate whether the first device is in the first mode.
  • the state of the first device can include either the first state or the second state described above.
  • the first device may be in either the first state or the second state, or there may be a state transition.
  • the state of the first device may include only one state (e.g., the second state).
  • the transmission parameters of the first device may be unrestricted. If the first mode includes a power-saving mode, the first device will not be in a power-saving state if the power-saving mode is not enabled.
  • the first AP can perform corresponding operations. For example, ... If the second AP's first mode is enabled, the multi-AP cooperation set established by the first AP may not include the second AP.
  • the AP that obtains the TXOP can become a shared AP.
  • the shared AP can send a cooperative transmission request frame to APs in the multi-AP candidate set.
  • APs receiving the cooperative transmission request frame can send a response frame to indicate whether they will participate in this M-AP cooperation.
  • the response frame may include information such as the allocation time expected by the shared AP and the status code (accept/reject).
  • the shared AP does not receive a response from any AP in the multi-AP candidate set, it can default to refusing to join the M-AP cooperation.
  • APs that agree to join the cooperative transmission and the requesting shared AP establish an M-AP cooperative transmission cooperation set; this group of APs will participate in subsequent cooperative transmissions.
  • APs in the candidate set but not joined will not participate in subsequent cooperative transmissions.
  • the interaction information between the cooperative transmission request frame and the response frame may vary depending on the M-AP cooperation scheme.
  • the first AP can determine which AP(s) to send a cooperative transmission request frame to.
  • the cooperative transmission request frame is used to request the peer AP to join the M-AP cooperative set.
  • the cooperative transmission request frame may include information such as the M-AP cooperative transmission scheme and allocated time. For example, if the second AP's first mode is enabled, the first AP may not invite or allow the second AP to join the multi-AP cooperative set.
  • the state of the first device at a first moment or during a first period of time may include the first state or the second state described above.
  • the first moment or the first period of time may include the current moment. That is, through the first information, the first device can report its current state to the first AP.
  • the first moment may include a future moment. That is, through the first information, the first device can report its future state to the first AP.
  • the first moment may belong to a first period of time, and the first information may include the state of the first device within that period of time.
  • the first AP can determine the operation related to cooperation with the M-AP based on the state of the first device at the first moment or the first period.
  • the first AP may choose not to invite or refuse the second AP to join the multi-AP cooperation.
  • the first AP may not send a cooperation transmission request frame to the second AP. That is, for APs in the multi-AP cooperation set, the first AP may not send a cooperation transmission request frame to APs in the first state.
  • the first AP can invite the second AP to join the multi-AP cooperation.
  • the first AP can send a cooperation transmission request frame to the second AP, requesting the second AP to join the cooperation transmission.
  • the second AP can send a response frame in response.
  • the response frame may include information such as the first duration and/or the second duration described below.
  • the first AP can instruct the first device to switch from the first state to a second state.
  • the first AP e.g., in the case where the first AP is a shared AP
  • the first AP can wake up a neighboring AP and/or a STA associated with the neighboring AP.
  • the first AP can send the second or third information described below to instruct the first device to switch from the first state to the second state at an appropriate time.
  • the first device includes a second AP
  • the first AP can send a cooperative transmission request frame to the second AP, and may also send the second or third information.
  • the first device can switch back from the second state to the first state. For example, the first device can switch from a higher capability state to a lower capability state, thereby saving energy consumption of the first device.
  • the first duration can be used to indicate the duration for the first device to switch from a first state to a second state. That is, the first duration can be used to indicate the duration for the first device to switch from a first state to a second state. For example, if the first mode includes an energy-saving mode, the first duration can be used to indicate the duration for switching from an energy-saving state to a non-energy-saving state, or the first duration can be used to indicate the duration for switching from a lower capability mode to a higher capability mode.
  • the second duration can be used to indicate the duration for a second device to switch from a first state to a second state.
  • the second device can be a device within the same BSS as the first device.
  • the first device can indicate the duration for other devices within its BSS to switch from the first state to the second state.
  • the duration of switching from the first state to the second state can be considered the delay caused by the state transition, i.e., the switching delay. Therefore, the first duration and the second duration can indicate the switching delay of different devices. Based on this, the first duration can be considered switching delay information; and/or, the second duration can be considered switching delay information.
  • the second device may belong to multiple devices within the same BSS as the first device.
  • the second duration can be determined based on the duration for which multiple devices switch from the first state to the second state.
  • the second duration can be the maximum value of the duration for which multiple devices switch from the first state to the second state.
  • the second device When the second device is enabled in the first mode, if the first device needs to communicate with the second device, the second device also needs to switch to the second state.
  • the first mode as a dynamic energy-saving mode and the first device as the second AP as an example
  • the second AP needs to communicate with the STA (i.e., the second device) within its BSS, that STA also needs to switch to a higher capability mode. Therefore, if the first AP wants to perform M-AP collaboration with the second AP, the STAs within the second AP's BSS also need to switch to a higher capability mode to achieve communication with the second AP. Therefore, the first device reporting the second duration allows the first AP to comprehensively consider the state switching durations of other STAs within its BSS, thereby improving the communication efficiency of the second AP participating in M-AP collaboration and avoiding resource waste.
  • the first information when the first mode is enabled, may include one or more of the following: the state of the first device at a first moment or during a first period, the first duration, and the second duration.
  • the first information when the first mode is not enabled, may... It excludes one or more of the following information: the state of the first device at the first moment or the first time period, the first duration, and the second duration.
  • the information in the first message can be contained in the same frame or in different frames.
  • the enabling information sent by the second AP and/or an indication of whether the second AP supports M-AP coordination may be included in a beacon frame or a multi-AP coordination management (e.g., multi-AP probe management) frame.
  • the beacon frame or M-AP coordination management frame may carry an M-AP coordinated information element.
  • This M-AP coordinated information element may include some or all of the parameters/functions supported by the AP for M-AP coordination.
  • only APs that support M-AP coordination can parse the M-AP coordination information element.
  • the beacon frame or M-AP coordination management frame may include an enable field to indicate the enabling information.
  • the state of the first device at a first moment or during a first period, the first duration, and the second duration, one or more of these can be carried by a dynamic power save (DPS) frame.
  • This DPS frame can be referred to as a DPS mode notification frame.
  • the first device can send this DPS frame. If the first mode is disabled, the first device may not send this DPS frame.
  • the first AP Upon receiving the first information, the first AP can send a response to the first device in response to the first information, informing the first device that the first AP has received the first information. For example, if the first information is carried in a DPS frame, the response to the first information can also be carried in a DPS frame.
  • the first message can be sent unsolicited or solicited by the first device.
  • solicited sending can be initiated by the first AP requesting the first device to send it.
  • Initiated sending can be done via beacon frames and/or AP-specific cooperative management frames.
  • the first information may be actively sent by the first device.
  • the first device may actively send the first information.
  • the first device may send the first information by sending a beacon frame.
  • the first device may actively send the first information to all neighboring sites. For example, before the multi-AP candidate set is established, each AP may actively send the first information. Since the multi-AP candidate set has not yet been established, the first information may be sent via broadcast.
  • the first AP is either AP1 or AP3
  • the first device is either AP2 or AP2's STA2.
  • AP1, AP2, and AP3 establish a candidate set.
  • AP2 indicates the activation of dynamic power-saving mode in the beacon frame, and AP1 and AP3 are aware that AP2 has activated dynamic power-saving mode.
  • AP2 sends a DPS frame to both AP1 and AP3.
  • This DPS frame can indicate one or more of AP2's state at the first moment, the first duration, and the second duration.
  • AP1 and AP3 can record information such as AP2's state and send a DPS frame to AP2 in response.
  • the transmission of the first information may be triggered by a first frame sent by the first AP.
  • the first frame can be used to request the transmission of the first information.
  • the first information can be requested by the first AP.
  • the first AP can send a first frame to the APs in the multi-AP candidate set to request them to send the first information.
  • the second AP belongs to the first AP's multi-AP candidate set. Therefore, by triggering the transmission of the first information based on the first frame, the first information can be sent selectively to the APs that request it, avoiding resource waste caused by sending the first information to devices that do not need to know it.
  • the first frame can be a DPS frame. This will be explained below with reference to Figure 11B.
  • the first AP can be AP1, and the second AP can be AP2.
  • AP1 acquires the TXOP and becomes the shared AP.
  • AP1 sends a DPS frame to AP2 to request AP2 to send first information.
  • AP2 After receiving the DPS frame sent by AP1, AP2 sends a DPS frame to AP1 in response to AP1's request.
  • the DPS frame sent by AP2 may include the first information.
  • the first AP may actively request AP2 to send the first duration and/or the second duration.
  • the first AP can instruct a first device in a first state to switch to a second state.
  • the first state may include an energy-saving state
  • the second state may include a non-energy-saving state. That is, when the first AP initiates M-AP cooperation, the first AP can wake up the first device so that devices participating in M-AP cooperation can make full use of communication resources.
  • the first AP can instruct the first device to switch from a first state to a second state.
  • the first AP can perform further operations. For instance, if the second state is a non-energy-saving state, the first AP will only begin M-AP cooperative transmission with the second AP after the second AP switches to the second state.
  • the first device needs to complete the switch to the second state before initiating M-AP cooperation. That is, the start time of M-AP cooperative transmission can be equal to or later than the time when the first device switches from the first state to the second state.
  • the first AP can instruct the second device to switch from a first state to a second state.
  • the first AP can perform further operations. For instance, if the second state is a non-energy-saving state, the first AP will only proceed if all STAs within the second AP's BSS or all STAs associated with the second AP have switched to the second state. It will begin M-AP collaborative transmission with the second AP.
  • the first AP may send second information.
  • the second information may be used to indicate a second time at which the first device switches from a first state to a second state.
  • the second time may be the moment when the first device completes the state switch.
  • the first device may complete the switch from the first state to the second state at or before the second time, or in other words, complete the switch no later than the second time.
  • the first AP may instruct the first device in advance at what time to complete the state switch, so that the first device can begin executing the state switch in advance, thereby ensuring that the first device has completed the switch from the first state to the second state before subsequent operations.
  • the first AP may send third information.
  • This third information may be used to indicate a third time.
  • the third time may be the start time of the first AP performing the first operation.
  • the third time may be the start time of a multi-AP cooperative transmission initiated by the first AP.
  • the first device may determine the time when it switches from a first state to a second state based on the third information. For example, the time when the first device switches from the first state to the second state may be earlier than or equal to the third time, or no later than the third time. It is understood that the first AP may not directly indicate the second time (i.e., implicitly indicate it), and the first device may calculate the second time based on the third information.
  • the first AP can inform the first device of the expected start time of the M-AP cooperative transmission, thereby indicating the time when the first device in the lower capability mode switches to the higher capability mode, i.e. the wake-up time, thus saving the overhead required for explicit wake-up.
  • the second or third information may be carried in the first frame.
  • the first frame may be transmitted during the pre-transmission phase; and/or during the M-AP cooperative transmission phase.
  • the first AP may send a first frame.
  • the first device In response to the first device receiving the first frame, the first device can switch from a first state to a second state. That is, upon receiving a specific frame, the first device can immediately perform a state switch. A detailed description of the first frame is provided above and will not be repeated here.
  • the first frame can be used to request the second AP to join the multi-AP collaboration set.
  • the first device in response to the first AP requesting the second AP to join the multi-AP collaboration set, can switch states.
  • the first frame can be used to request multiple APs to join a multi-AP cooperation set, and the multiple APs may include second APs.
  • the first frame is a trigger frame
  • the first AP is AP1
  • the second AP is AP2.
  • AP1 simultaneously requests AP2 and AP3 to join the multi-AP cooperation set.
  • the trigger frame sent by AP1 to AP2 and AP3 may contain third information.
  • AP2 switches to the second state before the third time indicated by the third information.
  • the first frame may be used only to request one AP to join the multi-AP cooperative set, and one AP may be a second AP.
  • the first frame is a trigger frame
  • the first AP is AP1
  • the second AP is AP2.
  • AP1 first requests AP2 to join the multi-AP cooperative set.
  • the trigger frame sent by AP1 to AP2 may contain third information.
  • AP2 switches to the second state before the third time indicated by the third information.
  • AP1 may then request AP3 to join the multi-AP cooperative set. If AP3's first mode is not enabled, or if AP3 is in the second state, the trigger frame sent by AP1 to AP3 may not contain the third information.
  • the first frame can be used to: initiate M-AP cooperative transmission.
  • the first device in response to the first AP initiating multi-AP cooperative transmission, the first device can switch states.
  • the first frame can be used to: initiate M-AP collaborative measurement.
  • the first device in response to the first AP initiating multi-AP collaborative measurement, the first device can switch states.
  • the first frame can be used to indicate the transmission parameters and/or transmission resources of the APs participating in M-AP cooperation. That is, the first frame can be used to announce the resource allocation in M-AP cooperation. For example, in response to the first AP indicating the transmission parameters and/or transmission resources of the APs participating in M-AP cooperation to the second AP, the first device can switch states.
  • the first frame can be used to wake up the first device.
  • the first frame may be sent by the first AP, and the first device may be the second AP or a STA associated with the second AP. Therefore, the first frame for waking up the first device can be a neighboring AP. If the first AP is a shared AP, then the first frame can be used by the shared AP to wake up the shared AP or a STA associated with the shared AP.
  • the first frame may include a padding field.
  • the padding field may be located at the end of the first frame.
  • the padding field may precede the FCS field or follow the FCS field.
  • the first duration described above can be used to determine the padding length of the first frame.
  • the padding length can be greater than or equal to the first duration.
  • the first device can complete the switch from the first state to the second state.
  • the second duration described above can be used to determine the padding length of the first frame.
  • the padding length can be greater than or equal to the second duration.
  • the second device can complete the switch from the first state to the second state.
  • the padding length of the first frame can be determined based on a first duration and a second duration.
  • the padding length can be greater than or equal to the maximum value of the first duration and the second duration.
  • the first device may send a second frame to the first AP.
  • the second frame may be used to indicate that the first device has completed the transition from the first state to the second state.
  • the second frame may, for example, be a clear to send (CTS) frame.
  • the first AP can be a shared AP
  • the second AP can be a shared AP
  • the first state is a lower capability state
  • the second state is a higher capability state.
  • the sharing AP can wake up the shared AP in a lower capability state while announcing resource allocation.
  • the sharing AP can send a C-MU-RTS frame with padding (i.e., the first frame) to the shared AP.
  • the user information field in the C-MU-RTS can carry resource allocation information for the shared AP.
  • the length of the padding in the C-MU-RTS frame is the value of the second duration sent by AP2.
  • the value of the second duration can be indicated by the DPS padding delay field.
  • a shared AP in a lower capability state switches to a higher capability state, it can send a CTS frame in response. Subsequently, the shared AP can send a padded MU-RTS to the associated STA in the lower capability state. The STA switches to the higher capability state and the channel specified in the MU-RTS frame, and sends a CTS in response.
  • FIG 13 is an example diagram of a C-OFDMA process.
  • the C-MU-RTS frame transmitted by AP1 includes a padding field (represented in Figure 13 by AP2 padding), the length of which is determined based on the duration of AP2 switching from the first state to the second state.
  • the MU-RTS frame transmitted by AP2 includes a padding field (represented in Figure 13 by BSS2 maximum padding), the length of which is determined based on the maximum duration of the STA in AP2's BSS (labeled BSS2) switching from the first state to the second state.
  • AP1 can send a broadcast trigger frame to trigger all APs to perform cooperative transmission. After the cooperative transmission is completed, AP2 can switch back to a lower capability state.
  • all APs participating in the cooperative transmission should obtain CSI information through channel probing via NDP.
  • AP1 can send a MU-RTS with a padding field (represented by maximum padding in BSS2 in Figure 14A) to wake up AP2 and STA2 in a lower capability state before channel probing.
  • the length of this padding field is the maximum time required for all STAs within AP2's BSS (labeled BSS2) to switch from the first state to the second state, thus ensuring the wake-up of all devices in the lower capability state within BSS2.
  • BSS2 BSS2's BSS
  • AP1 sends a trigger frame to trigger all APs to simultaneously perform C-BF transmission.
  • AP2 can switch back to the lower capability state after the transmission is completed.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending a padded MU-RTS frame.
  • handover delay information including a first duration and/or a second duration
  • AP1 can carry a padding field in the NDPA frame (represented by maximum padding in BSS2 in Figure 14B) to wake up AP2 and STA2 in a lower capability state.
  • the length of this padding field is the maximum time required for all STAs within AP2's BSS (labeled BSS2) to switch from the first state to the second state, thus ensuring the wake-up of all devices in the lower capability state within BSS2.
  • BSS2 BSS2's BSS
  • AP1 sends a trigger frame to trigger all APs to simultaneously perform C-BF transmission.
  • AP2 can switch back to the lower capability state after the transmission is completed.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending a padded NDPA frame.
  • handover delay information including a first duration and/or a second duration
  • J-TX also requires channel probing before data transmission. All APs participating in the cooperative transmission need to send full-channel CSI feedback from the STA. Specifically, the sharing AP can send an NDPA frame to all shared APs within the cooperative set, triggering the shared APs to initiate the channel probing process.
  • AP1 can send a MU-RTS with a padding field (represented by AP2 padding in Figure 15A) to trigger AP2, which is in a lower capability state, to switch to a higher capability state.
  • the length of the padding field can be the first duration.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending the MU-RTS frame with padding fields.
  • handover delay information including a first duration and/or a second duration
  • AP1 can send an NDPA frame with a padding field (represented by AP2 padding in Figure 15B) to trigger AP2, which is in a lower capability state, to switch to a higher capability state.
  • the length of the padding field can be a first duration.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending the MU-RTS frame with padding fields.
  • handover delay information including a first duration and/or a second duration
  • the following explanation uses different modes of M-AP cooperation as an example, taking the first frame as an example of a frame transmitted during the M-AP cooperation transmission phase, to illustrate the padding and implicit wake-up techniques for the first frame.
  • the first AP can be a shared AP
  • the second AP can be a shared AP
  • the first state is a lower capability state
  • the second state is a higher capability state.
  • shared APs can allocate time-domain resources.
  • APs in a multi-AP cooperative group can directly perform M-AP cooperative transmission.
  • AP1 sends an Initial Trigger Frame (MU-RTS) to all shared APs and STAs.
  • MU-RTS Initial Trigger Frame
  • the MU-RTS frame may carry the expected duration of the allocated TXOP.
  • the MU-RTS/CTS is primarily used to implement NAV protection.
  • AP1 sends a MU-RTS TXS frame with padding fields to AP2.
  • the MU-RTS TXS frame indicates information such as the duration of the shared TXOP with AP2 and traffic priority.
  • AP2 can independently wake up its associated STAs.
  • AP2 can send a CF-end frame to return the TXOP to AP1 and simultaneously switch back to a lower capability state.
  • AP1 continues to share the TXOP with AP3 following the same process.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending the padded MU-RTS TXS frame.
  • handover delay information including a first duration and/or a second duration
  • the initial trigger frame MU-RTS sent by AP1 can carry the expected M-AP cooperative transmission start time.
  • AP2 can automatically switch to a higher capability state before the expected M-AP cooperative transmission start time and wait for the TXOP allocation sent by AP1.
  • AP1 sending a trigger frame with a padding field can simultaneously wake up AP2 and STA2 in a lower capability state.
  • the trigger frame can carry cooperative transmission allocation information.
  • the length of the padding field can be the maximum value of the time required for an STA within BSS2 to switch from the first state to the second state.
  • AP1 may proactively request AP2 to send handover delay information (including a first duration and/or a second duration) before sending the trigger frame with the padding field.
  • handover delay information including a first duration and/or a second duration
  • the data transmission phase is synchronous, meaning that the sharing AP sends a trigger frame to the shared APs, initiating synchronous data transmission. If the shared APs need to return to their initial state before cooperative transmission, time must be reserved for media synchronization.
  • this application proposes a corresponding frame modification scheme.
  • M-AP collaboration capability information can be used to indicate whether an AP supports M-AP collaboration.
  • the M-AP collaboration support field can occupy 1 bit. For example, a value of 0 in the M-AP collaboration support field indicates that M-AP collaboration is supported; a value of 1 indicates that M-AP collaboration is not supported. Similarly, a value of 1 in the M-AP collaboration support field indicates that M-AP collaboration is supported; a value of 0 indicates that M-AP collaboration is not supported.
  • M-AP collaboration capability information can be carried in the coordinated M-AP support field.
  • the Collaborative M-AP Support field can be included in a capabilities element.
  • This capabilities element can be an EHT capabilities element.
  • the EHT MAC capabilities information field in an EHT capabilities element can include the Collaborative M-AP Support field.
  • the B14 reserved bit of the EHT MAC capabilities information field in related technologies can be modified to replace the Collaborative M-AP Support field.
  • Collaborative M-AP support fields can be carried in beacon frames or M-AP probe management frames.
  • the M-AP probe management frame can reuse the probe request frame from related technologies.
  • FIG 18 is a format example of an EHT MAC capability information field provided in an embodiment of this application.
  • the EHT MAC capability information field may include a cooperative M-AP support field.
  • the EHT MAC capability information field may also include one or more of the following fields: EPCS Priority Access Support, EHT OM Control Support, Triggered TXOP Sharing Mode 1 Support, Triggered TXOP Sharing Mode 2 Support, Restricted TWT Support, and SCS Traffic Description Support.
  • EHT includes: Trigger Support, Maximum MPDU Length, Maximum A-MPDU Length Exponent Extension, EHT TRS Support, TXOP Return Support in Triggered TXOP Sharing Mode 2, Two BQRs Support, and EHT Link Adaptation Support.
  • the AP has the ability to allocate TXOPs to other APs, or the AP has the ability to receive TXOP shares from other APs.
  • Beacon frames or M-AP probe management frames may include M-AP coordinated information elements. These elements can be used to indicate the M-AP coordinated parameters, capabilities, etc., supported by the AP.
  • FIG 19 is a format example of an M-AP collaboration information element.
  • an M-AP collaboration information element may include a "coordinated M-AP type support" field, and/or a "coordinated m-AP parameter information” field.
  • the parameter information field may include a "coordinated M-AP type support" field, and/or a "coordinated m-AP parameter information" field.
  • the M-AP type supports fields that indicate the supported M-AP collaboration schemes.
  • Table 1 shows examples of the values and meanings of the supported fields for the M-AP type.
  • Table 1 is only an example. Some entries in Table 1 can be implemented individually. The correspondences in Table 1 can be adjusted. Entries can be deleted or added to Table 1.
  • the collaborative M-AP parameter information field can be used to indicate the capabilities supported by the AP during M-AP collaboration.
  • the collaborative M-AP parameter information field can reuse the OM control field from related technologies.
  • Figure 20 is an example of the format of a cooperative M-AP parameter information field.
  • the M-AP parameter information field may include one or more of the following fields: channel width, 160/80+80BW, no LDPC, received NSS (Rx NSS), and received NSS type (Rx NSS type).
  • Operational elements in beacon frames or M-AP probe management frames can carry a dynamic power save enabled indication.
  • a dynamic power save enabled field can be added to the EHT Operation Parameters field of the EHT operation element.
  • the dynamic power saving enable field can occupy 1 bit.
  • This 1-bit field can be, for example, B6 of an EHT operand. For instance, a value of 0 in the dynamic power saving enable field indicates that dynamic power saving is not enabled; a value of 1 indicates that dynamic power saving is enabled. Similarly, a value of 1 indicates that dynamic power saving is not enabled; a value of 0 indicates that dynamic power saving is enabled.
  • the EHT operation element may also include one or more of the following fields: EHT operation information present, disabled subchannel bitmap present, EHT default PE duration, group addressed BU indication limit, group addressed BU indication exponent, and reserved.
  • the first piece of information can be carried in the DPS frame.
  • the DPS frame will be explained below.
  • a DPS frame may include a DPS control field.
  • the DPS control field can indicate one or more of the following information: the capability information of the first device in a first state, a first duration, a second duration, etc.
  • the DPS control field can indicate one or more of the following: the capability information of the first device in a lower capability state, its own state transition delay information, and the maximum state transition delay information of devices within the BSS.
  • a DPS frame can have one or more of the following fields: category, protected EHT action, DPS control field, and DPS switch information.
  • the DPS control field can be used to indicate capability information in a first state. For example, capability information in a lower capability mode.
  • the DPS control field can reuse the operating mode field.
  • Figure 23 shows an example format diagram of the DPS control field.
  • the DPS control field may include one or more of the following fields: channel bandwidth, 160/80+80BW, no LDPC, receive NSS, and receive NSS type.
  • the DPS handover information field can be used to indicate handover delay information.
  • Figure 24 shows an example of the format of the DPS handover information field.
  • the DPS handover information field may include a DPS padding delay field and/or a maximum padding delay field.
  • the DPS padding delay field can be used to indicate a first duration.
  • the maximum padding delay field can be used to indicate a second duration.
  • the maximum padding delay field can indicate the maximum padding delay required for capacity handover of all devices within the BSS.
  • the value of the DPS fill delay field can correspond to the value of the first duration.
  • Table 2 shows an example of this correspondence.
  • the third information can be carried in the pre-TX start field or the TX start field.
  • the value of the pre-TX start field or the TX start field can be the value of the third duration.
  • the unit can be microseconds ( ⁇ s).
  • the user information field in the trigger frame may include a pre-transmission start field.
  • Figure 25 is a schematic diagram of the format of the user information field in the trigger frame provided in an embodiment of this application. As shown in Figure 25, B40-B55 are the pre-transmission start fields. As shown in Figure 25, the user information field of the trigger frame may also include one or more of the following fields: AID12, RU allocation, ULFEC coding type, UL HE-MCS, UL DCM, SS allocation/RA-RU information, UL target receive power, and trigger dependent user information.
  • Figure 26 is a format example diagram of the common information field in the MU-RTS frame provided in the embodiments of this application.
  • the common information field of the MU-RTS frame may include a transmission start field.
  • B22-B30 can be the transmission start field.
  • the common information field of the MU-RTS frame may also include one or more of the following fields: trigger type, reserved, more TF, CS required, UL BW, HE/EHT P160, and special user information field flag.
  • a new C-MU-RTS frame can be defined.
  • the C-MU-RTS frame can reuse the MU-RTS frame in related technologies.
  • the format of the common information field of the C-MU-RTS frame can be shown in Figure 26.
  • the value of the trigger type field in the common information fields B0-B3 can be the first value.
  • the first value can be 8.
  • the first value indicates that the current frame type is C-MU-RTS.
  • the encoding format of the trigger field can be as shown in Table 3.
  • Figure 27A is an example diagram of the user information field format in a MU-RTS (or C-MU-RTS) frame provided in an embodiment of this application.
  • bits B0-B47 are the BSSID field.
  • the BSSID field can be used to indicate the BSS identifier of the shared AP.
  • the user information field in the MU-RTS frame may also include one or more of the following information: RU allocation, allocation duration, reservation, and PS160.
  • FIG 27B is a format example diagram of a MU-RTS (TXS) frame provided in an embodiment of this application.
  • the MU-RTS (TXS) frame can reuse the EHT MU-RTS (TXS) frame in related technologies.
  • Figure 27C is an example of the format of the common information field of a MU-RTS (TXS) frame.
  • the trigger TXOP sharing mode field located in B20-B21 of the common information field of a MU-RTS (TXS) frame can be set to 2, indicating that the frame is MU-RTS (TXS).
  • the shared AP can then interact with the associated STA in the allocated TXOP.
  • Figure 27D is an example of the format of the user information field in a MU-RTS (TXS) frame.
  • AID12 at B0-B11 can be the BSSID of the access point (AP), identifying different APs.
  • the allocation duration field at B20-B28 indicates the allocation time.
  • the RU allocation field at B12-B19 indicates the allocated frequency resources.
  • FIG 28 is a schematic structural diagram of a communication device 2800 provided in an embodiment of this application.
  • the communication device 2800 is a first access point (AP).
  • the communication device 2800 includes a receiving unit 2810.
  • the receiving unit 2810 is used to receive first information; wherein the first information is related to a first mode of the first device, and the first device includes a second AP and/or a STA associated with the second AP.
  • the communication device 2800 can be used to execute some or all of the method steps executed by the first AP in the above method embodiment.
  • the method flow has been described in detail in the foregoing embodiments.
  • the modules in this embodiment have the same function or perform the same steps, and will not be described again here.
  • those skilled in the art should know that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment and correspond to the modules in the communication device 2800.
  • the receiving unit 2810 may be a transceiver 3030.
  • the communication device 2800 may also include a processor 3010 and a memory 3020, as shown in FIG30.
  • Figure 29 is a schematic structural diagram of a communication device 2900 provided in this application.
  • the communication device 2900 is a first device.
  • the communication device 2900 includes a transmitting unit 2910.
  • the sending unit 2910 is used to send first information to the first AP; wherein the first information is related to a first mode of the first device, and the first device includes a second AP and/or a STA associated with the second AP.
  • the communication device 2900 can be used to execute some or all of the method steps executed by the first device in the above method embodiments.
  • the method flow has been described in detail in the foregoing embodiments.
  • the modules in this embodiment have the same function or perform the same steps, and will not be repeated here.
  • those skilled in the art should understand that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment, corresponding to the modules in the communication device 2900.
  • the transmitting unit 2910 may be a transceiver 3030.
  • the communication device 2900 may also include a processor 3010 and a memory 3020, as shown in FIG30.
  • Figure 30 is a schematic structural diagram of a communication apparatus according to an embodiment of this application.
  • the dashed lines in Figure 30 indicate that the unit or module is optional.
  • This apparatus 3000 can be used to implement the methods described in the above method embodiments.
  • the apparatus 3000 can be a chip or a communication device.
  • Apparatus 3000 may include one or more processors 3010.
  • the processor 3010 may support apparatus 3000 in implementing the methods described in the preceding method embodiments.
  • the processor 3010 may be a general-purpose processor or a special-purpose processor.
  • the processor may be a central processing unit (CPU).
  • the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the apparatus 3000 may further include one or more memories 3020.
  • the memories 3020 store a program that can be executed by the processor 3010, causing the processor 3010 to perform the methods described in the preceding method embodiments.
  • the memories 3020 may be independent of the processor 3010 or integrated within the processor 3010.
  • the device 3000 may also include a transceiver 3030.
  • the processor 3010 can communicate with other devices or chips through the transceiver 3030.
  • the processor 3010 can send and receive data with other devices or chips through the transceiver 3030.
  • This application also provides a computer-readable storage medium for storing a program.
  • This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.
  • the computer program product includes a program.
  • the computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.
  • This application also provides a computer program.
  • This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.
  • a “field” may also be referred to as a "domain", "subfield”, or “subfield”.
  • a field may occupy one or more bytes (byte/octet), or a field may occupy one or more bits (bit).
  • the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship.
  • a instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and/or other information.
  • correlate can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.
  • predefined or “preconfigured” can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including AP and STA).
  • predefined can refer to what is defined in the protocol.
  • the term "and/or” is merely a description of the relationship between related objects, indicating that three relationships can exist.
  • a and/or B can represent: A existing alone, A and B existing simultaneously, or B existing alone.
  • the character "/" in this document generally indicates that the preceding and following related objects have an "or" relationship.
  • “comprising” can refer to direct inclusion or indirect inclusion.
  • “comprising” mentioned in the embodiments of this application can be replaced with “indicating” or “used to determine”.
  • “A includes B” can be replaced with “A indicates B” or "A is used to determine B”.
  • the "protocol” may refer to a standard protocol in the field of communication, such as the WiFi protocol and related protocols applied to future WiFi communication systems, and this application does not limit it.
  • the disclosed systems, apparatuses, and methods can be implemented in other ways.
  • the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separate.
  • the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
  • the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
  • implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof.
  • software When implemented using software, it can be implemented entirely or partially in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
  • the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

提供了一种无线通信方法以及通信设备。该方法包括：第一AP接收第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。基于第一信息，一个AP可以获取到另一个AP(即第二AP)和/或另一个AP关联的STA的第一模式相关的信息，从而有针对性地进行M-AP协作过程，进而可以更加合理地安排或调度M-AP协作，使得M-AP协作能够达到预期的效果。

Description

无线通信方法以及通信设备 技术领域
本申请涉及通信技术领域，并且更为具体地，涉及一种无线通信方法以及通信设备。
背景技术
随着技术的发展，一些通信标准提出了多接入点(mutilate access point，M-AP)协作的技术方案。M-AP协作可以允许多个接入点(access point，AP)之间协作执行通信过程。例如，参与M-AP协作的多个AP可以共享传输资源，以提高传输资源利用率。
M-AP协作的技术方案存在改进空间。
发明内容
本申请提供一种无线通信方法以及通信设备。下面对本申请涉及的各个方面进行介绍。
第一方面，提供了一种无线通信方法，该方法包括：第一AP接收第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的站点(station，STA)。
第二方面，提供了一种无线通信方法，该方法包括：第一设备向第一AP发送第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。
第三方面，提供了一种通信设备，该通信设备为第一AP，该通信设备包括：接收单元，用于接收第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。
第四方面，提供了一种通信设备，该通信设备为第一设备，通信设备包括：发送单元，用于向第一AP发送第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。
第五方面，提供一种通信设备，包括处理器以及存储器，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序使得所述通信设备上述各个方面的方法中的部分或全部步骤。
第六方面，本申请实施例提供了一种通信系统，该系统包括上述的通信设备。在另一种可能的设计中，该系统还可以包括本申请实施例提供的方案中与该通信设备进行交互的其他设备。
第七方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序使得通信设备执行上述各个方面的方法中的部分或全部步骤。
第八方面，本申请实施例提供了一种计算机程序产品，其中，所述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，所述计算机程序可操作来使通信设备执行上述各个方面的方法中的部分或全部步骤。在一些实现方式中，该计算机程序产品可以为一个软件安装包。
第九方面，本申请实施例提供了一种芯片，该芯片包括存储器和处理器，处理器可以从存储器中调用并运行计算机程序，以实现上述各个方面的方法中所描述的部分或全部步骤。
基于第一信息，一个AP可以获取到另一个AP(即第二AP)和/或另一个AP关联的STA的第一模式相关的信息，从而有针对性地进行M-AP协作过程，进而可以更加合理地安排或调度M-AP协作，使得M-AP协作能够达到预期的效果。
附图说明
图1是本申请实施例应用的无线通信系统的示意图。
图2A是多AP协作的网络拓扑示例图。
图2B是一种多AP协作的场景示例图。
图2C是另一种多AP协作的场景示例图。
图2D是一种M-AP协作的框架示意图。
图3A是一种协作正交频分多址(coordinated orthogonal frequency division multiple access，C-OFDMA)传输中的协作带宽的示例图。
图3B是一种C-OFDMA传输的示意性流程图。
图4是协作上行多用户多进多出(uplink multi user multiple input multiple output，UL MU-MIMO)传输的示例图。
图5A是协作波束成形/调零的示例图。
图5B是一种显式的信道状态信息(channel state information，CSI)收集过程的示例图。
图6是协作空间复用的示例图。
图7是多AP联合传输的示例图。
图8A是协作时分多址(coordinated time division multiple access，C-TDMA)的示例图。
图8B是一个被共享AP的情况下C-TDMA过程的示例图。
图8C是多个被共享AP的情况下C-TDMA过程的示例图。
图9A是一种动态节能操作流程示意图。
图9B是一种动态节能操作流程示意图。
图10是本申请实施例提供的一种无线通信方法的示意性流程图。
图11A是一种第一信息传输过程的示例图。
图11B是另一种第一信息传输过程的示例图。
图12A是一种第一帧的传输过程示例图。
图12B是另一种第一帧的传输过程示例图。
图13是本申请实施例提供的一种C-OFDMA过程示例图。
图14A是本申请实施例提供的一种C-BF过程示例图。
图14B是本申请实施例提供的另一种C-BF过程示例图。
图15A是本申请实施例提供的一种J-TX过程示例图。
图15B是本申请实施例提供的另一种J-TX过程示例图。
图16A是本申请实施例提供的一种C-TDMA过程示例图。
图16B是本申请实施例提供的另一种C-TDMA过程示例图。
图17是本申请实施例提供的一种C-OFDMA过程示例图。
图18是本申请实施例提供的一种EHT MAC能力信息字段的格式示例图。
图19是一种M-AP协作信息元素的格式示例图。
图20是一种协作M-AP参数信息字段的格式示例图。
图21是EHT操作元素(EHT operation element)中的EHT操作参数字段的格式示例图。
图22是DPS帧的格式示例图。
图23是DPS控制字段的格式示例图。
图24为DPS切换信息字段的格式示例图。
图25是本申请实施例提供的触发帧中用户信息字段的格式示意图。
图26是本申请实施例提供的MU-RTS帧中公共信息字段的格式示意图。
图27A是本申请实施例提供的MU-RTS帧中用户信息字段格式示意图。
图27B是本申请实施例提供的一种MU-RTS(TXS)帧的格式示意图。
图27C是一种MU-RTS(TXS)帧的公共信息字段的格式示意图。
图27D是一种MU-RTS(TXS)帧的用户信息字段的格式示意图。
图28是本申请实施例提供的一种通信设备的示意性结构图。
图29是本申请实施例提供的另一种通信设备的示意性结构图。
图30是本申请实施例提供的一种用于通信的装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
通信系统
本申请实施例的技术方案可以应用于各种通信系统，例如：无线局域网(wireless local area networks，WLAN)、无线保真(wireless fidelity，WiFi)、高性能无线局域网(high performance radio local area networks，HIPELAN)、广域网(wide area networks，WAN)、蜂窝网或其他通信系统等。又例如，本申请实施例提供的技术方案可以应用于采用802.11标准的通信系统。示例性地，802.11标准包括但不限于：802.11ax标准，802.11be标准，更下一代的802.11标准等。
图1示出了本申请实施例适用的通信系统的示意图。参见图1所示，通信系统100中的通信设备可以包括AP111、AP112，以及站点(station，STA)121以及STA122，其中，STA121可以通过AP111接入网络，STA122可以通过AP112接入网络。
在一些实现方式中，STA可以与一个或多个AP建立关联关系，之后具有关联关系的STA和AP之间可以进行通信。参见图1所示，AP 111与STA 121之间可以在建立关联关系之后进行通信，AP 112与STA 122之间可以在建立关联关系之后进行通信。
在一些实现方式中，通信系统100中的通信可以是AP与non-AP STA之间的通信，也可以是non-AP STA与non-AP STA之间的通信，或者STA和peer STA之间的通信，其中，peer STA可以指与STA对端通信的设备，例如，peer STA可能为AP，也可能为non-AP STA。
应理解，图1示例性地示出了两个AP STA和两个non-AP STA，该通信系统100也可以包括更多数量的AP STA，或者该通信系统100可以包括其它数量的non-AP STA，本申请实施例对此不做限定。
另外，上述通信系统可以应用于多设备协作的场景，如多AP(multiple access points，multi-AP)协作，或者多站点协作等场景中。
在本申请实施例中，对AP和/或STA的名称不作限定。在一些场景中，AP又可以称为AP STA，即在某种意义上来说，AP也是一种STA。在另一些场景中，STA又可以称为非AP STA(non-AP STA)。
在一些场景中，上述通信设备还可以为“多链路设备(multi-link device，MLD)”，即可以通过多条通信链路进行通信的设备，其中，多条通信链路可以包括不同频段的通信链路，例如，可以包括毫米波频段和/或低频频段。通常，若多链路设备为AP，则该AP又可以称为“多链路AP”。若多链路设备为STA，则该STA又可以称为“多链路STA”。
在本申请实施例中，AP可以是无线网络中的设备。AP可以为通信服务器、路由器、交换机、网桥等通信实体，或，所述AP可以包括各种形式的宏基站，微基站，中继站等，当然AP还可以为这些各种形式的设备中的芯片或电路或处理系统，从而实现本申请实施例的方法和功能。AP可以应用于多种场景，比如为智慧城市中的传感器节点(比如，智能水表，智能电表，智能空气检测节点)，智慧家居中的智能设备(比如智能摄像头，投影仪，显示屏，电视机，音响，电冰箱，洗衣机等)，物联网中的节点，娱乐终端(比如AR，VR等可穿戴设备)，智能办公中智能设备(比如，打印机，投影仪等)，车联网中的车联网设备，日常生活场景中的一些基础设施(比如自动售货机，商超的自助导航台，自助收银设备，自助点餐机)等。
在一些实现方式中，STA在通信系统中的角色不是绝对的，在一些场景中，STA可以作为AP。例如，在手机连接路由的场景中，手机可以是non-AP STA，而在手机作为其他手机的热点的情况下，手机则充当了AP的角色。
在本申请实施例中，本申请实施例中的STA可以是具有无线收发功能的设备，比如可以为支持802.11系列协议，可以与AP或其他STA进行通信，例如，STA是允许用户与AP通信进而与WLAN通信的任何用户通信设备。STA例如为：用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
本申请实施例中的STA还可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。例如为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该STA还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，STA还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，在本申请实施例中，STA可以是车联网系统中的设备。车联网系统中的通信方式统称为V2X(X代表任何事物)。例如，该V2X通信包括：车辆与车辆(vehicle to vehicle，V2V)通信，车辆与路边基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
此外，在本申请实施例中，STA还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分终端设备)、接收AP的控制信息与下行数据，并发送电磁波，向AP传输数据。
另外，本申请实施例中的AP可以是用于与STA通信的设备，该AP可以是无线局域网中的网络设备，AP可用于与STA通过无线局域网进行通信。
从AP支持的通信制式的角度来介绍，在一些实现方式中，AP可以为支持802.11be制式的设备。AP也可以为支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来的802.11家族的WLAN制式的设备。
从STA支持的通信制式的角度来介绍，在一些实现方式中，non-AP STA可以支持802.11be制式。non-AP STA也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来的802.11家族的无线局域网(wireless local area networks，WLAN)制式。
在本申请实施例中，对WLAN技术可支持频段不作限定。在一些实现方式中，WLAN技术可支持频段可以包括但不限于：低频频段(例如2.4GHz、5GHz、6GHz)、高频频段(例如45GHz、60GHz)。
应理解，本申请实施例中对于STA和AP的具体形式不做特殊限制，在此仅是示例性说明。
M-AP协作
在BSS密集部署的环境中，M-AP协作技术能够显著地提高网络的吞吐量、提高频谱资源的利用率、降低设备间的相互干扰。M-AP协作可以包括M-AP协作传输或M-AP协作测量等技术。下面对M-AP协作的部分术语进行说明。
多AP候选集(candidate set)可以指的是能够发起或参与M-AP协作的AP的集合。
多AP协作集可以指的是参与多AP协作的AP的集合。多AP协作集可以是多AP候选集的子集。
共享AP(sharing AP)可以指的是获得TXOP并发起M-AP协作的AP。一个多AP候选集中至少有一个AP能够成为共享AP。
被共享AP(shared AP)可以参与同一多AP候选集中的共享AP发起的M-AP协作。
需要说明的是，参与协作的AP的角色可以为共享AP也可以为被共享AP，角色分配可以是动态的。例如，获取TXOP的AP可以为共享AP，其他参与协作的AP可以为被共享AP。
图2A为M-AP协作网络拓扑示例图。图2A所示的网络拓扑包含3个AP。3个AP均建立各自的BSS。其中，AP1和STA1相关联，AP2和STA2相关联，AP3和STA3相关联。AP间可以侦听到彼此。这些AP平等地竞争信道，任何一个竞争到TXOP的AP都可以成为共享AP。
图2B和图2C均为M-AP协作场景示例图。如图2B和图2C所示，OBSS中的任何AP都可以探测该OBSS中的任意其他节点。
M-AP协作的模式或方案可以包括：协作UL MU-MIMO、协作波束赋形(coordinated beamforming，C-BF)、协作空间复用(coordinated spatial reuse，C-SR)、多AP联合传输(joint transmission，J-TX)、C-TDMA以及C-OFDMA等。其中，图2B可以为C-BF和J-TX的场景图。图2C可以为C-TDMA或C-OFDMA场景图。
为便于理解，结合图2D举例说明M-AP协作的框架。如图2D所示，M-AP协作的框架可以包括以下阶段中的一项或多项：M-AP发现(discovery)阶段、协作传输协商(coordinate TX agreement)阶段、预传输(pre TX)阶段、M-AP协作传输(M-AP coordinated transmission)阶段。其中，M-AP发现阶段和协作传输协商阶段之间的相互独立的，并且是大多数M-AP协作传输方案必需的阶段。
在M-AP发现阶段，AP可以声明对M-AP协作能力的支持。在获取到TXOP前，每个AP都可以探测出一个多AP候选集。协作传输协商阶段可以在TXOP中进行。在协作传输协商阶段，获得TXOP的共享AP与其候选集内的被共享AP建立真正的多AP协作集。这个多AP协作集内的多个AP将参与协作。预传输是一个可选的阶段，对于某些M-AP方案，在数据传输前需要进行前期的准备工作。例如：对于C-OFDMA，可能需要切换主信道；对于C-BF或C-SR，可能需要信道探测。因此，C-OFDMA、C-BF或C-SR需要执行预传输阶段。M-AP协作传输阶段可以由共享AP触发。触发帧携带在该TXOP中分配给一个或多个被共享AP资源信息。其中，触发帧的接收方是在协作传输协商阶段决定的，即属于所述多AP协作集内的AP。
下文结合M-AP协作的不同模式，对M-AP协作进行详细举例说明。
C-OFDMA
在C-OFDMA传输中，共享AP和/或一个或多个被共享AP可以在协作带宽的不同频率部分发送各自下行多用户(downlink multi-user，DL MU)PPDU或向各自关联的STA发送请求上行数据的TB PPDU。
图3A是一种C-OFDMA传输中的协作带宽的示例图。如图3所示，协作带宽为40MHz。在40MHz中的20MHz部分，参与多AP传输的一个AP可以与关联的STA1、STA2或STA3交互数据。在40MHz 中的另外20MHz部分，参与多AP传输的另一个AP可以与关联的STA4或STA5交互数据。
图3B是一种C-OFDMA传输的示意性流程图。如图3B所示，该流程可以包括C-OFDMA准备(preparation for C-OFDMA)阶段和C-OFDMA TXOP共享SP(TXOP sharing SP for C-OFDMA)阶段。
在C-OFDMA TXOP共享SP阶段，共享AP发送触发(trigger)帧(例如基础触发(basic trigger)帧)，触发被共享AP(包括图3B所示的被共享AP1和被共享AP2)同时传输。触发帧可以携带TXOP共享所需要的分配信息。在接下来的数据传输中，被共享Ap可以使用预先分配的频率资源中传输自己的数据。
需要说明的是，在图3B所示的协作传输阶段之前，AP之间可以进行图2D中的M-AP发现阶段和/或协作传输协商阶段。
协作UL MU-MIMO
在M-AP协作UL MU-MIMO传输中，共享AP和/或一个或多个被共享AP可以在整个协作带宽上发送请求上行数据的TB PPDU，每个非AP STA被分配不同的空间流。例如，参与M-AP协作的一个或多个AP可以向各自关联的STA发送协作UL触发帧，响应于协作UL触发帧，STA可以发送上行数据帧。各个STA发送的上行数据帧可以完全对齐。
图4是协作UL MU-MIMO传输的示例图。如图4所示，被共享AP1(简称AP1)和STA1关联，被共享AP2(简称AP2)和STA2关联。共享AP发送多AP触发帧(multi-AP trigger frame，M-AP TF)。AP1向STA1发送协作UL触发帧。AP2向STA2发送协作UL触发帧。STA1和STA2均发送包括数据帧的UL PPDU。STA1和STA2发送的UL PPDU是完全对齐的。AP1收到STA1发送的UL PPDU后，向STA1发送块确认(block acknowledge，BA)帧。AP2收到STA2发送的UL PPDU后，向STA2发送BA帧。
协作波束成形
协作波束成形与调零(null steering)的原理类似，可以实现干扰抑制。例如，在进行数据发送/接收时，AP可以将朝向目标STA的波束增强。又如，在进行数据发送/接收时，AP可以朝向非目标STA的空间辐射调为零。
图5A为协作波束成形/调零的示例图。如图5A所示，AP1、STA1和STA2属于基本服务集(basic service set，BSS)1；AP2、STA3和STA4属于BSS2。AP1和AP2相互对对方的BSS内的STA进行调零。即，AP1对STA3和STA4的空间辐射调为零；AP2对STA1和STA2的空间辐射调为零。
协作波束成形过程可以包括以下4个阶段：
阶段0，半静态AP间的协作建立；
阶段1，增强空间重用机会(enhanced spatial reuse opportunity，eSRO)协作；
阶段2，CSI采集程序；
阶段3，带有空值(零位)的协作AP间数据传输和确认。
阶段0构建出一个多AP协作集合。阶段1，提供方AP(donor AP)可以主动广播其具有“调零”功能的eSRO。通过这种eSRO，donor AP期望减轻干扰的AP将做出响应并报告自己的ID。阶段2是CSI收集过程。一旦donor AP决定在AP间协作中需要被服务/调零的节点，参与其中的AP就需要相关的CSI来设置相应的波束/调零。在阶段3中，具有调零的协作AP间进行数据传输和确认。
图5B是一种显式的CSI收集过程的示例图。
协作空间复用
协作空间复用可以指的是：通过联合功率控制的方式，降低AP之间的干扰，从而使得多个AP可以并行传输，并将吞吐量总和最大化。
由于其不需要考虑同步和信道状态信息(channel state information，CSI)收集、不需要进行物理层(physical layer，PHY)更改、STA不需要协议更新、协作空间复用可以以相对较低的复杂度实现。换句话说，与其他M-AP协作方案相比，协作空间复用可以实现低复杂度和高性能(吞吐量和延迟)增益。
图6为协作空间复用的示例图。如图6所示，AP1和STA1属于BSS1；AP2和STA2属于BSS2。AP1和AP2之间可以传输控制信息。基于控制信息，AP1和AP2可以对对方的BSS内的STA进行干扰控制。即，AP1可以对STA2进行干扰控制；AP2可以对STA1进行干扰控制。
多AP联合传输
多AP联合传输(简称联合传输)指的是至少2个AP同时向目标用户(即目标STA)发送数据。多个AP发送的数据占据完全相同的频域资源(协作带宽)，并通过不同的空间流区分。对于接收数据的目标STA，联合传输是透明的。也就是说，目标STA无法区分接收到的数据是否是通过多AP联合传输的。在联合传输前，AP间可以通过回程链路(backhaul link)传输面向同一目标STA的数据。AP间可以通过有线连接或无线连接进行回程消息的传输。
图7为多AP联合传输的示例图。如图7所示，AP1和AP2可以实现多AP联合传输。AP1和AP2可以同时向STA1、STA2、STA3和STA4中的一个或多个发送数据。其中，STA1和STA2可以属于BSS1。STA3和STA4可以属于BSS2。AP1和AP2之间可以通过回程链路传输面向同一STA的数据。
相比单AP，多AP联合传输可以增加天线数量，从而增加总空间流数。并且，多AP联合传输可以同时服务多个STA，从而提高系统吞吐量。另外，多AP联合传输可以使得目标STA接收到的信道是来自多个位置的，从而增强了传输可靠性。
C-TDMA
C-TDMA可以指的是：共享AP分配其获得的TXOP中的某个时间段给被共享AP。在分配给被共享AP的时间段内，被共享AP可以进行任何PPDU传输，包括发送DL PPDU或请求UL PPDU。
图8A是C-TDMA的示例图。如图8所示，共享AP获取的TXOP(TXOP gained by sharing AP)可以被分配给被共享AP1和被共享AP2。在分配给被共享AP的时间(time allocation given to shared AP1)内，被共享AP1可以发送DL PPDU并接收对应的BA帧或者，在分配给被共享AP的时间内，被共享AP1可以发送触发帧，以请求上行基于触发的(trigger based，TB)PPDU。
图8B和图8C均是一种C-TDMA过程的示例图。
图8B示出了一个被共享AP的情况下C-TDMA过程的示例图。共享AP(即TXOP所有者，图8B中的AP1)发送调度声明(schedule announcement)帧，广播通知被共享AP(即被共享TXOP的AP)以及对应的BSS内的STA，共享AP将进行TXOP共享。这个帧的主要作用在于管理介质，并且被共享AP和对应BSS内的STA可以提前准备。其中，调度声明帧可以为多用户请求发送(multi-user request to send，MU-RTS)帧。另外，调度声明帧也可以提供TXOP的长度。接着，AP1和AP1的STA之间可以进行帧交换。AP1可以向指定的被共享AP(如图8B中的AP2)发送TXOP分配(allocation)帧，以通知共享的TXOP时间等分配信息。被共享AP可以通过CF-End帧将剩余的TXOP归还给共享AP。
图8C示出了多个被共享AP情况下C-TDMA过程的示例图。图8C和图8B的通信过程类似，不再赘述。
动态节能
为降低设备的功耗，相关技术对节能进行了研究。一些通信技术中提出了动态节能的技术方案，以进一步降低设备的功耗。动态节能技术可以适用于AP和non-AP STA端。在开启动态节能后，STA(包括AP或non-AP STA)可以默认处于较低能力模式(lower capability mode)。在较低能力模式下，STA的传输参数(或能力)将受到限制，无法达到其能力所能达到的最高传输参数。例如，在较低能力模式下，带宽(bandwidth，BW)和/或空间流数(number of spatial streams，NSS)会受到限制(例如：20MHz,1空间流(spatial streams，SS))。由于传输参数的限制，在较低能力模式下，STA只能接收特定的PPDU(即无法接收某些PPDU)。当处于较低能力模式的STA接收到切换请求时，STA可以从较低能力模式切换到较高能力模式(higher capability mode)。在较高能力模式下，STA的传输参数将不受到限制，或者，STA的传输参数可以高于较低能力模式下的传输参数。例如，在较高能力模式下，带宽和/或空间流数可以大于较低能力模式下的带宽和/或空间流数(例如：160MHz,2SS)。
发送方STA发送的切换请求可以用于请求响应方STA(或称为接收方STA)切换到更高能力模式。其中，切换请求例如可以为带有填充的初始控制帧(initial control frame，ICF)。
切换请求的发送方可以是AP也可以是STA。响应方STA可以切换到指定的唤醒状态，并回复一个响应帧给发送方STA。其中，响应帧例如可以为初始控制响应(initial control response，ICR)帧。这样的一组交互，就完成了对节能设备的唤醒(即切换到更高能力模式)。在接下来的帧交互过程中，发送方STA和接收方STA可以在唤醒状态下发送数据帧。
可选地，上文所述的ICF帧可以是MU-RTS触发帧或者块确认响应(block Ack response，BAR)帧。在这两种帧中，都需要在FCS字段前进行填充，从而使响应方STA有足够的时间切换到指定的唤醒状态。
较高能力模式(或唤醒状态)对应的BW/NSS等信息，可以从最新的Caps/OMN/OM控制(适用于AM和PS模式)中获取。
图9A是一种动态节能操作流程示意图。如图9A所示，在较低能力模式下，STA使用20MHz/1SS传输。第一个ICF帧指示STA切换到第一较高能力模式。第一较高能力模式下，STA使用80MHz/1SS传输。第二个ICF帧指示STA切换到第二较高能力模式，第二较高能力模式下，STA使用160MHz/2SS传输。
图9B是图9A的具体实施例。在图9B中，MU-RTS帧为第一个ICF帧。BAR帧为第二个ICF帧。
本申请发明人发现，在M-AP协作中，在通信设备处于某些状态的情况下，可能导致M-AP协作机制无法达成预期的工作目标。例如，如果某个或某些AP开启了动态节能模式，则该AP可能进入较低 能力模式。该所关联的某些STA也可能开启动态节能模式，因而这些STA也可能进入较低能力模式，共享AP可能请求该进入较低能力模式的AP加入多AP协作集，并为该AP分配协作传输资源。但是，由于该AP处于较低能力模式，则可能无法充分使用共享AP分配的资源(包括频域和/或时域资源)，从而导致资源的浪费。又如，如果某个或某些AP开启了动态节能模式，则参与M-AP协作的多个AP的状态可能不同，有的处于较高能力模式，有的处于较低能力模式，AP间状态不同步可能导致M-AP协作传输失败，无法实现真正的M-AP协作。
图10是本申请实施例提供的一种无线通信方法的示意性流程图，以解决上述问题。
图10可以由第一设备和第一AP执行。第一设备可以包括第二AP和/或与第二AP关联的STA。第一AP与第二AP可以是不同的AP。
在一些实施例中，第一AP可以包括共享AP。第二AP可以包括被共享AP。
需要说明的是，共享AP和一个或多个被共享AP可以参与M-AP协作。或者，共享AP可以不参与M-AP协作；两个或多个被共享AP可以参与M-AP协作。
图10所示的方法可以包括步骤S1010。
步骤S1010，第一AP接收第一信息。第一信息可以由第一设备发送。
第一信息可以与第一设备的第一模式相关。第一模式例如可以为包括节能模式。节能模式例如可以为动态节能模式。
在第一模式使能的情况下，第一设备可以处于第一状态或第二状态。在第一模式包括节能模式的情况下，第一状态可以为节能状态，第二状态可以为非节能状态；或者，第一状态可以为非节能状态，第二状态可以为节能状态。需要说明的是，节能状态和非节能状态可以是相对的。也就是说，对于相同的第一状态，在第二状态比第一状态节能的情况下，第一状态可以称为非节能状态，第二状态可以称为节能状态；或者，在第一状态比第二状态节能的情况下，第一状态可以称为节能状态，第二状态可以称为非节能状态。
需要说明的是，在节能状态下，第一设备的传输参数可能受到限制；或者，第一设备无法主动发送部分或全部信号；或者，第一设备无法接收部分或全部信号。在非节能模式下，第一设备的传输参数高于节能模式下的传输参数；或者，第一设备的传输参数不受限制；或者，第一设备能够接收器支持的全部信号；或者，第一设备能够发送其支持的全部信号。
示例性地，第一模式可以为动态节能模式。第一状态可以包括较低能力模式；第二状态可以包括较高能力模式。或者，第二状态可以包括较低能力模式；第一状态可以包括较高能力模式。或者，第一状态可以包括第一较高能力模式，第二状态可以包括第二较高能力模式。其中，第二较高能力模式对应的能力可以高于第一较高能力模式对应的能力。
第一状态和第二状态之间可以进行切换，即状态切换。状态切换可以包括第一状态切换到第二状态或者第二状态切换到第一状态。
可选地，在第一状态下，第一设备能够具备的能力可以为第一能力。在第二状态下第一设能够具备的能力可以为第二能力。其中，“能够具备的能力”可以为第一设备的能力上限。第一能力可以弱于第一设备具备的全能力(例如能力元素指示的能力)。第二能力可以强于第一能力。第二能力可以为全能力也可以为弱于全能力的能力。第一状态和第二状态之间的切换可以为第一能力和第二能力之间的切换。第一能力和第二能力之间的切换也可以称为能力切换。
基于第一信息，一个AP可以获取到另一个AP(即第二AP)和/或另一个AP关联的STA的第一模式相关的信息，从而有针对性地进行通信过程，进而提高通信效率和资源利用率。示例性地，当该方案应用在M-AP协作中时，基于第一信息可以更加合理地安排或调度M-AP协作，从而使得M-AP协作能够达到预期的效果。例如，第一AP为共享AP的情况下，共享AP可以基于第一信息合理进行资源调度，从而有效避免无效的资源分配导致的资源浪费。
在一些实施例中，第一信息可以包括以下中的一项或多项：使能信息、第一设备在第一时刻或第一时段所处的状态、第一时长、第二时长。下面分别进行说明。
使能信息可以用于指示第一设备是否开启第一模式。
在开启第一模式的情况下，第一设备所处的状态可以包括上文所述的第一状态或第二状态。也就是说，在开启第一模式的情况下，存在第一设备处于第一状态或第二状态的可能，或者存在状态切换的可能。
在未开启第一模式的情况下，第一设备所处的状态可以仅包括一个状态(例如第二状态)。例如，在未开启第一模式的情况下，第一设备的传输参数可以不受限制。在第一模式包括节能模式的情况下，在未开始节能模式的情况下，第一设备不会处于节能状态。
基于获取到的使能信息，第一AP建立多AP协作集时，第一AP可以执行对应的操作。例如，如 果第二AP第一模式使能，则第一AP建立的多AP协作集可以不包括第二AP。示例性地，在协作传输协商阶段，获取到TXOP的AP可以成为共享AP。共享AP可以向多AP候选集内的AP发送协作传输请求帧。接收到协作传输请求帧的AP可以发送响应帧以表示是否参与此次M-AP协作。响应帧可以包含被共享AP期望的分配时间、状态码(接收/拒绝)等信息。如果共享AP没有收到多AP候选集内某个AP的回复，则可以默认该AP拒绝加入M-AP协作。同意加入协作传输的AP与发送请求的共享AP建立一个M-AP协作传输协作集，这组AP将参与后续的协作传输。处于候选集，但未加入协作集的AP不会参与后续的协作传输。协作传输请求帧和响应帧的交互信息可以随着M-AP协作的方案不同有所不同。
例如，基于使能信息，第一AP可以确定向哪个或哪些AP发送协作传输请求帧。协作传输请求帧用于请求对端AP加入M-AP协作。协作传输请求帧可以包括M-AP协作传输的方案以及分配的时间等信息。例如，在第二AP的第一模式使能的情况下，第一AP可以不邀请或不允许第二AP加入多AP协作集。
第一设备在第一时刻或第一时段所处的状态可以包括上文所述的第一状态或第二状态。其中，第一时刻或第一时段可以包括当前时刻。也就是说，通过第一信息，第一设备可以向第一AP上报当前第一设备所处的状态。又如，第一时刻可以包括未来的时刻。也就是说，通过第一信息，第一设备可以向第一AP上报第一设备未来所处的状态。又如，第一时刻可以属于第一时间段，第一信息可以包括第一设备在第一时间段所处的状态。
第一AP可以根据第一设备在第一时刻或第一时段所处的状态确定与M-AP协作相关的操作。
可选地，如果第二AP处于第一状态，则第一AP可以不邀请或拒绝第二AP加入多AP协作。例如，第一AP可以不向第二AP发送协作传输请求帧。即对于多AP协作集中的AP，第一AP可以不向处于第一状态的AP发送协作传输请求帧。
可选地，如果第二AP处于第一状态，则第一AP可以邀请第二AP加入多AP协作。例如，第一AP可以向第二AP发送协作传输请求帧，请求第二AP加入协作传输。第二AP可以发送响应帧作为响应。响应帧可以包括后文所述的第一时长和/或第二时长等信息。
可选地，如果第一设备处于第一状态，则第一AP可以指示第一设备从第一状态切换到第二状态。示例性地，第一AP(例如在第一AP为共享AP的情况下)可以唤醒邻居AP和/或邻居AP关联的STA。例如，第一AP可以发送后文所述的第二信息或第三信息，以在合适的时刻指示第一设备从第一状态切换到第二状态。对于第一设备包括第二AP的情况，第一AP可以向第二AP发送协作传输请求帧，并且还可以发送第二信息或第三信息。
需要说明的是，在M-AP协作结束后，第一设备可以从第二状态切换回第一状态。例如，第一设备可以从较高能力状态切换回较低能力状态，从而节省第一设备的能耗。
第一时长可以用于指示第一设备从第一状态切换到第二状态的时长。也就是说，通过第一时长，第一设备可以用于指示自身从第一状态切换到第二状态的时长。例如，在第一模式包括节能模式的情况下，第一时长可以用于指示节能状态切换到非节能状态的时长，或者第一时长可以用于指示从较低能力模式切换到较高能力模式的时长。
第二时长可以用于指示第二设备从第一状态切换到第二状态的时长。其中，第二设备可以为第一设备所属的BSS内的设备。也就是说，通过第二时长，第一设备可以指示本BSS内的其他设备从第一状态切换到第二状态的时长。
可以理解的是，从第一状态切换到第二状态的时长可以为状态切换导致的时延，即切换时延。因此，第一时长和第二时长可以指示不同设备的切换时延。基于此，第一时长可以属于切换时延信息；和/或，第二时长可以属于切换时延信息。
在一些实施例中，第二设备可以属于第一设备所属的BSS内的多个设备。第二时长可以根据多个设备从第一状态切换到第二状态的时长确定。例如，第二时长可以为多个设备从第一状态切换到第二状态的时长的最大值。
在第二设备使能第一模式的情况下，第一设备如果需要与第二设备进行通信，第二设备也需要切换到第二状态。以第一模式为动态节能模式，第一设备为第二AP为例，若第二AP需要与第二AP的BSS内的STA(即第二设备)进行通信，该STA也需要切换到较高能力模式。因此，如果第一AP希望和第二AP进行M-AP协作，第二AP的BSS内的STA也需要切换到较高能力模式，才可以实现与第二AP的通信。因此，第一设备上报第二时长可以使得第一AP综合考虑第一设备所属的BSS内的其他STA的状态切换时长，从而有利于提高参与M-AP协作的第二AP的通信效率，避免资源浪费。
需要说明的是，在第一模式使能的情况下，第一信息可以包括以下信息中的一项或多项：第一设备在第一时刻或第一时段所处的状态、第一时长、第二时长。在第一模式不使能的情况下，第一信息可以 不包括以下信息中的一项或多项：第一设备在第一时刻或第一时段所处的状态、第一时长、第二时长。
第一信息中的信息可以包含在同一帧中，也可以包含在不同帧中。
在一些实施例中，在第一设备包括第二AP的情况下，第二AP发送的使能信息和/或第二AP是否支持M-AP协作的指示可以包含在信标帧或多AP协作管理(例如多AP探测管理(M-AP probe management))帧中。其中，信标帧或M-AP协作管理帧中可以携带信息元素多AP协作信息元素(M-AP coordinated information element)。多AP协作信息元素可以包括AP用于M-AP协作支持的部分或全部参数/功能。可选地，只有支持M-AP协作的AP才能解析多AP协作信息元素。示例性地，信标帧或M-AP协作管理帧可以包括使能字段，以指示所述使能信息。
在一些实施例中，第一设备在第一时刻或第一时段所处的状态、第一时长、第二时长中的一项或多项可以由动态节能(dynamic power save,DPS)帧携带。其中，该DPS帧可以称为DPS模式告知(DPS mode notification)帧。可选地，在第一模式使能的情况下，第一设备可以发送该DPS帧。在第一模式不使能的情况下，第一设备可以不发送该DPS帧。
在第一AP接收到第一信息的情况下，第一AP可以向第一设备反馈针对第一信息的响应，以告知第一设备第一AP已经接收到第一信息。例如，在第一信息承载在DPS帧的情况下，针对第一信息的响应也可以承载在DPS帧。
第一信息可以是第一设备主动发送的(unsolicited)，也可以是被动发送的(solicited)。示例性地，被动发送可以是由第一AP请求第一设备发送的。主动发送可以通过信标帧和/或AP间专用的协作管理帧发送。
在一些实施例中，第一信息可以是第一设备主动发送的。例如，在M-AP发现阶段，第一设备可以主动发送第一信息。示例性地，在M-AP发现阶段，第一设备可以通过发送信标帧发送第一信息。第一设备可以主动向所有邻居站点发送第一信息。例如，在多AP候选集建立前，各个AP可以主动发送第一信息。由于多AP候选集并未建立，因此，第一信息可以通过广播的方式发送。
下面结合图11A，以第一信息承载在DPS帧为例，说明第一信息的发送情况。在图11A中，第一AP为AP1或AP3，第一设备为AP2或AP2的STA2。在M-AP发现阶段，AP1、AP2和AP3建立候选集。AP2在信标帧中指示动态节能模式启动，AP1和AP3得知AP2开启动态节能模式。在建立多AP候选集后，AP2向AP1和AP3均发送DPS帧。该DPS帧可以指示AP2在第一时刻所处的状态、第一时长、第二时长中的一项或多项。在AP1和AP3接收到DPS帧后，可以记录AP2的状态等信息，并向AP2发送DPS帧以进行响应。
在一些实施例中，第一信息的发送可以是由第一AP发送的第一帧触发的。其中，第一帧可以用于请求发送第一信息。换句话说，第一信息可以是第一AP请求发送的。例如，在第一AP的多AP候选集建立完毕后，第一AP可以向多AP候选集中AP发送第一帧，以请求多AP候选集中的AP发送第一信息。在这种情况下，第二AP属于第一AP的多AP候选集。由此可知，基于第一帧触发发送的第一信息，可以针对性地向请求第一信息的AP发送第一信息，避免向不需要获知第一信息的设备发送第一信息导致的资源浪费。
在第一信息承载在DPS帧的情况下，第一帧可以为DPS帧。下面结合图11B进行说明。
在图11B中，第一AP可以为AP1，第二AP可以为AP2。如图11B所示，在协作传输协商阶段，AP1获取到TXOP，成为共享AP。AP1向AP2发送DPS帧以请求AP2发送第一信息。在收到AP1发送的DPS后，AP2向AP1发送DPS帧以响应AP1的请求。AP2发送的DPS帧可以包括第一信息。可选地，如果在协作传输协商阶段以及之前，AP2没有向AP1发送第一时长和/或第二时长，在协作传输协商阶段，如果AP2处于较低能力模式，则第一AP可以主动请求AP2发送第一时长和/或第二时长。
在一些实施例中，第一AP可以指示处于第一状态的第一设备切换到第二状态。例如，在第一AP发起M-AP协作的情况下，第一状态可以包括节能状态，第二状态可以包括非节能状态。也就是说，在第一AP发起M-AP协作的情况下，第一AP可以唤醒第一设备，以便参与M-AP协作的设备可以充分利用通信资源。
示例性地，第一AP可以指示第一设备从第一状态切换到第二状态。在第一设备完成状态切换(即第一时长后)的情况下，第一AP可以执行进一步的操作。例如，在第二状态为非节能状态的情况下，在第二AP切换到第二状态的情况下，第一AP才会与第二AP开始进行M-AP协作传输。或者，在开始进行M-AP协作前，第一设备需要完成切换到第二状态。即M-AP协作传输的开始时刻可以等于或晚于第一设备从第一状态切换到第二状态的时刻。
示例性地，第一AP可以指示第二设备从第一状态切换到第二状态。在第二设备完成状态切换(即第二时长后)的情况下，第一AP可以执行进一步的操作。例如，在第二状态为非节能状态的情况下，在第二AP的BSS内的所有STA或第二AP关联的所有STA均切换到第二状态的情况下，第一AP才 会与第二AP开始进行M-AP协作传输。
在一些实施例中，第一AP可以发送第二信息。第二信息可以用于指示第一设备从第一状态切换到第二状态的第二时刻。其中，第二时刻可以是第一设备完成状态切换的时刻。根据第二信息的指示，第一设备可以在第二时刻或第二时刻之前完成第一状态到第二状态的切换，或者说不晚于第二时刻完成第一状态到第二状态的切换。第一AP可以提前指示第一设备在什么时刻完成状态切换，以便第一设备提前开始执行状态切换，从而保证在后续操作前，第一设备已经完成了第一状态到第二状态的切换。
在一些实施例中，第一AP可以发送第三信息。第三信息可以用于指示第三时刻。其中，第三时刻可以为第一AP执行第一操作的开始时刻。例如，第三时刻可以为第一AP发起的多AP协作传输的开始时刻。第一设备可以根据第三信息，确定第一设备从第一状态切换到第二状态的时刻。例如，第一设备从第一状态切换到第二状态的时刻可以早于或等于第三时刻，或者说不晚于第三时刻。可以理解的是，第一AP可以不直接指示第二时刻(即隐式指示)，第一设备可以根据第三信息计算得到第二时刻。
示例性地，多AP协作集选择过程中，第一AP可以告知第一设备预期的M-AP协作传输开始时刻，从而指示处于较低能力模式的第一设备切换到较高能力模式的时刻，即唤醒的时刻，从而节省了显式唤醒所需要的开销。
在一些实施例中，第二信息或第三信息可以承载在第一帧中。其中，第一帧可以是预传输阶段传输的；和/或，M-AP协作传输阶段传输的。
在一些实施例中，第一AP可以发送第一帧。响应于第一设备接收到第一帧，第一设备可以从第一状态切换到第二状态。也就是说，在第一设备接收到某个特定的帧的情况下，第一设备即可立即执行状态的切换。第一帧的说明详见上文，此处不再赘述。
可选地，第一帧可以用于：请求第二AP加入多AP协作。例如，响应于第一AP请求第二AP加入多AP协作集，第一设备即可切换状态。
在一些实施例中，第一帧可以用于请求多个AP加入多AP协作集，多个AP可以包括第二AP。如在图12A中，第一帧为触发帧，第一AP为AP1，第二AP为AP2。在协作传输协商阶段，AP1同时请求AP2和AP3加入多AP协作集。AP1向AP2和AP3发送的触发帧中可包含第三信息，AP2接收到触发帧之后，在第三信息指示的第三时刻之前切换到第二状态。
在一些实施例中，第一帧可以仅用于请求一个AP加入多AP协作集，一个AP可以为第二AP。如在图12B中，第一帧为触发帧，第一AP为AP1，第二AP为AP2。在协作传输协商阶段，AP1先请求AP2加入多AP协作集。AP1向AP2发送的触发帧中可包含第三信息，AP2接收到触发帧之后，在第三信息指示的第三时刻之前切换到第二状态。AP1可以再请求AP3加入多AP协作集，在AP3的第一模式未使能，或者AP3处于第二状态的情况下，AP1向AP3发送的触发帧可以不包含第三信息。
可选地，第一帧可以用于：发起M-AP协作传输。例如，响应于第一AP发起多AP协作传输，第一设备即可切换状态。
可选地，第一帧可以用于：发起M-AP协作测量。例如，响应于第一AP发起多AP协作测量，第一设备即可切换状态。
可选地，第一帧可以用于：指示参与M-AP协作的AP的传输参数和/或传输资源。也就是说，第一帧可以用于宣告M-AP协作中的资源分配。例如，响应于第一AP指示第二AP参与M-AP协作的AP的传输参数和/或传输资源，第一设备即可切换状态。
在第一状态为非唤醒状态，第二状态为唤醒状态的情况下，第一帧可以用于唤醒第一设备。如上文所述，第一帧可以包括第一AP发送的，第一设备可以包括第二AP或与第二AP关联的STA。因此，唤醒第一设备的第一帧可以是邻居AP。若第一AP为共享AP，则第一帧可以用于共享AP唤醒被共享AP或被共享AP关联的STA。
在一些实施例中，第一帧可以包括填充(padding)字段。填充字段可以位于第一帧的尾部。例如，填充字段可以在FCS字段前，或者填充字段可以在FCS字段后。
在一些实施例中，上文所述的第一时长可以用于确定第一帧的填充长度。例如，填充长度可以大于或等于第一时长。在所述填充字段的传输时段中，第一设备可以执行完毕第一状态到第二状态的切换。
在一些实施例中，上文所述的第二时长可以用于确定第一帧的填充长度。例如，填充长度可以大于或等于第二时长。在所述填充字段的传输时段中，第二设备可以执行完毕第一状态到第二状态的切换。
在一些实施例中，第一帧的填充长度可以基于第一时长和第二时长确定。例如，填充长度可以大于或等于第一时长和第二时长中的最大值。在填充的传输过程中，第一设备和第二设备均可以执行完毕第一状态到第二状态的切换。
在一些实施例中，第一设备可以向第一AP发送第二帧。第二帧可以用于指示第一设备完成了从第一状态切换到第二状态。第二帧例如可以为允许发送(clear to send，CTS)帧。
为便于理解，下面结合不同模式的M-AP协作，以第一帧是预传输阶段传输的帧为例，进行说明。在下面的实施例中，第一AP可以为共享AP，第二AP可以为被共享AP，第一状态为较低能力状态，第二状态为较高能力状态。
C-OFDMA
在C-OFDMA方案中，如果协作集内存在开启动态节能的AP，其关联STA也随之处于较低能力状态。在预传输阶段，共享AP在宣告资源分配的同时可唤醒处于较低能力状态的被共享AP。共享AP可以发送带填充的C-MU-RTS帧(即第一帧)给被共享AP。C-MU-RTS中用户信息(user Info)字段中可以携带给被共享AP的资源分配信息。其中，C-MU-RTS帧中填充的长度是AP2发送的第二时长的值。其中，第二时长的值可以通过DPS填充时延字段指示。
处于较低能力状态的被共享AP切换到较高能力状态后，可以发送CTS帧作为响应。随后，被共享AP可以发送带填充的MU-RTS给关联的处于较低能力状态的STA。STA切换到较高能力状态以及MU-RTS帧指定的信道，发送CTS作为响应。
图13为一种C-OFDMA过程示例图。如图13所示，AP1发送的C-MU-RTS帧包括填充字段(图13通过AP2填充表示)，该填充字段的长度是基于AP2从第一状态切换到第二状态的时长确定的。AP2发送的MU-RTS帧包括填充字段(图13通过BSS2最大填充表示)，该填充字段的长度基于AP2的BSS(标记为BSS2)内的STA从第一状态切换到第二状态的时长最大值确定。
需要说明的是，在M-AP协作传输阶段开始前，多AP协作集内的AP及其关联的STA都需要切换到AP1指示的信道和能力。AP1可以发送广播的触发帧触发所有AP进行协作传输。在协作传输完成后，AP2可以切换回较低能力状态。
C-BF
C-BF中所有的STA都能监听到参与协作传输的AP。因此，AP2所关联的STA2也可以监听到AP1。
在预传输阶段，参与协作传输的所有AP都应该通过NDP进行信道探测来获得CSI信息。
如图14A所示，AP1可以在信道探测前发送带填充字段(图14A通过BSS2最大填充表示)的MU-RTS唤醒较低能力状态的AP2和STA2。其中，该填充字段的长度为AP2的BSS(标记为BSS2)内所有STA从第一状态切换到第二状态的时长最大值，从而保证唤醒BSS2内所有的较低能力状态设备。信道探测完成后，AP1发送触发帧触发所有AP同时进行C-BF传输。AP2可以在传输结束后，切换回较低能力状态。
可选地，AP1在发送带填充的MU-RTS帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
如图14B所示，AP1可以在NDPA帧中携带填充字段(图14B通过BSS2最大填充表示)唤醒较低能力状态的AP2和STA2。其中，该填充字段的长度为AP2的BSS(标记为BSS2)内所有STA从第一状态切换到第二状态的时长最大值，从而保证唤醒BSS2内所有的较低能力状态设备。信道探测完成后，AP1发送触发帧触发所有AP同时进行C-BF传输。AP2可以在传输结束后，切换回较低能力状态。
可选地，AP1在发送带填充的NDPA帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
J-TX
J-TX在数据传输前也需要进行信道探测操作，参与协作传输的所有的AP都需要STA发送全信道的CSI反馈。其中，可以由共享AP发送NDPA帧给协作集内所有被共享AP，触发被共享AP开启信道探测过程。
如图15A所示，在J-TX方案中，AP1可以发送带填充字段(图15A通过AP2填充表示)的MU-RTS来触发处于较低能力状态的AP2切换到较高能力状态，填充字段的长度可以是第一时长。
可选地，AP1在发送所述带填充字段的MU-RTS帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
如图15B所示，在J-TX方案中，AP1可以发送带填充字段(图15B通过AP2填充表示)的NDPA帧来触发处于较低能力状态的AP2切换到较高能力状态，填充字段的长度可以是第一时长。
可选地，AP1在发送所述带填充字段的MU-RTS帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
为便于理解，下面结合不同模式的M-AP协作，以第一帧是M-AP协作传输阶段传输的帧为例，说明第一帧的填充以及隐式唤醒的技术方案。在下面的实施例中，第一AP可以为共享AP，第二AP可以为被共享AP，第一状态为较低能力状态，第二状态为较高能力状态。
C-TDMA
在协作传输协商阶段，C-TDMA技术中，共享AP可以对时域资源进行分配，在协作传输协商阶段之后，多AP协作集中的AP可以直接进行M-AP协作传输。
AP1发送初始触发帧MU-RTS帧给所有的被共享AP以及STA。MU-RTS帧中可以携带分配的TXOP的预期持续时间。其中，MU-RTS/CTS主要是为了实现NAV保护。
如图16A所示，AP1发送带填充字段的MU-RTS TXS帧给AP2。其中，MU-RTS TXS帧可以指示与AP2共享TXOP的时长、流量优先级等信息。AP2在分配给自己的TXOP持续时间内，可以独立地唤醒关联的STA。当分配的时间到期时，AP2可以发送CF-end帧将TXOP返回给AP1，同时可以自行切换回到较低能力状态。AP1按照上述流程继续共享TXOP给AP3。
可选地，AP1在发送所述带填充的MU-RTS TXS帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
如图16B所示，在协作传输协商阶段，AP1发送的初始触发帧MU-RTS中可以携带预期的M-AP协作传输开始时间。AP2可以在预期的M-AP协作传输开始时间前自行切换到较高能力状态，并等待AP1发送的TXOP分配。
C-OFDMA
如图17所示，如果OBSS内的所有与AP1未关联的STA都能够收到AP1发送的帧，那么AP1发送带填充字段的触发帧能够同时唤醒较低能力状态的AP2和STA2。其中，触发帧可以携带协作传输的分配信息。为了唤醒AP2和STA2，填充字段的长度可以为BSS2内STA从第一状态切换到第二状态的时长的最大值。
可选地，AP1在发送所述带填充字段的触发帧之前可以主动请求AP2发送切换时延信息(包括第一时长和/或第二时长)。
需要说明的是，在C-OFDMA、C-BF和J-TX方案中，数据传输阶段是同步的，即由共享AP发送一个触发帧给被共享APs，触发同步的数据传输。如果被共享AP需要返回到协作传输前的初始状态，需要考虑为介质同步预留时间。
针对上述技术方案，本申请提出了对应的帧改动方案。
M-AP协作能力信息可以用于指示AP是否支持M-AP协作。协作M-AP支持字段可以占用1个比特。例如，协作M-AP支持字段的值为0可以表示支持M-AP协作；协作M-AP支持字段的值为1可以表示不支持M-AP协作。又如，协作M-AP支持字段的值为1可以表示支持M-AP协作；协作M-AP支持字段的值为0可以表示不支持M-AP协作。
M-AP协作能力信息可以承载在协作M-AP支持(coordinated M-AP support)字段。
协作M-AP支持字段可以包含在能力元素(capabilities element)中。其中，能力元素可以为EHT能力元素。示例性地，EHT能力元素中的EHT MAC能力信息(EHT MAC capabilities information)字段可以包括协作M-AP支持字段。例如，相关技术中EHT MAC能力信息字段的B14保留位可以修改为协作M-AP支持字段。
协作M-AP支持字段可以承载在信标帧或者M-AP探测管理帧。其中，M-AP探测管理帧可以复用相关技术中的探测请求(probe request)帧。
图18是本申请实施例提供的一种EHT MAC能力信息字段的格式示例图。如图18所示，EHT MAC能力信息字段可以包括协作M-AP支持字段。可选地，EHT MAC能力信息字段还可以包括以下字段中的一项或多项：EPCS优先接入支持(EPCS Priority Access Support)、EHT OM控制支持(EHT OM Control Support)、触发TXOP共享模式1支持(Triggered TXOP Sharing Mode 1Support)、触发TXOP共享模式2支持(Triggered TXOP Sharing Mode 2Support)、受限TWT支持(Restricted TWT Support)、SCS业务描述支持(SCS Traffic Description Support)、最大MPDU长度(Maximum MPDU Length)、最大A-MPDU长度指数扩展(Maximum A-MPDU Length Exponent Extension)、EHT TRS支持(EHT TRS Support)、在触发TXOP共享模式2中TXOP返回支持(TXOP Return Support In Triggered TXOP Sharing Mode 2)、两个BQR支持(Two BQRs Support)、EHT链路适应支持(EHT Link Adaptation Support)。
如果协作M-AP支持字段指示支持M-AP协作，且触发TXOP共享模式2支持字段的值为1，则可以指示AP具有可以分配TXOP给其他AP的能力，或者AP具有接收其他AP的TXOP共享的能力。
信标帧或M-AP探测管理帧可以包括M-AP协作信息元素(M-AP coordinated information element)。M-AP协作信息元素可以用于指示AP支持的M-AP协作参数、能力等。
图19是一种M-AP协作信息元素的格式示例图。如图19所示，M-AP协作信息元素可以包括协作M-AP类型支持(coordinated M-AP type support)字段，和/或，协作M-AP参数信息(coordinated m-AP  parameter information)字段。
M-AP类型支持字段可以指示支持的M-AP协作方案。表1为M-AP类型支持字段取值和对应的含义的示例。
表1
需要说明的是，表1仅为示例。表1中的部分条目可以单独实施。表1中的对应关系可以调整。表1可以删除或增加条目。
协作M-AP参数信息字段可以用于指示M-AP协作时，AP支持的能力信息。协作M-AP参数信息字段可以复用相关技术中的OM控制字段。
图20是一种协作M-AP参数信息字段的格式示例图。如图20所示，M-AP参数信息字段可以包括以下字段中的一项或多项：信道带宽(channel width)、160/80+80BW、无LDPC(no LDPC)、接收NSS(Rx NSS)、接收NSS类型(Rx NSS type)。
信标帧或者M-AP探测管理帧中的操作元素可以携带动态节能启用指示。如图21所示，可以在EHT操作元素(EHT operation element)中的EHT操作参数字段(EHT Operation Parameters field)中添加动态节能使能(dynamic power save enabled)字段。
动态节能使能字段可以占用1个比特。1个比特例如可以为EHT操作元素的B6。例如，动态节能使能字段的值为0可以指示设备没有开启动态节能；动态节能使能字段的值为1可以指示设备开启动态节能。又如，动态节能使能字段的值为1可以指示设备没有开启动态节能；动态节能使能字段的值为0可以指示设备开启动态节能。
如图21所示，EHT操作元素还可以包括以下字段中的一项或多项：EHT操作信息存在(EHT operation information present)、去使能子信道比特位图存在(disabled subchannel bitmap present)、EHT默认PE持续时间(EHT default PE duration)、组地址BU指示限制(group addressed BU indication limit)、组地址BU指示指数(group addressed BU indication exponent)、保留。
如上文所述，第一信息可以承载在DPS帧中。下面对DPS帧进行说明。
DPS帧可以包括DPS控制字段(DPS control filed)。DPS控制字段可以用于指示以下信息中的一项或多项：第一设备在第一状态下的能力信息、第一时长、第二时长等。例如，DPS控制字段可以指示第一设备在较低能力状态的能力信息、自身的状态切换时延信息、BSS内设备的状态切换时延最大值信息等中的一项或多项。
如图22所示，DPS帧可以以下字段中的一项或多项：分类(category)、保护EHT行动(Protected EHT Action)、DPS控制字段(DPS control field)、DPS切换信息(DPS Switch Info)。
DPS控制字段可以用于指示在第一状态下的能力信息。例如，在较低能力模式下的能力信息。DPS控制字段可以复用操作模式字段(operating mode field)。图23为DPS控制字段的格式示例图。DPS控制字段可以包括以下字段中的一项或多项：信道带宽、160/80+80BW、无LDPC、接收NSS、接收NSS类型。
DPS切换信息字段可以用于指示切换时延信息。图24为DPS切换信息字段的格式示例图。如图24所示，DPS切换信息字段可以包括DPS填充时延(DPS padding delay)字段，和/或最大填充时延(max padding delay)字段。DPS填充时延字段可以用于指示第一时长。最大填充时延)字段可以用于指示第二时长。例如，最大填充时延字段可以指示BSS内所有设备的能力切换所需填充时长的最大值。
DPS填充时延字段的取值可以与第一时长的取值存在对应关系。表2为该对应关系的示例。
表2
第三信息可以承载在预传输开始(pre TX start)字段或传输开始(TX start)字段。预传输开始字段或传输开始字段的值可以为第三时长的值。单位可以为微秒(μs)。
例如，在触发帧的用户信息(user Info)字段可以包括预传输开始字段。图25是本申请实施例提供的触发帧中用户信息字段的格式示意图。如图25所示，B40-B55为预传输开始字段。如图25所示，触发帧的用户信息字段还可以包括以下字段中的一项或多项：AID12、RU分配(RU allocation)、ULFEC编码类型(ULFEC coding type)、UL HE-MCS、UL DCM、SS分配/RA-RU信息(SS allocation/RA-RU information)、上行目标接收功率(UL target receive power)、触发相关用户信息(trigger dependent user Info)。
图26是本申请实施例提供的MU-RTS帧中公共信息字段的格式示例图。如图26所示，MU-RTS帧的公共信息字段可以包括传输开始字段。B22-B30可以为传输开始字段。如图26所示，MU-RTS帧的公共信息字段还可以包括以下字段中的一项或多项：触发类型(trigger type)、保留、更多TF(more TF)、要求CS(CS required)、UL BW、HE/EHT P160、特殊用户信息字段标记(special user Info field flag)。
又如，可以新定义一个C-MU-RTS帧。C-MU-RTS帧可以复用相关技术中的MU-RTS帧。C-MU-RTS帧的公共信息字段的格式可以如图26所示。
C-MU-RTS帧中，在公共信息字段B0-B3处的触发类型(trigger type)字段的值可以为第一值。第一值例如可以为8。第一值可以指示当前的帧类型为C-MU-RTS。触发字段的的编码格式可以如表3所示。
表3
图27A是本申请实施例提供的MU-RTS(或者C-MU-RTS)帧中用户信息字段格式示例图。如图27A所示，在B0-B47位为BSSID字段。BSSID字段可以用于指示共享AP的BSS标识。如图27A所示，MU-RTS帧中用户信息字段还可以包括以下信息中的一项或多项：RU分配(RU allocation)、分配时长(allocation duration)、保留、PS160。
图27B为本申请实施例提供的一种MU-RTS(TXS)帧的格式示例图。MU-RTS(TXS)帧可以复用相关技术中的EHT MU-RTS(TXS)帧。
图27C是一种MU-RTS(TXS)帧的公共信息字段的格式示例图。如图27C所示，在C-TDMA中使用的MU-RTS(TXS)帧在公共信息字段中位于B20-B21的触发TXOP共享模式字段可以设置为2，指示该帧是MU-RTS(TXS)。并且被共享AP可以在分配的TXOP中与关联的STA进行帧交互。
图27D是一种MU-RTS(TXS)帧的用户信息字段的格式示例图。用户信息字段中的B0-B11处的AID12可以是AP的BSSID，标识不同的AP。B20-B28处的分配时长字段可以指示分配的时间。B12-B19处的RU分配字段可以指示分配的频率资源。
上文详细描述了本申请的方法实施例，下面详细描述本申请的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图28是本申请实施例提供的一种通信设备2800的示意性结构图。通信设备2800为第一AP。通信设备2800包括接收单元2810。
接收单元2810用于接收第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。
在本申请实施例中，上述通信设备2800可以用于执行上述方法实施例中第一AP执行的部分或全部方法步骤。在前述实施方式中已经对方法流程有过详细的描述，本实施例中的模块具有相同的功能或者执行相同的步骤，此处不再赘述，但是作为本领域技术人员应知晓，前述方法实施例所对应的文字描述可引入本实施例，与通信设备2800中的模块相对应。
在可选的实施例中，所述接收单元2810可以为收发器3030。通信设备2800还可以包括处理器3010和存储器3020，具体如图30所示。
图29是本申请提供的一种通信设备2900的示意性结构图。通信设备2900为第一设备。通信设备2900包括发送单元2910。
发送单元2910用于向第一AP发送第一信息；其中，第一信息与第一设备的第一模式相关，第一设备包括第二AP和/或与第二AP关联的STA。
在本申请实施例中，上述通信设备2900可以用于执行上述方法实施例中第一设备执行的部分或全部方法步骤。在前述实施方式中已经对方法流程有过详细的描述，本实施例中的模块具有相同的功能或者执行相同的步骤，此处不再赘述，但是作为本领域技术人员应知晓，前述方法实施例所对应的文字描述可引入本实施例，与通信设备2900中的模块相对应。
在可选的实施例中，所述发送单元2910可以为收发器3030。通信设备2900还可以包括处理器3010和存储器3020，具体如图30所示。
图30是本申请实施例的用于通信的装置的示意性结构图。图30中的虚线表示该单元或模块为可选的。该装置3000可用于实现上述方法实施例中描述的方法。装置3000可以是芯片或通信设备。
装置3000可以包括一个或多个处理器3010。该处理器3010可支持装置3000实现前文方法实施例所描述的方法。该处理器3010可以是通用处理器或者专用处理器。例如，该处理器可以为中央处理单元(central processing unit，CPU)。或者，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
装置3000还可以包括一个或多个存储器3020。存储器3020上存储有程序，该程序可以被处理器3010执行，使得处理器3010执行前文方法实施例所描述的方法。存储器3020可以独立于处理器3010也可以集成在处理器3010中。
装置3000还可以包括收发器3030。处理器3010可以通过收发器3030与其他设备或芯片进行通信。例如，处理器3010可以通过收发器3030与其他设备或芯片进行数据收发。
本申请实施例还提供一种计算机可读存储介质，用于存储程序。该计算机可读存储介质可应用于本申请实施例提供的通信设备中，并且该程序使得计算机执行本申请各个实施例中的由通信设备执行的方法。
本申请实施例还提供一种计算机程序产品。该计算机程序产品包括程序。该计算机程序产品可应用于本申请实施例提供的通信设备中，并且该程序使得计算机执行本申请各个实施例中的由通信设备执行的方法。
本申请实施例还提供一种计算机程序。该计算机程序可应用于本申请实施例提供的通信设备中，并且该计算机程序使得计算机执行本申请各个实施例中的由通信设备执行的方法。
应理解，本申请中术语“系统”和“网络”可以被可互换使用。另外，本申请使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。
在本申请的实施例中，“字段”也可以称之为“域(field)”、“子域(subfield)”或“子字段”。一个字段可以占用一个或多个字节(byte/octet)，或者，一个字段可以占用一个或多个比特(bit)。
在本申请的实施例中，提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请实施例中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，“预定义”或“预配置”可以通过在设备(例如，包括AP和STA)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请的实施例中，所述“包括”可以指直接包括，也可以指间接包括。可选地，可以将本申请实施例中提到的“包括”替换为“指示”或“用于确定”。例如，A包括B，可以替换为A指示B，或A用于确定B。
在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本申请实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括WiFi协议以及应用于未来的WiFi通信系统中的相关协议，本申请对此不做限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital video disc，DVD))或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (48)

  1. 一种无线通信方法，其特征在于，包括：
    第一接入点AP接收第一信息；
    其中，所述第一信息与所述第一设备的第一模式相关，所述第一设备包括第二AP和/或与所述第二AP关联的站点STA。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括以下中的一项或多项：
    使能信息，用于指示所述第一设备是否开启所述第一模式，在开启所述第一模式的情况下，所述第一设备所处的状态包括第一状态或第二状态；
    所述第一设备在第一时刻或第一时段所处的状态；
    第一时长，用于指示所述第一设备从第一状态切换到第二状态的时长；
    第二时长，用于指示第二设备从第一状态切换到第二状态的时长，其中，所述第二设备为所述第一设备所属的BSS内的设备。
  3. 根据权利要求2所述的方法，其特征在于，所述第一时长和/或第二时长用于确定第一AP发送的第一帧的填充长度。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第二设备属于所述第一设备所属的BSS内的多个设备，所述第二时长用于指示所述多个设备从第一状态切换到第二状态的时长的最大值。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一信息的发送是由所述第一AP发送的第一帧触发的，所述第一帧用于请求发送所述第一信息。
  6. 根据权利要求3或5所述的方法，其特征在于，所述第一帧用于：
    请求所述第二AP加入多AP协作；或者
    发起多AP协作传输；或者
    发起多AP协作测量。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一AP发送第二信息；
    其中，所述第二信息用于指示所述第一设备从第一状态切换到第二状态的第二时刻。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一AP根据所述第一信息进行多AP协作。
  9. 根据权利要求8所述的方法，其特征在于，如果所述第二AP处于第一状态，则所述第一AP不邀请或拒绝所述第二AP加入多AP协作。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述第一模式为与节能相关的模式。
  11. 根据权利要求10中所述的方法，其特征在于，所述第一模式为动态节能模式，在开启所述动态第一模式的情况下，所述第一设备所处的状态包括较低能力模式或较高能力模式。
  12. 一种无线通信方法，其特征在于，包括：
    第一设备向第一接入点AP发送第一信息；
    其中，所述第一信息与所述第一设备的第一模式相关，所述第一设备包括第二AP和/或与所述第二AP关联的站点STA。
  13. 根据权利要求12所述的方法，其特征在于，所述第一信息包括以下中的一项或多项：
    使能信息，用于指示所述第一设备是否开启所述第一模式，在开启所述第一模式的情况下，所述第一设备所处的状态包括第一状态或第二状态；
    所述第一设备在第一时刻或第一时段所处的状态；
    第一时长，用于指示所述第一设备从第一状态切换到第二状态的时长；
    第二时长，用于指示第二设备从第一状态切换到第二状态的时长，其中，所述第二设备为所述第一设备所属的BSS内的设备。
  14. 根据权利要求13所述的方法，其特征在于，所述第一时长和/或第二时长用于确定第一AP发送的第一帧的填充长度。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第二设备属于所述第一设备所属的BSS内的多个设备，所述第二时长用于指示所述多个设备从第一状态切换到第二状态的时长的最大值。
  16. 根据权利要求12-15中任一项所述的方法，其特征在于，所述第一信息的发送是由所述第一AP发送的第一帧触发的，所述第一帧用于请求发送所述第一信息。
  17. 根据权利要求14或16所述的方法，其特征在于，所述第一帧用于：
    请求所述第二AP加入多AP协作；或者
    发起多AP协作传输；或者
    发起多AP协作测量。
  18. 根据权利要求12-17中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收所述第一AP发送的第二信息；
    其中，所述第二信息用于指示所述第一设备从第一状态切换到第二状态的第二时刻。
  19. 根据权利要求12-17中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收所述第一AP发送的第三信息；
    所述第一设备根据第三信息确定所述第一设备从第一状态切换到第二状态的时刻；
    其中，所述第三信息用于指示第三时刻，所述第三时刻为所述第一AP发起的多AP协作传输的开始时刻。
  20. 根据权利要求12-19中任一项所述的方法，其特征在于，所述第一模式为与节能相关的模式。
  21. 根据权利要求20中所述的方法，其特征在于，所述第一模式为动态节能模式，在开启所述动态第一模式的情况下，所述第一设备所处的状态包括较低能力模式或较高能力模式。
  22. 一种通信设备，其特征在于，所述通信设备为第一接入点AP，所述通信设备包括：
    接收单元，用于接收第一信息；
    其中，所述第一信息与所述第一设备的第一模式相关，所述第一设备包括第二AP和/或与所述第二AP关联的站点STA。
  23. 根据权利要求22所述的通信设备，其特征在于，所述第一信息包括以下中的一项或多项：
    使能信息，用于指示所述第一设备是否开启所述第一模式，在开启所述第一模式的情况下，所述第一设备所处的状态包括第一状态或第二状态；
    所述第一设备在第一时刻或第一时段所处的状态；
    第一时长，用于指示所述第一设备从第一状态切换到第二状态的时长；
    第二时长，用于指示第二设备从第一状态切换到第二状态的时长，其中，所述第二设备为所述第一设备所属的BSS内的设备。
  24. 根据权利要求23所述的通信设备，其特征在于，所述第一时长和/或第二时长用于确定第一AP发送的第一帧的填充长度。
  25. 根据权利要求23或24所述的通信设备，其特征在于，所述第二设备属于所述第一设备所属的BSS内的多个设备，所述第二时长用于指示所述多个设备从第一状态切换到第二状态的时长的最大值。
  26. 根据权利要求22-25中任一项所述的通信设备，其特征在于，所述第一信息的发送是由所述第一AP发送的第一帧触发的，所述第一帧用于请求发送所述第一信息。
  27. 根据权利要求24或26所述的通信设备，其特征在于，所述第一帧用于：
    请求所述第二AP加入多AP协作；或者
    发起多AP协作传输；或者
    发起多AP协作测量。
  28. 根据权利要求22-27中任一项所述的通信设备，其特征在于，所述通信设备还用于：
    发送第二信息；
    其中，所述第二信息用于指示所述第一设备从第一状态切换到第二状态的第二时刻。
  29. 根据权利要求22-28中任一项所述的通信设备，其特征在于，所述通信设备还用于：
    根据所述第一信息进行多AP协作。
  30. 根据权利要求29所述的通信设备，其特征在于，如果所述第二AP处于第一状态，则所述第一AP不邀请或拒绝所述第二AP加入多AP协作。
  31. 根据权利要求22-30中任一项所述的通信设备，其特征在于，所述第一模式为与节能相关的模式。
  32. 根据权利要求31中所述的通信设备，其特征在于，所述第一模式为动态节能模式，在开启所述动态第一模式的情况下，所述第一设备所处的状态包括较低能力模式或较高能力模式。
  33. 一种通信设备，其特征在于，所述通信设备为第一设备，所述通信设备包括：
    发送单元，用于向第一接入点AP发送第一信息；
    其中，所述第一信息与所述第一设备的第一模式相关，所述第一设备包括第二AP和/或与所述第二AP关联的站点STA。
  34. 根据权利要求33所述的通信设备，其特征在于，所述第一信息包括以下中的一项或多项：
    使能信息，用于指示所述第一设备是否开启所述第一模式，在开启所述第一模式的情况下，所述第一设备所处的状态包括第一状态或第二状态；
    所述第一设备在第一时刻或第一时段所处的状态；
    第一时长，用于指示所述第一设备从第一状态切换到第二状态的时长；
    第二时长，用于指示第二设备从第一状态切换到第二状态的时长，其中，所述第二设备为所述第一设备所属的BSS内的设备。
  35. 根据权利要求34所述的通信设备，其特征在于，所述第一时长和/或第二时长用于确定第一AP发送的第一帧的填充长度。
  36. 根据权利要求34或35所述的通信设备，其特征在于，所述第二设备属于所述第一设备所属的BSS内的多个设备，所述第二时长用于指示所述多个设备从第一状态切换到第二状态的时长的最大值。
  37. 根据权利要求33-36中任一项所述的通信设备，其特征在于，所述第一信息的发送是由所述第一AP发送的第一帧触发的，所述第一帧用于请求发送所述第一信息。
  38. 根据权利要求35或37所述的通信设备，其特征在于，所述第一帧用于：
    请求所述第二AP加入多AP协作；或者
    发起多AP协作传输；或者
    发起多AP协作测量。
  39. 根据权利要求33-38中任一项所述的通信设备，其特征在于，所述通信设备还用于：
    接收所述第一AP发送的第二信息；
    其中，所述第二信息用于指示所述第一设备从第一状态切换到第二状态的第二时刻。
  40. 根据权利要求33-38中任一项所述的通信设备，其特征在于，所述通信设备还应用于：
    接收所述第一AP发送的第三信息；
    根据第三信息确定所述第一设备从第一状态切换到第二状态的时刻；
    其中，所述第三信息用于指示第三时刻，所述第三时刻为所述第一AP发起的多AP协作传输的开始时刻。
  41. 根据权利要求33-40中任一项所述的通信设备，其特征在于，所述第一模式为与节能相关的模式。
  42. 根据权利要求41中所述的通信设备，其特征在于，所述第一模式为动态节能模式，在开启所述动态第一模式的情况下，所述第一设备所处的状态包括较低能力模式或较高能力模式。
  43. 一种通信设备，其特征在于，包括收发器、存储器和处理器，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，并控制所述收发器接收或发送信号，以使所述通信设备执行如权利要求1-21中任一项所述的方法。
  44. 一种装置，其特征在于，包括处理器，用于从存储器中调用程序，以使所述装置执行如权利要求1-21中任一项所述的方法。
  45. 一种芯片，其特征在于，包括处理器，用于从存储器调用程序，使得安装有所述芯片的设备执行如权利要求1-21中任一项所述的方法。
  46. 一种计算机可读存储介质，其特征在于，其上存储有程序，所述程序使得计算机执行如权利要求1-21中任一项所述的方法。
  47. 一种计算机程序产品，其特征在于，包括程序，所述程序使得计算机执行如权利要求1-21中任一项所述的方法。
  48. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1-21中任一项所述的方法。
PCT/CN2024/094079 2024-05-17 2024-05-17 无线通信方法以及通信设备 Pending WO2025236304A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/094079 WO2025236304A1 (zh) 2024-05-17 2024-05-17 无线通信方法以及通信设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/094079 WO2025236304A1 (zh) 2024-05-17 2024-05-17 无线通信方法以及通信设备

Publications (1)

Publication Number Publication Date
WO2025236304A1 true WO2025236304A1 (zh) 2025-11-20

Family

ID=97719238

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/094079 Pending WO2025236304A1 (zh) 2024-05-17 2024-05-17 无线通信方法以及通信设备

Country Status (1)

Country Link
WO (1) WO2025236304A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112188563A (zh) * 2019-07-02 2021-01-05 华为技术有限公司 协作通信方法、装置及系统
CN116636252A (zh) * 2020-12-15 2023-08-22 松下电器（美国）知识产权公司 用于协调服务时段的通信装置和通信方法
WO2023155149A1 (zh) * 2022-02-18 2023-08-24 Oppo广东移动通信有限公司 无线通信的方法和设备
CN117426124A (zh) * 2021-06-21 2024-01-19 三星电子株式会社 用于多ap运行的twt协调

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112188563A (zh) * 2019-07-02 2021-01-05 华为技术有限公司 协作通信方法、装置及系统
CN116636252A (zh) * 2020-12-15 2023-08-22 松下电器（美国）知识产权公司 用于协调服务时段的通信装置和通信方法
CN117426124A (zh) * 2021-06-21 2024-01-19 三星电子株式会社 用于多ap运行的twt协调
WO2023155149A1 (zh) * 2022-02-18 2023-08-24 Oppo广东移动通信有限公司 无线通信的方法和设备

Similar Documents

Publication Publication Date Title
US20230007684A1 (en) Method and apparatus for coordinated communication
US11602002B2 (en) Method and apparatus for multi-link operations
AU2021256154B2 (en) Communications method and communications apparatus
JP2023520069A (ja) アクセスポイントａｐマルチリンクデバイス発見方法および関連装置
TW202418870A (zh) 通訊方法及裝置
CA3177223A1 (en) Communication method, communication apparatus, chip and computer-readable storage medium applied to multilink device in wireless local
CN113938912B (zh) 数据传输方法及装置
WO2023236821A1 (zh) 多链路通信方法及装置
WO2023116352A1 (zh) 基于目标唤醒时间的通信方法、装置及系统
WO2023093747A1 (zh) 一种通信方法及装置
US20240097838A1 (en) Primary and non-primary subchannels in a basic service set of a wireless network
US12610316B2 (en) Low power listening mode for stations of a wireless network
WO2024174970A1 (zh) 多链路通信方法及装置
WO2025236304A1 (zh) 无线通信方法以及通信设备
WO2024067517A1 (zh) 一种通信方法及装置
US20260121717A1 (en) System and method for cbf sounding
US20260121698A1 (en) Operating state transitions in overlapping basic service sets
US20260059450A1 (en) Method and apparatus for power saving in wi-fi communication
US20260089642A1 (en) Transmission control method, apparatus, and storage medium
WO2025166559A1 (zh) 无线通信方法以及通信设备
WO2025166564A1 (zh) 无线通信方法以及通信设备
WO2026016129A1 (zh) 无线通信方法、非接入点站点以及接入点
WO2026081128A1 (zh) 通信方法、装置、设备、介质和程序产品
KR20260004939A (ko) 와이파이 통신을 위한 자원을 공유하는 방법 및 장치
WO2024255612A1 (zh) 协作通信的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24938326

Country of ref document: EP

Kind code of ref document: A1