DECLARATION OF STACY TROUBH
`
`I.
`
`My name is Stacy Troubh.
`
`I am over the age of twenty-one years, of sound mind,
`
`and capable of making the statements set forth in this Declaration. I am competent to testify about
`
`the matters set forth herein. All the facts and statements contained herein are within my personal
`
`knowledge.
`
`2.
`
`I visited the University of California at Irvine’s Science Library (“Science Library”)
`
`located in Irvine, California 92617 on January 17, 2020 and scanned certain pages from Bluetooth
`
`Operation and Use by Robert Morrow ("Morrow”).
`
`3.
`
`The Science Library’s call number for Morrow is TK5103.3 .M67 2002. The
`
`Science Library had one copy of Morrow, which was indexed and shelved as indicated by the
`
`Science Library’s online catalog. a true and correct copy of which is attached as Appendix A.
`
`In
`
`the copy of Morrow, I scanned the cover, the table of contents, the “Date Due” slip, and pages 20-
`
`29. A true and correct copy of these pages from Morrow is attached as Appendix B.
`
`4.
`
`5.
`
`One date stamp on the “Date Due” slip of Morrow states “DEC 17 2004.”
`
`I visited the University of California at Los Angeles’ Science and Engineering
`
`Library (“SEL”) located at 8270 Boelter Hall, Los Angeles, California 90095 on January 19, 2020
`
`and scanned certain pages from IEEE Transactions on Consumer Electronics, Volume 41
`
`(“ITCE”).
`
`6.
`
`SEL’s call number for ITCE is TK6563 .159t v.41 1995. SEL had one copy of
`
`ITCE, which was indexed and shelved as indicated by SEL’s online catalog, a true and correct
`
`copy of which is attached as Appendix C.
`
`In the copy of ITCE, I scanned the cover, the table of
`
`contents, the “Date Due” slip, and the article entitled “Experimental Test and Evaluation of a
`
`GMSK Chipset Compatible With the GSM and PCS Standards” by Huajing Fu and Kamilo Feher,
`
`991577412
`
`- 1 -
`
`Qualcomm Incorporated
`Exhibit 1037
`Page 1 of 43
`
`
`
`Qualcomm Incorporated
`Exhibit 1037
`Page 1 of 43
`
`

`

`
`
`_.._.u—a—-
`
`which is found on pages 804-808. A true and correct copy of these pages from ITCE is attached
`
`as Appendix D.
`
`7.
`
`8.
`
`One date stamp on the “Date Due” slip of ITCE states “MAY 09 1996.” -
`
`I declare under penalty of perjury that the foregoing is true and correct.
`
`Executed on January 23, 2020 in Irvine, California, USA.
`
`By: Elm TM
`Stacy Troubhl
`
`9925774 7.2
`
`- 2 -
`
`
`
`Page 2 of 43
`
`Page 2 of 43
`
`

`

`
`
`
`
`
`APPENDIX A
`
`APPENDIX A
`
`Page 3 of 43
`
`Page 3 of 43
`
`

`

`
`
` ÿ
`  
`ÿÿÿ
` ÿ
`
`ÿ
`ÿÿÿ
`
`!ÿ
` ÿ"
` ÿ#$
`   
`%&ÿ'(!ÿ)*+ÿ ÿ,ÿÿ-ÿ./ÿ01
`23456768ÿ9ÿ0.::.
`23456;<ÿ=ÿ>
`?ÿ,ÿ0@AB
`C6;ÿ0@ABÿ 0
`1ÿ 
`D
`
`C34E7ÿ
`
` ÿ 0
`
`FG
`HI86J6ÿKL=,ÿ::+MNO++PQÿ" ?ÿ,ÿ?ÿ  $-ÿKL=,ÿ::+MNO).O.
`R8S3SÿTF
`C37ÿU1
`U( Gÿÿ
`0 
`,
`V( Gÿ
`DÿWD
`ÿK(,
`U(,L00ÿXGÿL00ÿXGÿÿY#)M:NNÿ*+ÿ.::.
`
`
`
`Page 4 of 43
`
`

`

`APPENDIX B
`
`APPENDIX B
`
`Page 5 of 43
`
`Page 5 of 43
`
`

`

`LANOSSEFORP
`
`0 Indoor propagation and useful range calculations
`
`0 Data throughput in real-world applications
`
`0 Security operation and countermeasures against
`
`eavesdropping and
`
`Jamming
`
`0 Coexistence with other wireless networks
`
`0H
`
`ints and tips for max
`
`Imlzmg pe
`
`rformance
`
`
`
`.lillllr..:i..lllx.«w.).l.irl4.nl§l
`
`
`
`all:.215.1...1:
`
`Page 6 of 43
`
`

`

`
`
`A.
`
`..~
`“ 4
`.1 .
`1‘
`‘ "
`VIA-g9a'aié'i'v'
`'
`_ «' V. ~
`
`‘t'l._ "
`0“
`oress‘nqm.
` _
`
`m
`
`‘\‘:‘~\‘~§
`
`~ m .4 ( -
`"3|"-
`
`v
`
`.-
`
`Page 7 of 43
`
`

`

`
`
`
`‘liliilllllii‘iilllill'ETO0TH
`
`
`
`
`31970.-.02417 267
`
`
`wBLU ETOOTH
`
`'
`Bringing low-cost. low-power wireless connectivity to data-driven
`If you re the one
`devices, Bluetooth is revolutionizing human/technology interac-
`
`tion. Revenue generated by Bluetooth devices was $2 billion in
`2001. Bluetooth revenue will skyrocket to $333 billion per year by
`
`2006, according to international marketing. consulting. and train—
`ing firm Frost 8t Sullivan.
`__
`11THE INSIDE TRACK
`FOR WIRELESS PROFESSIONALS
`Packed with priceless experience, Bluetooth Implementation and
`Use cuts the time it takes you to
`0 Implement “wireless cable" for phones, other handhelds.
`and Portables
`0 Build futuristic Bluetooth apps—for refrigerators that update
`PDA shopping lists, PDAs that survey local stores for the best
`prices. and as many others as you can dream up
`
`
`
`who puts the bite into
`
`Bluetooth, this meaty
`'
`guide is for you. In
`
`these pages, master
`
`Bl uetooth instructor
`
`Dr. RObert Morrow lays
`
`out precise guidance on
`
`0 Examine operational characteristics in detail
`
`t Solve security issues
`
`making Bluetooth work
`
`0 Get technical insights on Bluetooth's coexistence with other
`wireless devices
`
`in today's and next-
`
`generation applications.
`
`Cover design and illustration: Kevin McGuinness
`
`Visit McGraw-Hill TELECOM at
`www.accessMHtelecom.com
`
`'
`
`0 Find the facts you want on packet structure. paging. host
`interfacing, and designing and testing the Bluetooth module
`
`0 Probe the math behind the specifications for further research
`
`iirH‘E HANDS-0N GUIDE TO BLUETOOTH
`Anyone tackling a jOb involving Bluetooth needs this in-depth
`guide. It goes beyond introducing the technology and prepares
`you for hands—on involvement with uses today and applications
`to come.
`
`;
`
`.__
`
`' 7““ "
`
`j~—-~ . - ~ _
`.
`4-
`i
`
`w
`ISBN U—U?-lE&??fi-X
`
`5 5 9 9 5
`
`‘
`
`-
`
`
`
`
`
`9 7 8 0 0 7 1
`
`387798
`
`
`McGrau‘J-Hill
`A Division ol‘l‘lichGmw-HiHCompanics
`
`g2
`
`_
`
`i
`i
`
`J
`i
`
`l
`i.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 8 of 43
`
`

`

`DATE DUE
`
`01501 7”
`
`W”? 0 1...-“‘
`
`DEMCO 13829810
`
`Page 9 of 43
`
`Page 9 of 43
`
`

`

`I1IJ..IIJl.
`
`
`
`...!1.1I|.I-I..!...l:l.l.|..ll1.llln|.l1l.llll
`lillllliiiillqlllllllnllliii
`
`__ ___._.....-_—--_._.,__...__.__-_—I.-..-I—-.-—______
`
`Page 10 of 43
`
`
`

`

` Cataloging-in-Publication Data is on file with the Library of Congress
`
`McGraw-Hill
`A Division of'lthch-HiflCmnpmis
`
`%
`
`Copyright © 2002 by The McGraw-Hill Companies, Inc. All rights reserved.
`Printed in the United States of America. Except as permitted under the United
`States Copyright Act of 1976, no part of this publication may be reproduced or
`distributed in any form or by any means, or stored in a data base or retrieval
`system, without the prior written permission of the publisher.
`1234567890 DOC/DOC 08765432
`
`ISBN 0-07-138779-X
`
`The sponsoring editor for this book was Judy Bass and the production
`supervisor was PamelaA. Pelton. It was set in Century Schoolbook by MacAllister
`Publishing Services, LLC.
`
`Printed and bound by R R. Donnelley & Sons Company.
`
`McGraw-Hill books are available at special quantity discounts to use as premiums
`and sales promotions, or for use in corporate training programs. For more information
`please write to the Director of Special Sales, McGraw-Hill Professional, Two Penn
`Plaza, New York, NY 10121-2298. Or contact your local bookstore.
`
`Information contained in this work has been obtained by The McGraw-Hill
`Companies, Inc. (“McGraw-Hill") from sources believed to be reliable. However,
`neither McGraw-Hill nor its authors guarantee the accuracy or completeness of
`any information published herein and neither McGraw-Hill nor its authors shall
`be responsible for any errors, omissions, or damages arising out of use of this
`information. This work is published with the understanding that McGraw-Hill
`and its authors are supplying information but are not attempting to render engi-
`neering or other professional services. If such services are required, the assis-
`
`tance of an appropriate professional should be sought.
`
`" This book is printed on recycled, acid-free paper containing a minimum of
`t)
`50 percent recycled, de-inked fiber.
`
`
`
`61.51 1.91143
`
`
`
`Page 11 of 43
`
`

`

`
`
`Preface
`
`Acknowledgments
`
`.
`Chapter\I/I'ntroduction
`Differences Between Wired and \Mreless Communications
`Advantages of the \Mreless Network
`Advantages of the Wired Network
`Regulation of Unlicensed Bands
`FCC Part l5 Requirements
`Rules for Transmission in the 2,4 GHz Band
`FCC Product Certification
`The Bluetooth Story
`The Bluetooth Special Interest Group (SIG)
`Overview of Bluetooth Applications
`Threein-One Phone
`Ultimate Headset
`Internet Bridge
`Data Access Point
`Object Push and File Transfer
`Automatic Synchronization
`Other Uses for Bluetooth
`Bluetooth Protocols and Profiles
`The osr Model
`Bluetooth Protocols
`Bluetooth Profiles
`Summary of Bluetooth Operation
`Paging and Inquiry
`Specifications, Standards, and the IEEE
`Evolution of a Standard
`Health Effects from Exposure to 2.4 GHz RF
`Specific Absorption Rate (SARI
`The $5 Pricing Goal
`Summary
`End Notes
`
`Chapter-y Indoor Radio Propagation and Bluetooth Useful Range
`Indoor Propagation Mechanisms
`LargeScaIe Path Loss (PL)
`
`3
`3
`5
`6
`7
`7
`9
`IO
`l0
`12
`13
`I4
`is
`I6
`I6
`l7
`l7
`I9
`20
`22
`23
`25
`26
`27
`28
`29
`30
`32
`33
`34
`
`35
`36
`38
`
`‘
`i
`5
`
`,
`
`t
`j
`
`J
`l
`
`I
`%
`1
`,
`5
`
`I
`i
`'
`:
`i
`3
`3
`5
`I
`I
`1
`1
`.:
`'
`i
`
`.
`
`II I I 1
`
`l i
`
` CONTENTS
`
`
`
`g;
`E5“
`355';
`$5
`' 5;:
`1 Egg)
`5&3
`I 3’5"
`j
`ff,
`Zis‘
`.253
`{It} _‘
`if:
`g {5'
`;.§:>"
`;
`;
`‘
`,
`
`r}
`35.;
`
`"
`
`"I;
`~1 '.
`_
`; "
`i
`
`g
`-‘
`
`_- “
`.“
`
`‘_
`
`
`
`lI i
`
`Page 12 of 43
`
`

`

` ;
`
`Viii
`
`6‘
`
`Contents
`
`Co:
`
`'.
`
`V‘
`
`-
`.
`'5}
`
`1:
`
`"
`
`".3-
`
`j';
`.
`
`L'
`7._
`,-
`
`,
`'.
`
`Link Budget Equation
`Using Decibels irtthe Link Budget Equation
`Simplified Path Loss (PL) Calculations
`The Effect of Wavelength on Path Loss (PL)
`PL Exponent and Typical Values
`Calculating Bluetooth Range
`Accuracy of the Simplified Path Loss (PL) Model
`Improving Path Loss (PL) Prediction Accuracy
`Log Normal Shadowing
`Adding Pessimism to the Calculations
`Primary Ray Tracing for improved Accuracy
`Direct Modeling of Partition Losses
`Bluetooth Range Estimations Using Primary Ray Tracing
`The Ups and Downs of Multipath
`Reflection, Transmission, and Absorption
`Phasor Diagram for Multiple Signal Arrivals
`Multipath Effect on Received Signal Strength
`Multipath Characteristics
`Doppler Spread
`Delay Spread
`Doppler Spread Versus Delay Spread
`Bluetooth Channel Fading Analysis
`Large-Scale Path Loss (PL) Using Multiple Ray Tracing
`Multipath Mitigation
`Fade Margin
`Diversity
`Equalization
`Error Control
`Antennas for Bluetooth
`Power Transfer and impedance Matching
`Radiation Pattern and Antenna Placement
`Bluetooth Antenna Implementation
`Summary
`End Notes
`.
`//
`Chapter 3 \Jhe Bluetooth Radio
`
`‘
`
`.
`
`Placing information onto the RF Carrier
`Amplitude, Frequency-, and Phase-Shift Keying
`FSK Modulation index and Bandwidth
`’
`Reducing FSK Bandwidth with Gaussian Baseband Filtering
`Bluetooth Modulation Requirements
`
`39
`39
`40
`4]
`42
`45
`48
`49
`51
`53
`54
`55
`60
`60
`62
`63
`64
`66
`67
`72
`76
`76
`77
`78
`78
`79
`84
`85
`86
`86
`87
`89
`93
`94
`
`97
`
`99
`100‘
`104
`l06
`l09
`
`
`
`Page 13 of 43
`
`

`

`
`
`Contents
`
`Channel Capacity Limits
`Shannon Limits as a Function of Bandwidth and SNR
`Power-Limited Channels
`Band-Limited Channels
`
`
`
`J Capacity of the Bluetooth Channel
`v The Nature of Interference
`
`Frequency Hop Spread Spectrum (FHSS)
`Synchronization Between Communicating Devices
`
`. FHSS Cross Interference
`“Bluetooth Transmitter Performance
`Transmitter Power Classes
`
`Consequences of Higher Transmit Power
`Transmitter Spurious Emissions and Drift
`’J Bluetooth Receiver Performance
`
`Sensitivity
`Interference immunity
`Summary
`End Notes
`
`Chapter Vaseband Packets and Their Exchange
`Time Division Duplexing (TDD)
`Single-Slave Operation
`Multislave Operation
`Multislot Packets
`
`System Clock for Timing Control
`Physical Links
`
`Synchronous ConnectionOriented (SCO) Link
`Asynchronous Connectionless (ACL) Link
`Error Control Coding
`Error Detection
`Error Correction
`Bluetooth Addresses and Names
`
`Bluetooth Device Address (BD_ADDR)
`Active Member Address lAM_ADDRl
`Parked Member Address (PM_ADDR)
`Access Request Address (AR_ADDR)
`Bluetooth Device Name
`Bluetooth Baseband Packet Format
`Access Code
`Header
`
`Payload
`
`97
`
`99
`
`mo
`l04
`106
`109
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ill
`“2
`H4
`HS
`Ho
`”7
`H9
`120
`l22
`l22
`l24
`IZS
`127
`l28
`l28
`l34
`l35
`
`137
`
`MO
`l4]
`l42
`MB
`144
`Mb
`146
`147
`147
`I48
`l54
`l59
`159
`l60
`160
`16l
`lbl
`l6l
`l62
`l68
`l7O
`
`
`
`Page 14 of 43
`
`

`

