Transcript 11-16/0371

March, 2016
doc.: IEEE 802.11-16/0371r2
Further consideration for MU-RTS/CTS
Date: 2016-03-14
Authors:
Name
Affiliations
Address
Phone
email
Jing Ma
NICT
3-4, Hikarino-oka,
Yokosuka, 2390847, Japan
+81-46-8475444
[email protected]
Gabriel Villardi
NICT
[email protected]
Kentaro Ishizu
NICT
[email protected]
[email protected]
Fumihide Kojima NICT
Submission
Slide 1
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Background
• MU-RTS/CTS operation is described in the proposed draft[1]
− Based on the RU allocation in the Per-User Info field addressed to the STA,
the CTS must be transmitted on the primary 20 MHz channel, primary 40
MHz channel, primary 80 MHz channel, 160 MHz channel, or 80+80 MHz
channel.
− Other indications are TBD.
− The CTS sent in response to an MU-RTS frame shall be transmitted on one
or more 20 MHz channels.
Submission
Slide 2
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Background
• The diagrams in the draft specification seems to indicate
that the assignment of one or more 20MHz channels must be
contiguous
− Example of MU-RTS/CTS/Trigger/HE trigger-based PPDU/ Multi-STA
BlockAck and NAV setting[1]
AP
STA1 and STA2
MU-RTS to
STA1 and STA2
Multi-STA
BlockAck to
STA1 and STA2
Trigger to STA1
and STA2
Simultaneous
CTS responses
to AP
HE_TRIG
PPDU to AP
Other
NAV (MU-RTS)
NAV (CTS)
Figure 2 – Example of MU-RTS/CTS/Trigger/HE_TRIG PPDU/Multi-STA BlockAck and NAV setting
Submission
Slide 3
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Background (con’t)
• Additional example of MU-RTS and CTS responses on the
primary 40MHz channel[1]
STA1
Primary
40MHz
STA2
Primary
20MHz
CTS to AP transmitted in
a 40MHz non-HT
duplicate PPDU as
indicated by MU-RTS
Primary
40MHz
Primary
20MHz
CTS to AP transmitted in
a non-HT PPDU as
indicated by MU-RTS
Primary
40MHz
Primary
20MHz
AP
MU-RTS to STA1 and
STA2 transmitted in a
40MHz non-HT duplicate
PPDU
Figure 3 - Example of MU-RTS and CTS Responses on Primary 40MHz Channel
Submission
Slide 4
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Proposal
•
The AP can assign one or more 20MHz channels noncontiguously to further improve the utilization
− (Current) Based on the RU allocation in the Per-User Info field addressed
to the STA, the CTS must be transmitted on the primary 20 MHz channel,
primary 40 MHz channel, primary 80 MHz channel, 160 MHz channel, or
80+80 MHz channel.
− (Current) The CTS sent in response to an MU-RTS frame shall be
transmitted on one or more 20 MHz channels.
− Other indication is TBD -> Proposal:
• For an STA, the one or more secondary 20 MHz channels need not be
contiguous to the primary 20 MHz channel. The secondary 40 MHz channel
needs not be contiguous to the primary 40MHz channel (for 160Mhz channel).
Submission
Slide 5
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Proposal (con’t)
− For an STA, the one or more secondary 20 MHz channel needs not be
contiguous to the primary 20 MHz channel. The secondary 40 MHz channel
needs not be contiguous to the primary 40MHz channel.
E.g.
For STA 2:
Submission
Slide 6
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
Conclusions
• In this contribution, we suggested that the AP can assign one or
more 20MHz channels non-contiguously to further improve the
utilization
Submission
Slide 7
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
SP
• Do you agree to add the following sentence which is marked in
blue to the 4.4 of 11ax TG SFD:
− MU-RTS will carry signaling for each STA to indicate the 20 MHz
channel(s) for transmitting CTS responses when CTS is sent in (duplicate)
non-HT PPDU
• When a STA sends CTS in response to MU-RTS, the CTS response shall be
transmitted in the 20 MHz channel(s) indicated in MU-RTS
provided other transmission conditions TBD are met (e.g. channel idleness)
• The indicated 20 MHz channel(s) can be either Primary20, Primary40, Primary80
or 160/80+80 MHz. For an STA, the one or more secondary 20 MHz channels
need not be contiguous to the primary 20 MHz channel. The secondary 40 MHz
channel needs not be contiguous to the primary 40MHz channel.
• Other indications are TBD.
• Exact Signaling TBD
Submission
Slide 8
Jing Ma, NICT
March, 2016
doc.: IEEE 802.11-16/0371r2
References
1.
2.
11-16/0024r1, Draft Specifications, March 2016
11-15/0132r15, Specification Framework for TGax, Jan 2016
Submission
Slide 9
Jing Ma, NICT