throbber
(12) United States Patent
`US 6,255,800 B1
`(10) Patent N0.:
`Bork
`
`(45) Date of Patent: Jul. 3, 2001
`
`USOO6255800B1
`
`(54) BLUETOOTH ENABLED MOBILE DEVICE
`CHARGING CRADLE AND SYSTEM
`
`Primary Examiner—Peter S. Wong
`Assistant Examiner—Pia Tibbits
`
`(75)
`
`Inventor: Stephan Bork, Richardson, TX (US)
`
`(73) Assignee: Texas Instruments Incorporated,
`Dallas, TX (US)
`
`ot1ce:
`* N'
`
`lsc a1mer, t e term 0 t ls
`u ect to an
`yd'l'
`h
`fh’
`Sbj
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. No.: 09/476,986
`
`Jan. 3’ 2000
`Flled:
`(22)
`Int. Cl.7 ........................................................ H02J 7/00
`(51)
`(52) US. Cl.
`............................................. 320/115; 455/463
`(58) Field of Search ............................. 320/115; 455/463,
`455/557, 466, 404
`
`(74) Attorney, Agent, or Firm—Ronald O. Neerings; Wade
`James Brady, III; Frederick J. Telecky, Jr.
`
`(57)
`
`ABSTRACT
`
`A mobile device charging cradle (46) to enable short dis-
`tance wireless communication between a personal computer
`(10) and at least one other short distance wireless commu-
`nication enabled electronic device (50).
`In a preferred
`embodiment of the invention, a short distance wireless radio
`(transceiver—Bluetooth enabled) (44) and antenna (42) are
`added to a charging cradle to produce a combination charg-
`ing and short distance wireless communication enabled
`cradle (46) which is coupled via a data cable (12) to a
`personal computer (10). The short distance wireless (in this
`case RF) communication enabled cradle enables a system in
`which a legacy architecture personal computer may com-
`municate with other short distance RF communication
`
`(56)
`
`References CitEd
`
`enabled electronic devices. Such communication is enabled
`
`U.S. PATENT DOCUMENTS
`
`3/1999 Noble ....................................... 717/4
`5,892,949 *
`
`670237241 * 11/1998 Chipper ~~~~~~~~~~~~~
`34235713
`................. 361/681
`6,028,764 *
`3/1999 Rlchardson et al.
`
`OTHER PUBLICATIONS
`
`“Specification of the Bluetooth System”, Specification vol.
`1, The ad hoc Scatternet for affordable and highly functional
`wireless connectivity, Core, v1.0A, 7/99.
`“WinHec ’99 White Paper”, Windows® Hardware Engi-
`neering Conference: Advancing the Platform, Bluetooth
`Radio System Overview, 4/99, 19 pages.
`
`whetheror not another RF communication enabled portable
`electromc dev1ce ls coupled to the cradle.
`In another
`embodiment of the invention, a universal serial bus USB in
`a computer is used as a power source for the previously
`described cradle. In one embodiment, a data/power cable
`(78) couples a computer (70) having an external USB
`connector (72) to the short distance wireless communication
`enabled cradle (74). The cable includes electronic circuitry
`(82) for converting the voltage level supplied by the USB to
`a voltage level usable by the cradle—including its Bluetooth
`radio (44) and any peripheral electronic device that may be
`coupled to the cradle (52,54).
`
`* cited by examiner
`
`30 Claims, 13 Drawing Sheets
`
`10
`
`©©
`©©
`
`cs
`
`Q
`@o
`\ 12
`
`4‘3
`Kw
`(OI/VJ
`(\K /
`\j\\j
`/>\\|\\\
`44'
`RF TRANSCEIVER
`
`
`
`
`
`
`21-5
`
`22
`
`ANTENNA
`42
`
`38
`
`36
`
`/‘/‘
`
`22
`
`BLUETOOTH ENABLED
`
`45
`CHARGING CRADLE
`
`1
`
`APPLE 1008
`
`APPLE 1008
`
`1
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 1 0f 13
`
`US 6,255,800 B1
`
` 7
`
`FIG.
`
`(PRIOR ART)
`
`
`
`FIG. 2
`
`(PRIOR ART)
`
`28'
`
`2
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 2 0f 13
`
`US 6,255,800 B1
`
`FIG. 3
`
`
`
`
`(PRIOR ART)
`
`FIG.
`
`4
`
`28"
`
`(PRIOR ART)
`
`3
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 3 0f 13
`
`US 6,255,800 B1
`
`FIG. 5
`
`(PRIOR ART)
`
`A3
`
`
`
`BATTERY
`PACK
`
`FIG. 6
`
`(PRIOR ART)
`
`4
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 4 0f 13
`
`US 6,255,800 B1
`
`
`
`FIG. 7
`
`
`
`(PRIOR ART)
`
`1O
`
`26
`
`FIG. 8
`
`(PRIOR ART)
`
`24
`
`
`
`
`
`22
`
`5
`
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 5 0f 13
`
`US 6,255,800 B1
`
`
`
`6
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 6 0f 13
`
`US 6,255,800 B1
`
`
`
`RF TRANSCEIVER
`BLUETOOTH ENABLED
`
`CHARGING CRADLE
`
`%
`\‘
`
`DATA LINES
`
`POWER LINE
`
`M C
`
`RADLE WITH
`BLUETOOTH
`
`10
`
`FIG. 72
`
`
`
`
`42 Q
`
`
`AR 010
`v \ v
`46
`
`
`
`\\
` MOBILE DEVICE
`
`WITHOUT
`BLUETOOTH RADIO
`
` M
`
`
`
`CRADLE WITH
`BLUETOOTH
`
`RADIO cow
`
`45
`
`BLUETOOTH
`
`RADIO
`
`Io
`
`FIG.
`
`7 4
`
`'- __________________ _I
`DATA LINES
`POWER LINE
`
`F]G. 73
`
`48x
`
`
` CRADLE WITH
`
`RADIO
`
`42
`
`42
`
`BLUETOOTH
`
`RADIO
`
`
`
`BLU ETOOTH
`
`m
`
`7
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 7 0f 13
`
`US 6,255,800 B1
`
`
`
`
`
`
`
`
`MOBILE DEVICE
`WITH BLUETOOTH
`RADIO
`
`42
`54
`\\
`
`
`
`
`
`
`CRADLE WITH
`BLUETOOTH
`
`RADIO
`
`10
`46
`
`50
`
`OTHER
`BLUETOOTH
`RADIO
`
`v
`
`42
`
`FIG. 76
`
`8
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 8 0f 13
`
`US 6,255,800 B1
`
`
`
`9
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 9 0f 13
`
`US 6,255,800 B1
`
`68
`
`60
`
`
`
`
`IMAGECOVE
`
`
`
`
`(PAN kSTILL
`
`RV
`
`HID CLASS
`DRIVER
`
`STREAMING
`CLASS
`DRIVER
`
`7
`/HID
`MINIDRIVER
`A
`
`V
`/UDIO
`MINIDRIVER
`A
`
`’VIRTUAL
`COMM PORT
`
`EMULAHON‘
`
`NETWORK TRANSPORT
`PROTOCOLS
`
`(ACCESS
`POINTS)
`
`MINIPORT
`/
`
`STILL IMAGE
`(USER MODE
`COVER)/
`
`COMM
`APPS AND
`OBEX
`
`
`
`USER
`
`KERNEL
`
`7/UETOOTN
`ADVISER
`A
`
`SPEAKER
`
`PHONE
`
`
`
`
`
` 56
`
`////////////////////
`
`////////////////////
`
`
`
`
`
`62
`
`[iicicEEvinEIEEE]
`
`SW
`
`HW
`
` SYSTEM BUS
`
`
`
`
`
`
`
`
`FIG. 78
`
`PC CARD INTERFACE
`AND HOST CONTROLLER
`
`BLUETOOTH LM
`
`BLUETOOTH BASEBAND
`
`USB INTERFACE AND
`HOST CONTROLLER
`
`BLUETOOTH LM
`
`BLUETOOTH BASEBAND
`
`10
`
`10
`
`

`