`
`
`
`
`_...,.,...._.__..,..._”7”]r
`
` ,‘>;.05-h!
`
`Contents
`
`Con
`
`14
`
`lI
`
`i i l i i
`
`Packets on the Physical Links
`ACL for Data
`
`SCO for Real-Rime Two-Way Voice
`Packet TYPE Codes
`
`Packet Broadcasting
`Data Whitening
`Logical Channels
`Summary
`
`_
`
`End Notes
`
`-
`
`Chapter 5/Establishing Contact Through inquiry and Paging
`
`Biuetooth Piconet Activity and States
`State Diagram: Point-to-Point Link Activity
`State Diagram: General Piconet Establishment
`Hop Sequence Selection
`Paging Other Biuetooth Devices
`General Description of the Page Process
`Prospective Slave: Page Scan and Page Response States
`Prospective Master: Page and Page Response States
`Optional Paging Schemes
`Paging Timers
`Finding Other Bluetooth Devices
`General Description of the inquiry Process
`Prospective Slave: inquiry Scan and Response States
`Prospective Master: inquiry State
`inquiry Timers
`Summary
`
`Chapter 6 Advanced Pic'onet Operation
`
`Low-Power Modes
`
`Sniff
`Hold
`Park
`
`Link Supervision
`Device Entry into an Existing Piconet
`Master Brings in New Slave
`
`Slave initiates its Own Entry
`The Scatternet and its implications
`Scatternet Timing issues
`
`173
`
`173
`181
`183
`184
`185
`i86
`187
`188
`
`189
`
`192
`192
`194
`196
`199
`199
`203
`205
`207
`208
`209
`209
`211
`212
`214
`215
`
`217
`
`218
`219
`220
`221
`226
`227
`228
`228
`228
`229
`
`;
`
`3
`
`:
`
`
`..-._.”~11,A.
`1
`W...--..~.-..S.A
`
`“u...1.;-__.,,
`
`;
`
`_:
`g
`1
`
`1 i 1 i g
`
`li
`
`il
`
`i
`
`.
`
`
`
`Page 15 of 43
`
`

`

`
`
`
`tfij‘xrflmmhfi
`
`:nts
`
`Contents
`
` 1
`55.
`1;
`, ‘V
`
`
`
`
`
`..yes-«me~mam—“éwafim-fi:fixissmma-asm
`
`4%
`
`.i
`
`'
`
`.
`
`173‘
`173
`181
`183
`184
`185
`
`186
`187
`188
`
`189
`
`192
`192
`I94
`I96
`199
`199
`203
`205
`207
`208
`209
`209
`21 1
`212
`214
`2l5
`
`2 I 7
`
`2 I8
`219
`220
`22]
`226
`227
`228
`228
`228
`229
`
`
`
`.H~.,q—~wwa»...b.wu.a_”MMas.”
`
`Master-Slave (MS) Switch
`
`Alternatives to Scatternet Operation
`Summary
`
`Chapter 7
`
`Managing the Piconet
`
`Link Manager Protocol (LMP)
`General Link Session
`LMP Packet Structure
`
`General Response Messages
`Requesting Host Connection
`Completing the Setup
`Opodes and Their Functions
`Link Configuration and Information
`Piconet Management
`Security Management
`Connection Setup Procedure
`Summary
`
`Chapter 8
`
`Transferring Data and Audio Information
`
`Logical Link Control and Adaptation Protocol (LZCAP) for Data
`L2CAP Functions
`
`~
`
`[JCAP Operating Environment
`LZCAP Channel Concept
`LZCAP Packet Structure and Mapping
`Communicating with the LZCAP Layer
`LZCAP Signaling
`L2CAP for Streaming Audio Applications
`Real-Time Voice Communication
`
`Methods of Digitizing Voice
`Establishing and Disconnecting the SCO Channel
`Summary
`End Notes
`
`Chapter 9
`
`Bluetooth Security
`
`Overview of Bluetooth Security
`Security Levels
`Limitations of Bluetooth Security Architecture
`
`Summary of Bluetooth Security Operations
`Authentication
`
`234
`237
`238
`
`239
`
`24]
`243
`244
`246
`249
`250
`250
`25]
`254
`260
`260
`262
`
`263
`
`265
`266
`268
`269
`270
`274
`281
`287
`288
`289
`293
`294
`295
`
`297
`
`299
`299
`300
`301
`303
`
`9.-
`
`-‘7"..
`""‘y
`
`:u.A»;5.."4:2,:
`
`
`.,-List-0...};\g‘L..“—«:..
`
`
`
`
`
`Page 16 of 43
`
`

`

