Introduction

**************************** Introduction *********************************

Bluetooth 'Apple Notification Center Service' is an example application where the device act as an Alert Notification Client with custom UUID as per Apple's ANCS specification.
This service is unique to Apple products and available only on iOS devices.
The ANCS Profile is used to enable a BTLC1000 device to obtain notifications from an iOS device (e.g. iPhone) that exposes 'Apple Notification Center Service'.
The ANCS Profile defines two roles:
Notification Provider (NP): The Notification Provider is a device that provides the IOS notifications.
Notification Consumer (NC): The Notification Consumer is a device that receives the IOS notifications and notification related data from Notification Provider.

Supported Evolution Kit -

ATSAML21-XPRO-B + ATBTLC1000 XPRO
ATSAMD21-XPRO + ATBTLC1000 XPRO
ATSAMG55-XPRO + ATBTLC1000 XPRO
ATSAM4S-XPRO + ATBTLC1000 XPRO

Running the Demo -

1. Build and flash the binary into supported evaluation board.
2. Open the console using TeraTerm or any serial port monitor.
3. Press the Reset button.
4. Wait for around 10 seconds for the patches to be downloaded device will initialize and start-up
5. Goto iPhone settings page and enable Bluetooth. The phone will start to scan for devices. ATMEL-ANCS will be appear amongst the devices scanned. Click on ATMEL-ANCS to connect on supported platform
6. Once connected, on the client side will request for pairing procedure with iPhone. The console log provides a guidance for the user to enter the pass- key on iPhone.
7. Upon completion of pairing process user can initiate a mobile terminated call to the iPhone. When the iPhone indicates an incoming call, the corresponding incoming call alert is indicated in the console log on supported platform . Once the call has terminated the device will wait for a new alert to occur.

Modules

***************************** Modules **************************************

BLE Manger -
- The Event Manager is responsible for handling the following:
  - Generic BLE Event Handling:-
    - BLE Event Manager handles the events triggered by BLE stack and also responsible for invoking all registered callbacks for respective events. BLE Manager handles all GAP related functionality. In addition to that handles multiple connection instances, Pairing, Encryption, Scanning.
  - Handling Multi-role/multi-connection:-
    - BLE Event Manager is responsible for handling multiple connection instances and stores bonding information and Keys to retain the bonded device. BLE Manager is able to identify and remove the device information when pairing/encryption gets failed. In case of multi-role, it handles the state/event handling of both central and peripheral in multiple contexts.
  - Controlling the Advertisement data:-
    - BLE Event Manager is responsible for generating the advertisement and scan response data for BLE profiles/services that are attached with BLE Manager.
BLE Services -
- The purpose of the Apple Notification Center Service (ANCS) is to give Bluetooth accessories (that connect to iOS devices through a Bluetooth low-energy link) a simple and convenient way to access many kinds of notifications that are generated on iOS devices.
- The ANCS exposes two characteristics:
  - Notification Source:
    - The Notification Source characteristic is the characteristic upon which an NC is informed of:
    - the arrival of a new iOS notification on the NP
    - the modification of an iOS notification on the NP
    - the removal of an iOS notification on the NP
  - Control Point and Data source:
    - An NC may want to interact with an iOS notification. It may want to retrieve more information about it, including its contents, or it may want to perform actions on it. The retrieval of these attributes is performed through the Control Point and Data Source characteristics.
    - An NC can issue a request to retrieve more information about an iOS notification by writing specific commands to the Control Point characteristic. If the write to the Control Point characteristic is successful, the NP will promptly respond to the request through a stream of GATT notifications on the Data Source characteristic.
BLE Platform Services -
- Interface Settings -
  - Connect ATBTLC1000 XPRO to SAML21-XPRO-B -> EXT1
  - Connect ATBTLC1000 XPRO to SAMD21-XPRO -> EXT1
  - Connect ATBTLC1000 XPRO to SAMG55-XPRO -> EXT1
  - Connect ATBTLC1000 XPRO to SAM4S-XPRO -> EXT1
- Serial Console COM port settings -
  - Baudrate 115200
  - Parity None, Stop Bit 1, Start Bit 1
  - No Hardware Handshake

6-Wire Mode Connection Setup -

Pins are 1:1 match with SAML21/D21 Xpro EXT1 Header to BTLC1000 XPro Header
UART(No Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin13, Tx-Pin14)
UART(With Flow Control)-SAM G55 Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6, Rx-Pin16, Tx-Pin17)
BTLC1000 Wakeup Pin-SAM G55 XPro Pins(Pin4)
BTLC1000 Chip Enable Pin-SAM G55 XPro Pins(Pin10)
BTLC1000 Vcc Pin-SAM L21/D21/G55 Xpro Pins(Pin20)
BTLC1000 GND Pin-SAM L21/D21/G55 Xpro Pins(Pin19)

4-Wire Mode Connection setup -

UART(With Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin15, Tx-Pin17, RTS-Pin16, CTS-Pin18)
BTLC1000 Wakeup Pin-SAM L21/D21 XPro Pins (Rx-Pin6)
BTLC1000 Chip Enable Pin-SAM L21/D21 XPro Pins (Rx-Pin4)
UART(With Flow Control)-SAM G55/4S Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6)
BTLC1000 Wakeup Pin-SAM G55/4S XPro Pins(Pin4)
BTLC1000 Chip Enable Pin-SAM G55/4S XPro Pins(Pin10)
BTLC1000 Vcc Pin-SAM L21/D21/G55/4S Xpro Pins(Pin20)
BTLC1000 GND Pin-SAM L21/D21/G55/4S Xpro Pins(Pin19)