[go: up one dir, main page]

WO2016175614A1 - Procédé d'envoi et de réception de signal de réponse de confirmation pour données multiutilisateur de liaison montante dans un système de réseau local sans fil, et appareil correspondant - Google Patents

Procédé d'envoi et de réception de signal de réponse de confirmation pour données multiutilisateur de liaison montante dans un système de réseau local sans fil, et appareil correspondant Download PDF

Info

Publication number
WO2016175614A1
WO2016175614A1 PCT/KR2016/004550 KR2016004550W WO2016175614A1 WO 2016175614 A1 WO2016175614 A1 WO 2016175614A1 KR 2016004550 W KR2016004550 W KR 2016004550W WO 2016175614 A1 WO2016175614 A1 WO 2016175614A1
Authority
WO
WIPO (PCT)
Prior art keywords
sta
frame
field
user
sig
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2016/004550
Other languages
English (en)
Korean (ko)
Inventor
김정기
류기선
조한규
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics 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 LG Electronics Inc filed Critical LG Electronics Inc
Priority to US15/567,009 priority Critical patent/US10284287B2/en
Publication of WO2016175614A1 publication Critical patent/WO2016175614A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2612—Arrangements for wireless medium access control, e.g. by allocating physical layer transmission capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0404—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas the mobile station comprising multiple antennas, e.g. to provide uplink diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0452—Multi-user MIMO systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0005—Synchronisation arrangements synchronizing of arrival of multiple uplinks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space

