Supplement To The Bluetooth Core Specification

Download as pdf or txt
Download as pdf or txt
You are on page 1of 37

Supplement to the

Bluetooth Core Specification


Bluetooth® Specification

▪ Revision: v9
▪ Revision Date: 2019-12-31
▪ Group Prepared By: Core Specification Working Group
▪ Feedback Email: core-main@bluetooth.org

Abstract:
This supplement contains information related to data types, common Profile and Service error
codes, and enumerates the services permitted to use Security Mode 4 Level 0.

Bluetooth SIG Proprietary


Supplement to Bluetooth Core Specification | CSS v9 page 2

Disclaimer and Copyright Notice


Use of this specification is your acknowledgement that you agree to and will comply with the
following notices and disclaimers. You are advised to seek appropriate legal, engineering, and
other professional advice regarding the use, interpretation, and effect of this specification.
Use of Bluetooth specifications by members of Bluetooth SIG is governed by the membership
and other related agreements between Bluetooth SIG and its members, including those
agreements posted on Bluetooth SIG’s website located at www.bluetooth.com. Any use of this
specification by a member that is not in compliance with the applicable membership and other
related agreements is prohibited and, among other things, may result in (i) termination of the
applicable agreements and (ii) liability for infringement of the intellectual property rights of
Bluetooth SIG and its members.
Use of this specification by anyone who is not a member of Bluetooth SIG is prohibited and is
an infringement of the intellectual property rights of Bluetooth SIG and its members. The
furnishing of this specification does not grant any license to any intellectual property of
Bluetooth SIG or its members. THIS SPECIFICATION IS PROVIDED “AS IS” AND
BLUETOOTH SIG, ITS MEMBERS AND THEIR AFFILIATES MAKE NO REPRESENTATIONS
OR WARRANTIES AND DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING ANY WARRANTIES OF MERCHANTABILITY, TITLE, NON-INFRINGEMENT,
FITNESS FOR ANY PARTICULAR PURPOSE, OR THAT THE CONTENT OF THIS
SPECIFICATION IS FREE OF ERRORS. For the avoidance of doubt, Bluetooth SIG has not
made any search or investigation as to third parties that may claim rights in or to any
specifications or any intellectual property that may be required to implement any specifications
and it disclaims any obligation or duty to do so.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BLUETOOTH SIG, ITS
MEMBERS AND THEIR AFFILIATES DISCLAIM ALL LIABILITY ARISING OUT OF OR
RELATING TO USE OF THIS SPECIFICATION AND ANY INFORMATION CONTAINED IN
THIS SPECIFICATION, INCLUDING LOST REVENUE, PROFITS, DATA OR PROGRAMS,
OR BUSINESS INTERRUPTION, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL,
INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE
THEORY OF LIABILITY, AND EVEN IF BLUETOOTH SIG, ITS MEMBERS OR THEIR
AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY OF THE DAMAGES.
Products equipped with Bluetooth wireless technology ("Bluetooth Products") and their
combination, operation, use, implementation, and distribution may be subject to regulatory
controls under the laws and regulations of numerous countries that regulate products that use
wireless non-licensed spectrum. Examples include airline regulations, telecommunications
regulations, technology transfer controls and health and safety regulations. You are solely
responsible for complying with all applicable laws and regulations and for obtaining any and all
required authorizations, permits, or licenses in connection with your use of this specification
and development, manufacture, and distribution of Bluetooth Products. Nothing in this
specification provides any information or assistance in connection with complying with
applicable laws or regulations or obtaining required authorizations, permits, or licenses.
Bluetooth SIG is not required to adopt any specification or portion thereof. If this specification is
not the final version adopted by Bluetooth SIG’s Board of Directors, it may not be adopted. Any
specification adopted by Bluetooth SIG’s Board of Directors may be withdrawn, replaced, or
modified at any time. Bluetooth SIG reserves the right to change or alter final specifications in
accordance with its membership and operating agreements.
Copyright © 2011–2019. All copyrights in the Bluetooth Specifications themselves are owned by
Apple Inc., Ericsson AB, Intel Corporation, Lenovo (Singapore) Pte. Ltd., Microsoft Corporation,
Nokia Corporation, and Toshiba Corporation. The Bluetooth word mark and logos are owned by
Bluetooth SIG, Inc. Other third-party brands and names are the property of their respective
owners.

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9 page 3

TABLE OF CONTENTS

Part A
DATA TYPES SPECIFICATION
1 Data Types definitions and formats ................................................... 9
1.1 Service UUID ............................................................................. 10
1.1.1 Description .................................................................... 10
1.1.2 Format........................................................................... 11
1.2 Local name ................................................................................ 11
1.2.1 Description .................................................................... 11
1.2.2 Format .......................................................................... 11
1.3 Flags .......................................................................................... 12
1.3.1 Description .................................................................... 12
1.3.2 Format........................................................................... 12
1.4 Manufacturer Specific Data ....................................................... 13
1.4.1 Description .................................................................... 13
1.4.2 Format........................................................................... 13
1.5 TX Power Level ......................................................................... 13
1.5.1 Description .................................................................... 13
1.5.2 Format........................................................................... 14
1.6 Secure Simple Pairing Out of Band (OOB)................................ 14
1.6.1 Description .................................................................... 14
1.6.2 Format........................................................................... 14
1.7 Security Manager Out of Band (OOB) ....................................... 15
1.7.1 Description .................................................................... 15
1.7.2 Format........................................................................... 15
1.8 Security Manager TK Value ....................................................... 16
1.8.1 Description .................................................................... 16
1.8.2 Format........................................................................... 16
1.9 Slave Connection Interval Range .............................................. 16
1.9.1 Description .................................................................... 16
1.9.2 Format........................................................................... 17
1.10 Service Solicitation .................................................................... 17
1.10.1 Description .................................................................... 17
1.10.2 Format........................................................................... 17
1.11 Service Data .............................................................................. 18
1.11.1 Description .................................................................... 18
1.11.2 Format........................................................................... 18
1.12 Appearance ............................................................................... 18

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9 page 4

