Presentation is loading. Please wait.

Presentation is loading. Please wait.

Interworking with 802.1Qat Stream Reservation Protocol

Similar presentations


Presentation on theme: "Interworking with 802.1Qat Stream Reservation Protocol"— Presentation transcript:

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

2 September 2008 November 2007 doc.: IEEE /2752r1 doc.: IEEE /1003r0 Mar 2010 Abstract This submission is an overview of proposed input from to 802.1Qat Annex-Q Clause Q.3 -- Discussions on the normative text (10/137r0) corresponding to 09/926r7 spawned interest in revisiting the solution proposed and seek a ‘future proof’ alternative, if possible. Note: In the rest of this presentation AP and non-AP STA denote implementations with dot1QatNetworking set to true. Slide 2 Ganesh Venkatesan, Intel Corporation, et al Page 2 Alex Ashley, NDS Ltd Peter Ecclesine, Cisco Systems

3 Handling SRP Reservation Requests
Mar 2010 Handling SRP Reservation Requests Ganesh Venkatesan, Intel Corporation, et al

4 Common Scenarios Mar 2010 Listener(s) Talker DMN DMN AP AP AP
September 2008 doc.: IEEE /1003r0 Mar 2010 Common Scenarios Listener(s) Talker DMN DMN AP AP AP non-AP STA non-AP STA non-AP STA non-AP STA Alternate Data Path Talker Listener(s) Talker Listener(s) Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

5 Advanced Scenario: STA is an Intermediate node or a Talker/Listener
September 2008 doc.: IEEE /1003r0 Mar 2010 Advanced Scenario: STA is an Intermediate node or a Talker/Listener Talker/Listener(s) non-AP STA are intermediate nodes, Talker or Listener Note: This scenario is included for completeness. Support for this requires resolution of the “Station Bridge issue*”. DMN AP non-AP STA non-AP STA Listener(s) Talker Listener(s) * See Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

6 MSPRDU Processing at the AP/DMN (adopted proposal – 10/137r0)
September 2008 doc.: IEEE /1003r0 Mar 2010 MSPRDU Processing at the AP/DMN (adopted proposal – 10/137r0) A non-AP STA can either be Talker/Listener or an intermediate node in the path from the Talker to the Listener. An intermediate node non-AP STA or a non-AP STA that is also the Talker/Listener just pass the MSRPDU to the AP AP forwards the MSRPDU to the AP’s DMN AP’s DMN invokes (DMN/AP interface) Reserve.request or Query.request with parameters corresponding to the received SRP Reservation/Query request If the MSRPDU is a Reservation Request and the AP has sufficient resources: AP’s SME issues a MLME.ADDTS.response to the talker AP’s SME issues a MLME.ADDTS.response to the listener AP responds to the DMN with a Reserve.confirm or Query.confirm Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

7 MSRP Handling at AP/DMN (to Talker/Listener)
September 2008 doc.: IEEE /1003r0 Mar 2010 MSRP Handling at AP/DMN (to Talker/Listener) In 10/137r0 Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

8 Table Q.3 SRP to 802.11 SME QoS Services Mapping
September 2008 doc.: IEEE /1003r0 Mar 2010 Table Q.3 SRP to SME QoS Services Mapping MSRP Attribute MAD Primitive SME QoS Service Description Talker Advertise MAD_Join_Request (new) SME.QUERY Query bandwidth availability without reservation Listener Ready or Listener Ready Failed SME.ADDTS 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 () SME.DELTS Free bandwidth associated with a stream MAD – MRP (Multiple Registration Protocol) Attribute Declaration Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

9 Changes to 802.11 – Summary 802.1Qat
September 2008 doc.: IEEE /1003r0 Mar 2010 Changes to – Summary Ability for APs to send Autonomous ADDTS Response Add ADDTS Response.indication to the STA MLME interface (omission in 10/137r0) To the DMN interface (out of scope for ) Add SME-QUERY.{request|confirm} Add SME-ADDTS.{request|confirm} 802.1Qat Mandate that STAs and APs supporting SRP shall also support EDCA Admission Control The AP and SRP DMN shall co-exist in the same device The SRP DMN shall generate TSPECs as described in document 09/926r7 Mandate that STAs and APs supporting SRP shall encapsulate and de-encapsulate the 802.1q Tag Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

10 Summary of discussions in LA
September 2008 November 2007 doc.: IEEE /2752r1 doc.: IEEE /1003r0 Mar 2010 Summary of discussions in LA Need a discussion on the internals of 802.1Qat as far as SRP goes Scheduled for the joint meeting with 802.1AVB in March, 2010 How does the current proposal (10/137r0) deal with Power Save? How does the current proposal deal with TSPEC, TCLAS and TCLAS processing negotiation? Would the current proposal be able to take advantage of enhancements in ? Should the solution be the same irrespective of if the STA is a Talker/Listener or is just a node in the path from the Talker to the Listener? Slide 10 Ganesh Venkatesan, Intel Corporation, et al Page 10 Alex Ashley, NDS Ltd Peter Ecclesine, Cisco Systems

