1. VTS SG PAR Scope Topics Date: 2007-12-17 Authors: November 2007
doc.: IEEE /2752r1
November 2007
VTS SG PAR Scope Topics
Date:
Authors:
Ganesh Venkatesan, Intel Corporation
Peter Ecclesine, Cisco Systems

2. November 2007
doc.: IEEE /2752r1
November 2007
Abstract
This submission is a high level description of VTS SG PAR Scope topics.
Ganesh Venkatesan, Intel Corporation
Peter Ecclesine, Cisco Systems

3. November 2007
doc.: IEEE /2752r1
November 2007
What is in the PAR Scope?
Interworking with relevant mechanisms including, but not limited to, 802.1Qat, 802.1Qav and 802.1AS
Fine-grained packet discarding
Increased robustness in overlapping BSS environments, based upon enhancing existing mechanisms without the requirement for a centralised management entity.
Modified EDCA timing and parameter selection for video transport
Asynchronous multicast streaming independent of power save modes employed by associated stations.
Broadcast Video
DRM Proximity requirements
802.1 “Wireless Bridge” proposal
Ganesh Venkatesan, Intel Corporation
Peter Ecclesine, Cisco Systems

4. November 2007
Interworking with 802.1
Map 802.1Qat and 802.1Qav into ; 802.1Qat – Stream Reservation Protocol, 802.1Qav – forwarding and Queuing Enhancements for Time-Sensitive Streams
Ganesh Venkatesan, Intel Corporation

5. Fine-grained packet discarding
November 2007
Fine-grained packet discarding
“Fine-grained ARQ and packet drop precedence to enable graceful degradation of video streams when there is insufficient channel capacity for the entire stream”
Goal is to provide mechanism that enables network to make better decisions about which packets to drop when network is congested or channel conditions deteriorate
Video is rather unusual in that it is a mixture of very important data, less critical data and duplicated data.
Analogue TV has a big advantage of a soft roll-off in performance as SNR decreases, whereas digital TV has an all-or-nothing cliff
By being more intelligent with the retransmission policy and packet discard policy, we can provide a graceful roll-off in performance
Ganesh Venkatesan, Intel Corporation

6. Overlapping BSS Issues
November 2007
Overlapping BSS Issues
Provide mechanisms so that a BSS can account for “relevant activities” in overlapping BSSs
Extend Public Action Frame to enable inter-BSS information exchange
Need to address all OBSS scenarios – AP within OBSS, some non-AP STAs within OBSS while AP is not, etc
Ganesh Venkatesan, Intel Corporation

7. November 2007
Modified EDCA
Extend EDCA to accommodate multiple streams and differentiate between them
Packet re-ordering? Send more important data first
Finer priorities within AC_VI
Address cases where performance of a video stream is impacted when changes happen in another video stream – Rx2 moves causing video at Rx1 to be unacceptable
Ganesh Venkatesan, Intel Corporation

8. November 2007
Broadcast Video
How to enable robust broadcast/multicast Video Streams?
Document 07/2954r1 – Video Broadcast/Multicast
Proposed Scope statement: A protocol to enable improved reliability and rate adaptation for broadcast and multicast video traffic.
Can replace “Asynchronous multicast streaming independent of power save modes employed by associated stations.”
Are there other requirements? Mobile Digital TV for handheld devices (DVB-H), Microsoft Broadcast Driver Architecture?
Ganesh Venkatesan, Intel Corporation

9. DRM Proximity Requirements
November 2007
DRM Proximity Requirements
How do you determine that the Content Sink is physically close to the Content Source?
WNG Presentation in Atlanta – doc # r2 “Content Protection Support in ”
Round trip ping is a method used to determine proximity – e.g. Round Trip Ping completes within 7ms.
Explore some of the techniques proposed in document r2.
Comment in the 12/10/07 teleconference – work with a DRM liaison and help address DRM requirements when the link used is (or wireless).
Ganesh Venkatesan, Intel Corporation

10. 802.1 “Wireless Bridge” Proposal
November 2007
802.1 “Wireless Bridge” Proposal
Intention is to use a device as a wired-wireless bridge. A detailed discussion on this is planned for Feb 01, 2008.
Some of the issues discussed in the SF joint meeting – what happens when a wireless device is a part of a wired/wireless network? 4-address frames were proposed as a solution to mitigate some of the issues.
Is this covered by “Interworking with mechanisms” part of the scope?
Comment in the Atlanta joint meeting – wanted an explicit statement in the Scope.
Ganesh Venkatesan, Intel Corporation