1. Submission Title: BAN closing report for San Diego, CA
<month year>
San Diego, July 2006
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: BAN closing report for San Diego, CA
Date Submitted: July 21, 2006
Source: Arthur W. Astrin, Ph. D.
Contact: Arthur W. Astrin, Astrin Radio
Voice: +1 (650) ,
Re: BAN Closing Report for May Session
Abstract: Closing Report for the 15 BAN session in San Diego, CA.
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
Art Astrin
Erik Schylander, Philips

2. BAN study items BAN Scope Market characteristics and requirements
San Diego, July 2006
BAN Scope
Market characteristics and requirements
Usage scenarios and applications
Device classes, application specific devices and services
BAN topology, technology, channel models and metrics
BAN Scalability, bit rate / throughput, range, QoS, power consumption, power saving support
BAN Security, safety requirements and models
Regulatory compliance, spectrum allocation and coexistence
Art Astrin

3. Objectives for this session
San Diego, July 2006
Objectives for this session
Presentations of responses to Call for Technology and Regulatory issues
Kamaya Yazdandoost
Stefan Drude
Huan-Bang Li
Anders Johansson
Ken Takizawa
IG BAN planning 
Art Astrin

4. San Diego, July 2006
Contribution List
Art Astrin

5. How do we distinguish ourselves from other TG / WGs?
San Diego, July 2006
How do we distinguish ourselves from other TG / WGs?
Operates on, inside, or in the vicinity of the body.
Limited range (< .01 – 2 meters)
The channel model will include human body effects. (absorption, health effects)
Extremely low consumption power (.1 to 1 mW) for each device
Capable of energy scavenging / battery-less operation
Support scalable Data Rate: 0.01 – 1,000 kbps (opt 10Mbps)
Support different classes of QoS for high reliability, asymmetric traffic, power constrained.
Needs optimized, low complexity MAC and Networking layer
High number of simultaneously operating piconets required.
Application specific, security/privacy required.
Small form factor for the whole radio, antenna, power supply system
Locating radios (” find me”) mode.
Art Astrin

6. 802.15 IG BAN to SG BAN? New Standard or Extension / Amendment ? Scope
San Diego, July 2006
IG BAN to SG BAN?
DRAFT Project Authorization Request (PAR) for Body Area Networks (BAN)
New Standard or Extension / Amendment ?
Scope
Purpose of proposed project
Intellectual Property
Other standards or projects with a similar scope?
how do we distinguish ourselves from other TGs?
Art Astrin

7. Distinct identity BAN Other 802 standards San Diego, July 2006
Configuration
15.3, 15.4 MAC
single scalable MAC with reliable delivery
Power consumption
Low power consumption
Extremely low power, while communicating, to protect human tissue
Power source
Conventional power source
Possible scavenge operation
Requirements
Low latency
guaranteed response to external stimuli
Frequency band
ISM
Medical authorities approved bands for in and around human body
Channel
Air
Air and in and around human body
Art Astrin

8. San Diego, July 2006
Motion:
IG BAN recommends the formation of an study group to investigate the use of unlicensed and medical authorities approved bands for in and around human body communications.
Moved by: Amjad Soomro
Second by: Ryuji Kohno
Vote 34/0/0, passed unanimously
Art Astrin

9. Call for Technology PHY and MAC Network architecture
San Diego, July 2006
PHY and MAC
Network architecture
BAN topology, technology, channel models and metrics
BAN scalability, bit rate / throughput, range, QoS, power consumption, power saving support
Regulatory compliance, spectrum allocation and coexistence
Art Astrin

10. Call for Regulatory compliance
San Diego, July 2006
Specific for the BAN Scope
Application specific devices and services
BAN Security
BAN safety requirements and models
Regulatory compliance
Art Astrin

11. Presentations of “Call for Technology” responses
San Diego, July 2006
Plans for Sept 2006 meeting
Presentations of “Call for Technology” responses
Presentations of “Call for Regulatory compliance” responses
Continue work on 5Cs and PAR
Art Astrin

12. San Diego, July 2006
Thank You !
Any Questions ?
Art Astrin

13. Welcome to Interest Group Body Area Networks 802.15 – IG BAN
<month year>
San Diego, July 2006
– IG BAN
Welcome to
Interest Group
Body Area Networks
Art Astrin
Erik Schylander, Philips

14. Call for Applications  Call for Technology & Regulatory conditions
San Diego, July 2006
Issues
IG BAN draft plan 
Call for Applications 
Call for Technology & Regulatory conditions
Tutorial sessions (invite medical service organization, a.o.) for July meeting
Art Astrin