1.12.1 Description .................................................................... 18


1.12.2 Format........................................................................... 18
1.13 Public Target Address ................................................................ 19
1.13.1 Description .................................................................... 19
1.13.2 Format........................................................................... 19
1.14 Random Target Address ............................................................ 19
1.14.1 Description .................................................................... 19
1.14.2 Format .......................................................................... 19
1.15 Advertising Interval .................................................................... 20
1.15.1 Description .................................................................... 20
1.15.2 Format .......................................................................... 20
1.16 LE Bluetooth Device Address .................................................... 20
1.16.1 Description .................................................................... 20
1.16.2 Format .......................................................................... 20
1.17 LE Role ...................................................................................... 21
1.17.1 Description .................................................................... 21
1.17.2 Format........................................................................... 21
1.18 Uniform Resource Identifier (URI) ............................................. 21
1.18.1 Description .................................................................... 21
1.18.2 Format ........................................................................ 22
1.19 LE Supported Features ............................................................. 22
1.19.1 Description .................................................................... 22
1.19.2 Format........................................................................... 22
1.20 Channel Map Update Indication ................................................ 22
1.20.1 Description .................................................................... 22
1.20.2 Format........................................................................... 23
1.21 BIGInfo ...................................................................................... 23
1.21.1 Description .................................................................... 23
1.21.2 Format........................................................................... 23
1.22 Broadcast_Code ........................................................................ 24
1.22.1 Description .................................................................... 24
1.22.2 Format........................................................................... 24
2 Examples ............................................................................................ 25
2.1 Host Examples .......................................................................... 25
2.1.1 Example extended inquiry response............................. 25
2.1.2 Example advertising data – Complete Local Name ...... 26
2.1.3 Example advertising data – URI ................................... 27
2.2 Controller Examples .................................................................. 29
2.2.1 Example ACAD – Channel Map Update Indication....... 29

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9 page 5

Part B
COMMON PROFILE AND SERVICE ERROR CODES
1 Overview of Common Profile and Service Error Codes................. 32
1.1 Usage Descriptions ................................................................... 32
1.2 List of Error Codes..................................................................... 32
2 Common Profile and Service Error Code Descriptions ................. 33
2.1 Out of Range (0xFF).................................................................. 33
2.2 Procedure Already in Progress (0xFE) ...................................... 33
2.3 Client Characteristic Configuration Descriptor Improperly
Configured (0xFD) ..................................................................... 33
2.4 Write Request Rejected (0xFC)................................................. 33

Part C
SERVICES PERMITTED TO USE SECURITY MODE 4 LEVEL 0
1 Services Permitted to use Security Mode 4 Level 0 ....................... 36
1.1 Security Mode 4 Level 0 over L2CAP Connection-oriented
Channels ................................................................................... 36
1.2 Security Mode 4 Level 0 over the L2CAP Connectionless Data
Channel ..................................................................................... 36

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification
Part A

PART A: DATA TYPES


SPECIFICATION

Bluetooth SIG Proprietary


Supplement to Bluetooth Core Specification | CSS v9, Part A page 7

Data Types Specification

CONTENTS

1 Data Types definitions and formats . . . . . . . . . . . . . . . . . . . . . . . . . 9


1.1 Service UUID ............................................................................ 10
1.1.1 Description ................................................................... 10
1.1.2 Format .......................................................................... 11
1.2 Local name ............................................................................... 11
1.2.1 Description ................................................................... 11
1.2.2 Format ......................................................................... 11
1.3 Flags ......................................................................................... 12
1.3.1 Description ................................................................... 12
1.3.2 Format .......................................................................... 12
1.4 Manufacturer Specific Data ...................................................... 13
1.4.1 Description ................................................................... 13
1.4.2 Format .......................................................................... 13
1.5 TX Power Level ........................................................................ 13
1.5.1 Description ................................................................... 13
1.5.2 Format .......................................................................... 14
1.6 Secure Simple Pairing Out of Band (OOB) ............................... 14
1.6.1 Description ................................................................... 14
1.6.2 Format .......................................................................... 14
1.7 Security Manager Out of Band (OOB) ...................................... 15
1.7.1 Description ................................................................... 15
1.7.2 Format .......................................................................... 15
1.8 Security Manager TK Value ...................................................... 16
1.8.1 Description ................................................................... 16
1.8.2 Format .......................................................................... 16
1.9 Slave Connection Interval Range ............................................. 16
1.9.1 Description ................................................................... 16
1.9.2 Format .......................................................................... 17
1.10 Service Solicitation ................................................................... 17
1.10.1 Description ................................................................... 17
1.10.2 Format .......................................................................... 17
1.11 Service Data ............................................................................. 18
1.11.1 Description ................................................................... 18
1.11.2 Format .......................................................................... 18
1.12 Appearance .............................................................................. 18
1.12.1 Description ................................................................... 18
1.12.2 Format .......................................................................... 18

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 8

Data Types Specification