`Authorization
`
`Pairing, Bonding, and Trust
`Encryption
`
`Security Management
`Bluetooth Security Implementation Process
`Security Entities
`Key Generation Functions
`Pairing
`Link Key Exchange
`Authentication
`
`Encryption
`
`Bluetooth Piconet Vulnerability
`Disclosure Threat
`
`Integrity Threat
`Denial-oF-Service (DOS) Threat
`Summary
`End Notes
`
`Chapter 1 0 Host Interfacing
`
`.
`
`Host Controller Interface (HCI) Functionality
`Commands, Events, and Data over HCI
`HCI Flow Control
`HO Commands
`Link Control Commands
`
`Link Policy Commands
`HC and Baseband Commands
`Informational Parameters
`
`Status Parameters
`
`"
`
`Testing Commands
`HCI Events .
`Event Process: Command with Immediate Execution
`
`
`
`-
`
`‘
`
`303
`
`303
`305
`
`308
`309
`309
`3 l3
`3 l 5
`3 l 6
`3 I 9
`
`32I
`
`325
`326
`
`33l
`339
`344
`345
`
`347
`
`349
`350
`356
`357
`359
`
`362
`364
`370
`
`37l
`
`372
`372
`373
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Event Status and Errors
`
`
`HCI as a High-Level Language
`Device Name Request
`
`
`Establishing an ACL Connection
`
`Authenticating a Link
`
`HCI Transport Mechanisms
`
`USB Transport
`
`
`
`Event Process: Command with Delayed Execution
`
`Event Process: Triggered by an Incoming Baseband Packet
`
`.
`
`373
`
`374
`
`37S
`375
`375
`
`.
`{
`
`
`
`Page 17 of 43
`
`

`

`ants
`
`Contents
`
`303
`303
`305
`308
`309
`309
`3 I 3
`3 I 5
`3 I 6
`3 I 9
`32]
`325
`326
`331
`339
`344
`345
`
`347
`
`UART Transport
`RS-232 Transport
`Summary
`End Notes
`
`Chapter ‘I 1 Bluetooth Profiles
`
`Overview of Bluetooth Profiles
`
`Profile Descriptions
`A Paradigm Shift
`General Profiles
`
`Generic Access Profile (GAP)
`Service Discovery Application Profile (SDAP)
`Serial Port Profile (SPP)
`Profiles Based upon Serial Port Communication
`Dial-up Networking (DUN)
`LAN Access
`Fax
`
`
`
`A,_<‘_
`
`
`
`37ft».~mrv‘.V554'.t','
`l‘.‘I."f'17.I“an...“-'w_-.--_
`
`I."
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`{LS-Janene14:44:44.4.»ammo-mow")an'
`
`.4ft"4:37..“
`
`
`
`
`
`
`
`
`
`
`
`
`38 I
`c 383
`384
`384
`
`385
`
`387
`389
`390
`391
`392
`395
`397
`400
`400
`401
`
`403
`403
`404
`405
`406
`406
`407
`407
`408
`409
`410
`412
`4 l3
`413
`415
`4i6
`4 i 6
`416
`417
`420
`422
`423
`424
`424
`
`349
`350
`356
`357
`359
`362
`364
`370
`37I
`372
`372
`373
`373
`
`374
`375
`375
`375
`377
`378
`379
`380
`
`:t
`
`.2..-ms.-..._-A
`
`Headset (HS)
`Hands-Free (HF)
`Video Conferencing
`Profiles Based upon Object Exchange
`Object Push
`File Transfer
`
`Synchronization
`
`Basic Printing
`Basic imaging
`Telephony Profiles
`
`Cordless Telephony
`Intercom
`
`Audio/Video Profiles
`Advanced Audio Distribution
`Video Distribution
`Miscellaneous Profiles
`Audioneo Remote Control
`
`Human interface Device (HID)
`Hardcopy Cable Replacement
`
`Personal Area Networking (PAN)
`Common lSDN Access
`
`Summary
`End Notes
`
`__3..“W“ummuflaw«-mwu-M
`
`
`
`
`Page 18 of 43
`
`

`

`
`
`Contents
`
`Co
`
`Chaptefil'lrl/Module Fabrication, Integration, Testing,
`
`and Qualification
`
`Hardware Architecture
`
`The Bluetooth Chipset
`Device Fabrication
`
`Packaging Options
`Singlechip Versus Twochip Solution
`Designing for Class I Transmit Power
`Power Consumption
`Integrating Bluetooth into a Host
`Selecting a Module
`Integration Strategies
`Qualification and Testing
`SIG Qualification
`
`'
`
`,
`
`.
`
`,
`
`425
`
`427
`
`427
`43I
`
`436
`44I
`443
`445
`447
`447
`448
`452
`453
`
`RF Test Setup
`Testing the Transmitter
`Testing the Receiver
`Protocol Conformance Testing: The Protocol Analyzer
`Interoperability Testing: The UnPIugFest
`Summary
`End Notes
`
`
`
`ChapterWCoexisting with Other \Mreless Systems
`Other Users in the 2.4 GHz ISM Band
`IEEE 802. I
`I
`Other Bluetooth Piconets
`Microwave Ovens and Other ISM Devices
`HomeRF
`
`Cordless Telephones
`Custom Devices
`Licensed Users
`
`Microwave Lighting
`Bluetooth and Wi-Fi: Can They Live Together?
`
`M-Fi Characteristics
`Bluetooth Characteristics
`Collocated Nodes
`
`Characterizing Bluetooth Interference
`
`Interfering Transmitter Disruption Distance
`Types of Disruption
`Approaches to Coexistence Analysis
`
`‘
`
`
`
`
`460
`464
`465
`467
`468
`470
`472
`
`475
`477
`478
`479
`480
`480
`
`481
`48]
`482
`
`482
`482
`
`483
`484
`485
`
`485
`
`486
`488
`
`'1
`
`Page 19 of 43
`
`

`

`
`
`Coexisting with iEEE 802.i lb M/i-Fi)
`\M-Fi Signal Strutture
`W—Fi Effect on Bluetooth
`Bluetooth Efi‘ect on WI-Fi
`
`425
`
`427
`427
`431
`436
`441
`443
`445
`447
`447
`
`448
`452
`
`453
`460
`464
`465
`467
`468
`470
`472
`
`475
`
`477
`
`478479
`480480
`
`481
`48l
`482
`482
`
`j
`j
`
`Coexisting with Other Bluetooth Piconets
`
`Coexisting with Microwave Ovens
`Noncollaborative Coexistence Solutions
`
`Adaptive Frequency Hopping (AFH)
`Adaptive Packet Selection
`TX Power Control
`Antenna isolation
`
`Coexistence Solutions for Wi-Fi
`Collaborative Coexistence Solutions
`
`Manual Switching
`Driver-Level Switching
`Collaborative Adaptive Hopping
`MAC-Level Switching
`
`System-Level integration
`Bluetooth Operation Aboard Commercial Aircraft
`Summary
`End Notes
`
`Chapter 1 4] The Future of Bluetooth
`
`Gaining Customer Confidence
`Future Applications
`Operational Enhancements
`End Notes
`
`Acronyms
`
`References
`
`index
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 20 of 43
`
`

