bluetooth specification version 1.1

Specification Volume 1

Specification of the Bluetooth SystemWireless connections made easy

Core

Version 1.1 February 22 2001

BLUETOOTH SPECIFICATION Version 1.1

page 2 of 1084

Revision HistoryThe Revision History is shown in Appendix I on page 886

ContributorsThe persons who contributed to this specification are listed in Appendix II on page 897.

Web SiteThis specification can also be found on the Bluetooth website: http://www.bluetooth.com

Disclaimer and Copyright NoticeThe copyright in these specifications is owned by the Promoter Members of Bluetooth SIG, Inc. (Bluetooth SIG). Use of these specifications and any related intellectual property (collectively, the Specification), is governed by the Promoters Membership Agreement among the Promoter Members and Bluetooth SIG (the Promoters Agreement), certain membership agreements between Bluetooth SIG and its Adopter and Associate Members (the Membership Agreements) and the Bluetooth Specification Early Adopters Agreements (1.2 Early Adopters Agreements) among Early Adopter members of the unincorporated Bluetooth special interest group and the Promoter Members (the Early Adopters Agreement). Certain rights and obligations of the Promoter Members under the Early Adopters Agreements have been assigned to Bluetooth SIG by the Promoter Members. Use of the Specification by anyone who is not a member of Bluetooth SIG or a party to an Early Adopters Agreement (each such person or party, a Member), is prohibited. The legal rights and obligations of each Member are governed by their applicable Membership Agreement, Early Adopters Agreement or Promoters Agreement. No license, express or implied, by estoppel or otherwise, to any intellectual property rights are granted herein. Any use of the Specification not in compliance with the terms of the applicable Membership Agreement, Early Adopters Agreement or Promoters Agreement is prohibited and any such prohibited use may result in termination of the applicable Membership Agreement or Early Adopters Agreement and other liability permitted by the applicable agreement or by aplicable law to Bluetooth SIG or any of its members for patent, copyright and/or trademark infringement. THE SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, SATISFACTORY QUALITY, OR REASONABLE SKILL OR CARE, OR ANY WAR-

2

22 February 2001


page 3 of 1084

RANTY ARISING OUT OF ANY COURSE OF DEALING, USAGE, TRADE PRACTICE, PROPOSAL, SPECIFICATION OR SAMPLE. Each Member hereby acknowledges that products equipped with the Bluetooth technology (Bluetooth Products) may be subject to various regulatory controls under the laws and regulations of various governments worldwide. Such laws and regulatory controls may govern, among other things, the combination, operation, use, implementation and distribution of Bluetooth Products. Examples of such laws and regulatory controls include, but are not limited to, airline regulatory controls, telecommunications regulations, technology transfer controls and health and safety regulations. Each Member is solely responsible for the compliance by their Bluetooth Products with any such laws and regulations and for obtaining any and all required authorizations, permits, or licenses for their Bluetooth Products related to such regulations within the applicable jurisdictions. Each Member acknowledges that nothing in the Specification provides any information or assistance in connection with securing such compliance, authorizations or licenses. NOTHING IN THE SPECIFICATION CREATES ANY WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING SUCH LAWS OR REGULATIONS. ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHTS OR FOR NONCOMPLIANCE WITH LAWS, RELATING TO USE OF THE SPECIFICATION IS EXPRESSLY DISCLAIMED. BY USE OF THE SPECIFICATION, EACH MEMBER EXPRESSLY WAIVES ANY CLAIM AGAINST BLUETOOTH SIG AND ITS PROMOTER MEMBERS RELATED TO USE OF THE SPECIFICATION. Bluetooth SIG reserves the right to adopt any changes or alterations to the Specification as it deems necessary or appropriate and to adopt a process for adding new Bluetooth profiles after the release of the Specification. Copyright 1999, 2000, 2001 3Com Corporation, Agere Systems, Inc., Ericsson Technology Licensing, AB, IBM Corporation, Intel Corporation, Microsoft Corporation, Motorola, Inc., Nokia Mobile Phones, Toshiba Corporation *Third-party brands and names are the property of their respective owners.

22 February 2001

3


page 4 of 1084

4

22 February 2001


page 5 of 1084

MASTER TABLE OF CONTENTSFor the Bluetooth Profiles, See Volume 2.Part A RADIO SPECIFICATION Contents .............................................................................................17 1 2 3 4 5 6 Scope ...................................................................................18 Frequency Bands and Channel Arrangement ......................19 Transmitter Characteristics...................................................20 Receiver Characteristics ......................................................24 Appendix A...........................................................................28 Appendix B...........................................................................31

Part B BASEBAND SPECIFICATION Contents .............................................................................................35 1 2 3 4 5 6 7 8 9 General Description .............................................................41 Physical Channel .................................................................43 Physical Links ......................................................................45 Packets.................................................................................47 Error Correction....................................................................67 Logical Channels..................................................................76 Data Whitening.....................................................................78 Transmit/Receive Routines...................................................79 Transmit/Receive Timing ......................................................85

10 Channel Control ...................................................................93 11 Hop Selection.....................................................................127 12 Bluetooth Audio..................................................................139 13 Bluetooth Addressing .........................................................143 14 Bluetooth Security ..............................................................149 15 List of Figures.....................................................................179 16 List of Tables ......................................................................18322 February 2001 5


page 6 of 1084

Part C LINK MANAGER PROTOCOL Contents .......................................................................................... 187 1 2 3 4 5 6 7 8 9 General .............................................................................. 191 Format of LMP ................................................................... 193 The Procedure Rules and PDUs........................................ 195 Connection Establishment ................................................. 234 Summary of PDUs ............................................................. 236 Test Modes......................................................................... 248 Error Handling.................................................................... 250 List of Figures .................................................................... 251 List of Tables ...................................................................... 253

Part D LOGICAL LINK CONTROL AND ADAPTATION PROTOCOL SPECIFICATION Contents .......................................................................................... 257 1 2 3 4 5 6 7 8 9 Introduction ........................................................................ 259 General Operation ............................................................. 263 State Machine .................................................................... 268 Data Packet Format ........................................................... 282 Signalling ........................................................................... 285 Configuration Parameter Options....................................... 299 Service Primitives .............................................................. 305 Summary ........................................................................... 323 References......................................................................... 324

10 List of Figures .................................................................... 325 11 List of Tables ...................................................................... 326 Terms and Abbreviations ........................................................ 327 Appendix A: Configuration MSCs ........................................... 328 Appendix B: Implementation Guidelines ................................. 331

