<?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 id="GUID-F2A793F1-A5B5-526B-B147-771D440B13A2" xml:lang="en"><title>Bluetooth
Extended Inquiry Response</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This is a guide to the Symbian platform Bluetooth implementation of Extended
Inquiry Response (EIR). </p>
<section id="GUID-F3729B8D-A900-41E2-868E-E04EFD21E76E"><title>Purpose</title> <p>EIR provides information about discoverable
devices during a Bluetooth Inquiry. </p> <p><b>Intended
audience:</b> </p> <p>This document is intended to be used by Symbian platform
licensees and third party application developers. </p> </section>
<section id="GUID-3F8DF3A7-47F8-47C2-9F47-570D22E4C999"><title>Introduction</title> <p>A Bluetooth communication connection
is created by two or more devices within a piconet. A device that wishes to
create a connection must find which other devices/services are available.
The Inquiry is a request sent by a Bluetooth-enabled device (the "Inquiring
Device") over a separate physical channel, not within an existing piconet.
The Inquiry requests all listening ("discoverable") Bluetooth devices to identify
themselves. In the standard Inquiry Response each device responds with their
own MAC identifier. The Inquiring Device then has to issue a request to each
device to determine the local name and any services that each device can support.
Supported services may include stereo headset or FTP. </p> <p>The Extended
Inquiry Response (EIR) replaces the standard Inquiry Response and contains
additional information. </p> <p>Legacy devices are supported so the set of
responses from all devices may include both EIR and standard Inquiry Responses. </p> </section>
<section id="GUID-04C48C8B-491E-456C-A2E4-C2AB99A491B9"><title>EIR response values</title> <p>The Extended Inquiry Response
includes the following: </p> <ul>
<li id="GUID-01F8A0CA-CA3B-5032-B934-0AA84E41FAF3"><p>device local name </p> </li>
<li id="GUID-1D61827C-8B5B-55FD-BCDD-B416292FDED6"><p>service class UUIDs
of each service the device supports </p> </li>
<li id="GUID-71BE4DDD-4406-5633-AAAA-8A23061242F5"><p>the transmission power </p> </li>
<li id="GUID-E5CA163A-26F3-5031-8F2B-C0FB543C51FB"><p>manufacturer specific
values </p> </li>
</ul> <p><b>Device
local name</b> </p> <p>On a device such as a phone handset the device local
name may be set by the user. For example, "Tom's Nokia E71". Otherwise the
local name defined by the manufacturer, for example "MyTech BT Headset". The
EIR data packet is a fixed size so the number of characters available for
the device local name may be insufficient for the entire device local name.
The data sent is as many characters as fit starting with the first character.
The number of characters available depends on how many service IDs are sent
and so this length varies from device to device. A flag is available to indicate
whether the device local name sent is the complete name or a truncated version. </p> <p><b>Service class UUIDs of each service the device supports</b> </p> <p>A
Service Class UUID is a value which identifies a particular type of service/functionality
provided by the device. For example, there would be a Service Class UUID to
identify a printer, and another Service Class UUID to identify a stereo headset. </p> <p><b>Transmission Power</b> </p> <p>A one byte value containing a transmission
power level between -127dBm and +127dBm. The Transmission Power (Tx Power)
value is optional. May be used in conjunction with the Received Signal Strength
Indicator (RSSI) to calculate pathloss and give an estimate of which of two
or more responding devices is physically closer to the Inquiring Device. </p> <p><b>Manufacturer specific values</b> </p> <p>This is a set of 8-bit bytes
and all interpretation and structure is entirely down to the specific manufacturer. </p> </section>
<section id="GUID-8EEE55FA-89F0-4186-A2CF-F9B9C47AF4A6"><title>EIR tutorials</title> <ul>
<li id="GUID-23BDCDE6-F8F1-5FAD-BF2B-F87917DB0558"><p> <xref href="GUID-783D0B50-0E8A-5199-A07E-749D4A71E671.dita">Processing
an Extended Inquiry Response</xref>  </p> </li>
</ul> </section>
</conbody></concept>