`US. Patent
`
`JuL3,2001
`
`Sheet 10 0f 13
`
`US 6,255,800 B1
`
`Eoomam
`
`zozomzzoo
`
`oz_._oz<_._
`
`Hmommz<mH
`
`\mm:
`
`150$3.5
`
`mm<>>om<z
`
`322%
`
`no22522
`
`BEG$15
`
`<03
`
`GI
`
`5%)sz
`
`EEO
`
`MOSHE
`
`moEmEE
`
`$355
`
`>>I$15
`
`moEmEE
`
`HmozEEO
`
`o_._25053.5
`
`SEE;
`
`58:35E
`
`
`
` 3E50585%
`
`585%
`
`mofimflé99E
`
`2:E1515053.5
`
`1505315
`
`s:
`
`Eoomam3180535
`
`0542
`
`15055.5
`
`mm:
`
`misEm:
`
`SSEmm:
`
`3.3858
`
`mmmzmo
`
`Eggmam
`
`203
`
`G:on
`
`E<mmj
`
`xofimmm:
`
`50:mm:
`
`3.3328
`
`2252:...mm:
`
`EZWE
`
`11
`
`11
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 11 0f 13
`
`US 6,255,800 B1
`
`
`
`HOST
`
`(ROOT TIER)
`
`
`
`
`
`
`
`,
`
`
`_!_l
`
`1232-- /
`
`TIER 1
`
`
`
`UPSTREAM
`DATA PORT
`
`FUNCTION
`
`UPSTREAM VBUS ———>IrR_E(:ULA;O—R1I
`1 UNIT LOAD (MAX)
`I_ _____ .I
`
`F IG. 2 3
`
`UPSTREAM
`DATA PORT
`
`UPSTREAM VBUS
`5 UNIT LOADS (MAX)
`
`
`FUNCTION
`CONTROLLER
`
`
`
`1 UNIT
`LOAD (MAx)
`FIG 24
`
`
`
`F ‘RE‘G‘ E; 7
`L__EL_A___I
`
`12
`
`12
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 12 0f 13
`
`US 6,255,800 B1
`
`
`
`72G.IF
`
`13
`
`13
`
`

