802.11 -- Interworking with 802.1Qat Stream Reservation Protocol September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 802.11 -- Interworking with 802.1Qat Stream Reservation Protocol Date: 2009-08-14 Authors: Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

September 2008 November 2007 doc.: IEEE 802.11-07/2752r1 doc.: IEEE 802.11-08/1003r0 Aug 2009 Abstract This submission is an overview of proposed input from 802.11 to 802.1Qat Annex-Q Clause Q.2. A companion word document will be generated when the details in this submission are finalized. Includes inputs from the 802.11aa teleconference on Aug 10th, 2009. Slide 2 Ganesh Venkatesan, Intel Corporation Page 2 Alex Ashley, NDS Ltd Peter Ecclesine, Cisco Systems

Aug 2009 Overview Annex-Q in IEEE 802.1Qat-Draft 3.2 is informative and describes implementation details for a Designated MSRP Node (DMN) From 802.11’s perspective, the DMN is co-located with the device that supports the AP function in a BSS When stream reservations are made the following needs to be completed: Appropriate TSPECs are passed to the AP in order to accomplish the desired level of QoS for the stream (Cl. Q.2.2 Table Q-4) All protocol and MLME interface semantics are maintained within 802.11 (Cl. Q.2.2 Table Q-3) Goals are to make no or minimal changes to Q-STAs and render the DMN implementation as agnostic to the underlying link technology (802.11, MoCA, etc.) used. Ganesh Venkatesan, Intel Corporation

Handling SRP Reservation Requests Aug 2009 Handling SRP Reservation Requests Ganesh Venkatesan, Intel Corporation

