May 2011 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comparison of Responses to Task Group 802.15.4j Call for Proposals] Date Submitted: [11 May 2011] Source: [Ray Krasinski] Company [Philips] Address [345 Scarborough Road, Briarcliff Manor, NY, USA] Voice:[1-914-333-9687], E-Mail:[raymond.krasinski@philips.com] Re: Comparison of TG 4j Call for Proposals responses Abstract: An overview of the areas of agreement between responses to the TG4j CFP and areas in need of further discussion. Purpose: To outline the points of agreement and differences between the TG4j CFP responses to help drive discussion of the proposals and help move towards consensus. 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. Ray Krasinski, Philips

Comparison of Responses to 802.15.4j Call for Proposals May 2011 Comparison of Responses to 802.15.4j Call for Proposals Ray Krasinski, Philips

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> May 2011 Content TG4j RFP Response Requirements Areas of Agreement Areas in Need of Further Discussion Ray Krasinski, Philips <author>, <company>

TG 4j Technical Requirements 15-11-0064 <month year> doc.: IEEE 802.15-<doc#> May 2011 TG 4j Technical Requirements 15-11-0064 Compliance with: FCC MBANS Rules Part 95 Subpart M – Medical Body Areas Network Service (device control) Amendments to technical requirements covering transmit frequencies, emissions, transmit powers etc TG4j PAR and 5 Criteria Physical Layer Compliant to the existing 802.15.4 DSSS PHY employing O-QPSK, operating in the 2450 MHz band MAC Layer Only additional MAC requirements to support the Physical Layer: To be defined Ray Krasinski, Philips <author>, <company>

High Level Proposal Comparison <month year> doc.: IEEE 802.15-<doc#> May 2011 High Level Proposal Comparison * The Vinno proposal was presented for informational purposes Ray Krasinski, Philips <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> May 2011 Areas of Agreement Use of 802.15.4 2450MHZ DSSS PHY 5 Mhz channel spacing 16-ary based OQPSK Modulation (Philips, Samsung) 32 I and Q chips for 250kbps (Philips, Samsung) Ray Krasinski, Philips <author>, <company>

Areas in Need of Further Discussion <month year> doc.: IEEE 802.15-<doc#> May 2011 Areas in Need of Further Discussion Attribute Additions to the MAC Forward Error Code Channelization Ray Krasinski, Philips <author>, <company>

Attribute Addition to MAC <month year> doc.: IEEE 802.15-<doc#> May 2011 Attribute Addition to MAC Need for addition of Phy Information Base (PIB) attribute Any further attributes needed for MAC? None identified now, but can be proposed Ray Krasinski, Philips <author>, <company>

doc.: IEEE 802.15-<doc#> <month year> doc.: IEEE 802.15-<doc#> May 2011 Forward Error Code Need for a FEC? There may be a need for a FEC for power management May be beneficial, but tbd Ray Krasinski, Philips <author>, <company>

Channelization Issues <month year> doc.: IEEE 802.15-<doc#> May 2011 Channelization Issues Need for guard bands at top and bottom band edge 0.5 Mhz guard bands at top and bottom band edge Possibility to reduce channel spacing to address Further study required Problem with 20 mW at top band edge Reduced duty cycle can be used to address since average power will then be reduced Not needed within the std Complex vs Simple Channel Plan Tradeoff between the flexibility of a complex plan against the extra cost in terms of scanning for channels by the nodes Need for a default Channel? Default channel location (2390 proposed) Ray Krasinski, Philips <author>, <company>