`

`US. Patent
`
`Jul. 3, 2001
`
`Sheet 13 0f 13
`
`US 6,255,800 B1
`
`
`
`7O
`
`26
`
`24
`
`
`
`
`
`I.F
`
`92G.
`
`14
`
`14
`
`
`

`

`US 6,255,800 B1
`
`1
`BLUETOOTH ENABLED MOBILE DEVICE
`CHARGING CRADLE AND SYSTEM
`
`FIELD OF THE INVENTION
`
`The present invention relates to the field of short distance
`wireless communications. More specifically, He present
`invention relates to a method of using a charging cradle to
`enable short distance wireless communication between a
`
`personal computing apparatus and at least one other short
`distance wireless communication enabled electronic device.
`
`10
`
`BACKGROUND OF THE INVENTION
`
`Currently, the most common form of short distance wire-
`less communication between a personal computer (“PC”)
`and a wireless communication enabled electronic device is
`
`15
`
`infrared (“IR) communication. IR communication, however,
`has shortcomings in being a very short distance communi-
`cation technique (typically a few meters at best) and requires
`an uninterrupted line of sight between RF ports on both
`devices. Both of the limitations associated with IR commu-
`
`nication are problematic in the modern world of portable
`electronic devices.
`Another form of wireless communication is radio fre-
`
`quency (“RF”) communication. Some legacy type architec-
`ture computers incorporate an IR port and circuitry to
`support
`IR communication. For short distance wireless
`applications, a legacy type computer can be combined with
`a portable phone (of the type used for short distance com-
`munication around the home or office—a traditional cellular
`
`phone is not acceptable for this purpose due to power,
`frequency and operational expense requirements) via a cable
`or direct connection to give the computer the ability to
`communicate with another electronic device (typically
`another computer) via RF communication from the portable
`phone to a receiver spaced a short distance away. FIG. 1
`illustrates a prior art embodiment of a legacy architecture
`portable computer 10 that is coupled via a cable 12 to a
`portable telephone 14, as required by such a system. Por-
`table telephone 14 provides RF transceiver functionality for
`portable computer 10. FIG. 2 illustrates another prior art
`embodiment of a short distance RF communication system
`in which a legacy architecture portable computer 10 is
`coupled via a data cable 12 to a dedicated short distance RF
`communication module or device 16 (i.e., which is able to
`transmit and receive RF signals over a short distance—e.g.,
`up to 10 meters). RF module or device 16 has an antenna 18
`and RF circuitry 20 (typically transceiver functionality)
`coupled to antenna 18. In both of the systems disclosed in
`FIGS. 1 and 2, there are two electronic apparatus and a
`coupling cable that a user must keep together.
`In addition to the above, portable computer 10, portable
`phone 14 and RF module or device 16 (as well as all
`electronic devices) each require a power source for proper
`operation. While one or more of these devices may derive its
`power solely from batteries, the more common and practical
`practice is to have each device derive its power from
`batteries while the device is in a portable mode and from a
`power cord coupled to a conventional power supply when
`the device is near a permanent power supply. FIGS. 3 and 4
`illustrate the systems of FIGS. 1 and 2, respectively, in
`which portable computer 10, portable phone 14 and RF
`device 16 obtain their power from a power cord 22 coupled
`to a conventional power supply 24 (such as a power
`receptacle—for example, 110 VAC). Devices having an
`input voltage requirement less than the supply voltage may
`also have a step down transformer or voltage reducing
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`circuit 26. For example, a transformer or other voltage
`conversion or regulator circuitry may be used to reduce a
`supply voltage of 110 VAC, supplied by a power receptacle
`on a wall, to the required input voltage of the device. For
`devices requiring DC voltage, an AC/DC converter may also
`coupled between the step down transformer and the device.
`Whether obtaining power solely from batteries, or from
`batteries only when no conventional power supply is
`available, the batteries will eventually run down and require
`replacement unless the batteries are of the rechargeable type
`and are recharged separately or while the device of which
`the batteries are a part is coupled to a conventional power
`supply. Rechargeable batteries may be recharged in one of
`three methods. First, batteries 28 within a portable electronic
`device may be physically removed from the device and
`placed in a battery recharge mechanism 30 until recharged,
`as illustrated in FIG. 5. The batteries are replaced in the
`electronic device after being recharged. Second, batteries 28
`may be recharged within the electronic device it powers (in
`this case portable computer 10, portable telephone 14 or RF
`device 16) via a power cord 22 (typically having a trans-
`former 26 at one end of the power cord—typically the
`portion that plugs into the power source) coupling the
`portable electronic device to a conventional power supply
`24, as discussed above and illustrated in FIGS. 3 and 4.
`Third, batteries within small portable electronic devices,
`such as portable phone 14 may also be recharged within the
`device while the device is placed within a cradle or recep-
`tacle 32 that is coupled, via a power cord 22, to a conven-
`tional power supply 24, as illustrated in FIG. 6.
`Removing a device’s batteries for recharging (as shown in
`FIG. 5) is awkward and burdensome. The electronic device
`using the batteries is typically unusable—if of the battery
`only type—while its batteries are removed. There is also the
`potential problem of losing or damaging the batteries and/or
`the device itself through mishandling of the device or
`batteries and wear resulting from the continual process of
`removing and replacing batteries. If the device is of the type
`allowing operation from a power cord only, the mobility of
`the device is limited to the length of the power cord. The
`method of recharging batteries shown in FIGS. 3 and 4 is
`more convenient than the method of FIG. 5 in that the
`
`batteries are not removed from the device while recharging,
`which facilitates immediate operation of the device, even if
`the batteries are not fully charged. For devices small enough,
`the recharging cradle is the most convenient method of
`recharging. One disadvantage of the charging cradles of the
`prior art is that they require a power cable coupling the
`charging cradle to a dedicated power source, such as a 110
`VAC wall outlet or 12 VDC outlet (such as an automotive
`cirgarette lighter power supply). Such recharging techniques
`are useless in situations where there are no, or insufficient,
`discrete power sources available to plug in the power cord
`of the charging cable.
`FIG. 7 illustrates a cradle 34 adapted to supply both power
`and data to an electronic device 14. In one embodiment,
`shown in FIG. 8, cradle 34 has both a connector for power
`36 and a data connector 38. In another embodiment, shown
`in FIG. 9, cradle 34 has a single power and data connector
`40 for coupling power (via cable 22) and data (via cable 12)
`to the portable phone 14.
`Combining the RF communication and power
`requirements, it soon becomes apparent that a user of any
`one of the previously described communication systems will
`need a portable computer 10, a power cord 22 for supplying
`external power to computer 10, a portable phone 14 or RF
`module 16, a power cable 22 for supplying external power
`15
`
`15
`
`

`

`US 6,255,800 B1
`
`3
`to portable phone 14 or RF module 16, and a data cable 14
`for coupling portable computer 10 to portable telephone 14
`or RF module 16—for a total of two electronic devices, two
`power cords and a data cable. For the recharging cradle
`embodiments—a total of three electronic devices,
`two
`power cords and a data cable are required.
`SUMMARY OF THE INVENTION
`
`The invention disclosed herein comprises a method of
`using a mobile device-charging cradle to enable short dis-
`tance wireless RF communication between a personal com-
`puter and at least one other short distance wireless RF
`communication enabled electronic device. In a preferred
`embodiment of the invention, a short distance wireless radio
`(transceiver—Bluetooth in this example) and antenna are
`added to a charging cradle to produce a combination charg-
`ing and short distance wireless communication enabled
`cradle which is coupled via a data cable to a personal
`computer. The short distance wireless (in this case RF)
`communication enabled cradle enables a system in which a
`legacy architecture personal computer may communicate
`with other short distance RF communication enabled elec-
`tronic devices. Such communication is enabled whether or
`
`not another RF communication enabled portable electronic
`device is coupled to the cradle.
`In another embodiment of the invention, a universal serial
`bus “USB” in a computer as a power source for the previ-
`ously described cradle. In one embodiment, a data/power
`cable couples a computer having an external USB connector
`to the short distance wireless communication enabled cradle.
`
`The cable includes electronic circuitry for converting the
`voltage level supplied by the USB to a voltage level usable
`by the cradle—including its Bluetooth radio and any periph-
`eral electronic device that may be coupled to the cradle.
`Advantages of the above-described embodiments of the
`invention include: elimination of the need to purchase a
`Bluetooth enabled computer in order to enable Bluetooth
`communications between a non-Bluetooth enabled com-
`
`puter and another Bluetooth enabled electronic device;
`elimination of the need to purchase a Bluetooth enabled
`computer in order to enable Bluetooth communications
`between a Bluetooth enabled computer having disabled or
`disabled Bluetooth capability with another Bluetooth
`enabled electronic device; elimination of the need for a
`second power cable when the computer and the cradle are
`used together—saving both cost of acquiring the additional
`power cable and travel space; a reduction from two dedi-
`cated power sources (one for computer and one for the
`cradle) to one (for the computer only); and a convenient way
`to supply power to the cradle from the computer’s batteries
`when no external power source is available for either device.
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The novel features believed characteristic of the invention
`
`are set forth in the appended claims. The invention itself,
`however as well as other features and advantages thereof,
`will be best understood by reference to the detailed descrip-
`tion which follows, read in conjunction with the accompa-
`nying drawings, wherein:
`FIG. 1 illustrates a data cable coupling a portable com-
`puter to a cellular telephone.
`FIG. 2 illustrates a data cable coupling a portable com-
`puter to a dedicated short distance RF communication
`module or device.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`computer to a dedicated AC power supply; and a second
`power cable coupling the cellular phone to a dedicated AC
`power supply.
`FIG. 4 illustrates a data cable coupling a portable com-
`puter to a dedicated short distance RF communication
`module or device; a first power cable coupling the computer
`to a dedicated AC power supply; and a second power cable
`coupling the dedicated short distance RF communication
`module or device to a dedicated AC power supply.
`FIG. 5 illustrates a battery pack being recharged in a
`dedicated battery recharger.
`FIG. 6 illustrates a cellular phone recharging in a cradle
`which itself is coupled to a dedicated power supply via a
`power cable.
`FIG. 7 illustrates a cradle for a cellular phone in which the
`cradle has a first connector coupled to a dedicated power
`supply via a power cable and a second connector coupled to
`a data source (computer) via a data cable.
`FIG. 8 illustrates a system in which a data cable couples
`a portable computer to a cradle upon which a cellular phone
`is resting and recharging; a power cable couples the portable
`computer to a dedicated AC power supply; and a power
`cable coupling the cradle to a dedicated AC power supply.
`FIG. 9 illustrates a system in which a data cable couples
`a portable computer to a cradle having a single data/power
`connector upon which a cellular phone may rest and/or
`recharge; a power cable couples the portable computer to a
`dedicated AC power supply; and a power cable coupling the
`cradle to a dedicated AC power supply.
`FIG. 10 illustrates a system in which a data cable couples
`a portable computer to a cradle having a Bluetooth radio and
`a data connector and a power connector upon which a
`cellular phone may rest and/or recharge; a power cable
`couples the portable computer to a dedicated AC power
`supply; and a power cable coupling the cradle to a dedicated
`AC power supply.
`FIG. 11 illustrates the system of FIG. 10 further including
`one technique for coupling the components within the
`cradle.
`
`FIG. 12 is a high-level block diagram of a system in which
`a data cable couples a personal computer to a cradle incor-
`porating a Bluetooth radio.
`FIG. 13 is the high-level block diagram of FIG. 12 further
`including another Bluetooth radio to which the Bluetooth
`radio in the cradle communicates.
`
`FIG. 14 is the high-level block diagram of FIG. 13 further
`including a mobile device without a Bluetooth radio being
`coupled to the cradle.
`FIG. 15 illustrates the system of FIG. 10 further including
`a non-Bluetooth enabled cellular telephone resting in the
`cradle and being coupled to the cradle’s power and data
`connectors.
`
`FIG. 16 is the high-level block diagram of FIG. 13 further
`including a mobile device incorporating a Bluetooth radio
`being coupled to the cradle.
`FIG. 17 illustrates the system of FIG. 10 further including
`a Bluetooth enabled cellular telephone resting in the cradle
`and being coupled to the cradle’s power and data connectors.
`FIG. 18 illustrates a high level block diagram of the
`relevant portions of personal computer 10 that enable the
`computer to communicate with a Bluetooth radio in a cradle.
`FIG. 19 is a high-level block diagram of the relevant
`elements of a cradle.
`
`FIG. 3 illustrates a data cable coupling a portable com-
`puter to a cellular telephone; a first power cable coupling the
`
`FIG. 20 illustrates a portable computer equipped with at
`least one universal serial bus “USB” connector.
`
`16
`
`16
`
`

`

`US 6,255,800 B1
`
`5
`FIG. 21 illustrates a bus topology for a universal serial
`bus.
`FIG. 22 illustrates a USB cable.
`
`FIG. 23 illustrates a low-power bus-powered function.
`FIG. 24 illustrates a high-power bus-powered function.
`FIG. 25 illustrates a system in which a data/power cable
`couples a portable computer to a cradle having a Bluetooth
`radio and a data connector and a power connector upon
`which a cellular phone may rest and/or recharge and a power
`cable couples the portable computer to a dedicated AC
`power supply, according to another embodiment of the
`invention.
`
`5
`
`10
`
`FIG. 26 illustrates the system of FIG. 25 further including
`one technique for coupling the components within the
`cradle.
`
`15
`
`FIG. 27 illustrates a connector that couples a data/power
`cable to the USB connector of a computer.
`FIG. 28 illustrates a system in which a first data/power
`cable couples a portable computer to a module having
`electronic circuitry, a second data/power cable couples the
`module to a cradle having a Bluetooth radio and a data
`connector and a power connector upon which a cellular
`phone may rest and/or recharge and a power cable couples
`the portable computer to a dedicated AC power supply,
`according to yet another embodiment of the invention.
`FIG. 29 illustrates the system of FIG. 25 in which a
`combined data/power connector replaces the separate data
`and power connectors in the cradle, according to still yet
`another embodiment of the invention.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`
`The communications industry has adopted the Bluetooth
`Specification as a recommended communications technique
`for short distance wireless RF communication applications.
`The Bluetooth Specification can be found at www.Blue-
`tooth.com or www.Bluetooth.net. FIG. 10 discloses a pre-
`ferred embodiment of the invention in which an antenna 42
`
`and an RF transceiver or radio 44 (a Bluetooth radio in the
`preferred embodiment, but could also be any other RF
`transceiver having a low power transmitter capable of short
`distance transmissions of less than 100 m) are added to a
`charging cradle (such as charging cradle 34) to produce a
`combination charging and short distance communication (in
`this case Bluetooth) enabled cradle 46. FIG. 11 illustrates
`one technique for coupling the data cable 12 to a USB hub
`43. USB hub 43 is coupled to radio 44 and to data connector
`38. Power line 22 is coupled to power connector 36 and
`radio 44.
`Short distance RF communication enabled cradle 46
`
`enables a system in which a legacy architecture personal
`computer 10 (to which it is coupled) to communicate to
`other short distance RF communication enabled electronic
`devices. Such communication is enabled whether or not
`
`another RF communication enabled portable electronic
`device is coupled to cradle 46. FIG. 12 is a high-level block
`diagram of a system comprising personal computer 10, data
`cable 12 and cradle 46. FIG. 13 illustrates the high level
`block diagram of the system of FIG. 12 further including
`another short distance RF communication device 50, such as
`a computer system, PDA, keyboard, etc., which can com-
`municate with short distance RF communication enabled
`
`system 48. FIG. 14 illustrates the system of FIG. 13 further
`including a mobile device without a Bluetooth radio 52. In
`this particular embodiment, mobile device 52 is a cellular
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`telephone that includes a transceiver and antenna to com-
`municate with cellular telephone base stations, but is not
`otherwise enabled to communicate with low power short
`distance wireless devices. FIG. 15 illustrates a system imple-
`mentation of the block diagram of FIG. 14.
`FIG. 16 illustrates the system of FIG. 13 further including
`a mobile device with a Bluetooth radio 54. In this particular
`embodiment, mobile device 54 is a cellular telephone that
`includes a transceiver and antenna to communicate with
`
`cellular telephone base stations and includes a transceiver
`and antenna to communicate with low power short distance
`wireless devices. FIG. 17 illustrates a system implementa-
`tion of the block diagram of FIG. 16.
`FIG. 18 illustrates a high level block diagram of the
`relevant portions of personal computer 10 that enable the
`computer to communicate with the Bluetooth radio in cradle
`46. Computer 10 includes a bus driver 56 (one example
`being shown on FIG. 3, page 12, of the WinHEC 99 White
`Page Bluetooth Radio System Overview, hereby incorpo-
`rated by reference). RF Communication 58 emulates a serial
`port to personal computer 10 (or, as an alternative, it can
`interface to the Network Transport Protocols, as shown in
`FIG. 3 of the WinHEC 99 White Page Bluetooth Radio
`System Overview). As a result, a PC application program-
`mer only sees the serial port, not the Bluetooth connection
`that is behind the serial port. Computer 10 also requires
`Bluetooth profiles 60, such as found in the Bluetooth Profile
`Specification, which can be found at www.Bluetooth.com or
`www.Bluetooth.net, hereby incorporated by reference,
`which are applications that insure compatibility between
`devices—not just at the physical layer or protocol layer, but
`compatibility at the application layer so that if, for example,
`data synchronization is required, the computer knows how
`to do data synchronization with mobile device 54 (see for
`example, FIG. 21 in the Profile Stack section on page 171 of
`the Bluetooth Profile Specification). Computer 10 can be
`enhanced by the addition of an application 60 that enables
`the user to configure, control, and use all Bluetooth devices
`that are connected to a computer (e.g., application such as
`Bluetooth Advisor—see WinHEC 99 White Paper submitted
`herewith, or Bluetooth Neighborhood—see also
`www.Bluetooth.net). In the event that computer 10 is to be
`coupled to cradle 46 via a Universal Serial Bus “USB”, the
`computer 10 also requires a USB driver 62 in addition to a
`PC operating system 61, such as Microsoft’s Windows 98.
`FIG. 19 is a high-level block diagram of the relevant
`elements of cradle 46. As with computer 10, cradle 46
`requires a bus driver. If computer 10 is to be coupled to
`cradle 46 via a Universal Serial Bus “USB”, cradle 46 will
`require a USB driver 62. Next, USB driver 62 is coupled to
`HCI 64 (which is a set of commands that describes how the
`cradle communicates with the computer—an example of
`which can also be see in HCI USB Transport Layer—
`addendum to the HCI document—in particular FIG. 1.2 on
`page 753 of the Bluetooth Specification Version 1.08, hereby
`incorporated by reference—or in general Host Controller
`Interface Functional Specification page 516—748, also incor-
`porated by reference). USB driver 62 and HCI 64 (host
`controller I/F for interpreting the Bluetooth software module
`high level commands) are further coupled to a Link Manager
`(carries control
`information exchange between the Link
`Manager master and slave—one example being shown on
`page 77 or the Bluetooth Baseband Specification—see also
`pages 191—244) and a Link Controller 66 (carries low level
`link control information like ARQ flow control and payload
`characterization—one example being shown on page 77 of
`the Bluetooth Baseband Specification and otherwise dis-
`17
`
`17
`
`

`

`US 6,255,800 B1
`
`7
`
`cussed in the Bluetooth Baseband Specification) and to a
`Bluetooth Base Band processor 68 (such as a BSN 6020
`Base Band processor available from Texas Instruments). In
`this particular embodiment of the invention, the Blue tooth
`applications do not run on the phone. For example, on
`computer 10, you can implement an application called
`“Bluetooth Advisor” or something similar. At the control
`panel, you might have an icon “Bluetooth Advisor” which,
`when selected, utilizes a data sync profile to work with a
`service discovery profile, which would list all of the devices
`around computer 10 that are Bluetootli devices. All of the
`Bluetooth software stack below HCI is performed by the
`Bluetooth radio on cradle 46. The software below the host
`controller interface is run on the radio in cradle 46. The rest
`
`is run on computer 10’s processor. The result to computer 10
`is the same as if computer 10 were itself short distance RF
`wireless communication enabled. An advantage of the
`present
`invention is that
`it enables Legacy architecture
`computers (PC without Bluetooth) to now become Blue-
`tooth enabled. It also enables a Bluetooth enabled computer,
`having a defective or disabled Bluetooth capability,
`to
`become Bluetooth enabled.
`
`In a preferred embodiment of the invention, computer 10
`communicates with cradle 46 via a Universal Serial Bus.
`
`FIG. 20 illustrates a portable computer 70 equipped with at
`least one universal serial bus “USB” connector 72. USB
`
`connector 72 is coupled to a USB within computer 70 (not
`shown). Universal serial bus is defined in the Universal
`Serial Bus Specification Revision 1.1, Sep. 23, 1998, incor-
`porated herein by reference. FIG. 21 illustrates a bus topol-
`ogy of the USE. The USB connects USB devices with the
`USB host. The USB physical interconnect is a tiered star
`topology. A hub is at the center of each star. Each wire
`segment is a point-to-point connection between the host and
`a hub or function, or a hub connected to another hub or
`function. There is only one host in any USB system. The
`USB interface to the host computer system is referred to as
`the Host Controller. The Host Controller may be imple-
`mented in a combination of hardware, firmware, or software.
`A root hub is integrated within the host system to provide
`one or more attachment points.
`USB devices are one of the following: hubs, which
`provide additional attachment points to the USB; or
`functions, which provide capabilities to the system, such as
`an ISDN connection, a digital joystick, speakers, etc. USB
`devices present a standard USB interface in terms of the
`following: their comprehension of the USB protocol; their
`response to standard USB operations, such as configuration
`and reset; and their standard capability descriptive informa-
`tion.
`
`The USB transfers signal and power over a four-wire
`cable, shown in FIG. 22. The signal occurs over two wires
`on each point-to-point segment. There are two data rates: the
`USB full-speed signal bit rate is 12 Mb/s; and a limited
`capability low-speed signal mode is also defined at 1.5 Mb/s.
`The low-speed mode requires less EMI protection. Both
`modes can be supported in the same USB bus by automatic
`dynamic mode switching between transfers. The low-speed
`mode is defined to support a limited number of low-
`bandwidth devices, such as mice, because general use would
`degrade bus utilization. The clock is transmitted, encoded
`along with the differential data. The clock-encoding scheme
`is NRZI with bit stuffing to ensure adequate transitions. A
`SYNC field precedes each packet to allow the receiver(s) to
`synchronize their bit recovery clocks. The cable also carries
`Vbus is nominally +5V at the source. The USB allows cable
`segments of variable lengths, up to several meters, by
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`choosing the appropriate conductor gauge to match the
`specified IR drop and other attributes such as device power
`budget and cable flexibility. In order to provide guaranteed
`input voltage levels and proper termination impedance,
`biased terminations are used at each end of the cable. The
`terminations also permit the detection of attach and detach
`at each port and differentiate between full-speed and low-
`speed devices.
`There are also both low and high power bus-powered
`functions. A low power function is one that draws up to one
`unit load from the USB cable when operational. FIG. 23
`shows a typical buspowered, low-power function, such as a
`mouse. Low-power regulation can be integrated into the
`function silicon. Low-power functions must be capable of
`operating with input Vbus voltages as low as 4.40V, mea-
`sured at the end of the cable.
`
`A function is defined as being high-power if, when fully
`powered, it draws over one but less than five unit loads from
`the USB cable. A high-power function requires staged
`switching of power. It must first come up in a reduced power
`state of less than one unit load. At bus enumeration time, its
`total power requirements are obtained and compared against

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