Signaling designs for coordinated beamforming in wireless communications
The proposed signaling methods for CoBF in wireless communications address the lack of PPDU transmission details by using U-SIGs and UHR-SIGs to facilitate efficient data transmission and reception in multi-AP systems, enhancing CoBF operations.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- MEDIATEK INC
- Filing Date
- 2025-10-30
- Publication Date
- 2026-05-07
AI Technical Summary
There is a need for a signaling method to enable coordinated beamforming (CoBF) in wireless communications, particularly in multi-access point (AP) Wi-Fi systems, as details regarding physical-layer protocol data unit (PPDU) transmission have not been specified.
Proposed schemes for signaling methods in CoBF involve generating and processing PPDU with specific fields and subfields to facilitate coordinated beamforming, including U-SIGs carrying BSS colors and UHR-SIGs indicating user numbers and spatial configurations, allowing for efficient CoBF operations.
The proposed signaling methods enhance the efficiency and coordination of CoBF in wireless communications, enabling effective data transmission and reception in multi-AP environments.
Smart Images

Figure CN2025131188_07052026_PF_FP_ABST
Abstract
Description
SIGNALING DESIGNS FOR COORDINATED BEAMFORMING IN WIRELESS COMMUNICATIONSCROSS REFERENCE TO RELATED PATENT APPLICATION
[0001] The present disclosure is part of a non-provisional patent application claiming the priority benefit of U.S. Provisional Patent Application No. 63 / 714,111 filed 30 October 2024, the content of which herein being incorporated by reference in its entirety.TECHNICAL FIELD
[0002] The present disclosure is generally related to wireless communications and, more particularly, to signaling methods for coordinated beamforming (CoBF or CBF) in wireless communications.BACKGROUND
[0003] Unless otherwise indicated herein, approaches described in this section are not prior art to the claims listed below and are not admitted as prior art by inclusion in this section.
[0004] In wireless communications, such as Wi-Fi (or WiFi) in wireless local area network (WLAN) systems in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, multi-access point (multi-AP) with CoBF is considered as a new key feature for next-generation Wi-Fi. To simplify the CoBF design, some constraints are considered. For instance, in CoBF, up to two access points (APs) may be supported in a multi-AP CoBF, with up to a total of 4 users and up to 4 as the number of spatial streams (Nss) . However, at the time of the present disclosure, details regarding a signaling method to enable CoBF physical-layer (PHY) protocol data unit (PPDU) transmission have yet to be specified. Therefore, there is a need for a solution of signaling methods for CoBF in wireless communications.SUMMARY
[0005] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
[0006] An objective of the present disclosure is to provide schemes, concepts, designs, techniques, methods and apparatuses pertaining to signaling methods for CoBF in wireless communications. It is believed that implementations of various schemes proposed herein may address or otherwise alleviate the aforementioned issues.
[0007] In one aspect, a method may involve an apparatus generating a PPDU. The method may also involve the apparatus transmitting the PPDU as part of a CoBF transmission. The PPDU may include signaling enabling the CoBF transmission.
[0008] In another aspect, a method may involve an apparatus receiving a PPDU as part of a CoBF transmission. The method may also involve the apparatus processing the PPDU. The PPDU may include signaling enabling the CoBF transmission.
[0009] It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as, Wi-Fi, the proposed concepts, schemes and any variation (s) / derivative (s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Bluetooth, ZigBee, 5th Generation (5G) / New Radio (NR) , Long-Term Evolution (LTE) , LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) , Industrial IoT (IIoT) and narrowband IoT (NB-IoT) . Thus, the scope of the present disclosure is not limited to the examples described herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation to clearly illustrate the concept of the present disclosure.
[0011] FIG. 1 is a diagram of an example network environment in which various solutions and schemes in accordance with the present disclosure may be implemented.
[0012] FIG. 2 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0013] FIG. 3 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0014] FIG. 4 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0015] FIG. 5 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0016] FIG. 6 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0017] FIG. 7 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0018] FIG. 8 is a diagram of an example design under a proposed scheme in accordance with the present disclosure.
[0019] FIG. 9 is a block diagram of an example communication system under a proposed scheme in accordance with the present disclosure.
[0020] FIG. 10 is a flowchart of an example process under a proposed scheme in accordance with the present disclosure.
[0021] FIG. 11 is a flowchart of an example process under a proposed scheme in accordance with the present disclosure. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[0022] Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview
[0023] Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and / or solutions pertaining to signaling methods for CoBF in wireless communications. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
[0024] FIG. 1 illustrates an example network environment 100 in which various solutions and schemes in accordance with the present disclosure may be implemented. FIG. 2 ~ FIG. 11 illustrate examples of implementation of various proposed schemes in network environment 100 in accordance with the present disclosure. The following description of various proposed schemes is provided with reference to FIG. 1 ~ FIG. 11.
[0025] Referring to part (A) of FIG. 1, network environment 100 may involve at least a station (STA) 110 communicating wirelessly with a STA 120. Either of STA 110 and STA 120 may function as an access point (AP) STA or, alternatively, a non-AP STA. In some cases, STA 110 and STA 120 may be associated with a basic service set (BSS) in accordance with one or more IEEE 802.11 standards (e.g., IEEE 802.11bn and future-developed standards) . Each of STA 110 and STA 120 may be configured to communicate with each other by utilizing the signaling methods for CoBF in wireless communications in accordance with various proposed schemes described below. It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately.
[0026] FIG. 2 illustrates an example design 200 under a proposed scheme in accordance with the present disclosure. Design 200 may pertain to a universal signal field (U-SIG) in a PPDU for CoBF. Referring to FIG. 2, a first U-SIG (U-SIG1) may carry two BSS colors (or identifiers of two BSS sets) , one for a sharing (or coordinating) AP and the other for a shared (or coordinated) AP that participate in CoBF (or coordinated spatial reuse (CoSR) ) operations. For instance, in U-SIG 1, bits B7 ~ B12 may carry a first BSS color (or BSS color 1, or identifier for the first coordinated BSS associated with the coordinating AP) and bits B20 ~ B25 may carry a second BSS color (or BSS color 2, or identifier for the second coordinated BSS associated with the coordinated AP) . Moreover, referring to FIG. 2, a field used to indicate a PPDU type in a second U-SIG (U-SIG2) may be set to a value to indicate that the PPDU is a CoBF PPDU. For instance, in U-SIG2, bits B0 ~ B1 may be set to indicate the PPDU type is a CoBF PPDU. Additionally, a field used to indicate a Ultra-High-Reliability (UHR) signal (UHR-SIG) modulation and coding scheme (MCS) may be set to a fixed value of 0 to indicate MCS0, which may involve binary phase-shift keying (BPSK) plus a code rate (R) of 1 / 2.
[0027] FIG. 3 illustrates an example design 300 under a proposed scheme in accordance with the present disclosure. Design 300 may pertain to a first option of indication of the number of non-orthogonal frequency-division multiple-access (non-OFDMA) users in a Common Field in UHR-SIG of a PPDU. In design 300, a subfield (e.g., bits B16 ~ B18) used to indicate the “number of non-OFDMA users” may be utilized to indicate the total number of users participating in the CoBF. For instance, a value of 0 may indicate 2 users (associated with an AP) , a value of 1 may indicate 3 users (associated with the AP) , and a value of 2 may indicate 4 users (associated with the AP) . That is, in design 300, the value of the “number of non-OFDMA Users” subfield may be equal to the total number of CoBF users associated with a given AP (e.g., sharing AP or shared AP) .
[0028] FIG. 4 illustrates an example design 400 under a proposed scheme in accordance with the present disclosure. Design 400 may pertain to a first option (Option-1) of BSS color indication by a Spatial Configuration subfield. In Option-1, for the “Number of non-OFDMA User” signaling in Option-1 described above, the total number of users in CoBF transmission (s) may be known, and the “Spatial Configuration” subfield may be redefined. Referring to FIG. 4, bits B3 ~B2 may indicate the number of users from an AP, and bits B1 ~ B0 may signal the spatial configurations.
[0029] In a second option of BSS color indication, with respect to the “Number of non-OFDMA User” subfield in the Common Field, the value of the “Number of non-OFDMA User” subfield may be set or configured to indicate: (1) the total number of users participating in CoBF; and (2) the number of users in each AP with BSS color 1 or BSS color 2. By using Option-2 signaling, the number of users per AP may be indicated, so that per-user fields belonging to BSS color 1 and BSS color 2 may be identified. The User Fields in UHR-SIG may be in an order corresponding to BSS color 1 and BSS color 2. For instance, the user fields for STAs from an AP with BSS color 1 may be before the user fields from another AP with BSS color 2.
[0030] FIG. 5 illustrates an example design 500 under a proposed scheme in accordance with the present disclosure. Design 500 may pertain to a second option (Opion-2) of BSS color indication by a Spatial Configuration subfield. In Option-2, for the “Number of non-OFDMA Users” signaling, the “Spatial Configuration” subfield may reuse the encoding of IEEE 802.11ax Spatial Configuration subfield. In particular, the maximum number of users per AP may be limited 3. Moreover, for the number of users = 1 for an AP or associated with BSS color 1 or BSS color 2, the entries 0000 –0010 may be used to indicate number of spatial streams (Nss) = 1 ~ 3.
[0031] FIG. 6 illustrates an example design 600 under a proposed scheme in accordance with the present disclosure. Design 600 may pertain to Spatial Configuration subfield encoding for CoBF. Under the proposed scheme, the Spatial Configuration subfield may be redefined as shown in FIG. 6 for CoBF when the number of users per AP (or per BSS color) is indicated in the Common Field.
[0032] FIG. 7 illustrates an example design 700 under a proposed scheme in accordance with the present disclosure. Design 700 may pertain to BSS color indication by Spatial Configuration subfield configuration. Under the proposed scheme, the Spatial Configuration subfield may be redefined as shown in FIG. 7 for CoBF when the number of users per AP (or per BSS color) is indicated in the Common Field. Furthermore, the bit B3 may be used to indicate the BSS color to which a STA is associated.
[0033] FIG. 8 illustrates an example design 800 under a proposed scheme in accordance with the present disclosure. Design 800 may pertain to a second option (Opion-3) of BSS color indication by a Spatial Configuration subfield. In Option-3, one dedicated bit per User field may be used to indicate each BSS color to which a STA belongs or is associated. In one approach, bit B20 of the “Reserved” subfield may be utilized to indicate the transmission as being from BSS color 1 or BSS color 2. In another approach, it may be assumed that low-density parity-check (LDPC) is used for the CoBF transmission (s) and, correspondingly, for the CoBF PPDU, bit B21 (e.g., the bit originally used as a “Coding” subfield to indicate the type of coding) may be re-purposed to indicate or differentiate two BSS colors. For instance, bit B21 of the User Field may be defined as “AP flag” or “BSS Color Indication” subfield, with a value of 0 to indicate BSS color 1 and a value of 1 to indicate BSS color 2. Illustrative Implementations
[0034] FIG. 9 illustrates an example system 900 having at least an example apparatus 910 and an example apparatus 920 in accordance with an implementation of the present disclosure. Each of apparatus 910 and apparatus 920 may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to signaling methods for CoBF in wireless communications including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above as well as processes described below. For instance, apparatus 910 may be implemented in STA 110 and apparatus 920 may be implemented in STA 120, or vice versa.
[0035] Each of apparatus 910 and apparatus 920 may be a part of an electronic apparatus, which may be a non-AP STA or an AP STA, such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. When implemented in a STA, each of apparatus 910 and apparatus 920 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus 910 and apparatus 920 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, each of apparatus 910 and apparatus 920 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus 910 and / or apparatus 920 may be implemented in a network node, such as an AP in a WLAN.
[0036] In some implementations, each of apparatus 910 and apparatus 920 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction set computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. In the various schemes described above, each of apparatus 910 and apparatus 920 may be implemented in or as a STA or an AP. Each of apparatus 910 and apparatus 920 may include at least some of those components shown in FIG. 9 such as a processor 912 and a processor 922, respectively, for example. Each of apparatus 910 and apparatus 920 may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and / or user interface device) , and, thus, such component (s) of apparatus 910 and apparatus 920 are neither shown in FIG. 9 nor described below in the interest of simplicity and brevity.
[0037] In one aspect, each of processor 912 and processor 922 may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors or one or more CISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 912 and processor 922, each of processor 912 and processor 922 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 912 and processor 922 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 912 and processor 922 is a special-purpose machine specifically designed, arranged and configured to perform specific tasks including those pertaining to signaling methods for CoBF in wireless communications in accordance with various implementations of the present disclosure.
[0038] In some implementations, apparatus 910 may also include a transceiver 916 coupled to processor 912. Transceiver 916 may include a transmitter capable of wirelessly transmitting and a receiver capable of wirelessly receiving data. In some implementations, apparatus 920 may also include a transceiver 926 coupled to processor 922. Transceiver 926 may include a transmitter capable of wirelessly transmitting and a receiver capable of wirelessly receiving data. It is noteworthy that, although transceiver 916 and transceiver 926 are illustrated as being external to and separate from processor 912 and processor 922, respectively, in some implementations, transceiver 916 may be an integral part of processor 912 as a system on chip (SoC) , and transceiver 926 may be an integral part of processor 922 as a SoC.
[0039] In some implementations, apparatus 910 may further include a memory 914 coupled to processor 912 and capable of being accessed by processor 912 and storing data therein. In some implementations, apparatus 920 may further include a memory 924 coupled to processor 922 and capable of being accessed by processor 922 and storing data therein. Each of memory 914 and memory 924 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM) , static RAM (SRAM) , thyristor RAM (T-RAM) and / or zero-capacitor RAM (Z-RAM) . Alternatively, or additionally, each of memory 914 and memory 924 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM) , erasable programmable ROM (EPROM) and / or electrically erasable programmable ROM (EEPROM) . Alternatively, or additionally, each of memory 914 and memory 924 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM) , magnetoresistive RAM (MRAM) and / or phase-change memory.
[0040] Each of apparatus 910 and apparatus 920 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus 910, as STA 110, and apparatus 920, as STA 120, is provided below in the context of example processes 1000 and 1100. It is noteworthy that, although a detailed description of capabilities, functionalities and / or technical features of apparatus 920 is provided below, the same may be applied to apparatus 910 although a detailed description thereof is not provided solely in the interest of brevity. It is also noteworthy that, although the example implementations described below are provided in the context of WLAN, the same may be implemented in other types of networks. Illustrative Processes
[0041] FIG. 10 illustrates an example process 1000 in accordance with an implementation of the present disclosure. Process 1000 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 1000 may represent an aspect of the proposed concepts and schemes pertaining to signaling methods for CoBF in wireless communications in accordance with the present disclosure. Process 1000 may include one or more operations, actions, or functions as illustrated by one or more of blocks. Although illustrated as discrete blocks, various blocks of process 1000 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks / sub-blocks of process 1000 may be executed in the order shown in FIG. 10 or, alternatively, in a different order. Furthermore, one or more of the blocks / sub-blocks of process 1000 may be executed repeatedly or iteratively. Process 1000 may be implemented by or in apparatus 910 and apparatus 920 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 1000 is described below in the context of apparatus 910 implemented in or as STA 110 functioning as a non-AP STA or an AP STA and apparatus 920 implemented in or as STA 120 functioning as an AP STA or a non-AP STA of a wireless network such as a WLAN in network environment 100 in accordance with one or more of IEEE 802.11 standards. Process 1000 may begin at block 1010.
[0042] At 1010, process 1000 may involve processor 912 of apparatus 910, as STA 110, generating a PPDU. The PPDU may include signaling enabling the CoBF transmission. Process 1000 may proceed from 1010 to 1020.
[0043] At 1020, process 1000 may involve processor 912 transmitting, via transceiver 916, the PPDU as part of a CoBF transmission (e.g., with apparatus 920 as STA 120) .
[0044] In some implementations, the PPDU may include U-SIG1 carrying two BSS colors, or identifiers of two BSS sets, for a sharing or coordinating AP and a shared or coordinated AP that participates in CoBF operations. In some implementations, bits B7 ~ B12 of the U-SIG1 may indicate a first BSS color (BSS color 1, or an identifier of a first coordinated BSS associated with the coordinating AP) , and bits B20 ~ B25 of the U-SIG1 may indicate a second BSS color (BSS color 2 , or an identifier of a second coordinated BSS associated with the coordinated AP) . In some implementations, the PPDU may further include a U-SIG2 having a PPDU Type subfield indicating that the PPDU is a CoBF PPDU.
[0045] In some implementations, the PPDU may include a Common field in a UHR-SIG having a Number of non-OFDMA Users subfield indicating a total number of users participating in the CoBF transmission. In some implementations, bits B16 ~ B18 of the Common field in the UHR-SIG may indicate the total number of users participating in the CoBF transmission.
[0046] In some implementations, the PPDU may include a User field having a Spatial Configuration subfield with four bits encoded by reusing encoding of an IEEE 802.11ax Spatial Configuration subfield encoding.
[0047] In some implementations, in transmitting the PPDU, process 1000 may involve processor 912 encoding a data portion of the PPDU, as a CoBF PPDU, with only LDPC.
[0048] In some implementations, a bit in a User field of the PPDU used to indicate coding may be repurposed and used for BSS color indication responsive to the PPDU type being indicated in a universal signal field (U-SIG) as a CoBF PPDU. In some implementations, the bit may be bit B21 in the User field of the PPDU, with a first value (or value 0) of the bit indicating a first BSS color (or indicating that a User field belongs to a first coordinated BSS) , and with a second value (or value 1) of the bit indicating a second BSS color (or indicating that the User field belongs to a second coordinated BSS) .
[0049] FIG. 11 illustrates an example process 1100 in accordance with an implementation of the present disclosure. Process 1100 may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above. More specifically, process 1100 may represent an aspect of the proposed concepts and schemes pertaining to signaling methods for CoBF in wireless communications in accordance with the present disclosure. Process 1100 may include one or more operations, actions, or functions as illustrated by one or more of blocks. Although illustrated as discrete blocks, various blocks of process 1100 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks / sub-blocks of process 1100 may be executed in the order shown in FIG. 11 or, alternatively, in a different order. Furthermore, one or more of the blocks / sub-blocks of process 1100 may be executed repeatedly or iteratively. Process 1100 may be implemented by or in apparatus 910 and apparatus 920 as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process 1100 is described below in the context of apparatus 910 implemented in or as STA 110 functioning as a non-AP STA or an AP STA and apparatus 920 implemented in or as STA 120 functioning as an AP STA or a non-AP STA of a wireless network such as a WLAN in network environment 100 in accordance with one or more of IEEE 802.11 standards. Process 1100 may begin at block 1110.
[0050] At 1110, process 1100 may involve processor 922 of apparatus 920, as STA 120, receiving, via transceiver 926, a PPDU (e.g., from apparatus 910 as STA 110) as part of a CoBF transmission. Process 1100 may proceed from 1110 to 1120.
[0051] At 1120, process 1100 may involve processor 922 processing the PPDU (e.g., decoding the PPDU) .
[0052] In some implementations, the PPDU may include U-SIG1 carrying two BSS colors, or identifiers of two BSS sets, for a sharing or coordinating AP and a shared or coordinated AP that participates in CoBF operations. In some implementations, bits B7 ~ B12 of the U-SIG1 may indicate a BSS color 1, or an identifier of a first coordinated BSS associated with the coordinating AP, and bits B20 ~ B25 of the U-SIG1 may indicate a BSS color 2, or an identifier of a second coordinated BSS associated with the coordinated AP. In some implementations, the PPDU may further include a U-SIG2 having a PPDU Type subfield indicating that the PPDU is a CoBF PPDU.
[0053] In some implementations, the PPDU may include a Common field in a UHR-SIG having a Number of non-OFDMA Users subfield indicating a total number of users participating in the CoBF transmission. In some implementations, bits B16 ~ B18 of the Common field in the UHR-SIG may indicate the total number of users participating in the CoBF transmission.
[0054] In some implementations, the PPDU may include a User field having a Spatial Configuration subfield with four bits encoded by reusing encoding of an IEEE 802.11ax Spatial Configuration subfield encoding.
[0055] In some implementations, in transmitting the PPDU, process 1100 may involve processor 922 decoding a data portion of the PPDU, as a CoBF PPDU, with only LDPC.
[0056] In some implementations, a bit in a User field of the PPDU used to indicate coding may be repurposed and used for BSS color indication responsive to the PPDU type being indicated in a universal signal field (U-SIG) as a CoBF PPDU. In some implementations, the bit may be bit B21 in the User field of the PPDU, with a first value (or value 0) of the bit indicating a first BSS color (or indicating that a User field belongs to a first coordinated BSS) , and with a second value (or value 1) of the bit indicating a second BSS color (or indicating that the User field belongs to a second coordinated BSS) . Additional Notes
[0057] The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected" , or "operably coupled" , to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable" , to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.
[0058] Further, with respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.
[0059] Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to, ” the term “having” should be interpreted as “having at least, ” the term “includes” should be interpreted as “includes but is not limited to, ” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an, " e.g., “a” and / or “an” should be interpreted to mean “at least one” or “one or more; ” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of "two recitations, " without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc. ” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B. ”
[0060] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
Claims
1.A method, comprising:generating, by a processor of an apparatus, a physical-layer protocol data unit (PPDU) ; andtransmitting, by the processor, the PPDU as part of a coordinated beamforming (CoBF) transmission,wherein the PPDU comprises signaling enabling the CoBF transmission.2.The method of Claim 1, wherein the PPDU comprises a first universal signal field (U-SIG1) carrying two basic service set (BSS) colors, or identifiers of two BSS sets, for a sharing or a coordinating access point (AP) and a shared or a coordinated AP that participate in CoBF operations.3.The method of Claim 2, wherein bits B7 ~ B12 of the U-SIG1 indicate a first BSS color (BSS color 1, or an identifier of a first coordinated BSS associated with the coordinating AP) , and wherein bits B20 ~ B25 of the U-SIG1 indicate a second BSS color (BSS color 2, or an identifier of a second coordinated BSS associated with the coordinated AP) .4.The method of Claim 2, wherein the PPDU further comprises a second universal signal field (U-SIG2) having a PPDU Type subfield indicating that the PPDU is a CoBF PPDU.5.The method of Claim 1, wherein the PPDU comprises a Common field in an Ultra-High-Reliability (UHR) signal field (UHR-SIG) having a Number of non-orthogonal frequency-division multiple-access (non-OFDMA) Users subfield indicating a total number of users participating in the CoBF transmission.6.The method of Claim 5, wherein bits B16 ~ B18 of the Common field in the UHR-SIG indicate the total number of users participating in the CoBF transmission.7.The method of Claim 1, wherein the PPDU comprises a User field having a Spatial Configuration subfield with four bits encoded by reusing encoding of an Institute of Electrical and Electronics Engineers (IEEE) 802.11ax Spatial Configuration subfield encoding.8.The method of Claim 1, wherein the transmitting of the PPDU comprises encoding a data portion of the PPDU, as a CoBF PPDU, with only low-density parity-check (LDPC) .9.The method of Claim 1, wherein a bit in a User field of the PPDU used to indicate coding is repurposed and used for basic service set (BSS) color indication responsive to the PPDU type being indicated in a universal signal field (U-SIG) as a CoBF PPDU.10.The method of Claim 9, wherein the bit is bit B21 in the User field of the PPDU, wherein a first value of the bit indicates a first BSS color (or indicating that a User field belongs to a first coordinated BSS) , and wherein a second value of the bit indicates a second BSS color (or indicating that the User field belongs to a second coordinated BSS) , and wherein the first value is 0 and the second value is 1.11.A method, comprising:receiving, by a processor of an apparatus, a physical-layer protocol data unit (PPDU) as part of a coordinated beamforming (CoBF) transmission; andprocessing, by the processor, the PPDU,wherein the PPDU comprises signaling enabling the CoBF transmission.12.The method of Claim 11, wherein the PPDU comprises a first universal signal field (U-SIG1) carrying two basic service set (BSS) colors, or identifiers of two BSS sets, for a sharing or a coordinating access point (AP) and a shared or a coordinated AP that participate in CoBF operations.13.The method of Claim 12, wherein bits B7 ~ B12 of the U-SIG1 indicate a first BSS color (BSS color 1, or an identifier of a first coordinated BSS associated with the coordinating AP) , and wherein bits B20 ~ B25 of the U-SIG1 indicate a second BSS color (BSS color 2, or an identifier of a second coordinated BSS associated with the coordinated AP) .14.The method of Claim 12, wherein the PPDU further comprises a second universal signal field (U-SIG2) having a PPDU Type subfield indicating that the PPDU is a CoBF PPDU.15.The method of Claim 11, wherein the PPDU comprises a Common field in an Ultra-High-Reliability (UHR) signal field (UHR-SIG) having a Number of non-orthogonal frequency-division multiple-access (non-OFDMA) Users subfield indicating a total number of users participating in the CoBF transmission.16.The method of Claim 15, wherein bits B16 ~ B18 of the Common field in the UHR-SIG indicate the total number of users participating in the CoBF transmission.17.The method of Claim 11, wherein the PPDU comprises a User field having a Spatial Configuration subfield with four bits encoded by reusing encoding of an Institute of Electrical and Electronics Engineers (IEEE) 802.11ax Spatial Configuration subfield encoding.18.The method of Claim 11, wherein the processing of the PPDU comprises decoding a data portion of the PPDU, as a CoBF PPDU, with only low-density parity-check (LDPC) .19.The method of Claim 11, wherein a bit in a User field of the PPDU used to indicate coding is repurposed and used for basic service set (BSS) color indication responsive to the PPDU type being indicated in a universal signal field (U-SIG) as a CoBF PPDU.20.The method of Claim 19, wherein the bit is bit B21 in the User field of the PPDU, wherein a first value of the bit indicates a first BSS color (or indicating that a User field belongs to a first coordinated BSS) , and wherein a second value of the bit indicates a second BSS color (or indicating that the User field belongs to a second coordinated BSS) , and wherein the first value is 0 and the second value is 1.