Combined QDID(s): [ B019990    ]

Layers   Core PICS   Profile PICS  
QDID:B021664
Product Name:LGE LTE Mobile Phone(LG-D821)
Product Type:End Product
TPG Version:TCRL 2013-1
Specification Name:4.0
Product Description:
LGE LTE Mobile Phone(LG-D821)


  Summary ICS  
  External to all Layers  



Controller Core Specification   [ top ]

Table 21: Controller Configuration Specification Version

Select the Specification Version used for the Controller Core Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Core Specification 2.0  Core 2.0   C.1      
Core Specification 2.0 + EDR  Core 2.0+EDR   C.1      
Core Specification 2.1  Core 2.1   C.1      
Core Specification 2.1 + EDR  Core 2.1+EDR   C.1      
Core Specification Addendum 1 (CSA1), Adopted 26 June 2008   CSA1   C.2      
Core Specification 3.0  Core 3.0   C.1      
Core Specification 4.0  Core 4.0   C.1      
10  Core Specification Addendum 2 (CSA2), Adopted 27 Dec 2011  CSA2   C.3      
11  Core Specification Addendum 3 (CSA3), Adopted 24 July 2012  CSA3   C.4      
12  Core Specification Addendum 4 (CSA4), Adopted 19 February 2013  CSA4   C.5      
C.1: Mandatory to support only one Controller Core Specification Version.
C.3: Optional if one of 21/5, 21/6, 21/8 or 21/9 (Core Spec 2.1 – 4.0) is supported, otherwise Excluded.
C.2: Optional if one of 21/3, 21/4, 21/5, or 21/6 (Core Spec 2.0 – 2.1+EDR) is supported, otherwise Excluded.
C.4: Optional if one of 21/5, 21/6, 21/8 or 21/9 (Core Spec 2.1 – 4.0) and 21/10 is supported, otherwise Excluded.
C.5: Optional if one of 21/5 or 21/6 or 21/8 or (21/9 and 21/11) (Core Spec 2.1- 3.0 or 4.0 with CSA3) is supported, otherwise Excluded.

Table 24: BR/EDR Controller Electrical Interfaces
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
UART Transport Layer  Vol. 4, Part A   O      
USB Transport Layer  Vol. 4, Part B   O      
Secure Digital (SD) Transport Layer  Vol. 4, Part C   O      
Three-wire UART Transport Layer (3-Wire)  Vol 4, Part D   O      
Core Spec Addendum 2 (CSA2), Audio Architecture USB Changes  Vol. 4, Part B   C.1      
Core Spec Addendum 3 (CSA3), Wireless Coexistence Interface (WCI-1) Transport  Vol.7, Part B*   C.2      
Core Spec Addendum 3 (CSA3), Wireless Coexistence Interface 2 (WCI-2) Transport  Vol.7, Part C*   C.2      
No PICS/ profile ICS exists for this part.
C.1: Optional if 21/10 and 24/2 are supported, otherwise Excluded.
C.2: Optional if 21/11 and 24/1 are supported, otherwise Excluded.

Table 31: Host Configuration Specification Version

Select the Specification Version used for the Host Core Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
(Item intentionally left blank)           
(Intentionally left blank)        
Core Specification 2.0/2.0 + EDR  Core 2.0 +EDR   C.1      
(Intentionally left blank)        
Core Specification 2.1/2.1 + EDR  Core 2.1 +EDR   C.1      
Core Spec Addendum (CSA) 1, Volume 3, Part A Adopted June 26 2008  CSA1   C.2      
Core Specification 3.0  Core 3.0   C.1      
Core Specification 3.0 + HS  Core 3.0 + HS   C.1      
10  Core Spec Version 4.0  Core 4.0   C.1      
11  Core Specification 4.0 + HS  Core 4.0 + HS   C.1      
12  Core Specification Addendum 2 (CSA2), Adopted 27 Dec 2011  CSA2   C.3      
13  Core Specification Addendum 3 (CSA3), Adopted 24 July 2012  CSA3   C.4      
14  Core Specification Addendum 4 (CSA4), Adopted 19 February 2013  CSA4   C.5      
C.1: Mandatory to support only one Host Core Specification Version.
C.2: Optional if one of 31/4 or 31/6 (Core Spec 2.0+EDR – 2.1+EDR) is supported, otherwise Excluded.
C.3: Optional if 31/10 or 31/11 (Core Spec Version 4.0) is supported, otherwise Excluded.
C.4: Optional if (31/10 or 31/11) and 31/12 are supported, otherwise Excluded.
C.5: Optional if 31/6 OR 31/8 OR 31/9 or (31/10 and 31/12) (Core Spec 2.1 -3.0 or 4.0 with CSA3) is supported, otherwise Excluded.

Table 33: Core Host Electrical Interfaces
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
UART Transport Layer  Vol 4, Part A   O      
USB Transport Layer  Vol 4, Part B   O      
Secure Digital (SD) Transport Layer  Vol 4, Part C   O      
Three-wire UART Transport Layer (3-Wire)  Vol 4, Part D   O      
Core Spec Addendum 2 (CSA2), Audio Architecture USB Changes  Vol. 4, Part D   C.1      
Core Spec Addendum 3 (CSA3), Wireless Coexistence Interface (WCI-1) Transport  Vol.7, Part B*   C.2      
Core Spec Addendum 3 (CSA3), Wireless Coexistence Interface 2 (WCI-2) Transport  Vol.7, Part C*   C.2      
No PICS/ profile ICS exists for this part.
C.1: Optional if 31/12 AND 33/2 are supported, otherwise Excluded.
C.2: Optional if 31/13 and 33/1 are supported, otherwise Excluded.

Table 41: AMP Controller Specification Version

Prerequisite: 21/5 or 21/6 or 21/8 or 21/9
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Core Spec Version 3.0 + HS or later  Core 3.0+HS
Core 4.0  
C.1      
Core Spec Addendum 2 (CSA2), 802.11 Protocol Adaptation Layer (802.11 PAL), Adopted 27 Dec 2012  CSA2   C.1      
C.1: Mandatory to support only one if PROD 2/3 or 2/6 is supported, otherwise Excluded.

Table 42: AMP Controller Specification Parts

Prerequisite: 41/1 or 41/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
802.11 Protocol Adaptation Layer (802.11 PAL)  Vol. 5, Part A   C.1      
802.11 MAC/PHY  IEEE 802.11-2007   C.2      
Core Spec Addendum 2 (CSA2), 802.11 Protocol Adaptation Layer (802.11 PAL)  CSA2   C.3      
802.11 MAC/PHY  IEEE 802.11-2007
Amendment 1   
C.4      
C.1. Mandatory if 41/1 is supported, otherwise Excluded.
C.2. Mandatory if 41/1 or 41/2 is supported, otherwise Optional.
C.3: Mandatory if 41/2 is supported, otherwise Excluded.
C.4: Mandatory if 42/3 is supported, otherwise Optional.

Table 43: AMP Controller Electrical Interfaces

Prerequisite: 41/1 or 41/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
UART Transport Layer  Vol. 4, Part A         
USB Transport Layer  Vol. 4, Part B         
Secure Digital (SD) Transport Layer  Vol 4, Part C         
Three-wire UART Transport Layer (3-Wire)  Vol 4, Part D         
No PICS/ profile ICS exists for this part.

Table 51: Low Energy Controller Configuration

Prerequisite: 21/9
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Low Energy Controller  Core 4.0   C.1      
C.1: Mandatory if PROD 2/4 or 2/5 or 2/6 is supported, otherwise Excluded.

Table 52: Low Energy Host Core Specification

Prerequisite: 31/10 or 31/11
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Low Energy Host  Core 4.0   C.1      
C.1: Mandatory if PROD 3/3 or 3/4 or 3/5 is supported, otherwise Excluded.





EDR Features   [ top ]

Table 22: EDR Features
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
EDR for asynchronous transports (single slot)   Core 2.0+EDR and later   C.1      
EDR for asynchronous transports (multi-slot)   Core 2.0+EDR and later   C.1      
EDR for synchronous transports  Core 2.0+EDR and 2.1+EDR   C.1, C.3      
EDR for synchronous transports   CSA1 and 3.0+HS or later   C.1, C.2      
C.1: Mandatory to support at least one if +EDR (21/4 or 21/6) is supported; Mandatory to support at least one if +HS (41/1 or 41/2) is supported, otherwise Optional
C.2: Optional if CSA1 or later (21/7 or 21/8 or 21/9 or 21/10) is supported, otherwise Excluded.
C.3: Optional if (21/3 or 21/4 or 21/5 or 21/6) is supported, otherwise Excluded.





  Product Type  
  External to All Layers  



Product Types   [ top ]

Table 1: Product Types

Please confirm the Product Type that was selected when Creating New Project
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
End Product   N/A    C.1      
Component (Tested)   N/A    C.1      
Component (Non-Tested)   N/A    C.1      
Host Subsystem   N/A    C.1      
Controller Subsystem   N/A    C.1      
Profile Subsystem   N/A    C.1      
Test Equipment   N/A    C.1      
Development Tool  N/A    C.1      
C.1: Mandatory to support one and only one Product Type.

Table 2: Controller Core Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
BR Controller  Vol. 0 Part B    C.1      
BR/EDR Controller   Vol. 0 Part B   C.1      
BR/EDR/HS Controller  Vol. 0 Part B   C.1      
LE Controller  Vol. 0 Part B   C.1      
BR/EDR/LE Combined Controller  Vol. 0 Part B   C.1      
BR/EDR/HS/LE Combined Controller  Vol. 0 Part B   C.1      
C.1: Mandatory to support only one Controller Configuration. Optional if 1/2 or 1/3 is Supported.

Table 3: Host Core Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
BR Host  Vol. 0 Part B   C.1      
BR/HS Host   Vol. 0 Part B   C.1      
LE Host   Vol. 0 Part B   C.1      
BR/LE Host   Vol. 0 Part B   C.1      
BR/HS/LE Host  Vol. 0 Part B   C.1      
C.1: Mandatory to support only one Host Configuration. Optional if 1/2 or 1/3 is Supported.





  Radio  
  Vol 2, Part A  



1.3.1 General Information   [ top ]

Table 1: RF Capabilities
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Power Class = 1  RF, 3   M.1      
Power Class = 2  RF, 3   M.1      
Power Class = 3  RF, 3   M.1      
Power Control  RF, 3   C.1      
1-slot packets supported  BB, 6.5   M      
3-slot packets supported  BB, 6.5   O      
5-slot packets supported  BB, 6.5   O      
79 Channels  RF, 2   M      
Support for GFSK modulation  RF, 3.1   M      
10  Support for pi/4-DQPSK modulation  RF, 3.2   C.2      
11  Support for 8DPSK modulation  RF, 3.3   C.3      
12  Enhanced Power Control  RF, 3   C.4      
M.1: Mandatory to support one and only one power class (1/1-3).
C.1: Mandatory if 1/1 is supported, otherwise Optional.
C.2: Mandatory if (SUM ICS 22/1 or 22/2 or 22/3 or 22/4) is supported, otherwise Excluded.
C.3: Mandatory if (SUM ICS 22/1 or 22/2 or 22/3) is supported; Optional if (SUM ICS 22/4) is supported, otherwise Excluded.
C.4: Optional if Core Specification 3.0 or later (SUM ICS 21/8 or SUM ICS 21/9) AND 1/4 is supported, otherwise Excluded.





  Baseband   
  Vol 2, Part B  



Physical Channel   [ top ]

Table 1: Physical Channel
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support frequency band and 79 RF channels  BB, 2.1   M      
Adaptive Frequency Hopping Kernel  BB, 2.6   M      

Table 1a: Modulation Schemes
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Basic Data Rate, 1 Mbps payload data rate  RF, 3.1   M      
Enhanced Data Rate, 2 Mbps payload data rate  RF, 3.2   C.1      
Enhanced Data Rate, 3 Mbps payload data rate  RF, 3.2   C.2      
C.1: Mandatory if (SUM ICS 22/1 or 22/2 or 22/3 or 22/4) is supported, otherwise Excluded.
C.2 Mandatory if (SUM ICS 22/1 or 22/2 or 22/3) is supported; Optional if (SUM ICS 22/4) is supported, otherwise Excluded.


Physical Links   [ top ]

Table 2: Link Types
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of ACL link  BB, 5.2   M      
Support of SCO link  BB, 5.4   O      
Support of eSCO link  BB, 4.3   O      
Support of Enhanced Data Rate ACL links  BB, 6.5.4   C.1      
Support of Enhanced Data Rate eSCO links  BB, 6.5.3   C.2      
Profile Broadcast Data Link  BB, 5.7   C.3      
C.1: Mandatory if (SUM ICS 22/1 or 22/2) is supported, otherwise Optional.
C.2: Mandatory if (SUM ICS 22/1 or 22/2 or 22/3) is supported; Optional if (SUM ICS 22/4) is supported, otherwise Excluded.
C.3: Optional if SUM ICS 21/12 (CSA4) or later is supported, otherwise Excluded.

