WO2018165554A1 - Procédures de partage spatial dans des systèmes wlan - Google Patents

Procédures de partage spatial dans des systèmes wlan Download PDF

Info

Publication number
WO2018165554A1
WO2018165554A1 PCT/US2018/021754 US2018021754W WO2018165554A1 WO 2018165554 A1 WO2018165554 A1 WO 2018165554A1 US 2018021754 W US2018021754 W US 2018021754W WO 2018165554 A1 WO2018165554 A1 WO 2018165554A1
Authority
WO
WIPO (PCT)
Prior art keywords
setting message
sta
nav
nav setting
group
Prior art date
Application number
PCT/US2018/021754
Other languages
English (en)
Inventor
Li-Hsiang Sun
Hanqing Lou
Xiaofei Wang
Rui Yang
Oghenekome Oteri
Original Assignee
Interdigital Patent Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Interdigital Patent Holdings, Inc. filed Critical Interdigital Patent Holdings, Inc.
Publication of WO2018165554A1 publication Critical patent/WO2018165554A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the NAV setting message may include at least a group identifier (ID), a duration field and a training (TRN) field.
  • ID group identifier
  • TRN training
  • a determination may be made as to whether or not NAV setting message is a message of a same basic service set (BSS) of a STA. This determination may provide an indication as to whether or not an associated AP is busy for the duration indicated by the NAV setting message. When an associated AP is busy, a STA may determine to not transmit. When an associated AP is available, a STA may transmit accordingly.
  • An AP may also make a determination to transmit available data based on any NAV setting messages received. This determination may be based on a group ID, a TRN field or a combination of the two.
  • an AP may provide an indication of a service period (SP) for an uplink transmission of a STA.
  • the method may further comprise performing directional reception, by the AP, by listening for the uplink transmission on one or more sectors.
  • An announcement message may be transmitted in advance of performing the directional reception, for indicating one or more receive sectors of the AP.
  • the announcement message may be a beacon frame.
  • a notice of a directional receive mode may be received by at least one non-AP STA.
  • An AP may allocate a candidate SP to a first STA and instruct a second STA to perform sector level sweep (SLS) training or a data transmission during the same candidate SP.
  • SLS sector level sweep
  • FIG. 1A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented;
  • FIG. 1 B is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;
  • FIG. 1 C 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;
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment
  • FIG. 2 is a diagram which illustrates an Institute of Electrical and Electronics
  • FIG. 3 is an illustration of an exemplary sector level sweep (SLS) procedure
  • FIG. 4 is an example of an exemplary sector sweep (SSW) frame format
  • FIG. 5 is an exemplary illustration of an SSW field
  • FIG. 6 is an example of two SSW feedback field formats for use when and when not transmitted as part of an initiator sector sweep (ISS);
  • FIG. 7 is an exemplary physical layer convergence protocol (PLCP) layer protocol data unit (PPDU) which carries beam refinement protocol (BRP) frame training (TRN) fields;
  • PLCP physical layer convergence protocol
  • PPDU physical layer protocol data unit
  • BRP beam refinement protocol
  • TRN frame training
  • FIG. 8 is a diagram of an enhanced SLS procedure
  • FIG. 9 is an illustration of setting a network allocation vector (NAV) based on a conservative omni-directional receive pattern
  • FIG. 10 is an illustration of a SLS in a beamforming training allocation (BTA).
  • FIG. 11 is an illustration of an access point (AP) inferring when transmissions between STAs may occur simultaneously with a DL transmission from the AP;
  • AP access point
  • FIG. 12 is a flowchart which illustrates a procedure for scheduling overlapping transmissions between stations (STAs) and an AP;
  • FIG. 13 is an illustration of an extended schedule element which may comprise an exemplary group ID.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • 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, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 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, such as the CN 106/115, the Internet 110, and/or the other networks 112.
  • 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, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • 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), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • 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 a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs
  • 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).
  • RAT radio access technology
  • the communications 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, and the like.
  • 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).
  • 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).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by 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., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-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), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • 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.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • 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, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c,
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • IP internet protocol
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links.
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG.
  • the WTRU 102 may include 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 global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any subcombination of the foregoing elements while remaining consistent with an embodiment.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality 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. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • 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) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • 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.
  • 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.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • a base station e.g., base stations 114a, 114b
  • the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be 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.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (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.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors 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.
  • 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.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an 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.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated 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.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell
  • the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME)
  • MME mobility management entity
  • a serving gateway (SGW) 164 a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SGW serving gateway
  • PDN packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the
  • 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 anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the 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.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may facilitate communications with other networks.
  • CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may 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.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • DS Distribution System
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer- to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 ⁇ , and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 ⁇ , 802.11ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, 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) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • 802.11 ah are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an 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.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated 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 for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs
  • WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • 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, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D 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. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b,
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b,
  • the UPF 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, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may facilitate communications with other networks.
  • CN 115 may include, or may 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.
  • IP gateway e.g., an IP multimedia subsystem (IMS) server
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) 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.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the 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 in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • a WLAN in Infrastructure Basic Service Set (BSS) mode has an Access Point or
  • Point Coordinator for the BSS and one or more stations (STAs) associated with the AP/PCP.
  • the AP/PCP typically has access or interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in and out of the BSS.
  • Traffic to STAs that originates from outside the BSS arrives through the AP/PCP and is delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS is sent to the AP/PCP to be delivered to the respective destinations.
  • Traffic between STAs within the BSS may also be sent through the AP/PCP where the source STA sends traffic to the AP/PCP and the AP/PCP delivers the traffic to the destination STA.
  • Such traffic between STAs within a BSS is really peer-to-peer traffic.
  • Such peer-to- peer traffic may also be sent directly between the source and destination STAs with a direct link setup (DLS) using an 802.11e DLS or an 802.11 z tunneled DLS (TDLS).
  • DLS direct link setup
  • TDLS 802.11 z tunneled DLS
  • IBSS Independent BSS
  • a WLAN using an Independent BSS (IBSS) mode has no AP/PCP, and/or STAs, communicating directly with each other. This mode of communication is referred to as an "ad-hoc" mode of communication.
  • the AP/PCP may transmit a beacon on a fixed channel, usually the primary channel.
  • This channel may be 20 MHz wide, and is the operating channel of the BSS.
  • This channel is also used by the STAs to establish a connection with the AP/PCP.
  • the fundamental channel access mechanism in an 802.11 system is Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA).
  • CSMA/CA Carrier Sense Multiple Access with Collision Avoidance
  • every STA, including the AP/PCP will sense the primary channel. If the channel is detected to be busy, the STA backs off. Hence, only one STA may transmit at any given time in a given BSS.
  • 802.11 ad is an amendment to the WLAN standard, which specifies the MAC and
  • VHT very high throughput
  • 802.11 ad has the following features: data rates up to 7 Gbits/s; three different modulation modes including: control PHY with single carrier and spread spectrum, single carrier PHY and OFDM PHY; use of the 60GHz unlicensed band, which is available globally.
  • the wavelength is 5mm, which makes compact and antenna or antenna arrays possible.
  • Such an antenna may create narrow RF beams at both transmitter and receiver, which effectively increase the coverage range and reduce the interference.
  • FIG. 2 illustrates a beacon interval 200.
  • a beacon interval 200 may comprise a beacon transmission interval (BTI) 202, association beamforming training (A-BFT) 204, announcement transmission interval (ATI) 206 and data transmission interval (DTI) 208.
  • the former three intervals e.g. the BTI, A-BFT and ATI, together may be referred to as a beacon header interval (BHI).
  • BHI beacon header interval
  • a beacon interval 200 is composed of three intervals.
  • the BTI 202 comprises multiple beacon frames, each transmitted by the PCP/AP on a different sector to cover all possible directions. This interval 202 may be used for network announcement and beamforming training of the PCP/AP's antenna sectors.
  • a beacon interval may be expressed in time units (TUs).
  • TUs time units
  • A-BFT 204 may be used by STAs to train their antenna sector for communication with the PCP/AP.
  • the PCP/AP exchanges management information with associated and beam-trained stations.
  • the DTI 208 may be comprised of one or more contention-based access periods (CBAPs) and scheduled service periods (SPs) where stations exchange data frames.
  • CBAP contention-based access periods
  • SPs scheduled service periods
  • An SP is assigned for communication between a dedicated pair of nodes as a contention free period.
  • a beamforming training protocol may be comprised of two components: a sector level sweep (SLS) procedure and a beam refinement protocol (BRP) procedure.
  • SLS sector level sweep
  • BRP beam refinement protocol
  • the SLS procedure is used for transmit beamforming training; the BRP procedure enables receive beamforming training, and iterative refinement of both the transmit and receive beams.
  • FIG. 3 represents an exemplary SLS training procedure 300. SLS training may be performed using a beacon frame or a dedicated sector sweep (SSW) frame.
  • SSW dedicated sector sweep
  • the AP/PCP may repeat the beacon frame with multiple beams/sectors within each beacon interval (Bl) and multiple STAs may perform beamforming (BF) training simultaneously.
  • Bl beacon interval
  • a STA may need to wait multiple Bis to complete an initiator sector sweep (ISS) training procedure and latency may become an issue.
  • An SSW frame may be utilized for point to point BF training.
  • an SLS procedure 302 may be performed between an initiator 304 and a responder 306.
  • the initiator 304 may perform an ISS procedure 308 and transmit multiple SS frames 310 during the ISS 308.
  • the responder 306 may perform a responder sector sweep (RSS) 312 and transmit SS frames 314.
  • the initiator 304 may transmit SS feedback 316 acknowledged 318 by the responder 306.
  • Beam refinement 320 may occur over time 322.
  • FIG. 4 illustrates an SSW frame 400 which may be transmitted using control PHY signaling. From left to right, FIG. 4 illustrates a 2 octet frame control field 402, a 2 octet duration field 404, a 6 octet receive address (RA) 406, a 6 octet transmit address (TA) 408, a 3 octet SSW field 410, a 3 octet SSW feedback field 412 and a 4 octet frame check sequence (FCS) field 414.
  • RA receive address
  • TA 6 octet transmit address
  • FIG. 5 illustrates an SSW field 500.
  • the SSW field 500 includes a direction 502, down counter (CDOWN) 504, sector ID 506, DMG antenna ID 508 and a receive sector sweep (RXSS) length field 510.
  • the one bit direction field 502 may indicate a direction of the transmission, for example, to indicate whether the frame is transmitted by a beamforming initiator or responder.
  • CDOWN 504 is a down counter indicating a number of remaining transmissions across all antennas.
  • Sector ID 506 may refer to an identifier of a transmission sector.
  • a DMG antenna ID 508 field may indicate a DMG antenna that an AP or PCP uses to receive frames during an allocation.
  • the RXSS length 510 field may refer to a combined total number of receive sectors over all receive DMG antennas of the STA.
  • FIG. 6 illustrates two distinct SSW feedback field formats 600, 620.
  • 600 may be an SSW feedback field format for use when transmitted as part of an ISS.
  • a total of 24 bits (3 octets) are utilized.
  • the first 9 bits (B0-B8) represent total sectors in ISS 602.
  • the next 2 bits (B9-B10) provide a number of RX directional multi-gigabit (DMG) antennas 604.
  • a reserved field 606 blocks off 5 bits (B11-B15) for potential later use.
  • a bit (B16) 608 may be used to indicate if a poll is required.
  • Another 7 bits (B17-B23) may be reserved 610 for later use.
  • a second SSW feedback field format 620 may be for use when not transmitted as part of an ISS.
  • 24 bits are again utilized.
  • the first 6 bits (B0-B5) represent a sector select 622.
  • Sector select 622 may be set to one or more values corresponding to a sector from the initiator DMG antenna that was used to transmit the SSW feedback.
  • the next 2 bits (B6- B7) provide for a DMG antenna select 624.
  • An antenna select 624 may be used to indicate a value of an RF Chain ID field.
  • a signal to noise ratio (SNR) report 626 may occupy 8 bits (B8-B15).
  • a bit (B16) may be used to indicate if a poll is required 628.
  • Another 7 bits (B17-B23) may be reserved 630 for future use.
  • Beam refinement is a process where a STA may improve its antenna configuration or antenna weight vectors both for transmission and reception.
  • BRP packets are used to train the receiver and transmitter antenna.
  • BRP packet may be carried by a DMG physical layer convergence protocol (PLCP) protocol data unit (PPDU) followed by a training field containing an automatic gain control (AGC) field and a transmitter or receiver training field as shown in FIG. 7.
  • PLCP physical layer convergence protocol
  • PPDU protocol data unit
  • a BRP packet may be carried by a DMG physical layer convergence protocol (PLCP) protocol data unit (PPDU) followed by a training field containing an automatic gain control (AGC) field and a transmitter or receiver training field as shown in FIG. 7.
  • a BRP packet may be carried by a DMG physical layer convergence protocol (PLCP) protocol data unit (PPDU) followed by a training field
  • FIG. 7 illustrates an exemplary PLCP layer PPDU 700 which includes a PLCP header 702 and carries a BRP frame 704, ACG field 706 and TRN-R/T field 708.
  • a value of N represents the training length given in the header field, which in this example indicates that the AGC 706 has 4N subfields and that the TRN-R T field 708 has 5N subfields.
  • the header field 702 may also comprise bandwidth information, a channel allocation, a single user or multi-user (SU/MU) indication, a modulation and coding scheme (MCS), a guard interval / cyclic prefix (GI/CP) length field and/or a number of spatial streams (SS).
  • MCS modulation and coding scheme
  • GI/CP guard interval / cyclic prefix
  • the channel estimation (CE) subfield may be the same as the one in the preamble.
  • One or more subfields in the beam training field are transmitted using rotated ⁇ /2 binary phase shift keying ( ⁇ /2-BPSK) modulation.
  • Each one of the 4N AGC subfields comprises 64 point Golay sequences (Ga64) . Other block sizes may also be used.
  • a BRP medium access control (MAC) layer frame may be an Action No ACK frame, which has the following fields: Category; Unprotected DMG Action; Dialog Token; BRP Request field; DMG Beam Refinement element; Channel Measurement Feedback element 1 to Channel Measurement Feedback element k.
  • MAC medium access control
  • Task Group ay may define standardized modifications to both the IEEE
  • TGay may also define operations for license-exempt bands above 45 GHz while ensuring backward compatibility and coexistence with legacy directional multi-gigabit stations, defined by IEEE 802.11 ad-2012 amendment, operating in the same band.
  • IEEE 802.11 ad-2012 amendment a much higher maximum throughput than that of 802.11 ad is a primary goal of TGay, some members of the group also proposed to include mobility and outdoor support. More than ten different use cases are proposed and analyzed in terms of throughput, latency, operation environment and applications.
  • 802.11 ay may operate in the same band as legacy standards, it is required that the new technology ensure backward compatibility and coexistence with legacies in the same band.
  • 802.1 l ay may support the following technologies: MIMO transmission, including SU-MIMO and MU-MIMO and multi-channel transmission, including channel bonding and channel aggregation.
  • an enhanced SLS procedure was proposed and agreed.
  • One method included in a contribution includes appending a TRN-R field to a DMG beacon frame. This may allow enhanced directional multi-gigabit (EDMG) STAs to perform RX training using beacon frames.
  • EDMG enhanced directional multi-gigabit
  • a beamforming training allocation is introduced in a data transmission interval (DTI).
  • DTI data transmission interval
  • a non-sector specific BTA is scheduled using an EDMG extended schedule element which is identical in all DMG beacons frames in the BTI.
  • an AP/PCP repeats a sector sweep in the same order as in the BTI, but in the RX mode.
  • a sector-specific BTA corresponding to a particular sector is scheduled using an EDMG extended schedule element in a DMG beacon frame transmitted from the sector.
  • STAs respond in a sector which corresponds to best sector during BTI TXSS.
  • a sector ACK frame may be transmitted from the AP/PCP in each sector.
  • the beamforming training allocation has two sub-phases: a responding sub- phase and an acknowledgement sub-phase.
  • STAs may transmit responding frames to the AP/PCP.
  • acknowledgement sub-phase the AP/PCP transmits acknowledgement to the STAs.
  • a directional allocation is introduced in a DTI portion. In this allocation, the AP/PCP's receive sector is specified and may be used to listen during the allocation.
  • FIG. 8 illustrates an enhanced SLS procedure 800 in a BTI 812.
  • FIG. 8 shows an initiator AP/PCP 802 and a plurality of responder STAs 804-810.
  • the initiator AP/PCP 802 performs TXSS transmitting through all sectors available 818-822.
  • responder STAs X 804, Y 806, Z 808, and L 810 are configured to receive using a quasi-omni directional pattern.
  • the responder STAs 804-810 may receive a TRN-R field appended to the DMG beacon frame and the STAs may use the appended TRN-R field to train for an antenna pattern, therefor discovering the best RX sector of the plurality of sector based transmissions.
  • STA X 804 receives best beam 824 in sector 1 820;
  • STA Y 806 receives best beam 826 in sector N-1 822;
  • STA Z 808 receives best beam 828 in sector 1 820;
  • STA L 810 receives best beam 830 in sector 0 818.
  • a beamforming training allocation portion may be performed.
  • the initiator AP/PCP 802 may configure a RX antenna to a directional mode.
  • the initiator AP/PCP 802 may repeat the sector sweep procedure of the BTI 812, but in this case using a RX mode.
  • Each one of the responder STAs 804-810 may transmit a frame to the initiator AP/PCP 802 in the sector which is detected as the best sector during the BTI 812 TXSS.
  • the responded transmission is performed in directional mode using the same sector trained during the BTI TRN-R.
  • time slots for example space-time slots, may be assigned for responders' transmissions.
  • An A-BFT section may not be used in a method and is shown only for exemplary purposes. Transmissions 832-838 to initiator AP/PCP 802 are shown for exemplary purposes only.
  • the responder AP/PCP may begin listening in the operating sector.
  • STA X 804 transmits 840 on a same sector as a transmission 842 of STA Z 808, however transmissions of these STAs are made on two different space-time slots.
  • STA Y 806 may transmit 844 at a time thereafter.
  • the initiator AP/PCP 802 may broadcast one or more sector ACK frames 846-848 containing information about every STA which transmission information is discovered in a corresponding sector and may also broadcast instructions for other STAs in this sector.
  • the EDMG AP or EDMG PCP should request each source DMG STA and each destination DMG STA involved in each candidate SP to perform measurements only after the STAs have beamforming trained with each other.
  • the EDMG AP or EDMG PCP should request each source DMG STA and each destination DMG STA involved in each candidate SP to perform measurements only after the STAs have beamforming trained with each other.
  • communication between 2 STAs which both are non-AP STAs beamforming trainings are required before the peer to peer communication takes place.
  • this may require an AP/PCP to allocate a SP for the two STAs to perform SLS and subsequent refinements. These procedures may take place in parallel with other STA communications with the AP/PCP so the resource may be fully utilized.
  • FIG. 9 illustrates an exemplary use of an omni-directional radio 900.
  • an AP-B 902 listens in a quasi-omni receive pattern in a contention-based access period (CBAP) in order to receive possible UL access from STAs in different directions.
  • CBAP contention-based access period
  • the NAV of AP-B 902 is set based on the duration setting of the overheard RTS/CTS message(s) 908.
  • AP-B 902 wishes to perform DL data transmission to STA-B 912 by sending RTS 910 to STA-B, but the NAV of AP-B 902 prevents it from initiating a transmit opportunity (TXOP).
  • TXOP transmit opportunity
  • the device initiating or accepting a new connection announces its intention in every direction (by sending an RTS or CTS message), thus preventing incoming connections to itself; in the directional (based on beamforming) case, the primary initiator does not broadcast its RTS in every direction, but rather sends it to its intended target (as it could be interfering with other existing transmissions if not using directional mode); similarly, the respondent of the primary initiator (termed here "primary responder”) replies with a CTS message in the directional mode as well; finally, the primary link (between the primary initiator and the respective responder) is established, while a number of other devices proximate to the primary link members may be unaware of this, and are likely to attempt communicating with the primary link members.”
  • a straightforward remedy for this problem is to apply spatial expansion, for example, sending duplicate copies of the same message on different directions, in one embodiment, with different small time offsets on the RTS message such that the 3rd party STAs would know the primary initiator/responder is busy for a NAV duration.
  • the 3rd party STAs should set their NAV and wait.
  • this solution is not considered complete without addressing the following issues:
  • the 3rd party STAs may not hear the directional CTS from the primary responder, or may not hear the start of the data transmission from the primary initiator because of a beamformed data transmission.
  • the NAV is then reset at the 3rd party STAs.
  • These STAs may start their own TXOP to communicate with primary link members (e.g. primary initiator is an AP) and would not get a response, causing an unbounded inflation of contention window.
  • a transmission with spatial expansion of a CTS-to-self message may resolve the NAV reset issue.
  • the OBSS STAs may not initiate communications within their BSS even if the communications do not interfere with the primary link.
  • an AP/PCP may assign a SP or CBAP for an uplink transmission, where the AP/PCP may perform directional reception by listening on a certain sector or sectors.
  • the AP/PCP may announce one or more receive sector(s) in advance such that non-AP/PCP STAs may notice the directional receive mode.
  • the allocation with directional receive mode may be a BTA, a directional allocation as shown in FIG. 8 or another type of allocation.
  • the receive sector(s) may be announced in beacon frames or other management/control frames.
  • non-AP/PCP STAs which may not be covered by that or those sector(s) or beam(s) may transmit. The transmission may not have significant interference to the AP/PCP reception.
  • methods and procedures are disclosed to enable spatial sharing on the existing SP/CBAP with directional reception.
  • Detailed procedures of spatial sharing transmission with an existing directional allocation may be disclosed. Terminologies including an "existing allocation" and a “candidate allocation” are used and are described further.
  • An existing allocation may refer to a main allocation, in which the AP/PCP may listen in one or more sectors, for example, during a BTA, or a directional allocation.
  • the term “candidate allocation” may refer to an allocation which may be concurrent with the existing allocation and may not interfere with an existing allocation.
  • the STA may need to know a set of sectors J from the STA from which an AP/PCP sector i cannot receive a signal.
  • the set of sectors J of the STA which corresponds to the sector i of the AP/PCP may be determined via the receive sector sweep (RXSS) of the STA performed during the TRN-R transmission of the DMG beacon from sector X. Therefore, when the AP/PCP may have an existing allocation with certain receive sector(s), the AP/PCP may schedule a concurrent allocation, for example, the candidate allocation to one or more STAs which may not be covered by the receive sector(s) of the existing allocation.
  • the candidate allocation may be used by two non-AP STAs to perform beamforming training while the AP/PCP is receiving from other STAs.
  • the feedback between these two STAs may be relayed through the AP/PCP using the established beamformed link.
  • the STA may acquire that information to feedback through one or more of the following procedures: SLS training and/or enhanced SLS training between the STAs which may be involved into the candidate allocation; BRP training and/or enhanced BRP training between the STAs which may be involved into the candidate allocation; a directional channel quality request/report between the AP/PCP for the two STAs involved into the candidate allocation.
  • a duration in which an AP/PCP receives at a pre-announced non-omni direction is referred to as a space-time slot.
  • An AP/PCP may allocate a candidate SP to a first and second STA, STA1 and STA2, to perform SLS training or data transmission at the same time as an allocation with directional receive mode, for example, the duration of AP/PCP reception in the BTA of FIG. 10, or at the same time as an SP in which an AP receives directionally.
  • STA1 is assigned to this SP and may already be associated with the AP/PCP and have previously performed SLS training with the AP/PCP.
  • STA1 may evaluate on a per Bl basis which TX antenna weight vector (AWV)/sector of STA1 could not be heard by AP/PCP when the AP/PCP operates on certain RX sectors.
  • AMV antenna weight vector
  • This evaluation is made possible by the enhanced BTI, which is supplemented with RX-TRN fields, as described in FIG. 8.
  • STA1 may record the TX sectors with strong and weak receive signal quality. STA1 may report the strong/weak TX sector information to the AP/PCP, for example, using the directional channel quality report for BTI. For a TX sector / from the AP/PCP, during the RX sector sweep (RXSS) training of the beacon trailer, STA1 may sweep through its RX sectors and determines a set of RX sectors J at which STA1 does not receive signal. In addition, the STA1 is also aware of the AP/PCP's RX sector in each space-time slot. This information is provided, in one embodiment, in a beacon frame, for the other STAs to perform association/random access to the AP/PCP using the space-time slots.
  • RXSS RX sector sweep
  • FIG. 10 illustrates an example 1000 of which during a space-time slot 1008 an AP
  • STA1 1004 may potentially transmit 1010 at a sector from set J without interfering 1012 with the reception 1008 at the AP/PCP 1002. Based on the receive direction at the AP 1002 during the time space-time slot, STA1 1004 may re-order its SLS sector sweep sequences and transmit (short) SSW frames 1010, 1014, 1016 in synchronization with the space-time slot.
  • a (short) SSW frame may be sent using STAI's 1004 TX sector j, in set J, which corresponds one of the worst RX sector trained by TRN-R field in the previous BTI corresponding to AP/PCP's sector / ' .
  • STAI's 1004 TX sector j in set J, which corresponds one of the worst RX sector trained by TRN-R field in the previous BTI corresponding to AP/PCP's sector / ' .
  • the STA1 1004 has no TX sector j matching the above criteria. In this case, the STA does not transmit a (short) SSW frame in this slot. If the STA does not receive a beacon frame from an AP/PCP's sector /, it may add all of its RX sectors into the set J associated with the AP/PCP's sector /.
  • the AP 1002 may inform STA1 1004 to perform SLS with the same TX sector/AWV in this (sub)set of slots, to facilitate the RXSS of a peer STA2 1006 who is the responder of the SLS, and to reduce the possibility of a collision at STA2 1006, who may be hearing SSW from STA1 1004 and a transmission of another STA which is using the space-time slot to access the AP/PCP 1002 at the same time.
  • the AP 1002 assigns the space-time slots to STA1 1004, the AP 1002 also informs a STA2 1006 to perform the role of responder, for example, to listen to the (short) SSW frames in a quasi-omni or in a RXSS manner if the AP configures STA1 1004 to perform RXSS.
  • STA2 1004 performs SLS by transmitting (short) SSW frames in a set of space-time slots assigned by the AP.
  • the STA2 1006 may feedback the result to AP/PCP 1002 and skip performing responder SLS.
  • STA1 1004 and STA2 1006 may report back to the AP/PCP 1002 the peer's TX sector(s) that each STA can receive (short) SSW frames with adequate signal strength. Additionally, STAs may report back the slot identification, such that AP would know that communication between STA1 and STA2 could happen simultaneously when the AP's sector corresponding to the slot is transmitting or receiving to/from other STAs. STA2 may receive transmission 1016 from STA1 and begin simultaneous communication without affecting 1018 AP 1002 or other STAs 1020.
  • FIG. 11 shows that an AP 1102 may infer that STA2 1106 -> STA1 1104 transmission may occur simultaneously with a DL transmission from the AP 1102.
  • the left hand side of FIG. 11 is a copy of FIG. 10 and shows that STA2 1106 reported to the AP 1102 that it received a best sector from STA1 1104 at space-time slot 1108.
  • the AP 1102 may then infer that: if the AP/PCP 1102 receives STA X's 1112 transmission in space time slot 1108, at the same time STA1 1104 and STA2 1106 performs training, it may potentially schedule a transmission 1110 from STA2 1106 to STA1 1104, simultaneously with the AP's 1102 DL transmission 1112 to STA X 1112 in the sector/AWV that the AP 1102 used for receiving in space-time slot 1108.
  • the AP 1102 may also infer that if the AP/PCP 1102 receives STA X's 1114 transmission in space time slot 1108 at the same time STA1 1104 and STA2 1106 perform training, then the AP 1102 may schedule STA1 1104 to STA2 1106 transmission at the same time for a future UL transmission from STA X 1112 to the AP/PCP's 1102 sector corresponding to time slot 1108.
  • the AP/PCP 1102 may indicate that spatial sharing is allowed in the existing allocation with directional receive mode, for example, BTA, directional allocation, or the like. This may enable OBSS SP/CBAP transmission. SLS retry may be possible with a smaller number of sectors due to a collision.
  • FIG. 12 is a flowchart 1200 which illustrates a procedure for scheduling overlapping transmissions between STAs and an AP.
  • STA2 may report the identification 1208 of the slot n to the AP/PCP.
  • the failure to decode may be caused by the collision at STA2 as other STAs may be transmitting to the AP/PCP.
  • the AP/PCP schedules 1210 in one or more of the next opportunities STA1 in space-time slots which has the same receive direction/sector at the AP as the failed slot n, to perform additional SLS transmissions from the same TX sector of the STA1 as the one in the previously failed slot n.
  • AP/PCP also informs 1212 STA2 of the retransmission slots that the retry of SLS from STA1 is scheduled.
  • the subsequent round of SLS may need less number of space-time slot assignments because AP/PCP and transmitter already know the TX sectors needs to be retransmitted.
  • AP/PCP may schedule a dedicated SP to STA1 to performed SSW from sectors corresponding to the slots reported by STA2 as failed slots.
  • STA2 re-evaluates 1216 the best sector of STA1 and report back to AP/PCP. If during the retransmission, there is still a collision, for example, energy was detected but packet detection/decoding failed at STA2 at a space-time slot, STA2 may report to AP/PCP the slot identity. This report may allow for an additional retry to be scheduled. If STA2 no longer detects energy in the retransmission slots, it reports back to the AP/PCP the best sector of STA1 and indicates it no longer detects collision.
  • the AP may schedule the space-time slot such that STA1 is receiving at the previously failed TX sector, while STA2 transmits in an antenna pattern it would normally use for the reception of SLS.
  • the AP/PCP may request a directional channel quality report from STA1 and STA2 using trained sectors between STA1 and STA2, for measuring interference during the BTA or BTI duration, or any duration that AP/PCP is not receiving omni-directionally.
  • STA2 reports at time block n, which corresponds to a receiving sector at AP at the time slot 1108 on the left hand side of FIG. 11 , that STA2 1106 does not receive excessive interference using the trained sector with STA1 1104. If the AP at time block n, has received a transmission from a STA X, then the AP 1102 may infer that STA s 1106 transmission to STA1 1104 may occur simultaneously with AP's 1104 transmission to STA X, if the AP 1102 transmits using the sector corresponding time slot 1108, as shown to the right of FIG. 11. This information may then be utilized for future SP scheduling.
  • the channel quality report of BTI may let the AP/PCP discover additional sector/AWVS that the AP may TX/RX simultaneously when STA1 and STA2 receives or transmits.
  • Either an AP or non-AP STA may perform one or more of the following steps.
  • AP/TXOP initiator may use a group ID as a source or destination association identifier (AID) in an allocation field of an Extended Schedule Element or EDMG Extended Schedule Element.
  • AID source or destination association identifier
  • FIG. 13 illustrates an EDMG extended schedule element 1300.
  • the extended schedule element 1300 may include an element ID 1302, length 1304, element ID extension 1306, number of allocations 1308 and a plurality of channel allocation fields 1311-1314 corresponding to the number of allocations.
  • Each channel allocation 1310-1414 may comprise a scheduling type field 1316, allocation key 1318, channel aggregation field 1320, bandwidth field 1322, asymmetric beamforming training field 1324, receive direction 1326 and a field reserved 1328 for later use.
  • the allocation key field 1318 may comprise an allocation ID 1330, source AID 1332, destination AID 1334.
  • Source AID 1332, destination AID 1334 may indicate a value which is a Group ID.
  • the allocation to a group of STAs may not necessarily be for multiple user multiple- input multiple-output (MU-MIMO) transmissions, but to serve the purpose of limiting the STAs that may be reached by a NAV-setting message which is sent with spatial expansion.
  • the STAs may potentially use this allocation to communicate with the AP.
  • the deafness problem may be avoided due to the message being sent in other directions to reach other STAs.
  • these STAs When these STAs receive the NAV-setting message, they will expect that the TXOP initiator/TXOP responder is busy for a NAV duration and should not attempt transmission to the TXOP initiator/TXOP responder.
  • a first NAV setting message for example a request to send (RTS) or a clear to send to self (CTS-to-self) message may have a TRN field appended or included.
  • the message may have a unicast RA.
  • An intended receiver, for example a transmission opportunity (TXOP) responder of the message may reply with a second NAV setting message.
  • TXOP transmission opportunity
  • a data transmission to the TXOP responder may follow immediately after the first message.
  • the second NAV setting message for example a CTS or denial-to-send (DTS), may also have a TRN field appended or included.
  • All the TRN subfields of the TRN field of the first or the second NAV setting message may be transmitted using an AWV/sector of each TX antenna, repeated for the entire TRN field.
  • the AWV/sector of each TX antenna may be the one used for data TX/RX after the NAV setting message(s).
  • a portion of the first or the second NAV-setting message which is not a TRN field may be sent with spatial expansion to reach more than one STA, or may be sent using the same AWV/sector used to transmit TRN subfields.
  • the first or the second message may have a control trailer or EDMG header-A indicating the group ID.
  • an EDMG header-A may include a bandwidth field to indicate one or more channels in which the first or second message is transmitted on.
  • an EDMG header-A may also include a primary channel number, length and information about the appended TRN field.
  • Information about the TRN field may include a length or configuration. The length may be variable depending on how much training information is transmitted. In accordance with FIG. 7, a training length may be specified in accordance with a number of training subfields.
  • the first or the second message may have an indication to identify the BSS of the
  • a one bit indication to identify the sender of the message may be included. This one bit may indicate that the sender is an AP/PCP.
  • the indication may be a field which is a (partial) BSSID or a color code.
  • a 3rd party STA may, in accordance with this indication, and/or TA/RA of the 1st or the 2nd message, and/or its own associated BSSID, determine that the 1st or the 2nd message is sent by an OBSS STA.
  • the packet type of the first or the second NAV setting message may be BRP-RX or
  • the 3rd party STA may not perform a NAV reset procedure which would normally be performed after receiving a RTS message but not after receiving a CTS message or a preamble of a data packet.
  • a 3rd party STA may mark the NAV associated with the TXOP initiator and the
  • TXOP responder with: which sector/AWV receives no or negligible signal during the receive training of the NAV-setting message(s), or which sector/AWV receives sufficiently strong signal during the receive training of the NAV-setting message(s).
  • the channel occupancy is indicated by the NAV setting message.
  • a 3rd party STA x may initiate or respond to a parallel TXOP to/from a STA y which is not the TXOP initiator or responder of the 1st or the 2nd NAV-setting message(s), if the sector/AWV used by STA x to communicate with STA y does not include the sector/AWV marked as receiving a sufficiently strong signal during the receive training for the NAV associated with the TXOP initiator and responder, or is within the set of sectors marked as receiving no or negligible signal during the receive training for the NAV associated with the TXOP initiator and responder, or the channel(s) used by the parallel TXOP does not include the channel marked as occupied in the NAV associated with the TXOP initiator and responder.
  • a 3rd party STA x may not respond to or may reject, for example, by responding with a DMG DTS, a parallel TXOP from a STA y which is not the TXOP initiator or responder of the 1st or the 2nd NAV-setting message(s), if the sector/AWV used by STA x to communicate with STA y includes the sector/AWV marked as receiving sufficiently strong signal during the receive training for the NAV associated with the TXOP initiator and responder, or is not within the set of sectors marked as receiving no or negligible signal during the receive training for the NAV associated with the TXOP initiator and responder, and/or the channel(s) used by the parallel TXOP includes the channel marked as occupied in the NAV associated with the TXOP initiator and responder.
  • a 3rd party STA which initiates a parallel TXOP may limit the end of the parallel
  • TXOP to be not later than the end of the TXOP of the 1st or the 2nd NAV-setting message.
  • the TXOP initiator/responder of the 1st or the 2nd NAV-setting message is not aware of the parallel TXOP and may initiate a subsequent TXOP which interferes with the parallel TXOP.
  • a 3rd party STA responding to a parallel TXOP may revise the end of the parallel TXOP to be not later than the end of the TXOP of the 1st or the 2nd NAV-setting message.
  • This embodiment may be applied to a system which uses a virtual carrier sensing (CS) mechanism similar to IEEE 802.11 NAV and uses directional transmission/reception.
  • CS virtual carrier sensing
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, 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).
  • ROM read only memory
  • RAM random access memory
  • register 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 in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil permettant de recevoir un message de réglage de NAV. Le message de réglage de NAV peut comprendre au moins un ID de groupe, un champ de durée et un champ TRN. Sur la base de l'ID de groupe du message de réglage de NAV, il peut être déterminé si le message de réglage de NAV est oui ou non un message d'un même BSS d'une STA. Cette détermination peut fournir une indication permettant de déterminer si un AP associé est occupé ou pas pendant la durée indiquée par le message de réglage de NAV. Lorsqu'un AP associé est occupé, une STA peut déterminer de ne pas transmettre. Lorsqu'un AP associé est disponible, une STA peut transmettre en conséquence. Un AP peut également effectuer une détermination visant à transmettre des données disponibles sur la base de tout message de réglage NAV reçu. Cette détermination peut être basée sur un ID de groupe, un champ TRN ou une combinaison des deux.
