alert notification as master or periferal?

RE: alert notification as master or periferal?

Ole Morten — Thu, 13 Mar 2014 11:35:28 GMT

There is no additional connection; you just start a service discovery by using the GATT Client API of the softdevice. It's a good idea to wait until bonding is finished however, since you may see INSUFFICIENT_AUTHENTICATION if you do things before that. You can refer to the proximity application in the SDK for an example, since it includes a GATT Client for the (very simple) Immediate Alert service, or also the ANCS or ANS example applications.

RE: alert notification as master or periferal?

Oleh — Thu, 13 Mar 2014 09:47:16 GMT

Thank you Ole for clarification.

What I'm trying to understand is how the connection is established in this case:

the phone is Central and is GATT Server for alert notification;
the nrf51822 for example will be peripheral and GATT Client (for ANS) and GATT Server (for Proximity);

The device will advertise, go thru bonding and is connected. Is it the right time now to connect to Phone and subscribe to ANS?

Thank you

RE: alert notification as master or periferal?

Ole Morten — Thu, 20 Feb 2014 12:11:58 GMT

An iOS app can keep a connection to a Peripheral in the background, so there shouldn't be any reason to not have the iOS device as the Central.

However, with the Alert Notification Service, it's most often the device that has the notifications (i.e. the phone) that would be the GATT Server, and the device accessing them (the device) would be the GATT Client. As explained here, this is however independent of the GAP role.