US006993615B2
`
`(12) United States Patent
`Falcon
`
`(10) Patent N0.:
`
`(45) Date of Patent:
`
`US 6,993,615 B2
`Jan. 31, 2006
`
`FOREIGN PATENT DOCUMENTS
`
`W0
`
`WO 99/38728
`
`*
`
`8/1999
`
`OTHER PUBLICATIONS
`
`Wall, Holger; Car Radio With A Removable Control Panel;
`WO 99/38728, English language translation; Publication
`date May 8, 1999.*
`pocketnoW.com—RevieW—“Compaq
`Adam Z
`Lein,
`Computer Corporation’s GSM/GPRS Wireless Expansion
`Pack,” Apr. 4, 2002, pp 1-19, printed Oct. 11, 2002.
`Christopher Spera, pocketnoW.com—Review “PDA Mounts
`with a TWist—Arkon Resources’ PDA Multimedia Mounts,”
`Aug. 20, 2001, pp. 1-16, printed Oct. 11, 2002.
`
`(Continued)
`
`Primary Examiner—Glenn A. Auve
`(74) Attorney, Agent, or Firm—Lee & Hayes, PLLC
`
`(57)
`
`ABSTRACT
`
`In accordance with one aspect, a portable computing device
`determines a type of an appliance in which the portable
`computing device is docked. The portable computing device
`identifies, based on the type of the appliance, a user interface
`configuration for the portable computing device, and con-
`figures the user interface of the portable computing device in
`accordance with the identified user interface configuration.
`In accordance with another aspect, a car stcrco includes a
`docking station into which an off-the-shelf handheld com-
`puter can be docked. The car stereo also includes an input/
`output (I/O) component that allows the car stereo to com-
`municate With the handheld computer when the handheld
`computer is docked in the docking station of the car stereo.
`In accordance with another aspect, an appliance in which a
`portable computing device can be docked is an integrated
`vehicle stereo and portable computing device docking sta-
`tion.
`
`24 Claims, 9 Drawing Sheets
`
`(54) PORTABLE COMPUTING
`DEVICE-INTEGRATED APPLIANCE
`
`(75)
`
`Inventor: Stephen R. Falcon, Woodinville, WA
`(US)
`
`(73) Assignee: Microsoft Corporation, Redmond, WA
`(US)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 601 days.
`
`(21) Appl. N0.: 10/295,305
`
`(22)
`
`Filed:
`
`Nov. 15, 2002
`
`(65)
`
`Prior Publication Data
`
`US 2004/0098571 A1
`
`May 20, 2004
`
`(51)
`
`Int. Cl.
`(2006.01)
`G06F 13/00
`(52) U.S. Cl.
`......................... .. 710/303; 381/86; 381/87
`(58) Field of Classification Search ................... .. None
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`11/1993 Canova, Jr. et al.
`5,265,238 A
`3/1996 Harada et al.
`5,497,490 A
`5/1998 Hall et al.
`5,751,548 A
`............. .. 701/36
`8/1998 Beckert et al.
`5,794,164 A *
`1/1999 Ross et al. ................ .. 361/686
`5,859,628 A *
`1/1999 Clark et al.
`5,859,762 A
`2/1999 Yanagisawa
`5,867,406 A
`3/2001 Dietz et al.
`6,196,850 B1
`6/2001 Buckley .................... .. 701/36
`6,246,935 B1*
`4/2002 Buckley .................... .. 701/36
`6,366,840 B1 *
`10/2002 Bates et al.
`6,459,969 B1
`6/2003 Obradovich ................. .. 701/1
`6,577,928 B2*
`9/2003 Knockeart et al.
`..
`701/202
`6,622,083 B1 *
`6,636,918 B1 * 10/2003 Aguilar et al.
`..
`710/303
`2003/0128504 A1*
`7/2003 Enners et al.
`361/683
`2003/0215102 A1* 11/2003 Marlowe ................... .. 381/77
`
`
`
`2oo—\
`
`
`
`mm. my-r
`u2.47
`or/15
`country
`Hyperspead (Q-fume)
`‘Ella Rock
`Prodigy
`Jan
`123Kb9'
`vulumn IIII|IIIIIlII|Jfl|]|Jll|Jll
`
`
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version:
`3.3.1.2
`
`

`