6

22 February 2001


page 7 of 1084

Part E SERVICE DISCOVERY PROTOCOL (SDP) Contents ...........................................................................................335 1 Introduction ........................................................................337 2 Overview ............................................................................340 3 Data Representation ..........................................................351 4 Protocol Description...........................................................354 5 Service Attribute Definitions...............................................368 6 Appendix ............................................................................379 Appendix A Background Information .....................................380 Appendix B Example SDP Transactions ..............................381

Part F:1 RFCOMM WITH TS 07.10 Contents ...........................................................................................397 1 2 3 4 5 6 7 8 9 Part F:2 IrDA INTEROPERABILITY Contents ...........................................................................................429 1 2 3 4 5 6 7 Introduction ........................................................................430 OBEX Object and Protocol.................................................433 OBEX over RFCOMM........................................................437 OBEX over TCP/IP.............................................................439 Bluetooth Application Profiles using OBEX........................441 References.........................................................................443 List of Acronyms and Abbreviations ...................................44422 February 2001 7

Introduction ........................................................................399 RFCOMM Service Overview ..............................................401 Service Interface Description .............................................405 TS 07.10 Subset Supported by RFCOMM.........................406 TS 07.10 Adaptations for RFCOMM ..................................408 Flow Control .......................................................................417 Interaction with Other Entities ............................................421 References.........................................................................424 Terms and Abbreviations....................................................425


page 8 of 1084

Part F:3 TELEPHONY CONTROL PROTOCOL SPECIFICATION Contents .......................................................................................... 447 1 2 3 4 5 6 7 8 9 General Description ........................................................... 451 Call Control (CC)................................................................ 455 Group Management (GM).................................................. 465 Connectionless TCS (CL) .................................................. 472 Supplementary Services (SS) ........................................... 473 Message formats ............................................................... 476 Message coding................................................................. 488 Message Error handling..................................................... 504 Protocol Parameters .......................................................... 506

10 Bluetooth Standard Character Set ..................................... 507 11 References......................................................................... 508 12 List of Figures .................................................................... 509 13 List of Tables ...................................................................... 510 Appendix 1 - TCS Call States ................................................ 511

Part F:4 INTEROPERABILITY REQUIREMENTS FOR BLUETOOTH AS A WAP BEARER Contents 1 2 3 4 5 6 7 8 9 Introduction ........................................................................ 517 The Use of WAP In the Bluetooth Environment ................. 518 WAP Services Overview .................................................... 520 WAP in the Bluetooth Piconet ............................................ 524 Interoperability Requirements ............................................ 529 Service Discovery .............................................................. 530 Link Manager .................................................................... 534 Generic Modes ................................................................. 535 References......................................................................... 536

8

22 February 2001


page 9 of 1084

Part H:1 HOST CONTROLLER INTERFACE FUNCTIONAL SPECIFICATION Contents ...........................................................................................541 1 2 3 4 5 6 7 8 9 Introduction ........................................................................546 Overview of Host Controller Transport Layer .....................550 HCI Flow Control ................................................................551 HCI Commands..................................................................553 Events ................................................................................727 List of Error Codes .............................................................769 List of Acronyms and Abbreviations ...................................780 List of Figures.....................................................................781 List of Tables ......................................................................782

Part H:2 HCI USB TRANSPORT LAYER Contents ...........................................................................................785 1 2 3 4 5 Overview ............................................................................786 USB Endpoint Expectations ...............................................788 Class Code.........................................................................795 Device Firmware Upgrade..................................................796 Limitations ..........................................................................797

Part H:3 HCI RS232 TRANSPORT LAYER Contents ...........................................................................................801 1 2 3 4 5 6 7 General ..............................................................................802 Overview ............................................................................803 Negotiation Protocol...........................................................804 Packet Transfer Protocol.....................................................808 Using delimiters with COBS for synchronization ................809 Using RTS/CTS for Synchronization ..................................812 References.........................................................................818

22 February 2001

9


page 10 of 1084

Part H:4 HCI UART TRANSPORT LAYER Contents .......................................................................................... 823 1 2 3 4 General .............................................................................. 824 Protocol.............................................................................. 825 RS232 Settings.................................................................. 826 Error Recovery................................................................... 827

Part I:1 BLUETOOTH TEST MODE Contents .......................................................................................... 831 1 2 3 4 General Description ........................................................... 832 Test Scenarios ................................................................... 834 Outline of Proposed LMP Messages ................................. 843 References......................................................................... 846

Part I:2 BLUETOOTH COMPLIANCE REQUIREMENTS Contents .......................................................................................... 849 1 2 3 4 Scope................................................................................. 850 Definitions .......................................................................... 851 Legal Aspects .................................................................... 853 Introduction to the Bluetooth Qualification Program .......... 854

Part I:3 TEST CONTROL INTERFACE Contents .......................................................................................... 859 1 2 3 4 510

Introduction ........................................................................ 861 General Description ........................................................... 863 Test Configurations ............................................................ 868 TCI-L2CAP Specification ................................................... 870 Abbreviations ..................................................................... 88122 February 2001


page 11 of 1084

Appendix I REVISION HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883

Appendix II CONTRIBUTORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

Appendix III ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907

Appendix IV SAMPLE DATA Contents ...........................................................................................919 1 2 3 4 5 6 7 8 9 Encryption Sample Data ....................................................920 Frequency Hopping Sample DataMandatory Scheme...955 Access Code Sample Data ................................................968 HEC and Packet Header Sample Data ..............................971 CRC Sample Data..............................................................972 Complete Sample Packets .................................................973 Whitening Sequence Sample Data ....................................975 FEC Sample Data ..............................................................978 Encryption Key Sample Data .............................................979

22 February 2001

11


page 12 of 1084

Appendix V BLUETOOTH AUDIO Contents ........................................................................................ 1007 1 General Audio Recommendations ................................... 1008

Appendix VI BASEBAND TIMERS Contents ........................................................................................ 1015 1 Baseband Timers............................................................. 1016

Appendix VII OPTIONAL PAGING SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1019 Contents ........................................................................................ 1021 1 2 General ............................................................................ 1023 Optional Paging Scheme I ............................................... 1024

Appendix VIII BLUETOOTH ASSIGNED NUMBERS The former appendix Bluetooth Assigned Numbers is now published as a separate document and the latest version is always available at: http://www.bluetooth.org/assigned-numbers.htm

12

22 February 2001