`

`Serialjuse,’ or PCMCIA‘Iriiertéce
`
`Serial; use, or PcMCIA Interface
`
`The OSI Model ‘
`
`Their Exchange.”
`
`Take a look again at the Bluetooth-to-host interface in Figure 1-9. A very
`complex process must occur just to get data from the host application to the
`radio in the module, across the wireless link, and to the destination host.
`How should the data be structured? How fast should the data be sent? And
`(gasp) how should the link be established and configured? After thinking
`about all of these factors together, it's tempting to give up in despair and
`return to a simpler life of designing vacuum tube oscillators.
`In 1977, the International Standards Organization (ISO) established a
`subcommittee to research the need to develop a standardized, layered
`approach to general computer communications. This work culminated in
`1982 with the Open Systems Interconnection (OSI) reference model, shown
`in Figure 1-10. By working through the layers of the model, a designer can
`gradually create an'entire computer communication system without becom-
`ing overwhelmed, and (theoretically, at least) a particular layer can be
`changed without affecting the other layers.3 The downside to using this
`method is that redundancy, along with its resulting inefficiencies, can creep
`into a design. We shall discover this characteristic when we examine the
`details of Bluetooth packet structure in Chapter 4, “Baseband Packets and
`
`Chapter 1
`
`-HostB
`
`Applications
`
`Bluetooth
`
`' ModuleB
`'BiuetSom
`hardwareand
`firmware
`
`‘
`
`‘
`
`HClflnnware
`
`Physical bus
`
`_
`
`_::
`2.
`
`5;
`
`HCI driver
`
`Physical bus
`
`V
`
`V
`
`Bluetooth
`sohware
`
`.
`,‘
`:
`;‘
`"
`,
`' 7'
`
`Bluetooth
`hardware Ind
`flnnware
`
`HCldrlvar
`
`.
`
`Physical bus
`
`3
`
`9
`
`_
`
`HClilrmware
`
`I
`
`Physical bus
`driver
`
`,
`C
`’
`
`.
`
`.
`
`,
`
`7f
`
`.3
`
`3
`.
`
`7
`
`3
`
`:
`'
`
`‘
`
`1'
`
`l i
`
`5
`
`l 3
`
`Figure 1-9
`An addon module is
`one method that
`Bluetooth can be
`connected to a
`
`computer.
`
`Page 21 of 43
`
`

`

`
`
`
`
`
`
`
`U
`.
`ppllcalion
`‘
`._
`"a .c L132; 2255, a 54 u.;.n;.'._:,;,,, Jib". P
`. ~.
`’ P
`
`
`
`Introduction
`
`gamma:
`
`Figure 1-10
`The OSI reference
`
`model provides a
`Standardized, layered
`approach to
`computer
`communications.
`
`V9]
`E
`R
`k
`
`g
`3
`
`I
`
`
`
`"15—3-2 my. :1». T;:.~.-‘;~.~.--,~;.:- ~.:,~'
`‘
`Datalink
`'
`3.,
`--
`-"-~-
`Jun
`we .z?"
`(logical link control)
`-;_
`5" """"
`"'
`Data link
`,
`
`d “’0“: ':—-~' ~ .;-.., ”if" I. :3:
`
`Physical (PHY)
`- “ 3'
`pkg; '.
`._
`.~ “'5 ..__.~.h.'\-_;_._.,.-‘..‘..
`
`
`
`|
`I
`I
`
`I
`l
`I
`I
`|
`
`I
`:
`
`
`
`
`
`
`T1- AW)” ’ ~”9.113.";-‘,\.»..v.‘i',’él R
`;
`,'
`,. L
`'
`j.
`'
`7.
`73 ¢
`‘
`Session
`.‘v’,'
`‘;f!.'.-11~";}’-~',2‘-1.5:;flat-‘43:"
`. E
`
`..;r.':.;«-'-..;A:_.:.‘;,..'-ri
`
`7f":tvz?=7~5"5j
`
`'
`
`The physical layer (PHY) contains the actual physical interface and the
`rules for its use. In Bluetooth, the PHY is RF and the modulation, and
`
`detection processes are listed in the specification. The PHY is made reliable,
`and link connection and detachment rules are provided by the data-link
`layer.This layer contains Media Access Control (MAC), which is a set of
`rules that determine the structure of basic data packets and how they are
`sent, and the Logical Link Control (LLC), which provides the protocol for
`link establishment and detachment. The network layer provides transpar-
`ent transfer of data between transport entities on each end of the commu-
`nication link. A properly implemented network layer relieves the transport
`layer from requiring any knowledge of the method by which data moves
`from source to destination. In other words, a Bluetooth device can appear to
`be a serial cable to the transport layer.
`Layers four and above in the OSI model are called higher layers (pro—
`found, yes?), and their functions start to become less well defined. The
`
`ished a
`
`layered
`rated in
`
`l, shown
`gner can
`t becom-
`' can be
`
`ling this
`an creep
`nine the
`sets and
`
`
`
`
`
`«rs—‘121:13::rt::s:wanntLA:uranmmmmmw
`
`l
`'ilt:
`:5.
`
` .
`
`transport layer includes optimization routines and other quality of service
`(QoS) methods for efficient data exchange, and the session layer contains
`the method for controlling dialog between applications on either end of the
`link. Finally, the presentation layer resolves differences between format and
`data representation between entities, and the application layer provides the
`means by which applications can access the OSI environment. As we move
`up the OSI layers, their implementation gradually changes from hardware,
`to firmware, and finally into software. The Bluetooth protocol stack exhibits
`the same behavior.
`
`Page 22 of 43
`
`

`