September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Topologies Figure Q-5 Talker is wired to the AP. Listeners can be STA(s) in the BSS or device(s) wired to the STA(s) in the BSS, Figure Q-6 Talker is wired to a STA in the BSS. Listeners can be other STA(s) in the BSS and/or device(s) wired to the AP/STA(s) Figure Q-7 Talker is wired to a STA (STA-A) in the BSS. Listener is another STA in the BSS which has a direct link established with STA-A. Question: Can STAs be intermediate nodes? (yes) If so, STAs need a “SRP agent” co-located: 802.11 is not well defined to deal with a wired/wireless bridge within the same device (See http://www.ieee802.org/1/files/public/docs2007/avb-nfinn-wireless-bridges-0707-v2.pdf for more details). Without fixing this issue, does it make sense to build over it? A solution that requires little or no changes to STA is preferred (see Goals in previous slide) Figures Q-5, Q-6 and Q-7 need to be updated to show that possibility. Yes? Could we propose two solutions – once for co-located talker/802.11 and another for talker and 802.11 being separate devices? 802.1Qat editor is fine with it. Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case-1: STA is the Talker/Listener September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case-1: STA is the Talker/Listener Talker logic in STA: Send/Receive the MSRPDU requesting reservation In addition, also use the MLME-ADDTS.Request to send a corresponding TSPEC to the AP DMN forwards the reservation request to the AP’s SME, AP’s MLME also forwards the MLME-ADDTS.Indication to the AP’s SME. Need a ‘Send me an ADDTS Request’ action frame from AP to STA in the case where an 802.11 STA is a listener. Additional complexity to SME at the AP – need some tag to associate ADDTS.Indication from the STA with the SRP reservation request from the DMN SME at the STA needs to send a ADDTS Request matching the SRP Reservation Request Works only when the STA is the SRP Talker/Listener Could we propose two solutions – once for co-located talker/802.11 and another for talker and 802.11 being separate devices? 802.1Qat editor is fine with it. Q: Should we limit 802.11 STA to be 802.1Qat Talker/Listener? Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case-1: STA is the Talker/Listener September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case-1: STA is the Talker/Listener Listener(s) Listener(s) DMN DMN DMN Q-AP Q-AP Q-AP Could we propose two solutions – once for co-located talker/802.11 and another for talker and 802.11 being separate devices? 802.1Qat editor is fine with it. Q-STA Q-STA Q-STA Q-STA Q-STA Talker Talker Listener(s) Talker Listener(s) Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case-1: Q.2.1 MSRP Handling at Talker September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case-1: Q.2.1 MSRP Handling at Talker How does this work for multicast? Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case-1: Q.2.1 MSRP Handling at QAP/Listener Aug 2009 Case-1: Q.2.1 MSRP Handling at QAP/Listener Ganesh Venkatesan, Intel Corporation

Aug 2009 Case 2: General Case An 802.11 STA can either be Talker/Listener or an intermediate node in the path from the Talker to the Listener. An intermediate node STA or a STA that is also the Talker/Listener just pass the MSRPDU to the AP DMN invokes MLME-Reserve.request with parameters corresponding to the received SRP reservation request Reserve Request Action frame includes a TSPEC that corresponds to the SRP traffic class Q-STA uses the TSPEC in the Reserve Request Action frame as a hint and constructs a TSPEC to be used in the resulting ADDTS request Q-STA receives a “successful” ADDTS response from the Q-AP Q-STA responds back to the Q-AP with a Reserve Response Action frame Q-AP responds to the DMN with a MLME-Reserve.confirm Ganesh Venkatesan, Intel Corporation

Case-2: STA is an Intermediate node or a Talker/Listener September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case-2: STA is an Intermediate node or a Talker/Listener Talker/Listener(s) Q-STA are intermediate nodes, Talker or Listener Q-STAs need to understand the new Reserve action frame Q-STAs need not parse SRP reservation message The additional complexity is limited to the QAP DMN Q-AP Q-STA Q-STA Listener(s) Talker Talker Listener(s) Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case 2: MSRP Handling at QAP September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case 2: MSRP Handling at QAP How does this work for multicast? Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Case 2: MSRP Handling at QAP September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Case 2: MSRP Handling at QAP How does this work for multicast? Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Table Q.3 SRP to MLME QoS Services Mapping September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Table Q.3 SRP to MLME QoS Services Mapping MSRP Attribute MAD Primitive MLME QoS Service Description Talker Advertise MAD_Join_Request (new) MLME.Query Query bandwidth availability without reservation Listener Ready or Listener Ready Failed MLME.Reserve Reserve bandwidth for a stream MAD_Join_Request () Modify bandwidth reserved for a stream – no renewal needed, if requirements have not changed. Listener Request Removed MAD_Leave_Request () MLME.DELTS Free bandwidth associated with a stream MAD – MRP (Multiple Registration Protocol) Attribute Declaration Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Questions on Table Q-3 Is there an 802.11 MLME command to query available bandwidth No. Is there an 802.11 MLME command for this? Is this bandwidth renewal even necessary? ADDTS with the same stream ID supersedes an existing reservation. Reservation renewal may be required if the reservation has timed out due to inactivity. At the 08/10/2009 teleconference: 802.1Qat does not support dynamic reservations (adapting to changing channel conditions). SRP does not allow for dynamic allocation Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

Mapping 802.11 TSPECs to SRP Traffic Classes Aug 2009 Mapping 802.11 TSPECs to SRP Traffic Classes Ganesh Venkatesan, Intel Corporation

TSPEC mapping (from July joint meeting) September 2008 November 2007 doc.: IEEE 802.11-07/2752r1 doc.: IEEE 802.11-08/1003r0 Aug 2009 TSPEC mapping (from July joint meeting) 802.11 TSPEC mapping to 802.1Qav TSPEC 802.11 QoS mechanisms: EDCA-AC HCCA What is the delay over a 802.11 link? Power save introduces at least 20msec delay What is possible for delay/frame size/rate in .11? 08/10/2009 teleconference – 4000 intervals per second. How many frames get sent in an interval depends on max frame size – What can 802.11 do in 250 usecs? SR Class-A SR Class-B Max delay tolerance 290us per hop 50msec over 7 hops (2 of which are .11) Max Frame Size 75% of 125us 1171bytes (includes IFG) 1500 Max Frame Rate 8000/s @ 100Mbps 4000/s (no class-A traffic) Slide 17 Ganesh Venkatesan, Intel Corporation Page 17 Alex Ashley, NDS Ltd Peter Ecclesine, Cisco Systems

What is possible with 802.11 (needs work)? September 2008 November 2007 doc.: IEEE 802.11-07/2752r1 doc.: IEEE 802.11-08/1003r0 Aug 2009 What is possible with 802.11 (needs work)? PHY RATES Overhead (channel access, preamble, inter frame space, etc) Data rate per interval (250 us) Overall data rate (without any aggregation) bits/sec Overall data rate (with aggregation) bits/sec Delay (MLME to MLME) Slide 18 Ganesh Venkatesan, Intel Corporation Page 18 Alex Ashley, NDS Ltd Peter Ecclesine, Cisco Systems

TS Info Field TSPEC Element Aug 2009 TSPEC Element TSPEC Body format Octets: 3 2 4 TS Info Nominal MSDU Maximum MSDU Size Minimum Service Interval Inactivity Suspension StartTime Data Rate   Mean Peak Data Rate Burst Size Delay Bound PHY Rate Surplus Bandwidth Allowance Medium Time RED indicates required parameters used in Admission Control TSPEC Value returned by AP if Admission Accepted (Admission Control) TS Info Field TSPEC Element 23 17 16 15 14 13 11 10 9 8 7 6 5 4 1 Reserved User Priority PSB Access Policy Direction TID Schedule TSInfo Ack Policy APSD Aggregation TSID Traffic Type WMM IEEE Up Down Bi 801.D User Priority 1=APSD 0-7 WMM 8-15 HCCA Access Policy EDCA, HCCA * Reproduced from https://mentor.ieee.org/802.11/dcn/08/11-08-1214-02-00aa-11e-tutorial.ppt Note: Often TID 0-7 = UP Ganesh Venkatesan, Intel Corporation

802.11 TSPECs (EDCA-AC) TSPEC Parameter Value (Class-A) Aug 2009 802.11 TSPECs (EDCA-AC) TSPEC Parameter Value (Class-A) Value (Class-B) TSINFO TID 0-7 Direction Up, Down Access Policy 10 (EDCA) ACK Policy (10/11)No ACK/Block ACK? APSD Aggregation <TBD> User Priority (802.1D) 4, 5 or 6 Nominal MSDU Size2 1500 bytes Maximum MSDU Size Mean Data Rate 48 Mbps Delay Bound* 29 usecs? 10% of 7 msecs? Minimum PHY Rate 70 Mbps Surplus Bandwidth Allowance 1.2+ *Time in usecs between when the frame arrived at the transmitting MAC to when it is transmitted to the destination – includes reception of any required Acknowledgements. + 20% surplus allocation? 2 Should bit-15 be set? Bit-15 indicates that the MSDU size is fixed Ganesh Venkatesan, Intel Corporation

TSPECs for HCCA (WMM-SA) Aug 2009 TSPECs for HCCA (WMM-SA) The basic QoS requirements such as jitter, latency, bandwidth etc are defined by the TSPEC ‘Standard’ TSPECs exist for: Voice Multi-Media (Video) Audio STAs send information on their TC and TSPEC, this allows HC to allocate the TXOPs and calculate QoS requirements (jitter, latency, bandwidth, etc.) Ganesh Venkatesan, Intel Corporation

TSPECs for HCCA (WMM-SA) Aug 2009 TSPECs for HCCA (WMM-SA) TSPEC Parameters SRP Class –A SRP Class-B TS Info TBD Nominal MSDU Size 1500 Bytes Maximum MSDU Size Minimum Service Interval Maximum Service Interval Inactivity Interval Minimum Data Rate Mean Data Rate 48 Mbps Maximum Burst Size Minimum PHY Rate 70 Mbps Peak Data Rate Delay Bound 29 usecs 10% of 7 msecs? Surplus Bandwidth Allowance 1.2 Ganesh Venkatesan, Intel Corporation

Table Q-4 Recommend replacing this table with two tables September 2008 doc.: IEEE 802.11-08/1003r0 Aug 2009 Table Q-4 Recommend replacing this table with two tables EDCA-AC for Class-A and Class-B HCCA for Class-A and Class-B Look at QSE work to see how this should be done Ganesh Venkatesan, Intel Corporation Alex Ashley, NDS Ltd

References 802.11 QoS Tutorial (08/1214r02) Aug 2009 References 802.11 QoS Tutorial (08/1214r02) Annex-K Example Use of TSPEC for Admission Control in Draft 803.11Revmb_D1.0.pdf Slide 24 Ganesh Venkatesan, Intel Corporation