page 13 of 1084

Appendix IX MESSAGE SEQUENCE CHARTS Contents .........................................................................................1031 1 2 3 4 5 6 7 8 9 Introduction ......................................................................1033 Services without connection request ...............................1034 ACL connection establishment and detachment ..............1038 Optional activities after ACL Connection establishment...1046 SCO Connection establishment and detachment ............1055 Special modes: sniff, hold, park .......................................1058 Buffer management, flow control......................................1064 Loopback Mode................................................................1066 List of Acronyms and Abbreviations .................................1069

10 List of Figures...................................................................1070 11 List of Tables ....................................................................1071 12 References .......................................................................1072

Index Alphabetical Index .........................................................................1073

22 February 2001

13


page 14 of 1084

14

22 February 2001

Part A

RADIO SPECIFICATION

BLUETOOTH SPECIFICATION Version 1.1 Radio Specification

page 17 of 1084

CONTENTS1 2 3 Scope ..................................................................................................18 Frequency Bands and Channel Arrangement .................................19 Transmitter Characteristics...............................................................20 3.1 MODULATION CHARACTERISTICS ........................................21 3.2 SPURIOUS EMISSIONS ...........................................................22 3.2.1 In-band Spurious Emission ...........................................22 3.2.2 Out-of-Band Spurious Emission ....................................23 3.3 RADIO FREQUENCY TOLERANCE .........................................23 Receiver Characteristics ...................................................................24 4.1 ACTUAL SENSITIVITY LEVEL..................................................24 4.2 INTERFERENCE PERFORMANCE ..........................................24 4.3 OUT-OF-BAND BLOCKING.......................................................25 4.4 INTERMODULATION CHARACTERISTICS..............................25 4.5 MAXIMUM USABLE LEVEL ......................................................26 4.6 SPURIOUS EMISSIONS ...........................................................26 4.7 RECEIVER SIGNAL STRENGTH INDICATOR (optional) .........26 4.8 REFERENCE SIGNAL DEFINITION .........................................27 Appendix A .........................................................................................28 Appendix B .........................................................................................31

4

5 6

22 February 2001

17


page 18 of 1084

18

22 February 2001


page 19 of 1084

1 SCOPEThe Bluetooth transceiver is operating in the 2.4 GHz ISM band. This specification defines the requirements for a Bluetooth transceiver operating in this unlicensed band. Requirements are defined for two reasons: Provide compatibility between the radios used in the system Define the quality of the system The Bluetooth transceiver shall fulfil the stated requirements under the operating conditions specified in Appendix A and Appendix B. The Radio parameters must be measured according to the methods described in the RFTest Specification.This specification is based on the established regulations for Europe, Japan and North America. The standard documents listed below are only for information, and are subject to change or revision at any time. Europe (except France and Spain): Approval Standards: European Telecommunications Standards Institute, ETSI Documents: ETS 300-328, ETS 300-826 Approval Authority: National Type Approval Authorities France: Approval Standards: La Reglementation en France por les Equipements fonctionnant dans la bande de frequences 2.4 GHz "RLAN-Radio Local Area Network" Documents: SP/DGPT/ATAS/23, ETS 300-328, ETS 300-826 Approval Authority: Direction Generale des Postes et Telecommunications Note: A new R&TTE EU Directive will be in effect by March 2000, with consequent effects on the manufacturers declaration of conformity and free circulation of products within the EU. Spain: Approval Standards: Supplemento Del Numero 164 Del Boletin Oficial Del Estado (Published 10 July 91, Revised 25 June 93) Documents: ETS 300-328, ETS 300-826 Approval Authority: Cuadro Nacional De Atribucion De Frecuesias Japan: Approval Standards: Association of Radio Industries and Businesses, ARIB Documents: RCR STD-33A Approval Authority: Ministry of Post and Telecommunications, MPT Note: The Japanese rules are in revision. Decisions on the revision will take place in Q2 1999. North Americas: Approval Standards: Federal Communications Commission, FCC, USA Documents: CFR47, Part 15, Sections 15.205, 15.209, 15.247 Approval Standards: Industry Canada, IC, Canada Documents: GL36 Approval Authority: FCC (USA), Industry Canada (Canada)

Scope

22 February 2001

19


page 20 of 1084

2 FREQUENCY BANDS AND CHANNEL ARRANGEMENTThe Bluetooth system is operating in the 2.4 GHz ISM (Industrial Scientific Medicine) band. In a vast majority of countries around the world the range of this frequency band is 2400 - 2483.5 MHz. Some countries have however national limitations in the frequency range. In order to comply with these national limitations, special frequency hopping algorithms have been specified for these countries. It should be noted that products implementing the reduced frequency band will not work with products implementing the full band. The products implementing the reduced frequency band must therefore be considered as local versions for a single market. The Bluetooth SIG has launched a campaign to overcome these difficulties and reach total harmonization of the frequency band.Geography USA, Europe and most other countries1) Regulatory Range 2.400-2.4835 GHz RF Channels f=2402+k MHz, k=0,,78

Table 2.1: Operating frequency bands Note 1. The Bluetooth Specification includes a special frequency hopping pattern to provide provisions for compliance with national limitations like in France. The frequency range for France is 2.4465 - 2.4835 GHz and the corresponding RF channels are f = 2454 + k MHz, k= 0,...,22. .

Channel spacing is 1 MHz. In order to comply with out-of-band regulations in each country, a guard band is used at the lower and upper band edge.Geography USA, Europe and most other countries Table 2.2: Guard Bands Lower Guard Band 2 MHz Upper Guard Band 3.5 MHz

20

22 February 2001

Frequency Bands and Channel Arrangement


page 21 of 1084

3 TRANSMITTER CHARACTERISTICSThe requirements stated in this section are given as power levels at the antenna connector of the equipment. If the equipment does not have a connector, a reference antenna with 0 dBi gain is assumed. Due to difficulty in measurement accuracy in radiated measurements, it is preferred that systems with an integral antenna provide a temporary antenna connector during type approval. If transmitting antennas of directional gain greater than 0 dBi are used, the applicable paragraphs in ETSI 300 328 and FCC part 15 must be compensated for. The equipment is classified into three power classes.Power Class Maximum Output Power (Pmax) Nominal Output Power Minimum Output Power1)

Power Control Pmin Link Key request to HostHCI Link Key Request event (BD_ADDR) HCI_Link_Key_Request_Reply (BD_ADDR, Link_Key) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status) LMP_au_rand (rand_nr)