1.13 Public Target Address ............................................................... 19


1.13.1 Description ................................................................... 19
1.13.2 Format .......................................................................... 19
1.14 Random Target Address ........................................................... 19
1.14.1 Description ................................................................... 19
1.14.2 Format ......................................................................... 19
1.15 Advertising Interval ................................................................... 20
1.15.1 Description ................................................................... 20
1.15.2 Format ......................................................................... 20
1.16 LE Bluetooth Device Address ................................................... 20
1.16.1 Description ................................................................... 20
1.16.2 Format ......................................................................... 20
1.17 LE Role ..................................................................................... 21
1.17.1 Description ................................................................... 21
1.17.2 Format .......................................................................... 21
1.18 Uniform Resource Identifier (URI) ............................................ 21
1.18.1 Description ................................................................... 21
1.18.2 Format ....................................................................... 22
1.19 LE Supported Features ............................................................ 22
1.19.1 Description ................................................................... 22
1.19.2 Format .......................................................................... 22
1.20 Channel Map Update Indication ............................................... 22
1.20.1 Description ................................................................... 22
1.20.2 Format .......................................................................... 23
1.21 BIGInfo ..................................................................................... 23
1.21.1 Description ................................................................... 23
1.21.2 Format .......................................................................... 23
1.22 Broadcast_Code ....................................................................... 24
1.22.1 Description ................................................................... 24
1.22.2 Format .......................................................................... 24
2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1 Host Examples ......................................................................... 25
2.1.1 Example extended inquiry response ............................ 25
2.1.2 Example advertising data – Complete Local Name ..... 26
2.1.3 Example advertising data – URI .................................. 27
2.2 Controller Examples ................................................................. 29
2.2.1 Example ACAD – Channel Map Update Indication ...... 29

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 9

Data Types Specification

1 DATA TYPES DEFINITIONS AND FORMATS

This part defines the basic data types used for Extended Inquiry Response
(EIR), Advertising Data (AD), Scan Response Data (SRD), Additional
Controller Advertising Data (ACAD), and OOB data blocks. Additional data
types may be defined in profile specifications.

Each data type shall only be used in accordance with the requirements
specified in Table 1.1.

Context

Data type EIR AD SRD ACAD OOB


Service UUID O O O O O
Local Name C1 C1 C1 X C1
Flags C1 C1 X X C1
Manufacturer Specific Data O O O O O
TX Power Level O O O X O
Secure Simple Pairing OOB X X X X O
Security Manager OOB X X X X O
Security Manager TK Value X X X X O
Slave Connection Interval Range X O O X O
Service Solicitation X O O X O
Service Data X O O O O
Appearance X C2 C2 X C1
Public Target Address X C2 C2 X C1
Random Target Address X C2 C2 X C1
Advertising Interval X C1 C1 X C1
LE Bluetooth Device Address X X X X C1
LE Role X X X X C1
Uniform Resource Identifier O O O X O
LE Supported Features X C1 C1 X C1
Channel Map Update Indication X X X C1 X
BIGInfo X X X C1 X
Broadcast_Code X X X X O
Table 1.1: Permitted usages for data types

O: Optional in this context (may appear more than once in a block).


C1: Optional in this context; shall not appear more than once in a block.
C2: Optional in this context; shall not appear more than once in a block and shall not
appear in both the AD and SRD of the same extended advertising interval.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 10

Data Types Specification

X: Reserved for future use.

The values for the data types are listed in Assigned Numbers.

All numerical multi-byte entities and values associated with the following data
types shall use little-endian byte order.

1.1 SERVICE UUID


GAP and GATT service UUIDs should not be included in a Service UUIDs AD
type, for either a complete or incomplete list.

1.1.1 Description

The Service UUID data type is used to include a list of Service or Service Class
UUIDs.

There are six data types defined for the three sizes of Service UUIDs that may
be returned:
• 16-bit Bluetooth Service UUIDs
• 32-bit Bluetooth Service UUIDs
• Global 128-bit Service UUIDs

Two Service UUID data types are assigned to each size of Service UUID. One
Service UUID data type indicates that the Service UUID list is incomplete and
the other indicates the Service UUID list is complete.

A packet or data block shall not contain more than one instance for each
Service UUID data size. If a device has no Service UUIDs of a certain size,
16-, 32-, or 128-bit, the corresponding field in the extended inquiry response or
advertising data packet shall be marked as complete with no Service UUIDs.
An omitted Service UUID data type shall be interpreted as an empty
incomplete-list.

16-bit and 32-bit UUIDs shall only be used if they are assigned by the
Bluetooth SIG. The Bluetooth SIG may assign 16-bit and 32-bit UUIDs to
member companies or organizations.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 11

Data Types Specification

1.1.2 Format

Data Type Description

«Incomplete List of 16-bit Service UUIDs» More 16-bit Service UUIDs available

«Complete List of 16-bit Service UUIDs» Complete list of 16-bit Service UUIDs

«Incomplete List of 32-bit Service UUIDs» More 32-bit Service UUIDs available

«Complete List of 32-bit Service UUIDs» Complete list of 32-bit Service UUIDs

«Incomplete List of 128-bit Service UUIDs» More 128-bit Service UUIDs available

«Complete List of 128-bit Service UUIDs» Complete list of 128-bit Service UUIDs

Table 1.2: Service UUID data types

1.2 LOCAL NAME

1.2.1 Description

The Local Name data type shall be the same as, or a shortened version of, the
local name assigned to the device. The Local Name data type value indicates if
the name is complete or shortened. If the name is shortened, the complete
name can be read using the remote name request procedure over BR/EDR or
by reading the device name characteristic after the connection has been
established using GATT.