Table 3: SCO Link Support

Prerequisite for Items (3/5-8): 2/3
Prerequisite for Items (3/1-4): 2/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Values
Allowed Supported
SCO links to same Slave  BB, 4.3  C.1      (1,2,3)
SCO links to different Slaves  BB, 4.3      (1,2,3)
SCO links from same Master  BB, 4.3  C.1      (1,2,3)
SCO links from different Masters  BB, 4.3      (> 2)
eSCO links to same Slave  BB, 4.2  C.2      (1,2,3,4,5,6)
eSCO links to different Slaves  BB, 4.2      (2,3,4,5)
eSCO links from same Master  BB, 4.2  C.2      (1,2,3,4,5,6)
eSCO links from different Masters  BB, 4.2      (2,3,4,5)
C.2: Mandatory to support at least one of 3/5 or 3/7.
C.1: Mandatory to support at least one of 3/1 or 3/3.

Table 3a: Profile Broadcast Data Link Support

Prerequisite: 2/6 (Support of Broadcast Data Link)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Connectionless Slave Broadcast Transmitter  BB 8.10.1
LMP 3.3 Table 3.4, Item 128  
C.1      
Connectionless Slave Broadcast Receiver  BB 6.5.1
BB 6.5.1.2  
C.1      
C.1: Mandatory to support at least one of the defined roles.


Packet Types   [ top ]

Table 4: Common Packet Types
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of ID packet type  BB, 6.5.1
BB,6.5.1.1  
M      
Support of NULL packet type  BB, 6.5.1
BB, 6.5.1.2  
M      
Support of POLL packet type  BB, 6.5.1
BB, 6.5.1.3  
M      
Support of FHS packet type  BB, 6.5.1
BB,6.5.1.4  
M      
Support of DM1 packet type  BB, 6.5.1
BB, 6.5.1.5
BB, 6.5.4
BB, 6.5.4.1  
M      

Table 5: ACL Packet Types
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of DH1 packet type  BB, 6.5.4
BB,6.5.4.2  
M      
Support of DM3 packet type  BB, 6.5.4
BB,6.5.4.3  
C.1      
Support of DH3 packet type  BB, 6.5.4
BB,6.5.4.4  
O      
Support of DM5 packet type  BB, 6.5.4
BB,6.5.4.5  
O      
Support of DH5 packet type  BB, 6.5.4
BB,6.5.4.6  
O      
Support of AUX1 packet type  BB, 6.5.4
BB,6.5.4.7  
O      
C.1: Mandatory if (9c/1 or 9c/2) is supported, otherwise Optional.

Table 5a: Enhanced Data Rate ACL Packet Types

Prerequisite: 2/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support 2-DH1 packet type  BB, 6.5.4.8   C.1      
Support 2-DH3 packet type   BB, 6.5.4.9   C.2      
Support 2-DH5 packet type   BB, 6.5.4.10   C.2      
Support 3-DH1 packet type   BB, 6.5.4.11   C.3      
Support 3-DH3 packet type   BB, 6.5.4.12   C.4      
Support 3-DH5 packet type   BB, 6.5.4.13   C.5      
C.1: Mandatory if (SUM ICS 22/1 or 22/2) is supported, otherwise Optional if (BB 1a/2) is supported.
C.2: Mandatory if (SUM ICS 22/2) is supported, otherwise Optional if (BB 1a/2) is supported.
C.3: Mandatory if (SUM ICS 22/1 or 22/2) is supported, otherwise Optional if (BB 1a/3) is Supported.
C.4: Mandatory if (SUM ICS 22/2) is supported, otherwise Optional if (BB 5a/2 and 5a/4) are supported.
C.5: Mandatory if (SUM ICS 22/2) is supported, otherwise Optional if (BB 5a/3 and 5a/4) are supported.

Table 6: SCO and eSCO Packet Types

Prerequisite for Items (6/1-4): 2/2
Prerequisite for Items (6/5-7): 2/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of HV1 packet type  BB, 6.5.2
BB,6.5.2.1  
C.1      
Support of HV2 packet type  BB, 6.5.2
BB,6.5.2.2  
O      
Support of HV3 packet type  BB, 6.5.2
BB,6.5.2.3  
O      
Support of DV packet type  BB, 6.5.2
BB,6.5.2.4  
C.1      
Support of EV3 packet type  BB, 6.5.3
BB,6.5.3.1  
C.2      
Support of EV4 packet type  BB, 6.5.3
BB,6.5.3.2  
O      
Support of EV5 packet type  BB, 6.5.3
BB,6.5.3.3  
O      
C.1: Mandatory if only 2/2 is supported.
C.2: Mandatory if only 2/3 is supported.

Table 6a: Enhanced Data Rate eSCO Packet Types

Prerequisite: 2/5
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support 2-EV3 packet type  BB, 6.5.3.4   C.1      
Support 2-EV5 packet type  BB, 6.5.3.5   C.2      
Support 3-EV3 packet type  BB, 6.5.3.6   C.3      
Support 3-EV5 packet type  BB, 6.5.3.7   C.4      
C.1: Mandatory if (SUM ICS 22/3) is supported, otherwise Optional if (BB 1a/2) is supported.
C.2: Optional if 1a/2 is supported.
C.3: Mandatory if (SUM ICS 22/3) is supported and (SUM ICS 22/4) is Not Supported, otherwise Optional if (BB 1a/3) is supported.
C.4: Optional if 1a/3 is supported.


Access Procedures   [ top ]

Table 7: Page Procedures
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support paging  BB, 8.3.2   M      
Support page scan  BB, 8.3.1   M      
(Intentionally left blank)        
(Intentionally left blank)        
Supports Interlaced Scan during page scan  BB, 2.4   O      
Support Truncated Paging  BB, 8.3.3   C.1      
Support Page Response Timeout Detection  BB, 8.3   C.2      
C.1: Mandatory if (3a/1 or 3a/2) is supported, otherwise Optional.
C.2: Mandatory if 3a/1 is supported, otherwise Optional.

Table 8: Paging Schemes
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Supports mandatory scan mode  BB, 8.3
BB, table 6.5  
M      

Table 9: Paging Modes
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Supports paging mode R0  BB, 8.3.1
BB, table 8.1  
C.1      
Supports paging mode R1  BB, 8.3.1
BB, table 8.1  
C.1      
Supports paging mode R2  BB, 8.3.1
BB, table 8.1  
C.1      
C.1: At least one of 9/1-3 is Mandatory.

Table 9b: Paging Train Repetition
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Supports Npage >= 1  BB, 8.3.2
BB, table 8.2  
O      
Supports Npage >= 128  BB, 8.3.2
BB, table 8.2  
O      
Supports Npage >= 256  BB, 8.3.2
BB, table 8.2  
M      
Note: The master should use Npage >= 256 unless it knows what SR mode the slave uses.

Table 9c: Synchronization Modes Support

Prerequisite: 2/6 (Support of Broadcast Data Link)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Synchronization Train  BB 8.3.5
LMP 3.3 Table 3.4, Item 130  
      
Synchronization Scan  BB 8.3.4
LMP 3.3 Table 3.4, Item 131  
      
C.1: Mandatory if 3a/1 is supported, otherwise Excluded.
C.2: Mandatory if 3a/2 is supported, otherwise Excluded.

Table 10: Inquiry Procedures
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support inquiry  BB, 8.4.2   O      
Inquiry scan with first FHS  BB, 8.4.2   O      
(Intentionally left blank)        
(Intentionally left blank)        
Supports the dedicated inquiry access code  BB, 6.3.1   O      
Supports interlaced Scan during inquiry scan  BB, 2.5   O      
Extended Inquiry Response  BB, 8.4.2, BB 8.4.3   C.1      
C.1: Mandatory if (GAP 1/3) and (Core Spec 2.1 or later), otherwise Optional. Excluded if (Core Spec 2.0) is supported.


Networking Capabilities   [ top ]

Table 11: Piconet Capabilities
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Values
Allowed Supported
Broadcast messages  BB, 7.6.1
BB, 7.6.5 
    (N/A)  
Point-to-multipoint connections  BB, 1      (2,3,4,5,6,7)

Table 12: Scatternet Capabilities
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Act as Master in one piconet and Slave in another piconet  BB, 1   O      
Act as Slave in more than one piconet  BB, 1   O      


Synchronous Data Formats   [ top ]

Table 13: Synchronous Coding Schemes

Prerequisite: 2/2 (SCO link support)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
A-law  BB, 9.1   O      
u-law  BB, 9.1   O      
CVSD  BB, 9.2   O      
Transparent Synchronous Data  BB, 5.4
BB, 5.5  
O      


Erroneous Data Reporting   [ top ]

Table 14: Erroneous Data Reporting
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Erroneous Data Reporting for SCO  BB 7.7   C.1      
Erroneous Data Reporting for eSCO  BB 7.7   C.2      
C.1: Optional if (Core Spec 2.1 or later) and (HCI 9/6) is supported, otherwise Excluded.
C.2: Optional if (Core Spec 2.1 or later) and (HCI 9/7) is supported, otherwise Excluded.


Persistent Sniff   [ top ]

Table 15: This table is intentionally left blank: DO NOT USE
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
(Intentionally left blank)        


Non-flushable Packet Boundary Flag   [ top ]

Table 16: Non-flushable Packet Boundary Flag
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support Non-flushable Packet Boundary Flag  Vol 2, Part B, Section 7.6.3   C.1      
C.1 Mandatory if (Core Spec 2.1 or later) and (HCI 12/1) is supported, otherwise optional. Excluded if (Core Spec 2.0) is supported.


Connection States   [ top ]

Table 17: Connection States
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Sniff Subrating Mode  Vol 2, Part C, Section 4.5.3.3   C.1      
C.1 Mandatory if (Core Spec 2.1 or later) and (LMP 2/8) is supported, otherwise optional. Excluded if (Core Spec 2.0) is supported.





  Link Manager  
  Vol 2, Part C  



General Response Messages   [ top ]

Table 1: Response Messages
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Accept message  LMP, 2.7   M      
Reject message  LMP, 2.7   M      


Supported Features (General Statement)   [ top ]

Table 2: Supported Features

Note: This table refers to the values in the LM feature request message. It is used within this PICS as a general statement that will be used as prerequisite for other tables.
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
3-slot packets  LMP, 4.1.10,
LMP,3.3  
O      
5-slot packets  LMP, 4.1.10,
LMP, 3.3  
O      
Encryption  LMP, 4.2.5,
LMP, 3.3  
C.5      
Slot offset  LMP, 4.4.1,
LMP, 3.3  
O      
Timing accuracy  LMP, 4.3.1,
LMP, 3.3  
O      
Role switch (Master/Slave)  LMP,4.4.2,
LMP, 3.3  
O      
Hold mode  LMP,4.5.1,
LMP, 3.3  
O      
Sniff mode  LMP,4.5.3,
LMP, 3.3  
O      
Park mode  LMP,4.5.2,
LMP, 3.3  
O      
10  Power Control  RF, 3
LMP, 4.1.3,
LMP, 3.3  
C.1      
11  Channel quality driven data rate  LMP, 4.1.7,
LMP, 3.3  
O      
12  SCO link  LMP, 4.6.1,
LMP, 3.3  
O      
13  RSSI  LMP, 3.3   O      
14  Broadcast encryption  LMP, 4.2.5,
LMP, 3.3  
O      
15  eSCO link  LMP, 4.6.2   O      
16  Adaptive frequency hopping  LMP, 4.1.4   O      
17  Enhanced Data Rate ACL  BB, 6.5.4
LMP, 3.3  
C.2      
18  Enhanced Data Rate eSCO  BB, 6.5.3
LMP, 3.3  
C.3      
19  Simple Pairing  LMP 4.2.7   C.4      
20  Enhanced Power Control  LMP, 4.1.3.1, LMP, 3.3   C.6      
21  BR/EDR Not Supported  LMP, 3.3   O      
22  LE Supported (Controller)  LMP, 3.3   O      
23  LE and BR/EDR to same device capable (Controller)  LMP, 3.3   O      
24  LE Supported (Host)  LMP, 3.3   C.7      
25  Simultaneous LE and BR/EDR to same device capable (Host)  LMP, 3.3   C.8      
C.1: Mandatory if (RF 1/1) is supported, otherwise Optional.
C.2: Mandatory if (SUM ICS 22/1 or 22/2) is supported, otherwise Excluded.
C.3: Mandatory if (SUM ICS 22/3 or 22/4) is supported, otherwise Excluded.
C.4: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Excluded.
C.5: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Optional.
C.6: Optional if (Core Spec 3.0 or later) and (LMP 2/10 and 2/13) are supported, otherwise Excluded.
C.7: Mandatory if 2/22 is supported, otherwise Excluded.
C.8: Mandatory if 2/24 is supported, otherwise Excluded.