PCT/US2018/021754 2017-03-10 2018-03-09 Procédures de partage spatial dans des systèmes wlan WO2018165554A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762469940P 2017-03-10 2017-03-10
US62/469,940 2017-03-10

Publications (1)

Publication Number Publication Date
WO2018165554A1 true WO2018165554A1 (fr) 2018-09-13

Family

ID=61837828

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/021754 WO2018165554A1 (fr) 2017-03-10 2018-03-09 Procédures de partage spatial dans des systèmes wlan

Country Status (1)

Country Link
WO (1) WO2018165554A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10912093B2 (en) 2018-10-04 2021-02-02 Sony Corporation Spatial loading announcement in MMW WLAN networks
US11405081B2 (en) * 2017-07-28 2022-08-02 Lg Electronics Inc. Method for performing MU-MIMO beamforming training in wireless LAN system, and method and device for supporting MU-MIMO beamforming training

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016112287A1 (fr) * 2015-01-09 2016-07-14 Interdigital Patent Holdings, Inc. Procédés, appareils et systèmes permettant la prise en charge de transmissions multi-utilisateurs dans un système de réseau local sans fil (wlan)
US20170048048A1 (en) * 2015-08-14 2017-02-16 Newracom, Inc. Block acknowledgement for multi-user transmissions in wlan systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016112287A1 (fr) * 2015-01-09 2016-07-14 Interdigital Patent Holdings, Inc. Procédés, appareils et systèmes permettant la prise en charge de transmissions multi-utilisateurs dans un système de réseau local sans fil (wlan)
US20170048048A1 (en) * 2015-08-14 2017-02-16 Newracom, Inc. Block acknowledgement for multi-user transmissions in wlan systems

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11405081B2 (en) * 2017-07-28 2022-08-02 Lg Electronics Inc. Method for performing MU-MIMO beamforming training in wireless LAN system, and method and device for supporting MU-MIMO beamforming training
US10912093B2 (en) 2018-10-04 2021-02-02 Sony Corporation Spatial loading announcement in MMW WLAN networks

Similar Documents

Publication Publication Date Title
US11843428B2 (en) MIMO channel access
US11750251B2 (en) Methods and apparatus for enhanced dynamic allocation for directional transmission
US20210234594A1 (en) Multiple channel transmission in mmw wlan systems
US20220216898A1 (en) Multi channel multiple input multiple output beamforming training in millimeter wave systems
US11895517B2 (en) Enhanced fragmented sector level sweep procedure in MMW WLAN systems
US20200059950A1 (en) Dynamic allocation in dense mmwave networks
WO2018165554A1 (fr) Procédures de partage spatial dans des systèmes wlan

Legal Events

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

Ref document number: 18714899

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18714899

Country of ref document: EP

Kind code of ref document: A1