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.
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)
Ganesh Venkatesan, Intel Corporation

4. 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? If so,
STAs need a “SRP agent” co-located
Figures Q-5, Q-6 and Q-7 need to be updated to show that possibility.
Ganesh Venkatesan, Intel Corporation

5. Aug 2009
Q.2.1 MSRP Handling
In Figure Q-8, MLME TS Request from the DMN to the Q-AP, MLME TS Response to the DMN are not supported in (See Cl a in mb Draft1.0)
Ganesh Venkatesan, Intel Corporation

6. Aug 2009
Q.2.1 MSRP Handling
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

7. Table Q.3 SRP to MLME QoS Services Mapping
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

8. 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.
Ganesh Venkatesan, Intel Corporation

9. 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.
Ganesh Venkatesan, Intel Corporation

10. 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?
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
100Mbps
4000/s (no class-A traffic)
Slide 10
Ganesh Venkatesan, Intel Corporation
Page 10
Alex Ashley, NDS Ltd
Peter Ecclesine, Cisco Systems

11. 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
(Schedule)
(TSInfo
Ack Policy)
User Priority
PSB
Aggregation
Direction
TID
801.D
User Priority Up
Down Bi
1=APSD
0-7 WMM
8-15 HCCA
Access Policy
EDCA, HCCA
Note: Often TID 0-7 = UP
* Reproduced from
Ganesh Venkatesan, Intel Corporation

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

13. 802.11 TSPECs (EDCA-AC) Aug 2009 TSPEC Parameter Value (Class-A)
Value (Class-B)
TSINFO
TID
Direction
APSD
User Priority
4 or 5
Value
Nominal MSDU Size
Maximum MSDU Size
0 (unspecified)
Minimum Service Interval
Maximum Service Interval
Inactivity Interval
Suspension Interval
Service Start Time
Minimum Data Rate
Mean Data Rate
Peak Data Rate
Burst Size
Delay Bound
Minimum PHY Rate
Surplus Bandwidth Allowance
Medium Time
Ganesh Venkatesan, Intel Corporation

14. TSPECs for HCCA (WMM-SA)
Aug 2009
TSPECs for HCCA (WMM-SA)
TSPEC Parameters
SRP Class –A
SRP Class-B
Element ID
Length
TS Info
Nominal MSDU Size
Maximum MSDU Size
Minimum Service Interval
Maximum Service Interval
Inactivity Interval
Minimum Data Rate
Mean Data Rate
Maximum Burst Size
Minimum PHY Rate
Peak Data Rate
Delay Bound
Surplus Bandwidth Allowance
Ganesh Venkatesan, Intel Corporation

15. Table Q-4 Recommend replacing this table with two tables
Aug 2009
Table Q-4
Recommend replacing this table with two tables
EDCA-AC for Class-A and Class-B (do we need one each for IEEE and WFA WMM?)
HCCA for Class-A and Class-B
Ganesh Venkatesan, Intel Corporation

16. References 802.11 QoS Tutorial (08/1214r02) Aug 2009 Slide 16
Ganesh Venkatesan, Intel Corporation