BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 991 of 1082
`
`Appendix V - Bluetooth Audio
`
`Bluetooth.
`
`to the loudness rating, in ITU R79 and at PGA value of 0 dB. Programmable
`Gain Amplifiers (PGAS) are used to control the audio level at the terminals by
`the user. For conversion between various PCM representations: A-law. u-law
`and linear PCM, ITU-T G.711, G.712, G.?14 give guidelines and PCM value
`relationships. Zero-code suppression based on ITU-T G.711 is also recom-
`mended to avoid network mismatches.
`
`General Audio Recommendations
`
`29 November 1999
`
`AFFLT029421 9
`
`Samsung Ex. 1019 p. 991
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 992 of 1082
`
`Appendix V - Bluetooth Audio
`
`1.7 FREQUENCY MASK
`
`Bluetooth-
`
`For interfacing a Bluetooth terminal to a digital cellular mobile terminal. a com-
`pliance of the CVSD deooder signal to the frequency mask given in the celluiar
`standard, is recommended to guarantee correct function of the speech coders.
`A recommendation for a frequency mask is given in ‘iabie ‘ifs. figure ‘L3:
`shows a plot of the frequency mask for Bluetooth (solid line). The GSM fre-
`quency mask (dotted line) is shown in 5'-‘igure 1.3: for comparison.
`
`i0.1
`
`0.5
`
`0.2
`
`0.3
`
`|
`1.0
`
`i
`2.0
`
`I
`i
`3.0 3.4
`
`I
`4.0
`
`"
`fkHz
`
`Figure 1.3.’ Plot of recommended frequency mask for Biuetootn. The GSM send frequency
`mask is given for comparison (dotted line)
`
`Frequency
`{Hz}
`
`Upper Limit
`(dB)
`
`Lower Limit
`{dB}
`
`Table 1.1: Recommended Frequency Mask for Biuetooth
`
`29 November 1999
`
`General Audio Recommendations
`
`AFFLT0294220
`
`Samsung Ex. 1019 p. 992
`
`

