Honda Exhibit 1017
`
`Page 1
`
`

`
`Bluetoothm
`
`Connect Without Cables
`
`Second Edition
`
`Jennifer Bray
`Charles F. Sturman
`
`ISBN U-L3-flhhlflb-E
`
`90000
`
`Prentice Hall PT/5?
`[)1 1
`l"l‘R Upper Saddle River, New Jersey 07458
`'—" www.phptr.com
`
`9 790130 66106
`
`Honda Exhibit 1017
`
`Page 2
`
`

`
`Library of Congress Cataloging-in-Publication Data
`
`Bray, Jennifer.
`Bluetooth 1.]: connect without cablesllennifer Bray, Charles Sturman.—2nd ed.
`p.cm.
`Includes bibliographical references and index.
`ISBN 0-13-066106-6
`1. Bluetooth technology. 2. Te1ecommunication—Equipment and supplies. 3. Computer
`network protocols. l. Stunnan, Charles F. ll. Title.
`
`'I'K5l03.3 .B72 2002
`004.6'2—dc21
`
`2001054573
`
`Publisher: Bernard Goodwin
`Editorial Assistant: Michelle Vincenti
`Marketing Manager: Dan DePasquale
`International Product Manager: Mike Vaccaro
`Manufacturing Buyer: Alexis Heydt-Long
`Cover Design: Talar Agasyan~Booruju
`Cover Design Director: Jeny Votta
`Cover Photograph: Charles F. Sturman
`Compositor/Production Services: Pine Tree Composition, Inc.
`
`M 1
`[-1 1,»
`' ‘
`
`© 2002 by Prentice Hall PTR
`Prentice-Hall, lnc.
`Upper Saddle River, NJ 07458
`
`BLUETOOTH is a trademark owned by Bluetooth SIG. lnc., USA.
`
`All products or services mentioned in this book are the trademarks or service marks of their respective
`companies or organizations.
`
`Some material in Chapter 10 © ETSI 1999, TS 101 369 v3 is the property of ETSI. Further use, modification.
`redistribution is strictly prohibited and must be the subject of another Copyright Authorisation.
`The above-mentioned standard may be obtained from the ETSI Publication Office, publications @etsi.fr,
`Tel: +33 (0)4 92 94 42 41 or downloaded from the website at http:J!www.etsi.org/eds/eds.htm
`
`All rights reserved. No part of this book may be
`reproduced, in any form or by any means, without
`permission in writing from the publisher.
`
`Printed in the United States of America
`
`ISBN O-I3-066106-6
`
`Pearson Education Ltd., London
`Pearson Education Australia Pty, Limited, Sydney
`Pearsonliducation Singapore, Pte. Ltd,
`Pearson Education North Asia Ltd. Hong Kong
`Pearson Education Canada, Ltd., Toronto
`Pearson Educacion de Mexico, S.A. de C.V.
`Pearson Education-—Japan, Tokyo
`Pearson Education Malaysia, Pte. Ltd.
`
`Honda Exhibit 1017
`
`Page 3
`
`

`
`Foreward to the Second Edition
`
`Foreward to the First Edition
`
`Preface to the Second Editon
`
`Preface to the First Editon
`
`Acknowledgments
`
`Introduction
`
`1 Overview
`
`1.1
`1.2
`1.3
`
`1.4
`
`1.5
`
`Bluetooth's Origins
`The Bluetooth SIG
`Aims
`
`The Protocol Stack
`
`Security
`
`Honda Exhibit 1017
`
`Page 4
`
`

`
`1.6
`
`1.7
`
`Applications and Profiles
`
`Using Bluetooth
`
`1.8 Management
`
`Test and Qualification
`1.9
`1.10 Bluetooth in Context
`
`1.11
`
`Summary
`
`Protocol Stack Part 1—The Bluetooth Module
`
`2 Antennas
`
`2.1
`
`2.2
`
`2.3
`2.4
`
`2.5
`2.6
`
`2.7
`
`Radiation Pattern
`
`Gains and Losses
`
`Types of Antennas
`Ceramic Antennas
`
`On-chip Antennas
`Antenna Placement
`
`Summary
`
`3 Radio
`
`3.1
`
`Introduction
`
`Frequency Hopping
`3.2
`3.3 Modulation
`
`3.4
`3.5
`
`3.6
`
`3.7
`
`3.8
`3.9
`
`Symbol Timing
`Power Emission and Control
`
`Radio Performance Parameters
`
`Simple RF Architecture
`
`RF System Timing
`Blue RF
`
`3.10
`
`Summary
`
`4 Baseband
`
`4.1
`
`4.2
`
`Introduction
`
`Bluetooth Device Address
`
`Honda Exhibit 1017
`
`Page 5
`
`

`
`4.3 Masters, Slaves, and Piconets
`
`4.4
`
`4.5
`4.6
`
`4.7
`
`4.8
`
`System Timing
`
`Physical Links: SCO and ACL
`Bluetooth Packet Structure
`
`Packet Types and Packet Construction
`
`Logical Channels
`
`Channel Coding and Bitstream Processing
`4.9
`4.10 Timebase Synchronisation and Receive Correlation
`
`4.11
`
`Frequency Hopping
`
`4.12 Summary
`
`5
`
`The Link Controller
`
`5. 1
`
`5.2
`
`5.3
`
`5.4
`
`5.5
`
`5.6
`
`Introduction
`
`Link Control Protocol
`
`Link Controller States
`
`Link Controller Operation
`
`Piconet Operation
`
`Scattemet Operation
`
`5.7 Master/ Slave Role Switching
`
`5.8
`5.9
`
`Low-Power Operation
`Baseband I Link Controller Architectural Overview
`
`5.10 Summary
`
`6 Audio
`
`6. 1
`
`6.2
`
`6.3
`6.4
`
`6.5
`
`6.6
`6.7
`
`6.8
`
`6.9
`
`Introduction
`
`Audio Transports in the Protocol Stack
`
`Quality and Bandwidth
`SCO Links
`
`Audio CODECs
`
`Audio Subsystem
`Audio Data Formats and HCI
`
`Implementation
`
`Summary
`
`Honda Exhibit 1017
`
`Page 6
`
`

`
`T-
`
`viii
`
`7
`
`The Link Manager
`
`7.1
`
`7.2
`
`7.3
`7.4
`
`7.5
`7.6
`
`7.7
`7.8
`
`7.9
`
`LMP Protocol Data Units (PDUS)
`
`The Link Management Channel
`
`Link Setup
`LMP Link Shutdown
`
`Role Change
`Control of Multi-Slot Packets
`
`Security
`Low-Power Modes
`
`Power Control
`
`7.10 Quality of Service
`
`7.1 1
`
`Information Messages
`
`Supported Features
`7.12
`7.13 LMP Version
`
`7.14 Name Request
`7.15 Test Mode
`
`7.16
`
`Summary
`
`8
`
`The Host Controller Interface
`
`8.1
`
`8.2
`8.3
`
`8.4
`
`8.5
`
`8.6
`
`8.7
`
`8.8
`
`8.9
`
`HCI Packet Types
`
`The HCI Transport Layer
`Flow Control
`
`Configuring Modules
`
`Inquiring: Discovering Other Bluetooth Devices
`
`Inquiry Scan: Becoming Discoverable
`
`Paging: Initiating Connections
`
`Page Scan: Receiving Connections
`
`Sending and Receiving Data
`
`8.10 Switching Roles
`8.1 1
`Power Control
`
`8.12 Summary
`
`Honda Exhibit 1017
`
`Page 7
`
`

`
`Protocol Stack Part 2—The Bluetooth Host
`
`9
`
`Logical Link Control and Adaptation Protocol
`
`9.] Multiplexing Using Channels
`
`9.2
`
`9.3
`
`9.4
`
`9.5
`
`9.6
`9.7
`
`9.8
`9.9
`
`L2CAP Signalling
`
`Establishing a Connection
`
`Configuring a Connection
`
`Transferring Data
`
`Disconnecting and Timeouts
`Connectionless Data Channels
`
`Enabling and Disabling Incoming Connectionless Traffic
`Handling Groups
`
`9.10 Echo and Ping
`9.11 Get Information
`
`9.12 L2CAP State Machine
`
`9.13
`
`Implementation-Dependent Issues
`
`9.14 Summary
`
`10 RFCOMM
`
`10.1
`
`10.2
`
`10.3
`
`10.4
`10.5
`
`Serial Ports and UARTs
`
`Types of RFCOMM Devices
`
`RFCOMM Frame Types
`
`Connecting and Disconnecting
`Structure of RFCOMM Frames
`
`10.6 Multiplexer Frames
`10.7
`Service Records
`
`10.8
`
`Summary
`
`11
`
`The Service Discovery Protocol
`11.1
`SDP Client/Server Model
`
`11.2
`
`The SDP Database
`
`11.3
`
`Browsing SDP Records
`
`Honda Exhibit 1017
`
`Page 8
`
`

`
`11.4
`
`11.5
`
`11.6
`
`1 1.7
`
`Universally Unique Identifiers (UUIDs)
`
`SDP Messages
`
`Service Discovery Profile
`
`Summary
`
`The Wireless Application Protocol
`12.1
`The WAP Forum
`
`12.2
`
`12.3
`
`The WAP Stack
`
`PPP Links
`
`12.4 WAP Clients and Servers
`
`12.5
`
`12.6
`
`Suspend and Resume
`
`Service Discovery
`
`12.7 WAP Interoperability
`
`12.8
`
`12.9
`
`Using WAP
`
`Summary
`
`OBEX and IrDA
`
`13.1
`
`13.2
`13.3
`
`13.4
`
`OBEX in the Bluetooth Stack
`
`Object Model
`Session Protocol
`
`Summary
`
`Telephony Control Protocol
`
`14.]
`
`14.2
`
`14.3
`
`14.4
`
`TCS Signalling
`
`Call Establishment Signalling
`
`Call Clearing Signalling
`
`DTMF Signalling
`
`14.5 Wireless User Group (WUG) Signalling
`
`14.6
`14.7
`
`14.8
`
`Connectionless Signalling
`TCS Call States
`
`Summary
`
`Honda Exhibit 1017
`
`Page 9
`
`