Definitions

  • the following description relates to a method and apparatus for transmitting and receiving an acknowledgment signal for multi-user or multi-station (STA) data in a WLAN system.
  • STA multi-station
  • IEEE 802.11a and b are described in 2.4. Using unlicensed band at GHz or 5 GHz, IEEE 802.11b provides a transmission rate of 11 Mbps and IEEE 802.11a provides a transmission rate of 54 Mbps.
  • IEEE 802.11g applies orthogonal frequency-division multiplexing (OFDM) at 2.4 GHz to provide a transmission rate of 54 Mbps.
  • IEEE 802.11n applies multiple input multiple output OFDM (MIMO-OFDM) to provide a transmission rate of 300 Mbps for four spatial streams. IEEE 802.11n supports channel bandwidths up to 40 MHz, in this case providing a transmission rate of 600 Mbps.
  • the WLAN standard uses a maximum of 160MHz bandwidth, supports eight spatial streams, and supports IEEE 802.11ax standard through an IEEE 802.11ac standard supporting a speed of up to 1Gbit / s.
  • An object of the present invention is to provide a method for efficiently setting signaling for transmitting an M-BA frame based on 11ax PPDU and an apparatus for performing the same.
  • the present invention is not limited to the above-described technical problem and other technical problems can be inferred from the embodiments of the present invention.
  • a method for receiving a multi-STA BlockAck (M-BA) frame by a station (STA) is based on a UL MU based on a trigger frame.
  • transmitting an uplink multi-user frame receiving an M-BA frame based on an OFDMA physical layer protocol data unit (PPDU) including an SIG B field; And obtaining a data stream including an ACK / NACK for the STA from the OFDM-A PPDU-based M-BA frame, wherein the STA includes a predetermined number of user fields included in the SIG B field.
  • PPDU physical layer protocol data unit
  • Another STA that has obtained the data stream according to the indication of the user field identified by ID, and wherein the data stream indicated by the user field identified by the predetermined ID performs UL MU transmission based on the trigger frame.
  • the same may be assigned to these.
  • a station (STA) for receiving an M-BA (Multi-STA BlockAck) frame may include a UL MU (based on a trigger frame).
  • a transmitter for transmitting an uplink multi-user) frame;
  • a receiver for receiving an M-BA frame based on an OFDMA physical layer protocol data unit (PPDU) including a SIG B field;
  • PPDU physical layer protocol data unit
  • a processor for obtaining a data stream including an ACK / NACK for the STA from the OFDM-A PPDU-based M-BA frame, wherein the processor comprises: a predetermined number of user fields included in the SIG B field; Another STA that has obtained the data stream according to the indication of the user field identified by ID, and wherein the data stream indicated by the user field identified by the predetermined ID performs UL MU transmission based on the trigger frame. The same may be assigned to these.
  • RUs resource units
  • whether at least one RU to which the STA and the other STAs are multiplexed is MU-MIMO allocated or single user (SU) allocated may be indicated by the RU allocation index set in the user common field. have.
  • the predetermined ID may be a group ID (GID) assigned through the trigger frame or an association ID (AID) of the STA.
  • GID group ID
  • AID association ID
  • the GID is assigned by a combination of a reference GID and a GID index included in the trigger frame, and the GID index indicates a difference between a value of the reference GID and a value of a GID assigned to the STA. can do.
  • the trigger frame may indicate whether the GID is allocated to the STA through a trigger type subfield or a GID providing subfield.
  • each of the plurality of user fields may include a spatial configuration index indicating whether the corresponding user field corresponds to MU-MIMO allocation or single user (SU) allocation. .
  • the number of data streams of the corresponding user field indicated by the spatial setting index is equal to the total number of data streams for all of the plurality of user fields. Can be set.
  • the data stream of the N + 1th user field may be set to be the same as the data stream of the Nth user field.
  • an AP transmits a multi-STA BlockAck (M-BA) frame to a station (STA) Transmitting a trigger frame to a plurality of STAs including a first STA and a second STA; Receiving a plurality of UL uplink multi-user (MU) frames from the plurality of STAs based on the trigger frame; And transmitting an M-BA frame based on an OFDMA physical layer protocol data unit (PPDU) including a SIG B field in response to receiving the UL MU frames, wherein the AP includes a plurality of M-BA frames included in the SIG B field.
  • M-BA multi-STA BlockAck
  • the data stream of the first STA assigned by the first user field, UL based on the trigger frame may be allocated to the second STA that has performed MU transmission.
  • the M-BA frame can be efficiently transmitted and received.
  • FIG. 1 is a diagram illustrating an example of a configuration of a WLAN system.
  • FIG. 2 is a diagram illustrating another example of a configuration of a WLAN system.
  • FIG. 3 is a diagram illustrating a block Ack mechanism utilized in a WLAN system.
  • FIG. 4 is a diagram illustrating a basic configuration of a block acknowledgment frame.
  • FIG. 5 is a diagram illustrating a specific configuration of a BA control field shown in FIG. 4.
  • FIG. 6 is a diagram illustrating a specific configuration of a BA information field shown in FIG. 4.
  • FIG. 7 is a diagram illustrating the configuration of a Block Ack start sequence control subfield.
  • FIG. 8 is a diagram illustrating a BA information field configuration of a compressed Block Ack frame.
  • FIG. 9 illustrates a BA information field of a Multi-TID Block Ack frame.
  • FIG. 12 shows an example of a HE PPDU.
  • FIG. 13 shows another example of an HE PPDU.
  • FIG. 14 shows another example of an HE PPDU.
  • 15 shows another example of an HE PPDU.
  • 16 shows another example of an HE PPDU.
  • 17 and 18 illustrate a padding scheme for HE-SIG B.
  • FIG 19 illustrates an uplink multi-user transmission situation according to an embodiment of the present invention.
  • FIG. 20A illustrates a trigger frame format according to an embodiment of the present invention.
  • M-BA Multi-STA BA
  • FIG 21 illustrates an M-BA frame according to an embodiment of the present invention.
  • FIG. 23 shows an example of an HE-SIG B structure according to an embodiment of the present invention.
  • FIG. 24 illustrates an embodiment in which an UL MU resource mapping ID is used according to an embodiment of the present invention.
  • FIG. 25 shows an embodiment of repeatedly transmitting an M-BA frame in units of 242 tones according to an embodiment of the present invention.
  • 26 illustrates M-BA frame transmission according to an embodiment of the present invention.
  • 27A-27O illustrate a trigger frame in accordance with embodiments of the present invention.
  • 28A and 28B illustrate channel-specific M-BA IDs according to embodiments of the present invention.
  • FIG 29 illustrates an M-BA frame according to another embodiment of the present invention.
  • FIG 30 illustrates STA multiplexing according to an embodiment of the present invention.
  • FIG. 31 illustrates an HE-SIG B field according to an embodiment of the present invention.
  • FIG 32 illustrates an M-BA frame transmission and reception method according to an embodiment of the present invention.
  • 33 is a view for explaining an apparatus according to an embodiment of the present invention.
  • the following description relates to a method and an apparatus therefor for efficiently utilizing a channel having a wide band in a WLAN system.
  • a WLAN system to which the present invention is applied will be described in detail.
  • FIG. 1 is a diagram illustrating an example of a configuration of a WLAN system.
  • the WLAN system includes one or more basic service sets (BSSs).
  • BSS is a set of stations (STAs) that can successfully synchronize and communicate with each other.
  • An STA is a logical entity that includes a medium access control (MAC) and a physical layer interface to a wireless medium.
  • the STA is an access point (AP) and a non-AP STA (Non-AP Station). Include.
  • the portable terminal operated by the user among the STAs is a non-AP STA, and when referred to simply as an STA, it may also refer to a non-AP STA.
  • a non-AP STA is a terminal, a wireless transmit / receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile terminal, or a mobile subscriber. It may also be called another name such as a mobile subscriber unit.
  • the AP is an entity that provides an associated station (STA) coupled to the AP to access a distribution system (DS) through a wireless medium.
  • STA station
  • DS distribution system
  • the AP may be called a centralized controller, a base station (BS), a Node-B, a base transceiver system (BTS), or a site controller.
  • BS base station
  • BTS base transceiver system
  • BSS can be divided into infrastructure BSS and Independent BSS (IBSS).
  • IBSS Independent BSS
  • the BBS shown in FIG. 1 is an IBSS.
  • the IBSS means a BSS that does not include an AP. Since the IBSS does not include an AP, access to the DS is not allowed, thereby forming a self-contained network.
  • FIG. 2 is a diagram illustrating another example of a configuration of a WLAN system.
  • the BSS shown in FIG. 2 is an infrastructure BSS.
  • Infrastructure BSS includes one or more STAs and APs.
  • communication between non-AP STAs is performed via an AP.
  • AP access point
  • a plurality of infrastructure BSSs may be interconnected through a DS.
  • a plurality of BSSs connected through a DS is called an extended service set (ESS).
  • STAs included in the ESS may communicate with each other, and a non-AP STA may move from one BSS to another BSS while seamlessly communicating within the same ESS.
  • the DS is a mechanism for connecting a plurality of APs.
  • the DS is not necessarily a network, and there is no limitation on the form if it can provide a predetermined distribution service.
  • the DS may be a wireless network such as a mesh network or a physical structure that connects APs to each other.
  • Block Ack Block Acknowledgment
  • the block Ack mechanism increases channel efficiency by transmitting a plurality of acknowledgments in one frame.
  • the immediate response method is advantageous for wide bandwidth and low delay traffic transmission, while the delay response method may be suitable for applications that are not sensitive to delay.
  • a STA that sends data using a block Ack mechanism is referred to as an originator and a STA that receives such data as a recipient.
  • FIG. 3 is a diagram illustrating a block Ack mechanism utilized in a WLAN system.
  • the block Ack mechanism may be initiated by the exchange of an add block acknowledgment (ADDBA) request / response frame as shown in FIG. 3 ((a) Setup step).
  • ADDBA add block acknowledgment
  • QoS data frame blocks may be sent from the sender to the receiver. Such blocks may be initiated in a polled TXOP or by winning an EDCA race.
  • the sphere of the frame in the block can be limited.
  • MPDUs in such a frame block may be acknowledged by a BlockAck frame received in response to a request by a BlockAckReq frame ((b) Data & Block Ack step).
  • the sender can terminate the Block Ack mechanism by sending a DELBA (delete Block Acknowledgment) frame to the receiver. Receiving such a DELBA frame, the receiver can release all resources allocated for Block Ack transmission ((c) Tear Down step).
  • DELBA delete Block Acknowledgment
  • FIG. 4 is a diagram illustrating a basic configuration of a block acknowledgment frame.
  • the block acknowledgment frame may include a MAC header field, a BA control field, and a BA information field as shown in FIG. 4.
  • the MAC header field may include a frame control field, a Duration / ID field, an RA field, and a TA field.
  • the RA field represents the address of the receiving STA
  • the TA field represents the address of the originating STA.
  • FIG. 5 is a diagram illustrating a specific configuration of a BA control field shown in FIG. 4.
  • the value of the BA Ack policy subfield in the BA control field may convey the meaning as shown in Table 1a below.
  • the Multi-TID, Compressed Bitmap, and GCR subfields in the BA control field may determine possible BlockAck frame transformation according to the following rule.
  • FIG. 6 is a diagram illustrating a specific configuration of a BA information field illustrated in FIG. 4, and FIG. 7 is a diagram illustrating a configuration of a Block Ack start sequence control subfield.
  • the BA information field may include a Block Ack Start Sequence Control (SSC) subfield and a Block Ack bitmap subfield.
  • SSC Block Ack Start Sequence Control
  • the Block Ack bitmap subfield has a length of 128 octets, and thus may indicate a reception state of 64 MSDUs.
  • Bit position n of the Block Ack bitmap field if set to 1, may indicate the successful reception of an MPDU having an MPDU sequence control value corresponding to (SSC + n), where SSC is the Block Ack start sequence control sub Represents a field value.
  • SSC is the Block Ack start sequence control sub Represents a field value.
  • bit position n of the Block Ack bitmap field when bit position n of the Block Ack bitmap field is set to 0, this may indicate that an MPDU having an MPDU sequence control value corresponding to (SSC + n) has not been received.
  • MPDU sequence control field and Block Ack start sequence control subfield values may be treated as 16-bit unsigned integers, respectively. For unused fragment numbers of the MSDU, the corresponding bit in the bitmap may be set to zero.
  • FIG. 8 is a diagram illustrating a BA information field configuration of a compressed Block Ack frame.
  • the Block Ack bitmap of the BS information field of the compressed Block Ack frame may have an 8 octet length as shown in FIG. 8, and may indicate reception states of 64 MSDUs and A-MSDUs.
  • the first bit of the bitmap corresponds to an MSDU or A-MSDU corresponding to the value of the start sequence number subfield, and each bit may sequentially correspond to the MSDU or A-MSDU following the MSDU or A-MSDU.
  • FIG. 9 illustrates a BA information field of a Multi-TID Block Ack frame.
  • the TID_INFO subfield of the BA control field of the Multi-TID BlockAck frame indicates how many TIDs are transmitted in the BA information field.
  • the value of the TID_INFO subfield indicates the number of TIDs -1 corresponding to the information of the BA information field. For example, when the TID_INFO value is 2, it may represent that the BA information field includes information on three TIDs.
  • a Per TID Info subfield may be additionally added to the Block Ack start sequence control subfield and the Block Ack bitmap subfield as shown in FIG. 9.
  • Per TID Info, block Ack start sequence control, and Block Ack bitmap subfields that appear first may be transmitted corresponding to the lowest TID value, and subsequent repeated subfields may correspond to the next TID. Triplet of these subfields may be repeated for each TID.
  • the AP may transmit MU-MIMO data frames to a plurality of STAs (STAs 1 to 3).
  • the STA 1 may transmit a BA frame immediately after receiving a downlink MU PPDU without requesting a BA.
  • the AP transmits a BA Request (BAR) frame to the STA 2 and the STA 3 to perform polling, and the STA 2 and the STA 3 may transmit a BA frame.
  • BAR BA Request
  • FIG. 11 is an example in which frame exchange is performed without SIFS after MU PPDU, and assumes that an Ack policy is set to Block Ack for all STAs. Accordingly, the AP may transmit and poll a BAR frame to all STAs.
  • HE PPDU High Efficiency Physical layer Protocol Data Unit
  • the HE-SIG A (or HE-SIG1) field is located after an L-Part (eg, L-STF, L-LTF, L-SIG), and repeats in 20 MHz units as in the L-Part. (duplication).
  • L-Part eg, L-STF, L-LTF, L-SIG
  • HE-SIG A includes common control information (e.g., BW, GI length, BSS index, CRC, Tail, etc.) for STAs.
  • the HE-SIG A field contains information for interpreting the HE PPDU, so the information contained in the HE-SIG A field may vary depending on the format of the HE PPDU (eg, SU PPDU, MU PPDU, or trigger-based PPDU).
  • the HE-SIG A field may include a DL / UL indicator, an HE PPDU format indicator, BSS Color, TXOP Duration, BW (bandwidth), MCS, CP + LTF length, coding information, number of streams, STBC (eg, use of STBC), transmission beamforming (TxBF) information, CRC, and Tail.
  • the HE-SIG B field may be omitted.
  • the HE-SIG A field may include a DL / UL indicator, a BSS Color, a TXOP Duration, a bandwidth (BW), MCS information of the SIG B field, a symbol number of the SIG B field, a HE LTF symbol number, and a full band. It may include at least one of the MU-MIMO usage indicator, CP + LTF length, transmission beamforming (TxBF) information, CRC and Tail.
  • the HE-SIG A field may include at least one of a format indicator (e.g., SU PPDU or trigger based PPDU), BSS Color, TXOP Duration, BW, CRC, and Tail.
  • the HE-SIG A may include user allocation information such as STA identifiers such as PAID or GID, allocated resource information, and number of streams (Nsts). At least one may be included.
  • the HE-SIG B (or HE-SIG2) may be transmitted for each OFDMA allocation.
  • the HE-SIG B is distinguished by the STA through the SDM.
  • the HE-SIG B may include additional user allocation information, for example, MCS, Coding information, Space Time Block code (STBC) information, TX Beamforming (TXBF) information, and the like.
  • HE-SIG B is sent after HE-SIG A.
  • the HE-SIG B may be transmitted through a full band based on the information (numerology) of the HE-SIG A.
  • the HE-SIG B may include user allocation information, for example, STA AID, resource allocation information (e.g., allocation size), MCS, stream number (Nsts), Coding, STBC, transmission beamforming (TXBF), and the like.
  • the HE-SIG B may be repeatedly transmitted for every unit channel.
  • the HE-SIG B may be repeatedly transmitted in units of 20 MHz.
  • the HE-SIG B may be transmitted by copying the same information per 20 MHz on an 80 MHz bandwidth.
  • the STA / AP that receives the HE-SIGB repeatedly transmitted per 20MHz channel may accumulate the HE-SIG B received per 20MHz channel to improve reliability of HE-SIG B reception.
  • the gain of the accumulated signal may be improved in proportion to the number of channels through which the signal is repeatedly transmitted.
  • a signal that is repeatedly transmitted may have a gain of 3 dB X number of channels compared to a signal before being repeatedly transmitted. Therefore, the HE-SIG B repeatedly transmitted may be transmitted by increasing the MCS level according to the number of repeatedly transmitted channels. For example, assuming that MCS0 is used for HE-SIG B when there is no repetitive transmission, MCS1 may be used for HE-SIG B repeatedly transmitted using 40 MHz. As the number of channels for repetitive transmission increases, the HE-SIG B can be transmitted through a higher MCS level, so the overhead of HE-SIG B per unit channel can be reduced.
  • the HE-SIG B may include independent information for each 20 MHz channel unit.
  • the HE-SIG B may be transmitted in a 1x symbol structure in the same manner as the legacy parts (e.g., L-STF, L-LTF, L-SIG) and HE-SIG A.
  • the length of “L-STF + L-LTF + L-SIG + HE-SIGA + HE-SIGB” should be the same in all channels.
  • the HE-SIG B transmitted per 20 MHz may include allocation information for the corresponding band, for example, allocation information for each user using the corresponding band, a user identifier, and the like.
  • the length of the HE-SIG B may be different from each other for each channel.
  • FIG. 17 illustrates a padding scheme for HE-SIG B in order to configure the length before the HE-STF (e.g., the length up to HE-SIG B) for each channel.
  • the HE-SIG B length may be aligned by repeating the HE-SIG B by a padding length.
  • the HE-SIG B as much as the required padding length from the beginning (or the last) of the HE-SIG B may be padded to the HE-SIG B.
  • one HE-SIG B field may be transmitted.
  • channels of 20 MHz size are each type 1 HE-SIG B (hereafter HE-SIG B [1]) or type 2 HE-SIG B (hereafter HE-SIG B [2]).
  • HE-SIG B [1] and the HE-SIG B [2] may be alternately transmitted.
  • the odd 20 MHz channel may transmit HE-SIG B [1] and the even 20 MHz channel may transmit HE-SIG B [2].
  • HE-SIG B [1] is transmitted on the first 20 MHz channel and HE-SIG B [2] is transmitted on the second 20 MHz channel.
  • HE-SIG B [1] is transmitted on the first 20 MHz channel
  • HE-SIG B [2] is transmitted on the second 20 MHz channel
  • the same HE-SIG B [1] is transmitted on the third
  • the same HE-SIG B [2] is repeated on the fourth 20 MHz channel. Similar transmission in the 160 MHz bandwidth.
  • the HE-SIG B may be repeatedly transmitted as the size of the bandwidth increases, and the HE-SIG B repeatedly transmitted is 20 MHz in size from the 20 MHz channel to which the same type of HE-SIG B is transmitted. It can be hopped and sent.
  • contents of the HE-SIG B [1] and the HE-SIG B [2] may be different.
  • the HE-SIG-Bs [1] all have the same content.
  • HE-SIG B [2] all have the same content.
  • HE-SIG B [1] includes only resource allocation information for odd 20 MHz channels, and HE-SIG B [2] contains only resource allocation information for even 20 MHz channels. It can be set to.
  • the HE-SIG B [1] includes resource allocation information for at least some of the even 20 MHz channels, or the HE-SIG B [2] is the odd 20 MHz channels. It may include resource allocation information for at least some of the.
  • the HE-SIG B may include a common field and a user specific field.
  • the common field may precede the user specific field.
  • the common field and the user specific field may be distinguished in bit units, not in OFDM symbol units.
  • the common field of the HE-SIG B includes information on all of the STAs designated to receive the PPDU in the corresponding bandwidth.
  • the common field may include resource unit (RU) allocation information.
  • the content is the same between the HE-SIG B [1], and the content is the same between the HE-SIG B [2]. For example, when dividing four 20 MHz channels constituting 80 MHz into [LL, LR, RL, RR], a common block for LL and RL is included in a common field of HE-SIG B [1], and HE- A common block for LR and RR may be included in a common field of SIG B [2].
  • the user specific field of the HE-SIG B may include a plurality of user fields, and each user field may include information specific to an individual STA designated to receive a PPDU.
  • the user field may include, but is not limited to, at least one of a station ID, an MCS for each STA, a stream number (Nsts), a coding (e.g., an indication for using an LDPC), a DCM indicator, and transmission beamforming information.
  • Table 2a shows 8-bit indexes (hereinafter, referred to as RU allocation indexes) that can be set in the RU allocation information subfield included in the common field of the HE-SIG B (e.g., 20 MHz channel).
  • the RU allocation index may indicate how many user fields (e.g., user fields in the user-specific field of the HE-SIG B) are included in the corresponding HE-SIG B for each RU. How many STAs are multiplexed into RUs (e.g., MU-MIMO) may be indicated by the RU arrangement.
  • MU-MIMO which multiplexes multiple STAs into one RU, may be supported in an RU having a size of 106 tons or more.
  • multiple STAs may be allocated the same RU, but data streams transmitted on the corresponding RU are not shared by the STAs. That is, in the MU-MIMO scheme, a plurality of STAs may be multiplexed on a STA common RU, but each STA may receive only its own data stream among a plurality of data streams transmitted through the STA common RU.
  • the number of entries indicates the number of RU allocation indices having the same RU arrangement but different numbers of user fields per RU (eg, different numbers of STAs multiplexed in 1 RU). For example, '00100 yyy' corresponds to a total of eight RU allocation indices. This is because yyy can be set to one of 000 to 111. Therefore, in Table 2a, yyy represents the number of STAs multiplexed on 1 RU.
  • the total number of user fields included in the user specific field of the HE-SIG B may be indicated.
  • Table 2b shows stream number (Nsts) information that can be set in a user field of a user specific field of HE-SIG B.
  • the stream number information may be referred to as a spatial configuration subfield.
  • the number of users may be determined based on the number of user fields of the HE-SIG B.
  • Four bits (B0-B3) that can be set in a spatial configuration subfield are defined for each user.
  • Nsts [i] corresponds to the i th user field.
  • Nsts [i] indicates the number of spatial streams transmitted to the STA identified through the i-th user field.
  • FIG 19 illustrates an uplink multi-user transmission situation according to an embodiment of the present invention.
  • a UL MU transmission scheme may be used, which means that the AP transmits a trigger frame to a plurality of STAs (eg, STA 1 to STA 4) as illustrated in FIG. 19. Can be started by.
  • the trigger frame may include UL MU allocation information.
  • the UL MU allocation information may include, for example, at least one of resource location and size, STA IDs or receiving STA addresses, MCS, and MU type (MIMO, OFDMA, etc.).
  • the trigger frame may include at least one of (i) a duration for the UL MU frame, (ii) the number of allocations (N), and (iii) information of each allocation.
  • the information of each allocation may include per user information.
  • the information of each allocation is, for example, AID (in addition, in the case of MU, additionally included by the number of STAs), power adjustment, resource (or tone) allocation information (eg, bitmap), MCS, number of streams (Nsts), It may include at least one of information on STBC, coding, and transmission beamforming.
  • the AP may acquire a TXOP for transmitting a trigger frame through a competition process to access a medium.
  • the STAs may transmit the UL data frame in the format indicated by the AP after SIFS of the trigger frame.
  • an AP performs an acknowledgment on a UL MU data frame through a block ACK (BA) frame.
  • BA block ACK
  • FIG. 20A illustrates a trigger frame format according to an embodiment of the present invention.
  • a trigger frame includes a frame control field, a duration field, a recipient STA address field, a transmitting STA address field, a common information field, and one or two. It may include at least one of the above Per User Info fields and the Frame Check Sum (FCS).
  • the RA field indicates an address or ID of a receiving STA and may be omitted according to an embodiment.
  • the TA field indicates the address of the transmitting STA.
  • the common information field may include a length subfield, a cascade indication, a HE-SIG A information subfield, a CP / LTF type subfield, a trigger type subfield, and a trigger-dependent common information.
  • Common Info may include at least one of the subfields.
  • the length subfield indicates the L-SIG length of the UL MU PPDU.
  • the cascade indicator indicates whether there is a transmission of a subsequent trigger frame after the current trigger frame.
  • the HE-SIG A information subfield indicates content included in HE-SIG A of the UL MU PPDU.
  • the CP / LTF type subfield indicates the CP and the HE LTF type included in the UL MU PPDU.
  • the trigger type subfield indicates the type of trigger frame.
  • the trigger frame may include type-specific common information and type-specific individual user information (Per User Info).
  • the trigger type may include, for example, a basic trigger type (eg, type 0), a beamforming report poll trigger type (eg, type 1), and a multi-user block ack request (MU-BAR) type (eg, Type 2) or multi-user ready to send (MU-RTS) type (eg, type 3) may be set, but is not limited thereto.
  • MU-BAR multi-user block ack request
  • MU-RTS multi-user ready to send
  • the trigger dependent common information subfield may include a GCR (Groupcast with Retries) indicator and a GCR address.
  • the Per User Info field includes a user identifier subfield, a resource unit (RU) allocation subfield, a coding type subfield, an MCS field, a dual sub-carrier modulation (DCM) subfield, and a spatial stream (SS) assignment. It may include at least one of a subfield and a trigger dependent per user info subfield.
  • the user identifier subfield indicates the AID of the STA that will use the corresponding resource unit in order to transmit the MPDU of the UL MU PPDU.
  • the RU allocation subfield indicates a resource unit for transmitting the UL MU PPDU by the corresponding STA.
  • the coding type subfield indicates the coding type of the UL MU PPDU transmitted by the corresponding STA.
  • the MCS subfield indicates the MCS of the UL MU PPDU transmitted by the corresponding STA.
  • the DCM subfield indicates information about dual carrier modulation of the UL MU PPDU transmitted by the corresponding STA.
  • the SS assignment subfield indicates information about spatial streams of the UL MU PPDU transmitted by the corresponding STA. If the trigger type is MU-BAR, the trigger dependent individual user information subfield may include BAR control and BAR information.
  • the M-BA frame may be set to a format in which the Multi-TID BlockAck frame is partially modified.
  • the M-BA frame may include an indicator indicating that the frame is an M-BA frame, and each BA information field in the M-BA frame has different STAs.
  • Bits 0 to 10 of the Per TID information field of the M-BA frame ie, B0-B10 are identifiers (eg, PAID or AID) of a receiver to receive the corresponding BA information field. Can be set.
  • a BA information field may be provided for each STA (Per STA).
  • Signaling indicating the ACK in the M-BA frame may be defined as follows. If bit 11 of the TID Info field (B11) is set to a specific value (eg, 0), the BA Bitmap (BlockAck bitmap) and BA SC (Block Ack Starting Sequence Control) within the BA information field. A subfield is not provided and such a BA information field may indicate an ACK (eg, reception success) for an STA having an AID indicated by the corresponding TID information field. If bit 11 of the TID information field is set to another value (e.g., 1), a BA Bitmap (BlockAck bitmap) and a BA A (Block Ack Starting Sequence Control) subfield may be provided in the BA information field.
  • a BA Bitmap BlockAck bitmap
  • BA A Block Ack Starting Sequence Control
  • the embodiments of transmitting a multi-STA BA (M-BA) frame in a HE-PPDU format (e.g., OFDMA PPDU) in an 11ax system will be described.
  • the HE-SIG B may be repeatedly transmitted for each channel unit (e.g., 20 MHz unit) of a predetermined size.
  • channel unit e.g. 20 MHz unit
  • the indices of the embodiments to be described later are for convenience of description, and the inventions may be configured by a combination of embodiments having independent indices or different indices for each embodiment.
  • the M-BA frame including information on the ACK / BA for the STAs that transmitted the received UL MU frame is the total bandwidth of the UL MU transmission (eg, 20/40/80 MHz) Can be sent over.
  • the M-BA frame may be set to the same size as the overall bandwidth of the UL MU transmission.
  • FIG. 21 illustrates an M-BA frame according to an embodiment of the present invention.
  • M-BA frames for STA1 to STA8s are transmitted at 40 MHz.
  • the resource allocation information included in the HE-SIG B may be set in the SU format, and the AID may be set in the broadcast ID.
  • the STAs After receiving the M-BA frame, the STAs can check whether the ACK / BA for themselves is included in the M-BA frame.
  • the M-BA frame transmitted over the entire band is illustrated in the SU format, according to another embodiment of the present invention, the HE PPDU of the M-BA frame transmitted over the entire band is set to the MU format May be In another embodiment, the M-BA frame transmitted over the entire band is set to the SU format, but the information in Table 3 is included in another field (eg, HE-SIG A) rather than the HE-SIG B field, and HE The -SIG B field may be omitted.
  • HE-SIG A another field
  • HE-SIG B field may be omitted.
  • the M-BA frame may be transmitted in 242 tones (e.g., 20 MHz units).
  • the 20/40/80 MHz band consists of 1/2/4 242 tonnes each (eg, 1 X 242 tonnes / 2 X 242 tonnes / 4 X 242 tonnes), one M- for each 242 tonnes.
  • a BA frame can be sent.
  • Each M-BA frame includes ACK / BA information on UL MU frames received on the corresponding 242 tone unit.
  • the M-BA frame transmitted through the first 242 tones includes ACK / BA information for STA1 to STA4, and the second 242 tones (eg, lower 242).
  • M-BA frame transmitted through the tone includes the ACK / BA information for STA5 ⁇ STA8.
  • STA 1 transmits a UL MU frame using at least some of the tones of the first 242 tones
  • the M-BA frame including the ACK / BA information for STA 1 is transmitted through the first 242 tones. It is preferable.
  • the M-BA frame including the ACK / BA information for STA 5 is transmitted on the second 242 tones. It is desirable to be.
  • the M-BA frame for the STA may be transmitted from 242 ton units different from the 242 ton units in which the STA transmits the UL MU frame, but is not limited thereto.
  • the ID information subfield may be set to the broadcast ID.
  • the STAs can decode all M-BA frames and check whether BA or ACK for them is included in the corresponding M-BA frame.
  • the HE-SIG B may indicate resource allocation information within 242 tons. Table 4 illustrates the HE-SIG B of the M-BA frame when the broadcast ID is used.
  • the ID information subfield of the HE-SIG B is set to the broadcast ID
  • a group ID may be used instead of the broadcast ID.
  • the MU GID may be used or a newly allocated GID may be used. Details of the allocation of the GID will be described later.
  • the GID When the GID is configured in the HE-SIG B, only STAs belonging to the group receive the frame (e.g., payload) by decoding the allocation information (e.g., HE SIG-B). Upon receiving the frame, the STA may check whether its address or identifier information is included in the MAC frame (e.g., payload).
  • Table 5 shows an exemplary setup of HE-SIG B according to this embodiment.
  • STA IDs may be set for each resource allocation information in the HE-SIG B field.
  • the STA ID may be AID / PAID.
  • IDs may be included as many as the number of STAs receiving resource allocation.
  • Table 6 illustrates an HE-SIG B field in which STA IDs are set for each resource allocation. Referring to Table 6, STA IDs may be mapped to each resource allocation. Information such as MCS, STBC, coding, etc. may be provided for each resource allocation.
  • the HE SIG-B may include information (e.g., Same resource size indication) indicating whether resources are allocated with the same size. If the same resource size indication is set to 1, it indicates that the OFDMA resources allocated by the corresponding HE-SIG B are all the same size, and the allocated resource size is included in the HE-SIG B. Can be.
  • the allocated resource size may be set to a predefined resource size index.
  • an ACK / BA frame e.g., M-BA frame
  • Table 7 illustrates the contents of the HE-SIG B field of FIG. 23.
  • HE-SIG B includes (i) a PPDU length subfield, (ii) resource allocation information subfield, (iii) STA ID information subfield, and (iv) individual STA information subfield. It may include at least one of.
  • the PPDU Length subfield may be omitted.
  • the PPDU length subfill in the HE SIG-B may be omitted.
  • the resource allocation information subfield may include the same resource size indicator. If the same resource size indicator is set to 1, resource size (RS) information may be included in the resource allocation information subfield. In another embodiment, the RS is predefined and the RS information may be omitted in the resource allocation information subfield. If the same resource size indicator is set to 0, the resource allocation information subfield may indicate how resources (e.g., 20 MHz each) of 242 tones are allocated. For example, the number of resources allocated in units of 242 tones (e.g., number of 20 MHz channels) and each position (e.g., location of each 20 MHz channel) may be indicated.
  • resources e.g., 20 MHz each
  • the number of resources allocated in units of 242 tones e.g., number of 20 MHz channels
  • each position e.g., location of each 20 MHz channel
  • 242 tones are allocated in units of 242 tones, and which 242 tones are allocated in units of 26 tons.
  • which 20 MHz is allocated in units of 242 tones and which 20 MHz is allocated in units of 26 tons may be indicated through the HE-SIG B. If there is a 20 MHz channel allocated in units of 26 tones, the information of 26 tones unit allocation (eg, location and number of units of 26 tones) included in the 20 MHz may be indicated through the HE-SIG B. .
  • the STA ID information subfield may indicate a STA ID mapped to each resource allocation information.
  • the individual STA information subfield may include information necessary for each STA to decode the payload.
  • Individual STA information may be set for each STA, and may include, for example, at least one of information on the number of streams, MCS information, STBC usage, and coding type.
  • RS (Resource size) 3 (eg, 242 tone units) may be set. Can be.
  • UL MU resource mapping indicator (UL MU resource) mapping indication may be included.
  • the UL MU resource mapping indicator may be used, for example, when frames are transmitted on a resource unit of fixed size. Accordingly, the UL MU resource mapping indicator may indicate that frames are transmitted in a resource unit of a fixed size.
  • the resource unit of fixed size may be 242 tons, but is not limited thereto, and other units of tones may be used. For convenience of description, it is assumed that a fixed size resource unit is 242 ton.
  • the UL MU resource mapping indicator may mean to decode only a frame transmitted through 242 tone units to which UL MU frames transmitted immediately before the corresponding frame (i.e., before SIFS) belong.
  • the UL MU resource mapping indicator includes a frame (eg, an M-BA frame including an UL MU resource mapping indicator) transmitted in units of 242 tones, and includes a corresponding frame (eg, M-BA including an UL MU resource mapping indicator).
  • Frame includes information (eg, ACK / BA) on UL MU frames (or PPDUs) transmitted immediately before through an OFDMA resource corresponding to 242 tones.
  • the UL MU resource mapping indicator is used in the embodiment of FIG.
  • the UL MU resource mapping indicator decodes only the data payload in which the STA1 to STA4s transmit the 1st M-BA frame, and the STA 5 to STA8s are 2nd. It may indicate to decode only the data payload in which the M-BA frame is transmitted.
  • the UL MU resource mapping indicator When the UL MU resource mapping indicator is used, additional OFDMA resource allocation information may not be included in the HE-SIG B. This is because, even without the OFDMA resource allocation information, the resource region allocated by each STA may be indicated through the UL MU resource mapping indicator. For example, the STA may recognize that the OFDMA resource is allocated in units of 242 tones (e.g., a fixed size resource unit) through the UL MU resource mapping indicator, and may decode the data payload of the corresponding frame.
  • the UL MU resource mapping indicator 0 may indicate that the resource allocation information subfield is explicitly included in the HE-SIG B and transmitted.
  • the meaning of each bit value of the UL MU resource mapping indicator may be set inversely. Table 8 illustrates the contents of HE-SIG B when the UL MU resource mapping indicator is used.
  • the HE-SIG B may include at least one of (i) a PPDU length subfield and (ii) a UL MU resource mapping indicator. Description overlapping with Table 7 may be omitted.
  • the HE-SIG B may include at least one of a resource allocation information subfield, a STA ID information subfield, and an individual STA information subfield (see description in Table 7).
  • the UL resource mapping indicator 1
  • at least one of the resource allocation information subfield, the STA ID information subfield, and the individual STA information subfield may be omitted in the HE-SIG B.
  • Information for payload decoding e.g., MCS, STBC, Nsts, Coding, etc.
  • MCS Mobility Control Coding
  • STBC Packet Control Coding
  • the UL MU resource mapping ID may be used in the HE-SIG B similarly to the UL resource mapping indicator.
  • the UL MU resource mapping ID may have multiple indices. For example, each index of the UL MU resource mapping ID may be used as follows.
  • the UL MU resource mapping ID or the UL MU resource mapping indicator may be referred to by another name and may also be used for other purposes.
  • the UL MU resource mapping ID or the UL MU resource mapping indicator may be transmitted through another preamble part such as HE-SIG A.
  • an HE-SIG may include individual STA IDs instead of broadcast IDs and may be transmitted.
  • the M-BA frame transmitted through the first M-BA resource eg, the first 242 tone unit
  • the corresponding M-BA frame is the first M-BA. It may include IDs (eg, AIDs or PAIDs of STAs 1 to 4) of STAs to which resources are allocated.
  • Table 9 illustrates the contents of the HE-SIG B field according to the present embodiment.
  • the HE-SIG B field includes (i) resource allocation information subfield, (ii) STA ID information subfield, and (iii) information for payload decoding, for example, number of streams, MCS, coding information, and the like. It may include at least one of. Duplicate descriptions with those described in Table 7 and / or Table 8 are omitted.
  • the resource allocation information subfield may be set through the method described in the embodiment 2-1 or the embodiment 2-2, but is not limited thereto.
  • the STA ID information subfield may be set for each resource allocation. For example, when there are a total of N resource allocations, STA ID information may be set for every N resource allocations.
  • a plurality of STAs may receive ACK / BA through one resource allocation, so that individual STA IDs (eg, AID or PAID) of STAs that will receive ACK / BA through each resource allocation may be set for each resource allocation. Can be. As such, multiple STAs may share one resource allocation.
  • STAs sharing a resource allocation may share a data stream transmitted through a payload. That is, one data stream may be shared by a plurality of STAs, and STAs sharing the data stream may be indicated through STA ID information.
  • Information for payload decoding may be set in common for all resource allocations or individually for each resource allocation.
  • a group ID may be used for the HE-SIG (e.g., HE-SIG B) instead of the individual STA ID (e.g., AID or PAID).
  • the first M-BA resource e.g, first 242 tone units
  • the first M-BA resource e.g, first The M-BA frame transmitted through 1 242 tones may include the GID of the group to use the first M-BA resource (eg GID of group 1).
  • Table 10 illustrates the contents of the HE-SIG B according to the present embodiment.
  • the HE-SIG B field includes (i) resource allocation information subfield, (ii) STA ID information subfield, and (iii) information for payload decoding, for example, number of streams, MCS, coding information, and the like. It may include at least one of. Descriptions overlapping with those described in Tables 7 to 10 will be omitted.
  • the STA ID information subfield may be set for each resource allocation. For example, when there are a total of N resource allocations, STA ID information may be set for every N resource allocations. One resource allocation may correspond to one group. Therefore, a GID may be set for each resource allocation.
  • information fields (eg, same resource size indicator, UL MU resource mapping indicator, etc.) included in the HE-SIG B described in the above-described embodiments for transmitting the M-BA frame in the OFDMA form must be M-. It is not limited to the transmission of the BA frame, and may be used to transmit other DL frames (eg, BA, ACK, BAR, NDPA, RTS, Trigger frame) in 11ax PPDU format (eg, HE PPDU).
  • the information fields (eg, same resource size indicator, UL MU resource mapping indicator, etc.) included in the HE-SIG B described in the above-described embodiments for transmitting the M-BA frame in the OFDMA form are the HE-SIG. In addition to B, it may be transmitted through other PHY preamble parts (eg, HE-SIG A or HE-SIG C, etc.).
  • Information fields (same resource size indicator, UL MU resource mapping indicator, etc.) included in the HE-SIG B may be transmitted through a trigger frame.
  • the AP when the AP transmits an M-BA frame based on OFDMA (e.g., transmitted in HE PPDU format), the AP may repeatedly transmit a predetermined resource unit (e.g., 242 tones).
  • a predetermined resource unit e.g., 242 tones
  • 25 shows an embodiment of repeatedly transmitting an M-BA frame in units of 242 tones.
  • a predetermined resource unit is 242 ton units (e.g., 20 MHz) is illustrated, this is for convenience of description and the present invention is not limited thereto.
  • an M-BA frame transmitted through each 242 tone unit may include ACK / BA information about UL MU frames of all STAs STA1 to STA8.
  • the M-BA frame transmitted through each 242 ton unit, the ACK / BA information of the UL MU frames received in the corresponding 242 ton unit, as well as the ACK / May contain all of the BA information.
  • the M-BA frame set as described above may be repeatedly transmitted in units of 242 tones.
  • the HE-SIG e.g., HE-SIG A or HE-SIG B
  • the M-BA frame may include information indicating that the M-BA frame is repeated in units of 242 tones.
  • the information indicating that the M-BA frame is repeated in units of 242 tones may be, for example, a repeat transmission indicator or HE-SIG B type information, but is not limited thereto.
  • Table 11 illustrates the contents of the HE-SIG B according to the present embodiment.
  • a corresponding frame e.g., M-BA frame
  • information indicating that the M-BA frame is repeatedly transmitted in units of 242 tones based on the OFDMA may be transmitted through a trigger frame.
  • the GID may be allocated to STAs through a trigger frame.
  • the AP may allocate resources to respective STAs through a trigger frame and allocate GIDs to the STAs.
  • the GID may be assigned using at least a portion of the AID range or may be assigned using at least a portion of the group ID of the MU-MIMO.
  • the present invention is not limited to a method of explicitly allocating a GID through a trigger frame.
  • the GID may be reserved in advance. Specifically, at least some of the IDs used in the HE-SIG B (e.g., last part, first part) may be reserved and used for GID purposes.
  • the group ID reserved for each 20 MHz (eg, 242 tone resource units) channel corresponds to 20 Can be mapped and used on MHz channels.
  • GID a on the first 20 MHz (e.g., 242 ton RU)
  • GID b on the second 20 MHz
  • GID c on the third 20 MHz
  • GID d on the fourth 20 MHz, respectively.
  • the GID may be implicitly assigned to the STAs.
  • the GID may be implicitly indicated through the 20 MHz channel allocated to the STA.
  • 20 MHz STAs allocated to channel 3 eg, 242 tone RU 3
  • GID c to STAs allocated to 20 MHz channel 4 (eg, 242 tone RU 3).
  • the AP explicitly signals one GID through a trigger frame, other GIDs available based on the signaled one GID may be implicitly specified.
  • the value of GID 2 may be determined using GID 1.
  • the total number of GIDs to be allocated may be determined according to the overall bandwidth. For example, 1/2/4 GID (s) may be used at 20/40/80 MHz.
  • GIDs implicitly determined may have a value that is contiguous from the explicitly signaled GID.
  • the signaled GID 1 may be mapped to the first 20 MHz, and other GIDs having a value subsequent to GID 1 may be sequentially mapped to the next 20 MHz.
  • mapping between the GID and the 20 MHz channel can be defined according to the above-described scheme.
  • the GID may be assigned not only through the trigger frame but also through other frames before the trigger frame transmission.
  • the transmission schemes of the M-BA frame described above may be applied regardless of whether the HE-SIG B structure is STA individual encoding based, joint encoding based, or independent coding based.
  • the use of GID may also be applied regardless of the HE-SIG B structure.
  • the AP allocates the GID for the M-BA to the STAs in assigning the GID through the trigger frame in order to transmit the M-BA frame in the OFDMA form (e.g., HE PPDU).
  • the OFDMA form e.g., HE PPDU
  • a GID may be allocated to each STA through a trigger frame.
  • Table 12 illustrates the contents of the trigger frame according to the present embodiment.
  • the AP may allocate a GID to each STA through a trigger frame. Thereafter, when the AP transmits the M-BA frame in the OFDMA scheme, the AP may set and transmit the ID subfield of the HE-SIG B included in the M-BA frame to the GID allocated through the trigger frame.
  • STAs assigned the GID through the trigger frame may receive the M-BA frame using the GID assigned by the STA after receiving the UL MU frame and transmitting the M-BA frame transmitted based on the OFDMA. . For example, the STA may use its GID to decode an OFDMA frame assigned to it.
  • GID signaling overhead is generated as many as GID size X total number of STAs. For example, if the GID is 11 bits and 8 STAs are scheduled, a total of 88-bit overhead occurs.
  • the AP includes any one of the total GIDs to be allocated to the trigger frame (eg, the GID having the lowest value) and the total number of GIDs to be allocated to each STA through a GID index. It may indicate the GID assigned to the STA.
  • Table 13 illustrates the contents of the trigger frame according to the present embodiment.
  • the lowest GID among the GID values to be allocated is 3 (eg, b00000000011) and the number of GIDs to be allocated is four.
  • the size of the GID index may be set to 2-bit.
  • the size of the GID index is ceiling (log 2 N), and N may be the total number of GIDs to be allocated.
  • N 4.
  • the length of the GID is assumed to be 11 bits, but is not limited thereto.
  • 11 is the number of bits needed to indicate the lowest GID
  • 3 is the number of bits required to indicate the total number of GIDs to be allocated
  • 16 is the number of bits required to indicate the 2-bit GID index to each of the 8 STAs. Indicates.
  • This embodiment may be used when the values of GIDs to be allocated are consecutive to each other.
  • the AP may allocate discontinuous GIDs to STAs.
  • a GID bitmap can be used as a method of allocating discontinuous GIDs. Each bit position and GID may be mapped in the GID bitmap.
  • the total number information of the allocated GIDs may be omitted.
  • the total number of bits set to 1 in the GID bitmap may indicate the total number K of allocated GIDs. Therefore, the size of the GID index is ceiling (log 2 K).
  • ceiling (A) means the minimum integer which has a value of A or more.
  • Table 14 illustrates the contents of the trigger frame according to the present embodiment.
  • the size of the GID index is 2 bits.
  • 11 denotes the number of bits (eg, b00000000011) for indicating the lowest GID value
  • 8 denotes the number of bits of the GID bitmap
  • 16 denotes the number of bits required to indicate the GID index of two bits to eight STAs.
  • the GID bitmap is 8 bits in total, 4 of the 8 GIDs having a range of 3 to 11 may be allocated through the GID bitmap.
  • the M-BA frame may be transmitted based on an OFDMA PPDU (e.g., HE PPDU), and the contents of the HE-SIG B field have been described.
  • OFDMA PPDU e.g., HE PPDU
  • the signaling methods of the OFDMA M-BA frame have been described.
  • examples of IDs that may be set in the ID information field of the HE-SIG field of the HE PPDU based M-BA frame include broadcast ID, multicast ID, GID and / or individual STA IDs (eg, PAID or AIDs). It was.
  • embodiments for allocating a GID to an STA have been described.
  • M-BA ID ID information set in the HE-SIG B field of the HE PPDU-based M-BA frame
  • M-BA ID ID information set in the HE-SIG B field of the HE PPDU-based M-BA frame
  • the AP may assign a STA ID, for example, an M-BA ID, to the STA through the trigger frame.
  • a STA ID for example, an M-BA ID
  • an unused STA ID may be assigned as an M-BA ID.
  • the allocated M-BA ID may be valid only for a corresponding transmission opportunity (TXOP). For example, when the TXOP expires, the STA can no longer use the M-BA ID assigned through the trigger frame.
  • TXOP transmission opportunity
  • the AP may transmit the M-BA frame by the OFDMA method using the M-BA ID assigned to the STA. Different M-BA IDs may be used for each resource unit in which each M-BA frame is transmitted.
  • the STA decodes the M-BA frame using the M-BA ID assigned thereto.
  • the STA may ignore the data payload indicated by the M-BA ID. For example, the STA may attempt to decode only the data payload indicated by the STA ID.
  • 26 illustrates M-BA frame signaling according to an embodiment of the present invention.
  • one M-BA ID may be assigned to a plurality of STAs.
  • the AP may allocate M-BA ID A to STAs 1, 2, 3, and 4 through a trigger frame, and assign M-BA ID B to STAs 5, 6, 7, and 8.
  • Each STA transmits a UL MU PPDU based on a trigger frame.
  • the AP transmits an M-BA frame including ACK / BA for STAs in a HE PPDU scheme (e.g., OFDMA PPDU).
  • the M-BA frame may be transmitted in units of 20 MHz channels.
  • the M-BA 1 payload includes ACK / BA for STA 1, 2, 3, 4 and is transmitted on 20 MHz channel 1.
  • the M-BA 2 payload includes ACK / BA for STA 5, 6, 7, 8 and is transmitted on 20 MHz channel 2.
  • each STA may receive an M-BA frame through the 20 MHz channel to which the resources used to transmit the UL MU PPDU belongs.
  • the AP may allocate resource units belonging to the same 20 MHz to STAs allocated to the same M-BA ID.
  • the M-BA 1 payload may be received through the HE-SIG B 1 and the M-BA 2 payload may be received through the HE-SIG B 2.
  • the M-BA 1 payload is received based on the M-BA ID A set in the STA ID subfield of HE-SIG B1, and the M-BA 2 payload is set in the STA ID subfield of HE-SIG B2. It may be received based on BA ID B.
  • each M-BA ID (e.g., 11 bits) to be allocated to each STA may be included in a per user info field of each STA.
  • each M-BA ID may be included in a trigger-dependent per user info subfield of the individual user information field.
  • FIG. 27A illustrates a common information field and an individual user field of a trigger frame according to option 1.
  • M-BA ID A may be included in the user information subfield.
  • M-BA ID B may be included in the subfield.
  • a specific M-BA ID among M-BA IDs (e.g., 11 bits) to be allocated may be included in a common information field.
  • the specific M-BA ID may be included in the trigger-dependent common info subfield of the common information field.
  • the specific M-BA ID is an M-BA ID to be allocated, which is an M-BA ID that each STA refers to to specify an actual M-BA ID assigned thereto.
  • the specific M-BA ID referenced by the STA will be referred to as a reference M-BA ID.
  • the reference M-BA ID may be a first M-BA ID (e.g., first M-BA ID) having the lowest value among the M-BA IDs to be allocated by the AP, but is not limited thereto.
  • an M-BA ID index (e.g., 3-bit) may be included in an individual user information field.
  • the M-BA ID index may be included in the trigger dependent individual user information subfield of the individual user information field.
  • the reference M-BA ID is STA common information because it is signaled through the common information field of the trigger frame, whereas the M-BA ID is signaled through an individual user information field, so it is viewed as STA specific information. Can be.
  • each STA may determine the M-BA ID assigned to itself by combining the STA common reference M-BA ID and the STA-specific M-BA ID index.
  • the length of the M-BA ID index may vary. For example, the length of the M-BA ID index may be determined based on the total number of M-BA IDs to be assigned. If there are 4 or 6 M-BA IDs, the length of the M-BA ID index may be 2 bits or 4 bits, respectively.
  • FIG. 27B illustrates the common information field and the individual user field of the trigger frame according to option 2.
  • FIG. 1 a reference M-BA ID
  • the M-BA ID index of the corresponding STA may be set in the individual user information field (eg, trigger-dependent individual user information subfield) of the trigger frame.
  • FIG. 26B illustrates that the 11-bit reference M-BA ID is set in the trigger-dependent common user information subfield, the present invention is not limited thereto.
  • a reference M-BA ID (eg, assumed to be M-BA ID A) is set in a common user information field common to STAs.
  • the AP may signal whether an M-BA ID index subfield for the corresponding STA exists in the trigger frame.
  • the STA receiving the trigger frame in which the M-BA ID index subfield does not exist may know that the M-BA ID is not allocated.
  • the AP does not necessarily allocate an M-BA ID when transmitting a trigger frame, and may not allocate an M-BA ID according to the selection of the AP. Even if the STA is not assigned an M-BA ID, the AP is not prohibited from allocating a resource for transmitting a UL MU PPDU to the STA through a trigger frame.
  • Whether the M-BA ID index subfield exists may be signaled through the common information field of the trigger frame. For example, as shown in FIG. 27C, when the reference M-BA ID included in the common information field (eg, trigger dependent common information subfield) is set to a preset value (eg, a value O for broadcast), the individual trigger frame may be separated. It may be indicated that the user information field (eg, trigger dependent individual user information subfield) does not include an M-BA ID index subfield.
  • a preset value eg, a value O for broadcast
  • the AP may include the M-BA ID in the trigger frame (optional).
  • the AP may include an M-BA ID presence field in a trigger frame.
  • the M-BA ID providing field may indicate whether a corresponding trigger frame includes an M-BA ID (e.g., M-BA ID allocation).
  • the M-BA ID provision field may be included in the trigger-dependent common information field or the trigger-dependent individual user information field. According to the embodiment in which the M-BA ID providing field is included in the trigger-dependent individual user information field, it may be interpreted that M-BA ID allocation / non-assignment is performed in units of STAs.
  • At least one of the M-BA ID, reference M-BA ID, and M-BA ID index in option 1 or 2 described above is a trigger-dependent common information field or a trigger-dependent individual user. It may or may not be included in the information field.
  • FIGS. 27D and 27E illustrate a case in which an M-BA ID is provided and a case in which an M-BA ID is not provided in the embodiment of the above-described option 1, respectively.
  • the M-BA ID provision field is included in the trigger dependent individual user information field.
  • the M-BA ID provision field is 1 as shown in FIG. 27D
  • the trigger dependent individual user information field includes the M-BA ID.
  • the M-BA ID providing field is 0 as shown in FIG. 27D
  • the trigger dependent individual user information field includes the M-BA ID.
  • the meaning of the bit value of the M-BA ID providing field may be reversed. According to the embodiments of FIGS.
  • the M-BA ID provision field is included in the STA-specific trigger dependent individual user information field, whether or not to provide an M-BA ID may be set differently for each STA.
  • the individual user information field for some STAs includes an M-BA ID value
  • the individual user information fields for some other STAs contain an M-BA ID value. You may not.
  • FIG. 27F and 27G illustrate a case in which an M-BA ID is provided and a case in which an M-BA ID is not provided in another embodiment of the above-described option 1, respectively.
  • the M-BA ID providing field is included in the common information field (e.g., trigger dependent common information field).
  • the M-BA ID provision field is 1 as shown in FIG. 27F
  • the trigger dependent individual user information field includes the M-BA ID.
  • the M-BA ID provision field is 0 as shown in FIG. 27F
  • the trigger dependent individual user information field includes the M-BA ID.
  • the meaning of the bit value of the M-BA ID providing field may be reversed. According to the embodiments of FIGS.
  • the M-BA ID provision field is included in a trigger dependent common information field that is STA common, whether or not an M-BA ID is provided is also set in common among STAs. For example, if the M-BA ID provision field is 0, all of the plurality of individual user information fields included in the trigger frame do not include an M-BA ID value. All of the individual user information fields of the contain an M-BA ID value.
  • FIG. 27H and 27I illustrate a case where an M-BA ID is provided and a case where an M-BA ID is not provided, respectively, in an embodiment of the above-described option 2.
  • the M-BA ID providing field is included in the common information field (e.g., trigger dependent common information field).
  • the M-BA ID provision field is 0 as shown in FIG. 27H
  • the trigger dependent common information field does not include the reference M-BA ID (eg, the first M-BA ID)
  • the trigger dependent individual user information field is M-BA. It does not include the BA ID index.
  • the M-BA ID provision field is 1 as shown in FIG.
  • the trigger dependent common information field includes a reference M-BA ID (eg, a first M-BA ID), and the trigger dependent individual user information field is an M-BA. Contains an ID index.
  • M-BA ID eg, a first M-BA ID
  • the M-BA ID provision field is included in a trigger dependent common information field common to STAs, whether to provide an M-BA ID is also set to be common to STAs. For example, if the M-BA ID provisioning field is 0, the trigger dependent common user field does not have a reference M-BA ID value, and all of the individual user information fields included in the trigger frame do not include the M-BA ID index value. Do not. If the M-BA ID provision field is 1, the trigger dependent common user field has a reference M-BA ID value, and all of the plurality of individual user information fields included in the trigger frame include the M-BA ID index value.
  • the value of the trigger type field included in the trigger frame may be newly defined for M-BA ID assignment.
  • the newly defined new trigger type may indicate that the trigger frame includes an M-BA ID (e.g., option 1) or an M-BA ID index (e.g., option 2). Therefore, the above-described M-BA ID providing field can be omitted.
  • the new trigger type may be selected from among reserved values.
  • the new trigger type may be any one of 4 to 15.
  • the new trigger type may be viewed as a basic trigger type with M-BA ID information added.
  • FIG. 27J illustrates a case where a new trigger type is set in the embodiment for the above-described option 1. If the new trigger type is set in the common information field of the trigger frame, a plurality of individual user information fields (e.g., trigger dependent individual user information fields) included in the trigger frame include an M-BA ID to be assigned to each STA.
  • a plurality of individual user information fields e.g., trigger dependent individual user information fields
  • FIG. 27K illustrates the case where the new trigger type is set in the embodiment for the above-described option 2.
  • the trigger dependent common information field includes a reference M-BA ID (eg, first M-BA ID), and a plurality of individual user information fields included in the trigger frame. (eg, trigger dependent individual user information fields) include an M-BA ID index indicating an M-BA ID to be assigned to each STA.
  • a range of values usable as the M-BA ID may be reserved.
  • the range of values usable with the M-BA ID may be set differently from the range of values usable with the AID. For example, values of the first range of values 0 to 2047 that can be indicated through a total of 11 bits are used for general AID purposes (eg, individual STA IDs), but values of the second range that do not overlap the first range. Can be used for M-BA ID purposes. For convenience of explanation, it is assumed that the values that can be used for the M-BA ID are eight from 2008 to 2015, but the present invention is not limited thereto. Since there are eight possible values for the M-BA ID, the length of the M-BA ID index can be set to 3-bits.
  • FIG. 27L illustrates a trigger frame based on option 2 but without a reference M-BA ID.
  • M-BA ID e.g., option 1
  • M-BA ID index e.g., option 2
  • FIG. 27N illustrates an embodiment based on option 2, in which an M-BA ID range is pre-reserved and an M-BA ID providing field is set to 1.
  • FIG. 27O illustrates an embodiment based on option 2, in which an M-BA ID range is pre-reserved and an M-BA ID providing field is set to 1.
  • M-BA ID provision field trigger dependent individual user information field set to 0 does not include M-BA ID index. The reference M-BA ID is omitted.
  • an unused STA ID among the STA IDs may be assigned to the STA for M-BA purposes (eg, M-BA ID) temporarily or for a predetermined time, and trigger frame for M-BA ID assignment.
  • M-BA ID M-BA ID
  • the M-BA frame may be transmitted in the OFDMA PPDU format, and the STA ID subfield of the HE-SIG B field of the M-BA frame may be set to the assigned M-BA ID.
  • the M-BA ID is included in the individual user information field.
  • the reference M-BA ID may be included in the common user information field, and the M-BA ID index indicating the M-BA ID to be actually assigned may be included in the individual user information field.
  • Option 2 has the advantage of lower signaling overhead compared to option 1.
  • the values available for the M-BA ID may be reserved, and the values available for the M-BA ID are preferably continuous with each other.
  • the M-BA ID may be effectively used only in the corresponding TXOP including the trigger frame. For example, when TXOP is terminated, an M-BA ID may be invalid or a process for extending the validity of the M-BA ID may be performed.
  • an M-BA ID (e.g., GID) may be predefined or mapped for each channel (e.g., 20 MHz channel or 242 tones).
  • a channel consisting of some tones of all the tones is referred to as a subchannel.
  • FIG. 28A illustrates M-BA ID for each channel according to an embodiment of the present invention.
  • a total of eight values from AID 2008 to 2015 may be used as the M-BA ID.
  • the STA may specify the M-BA ID to be used by the STA according to which subchannel the UL MU PPDU is transmitted.
  • FIG. 28A illustrates that the size of the subchannel is 242 tones
  • the present invention is not limited thereto.
  • the size of the subchannel may correspond to 106 tones. If one M-BA ID is allocated per 106 tons, a total of 16 values may be used as the M-BA ID from 2008 to 2023.
  • the STA may be automatically assigned an M-BA ID by transmitting a UL MU PPDU (or HE trigger based PPDU) through a resource included in a corresponding subchannel (e.g., 106/242 tones).
  • M-BA ID 2010 is allocated to the STA that has transmitted the UL MU PPDU on the third 242 tone (CH3).
  • the embodiment of the present invention is not limited to M-BA IDs allocated in units of subchannels corresponding to 242 tones, and may be allocated every 484 tones or every 996. For example, in the case of a 160 MHz channel, a total of 14 M-BA IDs from 2008 to 2021 may be allocated to each subchannel. In the case of an 80 MHz channel, a total of seven M-BA IDs may be allocated to each subchannel from 2008 to 2014.
  • the STA that transmits the UL MU PPDU on the second 242 tones CH2 may determine whether the M-BA ID is allocated every 242 tones, every 484 tones, or every 996 tones. , 2016 or 2020 values can be used as M-BA IDs.
  • the AP transmits the M-BA frame on the second 242 tone the AP may set 2009 as the M-BA ID in the STA ID subfield in the individual user information field of HE-SIG B of the M-BA frame.
  • the AP may set 2016 as the M-BA ID in the STA ID subfield in the individual user information field of HE-SIG B of the M-BA frame.
  • the AP may set 2020 as the M-BA ID in the STA ID subfield in the individual user information field of HE-SIG B of the M-BA frame.
  • M-BA ID information (e.g., mapping information between sub-channels and M-BA IDs) for each subchannel may be preset or predefined on the system.
  • M-BA ID information for each subchannel may be signaled to the STA through a management frame, for example, a beacon, a probe response, an association response, a wrapper frame, and the like, but is not limited thereto.
  • the STA may derive the M-BA ID for the corresponding subchannel based on the mapping information between the subchannel obtained through the management frame and the M-BA ID and the subchannel through which the UL MU PPDU is transmitted. Can be.
  • the STA may receive an OFDMA frame (e.g., an OFDMA PPDU M-BA frame) using the derived M-BA ID.
  • an OFDMA PPDU-based M-BA frame (hereinafter, referred to as an OFDMA M-BA frame) may be transmitted using an individual STA ID.
  • the M-BA frame may be transmitted through the individual STA ID instead of allocating and using the M-BA ID separately from the AID.
  • M-BA ID AID, which is an individual STA ID.
  • resource allocation information (eg, RU allocation information of Per User Info of HE-SIG B) provided to each STA through an OFDMA M-BA frame may indicate resources of an M-BA MPDU.
  • resource allocation information fields of at least two STAs signaled through an M-BA frame may indicate the same OFDMA resource (same OFDMA resource for the corresponding M-BA MPDU).
  • the overhead of the HE-SIG B may vary depending on the number of STAs, not the number of M-BA allocations.
  • RU resource unit
  • multiple STAs may be allocated the same RU, but data streams transmitted on the corresponding RU are not shared by the STAs. That is, in the MU-MIMO scheme, a plurality of STAs may be multiplexed on a STA common RU, but each STA may receive only its own data stream among a plurality of data streams transmitted through the STA common RU.
  • the corresponding 1 RU is not one of MU-MIMO transmission (eg, multiplex transmission of STA specific data streams) but one data stream. It can be used for transmission (eg, broadcast / multicast data transmission such as M-BA). Accordingly, STAs should be able to know whether the RU allocation by the AP is for MU-MIMO transmission or one data stream transmission (eg, broadcast / multicast of a PPDU set in SU format), thus distinguishing both. There is a need for a signaling method.
  • whether the RU allocation is the MU-MIMO allocation or the SU allocation may be indicated through the content of the common field of the HE-SIG B.
  • an 8-bit RU allocation index (see the description in Table 2a) set in the RU allocation field of HE-SIG B may be used. For example, using some of the reserved values of use of the RU allocation index, it may be indicated whether the corresponding RU is an SU allocation. Referring to Table 2a, since '000 1 xxxx', '011 xxxxx', and '111 xxxxx' are reserved, some of them may be used.
  • zzz may be set to one of 000 to 111. Therefore, in Table 15, zzz represents the number of STAs multiplexed on 1 RU. For example, when each bit of zzz is sequentially expressed as' z [3] z [2] z [1] ', the number of STAs multiplexed into one RU is' 2 2 * z [3] + 2 1 * z. [2] + 2 0 * z [1] +1 'corresponds.
  • the number of STAs multiplexed in one RU may be viewed as the number of STAs that share a data stream transmitted through the corresponding RU. For example, if the data stream is an M-BA MPDU and zzz is 011, the M-BA MPDU may include ACK / BAs for a total of three STAs.
  • the RU allocation index value When the RU allocation index value is set to the values defined in Table 2a, it may be indicated that the RU allocation is an MU-MIMO allocation. Alternatively, if the RU allocation index value is set to the values defined in Table 14, it can be indicated that the corresponding RU allocation is SU allocation.
  • the MU-MIMO indicator may be included in the common field of the HE-SIG B.
  • the MU-MIMO indicator may be set as a bitmap, and the MU-MIMO indicator bitmap may be included for each RU allocation.
  • each bit is mapped to an RU corresponding to yyy (eg, an RU in which yyy STAs are multiplexed), and indicates whether the RU corresponding to yyy is an MU-MIMO allocation or a SU-MIMO allocation. Can be.
  • the MU-MIMO indicator bitmap may be set to 2-bit. Referring to Table 2a, the maximum number of RUs (eg, multiplexing of STAs) of 106 or more tones in a RU array is supported (up to 2 for 10 yyy yyy). ). Meanwhile, an RU arrangement in which the number of RUs of 106 tons or more is 3 or more may be newly defined, and in this case, the size of the MU-MIMO indicator bitmap may also increase.
  • the MU-MIMO indicator bitmap may not be used. For example, when the RU allocation indicator is 00001111 or less, the MU-MIMO indicator bitmap may be omitted.
  • the RU array indicated by the RU allocation indicator contains only one RU corresponding to yyy (eg, 00100 yyy, etc.), only one bit is used in the MU-MIMO indicator bitmap or MU-MIMO instead of the bitmap.
  • Indicator 1 bit may be set.
  • the MU-MIMO indicator bitmap only the first bit is used to indicate whether the RU corresponding to yyy (eg, 106, 242, 484, 996 or (2 * 996) tone RU) is MU-MIMO, Bit is not used.
  • the first bit of the MU-MIMO indicator bitmap is used to indicate whether the first 106-tone RU is MU-MIMO, and the second bit has two It may be used to indicate whether the first 106 tone RU is used as MU-MIMO.
  • a total of N MU-MIMO indicator bitmaps (e.g., 2 bits each) may be included in the HE-SIG B.
  • an indicator indicating whether each user field included in the user specific field of HE-SIG B is for SU allocation or MU-MIMO allocation (eg, a 1-bit type field) May be included in the corresponding user field.
  • Table 16 illustrates a user field of a user specific field of HE-SIG B for SU allocation.
  • Table 17 illustrates a user field of a user specific field of HE-SIG B for MU-MIMO allocation.
  • the STA may know whether the corresponding user field relates to SU allocation or MU-MIMO allocation through a type subfield included in the user field.
  • FIG. 30 illustrates an example in which three STAs (e.g., three users) are SU MIMO allocated in one RU (e.g., 106 tone RU) according to an embodiment of the present invention.
  • whether or not to allocate SU may be indicated by using a spatial configuration subfield of a user field of a user specific field of HE-SIG B.
  • whether or not the SU allocation or the MU-MIMO allocation may be indicated using the remaining unused values (hereinafter, unused values) in Table 2b.
  • the same number of streams may be indicated to STAs corresponding to the number of users Nuser. For example, multiple STAs can share the same streams.
  • Tables 18 to 20 illustrate setting of a spatial configuration subfield for indicating whether to allocate an SU using unused values.
  • the shaded (or underlined) parts in Tables 18 to 20 correspond to unused values in Table 2b.
  • One or more of the unused values may indicate that all of the Total Nsts streams corresponding to the unused value are equally allocated to all identified STAs. .
  • Stream 1 is assigned to STA 1 identified by user field 1 (eg, the first user field corresponding to Nsts [1]) and assigned to user field 2 (eg, the second user field corresponding to Nsts [2]).
  • Stream 1 is also assigned to STA 2 identified by. That is, the same stream 1 is allocated to STA 1 and STA 2.
  • Stream 1 may be an M-BA MPDU including an ACK / BA for STA 1 and an ACK / BA for STA 2, but is not limited thereto.
  • Table 19 illustrates the case where the number of users is 4 to 6.
  • Table 20 illustrates the case where the number of users is 7 or 8.
  • Tables 18 to 20 are just examples, and the present invention is not limited thereto.
  • the number of Spatial Configuration indices defined to indicate SU allocation may be set to three or more.
  • the number of streams indicated is not limited to 1, 2, 3 and may be replaced by other values (e.g., 1,2,4 or 1, 3, 5) and the like.
  • the M-BA frame may include BA information for nine or more STAs. Therefore, there may be a case where 9 or more STAs are multiplexed per 1 RU for M-BA frame transmission.
  • the specific Spatial Configuration index may indicate that the spatial stream of the user field immediately following the corresponding user field is the same as the spatial stream of the corresponding user field.
  • Table 21 illustrates the encoding of a spatial configuration subfield to support nine or more STAs.
  • the spatial setting subfield of the eighth user field indicates 0010
  • two spatial streams for the eighth user field are equally applied to the ninth user field which is not defined through the table.
  • the spatial setting subfield of the ninth user field indicates 0010
  • two spatial streams for the ninth user field are equally applied to the tenth user field which is not defined through the table.
  • 0001 indicates one total stream
  • 0010 indicates two total streams
  • 0111 indicates three total streams.
  • the HE-SIG B field of FIG. 31 supports a total of nine STAs.
  • the spatial setting subfield is set to 0010. This is because each user field # 1 to # 8 uses the same RU and the same stream as the user field (e.g., user fields # 2 to # 9) located immediately after it. In the case of user field # 9, the space setting subfield is set to 1110. This is because the next user field # 10 using the same RU and the same stream as the user field # 9 does not exist.
  • the number of streams is two, but is not limited thereto. If the number of streams is 1, the space setting subfield of the user fields # 1 to # 8 indicates 0001, and the space setting subfield of the user field # 9 indicates 1111. If the number of streams is 3, the space setting subfield of the user fields # 1 to # 8 indicates 0011, and the space setting subfield of the user field # 9 indicates 1101.
  • each index value and the number of streams indicated by the index values may be changed according to an embodiment.
  • the number of streams is assumed to be 1 to 3
  • a spatial configuration index may be defined for four or more streams.
  • the AP transmits a trigger frame to the STA (S3205).
  • the AP may allocate a GID to a group ID (GID) STA allocated through a trigger frame.
  • the GID may be assigned by a combination of the reference GID and the GID index included in the trigger frame.
  • the GID index may indicate a difference between the value of the reference GID and the value of the GID assigned to the STA.
  • the trigger frame may indicate whether a GID is allocated to the STA through a trigger type subfield or a GID providing subfield.
  • the STA transmits a UL uplink multi-user (MU) frame based on the trigger frame (S3210).
  • MU uplink multi-user
  • the STA receives an M-BA frame based on an OFDMA physical layer protocol data unit (PPDU) including an SIG B field (S3215).
  • PPDU physical layer protocol data unit
  • S3215 The STA may obtain a data stream including ACK / NACK for itself from the M-BA frame based on the OFDMA PPDU (S3220).
  • the STA may obtain the data stream according to the indication of the user field identified by a predetermined ID (e.g., GID or AID) among the plurality of user fields included in the SIG B field.
  • the data stream indicated by the user field identified by the predetermined ID may be equally allocated to other STAs that have performed UL MU transmission based on the trigger frame.
  • the STA may be multiplexed with other STAs that have performed UL MU transmission based on the trigger frame on at least one of the resource units (RUs) allocated by the user common field of the SIG B field. For example, whether at least one RU to which the STA and other STAs are multiplexed is MU-MIMO allocated or single user (SU) allocated may be indicated by the RU allocation index set in the user common field.
  • RUs resource units
  • the data stream of the STA is shared with other STAs.
  • SU allocation because it can be viewed similarly to SU allocation in that multiple STAs share the same data stream.
  • the actual number of STAs receiving the data stream may be several.
  • MU-MIMO allocation the data stream is not shared between STAs.
  • each of the plurality of user fields included in the HE-SIG B has a spatial configuration index indicating whether the corresponding user field corresponds to MU-MIMO allocation or single user (SU) allocation. It may include. For example, when the corresponding user field corresponds to SU allocation, the number of data streams of the corresponding user field indicated by the spatial setting index may be set equal to the total number of data streams for all the plurality of user fields. In addition, if the spatial setting index in the N-th user field corresponds to a specific value, the data stream of the N + 1-th user field may be set equal to the data stream of the N-th user field.
  • 33 is a view for explaining an apparatus for implementing the method as described above.
  • the wireless device 800 of FIG. 33 may correspond to a specific STA of the above description, and the wireless device 850 may correspond to the AP of the above-described description.
  • the STA 800 may include a processor 810, a memory 820, a transceiver 830, and the AP 850 may include a processor 860, a memory 870, and a transceiver 880.
  • the transceivers 830 and 880 may transmit / receive wireless signals and may be executed at a physical layer, such as IEEE 802.11 / 3GPP.
  • Processors 810 and 860 run at the physical and / or MAC layers and are coupled to transceivers 830 and 880.
  • Processors 810 and 860 may perform the aforementioned UL MU scheduling procedure.
  • Processors 810 and 860 and / or transceivers 830 and 880 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits and / or data processors.
  • the memories 820 and 870 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media and / or other storage units.
  • ROM read-only memory
  • RAM random access memory
  • flash memory memory cards
  • the method described above can be executed as a module (eg, process, function) that performs the functions described above.
  • the module may be stored in the memory 820, 870 and executed by the processors 810, 860.
  • the memories 820 and 870 may be disposed inside or outside the processes 810 and 860 and may be connected to the processes 810 and 860 by well-known means.
  • the present invention has been described assuming that it is applied to an IEEE 802.11-based WLAN system, but the present invention is not limited thereto.
  • the present invention can be applied in the same manner to various wireless systems in which the AP can operate the Block Ack mechanism for a plurality of STAs.

