CBF via Coordinated Beamforming (CBF) session using three-way handshake negotiation
By exchanging frames during a CBF session through a three-way handshake negotiation mechanism to determine parameters and execute data unit transmission, the problems of low efficiency and high overhead of CBF sessions are solved, and more efficient CBF sessions and data transmission are achieved.
Patent Information
- Application Number
- CN202610603882.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2026-02-20
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-10
AI Technical Summary
In the prior art, coordinated beamforming (CBF) sessions are inefficient and suffer from excessive protocol overhead when extending the session after the initial transmission.
By using a three-way handshake negotiation mechanism, frames are exchanged during a CBF session to determine parameters, and multiple CBF transmissions of data units are performed during the session, including the exchange of indication and trigger frames, to achieve synchronization and coordination of multiple CBF transmissions.
It improves the efficiency of CBF sessions, reduces the overhead of repeated setup and switching, and enables longer CBF transmission times and more efficient data transmission.
Smart Images

Figure CN123074541A_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims the benefit and priority of Indian Patent Application No. 202521044559, filed May 8, 2025, and U.S. Provisional Application No. 63 / 826,208, filed June 18, 2025, the entire contents of which are incorporated herein by reference for all purposes. Technical Field
[0003] This disclosure generally relates to systems and methods for improving the efficiency of a coordinated beamforming (CBF) session and / or for extending or continuing a CBF session after an initial (or first) CBF transmission using frame sequences. Background Technology
[0004] Coordinated beamforming (CBF) is a multi-AP (access point) transmission technique in which two or more access points use shared or pre-negotiated parameters (such as zeroing direction, spatial stream allocation, or preamble-related information) to align their downlink transmissions with their respective stations, allowing these transmissions to occur concurrently and with reduced interference. Summary of the Invention
[0005] In one aspect, this disclosure provides a first access point comprising: a network interface; and one or more processors configured to: exchange one or more frames with a second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions in a session; and perform CBF transmissions of multiple data units to one or more stations (STAs) via the network interface using the one or more parameters during the session, wherein during the session, in response to performing a CBF transmission of a first data unit, the one or more processors are configured to: transmit a first frame indicating that the first access point is capable of participating in a next CBF transmission during the session; and, in response to receiving a second frame indicating that the second access point is capable of participating in the next CBF transmission during the session, transmit a trigger frame and then perform a CBF transmission of a second data unit.
[0006] In another aspect, this disclosure provides a first access point comprising: a network interface; and one or more processors configured to: exchange one or more frames with a second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions in a session; and perform CBF transmissions of multiple data units to one or more stations (STAs) via the network interface using the one or more parameters during the session, wherein during the session, in response to performing a CBF transmission of a first data unit, the one or more processors are configured to: transmit a second frame indicating that the first access point is capable of participating in the next CBF transmission during the session in response to receiving a first frame indicating that the second access point is capable of participating in the next CBF transmission; and perform a CBF transmission of a second data unit during the session in response to receiving a trigger frame.
[0007] In another aspect, this disclosure provides a method for performing coordinated beamforming (CBF) transmissions during a session, comprising: exchanging one or more frames with a first access point and a second access point to determine one or more parameters for performing CBF transmissions during the session; simultaneously performing a pair of first data units to one or more stations (STAs) by the first access point and the second access point using the one or more parameters during the session; in response to performing the CBF transmission of the pair of first data units, transmitting a first frame indicating that the first access point is capable of participating in a next CBF transmission by the first access point; in response to receiving the first frame, transmitting a second frame indicating that the second access point is capable of participating in a next CBF transmission by the second access point; in response to receiving the second frame, transmitting a trigger frame by the first access point; and in response to the trigger frame, simultaneously performing a pair of second data units to the one or more STAs by the first access point and the second access point using the one or more parameters during the session. Attached Figure Description
[0008] The various objects, aspects, features, and advantages of this disclosure will become more apparent and better understood through a detailed description taken in conjunction with the accompanying drawings, in which like reference numerals identify corresponding elements throughout. In the drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements.
[0009] Figure 1A It is a block diagram depicting a network environment comprising one or more access points communicating with one or more devices or stations, according to some embodiments.
[0010] Figure 1B and 1C This is a block diagram depicting a computing device that can be used in conjunction with the methods and systems described herein, according to some embodiments.
[0011] Figure 2 The frame sequence is set according to an instance CBF of some embodiments.
[0012] Figure 3 This is another instance of CBF setting the frame sequence according to some embodiments.
[0013] Figure 4 It is an example CBF acknowledgment (ACK) frame sequence based on some embodiments.
[0014] Figure 5 This is another instance of a CBF ACK frame sequence according to some embodiments.
[0015] Figure 6 This is yet another instance of a CBF ACK frame sequence according to some embodiments.
[0016] Figures 7A to 7E These are instance frame sequences for using a two-way handshake to negotiate and extend a CBF session, according to some embodiments.
[0017] Figure 8 This is a flowchart illustrating an example process for extending a CBF session using a two-way handshake negotiation, according to some embodiments.
[0018] Figures 9A to 9D It is an instance frame sequence for using a three-way handshake to negotiate and extend a CBF session, according to some embodiments.
[0019] Figure 10 This is a flowchart illustrating an example process for extending a CBF session using a three-way handshake negotiation, according to some embodiments.
[0020] Figure 11 This is a flowchart illustrating an instance process of extending a CBF session by negotiating the number of CBF transmissions, according to some embodiments.
[0021] Figure 12 This is a flowchart illustrating an example process for extending a CBF session by alternately transmitting trigger frames via an access point (AP) according to some embodiments.
[0022] Figure 13 It is a sequence of instance frames between the shared AP and the shared AP during CBF transmission according to some embodiments.
[0023] Details of various embodiments of the method and system are set forth in the accompanying drawings and the following description. Detailed Implementation
[0024] The following disclosure provides numerous different embodiments or instances for implementing various features of the provided subject matter. Specific examples of components and arrangements are described below to simplify this disclosure. Of course, these are merely examples and are not intended to be limiting. For example, in the following description, a first feature communicating or communicatively coupled to a second feature may include embodiments in which the first feature directly communicates with or is directly coupled to the second feature, and may also include embodiments in which an additional feature may intervene between the first and second features, such that the first feature indirectly communicates with or is indirectly coupled to the second feature. Furthermore, reference numerals and / or letters may be repeated in various instances of this disclosure. Such repetition is for simplicity and clarity and does not in itself indicate a relationship between the various embodiments and / or configurations discussed.
[0025] The following IEEE standards, including any draft versions thereof, are incorporated herein by reference in their entirety for all purposes and form part of this disclosure: the WiFi Alliance standards and the IEEE 802.11 standards, including but not limited to IEEE 802.11a. TM IEEE 802.11b TM IEEE 802.11g TM IEEE P802.11n TM IEEE P802.11ac TM ; and IEEE P802.11be TM To IEEE P802.11bn TM Standards. Although this disclosure may refer to aspects of these standards, it is in no way limited by them.
[0026] For the purpose of reading the following description of various embodiments, the following description of the sections of the specification and their corresponding contents may be helpful:
[0027] Section A describes the network and computing environments that can be used to practice the embodiments described herein; and
[0028] Section B describes embodiments of systems and methods for providing extended Ethernet frameworks.
[0029] A. Computing and Network Environment
[0030] Before discussing specific embodiments of this solution, it may be helpful to describe aspects of the operating environment and associated system components (e.g., hardware elements) in conjunction with the methods and systems described herein. References Figure 1AThis describes an embodiment of a network environment. In short, the network environment includes a wireless communication system comprising one or more access points (APs) or network devices 106, one or more stations or wireless communication devices 102, and network hardware components or network hardware 192. Wireless communication devices 102 may, for example, include laptop computers, tablet computers, personal computers, and / or cellular telephone devices. Reference Figure 1B and 1C More detailed descriptions are provided for embodiments of each station or wireless communication device 102 and AP or network device 106. In one embodiment, the network environment may be an ad hoc network environment, an infrastructure wireless network environment, a subnet environment, etc. Network device 106 or AP may be operatively coupled to network hardware 192 via a local area network (LAN) connection. In some embodiments, network device 106 is a 5G base station. Network hardware 192 (which may include routers, gateways, switches, bridges, modems, system controllers, appliances, etc.) may provide LAN connectivity for the communication system. Each of network device 106 or AP may have an associated antenna or antenna array to communicate with wireless communication devices in its area. Wireless communication device 102 may register with a specific network device 106 or AP to receive services from the communication system (e.g., via SU-MIMO or MU-MIMO configuration). For direct connections (e.g., point-to-point communication), some wireless communication devices may communicate directly via assigned channels and communication protocols. Some wireless communication devices 102 may be mobile or relatively stationary relative to network device 106 or AP.
[0031] In some embodiments, network device 106 or AP includes means or modules (comprising a combination of hardware and software) that allow wireless communication device 102 to connect to a wired network using Wi-Fi or other standards. Network device 106 or AP may sometimes be referred to as a wireless access point (WAP). Network device 106 or AP may be implemented (e.g., configured, designed, and / or built) for operation in a wireless local area network (WLAN). In some embodiments, network device 106 or AP may be connected as a standalone device to a router (e.g., via a wired network). In other embodiments, network device 106 or AP may be a component of a router. Network device 106 or AP may provide network access to multiple devices. Network device 106 or AP may, for example, connect to a wired Ethernet connection and use a radio frequency link to provide wireless connectivity to other devices 102 to utilize the wired connection. Network device 106 or AP may be implemented to support standards that use one or more radio frequencies to transmit and receive data. Those standards and the frequencies they use may be defined by IEEE (e.g., the IEEE 802.11 standard). Network device 106 or AP can be configured and / or used to support public Internet hotspots and / or extend the Wi-Fi signal range of a network over a network.
[0032] In some embodiments, access point or network device 106 may be used (e.g., in a home, vehicle, or building) for wireless networks (e.g., IEEE 802.11, Bluetooth, ZigBee, any other type of radio frequency-based network protocol, and / or variations thereof). Each of the wireless communication devices 102 may include a built-in radio and / or be coupled to a radio. Such wireless communication devices 102 and / or access point or network device 106 may operate according to various aspects of this disclosure as presented herein to enhance performance, reduce cost and / or size, and / or enhance broadband applications. Each wireless communication device 102 may have the ability to act as a client node seeking access to resources (e.g., data and connections to networked nodes, such as servers) via one or more access point or network devices 106.
[0033] The network connection may include any type and / or form of network and may include any of the following: point-to-point network, broadcast network, telecommunications network, data communication network, computer network. The network topology may be a bus, star, or ring network topology. The network may be any such network topology known to those skilled in the art capable of supporting the operations described herein. In some embodiments, different types of data may be transmitted via different protocols. In other embodiments, the same type of data may be transmitted via different protocols.
[0034] The communication device 102 and the access point or network device 106 can be deployed as any type and form of computing device, such as a computer, network device or appliance capable of communicating and performing the operations described herein on any type and form of network and / or performing them thereon. Figure 1B and 1C A block diagram depicting a computing device 100 that can be used to implement embodiments of wireless communication device 102 or network device 106. (See diagram for reference.) Figure 1B and 1C As shown, each computing device 100 includes a processor 121 (e.g., a central processing unit) and a main memory unit 122. Figure 1B As shown, the computing device 100 may include a storage device 128, a mounting device 116, a network interface 118, an I / O controller 123, display devices 124a to 124n, a keyboard 126, and a pointing device 127, such as a mouse. The storage device 128 may include an operating system and / or software. Figure 1C As shown, each computing device 100 may also include additional optional components such as memory port 103, bridge 170, one or more input / output devices 130a to 130n, and cache memory 140 that communicates with the central processing unit or processor 121.
[0035] The central processing unit or processor 121 is any logic circuit system that responds to and processes instructions fetched from main memory unit 122. In many embodiments, the central processing unit or processor 121 is provided by a microprocessor unit, such as a microprocessor unit manufactured by Intel Corporation of Santa Clara, California; a microprocessor unit manufactured by International Business Machines of White Plains, New York; or a microprocessor unit manufactured by Advanced Micro Devices of Sunnyvale, California. The computing device 100 may be based on any of these processors, or any other processor capable of operating as described herein.
[0036] Main memory unit 122 may be one or more memory chips capable of storing data and allowing direct access to any storage location by a microprocessor or processor 121, such as any type or variant of static random access memory (SRAM), dynamic random access memory (DRAM), ferroelectric RAM (FRAM), NAND flash memory, NOR flash memory, and solid-state drive (SSD). Main memory unit 122 may be based on any of the aforementioned memory chips, or any other available memory chips capable of operating as described herein. Figure 1B In the embodiment shown, processor 121 communicates with main memory unit 122 via system bus 150 (described in more detail below). Figure 1C An embodiment of computing device 100 is depicted, wherein the processor communicates directly with main memory unit 122 via memory port 103. For example, in Figure 1C In this context, the main memory unit 122 can be DRDRAM.
[0037] Figure 1C An embodiment is depicted in which the main processor 121 communicates directly with the cache memory 140 via a secondary bus (sometimes called a back-end bus). In other embodiments, the main processor 121 communicates with the cache memory 140 using a system bus 150. The cache memory 140 typically has a faster response time than the main memory unit 122 and is provided by, for example, SRAM, BSRAM, or EDRAM. Figure 1CIn the embodiments shown, processor 121 communicates with various I / O devices 130 via local system bus 150. Various buses can be used to connect the central processing unit or processor 121 to any of the I / O devices 130, such as VESA VL bus, ISA bus, EISA bus, Microchannel Architecture (MCA) bus, PCI bus, PCI-X bus, PCI-Express bus, or NuBus. In embodiments where the I / O device is a video display 124, processor 121 may use an Advanced Graphics Port (AGP) to communicate with the display 124. Figure 1C An embodiment of a computer or computer system 100 in which the main processor 121 can communicate directly with the I / O device 130b, for example, via HYPERTRANSPORT, RAPIDIO, or INFINIBAND communication technologies is described. Figure 1C An embodiment in which a hybrid local bus and direct communication is also depicted: the processor 121 communicates with I / O device 130a using the local interconnect bus, while simultaneously communicating directly with I / O device 130b.
[0038] The computing device 100 may contain various I / O devices 130a to 130n. Input devices include a keyboard, mouse, trackpad, trackball, microphone, dial pad, touchpad, touch screen, and drawing tablet. Output devices include a video display, speaker, inkjet printer, laser printer, projector, and dye-to-sublimation printer. The I / O devices can be controlled by the I / O controller 123, such as... Figure 1B As shown in the figure. The I / O controller can control one or more I / O devices, such as keyboard 126 and pointing device 127, such as mouse or light pen. In addition, the I / O devices can also provide storage and / or mounting media for computing device 100. In other embodiments, computing device 100 can provide USB connectivity (not shown) to receive handheld USB storage devices, such as the USB flash drive series devices manufactured by Twintech Industry, Inc. of Los Alamitos, California.
[0039] Refer again Figure 1BThe computing device 100 may support any suitable installation device 116, such as a disk drive, CD-ROM drive, CD-R / RW drive, DVD-ROM drive, flash drive, tape drive of various formats, USB device, hard disk drive, network interface, or any other device suitable for installing software and programs. The computing device 100 may further include a storage device, such as one or more hard disk drives or a redundant array of independent disks, for storing the operating system and other related software, and for storing application software programs, such as any program or software 120 used to implement (e.g., configured and / or designed for) the systems and methods described herein. Optionally, any installation device 116 may also be used as a storage device. Additionally, the operating system and software may be run from a bootable media.
[0040] Furthermore, the computing device 100 may include a network interface 118 to interface with a network via various connections, including but not limited to standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56kb, X.25, SNA, DECNET), broadband connections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet, Ethernet over SONET), wireless connections, or some combination of any of the above. Various communication protocols (e.g., TCP / IP, IPX, SPX, NetBIOS, Ethernet, ARCNET, SONET, SDH, Fiber Distributed Data Interface (FDDI), RS232, IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11ac, IEEE 802.11ad, CDMA, GSM, WiMAX, and direct asynchronous connections) can be used to establish connections. In one embodiment, computing device 100 communicates with other computing devices 100' via any type and / or form of gateway or tunneling protocol, such as Secure Sockets Layer (SSL) or Transport Layer Security (TLS). Network interface 118 may include a built-in network adapter, network interface card, PCMCIA network card, card bus network adapter, wireless network adapter, USB network adapter, modem, or any other means suitable for interfacing computing device 100 to any type of network capable of communicating and performing the operations described herein.
[0041] In some embodiments, computing device 100 may include or be connected to one or more display devices 124a to 124n. Therefore, any I / O devices 130a to 130n and / or I / O controller 123 may include any type and / or form of suitable hardware, software, or a combination of hardware and software to support, enable, or provide computing device 100 with connectivity to and use of display devices 124a to 124n. For example, computing device 100 may include any type and / or form of video adapter, video card, driver, and / or library to interface with, communicate with, connect to, or otherwise use display devices 124a to 124n. In one embodiment, a video adapter may include multiple connectors to interface with display devices 124a to 124n. In other embodiments, computing device 100 may include multiple video adapters, each connected to display devices 124a to 124n. In some embodiments, any portion of the operating system of computing device 100 may be configured to use multiple display devices 124a to 124n. In another embodiment, I / O device 130 may be a bridge between system bus 150 and external communication bus, such as USB bus, Apple Desktop bus, RS-232 serial connection, SCSI bus, FireWire bus, FireWire 800 bus, Ethernet bus, AppleTalk bus, Gigabit Ethernet bus, Asynchronous Transfer Mode bus, Fibre Channel bus, Fibre Bus, Serial Attached Small Computer System Interface bus, USB connection, or HDMI bus.
[0042] Figure 1B and 1CThe computing device 100 of the type described herein can operate under the control of an operating system that controls task scheduling and access to system resources. The computing device 100 can run any operating system, such as any version of Microsoft Windows, different versions of Unix and Linux, any version of MAC OS for Macintosh computers, any embedded operating system, any real-time operating system, any open-source operating system, any proprietary operating system, any operating system for mobile computing devices, or any other operating system capable of running on a computing device and performing the operations described herein. Typical operating systems include, but are not limited to: Android, produced by Google Inc.; Windows 7, 8, and 10, produced by Microsoft Corporation of Redmond, Washington; MAC OS, produced by Apple Computer of Cupertino, California; WebOS, produced by Research In Motion (RIM); OS / 2, produced by International Business Machines Corporation of Armonk, New York; and Linux, a free operating system distributed by Caldera Corp. of Salt Lake City, Utah, or any type and / or form of Unix operating system.
[0043] The computer system or computing device 100 may be any workstation, telephone, desktop computer, laptop or notebook computer, server, handheld computer, mobile phone or other portable telecommunications device, media playback device, gaming system, mobile computing device, or any other type and / or form of computing, telecommunications, or media device capable of communication. In some embodiments, the computing device 100 may have a different processor, operating system, and input device consistent with the device described herein. For example, in one embodiment, the computing device 100 is a smartphone, mobile device, tablet computer, or personal digital assistant. Furthermore, the computing device 100 may be any workstation, desktop computer, laptop or notebook computer, server, handheld computer, mobile phone, any other computer, or other form of computing or telecommunications device capable of communication and having sufficient processor power and memory capacity to perform the operations described herein.
[0044] The aspects of the operating environment and components described above will become apparent in the context of the systems and methods disclosed herein.
[0045] B. Features zero-reset coordinated beamforming (CBF)
[0046] Before a coordinated beamforming (CBF) transmission with zeroing occurs, where two or more APs concurrently transmit to their respective associated STAs, a setup phase may be performed. This setup phase includes handshakes and frame exchanges to coordinate upcoming downlink resources and / or timing. These frame exchanges may occur between the APs themselves or between each AP and its associated STA, allowing both AP alignment and AP-STA readiness to be established before the coordinated transmission begins.
[0047] Figure 2 This is an example of a CBF setup frame sequence 200 according to some embodiments. In the CBF setup frame sequence 200, AP1 (201) and AP2 (202) coordinate with their respective stations AP1-STA (203) and AP2-STA (204) before the coordinated beamforming downlink. In this sequence, AP1 begins with a CBF-invitation 211, and AP2 responds with a CBF-response 212. AP-STA readiness is established by exchanging an Initial Control Frame (ICF) 213 and an Initial Control Response (ICR) 214 between AP1 and AP1-STA, and by exchanging an ICF 215 and an ICR 216 between AP2 and AP2-STA. After these handshakes, AP1 transmits a CBF-trigger 217 to AP2 after a Short Interframe Spacing (SIFS) timing, thereby providing AP2 with alignment information for subsequent synchronous transmission. Subsequently, following the SIFS timing, the two APs execute their Coordinated Downlink Physical Layer Protocol Data Units (CBF PPDUs) 218 and 219.
[0048] refer to Figure 2The AP-AP frame exchange may include a CBF-invitation 211 transmitted by AP1 (201) to notify AP2 (202) of a CBF transmission opportunity (TXOP) and invite AP2 to participate in the CBF TXOP. The CBF-invitation may include information identifying which AP1-STAs will be served in the TXOP, the number of spatial streams (Nss) allocated to each AP1-STA, the maximum Nss allowed for AP2's STAs, the bandwidth of the CBF transmission, and / or the minimum and maximum duration of the CBF transmission that AP1 can support. A CBF-response 212 transmitted by AP2 in response to the CBF-invitation 211 informs AP1 whether AP2 will participate in the CBF TXOP, and if participation is confirmed, it may indicate to AP1 which AP2-STAs will be served in the TXOP, the number of spatial streams (Nss) allocated to each AP2-STA, the MCS to be used by each AP2-STA, and / or the minimum and maximum duration of the CBF transmission that AP2 can support. A CBF-trigger 217 transmitted by AP1 prior to CBF transmission 218 serves as a reference for AP2, ensuring that subsequent CBF transmissions from AP1 and AP2 are aligned in terms of start time, end time, frequency, and / or preamble content. The CBF-trigger may contain information necessary to construct the preamble for the CBFPPDU to be transmitted. AP-STA frame exchange may include an ICF (e.g., ICF 213) transmitted by the AP at or near the start of a TXOP to notify one or more associated STAs of an upcoming TXOP, inquiring about their availability and preparing them to receive or transmit data. For example, an ICF may trigger a STA operating in Enhanced Multi-Link Single Radio (EMLSR) listener mode or Dynamic Power Saving (DPS) low-capability mode to switch to full receive / transmit capability mode. An ICR (e.g., ICR 214) is transmitted by one or more STAs addressed via an ICF in response to receiving the ICF, and may indicate availability and confirm the switch to full receive / transmit capability mode. AP-AP frame switching can be interleaved with or embedded in AP-STA frame switching, enabling AP-AP coordination and AP-STA readiness to proceed in tandem.
[0049] Figure 3This is another example of a CBF setup frame sequence 300 according to some embodiments. In the CBF setup frame sequence 300, AP1 (301) combines the ICF to AP1-STA with the CBF-invitation to AP2 (302) (as message 311), receives the ICR (312), and then AP2 sends a combined message 313 of the ICF to AP2-STA (304) and the CBF-response to AP1, followed by the ICR 314. After SIFS, AP1 transmits a CBF-trigger 315 for timing and preamble reference, enabling the two APs to start downlink beamforming PPDUs 316, 317 in a synchronized manner.
[0050] Following a CBF transmission, a CBF acknowledgment (ACK) phase may occur, during which frames are exchanged between the AP and the corresponding STA to request or transmit acknowledgment frames, such as ACK and BlockACK (BA). These acknowledgment frames provide each AP with an indication of which MPDUs transmitted in the previous CBF transmission were correctly received and decoded at each STA without errors.
[0051] Figure 4 This is an example CBF ACK frame sequence 400 according to some embodiments. In frame sequence 400, each AP 401, 402 transmits CBF PPDUs 411, 412, whose embedded trigger requests immediate BlockAck (BA) feedback from its STA, wherein AP1 (401) addresses AP1-STA (403) and AP2 (402) addresses AP2-STA (404). After the embedded trigger, the addressed STA returns its corresponding BA in trigger-based (TB) PPDUs 413, 414 at SIFS. This sequence corresponds to the case where each AP signals the request for immediate ACK / BA in its CBF PPDU and relies on the embedded trigger to enable the TB PPDU response of the merged SIFS interval.
[0052] In the CBF ACK frame sequence 400, CBF PPDUs or transmissions 411, 412 may indicate a request for immediate ACK or BA to each AP 401, 402 and each of its corresponding STAs, and the CBF PPDU may be embedded in a trigger frame, which enables each STA to transmit its corresponding ACK or BA in a TB PPDU. Then, STAs 403, 404 associated with the two APs may jointly transmit their corresponding ACK or BA in a single TB PPDU 413, 414 transmitted at SIFS after the CBF transmission is completed, thereby allowing the acknowledgment process to occur in a unified uplink response.
[0053] Figure 5This is another example of a CBF ACK frame sequence 500 according to some embodiments. In frame sequence 500, AP1 (501) embeds a trigger for BA in its CBF PPDU 511 to AP1-STA 503, while AP2 (502) does not request immediate BA in its PPDU 512 to AP2-STA 504. After SIFS, AP1-STA 503 returns a TB PPDU 513 with BA. Subsequently, AP2 issues a Multi-User BA Request (MU-BAR) 514 to AP2-STA 504, upon which AP2 STA returns a TB PPDU 515 carrying BA. Figure 5 This demonstrates a scenario where only one AP triggers an immediate BA via an embedded trigger, while another AP obtains its BA using a separate MU-BAR after the first BA is completed.
[0054] In frame sequence 500, a CBF PPDU or transmission 511 may be configured such that AP1 instructs each of its associated STAs to request an ACK or Block ACK (BA) immediately after the CBF PPDU. This means that AP1's STAs are instructed to return their ACK or BA at SIFS after the CBF transmission ends, while AP2 does not include such an instruction for its associated STAs and therefore does not cause those STAs to transmit BA immediately after the CBF PPDU. When AP1 embeds triggers for each STA in a CBF transmission, such as when addressing more than one AP1-STA, all AP1-STAs may jointly transmit their ACK or BA in a single TB PPDU. However, when only one AP1-STA is included in a CBF transmission and AP1 chooses not to embed triggers for that STA, the STA may respond with an ACK or BA in a non-TB PPDU. Following an ACK or BA transmitted by AP1-STA at SIFS after CBF transmission, AP2 may transmit a BA request (BAR) to its own STA, and when AP2 addresses one or more STAs, it may transmit a multi-user BAR (MU-BAR) 514. STAs addressed by the BAR transmitted by AP2 then return their corresponding ACK or BA at SIFS after the BAR or MU-BAR ends, and when using a MU-BAR, the STAs may jointly respond in a TB PPDU (e.g., a TB PPDU 515 with a BA).
[0055] Figure 6This is yet another example of a CBF ACK frame sequence 600 according to some embodiments. In frame sequence 600, neither AP requests an immediate BA in its CBF PPDUs 611, 612, where AP1 (601) and AP2 (602) address AP1-STA (603) and AP2-STA (604), respectively. After the CBF PPDU, AP1 transmits MU-BAR 613 and receives TBPPDU 614 with BA. After another SIFS, AP2 transmits its MU-BAR 615 and then receives TBPPDU 616 with BA.
[0056] In CBF ACK frame sequence 600, neither AP indicates in the CBF PPDU or transmission that it will immediately request an ACK or BA after the CBF PPDU, and therefore none of the STAs associated with either AP transmit an ACK or BA when the CBF PPDU is completed. After the CBF PPDU at the SIFS interval, AP1 may transmit a BA request (BAR) to its STAs, and when AP1 is addressing one or more STAs, it may alternatively transmit a multi-user BAR (MU-BAR) 613. Then, the STAs addressed by the BAR or MU-BAR from AP1 transmit their corresponding ACK or BA at the SIFS after the BAR or MU-BAR ends, and when using the MU-BAR, the STAs jointly return their ACK or BA in TB PPDU 614. After completing the ACK or BA from the STA of AP1 at the SIFS following the BAR or MU-BAR, AP2 then transmits its own BAR to its associated STA, and AP2 may also transmit MU-BAR 615 when one or more STAs are addressed. Then, the STAs addressed by the BAR or MU-BAR from AP2 transmit their corresponding ACK or BA at the SIFS following the BAR or MU-BAR, and when AP2 uses MU-BAR, the STAs jointly transmit their ACK or BA in TB PPDU 616.
[0057] C. Systems and methods for providing CBF via coordinated beamforming (CBF) sessions
[0058] In one aspect, the multiple frames involved in setting up CBF transmission may introduce protocol overhead, and in order to minimize the impact of this overhead and improve efficiency, it is generally desirable to make CBF transmission as long as possible.
[0059] However, several constraints may prevent the use of a single long CBF transmission in all cases. Under the current 802.11 specification, there is a limit to the maximum duration of an OFDM-formatted PPDU, which is approximately 5.4 ms in the 2.4 GHz, 5 GHz, or 6 GHz bands. The maximum amount of data that can be transmitted to any STA in a single PPDU is limited by the maximum MPDU length (approximately 11 KB under the current 802.11 specification) and the maximum number of MPDUs that can be aggregated within a single A-MPDU in that STA's PPDU; this aggregation capacity is further limited by the AP's corresponding maximum transmit capability and the STA's maximum receive capability. The maximum number of incomplete MPDUs awaiting acknowledgment from the STA is further limited by the STA's BlockAck window size (BA window size), counting from the earliest incomplete MPDU, thus the STA benefits from acknowledging successfully received MPDUs from previous transmissions so that the AP can aggregate to the maximum limit in subsequent transmissions. The amount of STA data available at the associated AP of the STA at the start of CBF launch may also be limited by the provided service load or service profile, and this availability may constrain the launch duration of CBF PPDU even if other limitations would allow for longer launches.
[0060] To address these limitations, this disclosure may use CBF sessions (also referred to as “sessions”) to improve CBF efficiency and / or use frame sequences to extend or continue a CBF session after an initial (or first) CBF transmission. In some embodiments, a CBF session may be formed where there are successive additional CBF transmissions following the initial CBF transmission, and the additional CBF transmissions within a CBF session may result in less or reduced overhead compared to the initial overhead associated with the setup phase. According to some embodiments, this disclosure provides frame sequences and methods that achieve efficient CBF operation by allowing multiple CBF transmissions to occur within a single CBF session, thereby reusing previously established parameters and minimizing the need for repeated setup exchanges for successive CBF transmissions across sessions.
[0061] In some embodiments, a CBF session (or simply "session") can be a sequence of one or more CBF transmissions that reuse one or more parameters that remain constant across the CBF transmissions within the session, thereby allowing coordinated downlink activity to proceed without needing to renegotiate those parameters for each subsequent transmission. A CBF session may begin with an initial setup phase prior to the first CBF transmission in the sequence, establishing inter-AP and / or AP-STA conditions to achieve coordinated beamforming (CBF) with zeroing. Within the session, the STA may transmit ACK or BA (block ACK) frames to the AP between CBF transmissions to confirm which Media Access Control (MAC) Protocol Data Units (MPDUs) from previous CBF transmissions the STA correctly received, thereby allowing the AP to manage the MPDU window and determine the appropriate aggregation level for subsequent transmissions within the session.
[0062] In some embodiments, a CBF session can occur within a single TXOP, allowing consecutive CBF transmissions to be time-separated by SIFS intervals, and the group of APs participating in each CBF transmission can remain unchanged relative to previous transmissions within the same session. A group of STAs addressed via a CBF transmission can remain the same as or a subset of a group of STAs addressed via previous CBF transmissions within the session, and similarly, the MCS used for a STA in a CBF transmission can be the same as the MCS used for that STA in a previous CBF transmission. The Nss used for a STA in a CBF transmission can also remain the same, or may not exceed the Nss used for that STA in a previous CBF transmission. A set of zero-return directions used by the APs in CBF transmissions, representing the spatial direction or vector along which the AP zeros its transmitted signal, can similarly remain the same as the zero-return directions used in previous CBF transmissions within the session. APs participating in the session can exchange one or more CBF session-extended frames after each CBF transmission to determine whether the CBF session should continue or terminate, whether the parameters of the upcoming CBF transmission should be changed, and / or whether one or more parameters or contents of the preamble of the upcoming CBF transmission should be indicated. These CBF session-extended frames can be transmitted independently or embedded within other frames or PPDUs exchanged between the AP and its corresponding STA, such as MU-BAR frames or TB PPDUs concurrently carrying BAs from the STA. Several different embodiments of such CBF session-extended frame sequences are described (see [link to documentation]). Figures 7A to 7E 8, 9A to 9D, 10, 11, 12) can be used within a given CBF session.
[0063] In some embodiments, during a CBF session, ICF or ICR exchanges may not occur between an AP and its associated STA during the interval between consecutive CBF transmissions. In some embodiments, intermediate frames exchanged between APs may not be addressed to some STAs. As a result, STAs with EMLSR capability or DPS capability may need to remain in full RX / TX capability until a predetermined timeout period expires after a CBF transmission or CBF-ACK sequence. This behavior relies on the use of an EMLSR / DPS extended timeout mechanism already applied during the CBF initial setup phase, but the timeout interval applicable to the CBF-continue phase may differ from and is typically shorter than the timeout used during the CBF setup phase. The extended timeout may begin at the end of an ACK transmitted by a STA.
[0064] In cases involving sequential ACK (e.g., with CBF ACK frame sequence 500 (see...) Figure 5 ) or CBF ACK frame sequence 600 (see Figure 6 In the case of those sequential ACKs associated with , the extended timeout of the STA that transmits its ACK earlier may or must exceed the timeout of the STA that transmits its ACK later, thereby ensuring that each STA remains available during the time interval in which the STA may be addressed in a subsequent CBF PPDU. The extended timeout is configurable such that the next CBF PPDU intended for the STA is anticipated before the timeout expires. If no CBF-PPDU is received while the timeout is active, or if a CBF-PPDU not addressed to the STA is received, the extended timeout may end, and the EMLSR or DPS STA may return to a basic state, such as a listening or low-power listening mode. In some embodiments, the extended timeout rule may instruct the STA to reset its timer and restart the timeout countdown when it detects one or more frames associated with an intermediate AP-AP exchange, said one or more frames containing a CBF-continue frame or an intermediate CBF-invitation, intermediate CBF-response, or intermediate CBF-trigger, if such a frame is available before a CBF PPDU or CBF transmission. These rules may also specify that the STA resets its timer when it detects certain special or predefined control frames that relate to its associated AP as a transmitter or receiver, such as a clear send (CTS) to that AP (also known as "CTS-A").
[0065] In some embodiments, the ICF-ICR exchange performed at the beginning of a CBF TXOP confirms the availability of a STA for the expected transmission duration and also confirms whether those same STAs remain available for the duration of subsequent CBF PPDUs. In some cases, ICR verifies the known availability of a STA, enabling the AP to determine whether to continue transmitting multiple CBF PPDUs and identify which STAs are suitable targets for the next CBF PPDU. Alternatively, the CBF ACK sequence may embed a multi-STA block ACK (MBA) to signal the availability period for subsequent CBF PPDU transmissions, and this availability information can be used by the AP when choosing whether to continue the session and which STAs to address in future PPDUs.
[0066] In some embodiments, the AP may include in the MU-BAR or CBF-PPDU a signal indicating that it is triggering the last BA or otherwise indicating that there is no additional downlink data remaining for one or more non-AP STAs in the CBF session or TXOP. When an EMLSR or DPS non-AP STA receives such an indication, it may return to its listening mode or low-capacity mode immediately after transmitting its BA, rather than waiting for the extended timeout period to expire. This indication may be communicated within the final MU-BAR or the last CBF-PPDU in the CBF frame sequence and may be used as a common indication for all non-AP STAs addressed by the AP.
[0067] In some embodiments, various frames exchanged between APs during a CBF session between CBF transmissions (including CBFACK sequence frames (e.g., MU-BAR or TB PPDU with BA) and independent variations of intermediate CBF-invitation, intermediate CBF-response, CBF-continue, or intermediate CBF-trigger frames) may include padding to allow their intended recipient (e.g., AP) sufficient processing time. The amount of padding may be negotiated in advance, and / or the padding applied to intermediate CBF-invitation, intermediate CBF-response, and intermediate CBF-trigger frames may be less than the padding used for the corresponding CBF-invitation, CBF-response, and CBF-trigger frames during the initial setup phase.
[0068] In some embodiments, optional hidden node protection may be applied to subsequent CBF PPDUs even if ICF and / or ICR exchanges are not required before each non-initial CBF PPDU. Such protection may involve intermediate ICF and / or ICR exchanges between each AP and its corresponding participating STA. Intermediate ICFs may contain less padding or no padding compared to the initial phase ICF, because EMLSR or DPS STAs may not require additional time to switch to full RX / TX capability. Furthermore, intermediate ICFs and / or ICRs can utilize shorter duration frame sequences, such as MU-RTS / CTS or RTS / CTS, when addressing individual STAs, even when ICF / ICRs in the initial setup phase utilize longer sequences, such as Buffer Status Report Polling (BSRP) followed by Buffer Status Report (BSR) in a TB PPDU. Using shorter sequences reduces overhead during the continuation of the CBF session.
[0069] In some embodiments, when the CBF session uses CBF ACK frame sequence 500 (see CBF ACK frame sequence 500), Figure 5 ) or CBF ACK frame sequence 600 (see Figure 6 When ACKs are sent in a consistent sequence, APs can dynamically negotiate the order or sequence in which each AP's STA provides its ACK or BA. This negotiation determines which APs' acknowledgments occur first and which occur next, and can be flexibly adjusted during an active CBF session by renegotiating from one CBF-ACK sequence to the next. This negotiation can occur or be signaled in one or more previous frames exchanged before or within the ongoing CBF session.
[0070] In light of the foregoing, the following figures and descriptions illustrate various examples of techniques for using CBF sessions to improve CBF efficiency and / or for extending or continuing CBF sessions after the initial (or first) CBF transmission using frame sequences. The following figures and descriptions are non-limiting examples and can be implemented in any of a variety of other configurations while remaining within the scope of this disclosure. Other embodiments may be used alternatively or as alternatives. Details that will be obvious to those skilled in the art may be omitted. Some embodiments may be practiced with additional components or steps and / or without all the components or steps described. In some embodiments, a combination of two or more techniques may be used within a CBF session (e.g., more than one technique may be employed).
[0071] 1. Session extension frame sequence negotiated using a two-way handshake
[0072] In some embodiments, during a CBF session, after each CBF transmission, participating APs can negotiate whether a next CBF transmission will occur. This negotiation can take the form of a two-way handshake, where one AP sends a CBF-Continue message to the other AP, indicating, for example, based on service availability, whether it can participate in the next CBF transmission. When the CBF-Continue message indicates that the transmitting AP can participate in the next CBF transmission, the message may additionally convey information such as the maximum or minimum duration of the next CBF transmission that the AP can support, the set of STAs that will be addressed by the transmitting AP in the next CBF transmission, the MCS of each STA to be addressed, the number of spatial flows Nss for each STA to be addressed, and / or the preferred guard interval + long training field (GI+LTF) for the next CBF transmission.
[0073] In some embodiments, if the CBF-Continue message signals the ability to continue, the receiving AP can respond with an intermediate CBF-Trigger, which also indicates its ability to participate in the next CBF transmission based on service or related conditions. When the intermediate CBF-Trigger indicates that the transmitting AP can participate, the message may further specify the duration of the next CBF transmission, for example by conveying the L-SIG (Traditional Signal Field) length, and the contents of a set of STAs and one or more preamble fields of the transmitting AP to be addressed in the next CBF transmission, including the L-SIG length, GI+LTF, MCS of each STA, and / or Nss of each STA. When the intermediate CBF-Trigger confirms the AP's participation, the two APs may concurrently or simultaneously begin the next CBF transmission, for example at SIFS following the intermediate CBF-Trigger.
[0074] In some embodiments, the set of STAs addressed in the next CBF transmission may be the same set of STAs addressed in the previous CBF transmission or a subset of said STAs. Similarly, the Nss of each STA addressed in the next CBF transmission may be equal to or no more than the Nss used for said STA in the previous CBF transmission. CBF-continue messages or intermediate CBF-triggers may be transmitted as independent frames or may be embedded within a CBF ACK sequence associated with a previous CBF transmission; for example, either message may be included in a MU-BAR frame transmitted by an AP to its STA, allowing another AP to concurrently receive continue information, or one of these messages may be transmitted by an AP in a TB PPDU, which also includes a BA transmitted by a STA associated with another AP.
[0075] In some embodiments, to provide sufficient processing time for the intended receiver, the CBF-Continue message or intermediate CBF-Trigger may include padding, and this padding may be adjusted based on implementation constraints. When the CBF-Continue message is transmitted as a separate frame, the intermediate CBF-Trigger may follow at SIFS after the CBF-Continue information. When the CBF-Continue message is embedded within a CBFACK sequence, the intermediate CBF-Trigger may be transmitted at SIFS after the last frame of the CBF ACK sequence.
[0076] In some embodiments, the AP may pre-negotiate conditions for postponing the CBF ACK sequence until multiple CBF transmissions are completed within the CBF session (e.g., until the AP is unable to continue a CBF transmission without receiving an ACK or BA from its STA, or until the AP has no further pending traffic). In this case, the AP may notify its respective STA that a single CBF ACK sequence will be used to acknowledge the MPDU transmitted for multiple CBF transmissions across the CBF session. If any AP is unable to continue a further CBF transmission without receiving an ACK or BA from its STA, it may indicate this in a CBF-Continue or Intermediate CBF-Trigger message, such as a CBF ACK frame sequence 600 (see [link to CBF ACK sequence]). Figure 6 You can begin.
[0077] In some embodiments, there may be no ICF or ICR exchange between each AP and its corresponding STA between consecutive CBF transmissions occurring within the same CBF session. In some cases, the lack of a CBF-continue message from an AP may indicate that the AP cannot continue participating in the CBF session. APs may also agree in advance which AP is expected to transmit the CBF-continue message after each CBF transmission to prevent APs from transmitting continue messages simultaneously or concurrently, and the identity of the AP responsible for transmitting the CBF-continue message can alternate between APs across consecutive CBF transmissions in the session.
[0078] In some embodiments, the duration field in the MAC header of one or more frames (including frames such as CBF-trigger, ICF, ICR, CBF-response, or CBF-invitation frames) transmitted during the initial setup phase can be configured to protect subsequent frame sequences by allowing the receiver to postpone media access as needed until the end of an upcoming CBF transmission, the corresponding CBF ACK sequence, the CBF-continue message, or the intermediate CBF-trigger. When the AP agrees to extend the TXOP with additional CBF transmissions, the duration field can be set within the CBF-continue or intermediate CBF-trigger message to protect the second CBF transmission, the associated CBF ACK sequence, the next CBF-continue message, and / or the next intermediate CBF-trigger. This process can be repeated before each further CBF transmission to maintain ordered media access and ensure appropriate protection of the coordinated exchange.
[0079] Figures 7A to 7E These are instance frame sequences for using a two-way handshake to negotiate and extend a CBF session, according to some embodiments. Figure 7A The diagram depicts a CBF session-extended frame sequence 700, in which AP1 701 and AP2 702 complete the first coordinated downlink (CBF PPDU 1 (711, 712)) to AP1-STA 703 and AP2-STA 704, triggering an acknowledgment, exchanging continuation signaling, and then continuing towards the second coordinated downlink (CBF PPDU 2 (718, 719)). CBF PPDU 1 (711, 712) is transmitted from AP1 and AP2, a SIFS interval TB PPDU 713 with BA is transmitted from AP1-STA 703, AP2 transmits MU-BAR 714 to AP2-STA 704, and a subsequent TB PPDU 715 with BA is transmitted from AP2-STA 704. Subsequently, AP2 702 transmits CBF-Continue Instruction 716, and then AP1 701 transmits an intermediate CBF-Trigger 717 at SIFS prior to CBF PPDU 2 (718, 719).
[0080] Figure 7BThe CBF session is depicted as an extended frame sequence 720, in which AP1 721 and AP2 722 execute CBF PPDU 1 (731, 732), and AP1 receives a SIFS interval TB PPDU 733 with a BA from AP1-STA 723. AP2 transmits a MU BAR 734 to AP2-STA 724, and AP2-STA 724 transmits a TB PPDU 735 with a BA at the SIFS. Subsequently, AP1 transmits CBF-Continue 736, and AP2 responds with an intermediate CBF-Trigger 737 to initiate CBF PPDU 2 (738, 739).
[0081] Figure 7C The CBF session-extended frame sequence 740 is described, where CBF-Continuation is communicated or embedded within MU-BAR 754, rather than being communicated via a separate control frame. AP1 741 and AP2 742 perform the first coordinated downlink (CBF PPDU 1 (751, 752)) to AP1-STA 743 and AP2-STA 744, receiving a SIFS-interval TB PPDU 753 with BA from AP1-STA 743. AP2 then carries or embeds CBF-Continuation within MU BAR (MU BAR+CBF-Continuation 754). After transmitting a TB PPDU 755 with BA from AP2-STA 744, AP1 sends an intermediate CBF-Trigger 756 at SIFS to prepare for CBF PPDU 2 (757, 758).
[0082] Figure 7DThis presents a closely related scenario regarding the delivery of CBF-Continue within a TB PPDU. In the CBF session-extended frame sequence 760, AP1 761 and AP2 762 execute the first coordinated downlink (CBF PPDU 1 (771, 772)) to AP1-STA 763 and AP2-STA 764, receiving a TB PPDU 773 with a SIFS interval of BA from AP1-STA 763. AP2 sends MU-BAR 774, and then AP1 embeds CBF-Continue 775 within the TB PPDU at the SIFS interval following MU-BAR 774. In MU-BAR frame 774, AP2 may signal, indicate, or reserve space or frequency resource allocation for AP1 in subsequent TB PPDUs to allow AP1 to embed the CBF-Continue message within the TB PPDU. After concurrently transmitting TBPPDU 775 with CBF-continued and TB PPDU 776 with BA (from AP2-STA 764), AP2 sends an intermediate CBF-trigger 777 at SIFS to prepare CBF PPDU 2 (778, 779).
[0083] Figure 7E The CBF session-extended frame sequence 780 is described, wherein after AP1 781 and AP2 782 perform CBF PPDU 1 (791, 792), AP2 782 transmits CBF-Continue 795 at the SIFS interval following BA exchange (e.g., TB PPDU 793 with BA from AP1-STA 783, and TB PPDU 794 with BA from AP2-STA 784). For example, CBF-Continue is transmitted at the SIFS after the end of a TB PPDU containing BAs from the respective STAs of AP1 and AP2. Subsequently, AP1 781 transmits an intermediate CBF-Trigger 796, resulting in CBF PPDU 2 (797, 798).
[0084] In some embodiments, the first access point (e.g., Figures 7A to 7E AP1 and AP2 may include a network interface and one or more processors. In some embodiments, the term "network interface" may refer to any communication interface of an access point or other device that enables the device to transmit or receive radio frames, including control frames, trigger frames, data units, acknowledgments, or other radio protocol elements used during a CBF session. The network interface may support single-link or multi-link operation and may be configured to exchange signaling with peer access points or associated stations.
[0085] In some embodiments, the term "access point" may refer to a station or wireless network device capable of transmitting frames, coordinating CBF transmissions with peer APs, associating services, or negotiating CBF session parameters. An access point may initiate or respond to CBF-related signaling and may participate in concurrent or alternating CBF transmissions.
[0086] In some embodiments, the term "frame" may cover any wireless transmitting unit that conveys control signaling, CBF-related triggers, acknowledgments, MU-BARs, data payloads, or embedded information used to support CBF negotiation, continuation decisions, or scheduling. Frames may be standalone or embedded within a PPDU or TB PPDU.
[0087] One or more processors may exchange one or more frames with a second access point via a network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmission in a session.
[0088] In some embodiments, the term "parameters for performing CBF transmission" may include information used by the access point to align or coordinate its transmission, such as the selected station to be served, modulation and coding scheme, number of spatial streams, return-to-zero direction, transmission duration, or preamble-related configuration. Other parameters may be incorporated depending on the session's coordination requirements.
[0089] In some embodiments, the term "exchanging one or more frames" can refer to any communication in which a device, such as an access point, transmits or receives radio frames, which may contain control information, acknowledgments, CBF-related triggers, CBF-continue indications, or other signaling for initiating, maintaining, or terminating a CBF transmission sequence. Such an exchange can occur through independent frames or through frames in which CBF-related information is embedded within other protocol elements.
[0090] In some embodiments, the term "CBF transmission" may refer to a downlink PPDU or a set of PPDUs transmitted by an AP using coordinated beamforming parameters, enabling multiple APs to transmit data to their stations with aligned timing and reduced interference. A CBF transmission may be triggered prior to transmission, may depend on previously negotiated parameters, or may occur as part of a series of transmissions in a CBF session.
[0091] During a session, one or more processors may perform CBF transmissions of multiple data units to one or more stations (STAs) via a network interface using one or more parameters. During the session, in response to performing a CBF transmission of a first data unit, one or more processors may transmit a first frame (e.g., CBF-Continue) indicating that the first access point is eligible to participate in the next CBF transmission. In response to receiving a trigger frame, one or more processors may perform a CBF transmission of a second data unit.
[0092] In some embodiments, the term "data unit" may refer to any radio data carried in one or more PPDUs, MPDUs, aggregated frames, or other physical layer or MAC layer encapsulations used in coordinated or uncoordinated transmissions. Such data units may contain payloads intended for use at one or more stations and may be transmitted using beamforming or other physical layer techniques.
[0093] In some embodiments, the term "participating in CBF transmission" may refer to the role of an access point or station in transmitting, receiving, or acknowledging frames involved in a coordinated beamforming event. Participation may involve transmitting or responding to a CBF invitation frame, CBF response frame, CBF trigger frame, ICF, or ICR, transmitting a data unit, sending a control instruction regarding continuation in response to a trigger frame, or providing a BA in a TB PPDU.
[0094] In some embodiments, the term "station" may refer to a wireless client device that receives downlink transmissions, provides acknowledgments, or participates in trigger-based uplink transmissions during a CBF session. STAs may support features such as EMLSR (Enhanced Multi-Link Single Radio), dynamic power-saving operation, or multi-user reception, and may respond to BA requests initiated by APs or embedded triggers.
[0095] In some embodiments, the term "trigger frame" may refer to a frame transmitted by one access point to instruct another access point to perform a concurrent or subsequent CBF transmission. The trigger may specify timing, preamble information, BA method, or continuation information for the next CBF PPDU, and may appear as a standalone frame or be embedded within another protocol element (e.g., MU-BAR or TB PPDU).
[0096] In some embodiments, the term "next CBF transmission" may refer to any subsequent coordinated beamforming transmission performed after a previous transmission within a CBF session. Its occurrence may depend on continuation signaling exchanged between access points, service availability, station readiness, or negotiated session parameters.
[0097] In some embodiments, a trigger frame may be received within a short inter-frame interval (SIFS) after the transmission of a first frame (e.g., CBF-Continue). In some embodiments, a second data may be transmitted within the SIFS after the trigger frame is received. In some embodiments, the first frame may be transmitted within the SIFS after receiving a trigger-based physical layer protocol data unit (TB PPDU) with block acknowledgment (BA) from one or more STAs or a group of STAs associated with a second access point.
[0098] In some embodiments, the first frame may be embedded in a multi-user block acknowledgment request (MU-BAR) frame addressed to one or more STAs. In some embodiments, a trigger frame may be received within the SIFS after receiving a TB PPDU with a BA from one or more STAs or a group of STAs associated with the second access point. In some embodiments, the first frame may be embedded in the TB PPDU.
[0099] In some embodiments, the term "embedding a frame into another frame" may refer to placing CBF-related signaling (such as CBF-Continue messages, trigger indications, or other AP-to-AP coordination information) within a MU-BAR frame, a TB PPDU carrying a BA, or another MAC / PHY structure. Such embedding can reduce overhead or allow signaling to be transmitted concurrently to two stations and peer APs.
[0100] In some embodiments, the first access point (e.g., Figures 7A to 7E AP1 and AP2 in the diagram may include a network interface and one or more processors. One or more processors may exchange one or more frames with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions during the session. During the session, one or more processors may perform CBF transmissions of multiple data units to one or more stations (STAs) (e.g., STAs associated with the first access point) via the network interface using one or more parameters. During the session, in response to performing a CBF transmission of a first data unit, and in response to receiving a first frame indicating that the second access point can participate in the next CBF transmission, one or more processors may transmit a trigger frame and then perform a CBF transmission of a second data unit.
[0101] In some embodiments, a trigger frame may be transmitted within the SIFS after the first frame is received. In some embodiments, second data may be transmitted within the SIFS after the trigger frame is transmitted. In some embodiments, the first frame is received within the SIFS after a TB PPDU with a BA is received from one or more STAs or a group of STAs associated with the second access point.
[0102] In some embodiments, the first frame may be embedded in a MU-BAR frame addressed to one or more STAs associated with the second access point. In some embodiments, a trigger frame may be transmitted within the SIFS after receiving a TB PPDU with a BA from one or more STAs or a group of STAs associated with the second access point. In some embodiments, the first frame may be embedded in the TB PPDU.
[0103] Figure 8This is a flowchart illustrating an example process 800 for negotiating an extended CBF session using a two-way handshake, according to some embodiments. In some embodiments, process 800 may perform a CBF transmission during the session. In some embodiments, process 800 is executed by one or more processors (e.g., processor 121) of a device (e.g., device 102, network device 106, AP1 (201, 301, 401, 501, 601, 701, 721, 741, 761, 781), AP2 (202, 302, 402, 502, 602, 702, 722, 742, 762, 782), etc.). In other embodiments, process 800 is executed by other entities. In some embodiments, process 800 includes more than Figure 8 The steps shown in the document may be more, fewer, or different from those shown elsewhere.
[0104] At step 810, the first access point (e.g., one of AP1 201 and AP2 202) and the second access point (e.g., the other of AP1 201 and AP2 202) may exchange one or more frames with each other (e.g., Figure 2 Frames 211, 212, 213, 216, and 217 in the diagram are used to determine one or more parameters for performing CBF transmissions (e.g., CBF PPDUs 218 and 219) during a session. In some embodiments, the one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBF PPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed via the CBF transmission, the modulation and coding scheme (MCS) used for the STAs in the CBF transmission, the number of spatial streams used for the STAs in the CBF transmission, or at least one of a set of return-to-zero directions used by the AP in the CBF transmission. In some embodiments, the one or more parameters may be determined prior to the CBF transmission of multiple data units.
[0105] At step 820, the first access point (e.g., AP1 701) and the second access point (e.g., AP2 702) may concurrently perform CBF transmissions of a pair of first data units (e.g., CBF PPDU 1 (711), CBF PPDU 1 (712)) to one or more stations (STAs) (e.g., AP1-STA 703, AP2-STA 704) during the session using one or more parameters.
[0106] In some embodiments, the term "concurrently performing CBF transmission of a pair of data units" can refer to a scenario in which two access points transmit their respective data units at aligned times using pre-determined CBF parameters, such that the two transmissions occur in parallel while mitigating interference through coordinated beamforming. Concurrent transmissions can be repeated across multiple steps of a CBF session.
[0107] At step 830, in response to performing a CBF transmission of a pair of first data units, the first access point (e.g., AP1721) may transmit a first frame (e.g., CBF-Continue 736) indicating that the first access point is eligible to participate in the next CBF transmission. In some embodiments, the first frame (e.g., CBF-Continue 736) may be transmitted within SIFS after receiving a TB PPDU with a BA (e.g., TB PPDU with a BA 735) from one or more STAs (e.g., AP2-STA 724). In some embodiments, the first frame may be embedded in a MU-BAR frame (e.g., MUBAR+CBF-Continue 754) addressed to one or more STAs (e.g., AP-STA 744) associated with the first access point. In some embodiments, the first frame may be embedded in a TB PPDU (e.g., TB PPDU with CBF-Continue 775).
[0108] At step 840, in response to receiving the first frame (e.g., CBF-Continue 736), the second access point (AP2 722) may transmit a trigger frame (e.g., CBF-Trigger 737). In some embodiments, after transmitting the first frame (e.g., CBF-Continue 736), the trigger frame (e.g., CBF-Trigger 737) may be transmitted within the SIFS. In some embodiments, after receiving a TB PPDU with a BA (e.g., TB PPDU with a BA 755) from one or more STAs (e.g., AP2-STA 744), the trigger frame (e.g., CBF-Trigger 756) may be transmitted within the SIFS.
[0109] At step 850, in response to a trigger frame (e.g., CBF-trigger 756), the first access point and the second access point may concurrently perform a pair of second data units (e.g., CBF PPDU 2 (757, 758)) to one or more STAs during the session using one or more parameters.
[0110] 2. Session extension frame sequence negotiated using a three-way handshake
[0111] In some embodiments, within a CBF session, after each CBF transmission, the participating APs can negotiate whether the session will continue with the next CBF transmission. This negotiation can take the form of an intermediate three-way handshake, similar to the three-way AP handshake used during the initial setup phase prior to the first CBF transmission (e.g., as...). Figure 2 or Figure 3 The diagram illustrates CBF-invitation, CBF-response, and CBF-trigger. In this handshake, one AP may send an intermediate CBF-invitation message to another AP to indicate its ability to participate in the next CBF launch, for example, based on the service availability of its STA. The receiving AP may then send an intermediate CBF-response message, also taking into account its own service availability, indicating whether it can participate in the next CBF launch. Once the intermediate CBF-response confirms that the other AP is available to continue, the first AP may send an intermediate CBF-trigger to initiate the next coordinated launch from both APs.
[0112] In some embodiments, intermediate CBF-invitations, intermediate CBF-responses, and intermediate CBF-triggers may carry information similar to the corresponding CBF-invitations, CBF-responses, and CBF-triggers used in the initial setup phase prior to the first CBF transmission of the CBF session. However, in some embodiments, these intermediate frames may be shortened to reduce overhead. This reduction can be achieved by omitting certain information provided during the initial setup phase, such as a set of STAs for each AP to be addressed in the next CBF transmission, the MCS value of each STA, the NSS value of each STA, the GI+LTF parameters to be used in the next CBF transmission, whether each STA will use 2xLDPC, or the order of STAs in the CBF transmission; any information omitted from the intermediate three-way handshake can be inferred from the content initially signaled during the initial setup phase and therefore remains unchanged for subsequent CBF transmissions.
[0113] In some embodiments, there may be no ICF or ICR exchange between each AP and its STA between consecutive CBF transmissions within the same CBF session. In some cases, the lack of an intermediate CBF-invitation or intermediate CBF-response from an AP may indicate that the AP cannot continue participating in the CBF session. Intermediate CBF-invitation and intermediate CBF-response messages may be transmitted as separate frames or may be embedded in a CBF ACK sequence following a previous CBF transmission. For example, one of these intermediate messages may be embedded in a MU-BAR frame transmitted by an AP to its STA, allowing another AP to concurrently receive the continuation signal, or the message may be transmitted by the AP in a TB PPDU concurrently with a BA transmitted by a STA associated with another AP.
[0114] In some embodiments, when the intermediate CBF-invitation is transmitted as a separate frame rather than embedded within a CBF ACK sequence, the corresponding intermediate CBF-response may be transmitted in a separate frame at the SIFS following the intermediate CBF-invitation, and the intermediate CBF-trigger may be transmitted at the SIFS following the intermediate CBF-response. Similarly, when the intermediate CBF-response is transmitted as a separate frame rather than embedded within a CBF ACK sequence, the intermediate CBF-trigger may be transmitted at the SIFS following the intermediate CBF-response. When the intermediate CBF-response is embedded in a CBF ACK sequence, the intermediate CBF-trigger may alternatively be transmitted at the SIFS following the final frame in the CBF ACK sequence.
[0115] In some embodiments, APs may agree in advance (e.g., during initial negotiation) to postpone the CBF ACK sequence until multiple CBF transmissions within the CBF session have been completed. Such a postponed CBF ACK sequence may be used when any AP is unable to continue with additional CBF transmissions without receiving an ACK or BA from its STA, or when any AP has no further pending traffic. When using such a postponement, the AP may notify its respective STA that a single CBF ACK sequence will be used to acknowledge multiple CBF transmissions to each STA across the CBF session's MPDU. If any AP is unable to continue transmitting a CBF PPDU without first receiving an ACK or BA from its STA, it may indicate this condition within an intermediate CBF-invitation, intermediate CBF-response, or intermediate CBF-trigger sequence, thereby prompting the initiation of a CBF ACK sequence, such as CBF ACK frame sequence 600 (see CBF ACK frame sequence 600). Figure 6 ).
[0116] In some embodiments, APs may negotiate in advance which AP will transmit an intermediate CBF-invitation message after each CBF transmission, thus preventing AP conflicts by transmitting intermediate CBF-invitation messages simultaneously. In some embodiments, the negotiation of which AP will transmit the next intermediate CBF-invitation message may occur during a previous (initial or intermediate) CBF-invitation, CBF-response, or CBF-trigger. In some embodiments, the responsibility for transmitting an intermediate CBF-invitation may be assigned to the AP that initiated the CBF session and sent the first CBF-invitation during the initial setup phase, or consecutive CBF transmissions within the same CBF session may alternate between APs.
[0117] In some embodiments, to ensure media access protection, the duration field in the MAC header of frames transmitted during the initial setup phase (including CBF-trigger, ICF, ICR, CBF-response, or CBF-invitation) can be set to a value that protects the subsequent frame sequence by causing the receiving device to postpone media access by completing one or more CBF transmissions, corresponding CBF ACK sequences, intermediate CBF-invitations, intermediate CBF-responses, and intermediate CBF-triggers. When the AP agrees to extend the TXOP to accommodate a second CBF transmission, the duration field can be set in the intermediate CBF-invitation, intermediate CBF-response, or intermediate CBF-trigger to protect the second CBF transmission, corresponding CBF ACK sequence, any second intermediate CBF-invitation, any second intermediate CBF-response, and any second intermediate CBF-trigger. This method can be repeated before each subsequent CBF transmission within the session, so that frame exchange remains protected under the negotiated TXOP extension.
[0118] Figures 9A to 9D It is an instance frame sequence for using a three-way handshake to negotiate and extend a CBF session, according to some embodiments. Figure 9A The CBF session-extended frame sequence 900 is described, which employs an intermediate three-way handshake, such as intermediate CBF-invitation 916, intermediate CBF-response 917, and intermediate CBF-trigger 918, after a coordinated downlink (e.g., CBF PPDU 1 (911, 912)). AP1 901 and AP2 902 complete CBF PPDU 1 (911, 912) toward AP1 STA 903 and AP2 STA 904. After AP1-STA 903 sends TB PPDU 913 with BA, AP2 902 triggers SIFS interval BA using MU-BAR 914 and subsequent BA exchanges (e.g., TB PPDU 915 with BA). Subsequently, AP1 sends an intermediate CBF-invitation 916, and then AP2 sends an intermediate CBF-response 917, followed by an intermediate CBF-trigger 918 (from AP1) to start the next downlink at SIFS (CBF PPDU 2 (919, 920)).
[0119] Figure 9BDepicting a CBF session-extended frame sequence 920, where AP1 921 places or embeds an intermediate CBF-invitation within a TBPPDU (e.g., TB PPDU 935 with an intermediate CBF-invitation). AP1 921 and AP2 922 complete CBF PPDU 1 (931, 932) toward AP1 STA 923 and AP2 STA 924. After AP1-STA 923 sends TB PPDU 933 with a BA, AP2 922 triggers a SIFS interval BA using MU-BAR 934. Subsequently, AP1 921 concurrently sends an intermediate CBF-invitation 935 with a TB PPDU 936 with a BA transmitted from AP2-STA 924, and then AP2 issues an intermediate CBF-response 937, followed by an intermediate CBF-trigger 938 (from AP1) to begin the next downlink at SIFS (CBF PPDU 2 (939, 940)). In MU-BAR frame 934, AP2 may signal, indicate, or reserve space or frequency resources for subsequent AP1 allocation within the TB PPDU, so that AP1 may embed intermediate CBF-invitation messages in the TB PPDU (935).
[0120] Figure 9C Depicting a CBF session-extended frame sequence 940, where AP2 942 places or embeds an intermediate CBF-invitation within a MUBAR (e.g., MUBAR + intermediate CBF-invitation 954), and AP1 941 places or embeds an intermediate CBF-response within a TBPPDU (e.g., TB PPDU 955 with intermediate CBF-response). AP1 941 and AP2 942 complete CBF PPDU 1 (951, 952) toward AP1-STA 943 and AP2-STA 944. After AP1-STA 943 sends TB PPDU 953 with BA, AP2 942 triggers SIFS interval BA using MUBAR 954 with intermediate CBF-invitation. Subsequently, AP1 941 concurrently transmits TB PPDU 955 with an intermediate CBF-response embedded in it, along with TB PPDU 956 with BA transmitted from AP2-STA 944. Then, AP2 issues an intermediate CBF-trigger 957 to initiate the next downlink at SIFS (CBF PPDU 2 (958, 959)). In MU-BAR frame 954, AP2 may signal, indicate, or reserve space or frequency resource allocation for AP1 in subsequent TB PPDUs to allow AP1 to embed the intermediate CBF-response message in TB PPDU (955).
[0121] Figure 9DDepicting a CBF session – extended frame sequence 960, where AP1 961 and AP2 962 complete CBF PPDU 1 (971, 972) toward AP1-STA 963 and AP2-STA 964. After AP1-STA 963 and AP2-STA 964 concurrently transmit TB PPDU 973 with BA and TB PPDU 974 with BA, AP1 961 sends an intermediate CBF-invitation 975. Subsequently, AP2 962 sends an intermediate CBF-response 976, and then AP1 issues an intermediate CBF-trigger 977 to start the next downlink at SIFS (CBF PPDU 2 (978, 979)).
[0122] In some embodiments, the first access point (e.g., Figures 9A to 9D The AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may exchange one or more frames with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions during a session. During a session, one or more processors may perform multiple data unit (Data Unit) CBF transmissions to one or more stations (STAs) via the network interface using one or more parameters. During a session, in response to performing a CBF transmission of a first Data Unit, one or more processors may transmit a first frame indicating that the first access point can participate in the next CBF transmission during the session. In response to receiving a second frame indicating that the second access point can participate in the next CBF transmission during the session, one or more processors may transmit a trigger frame and then perform a CBF transmission of a second Data Unit.
[0123] In some embodiments, a second frame may be received within the SIFS after the first frame is transmitted. In some embodiments, a trigger frame may be transmitted within the SIFS after the second frame is received. In some embodiments, the first frame may be transmitted within the SIFS after receiving a TB PPDU with a BA from one or more STAs associated with the second access point. In some embodiments, the first frame may be transmitted within the SIFS after receiving a TB PPDU with a BA from one or more STAs associated with the first access point.
[0124] In some embodiments, the first frame may be embedded in a TB PPDU. In some embodiments, the first frame may be embedded in a MU-BAR frame addressed to one or more STAs. In some embodiments, the second frame may be embedded in a TB PPDU.
[0125] In some embodiments, the first access point (e.g., Figures 9A to 9DThe AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may exchange one or more frames with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions during a session. During a session, one or more processors may perform multiple data unit (Data Unit) CBF transmissions to one or more stations (STAs) via the network interface using one or more parameters. During a session, in response to performing a CBF transmission of a first Data Unit, and in response to receiving a first frame (e.g., CBF-invitation) indicating that the second access point can participate in the next CBF transmission during the session, one or more processors may transmit a second frame (e.g., CBF-response) indicating that the first access point can participate in the next CBF transmission. In response to receiving a trigger frame (e.g., CBF-trigger), one or more processors may perform a CBF transmission of a second Data Unit during the session.
[0126] In some embodiments, a second frame may be transmitted within the SIFS after the first frame is received. In some embodiments, a trigger frame may be received within the Short Interframe Space (SIFS) after the second frame is transmitted. In some embodiments, the first frame may be received within the SIFS after receiving a TB PPDU with a BA from one or more STAs.
[0127] In some embodiments, the first frame may be embedded in a TB PPDU. In some embodiments, the first frame may be embedded in a MU-BAR frame addressing one or more STAs associated with the second access point. In some embodiments, the second frame may be embedded in a TB PPDU.
[0128] Figure 10 This is a flowchart illustrating an example process 1000 for negotiating an extended CBF session using a three-way handshake, according to some embodiments. In some embodiments, process 1000 may perform coordinated beamforming (CBF) transmission during the session. In some embodiments, process 1000 is executed by one or more processors (e.g., processor 121) of a device (e.g., device 102, network device 106, AP1 (201, 301, 901, 921, 941, 961), AP2 (302, 302, 902, 922, 942, 962), etc.). In other embodiments, process 1000 is executed by other entities. In some embodiments, process 1000 includes more than Figure 10 The steps shown in the document may be more, fewer, or different from those shown elsewhere.
[0129] At step 1010, the first access point (e.g., one of AP1 201 and AP2 202) and the second access point (e.g., the other of AP1 201 and AP2 202) may exchange one or more frames with each other (e.g., Figure 3Frames 211, 212, 213, 215, and 217 in the diagram are used to determine one or more parameters for performing CBF transmissions (e.g., CBF PPDUs 218 and 219) during a session. In some embodiments, the one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBF PPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed via the CBF transmission, the modulation and coding scheme (MCS) used for the STAs in the CBF transmission, the number of spatial streams used for the STAs in the CBF transmission, or at least one of a set of return-to-zero directions used by the AP in the CBF transmission. In some embodiments, the one or more parameters may be determined prior to the CBF transmission of multiple data units.
[0130] At step 1020, the first access point (e.g., AP1 901) and the second access point (e.g., AP2 902) may concurrently perform CBF transmissions of a pair of first data units (e.g., CBF PPDU 1 (911, 912)) to one or more stations (STAs) (e.g., AP1-STA 903, AP2-STA 904) during the session using one or more parameters.
[0131] At step 1030, in response to performing a CBF transmission of a pair of first data units, a first access point (e.g., AP1901) may transmit a first frame (e.g., intermediate CBF-invitation 916) indicating that the first access point is eligible to participate in the next CBF transmission. In some embodiments, the first frame may be transmitted within the SIFS after receiving a TB PPDU with a BA (e.g., TB-PPDU 915 with a BA) from one or more STAs (e.g., AP2-STA 904). In some embodiments, the first frame is embedded in a TB PPDU (e.g., TB PPDU 935 with an intermediate CBF-invitation embedded). In some embodiments, the first frame is embedded in a MU-BAR frame (e.g., MUBAR 954 with an intermediate CBF-invitation embedded) addressed to one or more STAs (e.g., AP2-STA 944) associated with the first access point.
[0132] At step 1040, in response to receiving the first frame, the second access point may transmit a second frame (e.g., an intermediate CBF-response 917) indicating that the second access point (e.g., AP2 902) is eligible to participate in the next CBF transmission (e.g., CBF PPDU 2 920). In some embodiments, the second frame may be transmitted within the SIFS after the first frame is transmitted. The second frame may be embedded in a TBPPDU (e.g., a TB PPDU 955 embedded with an intermediate CBF-response).
[0133] At step 1050, in response to receiving the second frame, the first access point (e.g., AP1 901) may transmit a trigger frame (e.g., intermediate CBF-trigger 918).
[0134] At step 1060, in response to the trigger frame, the first access point and the second access point may concurrently perform CBF transmissions of a pair of second data units (e.g., CBF PPDU 2 (919, 920)) to one or more STAs (e.g., AP1-STA 903, AP2-STA 904) during the session using one or more parameters.
[0135] 3. Session-extended frame sequence by negotiating the number of CBF transmissions.
[0136] In some embodiments, during CBF session extension, participating APs may negotiate in advance the number of future (or additional) CBF transmissions that the APs will jointly perform within the session, denoted as N (e.g., a positive integer N), under the condition that the MCS and Nss values of each AP's set of participating STAs and the corresponding MCS and Nss values for each STA remain unchanged across these transmissions. This negotiated value N defines the structure of the upcoming coordinated beamforming activity and ensures that the CBF session is conducted with a consistent set of transmission parameters for all involved STAs.
[0137] In some embodiments, the negotiation of the value N can occur during the CBF setup phase prior to the first (initial) CBF launch in the session. During this CBF setup phase, the initiating AP can indicate its proposed number of CBF launches in a CBF-Invite or CBF-Trigger, or both. The responding AP can similarly indicate its proposed number of CBF launches in a CBF-Response. The final value of N for the session can be determined as the minimum of the two proposed values, thereby allowing both APs to participate without exceeding their respective service availability or capacity constraints.
[0138] In some embodiments, once negotiation is complete, the AP may proceed with N consecutive CBF transmissions (e.g., N CBF transmissions in a session, or the first CBF transmission in a session followed by N CBF transmissions). Each subsequent CBF transmission after the first CBF transmission may be preceded by a compressed CBF setup phase, such as a CBF setup phase involving only CBF-trigger frames similar to those used in the initial setup phase, or each subsequent CBF transmission may occur without any prior CBF setup phase. Parameters affecting subsequent CBF transmissions (including the participating STAs of any AP, the MCS of each STA, and / or the Nss value of each STA) may be established during the initial setup phase prior to the first transmission and may remain constant over the duration of the N transmissions.
[0139] In some embodiments, a CBF ACK sequence may follow each of the N transmissions to acknowledge the MPDU transmitted in the previous CBF transmission. Alternatively, the AP may agree in advance to postpone the CBF ACK sequence until all N transmissions are completed and may notify its STA of this arrangement. When such a postponement is used, a single final CBF ACK sequence can acknowledge the MPDU transmitted across all N CBF transmissions, thereby reducing the overhead associated with duplicate acknowledgment exchanges.
[0140] In some embodiments, there may be no ICF or ICR exchange between the AP and its STA during the interval between consecutive CBF transmissions. This omission reduces intermediate signaling and relies on the fact that the participating STAs and their corresponding transmission parameters have been negotiated and fixed for the entire sequence of N transmissions.
[0141] In some embodiments, the duration field in the MAC header of one or more frames (including one or more of CBF-Trigger, ICF, ICR, CBF-Response, and / or CBF-Invitation frames) transmitted during the initial setup phase can be set to a value that protects the subsequent coordinated frame sequence by causing the receiving device to postpone media access. This protection extends to all upcoming N CBF transmissions and the final CBF ACK sequence. When the AP agrees to extend the TXOP to support the complete sequence of N transmissions, the duration field can be configured accordingly so that each of the protected transmission and acknowledgment sequences can occur without interruption. If necessary, this same approach can be repeated before each subsequent CBF transmission to continue coordination and media protection.
[0142] Figure 11 This is a flowchart illustrating an example process 1100 for extending a CBF session by negotiating the number of CBF transmissions, according to some embodiments. In some embodiments, process 1100 may perform coordinated beamforming (CBF) transmissions during the session. In some embodiments, process 1100 is executed by one or more processors (e.g., processor 121) of a device (e.g., device 102, network device 106, AP1 (201, 301), AP2 (202, 302), etc.). In other embodiments, process 1100 is executed by other entities. In some embodiments, process 1100 includes more than Figure 11 The steps shown in the document may be more, fewer, or different from those shown elsewhere.
[0143] At step 1110, the first access point (e.g., one of AP1 201 and AP2 202) and the second access point (e.g., the other of AP1 201 and AP2 202) may exchange one or more frames with each other (e.g., Figure 2Frames 211, 212, 213, 215, and 217 in the diagram are used to determine one or more parameters for performing CBF transmissions (e.g., CBF PPDUs 218 and 219) during a session, and the number of CBF transmissions during the session (e.g., a non-negative integer N). In some embodiments, one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBF PPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed by the CBF transmission, the modulation and coding scheme (MCS) used for the STAs in the CBF transmission, the number of spatial streams used for the STAs in the CBF transmission, or at least one of a set of return-to-zero directions used by the AP in the CBF transmission.
[0144] In some embodiments, the term "number of CBF transmissions during a session" may refer to the number of coordinated transmissions that two or more access points agree to perform within a CBF session. This number may be explicitly negotiated, inferred from exchanged indicators, or dynamically reduced depending on service or capacity constraints.
[0145] At step 1120, during the session, the first access point (e.g., AP1 301) and the second access point (e.g., AP2 302) may concurrently perform multiple pairs of data units to one or more stations (STAs) CBF transmissions (e.g., (N+1) CBF transmissions) using one or more parameters depending on the number of CBF transmissions.
[0146] In some embodiments, one or more parameters may be determined prior to the CBF transmission of multiple pairs of data units. The multiple pairs of data units may include a first pair of data units and N additional pairs of data units. The CBF transmission of the multiple pairs of data units may include a first CBF transmission of the first pair of data units, followed by N additional CBF transmissions of the corresponding N pairs of additional data units.
[0147] In some embodiments, multiple pairs of data units spanning the first CBF transmission and N additional CBF transmissions can be acknowledged via a single acknowledgment sequence, which is deferred until after the N additional CBF transmissions are completed. The single acknowledgment sequence may include one or more MU BARs (e.g., MU BARs 514, 613, 615) and one or more TB PPDUs carrying a BA (e.g., TB PPDUs 513, 515, 615, 616 with a BA). The single acknowledgment sequence acknowledges one or more data units transmitted to each STA via the N additional CBF transmissions.
[0148] In some embodiments, the term "acknowledgment sequence" may refer to a series of transmissions involving MU-BAR, TBPPDU carrying BA, or other acknowledgment-related frames, which together indicate which data units in a previous CBF transmission have been successfully received by the station. Such an acknowledgment sequence may occur after each CBF transmission or may be delayed to cover multiple transmissions.
[0149] In some embodiments, the term "single acknowledgment sequence" may refer to an acknowledgment phase covering multiple CBF transmissions within a session, such that acknowledgment frames are deferred until a set of transmissions is completed. This sequence may include one or more MU-BARs and one or more TB PPDUs carrying BAs, and may provide feedback for multiple data units transmitted across several CBF PPDUs.
[0150] In some embodiments, between consecutive CBF transmissions in N additional CBF transmissions, at least one of the first or second access points may not perform an Initial Control Frame / Initial Control Response (ICF / ICR) exchange with one or more STAs. In some embodiments, each CBF transmission in N additional CBF transmissions may be preceded by an intermediate CBF-trigger transmitted by the first or second access point. In some embodiments, the intermediate CBF trigger may communicate the duration or length of the upcoming CBF transmission.
[0151] In some embodiments, the first access point (e.g., Figure 2 or Figure 3 The AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may exchange one or more frames with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions during a session, and the number of CBF transmissions during the session. During the session, one or more processors may perform multiple data unit (Data Unit) CBF transmissions to one or more stations (STAs) via the network interface using one or more parameters, depending on the number of CBF transmissions.
[0152] In some embodiments, one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBFPPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed via the CBF transmission, the modulation and coding scheme (MCS) used for the STAs in the CBF transmission, the number of spatial streams used for the STAs in the CBF transmission, or at least one of a set of return-to-zero directions used by the AP in the CBF transmission. In some embodiments, one or more parameters may be determined prior to the CBF transmission of multiple data units.
[0153] In some embodiments, the number of CBF transmissions can be N, where N is a non-negative integer. For example, for N=0, zero additional data units are transmitted after the first data unit. Multiple data units may comprise the first data unit and N additional data units. CBF transmissions of multiple data units may comprise a first CBF transmission of the first data unit, followed by N additional CBF transmissions of the corresponding N additional data units. Multiple data units spanning the first CBF transmission and the N additional CBF transmissions can be acknowledged via a single acknowledgment sequence, which is deferred until after the N additional CBF transmissions are completed. The single acknowledgment sequence may comprise at least one of one or more MU BARs or one or more TB PPDUs carrying a BA. The single acknowledgment sequence acknowledges one or more data units transmitted to each STA via the N additional CBF transmissions. In some embodiments, an ACK sequence may exist after M (<=N+1) CBF transmissions (M is a positive integer).
[0154] In some embodiments, between consecutive CBF transmissions in N additional CBF transmissions, one or more processors may not perform Initial Control Frame / Initial Control Response (ICF / ICR) exchange with one or more STAs. In some embodiments, one or more processors may transmit or receive an intermediate CBF trigger before each of the N additional CBF transmissions. In some embodiments, each intermediate CBF trigger may communicate the duration or length of the upcoming CBF transmission.
[0155] In some embodiments, the first access point (e.g., Figure 2 or Figure 3 The AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may transmit a first frame indicating a first non-negative integer to a second access point via the network interface. One or more processors may receive a second frame indicating a second non-negative integer from the second access point via the network interface. One or more processors may determine the minimum of a first positive integer and a second positive integer as the number of coordinated beamforming (CBF) transmissions performed during a session. For example, for N=0, zero additional data units are transmitted after the first data unit. In response to determining that the number of CBF transmissions is a positive integer, one or more processors may perform multiple data unit CBF transmissions to one or more stations (STAs) via the network interface during a session, based on the number of CBF transmissions.
[0156] In some embodiments, one or more parameters may be determined before the CBF transmission of multiple data units.
[0157] In some embodiments, the number of CBF transmissions can be N, where N is a non-negative integer. For example, for N=0, zero additional data units are transmitted after the first data unit. Multiple data units can comprise the first data unit and N additional data units. CBF transmissions of multiple data units can comprise a first CBF transmission of the first data unit, followed by N additional CBF transmissions for the corresponding N additional data units.
[0158] In some embodiments, multiple data units transmitted across the first CBF transmission and N additional CBF transmissions can be acknowledged via a single acknowledgment sequence, which is deferred until after the N additional CBF transmissions are completed. The single acknowledgment sequence may include at least one of one or more MU BARs or one or more TB PPDUs carrying a BA. The single acknowledgment sequence acknowledges one or more data units transmitted to each STA via the N additional CBF transmissions. In some embodiments, an ACK sequence may exist after M (<=N+1) CBF transmissions (M being a positive integer).
[0159] In some embodiments, between consecutive CBF transmissions in N additional CBF transmissions, one or more processors may not perform ICF / ICR exchange with one or more STAs. In some embodiments, one or more processors may transmit or receive an intermediate CBF trigger before each of the N additional CBF transmissions. In some embodiments, each intermediate CBF trigger may communicate the duration or length of the upcoming CBF transmission.
[0160] 4. Session extended frame sequence triggered by alternating transmission of trigger frames via AP
[0161] In some embodiments, during CBF session extension, each CBF transmission in the CBF session may be preceded by an AP (e.g., Figure 2The responsibility for issuing CBF-triggers can be alternated between APs, such that, for example, one AP issues the first, third, and fifth CBF-triggers in a session, while another AP issues the second, fourth, and sixth CBF-triggers. This alternation pattern can provide a structured sequence in which each AP, when acting as the issuer of a CBF-trigger, indicates a number extracted from a set of values (e.g., {0, 1, 2}) in the CBF-trigger, which specifies the number of future CBF-launches (or remaining CBF-launches in the session) that the AP can participate in based on its service availability or other relevant constraints. For example, when the number is zero, the CBF-trigger may indicate that the CBF session terminates immediately after the CBF-trigger; when the number is 1, the CBF-trigger may indicate that the CBF-launch following the current CBF-trigger becomes the last CBF-launch in the session; and when the number is 2, the CBF-trigger may indicate that after the CBF-launch following the current CBF-trigger has been completed, another AP becomes responsible for issuing the next CBF-trigger.
[0162] In some embodiments, when the number is 2, the first AP can perform two CBF transmissions, and may be able to perform more CBF transmissions after that. In some embodiments, when the number is 2, the first AP may initially not know that it can support more than two transmissions, but it may be able to make this determination at a future time (e.g., after the second CBF transmission). In some embodiments, after the first CBF transmission, the second AP transmits an indication of supporting the triggering of the second and third CBF transmissions. After the second transmission (supported by two APs), it is the first AP's turn to transmit a trigger. If the first AP has now determined that it can also support the third transmission, then it can transmit an indication of CBF triggering supporting the third (and possibly more) transmissions, thus continuing the chain. Otherwise, the first AP will transmit a trigger indicating that it cannot continue, and thus terminate the session.
[0163] In some embodiments, the CBF-trigger can be transmitted as a standalone frame, in which case the next CBF transmission may occur at SIFS following the CBF-trigger frame. Alternatively, the CBF-trigger can be embedded within a CBFACK sequence associated with a previous CBF transmission. In this case, the CBF-trigger may be embedded within a MU-BAR frame transmitted by an AP to its STA, such that another AP is concurrently notified, or it may be transmitted along with a TB BA from a STA associated with another AP. These embedding options allow the CBF-trigger to function as both an acknowledgment sequence element and an inter-AP coordination signal.
[0164] In some embodiments, the AP may negotiate an arrangement to postpone the CBF ACK sequence until multiple CBF transmissions within the session have been completed. When negotiating a postponed CBF ACK sequence, the CBF ACK sequence may be postponed until at least one of the APs is unable to continue a CBF transmission without receiving an ACK or BA from its STA, or when an AP has no remaining pending traffic. When this approach is adopted, the AP may notify its corresponding STA that a single CBF ACK sequence will be used to acknowledge data MPDUs transmitted via multiple CBF transmissions within the session. If the AP becomes unable to continue further CBF transmissions until receiving an ACK or BA from its STA, it may communicate this constraint in its CBF-trigger, thereby prompting the initiation of the CBF ACK sequence, for example... Figures 4 to 6 The CBF ACK frame sequence shown in the image is 400, 500, and 600.
[0165] In some embodiments, during the interval between consecutive CBF transmissions within the same CBF session, there may be no ICF or ICR exchange between each AP and its corresponding STA. This lack of intermediate AP-STA control signaling is possible because coordination between APs is maintained through alternating CBF-trigger frames and the information they convey about each AP's ability to continue participating in the session.
[0166] In some embodiments, the duration field in the MAC header of one or more frames (including CBF-trigger, ICF, ICR, CBF-response, or CBF-invitation) transmitted during the initial setup phase can be configured to protect the subsequent frame sequence by causing the receiver to postpone media access until one or more upcoming CBF transmissions, the associated CBF ACK sequence (if present), and the completion of the next CBF-trigger. When the AP agrees to extend the TXOP to include a second CBF transmission, the duration field in the second CBF-trigger can be set to protect the second CBF transmission, the associated CBF ACK sequence, and any subsequent CBF-triggers that may follow. This same protection mechanism can be repeated before each subsequent CBF transmission to ensure continuous media retention throughout the session.
[0167] Figure 12This is a flowchart illustrating an example process 1200 for extending a CBF session by alternately transmitting trigger frames via an access point (AP) according to some embodiments. In some embodiments, process 1200 may perform coordinated beamforming (CBF) transmission during the session. In some embodiments, process 1200 is executed by one or more processors (e.g., processor 121) of a device (e.g., device 102, network device 106, AP1 (201, 301), AP2 (202, 302), etc.). In other embodiments, process 1200 is executed by other entities. In some embodiments, process 1200 includes more than Figure 12 The steps shown in the document may be more, fewer, or different from those shown elsewhere.
[0168] At step 1210, the first access point (e.g., one of AP1 201 and AP2 202) and the second access point (e.g., the other of AP1 201 and AP2 202) may exchange one or more frames with each other (e.g., Figure 2 Frames 211, 212, 213, 215, and 217 in the diagram are used to determine one or more parameters for performing a CBF transmission (e.g., CBF PPDU 218, 219) in a session. In some embodiments, one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBF PPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed by the CBF transmission, the MCS used for the STAs in the CBF transmission, the number of spatial streams used for the STAs in the CBF transmission, or at least one of a set of return-to-zero directions used by the access points in the CBF transmission.
[0169] At step 1220, the first access point may transmit a first trigger frame, and the second access point may transmit a second trigger frame. In some embodiments, the first and second trigger frames may be transmitted alternately. In some embodiments, the term "two access points alternately transmitting trigger frames" may describe a coordinated mode in which the APs take turns sending triggers to initiate the next aligned CBF transmission. This alternation may continue through multiple transmissions and may reflect negotiations regarding remaining capacity or willingness to participate.
[0170] In step 1230, in response to either the first trigger frame or the second trigger frame, the first access point and the second access point may concurrently perform a CBF transmission of a pair of data units to one or more stations (STAs) during the session using one or more parameters. In some embodiments, the pair of data units may be transmitted within the SIFS after the transmission of the first trigger frame or the second trigger frame. In some embodiments, one or more parameters may be determined before the CBF transmission of the pair of data units.
[0171] In some embodiments, during a session, multiple data units comprising a pair of data units can be acknowledged via an acknowledgment sequence, which is deferred until after the CBF transmission of the multiple data units is complete. In some embodiments, an ACK sequence may exist after each CBF transmission. The acknowledgment sequence may contain at least one of one or more MU BARs or one or more TB PPDUs carrying a BA.
[0172] In some embodiments, at least one of the first trigger frame or the second trigger frame may be embedded in an acknowledgment sequence following a previous CBF transmission of the data unit. The acknowledgment sequence may include at least one of one or more MU BARs or one or more TBPPDUs carrying a BA.
[0173] In some embodiments, during a session, between consecutive CBF transmissions in a plurality of data units comprising a pair of data units, one or more processors may not perform ICF / ICR exchanges with one or more STAs.
[0174] In some embodiments, the first access point (e.g., Figure 2 or Figure 3 The AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may exchange one or more frames with a second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmissions during a session, and a first order in which the first and second access points transmit trigger frames for the next CBF transmission. One or more processors may transmit a first trigger frame via the network interface according to the first order, and then perform a first data unit to one or more stations (STAs) CBF transmission using one or more parameters during the session. In response to receiving a second trigger frame from the second access point according to the first order, one or more processors may perform a second data unit to one or more STAs CBF transmission using one or more parameters during the session. In some embodiments, in the first order, the first and second access points may alternately transmit trigger frames for the next CBF transmission.
[0175] In some embodiments, the first data unit may be transmitted within the SIFS after the transmission of the first trigger frame. In some embodiments, one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBF PPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed via the CBF transmission, the MCS used for the STA in the CBF transmission, the number of spatial streams used for the STA in the CBF transmission, or at least one of a set of return-to-zero directions used by the access points in the CBF transmission. In some embodiments, one or more parameters may be determined before the CBF transmission of the first data unit and the second data unit.
[0176] In some embodiments, during a session, multiple data units including a first data unit and a second data unit can be acknowledged via an acknowledgment sequence, which is postponed until after the CBF transmission of the multiple data units is completed. The acknowledgment sequence may include at least one of one or more MU BARs or one or more TB PPDUs carrying a BA.
[0177] In some embodiments, at least one of the first trigger frame or the second trigger frame may be embedded within an acknowledgment sequence following a previous CBF transmission of the data unit. The acknowledgment sequence may include at least one of one or more MU BARs or one or more TBPPDUs carrying a BA.
[0178] In some embodiments, during a session, between consecutive CBF transmissions in a plurality of data units including a first data unit and a second data unit, one or more processors may not perform ICF / ICR exchanges with one or more STAs.
[0179] In some embodiments, the first access point (e.g., Figure 2 or Figure 3 The AP1 and AP2 shown may include a network interface and one or more processors. One or more processors may exchange one or more frames with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming (CBF) transmission during a session. One or more processors may transmit a first message via the network interface indicating a first number of remaining CBF transmissions that the first access point can participate in, and based on the first number of remaining CBF transmissions, determine whether to perform CBF transmission of a first data unit using one or more parameters during the session. One or more processors may receive a second message via the network interface indicating a second number of remaining CBF transmissions that the second access point can participate in, and based on the second number of remaining CBF transmissions, determine whether to perform CBF transmission of a second data unit using one or more parameters during the session. In some embodiments, the first message may be carried in a first trigger frame, and the second message may be carried in a second trigger frame.
[0180] In some embodiments, the term "remaining CBF transmission" may refer to the number of future coordinated beamforming transmissions that an access point is still able or willing to perform during the current session. This information may be included in the trigger frame or other signaling and may guide whether the session continues or terminates after the current transmission.
[0181] In some embodiments, one or more processors may select a value from a first value, a second value, or a third value as the first number. The first value may indicate that the session terminates after the first trigger frame. The second value may indicate that only a single CBF transmission occurs after the first trigger frame. The session may terminate after a single CBF transmission. The third value may indicate that a CBF transmission occurs after the first trigger frame, and the second access point may transmit the next trigger after the CBF transmission following the first trigger frame.
[0182] In some embodiments, one or more parameters may include the duration and / or length of the CBF transmission / PPDU, one or more preamble contents of the CBFPPDU, a set of access points participating in the CBF transmission during the session, a set of STAs addressed by the CBF transmission, the MCS used for the STA in the CBF transmission, the number of spatial streams used for the STA in the CBF transmission, or at least one of a set of zeroing directions used by the access points in the CBF transmission.
[0183] In some embodiments, during a session, multiple data units can be acknowledged via an acknowledgment sequence that is deferred until after the CBF transmission of the multiple data units is complete. The acknowledgment sequence may include at least one of one or more MU BARs or one or more TB PPDUs carrying BAs.
[0184] In some embodiments, at least one of the first trigger frame or the second trigger frame may be embedded within an acknowledgment sequence following a previous CBF transmission of the data unit. The acknowledgment sequence may include one or more MU BARs or one or more TBPPDUs carrying a BA.
[0185] In some embodiments, during a session, between consecutive CBF transmissions in a plurality of data units including a first data unit and a second data unit, one or more processors may not perform ICF / ICR exchanges with one or more STAs.
[0186] 5. Multi-AP CBF mechanism (with shared APs and APs via shared access)
[0187] 5-1. CBF Frame Sequence
[0188] Figure 13 It is an instance frame sequence 1300 between shared AP 1301 and shared AP 1302 during CBF transmission according to some embodiments. Figure 13The diagram depicts coordinated beamforming switching within a shared TXOP 1305 involving shared AP 1301, via shared AP 1302, and their associated client stations STA11303 and STA2 1304. In frame sequence 1300, shared AP 1301 and via shared AP 1302 coordinate with their respective stations STA11303 and STA2 1304 prior to the coordinated beamforming downlink (e.g., DL PPDUs 1318, 1319). In this sequence, the shared AP initiates a CBF-invitation 1311, and the shared AP responds with a CBF-response 1312 at the SIFS time following the end of the CBF-invitation. AP-STA readiness is established via ICF 1313 and ICR 1314 exchanges between shared AP / STA1 and via ICF 1315 and ICR 1316 exchanges between shared AP / STA2. Following these handshakes, the sharing AP transmits a CBF-trigger 1317 to the transit AP after the SIFS timing, providing alignment information for subsequent synchronization transmissions. Subsequently, after the SIFS timing, both APs execute their coordinated downlink physical layer protocol data units (CBF PPDUs) 1318 and 1319. After the CBF PPDU, the sharing AP transmits a MU-BAR 1320 and receives a BA 1321. After another SIFS, the transit AP transmits its MU-BAR 1322 and then receives a BA 1323.
[0189] In some embodiments, the term "shared AP" may refer to an access point that initiates or coordinates certain aspects of a multi-AP communication process, including, but not limited to, generating, transmitting, or scheduling specific frames associated with a coordinated beamforming session. For example, a shared AP may primarily be a holder of a TXOP, such as an AP that has won channel access to initiate a CBF transmission. In some embodiments, the shared-shared AP role may be interchanged solely based on who gains channel access. In various embodiments, a shared AP may participate in determining which client devices are addressed in a coordinated transmission, may initiate one or more trigger frames for alignment or management of joint transmissions, or may otherwise provide signaling that enables additional access points to determine how and when to engage in a coordinated exchange. A shared AP may assume responsibility for managing the progress of a multi-AP session, such as indicating whether a subsequent transmission is expected, whether an acknowledgment should be triggered in a specific format, or whether additional coordination steps are required. Depending on system design and operating conditions, the entity acting as a shared AP may vary across sessions or even individual transmissions, and the role is not limited to a specific hardware configuration or network topology.
[0190] In some embodiments, the term "shared AP" can refer to an access point that collaborates with a shared AP during a coordinated transmission process and uses information conveyed by the shared AP to prepare its own corresponding transmission or response. In some embodiments, a shared AP can interpret signaling that identifies the timing of a coordinated beamforming exchange, acknowledges expected or continuation parameters. A shared AP can transmit its own trigger frames, acknowledgments, or control information based on instructions received, and can similarly convey whether it can or is willing to continue participating in an ongoing coordinated session. A shared AP can also manage interactions with its associated client devices during a coordinated exchange, including receiving or requesting acknowledgments or other uplink responses. Like a shared AP, the role of a shared AP is not limited to any particular device type or architecture, and different access points can assume the role of a shared AP under different network conditions or session structures.
[0191] refer to Figure 13 CBF frame sequence 1300 reflects a method in which sequential ACKs from clients of the shared AP and clients via the shared AP are used to complete the acknowledgment phase of each coordinated transmission. This sequence is widely supported because it maintains compatibility with baseline behavior while allowing efficient coordination between the shared AP and clients via the shared AP during CBF switching. In some arrangements / implementations, the first MU-BAR 1320 transmitted by the shared AP 1301 may be embedded within a previous downlink PPDU, consistent with baseline implementations that incorporate BA triggering information directly into the DL PPDU.
[0192] In some embodiments, the shared AP may be instructed on which method it will use to obtain the BA from its addressed CBF client. For example, it may be indicated whether the shared AP intends to transmit a separate MU-BAR or embed the MU-BAR information in a previous DL PPDU. This distinction can affect how the shared AP interprets the L-SIG duration and UL length fields and determine when the shared AP should transmit its own MU-BAR to its client. It can also affect whether the duration of the acknowledgment process in the shared AP BSS needs to be indicated separately or can be inferred by the shared AP itself.
[0193] In some embodiments, it can be determined whether to continue the TXOP after receiving a BA transmitted by a client via a shared AP. Because it is expected that multiple consecutive CBF PPDUs will be transmitted in the TXOP via coordinated beamforming, the shared AP and the AP via it can determine whether another CBF PPDU will follow the BA sequence and coordinate whether to continue the CBF session. Appropriate signaling of the continuation intention ensures that both APs act in unison in issuing or avoiding issuing subsequent CBF triggers.
[0194] In some embodiments, extended timeout handling for both the shared AP and CBF clients addressed via the shared AP can be determined. CBF clients operating in EMLSR or DPS mode may remain in extended listening state while waiting for a potential next CBF PPDU. In the absence of explicit indication of whether another transmission will follow, these clients may consume unnecessary power or remain unavailable for other channel access opportunities. By appropriately communicating whether the CBF session will continue or terminate, for example through embedded triggers or MU-BAR public / special user information fields, clients can more effectively manage their extended timeout behavior and align their power-saving state transitions with the actual boundaries of the CBF session.
[0195] 5-2. MU-BAR information transmitted by the shared AP
[0196] In some embodiments, within the context of coordinated beamforming, a shared AP may employ two different methods to transmit MU-BAR information and initiate a BA corresponding to a given CBF PPDU from its addressed CBF client. The shared AP may transmit a separate MU-BAR at the SIFS after the CBF PPDU is completed, or it may embed the MU-BAR information directly within the CBF PPDU it transmits to its client. Because these methods differ in timing and the clues available to peer APs, the shared AP may need to know in advance which method it intends to use.
[0197] In some embodiments, when the MU-BAR is transmitted independently, the shared AP can determine the expected MU-BAR timing based on the UL_length contained in the MU-BAR and the L-SIG of the BA transmitted by a client of the shared AP. When the MU-BAR information is alternatively embedded in the downlink PPDU, the shared AP can infer the corresponding timing solely from the L-SIG of the BA transmitted by a client of the shared AP, unless the embedding method is additionally indicated in the associated CBF-trigger. This distinction can affect how the shared AP schedules its own MU-BAR transmissions, as it may need to transmit its MU-BAR from a client of the shared AP at the SIFS following the BA, and may need to ensure that this timing aligns with the shared AP's selected BA triggering method.
[0198] In some embodiments, the shared AP may need to determine whether the CBF PPDU associated with the MU-BAR is the final CBF PPDU that the shared AP intends to transmit in the current TXOP. Using this knowledge, the shared AP can manage the extended timeout behavior of its associated CBF clients and decide how to continue transmissions on its other links. If the shared AP does not plan for additional CBF PPDUs, then the shared AP may need to initiate steps to terminate the extended timeout state and reallocate channel access for other transmissions.
[0199] For these reasons, the shared AP can provide an explicit indication of the method it will use to acquire the BA for each CBF PPDU, specifying whether the MU-BAR information is embedded in the CBF PPDU or transmitted as a separate MU-BAR. To maintain flexibility, this indication does not need to be part of any negotiation in the CBF setup or the initial handshake in the CBF TXOP. Instead, the indication can form part of a CBF-trigger corresponding to the CBF PPDU, such that the shared AP is notified of the BA acquisition method to be used for subsequent CBF PPDUs. Therefore, the CBF-trigger may contain a BA method field for the shared AP, which is set to zero when acquiring the ACK using a separate MU-BAR and set to 1 when acquiring the ACK using an embedded trigger in the CBF PPDU.
[0200] 5-3. Continuing with TXOP
[0201] In some embodiments, the initial handshake exchanged between the AP and its associated CBF client during a CBF TXOP may introduce non-negligible overhead, making it desirable to allow the transmission of multiple CBF PPDUs within the same CBF TXOP, rather than restarting the setup process for each PPDU. To support this, it can be assumed that the shared AP and a set of CBF clients via the shared AP, along with their corresponding transmission parameters, remain constant throughout the duration of the CBF TXOP (or the entire session). Under this assumption, the parameters exchanged and calculated for the first CBF PPDU can continue to be applied to all subsequent CBF PPDUs occurring within the same TXOP (or the same session). The only parameter that may vary across these PPDUs is the duration of the CBF PPDU itself, represented by its L-SIG length, which may differ from one PPDU to the next. Since the participating AP relies on previously established parameters, subsequent CBF PPDUs do not require additional rounds of CBF-invite and CBF-response exchanges or ICF / ICR exchanges with the CBF client.
[0202] Given these conditions, in some embodiments, the only frame between the BA transmitted by a client via the shared AP for a CBF PPDU and the start of the next CBF PPDU may be a CBF-trigger frame. The CBF-trigger may carry at least an indication of whether the BA associated with the upcoming PPDU will be acquired by the shared AP using a separate MU-BAR or using an embedded trigger within the CBF PPDU itself. This CBF-trigger can only be transmitted if both the shared AP and the client via the shared AP agree to continue transmitting further CBF PPDUs within the same TXOP. The decision to continue may depend on several factors, including the availability of data from the CBF client, the known availability or unavailability of the CBF client, the validity of the CBF transmission parameters, and / or whether sufficient duration is maintained for the additional PPDU and its corresponding acknowledgment sequence within the maximum TXOP limit. Since the shared AP is solely aware of the maximum TXOP length, its internal constraints also influence this decision to continue.
[0203] In some embodiments, to enable synchronized continuation decisions, two APs may communicate their readiness to continue with additional CBF transmissions. This exchange may or must occur before the next CBF-trigger is transmitted. The shared AP may communicate its readiness within the CBF-trigger, or, if using a separate MU-BAR, within that MU-BAR, because any indication placed within the CBF PPDU can only be heard by the CBF client and not by the shared AP. Correspondingly, the shared AP may communicate its readiness via the MU-BAR it transmits to its own CBF client. These mechanisms ensure that each AP is promptly informed of the other AP's willingness and ability to continue the coordinated session.
[0204] In some embodiments, a CBF-trigger or MU-BAR transmitted by the shared AP may contain a field designated as CBF-continue, which may be detected by the shared AP. When the shared AP does not transmit a separate MU-BAR, the CBF-trigger itself may carry the CBF-continue field. When transmitting a separate MU-BAR, the MU-BAR may alternatively carry the CBF-continue field, thus giving the shared AP additional time to gather information, such as newly arrived data from its CBF clients, before deciding whether to continue with another CBF PPDU. The CBF-continue field may be set to zero when the shared AP does not intend to transmit further CBF PPDUs and the current PPDU is the last PPDU in the session; it may be set to 1 when the shared AP intends to transmit an additional CBF PPDU in the same TXOP, assuming the shared AP also agrees to continue.
[0205] In some embodiments, the MU-BAR transmitted by the shared AP may contain a CBF-Continue field heard by the shared AP. This field may be set to zero when the shared AP does not intend to transmit a further CBF PPDU, because it has no more data to send, or because the shared AP has already transmitted a CBF-Continue equal to zero. The field may be set to 1 when the shared AP intends to participate in an additional CBF PPDU and the shared AP also signals a CBF-Continue equal to 1. In some embodiments, when two APs transmit a CBF-Continue equal to 1, the shared AP may or must transmit the next CBF-Trigger at the SIFS following the BA transmitted by the shared AP's client. In some embodiments, if either AP transmits a CBF-Continue equal to zero, the shared AP may not transmit any additional CBF-Trigger at the SIFS following the BA, thereby terminating the CBF session of the current TXOP. Any remaining portion of the TXOP can then be used by the shared AP for non-CBF transmissions.
[0206] 5-4. Extended timeout handling for addressed CBF clients
[0207] Using the scheme described in previous sections, in some embodiments, at the end of a BA transmitted by a client of the shared AP corresponding to CBF PPDU n, both the shared AP and the AP via the shared AP can deterministically know whether a CBF-trigger will occur for CBF PPDU(n+1). This deterministic knowledge can be followed by an exchange from the CBF-continue instruction and ensures that each AP has a clear view of session continuation before any subsequent SIFS interval control or data activity.
[0208] In some embodiments, as part of the extended timeout behavior of an EMLSR / DPS-enabled CBF client, the CBF client on both the shared AP and via the shared AP may continue to wait for subsequent CBFPPDUs even if both decide to terminate the session. This continued waiting can consume power and, in the case of EMLSR, may cause the client to lose channel access diversity while maintaining a high readiness state for a transmission that will not occur. Therefore, in some embodiments, an explicit handling of the extended timeout for the CBF client can be provided after the last CBF PPDU, allowing the client to quickly exit extended listening and return to its baseline power-saving behavior.
[0209] Therefore, in some embodiments, any CBF-continue transmitted in or via a MU-BAR within a shared AP can also be read by the client of the respective AP; this is why the indication is placed in the public / special user information field. For cases where the shared AP does not transmit a separate MU-BAR and therefore transmits CBF-continue within the CBF-trigger itself, the same indication can be copied for the client of the shared AP in the CBF-PPDU. This copy can be carried within the embedded trigger frame that triggers the BA, causing the client of the shared AP to receive the continue status regardless of the presence of a separate MU-BAR.
[0210] In some embodiments, the embedded trigger frame transmitted by the shared AP for acquiring the BA may therefore carry a CBF-Continue field. If the shared AP transmits CBF-Continue in a CBF-Trigger, it may also transmit the same value of CBF-Continue in a trigger embedded in the corresponding CBF PPDU. This consistency ensures that the AP and all addressed clients observe the same session continuation state of CBFPPDU n and can align their post-BA behavior accordingly.
[0211] In some embodiments, when the shared AP transmits CBF-continue=1 in its CBF-PPDU / MU-BAR corresponding to CBF PPDU n, and CBF-continue=1 is also transmitted by the shared AP in its MU-BAR corresponding to CBF PPDU n, a CBF-trigger for CBFPPDU n+1 can be transmitted by the shared AP. In this case, clients of the shared AP can continue their extended timeout behavior based on reading CBF-continue=1 in the embedded trigger frame of the shared AP within the CBF-PPDU or MU-BAR, and clients via the shared AP can continue their extended timeout behavior based on reading CBF-continue=1 in the MU-BAR via the shared AP.
[0212] In some embodiments, if the shared AP transmits CBF-continue=0 in its CBF PPDU or the embedded trigger frame within the MU-BAR corresponding to CBF PPDU n, then transmitting CBF-continue=1 via the shared AP in its MU-BAR corresponding to CBF PPDU n is not permitted, and therefore such a combination is invalid. This prohibition prevents conflicting continue states and preserves a single authoritative termination decision when issued by the shared AP.
[0213] In some embodiments, when the shared AP transmits CBF-continue=0 in its CBF-PPDU / MU-BAR corresponding to CBF PPDU n, and the shared AP transmits CBF-continue=0 in its MU-BAR corresponding to CBF PPDU n, it may not transmit CBF-trigger or CBF PPDU n+1. In this termination case, clients of the shared AP may abort their extended timeout behavior when reading CBF-continue=0 in the shared AP's CBF-PPDU / MU-BAR, and clients of the shared AP may abort their extended timeout behavior when reading CBF-continue=0 in the shared AP's MU-BAR.
[0214] In some embodiments, when a shared AP transmits CBF-continue=1 in its CBF-PPDU / MU-BAR corresponding to CBF PPDU n, and also transmits CBF-continue=0 in its MU-BAR corresponding to CBF PPDU n, it may not transmit CBF-trigger or CBF PPDU n+1, because continuation requires agreement from both APs. Under this asymmetric condition, a client of the shared AP can continue its extended timeout behavior based on reading CBF-continue=1 in the shared AP's CBF-PPDU / MU-BAR, which would otherwise cause it to wait unnecessarily.
[0215] For the benefit of these clients, in some embodiments, a CBF termination indication may be transmitted by the shared AP after a BA transmitted by a client of the shared AP. The CBF termination indication may be carried in a separate frame used as the last frame in the TXOP, or, if the shared AP chooses to use the remainder of the TXOP for a non-CBF transmission, it may be explicitly or implicitly embedded in the first frame initiating such a transmission. Upon receiving this CBF termination indication, a client of the shared AP may abort its extended timeout behavior and fall back to its regular eMLSR / DPS timeout behavior, whereas a client via the shared AP may have already aborted its extended timeout behavior based on reading CBF-continue=0 in the shared AP's MU-BAR.
[0216] 6. Advantages
[0217] The embodiments of this disclosure offer at least the following advantages and benefits. First, the embodiments of this disclosure can establish sessions that allow participating access points to reuse previously negotiated parameters across multiple CBF transmissions without repeating the multi-frame setup overhead typically incurred before each transmission. By allowing several CBF PPDUs to occur consecutively within a single session and by relying on a single CBF-trigger between consecutive PPDUs, the system can reduce the frequency of the initial handshake and control exchanges described during setup, which increases the amount of talk time available for downlink data and improves transmission efficiency. Therefore, the session model can support longer, more continuous coordinated beamforming activities while avoiding the constraints that arise when each CBF PPDU is preceded by a complete invitation and response sequence.
[0218] Second, embodiments of this disclosure provide a mechanism that allows for the extension of a session after each CBF transmission. In some embodiments, access points exchange CBF-continue indications via independent frames or frames embedded in acknowledgment traffic to signal their ability and willingness to participate in another coordinated transmission. Because these indications are delivered in a deterministic timing and because both devices evaluate each other's continue status before the next trigger opportunity, the system ensures that consecutive CBF transmissions only occur when both have the ability to continue traffic. This explicit continue signaling prevents ambiguous waiting intervals and enables rapid sequencing of additional CBF PPDUs, which enhances responsiveness and stability during ongoing multi-AP coordination. Explicit continue also prevents erroneous scenarios, such as, assuming a shared AP is continuing a CBF session but there is actually no data and / or no available clients due to its non-participation in those subsequent exchanges, thus leaving long, unwanted gaps in the media during which any other device could enter the channel. Such one-sided continue also reduces spectral efficiency because only the shared AP will be transmitting.
[0219] Third, embodiments of this disclosure can allow extended session signaling to improve the behavior of stations associated with each access point. When continuation information propagates via MU-BAR frames or embedded triggers, stations relying on extended timeout operations can determine whether further CBF PPDUs are anticipated and can accordingly maintain or exit their enhanced receive readiness. In some embodiments, when only one access point can continue, a termination indication can be transmitted, allowing the station to quickly return to its baseline listening or power-saving state instead of waiting for a transmission that will not occur. This alignment between session extended signaling and station power management requirements reduces unnecessary energy consumption and preserves predictable receive timing throughout the multi-PPDU session.
[0220] A reference to "or" can be interpreted as inclusive, such that any term described using "or" can refer to a single, more than one, or any of all the terms described. A reference to at least one of a list of conjunctions for terms can be interpreted as inclusive or to refer to a single, more than one, or any of all the terms described. For example, a reference to "at least one of 'A' and 'B'" can include only 'A', only 'B', or both 'A' and 'B'. Such references used in conjunction with "include" or other open terms can include additional terms.
[0221] It should be noted that certain paragraphs of this disclosure may refer to terms, such as “first” and “second,” used in conjunction with subsets of transmit spatial streams, probe frames, responses, and devices, for purposes of identification or distinction between one and another or for other purposes. These terms are not intended to relate entities (e.g., first and second devices) solely in time or according to sequence, but in some cases, these entities may include such relationships. These terms also do not limit the number of possible entities (e.g., STAs, APs, beamformers, and / or beamforming receivers) that may operate in the system or environment. It should be understood that the system described above may provide any or multiple of those components, and these components may be located on a standalone machine, or, in some embodiments, on multiple machines in a distributed system. Furthermore, bit field positions may be changed, and multiple bit words may be used. Additionally, the above-described systems and methods may be provided as one or more computer-readable programs or executable instructions embodied on or within one or more articles of manufacture (e.g., floppy disks, hard disks, CD-ROMs, flash memory cards, PROMs, RAMs, ROMs, or magnetic tapes). The program can be implemented in any programming language (e.g., LISP, PERL, C, C++, C#) or in any bytecode language (e.g., JAVA). The software program or executable instructions can be stored as object code on or within one or more artifacts.
[0222] While the foregoing written description of the methods and systems enables those skilled in the art to make and use embodiments thereof, those skilled in the art will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiments, methods, and examples herein. Therefore, the methods and systems herein should not be limited to the embodiments, methods, and examples described above, but should be limited to all embodiments and methods within the scope and spirit of this disclosure.
Claims
1. A first access point, comprising: Network interface; and One or more processors, configured to: One or more frames are exchanged with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming CBF transmission in the session; and During the session, multiple data units are transmitted via CBF to one or more stations (STAs) through the network interface using one or more parameters. During the session, in response to the CBF transmission of the first data unit, the one or more processors are configured to: The transmission indicates that the first access point is able to participate in the first frame of the next CBF transmission during the session; In response to receiving a second frame indicating that the second access point can participate in the next CBF transmission during the session, a trigger frame is transmitted, and then a CBF transmission of the second data unit is performed.
2. The first access point according to claim 1, wherein the second frame is received within a short inter-frame interval (SIFS) after the first frame is transmitted.
3. The first access point according to claim 1, wherein after receiving the second frame, the trigger frame is transmitted within a short inter-frame interval (SIFS).
4. The first access point of claim 1, wherein the first frame is transmitted within a short interframe interval (SIFS) after receiving a trigger-based physical layer protocol data unit (TB PPDU) with block acknowledgment (BA) from one or more STAs or a group of STAs associated with the second access point.
5. The first access point according to claim 1, wherein the first frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
6. The first access point according to claim 1, wherein the first frame is embedded in a multi-user block acknowledgment request (MU-BAR) frame addressed to the one or more STAs.
7. The first access point according to claim 1, wherein the second frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
8. A first access point, comprising: Network interface; and One or more processors, configured to: One or more frames are exchanged with the second access point via the network interface to determine one or more parameters for performing coordinated beamforming CBF transmission in the session; and During the session, multiple data units are transmitted via CBF to one or more stations (STAs) through the network interface using one or more parameters. During the session, in response to the CBF transmission of the first data unit, the one or more processors are configured to: In response to receiving a first frame indicating that the second access point can participate in the next CBF transmission during the session, a second frame indicating that the first access point can participate in the next CPF transmission is transmitted; and In response to receiving a trigger frame, a CBF transmission of a second data unit is performed during the session.
9. The first access point according to claim 8, wherein after receiving the first frame, the second frame is transmitted within a short inter-frame interval (SIFS).
10. The first access point according to claim 8, wherein the trigger frame is received within a short inter-frame interval (SIFS) after the second frame is transmitted.
11. The first access point of claim 8, wherein the first frame is received within a short interframe interval (SIFS) after receiving a trigger-based physical layer protocol data unit (TB PPDU) with block acknowledgment (BA) from one or more STAs.
12. The first access point of claim 8, wherein the first frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
13. The first access point of claim 8, wherein the first frame is embedded in a multi-user block acknowledgment request (MU-BAR) frame addressed to one or more STAs associated with the second access point.
14. The first access point of claim 13, wherein the second frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
15. A method for performing coordinated beamforming (CBF) transmission during a session, comprising: The first access point and the second access point exchange one or more frames with each other to determine one or more parameters for performing CBF transmission in the session; During the session, the first access point and the second access point simultaneously perform a pair of first data units to one or more stations (STAs) using one or more parameters. In response to the CBF transmission of the pair of first data units, the first access point transmits a first frame indicating that the first access point is able to participate in the next CBF transmission; In response to receiving the first frame, the second access point transmits a second frame indicating that the second access point is able to participate in the next CBF transmission; In response to receiving the second frame, the first access point transmits a trigger frame; and In response to the trigger frame, during the session, the first access point and the second access point simultaneously perform a pair of second data units to the one or more STAs using the one or more parameters.
16. The method of claim 15, wherein after transmitting the first frame, the second frame is transmitted within a short inter-frame interval (SIFS).
17. The method of claim 15, wherein after receiving a triggered physical layer protocol data unit (TB PPDU) with block acknowledgment (BA) from one or more STAs, the first frame is transmitted within a short interframe interval (SIFS).
18. The method of claim 15, wherein the first frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
19. The method of claim 15, wherein the first frame is embedded in a multi-user block acknowledgment request (MU-BAR) frame addressed to one or more STAs associated with the first access point.
20. The method of claim 19, wherein the second frame is embedded in a trigger-based physical layer protocol data unit (TB PPDU).
