Sept 2003 Sept 03 doc IEEE 802 15

  • Slides: 21
Download presentation
Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Project: IEEE P

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Project: IEEE P 802. 15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Bluetooth v 1. 2 Summary and TG 1 a Plans] Date Submitted: [15 Sept 03] Source: [Tom Siep] Company [TMS Consulting] Address [Suite 100, ms 365, 1802 Pleasant Valley Dr, Garland, TX, USA, 75040] Voice: [+1 972 496 0766], FAX: [+1 469 366 1480], E-Mail: [tom. siep@ieee. org] Re: [Original Document] Abstract: [Description of new Bluetooth Spec version and the work to be done to turn Bluetooth Specification 1. 2 into 802. 15. 1 a] Purpose: [Background for creation of 802. 15. 1 a] 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 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Bluetooth v 1.

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Bluetooth v 1. 2 Summary and TG 1 a Plans Tom Siep TMS Consulting 15 -03 -0394 -00 -001 a Submission 2 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Overview • What

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Overview • What is happening to v 1. 1 • Summary of changes v 1. 1 v 1. 2 • Timeline for creation of 802. 15. 1 a Submission 3 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 What is happening

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 What is happening to v 1. 1 • Active investigation of possible enhancements and fixes for Bluetooth Spec for last 1. 5 years • Current SIG effort (v 1. 2) is a codification of – Fixes – Minor updates – IEEE inputs • Internal SIG approval process in progress – Formal Reviews – Interoperability testing of prototypes • External review by IEEE now commencing Submission 4 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Summary of changes

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Summary of changes • Migration of 802 -15 -1 -2002 (Bluetooth 1. 1) to Bluetooth Specification 1. 2 (802 -15 -1 rev. A-2004) • Specifically this includes: – Format Changes – Fixes to the Protocol – New Features • • • Submission Architectural Overview Faster Connections Adaptive Frequency Hopping for improved coexistence Extended SCO Absence Masks Scatternet / Scattermode L 2 CAP Flow & Error Control LMP Improvements / HCI Improvements Anonymity Mode 5 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Format Changes •

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Format Changes • Type of changes – New volume structure – Cleaner formatting • Genesis of changes – IEEE Section ordering • Draft 6 reorder – rejected at the time • Final 15. 1 Structure – IEEE drawings extended Submission 6 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Fixes to 15.

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Fixes to 15. 1 Protocol • Errata from the SIG and IEEE applied – Many SIG-generated errata entered and resolved – Over 300 errata from IEEE process applied to new Spec • Cleanup of nomenclature • Specification changed to IEEE language – – – Submission Shall => is required to Must => is a natural consequence of Will => it is true that Should => is recommended that May => is permitted to Can => is able to 7 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Overview

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Overview • Describes how Bluetooth fits together – New first section in BT Spec that mirrors 802. 15. 1 – Redefines terms, for example • AM_ADDR becomes LTID (Logical Transport ID) • L 2 CAP CID becomes LLID (Logical Link ID) • Host Controller becomes Controller (Just like. 15) – Allows future specification versions to be more architecturally consistent Submission 8 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Diagram

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Diagram (old) Submission 9 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Diagram

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Architecture Diagram (new) Submission 10 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Faster Connections

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Faster Connections • Faster Inquiry is done by: – Interlaced Scanning on both page trains – Sending FHS packet on first ID packet and then randomly backing off – Reduced MAX_RAND – RSSI in Inquiry Results – Profile Specific DIAC’s • Faster Paging is done by: – Interlaced Scanning on both page trains Submission 11 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Faster Connections

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Faster Connections (cont’d) Submission 12 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Adaptive Frequency

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Adaptive Frequency Hopping • Defines a new hopping kernel which allows an arbitrary set of frequencies to be used – Good channels are still used – Bad channels are mapped onto good channels • Same Channel used for Tx and Rx • Channel Classification can be by Active or Passive means – Specification gives example algorithms – Subset of 802. 15. 2 Submission 13 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Extended SCO

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Extended SCO (e. SCO) • Enhances Synchronous Connection-Oriented [logical transport] • Adds EV 3, EV 4 and EV 5 packet types – EV 3 = HV 3 + CRC – EV 4 = 3 slot HV 2 + CRC – EV 5 = 3 slot HV 3 + CRC • CRC allows retransmissions of corrupted EV packets • Uses separate LTID (AM_ADDR) – Separate LTID implies separate ARQ scheme Submission 14 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Scatternet /

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Scatternet / Scattermode • Scatternet – Relaxes requirements of a slave to allow them to listen to two masters. This is required for Scattermode to be entered into. • Scattermode – Defines periodic packets that shall be sent by the master of a piconet so that slaves can synchronize. These packets contain data flow information so that time listening on one piconet is optimized. Submission 15 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Absence Masks

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Absence Masks • Define a period of time when a device will not be active in a piconet – Only applies to “low priority” traffic like ACL – SCO still works in absences • Used to notify a third device about a commitment with a second device, regardless of roles Submission 16 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: L 2

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: L 2 CAP Flow & Error Control • Segments SDU’s into multiple PDU’s • Each has – Sequence and Acknowledge numbers – Different 16 bit CRC to check data integrity – Flow Control bits to control flow and retransmissions per LLID • Two modes – Retransmission Mode – Flow Control Only Submission 17 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Qo. S Clarification

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Qo. S Clarification / Flow Spec • Harmonizes the difference between L 2 CAP and HCI definitions of Qo. S • Allows Qo. S to be defined in a bidirectional manner • Redefines Flush Timeout as time from when a Data packet enters Controller and not when it is first transmitted – A packet may never be transmitted if Flush Timeout is short and delay is long Submission 18 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: LMP /

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: LMP / HCI • LMP adds 15 bit op-codes – Adds a 15 bit LMP Op-codes to allow more LMP commands to be defined. Clarifies the procedures when an unknown LMP Opcode is received. • HCI Get LMP Handle – Gets LMP SCO Handle for SCO Channels • HCI Read Clock – Reads Local or Remote BT Clock – Returns Clock and Accuracy Submission 19 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Anonymity Mode

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Feature: Anonymity Mode • Private Bluetooth Addresses – BD_ADDR will become private information – Page Scan and Inquiry Scan on a random public BD_ADDR which changes periodically • Pairing done on Public Address – Once link is encrypted, then private addresses can be exchanged • Alias Authentication – Need to authenticate with a network address not a public address. Single alias address for multiple devices. Submission 20 Tom Siep, TMS Consulting

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Timeline for creation

Sept 2003 Sept 03 doc. : IEEE 802. 15 -03/0394 -00 Timeline for creation of 802. 15. 1 a Submission 21 Tom Siep, TMS Consulting