Authentication   [ top ]

Table 3: Authentication
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Initiate authentication before connection completed  LMP, 4.2.1   O      
Initiate authentication after connection completed  LMP, 4.2.1   O      
Respond to authentication request  LMP, 4.2.1   M      


Pairing   [ top ]

Table 4: Pairing
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Initiate pairing before connection completed  LMP, 4.2.2   O      
Initiate pairing after connection completed  LMP, 4.2.2   O      
Respond to pairing request  LMP, 4.2.2.1,
LMP, 4.2.2.3  
M      
Use fixed PIN and request responder to initiator switch  LMP, 4.2.2.2   C.1      
Use variable PIN  LMP, 4.2.2.2   C.1      
Accept initiator to responder switch  LMP, 4.2.2.2   C.2      
TSPC_Change_of_IO_Capabilities  LMP, 4.2.7.3.4   C.3      
C.1: Mandatory to support at least one of 4/4 or 4/5.
C.2: Mandatory if 4/5 and (4/1 or 4/2) are supported.
C.3: Mandatory if ESR05 is supported, otherwise Optional.


Link Keys   [ top ]

Table 5: Link Keys
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Creation of link key - Unit Key  LMP, 4.2.2.4   C.1      
Creation of link key - Combination Key  LMP, 4.2.2.4   C.1      
Initiate change of link key  LMP, 4.2.3   O      
Accept change of link key  LMP, 4.2.3   M      
(Intentionally left blank)           
(Intentionally left blank)           
Accept pairing with Unit Key  LMP, 4.2.2.4   O      
C.1: Mandatory to support at least one of 5/1 or 5/2.


Encryption   [ top ]

Table 6: Encryption

Prerequisite: 2/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Initiate encryption  LMP, 4.2.5.1   C.1      
Accept encryption requests  LMP, 4.2.5.1   M      
(Intentionally left blank)           
(Intentionally left blank)           
Key size negotiation  LMP, 4.2.5.2   M      
Start encryption, as master  LMP, 4.2.5.3   M      
Accept start of encryption  LMP, 4.2.5.3   M      
Stop encryption , as master  LMP, 4.2.5.4   M      
Accept stop of encryption  LMP, 4.2.5.4   M      
10  Encryption Pause/Resume  LMP 4.2.5.3   C.2      
C.1: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Optional.
C.2: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Excluded.


Information Requests   [ top ]

Table 7: Clock Offset Information
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request clock offset information  LMP, 4.3.2   O      
Respond to clock offset requests   LMP, 4.3.2   M      

Table 8: Slot Offset Information

Prerequisite: 2/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Send slot offset information  LMP, 4.4.1   C.1      
C.1: Mandatory if 13/1 is supported, otherwise Optional.

Table 9: Timing Accuracy Information

Prerequisite: 2/5
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request timing accuracy information  LMP, 4.3.1   O      
Respond to timing accuracy information requests  LMP, 4.3.1   M.1      

Table 10: LM Version Information
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request LM version information  LMP, 4.3.3   O      
Respond to LM version information requests  LMP, 4.3.3   M      

Table 11: Feature Support
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request supported features  LMP, 4.3.4   C.1      
Respond to supported features requests  LMP, 4.3.4   M      
Request extended features mask  LMP, 4.3.4   C.2      
Respond to extended features Request  LMP, 4.3.4   C.2      
C.1: Mandatory if any of the "Optional" features in Table 2 is supported, otherwise Optional. (LMP:2/1-3), (LMP:2/5), (LMP:2/7-12), (LMP:2/14-16), (LMP:26/1) is requested by the IUT, ELSE Optional.
C.2: Mandatory if a feature requiring another features page is supported, otherwise Optional.

Table 12: Name Information
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request name information   LMP, 4.3.5   O      
Respond to name requests  LMP, 4.3.5   M      


Link Handling   [ top ]

Table 13: Role Switch

Prerequisite: 2/6
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request Master Slave switch  LMP, 4.4.2   O      
Accept Master Slave switch requests  LMP, 4.4.2   M      

Table 14: Detach
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Detach connection  LMP, 4.1.2   M      

Table 14a: Setting Up and Removing Enhanced Data Rate ACL Connection
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Enter Enhanced Data Rate  LMP, 4.1.11   C.1      
Exit Enhanced Data Rate  LMP, 4.1.11   C.1      
C.1: Mandatory if 2/17 is supported, otherwise Excluded.

Table 14b: Setting Up and Removing Enhanced Data Rate eSCO Connection
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Enter and Exit eSCO Using Enhanced Data Rate Packets  LMP, 4.6.2   C.1      
C.1: Mandatory if 2/18 is supported, otherwise Excluded.

Table 15: Hold Mode

Prerequisite: 2/7
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Force hold mode  LMP, 4.5.1,
LMP, 4.5.1.2  
O      
Request hold mode  LMP, 4.5.1,
LMP, 4.5.1.3  
C.1      
Respond to hold mode requests  LMP, 4.5.1,
LMP, 4.5.1.3  
M      
Accept forced hold mode  LMP, 4.5.1.1,
LMP, 4.5.1.2  
M      
C.1: Mandatory if 15/1 is supported, otherwise Optional.

Table 16: Sniff Mode

Prerequisite: 2/8
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
(Intentionally left blank)           
Request sniff mode  LMP, 4.5.3,
LMP, 4.5.3.2  
O      
Respond to sniff mode requests (renegotiate or reject)  LMP, 4.5.3.2   M      
(Intentionally left blank)           
Request un-sniff  LMP, 4.5.3.2   C.1      
Accept un-sniff requests  LMP, 4.5.3.2   M      
Sniff Subrating Mode  LMP, 4.5.3.3   C.2      
C.1: Mandatory if 16/2 is supported, otherwise Optional.
C.2: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Excluded.

Table 17: Park Mode

Prerequisite: 2/9
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
(Intentionally left blank)           
Request park mode  LMP, 4.5.2,
LMP, 4.5.2.2,
LMP, 4.5.2.3  
O      
Respond to park mode requests  LMP, 4.5.2,
LMP, 4.5.2.2,
LMP, 4.5.2.3  
M      
(Intentionally left blank)           
Set up broadcast scan window  LMP, 4.5.2.3   O      
Accept changes to the broadcast scan window  LMP, 4.5.2.3   M      
Modify beacon parameters  LMP, 4.5.2.4   O      
Accept modification of beacon parameters  LMP, 4.5.2.4   M      
Request Unpark using PM_ADDR  LMP, 4.5.2.5   C.1      
10  Request Unpark using BD_ADDR  LMP, 4.5.2.5   C.1      
11  Slave requested Unpark  LMP, 4.5.2.5,
BB, 5.9.6  
O      
12  Accept Unpark using PM_ADDR  LMP, 4.5.2.5   M      
13  Accept Unpark using BD_ADDR  LMP, 4.5.2.5   M      
C.1: Mandatory to support at least one of (17/9 or 17/10), otherwise Optional.

Table 18: Power Control

Prerequisite for Items (18/1-2): 2/13
Prerequisite for Items (18/3-4): 2/10
Prerequisite for Items (18/5-10): 2/20
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request to increase power  LMP, 4.1.3   M.1      
Request to decrease power  LMP, 4.1.3   M.1      
Respond when max power reached  LMP, 4.1.3   M.2      
Respond when min power reached  LMP, 4.1.3   M.2      
Request to increment power a single step  LMP, 4.1.3.1.1   M.3      
Request to decrease power a single step  LMP, 4.1.3.1.1    M.3      
Request to go to max power  LMP, 4.1.3.1.1   O      
Respond to increment power a single step  LMP, 4.1.3.1.2   M.3      
Respond to decrease power a single step  LMP, 4.1.3.1.2   M.3      
10  Respond to go to max power  LMP, 4.1.3.1.2   M.3      
M.1: Mandatory if 2/13 is supported.
M.2: Mandatory if 2/10 is supported.
M.3: Mandatory if 2/20 is supported.

Table 19: Link Supervision Timeout
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Set link supervision timeout value  LMP, 4.1.6   O      
Accept link supervision timeout setting  LMP, 4.1.6   M      


Quality of Service   [ top ]

Table 20: Quality of Service
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Channel quality driven change between DM and DH packet type  LMP, 4.1.7   C.1      
Force/Request change of Quality of Service  LMP, 4.1.8,
LMP, 4.1.8.1  
M      
Request Change of Quality of Service  LMP, 4.1.8,
LMP, 4.1.8.2  
M      
C.1: Mandatory if 2/11 is supported (stated in the feature request), otherwise Optional.


SCO Links   [ top ]

Table 21: SCO Links

Prerequisite: 2/12
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Initiate SCO links, as Master  LMP, 4.6.1,
LMP, 4.6.1.1  
O      
Initiate SCO links, as Slave  LMP, 4.6.1,
LMP, 4.6.1.2  
O      
Accept SCO links  LMP, 4.6.1,
LMP, 4.6.1.1,
LMP, 4.6.1.2  
O      
Remove SCO links, as Master  LMP, 4.6.1,
LMP,4.6.1.5  
C.1      
Remove SCO links, as Slave  LMP, 4.6.1,
LMP,4.6.1.5  
C.2      
Negotiate SCO link parameters, as Master  LMP, 4.6.1,
LMP,4.6.1.3  
C.3      
Negotiate SCO link parameters, as Slave  LMP, 4.6.1,
LMP,4.6.1.4  
C.4      
C.1: Mandatory if 21/1 is supported, otherwise Optional.
C.2: Mandatory if 21/2 is supported, otherwise Optional.
C.3: Mandatory if (21/1 or 21/3) is supported, otherwise Optional.
C.4: Mandatory if (21/2 or 21/3) is supported, otherwise Optional.


Multi-Slot Packages   [ top ]

Table 22: Multi-Slot Packages
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Accept maximum allowed number of slots to be used  LMP, 4.1.10   C.1      
Request maximum number of slots to be used  LMP, 4.1.10   C.1      
Accept request of maximum number of slots to be used  LMP, 4.1.10   C.1      
C.1: Mandatory if (2/1 and/or 2/2) is supported, otherwise Optional.


Paging Scheme   [ top ]

Table 23: Paging Scheme
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Request page mode to use  LMP, 4.1.9,
LMP, 4.1.9.1  
O      
Accept suggested page mode  LMP, 4.1.9,
LMP,4.1.9.1  
O      
Request page scan mode to use  LMP, 4.1.9,
LMP,4.1.9.2  
O      
Accept suggested page scan mode  LMP, 4.1.9, LMP, 4.1.9.2   O      


Connection Establishment   [ top ]

Table 24: Connection Establishment
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Create connection for higher layers  LMP, 4.1.1   M      
Respond to requests to establish connections for higher layers  LMP, 4.1.1   M      
Indicate that link set-up is complete  LMP, 4.1.1   M      


Test Mode   [ top ]

Table 25: Test Mode
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Activate test mode  LMP, 4.7.1   O      
Ability to reject activation of test mode if test mode is disabled  LMP, 4.7.1   M      
Control test mode  LMP, 4.7.2   O      
Ability to reject est mode control commands if test mode is disabled.  LMP, 4.7.2   M      

Table 26: Adaptive Frequency Hopping

Prerequisite: 2/16
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of AFH switch as master  LMP, 4.1.4   O      
Support of AFH switch as slave  LMP, 4.1.4   M      
Support of Channel Classification reporting - post Role Switch (as Slave)  LMP, 4.1.5   C.1      
Support of Channel Classification reporting as slave  LMP, 4.1.5   C.2      
Support channel classification from host  LMP, 4.1.5   C.3      
Support of Channel Classification  LMP, 4.1.5   O      
C.1: Optional if 26/6 is supported, otherwise Excluded.
C.2: Mandatory if 26/6 is supported, otherwise Excluded.
C.3: Mandatory if 26/1 or 26/4 is supported, otherwise Optional.

Table 27: This Table is intentionally left blank.
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
This line is intentionally left blank.  N/A   O      
This line is intentionally left blank.  N/A   O      
N/A  N/A   O      
N/A  N/A   O      





  Logical Link Control and Adaptation Protocol   
  Vol 3, Part A  



1.3.1 Roles   [ top ]

