<month year> doc.: IEEE 802.15-<030158r0> July, 2004 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [extension of 802.15.4 for 802.15.4a ranging capability] Date Submitted: [9 July 2004] Source: [Ted Taekyoung Kwon] Company [Seoul National University] Address [School of Computer Engineering, Seoul National University, Seoul, South Korea] Voice:[(82-2) 880 9105], FAX: [(82-2) 872 2045],E-Mail:[tkkwon@snu.ac.kr] Re: [] Abstract: [We propose what kind of arguments should be added to existing 802.15.4 primitives and what variables should be added in MAC protocol entity for ranging capability] Purpose: [to identify what functionality should be added to 802.15.4 for ranging capability] 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. Ted Taekyoung Kwon, Seoul National University <author>, <company>

July, 2004 802.15.4a ranging capability Reporting time or distance measurement Leveraging UWB ranging capability Upper layer can input current position of a node E.g. GPS 2 dimension or 3 dimension MAC peer-to-peer operation to exchange location information New MAC command? or beacon? Ted Taekyoung Kwon, Seoul National University

Ranging report From PHY to MAC layer From MAC to upper layer July, 2004 Ranging report From PHY to MAC layer PD-DATA.indication primitive should add one more argument Elapsed time, Order: Picosecond? From MAC to upper layer MCPS-DATA.indication primitive should add one more argument Elapsed time or distance? Calculating distance may incur unnecessary operations if upper layer is not interested location Confidence level (how much error is implicated in measurements?) Ted Taekyoung Kwon, Seoul National University

July, 2004 Fix position Upper layer may want to input absolute or relative positions to MAC layer Absolute positioning case May reuse MLME-SET.request 2D (longitude, latitude) 3D (longitude, latitude, altitude) May have to consider different coordinate systems? 1D? More variables should be added to MAC layer E.g. macLongitude, macLatitude, macAltitude Ted Taekyoung Kwon, Seoul National University

Fix position (Relative positioning) July, 2004 Fix position (Relative positioning) Many complicated scenarios are possible E.g. who will initiate its position as (0,0)? how positioning can be propagated? Some papers in academia At least we should provide location exchange functionality to upper layers and between MAC entities To upper layer MLME-LOCATION.request/indication/response/confirm primitives Between MAC entities MAC command frames: location request/response Ted Taekyoung Kwon, Seoul National University