Bluetooth v3+HS


Published on

presentation about the core architecture of blueooth version 3 or high speed

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Bluetooth v3+HS

  1. 1. Bluetooth V 3.0+HS
  2. 2. What is the Bluetooth? Bluetooth wireless technology is a short-range communications system intended to replace the cable(s) connecting portable and/or fixed electronic devices. <ul><li>The key features of Bluetooth wireless technology are: </li></ul><ul><li>robustness. </li></ul><ul><li>low power. </li></ul><ul><li>low cost . </li></ul><ul><li>Many features of the core specification are optional. </li></ul><ul><li>allowing product differentiation. </li></ul>
  3. 3. Main Features of Bluetooth v 3.0+HS
  4. 4. Bluetooth V 3.O+HS Features Bluetooth 3.0 is the new Bluetooth wireless standard currently in development by the Bluetooth SIG and Wi-Media Alliance. The new standard is reportedly up to 160 times as fast as Bluetooth 2.1, and builds upon the previous standards.
  5. 5. Bluetooth V 3.O+HS Features It is fast: Bluetooth 3.0 will reportedly transfer files at rates of 480 megabits (60 Megabytes) per second in close proximity, and 100 megabits (12.5 Megabytes) per second at 10 meters. High bandwidth mitigates interference : Bluetooth 3.0 will operate in the 6-9 GHz range rather than the current 2.4 GHz range, eliminating the concern of interference from wireless networks and other devices that use the 2.4 GHz range. Backwards compatibility   Best of all, Bluetooth 3.0 will be backwards-compatible, so all of your old devices will be able to communicate with the new ones and vice versa. New devices will feature a 2.4 GHz Bluetooth radio on the same radio chip, or its own separate chip. 
  6. 6. Inside the Bluetooth Specification
  7. 7. Core system architecture Host Host Host BR/EDR Controller BR/EDR Controller AMP Controller BR/EDR Controller AMP Controller AMP Controller The Bluetooth core system consists of a Host and one or more Controllers. A computing device, peripheral, cellular telephone, access point to PSTN network or LAN, etc.
  8. 8. Core system architecture A host is defined as all of the layers below the profiles and above the Host Controller Interface (HCI). A Controller is defined as all of the layers below HCI. Two types of Controllers are defined in this version of the Core Specification: • A Basic Rate / Enhanced Data Rate(BR/EDR) Controller including the Radio, Baseband, Link Manager and optionally HCI. • An Alternate MAC/PHY (AMP) Controller including the AMP PAL (Protocol Adaptation Layer), AMP MAC, Protocol Adaptation Layer (PAL), and optionally HCI.
  9. 9. Version 2.1 artichitecture
  10. 10. Version 3 architecture
  11. 11. The AMP layer interfacing
  12. 12. Host Architectural Blocks <ul><li>Channel manager: </li></ul><ul><li>The channel manager is responsible for creating, managing and destroying </li></ul><ul><li>L2CAP channels for the transport of service protocols and application data </li></ul><ul><li>Streams. </li></ul><ul><li>L2CAP resource manager </li></ul><ul><li>The L2CAP resource manager block is responsible for managing the ordering of submission of PDU fragments to the baseband and some relative scheduling between channels. </li></ul><ul><li>AMP Manager Protocol: </li></ul><ul><li>The AMP manager is responsible for discovering </li></ul><ul><li>remote AMP(s) and determining their availability. It collects relevant remote </li></ul><ul><li>AMP(s) information. This information is used to set up and manage AMP physical links. The AMP manager uses a dedicated L2CAP signaling channel to communicate with remote AMP manager(s). </li></ul>
  13. 13. BR/EDR Controller Architectural Blocks <ul><li>Device Manager: </li></ul><ul><li>The device manager is the functional block in the baseband that controls the general behaviour of the Bluetooth device. It is responsible for all operation of the Bluetooth system that is not directly related to data transport. </li></ul><ul><li>Link Manager: </li></ul><ul><li>The link manager is responsible for the creation, modification and release of logical links (and, if required, their associated logical transports), as well as the update of parameters related to physical links between devices. The link manager achieves this by communicating with the link manager in remote Bluetooth devices using the Link Management Protocol (LMP.) </li></ul><ul><li>Baseband Resource Manager: </li></ul><ul><li>The baseband resource manager is responsible for all access to the radio medium. </li></ul>
  14. 14. BR/EDR Controller Architectural Blocks <ul><li>Link Controller: </li></ul><ul><li>The link controller is responsible for the encoding and decoding of Bluetooth packets from the data payload and parameters related to the physical channel, logical transport and logical link. </li></ul><ul><li>RF: </li></ul><ul><li>The RF block is responsible for transmitting and receiving packets of information </li></ul><ul><li>on the physical channel. </li></ul>
  15. 15. AMP Controller architectural blocks <ul><li>AMP HCI: </li></ul><ul><li>The AMP HCI is the logical interface between an AMP Controller and Host </li></ul><ul><li>(L2CAP and AMP manager). HCI is an optional layer used when the Host and AMP Controller(s) are physically separated. Support for AMPs requires additional HCI commands and events. These new commands and events are related to AMP physical and logical link management, QoS, as well as flow control. </li></ul><ul><li>AMP PAL: </li></ul><ul><li>The AMP PAL is the AMP layer interfacing the AMP MAC with the Host </li></ul><ul><li>(L2CAP and AMP Manager). </li></ul>
  16. 16. <ul><li>AMP MAC: </li></ul><ul><li>The AMP MAC is the MAC layer as defined in the IEEE 802 reference layer model. It provides services such as addressing and mechanisms to control and access channels. The AMP MAC is in between AMP PHY and AMP PAL layers. </li></ul><ul><li>AMP PHY: </li></ul><ul><li>The AMP PHY is the AMP physical layer. </li></ul>AMP Controller architectural blocks
  18. 18. <ul><li>Unframed data traffic: </li></ul><ul><li>If the application does not require delivery of data in frames, possibly because it includes in-stream framing, or because the data is a pure stream, then it may avoid the use of L2CAP channels and make direct use of a baseband logical link. </li></ul><ul><li>Framed data traffic: </li></ul><ul><li>The L2CAP layer services provide a frame-oriented transport for asynchronous and isochronous user data. </li></ul>DATA TRANSPORT ARCHITECTURE
  19. 19. BR/EDR packet structure
  20. 20. PHYSICAL CHANNELS <ul><li>- BR/EDR Physical Channels </li></ul><ul><li>Basic piconet channel : </li></ul><ul><li>The basic piconet channel is used for communication between connected devices during normal operation. </li></ul><ul><li>Adapted piconet channel: </li></ul><ul><li>The adapted piconet channel differs from the basic piconet channel in two </li></ul><ul><li>ways. First the frequencies on which the slaves transmit are the same as the </li></ul><ul><li>preceding master transmit frequency. In other words the frequency is not </li></ul><ul><li>recomputed between master and subsequent slave packets. The second way </li></ul><ul><li>in which the adapted piconet channel differs from the basic piconet channel is </li></ul><ul><li>that the adapted type can be based on fewer than the full 79 frequencies. </li></ul><ul><li>Inquiry scan channel: </li></ul><ul><li>In order for a device to be discovered an inquiry scan channel is used. A discoverable device listens for inquiry requests on its inquiry scan channel and </li></ul><ul><li>then sends responses to these requests. </li></ul>
  21. 21. <ul><li>Page scan channel: </li></ul><ul><li>A connectable device (one that is prepared to accept connections) does so using a page scan channel. </li></ul><ul><li>AMP physical channel: </li></ul><ul><li>An AMP physical channel is used for communication between connected devices during normal operation. It is used in parallel with an adapted piconet channel between the associated BR/EDR Controllers. </li></ul>PHYSICAL CHANNELS cons.
  22. 22. PHYSICAL links A physical link represents a baseband connection between Bluetooth devices. A physical link is always associated with exactly one physical channel (although a physical channel may support more than one physical link.) <ul><li>Active physical link: </li></ul><ul><li>The physical link between a master and a slave device is active if a default ACL logical transport exists between the devices. </li></ul><ul><li>Parked physical link: </li></ul><ul><li>The physical link between a master and a slave device is parked when the slave remains synchronized in the piconet, but has no default ACL logical transport. Such a slave is also said to be parked. </li></ul>
  23. 23. LOGICAL TRANSPORTS <ul><li>BR/EDR Asynchronous connection-oriented (ACL) </li></ul><ul><li>BR/EDR Synchronous Connection-Oriented (SCO) </li></ul><ul><li>BR/EDR Extended Synchronous Connection-Oriented (eSCO) </li></ul><ul><li>BR/EDR Active Slave Broadcast (ASB) </li></ul><ul><li>BR/EDR Parked Slave Broadcast (PSB) </li></ul>
  25. 25. Operation Procedures & modes <ul><li>BR/EDR Procedures: </li></ul><ul><ul><li>Inquiry (Discovering) Procedure: </li></ul></ul><ul><li>Bluetooth devices use the inquiry procedure to discover nearby devices, or to be discovered by devices in their locality . </li></ul><ul><ul><li>Paging (Connecting) Procedure: </li></ul></ul><ul><li>The procedure for forming connections is asymmetrical and requires that one Bluetooth device carries out the page (connection) procedure while the other Bluetooth device is connectable (page scanning.) The procedure is targeted, so that the page procedure is only responded to by one specified Bluetooth device. </li></ul><ul><ul><li>Connected mode: </li></ul></ul><ul><li>After a successful connection procedure over the BR/EDR Controller, the devices are physically connected to each other within a piconet. </li></ul>
  26. 26. Operation Procedures & modes <ul><li>BR/EDR Procedures: </li></ul><ul><ul><li>Hold mode: </li></ul></ul><ul><li>When in this mode, the physical link is only active during slots </li></ul><ul><li>that are reserved for the operation of the synchronous link types SCO and eSCO. All asynchronous links are inactive. </li></ul><ul><ul><li>Sniff mode: </li></ul></ul><ul><li>When in this mode the availability of these logical transports is modified by defining a duty cycle consisting of periods of presence and absence. </li></ul><ul><ul><li>Parked state : </li></ul></ul><ul><li>In this state the device cannot support any logical links to the </li></ul><ul><li>master with the exception of the PSB-C and PSB-U logical links that are used for all communication between the piconet master and the parked slave. </li></ul>
  27. 27. Operation Procedures & modes Role switch procedure : The role switch procedure is a method for swapping the roles of two devices connected in a piconet. Enhanced Data Rate: is a method of extending the capacity and types of Bluetooth packets for the purposes of increasing the maximum throughput, providing better support for multiple connections, and lowering power consumption, while the remainder of the architecture is unchanged.
  28. 28. Operation Procedures & modes <ul><li>AMP Procedures : </li></ul><ul><ul><li>AMP Discovery Procedures : </li></ul></ul><ul><li>The AMP Manager is responsible for discovering local AMP Controller(s) and maintaining that list over time as AMPs may be added or removed dynamically from the system . </li></ul><ul><ul><li>Physical Link Creation Procedure: </li></ul></ul><ul><li>Collects the necessary information about the remote AMP(s) to set up a physical link in an optimal way and then initiates the physical link creation. </li></ul><ul><ul><li>Logical Link Creation Procedure : </li></ul></ul><ul><li>Once a physical link exists, L2CAP creates an AMP logical link with the desired QoS. An L2CAP channel is then created over the logical link, at which point the channel is ready for data communications. </li></ul>
  29. 29. CHANGES FROM V2.1 TO V3.0 + HS Several new features are introduced in Bluetooth Core Specification v3.0 + HS. The major areas of improvement are: • AMP Manager Protocol (A2MP) • Enhancements to L2CAP including • Enhanced Retransmission Mode and Streaming Mode • Improvements to the L2CAP state machine for AMP channels • Fixed channel support • Enhancements to HCI for AMP • Enhancements to Security for AMP • 802.11 Protocol Adaptation Layer • Enhanced Power Control • Unicast Connectionless Data • HCI Read Encryption Key Size command • Generic Test Methodology for AMP • Enhanced USB and SDIO HCI Transports
  30. 30. تم بحمد الله