`
`.
`I rI
`
`5':
`
`Contents
`
`xi
`
`Protocol Stack Part 3-—Cross Layer Functions
`
`15 Encryption and Security
`
`15.1
`15.2
`
`15.3
`
`15.4
`15.5
`
`15.6
`
`15.7
`
`Key Generation and the Encryption Engine
`Secret Keys and PINS
`
`Pairing and Bonding
`
`Starting Encryption
`Security Modes
`
`Security Architecture
`
`Summary
`
`Low-Power Operation
`
`16.1
`16.2
`
`16.3
`
`16.4
`
`16.5
`
`Controlling Low-Power Modes
`Hold Mode
`
`Sniff Mode
`
`Park Mode
`
`Low-Power Oscillator
`
`16.6
`
`Summary
`
`Quality of Service
`
`17.1
`
`17.2
`
`17.3
`
`17.4
`
`17.5
`
`17.6
`
`17.7
`
`Requesting QOS
`
`QOS Violations
`
`Flushing and Delays
`
`Link Supervision
`
`Broadcast Channel Reliability
`
`Data Rates and Packet Types
`
`Summary
`
`18 Managing Bluetooth Devices
`
`18.1
`
`18.2
`
`Link Configuration and Management
`
`Device Manager Architecture
`
`Honda Exhibit 1017
`
`Page 10
`
`

`
`Security Management
`
`Integrating Applications
`
`Accounting Management
`
`Capacity
`
`User Interface Design
`
`Summary
`
`App1ications—The Bluetooth Profiles
`
`19
`
`Foundation Profiles
`
`19.1
`
`19.2
`
`19.3
`
`19.4
`19.5
`
`19.6
`
`19.7
`
`19.8
`
`Structure of Profiles
`
`The Generic Access Profile
`
`The Serial Port Profile
`
`Dial Up Networking
`FAX Profile
`
`Headset Profile
`
`LAN Access Point Profile
`
`Generic Object Exchange Profile
`
`Object Push Profile
`19.9
`19.10 File Transfer Profile
`
`19.11
`19.12
`
`Synchronisation Profile
`Intercom Profile
`
`19.13 The Cordless Telephony Profile
`19.14 Benefits of Profiles
`
`19.15
`
`Summary
`
`Draft Post — Foundation Profiles
`
`20.1
`
`20.2
`
`20.3
`
`20.4
`
`20.5
`20.6
`
`The Human Interface Device Profile
`
`The Hands-Free Profile
`
`The Basic Imaging Profile
`
`The Basic Printing Profile
`
`The Hard Copy Cable Replacement Profile
`Summary.
`
`Honda Exhibit 1017
`
`Page 11
`
`

