<?xml version="1.0" encoding="utf-8"?>

<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

<!-- This component and the accompanying materials are made available under the terms of the License 

"Eclipse Public License v1.0" which accompanies this distribution, 

and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

<!-- Initial Contributors:

    Nokia Corporation - initial contribution.

Contributors: 

-->

<!DOCTYPE concept

  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

<concept xml:lang="en" id="GUID-AB0A3E87-6725-5E83-B462-1219CE205187"><title>Bluetooth Notifiers Support Overview</title><shortdesc>The Bluetooth Notifiers Support component enables you to create dialogs to interact with device users about Bluetooth interactions. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Purpose</title> <p>The Bluetooth Notifiers component enables you to create dialogs for interacting with device users about Bluetooth interactions. You can offer Bluetooth dialogs for several purposes, but the main purpose is to provide security for Bluetooth interactions. </p> </section> <section><title>Required background</title> <p>You need to be familiar with the core Bluetooth concepts. </p> </section> <section><title>Key concepts and terms</title> <dl><dlentry><dt>Pairing</dt> <dd><p>Pairing takes place when two devices establish a trusted relationship with each other for secure communication. </p> </dd> </dlentry> <dlentry><dt>Passkey</dt> <dd><p>A passkey is a piece of data known only to the two parties involved in the communication. It is also known as a shared secret. In the Symbian Bluetooth context, a Passkey Display notifier is a dialog that uses a 6-digit number, which is generated by Symbian OS and then manually entered on a peer device. </p> </dd> </dlentry> <dlentry><dt>Secure Simple Pairing (SSP)</dt> <dd><p>Secure Simple Pairing is pairing that takes place with an automatically generated PIN. The user does not create a PIN. </p> </dd> </dlentry> </dl> </section> <section><title>Architecture</title> </section> <section><title>APIs</title> <p>The key classes of Symbian's implementation of Bluetooth Notifiers are as follows: </p> <table id="GUID-8DD9C644-EE92-5CA6-B9E0-97833F4675EA"><tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/><thead><row><entry>API</entry> <entry>Description</entry> </row> </thead> <tbody><row><entry><p> <xref href="GUID-848C1394-A007-3B4A-84FF-C790EC2FECAD.dita"><apiname>CPinCodeEntryNotifier</apiname></xref>  </p> </entry> <entry><p>The class to provide a PIN-code entry notifier. </p> </entry> </row> <row><entry><p> <xref href="GUID-1D32697F-4A33-3B9B-9A53-B3ADCA8A215A.dita"><apiname>CNumericComparisonNotifier</apiname></xref>  </p> </entry> <entry><p>The class to provide a numeric comparison notifier. </p> </entry> </row> <row><entry><p> <xref href="GUID-CA141385-E969-359A-9706-42451962CE0F.dita"><apiname>CPasskeyNotifier</apiname></xref>  </p> </entry> <entry><p>The class to provide a passkey display notifier. </p> </entry> </row> <row><entry><p> <xref href="GUID-986EFB63-1F05-35AF-87DB-3FED6B8E4588.dita"><apiname>CPasskeyDisplayNotifier</apiname></xref>  </p> </entry> <entry><p>The class to provide a passkey display notifier. The passkey entry display notifier can currently receive two types of updates: </p> <ul><li id="GUID-5A532F95-97D6-5687-96F9-A583CF5C0EA7"><p>Updates to the remote device name (the same as the other notifiers). </p> <p>Updates to provide the notification of a key press by the remote keyboard. </p> </li> </ul> <p>As a Symbian OS device will be the display part of the pairing method, the remote device will be keyboard only and so not feature a display. It is highly recommended that the key press notifications provide a visual representation of keys being registered to help the device user. </p> </entry> </row> </tbody> </tgroup> </table> </section> <section><title>Text notifiers library details</title> <p>The Bluetooth Notifiers component has one published library. The DLL that provides the functionality and the library to which your code must link is identified below. </p> <table id="GUID-C6EC280C-A748-55CE-8C82-34289E9F0B99"><tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/><thead><row><entry>DLL</entry> <entry>LIB</entry> <entry>Short description</entry> </row> </thead> <tbody><row><entry><p> <filepath>textnotifiers.dll </filepath>  </p> </entry> <entry><p> <filepath>textnotifiers.lib</filepath>  </p> </entry> <entry><p>Basic types used to allow interactions with standard Bluetooth notifiers. </p> </entry> </row> </tbody> </tgroup> </table> </section> <section><title>Typical uses</title> <p>The key purpose of Bluetooth Notifiers is to create dialogs to enable secure pairing. The Bluetooth Notifier provides the following types of authentication dialog to enable secure pairing: </p> <ul><li id="GUID-E2DE8A0B-33A7-5863-BE2C-28C0C2AA44AE"><p> <b>Authorisation dialog</b>  </p> <p>Authorisation dialogs offer device users the choice to accept or reject connections. </p> </li> <li id="GUID-B1940F8D-12E5-50E7-9109-2CAB7758B774"><p> <b>PIN-code entry notifier</b>  </p> <p>A user creates a PIN and sends it to the peer. </p> </li> <li id="GUID-07996989-0294-5CDD-8018-3450415F30D4"><p> <b>Numeric comparison notifier</b>  </p> <p>Numeric Comparison involves the user comparing 6-digit numbers displayed on both devices that are authenticating. Authentication is completed by the users of both devices signalling a confirmation that the displayed numbers are identical – if one device is unable to input a confirmation then only the other device needs to signal confirmation </p> </li> <li id="GUID-0BC7AA7C-7539-510D-8D0B-179A69D43200"><p> <b>Passkey display notifier </b>  </p> <p>Authentication by Passkey Entry involves the Symbian OS device displaying a 6-digit number which is manually entered on a device without a display (but with a numeric keypad). This is similar to PIN Code Entry except in this case the number is chosen for the user, and it need only be entered on the peer device. </p> </li> </ul> <p>In addition to the authentication notifiers, it is possible to use Bluetooth Notifiers for device selection dialogs. Device selection dialogs are for use by applications and profiles to decide which device the user wishes to connect to. Device selection dialogs do not need to be Bluetooth notifiers. Whereas the authentication notifiers are not associated with an application, device selection notifiers are. Therefore it is best to get the relevant application, for example a camera, to create the dialog. </p> </section> </conbody></concept>