TGm Work Plan Adhoc Report IEEE 802 16

TGm Work Plan Adhoc Report IEEE 802. 16 Presentation Submission Template (Rev. 9) Document Number: IEEE C 802. 16 m-09/0747 r 2 Date Submitted: 2009 -03 -10 Source: Jose Puthenkulam Intel Corporation (Chair TGm Work Plan Adhoc) Voice: E-mail: +1 -5032646121 jose. p. puthenkulam@intel. com Venue: Vancouver, BC, Canada Base Contribution: IEEE 802. 16 m Work Plan document (IEEE 802. 16 m-07/001 r 2) Purpose: For discussion and adoption of specific updates to the IEEE 802. 16 m work plan Notice: This document does not represent the agreed views of the IEEE 802. 16 Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who 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. 16. Patent Policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http: //standards. ieee. org/guides/bylaws/sect 6 -7. html#6> and <http: //standards. ieee. org/guides/opman/sect 6. html#6. 3>. Further information is located at <http: //standards. ieee. org/board/pat-material. html> and <http: //standards. ieee. org/board/pat >.

TGm Work Plan Adhoc Agenda • • • 3/10/2009 Opening Review and Approve Agenda Discuss input contributions (741, 744 r 1) Discuss Recommendations to TGm for Work Plan updates Summary Report Review 2

TGm Work Plan Adhoc Discussion Summary • Discussed Contribution 741: Proposed timeline updates and need for staging process • Discussed Contribution 744 r 1: Proposed a staging process for Features beyond the IMT-Advanced requirements • We developed some recommendations and a specific set of updates to the TGm Work Plan: – – – Recommendations to TGm (Slide 4) Process for staging of the feature development using RGs (Slide 5) Feature RG process (Slide 6) Suggestions for features RGs (Slide 7) Proposed timeline updates to the work plan (Slide 8) • We suggest some TGm Actions • Reviewed this report : That was accepted without objection 3/10/2009 3

Recommendations to TGm • Prioritize features in the 802. 16 m Amendment without compromising the overall completion by May 2010 • Use Feature Rapporteur Groups (RG) for staging work beyond the IMT-Advanced requirements in developing the 802. 16 m Amendment 3/10/2009 4

Proposed Process for staging 802. 16 m Amendment feature PHY/MAC development features required for IMTAdvanced for a working system AWD Feature inclusion vote 50% Feature 1 RG Feature 2 RG Feature N+1 50% WG LB 75% SB 75% Amendment Feature development: -Feature developed as a RG contribution to TGm -Finally included only as a complete proposal, not a partial one -Develop as a self contained clause/subclause unless it is essential -Do not put place holders in Amendment till the feature is ready. (SDD will still have all features) -RGs should track Amendment development for consistency -WG LB or SB recirculation scope should allow feature inclusion Feature WG Letter Ballot Next Project (New PAR) RG AWD = Amendment Working Doc 3/10/2009 P 802. 16 m draft RG = Rapporteur Group LB = Letter Ballot SB= Sponsor Ballot 5

Feature RG process for the Amendment • Feature Rapporteur Groups (RG) will develop contributions for adoption by TGm as per Process (in previous slide) • RGs will be authorized/re-authorized at each TGm session • TGm will provide final deadlines for completion of RG work. • RG must start with a work plan based on TGm final deadlines. • RGs must report progress at every TGm session • RG final output contribution must be complete by TGm deadlines for adoption into the AWD/Draft • RGs may meet during TGm sessions • RGs can arrange teleconferences with 7 day advance notice • RGs conduct straw polls for decision making • RGs are open to all participants 3/10/2009 6

Recommendations for potential feature RGs SDD Chapter Features Essential for IMTAdv. at Amendment level detail When to start RG 12 Inter-Radio Access Technology Functions No 13 LBS No 14 E-MBS No 15 Relay No 16 Co-deployment and Co-existence No 17 Femtocell No 18 Self organizing networks No 19 Multi-carrier Yes NA (40 MHz BW support. Not all aspects) 20 Interference Mitigation No 22 Inter-ABS Synchronization No When RG should finish NA In addition to chapters 12 -20, 22 TGm should review specific technical topics that are not required for IMT-Adv. That could be assigned to feature RGs to expedite development of the standard. 3/10/2009 7

2008 -07 -17 Proposed Updates to TGm Timelines Q 2 IEEE 802. 16 System Requirements Evaluation Methodology System Description IMT Advanced Proposal 2007 Q 3 Q 4 Q 1 2008 Q 2 Q 3 ITU-R IMT Advanced Circular Letter Q 1 Q 2 2009 Q 3 Q 4 Q 1 Q 4 Sep ’ 07* Jan’ 08* Amendment Ready for IMT-Adv evaluation Nov ’ 07 Jan 09* ITU based Updates Jan ’ 09 Sept ’ 09* Final Proposal Nov ’ 08 May ’ 09 Working Doc Refinements Nov ’ 09 Letter Ballot May ’ 10 Sponsor Ballot Jun ’ 08 ITU based Updates Oct ’ 08 IMT. EVAL Jan’ 09 Oct ’ 09 Proposal Submission IMT. RADIO ITU-R WP 5 D 2010 Q 2 Q 3 Apr May. Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May. Jun Jul Aug Sep Oct Nov. Dec Jan Feb Mar Apr May. Jun Jul Aug. Sep Oct Nov Dec 802. 16 m AmendmentŦ IMT. TECH Q 4 Jun ’ 10 Proposal Evaluation & Consensus Building Develop Recommendation Apr May. Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May. Jun Jul Aug Sep Oct Nov Dec *System Requirements and Evaluation Methodology, System Description, IMT-Advanced Proposal Documents may be further updated based on ITU output (shown by dotted lines). 3/10/2009 Ŧ 802. 16 m amendment is dependent on the 802. 16 Rev 2 Project completion 3 8

Suggested TGm Actions • Adopt into the TGm Work plan: 1. The “Proposed Process for staging 802. 16 m Amendment feature development” (slide 5) and “Feature RG process for the Amendment” (slide 6)” 2. The “Proposed Updates to TGm Timelines (slide 8)” • 3/10/2009 Consider creating RGs for some of the features suggested (in slide 7) 9

Motion to TGm • Motion: To adopt updates to the TGm Workplan provided in contribution “C 80216 m 09/0747 r 2” Moved: Second: 3/10/2009 10

TGm Work Plan Adhoc Attendees • • • • • 3/10/2009 Jose Puthenkulam, Intel Hokyu Choi, Samsung Dan Gal, Alcatel-Lucent Wooram Shin, ETRI Mark Cudak, Motorola Mike Hart, UK Broadband Rob Glassford, BT John Humbert, Sprint Chris Seagren, Sprint Hassan Yaghoobi, Intel Masoud Olfat, Clearwire Jin Sam Kwak, LGE Min-seok Oh, LGE Satoshi Imata, KDDI R&D Jim Mollenauer, Technology Strategy Associates Yousuf Saifullah, Nokia-Siemens Networks Prakash Bhat, Vodafone Shawn Taylor, Huawei Jianmin Lu, Huawei Roger Marks, Wi. MAX Forum 11