doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal in Response to Task Group j Call for Proposals] Date Submitted: [6 May 2011] Source: [Dave Evans] Company [Philips] Address [64-68 London Road, Redhill, UK] Voice:[ ], FAX: [Add FAX number], Re: TG4j Call for Proposals document number [If this is a response to a Call for Contributions, cite the name and date of the Call for Contributions to which this document responds, as well as the relevant item number in the Call for Contributions.] [Note: Contributions that are not responsive to this section of the template, and contributions which do not address the topic under which they are submitted, may be refused or consigned to the “General Contributions” area.] Abstract:Proposes that FCC MBANS rules can be met within the implementer defined MBANS application and minimal additional amendments are needed for the 15.4 PHY and MAC layers. Purpose:For consideration by TG4j in response to the Call for Proposals ( ) as a proposal that meets all of the Technical Requirements. Notice:This document has been prepared to assist the IEEE P 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 P

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 2 Proposal in Response to Task Group j Call for Proposals

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 3 Content Objective of this Proposal TG 4j Technical Requirements MBANS Electronic Key - Functionality MBANS Device – Schematic MAC Layer Physical Layer Conclusion

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 4 Objective of this Proposal The objective of this proposal is create an j Amendment that requires minimal or no changes to the MAC and Physical layer specifications Defer all of the requirements to meet the FCC MBANS Rules on device control to the implementer defined MBANS application Only those parameters to enable operation in the MBANS frequency band and the associated FCC MBANS technical requirements need to be specified by j

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 5 TG 4j Technical Requirements 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 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

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 6 MBANS Electronic Key - Functionality MBANS Control Point Single entity in each registered healthcare facility or location MBANS Coordinator Independent frequency coordination organisation. Maintains an electronic database regarding frequency assignments within the MHz band. Coordinator has knowledge of the location of healthcare facilities and frequency usage inputs from AMT sites. Note: MHz is not subject to coordination. MBANS Master Devices Master is responsible for channel selection within the allowed frequency band. Slave devices should cease transmissions within the MHz band when losing connection with the master Unique key, contains frequency information, either with or without specific time limit, automatic or semi automatic key deployment Electronic beacon, contains unique secure verification and frequency information. Defines the part of MHz band that may be used, fully automatic Note: This is not part of the 15.4j proposal, it is provided for information

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 7 MBANS Device - Schematic 15.4 MAC 15.4 PHY MBANS application (includes device control) Electronic Beacon, from MBANS Control Point MAC layer management entity service access point MAC common part sublayer service access point MBANS Master Device Application data Defined by MBANS device implementer Amendments to 15.4 to be defined by TG4j

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 8 MAC Layer MBANS MAC/PHY should provide necessary features to support MBANS device control as required by FCC rules 15.4 already has the necessary MAC data and management service elements for MBANS device control FCC MBANS rules require that a transmitter must employ an unrestricted contention-based protocol The 15.4 MAC already includes features to support such a protocol –Examples: CSMA with non-beacon mode, low duty cycle

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 9 Physical Layer Channelization Plan – Requirements MBANS band is effectively two sub-bands –2360 – 2390 MHz, in-hospital deployment –2390 – 2400 MHz, in-hospital, out-of-hospital and home deployment –In some instances usage of band may be confined to upper 10 MHz only Need to defer to the primary users –AMT, 2360 – 2390 MHz –Amateur, 2390 – 2400 MHz –Their usage is indeterminate For example, AMT usage may change from time to time –MBANS implementers may obtain information on actual AMT usage via the E-key mechanism

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 10 Physical Layer Channelization Plan – Requirements Existing chips constrain us to use channels centered on 1MHz steps –i.e MHz, not MHz Coexistence with –15.6 uses channels centered on 1 MHz steps –Allows two 15.6 channels to exist between 15.4j channels OOB emission limits –A channelization scheme using whole 1 MHz steps gives 0.5 MHz guard bands within the MBANS band –FCC MBANS rules already define 0.5 MHz guard bands outside of the band –Combination of these bands allows the dBm OOB emission limit to be achieved at 1 mW transmit power –Using 20 mW transmit power requires a reduced duty cycle Conclusion –Cannot fit eight 5 MHz channels into the band due to guard bands –A flexible channelization plan is needed to meet all of these requirements

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 11 Physical Layer Channelization Plan 35 overlapping channels defined in PHY with channel step of 1 MHz For in-hospital deployment –Five sets of 7 non-overlapping channels to promote coexistence with AMT For out-of-hospital deployment –Overlapping channels in the 2390–2400 MHz band offer flexibility to avoid interference –Low deployment density & low duty cycle will assist MBANS coexistence AMT spectrumGuard bands15.4j channelsAmateur radio spectrum MHz MHz 2360 MHz2390 MHz2400 MHz 0 (2363)5 (2368)10 (2373)15 (2378)20 (2383)25 (2388)30 (2393) 1 (2364)6(2369)11 (2374)16 (2379)21(2384)26 (2389)31 (2394) 2 (2365)7 (2370)132(2375)17 (2380)22 (2385)27 (2390)32 (2395) 3 (2366)8 (2371)13 (2376)18 (2381)23 (2386)28 (2391)33 (2396) 4 (2367) 9 (2372) 14 (2377)19(2382)24 (2387)29(2392)34 (2397)

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 12 Physical Layer No additional MAC requirements are necessary to support the Physical Layer other than –Phy Information Base (PIB) attribute phyPagesSupported RF exposure compliance –Need to address this with respect to the SAR limits defined in 47 CFR § for portable devices –Particularly applicable to 20 mW transmit power limit in the 2390 – 2400 MHz band –Low duty cycle of usage will assist compliance

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 13 Physical Layer 15.4 is already compliant with the MBANS allowed transmitter emission types and bandwidth Spurious Emissions –FCC § Unwanted Radiation limit is < 500 μV/m at 3m ( dBm) at 0.5 MHz outside MBANS band –Positioning the 1 st channel at 2363 MHz & last at 2397 MHz allows 15.4 using 1 mW transmit power to meet this out of band spurious emission limit at MBANS band edges –Use of 20 mW relies on OOB reduction through duty cycle Adjacent and alternate channel rejection requirements –Same as existing 15.4 requirements

doc.: IEEE j Submission May 2011 Dave Evans, PhilipsSlide 14 Conclusion The requirements of the FCC MBANS device control rules can be met within the MBANS application that is defined by the device implementer FCC MBANS amendments to the technical regulations can be met with this proposal The TG 4j technical requirements can be met with minimal modifications to the existing MAC and PHY layers