Generic Access Profile (GAP)
www.ti.com
30
SWRU271H–October 2010–Revised April 2019
Submit Documentation Feedback
Copyright © 2010–2019, Texas Instruments Incorporated
The Bluetooth Low Energy Protocol Stack
5.2.1.3 Connection Parameter Considerations
In many applications, the slave skips the maximum number of connection events. Consider the effective
connection interval when selecting or requesting connection parameters. Selecting the correct group of
connection parameters helps optimize the power of the Bluetooth Low Energy device. The following list is
a summary of the trade-offs in connection-parameter settings:
Reducing the connection interval will do the following:
• Increase the power consumed by both devices
• Increase the throughput to and from both devices
• Reduce the amount of time required to send data to and from both devices
Increasing the connection interval will do the following:
• Reduce the power consumed by both devices
• Reduce the throughput to and from both devices
• Increase the amount of time required to send data to and from both devices
Reducing the slave latency or setting it to zero will do the following:
• Increase the power consumed by the peripheral device
• Reduce the amount of time required to send data from the central device to the peripheral device
Increasing the slave latency will do the following:
• Reduce the power consumed by the peripheral device when it has no data to send to the central
device
• Increase the amount of time required to send data from the central device to the peripheral device
5.2.1.4 Connection Parameter Update
Sometimes the central device will request a connection with a peripheral device containing connection
parameters unfavorable to the peripheral device. Other times, a peripheral device might change
parameters based on the peripheral application during a connection. The peripheral device can send a
Connection Parameter Update Request to the central device to change the connection settings. For
Bluetooth 4.0 devices, the L2CAP layer of the protocol stack handles this request.
This request contains the following four parameters:
• A minimum connection interval
• A maximum connection interval
• A slave latency
• A timeout
These values represent the parameters the peripheral device requires for the connection (the connection
interval is given as a range). When the central device receives this request, it can accept or reject the
parameters.