`
`Contents
`
`21
`
`Personal Area Networking
`
`21.1
`
`21.2
`
`21.3
`
`The PAN Profile
`
`Bluetooth Network Encapsulation Profile
`Summary
`
`ESDP for UPnP
`
`22.1
`
`22.2
`
`22.3
`
`22.4
`
`Universal Plug and Play Device Architecture
`L2CAP Based Solutions
`
`IP Based Solutions
`
`Summary
`
`Test and Qualification
`
`Test Mode
`
`23.1
`
`23.2
`
`23.3
`
`23.4
`
`23.5
`
`Activating Test Mode
`
`Controlling Test Mode
`Radio Transmitter Test
`
`Loopback Test
`
`Summary
`
`Qualification and Type Approval
`24.1
`
`Bluetooth Qualification
`
`24.2
`
`24.3
`
`24.4
`
`Bluetooth Interoperability Testing
`
`Regulatory Type Approval
`
`Summary
`
`Bluetooth in Context
`
`Implementation
`25.1
`Introduction
`
`25.2
`
`25.3
`
`25.4
`
`System Partitioning
`
`Hardware Integration Options
`Bluetooth as an IP Core
`
`Honda Exhibit 1017
`
`Page 12
`
`

`
`25.5
`
`ASIC Prototyping and FPGAs
`
`25.6 Making the Right Design Choices
`
`25 .7
`
`25.8
`
`Radio Implementation
`
`Summary
`
`Related Standards and Technologies
`
`26.1
`
`Introduction
`
`26.2 What Are the Requirements?
`26.3
`Infrared Data Association (IrDA)
`
`26.4
`26.5
`
`26.6
`26.7
`26.8
`
`Digital Enhanced Cordless Telecommunications (DECT)
`IEEE 802.11
`
`The HomeRFTM Working Group (HRFWG)
`IEEE 802.15 and the Wireless Personal Area Network (WPAN)
`HIPERLAN
`
`26.9 MMAC
`
`26.10 The Future
`
`Summary
`26.11
`26.12 Useful Web Addresses
`
`The Bluetooth Market
`
`27.1
`
`Introduction
`
`27.2 Market Pull and Technology Push
`
`27.3 Market Segments
`
`27.4
`
`27.5
`27.6
`
`27.7
`
`27.8
`
`Success in the Marketplace
`
`Enabling Technologies and Components
`Consumer Products
`
`The Bluetooth Brand
`
`Summary
`
`Future Developments
`
`28.1 Working Groups and New Bluetooth Profiles
`28.2
`Profile Working Groups
`
`28.3
`
`28.4
`
`Future Bluetooth Core Specifications
`
`Summary
`
`Honda Exhibit 1017
`
`Page 13
`
`

`
`Appendix—Bluetooth 1.1 Updates
`
`Glossary
`
`References
`
`Index
`
`Honda Exhibit 1017
`
`Page 14
`
`

`
` Iii:éfac‘ét0the
`
`First Edition
`
`This book came about from a conversation in the Hotel Mercure bar in Brussels, Belgium.
`We had just finished the first day of client training in our Bluetooth solution, and hadn't
`said a single word about our implementation yet! Why? Well, Bluetooth was so new that
`nobody knew much about it, there were no textbooks, no courses, nothing but a thick
`specification document and a few white papers. So before we could begin to explain the
`fine details of what we'd done, we had to spend a day explaining the Bluetooth specif1ca—
`tion. After the first beer, we thought somebody ought to write a book about Bluetooth;
`after the second beer, we thought we should do it; after the last beer, we had a contents
`page.
`
`Why the title? Well, “Connect Without Cables” is basically what Bluetooth started
`out doing. It’s a short range wireless communication system, and the word “wireless”
`pretty much says it all. The first applications people came up with were all about throwing
`away the clutter of cables that plagues modern portable devices—Bluetooth took away
`the cable dangling from a headset, removed the clutter of wires at the back of a PC, and
`let a phone talk to a PDA without needing a cable that took up more pocket space than ei-
`ther device. Now there are more imaginative uses than straight cable replacement, from
`small wireless office networks to the much hyped Personal Area Network, or PAN. But
`the basic functionality that Bluetooth provides is still
`the same: connection without
`cables.
`
`Honda Exhibit 1017
`
`Page 15
`
`

`
`Preface to the First Edition
`
`During the last year or so, we have seen a Bluetooth system design evolve from ab-
`stract idea to evaluation board. Along the way, we struggled to understand the Bluetooth
`specification. Some parts of it don’t make sense until you’ve read later parts, some parts
`don’t make sense until you’ve tried them out, and some of the parts we started with will
`never make- sense and have since been corrected. The specification is in a much better
`state than the preliminary versions we started with, but like all such things, it's still not an
`easy read. So this book aims to provide people working with Bluetooth an easier introduc-
`tion than the one we had.
`
`A new version of the Bluetooth specification (version 1.1) is due to be published
`during the 4th quarter of 2000. In order to keep this text consistent, we only consider the
`existing version l.OB specification except for one or two proposed corrections for v1.1,
`which are especially worth mentioning here. Although these are mostly minor improve-
`ments and clarifications to the existing l.OB specification, it is important for the reader to
`keep abreast of any revisions particularly since there may well be other refinements be-
`fore the major evolution which Bluetooth 2.0 will represent. To facilitate this, there is a
`companion Website to accompany Bluetooth: Connect Without Cables where we will
`place any errata and useful updates to the text as Bluetooth evolves.
`
`Honda Exhibit 1017
`
`Page 16
`
`

