802 16 Project Planning Considerations Suggestions IEEE 802

  • Slides: 7
Download presentation
802. 16 Project Planning Considerations & Suggestions IEEE 802. 16 Presentation Submission Template (Rev.

802. 16 Project Planning Considerations & Suggestions IEEE 802. 16 Presentation Submission Template (Rev. 9) Document Number: IEEE C 802. 16 -10/0019 Date Submitted: 2010 -03 -17 Source: Jose Puthenkulam E-mail: jose. p. puthenkulam@intel. com Intel Corporation Venue: Orlando, FL, USA Base Contribution: None Purpose: To motivate the project planning aspects in the 802. 16 WG and provide guidance for PAR creation 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 >.

Outline • • Project Planning Considerations Motivation for Release Planning 802. 16 Standards Evolution

Outline • • Project Planning Considerations Motivation for Release Planning 802. 16 Standards Evolution since 2004 Release Planning Suggestions 12/18/2021 2

Project Planning Considerations • 802. 16 Project Planning based on System Releases tied to

Project Planning Considerations • 802. 16 Project Planning based on System Releases tied to industry needs – Ex: Wi. MAX Forum releases could be tracked for our project planning • Making sure Projects are focused around functionally scoped mostly but also considering major application thrusts • Planning the Sequencing of Projects based on industry needs and member interests 12/18/2021 3

Motivation for Release Planning • Need Standards completion in a predictable manner to serve

Motivation for Release Planning • Need Standards completion in a predictable manner to serve industry better • Need to address industry needs dynamically with appropriately sized projects • Need to build on top of existing functionality better by focused improvements, instead of redesign of some capabilities • Projects with ~1 -2 year cadence will help move the industry faster towards standards implementation • Also need to decide when to re-affirm versus revise the base standard. 12/18/2021 4

IEEE 802. 16 Standard Evolution since 2004 5. 8 GHz , Non-exclusive licensed bands

IEEE 802. 16 Standard Evolution since 2004 5. 8 GHz , Non-exclusive licensed bands (US: FCC 3650 -3700 MHz) 802. 16 -2004 Base Standard Fixed Applications (Licensed/Unlicensed- Non-LOS: < 11 GHz & LOS: 10 -66 GHz) OFDM 256 : Fixed Wi. MAX 802. 16 e Fixed and Mobile Amendment (Licensed : Non-LOS: < 6 GHz) OFDMA (512, 1024): Mobile Wi. MAX 802. 16 /Corrigendum 2 Q 2, 2007 Dec 2005 802. 16 f Fixed MIBs Amendment July 2004 802. 16 h Amendment License Exempt Co-existence Procedures (Unlicensed) 802. 16 j Amendment Mobile Multi-hop Relay 802. 16 i Mobile MIBs Amendment June 2009 ~Q 3 2007 Dec 2005 802. 16 g Fixed and Mobile Management Amendment ~Q 1 2010 Q 4, 2007 802. 16 -2009 Revised Base Standard (Consolidated book of 802. 16 -2004, 802. 16 e, 802. 16 f, 802. 16/Cor 2, 802. 16 g, 802. 16 i) May 2009 IEEE Approved Standards IEEE Draft Standard in Sponsor Ballot Task Group Working Document Task Group Initiated IEEE Draft Standards in WG Ballot Actual schedule Expected schedule 5 12/18/2021 5

802. 16 Release Planning Suggestions System Release Number Base Standard or Revisions Amendments /Corrigenda

802. 16 Release Planning Suggestions System Release Number Base Standard or Revisions Amendments /Corrigenda Title Amendments /Corrigenda Status/Target Major Functionality Release 1 IEEE Std 802. 16 -2004 IEEE 802. 16 f-2005 Amendment Completed Sept 2005 Fixed MIBs IEEE Std 802. 16 -2004 IEEE 802. 16 e-2005 Amendment + Cor 1 -2005 Completed Dec 2005 Combined Fixed and Mobile operation in Licensed Bands IEEE Std 802. 16 -2004 IEEE 802. 16 g-2007 Amendment Completed July 2007 Management Plane Procedures IEEE Std 802. 16 -2009 (2 nd Revision) Release 2 Release 3 FDD Support, CL-MIMO support, MBS and LBS support enhanced IEEE Std 802. 16 -2009 IEEE 802. 16 j-2009 Amendment Completed May 2009 Multi Hop Relay IEEE Std 802. 16 -2009 IEEE P 802. 16 h Amendment Expected Q 1, 2010 License Exempt Co-existence Procedures IEEE Std 802. 16 -2009 IEEE P 802. 16 m Amendment Expected Q 4, 2010 Advanced Air Interface for IMTAdvanced IEEE Std 802. 16 -2009 To be Reaffirmed or Revised IEEE P 802. 16 n Amendment Target 2011/2012 Example: Higher Reliability Networks (GRIDMAN) IEEE Std 802. 16 -2009 To be Reaffirmed or Revised IEEE P 802. 16 p Amendment Target 2011/2012 Example: Machine-to-Machine IEEE Std 802. 16 -2009 To be Reaffirmed or Revised IEEE P 802. 16 q Amendment Target 2012/2013 Example: TBD … …. . Target 2012/2013 Example: TBD New Revised Base Standard IEEE P 802. 16? Amendment Target for 2014/2015 Example: Very High Throughputs ( ~5 Gbps) 12/18/2021 6

Recommendations • We need to recognize industry needs and the competitive landscape to make

Recommendations • We need to recognize industry needs and the competitive landscape to make sure 802. 16 technology evolution remains strong • We need the 802. 16 projects to be focused on new features that build on top of existing functionality • We need to decide whether to revise or reaffirm the base standard (802. 16 -2009) 12/18/2021 7