System Description Document Development Process A Proposal IEEE

System Description Document Development Process – A Proposal IEEE 802. 16 Presentation Submission Template (Rev. 9) Document Number: IEEE C 802. 16 m-07/197 Date Submitted: 2007 -07 -19. Source: Ronny (Yong-Ho) Kim (ronnykim@lge. com), Min-Seok Oh(minoh@lge. com), LG Electronics, Inc. Sang Youb Kim (sangyoub@nortel. com), Mo-Han Fong (mhfong@nortel. com), Nortel Lei Wang (lwang@nextwave. com), Srikanth Gummadi(SGummadi@nextwave. com) Next. Wave Phillip V. Orlik (porlik@merl. com), Mitshubishi Electric Corporation Sunil Vadgama (Sunil. Vadgama@uk. fujitsu. com), Fujitsu Richard Li (richard 929@itri. org. tw) , ITRI Venue: IEEE 802. 16 Session #50 San Francisco, CA Base Contribution: None Purpose: To assist developing system description document (SDD) for 802. 16 m standard 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 >.

Motivation • 16 m has decided to develop SDD • To provide guidance to the 802. 16 members to prepare relevant and timely contributions for the SDD, a process for developing SDD should be outlined. • The following slides outline our proposal

System Description Document • What is SDD? – – – • A system view and architecture for the 802. 16 m air interface SDD helps us develop a coherent, consistent and high quality 16 m Standard and the 16 m amendment document. SDD helps us develop the initial IMT-Advanced proposals based on the architecture and technical concepts adopted SDD overall structure – Define System architecture • Functional Split, Interfaces, Reference model – e. g. , Section 4 Overall architecture (36. 300), • Functional components per layer • What is Functional task, performance task for system? – SDD outline with prioritization : Table of contents of SDD • Describe all essential and relevant technological concepts & how they fit within the overall architecture • all technological items in IMT. TECH and other technological items to meet 802. 16 m requirements. • Prioritization of technological items to facilitate developing functional components – E. g. , multiple access, frame structure, etc – Functional components (PHY, MAC) • Technical components descriptions

System Description Document

Steps for Developing SDD • Outline of SDD (1~2 Sessions) – – Table of Content Define & describe 16 m System Architecture & reference model Define & Describe 16 m Protocol Architecture Define, categorize and prioritize Main functional components • The prioritization would guide the 16 m members to generate relevant and timely contributions • The prioritization can be illustrated in a non-normative annex which would subsequently be removed once the SDD is matured. – Define functional sub-blocks and interconnections for each of the Main functional components. • Develop the Core Sections of SDD (3~4 Sessions) – Based on the prioritized list, define and develop all the necessary functional components, protocols and procedures for 16 m • For example, start with PHY framework, MAC framework and then progress to detail functional subblocks, protocols and procedures. • As one would expect, the Chair would issue call for proposals accordingly. The call may at Chair’s discretion contain prioritized list of topics based on the need and the progress of the SDD. • Evaluation and Approval of SDD (1~2 Sessions) • Finalize SDD draft • Call for Comments on the SDD • Finalization of SDD Note: the above steps may partially overlap

Proposed SDD Development Schedule Start Work Prepare Input to ITU-R workshop