If Link Key missed => Link Key request to HostHCI Link Key Request event (BD_ADDR) HCI_Link_Key_Request_Reply (BD_ADDR, Link_Key) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status)

LMP_sres (auth_res) HCI Authentication Complete event (Status=0x00, ConHandle)

Figure 4.1: Authentication Requested

1052

22 February 2001

Optional activities after ACL Connection

BLUETOOTH SPECIFICATION Version 1.1 Message Sequence Charts

page 1053 of 1084

4.2 SET CONNECTION ENCRYPTIONUsing the command HCI_Set_Connection_Encryption (Connection_Handle, Encryption_Enable), the Host is able to switch the encryption of a connection with the specified Connection_Handle to ON/OFF. This command can be applied on both the master- and slave sides (only the master side is shown in Figure 4.2 Set Connection Encryption). If this command occurs on the slave side, the only difference is that LMP_encryption_mode_req (encryption_mode) will be sent from the HC/LM Slave. LMP_encryption_key_size_req (key_size) and LMP_start_encryption_req (rand_nr) will still be requested from the HC/LM master.

Optional activities after ACL Connection establishment 22 February 2001

1053


page 1054 of 1084

Host-A

HC/LM-A Master

HC/LM-B Slave

Host-B

ACL Connection established Sub-scenario 1: Set Connection Encryption to ONHCI_Set_Connection_Encryption (ConHandle, Encr_Enable=ON) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_encryption_mode_req (encr_mode) LMP_accepted (opcode)

LMP_encryption_key_size_req (key_size) LMP_accepted (opcode)

LMP_start_encryption_req (rand_nr) LMP_accepted (opcode) HCI Encryption Change event (Status=0x00, ConHandle, Encr_Enable=ON) HCI Encryption Change event (Status=0x00, ConHandle, Encr_Enable=ON)

Sub-scenario 2: Set Connection Encryption to OFFHCI_Set_Connection_Encryption (ConHandle, Encr_Enable=OFF) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_encryption_mode_req (encr_mode) LMP_accepted (opcode)

LMP_stop_encryption_req () LMP_accepted (opcode)

HCI Encryption Change event (Status=0x00, ConHandle, Encr_Enable=OFF)

HCI Encryption Change event (Status=0x00, ConHandle, Encr_Enable=OFF)

Figure 4.2: Set Connection Encryption

1054

22 February 2001



page 1055 of 1084

4.3 CHANGE CONNECTION LINK KEYUsing the command HCI_Change_Connection_Link_Key (Connection_Handle), the Host can explicitly change the common link key shared between the BT Devices. Note: if the connection encryption was enabled and the temporary link key was used, it is the task of the BT Master to automatically restart the encryption (first stop and then restart) after the link key is successfully changed.

Figure 4.3: Change Connection Link Key

4.4 MASTER LINK KEYThe Figure 4.4 Master Link Key shows how the Host can explicitly switch between the temporary Link Key and the semi-permanent Link Key. Since this command can only be used for the BT Master, the Link Key switch will affect all connections. Note: if encryption was enabled, it is the task of the BT Master to restart the encryption separately for each slave.


1055


page 1056 of 1084

Figure 4.4: Master Link Key1056 22 February 2001 Optional activities after ACL Connection


page 1057 of 1084

4.5 READ REMOTE SUPPORTED FEATURESUsing the command HCI_Read_Remote_Supported_Features (Connection_Handle) the supported LMP Features of a remote BT Device can be read. These features contain supported packet types, supported modes, supported audio coding modes, etc. Note: if the LMP Features was exchanged during ACL Connection Setup, the HC/LM A may return the Read Remote Supported Features Complete event (Status, Connection_Handle, LMP_Features) without exchange of LMP PDUs.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Read_Remote_Supported_Features (ConHandle) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_features_req (features) LMP_features_res (features)

HCI Read Remote Supported Features Complete event (Status=0x00, ConHandle, LMP_Features)

Figure 4.5: Read Remote Supported Features

4.6 READ CLOCK OFFSETUsing the command HCI_Read_Clock_Offset (Connection_Handle) the BT Master can read the Clock Offset of the BT Slaves. The Clock Offset can be used to speed up the paging procedure in a later connection attempt. If the command is requested from the slave device, the HC/LM Slave will directly return a Command Status event and an Read Clock Offset Complete event without exchange of LMP PDUs.


1057


page 1058 of 1084

Host-A

HC/LM-A Master

HC/LM-B Slave

Host-B

ACL Connection establishedHCI_Read_Clock_Offset (ConHandle) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_clkoffset_req () LMP_clkoffset_res (clock_offset) HCI Read Clock Offset Complete event (Status=0x00, ConHandle, Clock_Offset)

Figure 4.6: Read Clock Offset

4.7 READ REMOTE VERSION INFORMATIONUsing HCI_Read_Remote_Version_Information (Connection_Handle) the version information consisting of LMP_Version, Manufacturer_Name and LMP_Subversion from the remote BT Device can be read.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Read_Remote_Version_Information (ConHandle) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_version_req (VersNr, CompId, SubVersNr) LMP_version_res (VersNr, CompId, SubVersNr) HCI Read Remote Version Information Complete event (Status=0x00, ConHandle, LMP_Version, ..)

Figure 4.7: Read Remote Version Information

1058

22 February 2001



page 1059 of 1084

4.8 QOS SETUPTo set up the Quality of Service, the command HCI_QoS_Setup (Connection_Handle, Flags, Service_Type, Token_Rate, Peak_Bandwidth, Latency, Delay_Variation) is used.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_QoS_Setup (ConHandle, Flags, Service_Type, ..) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_quality_of_service_req (poll_interval, N_bc) LMP_accepted (opcode)

HCI QoS Setup Complete event (Status=0x00, ConHandle, Flags, ..)

HCI QoS Setup Complete event (Status=0x00, ConHandle, Flags, ..)

Figure 4.8: QoS Setup


1059


page 1060 of 1084

4.9 SWITCH ROLEThe command HCI_Switch_Role (BD_ADDR, Role) can be used to explicitly switch the current role of the local BT Device for a particular connection with the specified BT Device (BD_ADDR). The local HC/LM has to check whether the switch is performed or not.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection established Sub-scenario 1: Master requires the Master/Slave Switch

/* Master-Role */ HCI_Switch_Role (BD_ADDR, Role=Slave)

/* Slave-Role */

HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_switch_req () LMP_slot_offset (slot_offset, BD_ADDR) LMP_accepted (opcode)

/* Master-Role */

Sub-scenario 2: Slave requires the Master/ Slave Switch

/* Slave-Role */

HCI_Switch_Role (BD_ADDR, Role=Master) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode)

LMP_slot_offset (slot_offset, BD_ADDR) LMP_switch_req () LMP_accepted (opcode)

Master/Slave Switch (common for sub-scenario 1 and 2)TDD-Switch ...

FHS (BD_ADDR, CoD, ..) "FHS-Ack" (ID-Packet)

Use new channel pameters ... /* Slave-Role */ HCI Role Change event (Status=0x00, BD_ADDR, New_Role=Slave) /* Master-Role */ HCI Role Change event (Status=0x00, BD_ADDR, New_Role=Master)

Figure 4.9: Switch Role

1060

22 February 2001



page 1061 of 1084

5 SCO CONNECTION ESTABLISHMENT AND DETACHMENT5.1 SCO CONNECTION SETUPSCO Connection setup requires an established ACL Connection. It is the task of the Host to create an ACL Connection first and then the SCO Link. Note: On the slave side, an incoming connection request can be automatically accepted by using HCI_Set_Event_Filter (Filter_Type, Filter_Condition_Type, Condition) with the Filter_Type = 0x02 /*Connection_Setup*/. Furthermore, for each SCO Link to a BT Device, a separate SCO Connection Handle is needed. 5.1.1 Master activates the SCO Connection setup To set up an SCO Connection, the HCI_Add_SCO_Connection (Connection_Handle, Packet_Type) command is used. The specified Connection_Handle is related to the ACL Connection that must have been created before the HCI_Add_SCO_Connection is issued.

Host-A

HC/LM-A Master

HC/LM-B Slave

Host-B

ACL Connection establishedHCI_Add_SCO_Connection (ACL_ConHandle, Packet_Type) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_sco_link_req (SCO_handle, timing_control_flags, ..) HCI Connection Request event (BD_ADDR, CoD, Link_Type=SCO) HCI_Accept_Connection_Request (BD_ADDR, Role) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_accepted (opcode)

HCI Connection Complete event (Status=0x00, SCO_ConHandle, ..)


Figure 5.1: SCO Connection setup (activated from master)

SCO Connection establishment and detachment

22 February 2001

1061


page 1062 of 1084

5.1.2 Slave activates the SCO Connection setup The same command HCI_Add_SCO_Connection (Connection_Handle, Packet_Type) can be used to create an SCO Link when the local BT Device is a BT Slave. Here the specified Connection_Handle belongs to the established ACL Connection between the BT Devices. Compared to 5.1.1, the only difference is that the HC/LM Slave starts the SCO Setup with LMP_sco_link_req first.

Host-A

HC/LM-A Master

HC/LM-B Slave

Host-B

ACL Connection establishedHCI_Add_SCO_Connection (ACL_ConHandle', Packet_Type) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_sco_link_req (..)

HCI Connection Request event (BD_ADDR, CoD, Link_Type=SCO) HCI_Accept_Connection_Request (BD_ADDR, Role) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_sco_link_req (..) LMP_accepted (opcode)



Figure 5.2: SCO Connection setup (activated from slave)

1062

22 February 2001

SCO Connection establishment and


page 1063 of 1084

5.2 SCO DISCONNECTIONAn established SCO Connection can be detached at any time. Since several SCO Connections can exist between a BT Master and a BT Slave, an SCO Disconnection only removes the SCO Link with the specified SCO Connection Handle. The other SCO Connections will still exist.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Disconnect (SCO_ConHandle, Reason) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_remove_sco_link_req (SCO_handle) LMP_accepted (opcode)

HCI Disconnection Complete event (Status=0x00, SCO_ConHandle, ..)

HCI Disconnection Complete event (Status=0x00, SCO_ConHandle, ..)

Figure 5.3: SCO Disconnection

SCO Connection establishment and detachment

22 February 2001

1063


page 1064 of 1084

6 SPECIAL MODES: SNIFF, HOLD, PARKEntry into sniff, hold or park mode requires an established ACL Connection. The following table summarizes the modes and the BT Role that can request, force, activate or exit the modes.

Sniff Request Force Activation Release Master/Slave Master Master Master/Slave

Hold Master/Slave Master/Slave Master/Slave Automatic

Park Master/Slave Master Master Master/Slave

Table 6.1: Summary of modes (Sniff, Hold, Park)

6.1 SNIFF MODESniff Mode is used when a slave shall participate in the piconet only in a sniff interval. For the Sniff Mode negotiation, the Host specifies the Sniff_Max_Interval and the Sniff_Min_Interval so that HC/LM will be able to choose the one sniff interval in this range. The used command is HCI_Sniff_Mode (Connection_Handle, Sniff_Max_Interval, Sniff_Min_Interval, Sniff_Attempt, Sniff_Timeout). Since Sniff Mode is a periodic mode, the command HCI_Exit_Sniff_Mode (Connection_Handle) is needed to return to Active Mode.

1064

22 February 2001

Special modes: sniff, hold, park


page 1065 of 1084

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Sniff_Mode (ConHandle, Sniff_Max_Interval, ..) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode)

/* A=Master */

Sub-scenario 1: Master forces Slave in Sniff ModeLMP_sniff (timing_control_flags, D_sniff, ..)

/* B=Slave */

/* A=Master or Slave */

Sub-scenario 2: Master or Slave requests Sniff ModeLMP_sniff_req (timing_control_flags, D_sniff, ..) LMP_accepted (opcode)

/* B=Slave or Master */

Sniff Mode startedHCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Sniff, ..)

HCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Sniff, ..)

Sub-scenario 3: Exit Sniff ModeHCI_Exit_Sniff_Mode (ConHandle) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) LMP_unsniff_req () LMP_accepted (opcode)

HCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Active, ..)


Figure 6.1: Sniff Mode

6.2 HOLD MODEHold Mode is useful when a BT Device doesnt want to participate in the connection for a Hold Mode Length. Using the command HCI_Hold_Mode (Connection_Handle, Hold_Max_Length, Hold_Min_Length), the Host specifies the Hold_Max_Length and Hold_Min_Length. The HC/LM will then be able to negotiate a Hold Mode Length in this range. When the hold mode is startedSpecial modes: sniff, hold, park 22 February 2001 1065


page 1066 of 1084