`
`Bluetooth has been the subject of much hype and media attention over the last couple of
`years. As various manufacturers prepare to launch products using Bluetooth technology,
`an unsuspecting public is about to be catapulted into the next stage of the information
`technology revolution.
`Bluetooth is a low cost, low power, short range radio technology, originally devel-
`oped as a cable replacement to connect devices such as mobile phone handsets, headsets,
`and portable computers. This in itself sounds relatively innocuous; however, by enabling
`standardised wireless communications between any electrical devices, Bluetooth has cre-
`ated the notion of a Personal Area Network (PAN), a kind of close range wireless network
`that looks set to revolutionise the way people interact with the information technology
`landscape around them.
`
`No longer do people need to connect, plug into, install, enable, or configure any-
`thing to anything else. Through a ubiquitous standardised communications subsystem, de-
`
`Honda Exhibit 1017
`
`Page 17
`
`

`
` 'm
`
`Overview
`
`vices will communicate seamlessly. One does not need to know where one’s cellular
`phone is, or even if it is switched on. As soon as the Web browser appears on the mobile
`computer screen, a link is established with the phone the Internet Service Provider is con-
`nected to, and the user is surfing the Web.
`The Bluetooth specification is an open, global specification defining the complete
`system from the radio right up to the application level. The protocol stack is usually im-
`plemented partly in hardware and partly as software running on a microprocessor, with
`different implementations partitioning the functionality between hardware and software in
`different ways.
`
`1.1 BLUETOOTH’S ORIGINS
`
`Version 1.0 of the Bluetooth specification came out in 1999, but Bluetooth started five
`years earlier, in 1994, when Ericsson Mobile Communications began a study to examine
`alternatives to the cables that linked its mobile phones with accessories. The study looked
`at using radio links. Radio isn't directional, and it doesn’t need line of sight, so it has ob-
`vious advantages over the infra-red links previously used between handsets and devices.
`There were many requirements for the study, including handling both speech and data, so
`that it could connect phones to both headsets and computing devices.
`Out of this study was born the specification for Bluetooth wireless technology. The
`specification is named after Harald Blatand (Blatand is Danish for Bluetooth), Harald was a
`tenth-century Danish Viking king who united and controlled Denmark and Norway. The
`name was adopted because Bluetooth wireless technology is expected to unify the telecom-
`munications and computing industries.
`
`1.2 THE BLUETOOTH SIG
`
`The Bluetooth Special Interest Group (SIG) is a group of companies working together to
`promote and define the Bluetooth specification. The Bluetooth SIG was founded in Feb-
`ruary 1998 by the following group of core promoters:
`
`- Ericsson Mobile Communications AB.
`
`~ Intel Corp.
`- IBM Corp.
`- Toshiba Corp.
`° Nokia Mobile Phones.
`
`In May 1998, the core promoters publicly announced the global SIG and invited other
`companies to join the SIG as Bluetooth adopters in return for a commitment to support the
`Bluetooth specification. The core promoters published version 1.0 of the Bluetooth speci-
`
`Honda Exhibit 1017
`
`Page 18
`
`

`
`The Bluetooth SIG
`
`3
`
`fication in July 1999, on the Bluetoofli Web site, http://www.bluetooth.com. In December
`1999, the Bluetooth core promoters group enlarged with the addition of four more major
`companies:
`
`- Microsoft.
`- Lucent.
`- 3COM.
`- Motorola.
`
`1.2.1
`
`Joining the Bluetooth SIG
`
`Any incorporated company willing to sign the Bluetooth SIG membership agreement can
`join the SIG as a Bluetooth adopter company. To join the SIG, companies simply fill in a
`form on the Bluetooth Web site, www.bluetooth.com. This form commits SIG members
`to contributing any key technologies which are needed to implement Bluetooth.
`This commitment to share technology means that Bluetooth SIG member compa-
`nies who put their products through Bluetooth qualification are granted a free license to
`build products using the Bluetooth wireless technology. The license is important because
`there are patents required to implement Bluetooth; companies that do not sign the Blue-
`tooth adopter’s agreement will not be entitled to use the technology. This offer proved so
`attractive that by April 2000, the SIG membership had grown to 1,790 members.
`In addition to getting a free license to patents needed to implement Bluetooth wire-
`less technology, Bluetooth SIG members also have permission to use the Bluetooth brand.
`There are restrictions on the use of the brand, and these are set out in the Bluetooth brand
`book. The trademark may only be used on products which prove they are correctly fol-
`lowing the Bluetooth specification by completing the Bluetooth qualification program (a
`testing process).
`
`To get the Bluetooth figure mark and instructions on how to use it, companies sign
`the Bluetooth trademark agreement, also available on www.bluetooth.com. Questions on
`the Bluetooth trademark can be emailed to brand.manager@Bluetooth.com.
`
`1.2.2 Bluetooth SIG Organisation
`
`At the head of the Bluetooth SIG is the program management board. This board oversees
`the operations of a number of other groups as shown in Figure 1-1.
`The main work of defining the specification is done by the technical working
`groups. Adopter companies can apply to become associate members of the SIG; they may
`then apply to join working groups and hence contribute directly to the forming of Blue-
`tooth specifications.
`
`Sitting on the technical working groups is quite time-consuming, and so many com-
`panies with valid comments on the specification do not have the resources to sit on the
`working groups. These companies can pass comments via email to the writers of the stan-
`dard and can also participate in an online discussion forum on the Bluetooth Web site.
`
`Honda Exhibit 1017
`
`Page 19
`
`

`
`' Program" _
`_
`"Management
`Board
`
`Overview
`
`Bluetooth
`
`Regulatory Z
`
`Legal
`Committee
`
`i
`
`‘
`
`.
`
`.
`_,
`
`-
`
`.
`Marketmg
`
`-
`
`_ Qualification
`Review Board
`/Logo_
`
`’
`
`lxrchiteeture
`Review
`Board
`
`.
`
`' S b I‘
`U '
`5
`gmups
`
`H
`g
`_
`.
`".5‘?3's-
`
`_
`'
`
`__
`_
`" ""AE'i'raii"t&"(3i)v‘i-iéirs
`_.a,nd .R9Vi9V.V P001.
`M... .‘,.
`,,_. -i --
`\_4..
`
`_
`
`_
`
`"
`.. _.
`
`T
`
`"Bluetooth"
`
`-i
`
`Technical
`I
`'-'_A__dv'i.s_ory Board ..
`
`..
`
`..B[u,e.{°.6m,..\._,_i.
`Qualification ‘
`L Adminigtratqr-5:
`.
`..
`_
`..
`Qualification =
`Body
`‘
`
`_
`
`'
`‘_
`
`Figure 1-1 Organisation of the Bluetooth SIG.
`
`1.3 AIMS
`
`Why should a group with such diverse interests as the Bluetooth promoters cooperate?
`Basically, because it’s good for their businesses. The members of the Bluetooth promot-
`ers group all stand to gain something from mobile devices communicating better, whether
`by selling devices that have enhanced functionality or by selling the extra software that
`people will need once they can more easily access information on the move.
`The reasons for making the Bluetooth specification freely available to anyone who
`cares to sign an adopter’s agreement are basically die same. The Bluetooth promoters
`group has made Bluetooth an open specification, rather than keeping it restricted and pro-
`prietary, because consumers are more likely to adopt a technology which can be bought
`from many manufacturers than one which is just limited to a select few. Wide acceptance
`
`Honda Exhibit 1017
`
`Page 20
`
`

`
`The Protocol Stack
`
`5
`
`among consumers is likely to lead to a larger overall market for Bluetooth devices. So the
`promoters will gain from more companies becoming involved in the Bluetooth SIG.
`The aim of the Bluetooth specification is basically to sell more of the core promoters‘
`products. This will happen because Bluetooth will make their products more useful by im-
`proving communications between them. Before the advent of Bluetooth, telecommunica-
`tions and computing devices were usually connected by cables, which were easily broken or
`lost. Cables are also awkward to carry around. The Bluetooth specification aimed to ease
`communication between mobile devices by providing a cable replacement.
`Being a cable replacement technology imposes several requirements. If Bluetooth
`technology is to replace cables, it can’t be much more expensive than a cable or nobody will
`buy it. At the time of writing, a data cable for a cellular mobile phone was about $10. Allo-
`cate half the cost of the cable to each end of the link and it’s obvious that for a cable re-
`placement technology to be attractive on purely financial grounds, each unit should cost no
`more than $5. So, the two ends of the link should cost the same as the cable they replace.
`Because Bluetooth technology is designed for mobile devices, it must be able to run
`on batteries. So, it must be very low power, and should run on low voltages. It must also
`be lightweight and small enough not to intrude on the design of compact mobile devices
`such as cellular phones, headsets, and PDAs.
`It must be as easy and convenient to use as plugging in a cable, and it must be as re-
`liable as the cable it replaces. Because it is a wireless technology, to be reliable, Bluetooth
`must also be resilient. Reliability means it works overall; resilience means that it can cope
`with errors.
`
`So, Bluetooth aims to be widely available, inexpensive, convenient, easy to use, re-
`liable, small, and low power. If Bluetooth achieves all these goals, it will be incredibly
`good for the businesses involved with it.
`
`1.4 THE PROTOCOL STACK
`
`A key feature of the Bluetooth specification is that it aims to allow devices from lots of
`different manufacturers to work with one another. To this end, Bluetooth does not just de-
`fine a radio system, it also defines a software stack to enable applications to find other
`Bluetooth devices in the area, discover what services they can offer, and use those
`services.
`
`The Bluetooth stack is defined as a series of layers, though there are some features
`which cross several layers.
`Every block in Figure 1-2 corresponds to a chapter in the core Bluetooth specifica-
`tion. The core specification also has three chapters on test and qualification:
`
`° Bluetooth Test Mode.
`
`- Bluetooth Compliance Requirements.
`° Test Control Interface.
`
`Honda Exhibit 1017
`
`Page 21
`
`

`
`-
`
`Overview
`
`The Bluetooth Profiles give guidelines on
`how applications should use the Bluetooth
`protocol stack
`
`‘ TCS (Telephony Control Protocol Specifi-
`cation) provides telephony services
`
`SDP (Service Discovery Protocol) lets
`Bluetooth devices discover what services
`other Bluetooth devices support
`
`WAP and OBEX provide interfaces to the
`higher layer parts of other Communica-
`tions Protocols
`
`RFCOMM provides an RS232 like serial
`interface
`
`.
`Loglcal Link Control and Adaptation
`"
`‘ ' ""'
`
`“'
`
`-_'.
`
`Logical Link Control and adaptation multi-
`plexes data from higher layers, and con-
`verts between different Packet sizes
`
`-- __
`.
`ntroller Interface
`'*" ‘-
`-—=
`
`-- -.-
`
`-
`
`-
`
`The Host Controller Interface handles
`communications between a separate host
`and a Bluetooth module
`
`The link manager controls and configures
`links to other devices
`
`..
`
`__
`
`'nk Controller
`‘-
`" v
`
`‘ ~
`
`The Baseband and Link Controller controls
`the physical links via the radio, assembling
`packets and controlling frequency hopping
`
`The radio modulates and demodulates
`data for transmission and reception on air
`
`Flgure 1-2 The Bluetooth protocol stack.
`
`The Bluetooth specification encompasses more than just the core specification. There are
`also profiles which give details of how applications should use the Bluetooth protocol
`stack, and a brand book which explains how the Bluetooth brand should be used.
`
`1.4.1 The OSI Reference Model
`
`Figure 1-3 shows the familiar Open Systems Interconnect (OSI) standard reference model
`for communications protocol stacks. Although Bluetooth does not exactly match the
`model, it is a useful exercise to relate the different parts of the Bluetooth stack to the vari-
`
`Honda Exhibit 1017
`
`Page 22
`
`

`
`The Protocol Stack
`
`«-
`
`'«A'p"p'iiati:§ Lay} ''
`
`Presentation Layer
`
`'
`
`I...
`
`.—.- - " - ..... »'
`
`t'Controllerl
`
`te_ ceiti-li
`
`. ""
`k Layer
`
`Physical Layer I
`
`I
`
`OSI Reference
`Model
`
`Bluetooth
`
`Figure 1-3 OSI reference model and Bluetooth.
`
`ous parts of the model. Since the reference model is an ideal, well-partitioned stack, the
`comparison serves to highlight the division of responsibility in the Bluetooth stack.
`The Physical Layer is responsible for the electrical interface to the communications
`media, including modulation and channel coding. It thus covers the radio and part of the
`baseband.
`
`The Data Link Layer is responsible for transmission, framing, and error control
`over a particular link, and as such, overlaps the link controller task and the control end of
`the baseband, including error checking and correction.
`From now on, it gets a little less clear. The Network Layer is responsible for data
`transfer across the network, independent of the media and specific topology of the net-
`work. This encompasses the higher end of the link controller, setting up and maintaining
`multiple links, and also covering most of the Link Manager (LM) task. The Transport
`Layer is responsible for the reliability and multiplexing of data transfer across the net-
`work to the.level provided by the application, and thus overlaps at the high end of the LM
`and covers the Host Controller Interface (I-ICI), which provides the actual data transport
`mechanisms.
`
`The Session Layer provides the management and data flow control services, which
`are covered by L2CAP and the lower ends of RFCOMM/SDP. The Presentation Layer
`provides a common representation for Application Layer data by adding service structure
`to the units of data, which is the main task of RFCOMM/SDP. Finally, the Application
`Layer is responsible for managing communications between host applications.
`
`Honda Exhibit 1017
`
`Page 23
`
`

`
`1.4.2 The Physical Layer
`
`Bluetooth devices operate at 2.4 GHz in the globally available, licence-free ISM band.
`This band is reserved for general use by Industrial, Scientific, and Medical (ISM) applica-
`tions, which obey a basic set of power and spectral emission and interference specifica-
`tions. This means d1atBluetooth has to be very robust, as there are a great many existing
`users and polluters of this shared spectrum.
`The operating band is divided into 1 Ml-Iz-spaced channels, each signalling data at
`1 Megasymbol per second so as to obtain the maximum available channel bandwidth.
`With the chosen modulation scheme of GFSK (Gaussian Frequency Shift Keying), this
`equates to 1 Mb/s. Using GFSK, a binary 1 gives rise to a positive frequency deviation
`from the nominal carrier frequency, while a binary 0 gives rise to a negative frequency
`deviation.
`
`After each packet, both devices retune their radio to a different frequency, effec-
`tively hopping from radio channel to radio channel (FHSS—frequency hopping spread
`spectrum). In this way, Bluetooth devices use the whole of the available ISM band and if
`a transmission is compromised by interference on one channel, the retransmission will al-
`ways be on a different (hopefully clear) channel. Each Bluetooth time slot lasts 625 mi-
`croseconds, and, generally, devices hop once per packet, which will be every slot, every 3
`slots, or every 5 slots.
`Designed for low-powered portable applications, the radio power must be min-
`imised. Three different power classes are defined, which provide operation ranges of ap-
`proximately 10 m, 20 m, and 100 m; the lowest power gives up to 10 In range, the highest
`up to 100 in.
`
`1.4.3 Masters, Slaves, Slots, and Frequency Hopping
`
`If devices are to hop to new frequencies after each packet, they must all agree on the se-
`quence of frequencies they will use. Bluetooth devices can operate in two modes: as a Mas-
`ter or as a Slave. It is the Master that sets the frequency hopping sequence. Slaves
`synchronise to the Master in time and frequency by following the Master's hopping
`sequence.
`Every Bluetooth device has a unique Bluetooth device address and a Bluetooth
`clock. The baseband part of the Bluetooth specification describes an algorithm which can
`calculate a frequency hop sequence from a Bluetooth device address and a Bluetooth
`clock. When Slaves connect to a Master, they are told the Bluetooth device address and
`clock of the Master. They then use this to calculate the frequency hop sequence. Because
`all Slaves use the Master’s clock and address, all are synchronised to the Master’s fre-
`quency hop sequence.
`In addition to controlling the frequency hop sequence, the Master controls when de-
`vices are allowed to transmit. The Master allows Slaves to transmit by allocating slots for
`voice traffic or data traffic. In data traffic slots, the Slaves are only allowed to transmit when
`replying to a transmission to them by the Master. In voice traffic slots, Slaves are required to
`transmit regularly in reserved slots whether or not they are replying to the Master.
`
`Honda Exhibit 1017
`
`Page 24
`
`

`
`Point to point
`
`Point to multipoint
`
`Figure 1-4 Point to point and point to multipoint piconets.
`
`The Master controls how the total available bandwidth is divided among the Slaves
`by deciding when and how often to communicate with each Slave. The number of time
`slots each device gets depends on its data transfer requirements. The system of dividing
`time slots among multiple devices is called Time Division Multiplexing (TDM).
`
`1.4.4 Piconets and Scatternets
`
`A collection of Slave devices operating together with one common Master is referred to
`as a piconet (see Figure l—4). All devices on a piconet follow the frequency hopping se-
`quence and timing of the Master.
`In Figure 1-4, the piconet on the left with only one Slave illustrates a point to point
`connection. The piconet on the right with three Slaves talking to the Master illustrates a
`point to multipoint connection. The Slaves in a piconet only have links to the Master;
`there are no direct links between Slaves in a piconet.
`The specification limits the number of Slaves in a piconet to seven, with each Slave
`only communicating with the shared Master. However, a larger coverage area or a greater
`number of network members may be realized by linking piconets into a scattemet, where
`some devices are members of more than one piconet (see Figure 1-5).
`When a device is present in more than one piconet, it must time-share, spending
`a few slots on one piconet and a few slots on the other. On the left in Figure 1-5 is a
`
`Figure 1-5 Scattemets.
`
`Honda Exhibit 1017
`
`Page 25
`
`

`
`*
`
`Overview
`
`scattemet where one device is a Slave in one piconet and a Master in another. On the right
`is a scattemet where one device is a Slave in two piconets. It is not possible to have a de-
`vice which is a Master of two different piconets, since all Slaves in a piconet are synchro-
`nised to the Master's hop sequence. By definition, all devices with the same Master must
`be on the same piconet.
`In addition to the various sources of interference mentioned already, a major source
`of interference for Bluetooth devices will clearly be other Bluetooth devices. Although
`devices sharing a piconet will be synchronised to avoid each other, other unsynchronised
`piconets in the area will randomly collide on the same frequency. If there is a collision on
`a particular channel, those packets will be lost and subsequently retransmitted, or if voice,
`ignored. So, the more piconets in an area, the more retransmissions will be needed, caus-
`ing data rates to fall. This is like having a conversation in a noisy room: the more people
`talking, the noisier it gets, and y