Reducing bluetooth connection latency using selective GATT cache requests

An apparatus, comprising:

• one or more network interfaces to communicate with a network;
• a processor coupled to the one or more network interfaces and configured to execute one or more processes;
• and a memory configured to store a process that is executable by the processor, the process, when executed, configured to:
• obtain generic attribute (GATT) information from a device;
• obtain long term key information by forming a Bluetooth connection with the device;
• perform an exchange with the device to determine whether the long term key information is valid or is no longer valid, wherein the exchange includes transmitting a key validity request to the device and receiving, from the device, a response indicating whether the long term key information is valid;
• determine that the GATT information of the device has changed based on at least one of being unable to decode the response, the response indicating an invalid long term key result, or failing to validate the long term key information;
• and
• obtain, based on the determining that the GATT information has changed, updated GATT information from the device, when the long term key information is no longer valid,
• wherein the updated GATT information from the device is attributable to a reboot of the device.

A tangible, non-transitory, computer-readable medium storing program instructions that cause a first device to execute a process comprising:

• obtaining, by the first device, generic attribute (GATT) information from a second device;
• obtaining, by the first device, long term key information by forming a Bluetooth connection with the second device;
• performing, by the first device, an exchange with the second device to determine whether the long term key information is valid or is no longer valid, wherein the exchange includes transmitting, by the first device, a key validity request and receiving, from the second device, a response indicating whether the long term key information is valid;
• determining, by the first device, that the GATT information of the second device has changed based on at least one of the first device being unable to decode the response, the response indicating an invalid long term key result, or the first device failing to validate the long term key information;
• and
• obtaining, by the first device and based on the determining that the GATT information has changed, updated GATT information from the second device, when the long term key information is no longer valid,
• wherein the updated GATT information from the second device is attributable to a reboot of the second device.