1. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 1 Convergence toward an IEEE 802. 22 Standard IEEE P802.22 Wireless RANs Date: 2006-07-19 Authors: Notice: This document has been prepared to assist IEEE 802.22. 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.22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures http://standards.ieee.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 Chairhttp://standards.ieee.org/guides/bylaws/sb-bylaws.pdf Carl R. StevensonCarl R. Stevenson 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.22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at patcom@iee.org.patcom@iee.org >

2. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 2 Convergence toward an IEEE 802. 22 Standard A Proposed Road Map

3. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 3 Acknowledgments As a member of IEEE 802.22, and an incumbent, I am extremely pleased and gratified with the work of the Group and what it accomplished to date I am appreciative of the time and effort the proponents have spend so far in consolidating and refining their proposal I am also mindful of the fact that there is a lot of work that need to be completed to develop a standard

4. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 4 Background IEEE 802.22 Group was created as a result of a proposed FCC Proceeding in November 2004 and the potential for operating in the TV band Incumbents joined the IEEE process because they believe that the IEEE 802.22 process will be based on good science and sound engineering, especially when it comes to protecting incumbents IEEE 802.22 work and standard development, especially when it comes to incumbents protection, is closely tied to the FCC process and decision. Completing the work prior to the FCC decision is crucial to insuring consideration of the IEEE 802.22 work BOTTOM LINE: WE ALL WIN IF THE FCC TAKES INTO ACCOUNT OUR WORK

5. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 5 Legislative Update Telecom Act of 2006 –Senate Activity Proposed Act includes a White Spaces provision. If approved by the Senate, the Bill will direct FCC to complete proceeding in 270 days. Bill will not limit the white space to wideband wireless network –House Activity Proposed Act approved by the House. Bill does not contains a White Spaces provision –Conference Committee If Bill is approved by Senate, a Conference Committee will convene and decide on the White Spaces provision THERE IS A POSSIBILITY THAT THE FCC WILL BE DIRECTED TO COMPLETE THE PROCEEDING IN 270 DAYS

6. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 6 IEEE 802.22 Dilemma If the legislation passes, the IEEE 802.22 activities and timetable will be out of sync with the FCC timetable, and there is a risk that all the work and consensus achieved to date will not be considered or shape the final FCC decision

7. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 7 Proposed Solution IEEE 802.22 need to accelerate, focus and streamline its process to realign its work with the legislative and regulatory reality How? –Step 1: Need to insure what the proposal is complete and meet all the required elements of the RFD –Step 2: Need to update the regulators on the progress of the work –Step 3: Need to complete the work in time

8. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 8 STEP 1: Insure Proposal is Complete –With the help of the proponents, get a tally of whether all the required elements in the FRD have been met by the mandatory elements in the current version of the document (version 0.1). An inventory of optional elements/features is also needed –If the current proposal is incomplete. Proponents need to submit all the missing required elements to complete the document ASAP –The Group should assign the highest priority to complete this task and defer any other activities until this task is completed. Discussion of optional elements/features in the proposal should be suspended until the task is completed

9. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 9 Step 2: Need to Update the Regulators IEEE 802.22 should work toward developing a second update of our activities to the FCC. Its been almost 10 months since we briefed the FCC on our activities. The FCC need to be aware of the progress we made to date, in the event they are contemplating developing rules by the end of 2006 Task the Chairman and/or a small group to work on the mechanics (how and when)

10. doc.: IEEE 802.22-06/0137r0 Submission July 2006 Victor Tawil, MSTVSlide 10 Step 3: Complete the Work in Time –Need to accelerate the Sensing Tiger Team work and focus the effort on simulation and testing rather than paper analysis –Need to create a new non-sensing Tiger Team to work on non-sensing techniques for protecting incumbents. The Team should work in parallel and be tasked with insuring that the proposal/ standard fully develop and/or adequately describe these techniques. This is essential part of our work in the event the regulators decide not to pursue a sensing approach. (Note that NPRM was negative on spectrum sensing option) –Explore the possibility of scheduling an additional interim meeting to complete the work on a baseline version of the standard (version 1.0). The baseline should address all the required elements in the FRD –Need to defer activities on new work or optional features until a baseline version is completed –Work need to be completed ASAP (by end of 2006)