`US 6,993,615 B2
`Page 2
`
`OTHER PUBLICATIONS
`Spera,
`Christopher
`pocketnow.com—ReView—“Still
`Rockin’ Down the HighWay—Arkon’s iPAQ Multimedia
`Pedestal,” Jun. 5, 2002, pp. 1-12, printed Oct. 11, 2002.
`Comworxx Inc. Presents Ready-to-Ship Port-IT(TM):
`Voice-Activated Telephone, Dynamic Navigation and
`
`Hands-Free Information Browsing, Las Vegas, Jan. 8, 2002,
`pp 1-3’ primed Oct’ 11’ 2002'
`Dan Hanttula, SemperAptus.com “The Future of the Pocket
`PC,” pp 1-4, printed Oct. 11, 2002.
`
`* cited by examiner
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 1 of 9
`
`US 6,993,615 B2
`
`106
`
`
`
`APPLIANCE (2)
`
`
`APPLIANCE (1)
`
`102
` PORTABLE
`
`COMPUTING
`DEVICE
`
`
`
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 2 of 9
`
`US 6,993,615 B2
`
`102
`
`140
`
`PORTABLE COMPUTING
`DEVICE
`
`APPLIANCE
`
`DE3CR|PTlON(S)
`
`146
`
`148
`
`150
`
`142
`
`144
`
`152
`
`HO COMPONENT
`
`I/O COMPONENT
`
`CONFIGURATION
`MODULE
`
`INTERFACE
`
`TYPE MODULE
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 3 of 9
`
`US 6,993,615 B2
`
`180
`
`Wed, October 3, 2001
`Owner: Jo Brown
`
`(123) 555-1212
`Noupmnmngapmflmnmnm
`No Unread messages
`1 Active Task
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 4 of 9
`
`US 6,993,615 B2
`
`214
`
`216
`
`216
`
`
`‘B05Rock
`
`
`
`MediaPlayer
`
`
`Hyperspeed(G-force)
`
`01/1502.47
`
`
`
`Prodigy128KbpsJazz
`
`
`VolumeIlIIIlIIIIII||]l]l]l][J|][]
`
`218
`
`(V
`
`9
`
`No
`
`C)
`
`9D
`
`N<r
`
`TCOLON
`
`0
`
`O
`5
`
`NV’
`N
`
` ('\l
`3
`N
`
`88
`N N
`
`/CD
`
`CN
`
` 2/2/2017, EAST Version: 3.3.1.2
` 2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 5 of 9
`
`US 6,993,615 B2
`
`214
`
`252
`
`252
`
`21
`
`216
`
`FM88.5 250
`
`204<%1
`
`202
`
`75%5
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 6 of 9
`
`US 6,993,615 B2
`
`
`
`kiwiEva:
`
`E2300
`
`._oommom.
`
`
`
`Amo._£-oVcomaemnir
`
`5»mo2:0
`
`Nnmamanxmmr
`
`.6_u9n_
`
`
`
`gDaagD=.__..._.._...o:::o>
`
`/Sm
`
` 2/2/2017, EAST Version: 3.3.1.2
`
`2/2/2017, EAST Version: 3.3.1.2
`
`
`
`
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 7 of 9
`
`US 6,993,615 B2
`
`402
`
`404
`
`406
`
`408
`
`412
`
`400
`
`DETERMINE TYPE OF APPLIANCE IN WHICH THE
`
`PORTABLE COMPUTING DEVICE IS DOCKED
`
`IDENTIFY, BASED ON THE TYPE OF APPLIANCE, A
`
`USER INTERFACE CONFIGURATION FOR THE
`
`DEVICE
`
`CONFIGURE THE USER INTERFACE FOR THE
`
`
`
`
`DEVICE IN ACCORDANCE WITH THE IDENTIFIED
`CONFIGURATION
`
`
`
`INPUTS RECEIVED VIA THE USER INTERFACE
`
` PROCESS USER
`
` DEVICE UNDOCKED
`?
`
`YES
`
`
`
`CONFIGURE THE USER INTERFACE FOR THE
`DEVICE IN ACCORDANCE WITH THE UNDOCKED
`
`
`CONFIGURATION FOR THE DEVICE
`
`
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 8 of 9
`
`US 6,993,615 B2
`
`WHEN PORTABLE COMPUTING DEVICE IS
`
`DOCKEO, SEND INDICATION OF THE TYPE OF
`
`442
`
`444
`
`
`
`THE APPLIANCE TO THE DEVICE
` 446
`
`
`RECEIVE USER INPUTS BY WAY OF THE
`
`PORTABLE COMPUTING DEVICE
`
`
`
`
`OPERATE APPROPRIATELY IN RESPONSE TO
`
`USER INPUTS
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`U.S. Patent
`
`Jan. 31, 2006
`
`Sheet 9 of 9
`
`US 6,993,615 B2
`
`500
`
`504
`
`SYSTEM MEMORY
`
`VOLATILE
`
`506
`
`508
`
`516
`
`—
`
`REMOVABLE
`
`STORAGE
`
`NON—REMOVABLE
`
`STORAGE
`
`UNIT NON—VOLAT|LE
`INPUT DEV|CE(S)
`CONNECTlON(S)
`
`|
`
`502
`
`510
`
`514
`
`
`
`PROCESSING
`
`COMMUNICATION
`
`512
`
` 2/2/2017, EAST Version: 3.3.1.2
`2/2/2017, EAST Version: 3.3.1.2
`
`

`

