Bluetooth Services

Modules implementing GATT services and characteristics. More...

Modules
	'Common service definitions'
	Constants, type definitions and functions that are common to all services.
	Alert Notification Service Client
	Alert Notification module.
	BLE Date Time characteristic type
	Definition of ble_date_time_t type.
	Battery Service
	Battery Service module.
	Blood Pressure Service
	Blood Pressure Service module.
	Cycling Speed and Cadence Service
	Cycling Speed and Cadence Service module.
	Device Firmware Update Service
	Device Firmware Update Service.
	Device Information Service
	Device Information Service module.
	Glucose Database Service
	Glucose Service module.
	Glucose Service
	Glucose Service module.
	Health Thermometer Service
	Health Thermometer Service module.
	Heart Rate Service
	Heart Rate Service module.
	Human Interface Device Service
	Human Interface Device Service module.
	Immediate Alert Service
	Immediate Alert Service module.
	Immediate Alert Service Client
	Immediate Alert Service Client module.
	Link Loss Service
	Link Loss Service module.
	Running Speed and Cadence Service
	Running Speed and Cadence Service module.
	Speed and Cadence Control Point
	Speed and Cadence Control Point module.
	TX Power Service
	TX Power Service module.

Detailed Description

All service modules have the same overall structure:

• Init function: All services have an init function which will add the service and the corresponding characteristics to the stack data base. Configuration of optional characteristics, behaviour, data values etc. is passed to the init function using an init structure. For most services, a service structure is returned by the init function. To enable having several instances of the same service type in a single application, the service structure is allocated in the application, and a pointer to it is passed to the init function. To identify the service instance, a pointer to this service structure is passed to all other functions in the service API.

• Stack event handler: Most services have a stack event handler (ble_xx_on_ble_evt()). It will react to events that are relevant to this service, and ignore all others. The handler must be called from the ble_stack_evt_handler callback function that is provided to the BLE Stack Event Handler by the application.

• Service event handler: For most services, the application can/must supply a service event handler to the service during initialization. Using this handler, the service can notify the application about events in the service.

• Service error handler: For some services, the application may supply a service error handler to the service during initialization. Using this handler, the service can notify the application about errors.

• API functions: Most services have a set of API functions which the application can use to interact with the services.