Landscapes

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

Abstract

La présente invention concerne, selon un mode de réalisation, un procédé par lequel une station (STA) reçoit une trame d'accusé de réception de bloc multi-STA (M-BA) dans un système de réseau local (LAN) sans fil prenant en charge l'accès multiple par répartition orthogonale de la fréquence (OFDMA), qui comprend les étapes consistant à : envoyer une trame multiutilisateur de liaison montante (MU UL) sur la base d'une trame de déclenchement ; recevoir une trame M-BA basée sur une unité de données de protocole de couche physique (PPDU) OFDMA comprenant un champ SIG B ; et acquérir un flux de données comprenant un accusé de réception/accusé de réception négatif (ACK/NACK) pour la STA à partir de la trame M-BA basée sur la PPDU OFDMA, la STA acquérant le flux de données conformément à une indication d'un champ utilisateur identifié par un identificateur (ID) prédéfini parmi une pluralité de champs utilisateurs inclus dans le champ SIG B, et le flux de données indiqué par le champ utilisateur identifié par l'ID prédéfini pouvant être attribué d'une manière égale à d'autres STA effectuant la transmission MU UL sur la base de la trame de déclenchement.
PCT/KR2016/004550 2015-04-29 2016-04-29 Procédé d'envoi et de réception de signal de réponse de confirmation pour données multiutilisateur de liaison montante dans un système de réseau local sans fil, et appareil correspondant Ceased WO2016175614A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/567,009 US10284287B2 (en) 2015-04-29 2016-04-29 Method for transmitting and receiving confirmation response signal for uplink multi-user data in wireless LAN system, and apparatus therefor

