US 20020131445A1
`
`a9 United States
`
`a2 Patent Application Publication (o Pub. No.: US 2002/0131445 Al
`
`Skubic et al.
`
`(43) Pub. Date: Sep. 19, 2002
`
`4
`
`(76)
`
`1)
`
`(22)
`
`SYSTEM AND METHOD FOR ANONYMOUS
`BLUETOOTH DEVICES
`
`Inventors: Janez Skubic, Hasselby (SE); Paul
`Dent, Pittsboro, NC (US); Nils
`Rydbeck, Cary, NC (US); Christian
`Gehrman, Lund (SE)
`
`Correspondence Address:
`JENKENS & GILCHRIST, P.C.
`1445 Ross Avenue, Suite 3200
`Dallas, TX 75202-2799 (US)
`
`Appl. No.: 09/802,095
`
`Filed: Mar. 7, 2001
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/252,828, filed on Nov.
`
`22, 2000.
`Publication Classification
`(51) Int. CL7 oo . H04J 3/16
`(52) US. Clo e 370/465
`67 ABSTRACT
`
`A method and apparatus for enabling anonymous commu-
`nications from a first Bluetooth device to a second Bluetooth
`device is disclosed wherein a temporary identification num-
`ber associated with the first Bluetooth device is obtained and
`used in transmissions from the first Bluetooth device to the
`second Bluetooth device. A temporary identification number
`provides no clear indication of the particular Bluetooth
`communications device transmitting messages.
`
`Generate Temporary D ——350
`
`Transmit Temporary ID
`Responsive to Request
`
`Google Exhibit 1010
`Google v. SecCommTech
`
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 1 of 6 US 2002/0131445 A1l
`
`LSB MSB
`Company_Assigned Company_ID
`72— LAP UAP NAP -6
`f=——24 bits 8 bits —t=—16 bits —
`FIG. 1
`138—~ LAP UAP NAP 1136
`~——24 Random Bits 8 16 Bits ——
`Random
`Bits
`FIG. 8
`
`Generate 32 Random Bits in LAP
`
`and UAP Fields 137
`
`\
`Update Bits in LAP and UAP Fields
`
`as Necessary 141
`Y
`
`Inquiry Process ——142
`Y
`
`Page ——143
`
`FIG. 9
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 2 of 6 US 2002/0131445 A1l
`Bluetooth Fixed Fixed Blugtooth
`Chi hi
`
`Ip 40— ID ID 40 p
`D - - 0 |
`55— Table Table 5525
`B30 30 P
`Algorithm Storage Storage Algorithm
`Bluetooth Device 20 20" Bluetooth Device
`10~ \15
`FIG. 2
`Generate Temporary 1D ~——50
`Y
`Transmit Temporary 1D 55
`Responsive to Request
`FIG. 3
`Generate Temporary ID ~—60
`i
`Generate Access Code ~—65
`i
`Transmit Temporary ID
`and Access Code 70
`Responsive to Request
`
`FIG. 4
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 3 of 6 US 2002/0131445 A1l
`
`Generate Random 1D ~——75
`
`Send lfiquiry Using 80
`Random D
`
`Receive Reply to Inquiry —~—85
`
`Select Service or Device ~—90
`
`Send Request for Temporary g5
`ID
`
`Receive and IllJ)se Temporary 100
`
`End Temporary ID Use ~—105
`
`FIG. 5
`
`Establish Connection Using Random ID |—-110
`
`|
`
`Establish Connection Using Temporary ID —-115
`
`!
`
`Temp ID
`Expired
`?
`
`Replace Temporary ID ——125
`
`FIG. 6
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 4 of 6 US 2002/0131445 A1l
`Temfi;)rory Message Time
`5’ 135/ 140/
`130
`FIG. 7
`Establish First Connection s
`Using Random 1D
`Perform Security Pairing 150
`Exchange Encrypted Non | 155
`Temporary 1D & Index Value
`FIG. 10a
`Generate Pseudo Random ID ——160
`Page with Pseudo Random ID ~—165
`Response +
`17 "
`Additional 475
`Method
`— |
`[
`Establish Connection —~—180
`
`FIG. 10b
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 5 of 6 US 2002/0131445 A1l
`
`Request Temporary ID ~——185
`
`\
`Establish Communication
`Using Temporary 1D
`
`FIG. 11
`
`——190
`
`Broadcast Identity Tokens ~—195
`
`\
`Accept Token ~——200
`
`\
`Establish Communication
`Using Token
`
`FIG. 12
`
`——205
`
`Store Multiple Identifiers —210
`
`\
`Randomly Select Identifiers ~——215
`
`\
`Establish Connection Using
`Randomly Selected Identifier
`
`—220
`
`FIG. 13
`
`
`
`
`
`
`
`
`Patent Application Publication Sep. 19, 2002 Sheet 6 of 6 US 2002/0131445 A1l
`
`Request Temporary ID from Y
`Independent Source
`Receive Temporary ID —230
`Establish Connection ~—-235
`FIG. 14
`Transmit Temporary 1D
`with Inquiry 240
`
`!
`
`Respond to Inquiry Using 945
`Temporary 1D
`
`FIG. 15
`
`
`
`
`
`
`
`
`
`US 2002/0131445 Al
`
`SYSTEM AND METHOD FOR ANONYMOUS
`BLUETOOTH DEVICES
`
`TECHNICAL FIELD
`
`[0001] The present invention relates to Bluetooth devices,
`and more particularly, to the enablement of anonymous
`communications between devices using the Bluetooth com-
`munications protocol.
`
`BACKGROUND OF THE INVENTION
`
`[0002] The Bluetooth communications protocol (Blue-
`tooth is a trademark of Telefonaktiebolaget LM Ericsson) is
`a wireless radio short range communications protocol
`enabling devices such as mobile telephones, computers and
`other electronic devices to communicate with each other
`over short ranges. When communicating using this protocol,
`a Bluetooth radio unit transmits over the wireless link a
`unique identity number that enables other devices to identify
`and address the Bluetooth radio unit. While use of the unique
`identity number is necessary for operation of units using the
`Bluetooth communications protocol, this requirement rep-
`resents a threat to the security and privacy of people that
`carry a Bluetooth device.
`
`[0003] This is due to the fact that the presence of a
`Bluetooth device can be established through identification of
`its unique identity number. If someone can register the
`presence of a specific Bluetooth unit and has also been able
`to identify a particular individual using this device, this
`person may identify through the presence of the Bluetooth
`device that the specific person is present within a particular
`location. In some circumstances this type of identification
`procedure may be highly undesirable. Thus, the need has
`arisen for some method of interaction among Bluetooth
`devices that does not necessarily provide the identity of the
`Bluetooth device, and hence the individual using the device
`is not made readily available.
`
`SUMMARY OF THE INVENTION
`
`[0004] The present invention overcomes the foregoing and
`other problems with a system and method enabling anony-
`mous communications to take place between a first Blue-
`tooth communications device and a second Bluetooth com-
`munications device. In a first embodiment, a first Bluetooth
`communications device generates a temporary identification
`number which is inserted within transmissions from the first
`Bluetooth communications device to the second Bluetooth
`communications device. Other embodiments have the first
`Bluetooth communications device utilizing randomly gen-
`erated identification numbers in order to first establish
`communications with the second Bluetooth communications
`device and then receiving a temporary identification number
`from the second Bluetooth device to support communica-
`tion.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0005] A more complete understanding of the method and
`apparatus of the present invention may be obtained by
`reference to the following Detailed Description when taken
`in conjunction with the accompanying Drawings wherein:
`
`Sep. 19, 2002
`
`[0006] FIG. 1 illustrates the format of a Bluetooth
`address;
`
`[0007] FIG. 2 is a block diagram illustrating Bluetooth
`devices capable of anonymously communicating with each
`other;
`
`[0008] FIG. 3 illustrates a first embodiment of a method
`for the anonymous communication between Bluetooth
`devices;
`
`[0009] FIG. 4 illustrates an alternative embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0010] FIG. 5 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0011] FIG. 6 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0012] FIG. 7 illustrates a message transmitted between
`Bluetooth devices using the method of FIG. 5.
`
`[0013] FIG. 8 illustrates a randomly generated Bluetooth
`address;
`
`[0014] FIG. 9 is a flow diagram illustrating one method
`for generating the random Bluetooth address of FIG. 8.
`
`[0015] FIGS. 10A and 10B illustrate yet a further
`embodiment of a method for communicating anonymously
`between Bluetooth devices;
`
`[0016] FIG. 11 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0017] FIG. 12 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0018] FIG. 13 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices;
`
`[0019] FIG. 14 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices; and
`
`[0020] FIG. 15 illustrates yet a further embodiment of a
`method for communicating anonymously between Blue-
`tooth devices.
`
`DETAILED DESCRIPTION
`
`[0021] Referring now to the drawings, and more particu-
`larly to FIG. 1, where there is illustrated an example of a
`Bluetooth device address (BD_addr) according to the
`present format utilized within the Bluetooth communica-
`tions protocol. A Bluetooth device address has a length of 48
`bits. The LAP (lower address part) 2 and the UAP (upper
`address part) 4 form the significant portion of the BD_addr
`and is completed by the NAP (non-significant address part)
`6. The LAP consists of 24 bits, the UAP consists of 8 bits,
`and the NAP consists of 16 bits to provide the 48 bit address.
`
`[0022] The Bluetooth access code comprises the first part
`of each packet transmitted within the Bluetooth protocol.
`Some of the access codes used in Bluetooth are uniquely
`
`
`
`
`
`
`
`
`US 2002/0131445 Al
`
`determined by the LAP in the Bluetooth device address.
`There are four different types of access codes. The Channel
`Access Code (CAQ) is derived from the Master’s LAP 2.
`The Device Access Code (DAC) is derived from the Slave’s
`LAP 2. The Inquiry Access Code (IAC) can be of two
`different forms but is derived from the special dedicated
`LAP values not related to any specific BD_addr.
`
`[0023] Thus, the CAC and DAC can be used to track the
`location of a specific user. Furthermore, the entire Bluetooth
`address is sent in a special frequency hop synchronization
`(FHS) packet used on certain occasions. The frequency
`hopping scheme in Bluetooth is determined by a hopping
`sequence. The hopping sequence calculation uses different
`input parameters. For the connection state, the LAP and the
`at least four most significant bits in the UAP of the master
`device are used. For the page state, the LAP/UAP of the
`paged unit is used. This makes it theoretically possible to
`obtain information on the LAP and the four most significant
`bits of the UAP based on the observed hopping scheme.
`Significant bits of the master device address in a connection
`may thus be revealed.
`
`[0024] Referring now to FIG. 2, there is illustrated a
`functional block diagram of a system providing anonymous
`Bluetooth communications between a first Bluetooth device
`10 and a second Bluetooth device 15. Each of the Bluetooth
`devices include a Bluetooth chip 20 thereon for enabling
`Bluetooth communications between the first Bluetooth
`device 10 and the second Bluetooth device 15. A number of
`structures and/or algorithms may be implemented within
`each of the Bluetooth chips 20 in order to provide the
`anonymous Bluetooth connection functionality of the
`present invention. However, it should be realized that only
`some of these algorithms and/or structures are necessary for
`implementing the various embodiments described in FIGS.
`2-11, and it is not necessary for each of the structures or
`algorithms to be present. Furthermore, the described algo-
`rithms and structures may be implemented outside of the
`Bluetooth chip 20, if desired.
`
`[0025] Each Bluetooth chip 20 includes an algorithm 25
`enabling the generation of a temporary identification number
`for a Bluetooth device 10, 15 each time the device sends out
`messages or responses including the identity number of the
`Bluetooth device. The algorithm 25 for generating a tem-
`porary identification number may be built into the Bluetooth
`chip 20 of a Bluetooth device 10, 15, downloaded into the
`Bluetooth device 10, 15 or user selected. The particular
`algorithm 25 is not important for the process except to the
`extent of the security and privacy level provided by the
`algorithm. The algorithm 25 must generate a Bluetooth
`identification number which complies with existing and/or
`future identification number formats.
`
`[0026] The Bluetooth chip 20 may additionally include a
`storage area 30 for temporarily storing a temporary identi-
`fication number generated by the algorithm 25. Furthermore,
`an identification table 55 may be utilized wherein temporary
`identifiers for other Bluetooth devices 15 with which a
`Bluetooth device 10 is presently communicating may be
`stored. Finally, a normal fixed identification number 40 is
`stored or associated somewhere with the Bluetooth chip 20
`to be available for operations necessarily requiring the fixed
`identification number.
`
`[0027] As described previously with respect to the algo-
`rithm 25 of FIG. 2, a number of algorithms may implement
`
`Sep. 19, 2002
`
`various methods for providing anonymous Bluetooth com-
`munications between a first Bluetooth device 10 and a
`second Bluetooth device 15. A variety of these methods are
`described with respect to FIGS. 3-15. Referring now to FIG.
`3, there is illustrated one embodiment wherein a Bluetooth
`device generates a temporary identification number at step
`50. The generation of the temporary identification number at
`step 50 may be done on a periodically recurring basis, at
`random time intervals or in response to each transaction
`between the first Bluetooth device 10 and the second Blue-
`tooth device 15. The Bluetooth device 10 transmits using the
`temporary identification number at step 55 responsive to a
`received request for inquiry from a second Bluetooth device
`15. The temporary identification number can be stored
`within the temporary storage area 30 mentioned previously
`with respect to FIG. 2. The temporary identification number
`may also be changed during a transaction period. In this
`case, the Bluetooth devices will exchange the new identifi-
`cation number or instructions on how to generate a tempo-
`rary identification number based upon knowledge of the
`existing identification number.
`
`[0028] Referring now to FIG. 4, there is illustrated an
`alternative embodiment wherein an access code is provided
`along with the temporary identification number responsive
`to a request between a first Bluetooth unit 10 and a second
`Bluetooth unit 15. As in the previous embodiment, the first
`Bluetooth device 10 generates at step 60 a temporary
`identification number for the first Bluetooth device 10. The
`first Bluetooth device 10 also generates at step 65 an access
`code including information about the format and category of
`the temporary identity number. Access codes currently
`defined in the Bluetooth specification may be used. The
`access codes provide for the possibility wherein another
`node can handle alternative ID formats. The node can
`generate alternative ID formats that may not fully comply to
`the standard specification using the access code. Responsive
`to an inquiry or request, the first Bluetooth device 10
`transmits at step 70 the temporary identification number and
`the access code to a second Bluetooth device 15. The
`advantage of this method is that it prepares for the possibility
`that the second Bluetooth device 10 handles alternative
`identification number formats that may not comply fully to
`a standard specification. This capability may not be desirable
`because it reduces general interoperability between units,
`but could be desirable in certain applications having high
`privacy requirements. The access codes currently defined
`within the Bluetooth specification (Bluetooth Special Inter-
`est Group, Specification of the Bluetooth System Version
`1.0B, Volumes 1 and 2, which is incorporated herein by
`reference) can be used for this purpose.
`
`[0029] Referring now to FIG. 5, there is illustrated yet
`another alternative embodiment of the method of the present
`invention. In this embodiment, the first Bluetooth device 10
`initially generates at step 75 a random identification number.
`An inquiry for a particular service or class of device is
`transmitted from the first Bluetooth device 10 at step 80. The
`first Bluetooth device 10 receives at step 85 a number of
`replies to its inquiry. The first Bluetooth device 10 selects at
`step 90 the desired service or device responsive to the
`received inquiries and establishes a connection with a
`selected unit using the generated random identification num-
`ber as the Bluetooth identifier number. Upon the selection of
`the service or device, the first Bluetooth device 10 transmits
`a request for a temporary identification number at step 95 to
`
`
`
`
`
`
`
`
`US 2002/0131445 Al
`
`the second Bluetooth device 15 from which it is requesting
`a service or device. The request still uses the random
`identification number as the Bluetooth identifier number.
`The first Bluetooth device 10 receives and uses a provided
`temporary identification number at step 100 for the length of
`a transaction between the first Bluetooth device 10 and the
`second Bluetooth device 15. At some point during or after
`the transaction, the first Bluetooth device 10 may end use of
`the temporary identification number at step 105. This may be
`in response by the first Bluetooth device 10 to leaving the
`area or expiration of the temporary identification number
`after a predetermined period of time. If the temporary
`identification number expires during a transaction, a new
`temporary identification number may be obtained by repeat-
`ing steps 75 through 100.
`
`[0030] Referring now to FIG. 6, there is illustrated yet
`another embodiment wherein the first Bluetooth device 10
`first establishes at step 110 a connection using a randomly
`selected identification number as the Bluetooth identifier
`number. Use of the random identification number enables
`establishment at step 115 of a connection using a temporary
`identification number as the Bluetooth identifier number as
`described previously with respect to FIG. 5. Inquiry step
`120 monitors for expiration of the temporary identification
`number established at step 115 and upon expiration of the
`temporary identification number, the temporary identifica-
`tion number is replaced at step 125. As shown in FIG. 7, the
`period of time a temporary identification number may be
`active can be established in a message 130 transmitted from
`a second Bluetooth device 15 to a first Bluetooth device 10
`response to a request from the first Bluetooth device 10.
`Included within the message 130 would be the temporary
`identification number 135 and a message time 140 indicating
`the length of time the temporary identification number 135
`is active.
`
`[0031] Referring now to FIGS. 8 and 9, there is illustrated
`one embodiment of a method for generating the random
`Bluetooth address referred to in FIGS. 5 and 6. This method
`utilizes short-lived Bluetooth addresses (BD_addr_active)
`which are chosen at random, but all units also include a
`long-lived Bluetooth address (BD_addr). The active
`address, BD_addr_active, includes the same NAP field 136
`as the BD_addr. The BD_addr_active address is obtained by
`generating 32 random bits at step 137 when a Bluetooth
`module is powered up. The 32 random bits may be generated
`according to any method. These 32 random bits determine
`the LAP 138 and UAP 139 fields within the BD_addr_active
`address. The LAP 138 and UAP 139 fields are also periodi-
`cally updated at step 141 to reselect the 32 random bits.
`
`[0032] Once a random BD_addr_active address has been
`generated, the Inquiry process will proceed in the same
`fashion as currently designed within the Bluetooth specifi-
`cation at step 142 except that the address used within an FHS
`(Frequency-hopping sequence) packet will comprise the
`BD_addr_active address. A first FHS packet will contain the
`BD_addr_active address of the master. Subsequent FHS
`packets may contain the BD_addr of the master transmitted
`in the clear or may alternatively transmit the BD_addr of the
`master in an encrypted format with a certain anonymity unit
`key belonging to the slave. The paging procedure within the
`Bluetooth communications protocol will proceed according
`to the currently defined Bluetooth specification at step 143
`
`Sep. 19, 2002
`
`except that the access code (CAC and DAC), as well as the
`frequency-hopping scheme, are based upon the BD_ad-
`dr_active addresses.
`
`[0033] After an inquiry and page have been done between
`a master and slave units using the BD_addr_active
`addresses, the master unit does not know the BD addr of the
`slave and vice versa. Once a connection has been estab-
`lished, the master and slave units may perform a security
`pairing procedure to enable an encrypted connection to be
`established between the two units so that the BD_addr
`addresses for each unit may be exchanged.
`
`[0034] Referring now to FIGS. 10A and 10B, there is
`illustrated a further embodiment wherein a connection is
`established at step 145 using a random identification number
`from the first Bluetooth device 10. Once a connection
`between a first Bluetooth device 10 and a second Bluetooth
`device 15 is established using the random identification
`number, a security pairing may be performed between the
`two devices at step 150. As a result of the security pairing,
`the Bluetooth devices exchange at step 155 encrypted,
`non-temporary Bluetooth identification numbers and an
`index value. Each Bluetooth unit has its own separate index
`value.
`
`[0035] Later when the first and second Bluetooth devices
`wish to contact each other, a pseudo-random identification
`number is generated at step 160 by the contacting Bluetooth
`device using the non-temporary identification number and
`the index value. The contacting Bluetooth device pages at
`step 165 the other Bluetooth device using the generated
`pseudo-random identification number. The contacting Blue-
`tooth device monitors for a response to the page at step 170.
`Upon receipt of a response to the page, a connection is
`established at step 180 between the Bluetooth devices. If no
`response is received, a connection may be established using
`another method at step 175, for example, the method
`described in FIG. 5.
`
`[0036] Referring now to FIG. 11, there is illustrated an
`alternative embodiment wherein upon entry into communi-
`cation of a first Bluetooth device 10 with a second Bluetooth
`device 15, the first Bluetooth device 10 requests at 185 a
`temporary identification number from the second Bluetooth
`device 15. Upon receipt of the temporary identification
`number from the second Bluetooth device 15, the first
`Bluetooth device 10 establishes communication with the
`second Bluetooth device 15 at step 190 using the provided
`temporary identification number.
`
`[0037] In the embodiment illustrated in FIG. 12, at least
`one Bluetooth device within the system broadcasts identity
`tokens at step 195. When a Bluetooth device desires to
`establish communication with another Bluetooth device, the
`device accepts an identity token at step 200 and establishes
`communications using the identity token at 205.
`
`[0038] Referring now to FIG. 13, there is illustrated yet
`another embodiment wherein a Bluetooth device 10 stores at
`step 210 multiple temporary identification numbers within,
`for example, the storage area 20 described in FIG. 1. Upon
`the need to establish a connection with a separate Bluetooth
`device 15, one of the multiple identification numbers is
`randomly selected at step 215. A connection may then be
`established at step 220 using the randomly selected identi-
`fication number.
`
`
`
`
`
`
`
`
`US 2002/0131445 Al
`
`[0039] Referring now to FIG. 14, there is illustrated yet
`another embodiment wherein a Bluetooth device requests a
`temporary identification number from an independent
`source at step 225. The requesting Bluetooth device receives
`at step 230 a temporary identification number from the
`independent source via, for example, a public wireless
`network or a Bluetooth connection. The Bluetooth device 10
`may then establish a connection at step 235 using the
`provided temporary identification number. Independent
`sources from which the Bluetooth device might receive the
`temporary identification number include, for example, net-
`work server, wireless network server, Internet server, etc.
`
`[0040] Referring now finally to FIG. 15, there is illus-
`trated yet a further embodiment wherein inquiries and
`communications transmitted from a first Bluetooth device 10
`to a second Bluetooth device 240 include a temporary
`identification number with the inquiry or communication.
`The contacted Bluetooth device 15 responds to the inquiry
`using the provided temporary identification number at step
`245 without going through the process of generating or
`obtaining another temporary identification number.
`
`[0041] Utilizing the above described embodiments, a
`Bluetooth device is able to act as an anonymous entity
`enabling communications with other Bluetooth device with-
`out readily providing the identity of the communicating
`device or the user associated with the Bluetooth device. Any
`user identification may be done in a secure fashion on the
`application level independently of the Bluetooth identity.
`Thus, unauthorized individuals may not inappropriately
`determine who is using a particular Bluetooth device.
`
`[0042] The previous description is of a preferred embodi-
`ment for implementing the invention, and the scope of the
`invention should not necessarily be limited by this descrip-
`tion. The scope of the present invention is instead defined by
`the following claims.
`
`What is claimed is:
`
`1. A method for enabling anonymous communications
`from a first device using Bluetooth communications proto-
`col, comprising the steps of:
`
`obtaining a temporary identification number for the first
`device; and
`
`transmitting information including the temporary identi-
`
`fication number from the first device.
`
`2. The method of claim 1, wherein the step of obtaining
`further comprises the step of generating the temporary
`identification number at the first device.
`
`3. The method of claim 2, wherein the step of generating
`further comprises generating the temporary identification
`number using an algorithm.
`
`4. The method of claim 2, wherein the step of generating
`further comprises generating the temporary identification
`number at a Bluetooth chip within the first device.
`
`5. The method of claim 2, wherein the step of generating
`further comprises the step of generating the temporary
`identification number on a periodic basis.
`
`6. The method of claim 2, wherein the step of generating
`further comprises the step of generating the temporary
`identification number at random intervals.
`
`7. The method of claim 2, wherein the step of generating
`further comprises the step of generating the temporary
`identification number at a beginning of a transaction.
`
`Sep. 19, 2002
`
`8. The method of claim 2, further including the steps of
`generating an access code identifying a format of the tem-
`porary identification number.
`
`9. The method of claim 8, wherein the step of transmitting
`further includes transmitting information including the tem-
`porary identification number and the access code.
`
`10. The method of claim 1, further including the step of
`periodically obtaining a new temporary identification num-
`ber to be associated with the first device.
`
`11. The method of claim 1, wherein the step of obtaining
`further comprises the step of receiving a temporary identi-
`fication number from a source located remotely from the
`first device.
`
`12. The method of claim 11, wherein the step of receiving
`further comprises the steps of:
`
`requesting the temporary identification number from the
`remote source; and
`
`receiving the temporary identification number from the
`remote source responsive to the request.
`13. The method of claim 12, wherein the step of request-
`ing the temporary identification number further includes the
`steps of:
`
`generating a random identification number at the first
`device; and
`
`using the random identification number within the request
`
`for the temporary identification number.
`
`14. The method of claim 13, wherein the step of gener-
`ating a random identification number comprises the step of
`randomly generating a portion of bits comprising a Blue-
`tooth address.
`
`15. The method of claim 14, further including the step of
`periodically regenerating the portion of the bits comprising
`the Bluetooth address.
`
`16. The method of claim 13, wherein the step of gener-
`ating a random identification number comprises the step of
`randomly generating 32 bits of the 48 bits of the Bluetooth
`addresses.
`
`17. The method of claim 13, wherein the step of gener-
`ating a random identification number comprises the step of
`randomly generating LAP and UAP fields of a Bluetooth
`address.
`
`18. The method of claim 11, wherein the step of receiving
`a temporary identification number further comprises receiv-
`ing an identity token for use as the temporary identification
`number broadcast from the remote source.
`
`19. The method of claim 18, wherein the identity token is
`substantially continuously broadcast.
`
`20. The method of claim 11, wherein the step of receiving
`further comprises the step of receiving the temporary iden-
`tification number responsive to an inquiry from the remote
`source.
`
`21. The method of claim 11, wherein the remote source
`comprises a non Bluetooth device.
`
`22. The method of claim 11, wherein the remote source
`comprises a Bluetooth device.
`
`23. The method of claim 1, wherein the step of obtaining
`further comprises the steps of:
`
`storing multiple temporary identification numbers within
`the first device; and
`
`
`
`
`
`
`
`
`US 2002/0131445 Al
`
`randomly selecting one of the multiple temporary identi-
`fication numbers as the temporary identification num-
`ber.
`
`24. The method of claim 1, wherein the step of obtaining
`further comprises the steps of:
`
`establishing a first connection between the first device and
`a second device;
`
`exchanging data over the first connection between the first
`and the second devices; and
`
`generating the temporary identification number using the
`exchanged data.
`
`25. The method of claim 24, wherein the data comprises
`a non-temporary identification number and an index value.
`
`26. A method for enabling anonymous communications
`between a first Bluetooth device and a second Bluetooth
`device, comprising the steps of:
`
`generating a temporary identification number at the first
`Bluetooth device using an algorithm within the first
`Bluetooth device;
`
`inserting the temporary identification number as a Blue-
`tooth identification number into messages to be trans-
`mitted from the first Bluetooth device; and
`
`transmitting the messages from the first Bluetooth device
`to the second Bluetooth device.
`
`27. The method of claim 26, wherein the step of gener-
`ating further comprises the step of generating the temporary
`identification number on a periodic basis.
`
`28. The method of claim 26, wherein the step of gener-
`ating further comprises the step of generating the temporary
`identification number at random intervals.
`
`29. The method of claim 26, wherein the step of gener-
`ating further comprises the step of generating the temporary
`identification number at a beginning of a transaction.
`
`30. The method of claim 26, further including the step of
`periodically obtaining a new temporary identification num-
`ber to be associated with the Bluetooth communications
`protocol.
`
`31. The method of claim 30, further including the step of
`inserting a period of time the temporary identification num-
`ber is valid into the message.
`
`32. A method for enabling anonymous communications
`between a first Bluetooth device and a second Bluetooth
`device, comprising the steps of:
`
`establishing a first connection between the first device and
`the second Bluetooth device;
`
`exchanging a non-temporary identification number and an
`index value over the first connection between the first
`Bluetooth and the second Bluetooth devices;
`
`generating a temporary identification number using the
`non-temporary identification number and an index
`value; and
`
`establishing a connection between the first Bluetooth
`device and the second Bluetooth device using the
`temporary identification number as a Bluetooth identi-
`fication number.
`
`Sep. 19, 2002
`
`33. A method for enabling anonymous communications
`between a first Bluetooth device and a second Bluetooth
`device, comprising the steps of:
`
`generating a random identification number at the first
`Bluetooth device;
`
`transmitting a request including the random identification
`number as a Bluetooth identification number to the
`second Bluetooth device;
`
`transmitting a response to the request including a tempo-
`rary identification number from the second Bluetooth
`device to the first Bluetooth device;
`
`establishing communications between the first and the
`
`second Bluetooth devices using the temporary identi-
`
`fication number as a Bluetooth identification number.
`
`34. A method for enabling anonymous communications
`
`between a first Bluetooth device and a second Bluetooth
`device, comprising the steps