nRF51 SDK
 All Data Structures Functions Variables Typedefs Enumerations Enumerator Groups Pages
0x14 - BLE_GAP_EVT_SEC_INFO_REQUEST

Event packet encoding

Frame format encoding of the BLE_GAP_EVT_SEC_INFO_REQUEST packet.

Event ID = 0x14 for BLE_GAP_EVT_SEC_PARAMS_REQUEST

All BLE Events, ble_evt_t, are encoded with the header ble_evt_hdr_t first, containing only the 'Event ID', followed by the event. The 'Event Length' will not be encoded as the size of the event could be of different sizes depending on decoder architecture.

The BLE GAP event contains a connection handle, and for the BLE GAP Security Info Request event, the ble_gap_evt_sec_info_request_t is encoded after connection handle as seen in Figure 1.

The "Encryption info present", "Identity info present", and "Signing info present" flags are all bitfields inside 1 byte as seen in Figure 2.

The order of the encoding is:

- 2 bytes: Connection Handle
- 1 byte: Address Type
- 6 bytes: Address
- 2 bytes: Encryption Diversifier
- 1 byte: (See Figure 2)
- 1 bit: Encryption info
- 1 bit: Identity info
- 1 bit: Signing info

Encoding of GAP Connection Security Updated event

event_sec_info_request_packet.png
Figure 1: Encoding of GAP Security Info Request event.

Encoding of Security mode and Level

event_sec_info_request_enc_id_sign_info.png
Figure 2: Encoding of Encryption info, Identity info, and Signing info inside a GAP Security Info Request event.