Table 0: Device Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
BR/EDR  1.1, [1] [2]   C.1      
Bluetooth low energy only  1.1, [2]   C.2      
BR/EDR/Bluetooth low energy  1.1, [2]   C.3      
C.1 Mandatory if (PROD 1/1 or 1/4) and ( PROD 3/1 or 3/2) are Supported (End Product or Host Subsystem with BR or BR/HS Host CC), otherwise Excluded. Optional for PROD 1/2 or 1/3 (Components).
C.2 Mandatory if (PROD 1/1 or 1/4) and (PROD 3/3) are Supported (End Product or Host Subsystem with LE Host CC), otherwise excluded. Optional for PROD 1/2 or 1/3 (Components).
C.3 Mandatory if (PROD 1/1 or 1/4) and (PROD 3/4 or 3/5) are Supported (End Product or Host Subsystem with BR/LE or BR/HS/LE Host CC), otherwise excluded. Optional for PROD 1/2 or 1/3 (Components).
Note - Only one transport shall be supported.

Table 1: Roles
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Data Channel Initiator  L2CAP   C.3      
Data Channel Acceptor  L2CAP   C.1      
LE Master  L2CAP   C.2      
LE Slave  L2CAP   C.2      
C.1: Mandatory if (0/1 or 0/3) is supported, otherwise Excluded.
C.2: Mandatory to support at least one of (1/3 or 1/4) if (0/2 OR 0/3) is supported, otherwise Excluded.
C.3: Optional if (L2CAP 0/1 OR L2CAP 0/3) is claimed, ELSE Excluded.


1.3.2 General Operation   [ top ]

Table 2: General Operation

"L2CAP" Reference applies to either [1] Core Specification v3.0+HS or [2] Core Specification v4.0.
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of L2CAP signalling channel  L2CAP, 2.2   C.20      
Support of configuration process  L2CAP, 7.1   C.20      
Support of connection oriented data channel  L2CAP, 2.2   C.20      
Support of command echo request  L2CAP, 4.8   C.21      
Support of command echo response  L2CAP, 4.9   C.20      
Support of command information request  L2CAP, 4.10   C.21      
Support of command information response  L2CAP, 4.11   C.20      
Support of a channel group  L2CAP, 2.2   C.21      
Support of packet for connectionless channel  L2CAP, 3.2   C.21      
10  Support retransmission mode  L2CAP, 8.5   C.21      
11  Support flow control mode  L2CAP, 8.5   C.21      
12  Enhanced Retransmission Mode  L2CAP, 8.6   C.1, C.13      
13  Streaming Mode  L2CAP, 8.7   C.1, C.14      
14  FCS Option  L2CAP, 5.5   C.2      
15  Generate Local Busy Condition  L2CAP, 8.6.4.3   C.3      
16  Send Reject  L2CAP 8.6.1.2   C.3      
17  Send Selective Reject  L2CAP 8.6.1.3   C.3      
18  Mandatory use of ERTM  L2CAP, 8.6   C.4      
19  Mandatory use of Streaming Mode  L2CAP, 8.7   C.5      
20  Optional use of ERTM  L2CAP, 8.6   C.4      
21  Optional use of Streaming Mode  L2CAP, 8.7   C.5      
22  Send data using SAR in ERTM  L2CAP, 3.3.2   C.6      
23  Send data using SAR in Streaming Mode  L2CAP, 3.3.2   C.7      
24  Actively request Basic Mode for a PSM that supports the use of ERTM or Streaming Mode   L2CAP, 5.4   C.8      
25  Supports performing L2CAP channel mode configuration fallback from SM to ERTM   L2CAP, 5.4   C.9      
26  Supports sending more than one unacknowledged I-Frame when operating in ERTM   L2CAP, 8.6.5   C.10      
27  Supports sending more than three unacknowledged I-Frame when operating in ERTM   L2CAP, 8.6.5   C.10      
28  Supports configuring the peer TxWindow greater than 1.   L2CAP, 5.4   C.11      
29  AMP Support  L2CAP, 9   C.12      
30  Fixed Channel Support  L2CAP, 2.1   C.12      
31  AMP Manager Support  L2CAP 2.1   C.12      
32  ERTM over AMP  L2CAP, 9   C.12      
33  Streaming Mode Source over AMP Support  L2CAP, 3.3, 8.7   C.15      
34  Streaming Mode Sink over AMP Support  L2CAP, 3.3, 8.7   C.15      
35  Unicast Connectionless Data, Reception  L2CAP, 3.3, L2CAP, 7.6   C.1, C.16      
36  Ability to transmit an unencrypted packet over a unicast connectionless L2CAP channel  L2CAP, 7.6   C.16      
37  Ability to transmit an encrypted packet over a unicast connectionless L2CAP channel.  L2CAP, 7.6, GAP, 5.2.2   C.16      
38  Extended Flow Specification for BR/EDR  L2CAP, 7.10   C.8      
39  Extended Window Size  L2CAP, 5.7   C.8      
40  Support of Low Energy signaling channel  [2], 2.1, 2.2   C.17      
41  Support of command reject  [2], 4.10   C.17      
42  Send Connection Parameter Update Request  [2], 4.20   C.18      
43  Send Connection Parameter Update Response  [2], 4.21   C.19      
44  Extended Flow Specification for AMP  [1], 5.6   C.22      
C.1: Mandatory to support at least one of (2/12 or 2/13 or 2/35) if (0/1 or 0/3) and (CSA 7 or Core Spec 3.0 or later) is supported, otherwise Excluded.
C.2: Optional if (2/12 or 2/13) is supported, otherwise Excluded.
C.3: Optional if 2/12 and 2/28 are supported, otherwise Excluded.
C.4: If 2/12 is supported then at least one of (2/18 or 2/20) is Mandatory, otherwise Excluded.
C.5: If 2/13 is supported then at least one of (2/19 or 2/21) is Mandatory, otherwise Excluded.
C.6: Optional if 2/12 is supported, otherwise Excluded.
C.7: Optional if 2/13 is supported, otherwise Excluded.
C.8: Optional if (2/12 or 2/13) is supported, otherwise Excluded.
C.9: Mandatory if (2/12 and 2/13 and 2/21) are supported, otherwise Excluded.
C.10: Optional if 2/12 is supported, otherwise Excluded.
C.11: Optional if 2/12 is supported, otherwise Excluded.
C.12: Mandatory if (SUM ICS 31/9) is supported, otherwise Optional.
C.13: Mandatory if (SUM ICS 31/9) is supported, otherwise Optional.
C.14: Optional if (Core Spec 3.0 or later) is supported, otherwise Excluded.
C.15: Optional if 2/29 is supported, otherwise Excluded.
C.16: Optional if (Core Spec 3.0 or later) is supported, otherwise Excluded.
C.17: Mandatory (0/2 OR 0/3) is supported, otherwise Excluded.
C.18: Optional if (Core Spec 4.0) and 1/4 is supported, otherwise Excluded.
C.19 : Mandatory if (Core Spec 4.0) and 1/3 is supported, otherwise Excluded.
C.20: Mandatory if (0/1 or 0/3) is supported, otherwise Excluded.
C.21: Optional if (0/1 or 0/3) is supported, otherwise Excluded.
C.22: Mandatory if 2/29 is supported, otherwise Excluded.


1.3.3 Configurable Parameters   [ top ]

Table 3: Configurable Parameters

"L2CAP" Reference applies to either [1] Core Specification v3.0+HS or [2] Core Specification v4.0.
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support of RTX timer  L2CAP, 6.2.1   M      
Support of ERTX timer  L2CAP, 6.2.2   C.4      
Support minimum MTU size 48 octets  L2CAP, 5.1   C.4      
Support MTU size larger than 48 octets  L2CAP, 5.1   C.5      
Support of flush timeout value for reliable channel  L2CAP, 5.2   C.4      
Support of flush timeout value for unreliable channel  L2CAP, 5.2   C.5      
Support of bi-directional quality of service (QoS) option field  L2CAP, 5.3   C.1      
Negotiate QoS service type  L2CAP, 5.3   C.5      
Negotiate and support service type 'No Traffic'  L2CAP, 5.3   C.2      
10  Negotiate and support service type 'Best effort'  L2CAP, 5.3   C.3      
11  Negotiate and support service type 'Gauranteed'  L2CAP, 5.3   C.2      
12  Support minimum MTU size 23 octets  [2], 5.1   C.6      
13  Negotiate and support service type ‘No traffic’ for Extended Flow Specification  [1], 5.6   C.7      
14  Negotiate and support service type ‘Best Effort’ for Extended Flow Specification  [1], 5.6   C.8      
15  Negotiate and support service type ‘Guaranteed’ for Extended Flow Specification.  [1], 5.6   C.9      
C.1: Mandatory if 3/8 is supported, otherwise Optional.
C.2: Optional if 3/8 is supported, otherwise Excluded.
C.3: Mandatory if 3/8 is supported, otherwise Excluded.
C.4: Mandatory if (0/1 or 0/3) is supported, otherwise Excluded.
C.5: Optional if (0/1 or 0/3) is supported, otherwise Excluded.
C.6: Mandatory if (0/2 or 0/3) is supported, otherwise Excluded.
C.7: Optional if (2/44 or 2/38) is supported, otherwise Excluded.
C.8: Mandatory if (2/44 or 2/38) is supported, otherwise Excluded.
C.9: Optional if (2/44 or 2/38) is supported, otherwise Excluded.





  Service Discovery Protocol  
  Vol 3, Part B  



1.3.1 UUID Capabilities   [ top ]

Table 1: Support Different Size Capabilities on UUID
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for 128 bit UUID  SDP, 2.7.1   M      
Support for 32 bit UUID  SDP, 2.7.1   M      
Support for 16 bit UUID  SDP, 2.7.1   M      

Table 1b: Roles
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for server role  SDP, 2.1   C.1      
Support for client role  SDP, 2.1   C.1      
C.1: Mandatory to support at least one of the defined roles.


1.3.2 Service Search Request PDU   [ top ]

Table 2: Valid Service Search Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for respond on search of single Service, using ServiceSearchRequest.  SDP, 4.5   C.2      
Support for respond on search of Service, using continuation state  SDP, 4.5   O      
Search for services using the continuation state.  SDP, 4.3   C.1      
C.1: Mandatory if 1b/2 is supported.
C.2: Mandatory if 1b/1 is supported.

Table 3: Invalid Service Search Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for error response on Service search request.  SDP, 4.4   M      


1.3.3 Service Attribute Request PDU   [ top ]

Table 4: Valid Service Attribute Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for respond on search of Attribute(s)  SDP, 4.6   M      
Support for respond on search of Attribute, using continuation state.  SDP, 4.6   O      
Support for respond on search on attribute AdditionalProtocolDescriptorList  SDP, 4.5, 5.1.6   O      

Table 5: Invalid Service Attribute Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for error response on Attribute search request.  SDP, 4.4   M      


1.3.4 Service Search Attribute Request PDU   [ top ]

Table 6: Valid Service Search Attribute Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for respond on search for Service(s) and Attribute(s)  SDP, 4.7   M      
Support for respond on search of Attribute, using continuation state.  SDP, 4.7   O      
Support for respond on search on attribute AdditionalProtocolDescriptorList on existing service  SDP, 4.7, 5.1.6   O      

Table 7: Invalid Service Search Attribute Request
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for error response on Service and Attribute request.  SDP, 4.4   M      


1.3.5 Service Browsing   [ top ]

Table 8: Service Browsing
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support for browsing, using SDP_ServiceSearchRequest and SDP_ServiceAttributeRequest  SDP, 4.5
SDP, 4.6
SDP, 2.8  
O      
Support for browsing, using SDP_ServiceSearchAttributeRequest  SDP, 4.7 SDP, 2.8   O      


1.3.6 Attributes   [ top ]

Table 9: Attributes Present in IUT
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
ServiceID  SDP, 5.1.4   O      
ProtocolDescriptorList  SDP, 5.1.5   O      
ServiceRecordState  SDP, 5.1.3   O      
ServiceInfoTimeToLive  SDP, 5.1.9   O      
BrowseGroupList  SDP, 5.1.7   O      
LanguageBaseAttributedIdList  SDP, 5.1.8   O      
ServiceAvailability  SDP, 5.1.10   O      
IconURL  SDP, 5.1.14   O      
ServiceName  SDP, 5.1.15   O      
10  ServiceDescription  SDP, 5.1.16   O      
11  ProviderName  SDP, 5.1.17   O      
12  VersionNumberList  SDP, 5.2.3   O      
13  ServiceDataBaseState  SDP, 5.2.4   O      
14  BluetoothProfileDescriptorList  SDP, 5.1.11   O      
15  DocumentationURL  SDP, 5.1.12   O      
16  ClientExecutableURL  SDP, 5.1.13   O      
17  AdditionalProtocolDescriptorList  SDP, 5.1.6   C.1      
18  ServiceRecordHandle  SDP, 5.1.1   M      
19  ServiceClassIDList  SDP, 5.1.2   M      
C.1: Optional if 9/2 is supported, otherwise Excluded.





  Generic Access Profile  
  Vol 3, Part C  



