1. Document Framework Section
January 2995
doc.: IEEE /1531r0
November 2005
Date:
Document Framework Section
Authors:
Name
Company
Address
Phone
Fahd Pirzada
Dell
One Dell Way
Round Rock, TX 78682
Pratik Mehta
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at
Fahd Pirzada - Dell
Bruce Kraemer, Conexant

2. November 2005
4.1 Introduction
This clause lays the framework for the use of the metrics, environments and methodologies defined in this recommended practice
- each of the metrics in the rest of the recommended practice 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
Objective:
(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

3. November 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 (“bidirectional real-time communications”) usage case.
Fahd Pirzada - Dell

4. Usage Cases November 2005 Streaming Media Usage Case High Bandwidth
Critical
Data Oriented
Usage Case
Latency Sensitive
Usage Case
Low
Low
High
Time Critical
Fahd Pirzada - Dell

5. 4.2 Use cases 4.2.2 Data oriented usage case
November 2005
4.2 Use cases
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 (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, , etc.
Typical metrics for this usage case are throughput and range.
- table showing relevant metrics (blank for now)
Fahd Pirzada - Dell

6. 4.2 Use cases 4.2.3 Streaming media usage case
November 2005
4.2 Use cases
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: 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)
Fahd Pirzada - Dell

7. November 2005
4.2 Use cases
4.2.4 Latency sensitive (“bidirectional real-time communications”) 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).
Example of such an application are Voice over IP (over wireless LAN), netmeeting and gaming.
Typical metrics for this use case are voice quality versus range.
- table showing relevant metrics (blank for now)
Fahd Pirzada - Dell

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