Applications Claiming Priority (20)

Application Number Priority Date Filing Date Title
US201562154134P 2015-04-29 2015-04-29
US62/154,134 2015-04-29
US201562159962P 2015-05-12 2015-05-12
US62/159,962 2015-05-12
US201562170700P 2015-06-04 2015-06-04
US62/170,700 2015-06-04
US201662276245P 2016-01-08 2016-01-08
US62/276,245 2016-01-08
US201662281121P 2016-01-20 2016-01-20
US62/281,121 2016-01-20
US201662296618P 2016-02-18 2016-02-18
US62/296,618 2016-02-18
US201662297948P 2016-02-22 2016-02-22
US62/297,948 2016-02-22
US201662298947P 2016-02-23 2016-02-23
US62/298,947 2016-02-23
US201662305473P 2016-03-08 2016-03-08
US62/305,473 2016-03-08
US201662314998P 2016-03-30 2016-03-30
US62/314,998 2016-03-30

Publications (1)

Publication Number Publication Date
WO2016175614A1 true WO2016175614A1 (fr) 2016-11-03

Family

ID=57199604

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/004550 Ceased WO2016175614A1 (fr) 2015-04-29 2016-04-29 Procédé d'envoi et de réception de signal de réponse de confirmation pour données multiutilisateur de liaison montante dans un système de réseau local sans fil, et appareil correspondant