Modes   [ top ]

Table 0: Device Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
BR/EDR  [1] or [2], 1.1   C.1      
LE  [2], 1.1   C.2      
BR/EDR/LE  [2], 1.1   C.3      
C.1: Mandatory if (PROD 1/1 or 1/4) and (PROD 3/1 or 3/2) are Supported (End Product or Host Subsystem with BR or BR/HS Host CC), otherwise excluded. Optional for PROD 1/2 or 1/3 (Components).
C.2: Mandatory if (PROD 1/1 or 1/4) and (PROD 3/3) are Supported (End Product or Host Subsystem with LE Host CC), otherwise excluded. Optional for PROD 1/2 or 1/3 (Components).
C.3: Mandatory if (PROD 1/1 or 1/4) and (PROD 3/4 or 3/5) are Supported (End Product or Host Subsystem with BR/LE or BR/HS/LE Host CC), otherwise excluded. Optional for PROD 1/2 or 1/3 (Components).
Note - Only one transport shall be supported.

Table 0a: Version Configuration
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Core Specification Addendum 3 (CSA3), GAP Connection Parameters Changes, Authentication and Lost Bond Changes, Private Addressing Changes, Dual Mode Addressing Changes, Adopted 24 July 2012  CSA3   C.1      
Core Specification Addendum 4 (CSA4)  CSA4   C.2      
C.1: Mandatory if CSA 3 (SUM ICS 31/13) is supported, otherwise Excluded.
C.2: Mandatory if CSA4 (SUM ICS 31/13) is supported, otherwise Excluded.

Table 1: Modes

Prerequisite: 0/1 or 0/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-discoverable mode  GAP, 4.1.1   C.1      
Limited-discoverable mode  GAP, 4.1.2   O      
General-discoverable mode  GAP, 4.1.3   O      
Non-connectable mode  GAP, 4.2.1   O      
Connectable mode  GAP, 4.2.2   M      
Non-bondable mode  GAP, 4.3.1   O      
Bondable mode  GAP, 4.3.2   C.2      
Non-Synchronizable Mode  GAP, 4.4.1   C.3      
Synchronizable Mode  GAP, 4.4.2   C.4      
C.1: Mandatory if 1/2 is supported, otherwise Optional.
C.2: Mandatory if 3/5 is supported, otherwise Optional.
C.3: Mandatory if 0a/2 (CSA4) or later is supported, otherwise Excluded.
C.4: Optional if 0a/2 (CSA4) or later is supported; Mandatory if 0a/2 (CSA4) or later and BB 3a/1 are supported, otherwise Excluded.

Table 2: Security Aspects

Prerequisite: 0/1 or 0/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Authentication procedure  GAP, 5.1   C.1      
Support of LMP-Authentication  GAP, 5.1   M      
Initiate LMP-Authentication  GAP, 5.1   C.5      
Security mode 1  GAP, 5.2.1   C.2      
Security mode 2  GAP, 5.2.2   O      
Security mode 3  GAP, 5.2.3   C.7      
Security mode 4  GAP, 5.2.4   C.4      
Support of Authenticated link key  GAP, 5.2.4   C.6      
Support of Unauthenticated link key  GAP 5.2.4   C.6      
10  Security Optional  GAP 5.2.4.   C.6      
C.1: Mandatory If (2/5 or 2/6) is supported, otherwise Optional.
Note 1: The Authentication Procedure in item GAP, 2/1 is the one described in Fig. 5.1 on page 198 in the GAP Profile Specification and not the LMP-Authenticaion.
C.2: Excluded if 2/7 is supported, otherwise Optional.
C.5: Mandatory If (2/5 or 2/6 or 2/7) is supported, otherwise Optional.
C.4: Mandatory if (Core Spec 2.1 or later) is supported, otherwise Excluded.
Note 2. If a Core 2.0 and earlier design claims to support secure communcation it should support either Security mode 2 or 3.
Note 3. A Core 2.1 or later device shall always support secure communication in Security Mode 4, and shall use that mode to connect with another Core 2.1 or later device. It shall use Security Mode 2 only for backward compatibility purposes with Core 2.0 and earlier devices. Security Mode 1 is excluded for Core 2.1 or later devices based on condition C.2.
C.6: If 2/7 is supported then at least one of (2/8 or 2/9 or 2/10) is Mandatory, otherwise Excluded.
C.7: Excluded if if 2/7 is supported, otherwise Optional.

Table 3: Idle Mode Procedures

Prerequisite: 0/1 or 0/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Initiation of general inquiry  GAP, 6.1   C.1      
Initiation of limited inquiry  GAP, 6.2   C.1      
Initiation of name discovery  GAP, 6.3   O      
Initiation of device discovery  GAP, 6.4   O      
Initiation of general bonding  GAP, 6.5   O      
Initiation of dedicated bonding  GAP, 6.5   O      
C.1: Mandatory to support at least one of GAP 3/1 (Initiation of general inquiry) or GAP 3/2 (Initiation of limited inquiry) if GAP 3/5 (Initiation of general bonding) is supported, otherwise Optional.

Table 4: Establishment Procedures

Prerequisite: 0/1 or 0/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support link establishment as initiator  GAP, 7.1   M      
Support link establishment as acceptor  GAP, 7.1   M      
Support channel establishment as initiator  GAP, 7.2   O      
Support channel establishment as acceptor  GAP, 7.2   M      
Support connection establishment as initiator  GAP, 7.3   O      
Support connection establishment as acceptor  GAP, 7.3   O      
Support synchronization establishment as receiver  GAP, 7.5   C.1      
C.1: Optional if 0a/2 (CSA4) or later is supported; Mandatory if 0a/2 (CSA4) or later and BB 3a/2 (Connectionless Slave Broadcast Receiver) are supported, otherwise Excluded.

Table 5: LE Roles

Prerequisite: 0/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Broadcaster  [2], 2.2.2   C.1      
Observer  [2], 2.2.2   C.1      
Peripheral  [2], 2.2.2   C.1      
Central  [2], 2.2.2   C.1      
C.1: It is mandatory to support at least one of the defined roles.
Note: Table 5 is applicable for LE-only configurations. For BR/EDR/LE configurations, see Table 38 for role declarations.

Table 6: Broadcaster Physical Layer

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Transmitter  [2], 2.2.2   M      
Receiver  [2], 2.2.2   O      

Table 7: Broadcaster Link Layer States

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Standby  [2], 2.2.2   M      
Advertising  [2], 2.2.2   M      

Table 8: Broadcaster Link Layer Advertising Event Types

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Connectable Undirected Event  [2], 2.2.2   M      
Scannable Undirected Event  [2], 2.2.2   O      

Table 8a: Broadcaster Link Layer Advertising Data Types

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
AD Type – Service UUID  [2] 11.1.1, [3] 1.1   O      
AD Type – Local Name  [2] 11.1.2, [3] 1.2   O      
AD Type – Flags  [2] 11.1.3, [3] 1.3   M      
AD Type – Manufacturer Specific  [2] 11.1.4, [3] 1.4   O      
AD Type – TX Power Level  [2] 11.1.5, [3] 1.5   O      
AD Type – Security Manager Out of Band (OOB)  [2] 11.1.6, [3] 1.6   C.1      
AD Type – Security Manager TK  [2] 11.1.7, [3] 1.7   O      
AD Type – Slave Connection  [2] 11.1.8, [3] 1.8   O      
AD Type - Service Solicitation  [2] 11.1.9, [3] 1.9   O      
10  AD Type – Service Data  [2] 11.1.10, [3] 1.10   O      
C.1: Optional if SM 2/4 (OOB supported) is supported, otherwise Excluded.

Table 9: Broadcaster Connection Modes and Procedures

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Connectable Mode  [2] 9.3.2   M      

Table 10: Broadcaster Broadcasting and Observing Features

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Broadcast Mode  [2] 9.1.1   M      

Table 11: Broadcaster Privacy Feature

Prerequisite: 5/1 or 38/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Privacy Feature  GAP 10.7   O      
Resolvable Private Address Generation Procedure  GAP 10.8.2.2   C.1      
C.1: Mandatory if 11/1 is supported, otherwise Excluded.

Table 12: Observer Physical Layer

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Receiver  [2], 2.2.2   M      
Transmitter  [2], 2.2.2   O      

Table 13: Observer Link Layer States

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Standby  [2], 2.2.2   M      
Scanning  [2], 2.2.2   M      

Table 14: Observer Link Layer Scanning Types

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Passive Scanning  [2], 2.2.2   M      
Active Scanning  [2], 2.2.2   O      

Table 15: Observer Connection Modes and Procedures

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Connectable Modes  [2], 9.3.2   M      

Table 16: Observer Broadcasting and Observing Features

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Observation Procedure  [2], 9.1.2   M      

Table 17: Observer Privacy Feature

Prerequisite: 5/2 or 38/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Privacy Feature  [2], 10.7   O      
Non-Resolvable Private Address Generation Procedure  [2], 10.8.2.1   C.1      
Resolvable Private Address Resolution Procedure  [2], 10.8.2.3   C.2      
Resolvable Private Address Generation Procedure  [2] 10.8.2.2   C.3      
C.1: Mandatory if 17/1 (Privacy Feature) and 14/2 (Active Scanning) are supported and 17/4 (Resolvable Private Address Generation Procedure) is Not Supported; Optional if CSA3 or later and 17/4 are supported, otherwise Excluded.
C.2: Optional if 17/1 (Privacy Feature) is supported, otherwise Excluded.
C.3: Mandatory if CSA3 or later and 17/1 (Privacy Feature) and 14/2 (Active Scanning) are supported and 17/2 (Non-Resolvable Private Address Generation Procedure) is not supported; Optional if CSA3 or later and 17/2 (Non-Resolvable Private Address Generation Procedure) are supported, otherwise Excluded.

Table 18: Peripheral Physical Layer

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Transmitter  [2], 2.2.2   M      
Receiver  [2], 2.2.2   M      

Table 19: Peripheral Link Layer States

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Standby  [2], 2.2.2   M      
Advertising  [2], 2.2.2   M      
Connection, Slave Role  [2], 2.2.2   M      

Table 20: Peripheral Link Layer Advertising Event Types

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Connectable Undirected Event  [2], 2.2.2   M      
Connectable Directed Event  [2], 2.2.2   O      
Non-Connectable Undirected Event  [2], 2.2.2   O      
Scannable Undirected Event  [2], 2.2.2   M      

Table 20A: Peripheral Link Layer Advertising Data Types

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
AD Type – Service UUID  11.1.1   C.1      
AD Type – Local Name  11.1.2   C.1      
AD Type – Flags  11.1.3   C.2      
AD Type – Manufacturer Specific Data  11.1.4   C.1      
AD Type – TX Power Level  11.1.5   C.1      
AD Type – Security Manager Out of Band (OOB)  11.1.6   C.3      
AD Type – Security Manager TK Value  11.1.7   C.1      
AD Type – Slave Connection Interval Range  11.1.8   C.1      
AD Type - Service Solicitation  11.1.9   C.1      
10  AD Type – Service Data  11.1.10   C.1      
C.1: Optional if (20/1 or 20/3 or 20/4) is supported, otherwise Excluded.
C.2: Mandatory if 22/2 (Limited Discoverable Mode) or 22/3 (General Discoverable Mode) is supported, otherwise Optional.
C.3: Optional if (20/1 (Connectable Undirected Event) or 20/3 (Non-Connectable Undirected Event) or 20/4 (Scannable Undirected Event)) and SM 2/4 (OOB supported) are supported, otherwise Excluded.

Table 21: Peripheral Link Layer Control Procedures

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Connection Update Procedure  [2], 2.2.2   M      
Channel Map Update Procedure  [2], 2.2.2   M      
Encryption Procedure  [2], 2.2.2   O      
Feature Exchange Procedure  [2], 2.2.2   M      
Version Exchange Procedure  [2], 2.2.2   M      
Termination Procedure  [2], 2.2.2   M      

Table 22: Peripheral Discovery Modes and Procedures

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Discoverable Mode  [2], 9.2.2   C.2      
Limited Discoverable Mode  [2], 9.2.3   C.1      
General Discoverable Mode  [2], 9.2.4   C.1      
Name Discovery Procedure  [2], 9.2.7   C.3      
C.1: Optional if (5/3 OR 42/2), otherwise Excluded.
C.2: Mandatory if (5/3 or 42/1) is supported, otherwise Excluded.
C.3: Optional if 5/3 is supported, otherwise Excluded.

