1. September 2011
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: [12 September 2011]
Source: [Dave Evans1, Liang Li2, Anuj Batra3, Ariton Xhafa3, Okundu Omeni4, Khurram Waheed5] Companies [Philips1, Vinno Technologies Inc.2, TI3, Toumaz4, Freescale 5]
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 with minimal additional amendments for the 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
Dave Evans, Philips

2. Proposal in Response to Task Group 802.15.4j Call for Proposals
September 2011
Proposal in Response to Task Group j Call for Proposals
Philips, Vinno Technologies Inc., Texas Instruments, Toumaz, Freescale
Dave Evans, Philips

3. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2011
Content
Objective of this Proposal
TG4j Technical Requirements
MAC Layer
Physical Layer
Conclusion
Dave Evans, Philips
<author>, <company>

4. Objective of this Proposal
<month year>
doc.: IEEE <doc#>
September 2011
Objective of this Proposal
The objective of this proposal is to create an j Amendment that requires minimal or no changes to the MAC and Physical layer specifications
Only those parameters to enable operation in the MBANS frequency band and the associated FCC MBANS technical requirements need to be specified by j
Dave Evans, Philips
<author>, <company>

5. TG4j Technical Requirements 15-11-0064
<month year>
doc.: IEEE <doc#>
September 2011
TG4j Technical Requirements
Compliance with:
FCC MBANS Draft 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
Dave Evans, Philips
<author>, <company>

6. MBANS Electronic Key - Functionality
<month year>
doc.: IEEE <doc#>
September 2011
MBANS Electronic Key - Functionality
Unique key, contain frequency information, either with or without specific time limit, automatic or semi automatic key deployment
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.
Electronic beacon, contains unique secure verification and frequency information.
Defines the part of MHz band that may be used, fully automatic
MBANS Control Point
Single entity in each registered healthcare facility or location
MBANS Master Devices
Master is responsible for channel selection within the allowed frequency band. Node devices should cease transmissions within the MHz band when losing connection with master
Note: This is not part of the 15.4j proposal, it is provided for information
Dave Evans, Philips
<author>, <company>

7. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2011
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
Dave Evans, Philips
<author>, <company>

8. Physical Layer Channelization Plan – Requirements
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer Channelization Plan – Requirements
MBANS band is effectively two sub-bands
2360–2390 MHz, in-hospital deployment subject to coordination
2390–2400 MHz, in-hospital, out-of-hospital and home deployment
In some instances usage of the band may be confined to the 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
Healthcare facilities must obtain information on coordinated MHz spectrum MBANS spectrum via the E-key mechanism
Dave Evans, Philips
<author>, <company>

9. Physical Layer Channelization Plan – Requirements
<month year>
doc.: IEEE <doc#>
September 2011
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 (same as above)
Allows two 15.6 channels to exist between 15.4j channels
Dave Evans, Philips
<author>, <company>

10. Physical Layer Channelization Plan – Requirements
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer Channelization Plan – Requirements
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 MBANS band
Combination of these bands allows the dBm OOB emission limit to be achieved at 1 mW transmit power
Using 20 mW transmit power near the upper sub-band edge (2400 MHz) 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
Dave Evans, Philips
<author>, <company>

11. Physical Layer Channelization Plan
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer Channelization Plan
AMT spectrum
Guard bands
15.4j channels
Amateur radio spectrum
2360.5
2360 MHz
2400
MHz
2390 MHz
2400 MHz
0 (2363)
1 (2368)
2 (2373)
3 (2378)
4 (2383)
5 (2388)
6 (2393)
14 (2395)
7 (2367)
8(2372)
9 (2377)
10 (2382)
11 (2387)
12 (2392)
13 (2397)
For in-hospital deployment
14 channels defined to promote coexistence with AMT
Non-overlapping channels will be used in MHz band
For out-of-hospital deployment
Overlapping channels in 2390–2400 MHz band offers flexibility to avoid interference
Low deployment density and low duty cycle will assist MBANS coexistence
Dave Evans, Philips
<author>, <company>

12. Physical Layer Channelization Plan
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer Channelization Plan
Points to note:
An implementer must obtain information on set of channels to use via the E-key and beacon mechanisms
Consequently hub devices will mostly likely use a set of channels that are the best fit around the primary users
Only non-overlapping channels will be used in MHz band
The chosen set of channels may apply to the whole of a medical facility and all hub devices will use these channels at any one time
15.4j has a total of 15 channels whereas 15.4 has 16
Dave Evans, Philips
<author>, <company>

13. Physical Layer Channelization Plan
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer Channelization Plan
New channel page 9 for the MBANS band
Channel numbering:
Fc = k in MHz, for k = 0, 1, …, 6
Fc = (k – 7) in MHz, for k = 7, 8, …,13
Fc = 2395 in MHz, for k = 14
Dave Evans, Philips
<author>, <company>

14. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2011
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
This is particularly applicable to the 20 mW transmit power limit in the 2390–2400 MHz band
Low duty cycle of usage in this sub-band will assist compliance
Dave Evans, Philips
<author>, <company>

15. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2011
Physical Layer
15.4 is already compliant with the allowed MBANS transmitter emission types and bandwidth
Spurious Emissions
FCC § Unwanted Radiation limit is < 500 μV/m at 3m (equivalent to dBm) at 0.5 MHz outside MBANS band
Positioning the 1st channel at 2363 MHz and the last at 2397 MHz allows 15.4j to use 1 mW transmit power whilst meeting this out of band spurious emission limit
Use of 20 mW requires a reduced duty cycle to meet the limit
Adjacent and alternate channel rejection requirements
Same as the existing 15.4 requirements
Dave Evans, Philips
<author>, <company>

16. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
September 2011
Conclusion
A flexible channel plan is proposed to make the best use the MBANS band given the need to assist primary user coexistence and to meet the OOB emission limits
This proposal meets the FCC MBANS Part 95 Rules and the amendments to the technical regulations
The TG4j technical requirements can be met with minimal modifications to the existing MAC and PHY layers
Dave Evans, Philips
<author>, <company>