Cooperative transmission method, device, medium and product
By using a cooperative transmission method, the initiating access point and the responding access point negotiate channel access capability parameters and coordinate the operation of multiple access points, thus solving the problem of low communication efficiency in the OBSS scenario and achieving more efficient communication and more reliable latency control.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- SANECHIPS TECH CO LTD
- Filing Date
- 2025-12-25
- Publication Date
- 2026-07-30
AI Technical Summary
In OBSS scenarios, the lack of R-TWT operation coordination among multiple access points leads to reduced communication efficiency, which has a significant impact on latency-sensitive applications.
By using a cooperative transmission method, the initiating access point and the responding access point negotiate channel access capability parameters and coordinate the operations of multiple access points to improve communication efficiency.
By negotiating and determining the channel access capability parameters, the cooperative transmission method can effectively reduce OBSS interference and improve communication efficiency, especially providing more predictable latency and higher reliability for latency-sensitive applications.
Smart Images

Figure CN2025145745_30072026_PF_FP_ABST
Abstract
Description
Collaborative transmission methods, equipment, media and products
[0001] Cross-reference to related applications
[0002] This application is based on and claims priority to Chinese Patent Application No. 2025101162073, filed on January 24, 2025, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communication technology, and in particular to a cooperative transmission method, network device and storage medium. Background Technology
[0004] R-TWT (Restricted Target Wake Time) aims to provide more predictable latency, lower worst-case latency, and / or lower jitter for latency-sensitive applications, and to offer greater reliability for this traffic. In some scenarios (such as OBSS scenarios), the lack of R-TWT operational coordination among multiple access points makes them susceptible to interference from OBSS (Overlapping Basic Service Set), leading to reduced communication efficiency.
[0005] Therefore, it is necessary to propose a solution to improve communication efficiency. Summary of the Invention
[0006] The main objective of this application is to provide a collaborative transmission method, device, storage medium, and computer program product, which aims to improve communication efficiency.
[0007] To achieve the above objectives, embodiments of this application provide a cooperative transmission method, which is applied to an initiating access point, and the method includes:
[0008] When at least one response access point supports channel access with a limited target wake-up time based on cooperation, the parameters of the channel access capability are negotiated with the at least one response access point so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the negotiated parameters of the channel access capability.
[0009] This application embodiment also provides a cooperative transmission method, which is applied to at least one response access point, and the method includes:
[0010] In the case of supporting channel access based on cooperation with limited target wake-up time initiated by the initiating access point, the parameters of the channel access capability are negotiated with the initiating access point;
[0011] Based on the negotiated parameters of the channel access capability, data is exchanged with the terminal corresponding to the at least one response access point.
[0012] This application embodiment also provides a cooperative transmission device, which is applied to an initiating access point, and the device includes:
[0013] The first negotiation module is used to negotiate with the at least one response access point to determine the parameters of the channel access capability when the at least one response access point supports channel access based on cooperative limitation of target wake-up time, so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability.
[0014] This application embodiment also provides a cooperative transmission device, which is applied to at least one response access point, and the device includes:
[0015] The second negotiation module is used to negotiate with the initiating access point to determine the parameters of the channel access capability when supporting channel access based on cooperation and limited target wake-up time initiated by the initiating access point.
[0016] An interaction module is used to perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability.
[0017] This application also provides a network device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the cooperative transmission method described above.
[0018] This application embodiment also provides a storage medium, which is a computer-readable storage medium, and stores a computer program thereon. When the computer program is executed by a processor, it implements the steps of the cooperative transmission method described above.
[0019] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the cooperative transmission method described above.
[0020] This application discloses a cooperative transmission method applied to an initiating access point. The method includes: negotiating with the at least one responding access point on parameters of the channel access capability when at least one responding access point supports channel access based on cooperative target wake-up time limitation, so that the at least one responding access point interacts with the terminal corresponding to the at least one responding access point based on the negotiated channel access capability parameters. By negotiating with at least one responding access point that supports channel access based on cooperative target wake-up time limitation, the operation of multiple access points can be coordinated, thereby improving communication efficiency. Attached Figure Description
[0021] Figure 1 is a schematic diagram of a wireless communication network in an embodiment of this application;
[0022] Figure 2 is a schematic diagram of the structure of the wireless communication device in an embodiment of this application;
[0023] Figure 3 is an exemplary flowchart of the cooperative transmission method in an embodiment of this application;
[0024] Figure 4 is another exemplary flowchart of the cooperative transmission method in the embodiments of this application;
[0025] Figure 5 is a schematic diagram of a first example scenario according to an embodiment of this application;
[0026] Figure 6 is a schematic diagram of a second example scenario according to an embodiment of this application;
[0027] Figure 7 is a schematic diagram of a third example scenario according to an embodiment of this application;
[0028] Figure 8 is a schematic diagram of a fourth example scenario according to an embodiment of this application;
[0029] Figure 9 is a schematic diagram of a fifth example scenario according to an embodiment of this application;
[0030] Figure 10 is a schematic diagram of the structure of the collaborative transmission device provided in an embodiment of this application;
[0031] Figure 11 is a schematic diagram of the structure of the collaborative transmission device provided in the embodiment of this application.
[0032] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0033] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.
[0034] Technical terms used in the embodiments of this application:
[0035] R-TWT: Requested Target Wake Time, limits the target's wake-up time;
[0036] Coordinated R-TWT: Coordinated target wake-up time;
[0037] BSS: Basic Service Set;
[0038] OBSS: Overlapping Basic Service Set;
[0039] ESS: Extended Service Set;
[0040] P2P: Peer-to-Peer;
[0041] IEEE 802.11be: A wireless communication standard;
[0042] AP: Access Point;
[0043] sharing AP: Initiating an access point;
[0044] shared AP: Response access point;
[0045] STA: Station, community station;
[0046] WLAN: Wireless Local Area Network;
[0047] MAC: Medium Access Control;
[0048] PHY: Physical Layer;
[0049] VR: Virtual Reality;
[0050] PLR: Packet Loss Rate;
[0051] LL: low latency;
[0052] SP: Service Period;
[0053] EDCA: Enhanced Distributed Channel Access;
[0054] CW: Contention Window;
[0055] AIFSN: Arbitration Interframe Space Number;
[0056] AC: Access Category;
[0057] DS: Distribution System;
[0058] TXOP: Transmission opportunity;
[0059] CCA: Clear Channel Assessment;
[0060] ICF: Initial Control Frame;
[0061] ICR: Initial Control Response;
[0062] HT: High Throughput;
[0063] VHT: Very High Throughput;
[0064] EHT: Extremely High Throughput;
[0065] LAN: Local Area Network;
[0066] LTE: Long-Term Evolution.
[0067] Currently, cooperative R-TWT allows the BSS and OBSS to negotiate a protected R-TWT service period. During the OBSS R-TWT service period (SP), the BSS AP / non-AP STA protects ongoing OBSS transmissions to reduce uncertainty. Specifically, the BSS AP / non-AP STA can terminate an ongoing transmission before the start of the R-TWT SP advertised by the OBSS AP. Furthermore, the BSS AP / non-AP STA can also block access to the channel during the SP to protect the ongoing OBSS SP. However, non-periodic real-time traffic may arrive at the BSS AP / non-AP STA during the SP. This cooperative R-TWT protection leads to increased data transmission latency because the AP / non-AP STA needs to exchange data only after the OBSS SP expires. For services requiring high real-time performance, the SP interval may be long, resulting in longer response times for real-time services.
[0068] Referring to Figure 1, which is a schematic diagram of a wireless communication network in an embodiment of this application, as shown in Figure 1, the implementation scheme discussed in this application can be applied to various wireless devices. The wireless implementation schemes described in detail below are only illustrative examples.
[0069] Figure 1 illustrates a network consisting of one or more wireless communication devices, including an access point (AP) 102 and a station (STA) 104. In some examples, these devices are capable of exchanging data according to the Institute of Electrical and Electronics Engineers (IEEE) 802 series standards. The IEEE 802 standards cover communication specifications for a wide range of network devices, from Local Area Networks (LANs) to Metropolitan Area Networks (MANs). In particular, the IEEE 802.11 standard sets clear guidelines for communication in Wireless Local Area Networks (WLANs). In these networks, communication must adhere to at least one communication protocol to ensure communication between different devices. These communication protocols are dynamically evolving and are continuously updated with technological advancements to enhance communication stability and improve data transmission efficiency.
[0070] IEEE 802.11 wireless communication technology can also be referred to as WiFi technology. In this example, AP102 and STA104 transmit data via one or more protocols from the IEEE 802.11 protocol family. These protocols cover a wide range, from early standards such as 802.11b, 802.11g, and 802.11a, to 802.11n's High Throughput (HT), 802.11ac's Very High Throughput (VHT), 802.11ax's High Efficiency (HE), and 802.11be's Extremely High Throughput (EHT). Furthermore, it includes next-generation IEEE 802.11 technologies such as the Ultra High Reliability (UHR) standard, as well as other developing IEEE 802.11 wireless communication specifications.
[0071] In other examples, AP102 and STA104 may communicate according to other standards, such as the Long-Term Evolution (LTE) standard developed by the Third Generation Partnership Project (3GPP). Furthermore, wireless communication standards may include LTE-A (an enhanced version of LTE), next-generation 5G NR technology, Bluetooth, global navigation satellite systems (such as GPS or GLONASS), and mobile television broadcasting standards (such as ATSC-M / H). These technologies can be used individually or in combination. In some embodiments, STA104 may be designed to support only a single wireless communication technology. The names of AP102 and STA104 may also differ depending on the technological context. For example, in an LTE network, AP102 may be referred to as an Evolved NodeB (eNB), while STA104 may be referred to as User Equipment (UE).
[0072] In some embodiments, the wireless terminal device, also known as a station (STA), may be more specifically defined as a non-access point STA (non-AP STA). These STAs 104 are capable of wirelessly connecting to nearby network devices, such as access points (APs 102). The wireless terminal device can be a mobile phone, handheld device, wearable device, computer or tablet, unmanned aerial vehicle (UAV), unmanned flight controller (UAC), vehicle, or virtually any type of wireless device. The STA may include a processor configured to execute program instructions stored in memory. The STA 104 can perform any of the methods described in this application by executing such stored instructions. Alternatively, the STA 104 may also include programmable hardware elements, such as field-programmable gate arrays (FPGAs), integrated circuits, or other hardware components configured to perform any part or all of the methods described in this application.
[0073] In some implementations, AP102 can be defined as a station (STA), and more specifically, as an access point STA (AP STA). AP102 can be, but is not limited to, a router, a mobile terminal that has enabled a hotspot, a base station, etc., all of which have hardware facilities for wireless communication with STA104. Furthermore, AP102 can also be configured to communicate with network 106, which can be a telecommunications network, such as the Public Switched Telephone Network (PSTN), the Internet, or other possible networks. Therefore, AP102 can not only enable communication between STA104, but also communication between STA104 and network 106. As will be further described later in this application, AP102 includes the hardware required to achieve wireless communication with STA104, and may also include hardware and software components for implementing or supporting the implementation of the features described in this application.
[0074] The communication range of AP102 is typically referred to as the Basic Service Set (BSS). AP102 and STA104 can communicate via various radio access technologies or wireless communication technologies, including but not limited to LTE, LTE Advanced (LTE A), 5G NR, WiFi, and Ultra Wideband (UWB). AP102 can also be configured to provide STA104 with communication connectivity to network 106.
[0075] The STA104 can also be configured to communicate with other STA104 devices. For example, the STA104 can be configured to support direct device-to-device communication, commonly referred to as peer-to-peer (P2P) communication. This communication method allows two devices to communicate directly without the AP102.
[0076] Multiple BSSs can be combined to form an Extended Service Set (ESS). In this example, AP102 may not be a single access point, but rather one of multiple access points. A controller, not shown in the diagram, can be responsible for storing and managing shared information among the multiple AP102s and for controlling the BSSs, such as allocating parameters like the primary channel and BSS color.
[0077] The traditional STA108 can operate according to one or more standards in the IEEE 802.11 standard family, which may include 802.11a / b / g / n / ac / ad / ah / ay / ax, etc. The AP102 can communicate with the traditional STA108 using traditional IEEE 802.11 communication technology.
[0078] The MAC and PHY layers in AP102 and STA104 exchange PDUs (Protocol Data Units) and SDUs (Service Data Units) during the management of wireless communication traffic. The PHY layer is configured to receive SDUs from the MAC layer, encapsulating the MAC SDUs into PPDUs (Physical Layer Protocol Data Units) by adding a preamble. In some embodiments, different types of PPDUs may exist, such as single-user (SU) PPDUs, downlink (DL) PPDUs, multi-user (MU) PPDUs, extended range (ER) SUPPDUs, and / or trigger-based (TB) PPDUs. The PPDU preamble may include various training fields that the receiving AP102 or STA104 uses to perform synchronization, gain control, channel characteristic estimation, and signal equalization. AP102 and STA104 then exchange wireless communication signals in PPDU format.
[0079] Wireless communication channel bandwidths offer a variety of options, including but not limited to 20MHz, 40MHz, 80MHz, 160MHz, and combinations such as 80+80MHz. Furthermore, in some embodiments, the channel bandwidth may reach 320MHz, or appear in a combination of 160+160MHz. For narrower channels, bandwidth options may include subdivisions from 1MHz to 10MHz, or combinations thereof, or other bandwidths less than or equal to the available bandwidth may also be used. In some embodiments, the channel bandwidth may also be determined based on the number of subcarriers carrying data, which may be 26, 52, 106, 242, 484, 996, and 2x996. In some embodiments, the allocation of bandwidth, tone, or number of subcarriers may be referred to as resource unit (RU) allocation.
[0080] In some embodiments of IEEE 802.11, such as the ax / be embodiment, AP102 gains control of the wireless channel through a contention mechanism to acquire a transmission window (TXOP). During the TXOP, AP102 can transmit frames containing EHT / HE trigger information, which may be related to the synchronous uplink and downlink data transmission of STA104. AP102 can provide the duration of the TXOP and RU allocation information. STA104 communicates with AP102 using multiple access technologies such as OFDMA or MUMIMO. During the TXOP, AP102 can send one or more PPDUs to exchange data with STA104.
[0081] In some implementations, STA104 and / or AP102 are configured to perform the methods and functions described in conjunction with Figure 1. The term "WiFi" may refer to one or more versions of the IEEE 802.11 communication standard. APs and STAs may include access points and terminal devices based on EHT / HE technology standards, as well as conventional wireless communication devices.
[0082] Referring to Figure 2, which is a schematic diagram of the structure of a wireless communication device in an embodiment of this application, Figure 2 serves as a block diagram of the wireless communication device 200. This structure is suitable for implementing various technologies or methods discussed in this application. In some embodiments, the device 200 can operate independently or establish connections with other devices to form a network system. When the device 200 is deployed in a network, it can operate as a server or client in a server-client mode, or as a node in a P2P network mode. The device 200 may represent AP102, STA104, STA108, or any other device capable of executing relevant instructions, including methods for implementing or supporting the features described in this application.
[0083] Device 200 may include processor 204 (e.g., central processing unit (CPU), graphics processing unit (GPU) or any combination thereof), memory 202, display device 212, input device 214, sensor device 216 and antenna 218.
[0084] Memory 202 stores the control program and various data used. AP102 and STA104, STA108 can be configured to implement or support the implementation of part or all of the methods described in this application, for example, by executing program instructions stored in the memory. The memory can be implemented as RAM, flash memory, ROM, EPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this respect, the memory can be coupled to the processor, allowing the processor to read information from and write information to the memory. In some embodiments, the memory may each include a cache for storing temporary variables or other intermediate information during the execution of instructions executed by the processor. The memory may also include non-volatile memory for storing instructions to be executed by the processor. After the device is powered on, one or more programs stored on a hard disk or read-only memory are transferred to random access memory and registers for storing variables and parameters required by this application.
[0085] Device 200 may also include display device 212 and input device 214 (e.g., keyboard and mouse). In some embodiments, display device 212 and input device 214 may be touch screen displays. Sensor 216 may be, for example, a Global Positioning System (GPS) sensor or other sensors.
[0086] Processor 204 is responsible for executing various instruction sets or software programs and managing data transmission and reception tasks. Processor 204 may include a Media Access Control Unit 206 (MAC unit), a Physical Layer Unit 208 (PHY unit), and a storage unit 210. These units, including PHY unit 208, MAC unit 206, and storage unit 210, can be interconnected and may be partially or entirely integrated onto a single chip. Processor 204 can implement or assist in implementing one or more functions, operations, or methods described in this application by running program code stored in storage units 202 or 210. Furthermore, processor 204 can be configured to use one or more antennas to transmit and receive signals with other wireless devices (e.g., AP 102, STA 104, or legacy device 108). In a particular embodiment, PHY unit 208 is responsible for performing functions such as signal encoding and decoding, power amplification, and filtering, including generating baseband signals for transmission and decoding received signals. PHY unit 208 can also transmit signals according to one of the 802.11 standards discussed herein, such as 802.11ax / 802.11be. MAC unit 206 is responsible for managing access rights to the wireless communication medium. In some embodiments, MAC unit 206 can compete for access to the wireless medium based on Network Allocation Vector (NAV) and Channel Clearance Assessment (CCA). Certain functions of signal transmission and reception may be performed collaboratively by PHY unit 208, MAC unit 206, and other components. In some embodiments, processor 204 may integrate one or more general-purpose or purpose-specific processors. Processor 204 may also be configured as a Field Programmable Gate Array (FPGA) or implemented using dedicated hardware components such as Application-Specific Integrated Circuits (ASICs) to implement the required hardware and logic circuitry. In some cases, the implementation of processor 204 may rely on the combination of software-configured elements with other hardware elements.
[0087] Antenna 218 may include one or more directional or omnidirectional antennas, including, for example, linearly polarized antennas, circularly polarized antennas, narrowband antennas, wideband antennas, ultra-wideband antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, antenna 218 may be configured to perform wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some embodiments, multi-user MIMO technology may be used for wireless communication.
[0088] In several embodiments, the methods described in this application may be implemented entirely in software, or partially through a combination of software and firmware. These software components and / or firmware may be encoded on a persistent computer-readable storage medium for the processor to read. The processor parses and executes these encoded instructions to complete the series of operations described in this application. These instructions may exist in various forms, including but not limited to raw source code, compiled code, scripts requiring interpretation, directly executable programs, statically compiled programs, or dynamically generated programs.
[0089] R-TWT technology, introduced in Wi-Fi 7 (802.11be), aims to provide more predictable latency, lower worst-case latency, and / or lower jitter for latency-sensitive applications, while offering greater reliability for these traffic flows. R-TWT allows for complete isolation of data flows by allocating dedicated time periods (SPs) to them, preventing data transmission from being interfered with by other traffic and thus providing strong QoS guarantees for real-time applications. R-TWT addresses an inherent problem in the default Wi-Fi 6 TWT specification: the possibility of encountering ongoing transmissions at the start of a TWT service period, which increases the uncertainty of when a scheduled transmission will begin. To avoid this, R-TWT forces non-AP STAs to end ongoing transmissions before the start of the R-TWT SP advertised by the AP. Furthermore, overlapping quiet intervals are arranged for each R-TWT SP to ensure that legacy non-AP STAs also remain silent.
[0090] Because of the lack of R-TWT operation coordination among APs in OBSS scenarios, the advantages of R-TWT are affected by OBSS interference. Coordinated R-TWT is not only a mechanism for transmitting delay-sensitive traffic, but it can also be used to coordinate the operation of multiple APs to avoid or reduce OBSS interference and improve communication efficiency in OBSS scenarios.
[0091] In the embodiments of this application, a complete Coordinated R-TWT includes at least one of the following steps:
[0092] 1. Coordinated R-TWT Discovery: At this stage, the Coordinated R-TWT initiating AP announces / declare its intention to coordinate operations with other APs based on R-TWT. The announcement may include basic functionalities and other coordination information related to Coordinated R-TWT. APs willing to participate in Coordinated R-TWT coordination should respond to the announcement. Responding APs should include their Coordinated R-TWT functional information in their response. Functional information may include support for different Coordinated R-TWT modes;
[0093] 2. Coordinated R-TWT Negotiation: In this phase, the Coordinated R-TWT initiating AP and the responding AP negotiate explicit parameters. The responding AP can also be called a shared AP. Negotiated parameters may include scheduling time information, such as wake-up duration and interval.
[0094] 3. BSS-based Coordinated R-TWT Advertisement: In this stage, the AP that initiated the Coordinated R-TWT advertises the Coordinated R-TWT as a regular R-TWT in its BSS. Shared APs need to enhance the R-TWT originating from the AP that initiated the Coordinated R-TWT; for example, a shared AP can specify QoS-aware Coordinated R-TWT rules for its own BSS.
[0095] 4. Coordinated R-TWT Negotiation within BSS: In this stage, the AP initiating the Coordinated R-TWT negotiates the Coordinated R-TWT as a regular R-TWT within its BSS. The shared AP can negotiate the protection rules for the Coordinated R-TWT with its STAs within the BSS.
[0096] 5. Once the initiating AP successfully negotiates the Coordinated R-TWT with the shared AP, the initiating AP can make any changes to the plan parameters. However, the initiating AP needs to notify the shared AP of the corresponding changes. The shared AP can renegotiate with the initiating AP.
[0097] 6. Coordinated R-TWT Termination: Either the initiating AP or the shared AP can terminate the Coordinated R-TWT protocol.
[0098] Referring to Figure 3, which is an exemplary flowchart of a cooperative transmission method in an embodiment of this application, the cooperative transmission method is applied to an initiating access point, and the method includes:
[0099] Step S10: If at least one response access point supports channel access with limited target wake-up time based on cooperation, negotiate the parameters of the channel access capability with the at least one response access point so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the negotiated parameters of the channel access capability.
[0100] For example, in the case where at least one responding access point supports channel access with a cooperatively limited target wake-up time, the step of negotiating the parameters of the channel access capability with the at least one responding access point further includes:
[0101] Send a coordinated operation intent based on cooperation to the at least one responding access point to limit the target wake-up time, so that the at least one responding access point sends response information to the initiating access point according to the coordinated operation intent;
[0102] Receive response information sent by the at least one response access point;
[0103] Based on the cooperative function information in the response information, determine whether the at least one response access point supports channel access with limited target wake-up time based on cooperation.
[0104] For example, during the Coordinated R-TWT discovery phase, the AP announces in its transmitted management frames whether it supports channel access capabilities based on Coordinated R-TWT. The AP and non-AP STA can obtain information about each other's support for channel access capabilities based on Coordinated R-TWT by listening to and interacting with beacon frames, probe frames, and association frames (such as UHR Capabilities elements).
[0105] For example, the parameters of channel access capability include at least one of the following: low latency service, channel access parameter information of low latency service, access type, channel access parameter information of access type, transmission bandwidth size within the service period, transmission puncturing bitmap within the service period, target wake-up time, and wake-up interval of target wake-up time.
[0106] For example, the channel access parameter information includes at least one of the following: minimum contention window, maximum contention window, number of arbitration inter-frame intervals, and transmission opportunity limit.
[0107] For example, during the service period of the channel access based on the cooperative limitation of the target wake-up time at the initiating access point, the method further includes:
[0108] The at least one response access point and the terminal corresponding to the at least one response access point send the low-latency service and / or the service corresponding to the access type, and the at least one response access point and the terminal corresponding to the at least one response access point use the channel access parameter information of the low-latency service and / or the channel access parameter information of the access type, and send data using the transmission bandwidth size within the service period; and / or,
[0109] The initiating access point competes for the channel using non-negotiated enhanced distributed channel access parameters, and sends data using the puncturing bandwidth according to the transmission puncturing bitmap and the transmission bandwidth size within the service period.
[0110] For example, during the service period of channel access based on cooperative limited target wake-up time, which is not the initiating access point, the at least one responding access point and the terminal corresponding to the at least one responding access point compete for the channel using non-negotiated enhanced distributed channel access parameters and send data using non-negotiated working bandwidth.
[0111] For example, when the service period of the channel access based on the cooperative target wake-up time of the initiating access point overlaps with the service period of the channel access based on the cooperative target wake-up time of the responding access point, the at least one responding access point and the terminal corresponding to the at least one responding access point compete for the channel using non-negotiated enhanced distributed channel access parameters and send data using non-negotiated working bandwidth.
[0112] For example, during the Coordinated R-TWT negotiation phase, the Coordinated R-TWT initiating AP negotiates the parameters of the channel access capability based on the Coordinated R-TWT with at least one responding AP.
[0113] For example, the parameters of the negotiated channel access capability include low-latency services, i.e., whether the responding AP is allowed to transmit low-latency services through channel access during the SP service period initiated by the AP in Coordinated R-TWT. The low-latency service can be a service type negotiated through SCS.
[0114] For example, if low-latency services are permitted, the EDCA channel access parameter information for low-latency services is included within the SP. EDCA access parameters may include CW min, CW max, AIFSN, TXOP limits, etc.
[0115] For example, the parameters of the negotiated channel access capability may also include the access type, i.e., whether the AC type information is allowed for the response AP (shared AP) to perform channel access transmission within the SP of the AP initiated by the Coordinated R-TWT.
[0116] For example, if an AC type that allows channel access exists, then information on the corresponding AC's EDCA channel access parameters is included. EDCA access parameters may include CWmin, CWmax, AIFSN, TXOP limit, etc.
[0117] For example, at least one response AP uses the bandwidth size and the punch bitmap of the transmission within the SP of the Coordinated R-TWT initiating AP.
[0118] For example, the parameters of the negotiated channel access capability may also include other information about the coordinated R-TWT, such as the Coordinated R-TWT SP Target Wake Time and TWT Wake Interval.
[0119] For example, within a Coordinated R-TWT SP, shared APs and non-AP STAs can transmit negotiated low-latency services and AC-type services, competing for the channel using negotiated EDCA channel access parameters and transmitting data using negotiated bandwidth. The Coordinated R-TWT initiating AP competes for the channel using its original EDCA parameters and transmits data using punctured bandwidth. Within a non-Coordinated R-TWT SP, shared APs and non-AP STAs compete for the channel using their original EDCA channel access parameters and transmit data using their original operating bandwidth. If a Coordinated R-TWT SP overlaps with this SP, then shared APs and non-AP STAs compete for the channel using their original EDCA channel access parameters and transmit data using their original operating bandwidth.
[0120] In this embodiment, the above-described scheme specifically involves the initiating access point negotiating the channel access capability parameters with at least one responding access point, provided that at least one responding access point supports channel access with limited target wake-up time based on cooperation. This allows the at least one responding access point to interact with the terminal corresponding to it based on the negotiated channel access capability parameters. By negotiating with at least one responding access point that supports channel access with limited target wake-up time based on cooperation, the operation of multiple access points can be coordinated, thereby improving communication efficiency.
[0121] Referring to Figure 4, which is another exemplary flowchart of the cooperative transmission method in an embodiment of this application, the cooperative transmission method is applied to at least one response access point, and the method includes:
[0122] Step S20: In the case of supporting channel access based on cooperation with limited target wake-up time initiated by the initiating access point, negotiate the parameters of the channel access capability with the initiating access point;
[0123] For example, in the case of supporting channel access based on cooperation with a limited target wake-up time initiated by the initiating access point, the step of negotiating the parameters of the channel access capability with the initiating access point further includes:
[0124] Receive the coordinated operation intent based on cooperation to limit the target wake-up time sent by the initiating access point;
[0125] According to the coordination operation intent, a response message is sent to the initiating access point, so that the initiating access point can determine whether the at least one responding access point supports channel access with a limited target wake-up time based on the cooperative function information in the response message.
[0126] For example, the parameters of channel access capability include at least one of the following: low latency service, channel access parameter information of low latency service, access type, channel access parameter information of access type, transmission bandwidth size within the service period, transmission puncturing bitmap within the service period, target wake-up time, and wake-up interval of target wake-up time.
[0127] For example, the channel access parameter information includes at least one of the following: minimum contention window, maximum contention window, number of arbitration inter-frame intervals, and transmission opportunity limit.
[0128] Step S30: Based on the parameters of the channel access capability determined through negotiation, perform data interaction with the terminal corresponding to the at least one response access point.
[0129] For example, before the step of interacting with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability, the method further includes:
[0130] The terminal corresponding to the at least one response access point sends the parameters of the channel access capability to the terminal, so that the terminal corresponding to the at least one response access point sends data to the at least one response access point according to the parameters of the channel access capability.
[0131] For example, during the service period of the channel access based on the cooperative limitation of the target wake-up time at the initiating access point, the method further includes:
[0132] The terminal corresponding to the at least one response access point sends the low-latency service and / or the service corresponding to the access type, and the terminal corresponding to the at least one response access point uses the channel access parameter information of the low-latency service and / or the channel access parameter information of the access type, and sends data using the transmission bandwidth size within the service period; and / or,
[0133] The initiating access point competes for the channel using non-negotiated enhanced distributed channel access parameters, and sends data using the puncturing bandwidth according to the transmission puncturing bitmap and the transmission bandwidth size within the service period.
[0134] For example, during the service period of channel access based on cooperative limited target wake-up time, which is not the initiating access point, the terminal corresponding to the at least one responding access point competes for the channel using non-negotiated enhanced distributed channel access parameters and sends data using non-negotiated working bandwidth.
[0135] For example, when the service period of the channel access based on the cooperative-limited target wake-up time of the initiating access point overlaps with the service period of the channel access based on the cooperative-limited target wake-up time of the responding access point, the terminal corresponding to the at least one responding access point competes for the channel using non-negotiated enhanced distributed channel access parameters and sends data using non-negotiated working bandwidth.
[0136] For example, during the Coordinated R-TWT announcement phase within the BSS, the AP announces channel access information based on the Coordinated R-TWT to non-AP STAs within the BSS, including but not limited to at least one of the following:
[0137] Low-latency service types that are allowed to be transmitted within the Coordinated R-TWT SP. SCS service types can be indicated by QoS Characteristics elements;
[0138] EDCA channel access parameters for low-latency service types. EDCA access parameters may include CWmin, CWmax, AIFSN, TXOP limit, etc.
[0139] The AC type allowed for channel access within the Coordinated R-TWT SP (the AC type mapped to the low-latency service type should be avoided to be the same as this AC type);
[0140] Information on the corresponding AC's EDCA channel access parameters, which may include CWmin, CWmax, AIFSN, TXOP limit, etc.
[0141] The bandwidth allowed for shared APs to transmit within a Coordinated R-TWT SP and the punch bitmap for Coordinated R-TWT-initiated APs to transmit within a Coordinated R-TWT SP.
[0142] Other information about the Coordinated R-TWT SP, such as the Coordinated R-TWT SP Target Wake Time and TWT Wake Interval, etc.
[0143] For example, when the Coordinated R-TWT initiating AP successfully negotiates a channel access protocol based on the Coordinated R-TWT with the shared AP, if either the Coordinated R-TWT initiating AP or the shared AP needs to modify relevant parameters, the aforementioned negotiation and announcement process needs to be repeated.
[0144] For example, within a Coordinated R-TWT SP, shared APs and non-AP STAs can transmit negotiated low-latency services and AC-type services, competing for the channel using negotiated EDCA channel access parameters and transmitting data using negotiated bandwidth. The Coordinated R-TWT initiating AP competes for the channel using its original EDCA parameters and transmits data using punctured bandwidth. Within a non-Coordinated R-TWT SP, shared APs and non-AP STAs compete for the channel using non-negotiated EDCA channel access parameters and transmit data using their original operating bandwidth. If a Coordinated R-TWT SP overlaps with this SP, then shared APs and non-AP STAs compete for the channel using non-negotiated EDCA channel access parameters and transmit data using non-negotiated operating bandwidth.
[0145] For example, a shared AP should ensure that its TXOP ends before the start time of the corresponding Coordinated R-TWT SP. Non-AP STAs associated with a shared AP that support Coordinated R-TWT negotiation should treat Coordinated R-TWT SPs according to the R-TWT baseline rules.
[0146] In this embodiment, the above-described scheme specifically involves at least one responding access point negotiating channel access capability parameters with the initiating access point when supporting channel access based on cooperative target wake-up time limitation initiated by the initiating access point. Based on the negotiated channel access capability parameters, data interaction is performed with the terminal corresponding to the at least one responding access point. By negotiating with the initiating access point, the operation of multiple access points can be coordinated, thereby improving communication efficiency.
[0147] Referring to Figure 5, which is a schematic diagram of a first example scenario according to an embodiment of this application, as shown in Figure 5, firstly, in the Coordinated R-TWT discovery phase, the Coordinated R-TWT initiating AP1 and the shared AP2 discover each other's Coordinated R-TWT function information through beacon frames, including information on whether channel access capability based on Coordinated R-TWT is supported. Subsequently, in the Coordinated R-TWT negotiation phase, the Coordinated R-TWT initiating AP1 sends a MAP request frame to the shared AP2 to initiate negotiation, and the shared AP2 sends a MAP response frame to respond to the negotiation. The MAP request frame and the MAP response frame may contain SP scheduling time information, such as wake-up duration and interval. Furthermore, if both the Coordinated R-TWT initiating AP1 and the shared AP2 support channel access capabilities based on Coordinated R-TWT, the negotiation information may also include the types of low-latency services allowed to access during the Coordinated R-TWT SP, the EDCA parameters of the low-latency service (or mapped AC), the AC type for channel access transmission (e.g., AC_VO) and the corresponding EDCA parameters, the bandwidth available to the shared AP2, and the punched bitmap of the data transmitted by AP1. This is followed by the Coordinated R-TWT announcement phase within the BSS. During this phase, the Coordinated R-TWT initiating AP1 announces the Coordinated R-TWT as a regular R-TWT in its BSS. The shared AP2 needs to apply the Coordinated R-TWT-based channel access method to the R-TWT originating from the Coordinated R-TWT initiating AP, and the shared AP2 carries the aforementioned negotiated parameter information in its beacon frame. Finally, during the Coordinated R-TWT negotiation phase within the BSS, non-AP STA1 and non-AP STA2 initiate R-TWT negotiations with AP1 and AP2, respectively.
[0148] Referring to Figure 6, which is a schematic diagram of a second example scenario according to an embodiment of this application, as shown in Figure 6, AP1 and AP2 have completed the negotiation process shown in Figure 5. AP1's SP is a Coordinated R-TWT SP. AP1 and AP2 negotiated that only AP2 and its subordinate non-AP STAs are allowed to access the channel for low-latency services within the Coordinated R-TWT SP, using the negotiated EDCA parameters. Therefore, during AP1's SP period, in addition to AP1 being able to send data addressed to non-AP STA1, non-AP STA2 can also send low-latency data addressed to AP2. The EDCA parameters used for sending low-latency data can be more aggressive than AP1's EDCA parameters, for example, smaller CWmin, CWmax, AIFSN, or a larger TXOP Limit compared to AP1's EDCA parameters. By setting more aggressive EDCA parameter values, the effect of channel preemption within the OBSS SP can be achieved. In other embodiments, the EDCA parameter can be set to the same or a more conservative EDCA parameter as AP1, thereby ensuring fairness while guaranteeing the opportunity for low-latency service transmission.
[0149] Referring to Figure 7, which is a schematic diagram of a third example scenario according to an embodiment of this application, as shown in Figure 7, AP1 and AP2 have completed the negotiation process shown in Figure 5. AP1's SP is a Coordinated R-TWT SP. AP1 and AP2 negotiated that only AP2's AC_VO type access channel is allowed during the Coordinated R-TWT SP, and used the negotiated EDCA parameters. Therefore, during AP1's SP, in addition to AP1 being able to send data addressed to non-AP STA1, AP2 can also send AC_VO type data addressed to non-AP STA2.
[0150] Referring to Figure 8, which is a schematic diagram of a fourth example scenario according to an embodiment of this application, as shown in Figure 8, AP1 and AP2 have completed the negotiation process shown in Figure 5. Since AP1 and AP2 have negotiated that there are no low-latency services and no AC type available for accessing the channel in the Coordinated R-TWT SP, AP2 and non-AP STA2 are prohibited from accessing the channel during AP1's SP period until AP1's SP expires. This achieves the effect of completely protecting AP1's SP transmission.
[0151] Referring to Figure 9, which is a schematic diagram of a fifth example scenario according to an embodiment of this application, as shown in Figure 9, AP1 and AP2 have completed the negotiation process shown in Figure 5. Both AP1 and AP2 have an operating bandwidth of 80MHz, but their primary 20MHz channel positions are different. AP2, as a shared AP, negotiates with AP1 that it can only use a 20MHz bandwidth to transmit data during AP1's SP (Service Pack). AP1 can puncture the channel where AP2's primary 20MHz channel is located (channel S20-2 for AP1) within the SP to avoid interference with the data transmitted by AP2. In some embodiments, if AP1 and AP2 have negotiated bandwidth parameters, AP2 can transmit any type of data within AP1's SP.
[0152] Furthermore, this application embodiment also provides a cooperative transmission device. Referring to Figure 10, Figure 10 is a schematic diagram of the cooperative transmission device structure provided in this application embodiment. The cooperative transmission device is applied to an initiating access point, and the device includes:
[0153] The first negotiation module is used to negotiate with the at least one response access point to determine the parameters of the channel access capability when the at least one response access point supports channel access based on cooperative limitation of target wake-up time, so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability.
[0154] Furthermore, this application embodiment also provides a cooperative transmission device. Referring to Figure 11, Figure 11 is a second schematic diagram of the cooperative transmission device structure provided in this application embodiment. The cooperative transmission device is applied to at least one response access point, and the device includes:
[0155] The second negotiation module is used to negotiate with the initiating access point to determine the parameters of the channel access capability when supporting channel access based on cooperation and limited target wake-up time initiated by the initiating access point.
[0156] An interaction module is used to perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability.
[0157] This application also provides a network device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the cooperative transmission method described above.
[0158] This application embodiment also provides a storage medium, which is a computer-readable storage medium, and stores a computer program thereon. When the computer program is executed by a processor, it implements the steps of the cooperative transmission method described above.
[0159] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the cooperative transmission method described above.
[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or computing device, etc.) to execute the methods described in the various embodiments of this application.
[0162] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
A cooperative transmission method, applied to an initiating access point, the method comprising: When at least one response access point supports channel access with a limited target wake-up time based on cooperation, the parameters of the channel access capability are negotiated with the at least one response access point so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the negotiated parameters of the channel access capability. The cooperative transmission method as described in claim 1, wherein, The step of negotiating the parameters of the channel access capability with the at least one responding access point, when at least one responding access point supports channel access based on cooperative limitation of target wake-up time, further includes the following before the step of negotiating the parameters of the channel access capability with the at least one responding access point: Send a coordinated operation intent based on cooperation to the at least one responding access point to limit the target wake-up time, so that the at least one responding access point sends response information to the initiating access point according to the coordinated operation intent; Receive response information sent by the at least one response access point; Based on the cooperative function information in the response information, determine whether the at least one response access point supports channel access with limited target wake-up time based on cooperation. The cooperative transmission method as described in claim 1, wherein, The parameters of the channel access capability include at least one of the following: Low-latency services; Channel access parameter information for low-latency services; Access type; Access type channel access parameter information; The amount of transmission bandwidth during the service period; Transmitted punch bitmap during the service period; Target wake-up time; The wake-up interval of the target wake-up time. The cooperative transmission method as described in claim 3, wherein, The channel access parameter information includes at least one of the following: minimum contention window value, maximum contention window value, number of arbitration inter-frame intervals, and transmission opportunity limit. The cooperative transmission method as described in claim 3, wherein, During the service period of the channel access based on the cooperatively limited target wake-up time of the initiating access point, the method further includes: The at least one response access point and the terminal corresponding to the at least one response access point send the low-latency service and / or the service corresponding to the access type, and the at least one response access point and the terminal corresponding to the at least one response access point use the channel access parameter information of the low-latency service and / or the channel access parameter information of the access type, and send data using the transmission bandwidth size within the service period; and / or, The initiating access point competes for the channel using non-negotiated enhanced distributed channel access parameters, and sends data using the puncturing bandwidth according to the transmission puncturing bitmap and the transmission bandwidth size within the service period. The cooperative transmission method as described in claim 3 further includes: During the service period of channel access based on cooperative limited target wake-up time, which is not the initiating access point, the at least one responding access point and the terminal corresponding to the at least one responding access point compete for the channel using non-negotiated enhanced distributed channel access parameters and transmit data using non-negotiated operating bandwidth; and / or, When the service period of the channel access based on the cooperative target wake-up time of the initiating access point overlaps with the service period of the channel access based on the cooperative target wake-up time of the responding access point, the at least one responding access point and the terminal corresponding to the at least one responding access point compete for the channel using non-negotiated enhanced distributed channel access parameters and send data using non-negotiated working bandwidth. A cooperative transmission method, applied to at least one response access point, the method comprising: In the case of supporting channel access based on cooperation with limited target wake-up time initiated by the initiating access point, the parameters of the channel access capability are negotiated with the initiating access point; Based on the negotiated parameters of the channel access capability, data is exchanged with the terminal corresponding to the at least one response access point. The cooperative transmission method as described in claim 7, wherein, In the case of supporting cooperative, target wake-up time-limited channel access initiated by the initiating access point, the step of negotiating the parameters of the channel access capability with the initiating access point further includes: Receive the coordinated operation intent based on cooperation to limit the target wake-up time sent by the initiating access point; According to the coordination operation intent, a response message is sent to the initiating access point, so that the initiating access point can determine whether the at least one responding access point supports channel access with a limited target wake-up time based on the cooperative function information in the response message. The cooperative transmission method as described in claim 7, wherein, The parameters of the channel access capability include at least one of the following: Low-latency services; Channel access parameter information for low-latency services; Access type; Access type channel access parameter information; The amount of transmission bandwidth during the service period; Transmitted punch bitmap during the service period; Target wake-up time; The wake-up interval of the target wake-up time. The cooperative transmission method as described in claim 9, wherein, The channel access parameter information includes at least one of the following: minimum contention window value, maximum contention window value, number of arbitration inter-frame intervals, and transmission opportunity limit. The cooperative transmission method as described in claim 7, wherein, Before the step of interacting with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability, the method further includes: The terminal corresponding to the at least one response access point sends the parameters of the channel access capability to the terminal, so that the terminal corresponding to the at least one response access point sends data to the at least one response access point according to the parameters of the channel access capability. The cooperative transmission method as described in claim 9, wherein, During the service period of the channel access based on the cooperatively limited target wake-up time of the initiating access point, the method further includes: The terminal corresponding to the at least one response access point sends the low-latency service and / or the service corresponding to the access type, and the terminal corresponding to the at least one response access point uses the channel access parameter information of the low-latency service and / or the channel access parameter information of the access type, and sends data using the transmission bandwidth size within the service period; and / or, The initiating access point competes for the channel using non-negotiated enhanced distributed channel access parameters, and sends data using the puncturing bandwidth according to the transmission puncturing bitmap and the transmission bandwidth size within the service period. The cooperative transmission method as described in claim 9 further includes: During the service period of channel access based on cooperative limited target wake-up time, which is not the initiating access point, the terminal corresponding to the at least one responding access point competes for the channel using non-negotiated enhanced distributed channel access parameters and transmits data using non-negotiated operating bandwidth; and / or, When the service period of the channel access based on the cooperative target wake-up time of the initiating access point overlaps with the service period of the channel access based on the cooperative target wake-up time of the responding access point, the terminal corresponding to the at least one responding access point competes for the channel using non-negotiated enhanced distributed channel access parameters and transmits data using non-negotiated working bandwidth. A cooperative transmission device, applied to an initiating access point, the device comprising: The first negotiation module is used to negotiate with the at least one response access point to determine the parameters of the channel access capability when the at least one response access point supports channel access based on cooperative limitation of target wake-up time, so that the at least one response access point can perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability. A cooperative transmission device is applied to at least one response access point, the device comprising: The second negotiation module is used to negotiate with the initiating access point to determine the parameters of the channel access capability when supporting channel access based on cooperation and limited target wake-up time initiated by the initiating access point. An interaction module is used to perform data interaction with the terminal corresponding to the at least one response access point based on the parameters of the channel access capability. A network device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the cooperative transmission method as described in any one of claims 1 to 13. A storage medium, which is a computer-readable storage medium, stores a computer program thereon, which, when executed by a processor, implements the steps of the cooperative transmission method as described in any one of claims 1 to 13. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the cooperative transmission method as described in any one of claims 1 to 13.