Multi-channel multiple-input multiple-output beamforming training in millimeter-wave systems
The enhanced beamforming training protocols address inefficiencies in millimeter wave systems by implementing modified frame formats and signaling for multi-channel operations, improving feedback mechanisms and user grouping, resulting in optimized antenna configurations and reduced latency.
Patent Information
- Application Number
- JP2023165270
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2017-08-31
- Filing Date
- 2023-09-27
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2038-07-06
AI Technical Summary
Existing beamforming training protocols in millimeter wave systems face issues such as inefficient feedback mechanisms, lack of multi-channel support, and inadequate user grouping, leading to suboptimal MIMO throughput and increased latency.
Implement enhanced beamforming training procedures that include modified frame formats and signaling to support multi-channel operations, improved feedback mechanisms, and optimized user grouping, utilizing extended schedule elements and BRP frames to convey additional information for better channel measurement and antenna alignment.
Enhances MIMO throughput and reduces latency by providing efficient multi-channel beamforming training, ensuring optimal antenna configurations and minimizing interference among users.
Smart Images

Figure 0007581457000001 
Figure 0007581457000002 
Figure 0007581457000003
Abstract
Description
[Background technology]
[0001] Beam refinement is a process by which a wireless station (STA) can improve its antenna configuration (eg, antenna weight vector) for transmission and / or reception. Summary of the Invention
[0002] Systems, methods, and devices for beamforming (BF) training are disclosed. In some examples, a receiver is configured to receive sector sweep (SSW) training frames from an initiator device, each of which indicates an antenna sector of the initiator device. A transmitter is configured to transmit the sector sweep (SSW) training frames to the initiator device, each of which indicates a best received antenna sector of the initiator device. The receiver receives sector sweep feedback (SSW FB) frames from the initiator device, and the transmitter transmits a sector sweep acknowledgement (SSW ACK) frame to the initiator device, indicating an antenna sector of the initiator device different from the antenna sector indicated by the SSW FB frame, if the SSW FB frame is best received by an antenna that does not correspond to the best received antenna sector of the initiator device. [Brief description of the drawings]
[0003] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A, according to an embodiment. [Figure 1C]FIG. 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A, according to an embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to an embodiment. [Diagram 2] 1 is a signal diagram illustrating an example Institute of Electrical and Electronics Engineers (IEEE) 802.11ad beacon interval. [Diagram 3] FIG. 2 is a signal diagram illustrating an example sector level sweep (SLS) training procedure. [Figure 4] 1 is a bitmap showing an example sector sweep (SSW) frame format by octets. [Diagram 5] 1 is a bitmap showing an example SSW field of an SSW frame in bits. [Figure 6] 1 is a bitmap showing an example SSW feedback field in bits for an SSW frame, where the SSW frame is transmitted as part of an initial sector sweep (ISS). [Figure 7] 1 is a bitmap showing an example SSW feedback field of an SSW frame in bits, where the SSW frame is not transmitted as part of the ISS. [Figure 8] FIG. 1 is a block diagram illustrating a Directional Multi-Gigabit (DMG) Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) followed by a training field that includes an automatic gain control (AGC) field and a transmitter or receiver training field. [Figure 9] FIG. 1 is a signal diagram illustrating the SISO phase in a Single User MIMO (SU-MIMO) BF training procedure. [Figure 10] 1 is a bitmap illustrating an example beamforming (BF) control field format. [Figure 11] 1 is a table illustrating exemplary control trailer fields. [Figure 12] 1 is a bitmap illustrating an example directional multi-gigabit (DMG) beam refinement element. [Figure 13] 1 is a signal diagram illustrating an example MIMO training procedure with full CSI information feedback. [Figure 14] 1 is a signal diagram illustrating an example sector level sweep (SLS) procedure on a secondary channel. [Figure 15] 1 is a bitmap illustrating an example sector sweep feedback field. [Figure 16] FIG. 13 is a signal diagram showing beamforming training for asymmetric links in a beamforming training allocation. [Figure 17] 1 is a bitmap illustrating an exemplary data frame. [Figure 18] 1 is a bitmap illustrating example control fields for frames transmitted within a Directional Multi-Gigabit (DMG) Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU). [Figure 19] 1 is a bitmap illustrating an example DMG media access control packet data unit (MPDU) delimiter. [Figure 20] FIG. 4 is a signal diagram illustrating an example savings achieved using delimiters. [Figure 21A] FIG. 13 is a signal diagram illustrating an example modified BPR TXSS procedure. [Figure 21B] FIG. 13 is a signal diagram illustrating an example modified BPR TXSS procedure. [Figure 22] 1 is a bitmap showing an example short SSW packet format. [Diagram 23] 1 is a bitmap illustrating an example BRP request field format. [Figure 24]A signal diagram showing an example frame exchange for an example procedure for SLS using multiple transmit and receive antennas. [Diagram 25] FIG. 1 is a signal diagram illustrating an example procedure for parallel RX determined by a receiver in BF training. [Figure 26] FIG. 13 is a signal diagram illustrating an example procedure for initiator-determined parallel RX in BF training. [Figure 27] FIG. 13 is a signal diagram illustrating an example procedure for initiator-determined parallel RX in BF training. [Figure 28] 11 is a table illustrating exemplary modified capability identification for an extended capabilities field. [Figure 29] 1 is a bitmap illustrating an example MIMO capability field or multi-BF capability field. [Diagram 30] 1 is a bitmap illustrating an example modified BF control field. [Diagram 31] 13 is a bitmap illustrating an example modified BF control field format for an extended schedule element. [Diagram 32] FIG. 1 is a signal diagram illustrating an example SLS procedure with receive antenna indication. [Diagram 33] FIG. 11 is a signal diagram illustrating another example SLS procedure with receive antenna indication. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0004] 1A illustrates an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, e.g., voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, e.g., Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tailed Unique Word DFT-Spread OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multi-Carrier (FBMC), etc.
[0005] 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as “stations” and / or “STAs”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0006] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, e.g., the CN 106 / 115, the Internet 110, and / or other networks 112. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a home Node B, a home eNode B, a gNB, an NR NodeB, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0007] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), e.g., a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless services to a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.
[0008] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0009] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using Wideband CDMA (WCDMA®). WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0010] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).
[0011] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as New Radio (NR) radio access, which may establish the air interface 116 using NR.
[0012] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement both LTE radio access and NR radio access, e.g., using a dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).
[0013] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as, for example, IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0014] The base station 114b in FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a wireless technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. 1A, base station 114b may have a direct connection to the Internet 110. Thus, base station 114b may not be required to access the Internet 110 via CN 106 / 115.
[0015] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various Quality of Service (QoS) requirements, such as separate throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high level security functions, such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, the CN 106 / 115, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.
[0016] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as TCP, UDP, and / or IP in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs that may employ the same RAT as the RAN 104 / 113 or a different RAT.
[0017] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers to communicate with separate wireless networks over separate wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based wireless technology, and with a base station 114b, which may employ an IEEE 802 wireless technology.
[0018] Figure 1B is a system diagram illustrating an example WTRU 102. As shown in Figure 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a GPS chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any subcombination of the above elements while remaining consistent with an embodiment.
[0019] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an ASIC, an FPGA circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0020] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., the base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0021] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0022] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.
[0023] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include RAM, ROM, a hard disk, or any other type of memory storage device. The removable memory 132 may include a SIM card, a memory stick, an SD memory card, or the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as a server or home computer (not shown).
[0024] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0025] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding a current location of the WTRU 102. The WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 in addition to or in lieu of information from the GPS chipset 136, and / or determine its location based on the timing of signals received from two or more neighboring base stations. It will be appreciated that the WTRU 102 may obtain location information through any suitable location determination method while remaining consistent with an embodiment.
[0026] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photos and / or videos), a USB port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.
[0027] The WTRU 102 may include a full-duplex radio in which the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the UL (e.g., for transmission) and the downlink (e.g., for reception)) may be in parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via signal processing in hardware (e.g., a choke) or via a processor (e.g., via a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio in which the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception)) may not occur in parallel and / or simultaneous.
[0028] 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0029] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO techniques. Thus, the eNode-B 160a may use multiple antennas, for example, to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0030] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0031] 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. Although each of the above elements is shown as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0032] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.
[0033] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as fixing the user plane during handover between eNode Bs, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.
[0034] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0035] The CN 106 may facilitate communication with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0036] Although the WTRU is depicted in FIGS. 1A-1D as a wireless terminal, in certain representative embodiments it is contemplated that such a terminal may be capable of using a wired communications interface (e.g., temporarily or permanently) with the communications network.
[0037] In an exemplary embodiment, the other network 112 may be a WLAN.
[0038] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic to the STA originating from outside the BSS may arrive through the AP and be distributed to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP and delivered to the respective destination. Traffic between STAs in the BSS may be sent through the AP, for example, if the source STA can send traffic to the AP, which can then deliver it to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) a source STA and a destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may have no APs, and STAs within or using an IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.
[0039] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be of fixed width (e.g., 20 MHz wide bandwidth) or dynamically set via signaling. The primary channel may be the operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, for example in an 802.11 system, a carrier sense multiple access with collision avoidance (CSMA / CA) scheme may be implemented. With CSMA / CA, STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected by a particular STA and / or determined to be busy, the particular STA may back out. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0040] High throughput (HT) STAs may, for example, use a 40 MHz wide channel for communication via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0041] A Very High Throughput (VHT) STA may support channels of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz width. A 40 MHz channel and / or an 80 MHz channel may be formed by combining adjacent 20 MHz channels. A 160 MHz channel may be formed by combining eight adjacent 20 MHz channels or by combining two non-adjacent 80 MHz channels (which may be referred to as an 80+80 configuration). For the 80+80 configuration, the data may be passed through a segment parser after channel encoding, which may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped onto two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed and the combined data can be sent to the Medium Access Control (MAC).
[0042] Sub-1 GHz modes of operation are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter-type control / machine-type communication, such as MTC devices in macro coverage areas. MTC devices can have limited capabilities, including specific capabilities, such as support for (e.g., only support for) specific and / or limited bandwidths. MTC devices can include batteries with above-threshold battery life (e.g., to have a very long battery life).
[0043] A WLAN system capable of supporting multiple channels and channel bandwidths, e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah, includes a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA that supports the smallest bandwidth operating mode among all STAs operating in the BSS. In the 802.11ah example, for a STA (e.g., an MTC type device) that supports (e.g., only supports) the 1 MHz mode, the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) setting may depend on the status of the primary channel. If the primary channel is busy, for example due to STAs (that only support a 1 MHz mode of operation) transmitting to the AP, then the entire set of available frequency bands may be considered busy even though most of those frequency bands may remain idle and therefore available.
[0044] In the United States, the available frequency bands that can be used by 802.11ah are from 902MHz to 928MHz. In South Korea, the available frequency bands are from 917.5MHz to 923.5MHz. In Japan, the available frequency bands are from 916.5MHz to 927.5MHz. The total available bandwidth for 802.11ah is 6MHz to 26MHz depending on the country code.
[0045] 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.
[0046] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO techniques. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a, for example. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multipoint (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).
[0047] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or different lengths of absolute time duration).
[0048] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect to a gNB 180a, 180b, 180c while also communicating / connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0049] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, supporting network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.
[0050] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the above elements is shown as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0051] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling separate PDU sessions with separate requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service being utilized by the WTRUs 102a, 102b, 102c. For example, separate network slices may be established for separate use cases such as services relying on Ultra-Reliable Low Latency (URLLC) access, services relying on Enhanced Large Capacity Mobile Broadband (eMBB) access, services related to Machine Type Communications (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.
[0052] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0053] The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.
[0054] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.
[0055] 1A-1D and corresponding descriptions thereof, one or more or all of the functions described herein in connection with one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-ab, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.
[0056] The emulation device may be designed to perform one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the network. The one or more emulation devices may perform one or more or all functions while being temporarily implemented and / or deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may perform testing using over-the-air wireless communication.
[0057] The one or more emulation devices may perform one or more functions, including all functions, while not implemented and / or deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing laboratory and / or testing scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to perform testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used to transmit and / or receive data by the emulation devices.
[0058] A WLAN operating in an infrastructure basic service set (BSS) mode may include an access point (AP / PCP) for the BSS and one or more stations (STAs) associated with the AP / PCP. The AP / PCP typically has access to or interfaces with a distribution system (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic to a STA originating from outside the BSS may arrive through the AP / PCP and be distributed to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP / PCP for distribution to the respective destination. Traffic between STAs in a BSS may also be sent through the AP / PCP if the source station (STA) sends traffic to the AP / PCP, which distributes it to the destination STA. Such traffic between STAs in a BSS may be referred to as peer-to-peer traffic. Peer-to-peer traffic can also be sent directly between source and destination STAs using 802.11e Direct Link Setup (DLS) or 802.11z Tunneled DLS (TDLS). A WLAN operating in an Independent BSS (IBSS) mode does not include an AP / PCP and allows STAs to communicate directly with each other. This mode of communication can be referred to as an "ad-hoc" mode of communication.
[0059] Using the 802.11ac infrastructure mode of operation, an AP / PCP can transmit beacons on a fixed channel, usually the primary channel. This channel can be 20 MHz wide and can be the operating channel of the BSS. This channel can also be used by STAs to establish a connection with the AP / PCP. The basic channel access mechanism in 802.11 systems is Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). In this mode of operation, every STA (including the AP / PCP) will sense the primary channel. If the STA detects that the channel is busy, it will back out. Thus, only one STA can transmit in a given BSS at any given time.
[0060] 802.11ad is an amendment to the WLAN standard that specifies the MAC and physical (PHY) layers in the 60 GHz band.
[0061] 802.11ad supports data rates up to 7 Gbit / s, supports three different modulation modes including single carrier and control PHY with spread spectrum, single carrier PHY, and orthogonal frequency division multiplexing (OFDM) PHY, and uses the unlicensed band of 60 GHz that is available worldwide. At 60 GHz, the wavelength is 5 mm, which allows for compact antennas or antenna arrays. Such antennas can create narrow RF beams at both the transmitter and receiver, which effectively increases the coverage range and reduces interference.
[0062] FIG. 2 is a signal diagram illustrating an exemplary IEEE 802.11ad, beacon interval (BI) 200, including a beacon header interval (BHI) 210 and a data transmission interval (DTI). The BHI includes a beacon transmission interval (BTI) 210, an association beamforming training (A-BFT) interval 220, and an announcement transmission interval (ATI) 230. The BTI 210 includes multiple beacon frames, each of which is transmitted by the PCP / AP on a separate sector of its one or more antennas to cover all possible transmission directions. The BTI 210 can be used for network announcements and beamforming training of the PCP / AP's antenna sectors. Stations train their antenna sectors for communication with the PCP / AP during the A-BFT. The PCP / AP communicates management information to and from associated beam-trained stations during the ATI.
[0063] The BI 200 also includes a Data Transmission Interval (DTI) 240. The DTI 240 includes one or more Contention-Based Access Periods (CBAPs) and / or Scheduled Service Periods (SPs) during which stations exchange data frames. In each CBAP, multiple stations may contend for the channel according to the IEEE 802.11 Enhanced Distributed Coordination Function (EDCF). The Service Periods (SPs) can be allocated in the DTI as contention-free periods for communication between dedicated pairs of nodes.
[0064] The 802.11ad frame structure facilitates mechanisms for beamforming training (discovery and tracking). The beamforming training protocol can include two components: a Sector Level Sweep (SLS) procedure and a Beam Refinement Protocol (BRP) procedure. The SLS procedure can be used for transmit beamforming training, and the BRP procedure can be used for receive beamforming training and iterative refinement of both transmit and receive beams.
[0065] 3 is a signal diagram illustrating an example SLS training procedure 300 between an initiator 305 and a responder 310. The SLS training procedure 300 includes an initiator sector sweep (ISS) 315 and a responder sector sweep (RSS) 320. During the ISS 315, the initiator 305 transmits a sector sweep (SS) frame 325 to the responder 310, and during the RSS 320, the responder 310 transmits an SS frame 330 to the initiator 305. The SS frames 325 and 330 can be implemented using beacon frames or SSW frames. If a beacon frame is used for SLS training, the AP / PCP (in this case the initiator) can repeat the beacon frame across multiple beams / sectors within each beacon interval (BI), and multiple STAs (in this case the responders) can perform BF training simultaneously. However, due to the size of the beacon frame, it is not guaranteed that the AP / PCP can sweep all sectors / beams within one BI. Therefore, the STA may need to wait for multiple BIs to complete the Initial Sector Sweep (ISS) training, and latency may be an issue. The SSW frame can be utilized for point-to-point BF training and can be transmitted using the control PHY.
[0066] FIG. 4 is a bitmap illustrating an exemplary SSW frame format 400 by octets. The SSW frame format 400 includes a frame control field 410, a duration field 420, an RA field 430, a TA field 440, an SSW field 450, an SSW feedback field 460, and an FCS 470. FIG. 5 is a bitmap illustrating an exemplary SSW field format 500 by bits. The SSW field format 500 includes a direction field 510, a countdown (CDOWN) field 520, a sector ID field 530, a DMG antenna ID field 540, and an RXSS length field 550. The SSW field format 500 can be used for the SSW field 450 of the SSW frame format 400.
[0067] 6 is a bitmap illustrating an example SSW feedback field format 600 of an SSW frame in bits where the SSW frame is transmitted as part of an ISS. The SSW feedback field format 600 includes a "total sectors in ISS" field 610, a "number of RX DMG antennas" field 620, a reserved field 630, a "polling required" field 640, and a reserved field 650. The SSW feedback field format 600 can be used for the SSW feedback field 460 of the SSW frame format 400.
[0068] 7 is a bitmap illustrating an example SSW feedback field format 700 for an SSW frame where the SSW frame is not transmitted as part of an ISS. The SSW feedback field format 700 includes a sector selection field 710, a DMG antenna selection field 720, an SNR report field 730, a "poll required" field 740, and a reserved field 750. The SSW feedback field format 700 can be used for the SSW feedback field 460 of the SSW frame format 400. Beam refinement is a process by which a STA can improve its antenna configuration (e.g., antenna weight vector) for transmission and / or reception. In an exemplary beam refinement procedure, a BRP packet is used to train the receiver and transmitter antennas of the STA. There can be two types of BRP packets: BRP-RX packet and BRP-TX packet. A BRP packet can be carried by a Directional Multi-Gigabit (DMG) Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) followed by a training field that includes an automatic gain control (AGC) field and a transmitter or receiver training field. FIG. 8 is a block diagram illustrating an exemplary DMG PLCP PPDU 800 followed by a BRP MAC body 830, followed by an AGC 850, and followed by a BRP receive and / or transmit training (TRN-R / T) field 880. N represents the training length given in the header field 800, which indicates that the AGC field 850 has 4N subfields and the TRN-R / T field 880 has 5N subfields. Each subfield of the AGC field 850 may include five Golay sequences, and each Golay sequence may have a size of 64. Each subfield of the TRN-R / T field 880 may include a channel estimation (CE) subfield or five Golay sequences, and each Golay sequence may have a size of 128. The CE subfield 881 may be the same or similar to the preamble described in the previous section. All subfields in the TRN-R / T field 880 are transmitted using rotated π / 2-BPSK modulation.The BRP MAC body 830 is an Action No ACK frame that includes the following fields: category, unprotected DMG action, dialogue token, BRP request field, DMG beam refinement element, and fields for channel measurement feedback element 1 through channel measurement feedback element k.
[0069] 9 is a signal diagram illustrating an example SU-MIMO beamforming training procedure 900 between an initiator 905 and a responder 910. In an I-TXSS phase 920, the initiator 905 transmits short SSW frames 922, 924, ..., 926 to the responder 910. In an R-TXSS phase 930, the responder 910 transmits short SSW frames 932, 934, ..., 936 to the initiator 905. In a SISO feedback phase 940, the initiator 905 transmits a BRP frame 950 and the responder 910 transmits a BRP frame 960. The BRP frame 950 includes a CDOWN field indicating the best TX sector of the responder 910 based on the RX sector of the initiator 905 that best received the SSW frames 932, 934, ..., 936. The BRP frame 960 includes a CDOWN field that indicates the best TX sector of the initiator 905 based on the RX sector of the responder 910 that best received the SSW frames 922, 924, . . . , 926.
[0070] A first problem that may arise in multi-user MIMO (MU-MIMO) beamforming training is that when SSW or short SSW frames may be used as beamforming training frames, BRP frames may be used to feed back channel information for sector-level sweeps. This problem may be called the problem of BRP feedback without setup.
[0071] In some examples, beam refinement can be a request / response based process. In that case, the SSW or short SSW frame may not have the capability (e.g., no available field) to signal what feedback type is required or selected. Existing schemes require feedback of a countdown (CDOWN) value and the corresponding signal-to-noise ratio (SNR). Here, CDOWN is a subfield in some beamforming training frames that provides the countdown number so that the STA can determine how many training frames are left.
[0072] The feedback of the value of CDOWN and SNR may not provide the best feedback in terms of beamforming training overhead and / or MIMO throughput. Depending on the implementation, channel state information (CSI) that can be used to obtain a full / partial MIMO channel can be used for feedback. In that case, the subsequent MIMO training phase can be reduced (e.g., truncated) or not required.
[0073] A second problem may arise in MU-MIMO beamforming training when short SSW frames are used for Enhanced Directional Multi-Gigabit (EDMG) sector-level training, for example as defined in IEEE 802.11ay. This problem may be referred to as a short SSW frame problem for multi-channel sector-level training. Existing short SSW frame formats transmitted using control mode PPDUs do not carry channel bandwidth information. However, short SSW frames may be used for multi-channel sector-level training. Therefore, a mechanism for providing multi-channel information may be used.
[0074] A third problem may arise in MU-MIMO beamforming training when MU-MIMO user grouping may need to be performed before the MU-MIMO BF training procedure defined in the DTI due to the fact that in some embodiments, the AP / PCP may be required to send an EDMG group ID set element before performing the MU-MIMO beamforming protocol. This problem may be called the MU-MIMO user grouping problem. In this method, MU-MIMO grouping may be performed purely based on the SLS performed in the BTI, in which case the best beam / sector may be fed back from the STA to the AP by SSW or short SSW frame. However, the information on the best beam / sector may not be enough to minimize inter-user interference between MU-MIMO STAs.
[0075] A fourth problem that may arise in MU-MIMO beamforming training is that in some embodiments, if a responder is not ready to immediately respond to a BRP frame, it may send a Quality of Service (QoS) Null frame. This problem may be referred to as an Inter Frame Spacing (IFS) negotiation problem for BRP feedback. However, current QoS Null frames may be transmitted over a single channel. Therefore, an extension to support multi-channel BRP training may be selected.
[0076] The QoS Null frame may be repeated and transmitted before the BRP frame. In some embodiments, if a BRP feedback frame is ready to be transmitted during a QoS Null frame transmission, the responder may need to wait for the completion of the QoS Null frame before transmitting the BRP frame. In some embodiments, waiting for the completion of the QoS Null frame may not be efficient.
[0077] A fifth problem that may arise in MU-MIMO beamforming training is related to the BRP TXSS procedure. The BRP frame may be used for sector-level sweeping, and the BRP TXSS procedure may be defined for this purpose. However, in the BRP TXSS, which includes both the initiator TXSS and the responder TXSS, there is no mechanism to support more efficient training with antenna reciprocity. This may be referred to as the antenna reciprocity problem.
[0078] A sixth problem that may arise in MU-MIMO beamforming training is related to the SLS procedure. Figure 32 is a signal diagram illustrating an example SLS procedure 3200 including receive antenna indication. In this example, the initiator 3205 transmits an SSW frame to the responder 3210 during SSW 3220. The responder 3210 transmits an SSW frame to the initiator 3230 during SSW 3230. The responder 3210 selects the initiator's 3205 best Tx sector x based on its Rx antenna and / or RF chain 1. The responder 3210 indicates this sector to the initiator 3205 in a CDOWN field in the frame of the SSW 3230. However, the initiator 3205 selects the responder's best Tx sector y of antenna 2 based on its RX antenna and / or RF chain 2. The initiator 3205 indicates this sector to the responder 3210 in the CDOWN field in the SSW-FBCK frame 3240. The CDOWN field carried in the SSW frame and the SSW-FBCK frame 3240 does not indicate which receive antenna was used to select the transmit sector. This may result in a mismatch between the TX and RX antennas, causing the responder to have separate antennas for transmit and receive. This may be referred to as the antenna mismatch problem.
[0079] The responder 3210 may indicate in the SSW ACK frame the initiator's best Tx sector z on the responder's Rx antenna 2. However, if the SSW ACK is lost or encounters a collision, the initiator may repeat the transmission of the SSW feedback using Tx sector x, which may not be heard by the responder's antenna 2.
[0080] A MIMO training and setup approach can be used to address the issue of BRP feedback without setup and / or short SSW frames for multi-channel sector-level training.
[0081] In some embodiments, assuming that an EDMG STA can operate multiple receive (Rx) RF chains simultaneously, the beamforming (BF) control field in the extended schedule element of the grant or grant ACK frame can be extended to convey the training configuration for the assignment. For example, the BF control field can be extended to indicate that the SLS is to be performed as a single-input single-output (SISO) phase of MIMO training.
[0082] In a first example, if BF training is between two or more non-AP STAs and is set up through BTI, the AP can use a legacy or enhanced extended schedule element in the beacon frame to carry MIMO multi-channel BF training information and allocate a service period contention-based access period (SP / CBAP) to two (or more) non-AP STAs. The AP can determine and indicate that the SP / CBAP can be used for MIMO and / or multi-channel BF training. The extended schedule element can carry the type of BF training, feedback request, and / or other related information. The non-AP STAs can use this configuration to initiate an SLS in the SP.
[0083] In a second example, if BF training is between an AP and a non-AP STA over multiple channels and is set up through a BTI, the AP can use a legacy or enhanced extended schedule element in a beacon frame to carry MIMO multi-channel BF training information and allocate an SP / CBAP for communication between the AP and one or more non-AP STAs over one or more channels (e.g., including non-primary channels on which BF training may not be performed during a BTI). The AP can determine and indicate that an SP / CBAP can be used for MIMO and / or multi-channel BF training. The extended schedule element can carry the type of BF training, feedback request, and / or other related information. The non-AP STA can use this configuration for SLS in the SP.
[0084] In a third example, if BF training is between two or more non-AP STAs and is set up through the ATI, the AP can use the legacy or enhanced extended schedule element and / or grant frame in the ATI to carry MIMO multi-channel BF training information and allocate the SP / CBAP to the two (or more) non-AP STAs. Note that there can be multiple transmissions during the ATI. For example, the AP can transmit to a first STA using a trained directional transmission, and the STA can respond. The AP can then transmit to a second STA using a trained directional transmission, and the STA can respond. The AP can determine and indicate that the SP / CBAP can be used for MIMO and / or multi-channel BF training. The extended schedule element and / or grant frame in the ATI can include the type of BF training, a feedback request, and / or other related information. The non-AP STA can use this configuration to initiate an SLS in the SP.
[0085] In a fourth example, if BF training is between an AP and a non-AP STA over multiple channels and is set up through the ATI, the AP can use legacy or enhanced extended schedule elements and / or grant frames in the ATI to carry MIMO multi-channel BF training information and allocate an SP / CBAP for communication between the AP and one or more non-AP STAs over one or more channels (including non-primary channels where BF training may not be performed during the BTI). This transmission can be directional, using the BF sector / beam trained in the BTI over the primary channel. The AP can determine and indicate that the SP / CBAP can be used for MIMO and / or multi-channel BF training. The extended schedule elements and / or grant frames in the ATI can carry the type of BF training, feedback request, and other related information. The non-AP STA can use this configuration for SLS in the SP.
[0086] In a fifth example, if the BF training is between two or more non-AP STAs and is set up through DTI, the initiator of the SP / CBAP can use a grant frame at the beginning of the SP / CBAP to carry MIMO multi-channel BF training information. Note that in the CBAP case, the STA can acquire the channel through contention and become the initiator, while in the SP case, the STA can be allocated as the initiator. The responder can reply with a grant ACK frame to acknowledge receipt of the configuration. The initiator can then start the SLS training. Note that in this procedure, the initiator can determine and indicate that the SP / CBAP can be used for MIMO and / or multi-channel BF training. The grant frame can carry the type of BF training, feedback request, and other related information. It should be noted that, without excluding any other combinations, the fifth example can be combined with the first example, in which case the MIMO multi-channel BF training setup can be performed in both BTI and DTI. It should also be noted that, without excluding any other combinations, the fifth example can be combined with the third example, in which case the MIMO multi-channel BF training setup can be performed in both ATI and DTI.
[0087] In a sixth example, if BF training is between an AP and a non-AP STA over multiple channels and is set up through DTI, the AP can be the initiator of the SP / CBAP. In the CBAP case, the AP can acquire the channel through contention, while in the SP case, the AP can be assigned as the initiator. The AP can use grant frames in the SP / CBAP to carry MIMO multi-channel BF training information between the AP and one or more non-AP STAs over one or more channels (e.g., including non-primary channels where BF training may not be performed during BTI). The transmission of grant and grant ACK frames can be directional, using the BF sector / beam trained in the BTI over the primary channel, or a duplication mode over multiple channels. The AP can determine and indicate that the SP can be used for MIMO and / or multi-channel BF training. The grant / grant ACK frames can carry the type of BF training, feedback request, and other related information. Non-AP STAs can use this configuration for SLS in SP / CBAP. It should be noted that the sixth example can be combined with the second example, in which case the MIMO multi-channel BF training setup can be performed in both BTI and DTI, without excluding any other combinations. It should also be noted that the sixth example can be combined with the fourth example, in which case the MIMO multi-channel BF training setup can be performed in both ATI and DTI, without excluding any other combinations.
[0088] If the AP / PCP requests channel measurement feedback using the control trailer, extended schedule element, or EDMG extended schedule element of the grant frame, the BRP frame in the SISO feedback subphase of the SU-MIMO BF training procedure may include a list of channel measurements. The responder may send a BRP frame to the initiator only a short interframe space (SIFS) after receiving the BRP frame from the initiator, which may include a list of CDOWN values and SNRs of the transmitting sectors received during the last initiator transmit sector sweep (TXSS). If the AP / PCP requests channel measurement feedback using the control trailer, extended schedule element, or EDMG extended schedule element of the grant frame, the BRP frame may also include a list of channel measurements. If the channel number / index used for TXSS is carried by the grant frame, extended schedule element, or EDMG extended schedule element, the feedback may be based on measurements on the channel indicated by that channel number / index.
[0089] If the SISO feedback subphase of the SU-MIMO BF training procedure provides channel measurement feedback, the MIMO subphase may be omitted. If the No-rep TXSS field is set to 1 in the grant frame, extended schedule element, or EDMG extended schedule element, the initiator TXSS and responder TXSS may be performed as if the last negotiated "Number of RX DMG antennas" field was equal to 1 from both the initiator and the responder.
[0090] 10 is a bitmap illustrating an example modified BF control field format 1000. The BF control field format 1000 includes a Beamforming Training subfield 1010, an IsInitiatorTXSS subfield 1020, an IsResponderTXSS subfield 1030, an RXSS Length subfield 1040, an RXSSTxRate subfield 1050, a "Requested Channel Measurements" subfield 1060, a "Number of Taps Requested" subfield 1070, a TXSS Channel Index subfield 1080, and a No-rep TXSS subfield 1090.
[0091] The BF control field format 1000 can be used, for example, when both the IsInitiatorTXSS subfield 1020 and the IsResponderTXSS subfield 1030 are equal to 1, when the Beamforming Training subfield 1010 is equal to 1, and / or when a BF control field is transmitted in an assignment field. When a BF control field having the format 1000 is transmitted in an assignment field and when both the IsInitiatorTXSS 1020 and the IsResponderTXSS 1030 subfields are equal to 1, and / or when the Beamforming Training field 1010 is equal to 1, the "Requested Channel Measurements" subfield 1060 can be set to 1 to indicate that the channel measurements subfield is requested as part of the MIMO BF training feedback in the SISO phase. Otherwise, the "Requested Channel Measurements" subfield 1060 is set to 0. It should be noted here that throughout this specification, bit values are exemplary. In different examples, any suitable bit mapping or combination of bits can be used to convey the desired information. For example, a bit depicted as being set to 1 to represent particular information in an exemplary embodiment can be set to 0 to represent the same information in other embodiments.
[0092] If a BF control field having format 1000 is transmitted in the assignment field and if both the IsInitiatorTXSS subfield 1020 and the IsResponderTXSS subfield 1030 are equal to 1 and if the beamforming training field 1010 is equal to 1, the "Number of Taps Requested" subfield 1070 may be set to the number of taps requested in the respective channel measurement. This subfield may be reserved if the "Channel Measurements Requested" 1060 subfield is set to 0.
[0093] If a BF control field having format 1000 is transmitted in the assignment field, and if both the IsInitiatorTXSS subfield 1020 and the IsResponderTXSS subfield 1030 are equal to 1, and if the beamforming training field is equal to 1, then the TXSS channel index subfield 1080 having a value of i indicates that the i+1 lowest channel number of the assignment may be the channel used for TXSS.
[0094] If the BF control field is transmitted in the assignment field and if both the IsInitiatorTXSS subfield 1020 and the IsResponderTXSS subfield 1030 are equal to 1 and if the beamforming training field 1010 is equal to 1, the No-rep TXSS subfield 1090 can be set to 1 to indicate that TXSS will be performed as if the last negotiated "Number of RX DMG Antennas" field was equal to 1 from both the initiator and the responder. Otherwise, the No-rep TXSS subfield 1090 is set to 0.
[0095] Note that the number of bits and the starting bit of the modified BF control field format 1000 may not be exactly the same as shown in Figure 10. The modified BF control field format 1000 may be used for grant frames, SPR frames, extended schedule elements, and / or DMG TSPEC elements.
[0096] Note that if the bit of the No-rep TXSS subfield 1090 is set to 1 in a Grant and / or Grant ACK frame, the "Number of RX DMG Antennas" field originally included in the Grant and / or Grant ACK frame may be ignored or reserved. The bit of the No-rep TXSS subfield 1090 may be used by the AP or initiator to indicate that the TXSS may not be repeated for the RX antennas regardless of how many RX antennas are available at the STA or responder side.
[0097] Note that instead of using the TXSS channel index, an AP or STA can set the BW field to indicate a single 2.16 GHz channel if the BF control field 1000 has the Beamforming Training field 1010 set to 1. This can avoid ambiguity as to which channel the SLS is scheduled / requested on.
[0098] In some embodiments, modified control trailers may be used. For example, Figure 11 is a table describing exemplary fields that may be added to the control trailer. Note that the number of bits and the start bit may not be exactly the same as shown in the table of Figure 11. The control trailer fields described above may be used, for example, in grant frames, SPR frames, RTS frames, and / or CTS-2-Self frames with a control trailer.
[0099] In some embodiments, a modified BRP frame may be used. By using the modified BRP frame, it may be possible to add bandwidth indication and / or channel number information in the BRP frame. Exemplary modifications may include a channel indication / bandwidth indication for a feedback request, or a channel indication / bandwidth indication for a feedback type.
[0100] 12 is a bitmap illustrating an example modified DMG beam refinement element format 1200. The DMG beam refinement element format 1200 includes an element ID field 1203, a length field 1205, an initiator field 1207, a TX training response field 1210, an RX training response field 1213, a TX-TRN-OK field 1215, a TXSS-FBCK-REQ field 1217, a BS-FBCK field 1220, a BS-FBCK antenna ID field 1223, an FBCK-REQ field 1225, an FBCK-TYPE field 1227, a MID extension field 1230, a capability request field 1233, an FBCK-REQ-BW field 1235, a BS-FBCK MSB field 1237, a BS-FBCK antenna ID includes an MSB field 1240, a number of measurements MSB 1243, an EDMG extension flags field 1245, an "EDMG channel measurements present" field 1247, a "Short SSW packets in use" field 1250, a BRP-TXSS-OK field 1253, a BRP-TXSS response field 1255, and an FBCK-TYPE-BW field 1257.
[0101] The DMG Beam Refinement elements in the BRP frame can be modified in one or more of the following ways: FBCK-REQ-BW 1235 can be used to indicate the channel index or bandwidth indication requested for feedback. FBCK-TYPE-BW 1257 can be used to indicate the channel index or bandwidth indication for the feedback conveyed in the current BRP frame. In some embodiments, the information can be carried in two elements / fields, e.g., the channel indication / bandwidth indication for the feedback request can be carried in the EDMG BRP Request element and the channel indication / bandwidth indication for the feedback type can be carried in the EDMG Channel Measurement Feedback element. In some embodiments, the channel indication / bandwidth indication can be added to the beginning of the element immediately after the Element ID extension field.
[0102] The BRP frame can additionally or alternatively be modified to include a No-rep TXSS field. No-rep TXSS can be set to 1 to indicate that TXSS should be performed as if the last negotiated "Number of RX DMG Antennas" field was equal to 1 from both the initiator and the responder. Otherwise, No-rep TXSS can be set to 0. This field (e.g., bit) in the BRP frame can be used to enable the setup for the BRP TXSS procedure, in which the BRP frame can be used to set up the TXSS procedure.
[0103] Some embodiments provide a MIMO training procedure with full CSI feedback. In some embodiments, which assume that MIMO multi-channel BF setup can be performed in BTI, ATI, or grant / grant ACK frames in DTI, CSI or channel measurements can be required. In this case, a simplified MIMO BF training procedure can be applied.
[0104] 13 is a signal diagram illustrating a simplified exemplary MIMO BF training procedure 1300 between an initiator 1305 and a responder 1310. The exemplary procedure includes a setup sub-phase, an initiator TXSS (I-TXSS) sub-phase 1335, a responder (R-TXSS) sub-phase 1355, and a SISO feedback sub-phase 1375.
[0105] In the setup subphase, the initiator may acquire the medium using a MIMO BF training setup by the AP using a scheduling element such as an extended schedule element. Alternatively, the initiator may set up the MIMO BF training using a grant or a grant-like frame before the MIMO BF training. An exemplary detailed MIMO BF setup procedure is described above with respect to the MIMO training setup. For example, an exemplary setup may include the following: In the extended schedule element, the BF control field may be set as follows: Both the IsInitiatorTXSS and IsResponderTXSS subfields may be set to 1, and the "requested channel measurement" subfield may be set to 1 to indicate that the channel measurement subfield is requested as part of the MIMO BF training feedback in the SISO phase. The "number of requested taps" subfield may be set to the number of taps requested in the respective channel measurement. The No-rep TXSS field may be set to 1 to indicate that the receiver does not need to repeat the TXSS to make changes and train another receive antenna. As an alternative to the extended schedule element setting, in the grant frame, the control trailer can be set as follows: The IsInitiatorTXSS and IsResponderTXSS subfields can both be set to 1. The "Channel Measurements Requested" field can be set to 1 to indicate that the channel measurements subfield is requested. The "Number of Taps Requested" subfield can be set to the number of taps requested in each channel measurement. The No-rep TXSS can be set to 1 to indicate that the receiver does not need to repeat the TXSS to make changes and train another receive antenna.
[0106] Alternatively, the setup subphase can be performed as follows: STAs that may be able to perform MIMO reception can use the complete RF chain for reception in case of BF training, e.g., if CSI feedback is requested by the initiator. The initiator can set up the MIMO BF training details in the training procedure, e.g., using SSW frames, short SSW frames, and / or BRP frames.
[0107] In the I-TXSS subphase 1335, the initiator 1305 can start an initiator sector level sweep by transmitting short SSW frames 1337, 1340, ..., 1343 using separate antennas and beams. The initiator 1305 can choose trained beams that are orthogonal. The initiator 1305 and / or the responder 1310 can use channel measurements to reconstruct the physical channel. In some embodiments, a field (e.g., a bit) in the short SSW frames 1337, 1340, ..., 1343 can be used to indicate the feedback type being requested. For example, if the bit is set to 1, it can indicate SNR feedback, while if the bit is set to 0, it can indicate full channel state information (CSI) feedback. In some embodiments, the MIMO multi-channel BF setup can be performed before the I-TXSS subphase 1335, and detailed feedback requests can be set up between the initiator 1305 and the responder 1310. A predefined interframe spacing is used between the short SSW frames 1337, 1340, ..., 1343 in each subphase. In this example, short interframe spacing (SIFS) is shown, but any suitable predefined interframe spacing can be used.
[0108] The responder 1310 may receive the I-TXSS short SSW frames 1337, 1340, ..., 1343 transmitted from the initiator 1305. In some embodiments, the responder may identify the I-TXSS short SSW frames 1337, 1340, ..., 1343 that are intended for MIMO BF training (e.g., through MIMO training setup in the BTI, ATI, and / or DTI). Thus, the responder 1310 may use all (or some) receive chains for reception. In some embodiments, the responder 1310 may not train its receive beam during MIMO BF training and may use a quasi-omni beam for reception. For example, a quasi-omni beam may be formed on each RF chain. In some embodiments, the responder 1310 may have trained its receive beam before MIMO BF training, and thus it may use the trained beam for reception. For each short SSW frame 1337, 1340, ..., 1343, the responder 1310 can use all (or some) of its receive chains to measure the observed channel (i.e., the channel between the transmitter and the receiver using the corresponding Tx and Rx beams). If time domain channel measurements are utilized, Ntap channel measurements can be obtained for the multi-tap channel for each receive chain. Thus, for N consecutive short SSW frames and Nr receive chains, the responder 1310 can have NxNrxNtap channel measurements. The responder 1310 can prepare to feed back the channel measurements to the initiator 1305.Alternatively, if the responder 1310 identifies the transmit beam used at the initiator side, the responder 1310 can reconstruct N×Nr physical MIMO channels between the initiator and the responder 1310, thereby obtaining up to Nr beamforming weights. Each beamforming weight can include Nt_element complex values, where Nt_element can be the total number of antenna elements supported at the initiator side. Here, for exemplary purposes, it can be assumed that there are Nt transmit antennas at the initiator side, where each transmit antenna can support multiple antenna elements. Thus, Nt_element≧Nt. To accurately acquire the complete channel, the number of training frames, e.g., short SSW frames, transmitted, N, can be equal to or greater than Nt. The responder 1310 can feed back the Nr beamforming weights. In some embodiments, the responder 1310 may feedback a set of Nr phase shifters obtained by the Nr beamforming weights. The phase shifters may include the phases of the respective complex values in the beamforming weights.
[0109] In the R-TXSS subphase 1355, the responder 1310 may start a responder sector level sweep by transmitting short SSW frames 1360, ..., 1363 using separate antennas and beams. The initiator 1305 may choose trained beams that are orthogonal. Thus, the initiator and / or the responder 1310 may use channel measurements to reconstruct the physical channel. In some embodiments, the procedures of the responder 1310 and the initiator 1305 in the R-TXSS may be the same as those of the initiator 1305 and the responder 1310 in the I-TXSS, respectively. In some embodiments, the responder 1310 may not train the response link using sweeping multiple responder beams, but instead may transmit one short SSW frame 1357 to the initiator 1305 to feed back the best TX beam observed in the previous I-TXSS. In the short SSW frame, the responder can indicate the best SISO sector observed in the previous I-TXSS, which can allow the next transmission from the initiator 1305 to the responder 1310 to be directional. Between each subphase (e.g., between the short SSWs 1343 and 1357), a predefined interframe spacing is used. In this example, medium beamforming interframe spacing (MBIFS) is shown, but any suitable predefined interframe spacing can be used.
[0110] In the SISO feedback subphase 1375, the initiator 1305 may transmit a BRP frame 1380 to the responder. The BRP frame may be transmitted using the SISO sectors fed back from the previously received short SSW frames 1357, 1360, ..., 1363 in the R-TXSS subphase 1355. The initiator 1305 may identify that CSI or channel measurements are requested by the responder 1310 through the MIMO training setup. Some or all of the following information may be carried in the BRP frame 1380: the requested channel measurements, the best SISO sector / antenna observed in the R-TXSS, a channel measurement feedback element (in which the measured channel or processed precoding weights may be fed back), and / or an EDMG channel measurement feedback element. The responder 1310 may transmit a BRP frame 1390 to the initiator. The BRP frame 1390 can be transmitted using SISO sectors fed back from a previously received BRP frame 1380 sent from the initiator 1305. The responder 1310 can identify that CSI or channel measurements are requested by the initiator 1305 through a MIMO training setup or a previously received BRP frame 1380 sent from the initiator 1305. Some or all of the following information can be carried in the BRP frame 1390: a channel measurement feedback element (in which the measured channel or processed precoding weights can be fed back), an EDMG channel measurement feedback element.
[0111] After the above-mentioned MIMO BF training, the initiator 1305 can obtain (e.g., from feedback) a set of weights that can be used to provide a higher rank MIMO transmission. The initiator 1305 can decide based on the feedback to skip the MIMO phase training and directly perform the MIMO transmission (e.g., if the weights are sufficient to provide a high rank (e.g., multiple data stream) communication between the initiator 1305 and the responder 1310). The responder 1310 can use a quasi-omni mode on all of its receive antennas to receive the MIMO transmission if they have not been previously trained.
[0112] In some embodiments, the initiator 1305 and the responder 1310 can decide to perform MIMO training to train directional receive beams. In some embodiments, the responder 1310 can suggest further MIMO training in the BRP feedback phase. In some embodiments, the initiator 1305 can decide whether to perform further MIMO training based on feedback from the responder 1310. For MIMO training, the initiator 1305 can select a set of TX beams or a set of TX combinations (i.e., a set of TX beams and AVWs), which can be formed by a set of amplitude vector weights (AVWs). The AVWs can be a subset of the beams used for SLS or not. For example, the AVWs can be formed by performing singular value decomposition (SVD) on the obtained MIMO channel. The initiator 1305 can repeat transmitting the selected TX beam combinations using the MIMO phase, whereby the responder 1310 can perform a sweep using the set of receive beams. The responder 1310 may select one or a set of the responder beams for further MIMO reception. In some embodiments, the responder 1310 may choose to sweep a set of orthogonal receive beams. By measuring the channel response using the receive beams, the responder 1310 may obtain Nt×Nr_component channels, where Nr_component may be the total number of receive antenna elements. A receive antenna weight vector (AWV) may be formed by using the Nt×Nr_component channels, for example, by performing SVD on the channels to obtain a set of AWVs.
[0113] Procedures may be provided to enable SLS on multiple channels. Both short SSW frames and SSW frames may be transmitted with the control mode. The control mode may not be able to indicate the bandwidth. MIMO training setup may be required to enable SLS with SSW and / or short SSW frames on non-primary channels.
[0114] During TXSS, and if the channel used for TXSS is provided by a grant frame, Extended Schedule element, or EDMG Extended Schedule element, the initiator and responder may send SSW or short SSW frames on the channel. The initiator may send duplicate SSW or short SSW frames on channels in addition to the channel used for TXSS if duplicate transmissions are required by the DMG channel access rules.
[0115] 14 is a signal diagram illustrating an example SLS procedure 1400 on a secondary channel. In this example, channel 1 (Ch1) is the primary channel and channel 2 (Ch2) is the secondary channel.
[0116] An initiator 1405, which may be an AP, may set up a MIMO multi-channel BF training in a beacon header interval 1415 including a BTI or ATI by using modified frames, fields, and signaling such as those described above. In this example, the initiator 1405 may indicate an SLS allocation using a short SSW frame in Ch2. Exemplary setup information may be included in an extended schedule element or in a grant frame. In an extended schedule element, the BF control field may be set as follows: Both IsInitiatorTXSS and IsResponderTXSS subfields may be set to 1, and the TXSS channel index field may be set to a channel index. In this example, the channel index may indicate Ch2. In a grant frame, the control trailer may be set as follows: Both IsInitiatorTXSS and IsResponderTXSS subfields may be set to 1, and the TXSS channel index field may be set to a channel index. In this example, the channel index may indicate Ch2.
[0117] The initiator 1405 may perform I-TXSS 1420 on Ch2 while the responder 1410 may receive I-TXSS 1420 on Ch2. The responder 1410 may perform R-TXSS 1425 on Ch2 while the initiator 1405 may receive R-TXSS 1425 on Ch2. Note that in the SSW frame or short SSW frame transmitted in R-TXSS 1425, the best TX sector / antenna observed in the previous I-TXSS 1420 may be included and fed back to the initiator 1405. The feedback information may be measured on the same channel on which the SSW frame or short SSW frame may be transmitted. In this example, the short SSW frame may be transmitted via Ch2, and thus the feedback information may be measured based on Ch2.
[0118] In the feedback subphase 1430, in some embodiments, the initiator 1405 can transmit an SSW feedback frame (in this example, a BRP frame 1435) to the responder, and the responder can transmit an SSW ACK frame (in this example, a BRP frame 1440) to the initiator. Using these frame exchanges, feedback information can be measured on the same channel on which the SSW frame or short SSW frame can be transmitted. In this example, the short SSW frame can be transmitted over Ch2, and thus the feedback information can be measured based on Ch2. For SISO feedback, the initiator 1405 can transmit the SSW feedback frame as a BRP frame 1435 to the responder 1410, and the responder 1410 can transmit the SSW feedback frame as a BRP frame 1440 to the initiator. The transmission of the BRP frame may be performed on a primary channel (Ch1), and the feedback information may be measured on another channel, for example Ch2.
[0119] In the procedure 1400, the initiator 1405 may be an AP. However, in some embodiments, the procedure may be performed using two non-AP STAs. In that case, the AP may set up MIMO training on the secondary channel using BTI or ATI, while the non-AP STA may be the initiator and responder. In some embodiments, the SLS for multiple channels may be performed using the BRP TXSS procedure, for example, as defined in IEEE 802.11ay, with one or more of the following modifications. In a BRP frame that may be used to set up the BRP TXSS, a Feedback Req BW and / or Feedback Type BW field may be included to indicate the channel number or the bandwidth of the channel measurement or SNR measured and reported in the feedback. In a BRP frame that may be used for BRP TXSS training, a Feedback Req BW and / or Feedback Type BW field may be included to indicate the channel number or the bandwidth of the channel measurement or SNR measured and reported in the feedback. The BRP frame may be transmitted using a duplication mode on multiple channels. On the primary channel, the BRP frame may be transmitted using a trained directional beam (if available). On one or more non-primary channels, the BRP frame may be transmitted using a quasi-omni-directional direction if SLS / beamforming training has not been previously performed. The training (TRN) field may be added using channel bonding or channel aggregation. The responder may receive the BRP frame on the primary channel and perform channel measurements using the TRN field on the channel indicated in the feedback Req BW field.In a BRP frame that may be used to carry BRP TXSS feedback, a Feedback Req BW and / or Feedback Type BW field may be included to indicate the channel number or bandwidth of the channel measurement or SNR measured and reported in the feedback.
[0120] For example, an SLS-based MU MIMO grouping mechanism can be provided to address the problem of MU-MIMO user grouping. For example, an AP can send an EDMG group management ID before performing MIMO BF training. Thus, the AP may need more information to determine which STAs can be grouped. For this example, it can be assumed that the AP can have performed SLS with the STAs and can group users based on feedback from the SLS training. In some examples, in cases where SLS can be performed using SSW frames and feedback may be using SSW frames with SSW feedback fields, the sector sweep feedback field can be modified to carry worst sector information, for example, as shown in FIG. 15.
[0121] 15 is a bitmap illustrating an example sector sweep feedback field 1500. The sector sweep feedback field 1500 includes a sector selection field 1505, a DMG antenna selection field 1510, an SNR report field 1515, a "poll required" field 1520, and a sector selection MSB field 1525, a reserved field 1530, and an EDMG extension flags field 1535.
[0122] As shown in FIG. 15, in the case where the EDMG extension flags field 1535 is set to 0, a 6-bit weak sector field 1540 that replaces the sector selection MSB field 1525 and the reserved field 1530 can be indicated in the SSW feedback field 1500. The weak sector field 1540 can indicate, for example, a sector where the STA is sensing negligible energy (e.g., below a threshold). The AP can use this sector to transmit to other STAs, and the STA can observe no significant interference. Having this information at the AP side can facilitate the AP to group users and / or minimize interference between them.
[0123] In some exemplary embodiments, in a beamforming training assignment procedure, e.g., as defined in IEEE 802.11ay, the best transmitting sector for each STA may be implicitly indicated by a slot-based feedback transmission.
[0124] For example, if a STA transmits in a slot associated with SectorID=K, it may implicitly indicate that TX sector K is the best sector for that STA (e.g., based on STA measurements). In some embodiments, an SSW frame or short SSW frame may be used as a feedback frame. Thus, the Sector ID field in the SSW or short SSW frame in a beamforming SP may be reinterpreted as the weak sector suggested by the STA. Alternatively, the Sector ID field in the SSW or short SSW frame in a beamforming SP may be reinterpreted as the second strongest sector suggested by the STA.
[0125] FIG. 16 is a signal diagram showing beamforming training for asymmetric links in a beamforming training assignment during beamforming SP 1600. During SP 1600, EDMG AP / PCP 1650 scans for SSWs on each of its receive antenna sectors. For example, during slot 1605, EDMG AP / PCP 1650 scans on sector 0 (SectorID=0) in each of several space time slots 1606, 1607, 1608, 1609. During slot 1605, EDMG STA 1660 transmits short SSW 1620 using its selected transmit sector. During space time slot 1607, the transmit antenna pattern of EDMG STA 1660 is aligned with the receive antenna pattern of EDMG AP / PCP 1650 receiving short SSW 1620 (i.e., slot 0 in this example).
[0126] Similarly, during slot 1625, the EDMG AP / PCP 1650 scans on sector 1 (SectorID=1) in each of several space time slots 1626, 1627, 1628, 1629. In some examples, slot 1625 starts one short beamforming interframe space (SBIFS) after slot 1605 ends. During slot 1625, the EDMG STA 1660 transmits the short SSW 1630 on its selected transmit sector. During space time slot 1626, the transmit antenna pattern of the EDMG STA 1670 is aligned with the receive antenna pattern of the EDMG AP / PCP 1650 receiving the short SSW 1630 (i.e., slot 1 in this example).
[0127] The EDMG AP / PCP 1650 continues scanning on its other sectors until the ACK slot 1640. During the ACK slot 1640, the EDMG AP / PCP 1650 transmits short SSW ACK signals for each of its sectors in space time slots 1641, 1642, 1643, 1644, ..., 1645, 1646. For example, the EDMG AP / PCP 1650 transmits a short SSW ACK signal 1647 to the EDMG STA 1660 during slot 1641 acknowledging receipt of the short SSW 1620. During the ACK slot 1640, the EDMG STA 1660 is receiving on its strongest beam 1690, which is the receive beam that corresponds to the transmit beam used to transmit the short SSW frame 1620. Receiving a short SSW ACK signal 1647 by an EDMG STA 1660 during slot 1641 implies that the strongest transmitting sector of the EDMG STA 1660 is the transmitting sector from which it transmitted the short SSW 1620. Since the strongest transmitting sector is implied, the sector ID field in the short SSW frame 1620 can be used to signal the weak sector, or the second strongest sector, or other information implied by the EDMG STA 1660.
[0128] Similarly, the EDMG AP / PCP 1650 transmits a short SSW ACK signal 1648 to the EDMG STA 1670 during slot 1642 acknowledging receipt of the short SSW 1630. During the ACK slot 1640, the EDMG STA 1670 is receiving on its strongest beam 1695, which is the receive beam that corresponds to the transmit beam used to transmit the short SSW frame 1630. Receiving the short SSW ACK signal 1648 by the EDMG STA 1670 during slot 1642 implies that the strongest transmitting sector of the EDMG STA 1670 is the transmitting sector from which it transmitted the short SSW 1630. Since the strongest transmitting sector is implied, the sector ID field in the short SSW frame 1630 can be used to signal the weak sector, or second strongest sector, or other information implied by the EDMG STA 1670.
[0129] In some examples, IFS negotiation may be provided to address the BRP feedback issue discussed above. In some embodiments, QoS Null frames may be transmitted using a duplicate control mode to enable transmission. For example, to enable a non-enhanced directional multi-gigabit (non-EDMG) duplicate control mode, a physical layer (PHY) transmission format may be provided that duplicates a 2.16 GHz non-EDMG transmission in two or more 2.16 GHz channels and allows stations (STAs) in a non-EDMG basic service set (BSS) on any one of those 2.16 MHz channels to receive the transmission, so that STAs that may be able to sense on a single channel understand the transmission. If the AP supports multiple channels, the duplicate transmission may duplicate a transmission on the primary channel. Exemplary non-EDMG duplication formats may include one of the following: 4.32 GHz non-EDMG duplication: A PHY transmission format that duplicates a 2.16 GHz non-EDMG transmission in two adjacent 2.16 GHz channels. 6.48GHz Non-EDMG Duplication: A PHY transmission format in which the 2.16GHz non-EDMG transmission is duplicated in three adjacent 2.16GHz channels. 8.64GHz Non-EDMG Duplication: A PHY transmission format in which the 2.16GHz non-EDMG transmission is duplicated in four adjacent 2.16GHz channels. 2.16+2.16GHz Non-EDMG Duplication: A PHY transmission format in which the 2.16GHz non-EDMG transmission is duplicated in two frequency segments of one 2.16GHz channel. 4.32+4.32GHz Non-EDMG Duplication: A PHY transmission format in which the 2.16GHz non-EDMG transmission is duplicated in two frequency segments of two adjacent 2.16GHz channels, where the two frequency segments of the channel are not necessarily adjacent.
[0130] In some embodiments, an EDMG STA transmitting an RTS frame addressed to an EDMG STA and carried in a non-EDMG duplicated format will set the TXVECTOR parameter CH_BANDWIDTH to the selected channel bandwidth. To provide complete bandwidth signaling information and MIMO indication, an EDMG STA may include a control trailer in the transmitted RTS frame.
[0131] To provide further control signaling, a control trailer may be inserted into the control mode PPDU. The EDMG STA will set the TXVECTOR parameter CONTROL_TRAILER to "Yes" to indicate the presence of a control trailer in the control mode PPDU, and may set the TXVECTOR parameter CT_TYPE to indicate the type of control trailer that will be included in the PPDU.
[0132] In some examples, for example, to address the IFS negotiation issue with BRP feedback discussed above, a QoS Null frame can be followed by multiple delimiters, followed by a feedback (FB) frame. When performing BRP, if the responding STA needs more than SIFS to send a BRP frame in response to a beam refinement training request from the requesting STA, the responding STA can keep the IFS below the Beam Refinement Protocol Inter Frame Spacing (BRPIFS) by sending one or more PPDUs to the requesting STA. This can also be done to prevent the beam link maintenance timer from expiring when the DMG STA has no MSDUs to send. In this case, the DMG STA can send a QoS Null frame to maintain the beamformed link. Each QOS Null frame can be at least 30 octets in size (e.g., FIG. 17 and FIG. 18). To reduce delay quantization, rather than the legacy method in which repeated QOS Null frames would be sent, multiple DMG MPDU delimiters of size 4 octets can be sent after the QOS Null frame until the information is ready to be transmitted.
[0133] 17 is a bitmap illustrating an exemplary data frame 1700. The exemplary data frame 1700 includes a frame control field 1705, a duration field 1710, an address 1 field 1715, an address 2 field 1720, an address 3 field 1725, a sequence control field 1730, an address 4 field 1735, a QoS control field 1740, an HT control field 1745, and an FCS field 1755. In this example, the frame control field 1705, the duration field 1710, the address 1 field 1715, the address 2 field 1720, the address 3 field 1725, and the sequence control field 1730 are present in all data frame subtypes. The presence of the address 4 field 1735 is determined by the settings of the "to DS" and "from DS" subfields of the frame control field 1705. The presence or absence of the QoS control field 1740 is determined based on the QoS subfield of the subtype of the frame control field 1705 (e.g., if that QoS subfield is set to 1). The frame control field 1705, duration field 1710, address 1 field 1715, address 2 field 1720, address 3 field 1725, sequence control field 1730, address 4 field 1735, QoS control field 1740, and HT control field 1745 make up the MAC header of the data frame 1700.
[0134] 18 is a bitmap illustrating an exemplary QoS Data frame 1800 and an exemplary QoS Null frame 1850. The exemplary QoS Data frame 1800 includes a TID field 1805, an EOSP field 1810, an ACK policy field 1815, an “A-MSDUs present” field 1820, an A-MSDU type field 1825, an “RDG / More PPDUs” field 1830, an “ACs buffered” field 1835, a reserved field 1840, and an AC constraints field 1845. The exemplary QoS Null frame 1850 includes a TID field 1805, an EOSP field 1810, an ACK policy field 1815, a reserved field 1855, a reserved field 1860, an “RDG / More PPDUs” field 1830, an “ACs buffered” field 1835, a reserved field 1840, and an AC constraints field 1845.
[0135] The MPDU delimiter may be four octets long. Figure 19 is a bitmap showing an example MPDU delimiter field 1900 that represents an example structure for the MPDU delimiter field when transmitted by a DMG or EDMG STA. The MPDU delimiter field 1900 includes a reserved field 1905, an MPDU length field 1910, a cyclic redundancy check (CRC) field 1915, and a delimiter signature field 1920. In this example, the MPDU length field 1910 may be set to zero for delimiters that are placeholders.
[0136] FIG. 20 is a signal diagram illustrating an example overhead savings that can be achieved using delimiters during a BRP. In this example, the overhead savings represents a reduction in the amount of time a STA needs to unnecessarily reserve the medium. In a first procedure 2000, a QoS Null frame 2010 is transmitted by the responding STA. In this example, the QoS Null frame 2010 is 30 octets long. In this example, the responding STA does not yet have BRP feedback available to transmit after transmitting the QoS Null frame 2010. Thus, a second QoS Null frame 2020 is transmitted by the responding STA. The second QoS Null frame 2020 is also 30 octets long. In this example, BRP feedback information becomes available for the responding STA to transmit during the transmission of the QoS Null frame 2020. Thus, a BRP feedback 2030 is transmitted by the responding STA following the QoS Null frame 2020.
[0137] In a second procedure 2050, a QoS Null frame 2060 is transmitted by the responding STA. In this example, the QoS Null frame 2060 is 30 octets long. In this example, the responding STA does not yet have BRP feedback available to send after transmitting the QoS Null frame 2060. Therefore, a DMG MPDU delimiter 2070 is transmitted by the responding STA. The DMG MPDU delimiter 2070 is 4 octets long. In this example, the responding STA does not yet have BRP feedback available to send after transmitting the QoS Null frame 2060. Therefore, a DMG MPDU delimiter 2080 is transmitted by the responding STA. The DMG MPDU delimiter 2080 is also 4 octets long. In this example, the BRP feedback information becomes available for the responding STA to send during the transmission of the DMG MPDU delimiter 2080. Thus, the BRP feedback 2090 is sent by the responding STA following the DMG MPDU delimiter 2080 .
[0138] In the exemplary procedure 2050, the responding STA sends an initial QOS NULL, then an A-MPDU delimiter thereafter until the feedback information is ready to be sent. Thus, the responding STA starts sending BRP feedback 22 octets earlier in procedure 2050 compared to procedure 2000. This illustrates the advantage of using the DMG MPDU delimiter in this method.
[0139] In some examples, a DMG MPDU delimiter transmitted before a BRP feedback transmission may indicate that the upcoming transmission is a non-zero packet.
[0140] 21A and 21B are signal diagrams illustrating an example modified BRP TXSS procedure 2100 between an initiator 2105 and a responder 2110. A BRP frame 2115 can be sent from the initiator 2105 to the responder 2110 to set up the BRP TXSS. The BRP frame 2115 can include two fields: TXSS-RECIPROCAL and TXSS-RESPONDER. If the TXSS-RECIPROCAL subfield in the EDMG BRP request element of the same frame is set to 1 and the TXSS-RESPONDER subfield in the EDMG BRP request element of the BRP frame initiating the BRP TXSS is equal to 1, the procedure using channel reciprocity can be applied. The procedure may include an initiator BRP TXSS and a responder BRP TXSS if the TXSS-RESPONDER subfield in the EDMG BRP request element of the BRP frame initiating the BRP TXSS is equal to 1, which is assumed for this example. The BRP frame 2120 conveys setup information from the responder 2110 to the initiator 2105 using the same or similar fields as the BRP frame 2115.
[0141] In the initiator TXSS, the responder 2110 can receive on multiple RX antennas sequentially or simultaneously. In this example, the responder 2110 sequentially receives on DMG antenna 1 through DMG antenna N while the initiator 2105 is performing a transmit sector sweep. resp,RX During the time that the responder 2110 is sensing with its respective DMG antenna, the initiator 2105 transmits EDMG BRP-TX packets 2125, 2130, 2135, 2140 over each of its DMG transmit antennas. Note that in some embodiments, EDMG BRP-RX packets can be used instead of EDMG BRP-TX packets.
[0142] Each RX antenna can form a quasi-omni-directional beam or a directional beam. During the initiator TXSS, the responder can observe that one or more RX antennas perform better than the rest. The performance of the antennas can be measured by SNR, SINR, RSSI, etc.
[0143] In the responder TXSS, the responder 2110 may determine (e.g., based on antenna reciprocity assumptions with the responder's receive antennas) to use one or more RX antennas that perform better (e.g., in terms of SNR, SINR, RSSI, or other suitable metric) than others in receiving the initiator TXSS (i.e., EDMG BRP-TX packets 2125, 2130, 2135, 2140) to transmit for the responder TXSS. In procedure 2100, antennas N_sel_1 through N_sel_n are selected to perform the responder TXSS. The responder 2110 transmits EDMGB RP-TX packets 2145, 2150, 2155, 2160, ... 2165, 2170 from each of the antennas N_sel_1 to N_sel_n to the initiator 2105, while the initiator 2105 transmits EDMGB RP-TX packets 2145, 2150, 2155, 2160, ... 2165, 2170 from each of its DMG antennas 1 to N, respectively. init,RX Reception is performed on each of the above.
[0144] The BRP CDOWN field of each EDMG BRP TX packet transmitted in the responder TXSS may indicate the number of remaining EDMG BRP TX packets to be transmitted by the responder 2110 .
[0145] After the initiator TXSS and responder TXSS phases, an identity of the best sector or sectors (e.g., in terms of SNR, SINR, RSSI, or other suitable metric) may be fed back from the receiver to the transmitter. For example, the initiator 2105 sends a BRP 2175 to the responder 2110, and the responder 2110 sends a BRP 2180 to the initiator 2105.
[0146] If a BRP packet is used in the previous initiator TXSS, the feedback sector can be identified using the value of BRP CDOWN and AWV Feedback ID. To include the BRP, CDOWN, and AWV Feedback ID in the BRP feedback frame, the BRP frame can include an EDMG Channel Measurement Feedback element. In the case where the EDMG Channel Measurement Feedback element is not present, one or more other elements and / or fields in the BRP frame can be modified to include the number of BRP CDOWN.
[0147] For example, to address the previously discussed problem of SSW feedback resulting in a responder having separate antennas for transmission and reception, SLS with receive antenna indication can be implemented. In some embodiments, the RSS message can indicate the identity of the selected sector with the best reception quality (e.g., in terms of SNR, SINR, RSSI, or other suitable metric) and / or the Rx antenna and / or RF chain that received the CDOWN. Based on this indication, the initiator can select in a subsequent feedback message the responder sector and / or CDOWN that corresponds to the indicated responder antenna / RF chain, such that the transmit and receive antennas of the responder after receiving the feedback message will be the same or matched.
[0148] In some embodiments, a bit may be added to a short SSW packet, SSW frame, or any other packet used to perform RSS to indicate that the current transmitting antenna (or RF chain) is the antenna (or RF chain) that received the selected sector indicated in the SSW feedback field (or short SSW feedback field) with the best quality.
[0149] In an exemplary embodiment, the bit can be included in the short SSW packet and / or SSW frame used for RSS or in the BRP TXSS packet. The initiator can select and indicate in a subsequent feedback message (e.g., SSW feedback) the sector corresponding to the responder's antenna with the best Rx quality. The antenna with the best Rx quality can be indicated by one or more bits added to the RSS message / packet. The initiator can select the responder sector based on the received signal strength and / or quality of the initiator antenna and / or RF chain of the initiator sector selected by the responder in the RSS. For example, the initiator can use only the received signal quality from the RF chain and / or antenna of the initiator sector selected by the responder in the RSS to choose the responder sector. If the bit is included in the short SSW packet, it can replace one of the reserved bits in the short SSW packet with the direction field equal to 1. If the bit is included in the SSW frame, it may replace one of the reserved bits in the BRP request field.
[0150] 22 is a bitmap showing an example short SSW packet format 2200 with a direction field of 1 (R-TXSS). The short SSW packet format 2200 includes a packet type field 2205, a direction field 2210 (set to 1 in this example), a "best Rx RF chain" field 2215, a source AID field 2220, a destination AID field 2225, a CDOWN field 2230, an RF chain ID field 2235, a short SSW feedback field 2240, and an FCS field 2245. Here, the "best Rx RF chain field" 2215 can be used to indicate the identity of the RF chain or receive antenna that received the selected sector with the best quality among all receive sectors using all receive RF chains / antennas.
[0151] 23 is a bitmap illustrating an example BRP request field format 2300. The BRP request field format 2300 includes an L-RX field 2305, a TX-TRN-REQ field 2310, a MID-REQ field 2315, a BC-REQ field 2320, a MID grant field 2325, a BC grant field 2330, a Chan-FBCK-CAP field 2335, a TX sector ID field 2340, an Other_AID field 2345, a TX antenna ID field 2350, a "further feedback requested" field 2355, a "best Rx antenna" field 2360, and a reserved field 2365. Here, the "best Rx antenna" field 2360 can be used to indicate the identity of the antenna that received the selected sector with the best quality among all receive antennas.
[0152] In some embodiments, the sector and / or CDOWN selected and / or fed back may depend on the antenna and / or RF chain transmitting the RSS packet. The sector / CDOWN selected / indicated in the SSW feedback field, short SSW feedback field, or in any other feedback field of the RSS packet may be different for different antennas / RF chains of the responder.
[0153] For example, in an RSS packet transmitted by a responder using a particular RF chain and / or antenna, the initiator's selected CDOWN / sector may be chosen based on reception strength and / or quality during the ISS using that antenna (e.g., the best initiator sector received using this responder antenna / RF chain).
[0154] If the initiator sends a subsequent feedback message (e.g., SSW feedback) using TX sector x selected and / or indicated in one of the RSS messages, the feedback message may select a responder sector and / or CDOWN using responder antenna and / or RF chain j, while initiator sector x was selected / indicated in the RSS message sent using responder antenna / RF chain j.
[0155] The initiator may determine the initiator antenna and / or RF chain i that receives the best quality RSS message. It may determine one or more RSS messages that indicate and / or select the initiator sector that uses antenna and / or RF chain i. The initiator then selects a responder sector based on the sector id and / or CDOWN of these RSS messages in a subsequent feedback message (e.g., SSW feedback).
[0156] The initiator may transmit a subsequent feedback message (e.g., SSW feedback) using the initiator sector indicated in the RSS message transmitted from the selected responder sector. For example, due to the responder selecting multiple initiator sectors in separate RSS messages transmitted from separate responder antennas, the responder may not know which initiator sector is used to transmit a subsequent feedback message (e.g., SSW feedback) and what corresponding Rx antenna the responder should use. The responder may listen on multiple RF chains and / or antennas to receive feedback messages.
[0157] Alternatively, the initiator may have knowledge that the responder cannot use multiple antennas simultaneously to receive feedback messages. In this case, the initiator may only select sectors from pre-agreed responder antenna x in the feedback message, and the responder may only use antenna x to receive the feedback message and to send ACKs of the feedback message. The pre-selected antenna may be agreed upon by both the initiator and the responder, and may be specified or signaled prior to transmission.
[0158] After the responder receives the feedback message, it can determine the Tx and / or Rx antennas to be used for subsequent communication based on the sector id and / or CDOWN selected in the feedback message. The responder can switch off other RF chains and / or antennas.
[0159] In some embodiments, the responder can switch to a different antenna / RF chain based on the responder sector selected in a feedback message from the initiator. For example, if the initiator indicates a responder sector in a feedback message (e.g., in an SSW feedback) and the indicated responder sector corresponds to an antenna x that is different from antenna y that the responder is using to receive the feedback message, the responder can switch from antenna y to x to send an ACK to the feedback message (e.g., an SSW ACK).
[0160] In the feedback field of the ACK message (e.g., the SSW feedback field of the SSW ACK), the responder may choose not to indicate the best initiator sector (received by the responder antenna x) if this best initiator sector is not a sector of the same initiator antenna that corresponds to the initiator sector z selected by the responder in the RSS message (i.e., the initiator sector indicated in the message used in the responder TX sector sweep). The responder may choose an initiator sector that uses the same antenna / RF chain as sector z.
[0161] Figure 33 is a signal diagram of an example SLS procedure 3300 between an initiator 3305 and a responder 3310 illustrating this concept. For example, in Figure 33, the overall best received SSW frame by the responder 3310 during sector sweep 3315 shows its initiator sector as CDOWN=1 (i.e., sector z) and was received by antenna y of the responder 3310. When measured by responder antenna x of the responder 3310, the best initiator sector would appear to be the initiator sector indicated by CDOWN=N. However, the initiator sector indicated by CDOWN=N is not the overall best initiator sector received by the responder 3310.
[0162] The responder 3310 transmits SSW frames to the initiator 3305 during sector sweep 3320, which indicate the overall best initiator sector, CDOWN=1, by setting the sector selection of each SSW frame equal to 1. The overall best received SSW frame from the responder 3310 by the initiator 3305 during SSW 3320 indicates the responder sector using CDOWN=1. This sector corresponds to responder antenna x.
[0163] Since the overall best initiator sector was received by responder antenna y, the responder 3310 uses antenna y to receive the SSW-FBCK message 3325. By receiving the SSW-FBCK message 3325, the responder 3310 is informed that the initiator selected a responder sector with CDOWN=1, which belongs to responder antenna x. The responder therefore switches from antenna y to antenna x to send the SSW-ACK message 3330. However, in the SSW-ACK message 3330 transmitted by responder antenna x, the responder 3310 does not indicate (or select) the initiator sector with CDOWN=N (i.e., the best initiator sector received by responder antenna x), but rather indicates (by setting sector selection equal to 0) the initiator sector with CDOWN=0, which corresponds to the same initiator antenna transmitting the initiator sector with CDOWN=1 (i.e., sector z).
[0164] In this example, the initiator 3305 selected the responder sector corresponding to CDOWN=1 / antenna x in the SSW-FBCK message 3325 because it did not know that the reported best initiator sector was measured by responder antenna y. By selecting CDOWN=0 in the SSW-ACK message 3330, the responder 3310 eliminates the need for the initiator 3305 to switch to another antenna, avoiding repeated antenna switching on both sides.
[0165] In some embodiments, a STA may have the capability to perform Tx and Rx using separate antennas. For example, the capability may be indicated before or during the SLS procedure, so that the initiator and / or responder will know if one or more of the above-mentioned embodiments are required to avoid sector selection resulting in separate Tx and Rx antennas.
[0166] The capability indication can be included in the EDMG capabilities element and exchanged along with other capabilities. The initial SLS between the initiator and responder can be performed using only a single RX antenna / RF chain to facilitate subsequent communication regarding this capability exchange. The capability can be included in the SLS packet itself, so that it is known from the SLS process without prior capability exchange.
[0167] Some implementations may include procedures for SLS using multiple transmit and receive antennas. Figure 24 is a signal diagram illustrating an example SLS communication 2400 between an initiator 2405 and a responder 2410. The initiator 2405 uses Ntx transmit antennas, each with N sectors, and the responder 2410 uses Nrx receive antennas, each with M sectors.
[0168] In the first phase of operation, the initiator 2405 transmits measurements in frames 2415, 2416 over Max(CDOWN)=(N×Ntx) sectors to the responder 2410. The frames 2415, 2416 can be SSW frames, short SSW frames, or any other type of frame suitable for SLS. Each number corresponds to a frame transmitted using a sector. Thus, in phase 1, 2N frames are transmitted. Each frame in the set of frames 2415, 2416 includes a CDOWN. In some examples, the CDOWN parameter can be counted over the total number of sectors in the initiator 2405. In this case, if the CDOWN parameter is greater than the number of sectors in the transmit antenna, the responder 2410 (transmitter) can implicitly estimate the index of the transmit antenna (e.g., floor(CDOWN / Nsectors)) based on the received CDOWN feedback. In some examples, the CDOWN parameter may be counted across each transmit antenna at the initiator 2405. In this case, the initiator 2405 may also transmit a transmit antenna index so that the responder 2410 can identify the particular transmit antenna being used.
[0169] The initiator 2405 may transmit a frame with the CDOWN parameters N_repetition times. In the case where the responder 2410 is capable of receiving on one antenna at a time, N_repetition may be equal to the number of receive antennas of the responder 2410. In the case where the responder 2410 is capable of receiving on N_concurrent_antennas antennas (i.e., antenna groups) at a time, N_repetition may be equal to N_rx / N_concurrent_antennas (or ceil(N_rx / N_concurrent_antennas)). During reception, each receive antenna of the responder 2410 may be set to a quasi-omnidirectional receive antenna beam. In the example SLS communication 2400, N_repetition=2, and frame 2416 may be considered a repetition of frame 2415.
[0170] To facilitate synchronization between the receive antennas (or antenna groups) of the responder 2410 and the transmit frame of the initiator 2405 (i.e., the receive antennas of the responder are synchronized in the sense that they are switched to the antennas assumed by the transmit frame of the initiator), one or more of the following approaches may be implemented: In addition to the CDOWN parameter, a repetition count parameter may be transmitted in each section of the measurement frame. A signal to indicate that a change in receive antennas (or antenna groups) should be performed may be transmitted during each repetition of the measurement frame. The signal may be a "dummy" signal, such as, for example, a signal with a known sequence, a signal with a known sequence and good auto / cross-correlation properties, or a signal that explicitly indicates the index of the measurement group. The transmit antenna / sector may be set to the first transmit antenna / sector used in transmitting the measurement frame. The dummy signal can be transmitted using an antenna pattern / set of antenna patterns with corresponding transmit power (e.g., boosted power) to ensure that the STA receives the signal to switch antennas, in which case the transmitter can switch to a quasi-omni-directional transmit antenna, or can sweep across all transmit antennas / sectors (e.g., using a short duration signal to reduce overhead).
[0171] In an exemplary SLS communication 2400, the initiator 2405 transmits a dummy signal 2419 to the responder 2410 after the first repetition (i.e., after frame 2415), and the responder 2410 switches from receiving on the first receive antenna (Rx1) 2420 to receiving on the second receive antenna (Rx2) 2425.
[0172] In a second phase of operation, the roles of the initiator and responder can be reversed in the sense that the initiator can be configured to receive and the responder can be configured to transmit, where the responder can also indicate the best antenna (or antenna group) corresponding to its Rx antenna and the CDOWN index corresponding to the initiator sector in transmitting to the initiator.
[0173] In the example SLS communication 2400, the responder 2410 transmits measurements to the initiator 2405 in frames 2435, 2436. The responder 2410 transmits a dummy signal 2439 to the initiator 2405 after the first iteration (i.e., after frame 2435) and the initiator 2405 switches from receiving on the first receive antenna (Rx1) 2440 to receiving on the second receive antenna (Rx2) 2445.
[0174] In a third phase of operation, the initiator may send SSW feedback, e.g., using an SSW-FBCK frame, indicating the best Tx antenna (or antenna group) of the responder that corresponds to the initiator's Rx antenna, and indicating a CDOWN index that corresponds to the responder sector in the transmission to the responder.
[0175] In an example SLS communication 2400, the initiator 2405 transmits an SSW-FBCK 2450 to the responder 2410 indicating the Tx antenna sector of the responder 2410 for transmission to one or more of the Rx antennas of the initiator 2405. The indicated Tx antenna sector of the responder 2410 can be calculated as a function of CDOWN and N_repetition. For example, the best sector can be indicated as the number k of CDOWN in repetition m.
[0176] In a fourth phase of operation, the responder can send a message back to the initiator acknowledging receipt of the SSW feedback, for example using an SSW-ACK frame. In the example SLS communication 2400, the responder 2410 sends an SSW-ACK frame 2460 to the initiator 2405 for this purpose. In the case of a mismatch in transmit and receive antennas for the initiator or responder, the procedure is complete if the STA (initiator or responder) is able to transmit and receive on separate antennas.
[0177] In a fifth phase of operation, if the STA (initiator or responder) is not capable of transmitting and receiving on separate antennas, the SSW ACK frame may include a request for additional Tx or Rx SSW. In some examples, the STA may request an Rx SSW and fix the receive antenna to the antenna corresponding to the best Tx sector, the STA may request a Tx SSW and fix the Tx sector (or antenna) to the sector (or antenna) corresponding to the best transmission, the STA may request that feedback be limited to the antenna corresponding to the previous feedback in the second phase of operation, or the sectors and antennas may be used as input to a beam-combining based BRP procedure to exhaustively search across transmit and receive antennas / sectors for the best set.
[0178] In the example SLS communication 2400, the SSW-ACK frame 2460 includes a request from the responder 2410 to the initiator 2405 for further SSW of its Tx antenna with the initiator's 2405 receive antenna locked on Rx1. The responder 2410 then transmits frames 2475 and 2476, one for each sector and with a CDOWN for each sector. The initiator 2405 locks onto the first receive antenna Rx1 2580 and receives. After the SSW, the initiator 2405 transmits feedback to the responder 2410 in a SSW-FBCK message 2580 indicating the responder's 2410 best Tx antenna.
[0179] For example, parallel reception can be implemented to address the problem of BRP feedback without setup discussed above. For STAs that can receive simultaneously using all RF chains, BF training overhead can be reduced. For example, BF training with parallel receive chains can be implemented using various procedures and detailed frame formats.
[0180] For example, the initiator of a BF SLS training may send a setup frame to a responder to start the BF SLS training. The setup frame may be a grant frame, a BRP frame, or an extended schedule element transmitted in the beacon header interval (BHI). If the setup frame / element is in the BHI, the responder may not send a setup frame back to the initiator. The setup frame may carry various information including the number of sectors for the initiator TXSS, whether the responder TXSS is required in the SLS, the TXSS repetition count, and the duration field setting if the setup frame and the subsequent training frame are in the same allocation.
[0181] More specifically, the number of sectors for the initiator TXSS field may indicate the number of sectors to be swept in the subsequent initiator TXSS. For example, this number may be the number of sectors without repeats for the responder to train separate antennas. The responder TXSS may be required in the SLS. The R-TXSS is optional. In this example, R-TXX is present. In the responder TXSS, the responder may repeat the sector sweep for N_TXSS_Repeat times. The value of N_TXSS_Repeat may be determined by the initiator and carried in the setup frame. If the setup frame and the subsequent training frame are in the same allocation, the initiator may set the allocation duration field by estimating the total duration including the initiator TXSS duration, the responder TXSS duration, and the feedback duration. The initiator TXSS duration may depend on the initiator TXSS Repeat, which may be determined by the responder. In this case, the initiator can estimate the value based on the responder's capabilities if it is able to set the number of parallel RX chains, or the initiator can assume that the Initiator TXSS Repetitions is 1 or another suitable (e.g., conservative) number. The initiator can then later overwrite the Duration field in the Training frame.
[0182] The responder of the BF SLS training can send a setup frame to the initiator. The setup frame can be a Grant ACK frame or a BRP frame. The setup frame can carry various information including the number of sectors for the responder TXSS, the number of TXSS repetitions, and the total number of training frames and / or sequences to be transmitted in the responder TXSS.
[0183] More specifically, the number of sectors for the responder TXSS field may indicate the number of sectors to be swept in the subsequent responder TXSS. For example, this number may be the number of sectors without repetition for the initiator to train separate receive antennas. In the initiator TXSS, the initiator may repeat the sector sweep N_TXSS_Repeat times. The value of N_TXSS_Repeat may be determined by the responder and carried in the setup frame. The total number of training frames / sequences to be transmitted in the responder TXSS may be calculated by the responder based on information carried in the setup frame transmitted from the initiator.
[0184] The initiator can calculate the total number of training frames / sequences to be transmitted in the initiator TXSS based on the information received in the setup frame sent from the responder. The initiator can transmit the training frames accordingly. In the training frame, the duration field can be updated based on the initiator TXSS Repeat field set by the responder. After the initiator TXSS, the responder TXSS can be performed by the responder. The initiator and the responder can then feed back the necessary information to each other.
[0185] FIG. 25 is a signal diagram illustrating an example procedure 2500 for parallel RX determined by a receiver in BF training. An initiator 2505 of BF SLS training can send a setup frame 2515 to a responder 2510 to start BF SLS training. The setup frame can be a grant frame, a BRP frame, or an extended schedule element transmitted in a beacon header interval (BHI). If the setup frame / element is in the BHI, the responder can not send a setup frame back to the initiator. The setup frame can carry various information including the number of sectors for the initiator TXSS, whether a responder TXSS is required in the SLS, the TXSS repeat count, and the duration field setting if the setup frame and the subsequent training frame are in the same allocation. In the example procedure 2500, the setup frame 2515 includes the number of times the responder 2510 should repeat transmitting the TXSS. The responder 2510 sends a setup frame 2520 including the number of times the initiator 2505 should repeat sending the TXSS. The initiator 2505 sends SSW frames 2525, 2530, ..., 2535 including the number of repetitions based on the setup frame 2520 to the responder 2510. The responder 2510 sends SSW frames 2540, 2545, ..., 2550 including the number of repetitions based on the setup frame 2515 to the initiator 2505.
[0186] Parallel reception determined by the AP can be implemented in the BF training. For example, the AP is the initiator and the STA is the responder. The initiator and the responder can exchange capability information. The number of parallel RX chains / antennas (i.e., the number of RX chains or antennas that can receive simultaneously) can be signaled in the capability field in the exchange.
[0187] The initiator of the BF SLS training can send a setup frame to start the BF SLS training. The setup frame can be a grant frame, a BRP setup frame, or an extended schedule element transmitted in the beacon header interval (BHI). In the last case, the responder can not send a setup frame back to the initiator. The setup frame can carry various information including whether the responder TXSS is required in the SLS, the TXSS repetition count, the number of sectors for the initiator TXSS, and the duration field setting if the setup frame and the subsequent training time are in the same allocation.
[0188] More specifically, if a responder TXSS is required in the SLS, the setup frame may indicate N_Responder_TXSS_Repeat, i.e., in the responder TXSS, the responder may repeat the sector sweep N_Responder_TXSS_Repeat times. The value of N_Responder_TXSS_Repeat may be determined by the initiator and carried in the setup frame. In case the responder TXSS may not be present, the field may be reserved.
[0189] The setup frame can indicate N_Initiator_TXSS_Repeat, i.e., the initiator can determine, e.g., from a capability exchange, the number of parallel RX chains and / or antennas that the responder can support. For example, if the responder can support N_rx_chains parallel RX chains / antennas and intends to train N_rx antennas, then N_initiator_TXSS_Repeat_base=ceil(N_rx / N_rx_chains), where ceil(x) is a function to obtain the smallest integer greater than or equal to x. Thus, based on the value of N_initiator_TXSS_Repeat_base, the initiator can choose a value for N_Initiator_TXSS_Repeat and signal it in the setup frame. The value indicates that the initiator can repeat the sector sweep N_Initiator_TXSS_Repeat times in the subsequent initiator TXSS.
[0190] The setup frame may indicate the number of sectors for the initiator TXSS. This field may indicate the number of sectors to be swept in the subsequent initiator TXSS. For example, this number may be the number of sectors without repetition for the responder to train separate antennas. If the setup frame and the subsequent training frame are in the same allocation, the initiator may set the allocation duration by estimating the total duration including the initiator TXSS duration, the responder TXSS duration, and the feedback duration.
[0191] The responder may transmit a setup frame. The responder setup frame may include the number of sectors for the responder TXSS. This field may indicate, for example, the number of sectors to be swept in the subsequent responder TXSS if presented. For example, this number may be the number of sectors without iterations for the responder to train separate antennas. Furthermore, in the exemplary procedure, the setup frame may be followed by an initiator TXSS, a responder TXSS, and a feedback phase.
[0192] 26 is a signal diagram illustrating an example procedure 2600 for parallel RX determined by the AP in BF training. The AP 2605 transmits capabilities to the STA 2610 in frame 2615, and the STA transmits capabilities to the AP 2605 in frame 2620. In the example procedure 2600, frames 2615 and 2620 include the number of receiver chains or antennas that can receive simultaneously. The AP 2605 sends a setup frame 2625 to the STA 2610, and the STA 2610 sends a setup frame 2630 to the AP 2605. In the example procedure 2600, the setup frame 2625 indicates the number of sectors for N_Responder_TXSS_Repeat, N_Initiator_TXSS_Repeat, and initiator TXSS, as described above, based on the exchanged capability information. For example, the repetitions can be calculated based on a relationship such as N_repeat=N_antenna / N_concurrent_antennas, or any other suitable relationship. The setup frame 2630 indicates the number of sectors for the responder TXSS as described above. The AP 2605 then transmits SSW frames 2650, 2655, ..., 2660 to the STA 2610 to repeat the SSW based on the setup frame 2625. The STA 2610 transmits SSW frames 2670, 2675, ..., 2680 to the AP 2605 to repeat the SSW based on the setup frame 2625.
[0193] Some embodiments include parallel receiver BF training without explicitly setting the number of TXSS repetitions. In some examples, the initiator and responder can exchange capability information. For example, the number of parallel RX chains and / or antennas can be signaled in the capability field. The initiator of the BF SLS training can send a setup frame to start the BF SLS training. The setup frame can be, for example, a grant frame, a BRP setup frame, or an extended schedule element transmitted in the beacon header interval (BHI). In the last case, the responder can not send a setup frame back to the initiator.
[0194] The setup frame may indicate the number of sectors for the initiator TXSS in a field indicating the number of sectors to be swept in a subsequent initiator TXSS. For example, this number may be the number of sectors without repetition for the responder to train a separate antenna. The setup frame may indicate the assignment duration if the setup frame and the subsequent training frame may be in the same assignment. The initiator may set the assignment duration by estimating the total duration including the initiator TXSS duration, the responder TXSS duration, and the feedback duration. The estimated initiator TXSS duration and the responder TXSS duration may be based on the "number of parallel RX chains and / or antennas" capability field.
[0195] The responder may transmit a setup frame, which may include a "Number of Sectors for Responder TXSS" field, which may indicate the number of sectors to be swept in the subsequent responder TXSS. For example, this number may be the number of sectors without repetition for the responder to train separate antennas.
[0196] In the initiator TXSS, the initiator may transmit a training frame. The initiator may sweep N transmission sectors and repeat this for N_Initiator_TXSS_Repeat times. N_initiator_TXSS_Repeat may be calculated based on the number of parallel RX chains / antennas supported by the responder. For example, if the responder may support N_rx_chains parallel RX chains / antennas and intend to train N_rx antennas to perform training, then N_initiator_TXSS_Repeat=ceil(N_rx / N_rx_chains), where ceil(x) is a function to obtain the smallest integer greater than or equal to x.
[0197] In the responder TXSS (if present), the responder may transmit a training frame. The responder may sweep N transmit sectors and repeat this for N_responder_TXSS_Repeat times. N_responder_TXSS_Repeat may be calculated based on the number of parallel RX chains / antennas supported by the initiator. For example, if the initiator may support N_rx_chains parallel RX chains / antennas and may intend to train N_rx antennas to perform training, then N_responder_TXSS_Repeat=ceil(N_rx / N_rx_chains), where ceil(x) is a function to obtain the smallest integer greater than or equal to x. The initiator and the responder may also transmit feedback frames.
[0198] FIG. 27 is a signal diagram showing an example procedure for parallel RX determined by an initiator in BF training. In this procedure, the AP is the initiator and the STA is the responder. Some examples include parallel Rx capabilities. For example, an EDMG STA can indicate whether it has the capability to receive simultaneously using multiple Rx antennas. In some embodiments, an EDMG STA can indicate whether it has the capability to receive simultaneously using multiple Rx antennas by modifying and reinterpreting the DMG capabilities field. The current DMG STA capabilities information field includes a "Number of Rx DMG Antennas" subfield. This subfield can be reinterpreted as the number of parallel Rx DMG antennas if the STA transmitting this field is an EDMG STA.
[0199] FIG. 27 illustrates an example procedure 2700 for parallel receiver BF training without explicitly setting the number of TXSS repetitions. The AP 2705 transmits capabilities to the STA 2710 in frame 2715, and the STA transmits capabilities to the AP 2705 in frame 2720. In the example procedure 2700, frames 2715 and 2720 include the number of receiver chains or antennas that can receive simultaneously. The AP 2705 sends a setup frame 2725 to the STA 2710, and the STA 2710 sends a setup frame 2730 to the AP 2705. In the example procedure 2700, the setup frame 2725 indicates the number of sectors for the initiator TXSS, as described above. The setup frame 2730 indicates the number of sectors for the responder TXSS, as described above. Thereafter, the AP 2705 transmits SSW frames 2750, 2755, ..., 2760 to the STA 2710 to repeat the SSW based on the initiator TXSS Repeat, which is implicitly determined based on the number of receiver chains or antennas capable of simultaneous reception, as indicated in the capability field 2720. The STA 2710 transmits SSW frames 2770, 2775, ..., 2780 to the AP 2705 to repeat the SSW based on the responder TXSS Repeat, which is implicitly determined based on the number of receiver chains or antennas capable of simultaneous reception, as indicated in the capability field 2715.
[0200] In some embodiments, an EDMG STA may indicate whether it has the capability to receive simultaneously using multiple Rx antennas. In some instances, the DMG Capabilities field may be modified to indicate this capability. For example, the legacy "Number of Rx DMG Antennas" subfield of the DMG STA Capabilities Information field in the EDMG Capabilities element may be modified and reinterpreted for this purpose if the STA transmitting this field is an EDMG STA.
[0201] In some examples, a "number of parallel Rx DMG antennas" field can be added to the EDMG Capability element. A new Capability ID can be specified for the MIMO field, or the Multi-BF Capability ID can be reused. In some examples, a 3-bit "number of parallel Rx DMG antennas" field can be defined in the MIMO field. In another example, the existing Beamforming field can be modified to carry a 3-bit "number of parallel Rx DMG antennas" field. For example, the existing Beamforming Capability field has 7 spare bits that can be used. A 3-bit "number of parallel Tx DMG antennas" can also be defined in the Capability field. Alternatively, the 3-bit "number of parallel Rx DMG antennas" field can be replaced by a 1-bit "parallel Rx" field. If this bit is set to 1, the STA can receive using all of its RF chains.
[0202] Figure 28 is a table showing an example specification for a new Capability ID for the MIMO field. Figure 29 is a bitmap showing an example reuse of a Multi-BF Capability ID 2900. The Multi-BF Capability ID 2900 includes a "Number of Parallel Rx DMG Chains / Antennas" field 2910, a Number of Parallel Tx DMG Chains / Antennas 2920, and a Reserved field 2930.
[0203] Some embodiments include a modified BF control field for grants and / or grant ACKs. The BF control field may be carried in grant and / or grant ACK frames. The grant and / or grant ACK frames may be used to reserve and / or grant BF training and / or SLS training opportunities, respectively. For example, if both the IsInitiatorTXSS and IsResponderTXSS subfields are equal to 1 and the BF control field is transmitted in a grant or grant ACK frame, the BF control field may be modified.
[0204] 30 is a bitmap illustrating an example modified BF control field 3000. The modified BF control field 3000 includes a beamforming training field 3010, an IsInitiatorTXSS field 3020, an IsResponderTXSS field 3030, a "number of sectors" field 3040, a TXSS Repeat field 3050, a TXSS Repeat field 3060, an EDMG field 3060, and a reserved field 3070.
[0205] In the modified BF control field 3000, the legacy spare bit may be used as the EDMG bit 3060. If the EDMG bit 3060 is set to 0, the BF control field 3000 may function as unmodified from the legacy control field. If the EDMG bit 3060 is set to 1, the 2-bit "Number of Rx DMG Antennas" field that was present in the legacy version may not be present, and the TXSS Repeat field 3050 (e.g., having 3 bits) may be added.
[0206] In some examples, if the BF control field 3000 is transmitted in a grant frame, the "number of sectors" field 3040 indicates the number of sectors the initiator uses during the initiator TXSS. If the BF control field 3000 is transmitted in a grant ACK frame, the "number of sectors" field 3040 indicates the number of sectors the responder uses during the responder TXSS. In both example cases, the total number of sectors used may be equal to the value of this field plus one.
[0207] In some examples, the BF control field 3000 is transmitted in a grant frame. For example, the transmitter of the grant frame may be the initiator, and the receiver of the grant frame may be the responder. In another example, an AP may grant a TXOP to two non-AP STAs. One of the non-AP STAs may be the initiator of the BF training, and the other of the non-AP STAs may be the responder, and the TXSS Repeat field 3050 (e.g., value +1) may indicate the number of times that the sector swept in the responder TXSS may be repeated. If the BF control field 3000 is transmitted in a grant ACK frame, the TXSS-Repeat field 3050 (e.g., value +1) may indicate the number of times that the sector swept in the initiator TXSS may be repeated.
[0208] If the EDMG field 3060 is set to 1, the total number of sectors used by the initiator / responder during the initiator / responder TXSS can be (Number of Sectors+1)*(TXSS Repeat+1). The initiator and responder can obtain information about the number of parallel RX chains from the capability exchange and set the TXSS Repeat 3050 accordingly. In the BF control field 3000, the TXSS Repeat field 3050 sent by the initiator can be used to set the repeat count for the responder TXSS, and the TXSS Repeat field 3050 sent by the responder can be used to set the repeat count for the initiator TXSS.
[0209] In another example, the TXSS Repeat field 3050 sent by the initiator can be used to set the repeat count for the initiator TXSS, and the TXSS Repeat field 3050 sent by the responder can be used to set the repeat count for the responder TXSS.
[0210] Alternatively, for the grant frame, the reserved bits in the BF control field 3000 and the control trailer can both be used to signal the number of sectors and the TXSS Repeat. This approach can allow more bits to be used. For example, 11 bits can be allocated to the number of sectors and 3 bits to the TXSS Repeat. For the grant ACK frame, the control trailer is not defined. However, the reserved bits in the BF control field 3000 and the reserved bits (e.g., 5 bits) in the grant ACK frame can be used to signal the number of sectors and the TXSS Repeat. This approach can allow more bits to be used. For example, 11 bits can be allocated to the number of sectors and 3 bits to the TXSS Repeat.
[0211] Some examples provide a modified control trailer for the grant frame. In some examples, the BF control field carried by the grant frame can be modified, or the control trailer carried by the grant frame can be modified as discussed further below. In other examples, the grant frame can be modified by modifying both the BF control field carried in the MAC body and the control trailer added to the PPDU. Using this approach, some information can be transmitted in the BF control field and some information can be transmitted in the control trailer.
[0212] An exemplary control trailer defined for the grant frame may include 30 reserved bits. In one example, 3 or 6 bits may be used for TXSS Repeat. The TXSS Repeat field may indicate that the grant frame may be used to allow a BF training allocation, the number of sectors for the TXSS (i.e., the number of sectors swept in the subsequent initiator TXSS). In some examples, this number is the number of sectors with no repeat for the responder to train separate antennas, the number of times the sectors swept in the responder TXSS may be repeated, and / or the number of times the sectors swept in the initiator TXSS may be repeated.
[0213] Some embodiments provide a modified BF control field for an extended schedule element. In some examples, a modified BF control field can be carried in an extended schedule element, which can be used to reserve and / or grant BF training and / or SLS training opportunities. There can be six reserved bits in an extended schedule element, and the frame can be modified to include several bits for TXSS Repeat. Exemplary modification options include one initial TXSS Repeat bit field, three initial TXSS Repeat bit fields, one responder TXSS Repeat bit field, three responder TXSS Repeat bit fields, or a modification of the existing 6-bit RXSS length field.
[0214] 1 Initial TXSS Repeat bit field can indicate whether the initial TXSS can be repeated or not. 3 Initial TXSS Repeat bit field can indicate whether the initial TXSS can be repeated or not and, if so, how many times it is repeated. 1 Responder TXSS Repeat bit field can indicate whether the responder TXSS can be repeated or not. 3 Responder TXSS Repeat field can indicate whether the responder TXSS can be repeated or not and, if so, how many times it is repeated. The modified 6-bit RXSS Length field can be reinterpreted as a "number of sectors" field, which can indicate the number of TXSS sectors (e.g., without repeats). In cases where 6 bits are insufficient, some spare bits can also be used. Since 6 bits are reinterpreted in this example, one spare bit can be used to indicate whether the 6 bits are for the RXSS Length field or the TXSS Packet field. One or more of these modifications may be used to enable parallel Rx in scheduled BF training assignments. Figure 31 is a bitmap illustrating an example modified BF control field format 3100 for an extended schedule element. The modified BF control field format 3100 includes a beamforming training field 3110, an IsInitiatorTXSS field 3120, an IsResponderTXSS field 3130, an RXSS length field 3140, an RXSS TxRate field 3150, a TXSS Repeat field 3160, and a reserved field 3070. The reserved field may have 3, 4, or 5 bits in some examples, or any suitable number of bits.
[0215] Although various features and elements herein are described in particular combinations, each feature or element can be used alone without other features and elements of the preferred embodiments, or in various combinations with or without other features and elements disclosed herein. Although the solutions described herein are described with respect to IEEE 802.11 specific protocols, it will be understood that the solutions described herein are not limited to IEEE 802.11 applications, but are applicable to other wireless systems and others.
[0216] Although features and elements are described above in certain combinations, one of ordinary skill in the art will understand that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, ROM, RAM, registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with software can be used to implement a radio frequency transceiver for use in a wireless transmit / receive unit WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. A station (STA) configured for beamforming (BF) training as a responder device to an initiator device, the STA comprising: a first plurality of antennas; Transceiver and Equipped with The transceiver includes: receiving, via the first plurality of antennas, a first plurality of packets transmitted from a second plurality of antennas of the initiator device via a first respective transmit (TX) sector during an initiator beam refinement procedure (BRP) transmit sector sweep (TXSS); transmitting a second plurality of packets during a responder BRP TXSS to the initiator device using one or more antennas of the first plurality of antennas that exhibited better performance than one or more other antennas in the first plurality of antennas during an initiator BRP TXSS; The device is configured to: The second plurality of packets are configured to be transmitted using the one or more antennas that have demonstrated better performance than the one or more other antennas via one or more second respective TX sectors during the initiator BRP TXSS based on an indication that the STA is antenna reciprocal to the initiator device. S.T.A.
2. The STA of claim 1 , wherein the transceiver is configured to receive the indication that the STA is antenna reciprocal in a subfield of a message received from the initiator device.
3. 13. The STA of claim 1, further comprising a processor configured to determine that the one or more antennas have performed better than the one or more other antennas based on an SNR, SINR, RSSI, or another metric.
4. 2. The STA of claim 1, wherein the first plurality of packets and the second plurality of packets each comprise an Enhanced Directional Multi-Gigabit (EDMG) packet.
5. The STA of claim 1 , wherein the transceiver is configured to transmit a BRP frame with feedback indicating results of measurements made on the first plurality of packets.
6. 6. The STA of claim 5, wherein results of measurements made on the first plurality of packets indicate one or more antennas of the second plurality of antennas that exhibited best performance during an initiator BRP TXSS.
7. 6. The STA of claim 5, wherein the BRP frame is a first BRP frame, and the transceiver is configured to receive a second BRP frame with feedback indicating results of measurements made on the second plurality of packets.
8. 8. The STA of claim 7, wherein results of measurements made on the second plurality of packets indicate one or more antennas of the first plurality of antennas that exhibited best performance during a responder BRP TXSS.
9. The STA of claim 1 , wherein the transceiver is further configured to receive a BRP frame from the initiator device configured to set up an initiator BRP TXSS.
10. A method of beamforming (BF) training in a station (STA) acting as a responder device to an initiator device, comprising: receiving, via a first plurality of antennas, a first plurality of packets transmitted from a second plurality of antennas of the initiator device via a first respective transmit (TX) sector during an initiator beam refinement procedure (BRP) transmit sector sweep (TXSS); transmitting a second plurality of packets during a responder BRP TXSS to the initiator device using one or more antennas of the first plurality of antennas that exhibited better performance than one or more other antennas in the first plurality of antennas during an initiator BRP TXSS, the second plurality of packets being configured to be transmitted using the one or more antennas that exhibited better performance than the one or more other antennas via one or more second respective TX sectors during the initiator BRP TXSS based on an indication that the STA is antenna reciprocal with respect to the initiator device; The method includes:
11. 11. The method of claim 10, further comprising receiving the indication that the STA is antenna reciprocal in a subfield of a message received from the initiator device.
12. 11. The method of claim 10, further comprising determining that the one or more antennas performed better than the one or more other antennas based on SNR, SINR, RSSI, or another metric.
13. 11. The method of claim 10, wherein the first plurality of packets and the second plurality of packets each comprise an Enhanced Directional Multi-Gigabit (EDMG) packet.
14. The method of claim 10 , further comprising: transmitting a BRP frame with feedback indicating results of measurements made on the first plurality of packets.
15. 15. The method of claim 14, wherein results of measurements taken on the first plurality of packets indicate one or more antennas of the second plurality of antennas that exhibited best performance during an initiator BRP TXSS.
16. 15. The method of claim 14, wherein the BRP frame is a first BRP frame, further comprising receiving a second BRP frame with feedback indicative of results of measurements made on the second plurality of packets.
17. 20. The method of claim 16, wherein results of measurements taken on the second plurality of packets indicate one or more antennas of the first plurality of antennas that exhibited best performance during a responder BRP TXSS.
18. The method of claim 10 , further comprising receiving a BRP frame from the initiator device configured to set up an initiator BRP TXSS.
Citation Information
Patent Citations
Apparatus, system and method of beamforming
WO2017078780A1
