doc.: IEEE /0926r5 Submission Interworking with 802.1Qat Stream Reservation Protocol Date: Authors: Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 1

doc.: IEEE /0926r5 SubmissionSlide 2 Abstract This submission is an overview of proposed input from 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 aa teleconference on Aug 10 th, 2009 and has been iteratively refined in later teleconferences/meetings. Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 2

doc.: IEEE /0926r5 Submission Annex-Q in IEEE 802.1Qat-Draft 3.2 is informative and describes implementation details for a Designated MSRP Node (DMN) Qat has decided to mark Annex-Q as normative. From ’s perspective, the DMN is co-located with the device that supports the QAP function in a BSS When stream reservations are made the following needs to be completed: Appropriate TSPECs are passed to the QAP 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 (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. Overview Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 3

doc.: IEEE /0926r5 Submission Handling SRP Reservation Requests Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 4

doc.: IEEE /0926r5 Submission Figure Q-5 Talker is wired to the Q-AP. Listeners can be STA(s) in the BSS or device(s) wired to the Q-STA(s) in the BSS, Figure Q-6 Talker is wired to a Q-STA in the BSS. Listeners can be other Q-STA(s) in the BSS and/or device(s) wired to the Q-AP/Q-STA(s) Figure Q-7 Talker is wired to a Q-STA (STA-A) in the BSS. Listener is another Q-STA in the BSS which has a direct link established with STA-A. Topologies Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 5

doc.: IEEE /0926r5 Submission Case-1: STA is the Talker/Listener Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 6 Talker Q-AP DMN Listener(s) Talker Q-AP DMN Listener(s) Talker Q-AP Listener(s) Q-STA

doc.: IEEE /0926r5 Submission Case-2: STA is an Intermediate node or a Talker/Listener Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 7 Q-AP DMN Listener(s) Q-STA Talker/Listener(s) 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 Q-AP Note: This scenario is included for completeness. Support for this requires resolution of the “Station Bridge issue*”. * See

doc.: IEEE /0926r5 Submission Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 8 Case-3: STA is the Talker/Listener Q-AP DMN Listener(s) Q-STA Talker Listener(s) Dqta Flow SRP Control Flow

doc.: IEEE /0926r5 Submission A Q-STA can either be Talker/Listener or an intermediate node in the path from the Talker to the Listener. An intermediate node Q-STA or a Q-STA that is also the Talker/Listener just pass the MSRPDU to the Q-AP Q-AP forwards the MSRPDU to the Q-AP’s DMN Q-AP’s DMN invokes MLME-Reserve.request or MLME- Query.request with parameters corresponding to the received SRP Reservation/Query request If the MSRPDU is a Reservation Request and the Q-AP has sufficient resources: Q-AP’s SME issues a MLME.ADDTS.response to the talker Q-AP’s SME issues a MLME.ADDTS.response to the listener Q-AP responds to the DMN with a MLME-Reserve.confirm or MLME-Query.confirm MSPRDU Processing at the Q-AP/DMN Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 9

doc.: IEEE /0926r5 Submission Case 2: MSRP Handling at Q-AP/DMN (to Talker/Listener) Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 10

doc.: IEEE /0926r5 Submission Table Q.3 SRP to MLME QoS Services Mapping Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 11 MSRP AttributeMAD PrimitiveMLME QoS Service Description Talker AdvertiseMAD_Join_Request (new) MLME.QUERYQuery bandwidth availability without reservation Listener Ready or Listener Ready Failed MAD_Join_Request (new) MLME.ADDTSReserve bandwidth for a stream Listener Ready or Listener Ready Failed MAD_Join_Request ()MLME.ADDTSModify bandwidth reserved for a stream – no renewal needed, if requirements have not changed. Listener Request Removed MAD_Leave_Request ()MLME.DELTSFree bandwidth associated with a stream MAD – MRP (Multiple Registration Protocol) Attribute Declaration

doc.: IEEE /0926r5 Submission Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 12 Changes to Summary 1.Ability for QAPs to send Autonomous ADDTS Response 2.Add MLME-QUERY.{request|confirm} 3.Modify MLME-ADDTS.{request|confirm} 4.Allow MLME-ADDTS.{request|confirm} to be invoked at the AP STA 802.1Qat 1.Mandate that STAs and APs supporting SRP shall also support EDCA Admission Control 2.The AP and SRP DMN shall co-exist in the same device 3.The SRP DMN shall generate TSPECs as described in slide and slideslide 4.Mandate that STAs and APs supporting SRP shall encapsulate and de-encapsulate the 802.1q Tag

doc.: IEEE /0926r5 Submission Mapping SRP Traffic classes to TSPECs Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 13

doc.: IEEE /0926r5 SubmissionSlide 14 TSPEC mapping (from July joint meeting) Nov 2009 Ganesh Venkatesan, Intel CorporationSlide TSPEC mapping to 802.1Qav TSPEC QoS mechanisms: EDCA-AC HCCA 1.What is the delay over a link? 2.Power save introduces at least 20msec delay 3.What is possible for delay/frame size/rate in.11? 4.08/10/2009 teleconference – 4000 intervals per second. How many frames get sent in an interval depends on max frame size – What can 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) 20ms per wireless hop Max Frame Size75% of 125us 1171bytes (includes IFG) 1500 Max Frame 100Mbps 4000/s (no class-A traffic)