A shortened name shall only contain contiguous characters from the beginning
of the full name. For example, if the device name is ‘BT_Device_Name’ then
the shortened name could be ‘BT_Device’ or ‘BT_Dev’.

1.2.2 Format

Data Type Description

«Shortened Local Name» Shortened local name

«Complete Local Name» Complete local name

Table 1.3: Local Name data types

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 12

Data Types Specification

1.3 FLAGS

1.3.1 Description

The Flags data type contains one bit Boolean flags. The Flags data type shall
be included when any of the Flag bits are non-zero and the advertising packet
is connectable, otherwise the Flags data type may be omitted. All 0x00 octets
after the last non-zero octet shall be omitted from the value transmitted.

Note: If the Flags AD type is not present in a non-connectable advertisement,


the Flags should be considered as unknown and no assumptions should be
made by the scanner.

Flags used over the LE physical channel are:


• Limited Discoverable Mode
• General Discoverable Mode
• BR/EDR Not Supported
• Simultaneous LE and BR/EDR to Same Device Capable (Controller)
• Simultaneous LE and BR/EDR to Same Device Capable (Host)

The LE Limited Discoverable Mode and LE General Discoverable Mode flags


shall be ignored when received over the BR/EDR physical channel. The ‘BR/
EDR Not Supported’ flag shall be set to 0 when sent over the BR/EDR physical
channel.

1.3.2 Format

The Flags field may be zero or more octets long. This allows the Flags field to
be extended while using the minimum number of octets within the data packet.

Data Type Octet Bit Description

«Flags» 0 0 LE Limited Discoverable Mode

0 1 LE General Discoverable Mode

0 2 BR/EDR Not Supported. Bit 37 of LMP


Feature Mask Definitions (Page 0)

0 3 Simultaneous LE and BR/EDR to Same


Device Capable (Controller). Bit 49 of
LMP Feature Mask Definitions (Page 0)

0 4 Simultaneous LE and BR/EDR to Same


Device Capable (Host). Bit 66 of LMP
Feature Mask Definitions (Page 1)

0 5..7 Reserved for future use

Table 1.4: Flags data types

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 13

Data Types Specification

1.4 MANUFACTURER SPECIFIC DATA

1.4.1 Description

The Manufacturer Specific data type is used for manufacturer specific data.
The first two data octets shall contain a company identifier from Assigned
Numbers. The interpretation of any other octets within the data shall be defined
by the manufacturer specified by the company identifier.

1.4.2 Format

Data Type Description

«Manufacturer Specific Data» Size: 2 or more octets


The first 2 octets contain the Company Identifier Code
followed by additional manufacturer specific data

Table 1.5: Manufacturer Specific data type

1.5 TX POWER LEVEL

1.5.1 Description

The TX Power Level data type indicates the transmitted power level of the
packet containing the data type. The TX Power Level should be the radiated
power level. The TX Power Level data type may be used to calculate path loss
on a received packet using the following equation:

pathloss = Tx Power Level – RSSI

where “RSSI” is the received signal strength, in dBm, of the packet received.

For example, if Tx Power Level = +4 (dBm) and the RSSI on the received
packet is -60 (dBm) then the total path loss is +4 – (-60) = +64 dB. If a second
packet were received at -40 dBm with a Tx Power Level data type = +15 dBm
the resulting pathloss would be +55 dB. An application could use these
pathloss values to choose which device it thinks might be closer (the one with
the lower pathloss value).

Unfortunately, due to fading and varying antenna, circuit, and chip


characteristics, these resulting pathloss values will have uncertainty. Some of
the uncertainty (for example, due to fading) may be able to be removed if
multiple packets are received from the same device.

Note: When the TX Power Level data type is not present, the TX power level of
the packet is unknown.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 14

Data Types Specification

1.5.2 Format

Data Type Description

«TX Power Level» Size: 1 octet


0xXX: -127 to +127 dBm

Table 1.6: TX Power Level data type

1.6 SECURE SIMPLE PAIRING OUT OF BAND (OOB)

1.6.1 Description

The Secure Simple Pairing Out of Band data types enable an out of band
mechanism to communicate discovery information as well as other information
related to the pairing process.

1.6.2 Format

The Secure Simple Pairing Out of Band data types shall be encapsulated in a
OOB data block as defined in [Vol 3] Part C, Section 5.2.2.7. The OOB data
block consists of the mandatory part with fields SSP OOB Length and
BD_ADDR as described in Table 1.7, followed by optional data types described
in Table 1.8.

Field Description

«SSP OOB Length» Size: 2 octets


0xXXXX: 8 to 65535 bytes
This field contains the length of the entire OOB data
block including the length field itself.

«BD_ADDR» Size: 6 octets


Format defined in [Vol 2] Part B, Section 1.2.

Table 1.7: Fields for OOB data block mandatory part

Data Type Description

«Class of Device» Size: 3 octets


Format defined in Assigned Numbers

«Simple Pairing Hash C-192» Size: 16 octets


Format defined in [Vol 2] Part H, Section 7.2.2.

«Simple Pairing Randomizer R-192» Size: 16 octets


Format defined in [Vol 2] Part H, Section 7.2.2.

«Simple Pairing Hash C-256» Size: 16 octets


Format defined in [Vol 2] Part H, Section 7.2.2.

Table 1.8: Data types for OOB data block optional parts

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 15

Data Types Specification