Table 23: Peripheral Connection Modes and Procedures

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Connectable Mode  [2], 9.3.2   C.1      
Directed Connectable Mode  [2], 9.3.3   O      
Undirected Connectable Mode  [2], 9.3.4   M      
Connection Parameter Update Procedure  [2], 9.3.9   O      
Terminate Connection Procedure  [2], 9.3.10   M      
C.1: Mandatory if 5/3 (LE Only – Peripheral role) OR 42/3 (BR/EDR/LE – Non-Connectable Mode) OR 42/4 (BR/EDR/LE – Connectable Mode) is supported, otherwise Excluded.

Table 24: Peripheral Bonding Modes and Procedures

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Bondable Mode  [2], 9.4.2   M      
Bondable Mode  [2], 9.4.3   C.1      
Bonding Procedure  [2], 9.4.4   C.1      
Multiple Bonds  [2.] 9.4   C.2      
C.1: Optional if 5/3 (LE Only – Peripheral role) OR (38/3 (BR/EDR/LE – Peripheral role) AND NOT 42/6 (BR.EDR/LE - Bondable Mode)) is supported, Mandatory if 42/6 (BR/EDR/LE – Bondable Mode) is supported, otherwise Excluded.
C.2: Optional if 24/2 (Bondable Mode) is supported, otherwise Excluded.

Table 25: Peripheral Security Aspects Features

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Mode 1  [2], 10.2.1   O      
Security Mode 2  [2], 10.2.2   O      
Authentication Procedure  [2], 10.3   C.2      
Authorization Procedure  [2], 10.5   O      
Connection Data Signing Procedure  [2], 10.4.1   O      
Authenticate Signed Data Procedure  [2], 10.4.3   O      
Authenticated Pairing (LE security mode 1 level 3)  [2.] 10.3   C.1      
Unauthenticated Pairing (LE security mode 1 level 2)  [2.]10.3   C.1      
C.1: Optional if 25/1 is supported, otherwise Excluded.
C.2: Mandatory if 0a/1 and 27/4 are supported, otherwise Optional.

Table 26: Peripheral Privacy Feature

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Privacy Feature  [2], 10.7   O      
Non-Resolvable Private Address Generation Procedure  [2], 10.8.2.1   C.1      
Resolvable Private Address Generation Procedure  [2], 10.8.2.2   C.2      
C.1: Optional if 26/1 is supported, otherwise Excluded.
C.2: Mandatory if 26/1 is supported, otherwise Excluded.

Table 27: Peripheral GAP Characteristics

Prerequisite: 5/3 or 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Device Name  [2], 12.1   M      
Appearance  [2], 12.2   M      
Peripheral Privacy Flag  [2], 12.3   C.1      
Reconnection Address  [2], 12.4   C.2      
Peripheral Preferred Connection Parameters  [2], 12.5   O      
Writeable Device Name  [2], 12.1   O      
Writeable Appearance  [2], 12.2   O      
Writeable Peripheral Privacy Flag  [2.] 12.3, 10.7.1   O      
C.1: Mandatory if 26/1 is supported, otherwise Excluded.
C.2: Optional if 26/1 and 27/3 are supported, otherwise Excluded.

Table 28: Central Physical Layer

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Transmitter  [2], 2.2.2   M      
Receiver  [2], 2.2.2   M      

Table 29: Central Link Layer States

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Standby  [2], 2.2.2   M      
Scanning  [2], 2.2.2   M      
Initiating  [2], 2.2.2   M      
Connection, Master Role  [2], 2.2.2   M      

Table 30: Central Link Layer Scanning Types

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Passive Scanning  [2], 2.2.2   O      
Active Scanning  [2], 2.2.2   C.1      
C.1: Mandatory if (5/4 or 38/4) is supported. Optional if 30/1 and (5/4 OR 38/4) is supported, otherwise Excluded.

Table 31: Central Link Layer Control Procedures

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Connection Update Procedure  [2], 2.2.2   M      
Channel Map Update Procedure  [2], 2.2.2   M      
Encryption Procedure  [2], 2.2.2   O      
Feature Exchange Procedure  [2], 2.2.2   M      
Version Exchange Procedure  [2], 2.2.2   M      
Termination Procedure  [2], 2.2.2   M      

Table 32: Central Discovery Modes and Procedures

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Limited Discovery Procedure  [2], 9.2.5   C.2      
General Discovery Procedure  [2], 9.2.6   C.1      
Name Discovery Procedure  [2], 9.2.7   C.3      
C.1: Mandatory if (5/4 or 40/1) is supported, else Excluded.
C.2: Optional if (5/4 or 40/2) is supported, otherwise Excluded.
C.3: Optional if (5/4 or 40/4) is supported, otherwise Excluded.

Table 33: Central Connection Modes and Procedures

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Auto Connection Establishment Procedure  [2], 9.3.5   C.3      
General Connection Establishment  [2], 9.3.6   C.1      
Selective Connection Establishment  [2], 9.3.7   C.3      
Direct Connection Establishment  [2], 9.3.8   C.2      
Connection Parameter Update Procedure  [2], 9.3.9   C.2      
Terminate Connection Procedure  [2], 9.3.10   C.2      
C.1: Mandatory if (5/4 or 40/5) and 36/1 is supported, otherwise Optional.
C.2: Mandatory if (5/4 or 40/5) is supported, otherwise Excluded.
C.3: Optional if (5/4 or 40/5) is supported, otherwise Excluded.

Table 34: Central Bonding Modes and Procedures

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Bondable Mode  [2], 9.4.2   C.1      
Bondable Mode  [2], 9.4.3   C.2      
Bonding Procedure  [2], 9.4.4   O      
C.1: Mandatory if (5/4 or 39/5) is supported, otherwise Excluded.
C.2: Optional if (5/4 or 39/6) is supported, otherwise Excluded.

Table 35: Central Security Features

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Mode 1  [2], 10.2.1   O      
Security Mode 2  [2], 10.2.2   O      
Authentication Procedure  [2], 10.3   O      
Authorization Procedure  [2], 10.5   O      
Connection Data Signing Procedure  [2], 10.4.1   O      
Authenticate Signed Data Procedure  [2], 10.4.3   O      
Authenticated Pairing (LE security mode 1 level 3)  [2.] 10.3   C.1      
Unauthenticated Pairing (LE security mode1 level2)  [2.] 10.3   C.1      
C.1: Optional if 35/1 is supported, otherwise Excluded.

Table 36: Central Privacy Feature

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Privacy Feature  [2], 10.7   C.3      
Non-Resolvable Private Address Generation Procedure  [2], 10.8.2.1   C.1      
Resolvable Private Address Resolution Procedure  [2], 10.8.2.3   C.2      
Write to Privacy Characteristic (Enable/Disable Privacy)  [2.] 10.7.1, 10.7.2   O      
C.1: Mandatory if 36/1 and 30/2 are supported, otherwise Excluded.
C.2: Mandatory if 36/1 is supported, otherwise Excluded.

Table 37: Central GAP Characteristics

Prerequisite: 5/4 or 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Device Name  [2], 12.1   M      
Appearance  [2], 12.2   M      
C.1: Mandatory if (5/4 or 38/4) is supported, otherwise Excluded.

Table 38: BR/EDR/LE Roles

Prerequisite: 0/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Broadcaster  [2], 13   C.1      
Observer  [2], 13   C.1      
Peripheral  [2], 13   C.1      
Central  [2], 13   C.1      
C.1: It is mandatory to support at least one of the defined roles.
Note: Table 38 is applicable for BR/EDR/LE configurations. For LE-only configurations, see Table 5 for role declarations.

Table 39: Central BR/EDR/LE Modes

Prerequisite: 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Discoverable Mode  [2], 13.1.1.1   C.1      
Discoverable Mode  [2], 13.1.1.2   C.2      
Non-Connectable Mode  [2], 13.1.2.1   C.3      
Connectable Mode  [2], 13.1.2.2   M      
Non-Bondable Mode  [2], 13.1.3.1   C.4      
Bondable Mode  [2], 13.1.3.2   C.5      
C.1: Mandatory if 1/1 is supported over BR/EDR, otherwise Excluded.
C.2: Mandatory if (1/2 or 1/3) is supported over BR/EDR, otherwise Excluded.
C.3: Mandatory if 1/4 is supported over BR/EDR, otherwise Excluded.
C.4: Mandatory if 1/6 is supported over BR/EDR, otherwise Excluded.
C.5: Mandatory if 1/7 is supported over BR/EDR, otherwise Excluded.

Table 40: Central BR/EDR/LE Idle Mode Procedures

Prerequisite: 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
General Discovery  [2], 13.2.1   C.1      
Limited Discovery  [2], 13.2.2   C.2      
Device Type Discovery  [2], 13.2.3.1   C.3      
Name Discovery  [2], 13.2.4   C.4      
Link Establishment  [2], 13.3   C.5      
C.1: Mandatory if 3/1 is supported over BR/EDR, otherwise Excluded.
C.2: Mandatory if 3/2 is supported over BR/EDR, otherwise Excluded.
C.3: Mandatory if (3/1 or 3/2) is supported over BR/EDR, otherwise Excluded.
C.4: Mandatory if 3/3 is supported over BR/EDR, otherwise Excluded.
C.5: Mandatory if (4/1 or 4/2) is supported over BR/EDR, otherwise Excluded.

Table 41: Central BR/EDR/LE Security Aspects

Prerequisite: 38/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Aspects  [2], 14   M      

Table 42: Peripheral BR/EDR/LE Modes

Prerequisite: 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Discoverable Mode  [2], 13.1.1.1   C.1      
Discoverable Mode  [2], 13.1.1.2   C.2      
Non-Connectable Mode  [2], 13.1.2.1   C.3      
Connectable Mode  [2], 13.1.2.2   M      
Non-Bondable Mode  [2], 13.1.3.1   C.4      
Bondable Mode  [2], 13.1.3.2   C.5      
C.1: Mandatory if 1/1 is supported over BR/EDR, otherwise Excluded.
C.2: Mandatory if (1/2 or 1/3) is supported over BR/EDR, otherwise Excluded.
C.3: Mandatory if 1/4 is supported over BR/EDR, otherwise Excluded.
C.4: Mandatory if 1/6 is supported over BR/EDR, otherwise Excluded.
C.5: Mandatory if 1/7 is supported over BR/EDR, otherwise Excluded.

Table 43: Peripheral BR/EDR/LE Security Aspects

Prerequisite: 38/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Aspects  [2], 14   M      





  Link Layer  
  Vol 6, Part B  



Controller States/Roles   [ top ]

Table 1: Controller States/Roles
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Advertising State  [1]: 4.4.2   C.1      
Scanning State  [1]: 4.4.3   C.1      
Initiating State  [1]: 4.4.4   C.1      
Slave Role  [1]: 4.5.5   C.3      
Master Role  [1]: 4.5.4   C.2      
C.1: Mandatory to support at least one of (1/1 or 1/2 or 1/3).
C.2 Mandatory if 1/3 is supported.
C.3: Optional if 1/1 is supported, otherwise Excluded.

Table 2: Device Addresses Types

Prerequisite: 1/1 or 1/2 or 1/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Public Address  [1]: 1.3   C.1      
Random Address  [1]: 1.3   C.1      
C.1: Mandatory if (2/1 or 2/2) is supported.
Note: Condition C.1 means that an observer device only does not need a device address, any other does but the type selection is not constrained.

Table 3: Protocol Advertising Features

Prerequisite: 1/1
(This section shall only be completed if 1/1 is supported)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Non-Connectable Undirected Events  [1]: 4.4.2.6   C.1      
Connectable Undirected Events  [1]: 4.4.2.3   C.2      
Advertising Data  [1]: 4.4.2.3, 4.4.2.5, 4.4.2.6   M      
Connectable Directed Events  [1]: 4.4.2.4   C.3      
Scannable Undirected Events  [1]: 4.4.2.5   C.4      
Sending Scan Responses  [1]: 4.4.2.3, 4.4.2.5    M      
Accepting Connection Requests  [1]: 4.4.2.3, 4.4.2.4    M      
Filtering Policies  [1]: 4.3.2   O      
The following conditionals define the requirements imposed on a design’s GAP role support. If you are qualifying a Controller Subsystem or Component product type, these conditionals may not be applicable to your design, but should be considered before implementation.
C.1: Mandatory if GAP 5/1 (Broadcaster) is supported; Optional if GAP 5/3 (Peripheral), otherwise Not Defined.
C.2: Mandatory if GAP 5/3 (Peripheral) is supported, otherwise Not Defined.
C.3: Optional if GAP 5/3 (Peripheral), otherwise Not Defined.
C.4: Optional if GAP 5/1 (Broadcaster) or GAP 5/3 (Peripheral) is supported, otherwise Not Defined.

Table 4: Protocol Scanning Features

