Document Framework Section

Slides:



Advertisements
Similar presentations
Outdoor Use Case Date: Authors: November 2005 January 2995
Advertisements

LB84 General AdHoc Group Sept. Closing TGn Motions
LB84 General AdHoc Group Sept. Closing TGn Motions
[ Interim Meetings 2006] Date: Authors: July 2005
Document Framework Section
TGn Sync Atlanta Presentation on Confirmation
IEEE White Space Radio Contribution Title
London TGu Motions Authors: January 2007 Date: Month Year
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGu Closing Report Date: Authors: November 2005
March 2014 Election Results
Legacy OFDM Transmission on several Antennas
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Attendance and Documentation for the March 2007 Plenary
Document Framework Section
[ Policies and Procedure Summary]
[ Policies and Procedure Summary]
3GPP liaison report May 2006 May 2006 Date: Authors:
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
3GPP liaison report July 2006
[place presentation subject title text here]
JTC1 Ad Hoc Closing Report
(Presentation name) For (Name of group) (Presenter’s name,title)
TGp Motions Date: Authors: November 2005 Month Year
TGp Closing Report Date: Authors: March 2006 Month Year
TGu-changes-from-d0-02-to-d0-03
TGp Closing Report Date: Authors: May 2007 Month Year
Contribution on Location Privacy
JTC1 Ad Hoc Mid-week Report
TGp Closing Report Date: Authors: March 2006 Month Year
Reflector Tutorial Date: Authors: July 2006 Month Year
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Experimental DTV Sensor
TGu Closing Report Date: Authors: September 2005
ADS Study Group Mid-week Report
Attendance for November 2006
TGu-changes-from-d0-01-to-d0-02
September Opening Report
Number of Encoder as a function of MCS
LB73 Noise and Location Categories
TGy draft 2.0 with changebars from draft 1.0
TGv Redline D1.04-D1.0 Insert and Deletion
TGv Redline D0.10 Insert and Deletion
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Redline of draft P802.11w D2.2 Date: Authors:
TGr Proposed Draft Revision Notice
TGu-changes-from-d0-02-to-d0-03
[ Policies and Procedure Summary]
March Opening Report Date: Authors: March 2011
May 2005 CAPWAP AHC Closing Report
Beamforming and Link Adaptation Motions
Draft P802.11s D1.03 WordConversion
Questions to the Contention-based Protocol (CBP) Study Group
January Opening Report
Motion to go to Letter Ballot
EC Motions – July 2005 Plenary
Outdoor Use Case Date: Authors: November 2005 January 2995
TGu-changes-from-d0-04-to-d0-05
for video transmission, Status
TGu-changes-from-d0-03-to-d0-04
TGu Motions Date: Authors: May 2006 May 2006
WNG SC Closing Report Date: Authors: November 2005
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
TGr Proposed Draft Revision Notice
TGp Motions Date: Authors: January 2006 Month Year
Presentation transcript:

Document Framework Section January 2995 doc.: IEEE 802.11-04/1531r0 September 2005 Date: 2005-09-20 Document Framework Section Authors: Name Company Address Phone email Fahd Pirzada Dell One Dell Way Round Rock, TX 78682 512 338 4400 Fahd_Pirzada@dell.com Pratik Mehta Pratik_Mehta@dell.com Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Fahd Pirzada - Dell Bruce Kraemer, Conexant

September 2005 4.1 Introduction This clause lays the framework for the use of the metrics, environments and methodologies defined in this standard - each of the metrics in the rest of the standard will reference one or more of the usage cases in this clause - each of the usage cases will list the metrics that are relevant to measuring performance of devices and systems when used in these applications - therefore: (a) users reading this section will be able to relate their specific usage cases to the metrics that pertain to their needs (b) users reading the metrics will get a clear understanding of the usage case(s) to which each metric pertains Fahd Pirzada - Dell

September 2005 4.2 Usage cases 4.2.1 General Three principal usage cases are covered by this standard, as follows: a) Data oriented usage case. b) Streaming media usage case. c) Latency sensitive usage case. 4.2.2 Data oriented usage case The data-oriented usage case represents the end-user experience of data-oriented applications in home and corporate environments. These applications do not impose critical requirements of quality of service (bandwidth, latency, jitter) on the network; essentially, the data-oriented traffic is accommodated by traditional best-efforts service. Examples are: web downloads, file transfers, file sharing, e-mail, etc. Typical metrics for this usage case are throughput and range. - table showing relevant metrics (blank for now) Fahd Pirzada - Dell

Usage Cases September 2005 High Low Bandwidth Critical Streaming Media Data Oriented Latency Sensitive Time Critical Fahd Pirzada - Dell

4.2 Use cases September 2005 4.2.3 Streaming media usage case The streaming-media usage case represents the end-user experience of streaming-media applications in a home or corporate environment. Network quality of service requirements for these applications generally include high bandwidth, and latency guarantees. Examples are: real-time audio/video streaming, stored content streaming, multicast high-definition television streaming. Typical metrics for this use case are video quality versus range. - table showing relevant metrics (blank for now) 4.2.4 Latency sensitive usage case The latency-sensitive use case represents the end-user experience of time-critical applications in home and corporate environments. Network quality of service requirements for these applications generally include hard latency guarantees, jitter limits and packet loss thresholds (given that enough bandwidth is available). An example of such an application is Voice over IP (over wireless LAN). Typical metrics for this use case are voice quality versus range. Fahd Pirzada - Dell

September 2005 4.3 General Examples - Placeholder for examples of using metrics for representing specific usage cases (blank for now) Fahd Pirzada - Dell