`
` BASEBAND TIMERS
`
`._
`This: ppengx contains a list of all timers
`defin_d the éaseband Specification.
`
`AFFLT0294221
`
`Samsung Ex. 1019 p. 993
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 994 of 1082
`
`Appendix VI - Base-band Timers
`
`29 November 1999
`
`AFFLT0294222
`
`Samsung Ex. 1019 p. 994
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 995 of 1082
`
`Appendix V.‘ - Baseband Timers
`
`CONTENTS
`
`Basehand “fimers
`
`1.3%
`
`LESS‘? C35‘:
`
`'¥"iEi.»’EE3F§'C“:T= ...................................................................
`
`132.“!
`
`§r1r.:ui§"y"i'{3 ...................................................................
`
`;‘:age‘E‘€."3
`
`............................................. .. . ...................... .
`
`§,3ageres.:_;.fE"O ................................................................
`
`énq="z~3SrJT() ..................................................................
`.r~=eu~«conne£:tic:n'?'{) .....................................................
`
`sL:pervi3i«Jn"£'O ........................................................... ..9‘3‘?
`
`29 November 1999
`
`AFFLT0294223
`
`Samsung Ex. 1019 p. 995
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Appendix Vi - Baseband Timers
`
`1 BASEBAND TIMERS
`
`page 996 of 1082
`
`Bluetooth-
`
`This appendix contains a list of all timers defined in this specification. Defini-
`tions and default values of the timers are listed below.
`
`All timer values are given in slots.
`
`1.1 LIST OF TIMERS
`
`1.1.1 inquiryTO
`
`The inquiryTO defines the number of slots the inquiry substate will last. Its
`value is determined by an HCI command.
`
`1.1.2 pageTO
`
`The page-TO defines the number of slots the page substate can last before a
`response is received. Its value is determined by an HCI command.
`
`1.1.3 pagerespT0
`
`In the slave, it defines the number of slots the slave awaits the master's
`response, FHS packet, after sending the page acknowledgment ID packet. In
`the master, pagerespTO defines the number of slots the master should wait for
`the FHS packet acknowledgment before returning to page substate. Both mas-
`ter and slave units should use the same value for this timeout, to ensure com-
`mon pagefscan intervals after reaching pagerespTO.
`
`The pagerespTO default value is 8 slots.
`
`1.1.4 inqrespT0
`
`In the inquiry scan substate, when a device triggers on an inquiry, it waits a
`RAND random number of slots and returns to inquiry scan. The inqRespTO
`defines the number of slots the device will stay in the inquiry scan substate
`without triggering on an inquiry after the RAND wait period. The timeout value
`should preferably be in multiples of an inquiry train period. Upon reaching the
`inqrespTO, the device returns to CONNECTION or STANDBY state.
`
`The inqrespTO default value is 128 slots.
`
`1.1.5 newconnectionT0
`
`Every time a new connection is started through paging, scanning, master-slave
`Switch or unparking, the master sends a POLL packet as the first packet in the
`new connection. Transmission and acknowledgment of this POLL packet is
`used to confirm the new connection. If the POLL packet is not received by the
`
`996
`
`29 November 1999
`
`Baseband ‘Timers
`
`AFFLT0294224
`
`Samsung Ex. 1019 p. 996
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 997 of 1082
`
`Appendix V.‘ - Baseband Timers
`
`Bluetooth
`
`slave or the response packet is not received by the master for newconnectil
`on T0 number of slots, both the master and the slave will return to the previous
`substate.
`
`newconnectionTO default value is 32 slots.
`
`1.1.6 supervisionT0
`
`The supervisionTO is used by both the master and slave to monitor link loss. If
`a device does not receive any packets that pass the HEC check and have the
`proper AM_ADDR for a period of supervisi'onTO, it will reset the link supervisi-
`onTO will work through hold and sniff periods.
`
`The supervisionTO value is determined by an HCI command. At the baseband
`level a default value that is equivalent to 20 seconds will be used.
`
`Baseband 1'|mers
`
`29 November 1999
`
`AFFLT0294225
`
`Samsung Ex. 1019 p. 997
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 998 of 1082
`
`Appendix VI - Base-band Timers
`
`29 November 1999
`
`Baseband '|'|mers
`
`AFFLT0294226
`
`Samsung Ex. 1019 p. 998
`
`

`
`AFFLT0294227
`
`Samsung Ex. 1019 p. 999
`
`

`
`
`
`
`
`AFFLT0294228
`
`Samsung Ex. 1019 p. 1000
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1001 of 1082
`
`Appendix VH - Optional Paging Schemes
`
`CONTENTS
`
`Bluetooth.
`
`ifiptianai Paging Sam-.:~me
`
`.12.?
`
`Page ..................................................................................... .1854
`
`Page Scan .......
`
`......................
`
`......................................... ..‘iO-’J:’_*.
`
`2.3
`2;;
`
`Page .§‘%e:s;:)onse ?3rccedus‘es1O£3{-‘.~
`Train Tracie" ......................................................................... ..
`
`29 November 1999
`
`AFFLT0294229
`
`Samsung Ex. 1019 p. 1001
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1002 of 1082
`
`Appendix VH - Optional Paging Schemes
`
`29 November 1999
`
`AFFLT0294230
`
`Samsung Ex. 1019 p. 1002
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1003 of 1082
`
`Appendix Vii - Optional Paging Schemes
`
`1 GENERAL
`
`For the access procedure, several paging schemes may be used. There is one
`mandatory paging scheme which has to be supported by all Bluetooth devices.
`This scheme has been described in Baseicand Spacifécatir:-n Si-3=‘;?_i0i".= 30$ on
`page 9%} In addition to the mandatory scheme, a Biuetooth unit may support
`one or more optional paging schemes. The method used for page scan is indi-
`cated in the FHS payload, see Basebami SSpecifi<.:atéos‘e Siectien xix-1.‘? .-it on page
`58. Three additional optional paging schemes are possible; only optional pag-
`ing scheme I has been defined yet.
`
`29 November 1999
`
`AFFLT0294231
`
`Samsung Ex. 1019 p. 1003
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Appendix Vii - Optionai Paging Schemes
`
`2 OPTIONAL PAGING SCHEME I
`
`page 1004 of 1082
`
`Bluetooth-
`
`In this section the first optional paging scheme is described which may be used
`according to the rules specified in Easebai-id Specification Section 10 on page
`95 and
`S;3ecificati<3n Sec-tier: 3.23 on page 223. The paging code for
`
`optional scheme I is 1 (0 is used for the mandatory scheme), see also Base-
`band Spet;%i"s<:atéo:': fsecttcc 4.4.1.4 on page :56
`
`The main difference between the first optional paging scheme and the manda-
`tory scheme is the construction of the page train sent by the pager. In addition
`to transmission in the even master slots, the master is transmitting in the odd
`master slots as well. This allows the slave unit to reduce the scan window.
`
`2.1 PAGE
`
`The same 32 frequencies that are used for transmitting ID-packets in the man-
`
`datory paging scheme are used in the optional paging scheme I (for the con-
`struction of page trains, see Basepand Spscificaieori Section ‘it .32 on page
`The 32 frequencies are also split into an A-train and B train. in contrast
`to the mandatory scheme, the same 32 frequencies that are used for transmit-
`ting are also used for reception trials, to catch the response from the
`addressed device.
`
`The construction of the page train in optional page scheme I differs from the
`page train in the mandatory scheme in two ways:
`
`-
`
`-
`
`the page train consists of 10 slots. or 6.25 ms
`
`the first 8 slots of the train are used to transmit the ID packets, the 9th slot is
`used to send a marker packet, and the 10th slot is used for the return of a
`slave response
`
`The marker packets precede the return slot, indicating the position where the
`slave can respond, and with which frequency. For the marker codes M_|D, bit-
`inverted page access codes are used. If a marker code is received at Tm with
`
`frequency fk, a return is expected at nominally Tm+525pS at frequency fk.
`
`Note: The bit-inverted code M_lD to be used as marker code is beneficial for
`the implementation of the correlators, because the sign of the correlation peak
`can be used to identify the mark code during page scanning. Still, the transmit-
`ting party is uniquely identified, since inverted ID packets are not identical to
`the ID packets for the device with bit-wise inverted LAP.
`
`The frequency ordering in the train and the frequencies used for the marker and
`receive slots change after every train. After 8 trains, all of which have a different
`appearance, the entire procedure is repeated. It is, therefore, more appropriate
`to talk about subtrains, each with length 6.25ms. Eight subtrains form a super-
`train, which is repeated. An example of a supertrain with the eight subtrains is
`
`20 November 1999
`
`Optional Paging Scheme I
`
`AFFLT0294232
`
`Samsung Ex. 1019 p. 1004
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1005 of 1082
`
`Appendix Vii - Optional Paging Schemes
`
`illustrated in F'ig=.sr'e 23%. The supertrain length is 50ms. In this example, the A-
`train is assumed with an estimated frequency of f3; as a consequence, the fre-
`
`quencies selected for the train range from to to f15. The marker codes M_lD are
`
`indicated as M; the receive (half) slots are indicated as R.
`
`6.25 ms
` &
`
`wmmulllllalaanlaalaiikfl
`wmmaalaalaamlaauanllaflh
`wmmaEaInnalaamIuIlnla::
`wmmfllllflllfllflfllllllllav
`wmmflflflllllflflllflllfllflfl I
`wmmalaalaulanlnalnamlafi
`wmmlElaalanlanIHamIal::
`
`sumraina I I I I I I I I I I I I I I I I I I
`
`,
`
`I E
`
`Figure 2.1: Exampie of train configuration for optional‘ page scheme i.
`
`Corresponding to the paging modes R0, R1 and R2 of the mandatory scheme,
`the optional scheme supports the same three modes as described for the man-
`datory scheme in ifiasetsand Specification Section 10.6.2 on page 99
`
`Since the subtrain length is now 10 slots, the 1.28s interval does not cover a
`multiple of (sub)trains any longer. Therefore, in contrast to the mandatory
`scheme, the exchange from A-train to B-train and vice versa is not based on
`the 1.28s interval, but instead on a multiple number of supertrains. For the R1
`and R2 modes, the repetition of a supertrain Nsup is indicated in "Estate 2.1
`below.
`
`1%
`R1
`N5up=7?
`
`Table 2.1: Reiation between repetition duration ofA- and B-trains and paging modes R1 and
`R2 when SCO iinks are present
`
`N3up=154
`
`Optional Paging Scheme I
`
`29 November 1999
`
`AFFLT0294233
`
`Samsung Ex. 1019 p. 1005
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1006 of 1082
`
`Appendix Vii‘ - Optional Paging Schemes
`
`Bluetooth-
`
`In accordance with the phase input to the hop selection scheme Xp in (E{.} 4) on
`page 135 in the Baseband Specification (Siectien 'l1..’5.2), the phase input Xp_opt
`in the optional mode is determined by:
`
`X;J_rJ;J;=[kQmU, up‘, + ST((:m]] mod 32
`
`(EQ Al )
`
`where kofigemp, is determined by the NB selection and the clock estimation of
`the recipient:
`
`kaJ(ly_;‘.£,: op!
`I
`H
`
`=
`
`+
`CLK_E]{,_11 + 8
`
`AA-‘tl'E.irI
`B-train
`
`{B0 A3)
`
`and ST is a function determining the structure of the sub- and supertrain:
`
`S'['(t.'nr) = ( cur mod [60 - 2*INT[ ((r.'m mod 160) 4' l8)i’20 ] } mod 16
`
`(1:20 A3)
`
`kofi5eLop,is determined once at the beginning of the repetition period.
`The CLKE value as is found at the beginning of the repetition interval is taken
`(the repetition interval being the interval in which the same supertrain is
`repeated all the time). As long as no train change takes place, kofisewp, is not
`updated. cm‘ is a counter which is reset to zero at the beginning of the repeti-
`tion interval and is incremented at the half-slot rate (3200 cyclesis)
`
`The first two ID-packets of a train are transmitted in an even numbered slot.
`
`2.2 PAGE SCAN
`
`The basic page scanning is identical to the mandatory scheme except that a
`scan duration of 9.5 - 0.625 = 5.9375 ms is sufficient at the slave side.
`
`If a device wants to scan concurrently for the mandatory and optional mode
`(e.g. after an inquiry response was sent), the device shall try to identify whether
`the paging party uses the optional scheme after an ID packet was caught. This
`can be done by train tracing; i.e. the device can determine whether transmis-
`
`sion takes place in consecutive slots (optional paging scheme 1) or in every
`over slot (mandatory paging scheme), andior whether mark codes are sent.
`
`2.3 PAGE RESPONSE PROCEDURES
`
`The page response procedures at the master and slave sides are almost iden-
`tical to the procedures described in the mandatory mode (see iieseband £3;':e::—
`ification Eiection
`on page 10-4). There are two difierences:
`
`- The page response routine starts after the transmission and reception of the
`marker code lv1_|D
`
`- The ID packet sent by recipient is identical to the frequency in which the
`marker code was received
`
`For the page response timing, see Figure
`
`and Figure
`
`29 November 1999
`
`Optional Paging Scheme I
`
`AFFLT0294234
`
`Samsung Ex. 1019 p. 1006
`
`

`
`AFFLT0294235
`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1007 of 1082
`
`Appendix Vii - Optionai Paging Schemes
`
`Master slot
`M
`
`2p
`M
`
`: fik}
`
`f(k+1) :
`
`MASTER
`
`«in
`
`raw)
`
`[TRAFFIC
`
`f'(m)
`
`H7
`
`:REsPoNsEj
`I
`I
`
`:RESPONSE,
`I
`
`E TRAFFIC
`I
`
`page hopping sequence
`
`I
`
`channel hopping sequence
`
`Ma ster slot
`M
`
`2p
`M
`
`:f(k)
`
`f(k+1}:
`
`MASTER
`
`IIIIII
`
`'f'(m)
`
`II
`
`I TRAFFIC .
`|'
`I
`
`.
`
`f{k+1)
`
`I
`
`.RESPONSE,
`I
`I
`
`I
`
`,RESPONSE,
`I
`
`page hopping sequence
`
`channel hopping sequence
`
`Figure 2.3: Messaging when marker code is received in second haif sic! of even master slot
`
`2.4 TRAIN TRACING
`
`This section outlines how a slave may search for the mark code although the
`current partitioning into A- and B-trains at the master side is not known. Train
`tracing means that the slave tries to receive as many page access codes from
`the train as possible. to catch a mark code as soon as possible. When search-
`ing for the mark codes, or trying to distinguish between the mandatory paging
`mode and the optional paging mode, a unit shall set up a hopping pattern for
`train tracing after the reception of the first access code. The hopping pattern
`
`Optional Paging Scheme I
`
`29 November 1999
`
`100?
`
`Samsung Ex. 1019 p. 1007
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1008 of 1082
`
`Appendix Vii - Optional Paging Schemes
`
`shall ensure that the transmission and reception is performed with a 50%
`probabiiity on the same frequency regardless of the actual frequency set
`(16 frequencies) used for paging.
`
`29 November 1999
`
`Optional Paging Scheme I
`
`AFFLT0294236
`
`Samsung Ex. 1019 p. 1008
`
`

`
`AFFLT0294237
`
`Aggendix VIII
`
`
`
`Is, OOTH ASSIGNED NUMBERS
`
`2E
`
`§' This Is a Iivi g document that lists assigned
`$5 numfiers, c
`as and identifiers in the
`fig Bluqiooths ndard.
`s'
`sh?
`‘E
`3
`g"
`E
`
`Samsung Ex. 1019 p. 1009
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1010 of1082
`
`Biuetooth Assigned Numbers
`
`29 November 1999
`
`AFFLT029423B
`
`Samsung Ex. 1019 p. 1010
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Bluetooth Assigned Numbers
`
`CONTENTS
`
`page 1011 of 1082
`
`Bluetouth.
`
`Eiuetacth Basehand .................................................................... "1312
`1.’!
`
`The Generah and Device--Specific Enquiry Accass
`Codes (WAGS) ..................................................................... .1012
`The Ciass 01' Devic;e:‘Serv§ce fieici ........................................ .1012
`
`1,2
`
`1.2.1
`
`fviajar Service Ciasse.-3 ............................................. ..1fJ13
`
`Major Device
`1.2.3 The winor Devéce Ciass:
`
`1.2.4 Miner Device Ciass fieid -- Computer Magor {2£as3.....1015i
`
`1.2.53 Minor" Device Ciass fieic‘ ~ Phone Maj<.2r Ciasss ..........1015
`1
`Minor Device Ciass fieid - LAN Access Pain:
`
`Major Ciass ............................................................. ..1fl‘?ES
`
`1.2.?’ Minor Dexrice C1333 fieiei - Atsriio Maia: {$1355 ...........1{}'‘;“{
`
`Link Manager Pmtacei {L399} ...................................................... ..‘i£3’i3
`
`2.11‘ f
`.54.‘
`
`The Linéi E\r‘%z«mger Version parameter .................................... .1018
`The LMP_Com_r;:id parameter codes .................................... .1018
`
`Logical Link Centres am: Adaptafiiars Praises? {LECAP} ........... 1:919
`3.1
`Clhannei Edarztifiezs ............................................................... ..1t'}'2£vI'
`
`3.2
`
`Frotccoi and Service ;’\-'?Ui‘ii§3iE!)€£3!‘ {PSM} ....
`
`....................... "1019
`
`Service fliscuvefy Prcetcscsrfi {SE9} .............................................. "1929
`4.1
`i}niver'saEiy Ur*.iq=.ae identifier {LiUiE3} $?i{3¥‘{ forms ................. ..1G:?i9
`
`4.2
`
`4.3
`
`4.4
`
`4.5
`
`4.5
`
`4.?
`
`Base Ur:%v'e:‘.=.=a§iy Unique §der11:ifie.r {_L5UiD} ........................... ..‘E.f}2{‘z
`Pretecota .............................................................................. .. ‘£021
`
`Service <:¥a.<3s3es
`
`Attribute Edentifier codes
`
`Protoc-oi
`
`.
`
`.
`
`...1G.’E:4
`
`Hc1stO;:eratEng Einvirc-rament identifiers ............................... ..102c‘i
`43.‘!
`Clientfixaczjtahieufii- sL:b3$.i§isEion strings
`
`iconijfii. stiiastittstiarz strings .................................... .,*EOE.’.?
`
`References .................................................................................... .1? 928
`
`Terms and Ahhreviatiens ............................................................ "1929
`
`List <2? Figures ............................................................................... "1339
`
`List as? 'i“a3::§es .........................................
`
`.................................... J93?
`
`29 November 1999
`
`AFFLTD294239
`
`Samsung Ex. 1019 p. 1011
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Biuetooth Assigned Numbers
`
`1 BLUETOOTH BASEBAND
`
`page 1012of1082
`
`Bluetooth-
`
`1.1 THE GENERAL- AND DEVICE-SPECIFIC INQUIRY
`
`ACCESS cones (males)
`
`The Inquiry Access Code is the first level of filtering when finding Bluetooth
`devices and services. The main purpose of defining multiple |ACs is to limit the
`number of responses that are received when scanning devices within range.
`
`LAP value
`
`lJx9E8B33
`
`UXQESBUU
`
`Usage
`
`Generallunlimited Inquiry Access Code (GIAC)
`
`Limited Dedicated Inquiry Access Code (LlAC}
`
`OXQESBO1-0x9E8B32, RESERVED FOR FUTURE USE
`Ox9E8B34-Dx9E8B3F
`
`Table 1.1: The inquiry Access Codes
`
`The Limited Inquiry Access Code (LIAC) is only intended to be used for limited
`time periods in scenarios where both sides have been explicitly caused to enter
`this state, usually by user action. For further explanation of the use ofthe LIAC,
`please refer to the Generic Access Profile £17}.
`
`In contrast it is allowed to be continuously scanning for the General Inquiry
`Access Code (GIACJ and respond whenever inquired.
`
`1.2 THE CLASS OF DEVICEISERVICE FIELD
`
`The Class of DeviceiService (C0D) field has a variable format. The format is
`indicated using the ‘Format Type field’ within the CoD. The length of the Format
`Type field is variable and ends with two bits different from '11 '. The version field
`starts at the least significant bit of the CoD and may extend upwards.
`
`. 24 bits
`
`.i
`
`a"ri'ri---
`
`Formal type field
`
`Figure 1. ‘I: General format of Class offlevice/Service
`
`In the ‘format#1' of the CoD (Format Type field = 00), 11 bits are assigned as a
`bit-mask (multiple bits can be set) each bit corresponding to a high level
`generic category of service class. Currently 7 categories are defined. These
`
`1012
`
`29 November 1999
`
`Bluetooth Baseband
`
`AFFLT0294240
`
`Samsung Ex. 1019 p. 1012
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1013 of 1082
`
`Biueioorh Assigned Numbers
`
`are primarily ofa ‘public service‘ nature. The remaining 11 bits are used to indi-
`cate device type category and other device~specific characteristics.
`
`Any reserved but otherwise unassigned bits, such as in the Major Service
`Class field, should be set to O.
`
`23
`
`16
`
`15
`
`8 7
`
`'
`
`octet 3
`11 bits
`
`octet 2
`-
`5 bits
`.
`.
`.
`I Reserved for Service Classes
`Major device class
`1 Networking
`
`octet 1
`6 bits
`.
`
`I
`
`-'
`
`.
`
`0 bittransmission order
`
`octet transmission order
`
`when interpreted as a
`We endian word
`— Format type
`
`-— Rendering
`— Capturing
`Object Transfer
`- Audio
`
`-- Telephony
`-— Information
`
`Figure 1.2: The Ciass of Device/Service iieid {format type 1). Note the order in which the
`octets are sent on the air and stored in rnerr.-oryc
`
`1.2.1 Major Service Classes
`
`Major Service Class
`
`Limited Discoverable Mode‘
`
`(reserved)
`
`(reserved)
`
`(reserved)
`
`Networking (LAN, Adhoc. ...}
`
`Rendering (Printing. Speaker. ...)
`
`Capturing (Scanner. Microphone. ...)
`
`Object Transfer (v-lnbox. v-Folder, ...}
`
`Audio (Speaker. Microphone. Headset service. ...)
`
`Telephony (Cordless telephony. Modem, Headset service, ...)
`
`Information (WEB—server. WAP-server. ...)
`
`Tebie 1.2: Major Service Ciasses
`
`1. As defined in £7;
`
`Bluetooth Baseband
`
`29 November 1999
`
`AFFLT0294241
`
`Samsung Ex. 1019 p. 1013
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`Biuetooth Assigned Numbers
`
`1.2.2 Major Device Classes
`
`page 1014 of1082
`
`Bluetooth-
`
`The Major Class segment is the highest level of granularity for defining a Blue-
`tooth Device. The main function of a device is used to determine the major
`class grouping. There are 32 different possible major classes. The assignment
`of this Major Class field is defined in Taste 3.3.
`
`Code (bits)
`
`Major Device Class
`
`bit no of COD
`
`Miscellaneous‘
`
`Computer (desktop, notebook, PDA, organizers, ...)
`
`Phone (cellular, cordless, payphone, modem. ...)
`
`LAN Access Point
`
`Audio (headset, speaker, stereo, ...)
`
`Peripheral (mouse,joysfck, keyboards, ...)
`
`Range 0x06 to 0><1E reserved
`
`Unclassified, specific device code not assigned
`
`Table 1.3: Major Device Classes
`
`1. Used where a more specific Major Device Class code is not suited (but only as speci-
`fied in this document. Devices that do not have a major class code assigned can use
`the all-1 code until classified’)
`
`1.2.3 The Minor Device Class field
`
`The ‘Minor Device Class field’ (bits 7 to 1 in the COD). are to be interpreted only
`in the context of the Major Device Class (but independent of the Service Class
`field). Thus the meaning of the bits may change, depending on the value of the
`‘Major Device Class field’. When the Minor Device Class field indicates a
`device class. then the primary device class should be reported, eg. a cellular
`phone that can also work as a cordless handset should use ‘Cellular’ in the
`minor device class field.
`
`29 November 1999
`
`Bluetoolh Baseband
`
`AFFLT0294242
`
`Samsung Ex. 1019 p. 1014
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1015 of 1082
`
`Biuetooth Assigned Numbers
`
`1.2.4 Minor Device Class field - Computer Major Class
`
`Code (bits)
`
`Minor Device Class
`
`bit no of CoD
`
`Unclassified. code for device not assigned
`
`Desktop workstation
`
`Server-ciass computer
`
`Laptop
`
`Handheld PCIPDA (clam shell)
`
`Palm sized PCJPDA
`
`Range 0x06-0x7F reserved
`
`6
`
`0 0 0 0 0 0
`
`x
`
`Table 1.4: Sub Device Class fieid for the ‘Computer’ Major Crass
`
`1.2.5 Minor Device Class field - Phone Major Class
`
`Code (bits)
`
`Minor Device Class
`
`bit no of CoD
`
`Unclassified. code not assigned
`
`Ceilular
`
`Cordiess
`
`Smart phone
`
`Wired modem or voice gateway
`
`Range 0x05-Ox7F reserved
`
`Tabie 1.5: Sub Device Classes for the 'Phone' Major Class
`
`Bluelooih Baseband
`
`29 November 1999
`
`AFFLT0294243
`
`Samsung Ex. 1019 p. 1015
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1016 of1082
`
`Bluetooth Assigned Numbers
`
`1.2.6 Minor Device Class field - LAN Access Point Major Class
`
`Code (bits)
`
`Minor Device Class
`
`6
`
`0
`0
`
`'
`
`' bit no of CoD
`
`Fully available
`1-17”/o utilized
`
`17 - 33% utilized
`
`33 - 50% utilized
`
`50 - 67% utilized
`
`6? — 83°/o utilized
`
`83 — 99% utilized
`
`7 O 0
`
`0 O
`
`1
`
`No Service Available‘
`
`Table 1.6: The LAN Access Point Load Factor field
`
`1. "Device is fully utilized and cannot accept additional connections at this time. please
`retry later"
`
`The exact loading formula is not standardized. It is up to each LAN Access
`Point implementation to determine what internal conditions to report as a utili-
`zation percentage. The only requirement is that the number refiects an ever-
`increasing utilization of communication resources within the box. As a recom-
`mendation, a client that locates multiple LAN Access Points should attempt to
`connect to the one reporting the lowest load.
`
`Code (bits)
`
`Minor Device Class
`
`bit no of Col)
`
`Unclassified (use this value if no other apply}
`
`range 0x01-0x0F reserved
`
`Table 1. 7: Reserved sub-field for the LAN Access Point
`
`29 November 1999
`
`Bluetoolh Baseband
`
`AFFLT0294244
`
`Samsung Ex. 1019 p. 1016
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1017 of 1082
`
`Biuetoorh Assigned Numbers
`
`1.2.7 Minor Device Class field - Audio Major Class
`
`Code (bits)
`
`Minor Device Class
`
`bit no of COD
`
`Unclassified. code not assigned
`
`Device conforms to the Headset profile
`
`Range 0x02-Ox‘./F reserved
`
`Table 1.8: Sub Device Classes forrhe ‘Audio’ Major Cress
`
`Bluelooih Eiaseband
`
`29 November 1999
`
`AFFLT0294245
`
`Samsung Ex. 1019 p. 1017
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1018 of1082
`
`Biuetootn Assigned Numbers
`
`2 LINK MANAGER PROTOCOL (LMP)
`
`2.1 THE LINK MANGER VERSION PARAMETER
`
`Parameter name
`
`Assigned values
`
`0
`
`Bluetooth LMP 1.0. E21
`
`1-255
`
`(reserved)
`
`Table 2.1.’ The LMF’ Version Parameter Vaiues
`
`2.2 THE LMP__COMP|D PARAMETER CODES
`
`This is the parameter used in the LMP Version procedure.
`
`Company
`
`Ericsson Mobile Communications
`
`Nokia Mobile Phones
`
`Intel Corp.
`
`IBM Corp.
`
`Toshiba Corp.
`
`(reserved)
`
`Unassigned. For use in internal and interoperability tests before a Company
`ID has been assigned. May not be used in products.
`
`Table 2.2: The LMP_Comp.'d parameter codes
`
`29 November 1999
`
`Link Manager Protocol (LMP)
`
`AFFLT0294246
`
`Samsung Ex. 1019 p. 1018
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1019 of 1082
`
`Biueiooth Assigned Numbers
`
`3 LOGICAL LINK CONTROL AND ADAPTATION
`
`PROTOCOL (LZCAP)
`
`Please see Section
`
`for assigned PSM values.
`
`3.1 CHANNEL IDENTIFIERS
`
`Destination CID
`
`Protocoliusage
`
`Reference
`
`UXOUUU
`
`0240001
`
`0x0002
`
`Illegal. should not be used
`
`L2CAP signalling channel
`
`LZCA connection less data
`
`0x0O03 - 0XUU3F
`
`(reserved)
`
`Table 3. is Pre-defined i_2CAP Channel identifiers
`
`3.2 PROTOCOL AND SERVICE MULTIPLEXOR (PSM)
`
`SOP
`
`RFCOMM
`
`TCS~BIN
`
`TCS-BlN—CORDLESS
`
`Tabie 3.2: Assigned Protocol and Service Muitipiexor vaiues (PSM)
`
`Logical Link Control and Adaptation Protocol (L2CAF']29 November 1999
`
`AFFLT0294247
`
`Samsung Ex. 1019 p. 1019
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1020 of1082
`
`Biuetooih Assigned Numbers
`
`Bluetooth-
`
`4 SERVICE DISCOVERY PROTOCOL (sop)
`
`4.1 UNIVERSALLY UNIQUE IDENTIFIER (UUID) SHORT
`FORMS
`
`The Bluetooth Service Discovery Protocol (SDP) specification defines a way to
`represent a range of UU|Ds (which are nominally 128-bits) in a shorter form. A
`reserved range of 232 values can be represented using 32—bits (denoted
`uuid32). Of these, a sub-range of 215 values can be represented using only 16-
`bits (denoted uuid16). Any value in the 232 range that is not assigned in this
`document is reserved pending future revisions of this document. In other
`words, no value in this range may be used except as specified in this or future
`revisions of this document. UUID values outside of this range can be allocated
`as described in {"193 for any purpose the allocater desires.
`
`4.2 BASE UNIVERSALLY UNIQUE IDENTIFIER (UUID)
`
`The Base UUID is used for calculating 128-bit UUIDS from ‘short UU|Ds’
`(uuid16 and uuid32) as described in the SDP Specification {4}.
`
`BASE_UU ID
`
`00000000-U000-1000-8000-00805F9B34FB
`
`29 November 1999
`
`Service Discovery Protocol (SDP)
`
`AFFLT029424B
`
`Samsung Ex. 1019 p. 1020
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1021 of 1082
`
`Bluetooth Assigned Numbers
`
`4.3 PROTOCOLS
`
`Mnemonic
`
`Tobie 4.1: Protocol Universafly Unique Identifiers and Names
`1. ‘Short UU|D'
`
`Service Discovery Protocol (SDP)
`
`29 November 1999
`
`AFFLT0294249
`
`Samsung Ex. 1019 p. 1021
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1022 of1082
`
`Biuetooth Assigned Numbers
`
`4.4 SERVICE CLASSES
`
`{mnemonic
`
`UUID
`
`Abstracmame
`
`ServiceDiscoveryserverserviceclasslD
`
`uuid16: OXTUUU
`
`ElrowseGroupDescriptorserviceclasslD
`
`uuid16: 0.11001
`
`Pub|icBrowseGroup
`
`Seria|Port
`
`LANAccessUsingPPP
`
`Dia|upNetworking
`
`|rMCSync
`
`OBEXObjectPush
`
`OBEXFi|eTransfer
`
`|rMCSyncCommand
`Headset
`
`C'.ord|essTelephony
`
`Intercom
`
`Fax
`
`HeadsetAudioGateway
`
`PnP|nformation
`
`GenericNetworking
`
`GenericFi|eTransfer
`
`GenericAudio
`
`uuid16: 0.21002
`
`uuid16: 0x110‘!
`
`uuid16: OXHO2
`
`uuid16: OXHO3
`
`uuid16: OXHO4
`
`uuid16: OXHO5
`
`uuid16: 0x1106
`
`uuid16: 0x110?
`uuid16: 0x1108
`
`uuid16: Ox1‘i09
`
`uuid16: 0x1‘i‘10
`
`uuid16: 0x1‘i11
`
`uuid16: 0x1112
`
`uuid16: 0x1200
`
`uuid16: 0x120?
`
`uuid16: 0x1202
`
`uuid16: 0x'i203
`
`nfa
`
`nia
`
`nia
`
`GenericTelephony
`
`uuid16: Ox1204
`
`nia
`
`Table 4.2: Service Class identifiers and Names
`
`1. If the specified Service Class directly and exactly implies a certain Profile, the Profile is
`indicated here (ie. for concrete Service Classes). Leave empty for abstract Service
`Classes.
`
`The Profile column in "facts 4.2 indicates which Service Class identifiers that
`
`also directly corresponds to a Bluetooth Profile. It is not allowed to use the Ser-
`vice Class UUID unless the service complies with the specified Profile. These
`UUlDs might also appear as Profile Identifiers in the
`BluetoothProfi|eDescriptorList attribute.
`
`29 November 1999
`
`Service Discovery Protocol (SDP)
`
`AFFLT0294250
`
`Samsung Ex. 1019 p. 1022
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 1023 of 1082
`
`Biuetoorh Assigned Numbers
`
`4.5 ATTRIBUTE IDENTIFIER CODES
`
`Mnemonic
`
`Attribute ID
`
`Reference
`
`Biuetoorh Service Discovery
`Protocoi (SOP), B luetooth SIG
`
`ServiceRecordHand|e
`
`ServiceC|asslDList
`
`ServiceRecordStaIe
`
`Servicel D
`
`Protoco|DescriptorList
`
`BrowseGroupList
`
`La ng uageBaseAnributelDList
`
`ServiceInfoTimeToLive
`
`Se-rviceAva i lability
`
`BIuetoothProfi!eDescriptorList
`
`DocumentaticnURL
`
`C|iemExecutab|eURL
`
`Icor110
`
`IconURL
`
`Reserved
`
`ServiceName
`
`ServiceDescripticn
`
`Providerhiame
`
`Versionhlumbertist
`
`ServiceDatabaseS1ate
`
`GrouplD
`
`Remote audio volume control
`
`Externai network
`
`Servioe Version
`
`Supported Data Stores List
`
`Supported Fcrmais List
`
`Tabie 4.3: Attribute identifiers
`
`OXOOUU
`
`0x0001
`
`CIX0002
`
`0x0003
`
`UX0004
`
`0x0005
`
`0x0006
`
`0x000?
`
`DX0008
`
`OXOOOQ
`
`OXOOOA
`
`UXOOUB
`
`OXOCIUC
`
`0x000D
`
`0x000E-
`OXO1 FF
`
`oxooog ... bi
`
`0x000‘! + b
`
`0x0O02 + b
`
`0x0200
`
`0x020‘!
`
`OXOZDO
`
`M03022
`
`0x0301
`
`Ox0300
`
`0x0301
`
`Service Discovery Protocol (SDPJ
`
`29 November 1999
`
`AFFLT0294251
`
`Samsung Ex. 1019 p. 1023
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 1024 of1082
`
`Bluetooth Assigned Numbers
`
`Bluetooth-
`
`Mnemenic
`
`Attribute ID
`
`Reference
`
`Fax Class 1 Support
`
`Fax Class 2.0 Support
`
`Fax Class 2 Support
`
`Audio Feedback Support
`
`Table 4. 3: Attribute identifiers
`
`0xO302
`
`0xCl303
`
`D)<U3D4
`
`DxCl305
`
`[123
`
`1.
`
`2.
`
`‘b’ in this table represents a base offset as given by the LanguageBaseAttribute|DList
`attribute. For the primary language. ‘b’ must be equal to 0x0100 as described in the
`SDP specification.
`Items in italic are tentative values in this version of the document.
`
`4.6 PROTOCOL PARAMETERS
`
`Parameter mnemonic
`
`L2CAP
`
`TCP or UDP
`
`RFCOMM
`
`Table 4.4: Protocol Parameters
`
`4.7 HOST OPERATING ENVIRONMENT IDENTIFIERS
`
`4.7.1 ClientExecutableURL substitution strings
`
`The operating environment identifier strings have the following format”:
`
`<cp u_type>-¢ manufa cturer>-[< l<erne|>-]<o s>[<version>] E-<0 bje ct_form at>]
`
`The general rule is that is that a new identifier should only be defined as
`required to differentiate incompatible operating environments concerning an
`executable file image. That is, for example different <version>~tags should not
`be used for compatible versions of the same operating system.
`
`1.