Prerequisite: 1/2
(This section shall only be completed if 1/2 is supported)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Passive Scanning  [1]: 4.4.3.1    C.1      
Receiving Advertising Data  [1]: 4.4.3.1, 4.4.3.2    M      
Active Scanning  [1]: 4.4.3.2    C.2      
Backoff Procedure  [1]: 4.4.3.2    M      
Filtering Policies  [1]: 4.3.3    O      
The following conditionals define the requirements imposed on a design’s GAP role support. If you are qualifying a Controller Subsystem or Component product type, these conditionals may not be applicable to your design, but should be considered before implementation.
C.1: Mandatory if GAP 5/2 (Observer) is supported; Optional if GAP 5/4 (Central), otherwise Not Defined.
C.2: Optional if GAP 5/2 (Observer) is supported; Mandatory if (GAP 5/4 and NOT LL4/7) is supported, otherwise Not Defined.

Table 5: Protocol Initiating Features

Prerequisite: 1/3
(This section shall only be completed if 1/3 is supported)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Requesting Connections  [1]: 4.4.4   M      
Requesting to Directed Advertising  [1]: 4.4.4   M      
Initiator Filtering  [1]: 4.3.4   M      

Table 6: Protocol Slave Role Features

Prerequisite: 1/4
(This section shall only be completed if 1/4 is supported)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Slave Transmissions  [1]: 4.5.1, 4.5.5, 4.5.6   M      
Acknowledgement Scheme  [1]: 4.5.9   M      
Unknown Response  [1]: 5.1.4, 2.4.2   M      
Responding in Feature Setup  [1]: 5.1.4   M      
Sending Data  [1]: 4.5.1, 4.5.6   M      
Receiving Data  [1]: 4.5.1, 4.5.6   M      
More Data  [1]: 4.5.6   O      
HCI Fragmentation  [2]: 5   O      
LL Defragmentation  [2]: 5   O      
10  Accepting Parameter Update  [1]: 5.1.1   M      
11  Accepting Channel Map Update  [1]: 5.1.2   M      
12  Encryption Start  [1]: 5.1.3   O      
13  Connection Control Timer  [1]: 5.2   M      
14  Sending Termination  [1]: 5.1.6   M      
15  Accepting Termination  [1]: 5.1.6   M      
16  Connection Supervision Timer  [1]: 4.5.2   M      
17  (Intentionally left blank)        
18  Slave Pause Encryption  [1]: 5.1.3   O      
19  Slave Version Exchange  [1]: 5.1.5   M      
20  Slave listens to multiple packets per connection event  4.5.7   O      
LL 6/5 indicates whether a device in the slave role supports data output from a Host.
LL 6/6 indicates whether the device supports data input to a Host.
LL 6/9 expresses if a Controller may recombine LL packets into HCI data packets.
Carrying HCI fragmentation flags in LL packets is indicated by LL 6/8.

Table 7: Protocol Master Role Features

Prerequisite: 1/5
(This section shall only be completed if 1/5 is supported)
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Master Transmissions  [1]: 4.5.1, 4.5.4, 4.5.6   M      
Acknowledgement Scheme  [1]: 4.5.9   M      
Unknown Responses  [1]: 5.1.4, 2.4.2   M      
Requesting Feature Setup  [1]: 5.1.4   M      
Sending Data  [1]: 4.5.1, 4.5.6   M      
Receiving Data  [1]: 4.5.1, 4.5.6   M      
More Data  [1]: 4.5.6   O      
HCI Fragmentation  [2]: 5   O      
LL Defragmentation  [2]: 5   O      
10  Requesting Parameter Update  [1]: 5.1.1   M      
11  Requesting Channel Map Update  [1]: 5.1.2   M      
12  Encryption Start  [1]: 5.1.3   O      
13  Connection Control Timer  [1]: 5.2   M      
14  Sending Termination  [1]: 5.1.6   M      
15  Accepting Termination  [1]: 5.1.6   M      
16  Connection Supervision Timer  [1]: 4.5.2   M      
18  Master Non-Connectable Events  [1]: 4.4.2.6   O      
19  Master Pause Encryption  [1]: 5.1.3   O      
20  Master Version Exchange  [1]: 5.1.5   M      
LL 7/5 indicates whether a device in the master role supports data output from a Host.
LL 7/6 indicates whether the device supports data input to a Host.
LL 7/18 indicates whether a device supports combining the advertising procedure to the master role.

Table 8: Physical Channels
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Support frequency band and 40 physical channels  [1]:1.4   M      
Advertising channels (channel index 37, 38, 39)  [1]:1.4.1   M      
Support Data channel selection algorithm  [1]: 4.5.8   C.1      
C.1: Mandatory if (1/4 or 1/5) is supported, otherwise Excluded.

Table 9: Supported Features
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
LL Encryption  [1]: 4.6.1   C.1      
C.1: Mandatory if (6/12 and 6/18) or (7/12 and 7/19) are supported.





  RF PHY  
  Vol 6, Part A  



Capability Statement   [ top ]

Table 1: Bluetooth LE RF Capabilities
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
LE Transmitter (Non-connectable, Broadcaster)  [2], 3   C.1      
LE Receiver (Non-connectable, Observer)  [2], 4   C.1      
LE Transceiver (Connectable, Peripheral/Central)  [2], 3, 4   C.1      
C.1: At least one of the capabilities shall be supported.

Table 2: Bluetooth LE Test Interface Capabilities
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
HCI Test Interface  [3], 2   C.1      
UART Test Interface  [3], 3   C.1      
C.1: At least one of the capabilities shall be supported.





  Generic Attribute Profile  
  Vol 3, Part G  



Generic Attribute Profile Role   [ top ]

Table 1: Generic Attribute Profile Support
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Generic Attribute Profile Client   GATT 2.2   C.1      
Generic Attribute Profile Server  GATT 2.2   C.2      
Complete GATT Client layer  GATT   C.3      
Complete GATT Server layer  GATT   C.4      
C.1: Mandatory to support at least one of 1/1 or 1/2. If 2/2 is supported it is Optional to support 1/1.
C.2: If 2/1 is supported it is Mandatory to support at least one of 1/1 or 1/2. If 2/2 is supported it is Mandatory to support 1/2.
C.3: Optional if 1/1 is supported, otherwise Excluded.
C.4: Optional if 1/2 is supported, otherwise Excluded.
NOTE: Support of a complete GATT Client or Server indicates the implementation is designed to support all defined Generic Profile Attributes in Vol. 3, Part G, Section 3 of Core Specification 4.0 and later. Support for these features is recommended for designs intending to have GATT based Profiles and Services added after the design is distributed.





ATT Bearer Transport   [ top ]

Table 2: Attribute Protocol Transport
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Attribute Protocol Supported over BR/EDR (L2CAP fixed channel support)  GATT 2.2   C.1      
Attribute Protocol Supported over LE  GATT 2.2   C.2      
C.1: Mandatory if (PROD 3/1 or 3/2 or 3/4 or 3/5) is supported, otherwise Excluded. (Mandatory if Host CC contains BR)
C.2: Mandatory if (PROD 3/3 or 3/4 or 3/5) is supported, otherwise Excluded. (Mandatory if Host CC contains LE).





Generic Attribute Profile Support   [ top ]

Table 3: Generic Attribute Profile Feature Support, by client

Prerequisite: 1/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Exchange MTU  4.3.1   C.1      
Discover All Primary Services  4.4.1   C.1      
Discover Primary Services by Service UUID  4.4.2   C.1      
Find Included Services  4.5.1   C.1      
Discover All characteristics of a Service  4.6.1   C.1      
Discover Characteristics by UUID  4.6.2   C.1      
Discover All Characteristic Descriptors  4.7.1   C.1      
Read Characteristic Value  4.8.1   C.1      
Read Using Characteristic UUID  4.8.2   C.1      
10  Read Long Characteristic Values  4.8.3   C.1      
11  Read Multiple Characteristic Values  4.8.4   C.1      
12  Write without Response  4.9.1   C.1      
13  Signed Write Without Response  4.9.2   C.1      
14  Write Characteristic Value  4.9.3   C.1      
15  Write Long Characteristic Values  4.9.4   C.1      
16  Characteristic Value Reliable Writes  4.9.5   C.1      
17  Notifications  4.10.1   C.1      
18  Indications  4.11.1   M      
19  Read Characteristic Descriptors  4.12.1   C.1      
20  Read Long Characteristic Descriptors  4.12.2   C.1      
21  Write Characteristic Descriptors  4.12.3   C.1      
22  Write Long Characteristic Descriptors  4.12.4   C.1      
23  Service Changed Characteristic  7.1   M      
24  Configured Broadcast  2.7   C.2      
C.1: Mandatory if 1/3 is supported, otherwise Optional.
C.2: Optional if 3/14 is supported, otherwise Excluded.

Table 3B: Profile Attribute Types and Formats, by client

Prerequisite: 1/3
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Primary Service Declaration  3.1   M      
Secondary Service Declaration  3.1   M      
Include Declaration  3.2   M      
Characteristic Declaration  3.3.1   M      
Characteristic Value Declaration  3.3.2   M      
Characteristic Extended Properties  3.3.3.1   M      
Characteristic User Description Descriptor  3.3.3.2   M      
Client Characteristic Configuration Descriptor  3.3.3.3   M      
Server Characteristic Configuration Descriptor  3.3.3.4   M      
10  Characteristic Format Descriptor  3.3.3.5   M      
11  Characteristic Aggregate Format Descriptor  3.3.3.6   M      
12  Characteristic Format: Boolean  3.3.3.5.2   M      
13  Characteristic Format: 2Bit  3.3.3.5.2   M      
14  Characteristic Format: nibble  3.3.3.5.2   M      
15  Characteristic Format: Uint8  3.3.3.5.2   M      
16  Characteristic Format: Uint12  3.3.3.5.2   M      
17  Characteristic Format: Uint16  3.3.3.5.2   M      
18  Characteristic Format: Uint24  3.3.3.5.2   M      
19  Characteristic Format: Uint32  3.3.3.5.2   M      
20  Characteristic Format: Uint48  3.3.3.5.2   M      
21  Characteristic Format: Uint64  3.3.3.5.2   M      
22  Characteristic Format: Uint128  3.3.3.5.2   M      
23  Characteristic Format: Sint8  3.3.3.5.2   M      
24  Characteristic Format: Sint12  3.3.3.5.2   M      
25  Characteristic Format: Sint16  3.3.3.5.2   M      
26  Characteristic Format: Sint24  3.3.3.5.2   M      
27  Characteristic Format: Sint32  3.3.3.5.2   M      
28  Characteristic Format: Sint48  3.3.3.5.2   M      
29  Characteristic Format: Sint64  3.3.3.5.2   M      
30  Characteristic Format: Sint128  3.3.3.5.2   M      
31  Characteristic Format: Float32  3.3.3.5.2   M      
32  Characteristic Format: Float64  3.3.3.5.2   M      
33  Characteristic Format: SFLOAT  3.3.3.5.2   M      
34  Characteristic Format: FLOAT  3.3.3.5.2   M      
35  Characteristic Format: Duint16  3.3.3.5.2   M      
36  Characteristic Format: utf8s  3.3.3.5.2   M      
37  Characteristic Format: utf16s  3.3.3.5.2   M      
38  Characteristic Format: struct  3.3.3.5.2   M      

Table 4: Attribute Profile Support, by server

Prerequisite: 1/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Exchange MTU  4.3.1   C.4      
Discover All Primary Services  4.4.1   M      
Discover Primary Services by Service UUID  4.4.2   M      
Find Included Services  4.5.1   M      
Discover All characteristics of a Service  4.6.1   M      
Discover Characteristics by UUID  4.6.2   M      
Discover All Characteristic Descriptors  4.7.1   M      
Read Characteristic Value  4.8.1   M      
Read Using Characteristic UUID  4.8.2   M      
10  Read Long Characteristic Values  4.8.3   C.4      
11  Read Multiple Characteristic Values  4.8.4   C.4      
12  Write without Response  4.9.1   C.2      
13  Signed Write Without Response  4.9.2   C.4      
14  Write Characteristic Value  4.9.3   C.3      
15  Write Long Characteristic Values  4.9.4   C.4      
16  Characteristic Value Reliable Writes  4.9.5   C.4      
17  Notifications  4.10.1   C.4      
18  Indications  4.11.1   C.1      
19  Read Characteristic Descriptors  4.12.1   C.4      
20  Read Long Characteristic Descriptors  4.12.2   C.4      
21  Write Characteristic Descriptors  4.12.3   C.4      
22  Write Long Characteristic Descriptors  4.12.4   C.4      
23  Service Changed Characteristic  7.1   C.1      
24  Configured Broadcast  7.2   C.5      
C.1: Mandatory if service definitions on the server can be added, changed, or removed, otherwise Optional.
C.2: Mandatory if 4/13 is supported, otherwise Optional.
C.3: Mandatory if 4/15 is supported, otherwise Optional.
C.4: Mandatory if 1/4 is supported, otherwise Optional.
C.5: Optional if 4/14 is supported, otherwise Excluded.

