Symbian3/SDK/Source/GUID-F2A793F1-A5B5-526B-B147-771D440B13A2.dita
changeset 7 51a74ef9ed63
equal deleted inserted replaced
6:43e37759235e 7:51a74ef9ed63
       
     1 <?xml version="1.0" encoding="utf-8"?>
       
     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
       
     3 <!-- This component and the accompanying materials are made available under the terms of the License 
       
     4 "Eclipse Public License v1.0" which accompanies this distribution, 
       
     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
       
     6 <!-- Initial Contributors:
       
     7     Nokia Corporation - initial contribution.
       
     8 Contributors: 
       
     9 -->
       
    10 <!DOCTYPE concept
       
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
       
    12 <concept id="GUID-F2A793F1-A5B5-526B-B147-771D440B13A2" xml:lang="en"><title>Bluetooth
       
    13 Extended Inquiry Response</title><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    14 <p>This is a guide to the Symbian platform Bluetooth implementation of Extended
       
    15 Inquiry Response (EIR). </p>
       
    16 <section id="GUID-F3729B8D-A900-41E2-868E-E04EFD21E76E"><title>Purpose</title> <p>EIR provides information about discoverable
       
    17 devices during a Bluetooth Inquiry. </p> <p><b>Intended
       
    18 audience:</b> </p> <p>This document is intended to be used by Symbian platform
       
    19 licensees and third party application developers. </p> </section>
       
    20 <section id="GUID-3F8DF3A7-47F8-47C2-9F47-570D22E4C999"><title>Introduction</title> <p>A Bluetooth communication connection
       
    21 is created by two or more devices within a piconet. A device that wishes to
       
    22 create a connection must find which other devices/services are available.
       
    23 The Inquiry is a request sent by a Bluetooth-enabled device (the "Inquiring
       
    24 Device") over a separate physical channel, not within an existing piconet.
       
    25 The Inquiry requests all listening ("discoverable") Bluetooth devices to identify
       
    26 themselves. In the standard Inquiry Response each device responds with their
       
    27 own MAC identifier. The Inquiring Device then has to issue a request to each
       
    28 device to determine the local name and any services that each device can support.
       
    29 Supported services may include stereo headset or FTP. </p> <p>The Extended
       
    30 Inquiry Response (EIR) replaces the standard Inquiry Response and contains
       
    31 additional information. </p> <p>Legacy devices are supported so the set of
       
    32 responses from all devices may include both EIR and standard Inquiry Responses. </p> </section>
       
    33 <section id="GUID-04C48C8B-491E-456C-A2E4-C2AB99A491B9"><title>EIR response values</title> <p>The Extended Inquiry Response
       
    34 includes the following: </p> <ul>
       
    35 <li id="GUID-01F8A0CA-CA3B-5032-B934-0AA84E41FAF3"><p>device local name </p> </li>
       
    36 <li id="GUID-1D61827C-8B5B-55FD-BCDD-B416292FDED6"><p>service class UUIDs
       
    37 of each service the device supports </p> </li>
       
    38 <li id="GUID-71BE4DDD-4406-5633-AAAA-8A23061242F5"><p>the transmission power </p> </li>
       
    39 <li id="GUID-E5CA163A-26F3-5031-8F2B-C0FB543C51FB"><p>manufacturer specific
       
    40 values </p> </li>
       
    41 </ul> <p><b>Device
       
    42 local name</b> </p> <p>On a device such as a phone handset the device local
       
    43 name may be set by the user. For example, "Tom's Nokia E71". Otherwise the
       
    44 local name defined by the manufacturer, for example "MyTech BT Headset". The
       
    45 EIR data packet is a fixed size so the number of characters available for
       
    46 the device local name may be insufficient for the entire device local name.
       
    47 The data sent is as many characters as fit starting with the first character.
       
    48 The number of characters available depends on how many service IDs are sent
       
    49 and so this length varies from device to device. A flag is available to indicate
       
    50 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
       
    51 Service Class UUID is a value which identifies a particular type of service/functionality
       
    52 provided by the device. For example, there would be a Service Class UUID to
       
    53 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
       
    54 power level between -127dBm and +127dBm. The Transmission Power (Tx Power)
       
    55 value is optional. May be used in conjunction with the Received Signal Strength
       
    56 Indicator (RSSI) to calculate pathloss and give an estimate of which of two
       
    57 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
       
    58 and all interpretation and structure is entirely down to the specific manufacturer. </p> </section>
       
    59 <section id="GUID-8EEE55FA-89F0-4186-A2CF-F9B9C47AF4A6"><title>EIR tutorials</title> <ul>
       
    60 <li id="GUID-23BDCDE6-F8F1-5FAD-BF2B-F87917DB0558"><p> <xref href="GUID-783D0B50-0E8A-5199-A07E-749D4A71E671.dita">Processing
       
    61 an Extended Inquiry Response</xref>  </p> </li>
       
    62 </ul> </section>
       
    63 </conbody></concept>