1 / 21

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [ Bluetooth v1.2 Summary and TG1a Plans ] Date Submitted: [ 15 Sept 03 ] Source: [ Tom Siep ] Company [ TMS Consulting ]

harding-vinson
Télécharger la présentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Bluetooth v1.2 Summary and TG1a 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.1a] Purpose: [Background for creation of 802.15.1a] Notice: This document has been prepared to assist the IEEE P802.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 P802.15. Tom Siep, TMS Consulting

  2. Bluetooth v1.2 Summary and TG1a Plans Tom Siep TMS Consulting 15-03-0394-00-001a Tom Siep, TMS Consulting

  3. Overview • What is happening to v1.1 • Summary of changes v1.1  v1.2 • Timeline for creation of 802.15.1a Tom Siep, TMS Consulting

  4. What is happening to v1.1 • Active investigation of possible enhancements and fixes for Bluetooth Spec for last 1.5 years • Current SIG effort (v1.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 Tom Siep, TMS Consulting

  5. Summary of changes • Migration of 802-15-1-2002 (Bluetooth1.1) to Bluetooth Specification 1.2 (802-15-1revA-2004) • Specifically this includes: • Format Changes • Fixes to the Protocol • New Features • Architectural Overview • Faster Connections • Adaptive Frequency Hopping for improved coexistence • Extended SCO • Absence Masks • Scatternet / Scattermode • L2CAP Flow & Error Control • LMP Improvements / HCI Improvements • Anonymity Mode Tom Siep, TMS Consulting

  6. 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 Tom Siep, TMS Consulting

  7. 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 • 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 Tom Siep, TMS Consulting

  8. 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) • L2CAP CID becomes LLID (Logical Link ID) • Host Controller becomes Controller (Just like .15) • Allows future specification versions to be more architecturally consistent Tom Siep, TMS Consulting

  9. Feature: Architecture Diagram (old) Tom Siep, TMS Consulting

  10. Feature: Architecture Diagram (new) Tom Siep, TMS Consulting

  11. 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 Tom Siep, TMS Consulting

  12. Feature: Faster Connections (cont’d) Tom Siep, TMS Consulting

  13. 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 Tom Siep, TMS Consulting

  14. Feature: Extended SCO (eSCO) • Enhances Synchronous Connection-Oriented [logical transport] • Adds EV3, EV4 and EV5 packet types • EV3 = HV3 + CRC • EV4 = 3 slot HV2 + CRC • EV5 = 3 slot HV3 + CRC • CRC allows retransmissions of corrupted EV packets • Uses separate LTID (AM_ADDR) • Separate LTID implies separate ARQ scheme Tom Siep, TMS Consulting

  15. 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. Tom Siep, TMS Consulting

  16. 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 Tom Siep, TMS Consulting

  17. Feature: L2CAP Flow & Error Control • Segments SDU’s into multiple PDU’s • Each has • Sequence and Acknowledge numbers • Different 16bit CRC to check data integrity • Flow Control bits to control flow and retransmissions per LLID • Two modes • Retransmission Mode • Flow Control Only Tom Siep, TMS Consulting

  18. QoS Clarification / Flow Spec • Harmonizes the difference between L2CAP and HCI definitions of QoS • Allows QoS 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 Tom Siep, TMS Consulting

  19. Feature: LMP / HCI • LMP adds 15 bit op-codes • Adds a 15bit LMP Op-codes to allow more LMP commands to be defined. Clarifies the procedures when an unknown LMP Op-code 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 Tom Siep, TMS Consulting

  20. 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. Tom Siep, TMS Consulting

  21. Timeline for creation of 802.15.1a Tom Siep, TMS Consulting

More Related