Table 4B: Profile Attribute Types and Characteristic Formats, by server

Prerequisite: 1/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Primary Service Declaration  3.1   M      
Secondary Service Declaration  3.1   M      
Include Declaration  3.2   M      
Characteristic Declaration  3.3.1   M      
Characteristic Value Declaration  3.3.2   M      
Characteristic Extended Properties  3.3.3.1   M      
Characteristic User Description Descriptor  3.3.3.2   M      
Client Characteristic Configuration Descriptor  3.3.3.3   M      
Server Characteristic Configuration Descriptor  3.3.3.4   M      
10  Characteristic Format Descriptor  3.3.3.5   M      
11  Characteristic Aggregate Format Descriptor  3.3.3.6   M      
12  Characteristic Format: Boolean  3.3.3.5.2   M      
13  Characteristic Format: 2Bit  3.3.3.5.2   M      
14  Characteristic Format: nibble  3.3.3.5.2   M      
15  Characteristic Format: Uint8  3.3.3.5.2   M      
16  Characteristic Format: Uint12  3.3.3.5.2   M      
17  Characteristic Format: Uint16  3.3.3.5.2   M      
18  Characteristic Format: Uint24  3.3.3.5.2   M      
19  Characteristic Format: Uint32  3.3.3.5.2   M      
20  Characteristic Format: Uint48  3.3.3.5.2   M      
21  Characteristic Format: Uint64  3.3.3.5.2   M      
22  Characteristic Format: Uint128  3.3.3.5.2   M      
23  Characteristic Format: Sint8  3.3.3.5.2   M      
24  Characteristic Format: Sint12  3.3.3.5.2   M      
25  Characteristic Format: Sint16  3.3.3.5.2   M      
26  Characteristic Format: Sint24  3.3.3.5.2   M      
27  Characteristic Format: Sint32  3.3.3.5.2   M      
28  Characteristic Format: Sint48  3.3.3.5.2   M      
29  Characteristic Format: Sint64  3.3.3.5.2   M      
30  Characteristic Format: Sint128  3.3.3.5.2   M      
31  Characteristic Format: Float32  3.3.3.5.2   M      
32  Characteristic Format: Float64  3.3.3.5.2   M      
33  Characteristic Format: SFLOAT  3.3.3.5.2   M      
34  Characteristic Format: FLOAT  3.3.3.5.2   M      
35  Characteristic Format: Duint16  3.3.3.5.2   M      
36  Characteristic Format: utf8s  3.3.3.5.2   M      
37  Characteristic Format: utf16s  3.3.3.5.2   M      
38  Characteristic Format: struct  3.3.3.5.2   M      
C.1: Mandatory if 1/4 is supported, otherwise Optional.
C.2: Mandatory if 4/17 or 4/18 is supported.
C.3: Mandatory if [broadcast feature] is supported.





Generic Attribute Profile Service   [ top ]

Table 5: Deleted
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
(Intentionally left blank)        





Generic Attribute Profile Service   [ top ]

Table 6: SDP Interoperability

Prerequisite: 2/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Discover GATT Services using Service Discovery Profile  GATT 4.4   C.1      
Publish SDP record for GATT services support via BR/EDR  GATT 9   C.2      
C.1: Mandatory if 1/1 and 2/1 are supported.
C.2: Mandatory if 1/2 and 2/1 are supported.

Table 7: Attribute Protocol Transport
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Mode 4  GAP 5   C.1      
LE Security Mode 1  GAP 10.2.1   C.2      
LE Security Mode 2  GAP 10.2.2   C.2      
LE Authentication Procedure  GAP 10.3   C.2      
LE connection data signing procedure  GAP 10.4.1   C.2      
LE Authenticate signed data procedure  GAP 10.4.2   C.2      
LE Authorization Procedure  GAP 10.5   C.2      
C.1: Mandatory if 2/1 is supported, otherwise Excluded.
C.2: Optional if 2/2 is supported, otherwise Excluded.





  Attribute Protocol  
  Vol 3, Part H  



Attribute Protocol Role   [ top ]

Table 1: Attribute Protocol Support
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Attribute Protocol Client   ATT 1.1, GAP 12   O      
Attribute Protocol Server  ATT 1.1, GAP 12   M      





Attribute Protocol Transport   [ top ]

Table 2: Attribute Protocol Transport
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Attribute Protocol Supported over BR/EDR (L2CAP fixed channel support)  ATT 1.3   C.1      
Attribute Protocol Supported over LE  ATT 1.3   C.1      
C.1: Mandatory to support at least one of 2/1 or 2/2.





Attribute Protocol Messages   [ top ]

Table 3: Attribute Protocol Client Messages

Prerequisite: 1/1
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Attribute Error Response  ATT, 3.4.1.1   M      
Exchange MTU Request  ATT, 3.4.2.1   O      
Exchange MTU Response  ATT, 3.4.2.2   C.1      
Find Information Request  ATT, 3.4.3.1   O      
Find Information Response  ATT, 3.4.3.2   C.9      
Find by Type Value Request  ATT, 3.4.4.3   O      
Find by Type Value Response  ATT, 3.4.4.4   C.2      
Read by Type Request  ATT, 3.4.4.1   O      
Read by Type Response  ATT, 3.4.4.2   C.3      
10  Read Request  ATT, 3.4.4.3   O      
11  Read Response  ATT, 3.4.4.4   C.10      
12  Read Blob Request  ATT, 3.4.4.5   O      
13  Read Blob Response  ATT, 3.4.4.6   C.4      
14  Read Multiple Request  ATT, 3.4.4.7   O      
15  Read Multiple Response  ATT, 3.4.4.8   C.5      
16  Read by Group Type Request  ATT, 3.4.4.9   O      
17  Read by Group Type Response  ATT, 3.4.4.10   C.6      
18  Write Request  ATT, 3.4.5.1   O      
19  Write Response  ATT, 3.4.5.2   C.7      
20  Write Command  ATT, 3.4.5.3   O      
21  Signed Write Command  ATT, 3.4.5.3   O      
22  Prepare Write Request  ATT, 3.4.6.1   O      
23  Prepare Write Response  ATT, 3.4.6.2   C.8      
24  Execute Write Request  ATT, 3.4.6.3   C.8      
25  Execute Write Response  ATT, 3.4.6.4   C.8      
26  Handle Value Notification  ATT, 3.4.7.1   M      
27  Handle-Value Indication  ATT, 3.4.7.2   M      
28  Handle Value Confirmation  ATT, 3.4.7.3   M      
29  Client Timeout  ATT, 3.3.3   M      
C.1: Mandatory if 3/2 is supported, otherwise Excluded.
C.2: Mandatory if 3/6 is supported, otherwise Excluded.
C.3: Mandatory if 3/8 is supported, otherwise Excluded.
C.4: Mandatory if 3/12 is supported, otherwise Excluded.
C.5: Mandatory if 3/14 is supported, otherwise Excluded.
C.6: Mandatory if 3/16 is supported, otherwise Excluded.
C.7: Mandatory if 3/18 is supported, otherwise Excluded
C.8: Mandatory if 3/22 is supported, otherwise Excluded.
C.9: Mandatory if 3/4 is supported, otherwise Excluded.
C.10: Mandatory if 3/10 is supported, otherwise Excluded.





Attribute Protocol Messages   [ top ]

Table 4: Attribute Protocol Server Messages

Prerequisite: 1/2
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Attribute Error Response  ATT, 3.4.1.1   M      
Exchange MTU Request  ATT, 3.4.2.1   M      
Exchange MTU Response  ATT, 3.4.2.2   M      
Find Information Request  ATT, 3.4.3.1   M      
Find Information Response  ATT, 3.4.3.2   M      
Find by Type Value Request  ATT, 3.4.4.3   M      
Find by Type Value Response  ATT, 3.4.4.4   M      
Read by Type Request  ATT, 3.4.4.1   M      
Read by Type Response  ATT, 3.4.4.2   M      
10  Read Request  ATT, 3.4.4.3   M      
11  Read Response  ATT, 3.4.4.4   M      
12  Read Blob Request  ATT, 3.4.4.5   O      
13  Read Blob Response  ATT, 3.4.4.6   C.1      
14  Read Multiple Request  ATT, 3.4.4.7   O      
15  Read Multiple Response  ATT, 3.4.4.8   C.2      
16  Read by Group Type Request  ATT, 3.4.4.9   M      
17  Read by Group Type Response  ATT, 3.4.4.10   M      
18  Write Request  ATT, 3.4.5.1   O      
19  Write Response  ATT, 3.4.5.2   C.3      
20  Write Command  ATT, 3.4.5.3   O      
21  Signed Write Command  ATT, 3.4.5.3   O      
22  Prepare Write Request  ATT, 3.4.6.1   O      
23  Prepare Write Response  ATT, 3.4.6.2   C.4      
24  Execute Write Request  ATT, 3.4.6.3   C.4      
25  Execute Write Response  ATT, 3.4.6.4   C.4      
26  Handle Value Notification  ATT, 3.4.7.1   O      
27  Handle-Value Indication  ATT, 3.4.7.2   O      
28  Handle Value Confirmation  ATT, 3.4.7.3   C.5      
29  Server Timeout  ATT, 3.3.3   C.5      
C.1: Mandatory if 4/12 is supported, otherwise Excluded.
C.2: Mandatory if 4/14 is supported, otherwise Excluded.
C.3: Mandatory if 4/18 is supported, otherwise Excluded.
C.4: Mandatory if 4/22 is supported, otherwise Excluded.
C.5: Mandatory if 4/27 is supported, otherwise Excluded.

Table 5: Attribute Protocol Transport
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Security Mode 4  GAP 5   C.1      
LE Security Mode 1  GAP 10.2.1   C.2      
LE Security Mode 2  GAP 10.2.2   C.2      
LE Authentication Procedure  GAP 10.3   C.2      
LE connection data signing procedure  GAP 10.4.1   C.2      
LE Authenticate signed data procedure  GAP 10.4.2   C.2      
LE Authorization Procedure  GAP 10.5   C.2      
C.1: Mandatory if 2/1 is supported, otherwise Excluded.
C.2: Optional if 2/2 is supported, otherwise Excluded.





  Security Manager Protocol  
  Vol 3, Part F  



Connection Roles   [ top ]

Table 1: Roles
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Master Role (Initiator)  [1] 2.4   C.1      
Slave Role (Responder)  [1] 2.4   C.1      
C.1: Mandatory to support at least one of the defined roles.


Security Properties   [ top ]

Table 2: Security Properties
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Authenticated MITM protection  [1] 2.3.1   O      
Unauthenticated no MITM protection  [1] 2.3.1   C.1      
No security requirements  [1] 2.3.1   M      
OOB supported  [1] 2.3.1   O      
C.1: Mandatory if 2/1 is supported, otherwise Optional.


Encryption Key Size   [ top ]

Table 3: Encryption Key Size

Prerequisite: 2/1 or 2/2 or 2/4
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Encryption Key Size Negotiation  [1] 2.3.4   M      


Pairing Method   [ top ]

Table 4: Pairing Method
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Just Works  [1] 2.3.5   O      
Passkey Entry  [1] 2.3.5   C.1      
Out of Band  [1] 2.3.5   C.1      
C.1: If 2/1 is supported, at least one of these features shall be supported.


Key Distribution and Usage   [ top ]

Table 5: Security Initiation
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Encryption Setup using STK  [1] 2.4   C.3      
Encryption Setup using LTK  [1] 2.4   O      
Slave Initiated Security   [1] 2.4.6   C.1      
Slave Initiated Security – Master response   [1] 2.4.6   C.2      
C.1: Mandatory if 1/2 is supported, otherwise Excluded.
C.2: Mandatory if 1/1 is supported, otherwise Excluded.
C.3: Mandatory if (2/1 or 2/2 or 2/4) is supported, otherwise Excluded.


Signing Algorithm   [ top ]

Table 6: Signing Algorithm
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Signing Algorithm - Generation  [1] 2.4   O      
Signing Algorithm - Resolving  [1] 2.4   O      

Table 7: Key Distribution
 Item   Capability  System Spec
 Reference
 Status  Support
[Yes] or [No]
Encryption Key  GAP 9.4.3   C.1      
Identity Key  GAP 10.7   C.2      
Signing Key  GAP 10.4   C.3      
C.1: Mandatory if (GAP 24/2 or 42/6) is supported, otherwise Optional.
C.2: Mandatory if (GAP 26/3) is supported, otherwise Optional.
C.3: Mandatory if (GAP 25/6 or 35/6) is supported, otherwise Optional.