802.16e requirements from n opertor s perspective IEEE 802.16 Presenttion Submission Templte (Rev. 8.3) Document Number: IEEE S802.16e-03/23 Dte Submitted: 2003-03-10 Source: Anthony (Tony) Klinkert Voice: 972-618-6400 WorldCom Fx: 6828 Colonnde Drive E-mil: Info@Klinkert.net Plno, Texs 75024 Venue: IEEE 802.16e Session #24, 2003-03-10 Bse Document: none Purpose: This document provides view from n opertor s perspective on requirements for mobile extension to 802.16. : This document hs been prepred to ssist IEEE 802.16. It is offered s bsis for discussion nd is not binding on the contributing individul(s) or orgniztion(s). The mteril in this document is subject to chnge in form nd content fter further study. The contributor(s) reserve(s) the right to dd, mend or withdrw mteril contined herein. Relese: The contributor grnts free, irrevocble license to the IEEE to incorporte mteril contined in this contribution, nd ny modifictions thereof, in the cretion of n IEEE Stndrds publiction; to copyright in the IEEE s nme ny IEEE Stndrds publiction even though it my include portions of this contribution; nd t the IEEE s sole discretion to permit others to reproduce in whole or in prt the resulting IEEE Stndrds publiction. The contributor lso cknowledges nd ccepts tht this contribution my be mde public by IEEE 802.16. IEEE 802.16 Ptent Policy: The contributor is fmilir with the IEEE 802.16 Ptent Policy nd Procedures <http://ieee802.org/16/ipr/ptents/policy.html>, including the sttement "IEEE stndrds my include the known use of ptent(s), including ptent pplictions, provided the IEEE receives ssurnce from the ptent holder or pplicnt with respect to ptents essentil for complince with both mndtory nd optionl portions of the stndrd." Erly disclosure to the Working Group of ptent informtion tht might be relevnt to the stndrd is essentil to reduce the possibility for delys in the development process nd increse the likelihood tht the drft publiction will be pproved for publiction. Plese notify the Chir <milto:chir@wirelessmn.org> s erly s possible, in written or electronic form, if ptented technology (or technology under ptent ppliction) might be incorported into drft stndrd being developed within the IEEE 802.16 Working Group. The Chir will disclose this notifiction vi the IEEE 802.16 web site <http://ieee802.org/16/ipr/ptents/notices>. 1
802.16e System Requirements Feedbck from n opertor perspective The opinions expressed in this presenttion re solely those of the uthor, nd not those of the WCA nor of WorldCom. Delivered By Tony Klinkert Engineering Committee - Vice Chirmn, WCA Director, Next Genertion Network, WorldCom
Introduction The IEEE sked prticipnts to provide feedbck to the 802.16e tsk group currently ssembling requirements for the extension of 802.16 (fixed point to multipoint) to 802.16e (mobile) brodbnd wireless stndrds. Contined herein re comments on these recommendtions for future collbortion. 3
S1-S3 S1: Operting frequencies: < 6GHz A focus on this segment is stisfctory but this requirement should not limit mnufcture of equipment on the high end (up to 11 GHz) nd the low end (down to 700 MHz). S2: Support of both fixed nd mobile services It is stisfctory to require performnce evlution t 75 km/h (city street speed) And it is stisfctory to require informtive evlution t 150 km/h Note this requirement ddresses interoperbility between fixed (current 16 stndrd) nd mobile (-16e) systems with the cvets of S3. Note further tht given trde-off between speed nd bndwidth, fvor bndwidth (optimizing round brodbnd speeds of 512 Kbps to 2Mbps, not precluding cellulr network speeds down to 128 kbps, but this should not be the focus) S3: Full support of the IEEE 802.16 ir interfce If dditionl flexibility for 16e is necessry to meet the priority requirements (see pge12) we support recommended chnges to 802.16. 4
S4: Chnnel Bndwidths 802.16 Chnnel Bndwidths from 1.25MHz 28 MHz depending upon lloctions It is stisfctory to require chnneliztion between 1.25 nd 28 MHz. Note however tht the MDS/ITFS rules revision project ([Individul compny]mircc), nd the WCA white pper (DA-02-2732A1.doc), submitted to the FCC, who then relesed request for comment (DA 02-2732) nd n NPRM. It is hoped this effort will move through the NPRM soon nd R&O (4Q03-1Q04) on new rules for the bnd, including recommended chnneliztion pln. In light of this, it is recommended the IEEE develop nd evlute chnneliztion nd performnce in lignment, to the extent possible, with this inititive. e.g., 3.5 & 7 MHz in the 3.5 GHz, nd 5 &10 MHz in the mobile bnds It is stisfctory to provide these chnnel spcings for proposl performnce evlution with 5.5 MHz (per the white pper msk) be used t the MMDS bnd. 5
S5-S6 S5: Support for ITU-R mobile QoS clsses: converstionl, streming, interctive, bckground. This requirement is stisfctory provided it supports reltime pplictions (for exmple using RTP), with the bility to provide the pproprite ltency nd priority (for exmple of 802.1p nd 802.1q schemes). S6: Support vehiculr terminls nd bttery operted devices (e.g., lptops, tblets, nd to n extent, PDAs, mobile phones) This requirement is stisfctory. It is suggested tht optimiztion occur round brodbnd pplictions (with rel-time trffic in the 0.5 to 2 Mbps rnge such s video, high fidelity udio nd bndwidth intensive interctive pplictions) versus round store nd forwrd, cellulr-bndwidth-clss pplictions such s voice, messging, personl informtion mnger (PIM), universl messging (UM), etc. 6
S7-S10: Cell nd deployment types S7: Support for indoor pico-cell (trget rdius: 100m) This requirement is supported but notes it is of less priority versus S8 nd S9 (plce priorities on S8 nd S9 over this). S8: Support for outdoor-to-indoor nd pedestrin micro-cell (trget rdius:100m 1000m) This is supported requirement s trget medium rnge but note tht lrger rnge my offer more implementtion flexibility. Notes further this is of lower priority thn S9 (optimize S9 over S8) S9: Support for vehiculr, high BS ntenn mcro-cell (trget rdius: 1 15 km) This is supported requirement but no upper limit on rnge would be better. I.e. rnge is to be constrined by technology nd not by n priori constrint. Trget could be mximum rnge consistent with blnced link budget gted by humn RADHAZ limits 1 or other fctors (size, power, etc.?). Specificlly support for mcro-cell configurtion is importnt, not necessrily vehiculr configurtion. Priority of 1) S9, 2) S8 nd 3) S7 cn be eliminted (equlized or reversed) if bse units hve smll enough footprint (size) with n-over-the-ir bck-hul option (tht elimintes the need to minimize mrket-wide number of cell sites thus minimizing recurring expense of rel-estte fees nd bckhul fees). S10: Support for hierrchicl cell opertion 1 See regultions for power limits nd to blnce the needs of high power nd long rnge, constrined by RADHAZ nd other regultions This requirement is supported regrding hndover, synchroniztion, nd wreness of lyers, for interference mitigtion, etc.. - Bse Sttion Power: FCC reference document is prt 21 section 21.107 for "trnsmit power" pg. 46 - CPE Power: FCC regultion in this re my be subject to chnge bsed on the WCA white pper tht sttes: For CPE devices: Licensee nd equipment mnufctures comport with the restrictions on power contined in Prt 1 nd 2 tht re designed to ssure the protection of humn helth nd sfety. Specificlly, licensees nd mnufctures re subject to the rdition exposure requirements specified in 1.1307(b), 2.1091, nd 2.1093 of the Rules nd mndting tht pplictions for equipment uthoriztion of mobile or portble devices operting contin sttement confirming complince with these requirements for both fundmentl emissions nd unwnted emissions. - RADHAZ for mobiles: FCC CFR, Title 47, prt 2, section 2.1091 for " Rdiofrequency rdition exposure evlution: mobile devices" - RADHAZ for portbles: FCC CFR, title 47, prt 2, section 2.1093 for "Rdiofrequency rdition exposure evlution: portble devices - Environmentl impct: FCC CFR (Code of Federl Regultion), Title 47, prt 1, section 1.1307 for "Actions tht my hve significnt environmentl effect, for which Environmentl Assessments (EAs) must be prepred". 7
Deployment scenrio ssumptions for evlution Scenrio Indoor Outdoor to indoor Outdoor vehiculr Prmeter BS Tx power 27 dbm 36 dbm 46 dbm (0.5 W) (4W) (40 W) SS Tx power 17 dbm 17 dbm 27 dbm BS nt gin 6 dbi 17 dbi 17 dbi SS nt gin 0 dbi 0 dbi 3 dbi BS nt height 15 m 30 m These vlues re supported for power levels, ntenn gins nd ntenn heights for evlution purposes but recommends test points nd overlpping rnges on the power levels to emphsize these re scenrios, but not requirements. Rnges on the third scenrio could indicte test points with with no upside limittion (e.g., on tower height). 8
S11-S12 S11: Support hnd-over between 802.16e BSs nd systems This speker supports fst, mke-before-brek hndover between single opertor systems in phse one implementtion, nd between opertors in phse two deployment scenrio. To the extent possible, in ddition to 802.16e, hndover to other stndrds (prticulrly 802.11) re considered highly desirble in phse two stndrdizing effort. Roming ( slow hndoff ) is essentil, semless mkebefore-brek high speed hndoff is desired. S12: Support for both FDD/TDD duplex modes This speker supports both FDD nd TDD duplex modes. This speker suggest tht for TDD stndrds, mode be vilble (on per chnnel bsis) to synchronize clocks within mrket for co-chnnel interference mitigtion between djcent (in geogrphy) opertors nd systems. 9
S13-S14 S13: Incorporte power svings in ctive nd stndby modes This speker supports the need for bttery operted devices to conserve bttery power, with the focus being on brodbnd pplictions nd devices. S14: Bse Sttion Synchroniztion is permissible This speker supports nd notes tht this requirement my improve self- nd co-chnnel (neighbor opertor) interference, llow high relibility hndoff (hnd-over, hnd-down nd hnd-up), nd robust opertion in the presence of noise. 10
S15-S16 S15: Rnging nd trcking for vehiculr opertion This speker supports this requirement S16: Power control for vehiculr opertion This speker supports the requirement for rnging, trcking nd power control to be dpted to fster chnnel vritions 11
Additionl Requirements Mintin high spectrl efficiency (B/Hz/km^2) MAC pylod frmes cpble of 802.1q & p trnsport (for protocols such s extended Ethernet frmes, nd to support dvnced services requiring MPLS tgs, etc.) 12
Requirement Rnking The rnking shown t right mrked, b or c, is provided s guide to discussions nd optimiztion. There re three clsses denoted:. criticl, b. importnt, nd c. desirble (with no specil definition ttched to these lbels, nd within clss, no rnking or precedence ssigned). Additionl requirements provided by the speker re deemed s criticl (). b b b c c c c Qulittive Rnking S9: Support for vehiculr, high BS ntenn mcro cells S6: Support for vehiculr terminls nd bttery operted devices S5: Support for ITU QoS clsses S2: Support for both fixed nd mobile services S14: Bse sttion synchroniztion is permissible S13: Incorporte power svings in ctive nd stndby modes S12 Support for both FDD nd TDD duplex modes S11 Support for hnd-over between 802.16e bse sttions nd systems S10: Support for hierrchicl cell opertion Deployment scenrio outdoor vehiculr S8: Support for outdoor to indoor nd pedestrin micro cells S4: Chnnel bndwidths from 1.25 to 28 MHz Deployment scenrio outdoor to indoor S7: Support for indoor pico cells <100m rdius S3: Full support for IEEE 802.16 S1: Operting frequencies <6GHz Deployment scenrio indoor 13
Possible dditionl work Continued definition of these requirements; Discussion of higher level requirements to ensure support by these phy/mc level requirements. Continued identifiction of (ny?) more requirements importnt to end users (customer requirements); Continued discussions to rnk nd prioritize requirements fter further definition nd clrifiction; Process to ddress trde-offs of key conflicting requirements. 14
Thnk you! To contct the speker: Info@Klinkert.net Notes: 802.16 802.16 802.16e Meeting Notice, 802.16: Here Meeting Notice: 802 Plenry Meeting 15