or complete, Mode Change event (Status, Connection_ Handle, Current_Mode, Interval) will be used to inform the Host about the actual mode. Note: the Hold Mode is exited when the Hold Mode Length has expired, so it is no guarantee that the remote BT Device is immediately active.

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Hold_Mode (ConHandle, Hold_Mode_Max_Interval, ..) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) /* A=Master */

Sub-scenario 1: Master forces Hold ModeLMP_hold (hold_time)

/* B=Slave */

/* A=Slave */

Sub-scenario 2: Slave forces Hold ModeLMP_hold (hold_time) LMP_hold (hold_time)

/* B=Master */

/* A=Master or Slave */

Sub-scenario 3: Master or Slave negotiates Hold ModeLMP_hold_req (hold_time) ... LMP_accepted (opcode)

/* B=Slave or Master */

Hold Mode startedHCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Hold, ..) HCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Hold, ..)

Hold Mode completeHCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Active, ..) HCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Active, ..)

Figure 6.2: Hold Mode

1066

22 February 2001



page 1067 of 1084

6.3 PARK MODEPark Mode is used to render the slaves inactive but still synchronized to the master using the beacon interval. In park mode, broadcast is performed. 6.3.1 Enter park mode Using the command HCI_Park_Mode (Connection_Handle, Beacon_Max_Interval, Beacon_Min_Interval) the Host specifies the Beacon_Max_Interval and Beacon_Min_Interval so that HC/LM can set up a Beacon-Interval in this range for the BT Slaves. In Park Mode, the BT Slave gives up its AM_ADDR.


22 February 2001

1067


page 1068 of 1084

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Park_Mode (ConHandle, Beacon_Max_Interval, ..) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode) /* A=Master */

Sub-scenario 1: Master forces Slave into Park ModeLMP_park (timing_control_flags, D_b, ..)

/* B=Slave */

/* A=Master */

Sub-scenario 2: Master requests Slave into Park ModeLMP_park_req () LMP_accepted (opcode)

/* B=Slave */

LMP_park (timing_control_flags, D_b, ..)

/* A=Slave */

Sub-scenario 3: Slave requests to be put into Park ModeLMP_park_req () LMP_park (timing_control_flags, D_b, ..)

/* B=Master */

Park Mode startedHCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Park, ..) HCI Mode Change event (Status=0x00, ConHandle, Current_Mode=Park, ..)

/* A=Master */

Optional LM Actions during Park ModeLMP_set_broadcast_scan_window (timing_control_flags, D_b, ..) LMP_modify_beacon (timing_control_flags, D_b, ..)

/* B=Slave */

Figure 6.3: Enter Park Mode

6.3.2 Exit Park Mode Since Park Mode is a periodic mode, the command HCI_Exit_Park_Mode (Connection_Handle) will be used to return to Active Mode. A parked BT Slave can send an Access_Request_Message to request to leave the Park Mode. It is the task of master HC/LM to use LMP_unpark_PM_ADDR_req (..) or LMP_unpark_BD_ADDR_req (..) to unpark a BT Slave.1068 22 February 2001 Special modes: sniff, hold, park


page 1069 of 1084

Host-A

HC/LM-A

HC/LM-B

Host-B

ACL Connection establishedHCI_Exit_Park_Mode (ConHandle) HCI Command Status event (Status, Num_Cmd, Cmd_OpCode)

/* A=Master */

Sub-scenario 1: Master unparks Slave using BD_ADDRLMP_unpark_BD_ADDR_req (timing_control_flags, D_b, BD_ADDR, ..) LMP_accepted (opcode)

/* B=Slave */

/* to all slaves */

/* only from this slave */

/* A=Master */

Sub-scenario 2: Master unparks Slave using PM_ADDRLMP_unpark_PM_ADDR_req (timing_control_flags, D_b, BD_ADDR, ..) LMP_accepted (opcode)

/* B=Slave */

/* to all slaves */

/* only from this slave */

/* A=Slave */

Sub-scenario 3: Slave unparks itself"Access_Request_Message" (ID-Packet)

/* B=Master */

LMP_unpark_BD_ADDR/ PM_ADDR_req (timing_control_flags, D_b, ..) LMP_accepted (opcode)



Figure 6.4: Exit Park Mode


22 February 2001

1069


page 1070 of 1084

7 BUFFER MANAGEMENT, FLOW CONTROLThe HC Data buffers are configured by the HC and managed by the Host. On initialization, the Host will issue HCI_Read_Buffer_Size. This specifies the maximum allowed length of HCI data packets sent from the Host to the HC, and the maximum number of ACL and SCO data packets that the HC can store in its buffer. After a connection is created, HC will frequently inform the Host about the number of sent packets using Number Of Completed Packets event (Number_of_Handles, Connection_Handle[I], HC_Num_Of_ Completed_Packets[i]) (see Figure 7.1 Host-to-HC flow control).

Host-A

HC/LM-A

HC/LM-B

Host-B

InitialisationHCI_Read_Buffer_Size ()

HCI Command Complete event (Status, ACL_Data_Packet_Length, ..)

ACL and/or SCO Connection establishedHCI-ACL or HCI-SCO data packets ... Baseband data packets ... HCI-ACL or HCI-SCO data packets ...

HCI Number Of Completed Packets event (Num_of_Handles, ConHandle[i], ..)

Figure 7.1: Host to HC flow control

Accordingly the HC to Host flow control can be applied in the same way so that during initialization the Host configures the Buffer Size and later the Host Controller will manage the Host Buffers. Using HCI_Set_Host_Controller_To_Host_Flow_Control (Flow_Control_Enable) the Host can decide to apply the HC to Host flow control or not. For flow control itself HCI_Host_Buffer_Size (Host_ACL_Data_Packet_Length, Host_SCO_Data_Packet_Length, Host_Total_Num_ACL_Data_Packets, Host_Total_Num_SCO_Data_Packets) and HCI_Host_Number_Of_Completed_Packets (Number_of_Handles, Connection_Handle[I], Host_Num_Of_Completed_Packets[I]) will be used (for details see Figure 7.2 HC to Host Flow Control).

1070

22 February 2001

Buffer management, flow control


page 1071 of 1084

Host-A

HC/LM-A

HC/LM-B

Host-B

InitialisationHCI_Set_Host_Controller_To_Host_Flow_Control (Flow_Control_Enable=ON) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status) HCI_Host_Buffer_Size (Host_ACL_Data_Packet_Length, ..) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status)

