1. July 2005
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [TG3c rate-range requirements: looking forward]
Date Submitted: [19 July, 2005]
Source: [Alireza Seyedi] Company [Philips]
Address [345 Scarborough Rd, Briarcliff Manor, NY, 10510]
Voice:[ ], FAX: [ ],
Re: [TG3c Technical Requirements sub-group]
Abstract: [This document provides proposed rate-range requirements that help c standard be competitive.]
Purpose: [Description of proposed rate-range requirements .]
Notice: This document has been prepared to assist the IEEE P 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
Alireza Seyedi, Philips

2. Rate-range requirements: Important factors
<month year>
doc.: IEEE <doc#>
July 2005
Rate-range requirements: Important factors
Compete with other WPAN standards
Use available BW wisely
Address application demand, with respect to product time-line
What are the appropriate values for rate/range requirements?
Alireza Seyedi, Philips
<author>, <company>

3. Rate-range requirements: Important factors
<month year>
doc.: IEEE <doc#>
July 2005
Rate-range requirements: Important factors
We must compete with other WPANs: UWB is cheaper, less power consuming and offers 0.5-1Gbps, and available now!
60GHz products will not come out for a few years:
Demanded rates will go up
Technology improves
Let’s not come back and redo the standardization for higher rate later
Let’s not waste the wide and clean BW we have
Alireza Seyedi, Philips
<author>, <company>

4. Suggestions for rate-range requirements
<month year>
doc.: IEEE <doc#>
July 2005
Suggestions for rate-range requirements
3m is too low. Let us increase it: m
We should specify more than one requirement point: (e.g. x 3m, y 6m, etc)
The lowest rate defines the efficiency of the higher rates. Let us define a minimum rate
10% of the highest required rate
Alireza Seyedi, Philips
<author>, <company>