11 September 2008 doc.: IEEE /1003r0 Mar 2010 Alternate Proposal-A MSRP Handling at AP/DMN (to Talker/Listener) non-AP STA at the Talker/Listener ends parse SRP and invoke corresponding mechanisms Synchronization issues need to be addressed at the AP Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

12 September 2008 doc.: IEEE /1003r0 Mar 2010 Alternate Proposal-A MSRP Handling at AP/DMN (to Talker/Listener) Network-side request for a .1Qat reservation is processed by DMN at AP (omitting .11 reservations) and passed to .1Qat Talker/Listener which requests the SME to complete a .11 ADDTS exchange. The .1Qat Talker/Listener reports the outcome to the DMN at AP No Synchronization issues at the AP Upper layer request for a .1Qat reservation is mapped by .1Qat Talker/Listener to a .11 ADDTS exchange, and if successful, the .1Qat Talker/Listener proceeds with MSRPDU exchanges No Synchronization issues at the AP Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

13 Alternate Proposal-B -- MSRP Handling at AP/DMN (to Talker/Listener)
September 2008 doc.: IEEE /1003r0 Mar 2010 Alternate Proposal-B -- MSRP Handling at AP/DMN (to Talker/Listener) Need a new “Reserve” management frame between AP to STA STA at Talker end does not have to parse SRP messages; no additional processing in No synchronization issues Addresses all issues listed in slide-10 Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

14 What is in the Reserve Request?
Mar 2010 What is in the Reserve Request? TSPEC Element with parameters set to values derived from information in the MSRPDU Optionally TCLAS and TCLAS Processing elements. Ganesh Venkatesan, Intel Corporation, et al

15 The TSPEC Element in Reserve Request
Mar 2010 The TSPEC Element in Reserve Request Element ID Length TS Info Nominal MSDU Size Max MSDU Size Min Service Interval Max Service Interval Inactivity Interval Suspension Interval EDCA-AC 13 55 09/926r7 Slide #20 SRP Tspec MaxFrameSize + 18 n/a HCCA 09/925r7 Slide #22 10 ? Octets 1 3 2 4 Service Start Time Minimum Data Rate Mean Data Rate Peak Data Rate Burst Size Delay Bound Minimum PHY Rate Surplus Bandwidth Allowance Medium Time (SRP Tspec MaxFrameSize +18) * SRP Tspec MaxIntervalFrames 20msecs *(SRP TSpec MaxFrameSize + 18) * SRP TSpec MaxIntervalFrames bits/sec 1.2 (SRP Tspec MaxFrameSize + 18) * SRP Tspec MaxIntervalFrames (SRP Tspec MaxFrameSize + 18) * SRP Tspec MaxIntervalFrames * 10-2 Ganesh Venkatesan, Intel Corporation, et al

16 What is in the Reserve Response?
Mar 2010 What is in the Reserve Response? A Status Code corresponding to the Success/Failure of TSPEC/TCLAS negotiation between the AP and the STA Ganesh Venkatesan, Intel Corporation, et al

17 Proposal 2.a Mar 2010 First ADDTS Response is autonomous
September 2008 doc.: IEEE /1003r0 Mar 2010 Proposal 2.a First ADDTS Response is autonomous ADDTS Request and ADDTS Response have a new IE – MSR Stream ID (64 bits) ADDTS Complete is same as Reserve Response and just has MSR Stream ID and Status IEs in it. Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

18 Proposal 2.b Mar 2010 Reserve Request has a TSPEC element in it.
September 2008 doc.: IEEE /1003r0 Mar 2010 Proposal 2.b Reserve Request has a TSPEC element in it. ADDTS Request and ADDTS Response have a new IE – MSR Stream ID (64 bits) Ganesh Venkatesan, Intel Corporation, et al Alex Ashley, NDS Ltd

19 Mar 2010 Straw Polls Should we stay with just the current solution (Slide-7)? 3/9 Which of the following alternate proposals do you prefer Slide-7 + ADDTS request/response exchange(s) + ADDTS Complete (Slide-13 – (Reserve Request + first ADDTS Req)) (10/2) Slide-13 (9/2) Do you prefer 2.a over 2.b? (9/2) Ganesh Venkatesan, Intel Corporation, et al


Download ppt "Interworking with 802.1Qat Stream Reservation Protocol"

Similar presentations


Ads by Google