ACL and/or SCO Connection establishedHCI-ACL or HCI-SCO data packets ... Baseband data packets ... HCI-ACL or HCI-SCO data packets ...

HCI_Host_Number_Of_Completed_Packets (Num_of_Handles, ConHandle[i], ..)

Figure 7.2: HC to Host Flow Control

Buffer management, flow control

22 February 2001

1071


page 1072 of 1084

8 LOOPBACK MODE8.1 LOCAL LOOPBACK MODEThe local Loopback Mode is used to loopback received HCI Commands, and HCI ACL and HCI SCO packets sent from the Host. The HC will send four Connection Complete events (one for ACL, three for SCO Connections) so that the Host can use the Connection_Handles to resend HCI ACL and HCI SCO Packet to HC. To exit the local Loopback Mode, HCI_Write_Loopback_Mode (Loopback_Mode=0x00) or HCI_Reset ( ) will be used.

1072

22 February 2001

Loopback Mode


page 1073 of 1084

Host

HC/LM

Enter Local Loopback ModeHCI_Write_Loopback_Mode (Loopback_Mode=local loopback) HCI Connection Complete event (Status, ACL_ConHandle, BD_ADDR, Link_Type=ACL, Encr_Mode) HCI Connection Complete event (Status, SCO_ConHandle1, BD_ADDR, Link_Type=SCO, Encr_Mode) HCI Connection Complete event (Status, SCO_ConHandle2, BD_ADDR, Link_Type=SCO, Encr_Mode) HCI Connection Complete event (Status, SCO_ConHandle3, BD_ADDR, Link_Type=SCO, Encr_Mode) HCI Command Complete event (Num_Cmd, Cmd_OpCode=HCI_Write_Loopback, Status)

Sub-scenario 1: loopback HCI-ACL and HCI-SCO packetsHCI-ACL, HCI-SCO packets .. /* loopback all received HCI-ACL and HCI-SCO packets */

HCI-ACL, HCI-SCO packets ..

Sub-scenario 2: loopback HCI Command packetsHCI-Command packets .. /* Special commands like HCI_Buffer_Size .. will not be looped back */

HCI Loopback Command event (HCI_Command_Packet)

Exit Local Loopback ModeHCI_Write_Loopback_Mode (Loopback_Mode=no loopback) HCI Disconnection Complete event (Status=0x00, SCO_ConHandle1, Reason) HCI Disconnection Complete event (Status=0x00, SCO_ConHandle2, Reason) HCI Disconnection Complete event (Status=0x00, SCO_ConHandle3, Reason) HCI Disconnection Complete event (Status=0x00, ACL_ConHandle, Reason) HCI Command Complete event (Num_Cmd, Cmd_OpCode=HCI_Write_Loopback_Mode, Status)

Figure 8.1: Local Loopback Mode

Loopback Mode

22 February 2001

1073


page 1074 of 1084

8.2 REMOTE LOOPBACK MODEThe remote Loopback Mode is used to loopback all received Baseband ACL and SCO Data received from a remote BT Device. During remote Loopback Mode, ACL and SCO Connection can be created. The remote Loopback Mode can be released with the command HCI_Write_Loopback_Mode (Loopback_Mode=0x00).

Host-A

HC/LM-A

HC/LM-B

Host-B

Enter Remote Loopback ModeHCI_Write_Loopback_Mode (Loopback_Mode=remote loopback) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status)

Create ACL Connection Create SCO ConnectionsHCI-ACL, HCI-SCO packets ..

Baseband ACL-, SCO-Packets ..

Baseband ACL-, SCO-Packets ..

HCI-ACL, HCI-SCO packets ..

Exit Remote Loopback Mode

Remove SCO Connections Remove ACL ConnectionHCI_Write_Loopback_Mode (Loopback_Mode=no loopback) HCI Command Complete event (Num_Cmd, Cmd_OpCode, Status)

Figure 8.2: Remote Loopback Mode

1074

22 February 2001

Loopback Mode


page 1075 of 1084

9 LIST OF ACRONYMS AND ABBREVIATIONS

BT HC HCI LAP LC LM LMP MSC PDU

Bluetooth Host Controller Host Controller Interface Lower Address Part Link Controller Link Manager Link Manager Protocol Message Sequence Chart Protocol Data Unit

List of Acronyms and Abbreviations

22 February 2001

1075


page 1076 of 1084

10 LIST OF FIGURESFigure 2.1: Figure 2.2: Figure 2.3: Figure 3.1: Figure 3.2: Figure 3.3: Figure 3.4: Figure 3.5: Figure 3.6: Figure 4.1: Figure 4.2: Figure 4.3: Figure 4.4: Figure 4.5: Figure 4.6: Figure 4.7: Figure 4.8: Figure 4.9: Figure 5.1: Figure 5.2: Figure 5.3: Figure 6.1: Figure 6.2: Figure 6.3: Figure 6.4: Figure 7.1: Figure 7.2: Figure 8.1: Figure 8.2: Remote Name Request ......................................................... 1035 One-Time Inquiry ................................................................... 1036 Periodic Inquiry ...................................................................... 1037 Overview of ACL Connection establishment and detachment....... 1038 ACL Connection Request phase ........................................... 1040 ACL Connection setup with pairing........................................ 1042 ACL Connection setup with authentication ............................ 1043 Encryption and Setup complete ............................................. 1044 ACL Disconnection ................................................................ 1045 Authentication Requested...................................................... 1046 Set Connection Encryption .................................................... 1048 Change Connection Link Key ................................................ 1049 Master Link Key ..................................................................... 1050 Read Remote Supported Features ........................................ 1051 Read Clock Offset.................................................................. 1052 Read Remote Version Information......................................... 1052 QoS Setup ............................................................................. 1053 Switch Role ............................................................................ 1054 SCO Connection setup (activated from master) .................... 1055 SCO Connection setup (activated from slave)....................... 1056 SCO Disconnection ............................................................... 1057 Sniff Mode.............................................................................. 1059 Hold Mode ............................................................................. 1060 Enter Park Mode.................................................................... 1062 Exit Park Mode ...................................................................... 1063 Host to HC flow control .......................................................... 1064 HC to Host Flow Control ........................................................ 1065 Local Loopback Mode............................................................ 1067 Remote Loopback Mode........................................................ 1068

1076

22 February 2001

List of Figures


page 1077 of 1084

11 LIST OF TABLESTable 6.1: Summary of modes (Sniff, Hold, Park)...................................1058

List of Tables

22 February 2001

1077


page 1078 of 1084