Country Status (2)

Country Link
US (1) US10284287B2 (fr)
WO (1) WO2016175614A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017218808A1 (fr) * 2016-06-15 2017-12-21 Qualcomm Incorporated Indication de multidiffusion à largeur de bande complète vers de multiples utilisateurs
CN113193884A (zh) * 2017-01-09 2021-07-30 韦勒斯标准与技术协会公司 用信号通知多用户分组的无线通信方法和无线通信终端

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016173103A1 (fr) * 2015-04-30 2016-11-03 华为技术有限公司 Procédé et appareil d'indication de ressources pour un système wlan
US10582025B2 (en) 2015-05-05 2020-03-03 Samsung Electronics Co., Ltd. Efficient signaling and addressing in wireless local area network systems
CN113992248B (zh) 2015-05-05 2024-02-02 三星电子株式会社 识别/指示无线局域网中的调度信息的装置和方法
CN106550479B (zh) * 2015-09-17 2021-11-05 中兴通讯股份有限公司 一种信道接入方法、接入点、站点
US10256961B2 (en) * 2015-10-23 2019-04-09 Marvell World Trade Ltd. Acknowledgment of uplink orthogonal frequency division multiple access transmission
GB2548155B (en) * 2016-03-11 2020-06-17 Canon Kk Improved access to random resource units by a plurality of BSSs
WO2018094279A2 (fr) * 2016-11-17 2018-05-24 Zte Corporation Accès aléatoire basé sur ofdma segmenté
CN108366395B (zh) * 2017-01-26 2023-04-28 中兴通讯股份有限公司 一种配置无线发送接收参数的方法、装置及系统
US10834671B2 (en) * 2017-12-22 2020-11-10 Intel IP Corporation Group identification indication signaling
JP2020141301A (ja) * 2019-02-28 2020-09-03 キヤノン株式会社 通信装置、通信装置の通信方法、及び、プログラム
US10873383B2 (en) * 2019-03-08 2020-12-22 Huawei Technologies Co., Ltd. Communications in spatial streams
CN110266821A (zh) * 2019-07-19 2019-09-20 南京世竹软件科技有限公司 一种物联网监测大数据的存储系统
CN111245763B (zh) * 2020-01-10 2023-01-31 展讯通信（上海）有限公司 Ofdm系统多ap操作的数据发送及接收方法、接入点、站点及存储介质
CN113132072A (zh) * 2020-01-11 2021-07-16 华为技术有限公司 打孔信息的指示方法及通信装置
US12267821B2 (en) 2020-05-15 2025-04-01 Samsung Electronics Co., Ltd. Methods and device for communicating PPDU
CN115333908B (zh) * 2021-05-10 2024-03-08 苏州速通半导体科技有限公司 无线局域网中的发射器及由其执行的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110095098A (ko) * 2010-02-18 2011-08-24 엘지전자 주식회사 무선 랜에서 수신 확인 전송 방법 및 장치
WO2013157787A1 (fr) * 2012-04-15 2013-10-24 엘지전자 주식회사 Procédé et appareil d'émission et de réception de trames de déclenchement de rétroaction dans des systèmes de réseau sans fil (wlan)
US20130301569A1 (en) * 2012-05-11 2013-11-14 Interdigital Patent Holdings, Inc. Method and apparatus for transmitting acknowledgements in response to received frames

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10181930B2 (en) * 2015-05-10 2019-01-15 Newracom, Inc. Multiplexing acknowledgment messages in response to downlink frames
CN113452494A (zh) * 2015-05-15 2021-09-28 韦勒斯标准与技术协会公司 用于多用户上行链路传输的无线通信终端和无线通信方法
US20170280424A1 (en) * 2016-03-22 2017-09-28 Chittabrata Ghosh Resource allocation signaling in uplink frames in wireless networks
US10575249B2 (en) * 2016-11-22 2020-02-25 Frontside Transmitting PPDU

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110095098A (ko) * 2010-02-18 2011-08-24 엘지전자 주식회사 무선 랜에서 수신 확인 전송 방법 및 장치
WO2011102575A1 (fr) * 2010-02-18 2011-08-25 엘지전자 주식회사 Procédé et appareil de transmission d'ack dans un wlan
WO2013157787A1 (fr) * 2012-04-15 2013-10-24 엘지전자 주식회사 Procédé et appareil d'émission et de réception de trames de déclenchement de rétroaction dans des systèmes de réseau sans fil (wlan)
US20130301569A1 (en) * 2012-05-11 2013-11-14 Interdigital Patent Holdings, Inc. Method and apparatus for transmitting acknowledgements in response to received frames

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KWON, YOUNG HOON ET AL.: "Issues on UL-OFDMA Transmission", IEEE 802.11-14/1431R0, 3 November 2014 (2014-11-03), XP055326477 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017218808A1 (fr) * 2016-06-15 2017-12-21 Qualcomm Incorporated Indication de multidiffusion à largeur de bande complète vers de multiples utilisateurs
US9967073B2 (en) 2016-06-15 2018-05-08 Qualcomm Incorporated Full bandwidth multicast indication to multiple users
CN113193884A (zh) * 2017-01-09 2021-07-30 韦勒斯标准与技术协会公司 用信号通知多用户分组的无线通信方法和无线通信终端
US12176975B2 (en) 2017-01-09 2024-12-24 Wilus Institute Of Standards And Technology Inc. Wireless communication method and wireless communication terminal for signaling multi-user packet

