雷人的生活

注：每个协议至少实现了那些mandatory requirements。

• Bluetooth End Product:至少含有Radio,BB,LM,L2CAP,SDP,GAP协议实现的产品。

• Bluetooth Host Subsystem Product：只实现了HCI以上至少L2CAP，GAP，SDP协议及一些Profile的产品；

• Bluetooth Controller Subsystem Product：只实现了HCI以下的，有可能还包括AMP协议的产品；

• Bluetooth Profile Subsystem Product：实现了至少1种Profile的所有必须要实现的协议条款。

• Bluetooth Component Product：为配合End Product或者Subsystem Product工作，实现了部分协议的产品；

• Bluetooth Development Tool

• Bluetooth Test Equipment

2. AMP – Alternate MAC/PHYs

Alternate MAC/PHYs (AMP) are secondary Controllers in the Bluetooth core system. The BR/EDR radio, the primary radio, is used to perform discovery, association, connection establishment, and connection maintenance. Once an L2CAP connection has been established between two devices over the BR/ EDR radio, the AMP Managers can discover the AMPs that are available on the other device. When an AMP is ommon between the two devices , the Core system provides mechanisms for moving data traffic from BR/EDR Controller to an AMP Controller.

Each AMP consists of a Protocol Adaptation Layer (PAL) on top of a MAC and PHY. The PAL is responsible for mapping the Bluetooth protocols and behavior (as specified by HCI) to the specific protocols of the underlying MAC and PHY.

L2CAP channels may be created on, or moved to, an AMP. L2CAP channels may also be moved back to the BR/EDR radio when those capabilities are not necessary or when the AMP physical link has a link supervision timeout. A link supervision timeout on the BR/EDR radio forces a disconnection of all AMP physical links between those devices.

AMPs may be enabled or disabled as needed in order to minimize power consumption in the system.

•  Host: A computing device, peripheral, cellular telephone,access point to PSTN network or LAN, etc. A Bluetooth Host attached to a Bluetooth Controller may communicate with other Bluetooth Hosts attached to their Controllers as well.
•  Controller: A collective term referring to all of the layers below HCI.

3.  CORE SYSTEM ARCHITECTURE

The Bluetooth Core system includes a Host, a BR/EDR Controller and zero or more AMP Controllers. A minimal implementation of the Bluetooth BR/EDR core system covers the four lowest layers and associated protocols defined by the Bluetooth specification as well as one common service layer protocol; the Service Discovery Protocol (SDP) and the overall profile requirements are specified in the Generic Access Profile (GAP). The BR/EDR Core system includes support of Alternate MAC/PHYs (AMPs) including an AMP Manager Protocol and Protocol Adaptation Layers (PALs) supporting externally referenced
MAC/PHYs.

• AMP Manager Protocol

The AMP manager is a layer that uses L2CAP to communicate to a peer AMP Manager on a remote device. It also interfaces directly to the AMP PAL for AMP control purposes. The AMP manager is responsible for discovering remote AMP(s) and determining their availability. It collects relevant remote 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).

• AMP HCI
  The AMP HCI is the logical interface between an AMP Controller and Host (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. There is one logical instantiation of an HCI per AMP Controller, and another logical instantiation for the BR/EDR Controller. The physical HCI transport layer manages the multiplexing of several Controllers over the same physical transport
  bus in cases where multiple Controllers exist in a single physical unit.
• AMP PAL
  The AMP PAL is the AMP layer interfacing the AMP MAC with the Host (L2CAP and AMP Manager). It translates commands from the Host into the specific MAC service primitives and primitives into commands, and it translates
  primitives from the AMP MAC into understandable event(s) for the Host. The AMP PAL provides support for AMP channel management, data traffic according to specified flow specifications, and power efficiency. There is not a requirement that the AMP PAL has exclusive access to the AMP itself. Implementers may choose to allow other protocols to be concurrent clients of the AMP. Specific mechanisms for allowing other protocols to share access to the AMP are outside the scope of this specification.
• AMP MAC
  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.
• AMP PHY
  The AMP PHY is the AMP physical layer.

4. PAL (Protocol Adaptation Layer) architecture

PAL architecture