12 REFERENCES[1] [2] [3] [4] Baseband Specification on page 33 Link Manager Protocol on pag e183 Host Controller Interface Functional Specification on page 535 Logical Link Control and Adaptation Protocol Specification on page253

1078

22 February 2001

References


page 1079 of 1084

Alphabetical IndexNumerics0x7E 808 CRC 806 CRC-CCITT 809, 810 CTS 812 current link key 201

AAbort- 436 ACCESS RIGHTS ACCEPT 467 ACCESS RIGHTS REJECT 467 ACCESS RIGHTS REQUEST 467 Ack Code 805 Ack code 804 Acknowledgement Timer (T1) 412 ALERTING 458 asynchronous notifications 526 AT+CMUX 410 authentication 196

DData Link Connection Identifier 403 data throughput 401 DCE 402 default URL 527 delayed loopback 838 Delimiter 806 delimiter 0x7E 809 delimiter, 0x7E 808 direction bit 413 DISC command 414 DISC command frame 410 DISCONNECT 462 Disconnect-request 435 DNS 521 drift 207 DTE 402, 411 DTMF ACKNOWLEDGE 474 DTMF start & stop 473 DTR/DSR 417

Bbasic option 406, 408 Baud Rate 805 baud rate 401, 804 beacon 218 beginning delimiter 809 Bluetooth 430 BOF(0x7E) 810 Briefcase Trick 518 business card 431 byte ordering 400 byte stream 437

EEIATIA-232-E 399, 401 eliminating zeros 809 emergency call 496 emulated ports 403 encryption 203 ending delimiter 809 EOF(0x7E) 810 Error detection 804 error message packet 809, 813 Error Message Packet (0x05) 803 error packet 812 Error Recovery 807 error recovery 804, 808 error recovery procedure 809, 812 Error Type 810, 813 ETSI TS 07.10 437 external call 496

CCall Control 451 CALL PROCEEDING 457 Calling Line Identity 473 checksum 809 CL INFO 472 claimant 196 clock offset 206 COBS 808, 809, 811 COBS code block 811 COBS code byte 811 commands in TS 07.10 406 Configuration distribution 465 CONNECT 458 Connect-request 434 Consistent Overhead Byte Stuffing 809 control channel 406 convergence layer 407

FFast inter member access 46522 February 2001 1079

BLUETOOTH SPECIFICATION Version 1.1 Confidential Bluetooth FCoff 417 FCon 417 flow control 417 Forbidden Message 519 frame types 406

page 1080 of 1084

MManagement Entity 526 Maximum Frame Size (N1) 412 Modem Status Command 407 multiple bearers 526 multiplexer control channel 410 Multiplexer Control commands 414

Ggenerator polynomial 809 Get-request 436 Group Management 451

Nname request 212 negotiation packet 804, 805 Negotiation Packet (0x06) 803 negotiation phase 804 null modem 402 null modem emulation 401 number of data bit 804 number of stop bit 804

HHCI RS232 Transport Layer 802 header ID 433 hold mode 213 Host Controller Interface 526 HTML 523 HTTP 521, 523

Iin-band tones/announcements 459 INFO ACCEPT 468 INFO SUGGEST 468 INFORMATION 457 initialisation key 197 intercom call 496 Internet Engineering Task Force (IETF) 522 interoperability 529 interrupt latency 804 IrCOMM 432 IrDA 430 IrMC 441 IrOBEX 430

OOBEX 430 OBEX session protocol 433 Obtain access rights 465 output power 224

Ppaging scheme 232 parity type 804 park mode 218 payload heade 193 PIN 197 PN command 415 port emulation entity 421 port proxy entity 421 Protocol Mode 806 protocol mode 804 protocol mode 0x13 809 protocol mode 0x14 812 Proxy/gateway Addressing 527 Put-request 435

JJavaScript 523 jitter 207

LL2CAP channel 423 latency requirements 423 link key 196 link loss notification 411, 423 link supervision 233 LISTEN REJECT 470 LISTEN REQUEST 469 LISTEN SUGGEST 469 loop back test 841 low power mode 423

QQ.931 451 Quality of Service 227

Rregister recall 473 RELEASE 462 RELEASE COMPLETE 462 reliability 423 reliable transmission 412

1080

22 February 2001


page 1081 of 1084

Response Timer for Multiplexer Control Channel (T2) 412 resynchronization 808 resynchronize 812 retransmission holding buffer 809, 813 retransmission packets 809, 812 RFCOMM 430 RFCOMM entity 403 RFCOMM multiplexer 410 RFCOMM reference model 405 RFCOMM Server Channel 421 RFCOMM server channels 403, 413 RFCOMM session 403, 410 RLS command 415 RPN command 414 RS-232 399, 401, 421 RS232 802 RS-232 control signals 402, 407 RS232 Transport Packet 803 RSSI 224 RTS 812 RTS/CTS 417, 804 RTS/CTS Mode 806

synchronize 812

TTCP 523 TCP port number 439 TCP/IP 430 TCS Binary 451 Tdetect 804 Tdetect Time 806 Tdetect time 812 temporary link key 201 test mode 248, 832 Tiny TP 432 transmitter test 837 TS 07.10 399 TS 07.10 multiplexer 403, 423

UUART 804 UART Settings 805 UDP 522 Uniform Resource Locators 527 unit key 200 URL 525 User Addressing 527

SSABM command 410 SCO link 228 semi-permanent link key 201, 202 SEQ No with Error 809 sequence number 803 sequence number field 809, 812 Sequence Number with Error field 809, 812 serial port emulation entity 405 service call 496 Service Discovery Protocol 524, 530 service records 421 SetPath- 436 SETUP 455 SETUP ACKNOWLEDGE 457 simple error recovery scheme 812 Smart Kiosk 519 sniff mode 216 SSL 523 START DTMF 474 START DTMF REJECT 474 STOP DTMF 474 STOP DTMF ACKNOWLEDGE 474 supervision timeout 233 synchronization 809

VvCalendar 431 vCard 431 verifier 196 vMessage 431 vNotes 431

WWAP Client 520 WAP Proxy/gateway 521 WAP Server 521 WDP 522 Wireless User Group 465 WSP 522 WTLS 522 WTP 522 WUG 465

XXML 523 XON/XOFF 417

Zzero elimination 811

22 February 2001

1081

BLUETOOTH SPECIFICATION Version 1.1 Confidential Bluetooth

page 1082 of 1084

1082

22 February 2001

1084