Data Type Description

«LE Secure Connections Confirmation Size: 16 octets


Value» Format defined in [Vol 3] Part H, Section
2.3.5.6.4.

«Simple Pairing Randomizer R-256» Size: 16 octets


Format defined in [Vol 2] Part H, Section 7.2.2

«LE Secure Connections Random Size: 16 octets


Value» Format defined in [Vol 3] Part H, Section
2.3.5.6.4.

Table 1.8: Data types for OOB data block optional parts

1.7 SECURITY MANAGER OUT OF BAND (OOB)

1.7.1 Description

The Security Manager Out of Band data type allows an out of band mechanism
to be used by the Security Manager to communicate discovery information as
well as other information related to the pairing process.

1.7.2 Format

The Security Manager Out of Band data type size is 1 octet.

Data Type Bit Description

«Security Manager Out of Band Flag» 0 OOB Flags Field


(0 = OOB data not present, 1 = OOB
data present)

1 LE supported (Host) (i.e. bit 65 of


LMP Extended Feature bits Page 1

2 Simultaneous LE and BR/EDR to


Same Device Capable (Host) (i.e. bit
66 of LMP Extended Feature bits
Page 1)

3 Address type (0 = Public Address, 1


= Random Address)

4..7 Reserved for future use

Table 1.9: Security Manager OOB Flags data type

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 16

Data Types Specification

1.8 SECURITY MANAGER TK VALUE

1.8.1 Description

The Security Manager TK Value data type allows an out of band mechanism to
be used by the Security Manager to communicate the TK value.

1.8.2 Format

Data Type Description

«Security Manager TK Value» Size: 16 octets


Value as used in pairing over LE Physical channel.
Format defined in [Vol 3] Part H, Section 2.3.

Table 1.10: Security Manager TK Value data type

1.9 SLAVE CONNECTION INTERVAL RANGE

1.9.1 Description

The Slave Connection Interval Range data type contains the Peripheral’s
preferred connection interval range, for all logical connections. See [Vol 3] Part
C, Section 12.3.

Note: The minimum value depends on the battery considerations of the


Peripheral and the maximum connection interval depends on the buffers
available on the Peripheral.

The Central should use the information from the Peripheral’s Slave Connection
Interval Range data type when establishing a connection.

Note: Central and Peripheral are GAP roles as defined in [Vol 3] Part C,
Section 2.2.2.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 17

Data Types Specification

1.9.2 Format

Data Type Description

«Slave Connection Interval Range» Size: 4 Octets


The first 2 octets defines the minimum value for
the connection interval in the following manner:
connIntervalmin = Conn_Interval_Min * 1.25 ms
Conn_Interval_Min range: 0x0006 to 0x0C80
Value of 0xFFFF indicates no specific minimum.
Values not defined above are reserved for future
use.

The other 2 octets defines the maximum value for


the connection interval in the following manner:
connIntervalmax = Conn_Interval_Max * 1.25 ms
Conn_Interval_Max range: 0x0006 to 0x0C80
Conn_Interval_Max shall be equal to or greater
than the Conn_Interval_Min.
Value of 0xFFFF indicates no specific maximum.
Values not defined above are reserved for future
use.

Table 1.11: Slave Connection Interval Range data type

1.10 SERVICE SOLICITATION

1.10.1 Description

A Peripheral device may send the Service Solicitation data type to invite Central
devices that expose one or more of the services specified in the Service
Solicitation data to connect. The Peripheral device should be in the undirected
connectable mode and in one of the discoverable modes. This enables a Central
device providing one or more of these services to connect to the Peripheral
device, so that the Peripheral device can use the services on the Central device.

Note: Central and Peripheral are GAP roles as defined in [Vol 3] Part C,
Section 2.2.2.

1.10.2 Format

Data Type Description

«List of 16 bit Service Solicitation UUIDs» List of 16 bit Service Solicitation UUIDs

«List of 32 bit Service Solicitation UUIDs» List of 32 bit Service Solicitation UUIDs

«List of 128 bit Service Solicitation UUIDs» List of 128 bit Service Solicitation UUIDs

Table 1.12: Service Solicitation UUID data types

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 18

Data Types Specification

1.11 SERVICE DATA

1.11.1 Description

The Service Data data type consists of a service UUID with the data associated
with that service.

1.11.2 Format

Data Type Description

«Service Data - 16 bit UUID» Size: 2 or more octets


The first 2 octets contain the 16 bit Service UUID fol-
lowed by additional service data

«Service Data - 32 bit UUID» Size: 4 or more octets


The first 4 octets contain the 32 bit Service UUID fol-
lowed by additional service data

«Service Data - 128 bit UUID» Size: 16 or more octets


The first 16 octets contain the 128 bit Service UUID
followed by additional service data

Table 1.13: Service Data data types

1.12 APPEARANCE

1.12.1 Description

The Appearance data type defines the external appearance of the device.

This value shall be the same as the Appearance characteristic, as defined in


[Vol 3] Part C, Section 12.2.

1.12.2 Format

Data Type Description

«Appearance» The Appearance value shall be the enumerated value as defined by


Assigned Numbers.

Table 1.14: Appearance data type

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 19

Data Types Specification

1.13 PUBLIC TARGET ADDRESS

1.13.1 Description

The Public Target Address data type defines the address of one or more
intended recipients of an advertisement when one or more devices were
bonded using a public address. This data type is intended to be used to avoid a
situation where a bonded device unnecessarily responds to an advertisement
intended for another bonded device.

1.13.2 Format

Data Type Description

«Public Target Address» Size: Multiples of 6 octets


The format of each 6 octet address is the same as the Public
Device Address defined in [Vol 6] Part B, Section 1.3.
The Public Target Address value shall be the enumerated
value as defined by Assigned Numbers.

Table 1.15: Public Target Address data type

1.14 RANDOM TARGET ADDRESS

1.14.1 Description

The Random Target Address data type defines the address of one or more
intended recipients of an advertisement when one or more devices were
bonded using a random address. This data type is intended to be used to avoid
a situation where a bonded device unnecessarily responds to an advertisement
intended for another bonded device.

1.14.2 Format

Data Type Description

«Random Target Address» Size: Multiples of 6 octets


The format of each 6 octet address is the same as the
Random Device Address defined in [Vol 6] Part B, Section
1.3.
The Random Target Address value shall be the enumer-
ated value as defined by Assigned Numbers.

Table 1.16: Random Target Address data type

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 20

Data Types Specification

1.15 ADVERTISING INTERVAL

1.15.1 Description

The Advertising Interval data type contains the advInterval value as defined in
[Vol 6] Part B, Section 4.4.2.2.

1.15.2 Format

Data Type Description

«Advertising Interval» Size: 2 octets (UINT16)


Units: 0.625 ms
advInterval value

Table 1.17: Advertising Interval data type

1.16 LE BLUETOOTH DEVICE ADDRESS

1.16.1 Description

The LE Bluetooth Device Address data type defines the device address of the
local device and the address type on the LE transport.

1.16.2 Format

Data Type Description

«LE Bluetooth Device Address» Size: 7 octets.


The format of the 6 least significant Octets
is the same as the Device Address defined
in [Vol 6] Part B, Section 1.3.
The least significant bit of the most signifi-
cant octet defines if the Device Address is a
Public Address or a Random Address.
LSB = 1 Then Random Device Address.
LSB = 0 Then Public Device Address.
Bits 1 to 7 in the most significant octet are
reserved for future use.

Table 1.18: Bluetooth Device Address data type

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 21

Data Types Specification

1.17 LE ROLE

1.17.1 Description

The LE Role data type defines the LE role capabilities of the device.

1.17.2 Format

The LE Role data type size is 1 octet.

Data Type Value Description

«LE Role» 0x00 Only Peripheral Role supported

0x01 Only Central Role supported

0x02 Peripheral and Central Role supported,


Peripheral Role preferred for connection
establishment

0x03 Peripheral and Central Role supported,


Central Role preferred for connection
establishment

0x04 – 0xFF Reserved for future use

Table 1.19: LE Role data type

1.18 UNIFORM RESOURCE IDENTIFIER (URI)

1.18.1 Description

The URI data type allows the representation of a URI, as defined in IETF STD
66. The URI data type is encoded using UTF-8. To help with compression, the
first UTF-8 code point in the URI data type value represents a scheme name
string, as defined below. All other UTF-8 code points in the URI data type shall
be appended to the decompressed scheme name string and the result forms
the URI.

The mapping of scheme name strings to UTF-8 code points is defined in


Assigned Numbers. Only permanent and provisional schemes, as defined by
the IETF (see http://www.iana.org/assignments/uri-schemes.html), shall be
assigned a scheme name and corresponding code point.

The code point of U+0001 shall be used when the scheme used is not defined
as either a permanent or provisional scheme. This code point maps to the
empty scheme name string.

When U+0001 is used, the actual scheme and ":" shall be included in the
remaining UTF-8 code points. Except for the special case of U+0001, the
decompressed scheme name string includes the “:” that separates the scheme
from the remainder (the “hier-part”) of the URI.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 22

Data Types Specification

1.18.2 Format

Data Type Description

«URI» Scheme name string and URI as a UTF-8 string

Table 1.20: URI data type

1.19 LE SUPPORTED FEATURES

1.19.1 Description

The LE Supported Features data type defines the LE features supported by the
device. All 0x00 octets after the last non-zero octet shall be omitted from the
value transmitted.

1.19.2 Format

The LE Supported Features data type size is zero or more octets long. This
allows the LE Supported Features to be represented while using the minimum
number of octets within the data packet.

Data Type Description

«LE Supported Features» The format is the same as the FeatureSet defined in
[Vol 6] Part B, Section 4.6.

Table 1.21: LE Supported Features data type

1.20 CHANNEL MAP UPDATE INDICATION

1.20.1 Description

The channel map (channelMap) used for periodic advertisements may be


updated at any time by the advertiser. The advertiser can update the channel
map by sending the Channel Map Update Indication data type in the extended
header of the packet containing the AUX_SYNC_IND PDU. The advertiser’s
Host may provide an initial channel map using the
HCI_LE_Set_Host_Channel_Classification command; however the
advertiser’s Controller can update the channels that were marked as unknown
by the Host in the channel map based on channel assessments without being
requested to by the Host. The Channel Map Update Indication data type shall
only be present in the extended header of the packet containing the
AUX_SYNC_IND PDU.

The channel map used before the instant is known as channelMapOLD. The
channel map contained in the Channel Map Update Indication data type and
used at the instant and after, is known as channelMapNEW.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 23

Data Types Specification

The Instant field shall be used to indicate the paEventCount value when
channelMapNEW shall apply; this value is called the instant.

Upon first transmission of the data type the advertiser should allow a minimum
of 6 AUX_SYNC_IND PDUs before the instant occurs.

When the value of paEventCount is equal to the Instant field, the


channelMapNEW shall become the current channelMap. The
lastUnmappedChannel shall not be reset. If the unmappedChannel is an
unused channel, then the channelMapNEW will be used when remapping. The
only parameter that changes is the channelMap.

The advertiser shall not send a new Channel Map Update Indication data type
before the instant.

1.20.2 Format

The Channel Map Update Indication data type size is 7 octets.

Data Type Octets Description

«Channel Map Update Indication» 0-4 ChM

5-6 Instant

Table 1.22: Channel Map Update Indication data type

The ChM field shall contain the channel map indicating Used and Unused data
channels. The format of this field is identical to the ChM field in the
CONNECT_IND PDU (see [Vol 6] Part B, Section 2.3.3.1).

The Instant field shall be set to indicate the instant as described in Section
1.20.1.

1.21 BIGINFO

1.21.1 Description

The BIGInfo data type contains the necessary information for a Synchronized
Receiver to synchronize to a BIG that is being broadcast by an Isochronous
Broadcaster.

1.21.2 Format

The format for BIGInfo is described in [Vol 6] Part B, Section 4.4.6.11.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 24

Data Types Specification

1.22 BROADCAST_CODE

1.22.1 Description

The Broadcast_Code data type contains the string format of the


Broadcast_Code for an encrypted BIG.

1.22.2 Format

The format for Broadcast_Code is described in [Vol 3] Part C, Section 3.2.6. It


should not include trailing zero octets.

Data Types definitions and formats Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 25

Data Types Specification

2 EXAMPLES

The following sections include examples of EIR and Advertising Data Types.

2.1 HOST EXAMPLES

2.1.1 Example extended inquiry response

This is an example extended inquiry response for a phone with PANU and
Hands-free Audio Gateway:

Value Notes

0x06 Length of this Data

0x09 «Complete Local Name»

0x50 'P'

0x68 'h'

0x6F 'o'

0x6E 'n'

0x65 'e'

0x05 Length of this Data

0x03 «Complete list of 16-bit Service UUIDs»

0x15 PANU service class UUID

0x11

0x1F Hands-free Audio Gateway service class UUID

0x11

0x01 Length of this data

0x05 «Complete list of 32-bit Service UUIDs»

0x01 Length of this data

0x07 «Complete list of 128-bit Service UUIDs»

0x00 End of Data (Not transmitted over the air)

Table 2.1: Example extended inquiry response

Examples Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 26

Data Types Specification

2.1.2 Example advertising data – Complete Local Name

This is an example of advertising data with AD types:

Value Notes

0x02 Length of this Data

0x01 «Flags»

0x01 LE Limited Discoverable Flag set

0x0A Length of this Data

0x09 «Complete local name»

0x50 ‘P’

0x65 ‘e’

0x64 ‘d’

0x6F ‘o’

0x6D ‘m’

0x65 ‘e’

0x74 ‘t’

0x65 ‘e’

0x72 ‘r’

Table 2.2: Example advertising data with AD types

Examples Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 27

Data Types Specification

2.1.3 Example advertising data – URI

This example represents an advertisement of the URI


“http://www.bluetooth.com”.

Value Notes

0x15 Length of this data

0x24 «URI»

0x16 UTF-8 code point for “http:”

0x2F ‘/’

0x2F ‘/’

0x77 ‘w’

0x77 ‘w’

0x77 ‘w’

0x2E ‘.’

0x62 ‘b’

0x6C ‘l’

0x75 ‘u’

0x65 ‘e’

0x74 ‘t’

0x6F ‘o’

0x6F ‘o’

0x74 ‘t’

0x68 ‘h’

0x2E ‘.’

0x63 ‘c’

0x6F ‘o’

0x6D ‘m’

Table 2.3: Example advertising data with a URI data type for http://www.bluetooth.com

Examples Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 28

Data Types Specification

This example represents an advertisement of the URI


“example://z.com/Ålborg”.

Value Notes

0x12 Length of this data

0x24 «URI»

0xC2 First UTF-8 octet for 'example:'

0xB9 Last UTF-8 octet for 'example:'

0x2F '/'

0x2F '/'

0x7A 'z'

0x2E '.'

0x63 'c'

0x6F 'o'

0x6D 'm'

0x2F '/'

0xC3 First UTF-8 octet for 'Å'

0x85 Last UTF-8 octet for 'Å'

0x6C 'l'

0x62 'b'

0x6F 'o'

0x72 'r'

0x67 'g'

Table 2.4: Example advertising data with a URI data type for example://z.com/Ålborg

Examples Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part A page 29

Data Types Specification

2.2 CONTROLLER EXAMPLES

2.2.1 Example ACAD – Channel Map Update Indication

Value Notes

0x08 Length of this Data

0x28 «Channel Map Update Indication»

0xFF ChM = 0x1FFFFFF7FF

0xF7

0xFF

0xFF

0x1F

0x64 Instant = 0x0064

0x00

Table 2.5: Example ACAD – Channel Map Update Indication

Examples Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification
Part B

PART B: COMMON PROFILE AND


SERVICE ERROR CODES

Bluetooth SIG Proprietary


Supplement to Bluetooth Core Specification | CSS v9, Part B page 31

Common Profile and Service Error Codes

CONTENTS

1 Overview of Common Profile and Service Error Codes . . . . . . . . 32


1.1 Usage Descriptions .................................................................. 32
1.2 List of Error Codes .................................................................... 32
2 Common Profile and Service Error Code Descriptions . . . . . . . . 33
2.1 Out of Range (0xFF) ................................................................. 33
2.2 Procedure Already in Progress (0xFE) ..................................... 33
2.3 Client Characteristic Configuration Descriptor Improperly
Configured (0xFD) .................................................................... 33
2.4 Write Request Rejected (0xFC) ................................................ 33

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part B page 32

Common Profile and Service Error Codes

1 OVERVIEW OF COMMON PROFILE AND SERVICE


ERROR CODES

This document lists the common profile and service error codes sent over the
Attribute Protocol. Error codes have a size of one octet.

1.1 USAGE DESCRIPTIONS


The purpose of this section is to give descriptions of how the common profile
error codes should be used. It is beyond the scope of this document to give
detailed descriptions of all situations where error codes can be used, especially
as this is implementation dependent.

1.2 LIST OF ERROR CODES


The possible range of common profile error codes is 0xE0 to 0xFF. The
Common Profile and Service Error Code Descriptions Part provides an error
code usage description for each failure error code.

Values marked as “Reserved for Future Use”, can be used in future versions of
the specification.

Error Code Name

0xE0 – 0xFB Reserved for Future Use

0xFC Write Request Rejected

0xFD Client Characteristic Configuration Descriptor Improperly Configured

0xFE Procedure Already in Progress

0xFF Out of Range

Table 1.1: List of Common Profile and Service Error Codes

Overview of Common Profile and Service Error Codes Revision Date: 2019-12-31
Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part B page 33

Common Profile and Service Error Codes

2 COMMON PROFILE AND SERVICE ERROR CODE


DESCRIPTIONS

2.1 OUT OF RANGE (0xFF)


The Out of Range error code is used when an attribute value is out of range as
defined by a profile or service specification.

2.2 PROCEDURE ALREADY IN PROGRESS (0xFE)


The Procedure Already in Progress error code is used when a profile or service
request cannot be serviced because an operation that has been previously
triggered is still in progress.

2.3 CLIENT CHARACTERISTIC CONFIGURATION


DESCRIPTOR IMPROPERLY CONFIGURED (0xFD)
The Client Characteristic Configuration Descriptor Improperly Configured error
code is used when a Client Characteristic Configuration descriptor is not
configured according to the requirements of the profile or service.

2.4 WRITE REQUEST REJECTED (0xFC)


The Write Request Rejected error code is used when a requested write
operation cannot be fulfilled for reasons other than permissions.
Note: This differs from the “Write Not Permitted” error response in Vol 3, Part F,
Section 3.4.1.1 (ATT), which is intended when the write operation cannot be
fulfilled due to permissions.

Common Profile and Service Error Code Descriptions Revision Date: 2019-12-31
Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification
Part C

PART C: SERVICES PERMITTED TO


USE SECURITY MODE 4 LEVEL 0

Bluetooth SIG Proprietary


Supplement to Bluetooth Core Specification | CSS v9, Part C page 35

Services Permitted to use Security Mode 4 Level 0

CONTENTS

1 Services Permitted to use Security Mode 4 Level 0 . . . . . . . . . . . 36


1.1 Security Mode 4 Level 0 over L2CAP Connection-oriented
Channels .................................................................................. 36
1.2 Security Mode 4 Level 0 over the L2CAP Connectionless Data
Channel .................................................................................... 36

Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Supplement to Bluetooth Core Specification | CSS v9, Part C page 36

Services Permitted to use Security Mode 4 Level 0

1 SERVICES PERMITTED TO USE SECURITY MODE 4


LEVEL 0

The following sections enumerate the services permitted to use Security Mode
4 Level 0 as defined in Volume 3, Part C, of the Bluetooth Core Specification,
v2.1 + EDR and later.

Section 1.1 enumerates those services that are permitted to use Security Mode
4 Level 0 over L2CAP connection oriented channels and Section 1.2
enumerates those services that are permitted to use Security Mode 4 Level 0
for unicast traffic over the L2CAP connectionless data channel (CID 0x0002).

Note: Security Mode 4 does not address broadcast traffic and hence this
section is not relevant to broadcast data sent over the L2CAP connectionless
data channel.

1.1 SECURITY MODE 4 LEVEL 0 OVER L2CAP CONNECTION-


ORIENTED CHANNELS
Services corresponding to the following UUIDs may use Security Mode 4 Level
0 over an L2CAP connection-oriented channel when operated over a BR/EDR
physical link. See Bluetooth Core Specification Volume 3, Part B, Section 2.5.1
for more information on UUIDs. Also see Bluetooth Assigned Numbers for a list
of assigned Service Class UUIDs.
• 0x1000 + Bluetooth_Base_UUID (Service Discovery Server)

1.2 SECURITY MODE 4 LEVEL 0 OVER THE L2CAP


CONNECTIONLESS DATA CHANNEL
Services corresponding to the following UUIDs may use Security Mode 4 Level
0 for unicast traffic over the L2CAP connectionless data channel (CID 0x0002)
when operated over a BR/EDR physical link. See Bluetooth Core Specification
Volume 3, Part B, Section 2.5.1 for more information on UUIDs. Also see
Bluetooth Assigned Numbers for a list of assigned Service Class UUIDs.
• 3D_Display + Bluetooth_Base_UUID
(3D Display service as defined in the 3D Synchronization Profile)
• 3D_Glasses + Bluetooth_Base_UUID
(3D Glasses service as defined in the 3D Synchronization Profile)

Services Permitted to use Security Mode 4 Level 0 Revision Date: 2019-12-31


Bluetooth SIG Proprietary
Bluetooth SIG Proprietary

You might also like