1. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IEEE 802.15rfid Application Considerations] Date Submitted: [May 11, 2009] Source: [René Struik] Company [Certicom Research] Address [5520 Explorer Drive, Fourth Floor, Mississauga, ON, L4W 5L1, Canada] Voice: [+1 (905) 501-6083], FAX: [+1 (905) 507-4230], E-Mail: [rstruik@certicom.com] Re: [IEEEE 802.15rfid - Call for Applications (09/0059r03)] Abstract:[This document suggests consideration of some lifecycle aspects and pleas for enforcing bidirectional communication capabilities for all devices enabled by the IEEE 802.15f effort. ] Purpose:[Promote RFID devices that facilitate ease of use and low lifecycle cost.] Notice:This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

2. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 2 IEEE 802.15.4rfid Application Considerations René Struik (Certicom Research)

3. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 3 IEEE 802.15nan PHY Requirements Alternate PHY amendment –MAC additions only where needed to support PHY License exempt frequency bands –No bands listed explicitly Low data rate: 40 kbps to 1000 kbps Optimal energy efficient link margin given the SUN environmental conditions –Principally outdoors, but also in basements, around corners… PHY frame sizes up to a minimum of 1500 octets Potentially dense deployments: at least 1000 direct neighbors Simultaneous operation for at least 3 co-located orthogonal networks Good coexistence mechanisms (both ways) References: [1] 15-09-0075-01-004g-phy-parameters-for-15-4g.doc [2] 15-08-0705-05-0nan-wnan-par.doc

4. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 4 Why another PHY? Utility sector: Dense deployments – many neighbors in close proximity Rural deployments – neighbors far away Support for IT infrastructure at higher layer (e.g., IP-based) – larger frame sizes Utility sector can live with mains-powered applications: Source: PAR, §5.2: up to 1W in some regulatory regimes These requirements may not be unique for utility sector!

5. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 5 Other applications These requirements may not be unique for utility sector! Examples: Energy sector: oil/gas pipelines (think: pipelines in Nigeria, Alberta, Russia) Mining sector: mine shafts, open mining Environmental monitoring: migration of species, biodiversity studies in tropics Defense/military applications, sabotage-resistant node placement Container handling and dispersed asset control Other: e.g., avoiding repeater by “stretched” communication link. Commonality: not always power source!

6. doc.: IEEE 802.15-09-0398-00-004f Submission May 11, 2009 René Struik (Certicom Research)Slide 6 Ideal IEEE 802.15nan PHY Requirements Alternate PHY amendment –MAC additions only where needed to support PHY License exempt frequency bands –No bands listed explicitly Low data rate: 40 kbps to 1000 kbps Optimal energy efficient link margin given the SUN environmental conditions –Principally outdoors, but also in basements, around corners… PHY frame sizes up to a minimum of 1500 octets Potentially dense deployments: at least 1000 direct neighbors Simultaneous operation for at least 3 co-located orthogonal networks Good coexistence mechanisms (both ways) Wishlist: Add requirements facilitating ubiquitous computing (“internet of things”): Should allow multi-year battery operation with 802.15.4-style duty cycle and same “application topology” Should have range/power consumption trade-off: with 802.15.4-style range, should allow similar power consumption