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

2. September 2008
November 2007
doc.: IEEE /2752r1
doc.: IEEE /1003r0
Aug 2009
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 10th, 2009.
Slide 2
Ganesh Venkatesan, Intel Corporation
Page 2
Alex Ashley, NDS Ltd
Peter Ecclesine, Cisco Systems

3. 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 ’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 (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

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

5. September 2008
doc.: IEEE /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:
is not well defined to deal with a wired/wireless bridge within the same device (See 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/ and another for talker and being separate devices? 802.1Qat editor is fine with it.
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

6. Case-1: STA is the Talker/Listener
September 2008
doc.: IEEE /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 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/ and another for talker and being separate devices? 802.1Qat editor is fine with it.
Q: Should we limit STA to be 802.1Qat Talker/Listener?
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

7. Case-1: STA is the Talker/Listener
September 2008
doc.: IEEE /1003r0
Aug 2009
Case-1: STA is the Talker/Listener
Listener(s)
Listener(s)
DMN
DMN
Q-AP
Q-AP
Q-AP
Could we propose two solutions – once for co-located talker/ and another for talker and 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

8. Aug 2009
Case 2: General Case
An 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” [autonomous] 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

9. Case-2: STA is an Intermediate node or a Talker/Listener
September 2008
doc.: IEEE /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
Listener(s)
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

10. Case 2: MSRP Handling at QAP (to Talker/Listener)
September 2008
doc.: IEEE /1003r0
Aug 2009
Case 2: MSRP Handling at QAP (to Talker/Listener)
How does this work for multicast?
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

11. Table Q.3 SRP to MLME QoS Services Mapping
September 2008
doc.: IEEE /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
Instead of a Query API – use the API for making a reservation for 100% of the bandwidth, on failure make it return the available bandwidth.
HCCA complexity is now reduced for the AP – it could be handled in the DMN (in a underlying MAC/PHY agnostic fashion)
MAD – MRP (Multiple Registration Protocol) Attribute Declaration
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

12. Changes to 802.11 -- Summary The following MLME primitives
Aug 2009
Changes to Summary
Ability for QAPs to send Autonomous ADDTS Response
The following MLME primitives
MLME-Query.{request|confitm}
MLME-Reserve .{request|confirm}
Ganesh Venkatesan, Intel Corporation

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

14. TSPEC mapping (from July joint meeting)
September 2008
November 2007
doc.: IEEE /2752r1
doc.: IEEE /1003r0
Aug 2009
TSPEC mapping (from July joint meeting)
TSPEC mapping to 802.1Qav TSPEC
QoS mechanisms:
EDCA-AC
HCCA
What is the delay over a 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 do in 250 usecs?
SR 802.1D Priority-4
SR 802.1D Priority-5
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
100Mbps
4000/s (no class-A traffic)
Are there any parameters to be added to the SR traffic classes?
Do not worry about supporting dynamic bandwidth management
What happens if the bandwidth falls below the reserved value? Just report to DMN and let DMN handle it.
Shaping in scheduled to support 802.1Qav is simple – reserved/available TxOP is known in advance. This can be used to shape the egress traffic.
Slide 14
Ganesh Venkatesan, Intel Corporation
Page 14
Alex Ashley, NDS Ltd
Peter Ecclesine, Cisco Systems

15. 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
Note: Often TID 0-7 = UP
Ganesh Venkatesan, Intel Corporation

16. Minimum PHY Rate Derivation
Aug 2009
Minimum PHY Rate Derivation
Mean Data Rate = SRP TSpec MaxFrameSize * SRP TSpec MaxIntervalFrames
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
1.43 * SRP TSpec MaxFrameSize * SRP TSpec MaxIntervalFrames bytes/sec
 1.43 * SRP TSpec MaxFrameSize * SRP TSpec MaxIntervalFrames * 8 bits bits/sec
11.44 * SRP TSpec MaxFrameSize * SRP TSpec MaxIntervalFrames bits/sec
With 1500 and 4000 for MaxFrameSize and MaxIntervalFrames the above turns into
68.57 (~70Mbps in the table in next slide)
Minimum PHY Rate is
  * SRP TSpec MaxFrameSize * SRP TSpec MaxIntervalFrames
Ganesh Venkatesan, Intel Corporation

17. EDCA-AC (Input to 802.1Qat) Aug 2009 TSPEC Parameter
Value (802.1D Priority-5)
TSINFO
TID 5
Direction
Up, Down
Access Policy
10 (EDCA)
ACK Policy
(10/11)No ACK/Block ACK
APSD
Aggregation
Yes
User Priority (802.1D)
Nominal MSDU Size2
SRP Tspec MaxFrameSize
Maximum MSDU Size
Mean Data Rate
SRP Tspec MaxFrameSize * SRP Tspec MaxIntervalFrames
Delay Bound*
10% of 7 msecs
Minimum PHY Rate
11.44 * Mean Data Rate
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

18. 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

19. TSPECs for HCCA (WMM-SA)
Aug 2009
TSPECs for HCCA (WMM-SA)
TSPEC Parameters
802.1D Priority-5
TS Info
TBD
Nominal MSDU Size
1500 Bytes
Maximum MSDU Size
Minimum Service Interval
10 msec
Maximum Service Interval
Inactivity Interval
Minimum Data Rate
Mean Data Rate
SRP Tspec MaxFrameSize * SRP Tspec MaxIntervalFrames
Maximum Burst Size
SRP Tspec MaxFrameSize * SRP Tspec MaxIntervalFrames * 10-2
Minimum PHY Rate
11.44 * Mean Data Rate
Peak Data Rate
Delay Bound
10% of 7 msecs
Surplus Bandwidth Allowance
1.2
Ganesh Venkatesan, Intel Corporation

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

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

22. Aug 2009
BACKUP Material
Ganesh Venkatesan, Intel Corporation

23. Case-1: Q.2.1 MSRP Handling at Talker
September 2008
doc.: IEEE /1003r0
Aug 2009
Case-1: Q.2.1 MSRP Handling at Talker
The Q-STA parses the MSRPDU before forwarding it to the AP. The Q-STA maps the parameters in the MSRPDU to a TSpec and generates an ADDTS request to the AP – this case requires the Q-STA to recognize and comprehend MSRPDUs.
The Q-STA parses the MSRPDU before forwarding it to the AP. The Q-STA maps the parameters in the MSRPDU to a TSpec and generates an ADDTS request to the AP – this case requires the Q-STA to recognize and comprehend MSRPDUs.
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

24. Case-1: Q.2.1 MSRP Handling at QAP/Listener
September 2008
doc.: IEEE /1003r0
Aug 2009
Case-1: Q.2.1 MSRP Handling at QAP/Listener
The DMN in the Q-AP receives the MSRPDU . The DMN invokes a primitive at the Q-AP MLME interface (MLME-Reserve). The Q-AP computes available resources and if not enough resource is available, fails the MLME-Reserve invocation. If there are enough resources, the Q-AP issues a “send me an ADDTS” request to the Q-STA (listener).
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

25. Case-1: Q.2.1 MSRP Handling at QAP/Listener
September 2008
doc.: IEEE /1003r0
Aug 2009
Case-1: Q.2.1 MSRP Handling at QAP/Listener
The DMN in the Q-AP receives the MSRPDU . The DMN invokes a primitive at the Q-AP MLME interface (MLME-Reserve). The Q-AP computes available resources and if not enough resource is available, fails the MLME-Reserve invocation. If there are enough resources, the Q-AP issues an autonomous ADDTS Response to the Q-STA (listener).
Ganesh Venkatesan, Intel Corporation
Alex Ashley, NDS Ltd

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

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

28. September 2008
doc.: IEEE /1003r0
Aug 2009
Questions on Table Q-3
Is there an MLME command to query available bandwidth
No.
Is there an 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

29. What is possible with 802.11 (needs work)?
September 2008
November 2007
doc.: IEEE /2752r1
doc.: IEEE /1003r0
Aug 2009
What is possible with (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 29
Ganesh Venkatesan, Intel Corporation
Page 29
Alex Ashley, NDS Ltd
Peter Ecclesine, Cisco Systems

30. 802.11 TSPECs (EDCA-AC) TSPEC Parameter 802.1D Priority-4
Aug 2009
TSPECs (EDCA-AC)
TSPEC Parameter
802.1D Priority-4
802.1D Priority-5
TSINFO
TID 4 5
Direction
Up, Down
Access Policy
10 (EDCA)
ACK Policy
(10/11)No ACK/Block ACK
APSD
Aggregation
Yes
User Priority (802.1D)
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