Also Published As

Publication number Publication date
US20190052353A1 (en) 2019-02-14
US10284287B2 (en) 2019-05-07

Similar Documents

Publication Publication Date Title
WO2016175614A1 (fr) Procédé d'envoi et de réception de signal de réponse de confirmation pour données multiutilisateur de liaison montante dans un système de réseau local sans fil, et appareil correspondant
WO2020013594A1 (fr) Procédé et dispositif de transmission de données dans un système lan sans fil
WO2020045891A1 (fr) Procédé et dispositif destinés à établir une transmission commune dans un système de réseau local sans fil
WO2019194516A1 (fr) Procédé et dispositif de transmission de ppdu sur la base d'un fdr dans un système lan sans fil
WO2021167436A1 (fr) Procédé d'émission et de réception de données dans un système de communication sans fil, et terminal de communication sans fil
WO2020022814A1 (fr) Procédé et appareil de réception de données d'ul dans un système lan sans fil
WO2018124725A1 (fr) Procédé de communication sans fil utilisant un accès aléatoire ofdma et terminal de communication sans fil qui l'utilise
WO2020050541A1 (fr) Procédé et dispositif pour transmettre une trame dans un système lan sans fil
WO2017150954A1 (fr) Procédé de communication sans fil et terminal de communication sans fil dans un ensemble de services de base chevauchant un autre ensemble de services de base
WO2020032430A1 (fr) Procédé et appareil pour la transmission de ppdu dans un système wlan
WO2019225986A1 (fr) Procédé et dispositif de transmission et de réception de ppdu sur la base d'un fdd dans un système lan sans fil
WO2016167609A1 (fr) Procédé de sondage de canal dans un système de communication sans fil et dispositif à cet effet
WO2019245265A1 (fr) Procédé et dispositif de transmission de données dans un système lan sans fil
WO2019164365A1 (fr) Procédé et dispositif de transmission de ppdu sur la base d'un fdr dans un système lan sans fil
WO2017043713A1 (fr) Procédé de transmission de données dans un système de communication sans fil et appareil associé
WO2016072766A1 (fr) Procédé et dispositif d'attribution d'unité de ressource sur la base d'un conteneur dans un lan sans fil
WO2020060168A1 (fr) Procédé et dispositif de transmission de données dans un système de lan sans fil
WO2020060169A1 (fr) Procédé et dispositif de réception de données dans un système lan sans fil
WO2017135770A1 (fr) Procédé et dispositif pour générer des signaux stf au moyen d'une séquence binaire dans un système lan sans fil
WO2019182267A1 (fr) Procédé et appareil pour la transmission d'une ppdu sur la base d'un fdr dans un système lan sans fil
WO2019182427A1 (fr) Procédé et appareil pour transmettre des données via nccb dans un système de réseau local sans fil
WO2019164362A1 (fr) Procédé et dispositif de transmission d'une ppdu sur la base d'un fdr dans un système lan sans fil
WO2020166770A1 (fr) Procédé et appareil destinés à réaliser une transmission conjointe dans un système lan sans fil
WO2019240541A1 (fr) Procédé et dispositif de réception de données de liaison montante dans un système lan sans fil
WO2017164687A1 (fr) Procédé de gestion de puissance dans un système lan sans fil et terminal sans fil l'utilisant

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: 16786800

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16786800

Country of ref document: EP

Kind code of ref document: A1