`
`
`In
`
`g
`Thl
`prc
`
`Chapter 1
`
`"
`
`Bluetooth Protocols
`
`Now that we’ve studied the OSI model, we can move on to the Bluetooth
`protocol stack shownm Figure 1-11. It’s at once apparent that the Blue-
`tooth protocol stack doesn’t conform to the OSI model exactly, but the lay-
`ers are still
`there and gradually transition from implementation in
`hardware and firmware (lower layers) to software (higher layers). If each of
`these groups of layers are separate entities, such as a PC card and laptop
`computer, then they can communicate with each other through the HCI.
`HCI provides paths for data, audio, and control signals between the Blue-
`tooth module and host.
`The radio completes the physical layer by providing a transmitter and
`receiver for two-way communication. Data packets are assembled and fed to
`the radio by the baseband state machine. The link controller provides more
`complex state operations, such as the standby, connect, and low-power
`modes. The baseband and link controller functions are combined into one
`layer in Figure 1-11 to be consistent with their treatment in the Bluetooth
`Specification 1.1. The link manager provides link control and configuration
`through a low-level language called the link manager protocol (LMP).
`The logical link control and adaptation protocol (LZCAP) establishes vir-
`tual channels between hosts that can keep track of several simultaneous ses-
`sions such as multiple file transfers. LZCAP also takes application data and
`breaks it into Bluetooth-size morsels for transmission, and reverses the
`process for received data. Radio frequency communication (RFCOMCM) is the
`Bluetooth serial port emulator, and its main purpose is to trick an applica-
`tion into thinking that a wired serial port exists instead of an RF link.
`Finally, the various software programs that are needed for the different Blue-
`tooth usage models enable a familiar application to use Bluetooth. These
`include service discovery protocol (SDP), object exchange (OBEX), telephony
`control protocol specification (T08), and Wireless Application Protocol (WAP).
`Aside from data communications, Bluetooth has a special provision for
`real-time, two—way, digitized voice as well; Once these voice packets are cre-
`ated by an application, they bypass most of the data protocol stack and are
`handled directly by the baseband layer. This prevents unacceptable delay
`between the time the packets are created and the time they arrive at their
`destination. Control of the Bluetooth module usually proceeds fiom the
`application through HCI to the module, also bypassing the protocol layers
`used for handling the data communication processitself.
`The Bluetooth radio and the baseband/link controller consist of hard-
`ware that is typically available as one or two integrated circuits. The
`firmware-based link manager and one end of the host controller interface,
`
`l
`
`£
`
`;
`:
`.-
`
`3
`
`;
`
`.
`1
`
`;
`’;1
`
`if
`I.
`
`.
`
`l’
`
`
`
`Page 23 of 43
`
`

`

