GATT Operation Flowcharts


Bluetooth Low Energy (BLE) defines a framework for a wide variety of communication schemes. It allows devices to discover each other, broadcast data, establish connections, and many other fundamental operations.

The primary objective of this document is to focus on the procedures defined for the "Generic Attribute Profile" (GATT) of the BLE stack.

Sequence diagrams are used to describe these procedures comprehensively, focusing on the following items:

This document does not expose the Bluetooth stack packet management nor it describes the host controller interface (HCI).

This document assumes that the necessary Bluetooth hardware is used, such as an EFR32 SoC or a BGM module.

Generic Attribute Profile (GATT) Operations

GATT provides a framework for all profiles defined either by the Bluetooth SIG or by the user. Bluetooth profiles are implemented using a hierarchical structure:

GATT database
*--> Services
        --> Characteristics (always placed under a service)
                  --> Descriptors (always placed under a characteristic)

The BLE specification refers to all the attributes within a single service as the service definition.

Primary Service Discovery

A primary service is the standard type of GATT service that includes relevant, standard functionality exposed by the GATT server. In other words, a service is a collection of characteristics. As a result, when a connection is established, it is necessary for the GATT client to be able to discover the available services.

The procedure iterates through all available services of the GATT database, an evt_gatt_service event is generated for each primary service discovered. After the end of the list is reached, an evt_gatt_end_procedure is raised by the stack.

After a client has obtained the handle range for a service, a similar procedure exists to retrieve a full list of the characteristics under that service.


As mentioned earlier, characteristics are data containers. They consist of a declaration (a label) and a value.

There are multiple types of characteristics:

Moreover, on a given characteristic, different types of read/write operations can be performed. The following procedures are discussed here:

We won't depict here the following sub-procedures:

For more information on these procedures, see the BLE core specification and Different Characteristic Value Types.

Read/Write Hex and utf-8 Type Characteristics

The BLE stack manages the read and write operations for these characteristics. Upon reception of the "Read request", the server's stack sends back a "Read response" containing the characteristic value, as shown below:

The following sequence diagram describes the write operation:

The "Write Response" contains only an error code indicating whether the write was successful or not.

Note that if the maximum length of the payload is reached, the read/write long characteristic is automatically used by the BLE stack.

Read User Characteristics

The "Read Characteristic Value" procedure is implemented via the gecko_cmd_gatt_read_characteristic_value() BGAPI command. In this procedure, the characteristic length must be less or equal to the maximum payload, that is (ATT_MTU-1) bytes. In other words, the length of the characteristic has to fit in one "Read Response".

Data is sent from the server to the client via the "Read Response". Then, the client application can retrieve the data via the "evt_gatt_characteristic_value" event.

If the characteristic does not fit in one "Read Response", the "Read Long Characteristic Value" procedure implemented via the gecko_cmd_gatt_read_characteristic_value() routine can be used. If the payload is bigger than (ATT_MTU-1), the stack will automatically pack and send the data using gecko_cmd_gatt_read_characteristic_value_from_value(). It is not the responsibility of the application to call gecko_cmd_gatt_read_characteristic_value_from_value(). Instead, the application will still use the gecko_cmd_gatt_read_characteristic_value() routine. The following sequence diagram describes the "Read Long Characteristic Value" mechanism using the offset routine.

The client reads the characteristic by chunks of (ATT_MTU-1) bytes. The client stack keeps and updates the byte offset used for the read request.

For more extensive description on long characteristic operations, see Working with Long Characteristic Values.

Write User Characteristics

The "Write Characteristic Value" procedure is implemented via the gecko_cmd_gatt_write_characteristic_value() BGAPI command. In this procedure, the characteristic length must be less or equal to the maximum payload, that is (ATT_MTU-3) bytes. In a similar way to the "Read Characteristic", the length of the characteristic has to fit in one "Write Request".

For longer characteristics, the same command can be used to write a characteristic in a remote GATT database. If the payload does not fit in one request, the "write long" procedure is automatically used when gecko_cmd_gatt_write_characteristic_value() is called. The value is buffered on the server side until all data is sent over. Upon reception by the server of all data, the client can issue a "write request execute" to trigger the effective write in the remote GATT database.

If the operation is successful, an evt_gatt_procedure_completed is sent by the server.

For more extensive on long characteristic operations, see KBA_BT_0916: Working with Long Characteristic Values

Notifications and Indications

Server-initiated updates can be sent from the GATT server to the client without the client having to request it. This has the advantage to save both power and bandwidth. Notifications and Indications are two types of server-initiated updates. In both cases, the procedure has to be enabled first on the remote GATT server using the gecko_cmd_gatt_set_characteristic_notification() beforehand.

Notifications includes the handle of the characteristic (i.e., its identifier) and the value. The client receives the notifications but does not send any acknowledgment back to the server.

The indications, on the other hand, have the same behavior but require an explicit acknowledgment from the client in form of confirmation. If the confirmation is not sent by the client, the server will not send further indications.

The indications uses the same attribute protocol feature as the notifications.