Datasheet

Page 85 of 161
nRF8001 Product Specification
Revision 1.2
When in active mode, nRF8001 will start advertising in order to establish a connection to a peer device in
the central role upon receiving the ACI commands Connect or Bond. A successful connection results in a
transition to the connected state.
Once connected, the nRF8001 initiates the service discovery procedure when required, see section 22.4.2
on page 85 for details.
A timeout value is set for advertising. nRF8001 advertises until a connection has been established, or until
the timeout value is exceeded. If nRF8001 successfully connects to a peer device, nRF8001 will remain
connected even after the timeout expires.
22.4.1 Advertising and Connection Establishment
While in Active mode, nRF8001 may be set to the following advertising modes;
• General Discoverable mode
5
(Connect when not bonding)
• Limited Discoverable mode
6
(Bond)
• Non-Discoverable mode
7
(Connect when bonded)
In the case of a successful connection establishment, nRF8001 generates a
ConnectedEvent followed
by one or more
PipeStatusEvents. nRF8001 will remain connected unless disconnected by the peer or
by the application controller. The connection may also be lost as a result of the nRF8001 or peer device
moving out of range or due to a protocol timeout or failure.
Upon advertisement timeout or connection loss, nRF8001 will return to Standby mode until a new
Bond or
Connect command is issued by the application controller.
22.4.2 Service Discovery
The service discovery procedure is initiated automatically upon connection establishment. The discovery
procedure discovers the remote services on the peer device that have been defined through the setup
procedure, see section 22.3 on page 81
. This procedure is required in order to establish the mapping
between the pipe number and the remote characteristic attribute. The nRF8001 service discovery
procedure activates the following GATT procedures:
• Discover Primary Services by Service UUID
8
• Discover All Characteristics of a Service
9
• Discover All Characteristic Descriptors
10
• Enabling the Service Changed characteristic
11
Upon execution of the service discovery procedure, a ConnectedEvent is generated followed by a
PipeStatusEvent, returning the service pipe availability status. Mulitiple PipeStatusEvents may
result as the pipe availability status is updated during the service discovery procedure.
5. Bluetooth Core specification v4.0, Vol. 3, Part C (GAP), Sect. 9.2.4, ‘General Discoverable Mode’.
6.
Bluetooth Core specification v4.0, Vol. 3, Part C (GAP), Sect. 9.2.3, ‘Limited Discoverable Mode’.
7.
Bluetooth Core specification v4.0, Vol. 3, Part C (GAP), Sect. 9.2.2, ‘Non-Discoverable Mode’.
8.
Bluetooth Core specification v4.0, Vol. 3, Part G (GATT), Sect. 4.4.2, ‘Discover Primary Service by Service UUID’.
9.
Bluetooth Core specification v4.0, Vol. 3, Part G (GATT), Sect. 4.6.1, ‘Discover All Characteristics of a Service’.
10.
Bluetooth Core specification v4.0, Vol. 3, Part G (GATT), Sect. 4.7.1, ‘Discover All Characteristics Descriptors’.
11.
Bluetooth Core specification v4.0, Vol. 3, Part G (GATT), Sect. 7.1, ‘Service Changed’.