`
`
`www.mgui.I_,.'
`
`
`“7.":“Z"TH?"TWA[
`
`Introduction
`
`E2: :2: ma :2:
`
`Figure 1-! ‘l
`The Bluetooth
`
`protocol stack
`
`"1‘5 ‘:
`
`_-
`~-
`»
`J
`-
`, w_ . l.
`.\.
`,
`-.. ..- n.1,..." ..«.
`'
`
`"H
`
`I
`
`I
`
`AI'll
`nun-"nun...“
`{ nun—urn;
`
`.,.~
`
`$3.; Us.” 7. v.49,
`
`BL?
`
`'3
`
`~r."~.-.
`
`l...r,-
`
`f
`I
`'
`Host controlled‘interface
`.,.- .H.
`,, 3.3.1.; :..~.._r.v.; 7: ”‘55
`
`/
`
`perhaps with a bus driver for connection to the host, complete the Bluetooth
`module shown in Figure 1-9. The remaining parts of the protocol stack and
`the host end of H01 can be implemented in software on the host itself.
`
`Bluetooth Profiles
`
`Lots of options are reduced to those needed for a specific function.
`
`a Procedures for a specific function can be taken from a set of base
`standards.
`
`a A common user experience is provided across devices from different
`manufacturers.
`
`”a,.r_-._.....V._v:......~._.M~
`
`Whereas protocols provide the basic building blocks for Bluetooth opera—
`tion, the profile is what gives a Bluetooth-equipped device its personality.
`Do you want the device to be a headset? Use the headset profile. A cordless
`phone? Use the cordless telephony profile. The purpose of profiles is three-
`fold:
`
`n..(
`
`Jug.
`
`
`
`-.s
`
`.-....u.:An..
`.‘Mnh-Ju."r'-.Jl'
`
`“H“E'V.'3<
`
`s,.I‘T,
`are;
`MW_m“w“...‘
`
`Page 24 of 43
`
`

`

`
`‘___4.—A——————.¢___.._.~.~_.-...-LL_‘4——LA‘.._._A_H_——.-__J‘__‘_v_.__<n.V...“—.—
`0.“er
`
`Chapter 1
`
`‘:—-—.~....~v—u.’
`
`Several profiles existed in the first release ofthe Bluetooth specification,
`and these original profiles and their interaction with each other are shown
`in Figure 1-12. For example, if a Bluetooth-equipped device is to have the
`ability to perform automatic file synchronization, then the Generic Access
`profile, Serial Port profile, Generic Object Exchange profile, and Synchro-
`nization profile will all play a role in the device’s capabilities. Profiles can be
`envisioned as a ‘fi/ertical slice” through the Bluetooth protocol stack, in
`which a subset of capabilities in each layer is selected for the particular
`Bluetooth function being developed. Automatic file synchronization, for
`example, doesn’t require the use of two-way real-time audio, so implement-
`ing audio isn’t necessary for that application. Each usage model has its own
`corresponding set of profiles. Other profiles continue to be added as they
`attain SIG approval. We will take a more detailed look at profiles and how
`they are constructed in Chapter 11.
`
`TCS-BlN—based profiles
`
`Intercom
`Cordless Telephony
`profile
`profile
`I
`-——--—--———- ------ ---———--—--’
`
`
`
`
`
`Generic Access profile
`
`Service Discovery
`Application profile
`
`’—-__—-
`
`'? Serial Portproflle
`
`Dial-up Networking
`profile
`,
`
`'
`
`.
`
`.
`
`_
`
`-
`:
`.
`
`,.
`
`.
`
`.
`
`,
`
`.
`..
`-=:-._:_~I
`File Transfer
`profile
`
`'
`'
`
`Object Push
`profile
`
`Synchronlzation
`profile
`
`_
`
`.
`.
`
`,
`~ ,
`
`an m
`
`Figure l -12
`Examples of
`Bluetooth profile
`interaction
`
`
`
`I
`
`n“Ah.--
`
`WWW__..
`
`
`
`"I'l',-*'\.:v,r
`
`‘{7‘1-
`
`Page 25 of 43
`
`

`

`
`
`Introduction
`
`arl
`
`tion,
`LOWD
`
`a the
`:cess
`
`shro-
`m be
`
`cular
`
`i, for
`nent-
`s own
`
`, they
`lhow
`
`'.x.meMWLHmm
`
`Summary of Bluetooth Operation
`
`Imagine, if you will, a digital communication link between (say) two laptop
`computers. Let’s call one A and the other B. If data is to be sent only in a
`one-way direction fromA to B, then we can equipA with a transmitter and
`B with a compatible receiver, and the PHY is done. Next, we can program
`microcontrollers inA and B to accept a particular data structure, and the
`MAC is done, and so on up the OSI chain. However, once we remember that
`the BER using wireless is somewhat high, we may decide that B should
`transmit an acknowledgment to A whenever a packet of data is received
`correctly. That gives A a chance to repeat a transmission that B had
`received in error. Clearly, A and B now require both a transmitter and a
`receiver. When should B send its acknowledgment? Ifboth A and B use the
`same frequency for their respective transmissions, then A’s transmitter
`must be ofi‘ and its receiver on when B transmits its acknowledgment. This
`requires timing coordination between A and B, but where does this coordi-
`nation come from? It probably makes sense to give one of the computers
`some kind of control over the network to prevent chaos due to problems
`with timing.
`c
`Bluetooth controls timing on the network by designating one of the
`devices a master and the other a slave. The master is simply the unit that
`initiates the communication link, and the other participants are slaves.
`When that link is later broken, the master/slave designations no longer
`apply. In fact, every Bluetooth device has both master and slave hardware.
`The network itself is. termed a piconet, meaning small network. When
`there is only one slave, then the link is called point-to-point. A master can
`control up to seven active slaves in a point-to-multipoint configuration.
`Slaves communicate only with the master, never with each other directly.
`Timing is such that members of the piconet cannot transmit simultane-
`ously, so these devices won’t jam each other. Finally, communication across
`piconets can be realized if a Bluetooth device can be a slave in more than
`one piconet, or a master in one and a slave in another. Piconets configured
`in this manner are called scatternets. These various arrangements are
`depicted in Figure 1-13.
`The existence of more than one piconet in the same room leads to
`another significant problem: Can two piconets interfere with each other?
`
`Surely they would if everyone operates on the same frequency. Bluetooth
`
`
`
`Page 26 of 43
`
`

`

`
`
`":a1
`
`”1..
`
`In
`
`Chapterl
`
`:
`
`-
`
`l "
`
`a 1
`
`,
`.
`26 -.
`
`
`
`:22: :2: m (2::
`
`Figure 1-13
`
`Point-to—point, point—
`