doc.: IEEE /0926r5 Submission Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 15 TSPEC Element Octets: TS InfoNominal MSDU Maximum MSDU Size Minimum Service Interval Maximum Service Interval Inactivity Interval Suspension Interval Service StartTime Minimum Data Rate Mean Data Rate Peak Data RateMaximum Burst Size Delay Bound Minimum PHY Rate Surplus Bandwidth Allowance Medium Time TSPEC Body format Reserved User PriorityPSBReservedAccess Policy DirectionTIDReserved ScheduleTSInfo Ack Policy APSDAggregationAccess Policy DirectionTSIDTraffic Type TS Info Field TSPEC Element 801.D User Priority Up Down Bi 0-7 WMM 8-15 HCCA Note: Often TID 0-7 = UP RED indicates required parameters used in Admission Control TSPEC Value returned by AP if Admission Accepted (Admission Control) 1=APSD Access Policy EDCA, HCCA * Reproduced from WMM IEEE

doc.: IEEE /0926r5 Submission Minimum PHY Rate Derivation Overhead = 10 byte VLAN tag + 8 byte Protocol definition Mean Data Rate = (SRP TSpec MaxFrameSize+overhead) * SRP TSpec MaxIntervalFrames* 4000 bytes/sec The Mean Data Rate is also the Max Data Rate (since we assume MSDU size is fixed). Assuming 70%* efficiency between the MAC and the PHY this translates into (10/7)* 4000 * (SRP TSpec MaxFrameSize+overhead) * SRP TSpec MaxIntervalFrames bytes/sec (10/7) * * (SRP TSpec MaxFrameSize+overhead) * SRP TSpec MaxIntervalFrames bits/sec Minimum PHY Rate is = * (SRP TSpec MaxFrameSize + overhead) * SRP TSpec MaxIntervalFrames bits/sec E.g., –With 1500 and 4000 for MaxFrameSize and MaxIntervalFrames the above turns into (~78Mbps) –For 64 byte SRP payload the equivalent minimum PHY rate is Mbps Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 16

doc.: IEEE /0926r5 Submission EDCA-AC (Input to 802.1Qat) Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 17 TSPEC ParameterSR Class B TSINFOTID5 DirectionUp, Down Access Policy10 (EDCA) ACK Policy(10/11)No ACK/Block ACK APSD0 AggregationYes User Priority (802.1D)5 Nominal MSDU Size 2 SRP Tspec MaxFrameSize + 18 Maximum MSDU SizeSRP Tspec MaxFrameSize + 18 Mean Data Rate(SRP Tspec MaxFrameSize + 18) * SRP Tspec MaxIntervalFrames Delay Bound* 20 msecs Minimum PHY Rate * (SRP TSpec MaxFrameSize + 18) * SRP TSpec MaxIntervalFrames bits/sec Surplus Bandwidth Allowance1.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 Bit-15 set to 1, indicates that the MSDU size is fixed

doc.: IEEE /0926r5 Submission Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 18 TSPECs for HCCA 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.)

doc.: IEEE /0926r5 Submission Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 19 TSPECs for HCCA TSPEC Parameters SR Class B TS Info TID8-15 DirectionUp, Down Access Policy01 (HCCA) ACK Policy(10/11)No ACK/Block ACK APSD0 AggregationYes User Priority (802.1D) 5 Nominal MSDU SizeSRP TSPEC MAX Frame Size + 18 Maximum MSDU SizeSRP TSPEC MAX Frame Size + 18 Minimum Service Interval10 msec Maximum Service Interval10 msec Inactivity Interval0 Minimum Data Rate0 Mean Data Rate (SRP Tspec MaxFrameSize +18) * SRP Tspec MaxIntervalFrames Maximum Burst Size (SRP Tspec MaxFrameSize + 18) * SRP Tspec MaxIntervalFrames * Minimum PHY Rate * (SRP TSpec MaxFrameSize + 18) * SRP TSpec MaxIntervalFrames bits/sec Peak Data Rate (SRP Tspec MaxFrameSize + 18) * SRP Tspec MaxIntervalFrames Delay Bound20 msecs Surplus Bandwidth Allowance1.2

doc.: IEEE /0926r5 Submission How User Priority is preserved end-to-end Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 20 ProtocolType/ Length LLC HeaderIEEE LLC Header VLAN- tagged IP AA-AA AA-AA The priority from is in the 802.1q Tag To preserve the priority end-to-end the aa STA shall encapsulate the VLAN Tag using a 10 byte SNAP encoding as shown in the example above

doc.: IEEE /0926r5 Submission Table Q-4 Recommend replacing this table with two tables –EDCA-AC for Class-B (Table from slide)slide –HCCA for Class-B (Table from slide)slide Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 21

doc.: IEEE /0926r5 Submission QoS Maintenance Report k provides a transmit stream/category measurement report. This report can be generated based on a trigger. SRP DMN may use the MLME-MREQUEST.request to setup triggers for the specific stream in order to generate triggered transmit stream/category measurement reports as needed to generate reports when channel conditions deteriorate Based on the data in the triggered transmit stream/category measurement report, the SRP DMN can generate appropriate QoS Maintenance Report. Nov 2009 Ganesh Venkatesan, Intel CorporationSlide 22

doc.: IEEE /0926r5 Submission References Slide 23 Nov 2009 Ganesh Venkatesan, Intel CorporationSlide QoS Tutorial (08/1214r02) 2. bridging-0308-v3.pdf 3.Annex-K Example Use of TSPEC for Admission Control in Draft Revmb_D1.0.pdf n