Connection parameter update request and response for bluetooth low energy host bluetooth speaker earbuds

The "Connection parameter update request" command allows the slave device to update the link layer connection parameters. These parameters include the connect event interval (how often the slave wants the master to allow the slave to send packets) the slave delay (the maximum value the slave can ignore the master's connect events) and the monitoring timeout. www.bjbjaudio.com

During a connection, this command can be used if the slave device wishes to modify the current connection parameters. For example, if the interval between connection events may be too fast, resulting in excessive power wastage. This is fine when the slave latency is high, but if not, the slave will listen to the link frequently. This is necessary in some cases, such as the first binding between devices, sending multiple data packets to each other, exploring services and device characteristics, etc. But in many other cases, minimizing the number of connection events a slave device must listen for is critical to improving battery life.

The connection parameter update request command is only used for sending from the device to the master device, because the master device can start the link layer connection parameter update control (Connection ParameterUpdateControl) procedure at any time. If the command is sent by the master, the slave will treat it as an error and return a "command rejected" command with a "command not understood" reason code. www.bjbjaudio.com  <a style="opacity:0.0;color:#ffffff">bluetooth speaker earbuds</a>             <a style="opacity:0.0;color:#ffffff">bluetooth speaker earbuds</a>

The slave can send this command at any time; if the master receiving this information can modify the connection parameters, it will return a "Connection ParameterUpdateResponse" with the result code set to "accepted". Then, the master device will start the link layer connection parameter update control procedure.

Of course, if the master does not agree with the slave's request parameters, it can reject the request by sending a connection parameter update response command with a result code of "rejected." At this point the slave has two options: either accept the The connection parameters used, or terminate the connection. Terminating the connection may seem radical at first, but the slave device will run out of battery in a week with the current parameters, while using the requested parameters can last for several days. Years, it became clear that there was only one reasonable choice. www.bjbjaudio.com

<a style="opacity:0.0;color:#ffffff">bluetooth speaker earbuds</a>           <a style="opacity:0.0;color:#ffffff">bluetooth speaker earbuds</a>

When modifying connection parameters, if you want to reduce the possibility of the master device rejecting the slave device's request, you can set an acceptable parameter range in the request. A well-designed slave will happily accept a wide range of parameters. Since the master device may be busy with tasks such as real-time conversational audio connections or high-quality voice connections, it can accept a range of connection interval parameters. The acceptable interval parameters for the device will vary depending on the current task and may be different from the parameters the last time the device was connected. Another way to improve the chances of the master accepting the connection parameters is for the slave to provide a reasonable slave delay. The master device can choose the most suitable connection event interval, and the slave device uses the slave device delay parameter for the best power consumption. www.bjbjaudio.com              <a style="opacity:0.0;color:#ffffff">bluetooth speaker earbuds</a>