throbber
BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 166 of €882
`
`Baseband Specification
`
`Bluetooth-
`
`order to distribute the starting states more uniformly. The operation is defined
`in (E0 30).
`
`When the encryption key has been created the LFSRs are loaded with their ini-
`tial values. Then, 200 stream cipher bits are created by operating the genera-
`tor. Of these bits, the last 128 are fed back into the key stream generator as an
`
`initial value of the four LFSRs. The values of C! and c,
`
`, are kept. From this
`
`point on, when clocked the generator produces the encryption (decryption)
`sequence which is bitwise XORed to the transmitted (received) payload data.
`
`In the following, we will denote octet I of a binary sequence X by the notation
`X] I] . We define bit 0 of X to be the LSB. Then, the LSB of X151 corresponds to
`
`hit 8:‘ of the sequence X, the MSB ofX1r] is bit Sil 7 ofX. Forinstance, bit 24
`of the Bluetooth address is the LS8 of ADR[3].
`
`The details of the initialization are as follows:
`
`1.
`
`Create the encryption key to use from the 128-bit secret key K(. and
`the 128-bit publicly known EN_RAND. Let L,
`I 3 L 3 I6, be the
`effective key length in number of octets. The resulting encryption key
`will be denoted K‘._«_-:
`
`K‘.-{.0 = ggM(1')(K{-(3') mod g“("’(x)),
`
`(1~:Q3o)
`
`where deg-,(g‘,"’(;l-}} = 8L and deg(g‘;"’[.r}} g [28 — SL. The polynomials
`are defined in Tehie 14.6.
`
`Shift in the 3 inputs K}-, the Bluetooth address, the clock, and the six-
`bit constant 111001 into the LFSRs. In total 208 bits are shifted in.
`
`a) Open all switches shown in Figure "M8 on page 158;
`
`b) Arrange inputs hits as shown in i"-lgcrte 14.8; Set the content of all
`shift register elements to zero. Set r = I).
`
`c) Start shifting bits into the LFSRs. The rightmost bit at each level of
`i:'E§_.‘;t.i.?‘€‘ 14.8 is the first bit to enter the corresponding LFSR.
`
`d) When the first input bit at level i reaches the rightmost position of
`LFSRi, close the switch of this LFSR.
`
`e) At r = 39 (when the switch of LFSR4 is closed), reset both blend
`registers «-3., = c3.,_1 = 0; Up to this point, the content of c, and
`c,
`1 has been of no concern. However, from this moment forward
`their content will be used in computing the output sequence.
`
`f) From now on output symbols are generated. The remaining input
`bits are oontinuously shifted into their corresponding shift register.
`When the last bit has been shifted in, the shift register is clocked
`with input = 0;
`
`Note: When finished, LFSR1 has effectively clocked 30 times
`with feedback closed, LFSR2 has clocked 24 times. LFSR3 has
`
`29 November 1999
`
`Bluetooth Security
`
`AFFLT0293394
`
`Samsung Ex. 1019 p. 166
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 187 of 1032
`
`Baseband Speolficallon
`
`clocked 22 times, and LFSR4 has effectively clocked 16 times
`with feedback closed.
`
`To mix initial data, continue to clock until 200 symbols have been
`produced with all switches closed (r = 239);
`
`. make a parallel load of the last 128
`Keep blend registers a, and c, _ ,
`generated bits into the LFSRS according to Figure ‘$4.9 at r = 240;
`
`After the parallel load in item 4, the blend register contents will be updated for
`each subsequent clock.
`:
`{Ll
`[Li
`8|
`32
`00227530 aizlfidii Cf923b9b bf6l'_'hDBf
`
`L
`
`den;
`[3]
`
`00000000 00000000 00000000 000001111
`
`deg
`[119]
`
`[16]
`
`[241
`
`[32]
`
`I40)
`
`E43]
`
`[56]
`
`[54]
`
`l?2l
`
`[so]
`
`[39]
`
`oooooooo ooonoono oooooooo 00010035
`
`cuooooao oonooooo oooooooo otoooodb
`
`00000000 oooooooo 00000001 ooooooat
`
`oooooouo oooooooo 00000100 oooaooze
`
`00000000 00000000 00010000 00000291
`
`00000000 00000000 01000000 00000095
`
`00000000 00000001 oooooooo oooooo1b
`
`00000000 00000100 oooooooo oooooeoe
`
`00000000 00010000 00000090 00000215
`
`00000000 01000000 oooooooo O000013b
`
`00000001 oonooooo oaoooooo ooooooed
`
`oooooloo oacooooo ouoooono oooooded
`
`00010000 oooooooo oooooooo 00000145
`
`01000000 00000000 00000000 00000097
`
`[1121
`
`[1041
`
`[96]
`
`[es]
`
`[71]
`
`[71]
`
`E63]
`
`[491
`
`E42]
`
`[35]
`
`[23]
`
`I21}
`
`:14}
`
`[71
`
`0O01e3fS 3d7659b3 ?fl3E2E8 ctrserefi
`
`Uoooolbe EG6c6c3a b1030A5a 1915aosb
`
`00000001 6abB9969 delTd6Tf d3736ad9
`
`oooooooo 01530532 91da5Dec 55715247
`
`00000000 00002c93 szaascco 54468311
`
`00000000 000000133 E7EffCC2 79E3ul073
`
`oooooooo ooonoooo a1ah815b c7ecso25
`
`oooooooo oooooooo 0002c980 lidshodd
`
`00000000 00000000 onooosae 2dE9AIbb
`
`oooooooo oooooooo oooooooc a76024d7
`
`00000000 oooooooo oooooooo lc9c26b9
`
`ouoooooo oooooono oooooooo 0O26d9e3
`
`oaoooona nuonaooo ouoooooo oooo4317
`
`00000000 00000000 00000000 00000039
`
`[123]
`
`1 00000000 00000000 00000000 00000000
`
`00000000 00000000 00000000 00000001
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`Table 14.6: Polynomials used when creating K}.
`All polynomials are in hexadeolmal notation. The l_SB is in the rlghtinosfposltlon.
`
`In Figure ta-3.8, all bits are shifted into the LFSRS. starting with the least signifi-
`cant bit (LSB). For instance, from the third octet of the address. ADR[2], first
`ADR15 is entered, followed by ADR17, etc. Furthermore, CLO corresponds to
`
`CLK1,..., CL25 corresponds to CLK25.
`
`Note that the output symbols .1-j,:' = I,
`
`4 are taken from the positions 24, 24,
`
`32, and 32 for LFSR1, LFSR2,LFSR3, and LFSR4, respectively (counting the
`leftmost position as number 1).
`
`Blueloolh Security
`
`29 November 1999
`
`AFFLT0293395
`
`Samsung Ex. 1019 p. 167
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 158 of €882
`
`Baseband Specification
`
`Bluetooth.
`
`AD|t[-t[t‘l_[1]I\Lc‘[l4]1(c'[!i.I|Kc'[fi]Kt-‘[2] £1.25
`
`AJJll]:"| .-\l)R[l| Kc'[]i] Kc'[l I |Ki:'[‘.'| K4213]
`
`(.‘.|.[I'.I]_]
`
`I
`
`I
`
`‘ =1’
`
`Figure 14.8: Arranging the input to the i_FSRs.
`
`In Figure 14.9, the 128 binary output symbols Z0,..., Z127 are arranged in octets
`denoted Z[O],.... Z[15]. The LSB of Z[0] corresponds to the first of these sym-
`bols, the MSB of Z[15] is the latest output from the generator. These bits shall
`be loaded into the LFSRs according to the figure. It is a parallel load and no
`update of the blend registers is done. The first output symbol is generated at
`the same time. The octets are written into the registers with the LS8 in the left-
`most position (i.e. the opposite of before). For example, 224 is loaded into posi-
`
`tion 1 of LFSR4.
`
`z[4]
`
`PET
`
`In
`
`::[5]
`
`-vi’
`
`z[m]
`
`.7
`z[3]
`
`z[9]
`
`-=7
`z[13]
`
`z[1]
`
`|
`
`-T
`”‘
`z[2]
`
`Z[6]
`
`Figure 14.9.’ Distribution of the 128 test generated output symbois within the LFSRS.
`
`14.3.6 Key stream sequence
`
`When the initialization is finished, the output from the summation combiner is
`used for encryptionidecryption. The first bit to use is the one produced at the
`
`parallel load, i.e. at r = 240. The circuit is run for the entire length of the current
`payload. Then, before the reverse direction is started. the entire initialization
`process is repeated with updated values on the input parameters.
`
`29 November 1999
`
`Bluetooth Security
`
`AFFLT0293396
`
`Samsung Ex. 1019 p. 168
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 169 of 1082
`
`Base-band Specification
`
`Sample data of the encryption output sequence can be found in “.&\pper‘.déx l‘v""'
`on page
`Encryption Sample Data. A necessary, but not sufficient, condi-
`tion for all Bluetooth-compliant implementations is to produce these encryption
`streams for identical initialization values.
`
`14.4 AUTHENTICATION
`
`The entity authentication used in Bluetooth uses a challenge-response scheme
`in which a claimant's knowledge of a secret key is checked through a 2-move
`protocol using symmetric secret keys. The latter implies that a correct claimant!
`verifier pair share the same secret key. for example K. In the challenge-
`response scheme the verifier challenges the claimant to authenticate a random
`input (the challenge), denoted by AU_RANDA, with an authentication oode,
`
`denoted by E] , and return the result SRES to the verifier, see
`
`14.30 on
`
`page ‘$59. This figure shows also that in Bluetooth the input to E1 consists of
`
`the tuple AU_RAN DA and the Bluetooth device address (BD_ADDR) of the
`claimant. The use of this address prevents a simple reflection attack‘. The
`secret K shared by units A and B is the current link key.
`
`Verifier (Unit A}
`
`Claimant (Unit B)
`
`AU R/‘NBA
`
`AU RAND“
`
`AU RANDA
`
`BD ADDRB
`
`Link key
`
`Figure 14.10: Chaiienge-response for the Biuetooth.
`
`The challenge-response scheme for symmetric keys used in the Bluetooth is
`depicted in i3'§g=..=r'e 14.1? on page ’§‘}’tJ.
`
`1. The reflection attack actually forms no threat in Bluetooth because all service requests are
`dealt with on a FIFO bases. When pre-emption is introduced, this attack is potentially dan-
`gerous.
`
`Bluetooth Security
`
`29 November 1999
`
`AFFLT0293397
`
`Samsung Ex. 1019 p. 169
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 170 of €882
`
`Baseband Specification
`
`Bluetooth-
`
`Verifier
`(User Al
`
`Claimant
`{Uscr B. with identity {DB}
`
`SRES — Eikcy. IDB. RAND]
`
`SRES' = Eikuy. IDB, RAND":
`
`Check: SRES‘ — SRES
`
`Figure 14. ‘ii: Chaiienge-response for symmetric key systems.
`
`In the Bluetooth. the verifier is not necessarily the master. The application indi-
`cates who has to be authenticated by whom. Certain appiications only require
`a one-way authentication. However, in some peer-to-peer communications.
`one might prefer a mutual authentication in which each unit is subsequently the
`challenger (verifier) in two authentication procedures. The LM coordinates the
`indicated authentication preferences by the application to determine in which
`direction(s) the authentication(s) has to take place. For mutual authentication
`with the units of i~"tg-are 14.18 on page ‘Z59, after unit A has successfully
`authenticated unit B, unit B could authenticate unit A by Sending a AU_RAND3
`
`(different from the AU_RAN DA that unit A issued) to unit A, and deriving the
`
`SRES and SRES‘ from the new AU_RANDB, the address of unit A, and the link
`
`key KAB.
`
`If an authentication is successful the value of ACO as produced by E, should
`be retained.
`
`14.4.1 Repeated attempts
`
`When the authentication attempt faiis, a certain waiting interval must pass
`before a new authentication attempt can be made. For each subsequent
`authentication failure with the same Bluetooth address, the waiting interval
`shall be increased exponentially. That is. after each failure, the waiting interval
`before a new attempt can be made, for example. twice as long as the waiting
`interval prior to the previous attempt1. The waiting interval shalt be limited to a
`maximum. The maximum waiting interval depends on the implementation. The
`waiting time shall exponentially decrease to a minimum when no new failed
`attempts are being made during a certain time period. This procedure prevents
`an intruder to repeat the authentication procedure with a large number of differ-
`ent keys.
`
`1. An other appropriate value larger than 1 may be used.
`
`1?0
`
`29 November 1999
`
`Bluetooth Security
`
`AFFLT029339B
`
`Samsung Ex. 1019 p. 170
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 171 of 1082
`
`Base-band Specification
`
`To make the system somewhat less vulnerable to denial-of-service attacks, the
`Bluetooth units should keep a list of individual waiting intervais for each unit it
`has established contact with. Clearly, the size of this list must be restricted only
`to contain the N units with which the most recent contact has been made. The
`
`number N can vary for different units depending on available memory size and
`user environment.
`
`14.5 THE AUTHENTICATION AND KEY-GENERATING
`
`FUNCTIONS
`
`This section describes the algorithmic means for supporting the Bluetooth
`security requirements on authentication and key generation.
`
`14.5.1 The authentication function E1
`
`The authentication function E] proposed for the Bluetooth is a computationally
`
`secure authentication code, or often called a MAC. E, uses the encryption
`
`function called SAFER+. The atgorithm is an enhanced version‘ of an existing
`64-bit block cipher SAFER-SK128, and it is freely available. In the sequel the
`
`block cipher will be denoted as the function A, which maps under a 128-bit key.
`
`a 128-bit input to a 128-bit output, i.e.
`
`123
`
`123
`‘
`><{0,[} —){0,l}
`A,.. {0,l}
`(k x x] i—> r.
`
`123
`
`(E031)
`
`The details of A, are given in the next section. The function E:
`
`is constructed
`
`using A,. as follows
`
`E :
`.i
`
`0‘ I
`
`133
`
`}
`
`0,
`
`I
`
`12:4
`
`33
`43
`}><{
`i—>l
`><l
`l
`><{
`(K, RAND, address) l—>(SRES, ACO),
`
`0’ I
`
`0‘ I
`
`0,
`
`9:5
`
`I
`
`}
`
`(mm
`
`where SRES = Hr:s:'1[K, RAND,addrcss, 6)[U,
`function defined asz.
`
`3], where Hash is a keyed hash
`
`Hasi:r:{0, I }'2“x to. llmx in. 1}“""‘x is, 12} —> {(1.
`
`I :33“
`
`(K. I], «'3. L) i—>.4‘.-tlif]. [E02, L) +1‘, <A,.U<. Il)<+3u,!l)1),
`
`and where
`
`1. It is presently one of the contenders for the Advanced Encryption Standard (AE8) submitted
`by Cylinlc, Corp. Sunnyvale, USA
`
`2. The operator +15 denotes bytewise addition mod 256 of the 16 octets. and the operator 69,5
`denotes bytewise XORing of the 16 octets.
`
`Bluetooth Security
`
`29 November 1999
`
`AFFLT0293399
`
`Samsung Ex. 1019 p. 171
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 172 of €882
`
`Baseband Specification
`
`Eziu,1}*""‘x{6,12_:--+{u,1}*"“°
`
`(X[0,....L l],L) |—>(X[i(modL-)] fori=0...l5),
`
`Bluetooth.
`
`(17-Q 34}
`
`is an expansion of the L octet word X into a 128-bit word. Thus we see that we
`
`have to evaluate the function A, twice for each evaluation of El . The key I? for
`
`the second use of .4, (actually A',.) is offseted from K as follows‘
`
`K10] =u<[0] l 233) mod 256, K[l]=K[l]Ei-D229,
`
`R12] =(K[2] : 223)
`
`rnod256, K[3]=K[3]EB 193,
`
`iq41=(K[4]+179) mod256, K[5]=K|5]®l6'i,
`
`R16] =(K[6] l 149) mod 256, K[7]=K[?]EBl3l,
`
`.?<[s]=K[8]e233,
`
`iC[9]=(K[9] : 229) mod 256,
`
`icnoi =1<[:o]@223,
`
`k[n1=u<[111+193)mod256,
`
`k[12]=K[z2]ea179.
`
`i<[13]=u<[13] u 16?) mod 256,
`
`i<[I41=K[I4is) I49.
`
`f<[15]=(K[15] u 131) n1od256.
`
`A data flowchart of the computation of El
`
`is depicted in Figure ‘$4.12 on page
`
`'3 7'3. E,
`
`is also used to deliver the parameter ACO (Authenticated Ciphering
`
`Offset) that is used in the generation of the ciphering key by E_,_ , see equations
`
`EEG 23} and {EC} 43}. The value of ACO is formed by the octets 4 through 15 of
`the output of the hash function defined in (EC? 33'}. i.e.
`
`ACO = H(:s!z(K, RAND,address, 6)]-4, ..., I5].
`
`(EQ 36}
`
`1. The constants are the first largest primes below 257 for which 10 is a primitive root.
`
`1?2
`
`29 November 1999
`
`Biuetooth Security
`
`AFFLT0293400
`
`Samsung Ex. 1019 p. 172
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 173 of 1082
`
`Base-band Specification
`
`Bluetooth.
`
`xor :16 8-bit xor-ings
`
`add: 16 8-bit additions mod 256
`
`Figure 14.12: Fiow ofdara for the computation of E 1
`
`.
`
`14.5.2 The functions A, and A’,
`
`The function A, is identical to SAFER-I». It consists of a set of8 layers, (each
`
`layer is called a round) and a parallel mechanism for generating the sub keys
`KP[_,i], p = I, 2, ..., 1?, the so-called round keys to be used in each round. The
`function will produce a 128-bit result from a 128-bit "random" input string and a
`128-bit “key". Besides the function .4,_. a slightly modified version referred to as
`
`A’, is used in which the input of round 1 is added to the input of the 3rd round.
`
`This is done to make the modified version non-invertible and prevents the use
`
`of A’, (especially in E1, ) as an encryption function. See §’§gure M-f3 on page
`‘ii’-4 for details.
`
`14.5.2.1 The round computations
`
`The computations in each round are a composition of encryption with a round
`key. substitution, encryption with the next round key, and, finally. a Pseudo
`Hadamard Transform (PHT). The computations in a round are shown in Fig:..=re
`14.1.’: on page ‘Jet-. The sub keys for round r, r = l, 2,
`8 are denoted
`
`Bluetooth Security
`
`29 November 1999
`
`AFFLT0293401
`
`Samsung Ex. 1019 p. 173
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 174 of €082
`
`Baseband Specification
`
`K3,.
`
`][j]. K3,.[,il,,«' = 0, 1,
`
`15.Afterthe last round knl,-‘|
`
`is applied in a similar
`
`fashion as all previous odd numbered keys.
`
`14.5.2.2 The substitution boxes ‘'9'’ and “i”
`
`In Figure 1.4.113 on page tit: two boxes occur, marked “e" and "I". These boxes
`implement the same substitutions as used in SAFER+; i.e. they implement
`
`e.i
`
`e
`
`I
`
`:
`
`:
`
`:
`
`{0,...,255}—>{0,...,255},
`
`i
`
`|—>(45*' (mod 257)) (mod 256),
`
`1‘
`
`l—>j s.t. i = e(i}.
`
`Their role, as in the SAFER+ algorithm, is to introduce non-linearity.
`
`
`
`.-I-...____'..—n=-u-—'_‘—¢-'—a2-.-—.-u—
`
`
`
`
`
`
`
`15-.'-..—es-...-
`
`lJr:l_\- lur .-\’r in romul 3
`
`I.“ A In pu|[fl..I5!
`
`IE
`
`.
`. 1\m|n..1s|
`
`..
`
`III
`
`Kzr|fl..l5]
`
`.:'-u'-41-.I:'-I‘$6I:
`
`
`
`.§..._'—f.--12-_'-u'sea..
`
`'._-uIL.'9.4
`
`T-u
`
`
`
`11-4as-I-"-o'_3-ow-43-_I-w-w-n
`
`I
`
`R(‘Jl.‘NDr.I-1.2....“
`
`PUT
`
`.Y
`
`.'I'
`
`Y
`'I'..
`.'l'
`..
`I
`'l'
`Mr: I
`PIIT
`I PHT I
`I PIl1'
`l
`i
`_
`I’
`I
`I
`'I'
`I
`I
`I
`'I'
`I‘ERMl‘T'E:8ll I2l52I65IEl9I-il.![|T-i]
`I
`I
`I
`_L__.t
`.l_.l. _I._L _I._t..
`.I_1
`_i_.I _i_t.
`I PH1'I
`I PHTI
`PHT
`“HT
`I PIITI
`PHT_I
`PHT
`.i
`Z
`l
`!
`L
`_'I_
`..I'
`.'l
`1.
`._I.
`I'..
`.1.
`.I
`..I_
`.I.
`I.
`'l'
`l‘ERMl."[‘I'-_':8lII2l52|65I£I9I4l.Hl7-£3
`
`._l
`
`L.
`I|_I
`_I
`I
`L_
`PHTI
`I'H'l'_IPH'l'LIIPHTI
`I
`I‘
`I‘
`'I'.
`I
`1'
`I
`Pl-‘.RMl‘TE:8IIl2I52l65Iil9I-II.HI74.!
`
`"iii
`.! Ll
`1:
`IPll'I'
`PHTI
`
`I
`
`I -I
`I
`
`|.I
`
`r:_i I._II I‘
`1.:.
`
`rm
`PH'l':IPHTIIl‘HTI
`
`r
`
`....
`53¢:
`
`£_
`
`.
`
`.:
`
`;_
`
`.
`
`3‘ ndllltlon mod :56
`
`hllvtlse xon
`"’f'
`PIlTIx.5'>- E2x+3- mm! 1515. n+_\- mm] 256!
`
`Figure 14.13: One round in .4, and A3. . The permuatetion boxes show how input byte indices are
`mapped onto output byte indioes. Thus, position 0 (ieiimosf) is mapped on position 8. position 1 is
`mapped on position 11, etcetera.
`
`1?4
`
`29 November 1999
`
`Bluetooih Security
`
`AFFLT0293402
`
`Samsung Ex. 1019 p. 174
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 175 of 1082
`
`Base-band Specification
`
`14.5.2.3 Kegscheduiing
`
`In each round, 2 batches of 16 octet-wide keys are needed. These so-called
`round keys are derived as specified by the key scheduling in SAFER+. Figiire
`‘l-if-t on page 1.75 gives an overview of how the round keys K,,|J'| are deter-
`mined. The bias vectors B2, B3, ..., B17 are computed according to following
`equation:
`
`app] = ((45“
`
`5-"”""' mod25
`
`T’ mod 25?) mod 256), rm: = 0,
`
`15.
`
`128 bit Key group-ed in [6 uclels
`
`sum oclcls
`hit-by-hit
`modulo lwn
`
`Sol:-cl aclels
`
`I), I ,2,....,l-1,15
`
`SI:'[I:'I‘.'l nctels
`
`1.2.3»--«.l5,lfI
`
`I
`ll
`
` -
`--
`1
`14
`I5
`16
`
`2..1,4....,l6,l!
`
`figure 14.14: Key scheduiingin A,..
`
`14.5.3 E2-Key generation function for authentication
`
`The key used for authentication is derived through a procedure that is shown in
`§3§QL§!'&‘:' 14. t
`on page 17?‘. The figure shows two different modes of operation
`
`for the algorithm. In the first mode, the function E; should produce on input ofa
`
`128-bit RAND value and a 48-bit address, a 128-bit link key K. This mode is
`utilized when creating unit keys and combination keys. In the second mode the
`
`function E: should produce, on input of a 128-bit RAND value and an L octet
`
`user PIN. a 128-bit link key K. The second mode is used to create the initializa-
`tion key, and also whenever a master key is to be generated.
`
`Bluetooth Security
`
`29 November 1999
`
`AFFLT0293403
`
`Samsung Ex. 1019 p. 175
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 176 of €882
`
`Baseband Specification
`
`Bluetooth-
`
`When the initialization key is generated, the PIN is augmented with the
`BD_ADDR of the claimant unit. The augmentation always starts with the least
`significant octet of the address immediately following the most significant octet
`of the PIN. Since the maximum length of the PIN used in the algorithm cannot
`exceed 16 octets, it is possibie that not all octets of BD_ADDR will be used.
`
`This key generating algorithm again exploits the cryptographic function. For-
`
`mally E: can be expressed for mode 1 (denoted E21 ) as
`
`53,:
`
`{(1,
`
`I }”“x {(1, 1}“-> {(1, i}'”
`
`(RAND, address] i—>A‘,{X, )0
`
`where (for mode 1)
`
`X = RANDIO... [4] kJ(RAND[ [5] ‘P3 6)
`in
`
`Y = Q adclrcssli (mod 6}]
`i=0
`
`Ii
`( Q
`
`39
`
`)
`
`Let L be the number of octets in the user PIN. The augmenting is defined by
`
`PIN[U...L -- |iuBD ADDR,,:(i...1nin{5, I5 - L}],
`
`L< ,6
`
`PIN‘ ={
`
`P[N[U...L 11,
`
`’
`
`L = '6»
`
`(EQ40)
`
`where it is assumed that unit B is the claimant. Then, in mode 2. E3 (denoted
`
`E33 ) can be expressed as
`
`E.,:
`_3{
`
`0,1 '3“
`0,1“"’
`}->{
`} Xi
`} Xt
`(PiN', RAND, L’) i—>.4',.(X, Y)
`
`1,2,...,15
`
`0,1 ”"
`1-
`
`(Wm
`
`i5
`
`X = L) PfN'[r' (mod L’)],
`i=0
`
`Y = R/\ND[0... I4] u(R/-\ND[1S] (-BL‘),
`
`and L‘ = min-{ 16, L + 6} is the number of octets in PIN‘.
`
`29 November 1999
`
`Biuetocth Security
`
`AFFLT0293404
`
`Samsung Ex. 1019 p. 176
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 177 of 1082
`
`Baseband Specification
`
`Bluetooth.
`
`BD_/\DDR
`
`43
`
`Figure 14. 15: Key generating aigoril‘i1m E2 and its two modes. Mode 1 is used for unit and
`
`combination keys, white mode 2 is used for KM, and Km_m,_, .
`
`14.5.4 E3-Key generation function for encryption
`
`The cipnering key Kr used by E“ is generated by E3. The function E3 is con-
`
`structed using A',.as follows
`
`E3: {n,1}‘3“x{o,|}”"x{0.I}
`
`_){n’l}1z:<
`
`on
`
`(K, RAND, cor) 1—>Hasi1(K, RAND, cor, :2)
`
`(HQ 43}
`
`where Hash is the hash function as defined by i_ EC: I33}. Note that the produced
`
`key length is 128 bits. However, before use within E”, the encryption key I((.
`
`will be shortened to the correct encryption key length, as described in Section
`
`14.3.5 on page ‘.555. A block scheme of E3 is depicted in :-”-figure 14.16.
`
`The value of COF is determined as specified by equation {EQ 333}.
`
`EN RAND
`
`COP
`
`Link key
`
`128
`
`96
`
`Figure 14.16: Generation of the enoryption key:
`
`Bluelooih Security
`
`29 November 1999
`
`AFFLT0293405
`
`Samsung Ex. 1019 p. 177
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 178 of €332
`
`Baseband Specification
`
`29 November 1999
`
`Bluetooth Security
`
`AFFLT0293406
`
`Samsung Ex. 1019 p. 178
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Base-band Spedficarion
`
`15 LIST OF FIGURES
`
`page 179 of 1032
`
`Bluetouth.
`
`Figure 1.1:
`iiigure 1.2:
`
`Different fiinciicmai biiacke in iiie E?:§i.i£¥T0{3ii‘i system ................. ..¢i~‘i
`
`Piccneis with e eingie sieve er:-ereiicin {e}, a muiii--sieve
`epereiion {is} and a eeetiereei eperetian {Lt}.
`
`iiigure 2.1:
`
`ifigure 2,2:
`
`T30 8i'it'§‘I§i1'ii!":§} ....................................................................... ..
`!\;i=..=iti-sieipackete
`
`634
`
`44
`
`figure 4.1:
`
`Figure 4.2:
`
`i-"ig1.:re 4.3:
`Figure «$.42
`
`Figure 4.5:
`Figure 4.8:
`
`Figure 43?:
`Figure 4.8:
`
`Sieriiiarci packet former. .......................................................... ..4'i’
`Ameee cede fermat
`
`Preembie ................................................................................. ..49
`
`sync were is if {a}, end when PASS
`Treiier in CA0 when M38
`of S}'E’!i'_‘. worrri is ‘i {in}.
`............................................................... .59
`rieeder format.
`......................................................................... .51
`
`Format of the
`{N pacisei fermai
`
`peyicad ..................................................... .136
`...
`
`Peyieed header format fer singie-eiet packets. ....................... ..62
`
`Figure 4.9:
`
`Peyieezi header format for niuiii—sE0: packers. ......................... ..62
`
`Bit»:-eipeiiiion ericciciing scheme. .............................................. ..E~3?‘
`
`Li"-SR generating the {'1.£i,1{}'i shortened Hamming cede.
`
`.
`
`.......E‘>8
`
`Receive protocoi for detei'rnining_3 the ARQN bii.
`
`.’i.
`
`5 5
`
`",2:
`«>
`Figure -).e.J:
`
`:v”v'igLire 5.4:
`
`Figure 5.5‘.
`
`Reireesrnit fiiieririg for packets wi‘ii"‘= CR8.
`Breedrgasst repeiiéien Scheme
`
`a"~"iQure 5.8:
`
`The LFSR icircruii generating Erie wee.
`
`.............................. ..7‘i
`
`Figure 57!:
`
`initiei state efthe HEC generating circuit.
`
`-
`
`Figure
`
`HE-C1 generation and checking.
`
`figure 5.9:
`
`The E.F'SR circuii generatirig Erie CREE.
`
`Figure 5.10:
`
`initia! state of {he CRC generating circuii.
`
`Figure 5.11:
`
`CRC. generation and checkirug ................................................ ..
`
`."-‘figure 731:
`
`Data whitening LFSFR.
`
`Figure 8.1:
`Figme 8.2:
`
`Figure €5.32
`Figure 8.4‘.
`
`i”-figure 9.1:
`
`figure
`
`9.2:
`
`Functienei diagram 0f'¥'X buffer-ing.
`Furictionei diagram of RX brifierirg ......................................... ..
`
`'
`
`Header bit r3roc:e5:ees.'
`
`Payiead bit moceesee.
`
`R><:"T>é cycie of Biueteoih master transceiver in nizrmai mode fear
`eingie-eioi packets.
`
`RXHX cycie of Biueieeth sieve tre_ris»::eiver in rimrrzei merje for
`siriggieeiet perskeis. .................................................................. ..88
`
`Figure 9.3:
`
`RX tizriireg ef siave retiirnirig fmm mid sieie.
`
`List of Figures
`
`29 November 1999
`
`AFFLTD293407
`
`Samsung Ex. 1019 p. 179
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 130 of 1082
`
`Baseband Specification
`
`R><:'?X cycie of Biueteoiri trerisceiver in PAGE mode.
`Figure 9.4:
`Figure 9.5: Timing cf F3-{S packet on etzeeeetsfui page in first hair eier.
`
`Figure 9.6:
`
`“firnirig of F3-E8 packer en successful page in second rzaif eioi. 332
`
`Figure 9.7:
`
`RKFTX timing in muir.i—siave configuration
`
`Figure 3{}.1: Biuetooth ciock.
`
`Figure 10.2: D-erévation 0fCi_i<E
`
`Figure 13.3: Derivation of CLK in master {3} and in sieve {I3}.
`
`.................... ..S}?
`
`Fi§_;ure ‘$0.4: Srete diagram ef BiLse1.ooiii iiiik r.:«::r~.r.rr;iier.
`
`.............................. ..i~38
`
`Figure 19.5:
`
`iierwentionai page {a}. page whiie one SCG iirik present G3},
`page while iwo $00 iénks present ie).
`
`1:33
`
`Figure ‘iilfit Messaging 43? iriitiei connection when sieve responds to first page
`message.
`.............................................................................. ..1fJ5
`
`Figure 10.7’: Messaging at iriiiiei cormeciieri when sieve responds in: secand
`page message.
`Figure 10.8: Generai beacon chennei format
`
`Figure “£0.92 flefinition {sf access winriow .................................................. .. 117
`
`Figure 'i£3.i{}:.¢\c:c:ess procedure appiying the pcsiiing technique.
`
`118
`
`Figure 10.11 fiiieturiaarice :3? access window by 8'00 traffic ...................... .. 118
`
`Figure ’i{3.’i2:Ei<ierir.ied eieep iritervai oi gjarked sieves.
`
`Figure 11.1: Genes‘:-3% i'3IOCi{ diagram of her) eeiectirin scheme.
`
`Figure 11.2: Hep seiectien scheme in CQNNECTSEDN state.
`
`119
`
`128
`
`128
`
`i-“-igure 11.3:
`
`iiiiorgié diagram of her: seieciicirr Kernei far the 753-hop sysierri. 129
`
`Figure 31.4: Siorsx diagrarri of her: eeiectiora kernei for iii-L‘: 234:9; system. 129
`
`Figure 31.5: XOR U§Jei‘8iiOi1fUi‘¥i‘§€% ‘E’ 94109 system. The 23-min system is the
`seme except fer {he .?.'.‘4L':?.»-'i> wire that does not exist.
`............ .. 1 30
`
`Figure 11.6: Fe,-:'muter'irJn operation for {he ‘:79 hop systerri.
`
`Figure ‘iii’: Peimuraiirsn operation for ‘me 23 her: r-zystern.
`
`...................... I/E32
`
`Figure 11.8:
`
`iiiutterfiy impiemerataiicin.
`
`Figure 12.1": Siocir Liiagsem rs? CVSE) encecier with eyiiabéc compandieg.
`
`..14O
`
`Figure 13.2:
`
`ifiieeir iiiagram of C‘-58!} decerier with eyiiabic compandirsg.
`
`.. iii-O
`
`Figure 12.3:
`
`r3~.ccum:.:iarr;r procetiure
`
`Figure 13.1: Formatoi'i3D____fi.CJi."JR
`
`Figure 13.2: Corzeiruciion ofthe syncword.
`
`Figure 13.3: LFSR and the etertirzg state it: gereereie
`
`M?
`
`Figure 14.1: Generation of uriit Frey. When the unit key has been exchanger},
`initieiizerirm key shai! be discarded in both units.
`155
`
`Figure “£4.21 Gerieraiirig; 23 combination key. The mid iink key‘ {K} sh:-1ii be
`discarded after me exr:hange cf 6: new combination key has
`sucaeeiied ............................................................................ .. 155
`
`29 November 1999
`
`List of Figures
`
`AFFLT0293408
`
`Samsung Ex. 1019 p. 180
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 181 of 1082
`
`Base-band Spedficarion
`
`2'-"figure 14.3: Master Eink Key £f§Si?ii)U!§€.}fi and corms 5; tier: of the
`::c:rrs.=s;.>:)nding e::c:'y;3tior3 key.
`
`Bluetouth.
`
`1&9
`
`‘E50
`
`‘E62
`153
`
`figtire ‘£4.42
`
`¥'§g;u2“e ‘$4.5:
`
`Figure 14.6:
`\
`Figure 143?:
`
`Stream ciphering for fsiuemoth with E9.
`Funcfionai deacription <31‘ the encryption 5.:-rocedtsre
`
`silonzzepicsf the encryptissn engine.
`
`Uvewiew of the (2-peratian of the encryption engine. Between
`each star‘; of 3 packet {TX or Fix}, the LFSSRS are
`re--iniiiafiized.
`...
`.
`
`i~“ig1.zr'e 14.8:
`
`Arranging the input 3:: the LFSRS.
`
`%‘?§gua'e 14.9:
`
`Elfistribution of
`
`328 East generated cuiptzt symiaols witim the
`
`Figure 1:3.‘§{}:Chaiienge»-response for the Biuetooth.
`
`Figure 14.1? :Cha%ienge—:‘es;)or=.se fur ayrrametric key systems.
`
`1 Y9
`
`figure 14.1212’:-‘éew sf datafor the comgzutation of El.
`
`..
`
`..
`
`Figtma '24.13:=f3ne round in .4, and
`
`Figme ‘§4.‘i»¢§:E<e;J 5c:?:edu%ing in Ar.
`F we 14.15:Ke~
`9
`x’ Q
`
`enerafin aivorifihm E and its two modes.
`9
`:§
`2
`
`............‘i?'5
`
`Mode 1 is used far unit and ccsrnbinatiean keys. while mode 23 is
`mi!
`mower
`used for K.
`and K
`....................................................... ..’§'?"3’
`
`;*"-igure 1c3».‘i€‘>:(‘:§ersera.«:tir3n ofthe encryption
`
`!.'}’}’
`
`List of Figures
`
`29 November 1999
`
`AFFLTD2934-O9
`
`Samsung Ex. 1019 p. 181
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 182 of €332
`
`Baseband Specification
`
`29 November 1999
`
`List of Figures
`
`AFFLT029341 0
`
`Samsung Ex. 1019 p. 182
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`Base-band Spedficarion
`
`16 LIST OF TABLES
`
`Tame 23%:
`
`flwaiiabée RF channels
`
`page 133 of 1032
`
`Bluetouth.
`
`Tabie 4.1:
`
`Tabie £1.21
`Tabie 4.3:
`
`Tabie 4.4:
`
`Tahie 4.5:
`"£'abEe 4.6:
`
`Tabie 4.3!‘:
`
`Tabie 4.8:
`
`Tabte 4.9‘
`
`Summary of access code types.
`
`Packets defined for SCO and ACE. {ink
`
`FHS payiaard ...............................................
`Desarégvtion of
`Contents ofsfiféeld ................................................................. ..
`
`Clontnantss
`
`filontants of gage scan moxie
`
`Logicai charmei L__CH fietd cantems ....................................... ..
`
`Use of payéoad header flaw bit on the Eogicai charmefis.
`Link control packets .........................
`..................................... ..
`
`Tahie 4.10:
`
`Tabie 4.11:
`
`SE30
`
`.
`
`.«
`
`.
`
`'
`
`'
`
`.
`
`Tabie 10.1:
`
`T:-zbie 10.2:
`
`Tabie 19.3:
`
`Tabie 13.4:
`
`'fabEe 19.5:
`Tabie 10.5:
`
`Tabiea 11.3:
`
`Tame 11.2:
`‘fabie 11.3:
`
`‘fame 11.4:
`
`Tame 12.1:
`
`Tsbie 12.2:
`
`“fabée 14.1:
`
`Tame 14.2:
`
`Tabie 14.3:
`
`Tame 1.4.4:
`
`Tabie 14.5:
`
`Reiaiionship between scan iniervai, i.r'a=.ir: repetéiéon, and paging
`modes R0. R‘: and R2 ............................................................ .191
`
`Reiatimzsluip betwesen train repetitiozu, and fiaging modes R0, R1
`and R2*.evi":e;1SCOiEn%<s are
`
`inétéai messaging dsring start-up.
`
`increase of train repestiticsn when SCO iirsks are ;::res53nt.......... 111
`
`Messaging during inquiry roL.1ti.r*=es."i’32
`
`Mandatory scan periods for P0, P1. P2 scan p-e:'io:s‘ medes.
`
`‘E12
`
`Contwi 0f the btstter'i"iiéas for the 79 E109 systerr:
`
`13'?
`
`€3ontr-.1: of the buiterfiies for the 23 hop system ..................... .131
`‘E34
`
`C:m£2'oi for '?9--hug:
`
`C(m$ro¥ for 23--hog:
`
`E34
`
`‘mice: ending schemes suppoi'ied on the air imerface ............ ..‘E3§3
`
`CV53?) parameter vaiues. The vaiuas are based on a ‘$6 hit
`signed numb:-3-r output from the accumuiator.......................... ..1r-'51
`
`Eniiiies used in authentication and encryption procedures......'i49
`
`Pcssibie traffic svzades fur a siave using a 5errii~-gxerrnanerrt fink
`
`Pcessibie erecrypmm modes for a sieve in pazssessinrz of a master
`key........................................................................................... ..1&3'i
`
`Tm fcaur primitive feedback poiynomiais.
`
`The mappings T, and T3. ...................................................... .465
`
`List of Tables
`
`29 November 1999
`
`AFFLTO29341 1
`
`Samsung Ex. 1019 p. 183
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 184 of €882
`
`Baseband Specification
`
`Tabie 4.4.6:
`
`Tahis: 14.8:
`
`:"~’0iyr~.r3.mia!s used amen creatérwg .
`is
`A33 ;3r;E3m<::né;=:Es are in hexadecimai :m¥aii.«:m. The
`in the 2'§ghtm<3sE positican. .. .. .................................................... ..
`
`‘:3?
`5
`
`Peiynaazaieais used when creating .
`mi poiyawomiais are in hexadecima! noiati-zzn. The LS3 is
`in the rightmost
`
`29 November 1999
`
`List of Tables
`
`AFFLT029341 2
`
`Samsung Ex. 1019 p. 184
`
`

`
`MANAGER PROTOCOL
`
`
`This: pecifi&tion describes the Link Manager
`ol (Lug) which is used for link set-up
`ontrol. §’he signals are interpreted and fil-
`teref out by _he Link Manager on the receiving
`sideiknd ar _not propagated to higher iayers.
`;
`g
`
`-
`
`.%
`E
`
`AFFLT029341 3
`
`Samsung Ex. 1019 p. 185
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 8
`
`page 186 of €332
`
`Link Manager Protocol
`
`29 November 1999
`
`AFFLT0293414
`
`Samsung Ex. 1019 p. 186
`
`

`
`BLUETOOTH SPECIFICATION Version 1.0 B
`
`page 187 of 1082
`
`Link Manager Protocol’
`
`CONTENTS
`
`fiéemzrai ............................................................................................. .3191
`
`Format of Liufii” ................................................................................ ..°’§§2
`
`‘me Prccedure Ruies and P3135 ................................................... ..1§3
`
`3.1
`
`Generai Resgmrgse Messages ................................................
`mjthenticarien
`
`3.2.1
`
`Eliaimani has link key
`
`3.2.2 Ciaimani has no fink key
`
`3.2.3 Repeated
`
`Pairin

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket