Denver March 2006 doc IEEE 802 15 06

  • Slides: 16
Download presentation
Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Project:

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: SG-BAN opening / closing report Date Submitted: March, 2006 Source: Erik Schylander, Philips Voice: +31 40 273 5585, E-Mail: erik. schylander@philips. com Abstract: Opening / Closing Report for the 15 Study Group BAN session in Denver, USA. Notice: This document has been prepared to assist the IEEE P 802. 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 P 802. 15. Submission 1 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 802.

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 802. 15 - SGB Welcome to Study Group Body Area Networks Submission 2 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Review

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Review IEEE/802 & 802. 15 Policies and Rules • • Study Group: Everyone Votes. All 802 policies apply All 802. 15 policies apply Submissions must meet document format criteria. • All Study Group voting requires 75% consensus. Submission 3 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Objectives

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Objectives for this session • Chair and Secretary for this meeting a. I. • Call for SG-BAN Chair and Secretary position • Review of SG charter • SG process planning • Define Study items • Presentations • Call for Applications and Technology Submission 4 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 BAN

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 BAN Study Group charter • Select officers – – • • • Chair Secretary Write the PAR (Project Description) Write the 5 C (criteria) Ask for the WG approval (of the documents) to be sent to Ex. Com for further approval processing to start a new TG. Submission 5 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 IEEE

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 IEEE 802 Five Criteria 1. BROAD MARKET POTENTIAL a) b) 2. 3. COMPATIBILITY DISTINCT IDENTITY a) b) 4. Substantially different from other 802 Projects One unique solution per problem (not two solutions to a problem) TECHNICAL FEASIBILITY a) b) 5. Broad sets of applicability Multiple vendors, numerous users Demonstrated system feasibility Proven technology, reasonable testing ECONOMIC FEASIBILITY a) b) Submission Known cost factors, reliable data Reasonable cost for performance 6 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 802.

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 802. 15 BAN PAR 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? Submission 7 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 BAN

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 BAN study items • • BAN Scope Market characteristics and requirements Usage scenarios and applications Device classes, Application specific devices and services • BAN topography, technology, channel models and metrics • BAN Scalability, bitrate / throughput, range, Qo. S, power save support • BAN Security requirements and models Submission 8 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Open

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Open Issues 1. SG plan 2. Call for Applications 3. Call for Technology Submission 9 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Presentations

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Presentations 1. "Medical sensor networks: Promising Body Area Network Applications “ – Submission Ryuji Kohno or Kenichi Takizawa 10 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Plans

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Plans for May 2006 meeting Submission 11 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Thank

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Thank You ! Any Questions ? Submission 12 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Project

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Project Authorization Request (PAR) • Use of Nescom Form • 13. Scope of Proposed Project – (See Nes. Com Conventions – Item #6, 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 Nes. Com 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. Submission 13 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria for Standards Development (5 C) 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 802. 1 Architecture, Management, and Interworking documents as follows: • Submission 802. Overview and Architecture, 802. 1 D, 802. 1 Q, and parts of 802. 1 f. 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. 14 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria for Standards Development (5 C) 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. Submission 15 Erik Schylander, Philips

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria

Denver, March 2006 doc. : IEEE 802. 15 -06 -0121 -00 -wng 0 Criteria for Standards Development (5 C) 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. Submission 16 Erik Schylander, Philips