15. IEEE 802 Five Criteria BROAD MARKET POTENTIAL COMPATIBILITY
San Diego, July 2006
IEEE 802 Five Criteria
BROAD MARKET POTENTIAL
Broad sets of applicability
Multiple vendors, numerous users
COMPATIBILITY
DISTINCT IDENTITY
Substantially different from other 802 Projects
One unique solution per problem (not two solutions to a problem)
TECHNICAL FEASIBILITY
Demonstrated system feasibility
Proven technology, reasonable testing
ECONOMIC FEASIBILITY
Known cost factors, reliable data
Reasonable cost for performance
Art Astrin

16. BAN Study Group charter
San Diego, July 2006
BAN Study Group charter
Select officers
Write the PAR (Project Description)
Write the 5C (criteria)
Ask for the WG approval (of the documents) to be sent to ExCom for further approval processing to start a new SG.
Art Astrin

17. Call for Applications BAN Scope
San Diego, July 2006
BAN Scope
Market characteristics and requirements
Usage scenarios and applications
Device classes, Application specific devices and services
BAN topography
BAN Scalability, bitrate / throughput, range, QoS, power consumption, power saving support
BAN Security, safety requirements and models
Regulatory compliance, Spectrum allocation and coexistence
Art Astrin

18. "Medical sensor networks: Promising Body Area Network Applications “
San Diego, July 2006
Presentations
"Medical sensor networks: Promising Body Area Network Applications “
Ryuji Kohno or Kenichi Takizawa
Art Astrin

19. IG BAN planning Mar 06 May 06 July 06 Sep 06 Nov 06
San Diego, July 2006
IG BAN planning
Mar 06
Submit Call for Applications 
May 06
Elect chair & secretary 
Presentation of Call responses 
Submit Call for Technology and Regulatory issues 
July 06
Tutorial session (invite medical service organization)
Presentation of Call responses
1st draft PAR & 5C (editors)
Sep 06
2nd draft PAR & 5C
Nov 06
Final draft PAR & 5C
Art Astrin

20. Project Authorization Request (PAR)
San Diego, July 2006
Project Authorization Request (PAR)
Use of Nescom Form
13. Scope of Proposed Project
(See NesCom Conventions – Item #6, Item #16, Item #17)
Briefly detail the projected output including technical boundaries
Is the completion of this document contingent upon the completion of another document?
14. Purpose of Proposed Project
(Briefly, clearly and concisely explain “why” the document is being created
(See NesCom Conventions – Item #16)
15. Reason for the Proposed Project
Give the specific reason for the standardization project. Focus on explaining the problem being addressed, the benefits to be provided and the stakeholders for the project.
Art Astrin

21. Criteria for Standards Development (5C)
San Diego, July 2006
Criteria for Standards Development (5C)
1. Broad Market Potential
A standards project authorized by IEEE 802 shall have a broad market potential. Specifically, it shall have the potential for:
a) Broad sets of applicability.
b) Multiple vendors and numerous users.
c) Balanced costs (LAN versus attached stations).
2. Compatibility
IEEE 802 defines a family of standards. All standards shall be in conformance with the IEEE Architecture, Management, and Interworking documents as follows:
802. Overview and Architecture, 802.1D, 802.1Q, and parts of 802.1f. If any variances in conformance emerge, they shall be thoroughly disclosed and reviewed with 802. Each standard in the IEEE 802 family of standards shall include a definition of managed objects that are compatible with systems management standards.
Art Astrin

22. Criteria for Standards Development (5C)
San Diego, July 2006
Criteria for Standards Development (5C)
3. Distinct Identity
Each IEEE 802 standard shall have a distinct identity. To achieve this, each authorized project shall be:
a) Substantially different from other IEEE 802 standards.
b) One unique solution per problem (not two solutions to a problem).
c) Easy for the document reader to select the relevant specification.
4. Technical Feasibility
For a project to be authorized, it shall be able to show its technical feasibility. At a minimum, the proposed project shall show:
a) Demonstrated system feasibility.
b) Proven technology, reasonable testing.
c) Confidence in reliability.
Art Astrin

23. Criteria for Standards Development (5C)
San Diego, July 2006
Criteria for Standards Development (5C)
5. Economic Feasibility
For a project to be authorized, it shall be able to show economic feasibility (so far as can reasonably be estimated) for its intended applications. At a minimum, the proposed project shall show:
a) Known cost factors, reliable data.
b) Reasonable cost for performance.
c) Consideration of installation costs.
Art Astrin