`US 6,993,615 B2
`
`1
`PORTABLE COMPUTING
`DEVICE-INTEGRATED APPLIANCE
`
`TECHNICAL FIELD
`
`This invention relates to computing devices, and particu-
`larly to portable computing devices and portable computing
`device-integrated appliances.
`
`BACKGROUND
`
`Portable computing devices, such as handheld PCs and
`personal digital assistants (PDAs) are becoming increas-
`ingly popular. Such devices provide users with a relatively
`small, portable device that can run various programs. Awide
`variety of such programs exist,
`including entertainment
`programs, reference programs, spreadsheet programs, word
`processing programs, calculators, and so forth. These pro-
`grams allow the portable computing devices to provide
`desired functionality to a wide range of users in a wide range
`of environments and situations.
`
`However, one problem encountered with portable com-
`puting devices is how the user is to use the device in various
`environments. For example, it is relatively easy for a user to
`hold the portable computing device in the palm of one hand
`and activate its functionality with the other hand while
`sitting in a waiting room. Other environments, however, do
`not allow such ease of use. For example, it is generally
`considered unsafe behavior for a user to use both hands to
`operate his or her portable computing device while driving
`a car.
`
`Some solutions to this problem in the car environment
`provide a cradle for holding the portable computing device.
`Such a cradle is typically mounted to the dashboard or some
`other part of the car and has a stand or “gooseneck” that
`allows the device to be positioned so that it can be better
`viewed by the user. While such solutions alleviate the need
`for the user to hold the device in one of his or her hands, they
`still suffer from being cumbersome to the user in the car
`environment.
`
`Thus, an improved way to hold portable computing
`devices is needed.
`
`SUMMARY
`
`A portable computing device-integrated appliance is
`described herein.
`
`In accordance with one aspect, a portable computing
`device determines a type of an appliance in which the
`portable computing device is docked. The portable comput-
`ing device identifies, based on the type of the appliance, a
`user interface configuration for the portable computing
`device, and configures the user interface of the portable
`computing device in accordance with the identified user
`interface configuration.
`In accordance with another aspect, a car stereo includes a
`docking station into which an off-the-shelf handheld com-
`puter can be docked. The car stereo also includes an input/
`output (I/O) component that allows the car stereo to com-
`municate with the handheld computer when the handheld
`computer is docked in the docking station of the car stereo.
`In accordance with another aspect, the appliance is an
`integrated vehicle stereo and portable computing device
`docking station.
`In accordance with another aspect, an appliance having a
`docking station determines when a portable computing
`device is docked in the docking station. When the portable
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`the
`computing device is docked in the docking station,
`appliance sends, to the portable computing device, an indi-
`cation of a type of the appliance. This indication can be used
`by the portable computing device to configure its user
`interface based on the type of the appliance.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The same numbers are used throughout the document to
`reference like components and/or features.
`FIG. 1 is a block diagram illustrating exemplary appli-
`ances in different environments in which a portable com-
`puting device may be docked.
`FIG. 2 is a block diagram illustrating a portable comput-
`ing device and appliance in additional detail.
`FIG. 3 illustrates an exemplary portable computing device
`in additional detail.
`FIG. 4 illustrates an exemplary vehicle stereo while a
`portable computing device is docked therein.
`FIG. 5 illustrates the vehicle of FIG. 4, except without a
`portable computing device docked therein.
`FIG. 6 illustrates another exemplary vehicle stereo with a
`portable computing device docked therein.
`FIG. 7 is a flowchart illustrating an exemplary process for
`changing a user interface on a portable computing device.
`FIG. 8 is a flowchart illustrating an exemplary process for
`operation of an appliance.
`FIG. 9 illustrates an exemplary general computing device.
`
`DETAILED DESCRIPTION
`
`Portable computer-integrated appliances are described
`herein. Each appliance is designed to readily allow a por-
`table computing device to be docked therein. Once docked,
`the portable computing device presents a user interface that
`is based at least in part on the type of the appliance.
`FIG. 1 is a block diagram illustrating exemplary appli-
`ances in different environments in which a portable com-
`puting device may be docked. FIG. 1 illustrates a portable
`computing device 102 and multiple (n) appliances 104, 106,
`and 108 into which device 102 can be docked. Appliances
`104 and 106 are both in the home environment 110 and may
`be, for example, a home entertainment system, an automa-
`tion and/or security system, an environment control system
`(e.g., for controlling a furnace, air conditioner, humidifier,
`etc.), a clock radio, a refrigeration appliance (e.g., refrig-
`erator, freezer, refrigerator/freezer combination, etc.), an
`oven or range, and so forth. Appliance 108 is in the vehicle
`(e.g., car, truck, van, recreational vehicle, boat, etc.) envi-
`ronment 112 and may be, for example, a vehicle stereo or
`entertainment system.
`Portable computing device 102 can be any of a wide
`variety of portable computing devices, such as a handheld or
`pocket computer, or a portable digital assistant (PDA) or
`organizer. Portable computing device 102 may also include
`telephone functionality (e.g., cellular telephone functional-
`ity). Examples of portable computing device 102 include:
`any of the Treo or Visor families of communicators or
`organizers available from Handspring, Inc. of Mountain
`View, Calif.; any of the Palm handheld devices available
`from Palm, Inc. of Milpitas, Calif.; any of the Cassiopeia
`family of personal PCs available from Casio Computer Co.
`of Dover, N.J.; any of the CLIE line of handheld devices
`available from Sony Corporation of America New York,
`N.Y.; any of the Jornada or iPAQ families of pocket PCs
`available from Hewlett-Packard Co. of Palo Alto Calif.; and
`so forth.
`
` 2/2/2017, EAST Version: 3.3.1.2
`3.3.1.2
`
`EAST Version:
`
`2/2/2017,
`
`

`

`US 6,993,615 B2
`
`3
`It should be noted that any of a variety of off-the-shelf
`portable computing devices, such as those discussed above,
`can be used as portable computing device 102. Such an
`off-the-shelf portable computing device may require an
`additional program(s) to be installed thereon to provide the
`functionality of configuration module 144 (and possibly to
`provide at least some of the functionality of I/O component
`142). Such program(s) can be obtained in any of a variety of
`manners, such as downloading the program(s) from a server
`over the Internet, obtaining a pluggable module or card
`including the program(s), and so forth.
`Portable computing device 102 can be docked in a dock-
`ing port of any of appliances 104, 106, and 108. Docking
`portable computing device 102 into an appliance refers to
`physically placing the device into a receptacle of the appli-
`ance. When the portable computing device is both docked in
`an appliance and turned on, the portable computing device
`presents a user interface that is appropriate to that appliance
`as well as the environment that the appliance is in. Depend-
`ing on the type of the appliance in which the portable
`computing device is docked, the portable computing device
`may make additional functionality available to the appli-
`ance.
`
`FIG. 2 is a block diagram illustrating a portable comput-
`ing device and appliance in additional detail. The portable
`computing device 102 of FIG. 2 is the same portable
`computing device 102 as in FIG. 1, and the appliance 140 in
`FIG. 2 can be any of the appliances 104, 106, or 108 of FIG.
`1.
`
`Portable computing device 102 includes an I/O compo-
`nent 142 and a configuration module 144. Appliance 140
`includes an I/O component 146, a type module 148, and a
`docking module 150.
`I/O componcnt 142 includes hardware and optionally
`software and/or firmware that allows portable computing
`device 102 to communicate with appliance 140 by way of
`I/O component 146. Similarly, I/O component 146 includes
`hardware and optionally software and/or firmware that
`allows appliance 140 to communicate with portable com-
`puting device 102 by way of I/O component 142.
`Appliance 140 and a docking station for portable com-
`puting device 102 are integrated, allowing portable comput-
`ing device 102 to be docked into appliance 140. Docking
`portable computing device 102 into an appliance refers to
`physically placing the device into a receptacle (also referred
`to as a docking port or docking station) of the appliance. The
`rcccptaclc may be implemented in a variety of different
`ways, such as a recessed portion of the appliance into which
`the portable computing device can be inserted, a receptacle
`that can be extended for docking of the portable computing
`device but which can be drawn into the appliance when no
`device is docked (e.g., a tray that can be pulled out for
`docking and pushed back in and out of the way when no
`device is docked), one or more clips that are activated to
`hold the portable computing device in place, and so forth.
`In one implementation, when docked in an appliance 140,
`a power connection is established between the portable
`computing device 102 and the appliance 140. This power
`connection can be used to power portable computing device
`102 and thus conserve the battery power of portable com-
`puting device 102. If the battery or batteries of portable
`computing device 102 are rechargeable, this power connec-
`tion can also be used to recharge the battery or batteries of
`portable computing device 102.
`Once docked in an appliance, the I/O components 142 and
`146 can communicate with one another, allowing data and
`commands to be passed between portable computing device
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`102 and appliance 140. The communication link established
`between I/O components 142 and 146 may be implemented
`in a variety of manners, such as by way of signals passed
`through electrical contacts of the portable computing device
`that are in physical contact with electrical contacts of the
`appliance, by radio frequency (RF) signals, by infrared (IR)
`signals, combinations thereof, and so forth. The exact man-
`ner in which signals are communicated between I/O com-
`ponents 142 and 146 can vary by device and appliance, and
`different devices and appliances may support different com-
`munication mechanisms. For example, one appliance may
`support RF signal communication, another appliance may
`support IR signal communication, and the portable comput-
`ing device may support both RF signal and IR signal
`communication.
`When portable computing device 102 is both docked in
`appliance 140 and turned on, portable computing device 102
`presents a user interface which is based at least in part on the
`type of appliance 140 in which portable computing device
`102 is docked. A configuration module 144 identifies the
`type of appliance that portablc computing device 102 is
`docked in, and uses this type information to determine an
`appropriate user interface for portable computing device
`102.
`
`Configuration module 144 can identify the type of appli-
`ance in a variety of different manners. In one embodiment,
`type module 148 of appliance 140 sends a data packet
`including a type identifier over the communication link
`between device 102 and appliance 140. Appliance 140 can
`be pre-programmed with the type identifier (e.g., by the
`manufacturer, seller, or purchaser of appliance 140). Type
`module 148 may send the type identifier to configuration
`module 144 when requested by configuration module 144,
`or alternatively may send the type idcntificr to configuration
`module 144 without being requested to do so by configu-
`ration module 144. The type identifier can be implemented
`in any of a wide variety of different manners, so long as
`portable computing device 102 and appliance 140 both
`know (e.g., are programmed with) the manner in which the
`type identifier is implemented. For example, the type iden-
`tifier may be an eight-bit number, an alphanumeric string,
`etc.
`
`In another embodiment, configuration module 144 relies
`on a more mechanical mechanism for identifying the type of
`appliance. Rather than receiving a type identifier from type
`module 148, portable computing device 102 includes one or
`more sensors. In such an embodiment, appliancc 140 need
`not include type module 148. When portable computing
`device 102 is docked in appliance 140, these one or more
`sensors are positioned to correspond to locations where
`protrusions from appliance 140 may be situated. The pres-
`ence or absence of a protrusion at each location is used to
`identify the type of appliance. The number of locations that
`are sensed depends on the number of different types of
`appliances to be identified. For example, one sensor can be
`used to uniquely identify two (21) different appliance types,
`two sensors can be used to uniquely identify four (22)
`different appliance types,
`three sensors can be used to
`uniquely identify eight (23) different appliance types, and so
`forth.
`
`The sensors can detect a protrusion at a particular location
`in a variety of different manners. For example, the detection
`may be performed optically (e.g., the protrusion may include
`a reflective material that is sensed, or the protrusion may
`break an optical beam and the breaking of the beam is
`sensed), or mechanically (e .g., the protrusions are positioned
`such that docking the portable computing device causes the
`
` 2/2/2017, EAST Version: 3.3.1.2
`3.3.1.2
`
`EAST Version:
`
`2/2/2017,
`
`

`

`US 6,993,615 B2
`
`5
`
`protrusion to actuate a button or tab that closes (or alterna-
`tively opens) an electrical connection that is sensed).
`Each type of appliance is associated with a particular
`environment in which that device is typically located. For
`example, a car stereo is typically located in the car envi-
`ronment, while a refrigerator or home entertainment system
`is typically located in the home environment. By having
`each appliance type associated with a particular environ-
`ment, the portable computing device can be configured to
`present a user interface appropriate to that environment each
`time the portable computing device is docked in that appli-
`ance. If a particular appliance may be used in multiple
`environments, then the user may be requested to select the
`appropriate environment (e.g., the user may be presented
`with a request to select a “home” button or a “vehicle”
`button), or alternatively one of those environments may be
`chosen as the default (which may be subsequently changed
`by the user as a user preference setting).
`Different user interfaces are appropriate in different envi-
`ronments. For example, in the vehicle environment larger
`buttons and text on a display may be more appropriate so
`that it is easier for the driver of the vehicle to see them on
`the display, while in the home environment smaller buttons
`and text may be more appropriate because the user is able to
`spend more time viewing the display (and is not concerned
`with being distracted from driving). Additionally, certain
`functionality may be more appropriate for certain environ-
`ments rather
`than other environments. For example, a
`spreadsheet program may be less appropriate in the vehicle
`environment than in the home environment because of the
`
`typically small size of the cells and cell contents in the
`spreadsheet, while a car stereo user interface would be more
`appropriate for the car environment.
`Configuration module 144 determines the appropriate
`user interface to present to the user based on the type of
`appliance in which the device is docked. In one embodi-
`ment, portable computing device 102 is programmed with
`one or more interface descriptions 152, each description
`describing a user interface for a particular type of appliance.
`Interface descriptions 152 is configured with one or more
`descriptions for each type of appliance into which portable
`computing device 102 may be docked. The interface
`descriptions 152 may be pre-loaded into portable computing
`device 102 by the manufacturer or seller of portable com-
`puting device 102, or alternatively may be added by the user
`of portable computing device 102 (e.g., the user may down-
`load a user interface description in a manner analogous to
`the downloading of software for running on portable com-
`puting device 102).
`Given an identification of the type of the appliance in
`which the device is docked (e.g., identified in any of the
`manners discussed above), configuration module 144
`accesses the interface descriptions 152 and searches for an
`appliance type that matches (e.g.,
`is the same as)
`the
`identified type. The interface description for the appliance
`type that matches the identified type is retrieved and used to
`configure the user interface of the portable computing
`device.
`
`In another embodiment, appliance 140 communicates the
`interface description to be used by portablc computing
`device 102, and appropriate for the environment in which
`appliance 140 is located, to portable computing device 102.
`In this embodiment,
`the user, seller, or manufacturer of
`portable computing device 102 need not be concerned with
`pre-programming portable computing device 102 for each
`possible appliance type the device may be docked in, but
`rather can rely on the appliance 140 to have the interface
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`description and transfer it to portable computing device 102.
`The interface description may be transferred to portable
`computing device 102 each time device 102 is docked in the
`appliance 140, or alternatively portable computing device
`102 may maintain user interface descriptions so that the
`description need only be transferred from appliance 140 to
`device 102 the first time device 102 is docked in appliance
`140. For subsequent dockings, device 102 can obtain the
`user interface description from the record it maintained.
`When docked in appliance 140, portable computing
`device 102 can send control information to appliance 140 in
`order to control the operation of appliance 140. For example,
`the user may enter selections through the user interface of
`portable computing device 102 to control playback of audio
`content (e.g., songs from disc, radio or satellite transmission,
`the Internet, etc.) by an appliance 140 that is a stereo. The
`appropriate commands to carry out the user-entered selec-
`tions are then communicated from portable computing
`device 102 to the stereo.
`
`Portable computing device 102 can also send data to
`appliancc 140 (e.g., operating as an audio source to appli-
`ance 140). The data sent to appliance 140 may be used
`directly by appliance 140 (e.g., MP3 (MPEG Audio Layer 3)
`or WMA (Windows Media Audio) audio data to be played
`back by an appliance 140 that is a stereo) or alternatively
`may be used indirectly (e.g., stored or transmitted else-
`where) by appliance 140 (e.g., data to be sent out by
`appliance 140 over the Internet, data to be communicated to
`a peripheral device coupled to appliance 140, data to be
`stored on a nonvolatile storage device of appliance 140, and
`so forth).
`When docked in appliance 140, portable computing
`device 102 can also make use of any resources of appliance
`140. For example, resources of appliancc 140 may include
`a hard drive, a modem or other network connector (wired or
`wireless) to connect to the Internet, a global positioning
`system (GPS) receiver, and so forth. The resources may be
`internal to appliance 140, or alternatively external (e.g.,
`coupled to appliance 140 via a Universal Serial Bus (USB)
`connector, IEEE 1394 connector, some other public or
`proprietary connector, etc.). Thus, by way of example, if
`portable computing device 102 is docked in an appliance
`140 that is a car stereo, a user interface may be presented to
`the user that lets the user control which music is played back
`by the car stereo (e.g., which radio or satellite channel is tune
`in and played back, or which song from the car stereo’s CD
`player or hard drive is played back), as well as access a GPS
`receiver and display location information to the user.
`Resources of portable computing device 102 may also be
`available to appliance 140. For example, music stored in a
`memory component (e.g., Flash memory) of portable com-
`puting device 102 may be made available to a car stereo for
`playback.
`Various functionality can thus be made available to por-
`table computing device 102 when docked in appliance 140.
`The appliance 140 can operate as an audio (or other data)
`source to portable computing device 102, such as by having
`a microphone for speech recognition, providing audio data
`from a broadcast for recording by portable computing device
`102, and so forth. Storagc devices of appliancc 140 (e.g., a
`hard drive or optical disc drive (such as a CD drive or DVD
`drive)) may also operate as a data source for portable
`computing device 102. For example, GPS or other mapping
`data stored on a CD or DVD may be made available to
`portable computing device 102 by way of the optical disc
`drive of appliance 140. Appliance 140 can also operate as an
`extensible peripheral bus for portable computing device 102.
`
` 2/2/2017, EAST Version: 3.3.1.2
`3.3.1.2
`
`EAST Version:
`
`2/2/2017,
`
`

`

`US 6,993,615 B2
`
`7
`Peripheral devices can be coupled to a bus (or busses) of
`appliance 140 (e.g., USB, IEEE 1394, PCMCIA, etc.), and
`these devices thus made available to portable computing
`device 102 when docked in appliance 140.
`Additionally, appliance 140 is designed to allow portable
`computing device 102 to be docked in appliance 140 and
`blend well with appliance 140. For example, rather than
`having a stand bolted to a car’s dashboard, appliance 140
`docks portable computing device 102 so that portable com-
`puting device 102 blends well with the car stereo. Such
`design improves the appearance of the appliance 140 with
`the portable computing device 102 docked therein, making
`the portable computing device 102 look as if it “belongs” or
`“fits in” to the appliance 140.
`It should be noted that the user interface for portable
`computing device 102 can change (and typically does
`change) as it is used in different types of appliances. For
`example, when the user drives home from work with the
`portable computing device docked in the user’s car stereo,
`the portable computing device presents one user interface.
`When the user gets home and docks the portable computing
`device in his or her home entertainment system, the portable
`computing device presents another user interface. Then,
`when the user is ready for bed and docks the portable
`computing device in his or her alarm clock, the portable
`computing device presents yet another user interface.
`FIG. 3 illustrates an exemplary portable computing device
`in additional detail. In FIG. 3, portable computing device
`102 is in a standalone or undocked environment (that is,
`portable computing device 102 is not docked in any appli-
`ance). An example user interface 180 is shown in FIG. 3,
`including the current date, the name and phone number of
`the owner of portable computing device 102, an indication
`of any upcoming appointments, unread messages, and active
`tasks. A “start” link is also included via which the user may
`select one or more programs to execute (e.g., analogous to
`the Windows® operating system start menu). A user may
`input commands and/or data to portable computing device
`102 by selecting a portion of the user interface 180 (e.g.,
`using a finger or stylus, if portable computing device 102
`includes a touchscreen), or by pressing one of buttons 182,
`184, 186, 188 or 190.
`FIG. 4 illustrates an exemplary vehicle stereo while a
`portable computing device is docked therein. In FIG. 4, the
`appliance that portable computing device 102 is docked in is
`car stereo 200. Although described herein with reference to
`a “car” stereo, it is to be appreciated that the stereo can be
`included in other vehicles as well, such as trucks, vans,
`recreational vehicles, boats, and so forth.
`Car stereo 200 incorporates typical car stereo functional-
`ity, such as: the ability to tune in radio stations (e.g., an
`AM/FM tuner and/or satellite tuner); the ability to play back
`compact discs, MP3 files, or WMA files; a power amplifier;
`radio controls such as channel seek and scan functions; CD
`controls such as play, pause, stop, fast forward, rewind; base
`and treble control; and so forth. Car stereo 200 may include
`all or only some of this functionality (e.g., car stereo may not
`include the ability to play back MP3 files). Car stereo 200
`may also include additional “automotivc PC” functionality,
`such as: a hard drive; peripheral ports; a modem (e.g.,
`wireless) for network (e.g., Internet) access; stereo echo
`cancellation circuitry; microphone
`input circuitry;
`an
`attached microphone; an attached push-to-talk button (e.g.
`allowing input for speech recognition); and so forth. Car
`stereo 200 may include all, none, or some of this automotive
`PC functionality.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`Car stereo 200 includes a source display 202, eight
`channel pre-set buttons 204, a scan channel up button 206,
`a scan channel down button 208, a slot 210 for insertion and
`removal of optical discs (e.g., CDs, DVDs, etc.), an eject
`button 212 for ejecting optical discs, a volume control knob
`214, and two peripheral device connectors 216 (e.g., USB
`ports). As illustrated, portable computing device 102 is
`docked in car stereo 200 such that the user interface display
`of the portable computing device 102 is approximately
`p