Part D. Mixing of Specification Versions
vAtlanta r00
1. Mixing of specification versions
This part describes how volumes, and parts within volumes, of different versions and Specification Addenda of the specification may be mixed in Bluetooth implementations. The Core System consists of a BR/EDR Controller Package (see Volume 2), a Low Energy Controller Package (see Volume 6), and a Host Package (see Volume 3).
All parts within a Controller implementation shall comply with the same version of Volume 2, Volume 4 Part E, and Volume 6.
All parts within a Host implementation of Volume 3 shall comply with the same version and, if included, with the same or a higher version of Volume 4 Part E.
The Controller and Host may comply with different versions within a single implementation.
In order to describe how these volumes and parts within volumes can be mixed, one needs to distinguish between four categories of features specified in the different specification versions. The four categories are:
Category | Description |
|---|---|
Type 1 | Feature that exists below HCI and cannot be configured/enabled via HCI |
Type 2 | Feature that exists below HCI and can be configured/enabled via HCI |
Type 3 | Feature that exists below and above HCI and requires HCI command/events to function |
Type 4 | Feature that exists only above HCI |
The outcome of mixing different Core System Packages are derived from the feature definitions in Table 1.1.
If an implementation contains features of type 1 or type 4, these features can function with any combination of Host Package and Controller Package versions with applicable addenda.
If an implementation contains features of type 2, these features can only be used under a default condition if a Host Package of a lower version with applicable addenda is mixed with a Controller Package of this version with applicable Core Specification Addenda (CSAs).
A feature can only be fully used under all conditions if the Host Package and the Controller Package comply with the same or a higher version with applicable CSAs.
If an implementation contains features of type 3, these features can only function if the Host Package supports this version or a higher version with applicable CSAs and if the Controller Package complies with this version or a higher version with applicable CSAs.
1.1. Features and their types
Table 1.2 lists the features, their types, and the version or addendum where the feature was first introduced.
Feature | Version | Type |
|---|---|---|
Basic AFH operation | 1.2 | 1 |
Enhanced inquiry | 1.2 | 1 |
Configuration of AFH (setting channels and enabling/disabling channel assessment) | 1.2 | 2 |
Enhanced synchronization capability | 1.2 | 2 |
Interlaced inquiry scan | 1.2 | 2 |
Interlaced page scan | 1.2 | 2 |
Broadcast encryption | 1.2 | 2 |
Enhanced flow specification and flush timeout | 1.2 | 3 |
Extended SCO links | 1.2 | 3 |
Inquiry Result with RSSI | 1.2 | 3 |
L2CAP flow and error control | 1.2 | 4 |
2 Mb/s EDR | 2.0 + EDR | 2 |
3 Mb/s EDR | 2.0 + EDR | 2 |
3 slot packets in EDR | 2.0 + EDR | 2 |
5 slot packets in EDR | 2.0 + EDR | 2 |
2 Mb/s eSCO | 2.0 + EDR | 2 |
3 Mb/s eSCO | 2.0 + EDR | 2 |
3 slot packets for EDR eSCO | 2.0 + EDR | 2 |
Erroneous Data Reporting | 2.1 + EDR | 3 |
Extended Inquiry Response | 2.1 + EDR | 3 |
Encryption Pause and Resume | 2.1 + EDR | 1 |
Link Supervision Timeout Changed event | 2.1 + EDR | 3 |
Non-Flushable Packet Boundary Flag | 2.1 + EDR | 3 |
Sniff subrating | 2.1 + EDR | 3 |
Secure Simple Pairing | 2.1 + EDR | 3 |
L2CAP Enhanced Retransmission Mode | Addendum 1/3.0 + HS | 4 |
L2CAP Streaming Mode | Addendum 1/3.0 + HS | 4 |
Enhanced Power Control | 3.0 + HS | 1 |
Generic Test Methodology | 3.0 + HS | 3 |
Unicast Connectionless Data | 3.0 + HS | 4 |
Low Energy Controller (PHY and LL) | 4.0 | 3 |
Low Energy Host (L2CAP and Security Manager) | 4.0 | 4 |
Attribute Protocol and Generic Attribute Profile | 4.0 | 4 |
Appearance Data Type | Addendum 2 | 4 |
MWS Coexistence Signaling | Addendum 3 | 2 |
Connectionless Peripheral Broadcast | Addendum 4 | 3 |
Unencrypted UCD | Addendum 4 | 4 |
BR/EDR Secure Connections | 4.1 | 3 |
Train Nudging | 4.1 | 2 |
Generalized Interlaced Scan | 4.1 | 2 |
Piconet Clock Adjustment | 4.1 | 3 |
Low Duty Cycle Directed Advertising | 4.1 | 2 |
32-bit UUID Support in LE | 4.1 | 4 |
LE Dual Mode Topology | 4.1 | 4 |
LE L2CAP Connection-Oriented Channel Support | 4.1 | 4 |
LE Privacy v1.1 | 4.1 | 4 |
LE Link Layer topology | 4.1 | 3 |
LE Ping | 4.1 | 2 |
LE Data Packet Length Extension | 4.2 | 2 |
LE Secure Connections | 4.2 | 4 |
Link Layer privacy | 4.2 | 3 |
Link Layer Extended Filter policies | 4.2 | 3 |
Slot Availability Mask | 5.0 | 2 |
LE 2M PHY | 5.0 | 2 |
LE Coded PHY | 5.0 | 3 |
High Duty Cycle Non-Connectable Advertising | 5.0 | 2 |
LE Advertising Extensions | 5.0 | 3 |
LE Channel Selection Algorithm #2 | 5.0 | 2 |
LE Higher Output Power | Addendum 5 | 1 |
Angle of Arrival/Angle of Departure | 5.1 | 2 |
GATT Caching | 5.1 | 4 |
Periodic Advertising Sync Transfer | 5.1 | 3 |
Control Length Extension | 5.1 | 1 |
Advertising Channel Index | 5.1 | 1 |
HCI support for debug keys in LE Secure Connections | 5.1 | 2 |
Sleep clock accuracy update mechanism | 5.1 | 2 |
ADI field in scan response data | 5.1 | 1 |
Interaction between QoS and Flow Specification | 5.1 | 2 |
Host channel classification for secondary advertising | 5.1 | 2 |
Allow the SID to appear in scan response reports | 5.1 | 1 |
LE Isochronous Channels | 5.2 | 3 |
Enhanced Attribute Protocol | 5.2 | 4 |
LE Power Control | 5.2 | 2 |
Periodic Advertising ADI support | 5.3 | 2 |
Set Min Encryption Key Size command and Encryption Change [v2] event | 5.3 | 2 |
Connection Subrating | 5.3 | 3 |
Channel Classification | 5.3 | 2 |
Advertising Coding Selection | 5.4 | 2 |
Encrypted Advertising Data | 5.4 | 4 |
Periodic Advertising with Responses | 5.4 | 3 |
LE GATT Security Levels Characteristic | 5.4 | 4 |
1.2. Core Specification Addenda
A Core Specification Addendum (CSA) contains one or more parts of a single volume, one or more parts in multiple volumes, changes on one or more parts, or a combination of parts and changes. Addenda are used to supersede a part in a volume or may be used to add a part to a volume according to the rules in Table 1.3.
Note
Note: Each Change may contain changes and/or additions to one or more parts of the specification.
Addendum | Volume and Part or change name | Addition/Changes/Replacement | Allowed Versions & Addenda | Mandatory / Optional / Conditional | Type |
|---|---|---|---|---|---|
1 | Volume 3, Part A | Replacement | 2.0 + EDR, 2.1 + EDR | O | 4 |
2 | Audio Architecture HCI changes | Change | 2.1 + EDR, 3.0 + HS, 4.0 | O | 2 |
Audio Architecture USB changes | Change | 2.1 + EDR, 3.0 + HS, 4.0 | O | 2 | |
LE Limited Discovery Time Changes | Change | 4.0 | C.1 | 4 | |
EIR and AD Data Types in GAP changes | Change | 4.0 | C.1 | 4 | |
EIR and AD Data Types Specification | Addition | 4.0 | C.1 | 4 | |
Volume 5, Part A | Replacement | 3.0 + HS, 4.0 | O | 3 | |
3 | LE Errata | Change | 4.0 with CSA2 | C.2 | Multiple |
GAP Connection Parameters Changes | Change | 4.0 with CSA2 | C.1 | 4 | |
GAP Authentication and Lost Bond Changes | Change | 4.0 with CSA2 | C.1 | 4 | |
Common Profile and Services Error Code Range Changes | Change | 4.0 with CSA2 | C.1 | 4 | |
Private Addressing Changes | Change | 4.0 with CSA2 | C.1 | 4 | |
Dual Mode Addressing Changes | Change | 4.0 with CSA2 | C.3 | 4 | |
MWS Coexistence Logical Signaling Specification | Addition | 2.1 + EDR, 3.0 + HS, 4.0 with CSA2 | O | 2 | |
MWS Coexistence HCI | Addition | 2.1 + EDR, 3.0 + HS, 4.0 with CSA2 | C.4 | 2 | |
Wireless Coexistence Interface 1 (WCI-1) Transport Layer Specification | Addition | 2.1 + EDR, 3.0 + HS, 4.0 with CSA2 | C.4 | 2 | |
Wireless Coexistence Interface 2 (WCI-2) Transport Layer Specification | Addition | 2.1 + EDR, 3.0 + HS, 4.0 with CSA2 | C.4 | 2 | |
4 | Connectionless Peripheral Broadcast | Change | 3.0 + HS, 4.0 with CSA3 | O | 3 |
Unencrypted UCD | Change | 3.0 + HS, 4.0 with CSA3 | O | 4 | |
Fast Advertising Interval | Change | 4.0 with CSA3 | C.1 | 4 | |
eSCO Reserved Slot Clarification | Change | 2.1 + EDR, 3.0 + HS, 4.0 with CSA3 | O | 1 | |
5 | Higher Output Power | Change | 4.0 with CSA3, 4.0 with CSA4, 4.1, 4.2 | O | 1 |
6 | Volume 0, Part B | Replacement | 4.0 with CSA3, 4.0 with CSA4, 4.0 with CSA5, 4.1, 4.1 with CSA5, 4.2, 4.2 with CSA5, 5.0 | M | N/A |
Volume 1, Part A | Change | 4.0 with CSA3, 4.0 with CSA4, 4.0 with CSA5, 4.1, 4.1 with CSA5, 4.2, 4.2 with CSA5, 5.0 | M | N/A |
- C.1:
Mandatory if either the Host Part of the Low Energy Core Configuration or the Host Part of the Basic Rate and Low Energy Combined Core Configuration is supported, otherwise Excluded.
- C.2:
Mandatory if either the Host Part of the Low Energy Core Configuration, Controller Part of the Low Energy Core Configuration, Host Part of the Basic Rate and Low Energy Combined Core Configuration, or Controller Part of the Basic Rate and Low Energy Combined Core Configuration is supported, otherwise Excluded.
- C.3:
Mandatory if the Host Part of the Basic Rate and Low Energy Combined Core Configuration is supported, otherwise Excluded.
- C.4:
Optional if MWS Coexistence Logical Signaling is supported, otherwise Excluded.