Mesh Topology for Relays IEEE 802.16 Presentation Submission Template (Rev. 9) Document Number: IEEE 802.16n-10/0062 Date Submitted: 2010-12-06 Source: D. J. Shyy MITRE E-mail: djshyy@mitre.org Venue: N/A Base Contribution: Purpose: To be discussed and adopted by TGn 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/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat >. 1

There are two proposals for implementing HR-RS topology within a cell Introduction There are two proposals for implementing HR-RS topology within a cell The topology between an HR-BS and its subordinate HR-RSs within the HR-BS cell is restricted to a tree topology. The topology for HR-RSs within the HR-BS cell can be a tree or mesh

Why are we developing TGn? Scope: This amendment specifies protocol enhancements to the IEEE 802.16 medium access control layer (MAC) for enabling increased robustness and alternate radio path establishment in degraded network conditions Purpose: This amendment addresses higher reliability requirements that are not supported by IEEE Std. 802.16 presently.

Two Approaches for Relay Topology Backwards compatible with 16j and 16m Higher reliability requirements that are not supported by IEEE Std. 802.16 presently Enabling increased robustness and alternate radio path establishment in degraded network conditions Single point of failure Increased Market for 802.16 Tree Yes No Weak MESH Strong

Questions for Tree Topology Proponents A new standard needs to be developed to have Broad Market Potential (the 1st criterion in 5C) Why are we wasting time in developing a new standard if the new standard has no significant difference in reliability as compared to previous 16 standards? We should learn from the history 16j standard was developed, but is there any indication that vendors will implement 16j? If no vendor implements 16j, why 16j was developed at the first place?

Bottom line The Military and Public Safety often require Mesh communications topologies.  If they can’t be efficiently supported in this standard, then those markets will need to look elsewhere (802.11, LTE, etc) for solutions, and WiMAX market share will shrink even further…

Proposed Text for SRD Change Add 6.1.2.4 HR-RS Mesh Topology HR-Network shall support mesh topology among HR-RSs within a cell